J Glad I could help. Good luck ______________________________________ Yifat Halili Financial Systems Consultant Exordia - a
division of PricewaterhouseCoopers SA From: Rocco Giumelli
[mailto:[EMAIL PROTECTED] YES, YES, YES, CSV Import sounds like the go. Thankyou From: Yifat
Halili [mailto:[EMAIL PROTECTED] Hi Rocco, I don’t know why the
inventitemlocation table is not populated automatically; all I know is that I
had to populate the table in several of my implementations. I did get clever
and used a csv import into Axapta. This made the process much quicker. It is
easy to populate the spread sheet once you have all the items, the warehouses
and the locations. Also once the inventitemlocation is set
up correctly, creating a stock counting journal is not a problem. If you create
the journal per warehouse then the system locks the items in each respective
warehouse (and location)… I hope this answers your questions.
Basically the inventitemlocation is very important for stock counting in
different warehouses. Regards, ______________________________________ Yifat Halili Financial Systems Consultant Exordia - a
division of PricewaterhouseCoopers SA From: Rocco Giumelli
[mailto:[EMAIL PROTECTED] Hi Yifat Do You Know Why The
InventItemLocation Table Does Not Get Populated automatically, Since in
our environment, the same item crosses dimensions and this InventItemLocation
table remains static, Does Locking the items treat the lock on one warehouse,
or does it apply to all, On our stocktake , I had to forever enter lines in
here that matched the item to the warehouse. and slowed down the Whole
Process, I could not find any documentation on how and especialy why it
does not autopopulate. June 2005 , is coming up quick, and I
would like to see Axapta create entries based on incoming and outgoing
transactions from warehouse dimensions . Ideally a Job that ran just prior
to the priniting of the countiong journals, that made a warehouse item
entry Lock count against each warehouse & item. Thanking you very much. Rocco From: Yifat
Halili [mailto:[EMAIL PROTECTED] Hi there, Rocco is correct, when Axapta creates a
stock sheet it is snap shot of the way the items are at that point in time.
Hence, one should not do any transactions once the stock sheet has been
created, a good idea is to lock the items in the stock count. Axapta cannot
handle movement of stock during the stock count. Another thing to keep in mind is the
unit of measure, make sure that the people are counting in the correct unit of
measure. i.e. the inventory unit of measure. For ease of use, we display the
unit of measure on the counting sheet. Also one needs to consider if you are
using standard costing or average costing. If you are using ave costing, when
you count up, the system takes that stock at a zero cost unless otherwise
specified – i.e. fill in the cost field in the stock counting journal. If
you are using std costing there is no problem. Hope this helps. ______________________________________ Yifat Halili Financial Systems Consultant Exordia - a division of PricewaterhouseCoopers SA From: Rocco Giumelli
[mailto:[EMAIL PROTECTED] Hi Stefan My first experience with Annual
Stocktaking was quite miserable. Firstly I had created my counting journals too
early and the Stock on hand was taken as at the date of printing the journals,
Do not print your journals too early for processing, Duplicate your system and
than print them out so you can get everyone ready. Creating the Counting
jounral on the day of the stock take. In my circumstances , we operate about 15
Warehouses national, and each Item Number must have a cross reference in the item
form, under setup called warehouse items. Each Item number needs to have the
associated warehouse loaded into here so. otherwise axapta locks the item
number against the first warehouse that is processed. I thought this
cross-reference would have been created by the actual transactions for that
item in the warehouse where it has been used. (Otherwise when Stocktake is
processed it keep saying that the item was locked, and it stops the flow) Now I am on Axapta 3.00 sp1 , so I not
sure whether this affects you, but I hope they have solved this problem in the
next release. I am Sure there is other things that I Missed completly, GOOD
Luck! Rocco From: Stefan Heidkamp
[mailto:[EMAIL PROTECTED]
Sharing the knowledge on Axapta.
Yahoo! Groups Links
|