HR Table Mapping

Before migrating data, your tables must be mapped correctly.

About this task

By default, all base-system tables in the global version of HR should map correctly to the corresponding tables in the scoped version. You can view the Migration Tables list to see the old tables from global HR and the new tables in scoped HR.

If you changed tables or added custom tables to the global version of HR and want to migrate them to the scoped version of HR, use Migration Tables. Changed or added tables in the global version require a target table in the scoped version of HR. This process is also called table mapping.

Note: Dependencies determine the order the tables appear. When adding new tables, add them at the end of the Migration Tables list and ensure that dependencies are complete.

Because tables have a hierarchical structure, start your data mapping from Table Mappingand then map columns and choice list data. Table Mapping provides a top-level view into what mapping is required. A table can have multiple columns and columns can have choice lists.

For example, the sn_hr_core_profile_bank_account table has multiple columns and several choices in the choice list.

  • The account_type column has a choice list with three values:
    • Checking
    • Savings
    • Other

Procedure

  1. Navigate to HR Migration > Data Mapping > Table Mapping.
  2. Click New or edit an existing table.
    OptionDescription
    Active Select to activate the migration table selected. When not selected, HR Migration skips this table.
    Global table name Enter the name of the custom table created in the global version of HR.
    Scoped table name Enter the name of the target table for the scoped version of HR.
    Order Enter a numeric value that determines the order the tables are migrated when data migration runs
  3. Click Submit or Update and the Migration Columns section appears. Verify that all columns are mapped. Refer to HR Column Mapping.