Data Import Options and Guidelines for Fusion Applications Suite

March 24, 2023 | 8 minute read
Bala Mahalingam
Consulting Solution Architect A-Team
Text Size 100%:


Oracle Cloud Applications suite is the complete cloud applications suite that brings consistent processes and a single source of truth across the business functions—from enterprise resource planning, supply chain management, and human capital management to advertising and customer experience. Oracle Fusion Applications Suite uses a unified data model across all application modules (ERP, SCM, HCM, CX (Sales, Service)).

One of the critical requirements during cloud application implementation is data migration. Data migration includes extract, transformation, and data load components. This blog provides data load/data import options within fusion cloud applications.

Many applications cloud customers implement multiple modules in fusion cloud applications. While architecturally similar, we have purpose-built frameworks for importing data across pillars within fusion cloud applications.

In continuation to my blogs on Data Extraction Options and Guidelines for Oracle Fusion Applications Suite, Options for migrating clean data to Fusion Applications Cloud and implementing multi-pillar Fusion applications, I wanted to share my experience on data import options from Oracle Fusion Applications Suite.

This blog will help you understand available import options and tools in Oracle Fusion Applications Suite.

FA Data Import

Data Import / Ingestion Use Cases

The most common data import/load/migration use cases for Oracle Fusion Applications Suite are:

  1. Ability to load/migrate initial/complete data set from source applications.
  2. Recurring / ongoing bulk data import from source applications.
  3. Incremental data load to keep data in sync between integrated applications.
  4. Mass update back into Oracle Fusion Cloud Applications.
  5. Enable business users to import required (usually small amount) data quickly.
  6. Automation of end-to-end import flows.

Data Import Tools & Options

Fusion Cloud Applications Suite has purpose-built data import options that give customers flexibility in choosing the right tools for data migration. The table below provides a high-level view of available data import capability across all pillars in Fusion Cloud Applications.

Import Option / Capability


Expected Volume

Best suited for





Import Management

Move/Migrate Customer Experience data into Oracle Applications Cloud in the form of CSV files. Make sure that any prerequisite objects already exist in the application.




HCM Data Loader

HCM Data Loader is a powerful tool for bulk-loading and maintaining data





External Data Integration Services

Use External Data Integration Services for Oracle Cloud to load data into the interface tables of Oracle Fusion Applications from external sources. External Data Integration Services uses file-based data import (FBDI) templates and processes to import data.




REST API / SOAP Services

Load data for near real-time integrations

Very Low

Near real-time

Intended for near real-time integrations only, and not recommended for bulk data import.

The table below provides the consolidated Oracle documentation (23A) links for respective data import options from every Fusion Cloud Application Suite pillar. As a best practice use the latest documentation.

Import Option





Import Management

Import Mgmt.

Not applicable

HCM Data Load

Not applicable

HCM Data Loader

Not applicable

Item / Product Data Import**

Not applicable

Product Management

External Data Integration Services

Not applicable








SOAP Services***





** Best Practices for Item Import Performance for Product Hub customers.

*** Use SOAP Services only where REST is not available

Data Import Guidelines

  • Plan your data migration effort and resources carefully.
  • Plan the iteration, sequence of loading, object dependencies, import option/method, and parallelization options during your data migration design.
  • Make sure that your environment is properly sized while migrating full data set.
  • Plan your environment refreshes in advance based on your plan for iterative data migration process.
  • All Oracle Fusion Apps Pods have a database statistics maintenance schedule: Weekly stats are collected on Sunday morning for all objects. In addition, there is a special job to collect statistics for rapidly changing objects which runs every half hour. During high volume data conversion, additional statistics gathering may be required. Collaborate with Oracle support as needed.
  • Plan to bring clean and active transactional data into ERP Cloud, avoid transaction history as migrating the historical data is complex, time consuming and lots of manual work on testing and reconciliation is required. Plan archiving and reporting strategy for historical data.
  • Understand the supported objects and volume/size limitations from pillar (HCM / CX / ERP / SCM) documentation based on your import option.
  • Consider mode of integration (batch or real-time), type of integration (synchronous or asynchronous), frequency (daily, weekly, monthly, …), data volume (# of records to be retrieved/processed), expected file size, storage/retrieval options, duration, and performance while choosing the import option.
  • Document the data import requirements and design the solution by considering usage of data, automation, and performance.
  • Plan your resources for data cleansing and exception handling. Do the necessary data cleansing and pre-validation in your source applications to eliminate any data rejections like duplicate legal names, tax registration numbers, etc.  
  • ERP and SCM Import processes are executed by the Enterprise Scheduler Service (ESS), which manages all concurrent processes. Plan to monitor the status of each process and access the output reports.
  • Do the import in multiple smaller batches instead of using a single big batch to expedite the import process.
  • Purge the interface tables regularly so that the processed records are removed. Keeping the interface tables empty will help improve the performance of the import jobs.
  • Leverage standard error and exception handling processes.
  • Consider Security, compliance, data privacy, encryption requirements while designing the data migration solution.
  • Leverage Oracle Infrastructure Cloud (OIC) and Oracle Integration Cloud (OIC) capabilities for orchestrating and automating the data imports and integrations.
  • Avoid using REST API / SOAP services for importing/loading high-volume data set into Oracle Fusion Cloud Application. REST API / SOAP services are recommended only for near real-time integrations.
  • Always refer to the latest documentation to get updates on features.
  • Research cloud customer connect if you find gaps and create ideas as needed.
  • Log a Service Request with Oracle if any of the above import options doesn’t meet your needs to get the right guidance.


To summarize the data import option selection for Oracle Fusion Cloud Application implementation, leverage the purpose-built standard import capabilities - HCM Data Loader for HCM, Import Management for CX, Item Publication for Products/Items, FBDI for ERP and SCM.

I hope this blog will enable your organization's data import processes efficiently.


Note: Always refer to the latest documentation.

  1. Oracle Cloud ERP Data Migration Recommendations and Best Practices
  2. Best practices from Oracle Support
    1. Using External Data Integration Services for Oracle ERP Cloud (Doc ID 2102800.1)
    2. Oracle Cloud ERP Data Migration Recommendations and Best Practices (Doc ID 2888897.1)
    3. Oracle CX Sales: Getting Started with Your Sales Implementation: Quick Import Macros (Doc ID 2229503.1)
    4. External Data Loader Client (EDLC) (Doc ID 2325249.1)
    5. Data Migration & Import and Export Management Resource Center (Oracle CX Sales and B2B Service) (Doc ID 2004646.1)
    6. Steps To Import Items Using FBDI (Recommended for Non-Product Hub Customers - CRM, FIN, PRC etc.) (Doc ID 1642772.1).
    7. Oracle HCM Cloud: Data Loading and Data Extraction Best Practices (Doc ID 2043581.1)


Bala Mahalingam

Consulting Solution Architect A-Team

Bala has over 27 years of techno-functional and hands-on product development, implementation, solution architecture  and consulting delivery experience with most of his career spent in architecture, design, development and deployment of applications and technology both on-premises and cloud. His expertise on data management, data integration, data quality and data governance has enabled him to help several customers globally in Hi-Tech, healthcare, financial, life-sciences, automotive and manufacturing industries.

Previous Post

Scaling Web Application Firewalls, Network Load Balancers, and Next Gen Firewalls in OCI

Raffi Shahabazian | 7 min read

Next Post

A routing scenario, transit traffic on OCI - Part Two

Andrei Stoian | 5 min read