Modeling Order Component Control Data Manually

If you do not have the OracleComms_OSM_CommonDataDictionary model project in your workspace, you must model 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."

To model order component control data manually:

Manually define the data elements for the order component control data structure in the data schema of the cartridge project you choose to include these data elements as follows:
- Create the ControlData/Functions structures as root level data elements at the data schema level; do not embed them in a nested data schema data structure.
  
  If you are modeling data where you recompose in the project data schema the data structures you compose in the Order Template (so that they have the same structure hierarchy from root to tip), use a single ControlData structure; that is, the ControlData/Functions structure and the ControlData/OrderItem structure in the data schema must belong to the same ControlData data element.
- Define a substructure for every order component in the fulfillment pattern; for example, ControlData/Functions/Order_Component_Name. These are the order components you define in the Order Component Specification editor; for example, ControlData/Functions/BillingFunction, where BillingFunction is an order component you define.
  
  Use the exact spelling and case of the order component name for its defined storage area (structure) in the order template. For example, if you named an order component BillingFunction, use ControlData/Functions/BillingFunction; do not use ControlData/Functions/billingfunction.
  
  Note:
  Some order components do not need to have data under ControlData/Functions: for example, those that are not in the fulfillment pattern.
- For the Order_Component_Name data element in ControlData/Functions/Order_Component_Name, set Minimum to 0 and set Maximum to unbounded in the Multiplicity field.
- Define a componentKey node as a string below the structure to contain the component key for order components; for example, ControlData/Functions/Order_Component_Name/componentKey.
  
  The component key is used for calculating the processing granularity. You implement the calculation that generates a component key per order item. OSM groups order items with the same component key into order components if a decomposition rule specifies such a grouping.
- Define a reference node to ControlData/OrderItem, ControlData/Functions/Order_Component_Name/OrderItem/orderItemRef,
  
  where:
  - OrderItem has Minimum set to 0 and Maximum set to unbounded in the Multiplicity field
  - orderItemRef is a reference node to ControlData/OrderItem
On the Order Component Specification editor in the Order Template tab, add from the data schema the data elements you defined to model the order component control data structure as follows:
```
ControlData
   Functions
      Order_Component_Name
         componentKey
         OrderItem
            orderItemRef
```
Save the order component.
On the Order editor in the Order Template tab, add from the data schema the substructure you defined for every order component in the fulfillment pattern; for example, ControlData/Functions/Order_Component_Name. The ControlData/Functions structure on the order must be populated with data for each of the order components in the fulfillment pattern.

Use the exact spelling and case of the order component name for its defined storage area (structure) in the order template. For example, if you named an order component BillingFunction, use ControlData/Functions/BillingFunction; do not use ControlData/Functions/billingfunction.
Save the order.