How to Avoid the Grouping of Material Requirements From Different Phantom (Doc ID 2100430.1)

Last updated on JANUARY 27, 2016

Applies to:

Oracle Work in Process - Version 12.1.3 and later
Oracle Bills of Material - Version 12.1.3 and later
Information in this document applies to any platform.

Goal

Per business requirements, we would like to see component requirements by BOM structures.
For example, there is an assembly A1 having three phantom components (B1,B2).
Item C1 is a component which is used under all of the three phantoms B1,B2. And B1,B2 are on the same operation (Op. #10) of assembly A1.

[BOM of Assembly A1]
Operation Seq Num   Component Item
10                              B1 (Phantom Item)
10                              B2 (Phantom Item)


In this scenario, we would like to see three component requirement lines, which is derived from B1 and B2 separately.
But per our test, Oracle WIP will automatically group these requirements to one requirement line on the job with summarized requirement quantity. How to let system not group material requirements from different phantom?

[Background]
It seems that the program group component requirement from these three phantom items together and combine into one requirement line.

In the table WIP_REQUIREMENT_OPERATIONS, there is a column COMPONENT_SEQUENCE_ID recording the source BOM structure ID from which WIP explosion procedure works. Actually, WIP should record all three component sequence id and its actual required quantity in base table and group the requirements in view.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms