About Modeling Order Component Control Data

The Control Data/Functions structure is populated by orchestration plan generation for every order component of the orchestration plan and is based on data defined on the Order Template tab in the Order Component Specification editor.

The ControlData/Functions structure is a data repository area that is required to process the fulfillment function; this data area includes the order items the decomposition process has generated for the fulfillment function.

The control data structure for order components is modeled automatically or manually depending on the following:

If you have the OracleComms_OSM_CommonDataDictionary model project in your workspace (recommended), and if the order component is both associated with an orchestration order and associated with an orchestration fulfillment pattern that is part of the orchestration plan, Design Studio automatically creates its control data structure.
If you do not have the OracleComms_OSM_CommonDataDictionary model project in your workspace, you must manually model the control data structure for each order component that is associated to an orchestration fulfillment pattern that is part of the orchestration plan. You must also manually add a reference node to it that points back to the order item control data structure. See "Modeling Order Component Control Data Manually" for information on adding this reference node.

Design Studio automatically defines the data on the Order Template tab in the Order Component Specification editor by using the OracleComms_OSM_CommonDataDictionary model project (see "About the OracleComms_OSM_CommonDataDictionary Model Project" for information on this project).

If you do not use the OracleComms_OSM_CommonDataDictionary model project, you must manually define the simple and structured data elements for the Control Data/Functions structure in the cartridge project of your choice and then manually add the data from its data schema onto the Order Template tab of the Order Component Specification editor. Manually modeling the Control Data/Functions structure for an order component is not recommended and should only be required if you decide not to use the OracleComms_OSM_CommonDataDictionary model project (for example, to minimize the upgrade impact of existing cartridges).

See "Modeling Order Component Control Data Automatically" for information on how to ensure that Design Studio can model the order component control data automatically by using the OracleComms_OSM_CommonDataDictionary model project.

See "Modeling Order Component Control Data Manually" for instructions on how to model the order component control data manually.

Note:

You must model a structure for order item control data in addition to modeling a structure for order component control data. For information on modeling a structure for order item control data, see "About Modeling Order Item Control Data".