Excess Quantity In A Planned Order Is Generating And Getting Pegged To Order Type Expired Lot Demand
(Doc ID 2459328.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Advanced Supply Chain Planning - Version 12.2.5 and later
Information in this document applies to any platform.
On : 12.2.6 version, Constrained Planning in All instances
users are on 12.2.6 and have applied patch 26969891 - 184.108.40.206 - Mandatory Cum Patch for 12.2.6 / R12.SCP_PF.C.Delta.7 - they are using 64 bit Linux MSONWL64.ppc with version MSONWL64.ppc 120.15.12020000.80 from 12.2.6 cum patch #2 27754021
They see Order Type = Expired Lot Demand getting generated and they're not understanding its function and believe it's creating excess demand and desire more information on how this example they have works. Example data:
item = XX-12670
Org = ZZ:332
Fixed Ord qty = 18
There's a planned order qty = 18 due 27-OCT-2018
The only actual demand is for qty = -3.6 also due on 27-OCT-2018 for planned order demand. There are no other demands for this item except it shows Order Type = Expired Lot qty = -14.4 due 25-APR-2019 which apparently is the the expected expiration for the balance of the planned order.
Users don't believe the Expired Lot Demand should be created at all
The issue can be reproduced at will with the following steps:
1. Create items with shelf life days and order modifiers
2. Run data collections and ASCP plan
3. Find that when there's excess left over supply that a demand called Expired Lot Demand is generated and shown in the ASCP workbench
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