HI Anthony,
First, please disregard Steve_IFS comment… he is looking at this from an IFS Apps or IFS Cloud perspective. These are different products from Alliance which is the subject of this forum.
Second, Andrew basically already confirmed your question and you as well. The ‘FIFO’ is not specifically on each individual part but relates to the last time the bin received that product. Specifically per the Andrew’s code review:
If not, it will try to allocate the remaining qty using FIFO based on the last_rec_date on the bins matching the product/warehouse/inventory type/owner company.
So, if you are looking for last receive date for every part received into the warehouse, this is not captured directly though may be retrieved I suppose from the logistics transaction table which would increase resource overhead to try to find all the matching records to review the logistics transaction date.
It is more like the name of the option which is Automatic Multi-Bins Allocation and is supposed to grab from the oldest receive date into the bin if the current defined bin does not have enough parts.
In addition, if the parts are not items, it would be impossible I would think to assure the picker takes the oldest non-item part from a bin (unless they really organized oldest to newest physically in the bin somehow) as you have nothing to link the individual part to a specific receiving.
To confirm, any receiving (misc. receive is included) into a bin resets the last received date of the bin and it is no longer considered the oldest bin to grab the oldest parts from other bins containing matching parts. The requested functionality is a RFE and would require a billable change request as the Alliance product is in support only mode in its lifecycle with no further functionalities added to standard.
