Hi,
Details:
I am working on Ax 2009
Application version: 5.0.1500.1313
Kernel version: 5.0.1600.3090
It has Process manufacturing add on installed on it.
Question:
In Inventory model group, Date-controlled is Checked
Inventory model is FIFO
As per the documentation for Ax 2012 with similar setup
https://technet.microsoft.com/en-us/library/aa571170.aspx
Purchase order line |
Item number |
Batch number |
Quantity |
Ship date |
---|---|---|---|---|
1 |
A |
1000 |
5 |
February 2, 2012 |
2 |
A |
1001 |
3 |
January 1, 2012 |
3 |
A |
1002 |
7 |
March 3, 2012 |
If the Date-controlled check box is selected and the Backward from ship date check box is cleared, batch 1001 is reserved because it is the batch with the first date of receipt (FIFO).
This works fine.
But if we try with Transfer order for a warehouse it fails.
Movement Journal for Warehouse 21
Movement Journal |
Item number |
Batch number |
Quantity |
Ship date |
---|---|---|---|---|
1 |
A |
1000 |
5 |
January 1, 2012 |
2 |
A |
1001 |
3 |
February 2, 2012 |
3 |
A |
1002 |
7 |
March 3, 2012 |
Transfer Order from Warehouse 21 to 11
Transfer Order |
Item number |
Batch number |
Quantity |
Ship date |
---|---|---|---|---|
1 |
A |
1000 |
5 |
May 1, 2012 |
2 |
A |
1001 |
3 |
April 2, 2012 |
3 |
A |
1002 |
7 |
June 3, 2012 |
If the Date-controlled check box is selected and the Backward from ship date check box is cleared, batch 1000 is reserved and not 1001.
I was expecting batch 1001 to be reserved based on FIFO for the Warehouse 11.
Please suggest if I am missing anything.
Regards,
Rajat
*This post is locked for comments
Hi Fredrik. thank you for your reply.
The date control is checking the last date on the inventTrans record, meaning a warehouse movement or transfer actually makes it update this date and seem newer. Yes... It's a feature, not a bug... But I agree it is not what it seems. Does really a warehouse transfer mess this up?
The best solution is FEFO...
Or...
What we solved this with on a customer of mine was that we used a generated batch number on all receipts and used the date or PO as the batchnumber. Then we picked the first alphanumeric number at picking. This giving it a fairly structured sequence which picked the oldest first, no matter the amount of inventory transfers or warehouse.
Hello Rajat,
I have same problem too.
Did you find any solutions for this?
Thanks
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,188 Super User 2024 Season 2
Martin Dráb 230,030 Most Valuable Professional
nmaenpaa 101,156