Examples of Loading Job Families
A job family groups similar or related jobs for ease of reporting. For example, you could add the Trust Analyst and Operations Analyst jobs to the Analyst job family. This topic provides some examples showing how to load and manage Job Family objects.
Creating Job Families Using Source Keys
This example JobFamily.dat file creates several job families that are identified using source keys.
METADATA|JobFamily|SourceSystemOwner|SourceSystemId|EffectiveStartDate|JobFamilyCode|JobFamilyName|ActiveStatus
MERGE|JobFamily|VISION|ANALYST|2000/01/01|ANALYST|Analyst|A
MERGE|JobFamily|VISION|TECHNICIAN|2000/01/01|TECHNICIAN|Technician|A
MERGE|JobFamily|VISION|CONSULT|2000/01/01|CONSULTANT|Consultant|A
MERGE|JobFamily|VISION|MANAGEMENT|2000/01/01|MANAGEMENT|Management|ALoading Translated Job-Family Names
Job family names must be unique in the enterprise. Supply job family names in the language of the user who's loading them. You supply a JobFamilyTranslation.dat file to translate job-family names into other enabled languages once the job families exist. This example translates the names of existing job families. The job families are identified by their source keys.
METADATA|JobFamilyTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|JobFamilyName
MERGE|JobFamilyTranslation|VISION|ANALYST|2000/01/01|FR|Analyste
MERGE|JobFamilyTranslation|VISION|TECHNICIAN|2000/01/01|FR|TechnicienDeleting Job Families
You can delete a Job Family object using HCM Data Loader, provided that the job family isn't referenced by any job. This example deletes a job family. It identifies the job family by its source key.
METADATA|JobFamily|SourceSystemOwner|SourceSystemId|EffectiveStartDate
DELETE|JobFamily|VISION|TECHNICIAN|2000/01/01