Last updated on NOVEMBER 15, 2016
Applies to:Oracle Advanced Supply Chain Planning - Version 12.2.4 and later
Information in this document applies to any platform.
On 12.2.4 Memory Based Planner in Test:
Users have applied VCP Cum Patch 22.214.171.124 - 19549533. They run an unconstrained ASCP plan and they use Lots with Shelf Life Control (Lot Expiration or sometimes known as Lot Expiry). They state that in the plan horizon they see Expired Lots creating gross requirements at the date they are expiring. Users are not expecting this to show up as demand and believe that planned orders are being created to satisfy the Expired Lots. Example data:
Item = JMExpire
Org = TST:M1
Safety Stock = 53 (Hard INV setup)
On hand = 1392
On hand qty = 700 expires 15-FEB-2016
On hand qty = 692 expires 15-MAR-2016
Forecast and Sales order demand totals 760 out through 19-OCT-2015 and there's no further demand. This leaves PAB = 632 until 15-FEB-2016 which is where qty = 357 on hand expires. This is shown as a gross requirement and drops PAB from 632 to 275. Then on 15-MAR-2016 the balance of qty = 275 on hand expires and is shown as a gross requirement and takes PAB to 0. However since safety stock = 53, a planned order is generated here for qty = 53 which then shows PAB for this bucket = 53 to match safety stock.
The 'Expired Lot' demands being shown as gross requirements are not demands that the customer expected. Because of this, they believe excess supply is created.
The issue can be reproduced at will with the following steps:
1. Run ASCP plan with on hand that will expire in the future
2. Review plan out , for orders 'Expired Lot'
3. Users see Expired Lots being shown as gross requirements
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms