1. HCM Data Loader
  2. How Data Is Loaded Using HCM Data Loader

How Data Is Loaded Using HCM Data Loader

This topic outlines the process of loading data in bulk from .dat files using HCM Data Loader. The data can be from any source.

This figure provides a high-level summary of the process.
This figure shows the flow from the user to the Oracle WebCenter Content server, and from there to HCM Data Loader. It shows that errors detected in the import stage are reported to the user, who can correct them and upload another file. Objects that get through the import stage successfully are loaded to the application tables. Errors detected in the load stage are also reported to the user, who can correct them and upload another file.

The steps of this process are:

  1. You place a .zip file containing your .dat files on the Oracle WebCenter Content server. You can upload your file directly to the server, or use the HCM Data Loader interface for local files.

  2. You submit a request to HCM Data Loader to import and load the .zip file. For this step, you can use either the HCM Data Loader interface or the HcmCommonDataLoader web service.

  3. HCM Data Loader decompresses the .zip file and imports individual data lines to its stage tables. In the stage tables, related data lines are grouped to form business objects.

    Any errors that occur during the import phase are reported on the HCM Data Loader interface.

  4. HCM Data Loader elevates the user before calling the relevant logical object interface method (delivered in product services) to load valid objects to the application tables.

    Any errors that occur during the load phase are reported in the HCM Data Loader interface.

  5. You review any errors from the import and load phases. You can perform this step either on the HCM Data Loader interface or using the HCM Data Loader Data Set Summary extract.

  6. You correct errors from the import and load phases in your source data.

  7. You load a new .zip file containing the corrected data to the WebCenter Content server.

You repeat this process from step 2 until all of the data is successfully loaded.

Note: By loading your data with the elevated user, HCM Data Loader bypasses the data security policies configured for the session user. However, you must supply data in the language configured for the FUSION_APPS_HCM_ESS_LOADER_APPID user, usually it is the base language of your environment.
Tip: You can also correct load errors interactively on the HCM Data Loader interface and resubmit any corrected data from there.

Related Topics