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.
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.
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.
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.
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.
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.
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.
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.
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.