To model order item control data:
Do one of the following:
If you are using the OracleComms_OSM_CommonDataDictionary model project (recommended), verify it is in your workspace.
If you do not have the model project in your workspace, that means you earlier dismissed and disabled the prompt to create it. To re-enable the prompt and accept it, see the discussion on orchestration preferences in "Defining OSM Preferences."
If you are not using the OracleComms_OSM_CommonDataDictionary model project, define the data element information for the ControlData/OrderItem/ structure in the data schema of whichever cartridge project you choose to include these data elements, using these guidelines:
Configure the ControlData/OrderItem/ structure as multi-instance with element constraint values of Minimum set to 0 and Maximum set to unbounded so that OSM creates an instance of the structure for every line item extracted off the customer order.
Set the maximum string length of ControlData to a reasonable value; the default value is often too low.
Create the order item specification for the orchestration order.
Do one of the following:
If you are using the OracleComms_OSM_CommonDataDictionary model project, drag the ControlData/OrderItem/ structure from its data schema onto the Order Template tab of the Order Item Specification editor.
Drag the ControlData/OrderItem/ structure from the data schema where you manually defined it onto the Order Template tab of the Order Item Specification editor.
In the Order Template tab of the Order Item Specification editor, do the following:
For every for every order item property you defined in the Order Item Properties tab (see "Order Item Specification Editor Order Item Properties Tab"), define a storage area; for example, if you defined lineId and lineItemName as order item properties, you would define the storage areas ControlData/OrderItem/lineId and ControlData/OrderItem/lineItemName.
Use the exact spelling and case of the order item property name for its defined storage area in the order template (ControlData/OrderItem/Order_Item_Property_Name).
Ensure the data schema element properties support the property values, such as type (string, number, structure) and maximum length.
Map line items that are qualifiers to a product on a parent line item to the parent product or orchestration product specification. For example, map a QoS line item to the parent orchestration product specification of a broadband product. The QoS line item is generated as an order item, but it must contain a reference to its parent through a parent key identifier.
Save the order item specification.
Include the ControlData/OrderItem structure in the creation task.