Suggested by Laurens van der Tang – New
In the location directive, you can configure the strategy "Location aging FIFO" for picking. The system checks the aging date of the location. However, the aging date is updated whenever you move a license plate into a location. The disadvantage is that if you add multiple license plates with different items to a location, the aging date gets updated each time a license plate is added. Let me explain with the following example:
- Item X001 is in location A001 with LP001 dated 1-05-XXXX.
- Item Y002 is in location A001 with LP002 dated 1-10-XXXX.
- Item X001 is in location A002 with LP003 dated 1-07-XXXX.
- Item Y003 is in location A002 with LP004 dated 1-09-XXXX.
In the above scenario, the aging date of location A001 is 1-10-XXXX, and the aging date of location A002 is 1-09-XXXX. If you release a sales order or transfer order for item X001 for picking, Dynamics will propose picking from location A002 because its aging date is older than that of location A001, even though the license plate of item X001 in location A001 is older than that in location A002.
It would be very helpful to have an additional location directive strategy that checks the aging of the license plate in combination with the item, rather than just the aging date of the location.
This is an absolute need for many of my clients who would like to FEFO/FIFO pick but do not have the space to allow for only one item per location and do not require batch management.