Link Between Internal Sales Order and Internal Requisition Lost Resulting In Excess Planned Order Demand After Collections And ASCP Plan Run
(Doc ID 1523689.1)
Last updated on FEBRUARY 01, 2019
Applies to:Oracle Advanced Supply Chain Planning - Version 12.1.3 to 188.8.131.52 [Release 12.1]
Information in this document applies to any platform.
12.1.3 instance and users have applied VCP 184.108.40.206 Patch 13833266. They are using 64 bit Linux MBP MSCNWL64.ppc 120.3.12010000.223 which came from 220.127.116.11 patching so no one offs against MBP at the moment. Users are running an Unconstrained ASCP plan. We are seeing issues where ORG PRD:M1 (demand org) is ordering parts from our distribution facility PRD:M2 (supply org) and the internal requisition has created an internal sales order. The problem is that ORG PRD:M2 shows additional Planned Order Demand pegged to the same internal requisition that has been released and internal sales order created. We cannot find the order number referenced in the planned order demand record in the ASCP workbench and believe ASCP is planning excess demand in supply org PRD:M2.
item = JMINT
Org = PRD:M1 - demand org
Org = PRD:M2 - supply org
Users released a planned order qty = 4 due 28-DEC-2012 in Org M1 which became internal requisition number = 20000124
This internal requisition then generated internal sales order 50000040 qty = 4 in Org = M2 due 28-DEC-2012
So far all is well. Collections was run and the ASCP plan. However there's still planned order demand qty = -4 due 28-DEC-2012 in Org = M2. This pegs back to the Internal Req = 20000124 in Org M1 and then to excess. The internal requisition in Org M1 pegging shows it also pegging to the planned order demand in Org M2 and then pegging to on hand. The internal sales order in M2 pegs to on hand.
We confirmed with screenshots that the IR and ISO are linked together in the source instance. We can't explain why this lone planned order demand is still out there in M2. It should've been replaced by the ISO that did get created. This makes demand look overstated in Org M2
Issue seems to be intermittent as they only found a few examples.
1. Run unconstrained ASCP plan
2. Release planned orders to create IR's and also generate ISO from same
3. Run collections to pick up the change
4. Run ASCP plan and review 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