Examples of Loading Person Types

System person types are predefined values that identify groups such as employees and contingent workers. You can't create, edit, or delete system person types. However, each system person type is associated with one or more user person types, which further categorize the group.

You can create, edit, and delete user person types. For example, you could define Associate and Remote Worker as user person types of the Employee system person type. For any system person type, one user person type must be identified as the default value. This topic provides examples showing how to load and manage user Person Type objects using HCM Data Loader.

Creating Person Types

This example PersonType.dat file creates the Officer and Rating user person types for the Employee system person type. It identifies the person types using source keys.

METADATA|PersonType|SourceSystemOwner|SourceSystemId|SystemPersonType|UserPersonType|ActiveFlag|DefaultFlag
MERGE|PersonType|VISION|PT_EMP_OFFICER|EMP|Officer|Y|N
MERGE|PersonType|VISION|PT_EMP_RATING|EMP|Rating|Y|N

Loading Translated Person-Type Names

Supply person-type names in the language of the user who's loading them. You supply a PersonTypeTranslation.dat file to translate person-type names into other enabled languages once the person types exist. This example translates the name of an existing person type. The person type is identified by its source key.

METADATA|PersonTypeTranslation|SourceSystemOwner|SourceSystemId|Language|UserPersonType
MERGE|PersonTypeTranslation|VISION|PT_EMP_OFFICER|FR|Officier

Deleting Person Types

You can delete Person Type objects using HCM Data Loader, provided that the person type isn't being used. This example PersonType.dat file deletes person types and any translated versions of the person-type names. It identifies the person types by their source keys.

METADATA|PersonType|SourceSystemOwner|SourceSystemId
DELETE|PersonType|VISION|PT_EMP_OFFICER
DELETE|PersonType|VISION|PT_EMP_RATING