My Oracle Support Banner

Want Outbound FIFO Break And Remaining Shelf Life Validation During Wave Allocation (Doc ID 2555974.1)

Last updated on MARCH 12, 2021

Applies to:

Oracle Warehouse Management Enterprise Edition Cloud Service - Version 18 and later
Information in this document applies to any platform.

Goal

Client needs to comply with food industry standards related to expiration
date & minimum shelf life. They want to ensure that "FIFO break" and
"Remaining Shelf-life" validations are covered in their Outbound Warehouse Flow.

FIFO Break for Outbound implies guaranteeing that any allocation of stock to
a sales order is not of an earlier expiry date than the previously shipped to
a customer. The allocation of stock-to-order preceding the picking execution
is defined as the critical point of prevention. FIFO Break configuration
should also be flexible enough to manage manual intervention in the cases
where customer accepts exceptions.

Remaining shelf life would work similar to the Remaining shelf life
validation in inbound. The system would use each item’s defined shelf life on
the item master, remaining shelf life on the inventory and validate by the
ship to company’s acceptable remaining shelf life threshold. If the inventory
expires before the acceptable threshold, it should not be selected and
another inventory should be selected. Remaining Shelf life configuration
should also be flexible enough to manage manual intervention in the cases
where customer accepts exceptions.


FIFO Break Example:

Variables Record
Customer:  CustName
Destination STORE_001
SKU / Reference ITM_00010
Last Lot Shipped LOT_0951
Last Exp.date shipped 8-May-2020

For Customer CustName with destination Store_001, the last recorded shipping of the
SKU: ITM_001 belong to LOT_0951 with an expiration date of 8-May-2020

This means that the next time client receives a sales order for CustName / Store_001,
the stock allocated for SKU: ITM_001 should not be of an earlier expiration date than 8-May-
2020 (allocated stock to the order >= 8-May-2020)

Remaining Shelf-life example:

Variables Record
Customer  CustName
Minimum Shelf-life 50% of product life
Shelf Life (Days) 365

Remaining Shelf-life definition:
Validation that the stock allocated to an order complies with the minimum remaining shelf-life
days determined by the customer. Remaining shelf-life days is defined for each ship to
company.

LPN Expiry Date (DD/MM/YYYY)
LPN1 01/10/2019
LPN2 10/12/2019
LPN3 30/12/2019

Bearing in mind the data in the above 2 tables, let us assume that if a wave is run on 10 June
2019 (10/06/2019) for Ship to Company = CustName, which has an acceptable shelf life
% of 50%, then by FEFO Logic, LPN1 should have been selected as it expires first, but due to
customer shelf life check, LPN2 should be selected, as its expiry date is (365*P) after the
current date.

In summary, want to have a functionality during wave allocation that would check for
the above mentioned FIFO break rules and Shelf life validation.
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.