Guidelines for Loading Goal Plan Sets
Goal plan sets are used for the mass assignment of related goal plans to worker populations. This topic describes aspects of the Goal Plan Set object that you must understand to load goal plan sets successfully.
Assigning Goal Plan Sets to Workers
When you load a goal plan set, it's not automatically assigned to workers. You can assign the goal plan set to workers in either of these ways:
-
Schedule goal plan set assignments using the Manage Goal Plan Sets task.
-
Load the Goal Plan Assignment component of the Goal Plan object. You may use this approach, for example, to assign goals following the transfer of workers from one legal entity to another.
The Mass Request Component
The Mass Request component identifies who's requesting the goal plan set. You can identify the plan requester on the goal plan set 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 set:
-
If you don't identify the plan requester on the Goal Plan Set 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 set is to be assigned.
Deleting Goal Plan Sets
You can delete Goal Plan Set objects using HCM Data Loader. When you delete a parent goal plan set, these child components are also deleted automatically:
-
Goal Plan Set Plan
-
Mass Request
Don't delete goal plan sets that have already been assigned to workers.
This example GoalPlanSet.dat file deletes a goal plan set and its child components.
METADATA|GoalPlanSet|GoalPlanSetExternalId
DELETE|GoalPlanSet|GPS_006_01