3Planning Data Collections

This chapter contains the following:

• Overview of Data Collections for Supply Chain Planning

• Global Entities

• Data Collection Types for Supply Chain Planning

• How the Order Orchestration and Order Promising Processes Use the Collected Planning Data

• How You Enable Cross-References of Entities by Data Collections

• How Planning Processes Collect Different Work Definitions and Item Structures

• Enable External Data Collection for the Oracle Fusion Source System

• Collect Planning Data from the Oracle Fusion Source System

• Load Planning Data from Others and External Source Systems

• Verify Collection Processes

• Aggregate Customer Data

Overview of Data Collections for Supply Chain Planning

To run plans from one of the Supply Chain Planning work areas, you must collect data into a planning data repository. Order promising and order management processes also use the planning data repository to promise and manage orders.

To collect data into the planning data repository, you can perform these tasks from one of the Supply Chain Planning work areas:

• Collect Planning Data: Use this task when you collect data from the Oracle Fusion source system.

• Load Planning Data from Files: Use this task when you collect data from a completely external source system.

Depending on your security privileges, you may need to manually add these tasks. In the Setup and Maintenance work area, use the following:

• Offering: Supply Chain Planning

• Functional Area: Supply Chain Planning Configuration

• Task: Collect Planning Data

The following figure illustrates the collections processes that you can use to populate the planning data repository.

Collect Planning Data

There are two steps involved in the data collection process. The Collect Planning Data process first pulls data from the Oracle Fusion source system into staging tables. The process then loads data from the staging tables into the planning data repository.

On the Collect Planning Data page, use the following tabs to select what data you want to collect:

• Reference Data

• Demand Planning Data

• Supply Planning Data

Most of the reference data are global entities. Global entities are common for all source systems. For example, Units of Measure (UOM) is common for all source systems. The supply planning and demand planning data are transactional data. Most of the transactional data are local entities. Local entities are specific to each source system. For example, On-hand Quantity is specific for each source system.

You can also select collection filters to further refine what data you want to collect. You can save your selections to collection templates.

Load Planning Data from Files

Use this option to populate the planning data repository using CSV files:

To load the planning data from files, follow these steps:

1. Create the CSV files. To create the CSV files, you can use a predefined set of Microsoft Excel files as import templates.

2. Import the CSV files. From the navigator, click File Import and Export, and create a new import. Specify scm/planningDataLoader/Import for the account.

3. Submit the Load Planning Data from Files process. When you submit the process, the process first pushes the data from the CSV files into the staging tables. The process then loads the data from the staging tables into the planning data repository.

• Update Existing Setup Data

Global Entities

Within data collections, Oracle Fusion Supply Chain Planning refers to certain business entities as global entities. Global entities are specific for each instance and are common for all source systems. They are common without regard to whether they are collected from the Oracle Fusion source system or collected from an external source system using the file-based data import (FBDI) method.

When collecting data 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.

For example, the following scenario describes the collection method of the global entity called units of measure (UOM) from three source systems, namely source system A, B, and C respectively.

• Source system A has an instance of UOM. During the collection of UOMs from source system 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.

• Source system B does not have any instances of UOM. During the collection of UOMs from source system B, the data collections process does not collect the kilogram value. Since there was no record for the kilogram UOM in source system B, the data collections process does not change the kilogram record in the data repository. The record of the kilogram value from source system A is still valid.

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

Note: When you use the FBDI collection method, 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 Supply Chain Planning, the following entities are classified as global entities:

• Order Orchestration Reference Objects

• Units of Measure and UOM Conversions

• Demand Classes

• Currency and Currency Conversion Class

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

• Customer and Customer Site

• Suppliers and Supplier Sites

• Regions and Zones

• Approved Supplier List

• Supplier Capacity

• Planners

Data Collection Types for Supply Chain Planning

When you collect planning data, one of the parameters you specify for the Collect Planning Data task is the Collection Type parameter. You can select this task from any of your Supply Chain Planning work areas. For the Collection Type parameter, you can select one of the following values:

• Targeted: Choose the Targeted collection type when you want to collect a significant volume of source system data. Typically, you use the Targeted collection type in scenarios such as bulk upload of transaction data, instance upgrade, and change in collection filters.

• Net change: Choose the Net change collection type when you want to collect changed data and new records since the last successful collection cycle.

• Automatic selection: Choose the Automatic collection type when you want the planning process to decide and automatically select an appropriate collection type for each of the entities.

Targeted

You use the Targeted collection type when you want to perform a complete refresh of the data in the data repository. In this mode, the planning process deletes the existing data for the selected entities from the data repository. Next, if subsequently collected from the source, the data for the selected entities replaces the deleted data.

Note: For the following data collection entities, you can use only the Targeted collection type: Item Costs, Resource Availability, Fiscal Calendars, and all Shipment and Booking History data.

Net change

When you use the Net Change collection type, you collect data incrementally. The Net Change collection type collects only changed or new data. Collecting data using the Net Change collection type is usually faster than using the Targeted collection type. You typically use the Net Change collection type when you have previously performed a Targeted collection, and now you want to keep your planning data current with your execution system data. You cannot select the demand planning data when the collection type is Net Change.

Automatic selection

You use the Automatic collection type when you are not sure which collection type to select and you want the planning process to decide the collection type for each entity. The planning process evaluates each entity on multiple factors, such as the last collected date for an entity, and decides whether to perform a Targeted or a Net Change collection for the entity. You can manually select the entities that you want to collect or you can use one of the predefined templates to select your entities. If you select one of the predefined templates, you can't make any changes in the Reference Data, Demand Planning Data, and Supply Planning Data tabs.

How the Order Orchestration and Order Promising Processes Use the Collected Planning Data

You perform data collections to populate the planning data repository. In addition to being used by Supply Chain Planning processes, the collected data is used by Oracle Fusion Order Management order orchestration processes and by Oracle Fusion Global Order Promising processes.

Data Collections

You must perform data collections to populate the planning data repository, also called the order orchestration and planning data repository, with data from the Oracle Fusion source system or from a completely external source system. When you load data from an external source system, use the XLSM files to organize your data in the required format and then convert the data into CSV files. You can then upload the CSV files to the planning data repository.

Order Orchestration

Order orchestration processes use some reference data directly from the planning data repository. You must perform data collections for the order orchestration reference entities even if you are not using the Supply Chain Planning work areas.

Note: Before collecting data from your Oracle Fusion source system, you must define at least one organization for the source system. After you have set up at least one organization, you must update the organization list on the Manage Planning Source Systems page and then enable at least one of the organizations for collections. If you have not enabled any organization, then the collections process ends with an error.

Order Promising

The Global Order Promising processes use an in-memory copy of the data from the planning data repository. When order orchestration processes send a scheduling request or a check availability request to Oracle Fusion Global Order Promising, the order promising processes use the data stored in main memory to determine the response to send back to order orchestration. You must refresh the Global Order Promising data store after every collections so that the main memory always reflect the current.

• Refresh the Global Order Promising Server

How You Enable Cross-References of Entities by Data Collections

Cross-references enable you to locate the correct source value for each cross-referenced entity. When you enable entities for cross-referencing, data collection pays attention to the cross-references that you have set up for certain values.

To enable cross-referencing of entities, click the Manage Planning Data Collection Processes task from your supply chain planning work area. Select the source system from the list, and then enable the available entities that you want to cross-reference during data collections.

You can view the cross-referenced data for each entity on the Cross-Reference Relationships for Collected Data page in the Plan Inputs work area.

How Planning Processes Collect Different Work Definitions and Item Structures

You may be concerned that the work definition and item structure data in your supply chain planning work area does not match with what was defined in Oracle Manufacturing Cloud. You don't need to worry. The planning application collects and uses data based on how the work definitions and item structures are defined and associated in the manufacturing source system.

Work Definitions and Item Structures in the Source System

The work definition is a primary source of data for the planning application. The planning process uses the work definition of make order items to determine component and resource requirements. In case the work definition is not defined, the planning process uses the defined item structure, but to plan for components only. If a work definition is defined and no item structure is associated to it, then you can manually add ad hoc components to it. If an item structure is associated to it, you can still add ad hoc components to the work definition, alongside the components in the item structure. Remember that while a work definition can be associated with only one item structure, one item structure can be associated with several work definitions within the parent item.

Work Definitions and Item Structures in the Planning Data Repository

In the manufacturing source system, the work definitions and item structures for an item can be defined and associated in different ways. The following table lists the most common source system combinations and how the collections and run plan processes proceed accordingly:

Manufacturing Cloud Definition	Item Structure Name and Work Definition Name in the Planning Data Repository	Planning Collections Processes
Only item structure is defined for an item. No work definition is defined.	Item structure name exists, no work definition name	The planning process collects the item structure information but does not collect information for routing, operations, or item resources. The planning process uses item structure to plan components and does not plan resources.
Only work definition is defined for an item. No item structure is defined.	Work definition name exists, no item structure name	The planning process collects the work definition information to populate the item structure and routing information. The planning process populates the component information and operation sequence number in the item structure based on the ad hoc components and operation assignment available in the work definition. The planning process uses the work definition information to plan both components and resources.
Both item structure and work definition are defined for the item.	Both work definition name and item structure name exist	The planning process uses the components that are associated with the work definition to plan. The planning process does not consider any components of item structure that are not associated with the work definition. You can override the item structure component usage within the work definition. The planning process collects component attributes (such as component effectivity) from the item structure if the components are associated with the work definition. The planning process uses the work definition to plan resources.
Both item structure and work definition are defined for the item, but the work definition does not refer to the item structure. Ad hoc components are assigned to the work definition operations.	Work definition name exists, no item structure name	The planning process collects the components from the work definition and not from the item structure in the Oracle Fusion Product Information Management solution. The process plans components based on work definition operation assignments and plans resources based on the work definition.

Enable External Data Collection for the Oracle Fusion Source System

Enable external data collection if you want to load transactional data from external systems. Typically, you do this if some of your supply chain processes are managed in external applications. You load the transactional data from these applications using file-based data imports (FBDI).

You can use external data sources for these functional areas: Inventory and Materials Management, Procurement, Order Management, and Manufacturing. When you enable external data collection for a functional area, be aware of these restrictions:

• You can't use configure-to-order, drop shipment, and back-to-back fulfillment.

• The entities associated with the functional area are no longer available for Oracle Fusion source collection. For example, if you enable Order Management, the Sales Orders entity won't be available on the Collect Planning Data page for you to select for Oracle Fusion source collection.

This table lists the entities for each functional area.

Functional Area	Entities
Inventory and Materials Management	On-hand Quantity and Transfer Orders
Procurement	Purchase Orders and Requisitions
Order Management	Sales Orders and Reservations
Manufacturing	Work Order Supplies, Resource Availability, Resources, Work Definitions, and Item Structures

Enable External Data Collection

Use these steps to enable external data collection:

1. Select the Manage Planning Source Systems task in the Tasks panel from any Supply Planning work area page. Or use this task in the Setup and Maintenance work area:

   • Offering: Supply Chain Planning

   • Functional Area: Supply Chain Planning Configuration

   • Task: Manage Planning Source Systems

2. In the list of source systems, select the row that has Oracle Fusion in the Version column.

3. In the Actions menu, click Select Data Sources.

4. Select the Enable External Data check box, and then select the functional areas that you want to source transactional entities for.

Note: Every time you enable or disable external data collection, you must run a targeted data collection to ensure complete refresh of data in the data repository.

Collect Planning Data from the Oracle Fusion Source System

How You Collect Different Data Types for Supply Chain Planning

When you collect data, you collect data from three categories: reference data, demand data, and supply data. On the Collect Planning Data page there is a tab for each of these categories.

The collected data are stored in the planning data repository.

The following figure illustrates the three categories of data that you collect from the Oracle Fusion source system to the planning data repository.

Explanation of Callouts

1. Reference data is primarily sourced from Oracle Fusion SCM Cloud

2. Demand data comes from Oracle Order Management Cloud Service and Oracle Materials Management Cloud Service

3. Supply data is sourced from Oracle Inventory Management Cloud Service, Oracle Manufacturing Cloud Service, and Oracle Purchasing Cloud Service

Reference Data

The collection process begins with reference data, which is primarily sourced from Oracle Fusion SCM Cloud. You collect the data collection entities, such as basic item, resource, organization, customers and suppliers, and calendar data.

Note: Oracle Fusion Sales and Operations Planning uses the Bill of Resources entity to link the make items with their associated components and resource requirements. For more information on collecting Bill of Resources from an external source system, see the Loading Planning Data from Files section.

You also use Oracle Supply Chain Planning Cloud to collect the following items:

• Item structures: To explode item-level demand into component demands and supplies.

• Work Definitions: To assign the component and resource requirements for make items.

• Units of measure: To align plan data and to convert plans from one set of units to another.

• Costs: To review plans in financial terms and evaluate the financial impact of planning decisions.

Demand Data

You collect demand data from two potential sources:

• Sales orders that flow from Oracle Order Management Cloud Service: You can use this as the basis of the demand forecast, while current orders can consume the demand in near-term forecast time buckets.

• Shipment history from Oracle Materials Management Cloud Service: You can use this to generate a shipments forecast.

Supply Data

You collect supply data from three sources:

• Oracle Inventory Management Cloud Service: This provides data related to on hand inventory, reservations, material transfers, in-transit supplies, and receipts.

• Oracle Manufacturing Cloud Service: This provides work in process status and any manufacturing work orders.

• Oracle Purchasing Cloud Service: This provides purchase requisitions and purchase orders.

Collection Filters and Collection Templates

You use collection filters and collection templates when you need to collect some common set of entities repeatedly. The collection filters and collection templates are located on the Collect Planning Data page. To open the Collect Planning Data page, click the Collect Planning Data task from one of the Supply Chain Planning work areas.

Depending on your security privileges, you can also open the Collect Planning Data page from the Setup and Maintenance work area. In the Setup and Maintenance work area, use the following:

• Offering: Supply Chain Planning

• Functional Area: Supply Chain Planning Configuration

• Task: Collect Planning Data

Collection Filters

Use collection filters to improve the performance and efficiency of the collections process, and to avoid accumulation of irrelevant data in the planning data repository. You can use several filter criteria while performing collections, such as by employing catalogs, order types, and price lists. You can also use date-based filters for collecting shipment and booking history information.

Enabling Collection Filters

To enable collection filters, you must first run the schedule process called Load Filter Names for Planning Data Collection from the Scheduled Processes work area. When you run the scheduled process, the filters get enabled in the Collect Planning Data page. Then, you can apply the filters from the next collection.

Collection Templates

Use collection templates when you want to collect a set of data repeatedly over a period. You can select either one of the predefined templates that serves your specific need, or you can create your own template and save it for future use.

When you select a predefined template from the list, the Collection Type field is defaulted to Automatic selection and you cannot edit the field. Also, when you select a predefined template, the Select Collection Filters field is disabled.

You can create a collection template on the Collect Planning Data page by selecting the data collection entities and saving the template for future use. For example, if you frequently collect certain supply planning transactional entities, such as On Hand, Purchase Orders, and Purchase Requisitions, then save these entities as a collection template. It reduces the overhead of selecting the same entities for subsequent collection cycles.

If the template file contains any error during the upload process, rectify the issue found in the log file and upload the template file again.

Collect Data Using the Targeted Collection Type

To perform a complete refresh of the data repository used by the Supply Chain Planning products, run a targeted collection. You can run the targeted collection immediately or you can schedule the process to run later. Demand planning data can only be collected by using the Targeted collection type.

Note: Before collecting demand planning data, you must successfully run the Load Filter Names for Planning Data Collection scheduled process.

Perform the following steps to collect reference data, demand planning data, and supply planning data using the Targeted collection type.

1. Access the Collect Planning Data page from a Supply Planning work area or the Setup and Maintenance work area.

   • If you are in one of the Supply chain Planning work areas:

     1. Click the Tasks panel tab.

     2. In the Tasks panel drawer, click the Collect Planning Data link.

   • If you are in the Setup and Maintenance work area, then select the following:

     • Offering: Supply Chain Planning

     • Functional Area: Supply Chain Planning Configuration

     • Task: Collect Planning Data

2. On the Collect Planning Data page, complete the following steps.

   • On the Parameters tab:

     1. Select your source system.

     2. For the collection type, select Targeted.

        Demand planning data can only be collected by using the Targeted collection type.

     3. Click Select Collection Filters to select the collection filters.

   • On the Reference Data subtab, move the required reference entities to the Selected Entities area.

   • On the Demand Planning Data subtab, set options to collect the historical demand data in the planning data repository. The planning process uses the historical demand data for statistical forecasting.

     • Collection Time Frame Options: You can specify a fixed or rolling date range for which to collect data.

       The Fixed Date Range option enables you to collect history data within a fixed date range that you specify.

       The Rolling Date Range option enables you to collect the history data for the number of days that you specify. For example, if you forecast weekly, specify 7 in the Number of Days to Collect field to collect the demand history data once per week. The data collections collect the demand history data for the latest week.

       Select Roll off time periods automatically to truncate the history data by the number of days that you specify in the Number of days to keep field each time you run collections for the demand history data. For example, if you prefer to forecast each week based on the history data of 52 weeks, select the Roll off time periods automatically check box and specify Number of days to keep as 364 days. This setting ensures that as you collect data every week, you keep the most recent history of 52 weeks and automatically purge history data older than 52 weeks.

     • History Measures and Attributes: Select your shipments history and bookings history measures.

     • Collection for ETO Items: Select Collect history from associated base models to collect bookings and shipments history for Engineer to Order (ETO) items from the associated base models. When you don't select this option, the history is collected from the standard ETO items.

     • History Data Options: To collect only specific order types, select from the Order Types to Include list of values. By default, all order types are included.

       Select Organization - Consumption Inventory Transactions to Include to collect consumption inventory transactions at the organization level. You can collect only the transfer orders inventory transactions or all consumption inventory transactions.

       Select Subinventory - Consumption Inventory Transactions to Include to collect consumption inventory transactions at the subinventory level. You can collect only the transfer orders inventory transactions or all consumption inventory transactions for the organizations that you enabled for subinventory planning.

       Select the Collect amount data for history check box to collect amount data.

     • Additional Options: Select additional options for collections.

       Collect Price Lists: Collect the price lists specified in the collections filter for price lists, or collect all price lists if no filter is specified.

       Collect Configure to Order Data: If you selected history measures and attributes, then select the relevant check boxes to collect shipment history options and booking history options.

       Sales Organization Hierarchy: Select Enable sales organization hierarchy collection to collect one or more sales hierarchies.

   • On the Supply Planning Data subtab:

     1. Move the required supply entities to the Selected Entities area.

     2. If you collect resource availability, then select a date range type: Fixed or Relative to collection run date.

        If you selected Fixed, then provide a start date and an end date for collecting resource availability.

        If you selected Relative to collection run date, then enter a number of days in the Collection Window in Days field. The number that you enter determines a collection window in days to collect resource availability based on a rolling time window. That rolling time window adjusts itself, based on the date that you run collections. For example, if you specify 90, then resource availability is collected for the next 90 days each time from the date of the collection run.

        Note: You can save your date range type selection for resource availability collection as a collection template to use later.

     3. You can collect the existing data for the resource availability.

     4. You can also regenerate the resource availability data and then collect the data. If you select the Regenerate data, and then collect option, the collections process runs the Update Resource Availability Job scheduled process first and then collects the resource availability data.

3. (Optional) Click the Schedule tab and set collections to run as soon as possible or schedule to run at a different time.

4. Click Submit to start the collections process.

5. Monitor the collection status using the Scheduled Processes page.

6. Review the collected data in the Plan Inputs work area.

• Set Up Forecast Consumption for Transfer Orders

Collect Data Using the Net Change Collection Type

You can collect data from the Oracle Fusion source system by running the net change collection or by scheduling to run the process later. Before running a Net Change collection, you must run a Targeted collection for the selected entities. After the first Targeted collection, you can run Net Change collections.

Perform the following procedure to collect reference data and supply planning data using the net change collection type:

1. If you are in one of the Supply Chain Planning work areas, then click the Tasks panel tab. In the Tasks panel drawer, click the Collect Planning Data task. If you are in the Setup and Maintenance work area, then use the following:

   • Offering: Supply Chain Planning

   • Functional Area: Supply Chain Planning Configuration

   • Task: Collect Planning Data

2. Complete the following parameters for the Collect Planning Data process:

   1. Select your source system.

   2. Select the collection type as Net change.

      Note: You cannot make any changes to the filter criteria and demand planning data in the net change collection type.

   3. In the Reference Data tab, move the required reference entities to the Selected Entities area.

   4. In the Supplies Planning Data tab, move the required supply entities to the Selected Entities area.

3. (Optional) Click the Schedule tab and set collections to run as soon as possible or schedule to run at a different time.

4. Click Submit to initiate the collections process.

5. Monitor the collection status using the Scheduled Processes page.

6. Review the collected data in the Plan Inputs work area.

• Update Existing Setup Data

Enable Organization Group Collection for the Net Change Collection Type

You can use organization groups to limit the net change data collection from a source system to specific organizations. Using organization groups for collection also eliminates the chances of data overlap when multiple instances of net change collections are run at a time. Planners can run collections for their organizations without waiting for each other.

Let's take a simple example where your organization considers only the D1 and D2 distribution centers in your source system for shipments to your customers. In such a case, you can create an organization group, assign D1 and D2 to the organization group, and collect net change data specifically for this group.

Note: Before you begin, ensure that you have your organization groups created. A supply planner creates and manages organization groups using the Manage Organization Groups button on the Maintain Supply Network Model page.

Do these to collect net change data for an organization group.

1. Access the Collect Planning Data page or Load Planning Data from Files page from a Supply Planning work area.

2. Select the source system. Organization groups are managed within the source systems.

3. Select the Net Change collection type. You can select an organization group for data collection only when the collection type is Net Change.

4. Enable the organization group collection, and then select an organization group.

5. Perform the net change data collection. Refer to the Collect Data Using Net Change Collection Type topic in this chapter for instructions.

Note: After selecting your organization group and other data collection entities, you can also save your selections as a template. Refer to the Collection Filters and Collection Templates topic in this chapter for additional information.

• How You Maintain Your Supply Network Model

Load Planning Data from Others and External Source Systems

How You Load Planning Data from Files

You upload data using CSV files for specific business objects using the targeted or net change method.

Note: To create the CSV files, you can use a set of Microsoft Excel template files that are provided for this purpose. You can download the templates from the File-Based Data Import for SCM Cloud guide in the Oracle Help Center.

You use the targeted mode when you want to refresh data for selected entities in the planning data repository. You use the net change mode to collect data incrementally. The net change collections mode collects only the changed or new data. Data collection using the net change mode is fast compared to the targeted mode. The net change mode is used to retain planning data to current with that of the executing system.

The following figure illustrates the process of collecting data from files.

To load planning data from files, you perform the following steps:

1. Create CSV files using Microsoft Excel template

2. Run the process to load planning data from files

3. Verify the load planning data process

4. Review the loaded data

Create CSV Files to Load Planning Data

To perform the Load Planning Data from Files task in one of the Supply Chain Planning work areas or Setup and Maintenance work area, you must prepare the data you want to load. You must create the necessary CSV files used to create files for import. This procedure explains how to create CSV files to prepare planning data for loading.

1. Locate the applicable file import templates (XLSM files) in the following guide: File Based Data Import for Oracle Supply Chain Management Cloud. Extract the templates to a local space.

   For additional information about creating and importing CSV files, see the following section in the Oracle SCM Cloud Implementing Common Features for Oracle SCM Cloud guide: External Integration chapter, External Data Integration Services for Oracle Cloud section.

2. Open the template file for the entity you are preparing and complete the file import template worksheet.

   You must enable the macros in the template file before generating the CSV file.

   Caution: For the cells that contain dates, ensure that the data is set to the correct format in the data type. For example, date must be set to YYYY/MM/DD.

3. After you finish preparing the data in the worksheet, generate the CSV file. The Generate CSV File button is located in the Instructions and CSV Generation worksheet of the workbook.

4. When you save the generated CSV file, you must use the suggested name of the entity. You can add underscore and add additional characters to the file name. For example, you can name the CSV file as ShipmentHistory_abc.csv and you can name the file as LoadingCSV.zip.

5. Compress the CSV file into a zipped file format using a compression utility. You can provide any name to the zipped file.

   Note: You can include multiple CSV files in a single compressed file for a source system. The load process uploads them in a sequential order. Select the CSV files and compress them directly. Do not compress the parent folder that contains the files.

   This completes the preparation of a file that you will upload to collect planning data.

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.

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.

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.

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.

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.

Import Templates Used to Create CSV Files for Supply Chain Planning

You can use the Microsoft Excel templates (XLSM files) to prepare the data for the supported collection entities. The templates are listed in the following guide: File-Based Data Import for Oracle Supply Chain Management Cloud. Extract the templates to a local drive, enter appropriate data as described in the template, and generate CSV files. Compress the CSV files to a zipped file format and upload the .zip file to the Universal Content Manager using the File Import and Export utility. The data is then loaded from the Universal Content Manger to the planning data repository.

Collect Data from the Oracle Fusion Source

The following table lists the collections entities that can be loaded into the planning data repository for the Oracle Fusion source. The Collection Entity column provides the name of the entities for which you can collect the data. The XLSM File Name column provides the template name that you will download for the respective collection entity. Download the XLSM template from the File-Based Data Import for Oracle Supply Chain Management Cloud guide (FBDI guide). The Link in Data Import Guide column provides the name of the topic in the FBDI guide from where you will download the template. For example, to collect data for the Item Costs collection entity, refer to the Item Cost Import topic in the FBDI guide.

Collections Entity	Link in Data Import Guide	XLSM File Name
Item Costs	Supply Chain Planning Item Cost	ScpItemCostImportTemplate.xlsm
Customer Specific Item Relationships	Supply Chain Planning Item Substitute	ScpItemSubstituteImportTemplate.xlsm
Planners	Supply Chain Planning Planners	ScpPlannersImportTemplate.xlsm
Item Suppliers	Supply Chain Planning Approved Supplier List	ScpApprovedSupplierListImportTemplate.xlsm
Demand Classes	Supply Chain Planning Demand Classes	ScpDemandClassImportTemplate.xlsm
Allocation Assignments and Allocation Rules	Supply Chain Planning Planning Allocation Rules	ScpPlanningAllocationRulesImportTemplate.xlsm
ATP Assignments and ATP Rules	Supply Chain Planning Available-to-Promise Rules	ScpATPRulesImportTemplate.xlsm
Supply Update Rules	Supply Chain Planning Real Time Supply Updates	ScpRealTimeSupplyUpdatesImportTemplate.xlsm
Measures	Supply Chain Planning Measures	ScpMeasuresImportTemplate.xlsm
Booking History	Supply Chain Planning Bookings History	ScpBookingHistoryImportTemplate.xlsm
Option Booking History	Supply Chain Planning Option Bookings History	ScpOptionBookingHistoryImportTemplate.xlsm
Shipment History	Supply Chain Planning Shipments History	ScpShipmentHistoryImportTemplate.xlsm
Option Shipment History	Supply Chain Planning Option Shipments History	ScpOptionShipmentHistoryImportTemplate.xlsm
Price Lists	Supply Chain Planning Price List	ScpPriceListImportTemplate.xlsm
Causal Factors	Supply Chain Planning Causal Factors	ScpCausalFactorsImportTemplate.xlsm
Forecast Measures	Supply Chain Planning Forecast Measures	ScpForecastMeasureImportTemplate.xlsm Note: This template has been superseded by the generic template ScpMeasuresImportTemplate.xlsm, but will continue to be supported. Future enhancements will be made only to the generic measures template.
Fiscal Calendars	Supply Chain Planning Fiscal Calendars	ScpFiscalCalendarImportTemplate.xlsm
Forecasts	Supply Chain Planning External Forecasts	ScpExternalForecastImportTemplate.xlsm
Safety Stock Levels	Supply Chain Planning Safety Stock Levels	ScpSafetyStockLevelImportTemplate.xlsm
Supplier Capacity	Supply Chain Planning Approved Supplier Capacity	ScpApprovedSupplierCapacityImportTemplate.xlsm
Planned Order Supplies	Supply Chain Planning Planned Order Supply	ScpPlannedOrderSupplyImportTemplate.xlsm
Sourcing Rule and Assignments	Supply Chain Planning Sourcing Rules	ScpSourcingImportTemplate.xlsm
Cross-Reference Mapping Information	Supply Chain Planning Cross-Reference Data	ScpCrossReferenceDataImportTemplate.xlsm

Collect Data from External Source - Version Others

The following table lists the collections entities that can be loaded into the planning data repository from an external source, where the version is Others. The Collection Entity column provides the name of the entities for which you can collect the data. The XLSM File Name column provides the template name that you will download for the respective collection entity. Download the XLSM template from the File-Based Data Import for Oracle Supply Chain Management Cloud guide (FBDI guide). The Link in Data Import Guide column provides the name of the topic in the FBDI guide from where you will download the template. For example, to collect data for the Items and Item Costs collection entities, refer to the Item Cost Import topic in the FBDI guide.

Collections Entity	Link in Data Import Guide	XLSM File Name
Item Costs	Supply Chain Planning Item Cost	ScpItemCostImportTemplate.xlsm
Customer Specific Item Relationships	Supply Chain Planning Item Substitute	ScpItemSubstituteImportTemplate.xlsm
Planners	Supply Chain Planning Planners	ScpPlannersImportTemplate.xlsm
Organizations (Warehouses) and Organization Site (Including Organization Site - Internal Location Mapping)	Supply Chain Planning Organizations	ScpOrganizationImportTemplate.xlsm
Subinventories	Supply Chain Planning Subinventories	ScpSubInventoryImportTemplate.xlsm
Suppliers and Supplier Sites	Supply Chain Planning Suppliers	ScpPlanningSupplierImportTemplate.xlsm
Item Suppliers	Supply Chain Planning Approved Supplier List	ScpApprovedSupplierListImportTemplate.xlsm
Interlocation Shipping Networks	Supply Chain Planning Interlocation Shipping Methods	ScpInterLocationShipMethodsImportTemplate.xlsm
Currencies, Currency Conversion Types, and Currency Conversion Rates	Supply Chain Planning Currencies	ScpCurrencyImportTemplate.xlsm
Units of Measure, Units of Measure Conversions, and Units of Measure Class Conversions	Supply Chain Planning Units of Measure	ScpUOMImportTemplate.xlsm
Calendars, Calendar Exceptions, Calendar Shifts, Week Start Dates, Period Start Dates, and Calendar Shift Workday Pattern	Supply Chain Planning Calendars	ScpCalendarImportTemplate.xlsm
Calendar Associations	Supply Chain Planning Calendar Assignments	ScpCalendarAssignmentsImportTemplate.xlsm
Demand Classes	Supply Chain Planning Demand Classes	ScpDemandClassImportTemplate.xlsm
Ship Mode of Transport, Ship Class of Service, and Carrier	Supply Chain Planning Carriers	ScpCarrierImportTemplate.xlsm
Allocation Assignments and Allocation Rules	Supply Chain Planning Planning Allocation Rules	ScpPlanningAllocationRulesImportTemplate.xlsm
ATP Assignments and ATP Rules	Supply Chain Planning Available-to-Promise Rules	ScpATPRulesImportTemplate.xlsm
Supply Update Rule	Supply Chain Planning Real Time Supply Updates	ScpRealTimeSupplyUpdatesImportTemplate.xlsm
Freight Terms, FOB Points, Invoicing and Accounting Rules, Shipment Priorities, Payment Terms, Return Reason, Tax Classification Code, Tax Exemption Reason, Sales Credit Type, Activity Type, Document Categories, Payment Methods, and Receipt Methods	Supply Chain Planning Order Orchestration	ScpOrderOrchestrationImportTemplate.xlsm
Measures	Supply Chain Planning Measures	ScpMeasuresImportTemplate.xlsm
Booking History	Supply Chain Planning Bookings History	ScpBookingHistoryImportTemplate.xlsm
Option Booking History	Supply Chain Planning Option Bookings History	ScpOptionBookingHistoryImportTemplate.xlsm
Shipment History	Supply Chain Planning Shipments History	ScpShipmentHistoryImportTemplate.xlsm
Option Shipment History	Supply Chain Planning Option Shipments History	ScpOptionShipmentHistoryImportTemplate.xlsm
Price Lists	Supply Chain Planning Price Lists	ScpPriceListImportTemplate.xlsm
Causal Factors	Supply Chain Planning Causal Factors	ScpCausalFactorsImportTemplate.xlsm
Forecasts Measures	Supply Chain Planning Forecast Measures	ScpForecastMeasureImportTemplate.xlsm Note: This template has been superseded by the generic template ScpMeasuresImportTemplate.xlsm, but will continue to be supported. Future enhancements will be made only to the generic measures template.
Fiscal Calendars	Supply Chain Planning Fiscal Calendars	ScpFiscalCalendarImportTemplate.xlsm
Forecasts	Supply Chain Planning External Forecast	ScpExternalForecastImportTemplate.xlsm
User-Defined Hierarchies	Supply Chain Planning User-Defined Hierarchies	ScpUser-DefinedHierarchyImportTemplate.xlsm
Safety Stock Levels	Supply Chain Planning Safety Stock Levels	ScpSafetyStockLevelImportTemplate.xlsm
Supply Reservations to Sales Orders	Supply Chain Planning Reservations	ScpReservationImportTemplate.xlsm
On Hand	Supply Chain Planning Supply On Hand	ScpOnhandImportTemplate.xlsm
Purchase Orders, Purchase Requisitions, PO in Receiving, and In Transits	Supply Chain Planning Purchase Order Requisitions	ScpPurchaseOrderRequisitionImportTemplate.xlsm
Transfer Orders	Supply Chain Planning Transfer Orders	ScpTransferOrderImportTemplate.xlsm
Supplier Capacity	Supply Chain Planning Approved Supplier Capacity	ScpApprovedSupplierCapacityImportTemplate.xlsm
Resources and Resource Shifts	Supply Chain Planning Resources	ScpResourcesImportTemplate.xlsm
Resource Availability	Supply Chain Planning Resource Availability	ScpResourceAvailabilityImportTemplate.xlsm
Work Definition (Including mapping between Item Structures and Work Definitions), Work Definition Operations, and Work Definition Operation Resources	Supply Chain Planning Routings	ScpRoutingsImportTemplate.xlsm
Work Order Supply	Supply Chain Planning Work Order Supplies	ScpWorkOrderSuppliesImportTemplate.xlsm
Work Order Material Requirements	Supply Chain Planning Work Order Component Demands	ScpWIPComponentDemandsImportTemplate.xlsm
Work Order Resource Requirements	Supply Chain Planning Work Order Operation Resources	ScpWIPOperationResourceImportTemplate.xlsm
Planned Order Supplies	Supply Chain Planning Planned Order Supply	ScpPlannedOrderSupplyImportTemplate.xlsm
Sourcing Rule and Assignments	Supply Chain Planning Sourcing Rules	ScpSourcingImportTemplate.xlsm
Cross Reference Mapping Information	Supply Chain Planning Cross-Reference Data	ScpCrossReferenceDataImportTemplate.xlsm
Key Customer Options	Supply Chain Planning Key Customer Options	ScpKeyCustomerOptionsImportTemplate.xlsm

Collect Data from External Source - Version External

The following table lists the collections entities that can be loaded into the planning data repository from an external source, where the version is External. The Collection Entity column provides the name of the entities for which you can collect the data. The XLSM File Name column provides the template name that you will download for the respective collection entity. Download the XLSM template from the File-Based Data Import for Oracle Supply Chain Management Cloud guide. The Link in Data Import Guide column provides the name of the topic in the File-Based Data Import for Oracle Supply Chain Management Cloud guide (FBDI guide) from where you will download the template. For example, to collect data for the Items and Item Costs collection entities, refer to the Item Cost Import topic in the File-Based Data Import for Oracle Supply Chain Management Cloud guide. All the planning-related entity names are prefixed with Supply Chain Planning in the FBDI guide.

Collection Entities	Link in FBDI Guide	XLSM File Name
Items	Supply Chain Planning Items	ScpItemImportTemplate.xlsm
Item Costs	Supply Chain Planning Item Cost	ScpItemCostImportTemplate.xlsm
Item Relationships	Supply Chain Planning Item Substitute	ScpItemSubstituteImportTemplate.xlsm
Catalogs, Categories, and Item Categories	Supply Chain Planning Catalogs	ScpCatalogImportTemplate.xlsm.xlsm
Item Structures	Supply Chain Planning Item Structures	ScpBillofMaterialImportTemplate.xlsm
Bill of Resources	Supply Chain Planning Bill of Resources	ScpBillOfResourcesImportTemplate.xlsm
Planners	Supply Chain Planning Planners	ScpPlannersImportTemplate.xlsm
Customers and Customer Sites	Supply Chain Planning Customers	ScpCustomerImportTemplate.xlsm
Regions	Supply Chain Planning Regions	ScpRegionsImportTemplate.xlsm
Zones	Supply Chain Planning Zones	ScpZonesImportTemplate.xlsm
Region-Zone Mapping	Supply Chain Planning Region Zone Mappings	ScpRegionZoneMappingImportTemplate.xlsm
Locations and Region-Location Mapping	Supply Chain Planning Locations	ScpLocationsImportTemplate.xlsm
Organizations and Organization Sites	Supply Chain Planning Organizations	ScpOrganizationImportTemplate.xlsm
Subinventories	Supply Chain Planning Subinventories	ScpSubInventoryImportTemplate.xlsm
Suppliers and Supplier Sites	Supply Chain Planning Suppliers	ScpSupplierImportTemplate.xlsm
Item Suppliers (Approved Supplier List)	Supply Chain Planning Approved Supplier List	ScpApprovedSupplierListImportTemplate.xlsm
Interlocation Shipping Networks and Transit Times	Supply Chain Planning Interlocation Shipping Methods	ScpInterLocationShipMethodsImportTemplate.xlsm
Currencies and Currency Conversions	Supply Chain Planning Currencies	ScpCurrencyImportTemplate.xlsm
Units of Measure, Units of Measure Conversions, and Units of Measure Class Conversions	Supply Chain Planning Units of Measure	ScpUOMImportTemplate.xlsm
Calendars, Calendar Exceptions, Shifts, Shift Workday Pattern, Week Start Dates, and Period Start Dates	Supply Chain Planning Calendars	ScpCalendarImportTemplate.xlsm
Calendar Associations	Supply Chain Planning Calendar Assignments	ScpCalendarAssignmentsImportTemplate.xlsm
Demand Classes	Supply Chain Planning Demand Classes	ScpDemandClassImportTemplate.xlsm
Carrier, Ship Mode of Transport, and Ship Class of Service	Supply Chain Planning Carriers	ScpCarrierImportTemplate.xlsm
GOP Allocation Rules and Rule Assignments	Supply Chain Planning Planning Allocation Rules	ScpPlanningAllocationRulesImportTemplate.xlsm
GOP ATP Rules and Rule Assignments	Supply Chain Planning Available-to-Promise Rules	ScpATPRulesImportTemplate.xlsm
GOP Supply Update Rules	Supply Chain Planning Real Time Supply Updates	ScpRealTimeSupplyUpdatesImportTemplate.xlsm
Order Orchestration Reference Objects: Freight Terms, FOB Points, Invoicing and Accounting Rules, Shipment Priorities, Payment Terms, Return Reason, Tax Classification Code, Tax Exemption Reason, Sales Credit Type, Activity Type, Document Categories, Payment Methods, and Receipt Methods	Supply Chain Planning Order Orchestration	ScpOrderOrchestrationImportTemplate.xlsm
Cross Reference Mapping Information	Supply Chain Planning Cross-Reference Data	ScpCrossReferenceDataImportTemplate.xlsm
Measures	Supply Chain Planning Measures	ScpMeasuresImportTemplate.xlsm
Booking History	Supply Chain Planning Bookings History	ScpBookingHistoryImportTemplate.xlsm
Option Booking History	Supply Chain Planning Option Bookings History	ScpOptionBookingHistoryImportTemplate.xlsm
Shipment History	Supply Chain Planning Shipments History	ScpShipmentHistoryImportTemplate.xlsm
Option Shipment History	Supply Chain Planning Option Shipments History	ScpOptionShipmentHistoryImportTemplate.xlsm
Price Lists	Supply Chain Planning Price Lists	ScpPriceListImportTemplate.xlsm
Causal Factors	Supply Chain Planning Causal Factors	ScpCausalFactorsImportTemplate.xlsm
Forecast Measures	Supply Chain Planning Forecast Measures	ScpForecastMeasureImportTemplate.xlsm Note: This template has been superseded by the generic template ScpMeasuresImportTemplate.xlsm, but will continue to be supported. Future enhancements will be made only to the generic measures template.
Fiscal Calendars	Supply Chain Planning Fiscal Calendars	ScpFiscalCalendarImportTemplate.xlsm
Measures, Sales and Operations Planning Backlog, Inventory, and Production History	Supply Chain Planning Measures	ScpMeasuresImportTemplate.xlsm
User-Defined Hierarchies	Supply Chain Planning User-Defined Hierarchies	ScpUser-DefinedHierarchyImportTemplate.xlsm
Forecasts	Supply Chain Planning External Forecasts	ScpExternalForecastImportTemplate.xlsm
Sales Orders	Supply Chain Planning Sales Orders	ScpSalesOrderImportTemplate.xlsm
Safety Stock Levels	Supply Chain Planning Safety Stock Levels	ScpSafetyStockLevelImportTemplate.xlsm
Supply Reservations to Sales Orders	Supply Chain Planning Reservations	ScpReservationImportTemplate.xlsm
On Hand	Supply Chain Planning Supply On Hand	ScpOnhandImportTemplate.xlsm
Purchase Orders, Purchase Requisitions, PO in Receiving, In Transits	Supply Chain Planning Purchase Order Requisitions	ScpPurchaseOrderRequisitionImportTemplate.xlsm
Transfer Orders (including expense type transfers)	Supply Chain Planning Transfer Orders	ScpTransferOrderImportTemplate.xlsm
Supplier Capacity	Supply Chain Planning Approved Supplier Capacity	ScpApprovedSupplierCapacityImportTemplate.xlsm
Resources, Resource Shifts	Supply Chain Planning Resources	ScpResourceImportTemplate.xlsm
Resource Availability	Supply Chain Planning Resource Availability	ScpResourceAvailabilityImportTemplate.xlsm
Work Definition (including mapping between Item Structures and Work Definitions), Work Definition Operations, Work Definition Operation Resources	Supply Chain Planning Routings	ScpRoutingsImportTemplate.xlsm
Work Order Supply	Supply Chain Planning Work Order Supplies	ScpWorkOrderSuppliesImportTemplate.xlsm
Work Order Material Requirements	Supply Chain Planning Work Order Component Demands	ScpWIPComponentDemandsImportTemplate.xlsm
Work Order Resource Requirements	Supply Chain Planning Work Order Operation Resources	ScpWIPOperationResourceImportTemplate.xlsm
Planned Order Supplies	Supply Chain Planning Planned Order Supply	ScpPlannedOrderSupplyImportTemplate.xlsm
Sourcing Rule and Assignments	Supply Chain Planning Sourcing Rules	ScpSourcingImportTemplate.xlsm
Key Customer Options	Supply Chain Planning Key Customer Options	ScpKeyCustomerOptionsImportTemplate.xlsm

Run the Load Planning Data from Files Process

To load planning data from files, first you must prepare the data you want to load. To prepare the data, download the relevant XLSM template, update the XLSM template with required data, and create the necessary CSV files for upload. This procedure explains how to load planning data from files after you have prepared the data and created CSV files.

1. From the Navigator, use the File Import and Export page to upload the previously prepared and zipped CSV files to the Universal Content Manager. Use the account scm/planningDataLoader/Import to upload the zipped file.

   Note: For more information about uploading files to the Universal Content Manager server, see the following section in the Oracle SCM Cloud Implementing Common Features for Oracle SCM Cloud guide: External Integration chapter, External Data Integration Services for Oracle Cloud section.

2. From one of the Supply Chain Planning work areas or Setup and Maintenance work area, Supply Chain Planning offering, select the Load Planning Data from Files task.

3. Complete the following parameters on the Load Planning Data from Files page:

   1. Select the source system.

   2. Select Collection Type: Net change or Target.

   3. Select the .zip file you previously imported into the Universal Content Manager.

4. Click Submit. Make a note of the process ID. You will need this process ID to review the status of the process.

Verify Collection Processes

Verify the Load Planning Data from Files Process

Perform the following steps to verify the process status of the uploaded file and review log file for any errors or warnings.

1. In the Navigator, click Scheduled Processes.

2. In the search area, enter the process ID you noted when you submitted during the Load Planning Data from Files process. Click Search.

3. Monitor the process to verify completion.

   If the process completes with warnings, select the request that shows the warning status and click the View Log button to review the details.

4. For the rows with errors, resolve the issues found in the log file, and then upload the CSV file again. To load only the revised rows, use the Net Change option.

Review Data in the Planning Data Repository

You can review the data collected or loaded into the planning data repository using two different options. The option you use depends on which data collection entities you want to review.

To review the data collected or loaded into the planning data repository, use one of the following options:

• Review data using the Plan Inputs page layout

• Review data using the Maintain Supply Network Model page

To review the following entities, use the Maintain Supply Network Model page:

• Organizations

• Customers

• Suppliers

• Carriers

• Interlocation Shipping Networks

To review data that is not part of the supply network model, use the Plan Inputs page layout. You can view the following data in the Plan Inputs page layout

• Supply data

• Demand data

You can view Carriers and Suppliers using either option.

Review Data Using the Plan Inputs Page Layout

Perform the following steps to review the planning data that you loaded.

1. In the Navigator, click Plan Inputs.

2. From the Plans menu, right-click Plan Inputs and click Open.

   
   Tip: You can set the preview pane to Full Pane for viewing your data in full pane. Click Change and select Full Pane.

3. On the Plan Inputs page, click Open, and click Full Pane.

4. On the Open Table, Graph, or Tile Set page, search for the table name.

5. Enter the criteria for the data you want to verify and click Search.

6. Review the data in the Search Results table.

Review Data Using the Maintain Supply Network Model Page

Perform the following steps to review the planning data using the Maintain Supply Network Model page.

1. In the Navigator, click Plan Inputs.

2. From the Tasks menu, click Maintain Supply Network Model.

3. Enter the criteria for the data you want to verify and click Search.

4. Review the data in the Search Results table.

Aggregate Customer Data

How You Aggregate Customer Data

Use the key customer data options collections template to identify key customers. The data for these customers will be visible. For each Zone, all non-key customers' data will be aggregated to a member named All Other. By aggregating the planning data for non-key customers, you can focus your analysis on the key customers. You use the ScpKeyCustomerOptionsImportTemplate.xlsm to identify the key customers; the rest of the customers' data will be aggregated under an All Other member.

The data that are not identified in the upload template are aggregated to an all other member for each zone. You can view the key customers and the All Other member containing the aggregated non-key customer data when you analyze the forecasts and other data.

Identifying key customers and aggregating non-key customer data helps you to do the following:

• Organize key customer data that are required for planning

• Save time by collecting only the required data from Oracle Supply Chain Management Cloud

• Build a plan specifically for your key customers

How can I reset the key customer aggregated data for a plan?

After you make changes to the aggregation level values in the ScpKeyCustomerOptionsImportTemplate.xlsm file, you must upload the file and run the plan again.

To reset the key customer aggregated data for a plan, do the following:

1. Review the ScpKeyCustomerOptionsImportTemplate.xlsm file.

2. Update the Aggregation Level values for all of the Level Name values (for example, Customer) and upload the CSV file.

3. From your Supply Chain Planning work area, open the plan and enable the Aggregate non-key customer data to All Other level member check box. Run the plan again.

Considerations for Collecting Key Customer Information

Use the ScpKeyCustomerOptionsImportTemplate.xlsm file to identify the key customers for which nonaggregated data must be made available. For non-key customers, the aggregation level that you define in the import template determines whether the data is retained or aggregated. You can differentiate between key customers and non-key customers and use the aggregated key customer data to build a plan specifically for your key customers.

Note: For details regarding the ScpKeyCustomerOptionsImportTemplate.xlsm file, refer to the File-Based Data Import for Oracle Supply Chain Management Cloud guide. This guide is one of the guides in the Oracle Help Center for Oracle Supply Chain Management Cloud. Use the Books link for a list of the guides by category, and look for the Development category.

In the ScpKeyCustomerOptionsImportTemplate.xlsm file template:

1. Define your key customers on the KeyCusOptnHeader tab. Enter the name of a valid customer hierarchy in the Hierarchy Name column.

2. Next, enter the level of that hierarchy in the Level Name column. All customers in this level are identified as key customers.

3. To have only certain customers identified as key customers, enter the specific customer names on the KeyCusOptnMembers detail tab.

4. Set the aggregation level values for both key and non-key customers. Use the settings in the template to set the data to different aggregation levels, such as 1, 2, or 3.

5. Upload the template.

Ignore Aggregate by Zone

There are two Customer hierarchies--Customer and Customer Zone--where the lowest level of each hierarchy is Customer Site. If you don't have any key customers, leave the Hierarchy Name and Hierarchy Level columns blank on the KeyCusOptnHeader tab. All customers not named in the template (non-key customers) are aggregated into an All Other member for the hierarchy.

The upload also creates All Other Zone members for the non-key customers in the Customer Zone hierarchy. If you don't want to aggregate by zone, enter #ignore_zone in the Hierarchy Name column in the KeyCusOptnHeader.csv and leave the Level Name column blank.

Aggregation Levels

The aggregation levels are listed in the following table.

Aggregation Level	Description
1	Retain all customer sites, and aggregate non-key customer sites. In addition to key customer data being available, non-key customer data is retained for plans that require data that is not aggregated. Aggregated customer data is available for plans that require aggregated non-key customer data.
2	Aggregate non-key customer sites. Customers that are not identified as key customers are aggregated to an All Other site by zone. However, if the Hierarchy Name and Level Name columns are blank, all customers are identified as non-key customers and aggregated to an All Other site by zone. This means that there are no key customers.
3	No aggregation of customer sites. All data is available at customer site level.

To remove the key customer designation for previously-loaded customers, use Aggregation Level 3. This enables data for all customers to be made available at the lowest level. No customers are marked as key customers.

If you select the aggregation level 3, the following happens:

• No aggregation is done. All data is at the customer site level only.

• If option 2 or 3 was used in previous collection runs, all non-key customer by zone members and data are deleted.

• Plans using the Key Customer feature become invalid and you have to run them again.

The KeyCusOptnMembers detail tab is optional. Use this tab to identify specific customers as key customers. The Hierarchy Name and Level Name column entries must be the same as the information entered on the KeyCusOptnHeader tab. Enter valid level member names in the Level Member Name column. These members are the only customers that will be identified as key customers.

• If the KeyCusOptnMembers detail tab is empty, all child members of the hierarchy level chosen in the Header tab are flagged as key customers.

• If the KeyCusOptnMembers detail tab is not empty, only the listed members are identified as key customers.

The members must be children of the hierarchy level named on the Header tab.

When you create a plan, there is an option in the Plan Options dialog box that determines what level of customer aggregation is used for the plan:

• Key customer data is available and non-key customer data is aggregated to a level member named All Other.

• No customer data is aggregated for the plan if the option is deselected.

Load Aggregated Customer Data from Oracle E-Business Suite

This topic explains the procedure you follow to load aggregated customer data from an Oracle E-Business Suite source system into your Oracle Supply Chain Planning Cloud destination system.

The procedure is comprised of the following steps:

1. Extract data from your Oracle E-Business Suite source system.

2. Prepare the Supply Chain Planning Key Customer Options file if you have defined key customers in your Oracle E-Business Suite source system.

3. Add the files to your desktop or local hard drive.

4. Import data into your Oracle Supply Chain Planning Cloud destination system.

Additional details for each step are provided in this topic.

Prerequisites

To perform the process required to extract data from your Oracle E-Business Suite source system, you must have an administrator role (Advanced Planning Administrator or Advanced Supply Chain Planner).

Your source system must be set up as one of the Trading Community Source Systems for Oracle Supply Chain Planning Cloud.

You can perform the steps to import data into your Oracle Supply Chain Planning Cloud destination system from one of the Supply Chain Planning work areas. You do not need an administrator role to perform these steps.

Extract Data

To extract the data from your Oracle E-Business Suite source system, run the Extract Data for Oracle Supply Chain Planning Cloud process.

Consider the following conditions for the MSD_DEM_CUSTOMER attribute when you run the process:

• If the MSD_DEM_CUSTOMER_ATTRIBUTE is set to null, then all sites are extracted.

• If the MSD_DEM_CUSTOMER_ATTRIBUTE is set to none, then all records are aggregated to Default Customer Site.

• If the MSD_DEM_CUSTOMER_ATTRIBUTE is set to a valid customer attribute, then all sites are extracted.

The extracted data is stored in a file in the zipped file format in the middle tier of your source system.

Prepare the Key Customer Options File

If you have defined key customers in your Oracle E-Business Suite source system, then perform these steps to prepare the Supply Chain Planning Key Customer Option file:

1. Download the template for file-based data loads for the Supply Chain Planning Key Customer Options object.

2. Add your data to the file.

3. Generate the CSV file.

For details on preparing files for loading planning data, refer to these help topics: Loading Planning Data from Files: Overview and Creating CSV Files Used to Load Planning Data: Procedure.

Add the Files to Your Desktop or Local Hard Drive

Locate the extracted Zip file on your Oracle E-Business Suite middle tier, and download or transfer the file to your desktop or local hard drive.

If you have defined key customers in the Oracle E-Business Suites source system, then include the Key Customer Options file in the Zip file.

Import Data into Your Oracle Supply Chain Planning Cloud Destination System

To import the data into your Oracle Supply Chain Planning Cloud destination system, perform these steps:

1. From the Navigator, click File Import and Export.

2. On the File Import and Export page, perform the upload action using these values:

   • File: The file you created

   • Account: scm/planning DataLoader/Import

3. From one of the Supply Chain Planning work areas, perform the Manage Planning Source Systems task to check if your source system is already created. If your source system is not already created, then create it with the following values:

   • Version: External.

   • Code: Must be the same as the one used for your Oracle E-Business Suite source system.

4. From a Supply Chain Planning work area, perform the Load Planning Data from Files task.