Entities You Can Cross-Reference in Order Management

Use the Order Orchestration and Planning repository to store data that you collect from different source systems and fulfillment systems, then use them to cross-reference the entities that Order Management uses during order import or to resolve cross-references.

Here are the types of entities you can store in the repository.

Type of Entity	Description
Global	Reference more than one instance of an entity that resides in more than one source system. Data Collection collects each entity into the Order Orchestration and Planning repository, validates it, then consolidates all the entities it collects into a single record that represents all entity instances across all systems. This single record is the global entity.
Source	Don't represent the same data in more than one source system. The instances of source data are distinct. For example, one source system might consider Warehouse as an organization while another source system uses some other classification.

Data Collection collects the transactions that are related to supply and demand so Global Order Promising can do planning and promising. It collects transactions into the Order Orchestration and Planning Repository. You set up the source system so Order Management can store details that identify the source of records and manage collection. The repository uses these details so it can identify the source system where records originate.

Global Entities That Data Collection Can Collect

• Activity Types

• Conversion Types

• Currencies

• Demand Classes

• Document Categories

• Free on Board

• Freight Carriers

• Freight Terms

• Invoicing and Accounting Rules

• Payment Terms

• Receipt Methods

• Return Reasons

• Sales Credit Types

• Ship Class of Service

• Ship Mode of Transport

• Shipment Priority

• Tax Classification Codes

• Tax Exemption Reason

• Unit of Measure

Data Collection can collect these source entities.

• Reason

• Warehouse