Sei sulla pagina 1di 38

Loading Talent Data

using HCM Data Loader

Oracle Fusion Human Capital Management 11g Release 9 (11.1.9)


ORACLE WHITE PAPER | JUNE 2015
Table of Contents
Loading Talent Data using HCM Data Loader 0
Introduction 1
How to Use the Information in This Document 1
Content Item 2
Considerations and Prerequisites for Content Item 2
Loading Content Item 2
Content Item 2
Content Item Rating Description 4
Content Item Errors 5
Deletion Support for Content Item 6
Content Item Translation 6
Content Item 6
Content Item Rating Description 7
Content Item Relationship 8
Considerations and Prerequisites for Content Item Relationship 8
Loading Content Item Relationship 8
Content Item Relationship 8
Content Item Relationship Errors 10
Deletion Support for Content Item Relationship 10
Education Establishment 11
Considerations and Prerequisites for Education Establishment 11
Loading Education Establishment 11
Education Establishment 11
Education Establishment Errors 13
Deletion Support for Education Establishment 13
Education Establishment Translation 13
Rating Model 14
Considerations and Prerequisites for Rating Model 14
Loading Rating Model 15
Rating Model 15
Rating Level 16

LOADING TALENT DATA USING HCM DATA LOADER


Rating Category 19
Rating Model Errors 20
Deletion Support for Rating Model 21
Rating Model Translation 21
Rating Model 21
Rating Level 22
Rating Category 22
Talent Profile 23
Considerations and Prerequisites for Talent Profile 23
Content Type 23
Talent Profile 23
Talent Profile Items 23
Loading Talent Profile 24
Talent Profile 24
Profile Item 26
Profile Relation 29
Profile Keyword 31
Talent Profile Errors 32
Deletion Support for Talent Profile 33
Talent Profile Translation 33
Talent Profile 33

Table of Figures
Figure 1: Manage Content Items .............................................................................................................................. 4
Figure 2: Manage Content Items: Content Item Proficiency Description ................................................................... 5
Figure 3: Related Content Items Tab ........................................................................................................................ 9
Figure 4: Manage Educational Establishment......................................................................................................... 12
Figure 5: Manage Profile Rating Models ................................................................................................................. 18
Figure 6: Manage Profile Rating Models - Review Points ....................................................................................... 18
Figure 7: Manage Profile Rating Models - Distributions .......................................................................................... 19
Figure 8: Manage Profile Rating Models - Rating Categories ................................................................................. 20
Figure 9: Person Details ......................................................................................................................................... 25
Figure 10: Job Details ............................................................................................................................................. 26
Figure 11: Person Details - Profile Details .............................................................................................................. 28
Figure 12: Job Details - Requirements ................................................................................................................... 29
Figure 13: Manage Model Profiles .......................................................................................................................... 31

LOADING TALENT DATA USING HCM DATA LOADER


Figure 14: Edit Skills and Qualifications .................................................................................................................. 32

LOADING TALENT DATA USING HCM DATA LOADER


Introduction
Whether implementing Oracle Fusion Global Human Resources for the first time or providing regular
updates, you can create talent profile 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 TALENT DATA USING HCM DATA LOADER


Content Item
A content item is a specific occurrence of a content type. Content items are stored in the content library representing
a list of values within an attribute set or content type. For example, a specific competency Communication Skills is a
content item of type Competency.

Considerations and Prerequisites for Content Item


The content type with its field properties must be available in the system before content items can be loaded using
HCM Data Loader. The content type field properties represent that information that you want to capture for the
content type. For example, one of the fields defined for the Memberships content type is the ITEM_DESCRIPTION
field. These field properties are set up such that the label of the field is Description and other properties are editable.
Therefore, when you load content item for the Memberships content type, the value of the Description attribute can
be left blank or you can enter a text describing the membership organization.

Loading Content Item


Content Item data must be supplied in the ContentItem.dat file for processing by HCM Data Loader.

CONTENT ITEM HIERARCHY

Component Functional Description Discriminator

Content Item A content item is an individual competency, skill, or qualification within a content type ContentItem
that you track in profiles. For example, if the content type is competency, a content item
might be communication or leadership.

The information on Rating Description for rating about a content item. For example, the RatingDescription
Content Item Rating description for Java competency rating Meets Expectations is "This person has
Description adequate java skills to do his job".

Content Item
The content item maintains the specific attributes defined for a content type.

The discriminator ContentItem is used to load content item records using HCM Data Loader. The following
ContentItem attributes are commonly used when loading a new content item. Other optional attributes may be
available.

CONTENT ITEM COMPONENT

HCM Data Loader User Interface


Functional Description
Attribute Prompt

SourceSystemId / * Name You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner * Context Name source key, or alternatively supply the user key attributes: Name and
ContextName.

ContentTypeId * Context Name The unique reference to the content type. If supplying user keys use the
ContextName attribute.

ContentItemCode Item Code A code to uniquely reference the content item. This code is only unique for a
content type; which means the same content item code can exists in different
content types.

2 | LOADING TALENT DATA USING HCM DATA LOADER


HCM Data Loader User Interface
Functional Description
Attribute Prompt

DateFrom * From Date Start date of the content item.

DateTo To Date End date of the content item.

ContentSupplierCode Supplier The content supplier code defines where the content item came from.

CountryId n/a The unique reference to the geography table. If supplying user keys, use the
CountryCountryCode and CountryGeographyCode attributes.

CountryCountryCode n/a The code for the country in the geography table.

CountryGeographyCode n/a The code for the country geography in the geography table.

StateProvinceId n/a The unique reference to the geography table. If supplying user keys use the
StateGeographyCode and StateCountryCode attributes.

StateCountryCode n/a The code for the state country in the geography table.

StateGeographyCode n/a The code for the state geography in the geography table.
*1
RatingModelId n/a Unique reference to the Rating Model. If using user keys supply the
RatingModelCode attribute. This attribute also supports the integration key types.
If you supplied a source key when creating the Rating Model you can supply the
same value here, simply add the source key hint to the attribute name. For
example, RatingModelId (SourceSystemId).

RatingModelCode * Rating Model Unique code that identifies the rating model.

ItemDescription Description The description of content item.


This can be translated for your other enabled languages by supplying a
ContentItemTranslation.dat file.

ItemNumber1 thru Depends on setup of Number column in content item that is used in defining content type properties.
ItemNumber10 content type properties

ItemDate1 thru Depends on setup of Date column in content item that is used in defining content type properties.
ItemDate10 content type properties

ItemText1 thru Depends on setup of Non translatable column in content item that is used in defining content type
ItemText30 content type properties properties.

ItemTextTl1 thru Depends on setup of Text column in content item that is used in defining content type properties.
ItemTextTl15 content type properties This can be translated for your other enabled languages by supplying a
ContentItemTranslation.dat file.

ItemDescrlong Long Description Long description of content item.


This can be translated for your other enabled languages by supplying a
ContentItemTranslation.dat file.

FLEX:HRT_CONTENT_I n/a Descriptive flexfield code. Supply this attribute if you want to load Descriptive
TEMS_B Flexfield data. The value provided should be the Descriptive Flexfield context for
the data line, if only global attributes are included the value here would be 'Global
Data Elements'.

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

Name * Name Name of the content item


This can be translated for your other enabled languages by supplying a
ContentItemTranslation.dat file.

ContextName Content Type Unique name that identifies content type.

3 | LOADING TALENT DATA USING HCM DATA LOADER


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

Figure 1: Manage Content Items


Navigation: Profiles > Manage Content Items > Create

Content Item Rating Description


The content item rating description holds the rating description information for rating on a content item. For example,
the description for Java competency rating Meets Expectations is "This person has adequate java skills to do his
job".

The discriminator RatingDescription is used to load content item rating description records using HCM Data
Loader. The following RatingDescription attributes are commonly used when loading a new content item rating
description.

CONTENT ITEM RATING DESCRIPTION COMPONENT

HCM Data Loader


User Interface Prompt Functional Description
Attribute

SourceSystemId / * Name You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner * Context Name source key, or alternatively supply the user key attributes: Name, ContextName,
and RatingLevelCode.
* Rating Level
*1
ContentItemId Content Name The unique reference to the content item table. If supplying user keys use the
Name and ContextName attributes. This attribute also supports the integration key
types, if you supplied a source key for the ContentItem supply the same value here
and append the source key hint to the attribute name, for example
ContentItemId(SourceSystemId).

ContentTypeId * Context Name The unique reference to the content type table. If supplying user keys use the
ContextName attribute.

RatingModelId*1 * Rating Model The unique reference to the rating model table. If supplying user keys use the

4 | LOADING TALENT DATA USING HCM DATA LOADER


HCM Data Loader
User Interface Prompt Functional Description
Attribute

RatingModelCode attribute. This attribute also supports the integration key types, if
you supplied a source key for the RatingModel supply the same value here and
append the source key hint to the attribute name, for example
RatingModelId(SourceSystemId).

RatingModelCode Rating Model Unique code that identifies the rating model.
*1
RatingLevelId n/a The unique reference to the rating level table. If supplying user keys use the
RatingLevelCode attribute. This attribute also supports the integration key types, if
you supplied a source key for the RatingLevel supply the same value here and
append the source key hint to the attribute name, for example
RatingLevelId(SourceSystemId).

ReviewRatingDescr Description Rating level description of content item.


This can be translated for your other enabled languages by supplying a
ReviewDescriptionTranslation.dat file.

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

Name Name Name of the content item

ContextName Content Type Unique name that identifies the content type

RatingLevelCode Rating Level Unique code that identifies the rating level of the rating model.

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

Figure 2: Manage Content Items: Content Item Proficiency Description


Navigation: Profiles > Manage Content Items > Create> Item Details Tab > Review Proficiency Description

Content Item Errors


You may experience errors while loading content item if the data is not provided as expected. Some common errors
are:

Error Resolution

The date must be on or after the from date. Change the to or from date so that the from date must be less than

5 | LOADING TALENT DATA USING HCM DATA LOADER


Error Resolution

the to date.

For competencies content type, you must make at least one A rating model must be selected for a competency content item.
selection for rating model.

The combination of content type and content item code must be If item code is provided, ensure that the code is unique for the
unique. content type.

Deletion Support for Content Item


You can delete a content item using HCM Data Loader.

Care should be taken 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: Content item records were loaded with erroneous data and need to be deleted.

If you delete a content item that is being used by other objects such as the person or job profile, it could impact the
object. In addition, the content item rating description will be deleted for that specific content item.

Content Item Translation

Content Item
The content item Name, Description, Long Description, and ItemTextTl1 thru ItemTextTl15 can be translated. The
ContentItemTranslation.dat file is used to provide translation data after the content item has been created.

CONTENT ITEM TRANSLATION ATTRIBUTES

HCM Data Loader


User Interface Prompt Functional Description
Attribute

SourceSystemId / * Context Name You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner source key, or alternatively supply the user key attributes: ContextName and
ContentItemName.

Name * Name The translated name of the content item

ItemDescription Description The translated description of the content item

ItemDescrlong Long Description The translated long description of the content item

ItemTextTl1 thru Depends on setup of The translated content item text columns that are used in defining the content type
ItemTextTl15 content type properties properties.

Language * not displayed The language of the supplied translated value. For example, FR, DE.

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

ContextName Content Type Unique name that identifies content type

ContentItemName n/a Name of the content item

6 | LOADING TALENT DATA USING HCM DATA LOADER


Content Item Rating Description
The content item rating description Rating Level Description can be translated. The
RatingDescriptionTranslation.dat file is used to provide translation data after the content item rating description
has been created.

CONTENT ITEM RATING DESCRIPTION TRANSLATION ATTRIBUTES

HCM Data Loader


User Interface Prompt Functional Description
Attribute

SourceSystemId / * Name You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner source key, or alternatively supply the user key attributes: Name and
RatingLevelCode

ReviewRatingDescr Description The translated rating level description of the content item

Language * not displayed The language of the supplied translated value. For example, FR, DE.

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

Name Name Name of the content item

RatingLevelCode n/a Unique code that identifies the rating level of the rating model.

7 | LOADING TALENT DATA USING HCM DATA LOADER


Content Item Relationship
The content item relationship defines the relationship between content items. The types of relationships are:

 A content type is a parent of another content type


 A content type supports another content type
Content items of content types with relationships inherit the relationship. You can't create two kinds of relationships
between two types or create a relationship between a type and itself. For example, content type A can't be both the
parent and child of content type B. A content type can't be related to itself. For example, if you have a content type
relationship where the goals content type supports the competencies content type, then on the content items for
competencies, you can enter the related goals.

Considerations and Prerequisites for Content Item Relationship


There are several rules regarding relationships between content types and content items:

 Related content type cannot be the same as the content type.


 Related content item cannot be the same as the content item.
In addition, in order to load related content items, the relationship must have been established at the content type
prior to loading the related content items.

Loading Content Item Relationship


Content Item Relationship data must be supplied in the ContentItemRelationship.dat file for processing by HCM
Data Loader.

CONTENT ITEM RELATIONSHIP HIERARCHY

Component Functional Description Discriminator

Content Item Defines the relationship between content items. For example, Action Oriented ContentItemRelationship
Relationship Competency is a parent of the Takes Initiative subcompetency.

Content Item Relationship


The content item relationship holds the relationship between content items.

The discriminator ContentItemRelationship is used to load content item relationship records using HCM Data
Loader. The following ContentItemRelationship attributes are commonly used when loading a new content item
relationship. Other optional attributes may be available.

CONTENT ITEM RELATIONSHIP COMPONENT

HCM Data Loader


User Interface Prompt Functional Description
Attribute

SourceSystemId / * Content Type You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner * Content Items source key, or alternatively supply the user key attributes: ContextName,
ContentItemName, RelatedContentTypeContextName, and
* Related Content Items RelatedContentItemName.

ContentItemId*1 * Content Items The unique reference to the content item table. If supplying user keys use the

8 | LOADING TALENT DATA USING HCM DATA LOADER


HCM Data Loader
User Interface Prompt Functional Description
Attribute

ContentItemName attribute. This attribute also supports the integration key types,
if you supplied a source key for the ContentItem supply the same value here and
append the source key hint to the attribute name, for example
ContentItemId(SourceSystemId).

ContentTypeId * Content Type The unique reference to the content type table. If supplying user keys use the
ContextName attribute.

DateFrom * From Date Start date of the content item relationship.

DateTo To Date End date of the content item relationship.

RelatedContentItemId* * Related Content Items The unique reference to the content item table. If supplying user keys use the
1
RelatedContentItemName attribute. This attribute also supports the integration key
types, if you supplied a source key for the ContentItem supply the same value here
and append the source key hint to the attribute name, for example
RelatedContentItemId(SourceSystemId).

RelatedContentTypeId n/a The unique reference to the content type table. If supplying user keys use the
RelatedContentTypeContextName attribute.

RelationshipCode Relationship Type Describes the relationships between content items.

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

ContextName Content Type Unique name that identifies the content type.

ContentItemName Content items Name of the content item.

RelatedContentTypeC n/a Unique name that identifies the related content type.
ontextName

RelatedContentItemN Related Content Items Name that identifies the related content item.
ame

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

Figure 3: Related Content Items Tab


Navigation: Profiles > Manage Content Items > Edit Content Item > Related Content Items Tab

9 | LOADING TALENT DATA USING HCM DATA LOADER


Content Item Relationship Errors
You may experience errors while loading content item relationship if the data is not provided as expected. Some
common errors are:

Error Resolution

The from date of the content item relationship must be within the Change the to or from date so that the from date must be less than
from date and to date of the content items for which you are creating the to date.
a relationship.

The to date of the content item relationship must be within the from Change the to or from date so that the from date must be less than
date and to date of the content items for which you are creating a the to date.
relationship.

A relationship between the same content items already exists. Either change the content items or delete the specific line entry.

A content type cannot be related to the same content type. Select a Change the content type.
content type other than the one for which you are setting up a
relationship.

Deletion Support for Content Item Relationship


You can delete a content item relationship using HCM Data Loader.

Care should be taken 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: Content item relationship records were loaded with erroneous data and need to be deleted.

If you delete a content item relationship that is being used by other objects, it could impact the object.

10 | LOADING TALENT DATA USING HCM DATA LOADER


Education Establishment
The education establishment object maintains the list of schools, colleges, universities, or organizations that workers
select when they add education information to their profile. It is not a content type itself, just referenced.

Considerations and Prerequisites for Education Establishment


Oracle Fusion Profile Management does not include a complete and comprehensive list of worldwide educational
establishments; however you can upload them using HCM Data Loader.

The following objects must already exist in Oracle Fusion Applications Common Components, before you can create
an education establishment that references these objects:

 Country
 State or Province
For more information on managing geographies, see the Oracle Fusion Applications Common Components help.

Loading Education Establishment


Education Establishment data must be supplied in the EducationEstablishment.dat file for processing by HCM
Data Loader.

EDUCATION ESTABLISHMENT HIERARCHY

Component Functional Description Discriminator

Education A school, college, university, or an organization that workers select when they add EducationEstablishment
Establishment education information to their profile. It is not a content type itself, just referenced.

Education Establishment
The education establishment holds the name, description, and location for an educational institution.

The discriminator EducationEstablishment is used to load education establishment records using HCM Data
Loader. The following EducationEstablishment attributes are commonly used when loading a new education
establishment. Other optional attributes may be available.

EDUCATION ESTABLISHMENT COMPONENT

HCM Data Loader User Interface


Functional Description
Attribute Prompt

SourceSystemId / * Code You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner source key, or alternatively supply the user key attributes: SchoolCode.

Name * Name Name of an educational establishment.


This can be translated for your other enabled languages by supplying a
EducationEstablishmentTranslation.dat file.

Description * Description Description of the establishment.


This can be translated for your other enabled languages by supplying an
EducationEstablishmentTranslation.dat file.

CountryId Country The unique reference to the geography table. If supplying user keys, use the
CountryCountryCode and CountryGeographyCode attributes.

11 | LOADING TALENT DATA USING HCM DATA LOADER


HCM Data Loader User Interface
Functional Description
Attribute Prompt

CountryCountryCode n/a The code for the country in the geography table.

CountryGeographyCode n/a The code for the country geography in the geography table.

StateProvinceId State or Province The unique reference to the geography table. If supplying user keys use the
StateGeographyCode and StateCountryCode attributes.

StateCountryCode n/a The code for the state country in the geography table.

StateGeographyCode n/a The code for the state geography in the geography table.

Location Location The location details of an establishment.


This can be translated for your other enabled languages by supplying an
EducationEstablishmentTranslation.dat file.

FLEX:HRT_ESTABLISH n/a Descriptive flexfield code. Supply this attribute if you want to load Descriptive
MENTS_B Flexfield data. The value provided should be the Descriptive Flexfield context for
the data line. If only global attributes are included the value here would be 'Global
Data Elements'.

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

SchoolCode * Code School code which has to be unique.

Figure 4: Manage Educational Establishment


Navigation: Profiles > Manage Education Establishment > Create Educational Establishment

12 | LOADING TALENT DATA USING HCM DATA LOADER


Education Establishment Errors
You may experience errors while loading education establishment if the data is not provided as expected. Some
common errors are:

Error Resolution

The establishment code must be unique. Ensure that the SchoolCode (Code) is unique for the establishment.

You must enter a value for SchoolCode, Name, and Description. SchoolCode (Code), Name, and Description are required attributes
for the Education Establishment.

Deletion Support for Education Establishment


You can delete an education establishment using HCM Data Loader.

Care should be taken 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: Education establishment records were loaded with erroneous data and need to be deleted.

If you delete an education establishment that is being used by other objects, it could impact the records referenced
by the other objects.

Education Establishment Translation


The education establishment Name, Description, and Location can be translated. The
EducationEstablishmentTranslation.dat file is used to provide translation data after the education establishment
has been created.

EDUCATION ESTABLISHMENT TRANSLATION ATTRIBUTES

HCM Data Loader


User Interface Prompt Functional Description
Attribute

SourceSystemId / * Code You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner source key, or alternatively supply the user key attributes: SchoolCode.

Name * Name The translated name for the education establishment.

Description * Description The translated description for the education establishment.

Location Location The translated location for the education establishment.

Language * not displayed The language of the supplied translated value. For example, FR, DE.

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

SchoolCode * Code The code of the school this translation is for.

13 | LOADING TALENT DATA USING HCM DATA LOADER


Rating Model
Rating models are used to rate workers on their performance and level of proficiency in the skills and qualities that
are set up on the person profile. You can also use rating models to specify target proficiency levels for items on a
model profile, so that the model profile can be compared to workers' profiles. Use the Manage Profile Rating Models
task in the Profiles work area to create a rating model.

To rate workers on their performance and proficiency, attach rating models to the content types included in the
person profile. Then you can rate workers on the items within the type. For example, you can rate workers on the
Communication content item within the Competencies content type.

For model profiles, you can specify target proficiency levels for items on the profile, to compare model profiles with
worker profiles. Using the ratings:

 Managers can compare a model profile to workers' profiles with and determine the best person suited to fill a
position.
 Workers can compare their profile to model profiles to identify:
o Suitable positions within the organization.
o Skill gaps and fill the gaps before applying for other positions.
Rating models that measure a worker’s potential and the impact and risk of loss are also available.

Rating models can include some or all of the following components, depending on the use for the model:

 Rating levels - Rating levels identify the qualitative values, such as 1, 2, 3, or 4, that you use to rate a worker.
For rating models that are used by Oracle Fusion Performance Management, you must:
o Define numeric ratings, particularly for rating models in performance documents that use calculated
ratings.
o Define rating levels using whole numbers, with the highest number indicating the best rating. Rating levels
determine high and low ratings in the analytics.
 Review points - Define review points for rating models in performance documents that use the sum or band
calculation method. The review points and point ranges that you define for the rating model are used to
calculate ratings.
 Rating categories - Using rating categories you can group rating levels together for analysis tools used in the
talent review process, such as the box chart that is used in the talent review process. You can group rating
levels into categories such as low, medium, and high, and those categories then become the labels for the
analytic. You shouldn't change rating categories after setting them up, as the changes could affect the analytic.
 Distributions - Oracle Fusion Compensation Management and Oracle Fusion Performance Management both
use rating model distributions to determine the targeted minimum and maximum percentage of workers that
should be given each rating level. Compensation Management uses the distribution values that you set up
directly on rating models. However, you can set up distributions at the performance template level for rating
models that are used in Performance Management.

Considerations and Prerequisites for Rating Model


There are several rules for creating rating models:

 Rating Model
o The from date must be less than the to date.
o The rating model code (code in the user interface) must be unique.
o The distribution threshold must be a positive number.
 Rating Level:

14 | LOADING TALENT DATA USING HCM DATA LOADER


o The from date must be less than the to date.
o The rating level code must be unique.
o The maximum rating distribution must be greater than the minimum rating distribution.
o The star rating must be unique within the rating model and between 0 and 10.
o The numeric rating must be a positive number.
 Rating Category:
o The category name must be unique.
o The upper boundary must be greater than, or equal to the lower boundary and both upper and lower
boundaries must be positive numbers.
o The upper and lower boundaries for rating categories within a rating model must not overlap each other.
o The upper boundary must not be greater than the maximum numeric rating provided for the rating model.

Loading Rating Model


Rating Model data must be supplied in the RatingModel.dat file for processing by HCM Data Loader.

RATING MODEL HIERARCHY

Component Functional Description Discriminator

Rating Model The rating levels, review points, rating categories, and distributions to rate workers on RatingModel
their performance and level of proficiency or to specify target proficiency levels for items
on a model profile.

Rating Level The qualitative values, such as 1, 2, 3, or 4, that you use to rate a worker, the review RatingLevel
points for rating models in performance documents that use the sum or band calculation
method, and the targeted minimum and maximum percentage of workers that should be
given each rating level.

Rating Category The grouping categories of rating levels for analysis tools used in the talent review RatingCategory
process, such as the box chart that is used in the talent review process.

Rating Model
The rating model holds the rating levels, review points, rating categories, and distributions to rate workers on their
performance and level of proficiency or to specify target proficiency levels for items on a model profile.

The discriminator RatingModel is used to load rating model records using HCM Data Loader. The following
RatingModel attributes are commonly used when loading a new rating model. Other optional attributes may be
available.

RATING MODEL COMPONENT

HCM Data Loader


User Interface Prompt Functional Description
Attribute

SourceSystemId / * Code You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner source key, or alternatively supply the user key attributes: RatingModelCode.

RatingName * Name Name of Rating Model.


This can be translated for your other enabled languages by supplying a
RatingModelTranslation.dat file.

RatingDescription Description Rating Model description.

15 | LOADING TALENT DATA USING HCM DATA LOADER


HCM Data Loader
User Interface Prompt Functional Description
Attribute

This can be translated for your other enabled languages by supplying a


RatingModelTranslation.dat file.

DateFrom * From Date Start date when rating model is valid.

DateTo To Date End date when rating model is valid.

DistributionThreshold Distribution Threshold The distribution threshold decides the visibility of minimum and maximum targets
in Rating Levels.

FLEX:HRT_RATING_ n/a Descriptive flexfield code. Supply this attribute if you want to load Descriptive
MODELS_B Flexfield data. The value provided should be the Descriptive Flexfield context for
the data line, if only global attributes are included the value here would be 'Global
Data Elements'.

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

RatingModelCode Code Unique code that identifies rating model.

Rating Level
The rating level holds the qualitative values, such as 1, 2, 3, or 4, that you use to rate a worker, the review points for
rating models in performance documents that use the sum or band calculation method, and the targeted minimum
and maximum percentage of workers that should be given each rating level.

The discriminator RatingLevel is used to load rating level records using HCM Data Loader. The following
RatingLevel attributes are commonly used when loading a new rating level. Other optional attributes may be
available.

NOTE: Bug 18243387 requires that the parent Rating Model must also be included in the .dat file while updating the
Rating Level and Rating Category child objects as part of the same load.

RATING LEVEL COMPONENT

HCM Data Loader


User Interface Prompt Functional Description
Attribute

SourceSystemId / * Code You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner * Rating Level source key, or alternatively supply the user key attributes: RatingModelCode and
RatingLevelCode
*1
RatingModelId * Code The unique reference to the rating model table. If supplying user keys use the
RatingModelCode attribute. This attribute also supports the integration key types, if
you supplied a source key for the RatingModel supply the same value here and
append the source key hint to the attribute name, for example,
RatingModelId(SourceSystemId).

DateFrom * From Date The start date from when the rating model becomes available.

RatingDescription Name (Rating Level Tab) Rating level description.


This can be translated for your other enabled languages by supplying a
RatingLevelTranslation.dat file.

RatingShortDescr * Short Description (Rating Rating Level short description.

16 | LOADING TALENT DATA USING HCM DATA LOADER


HCM Data Loader
User Interface Prompt Functional Description
Attribute

Level Tab) This can be translated for your other enabled languages by supplying a
RatingLevelTranslation.dat file.

StarRating Star Rating Star rating value for the rating level. Must be between 0 and 10.

NumericRating Numeric Rating Numeric rating for the rating level.

CareerStrDev Career Strength or Career Strength and Development.


Development

ReviewPoints Review Points Review points.

ReviewRatingDescr Description (Rating Level Review rating description.


and Review Points Tabs) This can be translated for your other enabled languages by supplying a
RatingLevelTranslation.dat file.

FromPoints From Points From point rating.

ToPoints To Points To point rating.

MinimumRatingDistrib Minimum Distribution Minimum distribution as a percentage.


ution

MaximumRatingDistrib Maximum Distribution Maximum distribution as a percentage.


ution

FLEX:HRT_RATING_ n/a Descriptive flexfield code, supply this attribute if you want to load Descriptive
LEVELS_B Flexfield data. The value provided should be the Descriptive Flexfield context for
the data line, if only global attributes are included the value here would be 'Global
Data Elements'.

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

RatingModelCode Code Unique code that identifies the rating model.

RatingLevelCode * Rating Level Unique code that identifies the rating level of the rating model.

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

17 | LOADING TALENT DATA USING HCM DATA LOADER


Figure 5: Manage Profile Rating Models
Navigation: Profiles > Manage Profile Rating Models > Edit > Rating Levels Tab

Figure 6: Manage Profile Rating Models - Review Points


Navigation: Profiles >Manage Profile Rating Models > Edit > Review Points Tab

18 | LOADING TALENT DATA USING HCM DATA LOADER


Figure 7: Manage Profile Rating Models - Distributions
Navigation: Profiles > Manage Profile Rating Models > Edit > Distributions Tab

Rating Category
The rating category holds the grouping categories of rating levels for analysis tools used in the talent review
process, such as the box chart that is used in the talent review process.

The discriminator RatingCategory is used to load rating category records using HCM Data Loader. The following
RatingCateogory attributes are commonly used when loading a new rating category. Other optional attributes may
be available.

NOTE: Bug 18243387 requires that the parent Rating Model must also be included in the .dat file while updating the
Rating Level and Rating Category child objects as part of the same load.

RATING CATEGORY COMPONENT

HCM Data Loader


User Interface Prompt Functional Description
Attribute

SourceSystemId / * Code You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner * Category Name source key, or alternatively supply the user key attributes: RatingModelCode and
CategoryName.

RatingModelId*1 * Code The unique reference to the rating model table. If supplying user keys use the
RatingModelCode attribute. This attribute also supports the integration key types, if
you supplied a source key for the RatingModel supply the same value here and
append the source key hint to the attribute name, for example
RatingModelId(SourceSystemId).

CategoryDescription Category Description Rating Category description.


This can be translated for your other enabled languages by supplying a
RatingCategoryTranslation.dat file.

19 | LOADING TALENT DATA USING HCM DATA LOADER


LowerBoundary * Lower Boundary Define the lower boundary of the category

UpperBoundary * Upper Boundary Define the upper boundary of the category

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

RatingModelCode * Code Unique code that identifies the rating model

CategoryName * Category Name Unique name of rating category

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

Figure 8: Manage Profile Rating Models - Rating Categories


Navigation: Profiles > Manage Profile Rating Models > Edit > Rating Categories Tab

Rating Model Errors


You may experience errors while loading rating model if the data is not provided as expected. Some common errors
are:

Error Resolution

The rating model or rating level code must be Provide a unique rating model or rating level code.
unique.

The rating category must be unique. Provide a unique rating category.

The upper boundary must be less than or equal Provide an upper boundary that is less than or equal to the highest numeric rating for the
to the highest numeric rating for the rating model. rating model.

From date is not less than the to date. Modify either the from or to date so it meets the validation.

The minimum distribution percentage must be Minimum Distribution must lie between 0 and 100. Indicate to user the possible values
between zero and one hundred. that may be entered, in this case from 0 to 100. Maximum and Minimum Distribution
percentages are assigned to rating levels for use in Compensation allocations.

The maximum distribution percentage must be The percentage value for Maximum Distribution lies between 0 and 100. Maximum and
between zero and one hundred. Minimum Distribution percentages are assigned to rating levels for use in Compensation
allocations.

20 | LOADING TALENT DATA USING HCM DATA LOADER


The rating distribution threshold must be greater Rating Distribution Threshold can be set for a rating model, and is typically used by
than or equal to zero. Compensation for allocations. The Rating Distribution Threshold identifies the minimum
size of population necessary for maximum and minimum distribution percentages to apply
for the rating levels in the specified rating model. This number cannot be negative, it must
be greater than or equal to 0.

The maximum distribution must be greater than The maximum distribution must be greater than the minimum distribution for a rating
the minimum distribution. level.

The star rating value must be unique. The star rating value must be unique. Star ratings are a numeric value assigned to rating
levels in a rating model, to indicate how many stars should appear for each rating level, if
stars are displayed instead of a number or description. For each rating level in the rating
model the value for the number of stars must be different.

Deletion Support for Rating Model


You can delete a rating model using HCM Data Loader.

Care should be taken 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: Rating model records were loaded with erroneous data and need to be deleted.

If you delete a rating model that is being used by other objects such as a content item or a profile, it will impact the
object.

NOTE: Bug 20235891: Rating model referenced by a content item gets deleted when the content item is deleted.

Rating Model Translation

Rating Model
The rating model Name and Description can be translated. The RatingModelTranslation.dat file is used to provide
translation data after the rating model has been created.

RATING MODEL TRANSLATION ATTRIBUTES

HCM Data Loader User Interface


Functional Description
Attribute Prompt

SourceSystemId / n/a You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner source key, or alternatively supply the user key attributes: RatingModelCode.

RatingName * Name The translated rating name of the rating model.

RatingDescription Description The translated rating description of the rating model.

Language * not displayed The language of the supplied translated value. For example, FR, DE.

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

RatingModelCode Code Unique code that identifies rating model.

21 | LOADING TALENT DATA USING HCM DATA LOADER


Rating Level
The rating level Name and Description can be translated. The RatingLevelTranslation.dat file is used to provide
translation data after the rating model has been created.

RATING LEVEL TRANSLATION ATTRIBUTES

HCM Data Loader User Interface


Functional Description
Attribute Prompt

SourceSystemId / n/a You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner source key, or alternatively supply the user key attributes: No user key defined bug:
18540858

RatingDescription Name (Rating Level The translated rating description of the rating level
Tab)

RatingShortDescr Short Description The translated rating short description of the rating level
(Rating Level Tab)

ReviewRatingDescr Description (Rating The translated description of the review points


Level and Review
Points Tabs)

Language * not displayed The language of the supplied translated value. For example, FR, DE.

Rating Category
The rating category Description can be translated. The RatingCategoryTranslation.dat file is used to provide
translation data after the rating model has been created.

RATING CATEGORY TRANSLATION ATTRIBUTES

HCM Data Loader


User Interface Prompt Functional Description
Attribute

SourceSystemId / * Code You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner source key, or alternatively supply the user key attributes: RatingModelCode and
CategoryName.

CategoryDescription Category Description The translated description of the rating category.

Language * not displayed The language of the supplied translated value. For example, FR, DE.

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

RatingModelCode Code Unique code that identifies the rating model.

CategoryName Category Name Unique name of rating category.

22 | LOADING TALENT DATA USING HCM DATA LOADER


Talent Profile
Managers and Human Resource (HR) Specialists can maintain information within person profiles about the skills,
qualifications, accomplishments, and career preferences of their workers. They can also maintain information in
model profiles about the targeted skills and qualifications of the jobs and positions within the company. Workers can
manage their own careers by keeping their talent profiles current so that their skills, qualifications, accomplishments,
and career preferences reflect their current performance and future career goals.

You can create:

 Person profile: A collection of a worker's skills, qualifications, education background, and so on.
 Model profile: A collection of the work requirements and required skills and qualifications of a workforce
structure, such as a job or position.

You can create model profiles for a job family or organizations, but you cannot attach the model profile to a job
family, like you can for jobs and positions. So you can create a model profile for a job family or organization for
informational purposes only.

Considerations and Prerequisites for Talent Profile

Content Type
Content type with its field properties must be available in the system before the profile can be loaded using HCM
Data Loader. The content type field properties represent that information that you want to capture for the content
type. A content type can be added to the person or model profile as a content section. You can include content
types from the content library and free-form ones.

Talent Profile
 PersonID or PartyID must be populated when the ProfileUsageCode is "P".
 PersonID and PartyID must be empty/null when the ProfileUsageCode is "M".
 A person profile is not allowed to have a profile relationship.
 Profile relation must be unique. A profile relation is a work structure, such as a job or position, that is associated
with the profile. The same work structure cannot be associated more than once with the same profile.
 A person can have only one profile. You cannot create multiple profiles for the same person.
 For the person profile you can define content section properties which are attributes that are used to define
data included in a person profile and displayed in the portrait.
 For workers to be able to add a content section to their profiles, you must set up role access for employees to
be able to edit the content section.

Talent Profile Items


 Duplicate content items in a profile are not permitted.
 A profile content item with the same qualifiers and overlapping from (start) and to (end) dates is not allowed if
one already exists.
 The mandatory attributes defined in the profile type section properties must be populated when creating a row
in profile item.
 Duplicate certifications profile item data is not allowed. Duplicates are identified by checking for same
ContentItem, qualifiers, overlapping from and to dates, and title.

23 | LOADING TALENT DATA USING HCM DATA LOADER


 Duplicate degree profile item data is not allowed. Duplicates are identified by checking for same ContentItem,
qualifiers, overlapping from and to dates, and major.
 ItemNumber1 must be unique. ItemNumber1 must not exist on any other row in the same profile at any date for
the same ContentType, ContentItem, and qualifiers.

Loading Talent Profile


Talent profile data must be supplied in the TalentProfile.dat file for processing by HCM Data Loader.

TALENT PROFILE HIERARCHY

Component Functional Description Discriminator

Talent Profile Individual instance of a profile, either person or job, based on a specific profile type. TalentProfile

Profile Item The elements which make up a Profile. The elements can be of any content type such ProfileItem
as competencies, objectives, and so forth. For example, a profile might contain a Java
competency.

Profile Relation A profile instance can be related to any model specified in Profile Type Relations. For ProfileRelation
example, JobCode or PosCode.

Profile Keyword Capture keywords for Areas of Expertise and Areas of Interests for person profiles. ProfileKeyword

Talent Profile
The talent profile holds information about the skills, qualifications, accomplishments, and career preferences of a
person and the targeted skills and qualifications of the jobs and positions within the company.

The discriminator TalentProfile is used to load talent profile records using HCM Data Loader. The following
TalentProfile attributes are commonly used when loading a new talent profile. Other optional attributes may be
available.

TALENT PROFILE COMPONENT

HCM Data Loader


User Interface Prompt Functional Description
Attribute

SourceSystemId / * Code You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner source key, or alternatively supply the user key attributes: ProfileCode.

OwnerPersonId*1 Person Number The unique reference to the owner of the profile. If supplying user keys use the
OwnerPersonNumber attribute. This attribute also supports the integration key
types, if you supplied a source key for the Person supply the same value here and
append the source key hint to the attribute name, for example
OwnerPersonId(SourceSystemId).

OwnerPersonNumber Person Number Unique number that identifies the person.


*1
PersonId n/a Unique id that identifies the person. If supplying user keys use the PersonNumber
attribute. This attribute also supports the integration key types, if you supplied a
source key for the Person supply the same value here and append the source key
hint to the attribute name, for example PersonId(SourceSystemId).

PersonNumber Person Number Unique number that identifies the person.

ProfileTypeId n/a Identify the profile type (for example, Person, Job, and others). If supplying user
keys use the ProfileTypeCode attribute.

ProfileTypeCode n/a Unique code that identifies the profile type.

24 | LOADING TALENT DATA USING HCM DATA LOADER


HCM Data Loader
User Interface Prompt Functional Description
Attribute

ProfileUsageCode n/a Usage code that identifies the profile as a person profile or model profile.

Description Description Description of the profile.


This can be translated for your other enabled languages by supplying a
TalentProfileTranslation.dat file.

ProfileStatusCode Status Status Code if the profile is active or inactive

Summary Person Summary Description that summarize the profile.


This can be translated for your other enabled languages by supplying a
TalentProfileTranslation.dat file.

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

ProfileCode * Code Unique code that identifies the profile

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

Figure 9: Person Details


Navigation: Profiles > Search Profiles > Person Profiles > Person Details > Overview

25 | LOADING TALENT DATA USING HCM DATA LOADER


Figure 10: Job Details
Navigation: Profiles > Search Profiles > Job Profiles > Job Profile

Profile Item
The profile item holds the elements which make up a profile. The elements can be of any content type such as
competencies, objectives, and so forth. For example, a profile might contain a Java competency.

The discriminator ProfileItem is used to load profile item records using HCM Data Loader. The following
ProfileItem attributes are commonly used when loading a new profile item. Other optional attributes may be
available.

PROFILE ITEM COMPONENT

HCM Data Loader


User Interface Prompt Functional Description
Attribute

SourceSystemId / n/a You must provide a unique reference for the record being created. No combination
SourceSystemOwner of user attributes exists that uniquely identify a profile item.

ProfileId*1 Code The unique reference to the profile table. If supplying user keys use the
ProfileCode attribute. This attribute also supports the integration key types, if you
supplied a source key for the Profile supply the same value here and append the
source key hint to the attribute name, for example ProfileId(SourceSystemId).

ContentItemId*1 Name The unique reference to the content item. If supplying user keys use the
Content Type ContentItem and ContentType attributes.
This attribute also supports the integration key types, if you supplied a source key
for the ContentItem supply the same value here and append the source key hint to
the attribute name, for example ContentItemId(SourceSystemId).

CountryCountryCode n/a The code for the country in the geography table.

CountryGeographyCo n/a The code for the country geography in the geography table.
de

StateCountryCode n/a The code for the state country in the geography table.

StateGeographyCode n/a The code for the state geography in the geography table.

26 | LOADING TALENT DATA USING HCM DATA LOADER


HCM Data Loader
User Interface Prompt Functional Description
Attribute

DateFrom * From Date Start date of the profile item

DateTo To Date End date of the profile item

Importance Importance Relative importance. This field is used in Search and Compare Profiles

InterestLevel Interest Level Level of interest

ItemDate1 thru Depends on setup of profile Date column in profile item; use in defining the profile properties
ItemDate10 content properties

ItemDecimal1 thru Depends on setup of profile Decimal column in profile item; use in defining the profile properties
ItemDecimal10 content properties

ItemNumber1 thru Depends on setup of profile Number column in profile item; use in defining the profile properties
ItemNumber10 content properties

ItemText20001 thru Depends on setup of profile Non-translatable column in profile item; use in defining the profile properties
ItemText20005 content properties

ItemText2401 thru Depends on setup of profile Non-translatable column in profile item; use in defining the profile properties
ItemText24015 content properties

ItemText301 thru Depends on setup of profile Non-translatable column in profile item; use in defining the profile properties
ItemText3015 content properties

Mandatory n/a A generic mandatory field that takes Y/N

ParentProfileItemId n/a Unique ID that identified the parent profile item

QualifierCode1 n/a Code to identify the qualifier along with the QualifierSetCode1

QualifierSetCode1 n/a Code to identify the qualifier along with the QualifierCode1

QualifierCode2 n/a Code to identify the qualifier along with the QualifierSetCode2

QualifierSetCode2 n/a Code to identify the qualifier along with the QualifierCode2
*1
RatingModelId1 n/a The unique reference to the rating model table. If supplying user keys use the
RatingModelCode1 attribute. This attribute also supports the integration key types,
if you supplied a source key for the RatingModel supply the same value here and
append the source key hint to the attribute name, for example
RatingModelId1(SourceSystemId).

RatingLevelId1*1 n/a The unique reference to the rating level table. If supplying user keys use the
RatingLevelCode1 and RatingModelCode1 attributes. This attribute also supports
the integration key types, if you supplied a source key for the RatingLevel supply
the same value here and append the source key hint to the attribute name, for
example RatingLevelId1(SourceSystemId).
*1
RatingModelId2 n/a The unique reference to the rating model table. If supplying user keys use the
RatingModelCode2 attribute. This attribute also supports the integration key types,
if you supplied a source key for the RatingModel supply the same value here and
append the source key hint to the attribute name, for example
RatingModelId2(SourceSystemId).

RatingLevelId2*1 n/a The unique reference to the rating level table. If supplying user keys use the
RatingLevelCode2 and RatingModelCode2 attributes. This attribute also supports
the integration key types. If you supplied a source key for the RatingLevel, supply
the same value here and append the source key hint to the attribute name, for
example RatingLevelId2(SourceSystemId).

RatingModelId3*1 n/a The unique reference to the rating model table. If supplying user keys use the
RatingModelCode3 attribute. This attribute also supports the integration key types.

27 | LOADING TALENT DATA USING HCM DATA LOADER


HCM Data Loader
User Interface Prompt Functional Description
Attribute

If you supplied a source key for the Rating Model, supply the same value here and
append the source key hint to the attribute name, for example
RatingModelId3(SourceSystemId).

RatingLevelId3*1 n/a The unique reference to the rating level table. If supplying user keys, use the
RatingLevelCode3 and RatingModelCode3 attributes. This attribute also supports
the integration key types. If you supplied a source key for the RatingLevel, supply
the same value here and append the source key hint to the attribute name, for
example RatingLevelId3(SourceSystemId).

FLEX:HRT_PROFILE n/a Descriptive flexfield code, supply this attribute if you want to load Descriptive
_ITEMS Flexfield data. The value provided should be the Descriptive Flexfield context for
the data line, if only global attributes are included the value here would be 'Global
Data Elements'.

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

ProfileCode Code Unique code that identifies the profile

ContentItem Name Content item name.

ContentType Content Type Unique code that identifies the content type.

RatingModelCode1 n/a Unique code that identifies the rating model

RatingLevelCode1 n/a Unique code along with the rating model id that identifies the rating level

RatingModelCode2 n/a Unique code that identifies the rating model

RatingLevelCode2 n/a Unique code along with the rating model id that identifies the rating level

RatingModelCode3 n/a Unique code that identifies the rating model

RatingLevelCode3 n/a Unique code along with the rating model id that identifies the rating level

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

Figure 11: Person Details - Profile Details


Navigation: Profiles > Search Profiles > Person Profile > Profile Details Tab

28 | LOADING TALENT DATA USING HCM DATA LOADER


Figure 12: Job Details - Requirements
Navigation: Profiles > Search Profiles > Job Profile > Requirements

Profile Relation
The profile relation holds the relationship between a model profile to any model specified in Profile Type Relations.
For example, JobCode or PositionCode.

The discriminator ProfileRelation is used to load profile relation records using HCM Data Loader. The following
ProfileRelation attributes are commonly used when loading a new profile relation. Other optional attributes may be
available.

PROFILE RELATION COMPONENT

HCM Data Loader


User Interface Prompt Functional Description
Attribute

SourceSystemId / * Code You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner * Workforce Structure source key, or alternatively supply the user key attributes: ProfileCode,
RelationCode and BusinessUnitName, PositionCode, or LocationCode,
LocationSetCode, or OrganizationName, or JobFamilyName

ObjectId n/a Contains the id of the actual model entity for example, job_id or position_id
*1
ProfileId * Code The unique reference to the profile table. If supplying user keys, use the
ProfileCode attribute. This attribute also supports the integration key types. If you
supplied a source key for the Profile, supply the same value here and append the
source key hint to the attribute name, for example. ProfileId(SourceSystemId).

RelationId n/a The unique reference to the relation table. If supplying user keys use the
RelationCode attribute.

JobId*1 Workforce Structures: Code The unique reference to the job table. If supplying user keys, use the JobSetCode
and JobCode attributes. This attribute also supports the integration key types. If
you supplied a source key for the Job, supply the same value here and append the
source key hint to the attribute name, for example JobId(SourceSystemId).

PositionId*1 Workforce Structures: Code Unique ID that identifies the position. If supplying user keys use the PositionCode
and BusinessUnitName attributes. This attribute also supports the integration key

29 | LOADING TALENT DATA USING HCM DATA LOADER


HCM Data Loader
User Interface Prompt Functional Description
Attribute

types. If you supplied a source key for the Position supply the same value here
and append the source key hint to the attribute name, for example
PositionId(SourceSystemId).

OrganizationId*1 Workforce Structures: Name The unique reference to the organization unit table. If supplying user keys use the
OrganizationName attribute. This attribute also supports the integration key types.
If you supplied a source key for the Organization, supply the same value here and
append the source key hint to the attribute name, for example
OrganizationId(SourceSystemId).
*1
JobFamilyId Workforce Structures: Name The unique reference to the job family table. If supplying user keys use the
JobFamilyName attribute. This attribute also supports the integration key types. If
you supplied a source key for the JobFamily supply the same value here and
append the source key hint to the attribute name, for example
JobFamilyId(SourceSystemId).

LocationId*1 Workforce Structures: Code The unique reference to the location table. If supplying user keys use the
LocationCode and LocationSetCode attributes. This attribute also supports the
integration key types. If you supplied a source key for the Location supply the
same value here and append the source key hint to the attribute name, for
example LocationId(SourceSystemId).

ObjectEffectiveStartD * Effective Start Date Object effective start date


ate

ObjectEffectiveEndDat Effective End Date Object effective end date


e

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

ProfileCode * Code Unique code that identifies the profile

RelationCode n/a Unique code that identifies the relation that can be associated to a model profile
(for example, organization, position)

JobSetCode Workforce Structures: Code Denotes the code for the job set

JobCode Workforce Structures: Code Denotes the job code

BusinessUnitName n/a Denotes the business unit name.

PositionCode Workforce Structures: Code The unique reference to the position table.

LocationCode Workforce Structures: Code Unique code that identifies the location

LocationSetCode Workforce Structures: Code Set code that uniquely identifies the set where the location belongs to.

OrganizationName Workforce Structures: Name Denotes the name of the organization.

JobFamilyName Workforce Structures: Name Denotes the name for the job family.

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

30 | LOADING TALENT DATA USING HCM DATA LOADER


Figure 13: Manage Model Profiles
Navigation: Profiles > Manage Model Profiles > Search > Edit > Job Profile

Profile Keyword
The profile keyword holds keywords for areas of expertise and areas of interests for person based profiles.

The discriminator ProfileKeyword is used to load profile keyword records using HCM Data Loader. The following
ProfileKeyword attributes are commonly used when loading a new profile keyword. Other optional attributes may
be available.

PROFILE KEYWORD COMPONENT

HCM Data Loader


User Interface Prompt Functional Description
Attribute

SourceSystemId / * Code You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner source key, or alternatively supply the user key attributes: ProfileCode,
KeywordType.

ProfileCode * Code Unique code that identifies the profile the keyword is for.

KeywordType * no prompt displayed The keyword type. This attribute has two valid values:
 AOE Area of Expertise
 AOI Area of Interest

Keywords Keywords Keywords value for areas of expertise and areas of interests for person based
profiles.

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

31 | LOADING TALENT DATA USING HCM DATA LOADER


Figure 14: Edit Skills and Qualifications
Navigation: Team Talent Overview > Select Person > Skills and Qualifications

Talent Profile Errors


You may experience errors while loading talent profile if the data is not provided as expected. Some common errors
are:

Error Resolution

The combination of values specified for the attributes You must specify a value either for the attribute person ID or party ID, or both
profile usage code, person ID, and party ID is invalid. attributes only when the value of the attribute profile usage code is P. Either change
the value of the attribute profile usage code to P or ensure that the attributes person
ID and party ID have no value when the value of the attribute profile usage code is
M.

The profile type relation must be unique. The workforce structure relation defined for the profile type cannot be a duplicate of
an existing relation.

Profile items data cannot be saved. Delete duplicate Some of the attributes were duplicated for the column PROFILE_ID {PROFILE_ID}
attributes or contact your administrator. with PROFILE_ITEM_ID {PROFILE_ITEM_ID} and CONTENT_ITEM_ID
{CONTENT_ITEM_ID}. One or more of the following attributes were duplicated:
ITEM_TEXT240_1 {ITEM_TEXT}, QUALIFIER_ID1 {QUALIFIER_ID1},
QUALIFIER_ID2 {QUALIFIER_ID2}, DATE_FROM {DATE_FROM}, DATE_TO
{DATE_TO}. Ignore attributes with no values. You or your administrator must delete
duplicate rows and try again.

A profile already exists for this person. A person can have only one profile. You cannot create multiple profiles for the same
person.

You cannot create a person profile with profile Oracle Fusion does not permit the Person Profile created in HR to have relationships
relationships. with any other Profile Type.

You cannot use this content item {CONTENT_ITEM} To add a content item from the content library to a profile, the appropriate content
because the associated content type is not defined as type must be associated with a section for that profile type. For example, the content
a section in the profile type. type COMPETENCY must be associated with a profile section before you can add a
competency of Leadership to a profile.

32 | LOADING TALENT DATA USING HCM DATA LOADER


Deletion Support for Talent Profile
You can delete a talent profile using HCM Data Loader.

Care should be taken 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: Profile records were loaded with erroneous data and need to be deleted.

If you delete a profile that is being used by other objects such as best fit, it will impact the object.

Talent Profile Translation

Talent Profile
The talent profile Description and Summary can be translated. The TalentProfileTranslation.dat file is used to
provide translation data after the talent profile has been created.

TALENT PROFILE TRANSLATION ATTRIBUTES

HCM Data Loader


User Interface Prompt Functional Description
Attribute

SourceSystemId / * Code You must provide a unique reference for the record being created. Either supply a
SourceSystemOwner source key, or alternatively supply the user key attributes: ProfileCode

Description Description The translated description of the profile.

Summary Person Summary The translated description that summarizes the profile.

Language * not displayed The language of the supplied translated value. For example, FR, DE.

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

ProfileCode * Code Unique code that identifies the profile.

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

33 | LOADING TALENT 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

blogs.oracle.com/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
facebook.com/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
twitter.com/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.
oracle.com
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. 0615

Loading Talent Data using HCM Data Loader


June 2015

Potrebbero piacerti anche