How You Review and Correct Errors

Errors that occur during the import and load stages of data loading are reported automatically on the Import and Load Data page. This topic describes how to review and correct reported errors.

Reviewing Import Errors

The Failed Lines column in both the Data Sets and Business Objects tables shows the number of records that failed to import. When the number in the Failed Lines column is greater than zero, clicking it opens the Failed Lines page. When you open the Failed Lines page from the Data Sets table, it lists:

• The METADATA line for each component

• All messages and the file lines in error for the selected data set

You can:

• Filter the list to show the METADATA lines and the file lines in error for the components of a single business object.

• Use Query by Example fields to show specific file lines or messages.

When you open the Failed Lines page from the Business Objects table, you see details for the selected object by default. You can filter the list to show failed lines for different objects from the same data set.

Examples of physical row errors are:

• The instruction or discriminator isn't recognized.

• The number of values in a data line doesn't match the number in the METADATA line.

• You didn't supply a unique reference for the component.

• The parent of a child component wasn't found, either in the file or in Oracle HCM Cloud.

• A required attribute is missing.

To correct import errors, you correct the source data before importing and loading it again. You need to add the corrected data file to a new .zip file. You can't process the existing file again.

Generating Failed Lines File

You can use the Extract Failed Lines option in both the Data Sets and Business Objects tables toolbar generate a file of failed lines for either a data set or a specific business object within the data set.

To generate a failed lines file:

1. On the Import and Load Data page, select the Data Set or Business Object for which you want to generate the failed lines file.

2. On the Schedule Request page, based on the type of file you want to generate, set one of these values in Actions:

   • Extract failed lines with messages

   • Extract failed lines

3. Specify the language in which the messages must be displayed when extracting the messages.

4. Click Submit to initiate the file generation.

   Use the Failed Lines File column to monitor the progress of the file generation by clicking Refresh. Once the file download icon appears, click the icon to access the generated file.

The Extract Failed Lines option is not enabled by default. To enable it:

1. Go to Setup and Maintenance > Configure HCM Data Loader and override the default for the Enable File Generation for Failed File Lines parameter and set it to one of the following:

   • Extract failed lines - includes only the failed lines

   • Extract failed lines with messages - includes all the messages against a file line or the object it forms immediately before the file line or group of files lines to which the message relates to.

Selecting either of these values enables the Extract Failed Lines option on the Import and Load Data page. The value supplied to this parameter is the default value when generating a file however, you can override the default value when requesting a failed lines file generation.

Accessing the Failed Lines File from the Oracle WebCenter Content Server

When error files are generated, they are encrypted by HCM Data Loader and can only be decrypted when downloading the file from the Import and Load Data page, as described above.

To enable generated error files to be accessed directly from the Oracle WebCenter Content Server:

1. Go to Setup and Maintenance > Configure HCM Data Loader and override the default for the Enable Oracle WebCenter Content Access to Error Files parameter and set it to one of the following:

   • Yes, with no encryption
   • PGP - Signed encryption
   • PGP - Unsigned encryption

When you request a generation of the error file, the File Encryption parameter will be available and defaulted to value selected here.

Note: When choosing to encrypt the file you will have to specify the encryption verification key.

Reviewing Load Errors

The Failed Objects column in both the Data Sets and Business Objects tables shows the number of objects that failed to load. When the number in the Failed Objects column is greater than zero, clicking it opens the Failed Objects Messages page. When you open the Failed Objects Messages page from the Data Sets table, it includes for each object in error:

• Its user keys and any source key

• The component in the object hierarchy for which the error is reported

• The error message

• A link to the object details, which opens the Object Hierarchy page

You can:

• Filter the list to show error details for a specific object in the data set.

• Use Query by Example fields to show specific keys or messages.

When you open the Failed Objects Messages page from the Business Objects table, you see details for the selected object by default. You can filter the list to show messages for different objects from the same data set.

Reviewing Messages

To review the messages for an import or load failure, click the icon in the Messages column of the Data Sets or Business Objects table. When you open the Messages page for a data set, you see for each message:

• The process where the message occurred, which can be Import or Load

• The message location

• The message itself, with the number of occurrences of the message

When you click the message link, you open the Message Details page. It provides details of the message with the information from the Failed Lines or Failed Objects page, as appropriate.

Tip: Messages appear in the session language if the HCM Data Loader configuration parameter Enable UI Message Translation is set to Yes in your environment.

Correcting Objects in Error

On the Object Hierarchy page, which you open from the Failed Object, Message Detail or Object Status page, you can expand object folders to see error details. When you click the name of a component entry, the Attribute Details dialog box opens. It shows the original and current values of each attribute. For components in error, you can edit an attribute to correct it before loading the object again on the Import and Load Details page. You can see how many objects you corrected in the Objects Corrected columns of the tables on the Import and Load Data page. When you click the number in the Objects Corrected column, the Failed Objects page opens for the corrected object.

If you prefer to correct object errors in the source data, then you need to import and load the corrected data again. You must add the corrected data file to a new .zip file. You can't process the existing file again.