Data Collection Sequence

This topic explores the sequence that you should follow for data collection.

Data collection involves collecting entities in a predefined sequence. The collected entities form the basis for supply planning calculations. To have accurate data, you must ensure to collect the entities in a proper sequence. You cannot collect some entities without collecting their precursor entities. The data collection sequence is very crucial when you collect data from an external source system using CSV files.

If you run targeted collections for all entities, you can ignore the sequence for collections because targeted collections automate the collection sequence for all entities within a single collections request. If you collect many entities in a single request, collections will process them according to the sequences shown in this topic. If you collect only a few entities, then you must be aware of the collections sequence information. For example, you should not collect work orders before you collect items or resources.

To make the workflow simple, the collection sequence is divided into two parts - Part A and Part B. The collection entities in Part B are dependent on the collection entities in Part A. You must collect the entities in Part A before you collect the entities in Part B. Also, the collection entities are grouped together for easier presentation. The data groups in Part A are:

Collections Sequence Part A for Item Data
Collections Sequence Part A for Region, Location, and Customer Data
Collections Sequence Part A for Currency, Calendar, Demand Class, and UOM Data

The data groups in Part B are:

Collections Sequence Part B for Sales Order and Assignment Sets
Collection Sequence Part B for Work Orders, Work Definition, and Item Structure

Every collection sequence in Part A starts with defining a source system where the collected data will reside. If you are collecting data to the same source system, you define the source system only once. Then, use the same source system to collect all the entities.

The following figure provides an overview of the data collection sequence. The overview shows how Part A and Part B fit together to form a complete data collection flow.

The image provides an overview of the data collection sequence. The data collection sequence is divided into smaller groups for easier presentation. This image shows how the smaller groups are related to make one complete workflow. This image is divided into two parts, Part A and Part B. Part A has three groups and Part B has two groups. Collect all the data in Part A and then proceed to part B. Part A has the following three groups. The first group is Collection Sequence Part A for Currency and Calendar Data. The second group is Collection Sequence Part A for regions and Customers Data. The third group is Collection Sequence Part A for Item Data. Part B has the following two groups. The first group is Collection Sequence part B for Sales Order and Assignment Sets. The second group is Collection Sequence Part B for Work Orders, Work Definition, and Item Structure.

Collections Sequence Part A for Item Data

The following image shows the collections sequence to follow while collecting Item data from external source systems. This image represents only half of the entities for collecting Item data.

Note: The Organization entity is marked with an asterisk because you can collect other entities such as Planner, Item Cost, Subinventory, Carrier, Calendar Assignment, Supplier, and Supplier Site after collecting Organization. For more information on the collection sequence for these entities, see the Collections Sequence Part A for Currency, Calendar, Demand Class, and UOM Data figure. Refer to the entities that are collected after Organization. Also, ensure that you collect Location before collecting Supplier Site.

Describes the collection sequence for Item data. The collection always starts with defining a source system and then creating organizations. Collect Organization and then continue to the collection sequence B. For collecting Items, after you create organizations, load UOM, then load items in Oracle Fusion Product Information Management, and then collect Items. Collect the following entities next, UOM Class Conversions, Customer Specific Item Relationships, Item Relationship, Item Costs, Item Structure, Item Catalog, Safety Stock Level. Then collect Item Structure Component, Catalog Category Association. Lastly, collect Item category, and then continue collecting data mentioned in collection sequence part B.

When you collect the data described here, continue to the collection sequence Part B described in the following subsections.

Collection Sequence Part B for Sales and Order and Assignment Sets
Collection Sequence Part B for Work Orders, Work Definition, and Item Structure

Collections Sequence Part A for Region, Location, and Customer Data

The following image shows the collections sequence to follow while collecting Regions and Customers data from external source systems. This image represents only half of the entities for Item data.

Describes the sequence to collect region, location, and customers data. The collection always starts with defining a source system. Then load customers and regions in trading community. After you load customers and regions, you can load the customer sites in trading community architecture (TCA). Then, you can collect location, customer, and region. After collecting region, you can collect ship methods, and then collect sourcing rules, sourcing assignments, source organization, receipt organization. After collecting location and customer, you can collect customer sites. Then, collect calendar assignments and customer-specific item relationships. After collecting calendar assignments, continue collecting data mentioned in collection sequence part B.

When you collect the data described here, continue to the collection sequence Part B described in the following subsections.

Collection Sequence Part B for Sales and Order and Assignment Sets
Collection Sequence Part B for Work Orders, Work Definition, and Item Structure

Collections Sequence Part A for Currency, Calendar, Demand Class, and UOM Data

The following image shows the collections sequence to follow while collecting Currency, Calendar, Demand Class, and UOM data from external source systems. Also, ensure that you collect Location before collecting Supplier Site.

Note: The Calendar entity is marked with an asterisk because there are other entities that are associated with Calendar that you must collect in a sequence. To collect other entities associated with Calendar, see the Calendar Upload Sequence figure.

Describes the sequence to collect currency, calendar, UOM, and demand class data. The collection always starts with defining a source system. Then collect currency, calendar data, demand class, location, and UOM. After collecting currency, you can collect currency conversion type, and then collect currency conversion rate. After collecting UOM, you can collect UOM conversions and UOM class conversions. After collecting calendar, or demand class, or both, collect organization. Continue the data collection as described in the next diagram.

Continue collecting data after Organization. After collecting organization, collect planner, item cost, subinventory, carrier, supplier. Then collect supplier site and then calendar assignment. You can also collect the calendar assignment directly if you do not want to collect carrier and supplier data. After collecting calendar assignments, item cost, and subinventory, continue collecting data mentioned in collection sequence part B.

When you collect the data described here, continue to the collection sequence Part B described in the following subsections.

Collection Sequence Part B for Sales and Order and Assignment Sets
Collection Sequence Part B for Work Orders, Work Definition, and Item Structure

Collection Sequence for Calendar Data

The following image shows the collections sequence to follow for collecting the Calendar data. Calendar data is a part of the data collection in Part A. You collect the Calendar data in the following subsection: Collection Sequence Part A for Currency, Calendar, Demand Class, and UOM Data.

Describes the sequence to collect calendar data. Calendar data includes a list of entities that you can collect. After you collect calendar, you can collect calendar shifts, calendar exceptions, period start days, and week start days. After you collect calendar shifts, you can collect the calendar workday pattern data. After you collect calendar exceptions, you can collect the generate calendar dates post collection data.

Collections Sequence Part B for Sales Order and Assignment Sets

The following image shows the collections sequence to follow while collecting Sales Order and Assignment Sets data from external source systems. The data entities in Part B are dependent on Part A. So, you must collect entities listed in Part A before you collect the entities in Part B.

Describes the sequence to collect sales order and assignment sets. After you collect all the entities that are described in the collection sequence part A, you can collect ship methods, sales order, approved supplier list (ASL), supplier capacity, planned orders, forecasts, on hand, transfer order, purchase orders, and ship methods. After collecting on hand, transfer order, and purchase order, you can collect reservations. After collecting ship methods, you can collect sourcing rules, sourcing assignments, source organization, and receipt organization.

Collection Sequence Part B for Work Orders, Work Definition, and Item Structures

The following image shows the collections sequence to follow while collecting Work Orders, Work Definition, and Item Structure data from external source systems. The data entities in Part B are dependent on Part A. So, you must collect entities listed in Part A before you collect the entities in Part B.

Describes the sequence to collect work orders, work definitions, and item structures. After you collect all the entities that are described in the collection sequence part A, you can collect UOM conversions, work orders, and department resources. After collecting work orders, you can collect reservations, work order material requirement, and work order resource requirement. After collecting department resources, you can collect work order resource requirement, resource availability, resource capacity, bill of resources, and work definition. After collecting work definition, you can collect item structure component operations, and then collect item component substitutes.