The order template of an order item specification must have a reserved area, the ControlData/OrderItem structure, that is used by decomposition and orchestration functions. The Control Data/OrderItem structure is populated by orchestration plan generation with the order items from the sales order and is based on data you define for the Order Item Properties tab in the Order Item Specification editor. OSM uses the order item specification to generate order items into the ControlData/OrderItem/ structure to include all of their properties from the in-bound message.
The OracleComms_OSM_CommonDataDictionary model project contains a predefined data schema that defines the ControlData structure and its data elements. If you have this model project in your workspace, you can use its predefined data schema when modeling the ControlData/OrderItem/ structure (you can drag the ControlData/OrderItem/ structure from the data schema onto the Order Template tab of the Order Item Specification editor). Otherwise, you must manually define the data element information for the structure in the data schema of whichever cartridge project you choose to include these data elements and then drag the ControlData/OrderItem/ structure (you manually defined) from that data schema onto the Order Template tab of the Order Item Specification editor.
See "Modeling Order Item Control Data" for instructions on modeling order item control data.
Order components also require a data structure for control data. See "About Modeling Order Component Control Data" for more information.