1. HCM Data Loading Business Objects
  2. Guidelines for Loading Positions

Guidelines for Loading Positions

A position is a single occurrence of a job in a specified department. Positions may also be restricted by location. For example, you could create the HR Manager Sales France position for the HR Manager job in the Sales department in France.

This topic describes aspects of the Position object that you must understand to load positions successfully.

Effective Start Dates

A Position object and its child components must have the same effective start date.

Loading Referenced Objects

Before you load positions, referenced objects must exist in the target environment. In particular:

  • Positions exist in business units. Ensure that referenced business units exist.

  • Both Job and Department are required attributes of a position. Ensure that referenced jobs and departments exist.

  • You can associate a location and valid grades with a position. Ensure that any referenced locations and grades exist.

Position Type

When the position type is Single incumbent, you must supply:

  • An FTE value. The value must be less than or equal to 1. For example, if the position incumbent works half the standard working hours, then the full-time equivalent value is 0.5.

  • A headcount of 1.

When the position type is Shared, you must supply:

  • An FTE value

  • A headcount that's equal to or greater than 1

Note: When loading positions, the position code can be automatically generated, hence we recommend you leave the position code blank in the dat file to avoid duplicate position codes being generated.

Loading Translated Position Names

Supply position names in the language of the user who's loading them. You supply a PositionTranslation.dat file to translate position names into other enabled languages once the positions exist. This example PositionTranslation.dat file translates the name of an existing position. It identifies the position by its source key.

METADATA|PositionTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|Name
MERGE|PositionTranslation|VISION|APP_SALES|2015/01/01|FR|Sales Consultant d'application

Deleting Positions

You can delete a Position object using HCM Data Loader, provided that it has never had an incumbent. When you delete a position, its child components are deleted automatically. This example Position.dat file deletes an existing position. The position is identified by its source key.

METADATA|Position|SourceSystemOwner|SourceSystemId|EffectiveStartDate
DELETE|Position|VISION|APP_SALES|2015/01/01

Prevent Inflight Position Updates

You can prevent inflight position updates when it's updated using the Request a Position Change, update, or correct flows, or when a date effective position record is deleted, when approvals are pending. You need to create and set the HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER profile option to No, if it's not already created; to prevent inflight position updates.

Related Topics