Load Planning Data from Files

This topic explains how you submit the scheduled process named Load Planning Data from Flat Files from your work area in Oracle Fusion Cloud Supply Chain Planning.

In your work area, on the Tasks panel tab, in Plan Inputs, you can click Load Planning Data from Files to open a dialog box through which you can submit the scheduled process named Load Planning Data from Flat Files. You can use this dialog box to submit the scheduled process from an Oracle Supply Chain Planning work area instead of going to the Scheduled Processes work area.

Before you start

Before you submit your scheduled process, you must prepare a compressed (.zip) file with the comma-separated values (.csv) files for the file-based data import (FBDI) templates that you're using to load your data. The compressed file can contain the .csv files for different import templates.

Then, you must upload your file using the File Import and Export page to the scm/planningDataLoader/import account on the WebCenter Content server. For information about the page, see the guide named Implementing Common Features for SCM.

Points to Note

Note these points while using this feature:

See the instructions in the import templates before using them.
For information about the import templates, see the guide named File-Based Data Import (FBDI) for SCM.
You can load data using a compressed file only once.
Once you load the file, its status changes, and you can't use it again.
You can use the scheduled process named Load Planning Data from Flat Files to load data into your planning repository from external sources, such as legacy systems and third-party applications. You can also use the scheduled process to load data from Oracle Fusion Cloud Applications.
If you've selected a Fusion source system, you can't load some entities. For example, you can't load customers because they're collected with the use of the Collect Planning Data page.
For a list of the allowed entities for different source systems, see the topic titled Import Templates Used to Create CSV Files for Supply Chain Planning.
If any string in your data contains special characters, enclose the entire string in quotation marks.
Ensure that no string in your data contains special characters in the middle.
Otherwise, the scheduled process will end in an error.
When the collection type is targeted, the data in the planning repository is deleted for an entity for which data is loaded through the compressed file, and the data in the compressed file is loaded thereafter. For example, if you're loading item costs through the import template named Supply Chain Planning Item Cost (ScpItemCostImportTemplate.xlsm), the item-cost data in the planning repository is deleted before the data in the compressed file is loaded. The entities for which data isn't loaded through the compressed file remain untouched in the planning repository.
Caution: If you select targeted as the collection type, the data in the planning repository is replaced with data for the entities in the compressed file. There's no way to recover this data. If you accidentally selected the targeted collection type, then you need to reload all the data for the affected entities.
When the collection type is net change, existing data for combinations in the planning repository is updated with changed data for the same combinations in the compressed file. If the combinations don't exist in the planning repository, the combinations are created with the data in the compressed file.
For example, if the compressed file contains data for five item-organization combinations that already exist in the planning repository, the records in the planning repository are updated if the data has changed. If the planning repository contains data for only three item-organization combinations, the records are updated if required for these item-organization combinations, and records are created for the remaining two item-organization combinations.
Note: Before you can use the net-change collection type for an entity, you should have run the scheduled process named Load Planning Data from Flat Files with the targeted collection type once for the entity.
For Oracle Fusion source systems, you can load data by organization groups for only the net-change collection type.
For source systems of the Others or External version, you can load data by organization groups for the targeted or net-change collection type.
The organization groups are those that you set up on the Organizations tab on the Maintain Supply Network Model page.
To know about the entities for which you can load data by organization groups, see the topic titled Load Planning Data from Files for a Selected Group of Organizations.
When you load data by organization groups, data in the compressed file is processed for only the organizations in the selected groups.
Any data in the compressed file that isn't dimensioned by the Organization dimension is ignored during targeted or net change collection for source systems of all versions. If the compressed file contains reference data and demand planning data, such as price lists and history, this data is ignored when you load data by organization groups.
When you load external forecasts using the import template named Supply Chain Planning External Forecasts (ScpExternalForecastImportTemplate.xlsm), you can choose to retain the forecast designators when you're performing a targeted collection of external forecasts for the second or a subsequent time.
This selection isn't relevant when you're performing a targeted collection of external forecasts for the first time because whatever data is in the compressed file will be loaded into the planning repository.
When the collection type is net change, the forecast designators in the planning repository are retained.
If the loaded data pertains to hierarchies, such as those for organizations, items, customers, and suppliers, the scheduled process named Create Trees for Dimensions is called by the scheduled process named Load Planning Data from Flat Files.
Therefore, ensure that you've the privileges for running the scheduled process named Create Trees for Dimensions. Otherwise, the scheduled process will fail, and data won't be loaded correctly.
You can load data for only measures that have the Refresh with current data checkbox selected on the Properties subtab on the Advanced tab in the Create Measure dialog box.
Note: If the measure has the Allow editing checkbox selected in the Create Measure dialog box, you'll lose manually entered measure values whenever you load data. Therefore, you should avoid selecting the Allow editing and Refresh with current data checkboxes together for a measure.
For purging previously loaded data based on a date range for only time-dimensioned measures from the MSC_MEASURE_DATA table, you must use these import templates:
- Supply Chain Planning Bookings History (ScpBookingHistoryImportTemplate.xlsm)
- Supply Chain Planning Causal Factors (ScpCausalFactorsImportTemplate.xlsm)
- Supply Chain Planning Forecast Measures (ScpForecastMeasureImportTemplate.xlsm)
- Supply Chain Planning Measures (ScpMeasuresImportTemplate.xlsm)
- Supply Chain Planning Option Bookings History (ScpOptionBookingHistoryImportTemplate.xlsm)
- Supply Chain Planning Option Shipments History (ScpOptionShipmentHistoryImportTemplate.xlsm)
- Supply Chain Planning Shipments History (ScpShipmentHistoryImportTemplate.xlsm)
In the import templates, you must enter YES in the Delete Indicator column for the combinations for which data must be purged.
Tip: You typically use this feature when you want to purge the data that was recently collected before you load the latest data. For example, if you're loading data for the measure named Bookings History: Booked Item by Scheduled Ship Date, the data would have typically changed over the last few days because of changes in the scheduled ship dates. Therefore, you'd want to load the data for the last few days while making no changes to the data for other time periods. You can't use the net-change collection type in this case because the data for the last few days won't get purged and would instead be updated if required for the same combinations in the planning repository and compressed file.
The null value in the Number of Days Before Today or Number of Days After Today fields is treated as zero. If the value in these fields is zero, the previously loaded data for time-dimensioned measures is purged for the current date.
Ensure that the date range you specify for purging previously loaded data for time-dimensioned measures matches the date range for which you're loading data. If the date range for purging data doesn't match the date range for which you're loading data, you could lose data. The data is loaded for only the dates specified in the .csv files.
For example, if your date range for purging time-dimensioned measures is 01-Nov-2023 to 19-Nov-2023, and your date range for loading data is 06-Nov-2023 to 19-Nov-2023, you'll lose the previously loaded data from 01-Nov-2023 to 05-Nov-2023.
For the date range for purging previously loaded data for time-dimensioned measures, if the profile option code named MSC_FIXED_DATE is set, the profile value is taken as the current date. Otherwise, the system date is taken as the current date.
Your selections for purging data for time-dimensioned measures don't affect the data for measures that aren't dimensioned by time and that are covered by the .csv files in the compressed file.
Ensure that you run only one instance of the scheduled process named Load Planning Data from Flat Files at a time for a combination of a source system and an organization group.
Don't run a targeted collection and a net change collection for the same entity at the same time.
To avoid performance-related issues, don't submit the scheduled process again shortly after having submitted it.

Here's what to do

From your work area in Oracle Supply Chain Planning, on the Tasks panel tab, in Plan Inputs, click Load Planning Data from Files.
The Load Planning Data from Files dialog box opens.
Provide the parameters for the scheduled process:
1. In Source System, select a source system.
  The name can pertain to the external source from which the data originated or the Fusion source system that's being supplemented with the loaded data.
2. In Collection Type, select the collection type.
3. In Data File, select the compressed file that you previously prepared and uploaded to the WebCenter Content server.
4. In Enable Organization Group Collection, select Yes to load data by organization groups.
  Otherwise, select No.
5. If you're loading data for an organization group, in Organization Group, select your organization group.
6. In Retain Other External Forecast Designators, select Yes or No.
7. In Enable Date Range for Purging Time-Dimensioned Measures, select Yes or No.
8. If you're purging data for time-dimensioned measures, enter the date range in the Number of Days Before Today and Number of Days After Today fields.
Enter submission notes for the scheduled process.
To be notified when the scheduled process ends whether the outcome is successful or not, select the checkbox named Notify me when this process ends.
To use the advanced options, click Advanced:
1. On the Schedule tab, select As soon as possible to submit the scheduled process immediately.
  Or, select Using a schedule, and use the fields that appear to submit the scheduled process later or according to a schedule.
2. On the Notification tab, provide the details of individuals who must be notified when the scheduled process ends and the conditions in which the notifications are sent.
Click Submit.
A confirmation dialog box is displayed. You can use the displayed process ID to search for the result of the scheduled process in the Scheduled Processes work area. For more information, see the topic titled Verify the Load Planning Data from Files Process.
Click OK.

What to do next

After loading the data, you can check for errors using the Collected Measure Data table in the Plan Inputs work area. For information, see the topic titled View Collected Data for Measures Before Running a Plan.

For data that you load using the import template named Supply Chain Planning Safety Stock Levels (ScpSafetyStockLevelImportTemplate.xlsm), you must check the MSC_SAFETY_STOCK_TXNS table.