loading work structures using hcm data loaderloading work structures using hcm data loader oracle...

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

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 17

Grade 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 26

Considerations and Prerequisites for Grade Ladder 26

Loading Grade Ladder 26

Grade Ladder Errors 32

Deletion Support for Grade Ladder 33

Grade Ladder Translation 33


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 60

Considerations 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 ......................................................................................................................................... 5 Figure 2: Manage Locations: Other Addresses ......................................................................................................... 7 Figure 3: Create Location: Extra Information ............................................................................................................ 8 Figure 4: Create Location: Legislative Information .................................................................................................. 10 Figure 5: Create Grade ........................................................................................................................................... 14 Figure 6: Create Grade: Grade Step Details ........................................................................................................... 15 Figure 7: Create Grade Rate .................................................................................................................................. 21 Figure 8: Grade Rate Values .................................................................................................................................. 23


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

1 | LOADING <BUSINESS OBJECT> 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.

Loading Describes 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 Attribute The 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 Prompt The 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 Description Additional information describing the attribute and how to supply

valid values.

Errors Identifies errors that may occur when loading data for the business object. Information

about resolving the error is provided.

Deletion Support Describes 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.1

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.


Location A location is the physical address of the place where you conduct business or which is of interest to your business. It

records 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 Locations

Location 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 Location is 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 file to identify attribute names for configured descriptive flexfield segments.

LOCATION ATTRIBUTES

HCM Data Loader

Attribute

User Interface

Prompt Functional 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.


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 derive the 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.


Figure 1: Create Location

Navigation: Workforce Structures - Manage Locations – Create 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 LocationOtherAddress is used to load Location Other Address records using HCM Data Loader.

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

Other optional attributes may be available.

LOCATION OTHER ADDRESS ATTRIBUTES

HCM Data Loader

Attribute User Interface Prompt Functional Description

SourceSystemId /

SourceSystemOwner


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

AddressUsageType.


HCM Data Loader


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



LocationId*1

* 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.


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 LocationExtraInfo is used to load location extra information records using HCM Data Loader.

The following LocationExtraInfo attributes 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 *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.



InformationType n/a Context code for the extensible flexfield.


HCM Data Loader


FLEX:PER_LOCATIO

N_INFORMATION_E

FF

n/a The context code for the Location Information EFF data 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 don’t support a source key when

creating new extensible flexfield data, then the SequenceNumber value becomes

mandatory 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 LocationLegislative is used to load location legislative extra information records using HCM Data

Loader. The following LocationLegislative attributes 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.


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 don’t 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.



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 EFF data 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.


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|Receiving

SiteFlag|BillToSiteFlag|OfficeSiteFlag|Building|Country|PostalCode|TownOrCity|Region1

|Region2|AddressLine1

MERGE|Location|VISION|LOC_HQ|HQ|COMMON|Vision Corporation HQ|Head

Quarters|1951/01/01|4712/12/31|A|Y|Y|Y|Y||US|10130|New York|New York|NY|Avenue beach

heights

MERGE|Location|VISION|LOC_RD_UK|RESEARCH_DEV_UK|COMMON|Vision Corporation

R&D|Research and Development

center|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 Corporation

Building 100|2000/01/01|4712/12/31|A|Y|Y|Y|Y||GB||Reading||Berkshire|Thames Valley

Park

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


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

Park

METADATA|LocationLegislative|SourceSystemOwner|SourceSystemId|LocationId(SourceSystem

Id)|LegislationCode|SequenceNumber|EffectiveStartDate|EffectiveEndDate|LleInformation

Category|FLEX:PER_LOCATION_LEG_EFF|EFF_CATEGORY_CODE|_HEADQUARTER_ESTABLISHMENT(PER_L

OCATION_LEG_EFF=HRX_US_REPORTING_INFORMATION)|_DUNS_NUMBER(PER_LOCATION_LEG_EFF=HRX_U

S_REPORTING_INFORMATION)|_NAICS_NUMBER(PER_LOCATION_LEG_EFF=HRX_US_REPORTING_INFORMAT

ION)

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


Location Translation

The location name and description can be translated. The LocationTranslation.dat file 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 the Creating

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 Recherche

et développement|Centre de recherche et de développement


Grade A grade identifies the worker’s rank or level of compensation. Typically customers using grades either associate a

salary 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 an

enterprise. 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 Grade is used to load grade records using HCM Data Loader. The following Grade attributes 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.


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


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 Details descriptive flexfield data. The

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


Figure 5: Create Grade

Navigation: Workforce Structures - Manage Grades – Create Grade

Grade Step Component

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

The discriminator GradeStep is 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


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


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 key

type 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|ActiveStatus

MERGE|Grade|VISION|ADMIN|1951/01/01|COMMON|ADMIN|Administrator|A

MERGE|Grade|VISION|SPEC|1951/01/01|COMMON|SPEC|Specialist|A

MERGE|Grade|VISION|IC1|1951/01/01|COMMON|IC1|Individual Contributor 1|A


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|EffectiveStartDate

DELETE|Grade|VISION|CADET|1951/01/01

DELETE|Grade|VISION|MID|1951/01/01

DELETE|Grade|VISION|SUBLT|1951/01/01

DELETE|Grade|VISION|LT|1951/01/01

DELETE|Grade|VISION|LT_CDR|1951/01/01

Grade Translation

The Grade Name can be translated. The GradeTranslation.dat file 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.



HCM Data Loader


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

GradeCode, SetCode, and ExistingGradeStepName.





GradeStepName * Step Name The translated name of the grade step 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 step.

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 step.

ExistingGradeStepNa

me

Step Name The name of the grade step supplied when creating it. Required if you do not

supply the source key to identify the grade step.


Grade Step Translation Dat File Example

Creating Grade Step Translation Using Source Keys

This file loads the French translation for the grades steps created in the Grade.dat example in Creating Grades with

Grade Steps Using Source Keys section.

GradeStepTranslation.dat

METADATA|GradeStepTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Lan

guage|GradeStepName

MERGE|GradeStepTranslation|VISION|LT_CDR1|1951/01/01|FR|Niveau 1





Creating Grade Step Translation Using User Keys

This file loads the French translation for the grades steps created in the Grade.dat example in Creating Grades with

Grade Steps Using Source Keys section.

GradeStepTranslation.dat

METADATA|GradeStepTranslation|GradeCode|SetCode|ExistingGradeStepName|EffectiveStartD

ate|Language|GradeStepName

MERGE|GradeStepTranslation|LT|COMMON|Level 1|1951/01/01|FR|Niveau 1






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

specific 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 Component

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

group.

The discriminator GradeRate is 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.


HCM Data Loader

Attribute

User Interface


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

Translation on page 24.

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 Details descriptive 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 Rates – Create 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.


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

GradeRateValue attributes 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.


* 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 GradeRateName

attribute.

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.


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 the Creating Grades with Grade Steps Using

Source Keys section on page 16. 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(SourceSyst

emId)|EffectiveStartDate|GradeRateName|RateType|ActiveStatus|RateFrequency|Annualizat

ionFactor|CurrencyCode

MERGE|GradeRate|VISION|GR_CIV_SAL|LDG_VI_UK|2000/01/01|Civilian

Salary|SALARY|A|ANNUAL|1|GBP

METADATA|GradeRateValue|SourceSystemOwner|SourceSystemId|LegislativeDataGroupId(Sourc

eSystemId)|RateId(SourceSystemId)|RateObjectId(SourceSystemId)|EffectiveStartDate|Min

imumAmount|MaximumAmount|ValueAmount

MERGE|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 don’t 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_4


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. If you

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


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


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|EffectiveStartDate

DELETE|GradeRate|Vision UK|Civilian Salary|2000/01/01

Grade Rate Translation

The grade rate GradeRateName can be translated. The GradeRateTranslation.dat file 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.




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|Lan

guage|GradeRateName

MERGE|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|EffectiveSta

rtDate|Language|GradeRateName

MERGE|GradeRateTranslation|Vision UK|Civilian Salary|2000/01/01|FR|Salaire civile


Grade Ladder A grade ladder is a hierarchy of grades representing the sequence of grades and how a worker would typically

progress.

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 Ladder

For 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 customer’s 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 GradeLadder is used to load Grade Ladder records using HCM Data Loader. The following

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

available.


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 * Name The name of the grade ladder. The grade ladder name is translatable. See Grade

Ladder Translation on page 33.

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 Details DFF data. The context of

the DFF data is supplied against this attribute.



user key.

Figure 9: Create Grade Ladder

Navigation: Workforce Structures - Manage Grade Ladders – Create 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 GradesInLadder is used to load Grades In Ladder records using HCM Data Loader. The following

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

available.


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 *1

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 supplied

to identify the grade.



user key.


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 StepRate is 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*1

* 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 page 34.


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


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.


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

StepRateValue attributes 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 *1

* 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 *1

* 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.








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.


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.


Deleting 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.dat file 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.


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 displayed The language of the supplied translated value, for example, FR, DE.


ExistingGradeLadder

Name

Name The name of the grade ladder this translation is for. Required if you do not supply

the source key to identify the grade ladder.


Grade Ladder Translation Dat File Examples

Translating Grade Ladder Using Source Keys

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

GradeLadderTranslation.dat

METADATA|GradeLadderTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|L

anguage|GradeLadderName

MERGE|GradeLadderTranslation|VISION|GRD_LDR_OFF|1951/01/01|FR|Officier

Step Rate Translation

The Step Rate RateName can be translated. The StepRateTranslation.dat file is used to provide translation data

after the Step Rate has been created.

STEP RATE TRANSLATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner



attributes; ExistingRateName, LegislativeDataGroup




the end of time.

RateName * Name The translated rate name in the language specified by the Language attribute.



ExistingRateName Name The name of the step rate this translation is for. Required if you do not supply the


HCM Data Loader


source key to identify the step rate.

LegislativeDataGroup Legislative Data Group The name of the legislative data group the step rate belongs to. Required if you do

not supply the source key to identify the step rate.



Job Family Job Family enables you to group jobs, facilitating easy reporting across similar jobs. For example, you can group the

Trust Analyst and Operations Analyst jobs into a job family named Analyst.

Considerations and Prerequisites for Job Family

If you want to associate an Action Reason with your Job Family records, these must be created prior to loading your

Job Family records using the Manage Action Reasons task.

Loading Job Family

Job Family data must be supplied in the JobFamily.dat file for processing by HCM Data Loader.

JOB FAMILY HIERARCHY


Job Family Job families enable you to group jobs, facilitating easy reporting across similar jobs. For

example, you can group the Trust Analyst and Operations Analyst jobs into a job family

name Analyst.

JobFamily

JobFamily Component

The discriminator JobFamily is used to load job family records using HCM Data Loader. The following JobFamily

attributes must be supplied when loading a new job family. Other optional attributes may be available, generate and

review the template file for this object to identify all available attributes.

JOB FAMILY ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner

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

source key or the user key attribute JobFamilyName.

EffectiveStartDate * Effective Start Date The start date of the job family, or the update to the job family if supplying date-

effective history.

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


JobFamilyName * Name The name of the job family, this must be unique for the enterprise. Supply the

name in the language of the user that will be loading your new job families.

This can be translated for your other enabled languages by supplying the

JobFamilyTranslation.dat file.

FLEX:PER_JOB_FAM

ILY_DFF

Context Value Only supply if loading Job Family Attributes DFF data. The context for the DFF

data is supplied against this attribute.

ActionReasonCode Action Reason The user defined code for the Action Reason.

ActiveStatus * Status Indicates if the job family is active or inactive. It is validated using the



Job Family Translation

The job family name can be translated. The JobFamilyTranslation.dat file is used to provide translation data after

the job family has been created.

JOB FAMILY TRANSLATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner



attributes; BaseJobFamilyName

EffectiveStartDate * Effective Start Date The start date of the job family this translation is for.



JobFamilyName * Name The translated value for the job family name.

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


BaseJobFamilyName Name The name of the job family that you want to translate. Required if you do not


Job Family Translation Dat File Examples

Translating Job Families Using Source Keys

This file translates existing job families, referencing the existing job family by source key.

JobFamilyTranslation.dat

METADATA|JobFamilyTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Lan

guage|JobFamilyName

MERGE|JobFamilyTranslation|VISION|ANALYST|2000/01/01|FR|Analyste

MERGE|JobFamilyTranslation|VISION|TECHNICIAN|2000/01/01|FR|Technicien

Translating Job Families Using User Keys

This file translates existing job families, referencing the existing job family by user key.

JobFamilyTranslation.dat

METADATA|JobFamilyTranslation|BaseJobFamilyName|EffectiveStartDate|Language|JobFamily

Name

MERGE|JobFamilyTranslation|Consultant|2000/01/01|FR|Consultant

MERGE|JobFamilyTranslation|Management|2000/01/01|FR|Manager


Job A job represents one or more roles that may be performed by an individual within an organization.

Considerations and Prerequisites for Job

Jobs are set enabled, that is, they can be created within a specific set to restrict their use to a certain business unit

or they can be created in Common Set to make them globally available.


needs.

If you want to associate job families with your jobs, then you need to load the job families before you load the jobs.

If you want to associate valid grades with your jobs, then you need to load the grades before you load the jobs. Valid

grades can be used to default or enforce the grade for an assignment.

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

records using the Manage Action Reasons task.

To use Benchmark Jobs, you first load the Benchmark Jobs with the Benchmark Job Flag set to Yes. Then you load

the rest of the Jobs. For those Jobs that should reference a Benchmark Job, use the Benchmark Job ID or Code to

populate the referenced Benchmark Job.

Loading Job

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

JOB HIERARCHY


Job One or more roles that may be performed by an individual within an organization. Job

Job Valid Grade A grade that is valid for this job. JobGrade

Job Evaluation Job Evaluation is used to capture job evaluation criteria, for example, to record the

required points for know-how, accountability and problem solving, if the hay evaluation

system is used.

JobEvaluation

Job Extra Information The extensible flexfield data for the Job. JobExtraInfo

Job Legislative Extra

Information

The legislative extensible flexfield data for the Job. JobLegislative

Job Component

The Job component holds the base definition of a job, including benchmark job, progression job, and medical

checkup information.

The discriminator Job is used to load Job records using HCM Data Loader. The following Job attributes are

commonly used for new Jobs. Other optional attributes may be available.


JOB ATTRIBUTES

HCM Data Loader

Attribute

User Interface


SourceSystemId /

SourceSystemOwner


source key or the user key attributes JobCode and SetCode.

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

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

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

SetCode * Job Set Sets are used as a grouping mechanism. The code of the set the job belongs to


Name * Name The name of the job. Supply the value in the language of the user that will be

loading your new jobs.


JobTranslation.dat file.

JobCode * Code A code to identify the job, this must unique within the Set.

ActiveStatus * Status Indicates if the job is active or inactive. It is validated using the ACTIVE_INACTIVE

lookup.

FullPartTime Full Time or Part Time Specify if the job is full or part-time. This attribute is validated using the

PART_FULL_TIME lookup.

RegularTemporary Regular or Temporary Specify if the job is regular or temporary. This attribute is validated using the

REGULAR_TEMPORARY lookup.

JobFamilyId*1

Job Family Optionally specify a job family for the job. If supplying the user key use the

JobFamilyName attribute.


appropriate hint to the attribute name.

JobFunctionCode Job Function The code for the job function. This attribute is validated using the

JOB_FUNCTION_CODE lookup.

ApprovalAuthority Level Integer number to identify levels across jobs which are used for approvals if the job

list builder is used.

ManagerLevel Management Level The management level of the job. This attribute is validated using the

MANAGER_LEVEL lookup.

MedicalCheckupRequired Medical Checkup

Required

Indicates if the job requires medical checkup.

BenchmarkJobFlag Benchmark Indicates if this job is a benchmark job.

BenchmarkJobId *1

Benchmark Job Identifier of the benchmark job.

ProgressionJobId *1

Progression Job Next possible job during promotion.

FLEX:PER_JOBS_DFF Context Value Only supply if loading Job Attributes DFF data. The context for the DFF data is

supplied against this attribute.


JobFamilyName Job Family The name of the job family this job belongs to. Required if you want your job to be

part of a job family and no other key type is supplied to uniquely reference the job

family.

BenchmarkJobCode Benchmark Job Code of the job that is used as an example for other jobs. Required if a benchmark


HCM Data Loader

Attribute

User Interface


job is to be specified and no other key type has been supplied to reference it.

ProgressionJobCode Progression Job Code Code of the progression job. Required if a progression job is to be specified and

no other key type has been supplied to reference it.



user key.

Figure 13: Create Job: Basic Details

Navigation: Work Structures - Manage Jobs - Create

Figure 14: Create Job: Job Details

Navigation: Work Structures - Manage Jobs - Create: Details

Job Valid Grade Component

The Job Valid Grade component defines the valid grades for a job.

The discriminator JobGrade is used to load Job Valid Grade records using HCM Data Loader. Valid grades can be

supplied when creating a new job, or maintained independently for existing jobs. The following JobGrade attributes

are commonly used when creating valid grades.


JOB VALID GRADE ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner


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

JobId*1

* Code The unique reference to job this valid grade is for. If using user keys supply the

JobCode and SetCode attributes.

If you supplied a source key for the Job record, supply the same SourceSystemId

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

JobId(SourceSystemId)

GradeId*1

* Grade The unique reference to the grade. The grade must belong to the same set as the

job. If supplying the user key value use the GradeCode, SetCode attributes.


appropriate hint to the attribute name, for example, GradeId(SourceSystemId).


JobCode Code The code of the job this grade is for. Required if no other key type is supplied to

identify the job.

SetCode Job Set The code of the set the job belongs to. Required if no other key type is supplied to

identify the job or grade.

GradeCode Grade The code of the grade. The grade must belong to the same set as the Job.

Required if no other key type is supplied to identify the grade.



user key.

Figure 15: Create Job: Valid Grades


Job Evaluation Component

The Job Evaluation component captures the evaluation criteria for a job.

The discriminator JobEvaluation is used to load Job Evaluation records using HCM Data Loader. Job evaluation

records can be supplied when creating a new job, or maintained independently for existing jobs. The following

JobEvaluation attributes are commonly used when creating job evaluation criteria. Other attributes may exist.

Generate a template file for Job to retrieve the attribute names used for flexfield segments.


JOB EVALUATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner


source key or the user key attributes SetCode, JobCode, EvaluationSystem, and

DateEvaluated.

JobId*1

* Name / Code The unique reference to job this evaluation is for. If using user keys supply the

JobCode and SetCode attributes.


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


EvaluationSystem * Evaluation System The evaluation system used for the job, for example Hay System. This attribute is

validated using the EVAL_SYSTEM lookup.

DateEvaluated * Evaluation Date Date of the evaluation.

MeasuredIn Measured In The measurement unit for the evaluation, for example points. This attribute is

validated using the EVAL_SYSTEM_MEAS lookup.

Mandatory if using the Hay System.

Knowhow Knowhow Know how is a seeded criterion for the hay evaluation system. Mandatory if using

the Hay System.

Accountability Accountability Accountability is a seeded criterion for the hay evaluation system. Mandatory if

using the Hay System.

ProblemSolving Problem Solving Problem Solving is a seeded criterion for the hay evaluation system. Mandatory if


FLEX:PER_EVALUAT

ION_CRITERIA_DFF

Context Only supply if loading Evaluation Criteria Attributes DFF data. The context for

the DFF data is supplied against this attribute.


JobCode Code The code of the job this job evaluation is for. Required if no other key type is

supplied to identify the job.


identify the job.



user key.


Figure 16: Create Job: Evaluation Criteria

Navigation: Work Structures - Manage Jobs - Create: Evaluation Criteria

Job Extra Information Component

The Job Extra Information component holds extensible flexfield data for the Job.

The discriminator JobExtraInfo is used to load Job Extra Information records using HCM Data Loader. The

following JobExtraInfo attributes must be supplied when loading a new job that has extensible flexfield data

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

You cannot load Job Extra Information records independently, they must always be supplied with the parent Job

record, in the same Job.dat file.

JOB EXTRA INFORMATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner


source key or the user key attributes SetCode, JobCode, JeiInformationCategory,

and SequenceNumber

JobId*1

* Name / Code The unique reference to job this extensible flexfield data is for. If using user keys

supply the JobCode and SetCode attributes.




EffectiveStartDate * Effective Start Date The start date of the job extra information, or the update to the job extra

information.



InformationType n/a Context Code for the extensible flexfield.

FLEX:PER_JOBS_EI

T_EFF

n/a The context code for the Job EIT Information extensible flexfield data is supplied

against this attribute.


HCM Data Loader


EFF_CATEGORY_C

ODE

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

Supply ‘JOB_EIT’.


JobCode Code The code of the job this extensible flexfield data is for. Required if no other key

type is supplied to identify the job.


identify the job.

SequenceNumber n/a The sequence number is only relevant for multi-row contexts and identifies the

order of the rows. Even for multi-row contexts it is optional as the system would


creating new extensible flexfield data the SequenceNumber becomes mandatory

as it is part of the user key.



user key.

Figure 17: Create Job: Job Extra Information


Job Legislative Extra Information Component

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

The discriminator JobLegislative is used to load Job Legislative Extra Information records using HCM Data Loader.

The following JobLegislative attributes must be supplied when loading a new job that has legislative extensible

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

segments.

You cannot load Job Legislative Extra Information records independently, they must always be supplied with the

parent Job record.


JOB LEGISLATIVE EXTRA INFORMATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner


source key or the user key attributes SetCode, JobCode, InformationCategory,

and SequenceNumber.

JobId*1

* Name / Code The unique reference to job this extensible flexfield data is for. If using user keys

supply the JobCode and SetCode attributes.




EffectiveStartDate * Effective Start Date The start date of the job legislative information, or the update to the job legislative

information.



InformationCategory n/a Extensible flexfield context code.

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

FLEX:PER_JOBS_LE

G_EFF

n/a The context code for the Job Legislative Information extensible flexfield data is


EFF_CATEGORY_C

ODE


Supply ‘JOB_LEG’.


JobCode Job Code The code of the job this extensible flexfield data is for. Required if no other key

type is supplied to identify the job.

SetCode Job Set Code The code of the set the job belongs to. Required if no other key type is supplied to

identify the job.








user key.


Figure 18: Create Job: Job Legislative Data


Job Dat File Example

Creating Jobs with Valid Grades Using Source Keys

This file creates jobs with valid grades and legislative data.

METADATA|Job|SourceSystemOwner|SourceSystemId|EffectiveStartDate|SetCode|JobCode|Name

|ActiveStatus|FullPartTime|RegularTemporary|JobFamilyId(SourceSystemId)|JobFunctionCo

de|ManagerLevel

MERGE|Job|VISION|SALES_CONS|2000/01/01|COMMON|SALES_CONS|Sales

Consultant|A|FULL_TIME|R|CONSULT||9

MERGE|Job|VISION|SALES_MGR|2000/01/01|COMMON|SALES_MGR|Sales

Manager|A|FULL_TIME|R|MANAGEMENT|MANAG|6

MERGE|Job|VISION|SALES_DIR|2000/01/01|COMMON|SALES_DIR|Sales

Director|A|FULL_TIME|R|MANAGEMENT|MANAG|1

MERGE|Job|VISION|MRKT_CONS|2000/01/01|COMMON|MRKT_CONS|Marketing

Consultant|A|FULL_TIME|R|CONSULT||9

MERGE|Job|VISION|MRKT_MGR|2000/01/01|COMMON|MRKT_MGR|Marketing

Manager|A|FULL_TIME|R|MANAGEMENT|MANAG|6

MERGE|Job|VISION|MRKT_DIR|2000/01/01|COMMON|MRKT_DIR|Marketing

Director|A|FULL_TIME|R|MANAGEMENT|MANAG|1

METADATA|JobGrade|SourceSystemOwner|SourceSystemId|EffectiveStartDate|JobId(SourceSys

temId)|GradeId(SourceSystemId)

MERGE|JobGrade|VISION|SALES_CONS_IC1|2000/01/01|SALES_CONS|IC1




MERGE|JobGrade|VISION|SALES_MGR_M1|2000/01/01|SALES_MGR|M1



MERGE|JobGrade|VISION|SALES_DIR_M1|2000/01/01|SALES_DIR|D1



MERGE|JobGrade|VISION|MRKT_CONS_IC1|2000/01/01|MRKT_CONS|IC1





Organization Organizations can be any organizing unit in the internal or external structure of your Enterprise.

Organization structures provide the framework for performing legal reporting, financial control, and management

reporting.

An organization can also represent a physical structure, such as a warehouse.

For HCM, an Organization is a logical group of people working together. We typically only use internal organizations

such as Legal Entities, Business Units, Divisions, and Departments.

Considerations and Prerequisites for Organization

Departments are set enabled, that is, they can be created within a specific set to restrict their use to a certain

business unit or they can be created in Common Set to make them globally available.


needs.

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

your Organization records using the Manage Action Reasons task.

The same organization can have multiple classifications. This means the same organization can be reused to have

multiple functions, for example a division can be also a department. So you can load multiple classifications for the

same organization unit.

Only departments are set enabled. The other organizations are not set enabled.

If you want to associate locations with your organizations, then you need to load the locations before you load the

organizations.

If you want to associate a reporting manager with your organization, then you need to load the organizations first

without the manager, then load the person and assignments and afterwards update your organizations with the

reporting manager.

As a person is hired into a legal employer and business unit and usually a department, you cannot load the persons

first before you load your organizations.

Loading Organization

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

ORGANIZATION HIERARCHY


Organization An organization is a logical group of people working together. It has a classification that

determines its type. For example department, legal employer.

Organization

Organization

Classification

The classification determines the type of organization. For example department, legal

employer.

OrgUnitClassification

Organization Extra

Information

The extensible flexfield for Organization. OrgInformation


Organization Component

The Organization component defines the name, classification, location and legal reporting unit for the organization.

The discriminator Organization is used to load Organization records using HCM Data Loader. The following

Organization attributes are commonly used when loading a new Organization. Other attributes may exist.

Generate a template file for Job to retrieve the attribute names used for flexfield segments.

ORGANIZATION ATTRIBUTES

HCM Data

Loader Attribute User Interface Prompt Functional 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 Name and ClassificationName.

EffectiveStartDate * Effective Start Date The start date of the organization, or update to the organization if supplying date-

effective history.



Name * Name The name of the organization. Supply the name in the language of the user that

will be creating your new organization.


OrganizationTranslation.dat file.

InternalAddressLine Internal Address Line Internal address of the organization.

ClassificationCode n/a The code for the organization’s classification. Alternatively the

ClassificationName can be supplied.

Valid values for HCM classifications are:

ENTERPRISE Enterprise

DEPARTMENT Department

HCM_BARGAINING_ASSOCIATION Bargaining Association

HCM_DIVISION Division

HCM_DISABILITY_ORGANIZATION Disability Organization

HCM_REPORTING_ESTABLISHMENT Reporting Establishment

HCM_LEMP Legal Employer

HCM_LRU Legal Reporting Unit

HCM_PSU Payroll Statutory Unit


LocationId*1

Location The location of the organization. If supplying the user key value, use the

LocationSetCode, LocationCode attributes.

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


that is, LocationId(SourceSystemId).

EstablishmentId*1

n/a Only supply for organizations that have a Legal Reporting Unit classification. If

supplying the user key, use the EstablishmentName attribute.

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


that is, EstablishmentId(SourceSystemId).

LegalEntityIdentfier n/a Should only be supplied for organizations that have a Legal Employer

classification.


HCM Data

Loader Attribute User Interface Prompt Functional Description

FLEX:

PER_ORGANIZATIO

N_UNIT_DFF

Context Value Only supply if loading Organization Attributes DFF data. The context for the

DFF data is supplied against this attribute.


ClassificationName In the UI we don’t use the

term ‘Organization’ but have

specific UIs for each of

them, for example Manage

Departments, Manage

Divisions, and so on. For

these examples

‘Department’ and ‘Division’

are the classification names.

The name of the organization’s classification. See the ClassificationCode

attribute for the list of valid HCM classification names.

LocationCode Location The code of the location for the organization. Required if you want to supply a

location for the organization and no other key type is supplied to identify the

location.

LocationSetCode Location Set Code The code of the set the location belong to. Required if you want to supply a

location for the organization and no other key type is supplied to identify the

location.

EstablishmentName Legal Reporting Unit User key attribute for EstablishmentId. Only supply for organizations that have a

Legal Reporting Unit classification where no other key type has been supplied to

identify the establishment.



user key.

Figure 19: Create Department

Navigation: Workforce Structures - Manage Departments - Create

Each Organization has its own dedicated UI, Manage Departments is one example


Figure 20: Create Reporting Establishment

Navigation: Workforce Structures - Manage Reporting Establishments - Create

Organization Classification Component

The Organization Classification component defines the type of organization, for example department, legal

employer. You must supply at least one classification when creating a new organization.

The discriminator OrgUnitClassification is used to load Organization Classification records using HCM Data

Loader. The following OrgUnitClassification attributes are commonly used when loading a new Organization.

Other optional attributes may be available, generate and review the template file for this object to identify all

available attributes.

ORGANIZATION CLASSIFICATION ATTRIBUTES

HCM Data Loader


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 ClassificationName, and

OrganizationName.

EffectiveStartDate * Effective Start Date The start date of the organization classification. This should match the

Organization’s effective start date.

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.

OrganizationId *1

* Name The organization this classification is for. If supplying user keys use the

OrganizationName attribute.

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


that is, OrganizationId(SourceSystemId)

ClassificationCode n/a The code for the organization’s classification. Alternatively the

ClassificationName can be supplied. Valid values for HCM classifications are:

ENTERPRISE Enterprise

DEPARTMENT Department

HCM_BARGAINING_ASSOCIATION Bargaining Association

HCM_DIVISION Division

HCM_DISABILITY_ORGANIZATION Disability Organization

HCM_REPORTING_ESTABLISHMENT Reporting Establishment


HCM Data Loader


HCM_LEMP Legal Employer

HCM_LRU Legal Reporting Unit

HCM_PSU Payroll Statutory Unit

Status * Status Indicates if the classification is active or inactive. This attribute is validated

using the lookup ACTIVE_INACTIVE

SetCode Department Set Mandatory for Department classifications. The code for the set the organization

belongs to.

Do not supply for other classification types.

LegislationCode n/a Only supply for Legal Employer classifications. The legislation code derived

from the legal entity.


OrganizationName Name The name of the organization this classification is for. Required if no other key

type is supplied to identify the organization.

ClassificationName In the UI, we do not use the


specific UIs for each of them.

For example, Manage

Departments, Manage


these examples,



The name of the organization’s classification. See the ClassificationCode

attribute for the list of valid HCM classification names.



user key.

Figure 21: Manage Departments: Other Classifications

Navigation: Workforce Structures - Manage Departments

Example of how the Other Classifications are displayed – there is no classification UI, but you can see for reference which other

classifications an Organization has. Other Classifications are displayed in the contextual area when navigating to an existing

Organization.


Organization Extra Information Component

The Organization Extra Information component holds the extensible flexfield information for an organization.

The discriminator OrgInformation is used to load Organization Extra Information records using HCM Data Loader.

The following OrgInformation attributes must be supplied when loading a new organization that has extensible

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

flexfield segments.

You cannot load Organization Extra Information records independently, they must always be supplied with the

parent Organization record, in the same Organization.dat file.

ORGANIZATION EXTRA INFORMATION ATTRIBUTES

HCM Data Loader

Attribute

User Interface


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 OrganizationName,

ClassificationName, OrgInformationContext, and SequenceNumber.

EffectiveStartDate * Effective Start Date The start date of the organization extensible flexfield data. This should match

the Organization’s effective start date.

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.

OrganizationId *1

* Name The organization this extensible flexfield data is for. If supplying user keys use

the OrganizationName and ClassificationName attributes

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


that is, OrganizationId(SourceSystemId)

FLEX:

PER_ORGANIZATION_IN

FORMATION_EFF

n/a Mandatory attribute. The context of the Organization Information EFF data

must be supplied against this attribute.

OrgInformationContext n/a Context Code for the extensible flexfield. This value should match the value

for the FLEX:PER_ORGANIZATION_INFORMATION_EFF attribute.

EFF_CATEGORY_CODE n/a Mandatory attribute. The extensible flexfield category code must be supplied

against this attribute. The extensible flexfield category code is the code of the

classification for all organizations except Legal Employer, PSU and TRU. For

these 3 the extensible flexfield category code will be for example HCM_LEMP_

<2 char leg code>.

You can find the category code by navigating to the Manage Extensible

Flexfields page and searching for the Flexfield Code

PER_ORGANIZATION_INFORMATION_EFF. Select and edit the

Organization Information EFF record. Expand the Category hierarchy to find

the relevant code for the organization type.

SequenceNumber n/a Unique sequence number for the extensible flexfield record for an organization.

This should start at 1, with the second EFF record for an organization having a

sequence number of 2 etc.


OrganizationName <Organization> Name The name of the organization this extensible flexfield record is for. Required if

no other key type is supplied to identify the organization.




user key.

Figure 22: Organization Information extensible flexfield

Navigation: Workforce Structures - Manage Departments - Create: Department Details

Figure 23: Organization Legislative Extra Information

Navigation: Workforce Structures - Manage Departments - Create: Department Details

Organization Dat File Examples

Creating an Organization Using Source Keys

This file creates an organization with division and department classifications and Organization Extra Information EFF

data.

The referenced location can be created using the Location dat file example supplied in the Creating Locations Using

Source Keys section on page 10.


METADATA|Organization|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Name|Classi

ficationCode|LocationId(SourceSystemId)

MERGE|Organization|VISION|MRKT|2000/01/01|Marketing|HCM_DIVISION|LOC_HQ

METADATA|OrgUnitClassification|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Or

ganizationId(SourceSystemId)|ClassificationCode|SetCode|Status

MERGE|OrgUnitClassification|VISION|MRKT_DIV|2000/01/01|MRKT|HCM_DIVISION||A

MERGE|OrgUnitClassification|VISION|MRKT_DEPT|2000/01/01|MRKT|DEPARTMENT|COMMON|A

METADATA|OrgInformation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Organizat

ionId(SourceSystemId)|FLEX:PER_ORGANIZATION_INFORMATION_EFF|EFF_CATEGORY_CODE|OrgInfo

rmationContext|SequenceNumber|_REPORTING_NAME(PER_ORGANIZATION_INFORMATION_EFF=PER_OR

G_MANAGER_INFO)

MERGE|OrgInformation|VISION|MRKT_INFO|2000/01/01|MRKT|PER_ORG_MANAGER_INFO|HCM_DIVISI

ON|PER_ORG_MANAGER_INFO|1|Vision Marketing

Creating a Disability Organization Using Source Keys

This file creates a disability organization.

The referenced location can be created using the Location dat file example supplied in the Creating Locations Using

Source Keys section on page 10.

METADATA|Organization|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Name|Classi

ficationName|LocationId(SourceSystemId)

MERGE|Organization|VISION|CLARITY|2000/01/01|Disability Organization Name|Disability

Organization|LOC_HQ


ganizationId(SourceSystemId)|ClassificationName|Status

MERGE|OrgUnitClassification|VISION|CLARITY_DIS|2000/01/01|CLARITY|Disability

Organization|A

Organization Errors

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


Error Resolution

The attribute {ATTRIBUTE_NAME} is invalid for the classification

{CLASSIFICATION_NAME}.

There is one generic organization service that is used for all

classifications. Some attributes are specific to one classification.

You must ensure that you only provide attributes that are valid for

the specified classification.

You must associate at least one classification to an organization. You cannot load an organization without associating it with a

classification.

You cannot classify an organization as an enterprise. As all organizations are created within the context of an Enterprise,

you cannot make any existing organization an Enterprise.

Deletion Support for Organization

You cannot delete organizations using HCM Data Loader. You can make those organization classifications which

are no longer used, inactive. However, you cannot make the organization itself inactive, but instead use the status of

the classification to make it inactive. For example, for an organization that has 2 classifications; department and


division, you can make the division inactive but leave the department as active so that you can still continue to use

the department.

If you want to deactivate the whole organization, you need to set the status for all classifications to inactive.

Inactivate Organization Dat File Examples

Making an Organization Inactive Using Source Keys

This file inactivates an existing organization classification, referencing the organization and its classification by

source key. You must supply a record for the organization with an effective start date of the date on which the

classification becomes inactive. If all classifications are made inactive the organization also becomes inactive.

Organization.dat

METADATA|Organization|SourceSystemOwner|SourceSystemId|EffectiveStartDate

MERGE|Organization|VISION|CLARITY|2015/01/01


ganizationId(SourceSystemId)|Status

MERGE|OrgUnitClassification|VISION|CLARITY_DIS|2015/01/01|CLARITY|I

Organization Translation

The Organization Name can be translated. The OrganizationTranslation.dat file is used to provide translation data

after the Organization has been created.

ORGANIZATION TRANSLATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner



attributes; BaseName, ClassificationName.


the organization being translated.



Name * Name The translated name of the organization in the language specified.

Language * not displayed The language of the supplied translated value.


BaseName Name The name of the Organization supplied when creating it. Required if you do not


ClassificationName In the UI we don’t use the


specific UIs for each of them,

for example Manage

Departments, Manage


these examples



The name of the organization’s classification. Required if you do not supply the

source key.


Position A Position is an instance of a job within a department. Often, a location and grade is also specified.

Considerations and Prerequisites for Positions

Positions are created within a business unit, so business units need to be created before you can load the Positions.

Job and Department are also mandatory attributes of the Position, so they need to be loaded before as well.

If you want to associate locations with your positions, then you need to load the locations before you load the

positions.

If you want to associate valid grades with your positions, then you need to load the grades before you load the

positions. Valid grades can be used to default or enforce the grade for an assignment.

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

records using the Manage Action Reasons task.

Loading Position

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

POSITION HIERARCHY


Position A position is an instance of a job within an organization. For example, you can create a

position HR Manager UK for the Human Resources organization for the Manager job.

Position

Position Valid

Grade

Grades that are valid for a position. PositionGrade

Position Evaluation Position evaluation is used to capture position evaluation criteria, for example, to record

the required points for know-how, accountability and problem solving, if the hay

evaluation system is used.

PositionEvaluation

Position Extra

Information

Represents the extensible structure for the position. PositionExtraInfo

Position Legislative

Extra Information

Represents the legislative extensible structure for the position. PositionLegislative

Position Component

The Position holds information like the Business Unit, Job, Department, Location and FTE, and Headcount.

The discriminator Position is used to load Position records using HCM Data Loader. The following Position

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


POSITION ATTRIBUTES

HCM Data Loader

Attribute

User Interface


SourceSystemId /

SourceSystemOwner


source key or the user key attributes BusinessUnitName and PositionCode.

EffectiveStartDate * Effective Start Date The start date of the position, or the update to the position if supplying date-

effective history.

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


PositionCode * Code A unique code for the position within the business unit.

BusinessUnitName * Business Unit The name of the business unit this position belongs to.

Name * Name The position name. This can be translated for your other enabled languages by

supplying the PositionTranslation.dat file.

ActionReasonCode Action Reason Code The action reason code for the position.

ActiveStatus * Status The status of the position. This attribute is validated using the ACTIVE_INACTIVE

lookup.

DepartmentId *1

* Department The department for the position. If supplying the user key value use the

DepartmentName attribute.

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


that is, DepartmentId(SourceSystemId).

JobId *1

* Job The job associated with the job. If supplying the user key value use the JobCode,

JobSetCode attributes.

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


that is, JobId(SourceSystemId).

LocationId *1

Location The optional location for this position. If supplying the user key value use the

LocationCode, LocationSetCode attributes.

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


that is, LocationId(SourceSystemId).

SupervisorId *1

Manager The optional supervisor for this position. If supplying the user key value use the

SupervisorPersonNumber attribute.

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


that is, SupervisorId(SourceSystemId).

SupervisorAssignmentId *1

Manager The optional supervisor’s assignment for this position. If supplying the user key

value use the SupervisorAssignmentNumber attribute.

If you supplied a source key when creating the supervisor assignment, supply the

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

name, that is, SupervisorAssignmentId(SourceSystemId).

FullPartTime Full Time or Part Time Specify if the position is full or part-time. This attribute is validated using the

PART_FULL_TIME lookup.

RegularTemporary Regular or Temporary Specify if the position is regular or temporary. This attribute is validated using the

REGULAR_TEMPORARY lookup.

FLEX:PER_POSITIONS_

DFF

Context Value Only supply if loading Position Attributes DFF data. The context for the DFF data

is supplied against this attribute.


HCM Data Loader

Attribute

User Interface


HiringStatus * Hiring Status The position hiring status, for example, Proposed, Frozen, Approved. This attribute

is validated using the HIRING_STATUS lookup.

PositionType Type The type of the position, for example Pooled, Shared, Single Incumbent or None.

This attribute is validated using the POSITION_TYPE lookup.

FTE FTE Full-time equivalent

HeadCount Head Count The head count, for example 1.

SecurityClearance Security Clearance The security clearance level for the position. This attribute is validated using the

SECURITY_CLEARANCE lookup.

ProbationPeriod Probation Period The length of the probation period. This attribute expects an integer.

ProbationPeriodUnitCd Probation Period The unit for the optional probation period, for example, Day, Week, Month or Year.

This attribute is validated using the PROBATION_PERIOD lookup.

BargainingUnitCd Bargaining Unit The bargaining unit code. This attribute is validated using the

BARGAINING_UNIT_CODE lookup.

OverlapAllowedFlag Overlap Allowed Is overlap allowed?

SeasonalFlag Seasonal Indicates if the position is seasonal.

SeasonalStartDate Seasonal Start Date The start date for seasonal positions.

SeasonalEndDate Seasonal End Date The end date for seasonal positions.

GradeLadderId Grade Ladder The optional grade ladder for this position. If supplying the user key value use the

GradeLadderName attribute.

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


that is, GradeLadderId(SourceSystemId).

EntryGradeId* Entry Grade The optional entry grade for this position. If supplying the user key value, use the

EntryGradeCode, EntryGradeSetCode, and EntryStepName attributes.

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


that is, EntryGradeId(SourceSystemId).

EntryStepId* Entry Step The optional entry grade step for this position. If supplying the user key value, use

the EntryGradeCode and EntryGradeSetCode attributes.

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


that is, EntryStepId(SourceSystemId).

WorkingHours Working Hours Number of standard working hours.

Frequency Frequency The frequency for the standard working hours. This attribute is validated using the

FREQUENCY lookup. Frequency is mandatory if you supply WorkingHours.

StartTime Start Time Regular start time.

EndTime End Time Regular end time.


DepartmentName Department The name of the department for the position. Required if no other key type is

supplied to identify the department.

JobCode Job The code for the job associated with this position. Required if no other key type is

supplied to identify the job.


HCM Data Loader

Attribute

User Interface


JobSetCode not displayed The set code for the job associated with this position. Required if no other key type

is supplied to identify the job.

LocationCode Location The code for the location of this position. Required if you want to specify a

location for the position and no other key type is supplied to identify the location.

LocationSetCode not displayed The set code for the location of this position. Required if you want to specify a

location for the position and no other key type is supplied to identify the location.

SupervisorPersonNum

ber

Manager The person number of the supervisor for this position. Required if you want to

specify a supervisor and no other key type is supplied to identify the supervisor.

SupervisorAssignment

Number

Manager The assignment number of the supervisor for this position. Required if you want to

specify a supervisor and no other key type is supplied to identify the supervisor

assignment.

GradeLadderName Grade Ladder The name of the grade ladder for this position. Required if you want to specify a

grade ladder and no other key type is supplied to identify the grade ladder.

EntryGradeCode Entry Grade The code for the entry grade for this position. Required if you want to specify an

entry grade and no other key type is supplied to identify the entry grade.

EntryGradeSetCode not displayed The set code for the entry grade for this position. Required if you want to specify

an entry grade and no other key type is supplied to identify the entry grade.

EntryStepName Entry Step The name for the entry grade step for this position. Required if you want to specify

an entry grade step and no other key type is supplied to identify the entry grade

step.



user key.


Figure 24: Create Position

Navigation: Workforce Structures - Manage Positions - Create: Position Details

Position Valid Grade Component

The Position Valid Grade component holds defines the valid grades for a position.

The discriminator PositionGrade is used to load Position Valid Grade records using HCM Data Loader. The

following PositionGrade attributes are commonly used when loading a new Position. Other optional attributes may

be available.

POSITION VALID GRADE ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner



PositionId *1

* Position The unique reference to position this valid grade is for. If using user keys supply

the PositionCode attribute.

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



HCM Data Loader


that is, PositionId(SourceSystemId).


effective history.

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


GradeId *1

* Grade The unique reference to the grade. If supplying the user key value, use the

GradeCode and SetCode attributes.


appropriate hint to the attribute name, for example, GradeId(SourceSystemId).


BusinessUnitName Business Unit The name of the business unit this position belongs to. Required if no other key

type is supplied to identify the position.

PositionCode Position Code The code of the position. Required if no other key type is supplied to identify the

position.

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

GradeSetCode not displayed The set code for the grade. Required if no other key type is supplied to identify the

grade.



user key.

Figure 25: Create Position: Valid Grades


Position Evaluation Component

The Position Evaluation component holds captures the evaluation criteria for a position.


The discriminator PositionEvaluation is used to load Position Evaluation records using HCM Data Loader. The

following PositionEvaluation attributes are commonly used when loading a new Position. Other optional attributes

may be available.

POSITION EVALUATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner



PositionId *1

* Position The unique reference to position this valid grade is for. If using user keys supply





EvaluationSystem * Evaluation System The evaluation system used for the position, for example Hay System. This

attribute is validated using the EVAL_SYSTEM lookup.

DateEvaluated * Evaluation Date Date of the evaluation.

MeasuredIn Measurement Unit The measurement unit for the evaluation, for example points. This attribute is

validated using the EVAL_SYSTEM_MEAS lookup.

Mandatory if using the Hay System.

Knowhow Knowhow Know how is a seeded criterion for the Hay evaluation system. Mandatory if using

the Hay System.

Accountability Accountability Accountability is a seeded criterion for the Hay evaluation system. Mandatory if


ProblemSolving Problem Solving Problem Solving is a seeded criterion for the Hay evaluation system. Mandatory if






position.



user key.


Figure 26: Create Position: Evaluation Criteria

Navigation: Workforce Structures - Manage Positions - Create: Evaluation Criteria

Position Extra Information Component

The Position Extra Information component holds extensible flexfield data for the position.

The discriminator PositionExtraInfo is used to load Position Extra Information records using HCM Data Loader.

The following PositionExtraInfo attributes are commonly used when loading a new Position. Other optional

attributes may be available.

POSITION EXTRA INFORMATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner




effective history.



PositionId *1

* Code The unique reference to position this valid grade is for. If using user keys supply





FLEX:PER_POSITIO

NS_EIT_EFF

n/a The context code for the Position EIT Information extensible flexfield data is


EFF_CATEGORY_C

ODE


Supply ‘POS_EIT’.

PoeiInformationCateg

ory

n/a The EFF context code.

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


HCM Data Loader


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




InformationType n/a Context Code for the extensible flexfield.

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




PositionCode Code The code of the position. Required if no other key type is supplied to identify the

position.



user key.

Figure 27: Create Position: Position Extra Information


Position Legislative Extra Information Component

The Position Legislative Extra Information component holds the legislative extensible flexfield data for the position.

The discriminator PositionLegislative is used to load Position Legislative Extra Information records using HCM

Data Loader. The following PositionLegislative attributes are commonly used when loading a new Position. Other

optional attributes may be available.

POSITION LEGISLATIVE EXTRA INFORMATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner




effective history.


HCM Data Loader




PositionId *1

* Position The unique reference to position this valid grade is for. If using user keys, supply





FLEX:PER_POSITIO

NS_LEG_EFF

n/a The context code for the Position Legislative Information extensible flexfield

data is supplied against this attribute.

EFF_CATEGORY_C

ODE


Supply ‘POS_LEG’.

InformationCategory n/a Extensible flexfield context code.






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





position.



user key.

Figure 28: Create Position: Position Legislative Data


Position Errors

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



Delete Position Dat File Examples

Deleting Position Using Source Key

This file deletes an existing position, referencing the position by source key.

Position.dat

METADATA|Position|SourceSystemOwner|SourceSystemId|EffectiveStartDate

DELETE|Position|VISION|APP_SALES|2015/01/01

Deleting Position Using User Key

This file deletes an existing position, referencing the position by user key.

Position.dat

METADATA|Position|BusinessUnitName|PositionCode|EffectiveStartDate

DELETE|Position|HDL_BU_COMMON|APP_SALES|2015/01/01

Position Translation

The Position Name can be translated. The PositionTranslation.dat file is used to provide translation data after the

Position has been created.

POSITION TRANSLATION ATTRIBUTES

HCM Data Loader


SourceSystemId /

SourceSystemOwner



attributes; BusinessUnitName, PositionCode.




the end of time.

Name * Position Name The translated value for the position name in the language specified.





PositionCode Code The code of the position. Required if no other key type is supplied to identify the

position.


Oracle Corporation, World Headquarters

500 Oracle Parkway

Redwood Shores, CA 94065, USA

Worldwide Inquiries

Phone: +1.650.506.7000

Fax: +1.650.506.7200

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0116 Loading Work Structures using HCM Data Loader January 2016

C O N N E C T W I T H U S

blogs.oracle.com/oracle

facebook.com/oracle

twitter.com/oracle

oracle.com

loading work structures using hcm data loaderloading work structures using hcm data loader oracle...

Documents