Examples of Loading Goal Plans

This topic provides examples showing how to load Goal Plan objects using HCM Data Loader.

Creating a Goal Plan

This example GoalPlan.dat file loads a goal plan without a Mass Request component. In this case, a mass request record for the goal plan is created automatically using the values passed for the ReqSubmittedByPersonNumber and RequestSubmissionDate attributes.

METADATA|GoalPlan|GoalPlanExternalId|GoalPlanName|GoalPlanTypeCode|GoalPlanActiveFlag|EnableWeightingFlag|StartDate|EndDate|EnforceGoalWeightFlag|GoalAccessLevelCode|IncludeInPerfdocFlag|ReqSubmittedByPersonNumber|RequestSubmissionDate|ReviewPeriodName
MERGE|GoalPlan|GP_001_01|GP_001_01|ORA_HRG_WORKER|A|Y|2015/01/01|2015/12/31|Y|HR specialist and manager|N|8153756|2015/09/20|Default Review Period - Vision Corporation Enterprise

Creating a Goal Plan with Document Types

This example GoalPlan.dat file creates a goal plan with the IncludeInPerfdocFlag attribute set to Y and assigns a document type. In this example, the GoalPlanExternalId attribute in the GoalPlanDocTypes component identifies the goal plan the performance document type is for.

METADATA|GoalPlan|GoalPlanExternalId|GoalPlanName|GoalPlanTypeCode|GoalPlanActiveFlag|EnableWeightingFlag|StartDate|EndDate|EnforceGoalWeightFlag|GoalAccessLevelCode|IncludeInPerfdocFlag|ReqSubmittedByPersonNumber|RequestSubmissionDate|ReviewPeriodName
MERGE|GoalPlan|GP_001_02|GP_001_02|ORA_HRG_WORKER|A|Y|2016/01/01|2016/12/31|Y|HR specialist and manager|Y|8153756|2016/10/04|Default Review Period - Vision Corporation Enterprise
METADATA|GoalPlanDocTypes|GoalPlanExternalId|DocTypeName
MERGE|GoalPlanDocTypes|GP_001_02|Annual Evaluations

Creating a Goal Plan with Mass Request Component

Use the MassRequest discriminator to load goal plan mass request records using HCM Data Loader. The Mass Request component holds attributes of the mass request object associated with the goal plan. It's referenced by sub-components that collectively define the employee population or organization to assign the goal plan to.

This example GoalPlan.dat file first loads a goal plan. The GoalPlanExternalId attribute in the MassRequest component that's later included in the file identifies the goal plan the mass request is for.

METADATA|GoalPlan|GoalPlanExternalId|GoalPlanName|GoalPlanTypeCode|GoalPlanActiveFlag|EnableWeightingFlag|StartDate|EndDate|EnforceGoalWeightFlag|GoalAccessLevelCode|IncludeInPerfdocFlag|ReviewPeriodName
MERGE|GoalPlan|GP_001_03|GP_001_03|Performance|A|Y|2016/01/01|2016/12/31|Y|HR specialist and manager|N|Default Review Period - Vision Corporation Enterprise
METADATA|MassRequest|GoalPlanExternalId|ReqSubmittedByPersonNumber
MERGE|MassRequest|GP_001_03|8153756

Note:

The attributes ReqSubmittedByPersonId and RequestSubmissionDate aren't specified for the GoalPlan component in this case.

The Mass Request Assignment component holds information about an organization to associate the goal plan with. Use the MassRequestAssignment discriminator to load mass request assignment records for a mass request within a goal plan using HCM Data Loader.

This example GoalPlan.dat file creates a goal plan with a mass request assignment for the mass request.

METADATA|GoalPlan|GoalPlanExternalId|GoalPlanName|GoalPlanTypeCode|GoalPlanActiveFlag|EnableWeightingFlag|StartDate|EndDate|EnforceGoalWeightFlag|GoalAccessLevelCode|IncludeInPerfdocFlag|ReviewPeriodName
MERGE|GoalPlan|GP_001_05|GP_001_05|Performance|A|Y|2016/01/01|2016/12/31|Y|HR specialist and manager|N|Default Review Period - Vision Corporation Enterprise
METADATA|MassRequest|GoalPlanExternalId|ReqSubmittedByPersonNumber
MERGE|MassRequest|GP_001_05|8153756
METADATA|MassRequestAssignment|OrganizationName|GoalPlanExternalId
MERGE|MassRequestAssignment|Vision Corporation Enterprise|GP_001_05

This example GoalPlan.dat file creates a mass request assignment for a goal plan and mass request that already exist. This file uses the user keys attributes to identify the existing goal plan and organization, but you can also use source keys instead.

METADATA|MassRequestAssignment|OrganizationName|GoalPlanExternalId
MERGE|MassRequestAssignment|Vision Air|GP_001_05

Creating a Goal Plan with Eligibility Criteria

Use the discriminator EligibilityProfileObject to load eligibility profile records for a goal plan using HCM Data Loader. The Eligibility Profile Object component includes a reference to an eligibility profile object that defines selection criteria for employees to assign the goal plan to.

This example GoalPlan.dat file creates a goal plan with Mass Request and Eligibility Profile Object components. In the Eligibility Profile Object component, the GoalPlanExternalId attribute identifies the goal with which the eligibility profile is associated. In this example, the Goals_EligibilityProfile_Software Developer 4 eligibility profile is associated with the GP_001_04 goal plan. This eligibility profile is marked as required.

METADATA|GoalPlan|GoalPlanExternalId|GoalPlanName|GoalPlanTypeCode|GoalPlanActiveFlag|EnableWeightingFlag|StartDate|EndDate|EnforceGoalWeightFlag|GoalAccessLevelCode|IncludeInPerfdocFlag|ReviewPeriodName
MERGE|GoalPlan|GP_001_04|GP_001_04|ORA_HRG_WORKER|A|Y|2016/01/01|2016/12/31|Y|HR specialist and manager|N|Default Review Period - Vision Corporation Enterprise
METADATA|MassRequest|GoalPlanExternalId|ReqSubmittedByPersonNumber
MERGE|MassRequest|GP_001_04|8153756
METADATA|EligibilityProfileObject|GoalPlanExternalId|EligibilityProfileName|RequiredFlag
MERGE|EligibilityProfileObject|GP_001_04|Goals_EligibilityProfile_Software Developer 4|Y

Creating a Goal Plan with Mass Request Hierarchy Component

The Mass Request Hierarchy component holds information about a manager hierarchy or specific employees included in the goal plan. Use the MassRequestHierarchy discriminator to load mass request hierarchy records for a goal plan using HCM Data Loader. You can specify any of these values for the CascadingLevel attribute:

0: Only to the manager
1: Employees who directly report to the manager
999999: All employees reporting to the manager
2: Manager and employees who directly report to the manager
1000000: Manager and all employees reporting to the manager

This example GoalPlan.dat file loads a goal plan with a hierarchy for the mass request. All employees in the hierarchy of the manager identified by the ManagerAssignmentNumber attribute in the Mass Request Hierarchy component are assigned the goal that's identified by the GoalPlanExternalId attribute.

METADATA|GoalPlan|GoalPlanExternalId|GoalPlanName|GoalPlanTypeCode|GoalPlanActiveFlag|EnableWeightingFlag|StartDate|EndDate|EnforceGoalWeightFlag|GoalAccessLevelCode|IncludeInPerfdocFlag|ReviewPeriodName
MERGE|GoalPlan|GP_001_06|GP_001_06|Performance|A|Y|2016/01/01|2016/12/31|Y|HR specialist and manager|N|Default Review Period - Vision Corporation Enterprise
METADATA|MassRequest|GoalPlanExternalId|ReqSubmittedByPersonNumber
MERGE|MassRequest|GP_001_06|8153756
COMMENT Assigning Worker to Goal Plan GP_001_06
METADATA|MassRequestHierarchy|GoalPlanExternalId|ManagerAssignmentNumber|CascadingLevel
MERGE|MassRequestHierarchy|GP_001_06|EEEE8153786|999999

This example GoalPlan.dat file creates a mass request hierarchy for a goal plan and mass request that already exist. This example uses the user key attribute to identify the goal plan and manager assignment. You can also use source keys to identify these records.

COMMENT Assigning Worker to Goal Plan GP_001_06
METADATA|MassRequestHierarchy|GoalPlanExternalId|ManagerAssignmentNumber|CascadingLevel
MERGE|MassRequestHierarchy|GP_001_06|EEEE8153794|0

Creating a Mass Request Exemption Component

You can create a mass request for goal plan assignment but exempt certain employees from the assignment. You do this by using the Mass Request Exemption component, which specifies the employees who are exempted from the goal plan. This component can only be passed for MassRequestHierarchy records where the CascadingLevel isn't zero. For example, when the cascading level is Direct reports, All reports, Self and direct reports, or Self and all reports.

Use the MassRequestExemption discriminator to load mass request exemption records for a goal plan using HCM Data Loader. This example GoalPlan.dat file creates a goal plan with a mass request exemption for the hierarchy.

METADATA|GoalPlan|GoalPlanExternalId|GoalPlanName|GoalPlanTypeCode|GoalPlanActiveFlag|EnableWeightingFlag|StartDate|EndDate|EnforceGoalWeightFlag|GoalAccessLevelCode|IncludeInPerfdocFlag|ReviewPeriodName
MERGE|GoalPlan|GP_001_07|GP_001_07|Performance|A|Y|2016/01/01|2016/12/31|Y|HR specialist and manager|N|Default Review Period - Vision Corporation Enterprise
METADATA|MassRequest|GoalPlanExternalId|ReqSubmittedByPersonNumber
MERGE|MassRequest|GP_001_07|8153756
COMMENT Assigning Worker to Goal Plan GP_001_07
METADATA|MassRequestHierarchy|GoalPlanExternalId|ManagerAssignmentNumber|CascadingLevel
MERGE|MassRequestHierarchy|GP_001_07|EEEE8153786|999999
COMMENT Excluding one worker from Goal Plan GP_001_07
METADATA|MassRequestExemption|GoalPlanExternalId|ManagerAssignmentNumber|WorkerAssignmentNumber
MERGE|MassRequestExemption|GP_001_07|EEEE8153786|EEEE8153787

This file creates a mass request exemption for an existing goal plan and mass request hierarchy.

COMMENT Excluding another worker from Goal Plan GP_012_01
METADATA|MassRequestExemption|SourceSystemId|SourceSystemOwner|WorkerAssignmentNumber|MassRequestHierarchyId(SourceSystemId)|GoalPlanExternalId
MERGE|MassRequestExemption|MRH_012_02_SSID|VISION|EEEE8153794|MRH_012_01_SSID|GP_012_01

The source key for mass request hierarchy MassRequestHierarchyId(SourceSystemId) identifies the mass request hierarchy. The GoalPlanExternalId attribute identifies the goal plan.