Troubleshooting
Problem
How does Yantra (hard/soft) allocate demand against FEFO time sensitive inventory supply
Symptom
Description:
------------------
This solution deals with the concept
of FEFO and how Yantra allocate Demand against Supply in case of time sensitive
items.
=========================================================
P
ART: Distributed Order Management 7.3 HF 23 Platform
PRODUCT:
<None>
COMPONENT: <None>
OS: Windows XP - Not Applicable
DATABASE:
Oracle - 9.2.0.6
WEB SERVER: WebLogic - 8.1 SP3
WEB BROWSER: Internet
Explorer - 6.0 sp1
===============================================
Cause
Resolving The Problem
shipByDate:
This can be looked in as an expiration date of an
item. While adjusting inventory we can give shipByDate for that set of
inventory which we are adjusting. If the shipByDate is not provided then Yantra
calculates it as:
-- "today + item's default expiration
days", for Supply Type of type Onhand
-- "ETA + item's
default expiration days", for Supply Type of type other than Onhand. (ETA =
Estimated Time of Arrival)
minShipByDate:
This is an
orderline attribute. If minShipByDate is specified in the orderline then Yantra
will allocate (Soft-matching) the Demand against Supply with
ShipByDate >= minShipByDate.
This is valid only for time sensitive
items. Business use case for this is:
Say the inventory picture is like
this:
ItemID ShipByDate
----------
-------------------
ITEM01 12/10/2005
ITEM01 12/20/2005
Now
if we place an order on 12/05/2005, Yantra will allocate DEMAND against Supply
with ShipByDate as 12/10/2005. But due to some constraints we know that we
won't be able to process the order by 12/10/2005, in this case we can override
this by providing minShipByDate of 12/11/2005 (say). Now Yantra will allocate
against Supply with ShipByDate as 12/20/2005.
For more information about
minShipByDate please refer to Ch-9.2.1.3 - Product Concept Guide.
So
this way whenever an order is created/scheduled/released it is soft allocated
according to FEFO.
The option of NOT selecting inventory according
to FEFO comes into picture only when we are confirming a shipment.
There
is a flag in inventory rules (Applications -> IS -> Inventory Rules -> Other
Rules)
"Assume FEFO if no 'Ship By Date' is provided"
This 'Ship By
Date' is a shipmentline level attribute and is mandatory for time sensitive
items. While confirming shipment, Demand is hard-allocated against Supply with
shipByDate = 'Ship By Date' (provided at the shipmentline level).
But if
above flag is checked then 'Ship By Date' is not mandatory and Demand is
hard-allocated against Supply according to FEFO.
Say in the above
example if the 'Ship By Date' = 12/20/2005 then Demand will be hard allocated
against Supply with shipByDate = 12/20/2005, otherwise (if above flag is
checked and 'Ship By Date' is not provided) Demand will be hard-allocated
against Supply with shipByDate = 12/10/2005.
Historical Number
PRI49632
Product Synonym
[<p><b>]Fact[</b><p>];
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21537090