Loading Work Structures Using HCM Data Loader

7/24/2019 Loading Work Structures Using HCM Data Loader

1/77

Loading Work Structures

Using HCM Data Loader

Oracle Fusion Human Capital Management 11g Release 9 (11.1.9)

O R A C L E W H I T E P A P E R | J A N U A R Y 2 0 1 6


2/77

LOADING WORK STRUCTURES USING HCM DATA LOADER

Table of Contents

Table of Figures 1

Introduction 1

How to Use the Information in This Document 1

Example Dat Files 2

Location 3

Considerations and Prerequisites for Location 3

Loading Locations 3

Location Errors 11

Changing the Logical Start and End Date for Location 11

Deletion Support for Location 11

Location Translation 12

Grade 13

Considerations and Prerequisites for Grade 13

Loading Grades 13

Grade Errors 16

Changing the Logical Start and End Date for Grade 17

Deletion Support for Grade 17

Grade Translation 17Grade Step Translation 18

Grade Rate 20

Considerations and Prerequisites for Grade Rate 20

Loading Grade Rates 20

Grade Rate Errors 23

Deletion Support for Grade Rate 24

Grade Rate Translation 24

Grade Ladder 26Considerations and Prerequisites for Grade Ladder 26

Loading Grade Ladder 26

Grade Ladder Errors 32

Deletion Support for Grade Ladder 33

Grade Ladder Translation 33


3/77


Step Rate Translation 34

Job Family 36

Considerations and Prerequisites for Job Family 36

Loading Job Family 36

Deletion Support for Job Family 37

Job Family Translation 38

Job 39

Considerations and Prerequisites for Job 39

Loading Job 39

Job Errors 48

Deletion Support for Job 48

Job Translation 49

Organization 50

Considerations and Prerequisites for Organization 50

Loading Organization 50

Organization Errors 57

Deletion Support for Organization 57

Organization Translation 58

Position 60Considerations and Prerequisites for Positions 60

Loading Position 60

Position Errors 69

Deletion Support for Position 70

Position Translation 71

Table of Figures

Figure 1: Create Location ......................................................................................................................................... 5Figure 2: Manage Locations: Other Addresses ........ ......... ......... ......... ........ ......... ......... ........ ......... ......... ......... ........ . 7Figure 3: Create Location: Extra Information ............................................................................................................ 8Figure 4: Create Location: Legislative Information ........ ......... ........ ......... ......... ......... ........ ......... ......... ........ ......... ... 10Figure 5: Create Grade ........................................................................................................................................... 14Figure 6: Create Grade: Grade Step Details ........................................................................................................... 15Figure 7: Create Grade Rate .................................................................................................................................. 21Figure 8: Grade Rate Values .................................................................................................................................. 23


4/77


Figure 9: Create Grade Ladder ............................................................................................................................... 27Figure 10: Create Grade Ladder: Grades ............................................................................................................... 29Figure 11: Create Grade Ladder: Grade Step Rates .............................................................................................. 30 Figure 12: Create Job Family ................................................................................................................................. 37

Figure 13: Create Job: Basic Details ...................................................................................................................... 41Figure 14: Create Job: Job Details ......................................................................................................................... 41Figure 15: Create Job: Valid Grades ...................................................................................................................... 42Figure 16: Create Job: Evaluation Criteria .............................................................................................................. 44Figure 17: Create Job: Job Extra Information ......................................................................................................... 45Figure 18: Create Job: Job Legislative Data ........................................................................................................... 47Figure 19: Create Department ................................................................................................................................ 52Figure 20: Create Reporting Establishment ............................................................................................................ 53Figure 21: Manage Departments: Other Classifications ......... ........ ......... ......... ........ ......... ......... ......... ........ ......... ... 54Figure 22: Organization Information extensible flexfield ......................................................................................... 56Figure 23: Organization Legislative Extra Information ............................................................................................ 56Figure 24: Create Position ...................................................................................................................................... 64Figure 25: Create Position: Valid Grades ............................................................................................................... 65Figure 26: Create Position: Evaluation Criteria ....................................................................................................... 67Figure 27: Create Position: Position Extra Information ........................................................................................... 68Figure 28: Create Position: Position Legislative Data ............................................................................................. 69


5/77

1 | LOADING USING HCM DATA LOADER

Introduction

When implementing Oracle Fusion Global Human Resources for the first time or providing regular

updates, you can create work structure records using HCM Data Loader.

For general information about how to prepare data for loading using HCM Data Loader, or the HCM

Data Loader file format, see the HCM Data Loader User Guide (MOS Doc ID:1664133.1).

How to Use the Information in This Document

This document provides a separate section for each business object that it describes. Each section

covers the following topics:

Considerations and Prerequisites What to consider before attempting to load data.

LoadingDescribes the business object hierarchy. For each business object component, a table of

the attributes that are commonly supplied when creating new records is provided. These tables

have the following columns:

HCM Data Loader AttributeThe attribute name to supply when providing your data in the

business object data (.dat) file. Attribute names with a *1 suffix are foreign-object references

that support the integration key types. As source keys are recommended where possible, the

document describes how to supply source key values. User key attributes are identified for

when you do not have the source key value.

User Interface PromptThe prompt seen on the user interface. The data that you supply in

the associated attribute derives this field value, which is not necessarily the same as the value

that you supply. For example, for the Location field on an Organization page you can supply

the Oracle Fusion surrogate ID, source key, or Oracle Fusion GUID to identify a location

uniquely. The value seen on the user interface will be the location name.

If the user interface prompt is prefixed with an asterisk (*), then the attribute is mandatory

when you create a new record.

Functional DescriptionAdditional information describing the attribute and how to supply

valid values.

Errors Identifies errors that may occur when loading data for the business object. Informationabout resolving the error is provided.

Deletion SupportDescribes the extent to which the business object supports data deletion. Some

objects do not support deletion, while others may support deletion of child records only.

Translation Information on how to provide translation data for the translatable attributes in the

business object hierarchy.
http://support.oracle.com/epmos/faces/DocumentDisplay?id=1664133.1http://support.oracle.com/epmos/faces/DocumentDisplay?id=1664133.1http://support.oracle.com/epmos/faces/DocumentDisplay?id=1664133.1http://support.oracle.com/epmos/faces/DocumentDisplay?id=1664133.1


6/77

2 | LOADING WORK STRUCTURES USING HCM DATA LOADER

Example Dat Files

This document provides working dat file examples for loading and deleting data using HCM Data

Loader. To use the source key examples, change the source system owner to a lookup code you have

pre-configured in the HRC_SOURCE_SYSTEM_OWNER lookup.

For both user key and source key examples ensure any references to foreign objects refer to data that

exists in your test environment.


7/77


Location

A location is the physical address of the place where you conduct business or which is of interest to your business. Itrecords the place, address, and other details and can be associated with an organization.

Considerations and Prerequisites for Location

Locations are set enabled, that is, you can create them either in a specific set to restrict their use to a certain

business unit or in the common set to make them globally available.

Make sure that the sets have been created and associated with business units according to business needs.

If you want to associate an action reason with your location records, then action reasons must be created using the

Manage Action Reasons task before you load your location records.

Loading LocationsLocation data must be supplied in the Location.dat file for processing by HCM Data Loader.

LOCATION HIERARCHY

Component Functional Description Discriminator

Location Basic details of the location. Location

Location Other

Address

Additional addresses for the location. LocationOtherAddress

Location Extra

Information

Extensible flexfield data for the location. LocationExtraInfo

Location Legislative

Extra Information

Legislative extensible flexfield data for the location. LocationLegislative

Location Component

The location component defines the basis of the location for an organization. It records location and contact data

along with billing and shipping information.

The discriminator Locationis used to load location records using HCM Data Loader. The following Location

attributes are commonly supplied when loading a new location. Other optional attributes may be available. Generate

and review the location template f ile to identify attribute names for configured descriptive flexfield segments.

LOCATION ATTRIBUTES

HCM Data Loader

Attribute

User Interface

PromptFunctional Description

SourceSystemId /

SourceSystemOwner

n/a You must provide a unique reference for the record being created. Supply either a

source key or the user key attributes LocationCode and SetCode.

EffectiveStartDate * Effective Start Date The start date of the location or of the update to the location if you are supplying

date-effective history.

EffectiveEndDate Effective End Date If you are supplying date-effective history, the last day of the date-effective

changes. If left blank, this value is the end of time by default.


8/77


HCM Data Loader

Attribute

User Interface


SetCode * Location Set The code of the set to which this location belongs. This attribute is mandatory for

new locations.

ActionReasonCode Action Reason The code of the reason why this location is created or updated.

LocationName * Name The name for the location. Supply the location name in the language of the user

loading your new locations.

This value can be translated for other enabled languages if you supply a

LocationTranslation.dat file.

LocationCode * Code A code to uniquely reference the location within the set. This attribute is

mandatory for new locations.

Description Description Optionally supply a description for the location in the language of the user loading

your new locations.

This value can be translated for other enabled languages if you supply a

LocationTranslation.dat file.

ActiveStatus * Status Specifies whether the location is active. This attribute is validated using the

ACTIVE_INACTIVE lookup.

InventoryOrganizationId*1

Inventory Organization Optionally specify an inventory organization for the location. If you are supplying

the user key, then use the InventoryOrganizationName attribute.

This attribute also supports the integration key type values by appending the

appropriate hint to the attribute name, for example, InventoryOrganizationId

(SourceSystemId) if you are supplying the source key you specified when creating

the organization.

FLEX:PER_LOCATIONS_

DF

Context Supply only if loading Location Attributes descriptive flexfield data. The context

of the descriptive flexfield data is supplied against this attribute.

Country * Country The country for the location address.

AddressLine1 *Address Line 1 Optionally supply the first line of the location address.

AddressLine2 Address Line 2 Optionally supply the second line of the location address.

TownOrCity Town or City Optionally supply the town or city of the location address. This value may be

mandatory depending on the country specified.

PostalCode PostCode / Zip Code Optionally supply the postal code of the location address. This value may be

mandatory depending on the country specified.

Region1 Region / State Optionally supply the primary region in which the address is located. This value

may be mandatory depending on the country specified.

User key attributes that are required only if no other key type is supplied to uniquely identify the object they reference

InventoryOrganizationNa

me

Inventory Organization The name of the inventory organization for this location. Required if specifying an

inventory organization and no other key type is supplied to uniquely reference the

organization.

The value supplied will derivethe value seen in the field specified in the User Interface Prompt.

*1 The foreign object references support use of all four key types: Oracle Fusion surrogate ID, Oracle Fusion GUID, source key, and

user key.


9/77


Figure 1: Create Location

Navigation: Workforce Structures - Manage LocationsCreate Location

Location Other Address Component

The Location Other Address component holds an additional address for a location. For example, you may use a PO

Box to receive mail at a mailing address instead of the physical address of the location.

The discriminator LocationOtherAddressis used to load Location Other Address records using HCM Data Loader.

The following LocationOtherAddressattributes are commonly supplied when loading a new address for a location.

Other optional attributes may be available.

LOCATION OTHER ADDRESS ATTRIBUTES

HCM Data Loader

AttributeUser Interface Prompt Functional Description

SourceSystemId /

SourceSystemOwner


source key or the user key attributes LocationCode, LocationSetCode, and

AddressUsageType.


10/77


HCM Data Loader


EffectiveStartDate * Effective Start Date The start date of the location address.


changes. If left blank, this value is the end of t ime by default.

LocationId * Code The location for which this is the address. If you are using user keys, then supply

the LocationCode and LocationSetCode attributes.

If you supplied a source key for the location record, then supply the same

SourceSystemId value here and add the source key hint to this attribute name,

that is, LocationId (SourceSystemId)

AddressUsageType *Address Type The type of address usage for the location. In the user interface this value is

available only when editing an existing location and adding another address.

Country * Country The country for the location address.

AddressLine1 Address Line 1 The first line of the location address.

AddressLine2 Address Line 2 The second line of the location address.

TownOrCity Town or City The town or city of the location address. This value may be mandatory depending

upon the country.

PostalCode Postal Code The postal code of the location address. This value may be mandatory depending

upon the country.

Region1 Region The primary region in which the address is located. This value may be mandatory

depending upon the country.


LocationCode Code The code of the location for this address.

LocationSetCode Location Set The code of the set to which the location belongs.



user key.


11/77


Figure 2: Manage Locations: Other Addresses

Navigation: Workforce Structures - Manage Locations - Edit Location - Other Address

Location Extra Information Component

The Location Extra Information component holds the extensible flexfield information for the location.

The discriminator LocationExtraInfois used to load location extra information records using HCM Data Loader.

The following LocationExtraInfoattributes are commonly supplied when loading a new location that has extensible

flexfield data associated with it. Generate a template file for location to retrieve the attribute names used for flexfield

segments.

You cannot load location extra information records independently. You must always supply the parent location

record in the same Location.dat file.

LOCATION EXTRA INFORMATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner


source key or the user key attributes LocationCode, SetCode, SequenceNumber,

and LeiInformationCategory.

LocationId *Code Unique reference to the location this extensible flexfield data is for. If you are

using user keys, then supply the LocationCode and SetCode attributes.



that is, LocationId (SourceSystemId).

EffectiveStartDate * Effective Start Date The start date of the extensible flexfield data.


changes. If left blank, this value is the end of t ime by default.

InformationType n/a Context code for the extensible flexfield.


12/77


HCM Data Loader


FLEX:PER_LOCATIO

N_INFORMATION_E

FF

n/a The context code for the Location Information EFFdata is supplied against this

attribute.

EFF_CATEGORY_C

ODE

n/a The category code for the extensible flexfield data is supplied against this attribute.

Supply HCM_LOC.


LocationCode Code The code of the location this extensible flexfield data is for.

SetCode Location Set The set code for the location this extensible flexfield data is for.

SequenceNumber n/a The sequence number is relevant only for multirow contexts and identifies the

order of the rows. Even for multirow contexts it is optional, as the system

automatically populates it. However, if you dont support a source key when

creating new extensible flexfield data, then the SequenceNumber value becomesmandatory as it is part of the user key.

LeiInformationCategory n/a The same value as EFF_CATEGORY_CODE.



user key.

Figure 3: Create Location: Extra Information


Location Legislative Extra Information Component

The Location Legislative Extra Information component holds the legislative extensible flexfield data for the location.

The discriminator LocationLegislativeis used to load location legislative extra information records using HCM Data

Loader. The following LocationLegislativeattributes are commonly supplied when loading a new location that has

legislative extensible flexfield data associated with it. Generate a template file for location to retrieve the attribute

names used for flexfield segments.


13/77


You cannot load location extra information records independently. You must always supply the parent location

record in the same Location.dat file.

LOCATION LEGISLATIVE EXTRA INFORMATION ATTRIBUTES

HCM Data Loader

Attribute

User Interface


SourceSystemId /

SourceSystemOwner


source key or the user key attributes LocationCode, SetCode, SequenceNumber,

and LleInformationCategory.

SequenceNumber n/a The sequence number is relevant only for multirow contexts and identifies the

order of the rows. Even for multirow contexts it is optional, as the system will

automatically populate it. However, if you dont support a source key when

creating new extensible flexfield data, then the SequenceNumber becomes

mandatory as it is part of the user key.

LocationId*1

*Code Unique reference to the location this extensible flexfield data is for. If you are

using user keys, then supply the LocationCode and SetCode attributes.



that is, LocationId (SourceSystemId).

EffectiveStartDate * Effective Start Date The start date of the extensible flexfield data.


changes. If left blank, this value is the end of time by default.

LegislationCode n/a Code of the legislation to which this context applies.

LleInformationCategory n/a Extensible flexfield context code. This should have the same value as the

FLEX:PER_LOCATION_LEG_EFF attribute.

FLEX:PER_LOCATION_L

EG_EFF

n/a The context code for the Location Legislative EFFdata is supplied against this

attribute.

EFF_CATEGORY_CODE n/a The category code for the extensible flexfield data is supplied against this attribute.

Supply HCM_LOC_LEG.


LocationCode Code The code of the location this extensible flexfield data is for. This value is required if

no other key type is supplied to identify the location.

SetCode Location Set The set code for the location this extensible flexfield data is for. This value is

required if no other key type is supplied to identify the location.


*1 The foreign object references support use of all four key types; Oracle Fusion surrogate ID, Oracle Fusion GUID, source key, and

user key.


14/77


Figure 4: Create Location: Legislative Information


Location Dat File Example

Creating Locations Using Source Keys

This file creates four new locations, one of which has Location Legislative EFF data.

Location.dat

METADATA|Location|SourceSystemOwner|SourceSystemId|LocationCode|SetCode|LocationName|Description|EffectiveStartDate|EffectiveEndDate|ActiveStatus|ShipToSiteFlag|ReceivingSiteFlag|BillToSiteFlag|OfficeSiteFlag|Building|Country|PostalCode|TownOrCity|Region1

|Region2|AddressLine1MERGE|Location|VISION|LOC_HQ|HQ|COMMON|Vision Corporation HQ|HeadQuarters|1951/01/01|4712/12/31|A|Y|Y|Y|Y||US|10130|New York|New York|NY|Avenue beachheights

MERGE|Location|VISION|LOC_RD_UK|RESEARCH_DEV_UK|COMMON|Vision CorporationR&D|Research and Developmentcenter|1951/01/01|4712/12/31|A|Y|Y|Y|Y||GB||Marlow||Buckinghamshire|18 High Street

MERGE|Location|VISION|LOC_UK_100|UK_100|COMMON|Building 100|Vision CorporationBuilding 100|2000/01/01|4712/12/31|A|Y|Y|Y|Y||GB||Reading||Berkshire|Thames ValleyPark

MERGE|Location|VISION|LOC_UK_200|UK_200|COMMON|Building 200|Vision Corporation


15/77


Building 200|2000/01/01|4712/12/31|A|Y|Y|Y|Y||GB||Reading||Berkshire|Thames ValleyPark

METADATA|LocationLegislative|SourceSystemOwner|SourceSystemId|LocationId(SourceSystem

Id)|LegislationCode|SequenceNumber|EffectiveStartDate|EffectiveEndDate|LleInformationCategory|FLEX:PER_LOCATION_LEG_EFF|EFF_CATEGORY_CODE|_HEADQUARTER_ESTABLISHMENT(PER_LOCATION_LEG_EFF=HRX_US_REPORTING_INFORMATION)|_DUNS_NUMBER(PER_LOCATION_LEG_EFF=HRX_US_REPORTING_INFORMATION)|_NAICS_NUMBER(PER_LOCATION_LEG_EFF=HRX_US_REPORTING_INFORMATION)

MERGE|LocationLegislative|VISION|LOC_LEG_HQ|LOC_HQ|US|1|1951/01/01|4712/12/31|HRX_US_REPORTING_INFORMATION|HRX_US_REPORTING_INFORMATION|HCM_LOC_LEG|Y|3SLJ3|3423AB

Location Errors

You may experience errors while loading locations if the data is not provided as expected. Some of the more

commonly occurring errors are:

Error Resolution

If the ship-to site value is yes, then the ship-to location

must be the same as the location name.

If the ship-to site value is yes, ensure that the ship-to

location value has the same name as the location.

Changing the Logical Start and End Date for Location

It is not possible to change either the first effective start date, or last effective end date for an existing location.

Make sure that you create your location records with an effective start date prior to any records that will be

referencing your locations.

Deletion Support for Location

You cannot delete locations using HCM Data Loader. Instead, you can make locations inactive.

Inactivate Location Dat File Example

Making a Location Inactive Using Source Keys

This file makes one of the locations inactive as of 01-Jan-2015.

Location.dat

METADATA|Location|SourceSystemOwner|SourceSystemId|EffectiveStartDate|ActiveStatus

MERGE|Location|VISION|LOC_UK_100|2015/01/01|I

Making a Location Inactive Using User Keys

The same change can be achieved by supplying the user key to uniquely reference the location.

Location.dat

METADATA|Location|LocationCode|SetCode|EffectiveStartDate|ActiveStatus

MERGE|Location|UK_200|COMMON|2015/01/01|I


16/77


Location Translation

The location name and description can be translated. The LocationTranslation.datfile is used to provide

translation data after the location has been created.

LOCATION TRANSLATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner

n/a You must provide a unique reference for the record being translated. Supply either

the source key used when creating your data or the user key attributes

LocationCode and SetCode.

EffectiveStartDate * Effective Start Date The start date of the translated value. This value must match the

EffectiveStartDate of the record being translated.

EffectiveEndDate Effective End Date If supplying date-effective history, the last day of the date-effective changes. If left

blank, this value is the end of time by default.

LocationName *Location Name The translated value for the location name.

Description Description The translated value for the location description.

Language *not displayed The language of the supplied translated value, for example, FR or DE.


LocationCode Code The code of the location this translation is for. This value is required if you do not

supply the source key.

SetCode Location Set The set code of the location this translation is for. This value is required if you do

not supply the source key.


Location Translation Dat File Example

Creating Location Translation Using Source Keys

This file loads the French translation for a location created in the Location.dat example provided in theCreating

Locations Using Source Keys section.

LocationTranslation.dat

METADATA|LocationTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Lang

uage|LocationName|Description

MERGE|LocationTranslation|VISION|LOC_RD_UK|1951/01/01|FR|Vision Corporation Rechercheet dveloppement|Centre de recherche et de dveloppement


17/77


Grade

A grade identifies the workers rank or level of compensation. Typically customers using grades either associate asalary range (a minimum and maximum) with each grade or they use grade steps, which point to a distinct monetary

value.

For the first case, grades are created without steps. Grade rates and minimum and maximum values can be

associated with the grade.

For the second case, the grades are created with steps. Then a grade ladder is created to group the grades into a

ladder and associate the rate values with the steps.

Considerations and Prerequisites for Grade

Grades are set enabled, that is, you can create them either in a specific set to restrict their use to a certain business

unit or in the common set to make them globally available.

Make sure the sets have been created and associated with business units according to business needs.

If you want to associate an action reason with your grade records, then you must create action reasons using the

Manage Action Reasons task before you load your grade records.

Loading Grades

Grade data must be supplied in the Grade.dat file for processing by HCM Data Loader.

GRADE HIERARCHY


Grade A grade shows the reflective rank, level, or status of a worker in an assignment in anenterprise. For example, IC3, M3.

Grade

Grade Step Grade steps represent the incremental points within a grade. GradeStep

Grade Component

This Grade record defines the name and active status of a grade.

The discriminator Gradeis used to load grade records using HCM Data Loader. The following Gradeattributes are

commonly supplied when loading a new Grade. Other optional attributes may be available.

GRADE ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner


source key or the user key attributes GradeCode and SetCode.

EffectiveStartDate * Effective Start Date The start date of the grade or the update to the grade.

EffectiveEndDate Effective End Date If you are supplying date-effective history, the last day for the date-effective

changes. If left blank, the effective end date is the end of time by default.


18/77


HCM Data Loader


SetCode * Grade Set Sets are used as a grouping mechanism. The code of the set the grade belongs

to.

GradeName * Name The name of the grade. This value can be translated if you supply the

GradeTranslation.dat file.

GradeCode * Code A code to identify the grade. This value must unique within the set.

ActiveStatus * Status Indicates whether the grade is active or inactive. This value is validated using the

ACTIVE_INACTIVE lookup.

ActionReasonCode Action Reason The code of the reason for creating or updating this grade.

FLEX:PER_GRADES

_DF

Context Supply only if loading Grade Additional Detailsdescriptive flexfield data. The

context for the descriptive flexfield data is supplied against this attribute.


Figure 5: Create Grade

Navigation: Workforce Structures - Manage GradesCreate Grade

Grade Step Component

The Grade Step component defines the incremental points available within a grade.

The discriminator GradeStepis used to load Grade Step records using HCM Data Loader. The following

GradeStep attributes are commonly used when loading a new Grade. Other optional attributes may be available.

GRADE STEP ATTRIBUTES

HCM Data Loader

Attribute User Interface Prompt Functional Description

SourceSystemId /

SourceSystemOwner


source key or the user key attributes GradeCode, SetCode, and GradeStepName.

EffectiveStartDate * Effective Start Date The start date of the grade step or the update to the grade step.

EffectiveEndDate Effective End Date If supplying date-effective history, the last day for the date-effective changes. If

left blank, the effective end date is the end of time by default.

GradeId*1

n/a The grade this grade step is for. If using user keys, supply the GradeCode and


19/77


HCM Data Loader


SetCode attributes.

If you supplied a source key for the grade record, then supply the same


that is, GradeId(SourceSystemId).

GradeStepSequence * Step Number Specifies the sequence of the steps in the grade.

GradeStepName * Step Name The name of the grade step, which must be unique for this grade. The grade step

name can be translated by loading translated values in the

GradeStepTranslation.dat file.

CeilingStepFlag * Ceiling Step Set to Y if this is the ceiling step for the grade; otherwise set to N. One grade step

must be marked as the ceiling step for a grade.


GradeCode Code The code that uniquely identifies the grade within the set. Required if no other keytype is supplied to identify the grade.

SetCode Grade Set The code that uniquely identifies the set the grade belongs to. Required if no other

key type is supplied to identify the grade.



user key.

Figure 6: Create Grade: Grade Step Details

Navigation: Workforce Structures - Manage Grades - Create: Grade Steps

Grade Dat File Example

Creating Simple Grade Using Source Keys

This file creates grades without grade steps.

Grade.dat

METADATA|Grade|SourceSystemOwner|SourceSystemId|EffectiveStartDate|SetCode|GradeCode|GradeName|ActiveStatusMERGE|Grade|VISION|ADMIN|1951/01/01|COMMON|ADMIN|Administrator|AMERGE|Grade|VISION|SPEC|1951/01/01|COMMON|SPEC|Specialist|AMERGE|Grade|VISION|IC1|1951/01/01|COMMON|IC1|Individual Contributor 1|A


21/77


You must select only one step, not several steps, as

ceiling step for the grade.

Ensure that one step for each grade is defined as the

ceiling step.

You must provide a value for the attribute Ceiling Step. Ensure that at least one grade step is marked as the

ceiling step, by having a CeilingStepFlag value of Y.

Changing the Logical Start and End Date for Grade

It is not possible to change either the first effective start date, or last effective end date for an existing grade. Make

sure that you create your grade records with an effective start date prior to any records that will be referencing your

grades.

Deletion Support for Grade

You can delete a grade using HCM Data Loader if it is not referenced anywhere else like in an assignment, job, or a

grade rate.

Note: You cannot recover records that you delete using HCM Data Loader.

Do not supply DELETE instructions in the same file as MERGE instructions for the same grade. HCM Data Loader

does not know in which order to process the two instructions.

Deletion Dat File Example

Deleting Grades using Source Keys

This file successfully deletes existing grades. If grade steps exist they will also be purged.

Grade.dat

METADATA|Grade|SourceSystemOwner|SourceSystemId|EffectiveStartDateDELETE|Grade|VISION|CADET|1951/01/01DELETE|Grade|VISION|MID|1951/01/01DELETE|Grade|VISION|SUBLT|1951/01/01DELETE|Grade|VISION|LT|1951/01/01DELETE|Grade|VISION|LT_CDR|1951/01/01

Grade Translation

The Grade Name can be translated. The GradeTranslation.datfile is used to provide translation data after the

Grade has been created.

GRADE TRANSLATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner


the source key used when creating your data or the user key attributes GradeCode

and SetCode.



22/77


HCM Data Loader





GradeName * Grade Name The translated name of the grade in the language specified.



GradeCode Grade Code The code that uniquely identifies the grade within the set. Required if you do not

supply the source key to identify the grade.

SetCode Grade Set Code The code that uniquely identifies the set the grade belongs to. Required if you do

not supply the source key to identify the grade.


Grade Translation Dat File Example

Creating Grade Translation using Source Keys

This file loads the French translation for the grades created in the Grade.dat example in theCreating Simple Grade

Using Source Keys section.

GradeTranslation.dat

METADATA|GradeTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|GradeNameMERGE|GradeTranslation|VISION|ADMIN|1951/01/01|FR|AdministrateurMERGE|GradeTranslation|VISION|SPEC|1951/01/01|FR|SpcialisteMERGE|GradeTranslation|VISION|IC1|1951/01/01|FR|Contributeur individuel 1MERGE|GradeTranslation|VISION|IC2|1951/01/01|FR|Contributeur individuel 2MERGE|GradeTranslation|VISION|IC3|1951/01/01|FR|Contributeur individuel 3MERGE|GradeTranslation|VISION|IC4|1951/01/01|FR|Contributeur individuel 4MERGE|GradeTranslation|VISION|M1|1951/01/01|FR|Superviseur 1MERGE|GradeTranslation|VISION|M2|1951/01/01|FR|Superviseur 2MERGE|GradeTranslation|VISION|M3|1951/01/01|FR|Superviseur 3MERGE|GradeTranslation|VISION|D1|1951/01/01|FR|Directeur 1MERGE|GradeTranslation|VISION|D2|1951/01/01|FR|Directeur 2MERGE|GradeTranslation|VISION|D3|1951/01/01|FR|Directeur 3

Grade Step Translation

The grade step name can be translated. The GradeStepTranslation.datfile is used to provide translation data after

the grade step has been created.

GRADE STEP TRANSLATION ATTRIBUTES

HCM Data Loader


SourceSystemId / n/a You must provide a unique reference for the record being translated. Supply either


24/77


Grade Rate

A Grade Rate is the name of a rate that is used to identify the currency, frequency, and annualization factor within aspecific legislative data group, for example, Hourly Rate Blue Collar Workers or Overtime Rate Analysts. Usually,

rate values are associated with a grade rate. Rate values can be defined as either a range, by entering minimum

and maximum values, or a specific monetary value.

Considerations and Prerequisites for Grade Rate

Grade rates are created within a legislative data group, so you need to load your legislative data groups before

loading the grade rates.

If you want to associate an action reason with your grade rate records, then you must create action reasons using

the Manage Action Reasons task before you load grade rate records.

Loading Grade Rates

Grade rate data must be supplied in the GradeRate.dat file for processing by HCM Data Loader.

GRADE RATE HIERARCHY


Grade Rate A grade rate is the name of a rate that is used to identify the currency, frequency, and

annualization factor within a legislative data group.

GradeRate

Grade Rate Value The monetary value or range for a grade rate. GradeRateValue

Grade Rate ComponentThe Grade Rate holds information such as the currency, frequency, and annualization factor within a legislative data

group.

The discriminator GradeRateis used to load grade rate records using HCM Data Loader. The following GradeRate

attributes are commonly supplied when loading a new grade rate. Other optional attributes may be available.

GRADE RATE ATTRIBUTES

HCM Data Loader

Attribute

User Interface


SourceSystemId /

SourceSystemOwner


source key or the user key attributes LegislativeDataGroup and GradeRateName.

LegislativeDataGroupId *1 *Legislative Data Group The legislative data group this grade rate is for. If using user keys, then supply the

LegislativeDataGroup attribute.

If you supplied a source key when creating the legislative data group record, then

supply the same SourceSystemId value here and add the source key hint to this

attribute name, that is, LegislativeDataGroupId(SourceSystemId).

EffectiveStartDate *Efffective Start Date The start date of the grade rate or the update to the grade rate.

EffectiveEndDate Effective End Date If supplying date-effective history, the last day for the date-effective changes. If left

blank, the effective end is the end of time by default.


25/77


HCM Data Loader

Attribute

User Interface


GradeRateName * Name The name for the rate. The grade rate name is translatable. SeeGrade Rate

Translationon page24.

RateType *Rate Type The rate type, for example, Salary, Bonus, Overtime.

This attribute is validated using the GRADE_PAY_RATE_TYPE lookup.

ActiveStatus * Status The rate status. This attribute is validated using the ACTIVE_INACTIVE lookup.

RateFrequency * Frequency Frequency of the rate, for example, Annual, Monthly, Hourly, Payroll Period.

This attribute is validated using the CMP_SALARY_BASIS lookup.

AnnualizationFactor Annualization Factor The multiplier to convert the rate to an annual amount.

CurrencyCode *Currency The currency code for the rate values defined by the Grade Rate Values

component.

ActionReasonCode Action Reason The code of the reason for creating or updating this grade rate.

FLEX:PER_RATES_DF Context Only supply if loading Rate Additional Detailsdescriptive flexfield data. The

context of the descriptive flexfield data is supplied against this attribute.


LegislativeDataGroup Legislative Data Group The name of the legislative data group. Required if no other key type is supplied to

identify the legislative data group.



user key.

Figure 7: Create Grade Rate

Navigation: Workforce Structure - Manage Grade RatesCreate Grade Rate

Grade Rate Value Component

The Grade Rate Value component holds the minimum and maximum amount if a range is associated with the grade

rate and the value if a specific amount is associated with the grade rate.


26/77


The discriminator GradeRateValue is used to load grade rate value records using HCM Data Loader. The following

GradeRateValueattributes are commonly supplied when loading a new grade rate. Other optional attributes may

be available.

GRADE RATE VALUE ATTRIBUTES

HCM Data Loader

Attribute

User Interface


SourceSystemId /

SourceSystemOwner


source key or the user key attributes LegislativeDataGroup and GradeRateName.

LegislativeDataGroupId*1

*Legislative Data Group The legislative data group this grade rate is for. If using user keys, supply the


If you supplied a source key when creating the legislative data group record, then



RateId *1 * Grade Rate The grade rate this value is for. If using user keys, supply the GradeRateNameattribute.

If you supplied a source key for the grade rate, supply the same SourceSystemId

value here and add the source key hint to this attribute name, that is, RateId

(SourceSystemId).

RateObjectId*1

* Grade The grade this rate value is for. If using user keys, supply the GradeCode and

SetCode attributes.

If you supplied a source key when creating the grade record, supply the same


that is, RateObjectId(SourceSystemId).

EffectiveStartDate * Effective Start Date The start date of the grade rate value or the update to the grade rate value.



MinimumAmount Minimum The minimum amount of the range. If the minimum is provided, then the maximum

is required.

MaximumAmount Maximum The maximum amount of the range. If the maximum is provided, then the minimum

is required.

MidValueAmount Midpoint The midpoint of the range. If this value is left blank, then the system will populate

the midpoint as (minimum + maximum) / 2.

ValueAmount Value A specific value. This is not required if minimum and maximum values are

provided.


GradeRateName *Name The name for the rate this value is for.

LegislativeDataGroup *Legislative Data Group The name of the legislative data group. Required if no other key type is supplied to

identify the legislative data group.

GradeCode * Grade The code of the grade this rate value is for. Required if no other key type is

supplied to uniquely identify the grade.

SetCode * Grade Set The code for the set the grade belongs to. Required if no other key type is supplied

to uniquely identify the grade.



user key.


27/77


Figure 8: Grade Rate Values

Navigation: Workforce Structures - Manage Grade Rates - Create: Grade Rate Values - Add Row

Grade Rate Dat File Example

Creating Grade Rates Using Source Keys

This file creates grade rates with grade rate values.

The referenced grades can be created using the Grade.dat example in theCreating Grades with Grade Steps Using

Source Keys section on page16.The referenced legislative data group can be created using the

LegislativeDataGroup.dat file found in the Loading Setup Data Using HCM Data Loader white paper, available from

MOS (DOC ID: 2042956.1).

GradeRate.dat

METADATA|GradeRate|SourceSystemOwner|SourceSystemId|LegislativeDataGroupId(SourceSystemId)|EffectiveStartDate|GradeRateName|RateType|ActiveStatus|RateFrequency|AnnualizationFactor|CurrencyCode

MERGE|GradeRate|VISION|GR_CIV_SAL|LDG_VI_UK|2000/01/01|CivilianSalary|SALARY|A|ANNUAL|1|GBP

METADATA|GradeRateValue|SourceSystemOwner|SourceSystemId|LegislativeDataGroupId(SourceSystemId)|RateId(SourceSystemId)|RateObjectId(SourceSystemId)|EffectiveStartDate|Min

imumAmount|MaximumAmount|ValueAmountMERGE|GradeRateValue|VISION|GRV_ADMIN|LDG_VI_UK|GR_CIV_SAL|ADMIN|2000/01/01|||16500

MERGE|GradeRateValue|VISION|GRV_SPEC|LDG_VI_UK|GR_CIV_SAL|SPEC|2000/01/01|25472|53103|

Grade Rate Errors

You may experience errors while loading Grade Rate if the data is not provided as expected. Some of the more


Error Resolution

You must enter the value, or both the minimum and maximum. Minimum and maximum must be provided together. If you provide

the value, then you dont need to provide minimum and maximum.

The maximum value must be greater than the midpoint. Provide a maximum value that is greater than the midpoint value.

The minimum value must be less than the midpoint. Provide a minimum value that is less than the midpoint value.
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=179258890754444&parent=DOCUMENT&sourceId=2020600.1&id=2042956.1&_afrWindowMode=0&_adf.ctrl-state=ytjb4o0oj_4https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=179258890754444&parent=DOCUMENT&sourceId=2020600.1&id=2042956.1&_afrWindowMode=0&_adf.ctrl-state=ytjb4o0oj_4https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=179258890754444&parent=DOCUMENT&sourceId=2020600.1&id=2042956.1&_afrWindowMode=0&_adf.ctrl-state=ytjb4o0oj_4https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=179258890754444&parent=DOCUMENT&sourceId=2020600.1&id=2042956.1&_afrWindowMode=0&_adf.ctrl-state=ytjb4o0oj_4


28/77


Deletion Support for Grade Rate

You can delete a grade rate using HCM Data Loader if it is not referenced, for example, by a salary basis. I f you

delete a grade rate, the grade rate values are deleted along with the grade rate.

Note:You cannot recover records that you delete using HCM Data Loader.

Do not supply DELETE instructions in the same file as MERGE instructions for the same grade rate.

Deletion Dat File Example

Deleting Grade Rates Using Source Keys

This file deletes existing grades rates, referencing the existing grade rate by source key. If grade rate values exist,

these are also purged.

GradeRate.dat

METADATA|GradeRate|SourceSystemOwner|SourceSystemId|EffectiveStartDate

DELETE|GradeRate|VISION|GR_CIV_SAL|2000/01/01

Deleting Grade Rates using User Keys

This file deletes existing grades rates, referencing the existing grade rate by user key. If grade rate values exist,

these are also purged.

GradeRate.dat

METADATA|GradeRate|LegislativeDataGroup|GradeRateName|EffectiveStartDateDELETE|GradeRate|Vision UK|Civilian Salary|2000/01/01

Grade Rate Translation

The grade rate GradeRateName can be translated. The GradeRateTranslation.datfile is used to provide

translation data after the grade rate has been created.

GRADE RATE TRANSLATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner


the source key used when creating your data or the user key attributes

ExistingGradeRateName and LegislativeDataGroup.



EffectiveEndDate Effective End Date The end date of the translated value. If left blank, the translated value will exist

until the end of time.

GradeRateName *Name The translated grade rate name, in the language specified by the Language

attribute.




29/77


HCM Data Loader


ExistingGradeRateNa

me

Name The name of the grade rate this translation record is for. Required if no other key

type is supplied to uniquely identify the grade rate being translated.

LegislativeDataGroup Legislative Data Group The legislative data group name that the grade rate belongs to. Required if no

other key type is supplied to uniquely identify the grade rate being translated.


Grade Rate Translation Dat File Examples

Translating Grade Rates Using Source Keys

This file translates existing grades rates, referencing the existing grade rate by source key.

GradeRateTranslation.dat

METADATA|GradeRateTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|GradeRateNameMERGE|GradeRateTranslation|VISION|GR_CIV_SAL|2000/01/01|FR|Salaire civile

Translating Grade Rates Using User Keys

This file translates existing grades rates, referencing the existing grade rate by user key.

GradeRateTranslation.dat

METADATA|GradeRateTranslation|LegislativeDataGroup|ExistingGradeRateName|EffectiveStartDate|Language|GradeRateNameMERGE|GradeRateTranslation|Vision UK|Civilian Salary|2000/01/01|FR|Salaire civile


30/77


Grade Ladder

A grade ladder is a hierarchy of grades representing the sequence of grades and how a worker would typicallyprogress.

You can set up grade ladders consisting of grades with steps or grades without steps but not a combination.

Grade ladders of grades with steps are typically used if the workers progress according to certain rules from one

step to the next, for example, based on the length of service and each step is associated with a specific monetary

value.

Step rates are different from grade rates. Whereas grade rates can be shared across grades and ladders and can

be accessed through the grade rate UI, step rates are defined just for one grade ladder and cannot be shared

across grade ladders.

Considerations and Prerequisites for Grade LadderFor a Grade Ladders you must specify the grade set. Only then you can add grades of that grade set or of the

Common Set to the ladder.

Make sure the sets have been created and associated with the business units according to the customers business

needs.

If you want to associate an Action Reason with your Grade Ladder records these must be created prior to loading

your Grade Ladder records using the Manage Action Reasons task.

Loading Grade Ladder

Grade Ladder data must be supplied in the GradeLadder.dat file for processing by HCM Data Loader.

GRADE LADDER HIERARCHY


Grade Ladder A grade ladder is a hierarchy of grades, which is used to order grades and define rates

for the grades or the steps attached to the grade.

GradeLadder

Grades In Ladder Grades in Ladder are the grades that have been added to the grade ladder. GradesInLadder

Step Rate A step rate is a pay rate that is defined for the grade steps. StepRate

Step Rate Value Step rate value is the monetary value for a step rate. StepRateValue

Grade Ladder Component

The Grade Ladder holds the basic information about the grade ladder like the name, if it is for grades with or without

steps and the grade set.

The discriminator GradeLadderis used to load Grade Ladder records using HCM Data Loader. The following

GradeLadderattributes are commonly used when loading a new GradeLadder. Other optional attributes may be

available.


31/77


GRADE LADDER ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner


source key or the user key attribute GradeLadderName.

EffectiveStartDate * Effective Start Date The start date of the grade ladder or the update to the grade ladder.


left blank the effective end date will default until the end of time.

GradeSetCode *Grade Set The set code for the grades to be included in this ladder.

GradeLadderName *NameThe name of the grade ladder. The grade ladder name is translatable. See Grade

Ladder Translation on page33.

GradeType * Grade Type The type of ladder, Grade (GRADE) or Grade with Steps (STEP). A combination of

these two is not possible.

ActveStatus * Status The status of the grade ladder.

This attribute is validated using the ACTIVE_INACTIVE lookup.

ActionReasonCode Action Reason The code for the action reason.

FLEX:PER_GRADE_L

ADDERS_DF

Context Only supply if loading Grade Ladder Additional DetailsDFF data. The context of

the DFF data is supplied against this attribute.



user key.

Figure 9: Create Grade Ladder

Navigation: Workforce Structures - Manage Grade LaddersCreate Grade Ladder

Grades In Ladder Component

The Grades In Ladder component holds the grades included in the grade ladder, like the Grade Code and the

sequence.

The discriminator GradesInLadderis used to load Grades In Ladder records using HCM Data Loader. The following

GradesInLadderattributes are commonly used when loading a new GradeLadder. Other optional attributes may be

available.


32/77


GRADES IN LADDER ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner


source key or the user key attributes GradeCode, GradeSetCode, and

GradeLadderName.

EffectiveStartDate *Effective Start Date The start date of the grade in ladder record or the update to the grade in ladder.



GradeLadderId * Name A unique reference to the grade ladder this record is for. If using user keys supply

the GradeLadderName.

If you supplied a source key for the grade ladder, supply the same value here and

add the source key hint to the attribute name, that is,

GradeLadderId(SourceSystemId).

GradeId Grade Name/Code

ID is not displayed

A unique reference to the grade. If using user keys supply the GradeCode and

GradeSetCode attributes.

If you supplied a source key when creating the Grade record, supply the same


that is, GradeId(SourceSystemId).

GradesInLadderSequ

ence

Not displayed The sequence of the grades in the grade ladder.


GradeLadderName *Name The name of the grade ladder.

GradeCode Name The code of the grade. Required if no other key type is supplied to identify the

grade.

GradeSetCode Code The code of the set the grade belongs to. Required if no other key type is suppliedto identify the grade.



user key.


33/77


Figure 10: Create Grade Ladder: Grades

Navigation: Workforce Structures - Manage Grade Ladders - Create: Grades

Step Rate Component

The Step Rate component holds information like the currency, frequency, and annualization factor within a

legislative data group.

If you are creating a grade ladder with a GradeType of STEP and supplying step rates, you must supply a

StepRateValue record for every step of every grade included in the grade ladder.

The discriminator StepRateis used to load Step Rate records using HCM Data Loader. The following StepRate

attributes are commonly used when loading a new Grade Ladder. Other optional attributes may be available.

STEP RATE ATTRIBUTES

HCM Data Loader

Attribute

User Interface


SourceSystemId /

SourceSystemOwner


source key or the user key attributes RateName, LegislativeDataGroup, and

GradeLadderName.

EffectiveStartDate * Effective Start Date The start date of the rate record or the update to the rate.



GradeLadderId *Grade Ladder Name The grade ladder this rate is for. If using user keys supply the attributes;

GradeLadderName.

If you supplied a source key when creating the Grade Ladder, supply the same


that is, GradeLadderId(SourceSystemId).

RateName *Grade Step Rate Name The name of the rate in the grade ladder. The rate name is translatable, see Step

Rate Translation on page34.

LegislativeDataGroupId*1

Legislative Data Group The legislative data group this grade rate is for. If using user keys supply the


34/77


HCM Data Loader

Attribute

User Interface



If you supplied a source key when creating the Legislative Data Group record,



RateType Rate Type The rate type, for example, Salary, Bonus, Overtime.

This attribute is validated using the GRADE_PAY_RATE_TYPE lookup.

RateFrequency Frequency Frequency of the rate, for example, Annual, Monthly, Hourly, Payroll Period.

This attribute is validated using the CMP_SALARY_BASIS lookup.

AnnualizationFactor Annualization Factor The multiplier to convert the rate to an annual amount.

CurrencyCode Currency The currency code for the rate values defined by the Grade Rate Values

component.

ActiveStatus Not displayed The rate status. This attribute is validated using the ACTIVE_INACTIVE lookup.

This is defaulted to ACTIVE.


LegislativeDataGroup Legislative Data Group The name of the legislative data group. Required if no other key type is supplied

to identify the legislative data group.

GradeLadderName Name The name of the grade ladder. Required if no other key type is supplied to identify

the grade ladder.



user key.

Figure 11: Create Grade Ladder: Grade Step Rates

Navigation: Workforce Structures - Manage Grade Ladders - Create: Rate Values

Step Rate Value Component

The Step Rate Value component holds the amount for each step as monetary value.


35/77


The discriminator StepRateValueis used to load Step Rate value records using HCM Data Loader. The following

StepRateValueattributes are commonly used when loading a new Grade Ladder. Other optional attributes may be

available.

STEP RATE VALUE ATTRIBUTES

HCM Data Loader

Attribute

User Interface


SourceSystemId /

SourceSystemOwner


source key or the user key attributes RateName, LegislativeDataGroup,

GradeLadderName, GradeCode, GradeSetCode, and GradeStepName.

RateId * Grade Step Rate Name The Step Rate this value is for. If using user keys supply the attributes RateName,

LegislativeDataGroup, GradeLadderName.

If you supplied a source key when creating the Step Rate record, supply the same


that is, RateId(SourceSystemId)

RateObjectId * not displayed The grade step the rate value is for. If using user keys supply the attributes

GradeCode, GradeSetCode, GradeStepName.If you supplied a source key when

creating the referenced Grade Step, supply the same SourceSystemId value here

and add the source key hint to this attribute name, that is,

RateObjectId(SourceSystemId)

StepRateValueAmount Value The value for each step for this grade step rate.

LegislationCode not displayed Code of the legislation.

User key attributes that are only required if no other key type is supplied to uniquely identify the object they reference.

RateName Grade Step Rates: Name The name of the rate this value is for. Required if no other key type is supplied to

identify the rate.

LegislativeDataGroup Legislative Data Group The legislative data group name. Required if no other key type is supplied to

identify the rate.

GradeLadderName Grade Ladder Name The name of the grade ladder this rate value is for. Required if no other key type is

supplied to identify the grade ladder.

GradeCode Grade Code The code of the grade this rate value is for. Required if no other key type is

supplied to identify the grade.

GradeSetCode Grade Set The code of the set for the grade this rate value is for. Required if no other key

type is supplied to identify the grade.

GradeStepName Grade Step Name The name of the grade step this rate is for. Required if no other key type is

supplied to identify the grade step.



user key.


37/77








MERGE|StepRateValue|VISION|SRV_LT1|2015/01/01|STP_RT_OFF|LT1|GB|39236





MERGE|StepRateValue|VISION|SRV_LT_CDR1|2015/01/01|STP_RT_OFF|LT_CDR1|GB|49424





Deletion Support for Grade Ladder

You can delete grade ladders using HCM Data Loader if it is not referenced by another object, for example an

assignment. For grade ladders with steps, the step rates and the values are deleted along with the grade ladder.

Note: You cannot recover records that you delete using HCM Data Loader.

Do not supply DELETE instructions in the same file as MERGE instructions for the same grade ladder. HCM Data

Loader does not know in which order to process the two instructions.

Deleting a grade ladder does not delete the associated grades.

Deletion Dat File ExampleDeleting Grade Ladder Using Source Keys

This file deletes existing grades ladders, referencing the existing grade ladder by source key.

GradeLadder.dat

METADATA|GradeLadder|SourceSystemOwner|SourceSystemId|EffectiveStartDate

DELETE|GradeLadder|VISION|GRD_LDR_OFF|1951/01/01

Grade Ladder Translation

The Grade Ladder GradeLadderName can be translated. The GradeLadderTranslation.datfile is used to provide

translation data after the Grade Ladder has been created.

GRADE LADDER TRANSLATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner

n/a You must provide a unique reference for the record being translated. Either supply

the source key used when creating your data, or alternatively supply the user key

attributes; ExistingGradeLadderName.


38/77


HCM Data Loader


EffectiveStartDate *Effective Start Date The start date of the translated value, this should match the EffectiveStartDate of

the record being translated.

EffectiveEndDate Effective End Date The end date of the translated value. If left blank the translated value will exist until

the end of time.

GradeLadderName * Name The translated grade ladder name in the language specified by the Language

attribute.

Language *not displaye

Documents

Loading Work Structures Using HCM Data Loader