This chapter covers the following topics:
If you are using match, and you change any of the following setups on your model, you will need to run the CTO Update Config and Optional Processing Request Set to ensure that your existing configurations are updated to reflect the changes.
Addition or change of sourcing rules, assignments, or option specific sourcing
Change of the Create Configured Item, BOM attribute setting
Change of ATP attributes
Enable the model item in a new organization
If you are not using match, you can choose to run this program if you want the setups applied to configurations on existing sales order lines.
The Update Existing Configured Items and optional processing programs' request set automatically creates configuration data in all necessary organizations for existing configurations. If specified, it also calculates the lead time, cost, and purchase price for the newly upgraded items.
The following table describes when to use this program and how the program creates data. The item attribute column refers to the item attribute Create Configured Item, BOM. See Model Items, Bills, and Routing for more information.
| Item Attribute | Sourcing Change | Match | Run Program | Reason | Program Behavior |
|---|---|---|---|---|---|
| 1 | Y | Y | Yes | Create data based on newly setup multiple sources or OSS and for future matches. | The program will create data based on the item attribute for all canned configurations having open orders, whose base models have multiple sources or OSS setup. |
| 1 | Y | N | Depends | Customers do not need to run program if match is off and they do not want to use the newly setup multiple sources or OSS on existing open order lines. They should run it if they want to apply the multiple sources or OSS on existing orders. | If Run, the program will create data based on the item attribute, for all configurations on open order lines whose base models have multiple sources or OSS setup. |
| 1 | N | Y | No | Customer chose to set profile to 1 even though match is on. | |
| 1 | N | N | No | Not needed. | |
| 2 | Y | Y | Yes | Create data based on newly setup multiple sources or OSS and for future matches. | The program will create data based on the item attribute for all canned configurations having open orders, whose base models have multiple sources or OSS setup. |
| 2 | Y | N | Depends | Customers need to run this program only if they want to use the newly setup multiple sources, OSS, shipment transaction flows or global procurement on existing open order lines. | If Run, the program will create items for all existing configurations on open order lines in all organizations where the model exists. It will perform purchase price and list price rollup in all organizations where the item gets created by this program. **The program will create BOMs and routings for all configurations on open order lines whose base models have multiple sources or OSS setup. |
| 2 | N | Y | Yes | To create items everywhere. Customer may have set profile to 2 because they want to use global procurement or transaction flows. | The program will create items everywhere for all configurations on open order lines. It will perform purchase price and list price rollup in all organizations where the item gets created by this program. **BOM and routings will not be created because multiple sources or OSS are not setup. |
| 2 | N | N | Depends | Customers need to run this program only if they want to use the newly setup shipment transaction flows or global procurement on existing open order lines. | If Run, the program will create items for all existing configurations on open order lines in all organizations where the model exists. It will perform purchase price and list price rollup in all organizations where the item gets created by this program. **BOM & routings will not be created since multiple sources or OSS are not setup. |
| 3 | Y | Y | Yes | Customer chose to create data everywhere | The program will create data everywhere for all canned configurations. ** |
| 3 | N | Y | Yes | Customer chose to create data everywhere | The program will create data everywhere for all canned configurations. ** |
| 3 | Y | N | Depends | Customers need to run the program only if they want to use the newly setup multiple sources, OSS, shipment transaction flows or global procurement on existing open order lines. | If Run, the program will create items for all existing configurations on open order lines in all organizations where the model exists. It will perform purchase price and list price rollup in all organizations where the item gets created by this program. **The program will create BOMs and routings in all organizations where the model BOMs and routings exist for all configurations on open order lines. |
| 3 | N | N | Depends | Customers need to run the program only if they want to use the newly setup shipment transaction flows or global procurement on existing open order lines. | If Run, the program will create items for all existing configurations on open order lines in all organizations where the model exists. It will perform purchase price and list price rollup in all organizations where the item gets created by this program. **The program will create BOMs and routings in all organizations where the model BOMs and routings exist for all configurations on open order lines. |
Note: It is recommended that you use the Update Configurations and Optional Processing concurrent request (Available under BOM, ATO) if you intend to calculate lead times cost or purchase prices of newly upgraded items. The update existing configurations program by itself (Available under BOM, others) should only be used if you do not want to calculate lead time/cost or purchase price of the newly upgraded items.
The Update Existing Configurations concurrent program has the following parameters:
Items
All models
Item Category (all models in this item category)
Specific Configuration item (this configuration item)
Category Set (enabled if item category is selected)
Item Category (enabled only if Category Set is selected)
Configuration item (enabled only if Configuration Item option is selected in 1)
Has sourcing changed?
Yes
No
Process nonmatchable models?
Yes
No
Upgrade Mode
Update Items
Update Items and Update ATP attributes
Update ATP attributes
You can use the Update Existing Configurations concurrent program to update all existing models, all models in an item category, or a single configuration item. This program will create all items and items data. This program also creates new sourcing for the items, but in a new assignment set, CTO Update Configurations, seeded for the purpose of this program. Once all items have been created, subrequests are launched for the AutoCreate BOMs Across Organizations program. One subrequest is launched per 100 items. These sub programs create BOMs and routings, and perform flow calculations for the items created by the parent program. The program also replaces the sourcing in MRP: Default Assignment Set with new sourcing created by the earlier program in the new seeded assignment set, if BOM creation succeeds.
Note: It is possible that items may be created in new organizations, and the subprograms could fail the BOM creation process. This is why sourcing is not updated until BOM creation succeeds.
All models: If you select all models, all existing models on open order lines and in the match tables are upgraded. You can do additional filtering by other input parameters).
Item Category: Enables you to specify a specific item category set and category to upgrade.
Specific Configuration Item: Enables you to specify a configuration item to upgrade.
The Category set which includes the upgrade category described later. Enabled only if Item Category is specified in Item.
Define a new Item Category for the purposes of this program and put all models to be upgraded in this category before running the program. The program processes all configurations of these models and their child models. If you choose to put only top level models in the category, configurations of child models are automatically processed, even if they are not assigned to the category, if they are part of the same order line as the top parent or if they are canned for matching. However, order lines for the child configuration item itself will not processed. Parent models of the model in the category (if any) will not be processed if they are not assigned to the category. Hence, you are recommended to put all models related to each other in this category to avoid having inconsistent data being processed. After the program processes the models successfully, they will be automatically removed from the category. If the same model needs to be processed again due to a new feature being enabled, it should be put in the category again. You should not use an existing category for this program, because at the end of the program all item assigned to this category will be removed from the category. Enabled only if Item Category is specified in Item.
This option processes a specified configuration item only. Select the configuration item with the Configuration item parameter.
If sourcing has changed on any of the models specified in the Items parameter, select Yes. Defining Option Specific Sourcing is considered a sourcing change. If sourcing has not changed on any models, select No. If this parameter is selected as No, the concurrent program processes only configuration items with the Configured Item, BOM creation attribute set to Based on Model or Item Based on Model, BOM Based on Sourcing. If this parameter is set to Yes, all configuration items are processed. If sourcing (or OSS) has changed, this parameter must be set to Yes, otherwise you could end up with configuration data created in organizations that do not match the configuration item sourcing.
Note: If you change the sourcing, and supply is already created for a sales order based on old sourcing, the existing sales orders may have supply created in the wrong organization. The next plan run should indicate excess supply in that organization.
Select No if you do not want to use newly setup features on existing order lines. This option is available only for models that have the Enable Configuration Matching attribute set to No. Open order lines for models that have this attribute set to Standard match or Custom match are always upgraded.
Select Update Items to create items, BOMs, and routings in additional organizations based on the sourcing changes and the setting of the Configured Item, BOM creation attribute. This will not update ATP attributes.
Select Update ATP attributes to update only the ATP attributes on the selected configuration items. If the profile INV:Capable to Promise is set to Based on Planning Output, and match is enabled, run this program in ATP attributes mode for all of your existing configurations.
Select Update Items and Update ATP Attributes to create the item, BOMs and routings, and update the ATP attributes on all existing instances of the selected configuration item.
Note: It is recommended that you update all models in batches by putting them in the category one batch at a time. This improves performance and avoids redundant processing.
Note: This process will update both autocreated and preconfigured items.
The program creates the following data:
A seeded request set, CTO Update Configuration and Optional Processing Request Set, is available to execute the Update Existing Configurations batch program, and some or all of the optional processing batch programs together. The request set includes the following programs:
Update Existing Configurations
Update Configurations-CTO Calculate Lead Time
This program calculates lead time for all configuration items that are processed by the main program in all organizations where the item routing is newly created. You can skip this processing by setting an input parameter, Calculate Lead Time to No.
Update Configurations-CTO Purchase Price Calculation
This program rolls up list price and purchase price for all configuration items processed by the main program, in all organizations where the item is newly created. You can skip this processing by setting an input parameter, Perform Purchase Price Rollup to No.
Update Configurations-CTO Calculate Cost Rollup
This program rolls up cost for all configuration items processed by the main program in all organizations where the item exists. You can skip this processing by setting an input parameter, Perform cost rollup to No.
Note: Execute this request set with the parameter Perform Cost Rollup set to Yes, to have the costs roll up, while upgrading the configured items. Running the request Update Existing Configurations alone does not perform a cost rollup to the configured items while upgrading.
Sourcing rules are deleted and re-created for each item that is processed. New sourcing is created based on the new sourcing defined for the model and the value of item attribute Create Configured item, BOM. The program does not recreate sourcing for the following items:
Configuration items in match tables that are not linked on open sales order lines and have item attribute set to Based on Sourcing or Items Based on Model, BOMs and Routings Based on Sourcing (if match is being used).
Note: When a match is found for such an item, the AutoCreate Configurations program creates the data and sourcing based on the model sourcing. Match during ATP is not possible for such items; however, the recommended attribute setting if Match is being used with PDS ATP is Based on Model.
Items are created in the organizations required based on the new sourcing defined for the model and the value of item attribute Create Configured item, BOM, if it does not already exist. If the item is an autocreated item in all organizations, it inherits item attributes from the model item in that organization. If the item is a preconfigured item in at least one organization, it inherits item attributes either from the model item in that organization, or from the preconfigured item, based on the item attribute control level. If the item is a pre-configured item in more than one organization, any one organization is randomly selected to inherit the item attributes.
BOMs and routings are created in the organizations required based on the new sourcing defined for the model and the value of item attribute Create Configured item, BOM, if it does not already exist. The program does not check for dropped components on the BOM in existing organizations. If there are dropped components in the new organizations where the BOM is created, all open order lines to which this configuration item is linked are put on hold. Dropped components effectivity is checked based on:
Sysdate if match is being used and the item is not linked to any open sales order
Schedule ship date of one of the order lines to which this item is linked (randomly picked)
The program creates data for the following items (depending on the parameters selected):
Configuration items linked on open sales order lines
Additional configuration items in match tables that are not linked on open sales order lines and have item attribute set to Based on Model (if match is being used)
This includes preconfigured items in the matched tables and matched on open order lines.
The program does not create data for the following type of items:
ATO items created manually.
Preconfigured items that have base models with the match attribute set to No.
Preconfigured items ordered directly on open order lines.
Autocreated configuration items that are delinked from all open sales order lines, and are not canned for future matching, but are being ordered as ATO items on the order line.
Data is not created for a particular item for the following type of errors:
Dropped components on a BOM. If dropped components are found while creating the BOM for a configuration item in a certain organization, the BOM will be created or not created based on the profile BOM: Create Configuration Exception Behavior. If the profile is set to not create the BOM, BOMs, routings, and sourcing are not created for this configuration item in all organizations. Optional processing is also not performed for this item. However, configuration items are created for this item. Parent configuration BOMs are also created.
Lower level configuration item does not exist in BOM creation organization. Configuration BOM are not created if any of the lower level configuration items do not exist in this organization. In this case, BOMs, routings, and sourcing are not created for this configuration item in all organizations. Optional processing is not performed for this item. However, configuration items are created for this item. This may happen if you choose not to create data for preconfigured items, and the preconfigured item is a child on an autocreated item BOM.
Note: If any items fail correct the issue and resubmit the item for processing by adding it to the assignment set again. Or you can process them directly.
It is recommended that you make setup changes to a subset of models rather than trying to change them all at once. Perform the following steps for the items you are changing before running the Update Existing Configuration concurrent program:
Setup Option Specific Sourcing if applicable.
Setup Multiple Sourcing if applicable.
Setup Shipment and Procurement Transaction flows if applicable.
Setup Global Procurement and Blanket Agreements if applicable.
Set the following profiles, if they are not already set:
BOM: CTO Perform Cost Rollup
BOM: CTO Perform List Price and Purchase Price Rollup
BOM: CTO Perform Flow Calculations
BOM: Perform Lead Time Calculations
Set the BOM parameter Create Configuration BOM to No in organizations where you do not want configuration BOMs to be created (for example, OM validation organization).
Set the following attributes for all models you are going to update, or, if you want to default from the profile, leave them null:
Configured Item, BOM creation
Enable Configuration Matching
Deactivate configurations and run update pending status to deactivate as many old configurations as possible. This will improve the performance of the update program.
Purge data from matched tables for configurations you no longer want to match and are not ready to be deactivated. This will improve the performance of the update program.