About Order Components

Order components are containers for order items. The contents of an order component are determined by the evaluation of decomposition rules and by the fulfillment pattern that is associated with the order items on the incoming order. The order in which OSM creates order components and the manner in which OSM includes order items in order components is based on the orchestration sequence used to process the order. Order components that are executable are mapped to a static process configured in Design Studio.

Required Control Data Structures

Orchestration plan generation requires two structures which you must model at design time at the order component level and the order item specification level:

ControlData
   OrderItem
   Functions
      Order_Component_Name
         componentKey
         OrderItem
            orderItemRef

For information on how to model the Control Data/OrderItem structure, see "About Modeling Order Item Control Data."

For information on how to model the ControlData/Functions structure, see "About Modeling Order Component Control Data." Design Studio automatically creates this structure if auto generation of order component control data is enabled. See "About Autogeneration of Order Component Control Data."

For general information about modeling control data, see "About Modeling Control Data."

Order Component Control Data

When OSM finishes generating the plan to orchestrate for the incoming order, it produces a set of order components, one per unique combination of function, fulfillment system, and processing granularity. Each order component contains the appropriate set of order items and dependencies between order items within that order component and order items on other order components.

In addition to the order components, OSM produces a set of control data. The control data, unique to each incoming order, provides information OSM requires to fulfill the order. For example, OSM uses the control data to track the status of the entire order and to track the status of the individual order items. During fulfillment, order component transactions update this control data with responses from the external systems used to fulfill line items.

Order component control data is configured by modeling the ControlData/Functions structure in the Order Template tab of the Order Component Specification editor. 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, Design Studio automatically creates the required order component control data for orchestration orders. For more information on the ControlData/Functions structure, see "About Modeling Order Component Control Data."

Order Component Order Items

OSM uses reference nodes to manage order items across multiple components. Reference nodes are pointers to values contained in different data nodes, and they enable you to create information once and reuse it in multiple locations in your data model. Rather than copying the order item data to each component, OSM creates in the component control data a reference node back to the original order item.

You model the reference node for the order component control data in the Order Template tab of the Order Component Specification editor as ControlData/Functions/Order_Component_Name/OrderItem/orderItemRef. Design Studio automatically inserts the modeling of this reference node on the order component control data if you have the OracleComms_OSM_CommonDataDictionary model project in your workspace. For more information on the ControlData/Functions structure, see "About Modeling Order Component Control Data."

For more information about reference nodes, see "About Reference Nodes" and "Adding Reference Data Nodes."