Invoke Oracle Configurator from within Oracle Bills of Material to create a configured bill of material and routings for a predefined ATO item. This is useful in a business to business environment where the same configuration is ordered repeatedly. Preconfigured items can be built to forecast and kept on hand. Customers can order the preconfigured items directly, as they would a standard ATO item.

Preconfigure BOM respects the new organization level BOM parameter Create Configuration BOM. An error message displays if you try to preconfigure in an organization where this parameter is set to No.

You can preconfigure multilevel structures within BOM in a manner similar to that done in Order Management. The configurator uses the item validation organization defined in the OM parameters form for the current organization to determine the BOM to present during the configuration session. Once the options are chosen, the sourcing rules on the models, the setting of the Create Configuration Item, BOM, and Routing attribute, and any Option Specific Source definition are used to determine the organizations in which to create the BOM and routings.

The profile option BOM: Use OM Validation Organization When Pre-Configuring Single Level Items determines whether the current organization or the OM validation organization is used when preconfiguring a single level BOM. Usually, this value
should be set to Yes.

The Preconfiguration process matches to existing configurations, if the profile BOM: Match to Existing Configuration is set to Yes, and the model is set to perform matching. If the program finds a match for the top-level model you will be asked if you want to use the matched item id or create a new configuration for the new item. If you choose to use the match, no BOM is created for the current item. If you choose to create a new configuration for the new item, the new configuration replaces the old configuration in the match tables, and future matches in OM or BOM will match to the new predefined
configuration.

If a match is found for any of the lower level models, the matched configuration item is used by default.

Enabling Items
It is recommended that you enable the preconfigured item in all organizations that require it for the configuration process. If you do not enable the preconfigured item, the preconfiguration process automatically enables it in all organizations identified by the base model's item attribute Create Configured Item, BOM, and the base model's sourcing chain from this organization.

These items are created as autocreated items by setting AutoCreated Configuration to Yes in these organizations. If you want these items to be treated as preconfigured items, enable them in all organizations before preconfiguring the BOM
deselect the configuration item attribute AutoCreated Configuration on the preconfigured item in all organizations.

When the item is automatically enabled in an organization, for attributes that have the attribute control set at the organization level, attribute values for these items are inherited from the base model in that organization. Item attributes are copied from the preconfigured item if the attribute control is set at the master level.

Note: Child configuration items are created as autocreated items with all attributes set as in Create Configuration Items.
If you want the child configurations to be treated as preconfigured items, you must either:

• Preconfigure them before the parent configuration You must use the match functionality and then configure all levels ofconfigurations from the bottom up.
• Clear the AutoCreated Configuration attribute on the configurations you want to treat as preconfigured items.

Note: For preconfigured items, because the item is created by the user, item attributes are not copied from or validated against the base model item attributes. It is up to the user to set them appropriately. The Assemble to Order and Build in WIP flag must be selected. It is recommended that you use the ATO item template for these items.