Load Planning Data from Flat Files
Use the scheduled process named Load Planning Data from Flat Files to load data into the planning repository for Oracle Fusion Cloud Supply Chain Planning from external sources, such as legacy systems and third-party applications.
In addition, you can use the scheduled process to supplement the data collected from an Oracle Fusion source system. For example, you can supplement the collected data with sourcing rule and assignment set data. You can also use the scheduled process to load data from Oracle Fusion Cloud Applications.
Run the scheduled process from the Scheduled Processes work area. You can also submit the scheduled process from your work area for Oracle Supply Chain Planning by clicking Load Planning Data from Files in Plan Inputs on the Tasks panel tab.
You can also submit the scheduled process using the ERP Integrations REST service. For information, see the topic titled ERP Integrations REST Service.
When to Use
Run this scheduled process whenever transaction data needs to be updated. For example, you might want to load sales orders, purchase orders, and work orders nightly to ensure planning has the updated supply and demand data.
You can also run this scheduled process to load reference data. The reference data changes less often, and you need to run the scheduled process only when changes occur. For example, you need to load planner data when a new planner is hired.
Privileges Required
- Perform Order Orchestration and Planning Data Load (MSP_PERFORM_ORDER_ORCHESTRATION_AND_PLANNING_DATA_LOAD_PRIV)
- Run Plan with Snapshot (MSC_RUN_PLAN_WITH_SNAPSHOT_PRIV) Note: You require this privilege to run the scheduled process named Create Trees for Dimensions, which is run as a part of the scheduled process named Load Planning Data From Flat Files if the loaded data pertains to hierarchies, such as those for organizations, items, customers, and suppliers.
Specifications
Before running the scheduled process named Load Planning Data from Flat Files, you must use the file-based data import (FBDI) templates to create one or more comma-separated values (.csv) files for the data you want to load. For information about the import templates, see the guide named File-Based Data Import (FBDI) for SCM.
You must include the .csv files in a compressed (.zip) file and upload the compressed 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.
Check these specifications before you run the process.
| Specification | Description |
|---|---|
| Job Type |
|
| Frequency |
|
| Time of Day | It’s typical for businesses to run the scheduled process at night. However, you can also run this scheduled process during the day if the updates must quickly get into the planning repository. |
| Duration | The duration of the scheduled process varies, depending on how many .csv files are included in the compressed file and the collection type. For example, when first loading data into the planning repository, you’ll be using the targeted collection type to load all organizations, items, customers, suppliers, and so on. This run will take longer to complete than if you were just loading changes that occurred the previous day using the net-change collection type. |
| Compatibility |
|
Parameters
| Parameter | Optional or Required | Description | Parameter Value | Special Combinations Required | Notes |
|---|---|---|---|---|---|
| Source System | Required | The name of the source system from where the data originated, or in the case of an Oracle Fusion source system, the name of the source system that's being supplemented with data. | Name of valid source system | None | If you've selected an Oracle 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. |
| Collection Type | Required | The type of collection. 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. 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. |
Net change Targeted |
None | 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. Before you can use the net-change collection type for an entity, you should have run the scheduled process with the targeted collection type once for the entity. |
| Data File | Required | Name of the compressed (.zip) file containing the .csv files to be processed. | None | None | None |
| Enable Organization Group Collection | Optional | Determines whether only the organizations included in the organization group should be processed. | No Yes |
None | 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. |
| Organization Group | Optional | The group of organizations to be processed when the scheduled process runs. | Name of valid organization group | You must select Yes in Enable Organization Group Collection. | 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. |
| Retain Other External Forecast Designators | Optional | Retains the existing forecast designators in the planning repository when the external forecast is loaded through the import template named Supply Chain Planning External Forecasts (ScpExternalForecastImportTemplate.xlsm) | No Yes |
None | 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. 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. When the collection type is net change, the forecast designators in the planning repository are retained. |
| Enable Date Range for Purging Time-Dimensioned Measures | Optional | Enables the deletion of previously loaded data for time-dimensioned measures for which .csv files are included in the compressed file | No Yes |
None | 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:
In the import templates, you must enter YES in the Delete Indicator column for the combinations for which data must be purged. 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. |
| Number of Days Before Today | Optional | Specifies the number of days before the current date for deletion of previously loaded data from time-dimensioned measures | Numeric value greater than or equal to zero | You must select Yes in Enable Date Range for Purging Time-Dimensioned Measures. | Null value is treated as zero If the value in the Number of Days Before Today and Number of Days After Today fields is zero, the previously loaded data for time-dimensioned measures is purged for the current date. |
| Number of Days After Today | Optional | Specifies the number of days after the current date for deletion of previously loaded data from time-dimensioned measures | Numeric value greater than or equal to zero | You must select Yes in Enable Date Range for Purging Time-Dimensioned Measures. | Null value is treated as zero If the value in the Number of Days Before Today and Number of Days After Today fields is zero, the previously loaded data for time-dimensioned measures is purged for the current date. |
Troubleshooting Information
- You can search for the status of the scheduled process by the process ID in the Scheduled Processes work area.
- See the import templates for instructions on which columns are required, valid values, and date-formatting specifics. For example, date columns must be in YYYY/MM/DD format.
- You can select only compressed files in the Data File field.
- 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.
- 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.
- 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.
- 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.
- To avoid performance-related issues, don't submit the scheduled process again shortly after having submitted it.
- 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.