Last updated on JULY 13, 2016
Applies to:Oracle Order Management - Version 11.5.9 to 22.214.171.124 [Release 11.5 to 11.5.10]
Information in this document applies to any platform.
AutoCreate Configuration Processor
DRP - Distribution Requirements Planning
When a Parent ATO contains an Option Class of Phantom Source, and this Option contains an Option ATO Model,
the child ATO Model does not get built and is not seen in the BOM for the Parent Model, even though it gets configured and selected in Configurator prior to booking the order line.
Expect the Child ATO which has a Source type of "Operations Pull" to be created as well as the parent ATO.
When the Source Type of the Option Class is changed from "Phantom" to "Assembly Pull", then the Parent Model Star BOM will contain the Child Start Configured items correctly and the Child Model gets billed correctly.
An Option Class should have a supply type of Phantom.
And since the child ATO Model within that option class has a supply type of Operation Pull, configured item for the child should be contained in the Parent star's BOM
So even with an Option Class of supply type phantom, we should see child star item in the parent star's BOM
1. The BOM for the parent ATO Model Item, contains an Option Class (supply type of the option class is Phantom).
This option Class contains the Child ATO Model (supply type is operation pull).
2. Book an Order for the Parent Model
3. Run the AutoCreate Configuration Items program, then the configuration item (star item) for the parent model gets created.
4. Query the BOM for the parent configuration item in BOM. It should contain the configuration item for the child model.
But this does not happen. The BOM of the parent star item does not contain the child star item, so the child star does not get created at all.
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