1. Using Sales and Operations Planning
  2. Global Entities

Global Entities

Within data collections, certain business entities in Oracle Fusion Cloud Supply Chain Planning are referred to as global entities.

Global entities are specific for each instance and are common for all source systems. They're common without regard to whether they're collected from the Oracle Fusion source system or from an external source system with the use of the file-based data import (FBDI) templates.

When data is collected for a global entity, the planning data repository stores only one record for each instance of the global entity. The data collections process removes the source system reference from the global entity and stores the data in the data repository. If the data collections process collects the same instance of a global entity from more than one source system, the data repository stores the value from the last collection.

The following example describes the collection of the global entity called unit of measure (UOM) from three source systems, namely A, B, and C:

  • A has an instance of a UOM. During the collection of UOMs from A, the kilogram UOM is collected. This is the first time the kilogram UOM is collected. The data collections process creates a kilogram record in the data repository.

  • B doesn't have any instances of a UOM. During the collection of UOMs from B, the data collections process doesn't collect the kilogram value. Because there was no record for the kilogram UOM in B, the data collections process doesn't change the kilogram record in the data repository. The record of the kilogram value from A is still valid.

  • C has an instance of a UOM. During the collection of UOMs from C, the kilogram UOM is again collected. The data collections process registers the kilogram record in the data repository to match the value from C.

Note:

When you use the FBDI templates, the global entity files require a source system. The collections framework validates that the source system matches each record's source system. A source system identifier marks each data record.

In Oracle Supply Chain Planning, the following entities are classified as global entities:

  • Approved Supplier List

  • Currencies and Currency Conversion Class

  • Customer and Customer Site

  • Demand Class

  • Order Orchestration Reference Objects

  • Planners

  • Regions and Zones

    Note: When you set up your geographies in the Oracle Trading Community Architecture or regions using the Supply Chain Planning Regions import template (ScpRegionsImportTemplate.xlsm), ensure that the names used for the first- and second-level regions are different. If the names are the same, collections won't happen for the second-level region and child regions.

  • Shipping Methods (Carrier, Mode of Transport, Service Level)

  • Supplier Capacity

  • Suppliers and Supplier Sites

  • Units of Measure and UOM Conversions