1. HCM Data Loading Business Objects
  2. Examples of Loading Succession Plans

Examples of Loading Succession Plans

You can use HCM Data Loader to create and update succession plans. A succession plan identifies a group of workers as candidates to replace key personnel in an organization.

Succession plans include assessments of a worker's readiness to move into a vacancy and the risk and impact of the worker's loss. This topic provides some examples showing how to load succession plans.

Create Succession Plans

This example SuccessionPlan.dat file creates an incumbent succession plan using source keys.

METADATA|SuccessionPlan|SourceSystemOwner|SourceSystemId|PlanName|PlanType|Status|AccessTypeCode|IncumbentPersonId(SourceSystemId)
MERGE|SuccessionPlan|VISION|SP816003|Name of the incumbent succession plan|INCUMBENT|ACTIVE|PRIVATE|VISION006
METADATA|SuccessionPlanOwner|SourceSystemOwner|SourceSystemId|PlanId(SourceSystemId)|OwnerTypeCode|PersonId(SourceSystemId)
MERGE|SuccessionPlanOwner|VISION|SPO816003|SP816003|ADMINISTRATOR|VISION013
METADATA|SuccessionPlanCandidate|SourceSystemOwner|SourceSystemId|PlanId(SourceSystemId)|PersonId(SourceSystemId)|Status|CandidateReadiness
MERGE|SuccessionPlanCandidate|VISION|SPC816003|SP816003|VISION014|ACTIVE|READY_NOW

This example SuccessionPlan.dat file creates a job succession plan. It uses user keys to reference the job to which the succession plan relates, the succession plan owner, and its candidates.

METADATA|SuccessionPlan|SourceSystemOwner|SourceSystemId|PlanName|PlanType|Status|AccessTypeCode|JobCode|JobSetCode
MERGE|SuccessionPlan|VISION|SP_MRKT_DIR|Name of the job succession plan|JOB|ACTIVE|PRIVATE|HSDL_MRKT_DIR|COMMON
METADATA|SuccessionPlanOwner|SourceSystemOwner|SourceSystemId|PlanId(SourceSystemId)|OwnerTypeCode|PlanOwnerPersonNumber
MERGE|SuccessionPlanOwner|VISION|SPO_MRKT_DIR|SP_MRKT_DIR|ADMINISTRATOR|1023853
METADATA|SuccessionPlanCandidate|SourceSystemOwner|SourceSystemId|PlanId(SourceSystemId)|PlanCandidatePersonNumber|Status|CandidateReadiness
MERGE|SuccessionPlanCandidate|VISION|SPC009_MRKT_DIR|SP_MRKT_DIR|1023119|ACTIVE|READY_NOW
MERGE|SuccessionPlanCandidate|VISION|SPC008_MRKT_DIR|SP_MRKT_DIR|1032314|ACTIVE|READY_NOW
MERGE|SuccessionPlanCandidate|VISION|SPC007_MRKT_DIR|SP_MRKT_DIR|1023112|ACTIVE|READY_NOW

These rules apply when you create a succession plan using HCM Data Loader:

  • You must supply a Success Plan Owner component, and the OwnerTypeCode attribute must be ADMINISTRATOR. A succession plan must always have an administrator owner.

  • Incumbents, plan owners, and plan candidates must have active assignments.

Enable Alerts for Succession Plans

A succession plan has an Alerts section. This section has check boxes that control whether notifications are sent or not for assignment changes of either the plan incumbent or candidates. You can upload these alerts related attributes for succession plans:

  • IncumbentRoleChangeFlag: Indicates whether the job role has changed for the incumbent of a succession plan

  • EnableSuccessorAlert: Indicates whether an alert notification should be sent when a candidate moves to the role of the succession plan

  • EnableMovedToDiffRoleAlert: Determines whether an alert notification should be sent when a candidate moves to a role that's different from the role of the succession plan

  • EnableIncumbentJobChangeAlert: Determines whether an alert notification should be sent when the plan incumbent's role changes

    Note: You can set a value for this attribute only for Incumbent type succession plans.

When you upload data about the succession plan owners, use the EnableAlert attribute to enable alerts for the plan owner.

When you upload candidate data, you can also upload these attributes:

  • ShowSuccessionStatusFlag: Determines if banners are shown in the Candidates section when a candidate changes roles.

  • SuccessionStatus: Indicates the code of the candidate succession status. The values that you can enter are NULL, ORA_HRM_MOVED_TO_DIFF_ROLE, and ORA_HRM_SUCCESSOR. The default value is NULL.

This example SuccessionPlan.dat file creates a job succession plan. It enables alerts for these assignment changes:

  • Candidate moves to the role of the succession plan

  • Candidate moves to a role that's different from the role of the succession plan

It also enables alerts for the plan owner and shows a banner for a candidate to indicate the candidate's role change.

METADATA|SuccessionPlan|SourceSystemOwner|SourceSystemId|PlanName|PlanType|Status|AccessTypeCode|JobCode|JobSetCode|EnableSuccessorAlert|EnableMovedToDiffRoleAlert
MERGE|SuccessionPlan|VISION|SP_MRKT_MGR|Marketing Manager job succession plan|JOB|ACTIVE|PUBLIC|HDL_MRKT_MGR|COMMON|Y|Y
METADATA|SuccessionPlanOwner|SourceSystemOwner|SourceSystemId|PlanId(SourceSystemId)|OwnerTypeCode|PlanOwnerPersonNumber|EnableAlert
MERGE|SuccessionPlanOwner|VISION|SPO_MRKT_DIR|SP_MRKT_DIR|ADMINISTRATOR|1023853|Y
METADATA|SuccessionPlanCandidate|SourceSystemOwner|SourceSystemId|PlanId(SourceSystemId)|PlanCandidatePersonNumber|Status|EmergencySuccessor|CandidateReadiness|ShowSuccessionStatusFlag|SuccessionStatus
MERGE|SuccessionPlanCandidate|VISION|SPC009_MRKT_DIR|SP_MRKT_MGR|1023119|ACTIVE|Y|READY_NOW|Y|ORA_HRM_SUCCESSOR
MERGE|SuccessionPlanCandidate|VISION|SPC008_MRKT_DIR|SP_MRKT_DIR|1032314|ACTIVE|READY_IN_2_YEARS|N|NULL

Remove Plan Owners

Sometimes workers may no longer be part of the organization. You may want to remove terminated workers who were added as owners from succession plans.

This example SuccessionPlan.dat file is used for removing a terminated plan owner from a succession plan. It uses source keys to identify the succession plan.

METADATA|SuccessionPlanOwner|SourceSystemOwner|SourceSystemId|PlanId(SourceSystemId)|PlanOwnerPersonNumber
DELETE|SuccessionPlanOwner|VISION|SPO_MRKT_DIR|SP_MRKT_DIR|1023853