1. Integration Playbooks for SCM
  2. File-Based Data Import (FBDI)

File-Based Data Import (FBDI)

With this option, you can use the provided FBDI import templates to quickly create and import data into Oracle Fusion Cloud Supply Chain Planning during the early stages of implementation.

Once you've confirmed the format of the data to be imported into Oracle Supply Chain Planning, you can automate process of exporting data from an external execution system to comma-separated values (CSV) files. For more information, see Load Data into Tables.

Information about key features, best practices, and constraints for the available FBDI templates is in the sections that follow.

Note: Best Practices and Constraints sections appear only where they're applicable.

Applicable to Most FBDI Import Templates

Key Features

  • Upload reference and transactional data into planning from an external source system.
  • Upload reference and transactional data into planning from Oracle E-Business Suite.
  • Upload transactional data into an Oracle Fusion planning source system in cases where the reference data is coming from an Oracle Fusion source system, but the transactional data still exists in a legacy system.

Best Practices

  • It's recommended to keep the combined compressed file close to 100 MB in size, but it varies depending on the pod size. Users with larger pod sizes have been able to upload larger compressed files.
  • If the customer's extract is larger than what ERP Integration Service can support, the compressed files must be split into multiple smaller compressed files.

  • When grouping comma-separated values (CSV) files into multiple smaller compressed (.zip) files, the CSV files must be grouped and uploaded in the order in which the entities are processed.

ScpApprovedSupplierListImportTemplate.xlsm

Key Features

Use this template to define item-supplier, supplier lead time, and supplier calendar.

Best Practices

For drop-shipped assemble-to-order (ATO) models used in Oracle Fusion Cloud Global Order Promising, provide a supplier calendar value whenever supplier lead time is defined for an individual configuration or for a model.

ScpApprovedSupplierCapacityImportTemplate.xlsm

Key Features

Use this template to define supplier capacity for an item-supplier combination.

Best Practices

Before defining supplier capacity, ensure that there's already a record for the item-supplier in the ScpApprovedSupplierListImportTemplate.xlsm template.

ScpBookingHistoryImportTemplate.xlsm

Used for Oracle Demand Management, Oracle Planning Central, Oracle Replenishment Planning, and Oracle Sales and Operations Planning.

Key Features

  • Use this template to upload only the predefined bookings history measures only. See the instructions tab of the FBDI template for the measures that you can upload using this template.
  • The Bookings History and Bookings History Value measures are populated from these measures based on the setting for the MSC_DFLT_BOOKING_HIST_MEASURE profile option. The default is to populate the Bookings History measure from the loaded Bookings History: Booked Item by Booked Date measure and to populate the Bookings History Value measure from the loaded Bookings History Value: Booked Item by Booked Date measure.

Constraints

Bookings History must be loaded at the lowest level:

  • Item
  • Organization
  • Customer Site:
    • Required for Oracle Demand Management, Oracle Planning Central, and Oracle Sales and Operations Planning.
    • Optional for Oracle Replenishment Planning.
  • Demand Class:
    • Required for Oracle Demand Management, Oracle Planning Central, and Oracle Sales and Operations Planning.
    • Optional for Oracle Replenishment Planning.
  • Sales Rep (optional)
  • Day (use the first day of the time period when loading in weekly, monthly, or period buckets).

ScpShipmentHistoryImportTemplate.xlsm

Used for Oracle Demand Management, Oracle Planning Central, Oracle Replenishment Planning, and Oracle Sales and Operations Planning.

Key Features

  • Use this template to upload only the predefined shipments history measures. See the instructions tab of the FBDI template for the measures that you can upload using this template.
  • The Shipments History and Shipments History Value measures are populated from these measures based on the setting for the MSC_DFLT_SHIPMENT_HIST_MEASURE profile option. The default is to populate the Shipments History measure from the loaded Shipments History: Requested Item by Shipped Date measure and to populate the Shipments History Value measure from the loaded Shipments History Value: Requested Item by Shipped Date measure.

Constraints

Shipments History must be loaded at the lowest level:

  • Item
  • Organization
  • Customer Site:
    • Required for Oracle Demand Management, Oracle Planning Central, and Oracle Sales and Operations Planning.
    • Optional for Oracle Replenishment Planning.
  • Demand Class:
    • Required for Oracle Demand Management, Oracle Planning Central, and Oracle Sales and Operations Planning.
    • Optional for Oracle Replenishment Planning.
  • Sales Rep (optional)
  • Day (use the first day of the time period when loading in weekly, monthly, or period buckets).

ScpOptionBookingHistoryImportTemplate.xlsm

Used for Oracle Demand Management.

Key Features

  • Use this template to upload only the predefined Option Bookings History measure.
  • The Configured to Order Level Member Value column contains the concatenated member names of the option and its parents in the bill of materials.
  • The base model history data is loaded in the Bookings History upload template. The base model in the concatenated name must be included in the Bookings History upload template.

Constraints

Option Bookings History must be loaded at the lowest level:

  • Item
  • Organization
  • Customer Site
  • Demand Class
  • Day (use the first day of the time period when loading in weekly, monthly, or period buckets).

ScpOptionShipmentHistoryImportTemplate.xlsm

Used for Oracle Demand Management.

Key Features

  • Use this template to upload only the predefined Option Shipments History measure.
  • The Configured to Order Level Member Value column contains the concatenated member names of the option and its parents in the bill of materials.
  • The base model history data is loaded in the Shipments History upload template. The base model in the concatenated name must be included in the Shipments History upload template.

Constraints

Option Shipments History must be loaded at the lowest level:

  • Item
  • Organization
  • Customer Site
  • Demand Class
  • Day (use the first day of the time period when loading in weekly, monthly, or period buckets).

ScpForecastMeasureImportTemplate.xlsm

Used for Oracle Demand Management.

Key Features

Use this template to upload only predefined forecast measures. See the instructions tab of the FBDI template for the measures that you can upload using this template.

ScpMeasuresImportTemplate.xlsm

Used for Oracle Demand Management, Oracle Planning Central, Oracle Replenishment Planning, and Oracle Sales and Operations Planning.

Key Features

Use this template to load both predefined and user-defined measures for which a specific template doesn't exist.

Constraints

Don't use this template to load any of these measures because there are specific templates for each:

  • Predefined bookings history measures including option history.
  • Predefined shipments history measures including option history.
  • Predefined forecast measures.
  • Predefined or user-defined global causal factors measures.
  • Predefined price measure.

Related Topics