My Oracle Support Banner

ASCP Not Exploding The Components In a BOM - Looping in Source Data Found In MSCNSW - Snapshot Worker (Doc ID 1083422.1)

Last updated on FEBRUARY 04, 2022

Applies to:

Oracle Advanced Supply Chain Planning - Version and later
Information in this document applies to any platform.

Executable:MSCNSP - Memory-Based Snapshot
ConcurrentProgram:MSCNSW - Memory-Based Snapshot Worker


Users run unconstrained plan with many organizations. However they have run into a problem we believe is a data issue and not a code issue and we need help finding the problem. They have a 25 level bill of material for a particular item and this was planning just fine until this past Saturday, 20-MAR-2010, all the way down. Then at this point, about 10 levels down there's a Make subassembly that stopped planning at that level and the balance of the BOM for 15 levels below it does not explode/plan. All the other parts at the same level as the problem sub assembly plan as expected.

If they release a wip discrete job for the next higher assembly above the problem sub assembly, then they do get wip discrete job demand for the problem item and all the way down the BOM to satisfy that particular WIP job. However there are many more planned orders for the next assembly that have not yet been released.

We found in the MSCNSW - Memory Based Snapshot Worker log a huge loop that's probably 10 pages long and includes the problem subassembly in the looping. 

Please note that profile option MSC:Prevent Loops when pegging Non-Standard Jobs = Yes

1. Responsibility : Advanced supply chain planning
2. Responsibility : Supply chain planning  Workbench
3. One of the child item is not planned in parent items bill


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

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