0% found this document useful (0 votes)

69 views65 pages

Load Goal Data with HCM Data Loader

This technical brief outlines the process for loading goal data using HCM Data Loader in Oracle Fusion Human Capital Management. It details various business scenarios, prerequisites, and the structure of data files necessary for loading goals, goal plans, and goal plan sets. Additionally, it provides examples of data attributes and error handling related to goal management functionalities.

Uploaded by

Dinesh

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

69 views65 pages

Load Goal Data with HCM Data Loader

Uploaded by

Dinesh

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

Loading Goal Data

Using HCM Data Loader

Oracle Fusion Human Capital Management 11g Release 11 Update 12 and Later
O R A C L E TECHNICAL BRIEF | DECEMBER 2016
Table of Contents

Introduction 1
How to Use the Information in This Document 1
Example Dat Files 2
Supported Business Scenarios 3
Considerations and Prerequisites for Goal 4
Loading Goal 4
Goal 4
Goal Action 9
Goal Plan Goal 11
Goal Target Outcome 13
Goal Measurement 15
Goal Access 18
Goal Alignment 19
Goal Errors 20
Deletion Support for Goal 23
Deleting Goal Dat File Examples 24
Considerations and Prerequisites for Goal Plan 25
Loading Goal Plan 25
Goal Plan 25
Goal Plan Dat File Examples 27
Goal Plan Goal 27
Goal Dat File Examples 29
Goal Plan Document Type 30
Goal Plan Dat File Examples 30
Mass Request 31
Goal Plan Dat File Examples 32
Eligibility Profile Object 32
Goal Plan Dat File Examples 33
Mass Request Assignment 34
Goal Plan Dat File Examples 34

LOADING GOAL DATA USING HCM DATA LOADER

Mass Request Hierarchy 35
Goal Plan Dat File Examples 36
Mass Request Exemption 37
Goal Plan Dat File Examples 39
Goal Plan Assignment 39
Goal Plan Dat File Examples 41
Goal Plan Errors 43
Deletion Support for Goal Plan 45
Deleting Goal Plan Dat File Examples 45
Considerations and Prerequisites for Goal Plan Set 47
Loading Goal Plan Set 47
Goal Plan Set 47
Goal Plan Set Dat File Examples 49
Goal Plan Set Plan 49
Goal Plan Set Dat File Examples 50
Mass Request 51
Goal Plan Set Dat File Examples 52
Eligibility Profile Object 52
Goal Plan Set Dat File Examples 53
Mass Request Hierarchy 53
Goal Plan Set Dat File Examples 55
Mass Request Exemption 56
Goal Plan Set Dat File Examples 57
Goal Plan Set Errors 58
Deletion Support for Goal Plan Set 59
Delete Goal Plan Set Dat File Examples 60

Table of Figures
Figure 1: Goal (Goal Details) .................................................................................................................................... 8
Figure 2: Goal Action (Goal Details) ....................................................................................................................... 10
Figure 3: Goal Plan Goal ........................................................................................................................................ 12
Figure 4: Goal Target Outcome (Goal Details) ....................................................................................................... 15

LOADING GOAL DATA USING HCM DATA LOADER

Figure 5: Goal Measurement (Goal Details) ........................................................................................................... 17
Figure 6: Goal Access ............................................................................................................................................ 18
Figure 7: Goal Alignment ........................................................................................................................................ 20
Figure 8: Goal Plan (Manage Goal Plans) .............................................................................................................. 27
Figure 9: Goal Plan Goal (Manage Goal Plans) ...................................................................................................... 29
Figure 10: Eligibility Profile Object (Manage Goal Plans) ........................................................................................ 33
Figure 11: Mass Request Assignment (Manage Goal Plans).................................................................................. 34
Figure 12: Mass Request Hierarchy (Manage Goal Plans) ..................................................................................... 36
Figure 13: Mass Request Exemption (Manage Goal Plans) ................................................................................... 38
Figure 14: Worker’s Goal Plan (My Goals) ............................................................................................................. 41
Figure 15: Goal Plan Set (Manage Goal Plan Sets) ............................................................................................... 48
Figure 16: Goal Plan Set Plan (Manage Goal Plan Sets) ....................................................................................... 50
Figure 17: Eligibility Profile Object (Manage Goal Plan Sets) ................................................................................. 53
Figure 18: Mass Request Hierarchy (Manage Goal Plan Sets) ............................................................................... 55
Figure 19: Mass Request Exemption (Manage Goal Plan Sets) ............................................................................. 57

LOADING GOAL DATA USING HCM DATA LOADER

Introduction
Whether implementing Goal Management for the first time or providing regular updates, you can
create goal, goal plan, and goal plan set records using HCM Data Loader.

For general information about preparing data for loading using HCM Data Loader or the HCM Data
Loader file format, see the HCM Data Loader User’s Guide (MOS Doc ID: 1664133.1).

How to Use the Information in This Document

This document provides a separate section for each business object that it describes. Each section
covers the following topics:

 Considerations and Prerequisites What to consider before attempting to load data

 Loading Describes the business object hierarchy. For each business object component, a table of
the attributes that are commonly supplied when creating new records is provided. These tables
have the following columns:

 HCM Data Loader Attribute The attribute name to supply when providing your data in the
business object data (.dat) file. Attribute names with a *1 suffix are foreign-object references
that support the integration key types. As source keys are recommended where possible, the
document describes how to supply source key values. User key attributes are identified for
when you do not have the source key value.
 User Interface Prompt The prompt seen on the user interface. The data that you supply in
the associated attribute derives this field value, which is not necessarily the same as the value
that you supply. For example, for the Location field on an Organization page you can supply
the Oracle Fusion surrogate ID, source key, or Oracle Fusion GUID to identify the location
uniquely. The value seen on the user interface will be the location name.
If the User Interface Prompt is prefixed with an asterisk (*), then the attribute is mandatory
when you create a new record.
 Functional Description Additional information describing the attribute and how to supply
valid values.

 Errors Identifies errors that may occur when loading data for the business object. Information
about resolving the error is provided.
 Deletion Support Describes the extent to which the business object supports data deletion. Some
objects do not support deletion, while others may support deletion of child records only.
 Translation Information on how to provide translation data for the translatable attributes in the
business object hierarchy.

1 | LOADING GOAL DATA USING HCM DATA LOADER

Example Dat Files
This document provides working dat file examples for loading and deleting data using HCM Data
Loader. To use the source key examples, change the source system owner to a lookup code you have
preconfigured in the HRC_SOURCE_SYSTEM_OWNER lookup.

For both user key and source key examples, ensure any references to foreign objects refer to data that
exists in your test environment.

2 | LOADING GOAL DATA USING HCM DATA LOADER

Supported Business Scenarios
The table below lists scenarios that could be implemented using HCM Data Loader and shows the
required load sequence for each scenario.

Business Scenario Object Load Sequence Notes

Load Library Goals 1. Content Item Library goals are loaded as Content Items.

Load Template Goals 1. Person (HR) Goal plans are required.

2. Assignment (HR)
3. Goal Plan
4. Goal

Load Organization Goals 1. Person (Line Manager) Person refers to the organization owner.
2. Organization Goal plans are required.
3. Goal Plan
4. Goal

Load Goal Plans 1. Goal Goal plan objects can reference template
2. Assignment (Worker) goals.
3. Person (Worker) Primary worker job assignments are required if
4. Eligibility Profile workers and managers are referenced.
5. Organization
6. Goal Plan Doc Type Organizations are required for organization
7. Goal Plan goal plans.
Review periods must exist in the database
before uploading associated goal plans.
Goal Plan Document Type entry is required in
the [Link] file when the
IncludeInPerfDoc flag has value of Y.

Load Goal Plan Sets 1. Goal Plan Goal plan set objects can reference goal
2. Person (Worker) plans.
3. Assignment (Worker) Primary worker job assignments are required if
4. Eligibility Profile workers and managers are referenced.
5. Goal Plan Set
Review periods must exist in the database
before uploading associated goal plan sets.

Load Worker Performance 1. Assignment (Worker) Goal supports references to library goals.
Goals 2. Person (Worker) Worker performance goals must be associated
3. Goal Plan with goal plans.
4. Content Item
5. Goal

Load Worker Development 1. Person (Worker) Worker development goals are not associated
Goals 2. Content Item with goal plans.
3. Goal

Goal
Goals represent objectives of employees and organizations and can be used as templates for other goals. Goals
can have tasks and desired outcomes; achievement of goals can be measured. Employees can share their goals
with other employees; they can also align their goals with other employee and organization goals. Goals can be
associated with goal plans. The load use cases for goal are listed in the Supported Business Scenarios section
above and they are Load Template Goals, Load Organization Goals, Load Worker Performance Goals, and Load

3 | LOADING GOAL DATA USING HCM DATA LOADER

Worker Development Goals. Load Worker Performance Goals and Load Worker Development Goals are
collectively referred to as Load Worker Goals.

For more information on goals and their types, see the help topic Goal Management: Explained in Oracle
Applications Help at [Link]

Considerations and Prerequisites for Goal

There are three distinct uses of the Goal object:

 Template Goal – a goal used in goal plan objects

 Organization Goal – a goal created by a manager for a specific organization
 Worker Goal – a goal assigned to a worker by HR or a manager
See the Supported Business Scenarios section to identify prerequisites for loading Goal data for each of these
cases.

Library Goals are stored and loaded as Profile Content Items. Loading of Profile Content Items is not covered in this
document. Library Goals however can be referenced in Goal objects as described below in the Goal section.

Loading Goal
Goal data must be supplied in the [Link] file for processing by HCM Data Loader.

GOAL HIERARCHY

Component Functional Description Discriminator

Goal Details of a goal. Goal

Goal Action Details of goal tasks. GoalAction

Goal Plan Goal Details of relationships between goals and goal plans. GoalPlanGoal
Used in Load Worker Performance Goals and Load Organization Goals cases.

Goal Target Outcome Desired goal outcomes. GoalTargetOutcome

Choices for target outcomes are limited to three seeded content types.
Not used in Load Organization Goals.

Goal Measurement Details of single and multiple measurements associated with a goal. GoalMeasurement
Only single measurement can be defined for a development goal.

Goal Access Details of workers the goal is shared with. GoalAccess

Used in Load Worker Goals cases.

Goal Alignment Details of a goal the goal is aligned to. GoalAlignment

Used in Load Worker Goals and Load Organization Goals cases.

Goal
The Goal component holds the main information about a goal including its name, success criteria, completion
percentage, and other attributes.

4 | LOADING GOAL DATA USING HCM DATA LOADER

The discriminator Goal is used to load goal records using HCM Data Loader. The following Goal attributes are
commonly supplied when loading a new goal.

GOAL ATTRIBUTES

HCM Data Loader User Interface

Functional Description
Attribute Prompt

GoalName * Goal Name The name of the goal. There is no unique requirement.

StartDate *Start Date The start date of the goal.

TargetCompletionDate Target Completion Date The target completion date for the goal.

GoalTypeCode * Goal Type The type of goal.

Load Template Goals / Load Worker Goals scenario:
This attribute is validated using the lookup HRG_GOAL_TYPE. If not passed, this
attribute defaults to PERFORMANCE.
Load Organization Goals Scenario:
You must either pass PERFORMANCE for this attribute or leave it blank.

GoalSubTypeCode Subtype The subtype of the goal.

Load Template Goals / Load Worker Goals scenario:
This attribute is validated using the lookup HRG_SUB_TYPE_CODE.
Load Organization Goals scenario:
Not used.

GoalVersionTypeCode * (not displayed) The goal status.

Load Worker Goals / Load Organization Goals scenario:
On initial load, the value must be ACTIVE or left blank
Load Template Goals scenario:
Supply MASS_REQ.
This attribute is validated using the lookup HRG_GOAL_VERSION_TYPE.

GoalExtId External ID Provides a reference to an external goal source.

*1
PersonId * Person Number Unique ID that identifies a person.
Load Worker Goals scenario:
Reference the person the goal is for.
Load Template Goals scenario:
Reference the HR Specialist who is creating the goal plan that will contain these
goals.
If supplying user keys, then use the WorkerPersonNumber attribute.
This attribute also supports the integration key types. If you supplied a source key
for the person, then supply the same value here and append the source key hint to
the attribute name. For example: PersonId(SourceSystemId).

AssignmentId 1 Assignment Number Unique ID that identifies an assignment.

Load Worker Goals scenario:
Reference the assignment the goal is for.
Load Template Goals scenario:

5 | LOADING GOAL DATA USING HCM DATA LOADER

HCM Data Loader User Interface
Functional Description
Attribute Prompt

Reference the assignment of the HR Specialist who is creating the goal plan that
will contain these goals.
If supplying user keys, then use the WorkerAssignmentNumber attribute.
This attribute also supports the integration key types. If you supplied a source key
for the assignment, then supply the same value here and append the source key
hint to the attribute name. For example, AssignmentId(SourceSystemId).
*1
OrganizationId * Department Used for the Load Organization Goals scenario only.
Unique ID that identifies the organization this goal is for. If supplying user keys,
then use the OrganizationName attribute.
This attribute also supports the integration key types. If you supplied a source key
for the organization, then supply the same value here and append the source key
hint to the attribute name. For example: OrganizationId(SourceSystemId).

PublishedFlag Published Used for the Load Organization Goals scenario only.
Indicates whether an organization goal is published to the organization. The
manager who owns the goal can set the flag using the goal action Publish in the
application.

Description Description Goal description.

SuccessCriteria Success Criteria Success criteria for goal achievement.

PercentCompleteCode Completion Percentage Goal completion percentage code. This attribute is validated using the lookup
HRG_PERCENT_COMPLETE.

StatusCode * Status Status of the goal. This attribute is validated using the lookup
HRG_GOAL_STATUS

ActualCompletionDate Actual Completion Date Actual completion date of the goal.

PriorityCode Priority Priority of the goal. This attribute is validated using the lookup HRG_PRIORITY.
*1
RequestorPersonId (not displayed) Unique ID that identifies the person requesting the goal. If supplying user keys,
then use the RequestorPersonNumber attribute.
This attribute also supports the integration key types. If you supplied a source key
for the person, then supply the same value here and append the source key hint to
the attribute name. For example, RequestorPersonId(SourceSystemId). This
attribute is not mandatory.

AssignedByPersonId *1 * derived as Organization Unique ID that identifies the person assigning the goal. If supplying user keys, then
Owner for Organization use the AssignedByPersonNumber attribute.
Goals and not displayed This attribute also supports the integration key types. If you supplied a source key
in other scenarios for the person, then supply the same value here and append the source key hint to
the attribute name. For example AssignedByPersonId(SourceSystemId).

GoalSourceCode * Source The source of the goal assignment.

Load Worker Goals / Load Template Goals scenario:
Supply HR.
Load Organization Goals scenario:
Supply ORG_OWNER.
This attribute is validated using the lookup HRG_GOAL_ASGN_SOURCE_TYPE.

MeasureCalcRuleCode Calculation Rule The calculation rule for aggregating measurements. This attribute is validated
using the lookup HRG_MEASURE_CALC_RULE.
The default rule SUM is applied if no value is specified.
*1
ReferenceContentItemId (not displayed) Holds a reference to a Library Goal (which is loaded as a Content Item). The

6 | LOADING GOAL DATA USING HCM DATA LOADER

HCM Data Loader User Interface
Functional Description
Attribute Prompt

items must have already been loaded. If supplying user keys, then use the
ReferenceContentItemName attribute to pass the goal name of the Library Goal.
This attribute also supports the integration key types. If you supplied a source key
for the ContentItem, then supply the same value here and append the source key
hint to the attribute name. For example:
ReferenceContentItemId(SourceSystemId).

ReferenceGoalId (not displayed) Used in the Load Worker Goals scenario only.
If a worker goal is created from a shared goal or published organization goal, then
supply a unique ID to identify the referenced goal.
In Release 11, user keys are not supported. You need to supply a different key
type to identify uniquely the referenced goal. For example:
ReferenceGoaldId(SourceSystemId).

PublishDate (not displayed) Used in the Load Organization Goals scenario only.
The goal published date.

LevelCode Level The level code of the goal. This attribute is validated using the lookup
HRG_GOAL_MEASUREMENT_LEVEL.

CategoryCode Category Administrator-defined category for a goal.

Performance Goals
This attribute is validated using the lookup HRG_PERF_GOAL_CATEGORY.
Development Goals
This attribute is validated using the lookup HRG_DEV_GOAL_CATEGORY.
Supply the lookup_code and not the lookup meaning for this attribute. The lookup
meaning is not currently supported for this attribute.

IncludeInPerfdocFlag Enable Inclusion into Determines whether the goal must be included in performance documents of the
Performance Document worker. Accepts values Y, N, or null. Null is considered as N.

AllowKeyAttrUpdateFlag (not displayed) Determines whether the worker can update key attributes of the goal. Accepts
values Y, N, or null. Null value defaults to Y.

GoalUrl Related Link A URL resource associated with the goal.

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

WorkerPersonNumber *Person Number Person number of the person the goal is for.

WorkerAssignmentNu *Assignment Number Assignment number of the assignment the goal is for.
mber

OrganizationName Department The name of the organization this goal is for.

RequestorPersonNum (not displayed) Person number of the person who requested the goal.
ber

AssignedByPersonNu * derived as Organization Person number of the person who assigned the goal.
mber Owner for Organization
Goals and not displayed in
other scenarios

ReferenceContentItem (not displayed) The name of the referenced goal library goal.
Name

The value supplied will derive the value seen in the field specified in the User Interface Prompt.
*1
The foreign object references support use of all four key types: Oracle surrogate ID, Oracle GUID, source key, and user key.

7 | LOADING GOAL DATA USING HCM DATA LOADER

Figure 1: Goal (Goal Details)
Navigation: Manage Goal Plans – Goal Details
Navigation for other goal types:
 Administer Goals - Goal Details
 My Organization Goals - Goal Details
 Goals - Goal Details
 Career Development – Goal Details

Goal Dat File Examples

In Release 11, user keys are not supported for the Goal object. You must supply a source key to provide a unique
reference for the goal record.

Creating a Worker Goal

[Link]

This file creates an active performance goal for a worker. The PersonId and AssignmentId attributes must
correspond to those of the worker. Alternatively, supply the user key attributes WorkerPersonNumber and
WorkerAssignmentNumber.

The AssignedByPersonId attribute must correspond to the HR specialist creating the goal. Alternatively, the user key
attribute AssignedByPersonNumber can be used.

For performance goals, GoalPlanGoal entry must also be part of the .dat file. For development goals, GoalPlanGoal
entry must not be specified.

8 | LOADING GOAL DATA USING HCM DATA LOADER

Creating a Worker Goal Against a Library Goal

[Link]

This file creates an active performance goal against a library goal for a worker. Currently HCM Data Loader does not
default the attributes from the library goal. You must supply these values for the worker goal.

Creating an Organization Goal

[Link]

This file creates an organization goal for a line manager belonging to the organization Vision Corporation Enterprise.

The AssignedByPersonId attribute must correspond to the line manager who owns the organization goal.
Alternatively use the user key attribute AssignedByPersonNumber. If you want to publish the organization goal
while loading, set the PublishedFlag attribute to Y.

Creating a Template Goal to Include in a Goal Plan

Refer to the sample METADATA and MERGE lines in the Loading Goal Plan, Goal Plan Goal section.

Goal Action
The Goal Action component holds details of tasks defined for the goal.

The discriminator GoalAction is used to load goal task records using HCM Data Loader. The following GoalAction
attributes are commonly supplied when loading a new goal task.

9 | LOADING GOAL DATA USING HCM DATA LOADER

GOAL ACTION ATTRIBUTES

HCM Data Loader

User Interface Prompt Functional Description
Attribute

SourceSystemId / * (not displayed) You must provide a unique reference for the record being created. In Release 11,
SourceSystemOwner user keys are not supported for this object. You must supply a source key to
provide a unique reference for the goal action record.
*1
GoalId * (not displayed) You must provide a unique reference for the goal this action is for. In Release 9,
user keys are not supported for this reference. You must supply the source key
used for the goal record. When supplying source key values remember to append
the source key hint to the attribute name. For example: GoalId(SourceSystemId).

ActionName * Name Name of the goal task.

ActionTypeCode * Type The type of goal task. This attribute is validated using the lookup
HRG_GOAL_TASK_TYPE.

PriorityCode Priority The priority of the goal task. This attribute is validated using the lookup
HRG_PRIORITY.

StartDate Start Date The start date of the goal task.

TargetCompletionDate Target Completion Date The target date to achieve the goal task.

PercentCompleteCode Completion Percentage Goal completion percentage code. This attribute is validated using the lookup
HRG_PERCENT_COMPLETE.

StatusCode Status The action status. This attribute is validated using the lookup
HRG_GOAL_TASK_STATUS.

ActionUrl Related Link URL to launch a page related to the goal task.

Comments Comments Comments related to the task progress.

Figure 2: Goal Action (Goal Details)

Navigation: Goal Details - Tasks

10 | LOADING GOAL DATA USING HCM DATA LOADER

Goal Dat File Examples

In Release 11, user keys are not supported for the GoalAction object. You must supply a source key to provide a
unique reference for the goal action record.

Creating a Goal Action (Task) Record

[Link]

This file creates a worker goal with an action (task). While creating a performance goal, you must provide a goal
plan goal.

Goal Plan Goal

The Goal Plan Goal component holds details of relationships between goals and goal plans.

The discriminator GoalPlanGoal is used to load goal plan records using HCM Data Loader. The following
GoalPlanGoal attributes are commonly supplied when loading a new goal plan goal.

The goal plan goal component is mandatory while creating performance goals. GoalPlanGoal records can be
passed through HCM Data Loader to associate a Worker or Organization goal to goal plans that do not have
autoassociation enabled or to update or delete existing records. This component is not required for developmental
goals and must not be provided.

GOAL PLAN GOAL ATTRIBUTES

HCM Data Loader

User Interface Prompt Functional Description
Attribute

GoalId *1 * (not displayed) You must provide a unique reference for the goal this plan goal is for. In Release 11,
user keys are not supported for this reference. You must supply the source key used
for the goal record. When supplying source key values remember to append the
source key hint to the attribute name. For example: GoalId(SourceSystemId).

PriorityCode Priority The priority of the goal. This attribute is validated using the lookup HRG_PRIORITY.

11 | LOADING GOAL DATA USING HCM DATA LOADER

HCM Data Loader
User Interface Prompt Functional Description
Attribute

Weighting Weight The weight or importance of a goal relative to other goals in the same goal plan.
Expressed as a percentage. Mandatory if the goal plan enforces the 100% sum of
weights rule.

GoalPlanId *1 * Goal Plan Name The unique reference to the goal plan this goal is associated with. If using user keys,
* Start Date then supply the user key attributes GoalPlanName, GoalPlanStartDate, and
GoalPlanEndDate.
* End Date
This attribute also supports the integration key types. If you supplied a source key for
the Goal Plan, then supply the same value here and append the source key hint to
the attribute name. For example: GoalPlanId(SourceSystemId).

GoalPlanSetExternalld Shown within brackets in the The unique reference to the goal plan set associated with the goal plan that includes
“Goal Plan” section if a goal the goal.
plan is included in a goal
plan set.

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalPlanName * Goal Plan Name The name of the goal plan.

GoalPlanStartDate * Start Date The start date of the goal plan.

GoalPlanEndDate * End Date The end date of the goal plan.

The value supplied will derive the value seen in the field specified in the User Interface Prompt.
*1
The foreign object references support use of all four key types: Oracle Fusion surrogate ID, Oracle Fusion GUID, source key, and
user key.

Figure 3: Goal Plan Goal

Navigation: My Goals

Goal Dat File Examples

In Release 11, user keys are not supported for the GoalPlanGoal object. You must supply a source key to provide a
unique reference for the goal plan goal record.

12 | LOADING GOAL DATA USING HCM DATA LOADER

Creating a Goal Plan Goal Record
[Link]

This file creates a worker goal with a plan goal.

Goal Target Outcome

The Goal Target Outcome component holds desired target outcomes for the goal.

The discriminator GoalTargetOutcome is used to load target outcome records using HCM Data Loader. The
following GoalTargetOutcome attributes are commonly supplied when loading a new goal.

GOAL TARGET OUTCOME ATTRIBUTES

HCM Data Loader User Interface

Functional Description
Attribute Prompt

GoalId *1 * (not displayed) You must provide a unique reference for the goal this target outcome is for. In
Release 11, user keys are not supported for this reference. You must supply the
source key used for the goal record. When supplying source key values remember to
append the source key hint to the attribute name. For example:
GoalId(SourceSystemId).

ContentItemId *1 * Content Item Type The unique reference to the content item for this target outcome. If using user keys,
* Content Item Name then supply the user key attributes ContentItemName and
ContentTypeContextName.
This attribute also supports the integration key types. If you supplied a source key for
the Content Item, then supply the same value here and append the source key hint
to the attribute name. For example: ContentId(SourceSystemId).

Comments Comments Comments for this target outcome entry.

TargetRatingLevelId *1 Target Proficiency Level The first target rating level associated with this target outcome. If using user keys,
then supply the user key attributes ContentItemName, ContentTypeContextName,
and TargetRatingLevelCode.
(Used only for
Competencies and This attribute also supports the integration key types. If you supplied a source key for
Languages) the rating level, then supply the same value here and append the source key hint to
the attribute name. For example, TargetRatingLevelId(SourceSystemId).

TargetRatingLevelId2 *1 Target Proficiency Level The second target rating level associated with this target outcome. If using user
(Used only for Languages) keys, then supply the user key attributes ContentItemName,
ContentTypeContextName, and TargetRatingLevelCode2.
This attribute also supports the integration key types. If you supplied a source key for
the rating level, then supply the same value here and append the source key hint to

13 | LOADING GOAL DATA USING HCM DATA LOADER

HCM Data Loader User Interface
Functional Description
Attribute Prompt

the attribute name. For example: TargetRatingLevelId2(SourceSystemId).

*1
TargetRatingLevelId3 Target Proficiency Level The third target rating level associated with this target outcome. If using user keys,
(Used only for Languages) then supply the user key attributes ContentItemName, ContentTypeContextName,
and TargetRatingLevelCode3.
This attribute also supports the integration key types. If you supplied a source key for
the rating level, then supply the same value here and append the source key hint to
the attribute name. For example: TargetRatingLevelId3(SourceSystemId).
*1
ApprovedRatingId Manager Rating (Used only The manager-approved rating level associated with this target outcome. If using user
for Competencies and keys, then supply the user key attributes ContentItemName,
Languages) ContentTypeContextName, and ApprovedRatingCode.
This attribute also supports the integration key types. If you supplied a source key for
the rating level, then supply the same value here and append the source key hint to
the attribute name. For example: ApprovedRatingId(SourceSystemId).

ContentSourceCode Source The source of the content referred to in the target outcome. This attribute is validated
using the lookup HRG_TARGET_OUTCOME_SOURCE.

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

ContentItemName * Content Item Name The content item name.

ContentTypeContextNa * Content Item Type The content type context name.

TargetRatingLevelCode Target Proficiency Level The code for the first target rating level.
Reading – for Languages

TargetRatingLevelCode2 Writing – for Languages The code for the second target rating level.

TargetRatingLevelCode3 Speaking – for Languages The code for the third target rating level.

ApprovedRatingCode Manager Rating The code for the manager-approved rating.

14 | LOADING GOAL DATA USING HCM DATA LOADER

Figure 4: Goal Target Outcome (Goal Details)
Navigation: Goal Details - Target Outcomes

Goal Dat File Examples

In Release 11 user keys are not supported for the GoalTargetOutcome object. You must supply a source key to
provide a unique reference for the goal target outcome record.

Creating a Goal Target Outcome Record

[Link]

This file creates a worker goal with a target outcome. You must provide a goal plan goal attribute while creating a
performance goal.

Goal Measurement

15 | LOADING GOAL DATA USING HCM DATA LOADER

The Goal Measurement component holds measurements for the goal.

The discriminator GoalMeasurement is used to load goal measurement records using HCM Data Loader. The
following GoalMeasurement attributes are commonly supplied when loading a new goal.

GOAL MEASUREMENT ATTRIBUTES

HCM Data Loader User Interface

Functional Description
Attribute Prompt

GoalId *1 * (not displayed) You must provide a unique reference for the goal this goal measurement is for. In
Release 11, user keys are not supported for this reference. You must supply the
source key used for the goal record. When supplying source key values, remember
to append the source key hint to the attribute name. For example:
GoalId(SourceSystemId).

MeasurementName * Name The name of the measurement.

MeasureTypeCode *Quantitative or The type of the measurement, which can be either quantitative or qualitative. This
Qualitative (not attribute is validated using the lookup HRG_GOAL_MEASUREMENT_TYPE.
displayed )

UomCode Unit of Measurement The unit of measurement. This attribute is validated using the lookup
HRG_GOAL_QUANTITATIVE_UOM.

TargetType Target Type The target type of the measurement. This attribute is validated using the lookup
HRG_GOAL_QUANT_MEASURE_TYPE.

TargetValue Target Value The target value of the measurement.

TargetPercentage Target Percentage The target percentage of the measurement.

StartDate Start Date The start date of the measurement.

EndDate End Date The end date of the measurement.

MinTarget Min Target The minimal target value of the measurement.

MaxTarget Max Target The maximum target value of the measurement.

DisplaySequence Sequence Number The display sequence of the measurement as seen in the user interface.

Comments Measure-specific Comments related to the measurement.

Comments

AchievedWeight Achieved Weight The achieved weight of the measurement.

ActualValue Actual Value The actual value of the measurement.

16 | LOADING GOAL DATA USING HCM DATA LOADER

Figure 5: Goal Measurement (Goal Details)
Navigation: Goal Details - Measurements

Goal Dat File Examples

In Release 11, user keys are not supported for the GoalMeasurement object. You must supply a source key to
provide a unique reference for the goal measurement record.

Creating a Goal Measurement Record

[Link]

This file creates a worker goal with a goal measurement. You must provide a goal plan goal attribute while creating
a performance goal.

17 | LOADING GOAL DATA USING HCM DATA LOADER

Goal Access
The Goal Access component holds references to workers the goal is shared with.

The discriminator GoalAccess is used to load goal-sharing records using HCM Data Loader. The following
GoalAccess attributes are commonly supplied when loading a new goal sharing record.

GOAL ACCESS ATTRIBUTES

HCM Data Loader

User Interface Prompt Functional Description
Attribute

GoalId *1 * (not displayed) You must provide a unique reference for the goal this goal access is for. In Release
11, user keys are not supported for this reference. You must supply the source key
used for the goal record. When supplying source key values, remember to append
the source key hint to the attribute name. For example: GoalId(SourceSystemId).

PersonId *1 * Name You must provide a unique reference to the person that the goal is shared with. If
supplying user keys, then use the GoalAccessPersonNumber attribute. This
attribute also supports the integration key types. If you supplied a source key for the
person, then supply the same value here and append the source key hint to the
attribute name. For example: PersonId(SourceSystemId).

GoalActionAccessFlag Share tasks The flag that indicates whether the goal tasks must be accessible by the referenced
person.

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalAccessPersonNu Name The number of the person the goal is shared with.
mber

Figure 6: Goal Access

Navigation: My Goals – Shared With List

18 | LOADING GOAL DATA USING HCM DATA LOADER

Goal Dat File Examples

In Release 11, user keys are not supported for the GoalAccess object. You must supply a source key to provide a
unique reference for the goal access record.

Creating a Goal Access Record

[Link]

This file creates a worker goal with a goal access record to share the goal (along with the corresponding task) with
another worker. You must provide a goal plan goal attribute while creating a performance goal.

Goal Alignment
The Goal Alignment component holds a reference to a goal with which the goal is aligned.

The discriminator GoalAlignment is used to load goal access alignment using HCM Data Loader. The following
GoalAlignment attributes are commonly supplied when loading a new goal alignment.

GOAL ALIGNMENT ATTRIBUTES

HCM Data Loader

User Interface Prompt Functional Description
Attribute

GoalId *1 * (not displayed) You must provide a unique reference for the goal this goal alignment is for. In
Release 11, user keys are not supported for this reference. You must supply the
source key used for the goal record. When supplying source key values, remember
to append the source key hint to the attribute name. For example:
GoalId(SourceSystemId).

AlignedGoalId *1 * Aligned to Goal You must provide a unique reference for the alignment goal. In Release 11, user
keys are not supported for this reference. You must supply the source key used for
the goal record. When supplying source key values, remember to append the
source key hint to the attribute name. For example:
AlignedGoalId(SourceSystemId).

19 | LOADING GOAL DATA USING HCM DATA LOADER

Figure 7: Goal Alignment
Navigation: My Goals - Goal Alignment

Goal Dat File Examples

In Release 11, user keys are not supported for the GoalAlignment object. You must supply a source key to provide a
unique reference for the goal alignment record.

Creating a Goal Alignment record

[Link]

This file creates a worker goal with an alignment record to align the goal with the organization goal.

Note: The organization goal must already exist in the Oracle HCM Cloud before a goal alignment can be supplied to
reference it.

Goal Errors
You may experience errors while loading goals if the data is not provided as expected. Some of the more commonly
occurring errors are:

20 | LOADING GOAL DATA USING HCM DATA LOADER

Goal

Error Resolution

The assigned by person ID does not Ensure that the value passed for the AssignedByPersonId attribute is valid.
exist.

The requester person ID does not exist. Ensure that the value passed for the RequestorPersonId attribute is valid.

The goal does not exist in the goal Ensure that the value passed for the ReferenceContentItemId attribute is valid. Also, note that
library. ReferenceGoalId must not be passed when ReferenceContentItemId is passed.

The reference goal does not exist. Ensure that the value passed for the ReferenceGoalId attribute is valid. Also, note that
ReferenceContentItemId must not be passed when ReferenceGoalId is passed.

The assignment does not exist. Ensure that the value passed for the AssignmentId attribute is valid.

Development goals and personal goals IncludeInPerfdocFlag must be set to Y for Performance Goals only.
cannot be included in performance
documents.

Development goals and personal goals While creating Organization goals, GoalTypeCode must be set to PERFORMANCE or null.
cannot be created as organization
goals.

The goal cannot be published because The PublishedFlag attribute can be set to Y for Organization goals only.
it is not an organization goal.

Development goals or personal goals GoalAlignment records can be passed in the [Link] file for Performance goals only.
cannot be aligned with other goals.

This action cannot be performed Ensure that the profile option HRG_ENABLE_PERFORMANCE_GOAL is set to Y to enable
because the use of the Performance creation of Performance goals.
goal type is not enabled.

No actions can be performed on Ensure that the profile option HRG_ENABLE_DEVELOPMENT_GOAL is set to Y to enable
development goals because the use of creation of Development goals.
development goals is not enabled.

The target completion date must be Ensure that the TargetCompletionDate on the goal is later than or equal to the StartDate on the
later or equal to the start date. goal. Also, ensure that the ActualCompletionDate on the goal is later than or equal to the Start
Date.

Failed to validate a row with key … in Ensure that the GoalSourceCode is being passed as Organization owner while creating
GoalEO” error while creating an Organization goals.
Organization goal.

You must provide a value for the person The PersonId column on the goal is mandatory for Worker goals and Template goals.
ID.

The person ID does not match the Ensure that the PersonId and AssignmentId values on the goal are valid together.
assignment ID. Enter a new person ID
or assignment ID and try again.

An assignment ID or organization ID is AssignmentId is mandatory for Worker goals and Template goals. OrganizationId is mandatory
required to create a performance goal. for Organization goals.

A value for either the assignment ID or AssignmentId is mandatory for Worker goals and Template goals. OrganizationId is mandatory
organization ID must be entered, not for Organization goals. Both attributes cannot be populated for the same goal.
both.

The actual completion date must be The ActualCompletionDate cannot be a future date. It must be earlier than or equal to the current
earlier than or equal to {TODAY’S date.
DATE}.

You cannot save this goal until it is Goal Plan association with the goal is required. Add goal plan goal entry to the [Link] file.

21 | LOADING GOAL DATA USING HCM DATA LOADER

associated with a goal plan.

GoalAction:

Error Resolution

Date error while loading GoalAction Ensure that the TargetCompletionDate on the goal action is later than or equal to the StartDate
record. on the goal action.

The goal task start date and end dates As the message states, the goal task start date and end dates must be later than or equal to the
must be later than or equal to the goal goal start date and earlier than or equal to the goal target completion date.
start date and earlier than or equal to
the goal target completion date.

Goal tasks cannot be created because Enable goal tasks by setting the profile option HRG_ENABLE_TASK.
the use of goal tasks is not enabled.

GoalPlanGoal:

Error Resolution

The same goal type must be used for Ensure that the GoalPlanId specified on the GoalPlanGoal row is of the same type (Performance
both the goal and the goal plan. or Development) as the goal.

Goal Weights cannot be assigned The weighting attribute cannot be populated on the GoalPlanGoal record unless weights are
because the use of goal weighting is not enabled for the Goal Plan.
enabled.

The goal cannot be assigned because it Ensure that the goal plan is assigned to the worker before creating a GoalPlanGoal record to
belongs to a goal plan that is not assign the goal to the goal plan.
assigned to the worker.

This action cannot be performed Enable Performance Goal Plans by setting the profile option HRG_USE_PERF_GOAL_PLANS.
because the use of performance goal
plans is not enabled.

This action cannot be performed Enable Development Goal Plans by setting the profile option HRG_USE_DEV_GOAL_PLANS.
because the use of development goal
plans is not enabled.

GoalTargetOutcome:

Error Resolution

The content item does not exist. Ensure that the value passed for the ContentItemId is valid.

Goal target outcomes cannot be Enable goal target outcomes by setting the profile option HRG_ENABLE_OUTCOMES.
created because the use of goal target
outcomes is not enabled.

GoalMeasurement:

Error Resolution

The measurement end date must be Ensure that the EndDate on the measurement is later than or equal to the StartDate on the
later than or equal to measurement start measurement.
date.

22 | LOADING GOAL DATA USING HCM DATA LOADER

A record with value The measurement names must be unique for a goal.
{MeasurementName} already exists.
Enter a unique value.

GoalAccess:

Error Resolution

The goals cannot be shared because Ensure that the value passed for the PersonId attribute is valid.
the person ID of a person with whom
the goals are shared does not exist.
Enter another person ID and try again.

The goal is already shared with A goal can be shared with a person once only. Check the PersonId attribute and ensure that the
{PERSON _NAME}. goal is not already shared with that person.

Goals cannot be shared because the Enable shared goals by setting the profile option HRG_ENABLE_GRANT_ACCESS.
use of shared goals is not enabled.

GoalAlignment:

Error Resolution

You cannot align the goal A goal can be aligned once only.
{SOURCE_GOAL} because it is already
aligned to the goal {ALIGNED_GOAL}.

The goal to which you are aligning the Ensure that the value passed for AlignedGoalId column is valid.
performance goal does not exist.

Development goals or personal goals Only performance goals can be aligned with other goals.
cannot be aligned with other goals.

Goals cannot be aligned because the Enable alignment of goals by setting the profile option HRG_ENABLE_GOAL_ALIGN.
use of alignment goals is not enabled.

You cannot align the goal to the Ensure that there is no cyclic alignment between goals.
selected goal because the selected goal
is aligned to other goals in a hierarchy
that is aligned to the original goal.

The goal cannot be aligned because the Ensure that the goal to which the current goal is being aligned to is not canceled.
goal to which it is being aligned has the
status Canceled.

Deletion Support for Goal

You can delete goals using HCM Data Loader.

You must take care when using HCM Data Loader to delete records, as deleted records cannot be recovered. Do
not supply DELETE instructions in the same file as MERGE instructions.

Use Case: Delete Goals and Their Child Records

When we delete a goal record using HCM Data Loader, the following child records are automatically deleted along
with the parent record:

23 | LOADING GOAL DATA USING HCM DATA LOADER

 GoalAccess
 GoalAction
 GoalAlignment, where GoalId = current GoalId
 GoalAlignment, where AlignedGoalId = current GoalId
 GoalTargetOutcome
 GoalPlanGoal

Note: GoalMeasurement records are not automatically deleted when the parent goal is deleted using HCM Data
Loader. You must delete the GoalMeasurement records explicitly before deleting the parent goal.

Other child records can also be individually deleted using HCM Data Loader if needed.

Deleting Goal Dat File Examples

In Release 11, user keys are not supported for Goal or its child components. You must supply a source key to
provide a unique reference for the same.

Deleting a Worker Goal and Its Child Records

Following are sample METADATA and DELETE lines to delete the worker goal created in Creating a Worker Goal
on page 8, along with its child records.

Note: GoalMeasurement records are not automatically deleted when the parent goal is deleted using HCM Data
Loader. You need to explicitly pass a DELETE line for the same in the [Link] file.

[Link]

This file deletes a measurement record.

[Link]

This file deletes a goal and its other child records.

24 | LOADING GOAL DATA USING HCM DATA LOADER

Goal Plan
Goal plans are used for mass assigning sets of goals to employee populations. Employee populations can be
defined using eligibility profiles or by selecting manager hierarchies; specific employees can be exempted from the
assignment. Employees get copies of goals in the goal plan during the assignment process. Goal plans can also be
created or assigned to workers or organizations without goals.

For more information on goal plans, see the help topic Goal Plans: Explained in Oracle Applications Help at
[Link]

Considerations and Prerequisites for Goal Plan

Prerequisites for loading goal plan setup objects are listed in the section Supported Business Scenarios above.

The load process for Goal Plan loads goal plan objects but it does not run the actual assignment of the goal plans to
employees. The latter is done either in the application by HR or administrators when they schedule execution of goal
plan assignments using the Manage Goal Plans task or via HCM Data Loader using the GoalPlanAssignment
component of the GoalPlan object.

Loading Goal Plan

Goal Plan data must be supplied in the [Link] file for processing by HCM Data Loader.

GOAL PLAN HIERARCHY

Component Functional Description Discriminator

Goal Plan Details of goal plans. GoalPlan

Goal Plan Goal Details of template goals included in the goal plan. GoalPlanGoal

Goal Plan Details of document types associated with the goal plan. GoalPlanDocTypes
Document Type

Mass Request Details of goal plan generation requests submitted by HR or an administrator. This MassRequest
component is mandatory while loading the full hierarchy.

Eligibility Profile Details of eligibility profiles attached to the goal plan. EligibilityProfileObject
Object

Mass Request Details or organizations associated with the goal plan. MassRequestAssignment
Assignment

Mass Request Details of workers and managers included in the goal plan. MassRequestHierarchy
Hierarchy

Mass Request Details of workers exempted from the goal plan. MassRequestExemption
Exemption

Goal Plan Details of worker or organizational assignments associated with the goal plan. GoalPlanAssignment
Assignment

Goal Plan

25 | LOADING GOAL DATA USING HCM DATA LOADER

The Goal Plan component holds information about the goal plan.

The discriminator GoalPlan is used to load goal plan records using HCM Data Loader. The following GoalPlan
attributes are commonly supplied when loading a new goal plan.

GOAL PLAN ATTRIBUTES

HCM Data Loader User Interface

Functional Description
Attribute Prompt

SourceSystemId / * External ID You must provide a unique reference for the record being created. Supply either a
SourceSystemOwner source key or the user key attribute GoalPlanExternalId.

GoalPlanName * Goal Plan Name The name of the goal plan.

StartDate *Start Date The start date of the goal plan.

EndDate *End Date The end date of the goal plan.

IncludeInPerfdocFlag *Include in The flag that determines whether employee goals associated with this goal plan
Performance Document must be included in the employee performance document. The GoalPlanDocTypes
component is required when this flag is set to Y.

GoalPlanTypeCode *Type This attribute is validated using the lookup HRG_GOAL_OBJECT_TYPE.

GoalPlanActiveFlag *Status This attribute is validated using the lookup ACTIVE_INACTIVE.

EnableWeightingFlag Enable Weight The flag that determines whether the weight feature must be enabled for goals
associated with this goal plan.

EnforceGoalWeightFlag Enforce Sum of Goal The flag that determines whether the sum of goal weights associated with this goal
Weights to 100% plan must be validated to be equal to 100%.

GoalAccessLevelCode *Allow Updates to This attribute is validated using the lookup HRG_GOAL_ACCESS_LEVELS.
Goals By

GoalSubTypeCode Subtype This attribute is validated using the lookup. HRG_SUB_TYPE_CODE.

ReqSubmittedByPersonId *1 *(not displayed) Provide a unique reference to the person who would be creating the goal plan. If
using user keys, then supply the user key attribute
ReqSubmittedByPersonNumber.
This attribute also supports the integration key types. If you supplied a source key
for the referenced person, then supply the same value here and append the
source key hint to the attribute name. For example:
ReqSubmittedByPersonId(SourceSystemId).
This attribute is mandatory while creating new goal plans if the MassRequest
component is not being passed in the [Link] file.

RequestSubmissionDate *(not displayed) Provide the date when HR is creating this goal plan. This attribute is mandatory
while creating new goal plans if the MassRequest component is not being passed
in the [Link] file.

ReviewPeriodId *Review Period Name A unique reference to a review period.

User key attributes that are only required if no other key type is supplied to uniquely identify the object they reference.

ReqSubmittedByPers *(not displayed) The person number of the person creating the goal plan.
onNumber

GoalPlanExternalId * External ID A unique reference to the plan in an external system.

ReviewPeriodName *Review Period Name A unique reference to a review period.

26 | LOADING GOAL DATA USING HCM DATA LOADER

Figure 8: Goal Plan (Manage Goal Plans)
Navigation: Manage Goal Plans - Goal Plan Details

Goal Plan Dat File Examples

Creating a Goal Plan

Here are sample METADATA and MERGE lines to load a goal plan header record without a Mass Request
component in the [Link] file. In this case, the template mass request record for the goal plan is created
automatically using the values passed for attributes ReqSubmittedByPersonId and RequestSubmissionDate. While
loading new goal plans, note that the components Mass Request Hierarchy, Mass Request Exemption, Mass
Request Assignment and Eligibility Profile Object cannot be present in the [Link] file without the parent Mass
Request component.

[Link]

MERGE|GoalPlan|GP_001_01|GP_001_01|Performance|A|Y|2015/01/01|2015/12/31|Y|HR
specialist and manager|N|8153756|2015/09/20|Default Review Period - Vision
Corporation Enterprise

Goal Plan Goal

The Goal Plan Goal component holds information about template goals included in the plan.

27 | LOADING GOAL DATA USING HCM DATA LOADER

The discriminator GoalPlanGoal is used to load goal plan goal records using HCM Data Loader. The following
GoalPlanGoal attributes are commonly supplied when loading a new goal plan goal record. Note that the template
goals (with GoalVersionTypeCode set to MASS_REQ and the PersonId and AssignmentId corresponding to those
of the HR creating the goal plan) must have been created already using [Link] file. Since a template goal cannot
be created without associating it with a goal plan, the goal plan goal record is also typically created using the same
[Link] file. See the Goal Dat File Examples section for sample METADATA and MERGE lines to create a
template goal and associate it with a goal plan.

GOAL PLAN GOAL ATTRIBUTES

HCM Data Loader User Interface

Functional Description
Attribute Prompt

SourceSystemId / * (not displayed) You must provide a unique reference for the record being created. In Release 11
SourceSystemOwner user keys are not supported for this object. You must supply a source key to provide
a unique reference for the goal plan goal record.

GoalPlanId *1 * (not displayed) You must provide a unique reference for the goal plan this record is for. If using user
keys, then supply the user key attribute GoalPlanExternalId.
This attribute also supports the integration key types. If you supplied a source key for
the goal plan, then supply the same value here and append the source key hint to
the attribute name. For example: GoalPlanId(SourceSystemId).

GoalId *1 *Goal Name Provide a unique reference for the goal. In Release 11 user keys are not supported
for this object. You must supply a source key to provide a unique reference for the
goal.

PriorityCode Priority The priority of the goal in the goal plan. This attribute is validated using the lookup
HRG_PRIORITY.

Weighting Weight The weight of the goal in the goal plan. The weight value must be between zero and
one hundred. The type of this attribute is NUMBER (5, 2) and so it also supports
decimals.

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalPlanExternalId External ID The external ID for the goal plan to which this goal plan goal belongs.

28 | LOADING GOAL DATA USING HCM DATA LOADER

Figure 9: Goal Plan Goal (Manage Goal Plans)
Navigation: Manage Goal Plans - Worker Assignment: Goals

Goal Dat File Examples

Loading a Template Goal in a Goal Plan

Following are sample METADATA and MERGE lines to create a template goal and include it in an existing goal
plan. Note that the goal plan referenced in the GoalPlanGoal record should have already been created before you
load template goals.

[Link]

This file creates a template goal.

MERGE|Goal|TemplateGoal_001_SSID|VISION|TemplateGoal_001|TemplateGoal_001|2015/
01/01|2015/12/31|8153756|EEEE8153756|0|Not started|HR
specialist|N|Y|Y|8153756|Mass request

29 | LOADING GOAL DATA USING HCM DATA LOADER

Goal Plan Document Type
The Goal Plan Document Type component holds information about document types associated with the goal plan.
This component is required if the value of the goal plan attribute IncludeInPerfDocFlag is Y.

The discriminator GoalPlanDocTypes is used to load goal plan document type records for a goal plan using HCM
Data Loader. The following GoalPlanDocTypes attributes are commonly supplied when loading a new goal plan.

HCM Data Loader Attribute User Interface Prompt Functional Description

SourceSystemId/SourceSystemOwner *(not displayed) You must provide a unique reference for the
record being created. You must supply a
source key to provide a unique reference for
the document type record.

GoalPlanId *1 *(not displayed) You must provide a unique reference for the
goal plan this record is for. If using user
keys, then supply the user key attribute:
GoalPlanExternalId
This attribute also supports the integration
key types. If you supplied a source key for
the goal plan, then supply the same value
here and append the source key hint to the
attribute name. For example:
GoalPlanId(SourceSystemId).

DocTypeId *Document Types Provide a unique reference to the document

type this record belongs to. If using user
keys, then supply the user key attribute
DocTypeName.

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalPlanExternalId External ID The external ID for the goal plan this goal plan goal belongs to.

DocTypeName *Document Types The document type name this record belongs to

Goal Plan Dat File Examples

Creating a Goal Plan with Goal Plan Document Types

This file creates a goal plan with IncludeInPerfdocFlag set to Y and also assigns a document type.

[Link]

30 | LOADING GOAL DATA USING HCM DATA LOADER

Mass Request
The Mass Request component holds attributes of the mass request object associated with the goal plan. It is
referenced by subcomponents that collectively define the employee population or organization to assign the goal
plan to. These subcomponents are listed in the Goal Plan Hierarchy table above. Every goal plan needs to be
associated with a mass request record having a RequestTypeCode of TEMPLATE, irrespective of the presence of
these subcomponents.

The discriminator MassRequest is used to load goal plan mass request records using HCM Data Loader.

Note: The MassRequest component is mandatory if the attributes ReqSubmittedByPersonId and

RequestSubmissionDate are not provided for the GoalPlan component while loading a new goal plan. If these
attributes are provided for the GoalPlan component, then the template mass request record for the goal plan is
created automatically using these values.

Customers must pass the MassRequest component explicitly if they want to associate a SourceSystemId to the
template mass request record, which they can use later for updating or deleting the subcomponents that define the
employee population or organization included in the goal plan.

While loading new goal plans, note that the components Mass Request Hierarchy, Mass Request Exemption, Mass
Request Assignment and Eligibility Profile Object cannot be present in the [Link] file without the parent Mass
Request component.

The following MassRequest attributes are commonly supplied when loading a new goal plan.

MASS REQUEST ATTRIBUTES

HCM Data Loader

User Interface Prompt Functional Description
Attribute

SourceSystemId / * (not displayed) You must provide a unique reference for the record being created. Supply either a
SourceSystemOwner source key or the user key attribute GoalPlanExternalId.

ReqSubmittedByPers * (not displayed) Provide a unique reference to the person who is creating the goal plan. If supplying
onId *1 user keys, then use the ReqSubmittedByPersonNumber attribute.
This attribute also supports the integration key types. If you supplied a source key for
the person, then supply the same value here and append the source key hint to the
attribute name. For example: ReqSubmittedByPersonId(SourceSystemId).

RequestSubmissionD (not displayed) Provide the date when HR is creating this goal plan. If this attribute is not passed, it
ate is defaulted to the current system date.

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalPlanExternalId (not displayed) The external ID for the goal plan to which this goal plan goal belongs.

ReqSubmittedByPers (not displayed) The number of the person who is creating the goal plan.
onNumber

The value supplied will derive the value seen in the field specified in the User Interface Prompt.

31 | LOADING GOAL DATA USING HCM DATA LOADER

*1
The foreign object references support use of all four key types: Oracle surrogate ID, Oracle GUID, source key, and user key.

Goal Plan Dat File Examples

Creating a Goal Plan with a MassRequest Component

[Link]

This file creates a goal plan with a mass request. Note that the attributes ReqSubmittedByPersonId and
RequestSubmissionDate are not supplied for the GoalPlan component in this case

Eligibility Profile Object

The Eligibility Profile Object component holds a reference to an eligibility profile object that defines selection criteria
for employees to assign the goal plan to.

The discriminator EligibilityProfileObject is used to load eligibility profile records for a goal plan using HCM Data
Loader. The following EligibilityProfileObject attributes are commonly supplied when loading a new goal plan.

ELIGIBILITY PROFILE OBJECT ATTRIBUTES

HCM Data Loader

User Interface Prompt Functional Description
Attribute

SourceSystemId / * (not displayed) You must provide a unique reference for the record being created. Supply either a
SourceSystemOwner source key or the user key attributes EligibilityProfileName andGoalPlanExternalId.

ObjectId *1 * (not displayed) Provide a unique reference to the mass request this record belongs to. If using user
keys, then supply the user key attribute GoalPlanExternalId.
This attribute also supports the integration key types, if you supplied a source key for
the mass request, then supply the same value here and append the source key hint
to the attribute name. For example: ObjectId(SourceSystemId).

EligibilityProfileName * Eligibility Profile The name of the eligibility profile.

RequiredFlag Required The flag that determines whether this eligibility profile is required.

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalPlanExternalId (not displayed) The external ID for the goal plan this eligibility profile object belongs to.

EligibilityProfileName Eligibility Profile The name of the eligibility profile.

The value supplied will derive the value seen in the field specified in the User Interface Prompt.

32 | LOADING GOAL DATA USING HCM DATA LOADER

*1
The foreign object references support use of all four key types: Oracle surrogate ID, Oracle GUID, source key, and user key.

Figure 10: Eligibility Profile Object (Manage Goal Plans)

Navigation: Manage Goal Plans - Worker Assignment: Eligibility Profile

Goal Plan Dat File Examples

Creating a Goal Plan with Eligibility Profile

[Link]

This file creates a goal plan with eligibility criteria for the mass request.

Associating Eligibility Profile with Existing Goal Plan

[Link]

This file creates the eligibility profile object for an existing goal plan and mass request.

METADATA|EligibilityProfileObject|GoalPlanExternalId|EligibilityProfileName|Requ
iredFlag

33 | LOADING GOAL DATA USING HCM DATA LOADER

MERGE|EligibilityProfileObject|GP_001_04|Age 22 and above|Y

Mass Request Assignment

The Mass Request Assignment component holds information about an organization to associate the goal plan with.
Note that the MassRequestAssignment component does not support selecting an organization owner for an
organization. Note that only one organization can be assigned to a goal plan.

The discriminator MassRequestAssignment is used to load mass request assignment records for a mass request
within a goal plan using HCM Data Loader. The following MassRequestAssignment attributes are commonly
supplied when loading a new goal plan.

MASS REQUEST ASSIGNMENT ATTRIBUTES

HCM Data Loader

User Interface Prompt Functional Description
Attribute

SourceSystemId / * (not displayed) You must provide a unique reference for the record being created. Supply either a
SourceSystemOwner source key or the user key attributes OrganizationName and GoalPlanExternalId.

OrganizationId *1 * Organization Name Provide a unique reference to the organization. If using user keys, then supply the
user key attribute OrganizationName.
Currently this attribute does not support the source key

MassRequestId *1 * (not displayed) Provide a unique reference to the mass request this record belongs to. If using user
keys, then supply the user key attribute GoalPlanExternalId.
This attribute also supports the integration key types. If you supplied a source key for
the mass request, then supply the same value here and append the source key hint
to the attribute name. For example: MassRequestId(SourceSystemId).

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalPlanExternalId (not displayed) The external ID for the goal plan to which this eligibility profile object belongs.

OrganizationName Organization Name The name of the organization.

Figure 11: Mass Request Assignment (Manage Goal Plans)

Navigation: Manage Goal Plans - Organization Assignment

Goal Plan Dat File Examples

Creating a Goal Plan with Mass Request Assignment Component

[Link]

34 | LOADING GOAL DATA USING HCM DATA LOADER

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

Associating Mass Request Assignment with Existing Goal Plan

[Link]

This file creates a mass request assignment for a goal plan and mass request that already exist. Note: user keys
can be used in this case.

Mass Request Hierarchy

The Mass Request Hierarchy component holds information about a manager hierarchy or specific employees
included in the goal plan.

The discriminator MassRequestHierarchy is used to load mass request hierarchy records for a goal plan using
HCM Data Loader. The following MassRequestHierarchy attributes are commonly supplied when loading a new
goal plan.

MASS REQUEST HIERARCHY ATTRIBUTES

HCM Data Loader

User Interface Prompt Functional Description
Attribute

MassRequestId *1 * (not displayed) Provide a unique reference to the mass request this record belongs to. If using
user keys, then supply the user key attribute GoalPlanExternalId.
This attribute also supports the integration key types. If you supplied a source key
for the mass request, then supply the same value here and append the source key
hint to the attribute name. For example: MassRequestId(SourceSystemId).

ManagerAssignmentId Job Provide a unique reference to the manager assignment (or the worker assignment
*1
if the Cascading Level is Self). If using user keys, then supply the user key
attribute ManagerAssignmentNumber.
This attribute also supports the integration key types. If you supplied a source key
for the manager (or worker) assignment, then supply the same value here and
append the source key hint to the attribute name. For example:

35 | LOADING GOAL DATA USING HCM DATA LOADER

HCM Data Loader
User Interface Prompt Functional Description
Attribute

ManagerAssignmentId(SourceSystemId).

ManagerId *1 Name Provide a unique reference to the manager (or the worker if the Cascading Level is
Self). If using user keys, then supply the user key attribute
ManagerAssignmentNumber.
This attribute also supports the integration key types. If you supplied a source key
for the manager (or worker), then supply the same value here and append the
source key hint to the attribute name. For example: ManagerId(SourceSystemId).

CascadingLevel Assignees Specific the type of hierarchy selection method. Provide one of the following
values (0,1, 999999,2 or 1000000):
0 - Self
1 - Direct reports
999999 - All reports
2 - Self and direct reports
1000000 - Self and all reports

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalPlanExternalId External ID The external ID for the goal plan this eligibility profile object belongs to.

ManagerAssignmentN Job The assignment number for the manager.

umber

Figure 12: Mass Request Hierarchy (Manage Goal Plans)

Navigation: Manage Goal Plans - Worker Assignment: Workers

Goal Plan Dat File Examples

Creating a Goal Plan with Mass Request Hierarchy Component

[Link]

This file creates a goal plan with a hierarchy for the mass request.

36 | LOADING GOAL DATA USING HCM DATA LOADER

Associating Mass Request Hierarchy with Existing Goal Plan

[Link]

This file creates a mass request hierarchy for a goal plan and mass request that already exist. Note: user keys can
be used in this case.

COMMENT Assigning Worker to Goal Plan GP_001_06

Mass Request Exemption

The Mass Request Exemption component holds references to employees exempted from the goal plan. This
component can only be passed for MassRequestHierarchy records where the CascadingLevel is not zero. For
example, when the cascading level is Direct reports, All reports, Self and direct reports, or Self and all reports.

The discriminator MassRequestExemption is used to load mass request exemption records for a goal plan using
HCM Data Loader. The following MassRequestExemption attributes are commonly supplied when loading a new
goal plan.

MASS REQUEST EXEMPTION ATTRIBUTES

HCM Data Loader

User Interface Prompt Functional Description
Attribute

SourceSystemId / * (not displayed) You must provide a unique reference for the record being created.
SourceSystemOwner

MassRequestHierarch *(not displayed) You must provide a unique reference for the mass request hierarchy this record is
yId *1 for. This attribute also supports the integration key types. If you supplied a source
key for the mass request hierarchy, then supply the same value here and append
the source key hint to the attribute name. For example:
MassRequestHierarchyId(SourceSystemId). If using user keys, then supply the user
key attributes GoalPlanExternalId and ManagerAssignmentNumber.

MassRequestId *1 (not displayed) Provide a unique reference for the mass request. If using user keys, then supply the

37 | LOADING GOAL DATA USING HCM DATA LOADER

HCM Data Loader
User Interface Prompt Functional Description
Attribute

user key attribute GoalPlanExternalId.

Note that the source key is not supported for this attribute currently.
Do not supply this attribute while loading a MassRequestExemption component
along with parent MassRequestHierarchy, MassRequest, and GoalPlan
components in the same [Link] file. The value for this column is
automatically derived in this case.
This column is mandatory while loading a MassRequestExemption component
separately after loading the parent GoalPlan, MassRequest and
MassRequestHierarchy components in a different [Link] file. Refer to the
sample MERGE lines given in this section.

PersonId *1 * Name Provide a unique reference to the person who needs to be exempted from the goal
plan. If using user keys, then supply the user key attribute
WorkerAssignmentNumber.
This attribute also supports the integration key types. If you supplied a source key
for the person, then supply the same value here and append the source key hint to
the attribute name. For example: PersonId(SourceSystemId).

AssignmentId *1 * Job Provide a unique reference to the assignment of the person who needs to be
exempted from the goal plan. If using user keys, then supply the user key attribute
WorkerAssignmentNumber.
This attribute also supports the integration key types. If you supplied a source key
for the assignment, then supply the same value here and append the source key
hint to the attribute name. For example: AssignmentId(SourceSystemId).

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalPlanExternalId (not displayed) The external ID for the goal plan to which this eligibility profile object belongs.

ManagerAssignmentN Job The assignment number for the manager.

umber

WorkerAssignmentNu Job (In the “Select or The assignment number for the worker.
mber deselect assignees” popup)

Figure 13: Mass Request Exemption (Manage Goal Plans)

Navigation: Manage Goal Plans - Worker Assignment: Workers (select a manager in Workers section) - Assignee Details

38 | LOADING GOAL DATA USING HCM DATA LOADER

Goal Plan Dat File Examples

Creating a Goal Plan with Mass Request Exemption Component

[Link]

This file creates a goal plan with a mass request exemption for the hierarchy

Note: Do not pass a value for the MassRequestId attribute in this case as the value is automatically derived.

Associating Mass Request Exemption with an Existing Goal Plan

[Link]

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

Note that the user keys ManagerAssignmentNumber and GoalPlanExternalId are not currently supported for the
attribute MassRequestHierarchyId while loading a MassRequestExemption record separately, and they cannot
identify the parent mass request hierarchy record in this case. We need to pass the source key for mass request
hierarchy MassRequestHierarchyId(SourceSystemId) instead, as shown below. Also, note that the attribute
MassRequestId is mandatory in this case and, since source key is not supported for this attribute, you need to pass
GoalPlanExternalId as shown below.

COMMENT Excluding another worker from Goal Plan GP_012_01

Goal Plan Assignment

39 | LOADING GOAL DATA USING HCM DATA LOADER

The Goal Plan Assignment component holds information about worker or organization assignments for the goal
plan.

The discriminator GoalPlanAssignment is used to load goal plan assignment records using HCM Data Loader. The
following GoalPlanAssignment attributes are commonly supplied when assigning a goal plan to a worker
population or organization.

GOAL PLAN ASSIGNMENT ATTRIBUTES

HCM Data Loader User Interface

Functional Description
Attribute Prompt

SourceSystemId / * (not displayed) You must provide a unique reference for the record being created. You must supply
SourceSystemOwner a source key to provide a unique reference for the goal plan assignment record.

GoalPlanId *1 * (not displayed) You must provide a unique reference for the goal plan this record is for. If using
user keys, then supply the user key attribute GoalPlanExternalId.
This attribute also supports the integration key types. If you supplied a source key
for the goal plan, then supply the same value here and append the source key hint
to the attribute name. For example: GoalPlanId(SourceSystemId).

GoalPlanStartDate * Start Date The start date of the goal plan. If this attribute is not passed, then it is the start date
of the Goal Plan by default.

GoalPlanEndDate * End Date The end date of the goal plan. If this attribute is not passed, then it is the end date
of the Goal Plan by default.

GoalPlanSetId*1 * (not displayed) You must provide a unique reference for the goal plan set this record is for. If using
user keys, then supply the user key attribute GoalPlanSetExternalId.
This attribute also supports the integration key types. If you supplied a source key
for the goal plan set, then supply the same value here and append the source key
hint to the attribute name. For example: GoalPlanSetId(SourceSystemId).

GoalPlanSetStartDate * Start Date The start date of the goal plan set. If this attribute is not passed, then it is the start
date of the Goal Plan Set by default.

GoalPlanSetEndDate * End Date The end date of the goal plan set. If this attribute is not passed, then it is the end
date of the Goal Plan Set by default.

PersonId *1 * Name Provide a unique reference to the person with whom the goal plan is being
associated. If supplying user keys, then use the WorkerAssignmentNumber
attribute. This attribute also supports the integration key types. If you supplied a
source key for the person, then supply the same value here and append the source
key hint to the attribute name. For example: PersonId(SourceSystemId).

AssignmentId *1 Job Provide a unique reference to the assignment. If using user keys, then supply the
user key attribute WorkerAssignmentNumber.
This attribute also supports the integration key types. If you supplied a source key
for the worker assignment, then supply the same value here and append the source
key hint to the attribute name. For example: AssignmentId(SourceSystemId).

OrganizationId * Department Used for the Organization Goal Plan scenario only.
Unique ID that identifies the organization this goal plan is for. If supplying user keys,
then use the OrganizationName attribute.
This attribute also supports the integration key types. If you supplied a source key
for the organization, then supply the same value here and append the source key
hint to the attribute name. For example: OrganizationId(SourceSystemId).

Weighting Weight The weight of the goal plan in the goal plan set. The weight value must be between
zero and one hundred. The type of this attribute is NUMBER (5, 2) and so it also
supports decimals.

40 | LOADING GOAL DATA USING HCM DATA LOADER

HCM Data Loader User Interface
Functional Description
Attribute Prompt

Status Status The Goal Plan Assignment status.

This attribute is validated using the lookup
HRG_GOAL_PLAN_SET_ASSGN_STATUS.

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalPlanExternalId External ID The external ID for the goal plan to which this goal plan assignment belongs.

GoalPlanSetExternalId Shown within brackets The external ID for the goal plan set to which this goal plan assignment belongs.
in the “Goal Plan”
section if a goal plan is
included in a goal plan
set.

WorkerAssignmentNumber Job Used for Worker Goal Plan assignment scenario.

Assignment number for the worker.

OrganizationName Department Used for the Organization Goal Plan assignment scenario only.

The name of the organization this goal plan assignment is for.

Figure 14: Assigned Worker Goal Plan (My Goals)

Navigation: My Goals

Goal Plan Dat File Examples

Creating a Goal Plan with Goal Plan Assignment Component for a Worker

41 | LOADING GOAL DATA USING HCM DATA LOADER

[Link]

This file creates a new goal plan and goal plan assignment for a worker.

Associating a Goal Plan Assignment with an Existing Goal Plan for a Worker
[Link]

This file creates a worker goal plan assignment for a goal plan that already exists. Note: user keys can be used in
this case.

Creating a Goal Plan with a Goal Plan Assignment Component for an Organization
[Link]

This file creates a new goal plan and goal plan assignment for an organization.

Associating a Goal Plan Assignment with an Existing Goal Plan for an Organization
[Link]

This file creates a worker goal plan assignment for a goal plan that already exists. Note: user keys can be used in
this case.

42 | LOADING GOAL DATA USING HCM DATA LOADER

Goal Plan Errors
You may experience errors while loading Goal Plan if the data is not provided as expected. Some of the more
commonly occurring errors are:

GoalPlan

Error Resolution

This action cannot be performed Ensure that the profile option HRG_USE_PERF_GOAL_PLANS is set if you are creating
because the use of performance goal performance goal plans.
plans is not enabled.

This action cannot be performed Ensure that the profile option HRG_USE_DEV_GOAL_PLANS is set if you are creating
because the use of development goal development goal plans.
plans is not enabled.

No actions can be performed on Ensure that the profile option HRG_ENABLE_DEVELOPMENT_GOAL is set if you are creating
development goals because the use of development goal plans.
development goals is not enabled.

This action cannot be performed Ensure that the profile option HRG_ENABLE_PERFORMANCE_GOAL is set if you are creating
because the use of the Performance development goal plans.
goal type is not enabled.

The goal plan end date must be later Ensure that the goal plan end date is later than or equal to the goal plan start date.
than or equal to the goal plan start date.

Unique key validation error. While loading goal plan records, ensure that the combination of GoalPlanName, StartDate, and
EndDate is unique. Also, ensure that the GoalPlanExternalId is unique.

An application error occurred: The attributes ReqSubmittedByPersonId and RequestSubmissionDate are mandatory when the
[Link]. goal plan record is loaded without the MassRequest component in the [Link] file. See the
sample MERGE line in the GoalPlan section.

GoalPlanGoal

Error Resolution

You cannot create a goal plan period for Ensure that the value passed for the GoalPlanId attribute is valid.
a goal plan that does not exist.

The goal does not exist. Ensure that the value passed for GoalId is valid. The GoalId must correspond to a template goal
(GoalVersionTypeCode = MASS_REQ). See the sample MERGE lines in the GoalPlanGoal
section.

The same goal type must be used for Ensure that the goal type on the template goal matches the goal plan type.
both the goal and the goal plan.

Goal Weights cannot be assigned The weighting attribute cannot be populated on the GoalPlanGoal record unless weights are
because the use of goal weighting is not enabled for the Goal Plan.
enabled.

This action cannot be performed Enable Performance Goal Plans by setting the profile option HRG_USE_PERF_GOAL_PLANS.
because the use of performance goal
plans is not enabled.

This action cannot be performed Enable Development Goal Plans by setting the profile option HRG_USE_DEV_GOAL_PLANS.
because the use of development goal
plans is not enabled.

43 | LOADING GOAL DATA USING HCM DATA LOADER

A parent for this record was not found. In Release 11, user keys are not supported for the GoalPlanGoal object. You must supply a
Use any of the four supported key- source key to provide a unique reference for the goal plan goal record.
resolution systems to supply a valid
parent reference.

MassRequest

Error Resolution

The requester ID does not exist. Ensure that the value passed for RequestSubmittedPersonId is valid.

EligibilityProfileObject

Error Resolution

You have selected the same eligibility An eligibility profile can only be assigned once to a goal plan.
profile more than once for the
performance template or period. Select
a unique eligibility profile.

MassRequestAssignment

Error Resolution

The same assignment was entered An organization can be included only once in a goal plan.
more than once.

MassRequestHierarchy

Error Resolution

The request cannot be completed Ensure that the value passed for the ManagerId column is valid.
because {PersonId} does not exist.

The same manager and cascading level A manager and cascading level combination can be included once only in a goal plan.
can only be entered once in this
request.

MassRequestExemption

Error Resolution

A parent for this record was not found. User keys are not supported for the MassRequestExemption component while loading
Use any of the four supported key- MassRequestExemption records separately. You must supply a source key to provide a unique
resolution systems to supply a valid reference for the mass request exemption record in this case. Also, note that the user key
parent reference. attributes ManagerAssignmentNumber and GoalPlanExternalId are not supported for the
MassRequestHierarchyId attribute while loading MassRequestExemption record separately. You
must pass a source key for mass request hierarchy while loading the mass request exemption
records separately. See the sample MERGE lines given in the MassRequestExemption section.

The record referenced by the foreign Do not pass the MassRequestId attribute while loading the MassRequestExemption component
key attribute MassRequestId was not along with parent MassRequestHierarchy, MassRequest, and GoalPlan components in the same
found. Either specify a valid foreign key [Link] file. The value for this column is automatically derived in this case.

44 | LOADING GOAL DATA USING HCM DATA LOADER

Error Resolution

or create the referenced record first. See the sample MERGE lines given in the MassRequestExemption section.

JBO-27014: Attribute MassRequestId in The attribute MassRequestId is mandatory while loading MassRequestExemption component
MassReqExemptionsEO is required. separately after loading the parent GoalPlan, MassRequest, and MassRequestHierarchy
components in a different [Link] file. Source keys are not supported for this attribute. You
must supply GoalPlanExternalId. See the sample MERGE lines given in the
MassRequestExemption section.

Deletion Support for Goal Plan

You can delete Goal Plan using HCM Data Loader.

You must take care when using HCM Data Loader to delete records, as deleted records cannot be recovered. Do
not supply DELETE instructions in the same file as MERGE instructions.

Use Case: Delete Goal Plans and Their Child Records.

When we delete a goal plan record using HCM Data Loader, the following child records are automatically deleted
along with the parent record:

 Template MassRequest
 MassRequestHierarchy
 MassRequestExemption
 EligibilityProfileObject
 MassRequestAssignment

Note: GoalPlanGoal records (which link the goal plan to template goals) and GoalPlanAssignment records are not
automatically deleted when the parent goal plan is deleted using HCM Data Loader. Delete the relevant
GoalPlanGoal and GoalPlanAssignment records explicitly before deleting the parent goal plan. Other child records
can also be individually deleted using HCM Data Loader if needed.

Deleting Goal Plan Dat File Examples

Deleting Goal Plan Goal Record That Links a Goal Plan with a Template Goal

Following are sample METADATA and MERGE lines to delete the goal plan goal record that links goal plan
GP_001_01 with template goal TemplateGoal_001 (SourceSystemId: TemplateGoal_001_SSID).

[Link]

This file deletes the goal plan goal created in the Creating a Goal Plan with a Goal section.

Deleting a Goal Plan Assignment That is Linked to a Goal Plan

[Link]

45 | LOADING GOAL DATA USING HCM DATA LOADER

This file deletes the goal plan assignment created in the Creating a Goal Plan with Goal Plan Assignment for a
Worker section.

Deleting Template Goal

Following are sample METADATA and MERGE lines to delete the template goal TemplateGoal_001
(SourceSystemId: TemplateGoal_001_SSID).

[Link]

Deleting Goal Plan Record and Its Other Child Records

Following are sample METADATA and DELETE lines to delete the goal plan GP_001_01 along with its other child
records.

[Link]

METADATA|GoalPlan|GoalPlanExternalId
DELETE|GoalPlan|GP_001_01

46 | LOADING GOAL DATA USING HCM DATA LOADER

Goal Plan Set
Goal plan sets are used for mass assigning related goal plans to employee populations. Employee populations can
be defined using eligibility profiles or by selecting manager hierarchies; specific employees can be excluded from
the assignment.

For more information on goal plan sets, see the help topic Goal Plan Sets: Explained in Oracle Applications Help at
[Link]

Considerations and Prerequisites for Goal Plan Set

Prerequisites for loading goal plan set objects are listed in the section Supported Business Scenarios above.

The load process for Goal Plan Set will load goal plan set objects but it will not run the actual assignment of the goal
plan sets to employees. The latter is done either in the application by HR or administrators when they schedule
execution of goal plan set assignments using Manage Goal Plan Sets task or via HCM Data Loader using the
GoalPlanAssignment component of the GoalPlan object.

Loading Goal Plan Set

Goal Plan Set data must be supplied in the [Link] file for processing by HCM Data Loader.

GOAL PLAN HIERARCHY

Component Functional Description Discriminator

Goal Plan Set Details of goal plan sets. GoalPlanSet

Goal Plan Set Plan Details of goal plans attached to a goal plan set. GoalPlanSetPlan

Mass Request Details of goal plan set generation request submitted by HR or administrator. This MassRequest
component is mandatory while loading the full hierarchy.

Eligibility Profile Details of eligibility profiles attached to a goal plan set. EligibilityProfileObject
Object

Mass Request Detail of workers and managers attached to a goal plan set. MassRequestHierarchy
Hierarchy

Mass Request Details of workers exempted from a goal plan set. MassRequestExemption
Exemption

Goal Plan Set

The Goal Plan Set component holds information about the goal plan set.

The discriminator GoalPlanSet is used to load goal plan set records using HCM Data Loader. The following
GoalPlanSet attributes are commonly supplied when loading a new goal plan set.

47 | LOADING GOAL DATA USING HCM DATA LOADER

GOAL PLAN SET ATTRIBUTES

HCM Data Loader User Interface

Functional Description
Attribute Prompt

SourceSystemId / * External ID You must provide a unique reference for the record being created. Supply either a
SourceSystemOwner source key or the user key attribute GoalPlanSetExternalId

GoalPlanSetExternalId *External ID A unique reference to the goal plan set in an external system.

GoalPlanSetName Goal Plan Set The name of the goal plan set.
Name

GoalPlanSetActiveFlag Status This attribute is validated using the lookup ACTIVE_INACTIVE.

Description Description Description of the goal plan set.

StartDate Start Date The start date of the goal plan set.

EndDate End Date The end date of the goal plan set.

ReqSubmittedByPersonId*1 *(not displayed) Provide a unique reference to the person creating the goal plan set. If using user
keys, then supply the user key attribute ReqSubmittedByPersonNumber.
This attribute also supports the integration key types. If you supplied a source key for
the referenced person, then supply the same value here and append the source key
hint to the attribute name. For example: ReqSubmittedByPersonId(SourceSystemId).
This attribute is mandatory while creating new goal plan sets if the MassRequest
component is not being passed in the [Link] file.

RequestSubmissionDate (not displayed) Provide the date when HR is creating this goal plan set. This attribute is mandatory
when creating new goal plan sets if the MassRequest component is not being
passed in the [Link] file.

ReviewPeriodId Review Period Provide a unique reference to an existing Review Period.

Name

Figure 15: Goal Plan Set (Manage Goal Plan Sets)

Navigation: Manage Goal Plan Sets - Goal Plan Set Details

48 | LOADING GOAL DATA USING HCM DATA LOADER

Goal Plan Set Dat File Examples

Creating a Goal Plan Set

These sample METADATA and MERGE lines load a goal plan set header record without a Mass Request
component in the [Link] file.

[Link]

This file creates a goal plan set without a mass request. In this case, the template mass request record for the goal
plan set is created automatically using the values passed for attributes ReqSubmittedByPersonId and
RequestSubmissionDate. While loading new goal plan sets, note that the components Mass Request Hierarchy,
Mass Request Exemption, and Eligibility Profile Object cannot be present in the [Link] file without the
parent Mass Request component.

Goal Plan Set Plan

The goal plan set plan component holds information about goal plans included in the goal plan set.

The discriminator GoalPlanSetPlan is used to load goal plan set plan records using HCM Data Loader. The
following GoalPlanSetPlan attributes are commonly supplied when loading a new goal plan set plan.

Note that the goal plans that need to be included in the goal plan set must have been created previously using
[Link] file. When [Link] and [Link] files are included in the same zip file, [Link] is
processed before [Link].

GOAL PLAN SET PLAN ATTRIBUTES

HCM Data Loader User Interface

Functional Description
Attribute Prompt

SourceSystemId / * (not displayed) You must provide a unique reference for the record being created. Supply either
SourceSystemOwner a source key or the user key attributes GoalPlanExternalId and
GoalPlanSetExternalId.

GoalPlanSetId * (not displayed for this You must provide a unique reference for the goal plan set this record is for. If
component) using user keys, then supply the user key attribute GoalPlanSetExternalId.
This attribute also supports the integration key types. If you supplied a source
key for the goal plan set, then supply the same value here and append the
source key hint to the attribute name. For example:
GoalPlanSetId(SourceSystemId).

GoalPlanId *Goal Plan Name You must provide a unique reference for the goal plan this record is for. If using
user keys, then supply the user key attribute GoalPlanExternalId.
This attribute also supports the integration key types. If you supplied a source
key for the goal plan, then supply the same value here and append the source
key hint to the attribute name. For example: GoalPlanId(SourceSystemId).

49 | LOADING GOAL DATA USING HCM DATA LOADER

HCM Data Loader User Interface
Functional Description
Attribute Prompt

Weighting Weight The weight of the goal plan in the goal plan set. The weight value must be
between zero and one hundred. The type of this attribute is NUMBER (5, 2) and
so it also supports decimals.

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalPlanSetExternalId (not displayed for this The external ID for the goal plan set this goal plan belongs to.
component)

GoalPlanExternalId Goal Plan Name The external ID for this goal plan.

Figure 16: Goal Plan Set Plan (Manage Goal Plan Sets)
Navigation: Manage Goal Plan Sets - Worker Assignment - Goal Plans

Goal Plan Set Dat File Examples

Creating a Goal Plan Set with Goal Plans

[Link]

This file creates a goal plan set to include two goal plans.

50 | LOADING GOAL DATA USING HCM DATA LOADER

MERGE|GoalPlanSetPlan|GPS_002_01|GP_001_03|40

Mass Request
The Mass Request component holds attributes of the mass request object associated with the goal plan set. It is
referenced by subcomponents that collectively define the employee population to assign the goal plan set to. These
subcomponents are listed in the Goal Plan Set Hierarchy table above. Every goal plan set needs to be associated
with a mass request record having a RequestTypeCode of TEMPLATE, irrespective of the presence of these
subcomponents.

The discriminator MassRequest is used to load goal plan set mass request records using HCM Data Loader. Note
that the MassRequest component is mandatory if the attributes ReqSubmittedByPersonId and
RequestSubmissionDate are not provided for the GoalPlanSet component while loading a new goal plan set. If
these attributes are provided for the GoalPlanSet component, then the template mass request record for the goal
plan set is created automatically using these values. Customers must pass the MassRequest component explicitly if
they want to associate a SourceSystemId to the template mass request record that they can use later for updating or
deleting the subcomponents that define the employee population.

While loading new goal plan sets, note that the components Mass Request Hierarchy, Mass Request Exemption,
and Eligibility Profile Object cannot be present in the [Link] file without the parent Mass Request
component.

The following MassRequest attributes are commonly supplied when loading a new goal plan set.

MASS REQUEST ATTRIBUTES

HCM Data Loader User Interface

Functional Description
Attribute Prompt

SourceSystemId / * (not displayed) You must provide a unique reference for the record being created. Supply either a
SourceSystemOwner source key or the user key attribute GoalPlanSetExternalId.

GoalPlanSetId *1 External ID You must provide a unique reference for the goal plan set this record is for. If using
user keys, then supply the user key attribute GoalPlanSetExternalId
This attribute also supports the integration key types. If you supplied a source key for
the goal plan set, then supply the same value here and append the source key hint
to the attribute name. For example: GoalPlanSetId(SourceSystemId)

ReqSubmittedByPersonId *1 * (not displayed) Provide a unique reference to the person who is creating the goal plan set. If
supplying user keys, then use the ReqSubmittedByPersonNumber attribute.
This attribute also supports the integration key types. If you supplied a source key for
the person, then supply the same value here and append the source key hint to the
attribute name. For example: RequestSubmittedByPersonId(SourceSystemId)

RequestSubmissionDate (not displayed) Provide the date when HR is creating this goal plan set. If this attribute is not passed,
it is defaulted to sysdate.

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalPlanSetExternalId (not displayed) The external ID for the goal plan set.

ReqSubmittedByPerson * (not displayed) The number of the person who is creating the goal plan set.
Number

51 | LOADING GOAL DATA USING HCM DATA LOADER

Goal Plan Set Dat File Examples

Creating a Goal Plan Set with Mass Request Component

[Link]

This file creates a goal plan set with a mass request. You must not provide the ReqSubmittedByPersonId and
RequestSubmissionDate attributes for the GoalPlanSet component in this case.

Eligibility Profile Object

The Eligibility Profile Object component holds a reference to an eligibility profile object that defines selection criteria
for employees to assign the goal plan set to.

The discriminator EligibilityProfileObject is used to load eligibility profile records for a goal plan set using HCM
Data Loader. The following EligibilityProfileObject attributes are commonly supplied when loading a new goal plan
set.

ELIGIBILITY PROFILE OBJECT ATTRIBUTES

HCM Data Loader User Interface

Functional Description
Attribute Prompt

ObjectId *1 * (not displayed) Provide a unique reference to the mass request this record belongs to. If using user
keys, then supply the user key attribute GoalPlanSetExternalId.
This attribute also supports the integration key types. If you supplied a source key for
the mass request, then supply the same value here and append the source key hint to
the attribute name. For example: ObjectId(SourceSystemId).
.

EligibilityProfileName Eligibility Profile The name of the eligibility profile.

RequiredFlag Required The flag that determines whether this eligibility profile is required.

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalPlanSetExternalId (not displayed for this The external ID for the goal plan set this eligibility profile object belongs to.
component)

Eligibility Profile The name of the eligibility profile.

EligibilityProfileName

52 | LOADING GOAL DATA USING HCM DATA LOADER

Figure 17: Eligibility Profile Object (Manage Goal Plan Sets)
Navigation: Manage Goal Plan Sets - Worker Assignment: Eligibility Profile

Goal Plan Set Dat File Examples

Creating a Goal Plan Set with Eligibility Profile

[Link]

This file creates a goal plan set with an eligibility profile object.

Associating Eligibility Profile with Existing Goal Plan Set

[Link]

This file creates an eligibility profile object for an existing goal plan set.

Mass Request Hierarchy

The Mass Request Hierarchy component holds details of a manager hierarchy or specific employees to assign the
goal plan set to.

The discriminator MassRequestHierarchy is used to load mass request hierarchy records for a goal plan set using
HCM Data Loader. The following MassRequestHierarchy attributes are commonly supplied when loading a new
goal plan set.

53 | LOADING GOAL DATA USING HCM DATA LOADER

MASS REQUEST HIERARCHY ATTRIBUTES

HCM Data Loader User Interface

Functional Description
Attribute Prompt

SourceSystemId / * (not displayed) You must provide a unique reference for the record being created. Supply either a
SourceSystemOwner source key or the user key attributes ManagerAssignmentNumber and
GoalPlanSetExternalId.
*1
MassRequestId * (not displayed) Provide a unique reference to the mass request this record belongs to. If using
user keys, then supply the user key attribute GoalPlanSetExternalId.
This attribute also supports the integration key types. If you supplied a source key
for the mass request, then supply the same value here and append the source key
hint to the attribute name. For example: MassRequestId(SourceSystemId).

ManagerAssignmentId *1 Job Provide a unique reference to the manager assignment (or the worker assignment
if the Cascading Level is Self). If using user keys, then supply the user key
attribute ManagerAssignmentNumber.
This attribute also supports the integration key types. If you supplied a source key
for the manager (or worker) assignment, then supply the same value here and
append the source key hint to the attribute name. For example:
ManagerAssignmentId(SourceSystemId).

CascadingLevel Assignees Specific type of hierarchy selection method. Provide one of the following values
(0,1, 999999,2 or 1000000):
0 - Self
1 - Direct reports
999999 - All reports
2 - Self and direct reports
1000000 - Self and all reports

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalPlanSetExternalId (not displayed for this The external ID for the goal plan set this mass request hierarchy object belongs to.
component)

ManagerAssignmentNu Job The assignment number for the manager.

mber

54 | LOADING GOAL DATA USING HCM DATA LOADER

Figure 18: Mass Request Hierarchy (Manage Goal Plan Sets)
Navigation: Manage Goal Plan Sets - Worker Assignment: Workers

Goal Plan Set Dat File Examples

Creating a Goal Plan Set with Mass Request Hierarchy Component

[Link]

This file creates a goal plan set with a mass request and mass request hierarchy.

Associating Mass Request Hierarchy with Existing Goal Plan Set

[Link]

This file creates a mass request hierarchy for an existing goal plan set with a mass request.

COMMENT Assigning Worker to Goal Plan Set GPS_001_04

55 | LOADING GOAL DATA USING HCM DATA LOADER

Mass Request Exemption
The Mass Request Exemption component holds details about workers exempted from the goal plan set. This
component can only be passed for MassRequestHierarchy records with a CascadingLevel not equal to zero. For
example, where cascading level is Direct reports, All reports, Self and direct reports, or Self and all reports.

The discriminator MassRequestExemption is used to load mass request exemption records for a goal plan set
using HCM Data Loader. The following MassRequestExemption attributes are commonly supplied when loading a
new goal plan set.

MASS REQUEST EXEMPTION ATTRIBUTES

HCM Data Loader

User Interface Prompt Functional Description
Attribute

SourceSystemId / * (not displayed) You must provide a unique reference for the record being created.
SourceSystemOwner

MassRequestHierarch (not displayed) You must provide a unique reference for the mass request hierarchy this record is
yId *1 for.
This attribute also supports the integration key types. If you supplied a source key
for the mass request hierarchy, then supply the same value here and append the
source key hint to the attribute name. For example:
MassRequestHierarchyId(SourceSystemId). If using user keys, then supply the
user key attributes GoalPlanSetExternalId and ManagerAssignmentNumber.

MassRequestId *1 (not displayed) Provide a unique reference for the mass request. If using user keys supply the
user key attribute GoalPlanSetExternalId.
Note that the source key is not supported for this attribute currently.
Do not pass this attribute while loading MassRequestExemption component along
with parent MassRequestHierarchy, MassRequest, and GoalPlanSet components
in the same [Link] file. The value for this column is automatically
derived in this case.
This column is mandatory while loading a MassRequestExemption component
separately after loading the parent GoalPlanSet, MassRequest, and
MassRequestHierarchy components in a different [Link] file. See the
sample MERGE lines given in this section.

PersonId *1 Name Provide a unique reference to the person who needs to be exempted from the goal
plan set. If using user keys, then supply the user key attribute
WorkerAssignmentNumber.
This attribute also supports the integration key types. If you supplied a source key
for the person, then supply the same value here and append the source key hint to
the attribute name. For example: PersonId(SourceSystemId).

AssignmentId *1 Job Provide a unique reference to the assignment of the person who needs to be
exempted from the goal plan set. If using user keys, then supply the user key
attribute WorkerAssignmentNumber.
This attribute also supports the integration key types. If you supplied a source key
for the assignment, then supply the same value here and append the source key
hint to the attribute name. For example: AssignmentId(SourceSystemId).

User key attributes that are required only if no other key type is supplied to identify uniquely the object they reference.

GoalPlanSetExternalId (not displayed for this The external ID for the goal plan set this mass request exemption object belongs
component) to.

ManagerAssignmentNu Job The assignment number for the manager.

mber

56 | LOADING GOAL DATA USING HCM DATA LOADER

HCM Data Loader
User Interface Prompt Functional Description
Attribute

WorkerAssignmentNu Job (In the “Select or The assignment number for the worker.
mber deselect assignees” popup)

Figure 19: Mass Request Exemption (Manage Goal Plan Sets)

Navigation: Manage Goal Plan Sets - Worker Assignment: Workers (select a manager) - Assignee Details

Goal Plan Set Dat File Examples

Creating a Goal Plan Set with Mass Request Exemption Component

[Link]

This file creates a goal plan set with a mass request hierarchy and exemption.

Do not pass a value for the MassRequestId attribute in this case as the value is automatically derived.

57 | LOADING GOAL DATA USING HCM DATA LOADER

erAssignmentNumber
MERGE|MassRequestExemption|GPS_001_05|EEEE8153786|EEEE8153787

Associating Mass Request Exemption with Existing Goal Plan Set

[Link]

This file creates a mass request exemption for an existing goal plan set and mass request hierarchy. Note: the user
keys ManagerAssignmentNumber and GoalPlanSetExternalId are not currently supported for the attribute
MassRequestHierarchyId while loading a MassRequestExemption record separately, and they cannot identify the
parent mass request hierarchy record in this case. You must supply the mass request hierarchy source key instead,
as shown below.

The GoalPlanSetExternalId must also be supplied, as the source key for the mass request is not currently
supported.

COMMENT Excluding another worker from Goal Plan Set GPS_006_01

Goal Plan Set Errors

You may experience errors while loading Goal Plan Set if the data is not provided as expected. Some of the more
commonly occurring errors are:

GoalPlanSet

Error Resolution

A goal plan set with the code value Ensure that the GoalPlanSetExternalId value is unique.
{GOAL_PLAN_SET_CODE} already
exists. Enter a unique code.

The goal plan end date must be later Ensure that the goal plan set end date is later than or equal to the goal plan set start date.
than or equal to the goal plan start date.

An application error occurred: The attributes ReqSubmittedByPersonId and RequestSubmissionDate are mandatory when the
[Link]. goal plan set record is loaded without the MassRequest component in the [Link] file.
See the sample MERGE line in the GoalPlanSet section.

MassRequest

Error Resolution

The requester ID does not exist. Ensure that the value passed for RequestSubmittedPersonId is valid.

EligibilityProfileObject

Error Resolution

You have selected the same eligibility An eligibility profile can be assigned once only to a goal plan set.

58 | LOADING GOAL DATA USING HCM DATA LOADER

Error Resolution

profile more than once for the

performance template or period. Select
a unique eligibility profile.

MassRequestHierarchy

Error Resolution

The request cannot be completed Ensure that the value passed for the ManagerId column is valid.
because {PersonId} does not exist.

The same manager and cascading level A manager and cascading level combination can be included once only in a goal plan set.
can only be entered once in this
request.

MassRequestExemption

Error Resolution

A parent for this record was not found. User keys are not supported for the MassRequestExemption component while loading
Use any of the four supported key- MassRequestExemption records separately. You must supply a source key to provide a unique
resolution systems to supply a valid reference for the mass request exemption record in this case. Also, note that the user key
parent reference. attributes ManagerAssignmentNumber and GoalPlanSetExternalId are not supported for the
MassRequestHierarchyId attribute while loading a MassRequestExemption record separately.
You must pass a source key for mass request hierarchy while loading mass request exemption
records separately. See the sample MERGE lines given in the MassRequestExemption section.

The record referenced by the foreign Do not pass the MassRequestId attribute while loading MassRequestExemption component
key attribute MassRequestId was not along with parent MassRequestHierarchy, MassRequest, and GoalPlanSet components in the
found. Either specify a valid foreign key same [Link] file. The value for this column is automatically derived in this case.
or create the referenced record first. See the sample MERGE lines given in the MassRequestExemption section.

JBO-27014: Attribute MassRequestId in The attribute MassRequestId is mandatory while loading MassRequestExemption component
MassReqExemptionsEO is required. separately after loading the parent GoalPlanSet, MassRequest, and MassRequestHierarchy
components in a different [Link] file. In addition, since source key is not supported for
this attribute, you need to pass GoalPlanSetExternalId instead. See the sample MERGE lines
given in the MassRequestExemption section.

Deletion Support for Goal Plan Set

You can delete Goal Plan Set using HCM Data Loader.

You must take care when using HCM Data Loader to delete records, as deleted records cannot be recovered. Do
not supply DELETE instructions in the same file as MERGE instructions for the same goal plan set records.

Use Case: Delete Goal Plan Sets and Their Child Records

When we delete a goal plan set record through HCM Data Loader, the following child records are automatically
deleted along with the parent record. These child records can also be individually deleted through HCM Data Loader
if needed.

 Template MassRequest
 MassRequestHierarchy

59 | LOADING GOAL DATA USING HCM DATA LOADER

 MassRequestExemption
 EligibilityProfileObject
 GoalPlanSetPlan

Do not delete goal plan sets that have already been assigned to workers.

Delete Goal Plan Set Dat File Examples

Deleting Goal Plan Set record and its child records

[Link]

This file deletes a goal plan set along with all its child components.

METADATA|GoalPlanSet|GoalPlanSetExternalId
DELETE|GoalPlanSet|GPS_006_01

60 | LOADING GOAL DATA USING HCM DATA LOADER

Oracle Corporation, World Headquarters Worldwide Inquiries
500 Oracle Parkway Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200

CONNECT W ITH US

[Link]/oracle Copyright © 2014, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
[Link]/oracle fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
[Link]/oracle means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
[Link]
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 1116

Loading Goal data Using HCM Data Loader

December 2016

Oracle HCM Business Object Structure
No ratings yet
Oracle HCM Business Object Structure
3 pages
Loading Work Structures in HCM Data Loader
No ratings yet
Loading Work Structures in HCM Data Loader
77 pages
Oracle HCM Cloud HCM Data Loader Business Objects and File Formats
No ratings yet
Oracle HCM Cloud HCM Data Loader Business Objects and File Formats
31 pages
HCM Data Loader User Guide 11g
No ratings yet
HCM Data Loader User Guide 11g
70 pages
Load Data into Oracle HCM Cloud Guide
No ratings yet
Load Data into Oracle HCM Cloud Guide
6 pages
Loading Workers with HCM Data Loader
No ratings yet
Loading Workers with HCM Data Loader
52 pages
Overview of Oracle Workforce Scheduling
No ratings yet
Overview of Oracle Workforce Scheduling
12 pages
Testing HR Integration Scripts Guide
No ratings yet
Testing HR Integration Scripts Guide
30 pages
Oracle Performance ManagementTroubleshooting BIP Notification Report Customization Issues
No ratings yet
Oracle Performance ManagementTroubleshooting BIP Notification Report Customization Issues
10 pages
HDL Data Load Process Overview
No ratings yet
HDL Data Load Process Overview
4 pages
Workforce Structure in Oracle HCM
No ratings yet
Workforce Structure in Oracle HCM
20 pages
Oracle Fusion Technical Training Program
No ratings yet
Oracle Fusion Technical Training Program
17 pages
Payroll Batch Loader Automation Guide
No ratings yet
Payroll Batch Loader Automation Guide
14 pages
Enterprise Scheduler Job Roles in HCM
No ratings yet
Enterprise Scheduler Job Roles in HCM
33 pages
Oracle Fusion Cloud HCM Overview
No ratings yet
Oracle Fusion Cloud HCM Overview
46 pages
Recruiting Implementation Guide
No ratings yet
Recruiting Implementation Guide
13 pages
Winfo Solutions: Oracle HCM Overview
No ratings yet
Winfo Solutions: Oracle HCM Overview
2 pages
Oracle HCM Enterprise Structures Guide
No ratings yet
Oracle HCM Enterprise Structures Guide
34 pages
HCM Annual Performance Test Cases
No ratings yet
HCM Annual Performance Test Cases
18 pages
Oracle Fusion HCM Course Overview
No ratings yet
Oracle Fusion HCM Course Overview
3 pages
Understanding Jobs and Positions in HR
No ratings yet
Understanding Jobs and Positions in HR
2 pages
Kotak Mahindra's Shift to Oracle HCM
No ratings yet
Kotak Mahindra's Shift to Oracle HCM
1 page
Oracle Fusion HCM Case Study Overview
No ratings yet
Oracle Fusion HCM Case Study Overview
3 pages
HCM Data Loader Fast Formula Guide
No ratings yet
HCM Data Loader Fast Formula Guide
7 pages
OTL Management in Oracle Fusion HCM
0% (1)
OTL Management in Oracle Fusion HCM
1 page
Payroll Batch Loader Overview
No ratings yet
Payroll Batch Loader Overview
2 pages
HRMS Workforce Performance Management Guide
No ratings yet
HRMS Workforce Performance Management Guide
55 pages
HCM Personalization Helper Tool Guide
No ratings yet
HCM Personalization Helper Tool Guide
6 pages
Oracle HCM Implementation and Roles Guide
No ratings yet
Oracle HCM Implementation and Roles Guide
6 pages
Oracle HCM R12 Boot Camp Courseware
No ratings yet
Oracle HCM R12 Boot Camp Courseware
51 pages
Visual Builder Studio - Lab Guide
No ratings yet
Visual Builder Studio - Lab Guide
81 pages
Core HRMS Key Tables Overview
No ratings yet
Core HRMS Key Tables Overview
4 pages
Evaluating Oracle HCM Cloud Onboarding
No ratings yet
Evaluating Oracle HCM Cloud Onboarding
4 pages
HCM EXTRACT Class 78,82,84,86,89,94
No ratings yet
HCM EXTRACT Class 78,82,84,86,89,94
16 pages
HDL for Loading Content Items
No ratings yet
HDL for Loading Content Items
7 pages
Leave Notification Alert Report
No ratings yet
Leave Notification Alert Report
9 pages
HCM Extracts: Types and Templates Guide
No ratings yet
HCM Extracts: Types and Templates Guide
20 pages
HR Employee End Date Document 1075831.1
No ratings yet
HR Employee End Date Document 1075831.1
7 pages
Seamless Oracle Redwood Migration Guide
No ratings yet
Seamless Oracle Redwood Migration Guide
13 pages
Oracle Fusion HCM Export Worksheet
No ratings yet
Oracle Fusion HCM Export Worksheet
86 pages
Workforce Compensation in Oracle HCM
No ratings yet
Workforce Compensation in Oracle HCM
6 pages
Oracle HCM Cloud for Retail Firms
No ratings yet
Oracle HCM Cloud for Retail Firms
10 pages
Managing Approval Rules in Talent Management - Examples
No ratings yet
Managing Approval Rules in Talent Management - Examples
26 pages
XML Data Fetching Procedures Guide
0% (1)
XML Data Fetching Procedures Guide
33 pages
UBS Dividend Equivalent Interface Design
No ratings yet
UBS Dividend Equivalent Interface Design
22 pages
Fast Formula Overview for Compensation
No ratings yet
Fast Formula Overview for Compensation
6 pages
Configure Approval Rules for Termination
No ratings yet
Configure Approval Rules for Termination
3 pages
Create Employee in Oracle HCM Cloud
No ratings yet
Create Employee in Oracle HCM Cloud
5 pages
Fast Formula Context Management Guide
No ratings yet
Fast Formula Context Management Guide
26 pages
Understanding Extra Information Types
No ratings yet
Understanding Extra Information Types
10 pages
Oracle HCM Consultant Profile: Tharun Kumar
No ratings yet
Oracle HCM Consultant Profile: Tharun Kumar
4 pages
Oracle Recruiting Cloud Candidate Search
No ratings yet
Oracle Recruiting Cloud Candidate Search
7 pages
EMEA Localizations in Oracle HCM Cloud
No ratings yet
EMEA Localizations in Oracle HCM Cloud
21 pages
HCM Fusion Reports Overview
No ratings yet
HCM Fusion Reports Overview
163 pages
MDA Business Trip Payment Entries
No ratings yet
MDA Business Trip Payment Entries
4 pages
Setup D58320GC10
No ratings yet
Setup D58320GC10
13 pages
Future Process Model for I-Recruitment
No ratings yet
Future Process Model for I-Recruitment
36 pages
2.5 Approvals and Workflow
No ratings yet
2.5 Approvals and Workflow
21 pages
Goal HDL Documentation
0% (1)
Goal HDL Documentation
65 pages
Loading Work Structures Using HCM Data Loader
100% (2)
Loading Work Structures Using HCM Data Loader
77 pages
Big Data Concepts: Hive, Pig, NoSQL, Graphs
No ratings yet
Big Data Concepts: Hive, Pig, NoSQL, Graphs
2 pages
Blockchain-Enhanced Cloud Security Framework
No ratings yet
Blockchain-Enhanced Cloud Security Framework
7 pages
Rich Internet Applications Overview
No ratings yet
Rich Internet Applications Overview
2 pages
Nixos in Production
No ratings yet
Nixos in Production
88 pages
Advanced GPU Programming MCQs Guide
No ratings yet
Advanced GPU Programming MCQs Guide
15 pages
ArogyaAI: AI Triage for Rural Healthcare
No ratings yet
ArogyaAI: AI Triage for Rural Healthcare
3 pages
Women's University in Africa: Computer Applications Exam
No ratings yet
Women's University in Africa: Computer Applications Exam
9 pages
Fusion 2.0.6 Release Notes Summary
No ratings yet
Fusion 2.0.6 Release Notes Summary
14 pages
Azure Cloud Week Curriculum Overview
No ratings yet
Azure Cloud Week Curriculum Overview
24 pages
Social Media Evidence Acquisition Guide
No ratings yet
Social Media Evidence Acquisition Guide
33 pages
Srikanth Bellary: Data Architect Resume
No ratings yet
Srikanth Bellary: Data Architect Resume
6 pages
Social Media Marketing Essentials Guide
No ratings yet
Social Media Marketing Essentials Guide
34 pages
U2000 Northbound Alarm SNMP Interface Technical Poster
No ratings yet
U2000 Northbound Alarm SNMP Interface Technical Poster
1 page
Dell Target Code Release Notes 9.2.0c3
No ratings yet
Dell Target Code Release Notes 9.2.0c3
8 pages
Python Doctor Appointment System
No ratings yet
Python Doctor Appointment System
5 pages
Form 2 Computer Studies Exam Paper
100% (1)
Form 2 Computer Studies Exam Paper
4 pages
Understanding Association Rule Mining
No ratings yet
Understanding Association Rule Mining
13 pages
XSS Attack Lab Instructions
No ratings yet
XSS Attack Lab Instructions
7 pages
AWS AI and ML Services Overview
No ratings yet
AWS AI and ML Services Overview
23 pages
Synchronizing Five Processes Using Barriers
No ratings yet
Synchronizing Five Processes Using Barriers
12 pages
Fiori Activation Guide for S/4HANA
No ratings yet
Fiori Activation Guide for S/4HANA
78 pages
Operating Systems: Process Management Overview
No ratings yet
Operating Systems: Process Management Overview
64 pages
PySpark Performance Tuning Guide
No ratings yet
PySpark Performance Tuning Guide
5 pages
Project Management Frameworks and Tools
No ratings yet
Project Management Frameworks and Tools
39 pages
Routing Protocols: Static vs Dynamic Analysis
No ratings yet
Routing Protocols: Static vs Dynamic Analysis
3 pages
Generative AI: Practical Applications Guide
No ratings yet
Generative AI: Practical Applications Guide
41 pages
Groovy Script Methods for Asset Management
No ratings yet
Groovy Script Methods for Asset Management
6 pages
TypeScript and OOP Easy Notes
No ratings yet
TypeScript and OOP Easy Notes
4 pages
Affordable Hybrid Smart Home Solution
No ratings yet
Affordable Hybrid Smart Home Solution
1 page
AZ-900 Practice Quiz Overview
No ratings yet
AZ-900 Practice Quiz Overview
53 pages

Load Goal Data with HCM Data Loader

Uploaded by

Load Goal Data with HCM Data Loader

Uploaded by

Loading Goal Data

Using HCM Data Loader

LOADING GOAL DATA USING HCM DATA LOADER

LOADING GOAL DATA USING HCM DATA LOADER

LOADING GOAL DATA USING HCM DATA LOADER

How to Use the Information in This Document

 Considerations and Prerequisites What to consider before attempting to load data

1 | LOADING GOAL DATA USING HCM DATA LOADER

2 | LOADING GOAL DATA USING HCM DATA LOADER

Business Scenario Object Load Sequence Notes

Load Template Goals 1. Person (HR) Goal plans are required.

3 | LOADING GOAL DATA USING HCM DATA LOADER

Considerations and Prerequisites for Goal

 Template Goal – a goal used in goal plan objects

Component Functional Description Discriminator

Goal Details of a goal. Goal

Goal Action Details of goal tasks. GoalAction

Goal Target Outcome Desired goal outcomes. GoalTargetOutcome

Goal Access Details of workers the goal is shared with. GoalAccess

Goal Alignment Details of a goal the goal is aligned to. GoalAlignment

4 | LOADING GOAL DATA USING HCM DATA LOADER

HCM Data Loader User Interface

StartDate *Start Date The start date of the goal.

GoalTypeCode * Goal Type The type of goal.

GoalSubTypeCode Subtype The subtype of the goal.

GoalVersionTypeCode * (not displayed) The goal status.

GoalExtId External ID Provides a reference to an external goal source.

AssignmentId *1 * Assignment Number Unique ID that identifies an assignment.

5 | LOADING GOAL DATA USING HCM DATA LOADER

Description Description Goal description.

SuccessCriteria Success Criteria Success criteria for goal achievement.

ActualCompletionDate Actual Completion Date Actual completion date of the goal.

GoalSourceCode * Source The source of the goal assignment.

6 | LOADING GOAL DATA USING HCM DATA LOADER

CategoryCode Category Administrator-defined category for a goal.

GoalUrl Related Link A URL resource associated with the goal.

OrganizationName Department The name of the organization this goal is for.

7 | LOADING GOAL DATA USING HCM DATA LOADER

Goal Dat File Examples

Creating a Worker Goal

8 | LOADING GOAL DATA USING HCM DATA LOADER

Creating a Worker Goal Against a Library Goal

Creating an Organization Goal

Creating a Template Goal to Include in a Goal Plan

9 | LOADING GOAL DATA USING HCM DATA LOADER

HCM Data Loader

ActionName * Name Name of the goal task.

StartDate Start Date The start date of the goal task.

Comments Comments Comments related to the task progress.

Figure 2: Goal Action (Goal Details)

10 | LOADING GOAL DATA USING HCM DATA LOADER

Creating a Goal Action (Task) Record

Goal Plan Goal

GOAL PLAN GOAL ATTRIBUTES

HCM Data Loader

11 | LOADING GOAL DATA USING HCM DATA LOADER

GoalPlanName * Goal Plan Name The name of the goal plan.

GoalPlanStartDate * Start Date The start date of the goal plan.

GoalPlanEndDate * End Date The end date of the goal plan.

Figure 3: Goal Plan Goal

Goal Dat File Examples

12 | LOADING GOAL DATA USING HCM DATA LOADER

This file creates a worker goal with a plan goal.

Goal Target Outcome

GOAL TARGET OUTCOME ATTRIBUTES

HCM Data Loader User Interface

Comments Comments Comments for this target outcome entry.

13 | LOADING GOAL DATA USING HCM DATA LOADER

the attribute name. For example: TargetRatingLevelId2(SourceSystemId).

ContentItemName * Content Item Name The content item name.

ContentTypeContextNa * Content Item Type The content type context name.

ApprovedRatingCode Manager Rating The code for the manager-approved rating.

14 | LOADING GOAL DATA USING HCM DATA LOADER

Goal Dat File Examples

Creating a Goal Target Outcome Record

15 | LOADING GOAL DATA USING HCM DATA LOADER

AssignmentId 1 Assignment Number Unique ID that identifies an assignment.