1. HCM Data Loading Business Objects
  2. Guidelines for Loading Goal Plans

Guidelines for Loading Goal Plans

Goal plans are used for the mass assignment of goals to worker populations. This topic describes aspects of the Goal Plan object that you must understand to load goal plans successfully.

Assigning Goals to Workers

When you load a Goal Plan object, the plan isn't automatically assigned to workers. You can assign the goal plan to workers in either of these ways:

  • Schedule goal plan assignments using the Manage Goal Plans task.

  • Load the Goal Plan Assignment component of the goal plan.

The Mass Request Component

The Mass Request component identifies who's requesting the goal plan. You can identify the plan requester on the goal plan itself by supplying the RequestSubmissionDate and ReqSubmittedByPersonNumber attributes, for example. In this case, the Mass Request component is created automatically and you don't have to supply it. However, you must supply a Mass Request component when you create a goal plan:

  • If you don't identify the plan requester on the Goal Plan object.

  • To associate a source key with the Mass Request record.

    Alternatively, you can update the default source key later using the Source Key object.

  • If you're loading child components of the Mass Request component.

    The child components of the Mass Request component identify the employee population to which the goal plan is to be assigned.

Deleting Goal Plans

You can delete Goal Plan objects using HCM Data Loader. However, don't delete goal plans that have been assigned to workers. When you delete a parent Goal Plan object, these child components are also deleted automatically:

  • Goal Plan Document Types

  • Mass Request

    Note: When you delete a Mass Request component, its child components are deleted automatically.

You can also delete child components individually, if required.

Goal Plan Goal and Goal Plan Assignment components aren't deleted automatically when you delete the parent Goal Plan component using HCM Data Loader. You must delete those components explicitly before you delete the parent goal plan. This example GoalPlan.dat file deletes the Goal Plan Goal component that links goal plan GP_001_01 with template goal TemplateGoal_001.

METADATA|GoalPlanGoal|SourceSystemId|SourceSystemOwner|GoalPlanExternalId
DELETE|GoalPlanGoal|GPG_001_01_SSID|VISION|GP_001_01

This example Goal.dat file deletes the template goal TemplateGoal_001 (SourceSystemId: TemplateGoal_001_SSID).

METADATA|Goal|SourceSystemId|SourceSystemOwner
DELETE|Goal|TemplateGoal_001_SSID|VISION

This example GoalPlan.dat file deletes the goal plan GP_001_01 and relevant child records.

METADATA|GoalPlan|GoalPlanExternalId
DELETE|GoalPlan|GP_001_01

Related Topics