The OracleComms_OSM_CommonDataDictionary model project enables autogeneration of orchestration control data. This model project is managed as a sealed cartridge. Do not modify the data elements of its data schema. See "Working with OSM Cartridge Projects" for information on how to create this orchestration model project in your workspace.
The data schema of the OracleComms_OSM_CommonDataDictionary model project comprises predefined data elements of which control data structures are composed. The data schema includes the base ControlData structure and the data elements it references: base order item data elements and base function data elements.
You use the data elements of this model project to manually model control data for order items. Design Studio uses the data elements of this model project to automatically model control data for order components. When an order component is created and added to the orchestration fulfillment pattern that is part of the orchestration plan, Design Studio automatically includes the ControlData structure from this data schema into the order template of the order and order component. The structures and types defined in the data schema of this model project are used as base types. For example, the data schema contains a FulfillmentFunctionType data element that describes all of the required data needed for a fulfillment function. When you create a new function order component, Design Studio for OSM creates a new and separate data element with the name of the function order component that uses FulfillmentFunctionType as a base type. The new function structure (ControlData/Functions/Order_Component_Name) is stored in the data schema of the project in which the function order component is contained; that is, it is no longer stored in the data schema of the OracleComms_OSM_CommonDataDictionary model project.
The OracleComms_OSM_CommonDataDictionary model project works for existing cartridge projects where the ControlData structure is already defined. When you create the model project in your existing workspace, you enable Design Studio to automatically update your existing ControlData structure with data for order components newly created thereafter.
See "About Autogeneration of Order Component Control Data" for information on orchestration entities that must be set up for Design Studio to be able to automatically model order component control data.