Browser version scriptSkip Headers

Oracle® Fusion Applications Compensation Management Implementation Guide
11g Release 5 (11.1.5)
Part Number E20376-05
Go to contents  page
Contents
Go to Feedback page
Contact
Us

Go to previous page
Previous
Go to previous page
Next

7 Common Applications Configuration: Define Batch Data Loads

This chapter contains the following:

The Load Batch Data Process: Explained

Loading Batch Data into Oracle Fusion: Explained

Load Batch Data Parameters

Data-Load Batch-Status Values: Explained

Data-Load Object-Status Values: Explained

Uploading Data Using HCM Spreadsheet Data Loader: Explained

Uploading Data Using HCM Spreadsheet Data Loader: Worked Example

FAQs for Define Batch Data Loads

How can I fix HCM Spreadsheet Data Loader errors

How can I manage dependencies between business objects when using HCM Spreadsheet Data Loader

The Load Batch Data Process: Explained

HCM Data Loader, which you invoke using the Load Batch Data task, is an open-interface process for loading volume data, for a specific subset of objects, into Oracle Fusion Human Capital Management (HCM).

As HCM Data Loader uses Oracle Fusion object and service interfaces to load the data, the following occur during the data load:

HCM Data Loader is used:

HCM Data Loader is also available for use by other source applications.

The following figure shows an overview of the data-load process.

HCM Data Loader

To use the HCM Data Loader, you:

  1. Map data between your source application and Oracle Fusion HCM.

  2. Extract data from your source application and place it in the HCM Data Loader staging tables in the supported Oracle Fusion HCM object-data format.

  3. Run the Load Batch Data process to load the data into Oracle Fusion HCM.

Loading Batch Data into Oracle Fusion: Explained

The Load Batch Data process, which you run from the Data Exchange work area, imports data into Oracle Fusion from external sources.

From the Load Batch Data page, you can:

Loading Data for HCM Coexistence

To load data for HCM coexistence, you run the HCM coexistence process Load HCM Data, which comprises two phases: Import and Load. If you select both phases of that process, then the Load Batch Data process runs automatically to complete the Load phase. If you select the Import phase only, then you must run the Load Batch Data process manually to complete the Load phase. In this case, when running Load Batch Data you select the batch name that you created for the HCM coexistence process Load HCM Data.

Monitoring Data Loads

You can monitor the status of a data load in the Batch Status column of the Search Results section of the Load Batch Data page. Detailed information about any data load that you select in the Search Results section appears in the Details section of the page.

Correcting Data Errors

On the Failed tab in the Details section for a batch data load, you can see the details of any errors.

To resolve the errors and complete the data load, you can:

Rerunning Data Loads

After correcting any errors, you can select the batch file in the Search Results section and click Run. Any object with the status Error in Row is reset to Ready to Process and included in the load. Objects with the status Successful or Ignore are not processed.

Load Batch Data Parameters

The Load Batch Data process imports batch data into the Oracle Fusion application tables from the HCM Data Loader's staging tables. You run Load Batch Data from the Data Exchange work area.

When you schedule the Load Batch Data process, you specify values for the following parameters.

Load Batch Data Parameters

Batch Name

The name of the batch file to be loaded.

Loader Chunk Size

The number of logical business objects that a single Load Batch Data thread processes in a single action.

Loader Maximum Errors Allowed

The maximum number of errors in a thread before processing terminates. If an error occurs during the processing of a complex logical business object (such as a person record), then all rows for that business object are rolled back and marked as Error in Row.

Loader Number of Processes

The number of Load Batch Data threads to run in parallel. If you are processing large amounts of data (for example, more than 1000 rows) or complex data (such as person and work relationship data) consider running 4 or 8 threads in parallel.

Data-Load Batch-Status Values: Explained

The Data Exchange work area displays batch-status values for the Load Batch Data and Load HCM Data tasks. This topic explains the batch-status values.


Batch Status

Description

New

The batch is new and has not been processed.

Processing

The data-load process for the batch is currently running.

Refresh AM

The data-load process for the batch is performing an internal refresh against the Application Module (clearing the loader cache).

Canceled

The data-load process for the batch has been canceled.

Complete with Errors

Data-load processing for the batch is complete; object instance errors exist.

System Error

The data-load process for the batch was terminated by a system error.

Complete

The data-load process for the batch completed successfully.

Data-Load Object-Status Values: Explained

From the Batch Summary and Failed tabs in the Details section of the Load Batch Data page, you can display information about the load status of individual business objects. This topic explains the object-status values.


Object Status

Description

New

The object is new and has not been processed.

Pending Action

During the import phase, a validation error occurred for the object instance. (Typically, this status is set by Oracle Data Integrator.)

Ready to Process

The object has not been processed but is ready for processing.

Error in Row

The object is in error. Either the object itself is in error or the complex business object to which it belongs is in error.

Ignore

The object is to be ignored during processing.

Successful

The object has been successfully processed.

Uploading Data Using HCM Spreadsheet Data Loader: Explained

HCM Spreadsheet Data Loader enables you to upload business objects to Oracle Fusion Human Capital Management (HCM) from a spreadsheet. Business objects that you can upload include person and assignment data, grades, jobs, benefit plan types, content items, performance templates, and rating models. You can view the complete list of supported business objects on the Initiate Data Load page, where objects appear in the recommended load order.

This topic describes:

How Data Is Uploaded Using HCM Spreadsheet Data Loader

Uploading business objects using HCM Spreadsheet Data Loader is a two-stage process. You:

  1. Generate a spreadsheet for a single HCM business object, enter data in the spreadsheet, and upload the data to a named batch in the HCM Data Loader staging tables.

    HCM Data Loader is a generic process for loading data to Oracle Fusion HCM from external sources.

  2. Run the Load Batch Data process to transfer data from the HCM Data Loader staging tables to the Oracle Fusion application tables.

The following figure, which also shows one approach to error correction, summarizes both stages of this process.

The HCM Spreadsheet Data Loader

Correcting Upload Errors

When you upload data from a spreadsheet to a batch in the HCM Data Loader staging tables, the status of each spreadsheet row is updated to show whether the row was inserted successfully in the batch. If the row insertion fails, you can double-click the status value to display information about the error. After correcting the error, you upload the corrected data to the existing batch.

Correcting Load Batch Data Errors

When you run Load Batch Data to transfer data from the HCM Data Loader staging tables to the Oracle Fusion application tables, the data is validated.

If errors occur, you can:

When to Use HCM Spreadsheet Data Loader

You can use HCM Spreadsheet Data Loader to create any of the business objects that it supports and edit person and assignment data; however, you cannot use HCM Spreadsheet Data Loader to delete business objects. Supported actions for each business object appear on the Initiate Data Load page.

Each business object is represented as a single row in the spreadsheet. Any hierarchical data that you can upload with HCM Spreadsheet Data Loader has been flattened to accommodate single-row representation.

HCM Spreadsheet Data Loader is most efficient for uploading medium or large amounts of data. For example, if your enterprise has 100 job definitions or 60 performance templates, creating those business objects in a spreadsheet and uploading them to Oracle Fusion HCM is likely to be more efficient than creating them individually using the Create Job or Create Performance Template interfaces. However, if you need to create just a few business objects, it may be quicker to use the Oracle Fusion HCM interfaces.

Who Can Use HCM Spreadsheet Data Loader

To use HCM Spreadsheet Data Loader, you can:

Users who have the Human Capital Management Application Administrator job role can perform the Initiate HCM Spreadsheet Load task. Users who have the Application Implementation Consultant job role can perform both tasks; both job roles inherit the HRC_SPREADSHEET_LOADING_DUTY duty role.

Spreadsheet and Batch Names

If you are uploading several types of business objects over a period of time, devise a naming scheme for the generated spreadsheets that enables you to locate spreadsheets easily on your desktop. For example, you could include both the business-object type and the date in the spreadsheet names. If you upload several batches of data of a single type on one date, you can use a suffix value to differentiate spreadsheets.

Batch names are generated automatically but you can overwrite them. They identify batches submitted to the Load Batch Data process and must be unique. Using the same names for spreadsheets and batches will help you quickly to associate a spreadsheet with the batch to which you load it. For example, for uploading rating models on 01/08/13, you could use the spreadsheet name RatingModels010813.xlsx and the batch name RatingModels010813.

Uploading Data Using HCM Spreadsheet Data Loader: Worked Example

This example shows how to upload positions for the enterprise Sales Department.

The following table summarizes key decisions for this scenario.


Decisions to Consider

In This Example

Which business objects will I load?

Positions

What are my spreadsheet names?

  • SalesPositionsMMDDYYBatchnn.xlsx

  • SalesPositionsMMDDYYBatchnnErrorsnn.xlsx

What is my batch name?

SalesPositionsMMDDYYBatchnn

Where will I fix Load Batch Data errors?

In the spreadsheet SalesPositionsMMDDYYBatchnnErrorsnn.xlsx

Summary of the Tasks

Upload the position data by:

  1. Selecting the Initiate HCM Spreadsheet Load task

  2. Creating the positions spreadsheet

  3. Entering data in the positions spreadsheet

  4. Uploading positions data to the HCM Data Loader staging tables

  5. Loading positions data to the application tables from the HCM Data Loader staging tables

  6. Reviewing the results of the Load Batch Data process and correcting errors

Prerequisites

Before you can complete this task, you must have:

  1. Installed the desktop client Oracle ADF 11g Desktop Integration
  2. Enabled the Trust Center setting Trust access to the VBA project object in Microsoft Excel

Selecting the Initiate HCM Spreadsheet Load Task

  1. On the Overview page of the Setup and Maintenance work area, click the All Tasks tab.
  2. In the Search region, complete the fields as shown in this table.

    Field

    Value

    Search

    Task

    Name

    Initiate HCM Spreadsheet Load


  3. Click Search.
  4. In the search results, click Go to Task for the Initiate HCM Spreadsheet Load task.

    Alternatively, you can start the Initiate HCM Spreadsheet Load task from an implementation project or select the Initiate Data Load task in the Data Exchange work area.

Creating the Positions Spreadsheet

  1. On the Initiate Data Load page, find the entry for Create Position in the list of business objects.

    Notice that Create Position appears after other business objects such as departments, locations, and jobs, emphasizing that those business objects (regardless of how you create them) must be defined before positions.

  2. Click Create Spreadsheet for the Create Position entry.
  3. When prompted, save the spreadsheet locally using the name SalesPositions113012Batch01.xlsx.
  4. When prompted, sign in to Oracle Fusion Applications using your Oracle Fusion user name and password.

Entering Data in the Positions Spreadsheet

  1. In the Batch Name field of the spreadsheet SalesPositions113012Batch01.xlsx, replace the default batch name with the batch name SalesPositions113012Batch01.
  2. Enter position data in the spreadsheet.

    Ensure that you provide any required values and follow instructions in the spreadsheet for creating additional rows.

Uploading Positions Data to the HCM Data Loader Staging Tables

Use the default values except where indicated.

  1. In the positions spreadsheet, click Upload.
  2. In the Upload Options window, click OK.

    As each row of data is uploaded to the HCM Data Loader staging tables, its status is updated.

  3. When uploading completes, identify any spreadsheet rows with the status Insert failed, which indicates that the row failed to upload.
  4. For any row that failed to upload, double-click the status value to display a description of the error.
  5. When you have corrected any errors, click Upload again to load the remaining rows to the same batch.

Loading Positions Data to the Application Tables from the HCM Data Loader Staging Tables

Use the default values except where indicated.

  1. In Oracle Fusion Applications, select Navigator - Workforce Management - Data Exchange.
  2. In the Tasks pane of the Data Exchange work area, click Load Batch Data.
  3. In the Search region of the Load Batch Data page, enter the batch name SalesPositions113012Batch01 in the Batch Name field.
  4. Click Search.
  5. In the Search Results region, select the batch SalesPositions113012Batch01 and click Run.
  6. On the Schedule Request page, click Submit.

Reviewing the Results of the Load Batch Data Process and Correcting Errors

  1. On the Load Batch Data page, search again for the batch SalesPositions113012Batch01 and review its status in the Batch Status column of the Search Results region.
  2. If the batch status is Complete, click Done to close the Load Batch Data page; otherwise, continue with the next step.
  3. If the batch completed with errors, select the batch in the Search Results.
  4. On the Batch Summary tab of the Batch Details region, select Action - Extract Failed Objects to Spreadsheet.

    An errors spreadsheet is created automatically.

  5. Save the errors spreadsheet locally as SalesPositions113012Batch01Errors01.xlsx.
  6. Leave the batch name in the errors spreadsheet as SalesPositions113012Batch01.
  7. Review the error messages in the spreadsheet and correct the errors.
  8. Repeat this process from the section Uploading Positions to the HCM Data Loader Staging Tables until all errors are fixed.

    If further errors occur, increment the errors-spreadsheet suffix by 1 (for example, SalesPositions113012Batch01Errors02, SalesPositions113012Batch01Errors03, and so on.)

  9. Click Done to close the Load Batch Data page.

    To load a new batch of positions for the Sales Department on the same date, increment the batch number in the spreadsheet and batch names (for example, SalesPositions113012Batch02).

FAQs for Define Batch Data Loads

What happens if I cancel a Load Batch Data process?

The Load Batch Data process completes the processing of any business objects currently in progress, but does not process further objects.

Can I load date-effective data using HCM Spreadsheet Data Loader?

Yes. You can create date-effective business objects. You can also update date-effective person and assignment data using HCM Spreadsheet Data Loader.

You cannot delete or correct date-effective data using HCM Spreadsheet Loader.

How can I fix HCM Spreadsheet Data Loader errors?

Errors may occur when you run the Load Batch Data process to transfer data from the HCM Data Loader staging tables to the Oracle Fusion application tables. You can fix these errors in the staging tables by navigating to the object detail from the Total Objects column (click the number of objects) on the Failed tab in the Details section of the Load Batch Data page. This approach may be suitable if there are few errors or you do not need to correct the source data.

Alternatively, you can download error rows from the HCM Data Loader staging tables to a spreadsheet by selecting Action - Extract Failed Objects to Spreadsheet on the Batch Summary tab of the Details region on the Load Batch Data page. In this case, a spreadsheet containing the rows in error is generated automatically. After fixing the errors in the spreadsheet, you upload the corrected data to the staging tables and run Load Batch Data again. This solution is available only for data initially uploaded using HCM Spreadsheet Loader.

How can I manage dependencies between business objects when using HCM Spreadsheet Data Loader?

When you load business objects using HCM Spreadsheet Data Loader, you must take data dependencies into account. For example, any attempt to load positions will fail if the jobs that they reference do not exist. You can avoid data-dependency errors by following the order in which business objects are listed on the Initiate Data Load page. For example, Create Location appears before Create Business Unit on the Initiate Data Load page, which indicates that you must create locations before you can create business units.

You can create business objects using any of the available methods. For example, you can create locations on the Create Location page before uploading business units using HCM Spreadsheet Data Loader.