How Data Is Imported and Loaded

HCM Data Loader imports data initially to stage tables, where some validation occurs. HCM Data Loader then loads valid logical objects from the stage tables to the application tables. You can perform the import and load steps either separately or as one step.

This topic summarizes the processing that occurs in each step. It also describes how you specify import and load options.

Importing Records to the Stage Tables

In the import stage, HCM Data Loader:

  • Extracts the business-object data from your .zip file on the Oracle WebCenter Content server and decrypts it, if the file is encrypted.

  • Validates the business-object file name and METADATA definitions and raises any errors.

  • Imports records from the data files into the HCM Data Loader stage tables.

  • Validates the data against attribute data types and raises any errors.

  • Groups the data by local key values to form logical records of related date-effective file lines. For example, all date-effective file lines supplied for a Job object are grouped into a logical occurrence of a job, such as the Accountant job.

  • Forms logical objects by resolving references to parent components. For example, the logical record for a valid grade is associated with its parent Job object.

  • Records the status of all imported objects. View the status when you click the Total Objects count from the Import and Load status page.

Loading Objects to the Application Tables

HCM Data Loader doesn't load valid logical objects directly into the application tables. Instead, it passes valid object data to business-object-specific services. For example, to load Worker objects, HCM Data Loader passes them to the worker service. These services perform the validation that's specific to the business object, raise any errors, and load valid objects to the application tables.

Setting the File Action Parameter

When you import a file on the Import and Load data page, you can set the File Action parameter on the Schedule Request page. The value that you specify here overrides the enterprise default setting. This table describes how the File Action parameter controls import and load.

File Action Value

Description

Import and load

HCM Data Loader imports the contents of the .zip file to the stage tables and calls object services to load valid logical objects to the application tables.

Import only

HCM Data Loader imports the contents of the .zip file to the stage tables but doesn't pass valid logical objects to the relevant object service. Instead, you perform that step separately on the Import and Load data page by clicking Submit and selecting the Load action for each business object.

You may want to select Import only when you start to load data so you can fix import errors before attempting to load objects. Once your data loading is routine, use Import and load to run them both with one job submission.

Tip: You can validate your data file before you load it. Use the Data File Validator tool for HCM Data Loader. For more information, see Data File Validator Tool for HCM Data Loader (2022617.1) on My Oracle Support at https://support.oracle.com.

Automating Data Loading

When you automate data loading using the HCM Data Loader web service, you can set File Action to Import only or Import and load. If you select Import only, then you load the imported objects manually on the Import and Load Data page.

Reviewing Object History

For some object components, such as Assignment, you can review the object history to see who last updated the object. When the object was last updated using HCM Data Loader, the Last Updated By value is FUSION_APPS_HCM_ESS_LOADER_APPID. You don't see the user name of the user who uploaded the changes.