1. HCM Data Loader
  2. Include Reconciliation and Reporting Information

Include Reconciliation and Reporting Information

You can include reference attributes for your spreadsheet rows.

They enable you to record reference data for the spreadsheet row, which could include values already supplied on the spreadsheet row, or source-system information, such as the database-table name, column names, and attribute values from the source system. The Object Status page within the Import and Load Data interface, displays the reference values supplied against your spreadsheet row. You can create OTBI reports to include these values using the HCM Integrations Real Time subject area. The reference names and values are available in the Imported Objects sub-folder within the HCM Data Loader folder.

For example, when loading element entries, you may want to filter and reconcile by the assignment number, element name and amount. This would then allow you to filter by the assignment number and element name, to check the status of the element entry, while reviewing the amount specified for the element entry.

To add a reference attribute to your spreadsheet template:

  1. On the Data Exchange work area, select Spreadsheet Templates.
  2. Search and click the name of the template to edit.
  3. On the Design Tab, click the Add Reference Attribute icon on the Selected Attributes panel toolbar.
  4. Specify which of the 10 reference attributes you want to use and define a reporting name, which will be passed to HCM Data Loader and a column heading to display in the spreadsheet if the attribute is visible.
  5. Optionally configure a default value. For example, you can default the value of the reference attribute to the value of another selected attribute in the template, such as Assignment Number, or Element Name.
  6. Click OK.

You aren't restricted to the values you supply as there is no validation of these attributes. The data supplied to them is stored only in the staging tables. It is not saved to the application tables.

Note: While defaulting values for reference attributes from other selected attributes, ensure that the attribute selected for copying has the same value across all records for the logical object created. Examples of a logical object are new hire, element entry, or salary. Reference attributes are stored only against the top-level record in the object hierarchy. Hence, the upload will fail if the value is sourced from an attribute that changes values across those rows. For example, consider that your template maintains phone numbers for your employees and includes multiple phone records such as work, home, or mobile for the same employee. You can safely default a reference attribute from the Person Number attribute, which will be the same for all entries. However, defaulting a reference attribute to the phone number or phone type will cause three different values to be stored, causing the upload to fail. It is only a concern for templates having duplicate attributes for child records or where multiple spreadsheet rows are supplied for the same record, for example, for date-effective history.

Non-reference attributes specific to the object hierarchy are stored in anonymous stage table columns. It's not possible to retrieve the specific attribute information. Reference attribute values are visible on the Import and Load Data user interface, available in HCM Extracts and OTBI. Using the reference attributes, you can easily create reconciliation reports to filter and report on the attribute values required for your use case.