Not Able To Backflush Phantom Components From More Than One Subinventory (Doc ID 1671521.1)

Last updated on MAY 15, 2016

Applies to:

Oracle Bills of Material - Version 12.1.3 and later
Information in this document applies to any platform.
phantom assembly, Backflush Subinventory/Locator

Symptoms

 

PROBLEM STATEMENT
=================
There BOM structure where one phantom assembly is used for more than one product line.

Each product line has a different backflush subinventory.

When the phantom is structured to the final assembly BOM, the WIP job that gets created, it is standard functionality that the Phantom item is not part of the WIP job.

It's the phantom components that are seen on the job.

In this scenario, the WIP job shows the backflush subinventory/locator information that is entered on the components on the phantom BOM.

This doesn't allows use of the phantom assembly across product lines, which is one of the main ways a Phantom can be used.

It seems like it would be a very common practice, so would assume that there's standard functionality somewhere that would allow us to identify the Backflush Subinventory/Locator if, say, the subinv and locator were identified for the Phantom Item in the Final Assembly Bill of material.

 

Cause

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