Integrating With HCM PDF

Oracle Human Capital
Management Cloud
Integrating with HCM
20A
Oracle Human Capital Management Cloud
20A
Part Number F24403-02
Copyright © 2011, 2020, Oracle and/or its aliates. All rights reserved.
Authors: Suzanne Kinkead, Alison Firth, Susan Saha, Lakshmi Venkat, Gina Baronian-Moore, Mridula Menon
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by
intellectual property laws. Except as expressly permied in your license agreement or allowed by law, you may not use, copy, reproduce, translate,
broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you nd any errors, please report
them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then
the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition
Regulation and agency-specic supplemental regulations. As such, use, duplication, disclosure, modication, and adaptation of the programs,
including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license
terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use
in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in
dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe
use. Oracle Corporation and its aliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its aliates. Other names may be trademarks of their respective owners.
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.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle
Corporation and its aliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and
services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its aliates will not be responsible
for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable
agreement between you and Oracle.
The business names used in this documentation are ctitious, and are not intended to identify any real companies currently or previously in existence.
Contents
Preface i
1 Introduction to Integrating with Oracle HCM Cloud 1

Overview of Integrating with Oracle HCM Cloud ................................................................................................................... 1
Inbound Integrations .................................................................................................................................................................... 6
Outbound Integrations ................................................................................................................................................................. 7
2 Introduction to HCM Data Loader 9

Overview of HCM Data Loader .................................................................................................................................................. 9
HCM Data Loader and Implementation Scenarios .............................................................................................................. 10
How Data Is Loaded Using HCM Data Loader ...................................................................................................................... 11
Supported Key Types ................................................................................................................................................................. 13
Source Keys .................................................................................................................................................................................. 14
User Keys ....................................................................................................................................................................................... 15
Oracle Fusion GUIDs and Surrogate IDs ................................................................................................................................ 16
Business-Object Structure ......................................................................................................................................................... 16
FAQs for Introduction to HCM Data Loader ......................................................................................................................... 18
3 Data File Instructions and Delivery 19

HCM Data Loader Data and .zip Files ..................................................................................................................................... 19
File Line Instructions and File Discriminators ...................................................................................................................... 20
The METADATA Instruction ..................................................................................................................................................... 22
The MERGE Instruction ............................................................................................................................................................. 23
The DELETE Instruction ............................................................................................................................................................ 24
The SET Instruction .................................................................................................................................................................... 25
Generate and Use Template Files ........................................................................................................................................... 28
FAQs for Data File Instructions and Delivery ....................................................................................................................... 29
4 Preparing to Use HCM Data Loader 31

Sources of Business-Object Information ................................................................................................................................ 31
HCM Data Loader Conguration Parameters ....................................................................................................................... 32
How You Dene Referenced Objects ..................................................................................................................................... 37
How You Review Lists of Values ............................................................................................................................................. 39
Dene the Source-System Owner ........................................................................................................................................... 39
How You Test the HCM Data Loader Process Flow and Connections ............................................................................ 40
How You Audit Objects Loaded in Bulk ................................................................................................................................. 41
FAQs for Preparing to Use HCM Data Loader ..................................................................................................................... 42
5 Data Preparation 45
Guidelines for Preparing the Source Data ............................................................................................................................ 45
General Data Considerations for HCM Data Loader ........................................................................................................... 45
How You Load Images, Aachments, and Large Strings .................................................................................................. 47
How You Supply Source Keys ................................................................................................................................................. 48
How You Update Source Keys ................................................................................................................................................ 49
How You Supply User Keys ..................................................................................................................................................... 50
Examples of Supplying Oracle Fusion Surrogate IDs ......................................................................................................... 50
Examples of Supplying Oracle Fusion GUIDs ....................................................................................................................... 51
How You Manage Reserved Characters ................................................................................................................................ 52
How You Load and Maintain Translated Objects ................................................................................................................ 53
How You Include Source-System References in Data Files .............................................................................................. 54
Data Deletion Using HCM Data Loader ................................................................................................................................. 55
6 Loading Date-Eective Data 57

Overview of Loading Date-Eective Objects ........................................................................................................................ 57
How You Load Objects with Multiple Changes per Day .................................................................................................... 58
Options for Updating Date-Eective Objects with Future-Dated Records .................................................................... 60
Example of Retaining Aribute Values in Future-Dated Records .................................................................................... 62
Options for Carrying Forward Changed Aribute Values in Retain Mode ..................................................................... 63
Example of Replacing Aribute Values in Future-Dated Records ................................................................................... 65
Examples of Changing First Eective Start Date and Last Eective End Date ............................................................. 66
7 Loading Flexeld Data 69

Guidelines for Loading Flexeld Data .................................................................................................................................... 69
How You Load Data for Descriptive Flexelds .................................................................................................................... 70
Example of Loading Data for Descriptive Flexelds ............................................................................................................ 71
How You Load Data for Extensible Flexelds ...................................................................................................................... 73
Example of Loading Data for Extensible Flexelds ............................................................................................................ 74
8 Loading Setup Objects 75

Guidelines for Loading Absence Cases ................................................................................................................................. 75
Examples of Loading Actions .................................................................................................................................................. 75
Examples of Loading Action Reasons ................................................................................................................................... 76
Guidelines for Loading Calendar Events ............................................................................................................................... 77
Guidelines for Loading Checklist Templates ........................................................................................................................ 78
Examples of Loading Checklist Templates ........................................................................................................................... 79
Guidelines for Loading Document Delivery Preferences .................................................................................................... 81
Guidelines for Loading Document Types .............................................................................................................................. 82
Examples of Loading Document Types ................................................................................................................................ 84
Examples of Loading Extended Lookup Codes ................................................................................................................... 86
Guidelines for Loading Name Formats ................................................................................................................................. 87
Examples of Loading Person Types ....................................................................................................................................... 89
Examples of Loading Resource Exceptions ......................................................................................................................... 90
Guidelines for Loading Time and Labor Event Groups ...................................................................................................... 91
Examples of Loading Time and Labor Event Groups ......................................................................................................... 92
Columns and Event Source Objects for Time and Labor Events ..................................................................................... 93
Examples of Loading Time and Labor Event Actions ........................................................................................................ 96
9 Loading Workers 99
Overview of Loading Workers ................................................................................................................................................. 99
Guidelines for Preparing to Load Workers .......................................................................................................................... 101
Eective Start and End Dates for Worker Components ................................................................................................... 102
Guidelines for Deleting Worker Components ..................................................................................................................... 103
How You Check for Duplicate Person Records .................................................................................................................. 104
Person Numbers in Worker Objects ..................................................................................................................................... 105
Guidelines for Loading External Identiers ......................................................................................................................... 107
Guidelines for Loading Person Names ................................................................................................................................ 107
Guidelines for Loading Person Images ................................................................................................................................ 108
Examples of Loading Work Relationship Changes ........................................................................................................... 108
How You Perform a Global Transfer ..................................................................................................................................... 110
Guidelines for Loading Additional Assignments ................................................................................................................. 111
Guidelines for Loading Temporary Assignments ............................................................................................................... 112
Start Dates for Person Legislative Data ................................................................................................................................ 113
Employment Terms Override at Assignment ...................................................................................................................... 114
Automatic Calculation of FTE Values for Workers ............................................................................................................. 114
Create a Default Working-Hour Paern ................................................................................................................................ 115
Examples of Loading Worker Working Hour Paern ......................................................................................................... 115
Examples of Loading Assignment Eligible Jobs ................................................................................................................. 116
Guidelines for Loading Seniority Dates ................................................................................................................................ 118
Examples of Loading Seniority Date Adjustments ............................................................................................................. 119
Examples of Loading Seniority Hours ................................................................................................................................... 121
Example of Loading a Contract Extension .......................................................................................................................... 123
Example of Loading a Default Expense Account for a Worker ....................................................................................... 123
FAQs for Loading Workers ..................................................................................................................................................... 124
10 Loading Worker-Related Objects 127

Example of Loading an Allocated Checklist ........................................................................................................................ 127
Guidelines for Loading Areas of Responsibility .................................................................................................................. 127
Guidelines for Loading Document Records ........................................................................................................................ 128
Example of Loading PeopleGroup for a Worker ................................................................................................................ 130
Guidelines for Loading Time Record Groups ...................................................................................................................... 131
Examples of Loading Time Record Groups ......................................................................................................................... 133
Guidelines for Loading User-Update Requests .................................................................................................................. 134
Examples of Loading User-Update Requests ..................................................................................................................... 135
Guidelines for Loading Worker Schedules ........................................................................................................................... 137
Examples of Creating Worker Schedules ............................................................................................................................. 138
Examples of Updating Worker Schedules ........................................................................................................................... 140
FAQs for Loading Worker-Related Objects .......................................................................................................................... 141
11 Loading Work Structures 143

Overview of Loading Work Structures ................................................................................................................................. 143
Examples of Loading Collective Agreements ..................................................................................................................... 144
Guidelines for Loading Grades .............................................................................................................................................. 145
Guidelines for Loading Grade Ladders ................................................................................................................................ 146
Guidelines for Loading Grade Rates ..................................................................................................................................... 147
Guidelines for Loading Jobs ................................................................................................................................................... 147
Examples of Loading Job Families ....................................................................................................................................... 148
Guidelines for Loading Locations ......................................................................................................................................... 149
Guidelines for Loading Organizations .................................................................................................................................. 150
Guidelines for Loading Positions ........................................................................................................................................... 151
Examples of Loading HCM Position Hierarchies ................................................................................................................ 153
Guidelines for Loading Department Trees .......................................................................................................................... 154
Guidelines for Loading Department Tree Nodes ............................................................................................................... 156
Examples of Loading Department Tree Nodes .................................................................................................................. 156
Guidelines for Loading Organization Trees ........................................................................................................................ 159
Guidelines for Loading Organization Tree Nodes ............................................................................................................. 160
Examples of Loading Organization Tree Nodes ................................................................................................................. 161
12 Loading Compensation Objects 165

Guidelines for Loading Market Data Objects ...................................................................................................................... 165
Examples of Loading Market Data Career Level, Career Stream, and Other Level .................................................... 166
Examples of Loading Market Data Job Family and Function ......................................................................................... 167
Examples of Loading Market Data Location List and Job List ....................................................................................... 168
Example of Loading Market Data Survey Data .................................................................................................................. 169
Guidelines for Loading Progression Grade Ladders ......................................................................................................... 169
Examples of Loading Progression Grade Ladders with Steps ......................................................................................... 171
Examples of Loading Progression Grade Ladders Without Steps .................................................................................. 174
Guidelines for Loading Progression Grade Rates .............................................................................................................. 175
Examples of Loading Progression Grade Rates ................................................................................................................. 176
Guidelines for Loading Progression Rules ........................................................................................................................... 177
Examples of Loading Progression Rules ............................................................................................................................. 178
Guidelines for Loading Salary Basis Records ..................................................................................................................... 179
Guidelines for Loading Salary Records ................................................................................................................................. 181
Examples of Loading Salary Records ................................................................................................................................... 182
Examples of Loading Salary Range Dierential Proles and Values ............................................................................. 184
Guidelines for Making Date-Eective Changes to Salary Range Dierentials ............................................................. 185
13 Loading Payroll Relationships 187

Payroll Information ................................................................................................................................................................... 187
Assigned Payroll ........................................................................................................................................................................ 189
Payroll Assignments .................................................................................................................................................................. 191
14 Loading Payroll Setup Objects 195

Examples of Loading Legislative Data Groups ................................................................................................................... 195
Object Groups ............................................................................................................................................................................ 195
Example of Loading Payroll Consolidation Group ............................................................................................................. 198
Payroll Denitions and Time Periods ................................................................................................................................... 198
Time Denitions ........................................................................................................................................................................ 202
Example of Loading Payroll Element Run Usage .............................................................................................................. 205
User-Dened Tables ................................................................................................................................................................ 206
Examples of Loading Payroll Balance Denitions .............................................................................................................. 211
Payroll Balance Groups ............................................................................................................................................................ 213
Fast Formulas ............................................................................................................................................................................. 221
Elements ...................................................................................................................................................................................... 222
15 Loading Payroll Transactional Data 235

Example of Loading Payroll Time Cards ............................................................................................................................. 235
Guidelines for Loading Calculation Cards ........................................................................................................................... 235
Example of Loading Wage Basis Rules ................................................................................................................................ 237
Element Entries ......................................................................................................................................................................... 238
16 Initializing and Adjusting Balances 251

Balance Initializations ............................................................................................................................................................... 251
Balance Adjustments ............................................................................................................................................................... 257
17 Loading Payment Methods 265

Examples of Loading Banks ................................................................................................................................................... 265
Examples of Loading Bank Branches .................................................................................................................................. 265
Examples of Loading External Bank Accounts .................................................................................................................. 266
Organization Payment Methods ........................................................................................................................................... 267
Example of Loading Personal Payment Methods ............................................................................................................. 269
Example of Loading Third-Party Organization Payment Method .................................................................................. 271
Example of Loading Third-Party Personal Payment Method ......................................................................................... 273
18 Loading Payroll Costing 277

Overview of Loading Payroll Costing ................................................................................................................................... 277
Example of Loading Element Eligibility Costing ................................................................................................................ 278
Example of Loading Costing of Payroll ................................................................................................................................ 281
Example of Loading Costing of Departments .................................................................................................................... 282
Example of Loading Costing of Jobs ................................................................................................................................... 285
Example of Loading Costing of Positions ........................................................................................................................... 286
Example of Loading Payment Source Costing .................................................................................................................. 287
Example of Loading Person Costing .................................................................................................................................... 288
Example of Loading Person Costing at Payroll Relationship Level ............................................................................... 288
Example of Loading Person Costing at Assignment Level ............................................................................................. 289
Example of Loading Person Element Costing at Assignment Level ............................................................................. 290
Example of Loading Person Element Costing at Payroll Relationship Level ............................................................... 290
Example of Loading Element Entry Costing ....................................................................................................................... 291
19 Loading Payroll Data Using Transformation Formula 293

Payroll Transformation Formula for HCM Data Loader ................................................................................................... 293
Payroll Transformation Formula for HCM Spreadsheet Data Loader .......................................................................... 305
20 Loading Talent Objects 309

Overview of Loading Goals, Goal Plans, and Goal Plan Sets .......................................................................................... 309
Guidelines for Loading Goals ................................................................................................................................................. 310
Examples of Loading Goals ..................................................................................................................................................... 312
Guidelines for Loading Goal Plans ........................................................................................................................................ 314
Examples of Loading Goal Plans ........................................................................................................................................... 315
Guidelines for Loading Goal Plan Sets ................................................................................................................................. 316
Examples of Loading Goal Plan Sets .................................................................................................................................... 317
Examples of Loading Mass Actions for Performance Documents ................................................................................. 318
Examples of Loading Succession Plans .............................................................................................................................. 320
Examples of Loading Talent Pools ........................................................................................................................................ 321
Guidelines for Loading Talent Prole Data ......................................................................................................................... 322
Examples of Loading Talent Review Meetings .................................................................................................................. 324
FAQs for Loading Talent Objects .......................................................................................................................................... 327
21 Loading Learning Objects 329

Examples of Loading Classroom Resources ....................................................................................................................... 329
Examples of Loading Course Oering Pricing Defaults ................................................................................................... 329
Guidelines for Loading Courses ............................................................................................................................................ 330
Examples of Loading Courses ................................................................................................................................................ 331
Examples of Associating Global Access Groups ................................................................................................................ 332
Example of Loading a Learning Record Activity Aempt ................................................................................................ 333
Examples of Loading Legacy Learning Items .................................................................................................................... 333
Examples of Loading Oering Custom Pricing Objects ................................................................................................... 334
Example of Loading a Specialization ................................................................................................................................... 335
22 Loading Absences Topics 337

Example of Loading Accrual Plan Enrollments .................................................................................................................. 337
Example of Loading Absence Qualication Plan Entitlement ......................................................................................... 337
Guidelines for Loading Absence Entry ................................................................................................................................ 338
Examples of Loading Absence Entry ................................................................................................................................... 339
23 Loading Benets Objects 341

Example of Loading Beneciary Enrollments ..................................................................................................................... 341
Example of Loading Person Beneciary Organizations ................................................................................................... 342
Example of Loading Dependent Enrollments .................................................................................................................... 342
Example of Loading Participant Enrollments .................................................................................................................... 344
Example of Loading Person Benet Group ........................................................................................................................ 345
Example of Loading Person Benet Balance ..................................................................................................................... 346
Example of Loading Person Habits ...................................................................................................................................... 346
24 Importing and Loading Data Using HCM Data Loader 347

How Data Is Imported and Loaded ...................................................................................................................................... 347
Import and Load Data ............................................................................................................................................................. 348
Upload Data Using HCM Data Loader ................................................................................................................................. 350
How You Review and Correct Errors .................................................................................................................................... 352
Stop HCM Data Loader Processing ...................................................................................................................................... 354
Overview of Automating Data Loading ............................................................................................................................... 355
How to Review the Objects Processed in a Data Set ........................................................................................................ 356
FAQs for Importing and Loading Data Using HCM Data Loader ................................................................................... 356
25 Data Loading Using Spreadsheets 359

Spreadsheet Data Loaders ..................................................................................................................................................... 359
Set Up Desktop Integration for Excel .................................................................................................................................. 360
Troubleshoot Desktop Integration for Excel ....................................................................................................................... 361
26 Introduction to HCM Spreadsheet Data Loader 363

Guidelines for Using HCM Spreadsheet Data Loader ...................................................................................................... 363
How Data Is Uploaded Using HCM Spreadsheet Data Loader ....................................................................................... 364
How You Test the HCM Spreadsheet Data Loader Process Flow and Connections .................................................. 366
Spreadsheet Business Object Access ................................................................................................................................... 367
Manage Spreadsheet Business Object Access .................................................................................................................. 368
How You Enable Access to HCM Spreadsheet Data Loader Tasks ............................................................................... 369
FAQs for HCM Spreadsheet Data Loader ............................................................................................................................ 371
27 HCM Spreadsheet Data Loader Templates 373

HCM Spreadsheet Data Loader Templates ......................................................................................................................... 373
Dene Categories for Spreadsheet Templates .................................................................................................................. 375
Create and Edit Spreadsheet Templates ............................................................................................................................. 375
How You Associate a User Name with a Data Upload ..................................................................................................... 378
Set Spreadsheet Template Parameters ............................................................................................................................... 378
Spreadsheet Template Design .............................................................................................................................................. 380
Guidelines for Designing Spreadsheet Templates ............................................................................................................ 382
How You Congure Default Values for Spreadsheet Aributes ..................................................................................... 383
Congure Lists of Values for Aribute Validation ............................................................................................................ 385
Autogenerated Aribute Values in Spreadsheet Templates .......................................................................................... 386
Copy Spreadsheet Templates ................................................................................................................................................ 387
Export and Import Spreadsheet Templates ....................................................................................................................... 388
How You Enable Business Users with Custom Roles to Load Spreadsheet Data ....................................................... 388
Add a Custom Role to a Predened Spreadsheet Template .......................................................................................... 389
FAQs for HCM Spreadsheet Data Loader Templates ...................................................................................................... 390
28 Importing and Loading Data Using HCM Spreadsheet Data Loader 391
Generate Spreadsheets ............................................................................................................................................................ 391
Import Data to a Spreadsheet ................................................................................................................................................ 391
Manage Spreadsheet Data Sets ............................................................................................................................................ 392
Upload Data Using HCM Spreadsheet Data Loader ......................................................................................................... 394
How You Delete Data Using HCM Spreadsheet Data Loader ......................................................................................... 396
FAQs for Importing and Loading Data Using HCM Spreadsheet Data Loader ........................................................... 396
29 Postload Processing 399

Processes to Run After Loading Data ................................................................................................................................. 399
Guidelines for Running Postload Processes ....................................................................................................................... 401
How You Validate Loaded Data ............................................................................................................................................ 402
Disable Postload Processing .................................................................................................................................................. 403
30 Purging Person Data from Test Environments 405

Enable the Purge Person Data in Test Environments Process ...................................................................................... 405
Disable Postload Processing .................................................................................................................................................. 406
Purge Person Data from Test Environments .................................................................................................................... 406
Tables Purged by the Purge Person Data in Test Environments Process ................................................................... 408
31 HCM Extracts and Diagnostics for HCM Data Loader and HCM 415
Spreadsheet Data Loader
HCM Data Loader Extracts ..................................................................................................................................................... 415
Seing Up HCM Data Loader Extracts ................................................................................................................................. 415
Running HCM Data Loader Extracts .................................................................................................................................... 420
Diagnostic Tests for HCM Data Loader ............................................................................................................................... 423
Diagnostic Tests for HCM Spreadsheet Data Loader ....................................................................................................... 425
32 Best Practices for HCM Data Loader and HCM Spreadsheet Data Loader 429
HCM Data Loader Best Practices .......................................................................................................................................... 429
Overview of Maintaining the Stage Tables ........................................................................................................................ 430
Example of the Automatic Deletion and Backup of Stage Table Data ......................................................................... 432
Maintain the HCM Data Loader Stage Tables ................................................................................................................... 434
Maintain the HCM Spreadsheet Data Loader Stage Tables ........................................................................................... 436
33 Time, Absence, and Pension Data for Payroll 439

Overview ..................................................................................................................................................................................... 439
Prerequisite Payroll Setup for Importing Time Entries ................................................................................................... 440
Create Elements for Time Card Entries ............................................................................................................................... 443
Import Time Card Entries to Payroll .................................................................................................................................... 445
File Format for Importing Time Entries .............................................................................................................................. 447
Integrate Absence Management with Global Payroll ....................................................................................................... 450
Dene Payroll Elements to Process Absences ................................................................................................................... 451
Importing Absence Entries to Payroll: Procedure ............................................................................................................. 454
File Format for Importing Absence Entries ........................................................................................................................ 457
Run the Load Benet Batches Process ............................................................................................................................... 459
File Format for Importing Pension Deductions .................................................................................................................. 461
34 Managing HCM Extracts 465

Extract Components ................................................................................................................................................................ 465
HCM Extract Types .................................................................................................................................................................. 466
Overview of Payroll Interface Extract Denitions .............................................................................................................. 467
Best Practices for Viewing User Entity Details .................................................................................................................. 468
User Entities in HCM Extracts ............................................................................................................................................... 469
HCM Extracts Templates ........................................................................................................................................................ 470
Dene Extracts ........................................................................................................................................................................... 471
Dene Extracts in the Simplied Interface ......................................................................................................................... 478
How Extracts are Validated .................................................................................................................................................... 484
Review Extract Run Details .................................................................................................................................................... 484
Purge Extracts Archive Information ..................................................................................................................................... 485
FAQs for Managing Extracts ................................................................................................................................................. 486
35 Filtering and Delivering HCM Extracts 491

Guidelines for Using Dierent Modes for HCM Extracts ................................................................................................. 491
Filter Extracts Using Advanced Filter Criteria .................................................................................................................... 492
HCM Extract Formula Types .................................................................................................................................................. 493
Guidelines for Delivering Extracts ........................................................................................................................................ 494
Dene the BI Publisher Template in HCM Extracts .......................................................................................................... 494
Best Practices for Delivering Encrypted Data Using HCM Extracts .............................................................................. 496
FAQs for Filtering and Delivering HCM Extracts ............................................................................................................... 496
36 Flow Paerns 501

Flow Paerns for Extracts and Reports ............................................................................................................................... 501
Checklist and Flow Tasks ........................................................................................................................................................ 501
How Flow Paerns are Edited ................................................................................................................................................ 501
Flow Paern Parameters ........................................................................................................................................................ 502
Flow Task Start and Due Dates ............................................................................................................................................ 506
Examples of Editing Flow Paerns ....................................................................................................................................... 507
Add a BI Publisher Report to a Flow .................................................................................................................................... 510
Create a Flow within a Flow .................................................................................................................................................... 511
FAQs for Flow Paerns ............................................................................................................................................................ 513
37 Benets Data Extract 515

Guidelines for Extracting Benets Data Using HCM Extracts .......................................................................................... 515
Congure Benets for Extracting Data ................................................................................................................................ 515
Valid Extract Names ................................................................................................................................................................. 518
Generate and Transmit Benet Extracts .............................................................................................................................. 519
Example of a Custom Layout for Benets Extract ............................................................................................................ 520
38 Talent Review and Succession Management Data Extract 529

Guidelines for Extracting Talent Review Data Using HCM Extracts .............................................................................. 529
Guidelines for Extracting Succession Management Data Using HCM Extracts .......................................................... 530
39 Transferring Encrypted Data 533

Set up Encryption for File Transfer ...................................................................................................................................... 533
Encrypt and Upload Files Automatically ............................................................................................................................. 535
Transfer Files Automatically from HCM Extracts with PGP Encryption ........................................................................ 536
40 Oracle Taleo Recruiting Cloud Service Integration 539

HCM and Oracle Taleo Recruiting Cloud Service Components: How They Work Together ..................................... 539
Importing Data From Oracle Taleo Recruiting Cloud Service: Explained ..................................................................... 539
Exporting Data to Oracle Taleo Recruiting Cloud Service: Explained ........................................................................... 540
FAQs for Oracle Taleo Recruiting Cloud Service and HCM Integration ........................................................................ 542
41 Web Services 543

Overview of Web Services ...................................................................................................................................................... 543
Oracle Human Capital Management Cloud Preface
Preface
This preface introduces information sources that can help you use the application.
Using Oracle Applications
Help
Use help icons to access help in the application. If you don't see any help icons on your page, click your user image
or name in the global header and select Show Help Icons. Not all pages have help icons. You can also access the Oracle
Help Center to nd guides and videos.
Watch: This video tutorial shows you how to nd and use help.

You can also read about it instead.
Additional Resources
• Community: Use Oracle Cloud Customer Connect to get information from experts at Oracle, the partner
community, and other users.
• Training: Take courses on Oracle Cloud from Oracle University.
Conventions
The following table explains the text conventions used in this guide.
Convention Meaning
boldface Boldface type indicates user interface elements, navigation paths, or values you enter or select.
monospace Monospace type indicates le, folder, and directory names, code examples, commands, and URLs.
> Greater than symbol separates elements in a navigation path.
i
Oracle Human Capital Management Cloud Preface
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website.
Videos included in this guide are provided as a media alternative for text-based help topics also available in this guide.
Contacting Oracle
Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For
information, visit My Oracle Support or visit Accessible Oracle Support if you are hearing impaired.
Comments and Suggestions

Please give us feedback about Oracle Applications Help and guides! You can send an e-mail to:
[email protected].
ii
Oracle Human Capital Management Cloud Chapter 1
Integrating with HCM Introduction to Integrating with Oracle HCM Cloud
1 Introduction to Integrating with Oracle HCM

Cloud
Overview of Integrating with Oracle HCM Cloud

This guide describes the ways in which you can integrate applications with Oracle HCM Cloud. Most of the content
describes ways of loading or extracting data.
This topic shows the scope of this guide and summarizes the contents of each chapter.
Introduction
This table describes Chapter 1.
Chapter Title Contents
1 Introduction to Integrating with Oracle An introduction to this guide and an

HCM Cloud overview of the available approaches to
data loading and extracts.

Data Loading Using HCM Data Loader

This table describes chapters related to bulk data loading with HCM Data Loader.
2 Introduction to HCM Data Loader An introduction to HCM Data Loader and

the data-loading process.

3 Data File Instructions and Delivery Valid instructions to include in data les,
how to deliver data les for upload, and
how to generate and use business-object
templates.

4 Preparing to Use HCM Data Loader Seing conguration parameters, dening

referenced objects, reviewing lists of
values, and nding business-object
information.

1
5 Data Preparation General guidance for preparing various

types of data, such as images and
aachments, to ensure successful
loading. Information about specifying the
supported key types.

6 Loading Date-Eective Data How to load date-eective objects

successfully and achieve the required
results.

7 Loading Flexeld Data How to load data for descriptive and

extensible exelds.

8 Loading Setup Objects How to load setup objects, such as

Actions, Action Reasons, Name Format,
and Person Type.

9 Loading Workers How to load components of the Worker

object.

10 Loading Worker-Related Objects How to load worker-related objects, such

as Area of Responsibility, Document
Record, and User.

11 Loading Work Structures How to load work structures, such as

Grade, Job, and Organization.

12 Loading Compensation Objects How to load compensation objects, such

as Progression Grade Ladder, Salary Basis,
and Salary.

13 Loading Payroll Relationships How to load payroll information at the

payroll relationship, payroll assignment
records, and at assigned payroll levels.

14 Loading Payroll Setup Objects How to load payroll setup objects, such
as object groups, payroll consolidation
groups, payroll denitions, time
denitions, user-dened tables, fast
formula, and elements.

15 Loading Elements and Element Entries How to load elements, which determine
the payment of base pay, benets,
absences, earnings and deductions.

16 Initializing and Adjusting Balances How to load payroll balance groups and to
initialize, and adjust balances.

2
17 Loading Payment Methods How to load banks, bank branches,

external bank accounts, and organization
and personal payment methods.

18 Loading Payroll Costing How to load payroll costing setup details

for dierent payroll accounts.

19 Loading Payroll Data Using How to use transformation formula to

Transformation Formula transform your payroll data into a format
that is supported by HCM Data Loader or
HCM Spreadsheet Data Loader.

20 Loading Talent Objects How to load talent objects, such as Goal

and Goal Plan.

21 Loading Learning Objects How to load learning objects, such as

Course, Classroom Resource, and Legacy
Learning Item.

22 Loading Absences Objects How to load absences objects, such as

Accrual Plan Enrollment and Absence
Entry.

23 Loading Benets Objects How to load benets objects, such as

Beneciary Enrollments, Person Benet
Groups, and Person Habits.

24 Importing and Loading Data Using HCM How to import and load data and correct
Data Loader any errors.

Data Loading Using Spreadsheet Loaders

This table describes chapters related to bulk data loading with spreadsheets.
25 Data Loading Using Spreadsheets An overview of the available spreadsheet

loaders and general setup requirements
for spreadsheet usage.

26 Introduction to HCM Spreadsheet Data An overview of HCM Spreadsheet Data

Loader Loader, its processing, and its access
requirements.
3
27 HCM Spreadsheet Data Loader Templates How to create, edit, copy, export, and
import spreadsheet templates.

28 Importing and Loading Data Using HCM How to generate a spreadsheet from
Spreadsheet Data Loader a template, populate the spreadsheet,
import and load the data, and x any
errors.

Postload Processing
This table lists chapters related to postload processing for bulk data loading.
29 Postload Processing for HCM Data Loader Processes that you must run after loading
specic business objects using either HCM
Data Loader or HCM Spreadsheet Data
Loader.

30 Purging Person Data from Test Processes to run in test environments to

Environments purge person and dependent data.

31 HCM Extracts and Diagnostics for HCM How to congure and run HCM extracts
Data Loader and HCM Spreadsheet Data for HCM Data Loader. How to run the
Loader HCM Data Loader Error Analysis Report
diagnostic test and the HCM Spreadsheet
Data Loader diagnostic report.

Best Practices
This table lists chapters that oer advice for your data loading eorts.
32 Best Practices for HCM Data Loader and Recommended approaches to data
HCM Spreadsheet Data Loader creation and maintenance.

4
Loading Payroll
This table lists chapters associated with loading third-party data.
33 Time, Absence, and Pension Data for Loading third-party time entries, pension
Payroll deductions, and absence information in
XML format to Oracle Global Payroll.

Extracting Data
This table describes chapters that discuss data extracts.
34 Managing HCM Extracts Using HCM Extracts to extract data from

Oracle HCM Cloud.

35 Filtering and Delivering HCM Extracts Filtering HCM Extracts data and selecting
a delivery format.

36 Flow Paerns Using ow paerns to complete extract

reports and processes.

37 Benets Data Extract Seing up benets plan carriers and

extracting benets enrollment information
into an XML le for each carrier.

38 Talent Review and Succession The user entity, database items group,
Management Data Extract and extract denition type for the Talent
Review and Succession Management data
that you can extract using HCM Extracts.

5
Transferring Encrypted Data

This table describes chapters that relate to moving encrypted data.
39 Transferring Encrypted Data How to set up data encryption. How to

upload and extract encrypted data.

Oracle Taleo Recruiting Cloud Service Integration

This table describes chapters that cover integration between Oracle Taleo Recruiting and Oracle HCM Cloud.
40 Oracle Taleo Recruiting Cloud Service How integration between Oracle Taleo
Integration Recruiting Cloud Service and Oracle HCM
Cloud is managed.

Web Services
This table lists chapters that discuss integrating web services with Oracle HCM Cloud.
41 Web Services Using web services to integrate web-based

applications with Oracle HCM Cloud.

Inbound Integrations
This topic introduces ways of developing inbound integrations to Oracle HCM Cloud.
These include:
• HCM Data Loader

• HCM Spreadsheet Data Loader
6
HCM Data Loader

Use HCM Data Loader to load data in bulk from any source to Oracle HCM Cloud.
HCM Data Loader loads:

• Complex, hierarchical data
• Large volumes of data, such as complete system extracts
• Object history
You can use HCM Data Loader for both data migration and ongoing data maintenance. Major benets of HCM Data
Loader include support for:
• Most HCM business objects
• Incremental or partial data loading
• Four types of keys to identify records uniquely
• Congured descriptive exelds and extensible exelds, translation data, tree hierarchies, person images, and
document-record aachments
HCM Data Loader provides:

• A comprehensive user interface for initiating data upload, monitoring progress, and reviewing errors
• A template le for each supported business-object hierarchy, which you can use as the basis for your own data
les
• A user interface for reviewing the structure and aributes of every supported business-object hierarchy
• A web service that you can use to automate data upload
Note: The precursor of HCM Data Loader is HCM File-Based Loader. For information, see Overview:
Transitioning from HCM File-Based Loader to HCM Data Loader (2206596.1) on My Oracle Support at hps://
support.oracle.com.
HCM Spreadsheet Data Loader

Use HCM Spreadsheet Data Loader to import data to the HCM Data Loader stage tables from spreadsheets. HCM
Spreadsheet Data Loader supports most of the business objects that HCM Data Loader supports. It oers both ease of
use and exibility. For example, you can congure spreadsheet templates to suit business needs by omiing aributes,
changing aribute order, changing aribute labels, and adding help text.
Related Topics
• Overview of HCM Data Loader
• Guidelines for Using HCM Spreadsheet Data Loader
Outbound Integrations
This topic introduces ways of developing outbound integrations from Oracle HCM Cloud.
These include:
• HCM Extracts
7
• Oracle Business Intelligence Publisher (Oracle BI Publisher)
HCM Extracts
The main way to retrieve data in bulk from Oracle HCM Cloud is HCM Extracts, which is a tool for generating data les
and reports.
HCM Extracts has a dedicated interface for specifying the records and aributes to be extracted. You:
• Identify records for extraction using complex selection criteria.

• Dene data elements in an HCM extract using fast formula database items and rules.
You manage HCM Extracts either in the Data Exchange work area or using the Checklists interface in the Payroll work
area. Alternatively, you can run extracts using the Flow Actions Service web service from outside Oracle HCM Cloud.
This feature enables you to automate the outbound extract as part of an overall integration ow.
HCM Extracts Output Formats

Using the built-in integration with Oracle BI Publisher, you can generate extracts in various formats, including CSV, XML,
Microsoft Excel, HTML, RTF, and PDF.
You can download the raw hierarchical XML from a completed extract using the Extract Actions Service web service.
Alternatively, you can download the formaed BI report (for example, the CSV le) using the BI ScheduleService. In both
cases, the output is streamed in a byte array. Therefore, any orchestration mechanism must handle this output, possibly
by means of wrapper code.
You can also generate an HCM Extract without specifying an output format at the design stage. Subsequently, you can
generate a BI report based on the extract using either Oracle BI Publisher or the BI ReportService. This technique uses a
dedicated BI data model that interfaces with the generated HCM Extracts XML.
Oracle BI Publisher
Oracle BI Publisher supports both scheduled and unplanned reporting, based on either predened Oracle Transactional
Business Intelligence analysis structures or your own data models. You can generate reports in various formats. To use
Oracle BI Publisher for outbound integrations, you generate reports in a format suitable for automatic downstream
processing, such as XML or CSV.
8
Integrating with HCM Introduction to HCM Data Loader
2 Introduction to HCM Data Loader
Overview of HCM Data Loader

HCM Data Loader is a powerful tool for bulk-loading and maintaining data. The data can be from any source. You can
use HCM Data Loader for data migration, ongoing maintenance of HCM data, and coexistence scenarios, where core HR
data is uploaded regularly. This topic introduces the main features and advantages of HCM Data Loader.
Business-Object Support
You can load business objects for most Oracle Fusion Human Capital Management (HCM) products. These products
include Oracle Fusion Absence Management, Compensation, Global Human Resources, Global Payroll, Performance
Management, Prole Management, Talent Review and Succession Management, and Workforce Management. You can
also update business objects using HCM Data Loader, regardless of how they were created.
Ease of Use
HCM Data Loader has a comprehensive user interface for loading data, monitoring progress, and reviewing any errors.
It provides real-time information for all stages of its processing. HCM Data Loader's user interface also includes detailed
information about the component hierarchies and aributes of supported business objects.
You can load data from either delimited data (.dat) les or spreadsheets. You can load most supported business objects
using either method. You can generate business-object templates to use as the basis of your own .dat les. For a
selected business-object component, the template includes every aribute, including those for congured exelds.
When using spreadsheets, you dene spreadsheet templates to suit business needs and generate spreadsheets from
those templates.
Performance
HCM Data Loader supports multithreaded processing, which enables you to upload complete data extracts without
severe performance impacts. References among objects that are processed on separate threads are managed
automatically. You can set HCM Data Loader conguration parameters to optimize processing for your environment.
You can also perform partial or incremental loads to update existing objects, thereby minimizing the related processing.
Supported Key Types

HCM Data Loader supports all of the following key types for most business objects:
• Oracle Fusion GUID

• Oracle Fusion surrogate ID
9
• Source key
• User key
As user keys and source keys are supported, knowledge of Oracle Fusion internal IDs isn't required.
Business-Object Features
HCM Data Loader supports most business-object features and requirements. For example, you can upload:
• Current and historical records for date-eective objects. You determine the amount of history to load.
• End-dated, terminated, or inactive records.
• Translated aributes in multiple languages. You specify the character set of the data le on the File Character
Set conguration parameter for HCM Data Loader.
• Descriptive exelds and extensible exelds.
• Hierarchical tree data, such as organization and department trees.
• Aachments and pictures.
• Data from multiple sources. You can include source-system references in uploaded data.
Automation
You can initiate HCM Data Loader using a web-service call, which enables you to automate data upload.
HCM Data Loader and Implementation Scenarios

You can implement Oracle HCM Cloud in either full or coexistence mode. In a coexistence implementation, you use
Oracle Fusion Talent Management or Oracle Fusion Compensation, but continue to use your existing HR applications.
For both full and coexistence implementations, you implement Oracle HCM Cloud by performing the tasks that appear
in your implementation project or for selected functional areas. This topic describes how HCM Data Loader supports
these implementation types.
Full Implementations
If you're performing a full implementation of Oracle HCM Cloud, then you can use HCM Data Loader to bulk-load any
existing HCM data at appropriate stages in the implementation. Typically, you load each type of data once only for this
type of implementation. Following successful upload, you manage your data in Oracle HCM Cloud.
10
Coexistence Implementations
In a coexistence implementation, you use Oracle Fusion Talent Management or Oracle Fusion Compensation, but
maintain your existing HR applications. For this type of implementation, you:
• Move talent data permanently to Oracle HCM Cloud, which becomes the application of record for talent data.
• Upload other types of data, such as person records, periodically to Oracle HCM Cloud. The source system
remains the application of record for this data.
To implement an HCM coexistence scenario, for any source system, you can use HCM Data Loader for data upload.
Follow the general instructions provided for HCM Data Loader. Oracle doesn't supply tools to extract data from your
source systems. Work with your implementation partner or develop your own process for extracting the source data.
HCM Data Loader provides a Compensation Changes extract. You can extract assignment, bonus, and salary changes
for a specied compensation run if you're using Oracle Fusion Compensation in a coexistence scenario.
How Data Is Loaded Using HCM Data Loader

This topic outlines the process of loading data in bulk from .dat les using HCM Data Loader. The data can be from any
source.
11
This gure provides a high-level summary of the process.
HCM Data Loader
To WebCenter Content
Import
Stage Tables
Import Errors
Load Errors
Load
Application Tables
The steps of this process are:

1. You place a .zip le containing your .dat les on the Oracle WebCenter Content server.
2. You submit a request to HCM Data Loader to import and load the .zip le. For this step, you can use either the
HCM Data Loader interface or the HcmCommonDataLoader web service.
3. HCM Data Loader decompresses the .zip le and imports individual data lines to its stage tables. In the stage
tables, related data lines are grouped to form business objects.
Any errors that occur during the import phase are reported on the HCM Data Loader interface.
4. HCM Data Loader calls the relevant logical object interface method (delivered in product services) to load valid
objects to the application tables.
Any errors that occur during the load phase are reported in the HCM Data Loader interface.
5. You review any errors from the import and load phases. You can perform this step either on the HCM Data
Loader interface or using the HCM Data Loader Data Set Summary extract.
6. You correct errors from the import and load phases in your source data.
7. You load a new .zip le containing the corrected data to the WebCenter Content server.
You repeat this process from step 2 until all of the data is successfully loaded.
Tip: You can also correct load errors interactively on the HCM Data Loader interface and resubmit any
corrected data from there.
12
Related Topics
• How Data Is Uploaded Using HCM Spreadsheet Data Loader
Supported Key Types

When planning to integrate data from one system to another, you must select key types to identify records uniquely.
This topic introduces the key types that HCM Data Loader supports.
What Keys Identify

In HCM Data Loader, you use unique keys to identify:
• The record that you're creating or updating.
• The parent of the record that you're creating or updating.
The parent record may either be in the same data le or exist already in Oracle HCM Cloud.
• Any objects referenced by the record that you're creating or updating.
Supported Key Types

HCM Data Loader supports the following key types, which you can use for all types of object references. When more
than one key value exists for an object, key references are resolved in this order:
1. Oracle Fusion Globally Unique Identier (GUID)
2. Source key
3. Oracle Fusion surrogate ID
4. User key
If you supply multiple key values, then no cross-validation occurs. For example, if you supply both a GUID and a source
key, then the GUID is used and the source key is ignored. If the source key identies a dierent record from the GUID,
then no error is raised.
Tip: Whenever possible, use source keys for both creating and updating business objects.
Key-Type Features
The following table summarizes the main features of the available key types. The Create and Update columns indicate
whether you can use the key type when creating and updating objects.
Key Type Create Update Held on Object Type Generated

Automatically
GUID No Yes No Hexadecimal Yes

Surrogate ID No Yes (see note) Yes Numeric Yes

13
Key Type Create Update Held on Object Type Generated

Automatically
Source Key Yes Yes No Alphanumeric Conditionally (see

note)

User Key Yes Yes (see note) Yes Alphanumeric No

Note: You can use surrogate IDs when updating objects, but the IDs may not be readily available to Oracle
HCM Cloud users. Default source keys are generated only if you don't supply a source key when creating an
object. You can't use user keys alone when updating some objects because their values are subject to change.
Keys that aren't held on the object exist in the Integration Key Map table.
Foreign-Object References
Oracle Fusion GUIDs and surrogate IDs are generated only when the associated record is successfully created in Oracle
HCM Cloud. Source keys aren't recognized in Oracle HCM Cloud until the associated record exists in Oracle HCM Cloud.
Therefore, before you aempt to load data that references foreign objects, you must ensure that those foreign objects
exist in Oracle HCM Cloud. For a new implementation, you're recommended to load each business object separately
and ensure that it loads successfully before importing the next. If you supply all business objects in the same .zip le,
then HCM Data Loader loads them in order of dependency. In this case, a reference to a foreign object fails only if the
referenced object failed to load.
Source Keys
A source key is the ID that identies a business object in its source system. Source keys are supported only for
integration-enabled business objects. You can use source keys when creating or updating business objects. You're
recommended to use source keys for all implementations but particularly for ongoing integrations, where data is
maintained in the source system.
Source-Key Structure
A source key has the two components shown in this table.
Component Description
Source-system owner Identies where the data originated.

Source-system ID ID used in the source system. The ID must be unique for the business-object component and
source-system owner.

Having a source-system owner component to the key enables you to upload data from multiple source systems for the
same business objects. For example, you may have person data in both US and UK databases to combine in one Oracle
14
HCM Cloud system. The source-system ID doesn't have to be unique across both source systems. It must be unique
only for the business-object component and source-system owner.
If you don't have an obvious source-system ID for a record, then you can generate or derive one. For example, you
could derive a source-system ID for a person address by concatenating the person number with the address type.
Source keys aren't held against the created record. They exist in the Integration Key Map table.
Source Keys for Date-Eective Business Objects

If you're supplying date-eective history for an object, then you must supply the source system IDs for every date-
eective record in the le. The values must be the same for each line of the date-eective history.
Default Source Keys

If you provide no source key when creating an object, then the source key is created automatically. The default source-
system owner is FUSION and the default source-system ID is the surrogate ID. You can update the source key later
using the Source Key business object. In the Source Key business object, you supply the new source key and a reference
to the object that you're updating.
Source-System Owner Values

The source-system owner value is validated against the HRC_SOURCE_SYSTEM_OWNER lookup type. You must add
your source-system names to this lookup type before loading data using source-system references. Use the Manage
Common Lookups task in the Setup and Maintenance work area to update HRC_SOURCE_SYSTEM_OWNER.
User Keys
Most Oracle HCM Cloud business objects, regardless of whether they're enabled for integration, have one or more
aributes that make up a user key. The user key, which is also known as a natural key, is always visible on the user
interface.
For example:
• The user key for an organization is the organization name.
• The user key for an area of responsibility is the responsibility name plus the person number.
When to Use User Keys

User keys are part of the business object denition. They're always required when you create a logical object, regardless
of how you create it.
You can also use user keys when updating logical objects. However, the value of a user key can change, and some user-
key aributes are translatable. For this reason, you can't update some business objects if you supply only user keys to
reference them. Therefore, whenever possible, you're recommended to use source keys when updating objects.
User keys are recommended when:

• You're referencing or maintaining an object that wasn't created with a source key.
• The source-key value is unknown.
15
User Keys for Child Objects

When a business object is bound by another, the user key must include the user key for its parent. For example:
• Jobs are always part of a set. Therefore, job code alone doesn't uniquely identify a job. Instead, the set code
must be part of the user key for a job.
• Job grades apply to a specic job. Therefore, the user key for a job grade must include both the user key for
the grade and the user key for the parent job. Therefore, the user key for the job grade is made up of the grade
code, job code, and set code.
Oracle Fusion GUIDs and Surrogate IDs

Oracle Fusion Globally Unique Identiers (GUIDs) and surrogate IDs are two of the four types of keys that HCM Data
Loader supports. This topic describes when you can use GUIDs and surrogate IDs to identify business objects uniquely.
Oracle Fusion GUIDs

When you create an integration-enabled business object in Oracle HCM Cloud, a GUID is generated for the object
automatically. As the GUID is generated when you create the business object, it's suitable only for identifying business
objects that already exist. You can't supply a GUID when creating a business object. The GUID, a hexadecimal value, isn't
held on the created object but exists in the Integration Key Map table.
GUIDs are useful when you share changes with down-stream applications, such as third-party payroll providers. You
extract the changes for the third-party payroll and provide the GUID as the unique key to the worker. When reporting
any updates back to Oracle HCM Cloud, you can use GUIDs to identify the records to update.
Oracle Fusion Surrogate IDs

The surrogate ID, a numeric value, is the internal system identier that's generated when you create a business
object. All objects, including those that aren't integration-enabled, have surrogate IDs. The surrogate ID is held on the
object. The ID is also used in the Integration Key Map table to provide a mapping for GUID and source-key values. As
the surrogate ID isn't generated until the object is created, you can't use this value when creating objects. Access to
surrogate IDs may also be limited. On-premises customers are more likely to have access to surrogate IDs than Oracle
HCM Cloud customers.
Business-Object Structure
Each Oracle HCM Cloud business object is a hierarchy of business-object components. At the top of the hierarchy is
the parent component, and beneath it may be child and grandchild components. Each business-object component has
multiple aributes.
16
This gure shows a generic business-object structure.
Parent Component
Parent Component
Attributes
Child Component
Child Component
Attributes
Child Component
Child Component
Attributes
For example, the Rating Model business object includes Rating Model, Rating Level, and Rating Category components.
The Rating Model component is the parent of the other two components. Each component has aributes such as
RatingName, RatingModelCode, RatingLevelCode, and so on.
The most complex business object supported by HCM Data Loader is the Worker object, where ve levels exist in
the object hierarchy. These range from the Worker component at the top to Assignment Work Measure, Assignment
Manager, Assignment Grade Steps, and Assignment Extra Information at the boom. By contrast, the Person Type
object has only the Person Type component.
Terminology
This table denes the terms used by HCM Data Loader to refer to business objects.
Term Meaning
Object or business object Refers to the complete object, which is the parent component and all child components. For
example, Grade and Worker are business objects.

Component or business-object Refers to components of a business object. For example, Person Name and Work Relationship
component are components of the Worker object.

Logical object Refers to a group of related components that form one occurrence of a business object. For
example, the grade IC1 is a logical object.

17
Loading Logical Objects

When you deliver multiple components for the same business object together, HCM Data Loader groups them and
loads the complete logical object. It doesn't process the components separately. If any component of the logical object
fails validation, then the whole logical object is rejected. As HCM Data Loader loads only complete logical objects,
you can be sure of exactly which data has been loaded. For example, when loading jobs, you know which jobs loaded
successfully and which jobs failed to load.
Integration-Enabled Objects
HCM Data Loader can load any integration-enabled business object. An integration-enabled business object supports
these four key types:
• Oracle Fusion GUID

• Oracle Fusion surrogate ID
• Source key
• User key
An integration-enabled object has an entry in the Integration Key Map table, where its GUIDs and source keys exist.
HCM Data Loader can also load a few objects, such as Department Tree, that aren't integration enabled. Typically,
Oracle HCM Cloud doesn't own such objects and they support neither source keys nor GUIDs.
Tip: You can review business-object details on the View Business Objects page. The Integration Keys
Supported eld on the Component Details tab for a selected component indicates whether the component is
integration enabled.
Related Topics
• Sources of Business-Object Information
FAQs for Introduction to HCM Data Loader

Why can't I access HCM Data Loader?
You may not have the correct permissions. You must have the Human Capital Management Integration Specialist job
role or privileges to access HCM Data Loader.
18
Integrating with HCM Data File Instructions and Delivery
3 Data File Instructions and Delivery
HCM Data Loader Data and .zip Files

You use .zip les to load data with HCM Data Loader. Each .zip le can contain one or more data (.dat) le. Each le
includes data for a single business object, such as Location, Grade, Worker, or Salary. Your data le has the name of a
business object that's specied by HCM Data Loader, such as Job.dat or Worker.dat. In any .zip le, you supply data les
only for the business objects that you're loading.
This gure shows an example .zip le structure. The .zip le contains no folders for data (.dat) les.
You dene the name of the .zip le, which must be in alphanumeric characters (a-z, A-Z, and 0-9). The .zip le can be
encrypted as a whole, but HCM Data Loader doesn't support the encryption of individual data les.
BlobFiles and ClobFiles Folders in the .zip File

The only two folders that can appear in the .zip le are:
• BlobFiles, which is for binary large objects

• ClobFiles, which is for character large objects
You use these folders for les you want to load as aachments or into large objects. The le names of these
aachments or images must be in alphanumeric characters (a-z, A-Z, and 0-9). The data type of the aribute that's
used to load your aachment or large-object data determines which folder to use. For example, the File aribute in the
Document Record object is used for loading aachment les and has a data type of BLOB. Therefore, you place les to
be loaded as aachments to document records in the BlobFiles folder.
19
This gure shows a .zip le structure when aachments are included.
This gure shows the contents of the BlobFiles folder.
Data Files
Each HCM Data Loader data le is specic to a business object. You provide all components that you want to load for
a business-object hierarchy in the same data le. For example, you provide Job, Job Valid Grade, Job Evaluation, Job
Extra Information, and Job Legislative Extra Information components in Job.dat. This approach lets you to see all data
for a business object and supports the validation of parent references on all child components. It also simplies the
construction of the .zip le, as separate directories aren't required and fewer data les have to be generated.
Tip: You can generate data-le templates for all supported objects on the View Business Objects page. Each
template denes the complete structure of the selected object.
Third Party Data Files

You can use third party .zip les to load data with HCM Data Loader, such as pay slips that were generated by a payroll
application. The data le must conform to the requirements for the business object you want to load, and the .zip
le must have been compressed with java.util.zip. If not, then you must extract the les and compress again using
java.util.zip for the load to work properly.
Related Topics
• How You Load Images, Aachments, and Large Strings
20
File Line Instructions and File Discriminators

Each line in a data le begins with an instruction, and most lines include a le discriminator. This topic introduces the
available instructions and describes the le discriminators.
File Line Instructions

This table identies the instructions that can appear in an HCM Data Loader data le.
Instruction Line Type Description
METADATA Denition Identies the business-object component

and the aributes of that component for
which you're including values in the data
le

MERGE Data Provides data to be merged in Oracle HCM

Cloud

DELETE Data Identies a business-object component to

be purged from Oracle HCM Cloud

SET Control Overrides aspects of the default

processing for a le

COMMENT Comment Adds a comment to the data le

File Discriminators
METADATA, MERGE, and DELETE lines must include a le discriminator value, which identies the business-object
component to which the instruction applies. For example, the available le discriminators for the Job business object
are shown in this table.
Business-Object Component File Discriminator
Job Job

Job Valid Grade JobValidGrade

Job Evaluation JobEvaluation

21
Business-Object Component File Discriminator
Job Extra Information JobExtraInfo

Job Legislative Extra Information JobLegislative

The le discriminator appears immediately after the instruction in a le line. HCM Data Loader templates for a business
object include the le discriminator for each of the object's components. This example shows instructions, the le
discriminator, aribute names, and aribute values for the Job business object.
METADATA|Job|EffectiveStartDate|EffectiveEndDate|SetCode|JobCode|Name
MERGE|Job|1950/01/01|4712/12/31|COMMON|CFO|Chief Financial Officer
MERGE|Job|1950/01/01|2013/01/01|COMMON|PM|Manager Projects
MERGE|Job|2013/01/02|4712/12/31|COMMON|PM|Manager Projects
MERGE|Job|1950/01/01|4712/12/31|COMMON|VP_OF_HR|VP Human Resources
MERGE|Job|1950/01/01|4712/12/31|COMMON|PROG_MGR|Program Manager
In this example:
• The instruction, METADATA or MERGE, appears at the start of the line.
• The discriminator on all lines is Job.
• Aribute names appear in the METADATA line after the Job discriminator and separated by the vertical bar
character (|).
• Aribute values appear in MERGE lines after the Job discriminator and separated by the vertical bar character
(|).
The METADATA Instruction

The METADATA instruction in an HCM Data Loader data le identies a business-object component and its aributes.
The aributes are those for which you're including values in the data le.
Instruction Format
The METADATA line has this format:
METADATA|<DISCRIMINATOR>|<ATTRIBUTE 1>|<ATTRIBUTE 2>|<ATTRIBUTE n>
For example:
METADATA|Job|SetCode|JobCode|JobFamilyName|JobName|EffectiveStartDate|EffectiveEndDate
Restrictions
These restrictions apply to the METADATA instruction:
• The METADATA line must appear before the MERGE or DELETE data line to which it relates.
• You can include multiple METADATA lines in a single data le. However, each line must be for a dierent
business-object component. For example, in a Job.dat le, you can include METADATA lines for the Job and
Job Valid Grade components. However, you can't include two Job METADATA lines.
22
Validation
Each METADATA line must:
• Include a valid discriminator for the object that's identied in the data le name. For example, in a Job.dat le,
the METADATA line must include one of these discriminators: Job, JobGrade, JobEvaluation, JobExtrainfo, and
JobLegislative.
• Be unique in the le. That is, you can't provide multiple METADATA lines for the same discriminator in a single
data le.
For example, having two METADATA lines for the JobGrade discriminator in the same data le is invalid.
• Include only valid aributes for the discriminator. Aribute names are case-sensitive, but they can appear in
any order.
• Include the aributes for at least one of the supported key types. For example, if you're using source keys to
identify a record uniquely, then you must include SourceSystemOwner and SourceSystemId aributes in the
METADATA line.
HCM Data Loader business-object templates include METADATA lines with all available aributes for each component
of a business object.
The MERGE Instruction

The MERGE instruction identies a data line. You use the MERGE instruction whether creating or updating objects, and
HCM Data Loader identies the correct action.
You can supply either partial or complete objects using the MERGE instruction. The data supplied on the MERGE line is
merged into existing Oracle HCM Cloud data. The order in which you specify MERGE lines isn't necessarily the order in
which HCM Data Loader processes them.
Instruction Format
The MERGE line has this format:
MERGE|<DISCRIMINATOR>|<ATTRIBUTE 1>|<ATTRIBUTE 2>|<ATTRIBUTE n>
For example:
MERGE|Job|SE|Software Engineer|Common|2015/01/01|4712/12/31
Restrictions
These restrictions apply to the MERGE line:
• You must not supply multiple MERGE lines for the same component in a single data le, unless the object is
date-eective. For example, you can't supply two MERGE lines, one to create a Person Ethnicity component and
one to update it, in the same data le. As the component isn't date-eective, these instructions would correct
the data rather than update it. In such cases, you can supply only current data. Alternatively, you can create the
record in one data le and update it in a dierent data le.
23
Note: HCM Data Loader doesn't process individual le lines, but groups related lines. This grouping
works for date-eective records because the le lines are processed in order of eective start date.
• You can include MERGE and DELETE instructions in the same le, but not for the same logical record. For
example, you can't load multiple date-eective records for the same component, such as a single Job, using a
mix of MERGE and DELETE instructions. However, you can provide both MERGE and DELETE instructions for
components of a single logical object. For example, you can provide:
◦ MERGE instructions for Worker and Person Name

◦ DELETE instructions for the Person Email and Person Phone components of the same Worker object
Validation
Each MERGE line must:
• Be preceded by the METADATA line for the same discriminator.
• Contain the same aributes as the relevant METADATA line and in the same order.
• Not include values for aributes that aren't in the METADATA line.
• Contain a unique identier for itself, using any of the supported key types. In addition, each data line for a child
component must include a unique reference to its parent. For example, GradeRateValue must include a unique
reference to its associated GradeRate.
The DELETE Instruction

The DELETE instruction identies a business-object component to purge from Oracle HCM Cloud. The component
doesn't have to have been loaded using HCM Data Loader.
Instruction Format
The DELETE instruction has this format:
DELETE|<DISCRIMINATOR>|<ATTRIBUTE 1>|<ATTRIBUTE 2>|ATTRIBUTE n>
For example:
METADATA|JobFamily|EffectiveStartDate|EffectiveEndDate|JobFamilyName
DELETE|JobFamily|2012/10/01|4712/12/31|Sales01
Restrictions
These restrictions apply to the DELETE instruction:
• You can delete a business object or a component of a business object. However, you can't delete individual
date-eective records.
• You can't provide MERGE and DELETE instructions for the same record in a single data le. The order in which
HCM Data Loader processes instructions is unpredictable.
• You can't recover deleted records. Therefore, try to correct data rather than delete and recreate it.
24
• Not all business-object components can be deleted. For information about deletion support, see the business-
object details available from the View Business Objects page in the Data Exchange work area.
The SET Instruction

The SET instruction is optional in a .dat le and has no discriminator. You use SET instructions to alter default
processing for the le in which they appear. You can include any number of SET instructions in a .dat le, but they must
appear before the rst METADATA line. This topic describes when to use the SET instruction.
This table lists the SET instructions and their default values.
Instruction Default Value
SET PURGE_ FUTURE_CHANGES Y|N Y

SET DISABLE_ POST_ PROCESS_ Not applicable

TASKS <process>

SET INVOKE_ POST_PROCESS Y|N Y

SET FILE_ DELIMITER <delimiter> Vertical bar (|)

SET FILE_ESCAPE <escape Backslash (\)

character>

SET FILE_NEWLINE <newline n

character>

SET ENABLE_ AUDIT_DATA Y|N N

SET PURGE_ AUDIT_DATA Y|N N

SET CALCULATE_FTE Y|N N

SET CREATE_ DEFAULT_ WORKING_ N

HOUR_ PATTERN Y|N

Tip: The default values shown here are predened for the enterprise. You can override these values for the
enterprise using the Congure HCM Data Loader task in the Setup and Maintenance work area.
25
SET Instruction Descriptions

This section provides an alphabetic list of all SET instructions with their descriptions.
SET CALCULATE_FTE
To request automatic calculation of full-time equivalent (FTE) values for all worker assignments in a Worker.dat le,
include the SET CALCULATE_FTE instruction. For example:
SET CALCULATE_FTE Y
SET CREATE_DEFAULT_WORKING_HOUR_PATTERN
To request automatic creation of a default working-hour paern for all worker assignments in a Worker.dat le, include
the SET CREATE_DEFAULT_WORKING_HOUR_PATTERN instruction. For example:
SET CREATE_DEFAULT_WORKING_HOUR_PATTERN Y
SET DISABLE_POST_PROCESS_TASKS
By default, these processes run automatically after you load workers:
• Refresh Manager Hierarchy

• Update Person Search Keywords
To prevent Refresh Manager Hierarchy from running automatically, you can include this SET instruction in the
Worker.dat le:
SET DISABLE_POST_PROCESS_TASKS RefreshManagerHierarchy
To prevent Update Person Search Keywords from running automatically, you can include this SET instruction in the
Worker.dat le:
SET DISABLE_POST_PROCESS_TASKS UpdatePersonSearchKeywords
By default, the FlaenPositionHierarchy process runs automatically after you load HCM position hierarchies. To
prevent FlaenPositionHierarchy from running automatically, include this SET instruction in the PositionHierarchy.dat
le:
SET DISABLE_POST_PROCESS_TASKS FlattenPositionHierarchy
Tip: To prevent postload processes from running automatically, you can use the SET
INVOKE_POST_PROCESS instruction instead.
SET ENABLE_AUDIT_DATA
Audit of objects loaded using HCM Data Loader is enabled or disabled for the enterprise using the Enable Audit
Data conguration parameter. You can override the enterprise seing for individual .dat les by including this SET
instruction. For example, if audit is enabled for the enterprise, then you can disable it for an individual .dat le.
SET FILE_DELIMITER
Use this instruction to change the default le delimiter, which is the vertical bar (|). For example, to change it to a
comma, include this instruction:
SET FILE_DELIMITER ,
26
The new value can be up to 10 characters.
SET FILE_ESCAPE
Use this instruction to change the default le escape character, which is the backslash (\). For example, to change it to
the equal sign (=), include this instruction:
SET FILE_ESCAPE =
SET FILE_NEWLINE
Use this instruction to change the default le newline character, which is the character n. For example, to change it to
the string newline, include this instruction:
SET FILE_NEW_LINE newline
SET INVOKE_POST_PROCESS
By default, these processes run automatically after you load workers:

By default, the FlaenPositionHierarchy process runs automatically after you load HCM position hierarchies.
To prevent such processes from running automatically, you can include this SET instruction in the relevant .dat le:
SET INVOKE_POST_PROCESS N
SET PURGE_AUDIT_DATA
Use this instruction to purge the audit data for the objects in a .dat le. This feature is intended primarily to remove the
audit records for personally identiable information in worker records.
You can't include both of the following instructions in a single .dat le:
• SET ENABLE_AUDIT_DATA Y
• SET PURGE_AUDIT_DATA Y
If auditing of loaded objects is enabled for the enterprise, then you must disable it in any .dat le where you're purging
audit data. That is, you include the following instructions:
• SET ENABLE_AUDIT_DATA N
• SET PURGE_AUDIT_DATA Y
SET PURGE_FUTURE_CHANGES
When you create business objects containing date-eective components, you include this instruction at the start of the
le:
SET PURGE_FUTURE_CHANGES Y
This instruction sets the date-eective maintenance mode to Replace. In this mode, which is the default mode, the
contents of the .dat le replace any existing data.
27
When you update business objects containing date-eective components, you include this instruction at the start of the
le:
SET PURGE_FUTURE_CHANGES N
This instruction sets the date-eective maintenance mode to Retain. In this mode, any existing future-dated changes
are retained.
Related Topics
• How You Manage Reserved Characters
• Overview of Loading Date-Eective Objects
• Enable Audit for Oracle HCM Cloud Business Objects
• HCM Data Loader Conguration Parameters
Generate and Use Template Files

HCM Data Loader provides a template le for each supported business-object hierarchy. The template contains:
• A COMMENT line, which identies the business object, its version, and the le-creation date.
• A METADATA line for each component of the business-object hierarchy that you can load for the business
object. The METADATA line includes every aribute of the component, including environment-specic
congured exeld aributes.
You can generate template les and use them as the basis of your own data les. The topic describes how to generate
and use template les.
Generate a Single Template File

Follow these steps:
1. Open the Data Exchange work area and select the View Business Objects task on the Tasks panel tab.
By default, the View Business Objects page lists all business objects that HCM Data Loader supports. You can
sort the list by product area, business object, or load order, for example. You can also retrieve a specic object
by entering its name in the Business Object query-by-example eld and pressing Enter.
2. If a template already exists for the object, then you can click the icon in the File column to download it.
The Last Refreshed column shows when the object denition was last updated and the template was last
generated. Alternatively, you can update the object denition before you download the template, as follows:
a. Select the object row in the business objects table.
b. Click Refresh Object.
c. In the Schedule Request dialog box, click Submit. Click OK to close the conrmation message.
When you click Submit, you start the process that updates the object denition and generates the latest
template le.
Tip: To monitor progress, click View Process Results to open the View Process Results
page.
3. On the View Business Objects page, click the Refresh icon.
28
Check the value in the Last Refreshed column to conrm that the template has been updated.
4. Click the icon in the File column to download the template.
Tip: You can download the complete object denition for oine use. To download the object denition, click
the icon in the Download column. The spreadsheet that you download is documentation for the object, not a
template le.
Generate Template Files for All Business Objects

Follow these steps to generate template les for all business objects in a product area or all business objects:
1. Click the Refresh All Objects buon on the View Business Objects page.
2. In the Schedule Request dialog box, you can either select a product area or leave Product Area set to All.
3. Click Submit.
4. When the generation process completes, you can download templates individually. Click the icon in the File
column for an object on the View Business Objects page. Alternatively, follow these steps to download a
single .zip le of the generated templates:
a. Click View Process Results.

b. On the View Process Results page, click the icon in the File column for your process.
Use Template Files

Template les identify the names of all available aributes of a business object, including those of environment-specic
aributes, such as exeld segments. Don't simply copy the METADATA lines from the template le and use them in
your own data les. Instead, include in your data les:
• METADATA lines for the components that you want to load

• Aribute names for the values you want to supply
You can improve the speed and eciency of the import and load processes by including only the aributes for which
you're supplying data. Remove METADATA lines and aribute names that you don't plan to use.
HCM Data Loader validates every aribute name on every METADATA line. It also identies any potential dependencies
on other business objects in the same .zip le by reviewing the aributes supplied in the METADATA lines. For example,
the Job.dat le may contain a METADATA line for the Job Valid Grade component with the Grade ID aribute. In this
case, HCM Data Loader assumes that the Job.dat le has a potential dependency on grades.
FAQs for Data File Instructions and Delivery

How should I deliver data when creating objects?
Deliver one object per .zip le. For example, create one .zip le for jobs, one for workers, and so on. Correct any errors
before loading the next object to avoid data-reference errors.
29
How should I deliver data for incremental updates?

Supply only changed and required aribute values. Deliver all business-object les in the same .zip le. HCM Data
Loader processes them in the correct order and loads referenced data before the data that references it.
Can I include comments in a .dat le?

Yes. Use the COMMENT instruction to add a comment to a .dat le.
For example:
COMMENT Data for Business Object: Job Version: V2 Created on: 25-03-2017
You can include any number of COMMENT instructions and they can appear anywhere in the le. They have no eect
on processing.
30
Integrating with HCM Preparing to Use HCM Data Loader
4 Preparing to Use HCM Data Loader
Sources of Business-Object Information

To load a business object or component successfully using HCM Data Loader, you must understand its structure,
supported key systems, data formats, and required aributes. You must also understand any business rules that apply
to the object. This topic identies where you can nd this information.
Business-Object Details
When you click the name of a business object on the View Business Objects page, you access information about the
object. This information includes:
• The component hierarchy of the object.

• Component details for the currently selected component. These include:
◦ Its parent component, le discriminator, .dat le, and translation object
◦ Whether it supports integration keys
◦ Its supported actions, for example, whether you can delete the component
◦ Whether it's date eective and, if so, whether you can change the component's rst start date and last
end date
• Aribute details for each aribute of the currently selected component. These include:
◦ Its name, type, and length

◦ Whether it's required always or for new objects only
◦ Whether it's a key value or can be used as a key value and, if so, the key type
◦ For aributes that are keys of type surrogate ID, parent surrogate ID, or foreign-object reference, whether
integration keys are also supported
◦ The names of any user-key aributes that you can use in place of surrogate IDs
◦ Names of lookup types, for aributes that are lookup-validated
If you can load exelds for the component, then the Flexeld Aributes tab appears. For descriptive exelds and
extensible exelds, you can see the aributes for a selected exeld and context. For extensible exelds, category
also appears. When a exeld context supports multirow entries, one or more exeld aributes are identied as user
keys to reference a single record uniquely. These aributes are identied in the User Key column on the Flexeld
Aributes tab. This column doesn't appear if the exeld doesn't support multirow entries.
You can refresh business objects using the Refresh Object icon and the Refresh All Objects buon. When you refresh
an object:
• Aribute and exeld information for the selected business objects is updated.
• Up-to-date templates of METADATA lines are generated for the selected business objects.
31
You're recommended to refresh all objects after an update. The refresh ensures that any changes from the update
appear on the View Business Objects page and in object templates. If no details exist for a selected object when you
view it, then you're prompted to refresh the object.
You can download the complete denition of an object for oine use by clicking the icon in the Download column for
the object. The default le name of the downloaded spreadsheet is GenericBusObjDetails.xlsx, but you can change the
name when you save the le.
Tip: Whenever you open a downloaded spreadsheet, you're invited to sign in again. If you sign in, then the
spreadsheet is updated automatically with latest information as you select each tab. These updates overwrite
any changes that you may have made to the spreadsheet. If you prefer to keep your changes, then don't sign
in.
Business Rules
Business rules for many objects are included in the Integrating with Oracle HCM Cloud guide. For objects that aren't
described in the Integrating with Oracle HCM Cloud guide, see HCM Data Loader: Business Object Documentation
(2020600.1) on My Oracle Support at hps://support.oracle.com. This document also provides aribute descriptions
and example .dat les for some business objects.
Example .dat les for many business objects are also available on Cloud Customer Connect. Select Navigator >
Others > Cloud Customer Connect. After signing in, select the HCM Cloud Integrations forum on the Human Capital
Management page.
Other documents on My Oracle Support provide information about business objects for specic localizations. Many are
linked from the document All White Papers for Oracle Fusion HCM (1504483.1). For example:
• Oracle Fusion HCM: HCM Address Validation (2140848.1)
• Oracle Fusion HCM: Person Name Validation (2146270.1)
• Validating National Identiers in Oracle Fusion Human Capital Management (2159758.1)
Related Topics
• HCM Data Loader: Business Object Documentation (2020600.1)
HCM Data Loader Conguration Parameters

The HCM Data Loader conguration parameters control the HCM Data Loader and HCM Spreadsheet Data Loader
import and load processes. The default seings of the parameters suit most requirements. However, you can override
these seings to suit the conguration of your environment and the amount of data being loaded. Users can also
override most enterprise seings for individual load processes.
In the Setup and Maintenance work area, use the following to review or override the predened seings for the
enterprise:
• Functional Area: HCM Data Loader
• Task: Congure HCM Data Loader
On the Congure HCM Data Loader page, select the HCM Data Loader tab. You can lter the parameters by these
category values:
• Availability
32
• Diagnostics
• File Denition
• Performance
• Scheduling Default
Parameters that are specic to a business object appear in a separate section. This topic describes each of the
conguration parameters within its category. Object-specic parameters are described following the category sections.
Note: HCM Spreadsheet Data Loader has its own versions of some conguration parameters, which you
manage on the HCM Spreadsheet Data Loader tab. For these parameters, you can set dierent default values
for HCM Data Loader and HCM Spreadsheet Data Loader. Users can override the HCM Spreadsheet Data
Loader default values in spreadsheet templates.
Availability Parameters
Enable Audit Data
Species whether audit data is captured for business objects loaded using HCM Data Loader. If you set this parameter
to Yes, then audit must also be enabled for Oracle Fusion Applications.
You can set this parameter separately for HCM Data Loader and HCM Spreadsheet Data Loader.
Default Value: No
Enable Load Group Size Calculation
Species whether the load-group size is to be calculated automatically. Set to Yes to enable the optimal load-group size
to be calculated based on the number of objects to process and the available concurrent threads. When Enable Load
Group Size Calculation is Yes, the Load Group Size parameter doesn't appear on the Schedule Request page. Also, the
default value of the Load Group Size parameter is ignored.
Default Value: Yes
Enable UI Message Translation
Species whether messages on the Import and Load Data page are to appear in the language of the signed-in user. Set
to Yes to enable translated messages. If this parameter is set to No, then messages appear in the language of the user
who submied the import and load request.
Default Value: No
Generate Business Object Mapping Files
Species one of three options for generating Business Object Mapping Files. The mapping le describes the HCM Data
Loader shape and you can import this into Oracle Integration Cloud to dene transformation and mappings rules.
The default value of No means you haven't enabled the option to generate mapping les.
The Custom only value lets you generate mapping les for business object dat les you upload to HCM Data Loader.
Only the aributes included in the uploaded le will be included in the mapping le. Under the Parameters section,
select the Generate Objects Mapping File feature. Refresh the Business Objects task bar until the Download Mapping
File link activates and then you can retrieve the map.
A parameter value of Yes lets you request a mapping le from the Import and Load Data interface, just like Custom
only. In addition, on the View Business Objects page, you can Refresh an individual object and it will automatically
33
generate a mapping le for you. Refresh the page until Last Refreshed indicates today's date. Download the mapping
le using the link under Integration Mapping File.
Default Value: No
HCM Data Loader Scope
Species whether HCM Data Loader is used for all data loading.
From Release 10, the default value of the HCM Data Loader Scope parameter is Full for new customers only. You can't
change this seing.
For existing customers upgrading from Release 9, the default value of this parameter is Limited. If you set it to Full,
then you can't change the seing back to Limited.
Default Value: Full
Purge Person Enabled Key
Key value supplied by Oracle Support to enable the Purge Person Data in Test Environments process.
You can't enable and run this process in production environments.

Default Value: None
Diagnostics Parameters
Complex Error Stack Trace Occurrences by Thread
Maximum number of complex error message occurrences on a processing thread for which stack trace is recorded.
Default Value: 5
Data Error Stack Trace Occurrences by Thread
Maximum number of data error message occurrences on a processing thread for which stack trace is recorded.
Default Value: 2
File Denition Parameters

Data Set Name
For data loads initiated by web service, species whether the Oracle WebCenter Content document title or the .zip le
name is used as the data set name.
Default Value: File name
File Character Set
Character set used for business object and aachment les.

Default Value: UTF-8
File Delimiter
A value of up to 10 characters used to separate aribute names on METADATA lines and aribute values on data lines.
Default Value: Vertical bar (|)
34
File Encryption
Default le encryption.

Default Value: None
File Escape Indicator
A value of up to 10 characters used to indicate that the next character is to be ignored on data lines.
Default Value: Backslash (\)
File New Line Indicator
A value of up to 10 characters used to indicate a new line in an aribute value. This value must be preceded by the le
escape indicator.
Default Value: n
Flexelds Enabled
Controls whether exeld data can be loaded.

Default Value: Yes
Purge Audit Data
Species whether audit data is to be purged automatically for objects successfully updated or deleted.
Default Value: No
Note: You can't override the default value for the enterprise. You can include a SET instruction in
individual .dat les to purge audit data for the objects in the les.
Performance Parameters
Days to Retain Data Sets Before Archiving
The number of days since a data set was last updated before it can be automatically backed up in archive stage tables.
Qualifying data sets are backed up only if the number of data lines in the stage tables exceeds the Maximum Data
Lines Before Archiving value.
Default Value: 5
Days to Retain Data Sets Before Deleting
The number of days since a data set was last updated before it's automatically and permanently deleted from the stage
tables.
Default Value: 30
Environment Conguration
Value made up of 1 or 2 leers followed by a number in the range 0 through 99 that's supplied by Oracle Support. HCM
Data Loader uses this value to calculate the maximum number of concurrent threads that you can use when loading
data. The resulting maximum value is used to validate the value that you specify:
• For the Maximum Concurrent Threads for Load parameter on the Congure HCM Data Loader page
• When importing and loading data on the Import and Load data page
35
• When importing and loading data using a web service
In these cases, if the Maximum Concurrent Threads for Load value is higher than the calculated maximum value, then
an error is raised.
Note: You raise a service request (SR) to obtain the value of this parameter for your environment.
If you leave the Environment Conguration parameter blank, then the default value of the calculated maximum is
1000.
Default Value: None
Load Group Size
Number of business objects processed as a single unit of work by a single thread.

Default Value: 100
Maximum Concurrent Threads for Import
Maximum number of threads to run concurrently when importing data to the stage tables.
Default Value: 8
Maximum Concurrent Threads for Load
Maximum number of threads to run concurrently when loading data from the stage tables to the application tables.
This parameter is used in conjunction with the Load Group Size parameter. Only the threads required to load your
objects based on the Load Group Size parameter are created.
Default Value: 8
Maximum Data Lines Before Archiving
The number of data lines that can be held in the stage tables before data sets are automatically backed up.
Default Value: 10000000
Transfer Group Size
Number of le lines processed as a single unit of work by a concurrent thread.

Default Value: 100000
Scheduling Default Parameters

Date-Eective Update Mode
Species whether future-dated records should be purged when date-eective objects are loaded.
Default Value: Replace
Delete Source File
Species whether to delete source les from the Oracle WebCenter Content server once they have been processed.
36
Default Value: Yes
Disable Post Process Tasks
This parameter is read-only. You can disable individual postload processes by including a SET instruction in the relevant
Worker.dat or Position.dat le.
Default Value: None
File Action
Default le-processing action.
Import and load means that valid objects are loaded automatically once import completes. Import only means that
your data is imported to the stage tables but load isn't initiated.
Default Value: Import and load
Initiate Business Object Post Processing
Species whether processes registered to run automatically after an object is loaded should run.
Default Value: Yes
Maximum Percentage of Import Errors
Percentage of le lines in error that can occur in a business object before the import process stops for the object.
Default Value: 100
Maximum Percentage of Load Errors
Percentage of business-object instances in error that can occur for a business object before the load process stops.
Default Value: 100
Business Object Parameters: Worker

You can set these parameters separately for HCM Data Loader and HCM Spreadsheet Data Loader.
Calculate Worker Full-Time Equivalent
Species whether the full-time equivalent (FTE) value should be calculated automatically for all worker assignments in a
Worker.dat le.
Default Value: No
Create Worker Default Work Hour Paern
Species whether a default working-hour paern should be created automatically for all worker assignments in a
Worker.dat le.
Default Value: No
Related Topics
• The SET Instruction
37
How You Dene Referenced Objects

Business objects that you're loading may reference a few business objects that you can't load using HCM Data
Loader because they're not integration enabled. You dene or review these objects in the target Oracle HCM Cloud
environment before you load data that references them. You may have performed this step during implementation of
Oracle HCM Cloud. This topic identies how you dene these referenced objects.
This table identies the main objects of this type. It lists the tasks that you use to manage them and the functional area
to which each task belongs in the Setup and Maintenance work area.
Business Object Functional Area Task
Application Reference Data Set Enterprise Prole Manage Reference Data Sets

Assignment Status Type Workforce Information Manage Assignment Status

Business Unit Organization Structures Manage Business Unit

Content Type Workforce Proles Manage Prole Content Types

Currency Code Financial Reporting Structures Manage Currencies

Element Type Elements and Formulas Manage Elements

Legal Entity Legal Structures Manage Legal Entity

Ocial Language Code Application Extensions Manage Languages

Prole Type Workforce Proles Manage Prole Types

Schedule Workforce Information Manage Work Schedules

Foreign-Object References
When you refer to these objects from objects that you're loading, you use their user keys. (Alternatively, you can use
their surrogate IDs, if available.) HCM Data Loader provides business-object documentation for all supported objects.
This documentation identies the user key that you can use for foreign-object references. For example, the Position
object includes a reference to the Business Unit object, which isn't integration enabled. The position documentation
identies the business-unit name as its user key. Therefore, when loading a Position object, you can refer to the
38
associated business unit using the business-unit name. To see the supplied documentation for a business object, click
the object name on the View Business Objects page.
How You Review Lists of Values

The permied values of many object aributes are dened in lists of values. Some lists of values are predened and
can't be updated in any way. Others contain some values, but you can also add your own. In some cases, you can edit
or remove predened values. In Oracle HCM Cloud, lists of values are dened as lookup types. You're recommended to
review the predened lookup types and make any updates before you aempt to load data that uses them. You may
have completed this process during implementation of Oracle HCM Cloud.
Reviewing Lookup Types

To manage lookup types, perform relevant tasks in the Setup and Maintenance work area. For example, the Workforce
Information functional area contains tasks for managing many lookup types, including person lookups, termination
lookups, document lookups, and checklist lookups. To manage person lookup types, perform the Manage Person
Lookups task. On the Manage Person Lookups page, select a lookup type to edit. The list includes:
• Address types
• Contact relationships
• Ethnicity
• Highest education level
• Honors
• Marital status
• Military rank
• Phone types
• Religion
Ensure that the dened lookup values support the data that you're planning to load.
Related Topics
• Overview of Lookups
Dene the Source-System Owner

If you plan to use source keys, then you must add your source-system owner values to the
HRC_SOURCE_SYSTEM_OWNER lookup type before you load data. You must have the Application Implementation
Consultant or Human Capital Management Application Administrator job role or privileges to perform this task.
Use the Manage Common Lookups task in the Setup and Maintenance work area. Follow these steps:
1. On the Manage Common Lookups page, search for the lookup type HRC_SOURCE_SYSTEM_OWNER.
2. In the search results, select the lookup type to display its lookup codes.
3. In the Lookup Codes section of the page, click the New icon to add a lookup-code row.
4. Complete the elds in the row. Ensure that the new code is enabled and the dates are valid for the data that
you're loading.
39
5. Repeat steps 3 and 4 for additional source-system owner values.

6. Click Save and Close.
Related Topics
• Source Keys
How You Test the HCM Data Loader Process Flow and
Connections
In a new environment, you may want to test HCM Data Loader end-to-end processing without creating unwanted data.
Once you're sure that HCM Data Loader processing and connections are working as expected, you can load your own
data with condence. This topic describes how to test HCM Data Loader end-to-end processing.
Testing End-to-End Processing

HCM Data Loader provides:
• A process, Test HCM Data Loader Process Flow and Connections
• An object, Example Object
When you submit the Test HCM Data Loader Process Flow and Connections process, set the Action parameter to
Test HCM Data Loader. The process:
1. Generates a le of MERGE instructions for the Example Object
2. Adds the ExampleObject.dat le to the ExampleObject||<date and time>||.zip le
3. Uploads the .zip le to the hcm/dataloader/import directory on the Oracle WebCenter Content server
4. Initiates HCM Data Loader to import and load the le
5. Provides a log le
You can review progress and results on the Import and Load Data page.
The Example Object

When you run the Test HCM Data Loader Process Flow and Connections process, the Example Object data is saved
to its own tables. No data is saved to the application tables. You can review the structure and aributes of the Example
Object on the View Business Objects page in the Data Exchange work area. The example object:
• Has child and grandchild components and a translation object
• Supports all key types
• Supports Create and Delete actions
• Has aributes of most data types
• Has lookup-validated aributes
You can generate a template le for the Example Object.
Note: Although an Example Object Translation object exists, no translation data is generated when you run
the Test HCM Data Loader Process Flow and Connections process.
40
Deleting the Test Data

You're recommended to run the Test HCM Data Loader Process Flow and Connections process periodically to
delete the test data and associated data sets. When you submit the process, set the Action parameter to Delete test
data. In this case, the process generates a le of DELETE instructions, adds it to the DeleteExampleObject||<date and
time>||.zip le, and uploads it.
How You Audit Objects Loaded in Bulk

You can audit changes made to objects when you bulk load them using either HCM Data Loader or HCM Spreadsheet
Data Loader. When audit is enabled, the creation, update, and deletion of objects are audited. This topic describes how
to enable and manage audit for bulk-loaded objects.
Enabling Audit for Bulk-Loaded Objects

Auditing is optional. To audit bulk loading of objects, you must:
1. Perform the Manage Audit Policies task in the Setup and Maintenance work area to select objects and their
aributes for audit.
2. Enable auditing in general on the Manage Audit Policies page.
3. Enable auditing of bulk-loaded data, either for the enterprise or in individual .dat les and spreadsheet
templates.
Enabling Audit for HCM Data Loader

The Enable Audit Data parameter on the HCM Data Loader parameters tab of the Congure HCM Data Loader
page controls audit for the enterprise. By default, Enable Audit Data is set to No, but you can override that seing.
Alternatively, you can enable audit selectively by including the following SET instruction in relevant .dat les:
SET ENABLE_AUDIT_DATA Y
Enabling Audit for HCM Spreadsheet Data Loader

The Enable Audit Data parameter on the HCM Spreadsheet Data Loader parameters tab of the Congure HCM Data
Loader page controls audit for the enterprise. By default, the Enable Audit Data parameter is set to No, but you can
override that seing. Alternatively, you can enable audit selectively by seing the Enable Audit Data parameter in the
relevant spreadsheet template to Yes.
When to Enable Audit for the Enterprise

Seing the Enable Audit Data conguration parameters to Yes for the enterprise may aect performance. Consider
enabling audit in this way only for ongoing integrations.
41
Purging Audit Data

You may want to purge audit data, typically when disposing of personally identiable information in worker records. By
default, the purging of audit data is disabled for the enterprise and you can't override this seing at the enterprise level.
However, you can include the following SET instruction in individual .dat les:
SET PURGE_AUDIT_DATA Y
In spreadsheet templates, you can set the Purge Audit Data parameter to Yes. These instructions purge the audit data
for the business objects in the .dat le or spreadsheet.
Restrictions exist on enabling audit and purging data at the same time. You can't include both of the following SET
instructions in a single .dat le:
SET ENABLE_AUDIT_DATA Y
SET PURGE_AUDIT_DATA Y
Similarly, you can't include both of the following parameter values in a spreadsheet template:
Parameter Value
Enable Audit Data Yes

Purge Audit Data Yes

To purge audit data when auditing is enabled for the enterprise, you must disable audit in the same .dat le or
spreadsheet template. That is, you must do one of the following:
• Include a SET_ENABLE_AUDIT_DATA N instruction in the same .dat le.

• Set the Enable Audit Data parameter in the spreadsheet template to No.
Correcting Load Errors for Audited Objects

When audit is enabled for an object, you can't correct load errors for it in the HCM Data Loader user interface. For
example, your .zip le may contain both Worker and Job objects. If you include the SET ENABLE_AUDIT_DATA Y instruction
in the Worker.dat le only, then you can't correct load errors from that le in the user interface. However, you can
correct errors in the Job objects, as audit isn't enabled in the Job.dat le.
Related Topics
• Enable Audit for Oracle HCM Cloud Business Objects
• Set Spreadsheet Template Parameters
FAQs for Preparing to Use HCM Data Loader
42
Can I load data in multiple languages?

Yes. Language packs for the required languages must be installed. For cloud implementations, requested language
packs may be installed before the environment is delivered. Alternatively, you can request language packs by raising a
service request (SR).
43
44
Integrating with HCM Data Preparation
5 Data Preparation
Guidelines for Preparing the Source Data

This topic describes some ways in which you can prepare your data for loading to Oracle HCM Cloud and ensure that it
loads successfully.
Reviewing and Cleansing the Source Data

Identify the business objects that you're planning to upload to Oracle HCM Cloud and their source systems. Review this
source data, and verify that it's both accurate and current. Correct any problems before you aempt to extract it. For
example:
• Ensure that a manager is identied for every worker and that the information is accurate.
• For jobs and positions, ensure that correct job codes and titles exist in the source systems.
• For worker history, establish the accuracy of any historical data. Understand whether all historical data must be
uploaded or just key events, such as hire, promotion, and termination.
Preparing the source data in this way minimizes the problems that can occur when you upload data to Oracle HCM
Cloud. It also makes it less likely that you load inaccurate data to the new environment.
Extracting Data from the Source System

You must dene mappings between your source data and the Oracle HCM Cloud business-object model by comparing
source and target aributes. To review the structure of a business object in Oracle HCM Cloud:
1. Open the View Business Objects page in the Data Exchange work area.
2. Search for the object by entering its name in the Business Object query-by-example eld and pressing Enter.
3. Click the object name to open the Business Object Details page for the object. This page provides
comprehensive information about the object's structure and aributes.
You must also dene the transformation logic and build extraction routines. You can use tools that are native to the
source system, such as PL/SQL in Oracle E-Business Suite or SQR in Oracle PeopleSoft. Alternatively, you can use an
Extract, Transform, and Load tool, such as Oracle Data Integrator or PowerCenter Informatica.
Validating the Source Data Before Upload

HCM Data Loader validates your data during both the import and load phases of data loading. The Data File Validator
tool, available from My Oracle Support, can perform most of the data-formaing validations before you aempt to load
the data. You run this utility in your source environment to test your generated .dat les. The utility generates a list of
validation errors in HTML format. You can correct the errors in the .dat les before you load them.
You can download the Data File Validator tool from the My Oracle Support document, Data File Validator Tool for HCM
Data Loader (document ID 2022617.1).
Related Topics
• Data File Validator Tool for HCM Data Loader (2022617.1)
45
General Data Considerations for HCM Data Loader

This topic describes some general aspects of data preparation. Follow these rules to ensure successful data upload.
Unchanged Aributes
When you update existing data in Oracle HCM Cloud, you supply:
• A unique identier for the record being updated

• The aributes that have changed
Any aributes that you omit retain their current values. For performance reasons, you're recommended not to include
aributes that haven't changed.
Note: For date-eective records, all aributes that you supply are updated for the specied date range.
Null Aribute Values

To set an aribute value explicitly to null, you must supply the #NULL token as the aribute value. You can't simply
leave the aribute blank.
Lookup-Validated Aributes
For nonexeld aributes that are dened in Oracle HCM Cloud as lookup types, you can specify either the lookup code
or its meaning. For example, you can specify the sex of a person using either the lookup codes or the lookup meanings
shown in this table.
Lookup Code Lookup Meaning
M Male

F Female

You're recommended to use the lookup code, as the lookup meaning can be translated. The language of the lookup
meaning must match the language of the user who's uploading the data.
Dierent rules apply to exeld aributes that are dened as lookup types.
Numeric Values
For numeric values, only the decimal separator is supported. Don't include currency symbols, scientic notation, or
thousands separators. To set an existing numeric value to null, supply the #NULL token as the aribute value.
46
Date and Time Aributes

The expected formats for date and time values are shown in this table.
Date or Time Format
Date YYYY/MM/DD

Time YYYY/MM/DD HH24:MI:SS

For example: 2016/11/05 14:20:00
To set an existing date or time value to null, supply the #NULL token as the aribute value.
Related Topics
• Guidelines for Loading Flexeld Data
How You Load Images, Aachments, and Large Strings

You can load both Character Large Objects (CLOB) and Binary Large Objects (BLOB) using HCM Data Loader. However,
the way in which you provide data for these objects is unique to these aributes. Instead of supplying the data directly
in the data (.dat) le, you supply it in a separate le. You supply the name of this le as the value of the relevant
aribute in the data le.
This example shows a data le for the Document Aachment component. The File aribute references a text
aachment le in each MERGE line.
METADATA|DocumentAttachment|DocumentType|File|PersonNumber|...
MERGE|DocumentAttachment|Drivers License|file01.txt|23901|...
MERGE|DocumentAttachment|Drivers License|file02.txt|64235|...
This approach is used because data for these data types can be very large. Also, data to be loaded directly rather than
by aachment may need new-line characters, making it complex to include in the business-object data le.
How to Supply CLOB and BLOB Files

To load data into a CLOB aribute, you supply the data in a separate le. You place the le in a ClobFiles folder in the
same .zip le as the business-object data le. Similarly, to load data or upload an aachment to a BLOB aribute, you
supply the data or le to aach in a BlobFiles folder. The data type of the aribute that's used to load a large object or
aachment determines which folder to use.
47
The business-object documentation species the data types of all aributes. For example, the File aribute of the
Document Aachment component has the BLOB data type. Therefore, you place referenced les in the BlobFiles
folder, as shown in this gure.
Documents of
Record.zip
BlobFiles Folder
file01.txt
file02.txt
file03.txt
File names in the ClobFiles and BlobFiles folders can include UTF-8 single-byte characters. For example, le names
can include the alphanumeric characters a through z, A through Z, and 0 through 9, underscore (_), hyphen (-) and
parentheses ( ). Most le-name extensions are supported, though CLOB data is usually supplied in text (.txt) les.
How You Supply Source Keys

The source key is made up of two aributes, SourceSystemOwner and SourceSystemId. If you use a source key to
identify a record being merged, then you can also use source keys to identify integration-enabled foreign objects. For
example, you can identify the parent record of a child component using a source key. You can't use source keys for
foreign-object references if you aren't also using a source key for the local record.
This topic describes how to supply source keys for both local records and foreign-object references. It also describes
how default source keys are constructed.
48
Dening Source-System Owner Values

The SourceSystemOwner aribute is common to all source keys supplied in a record. Therefore, all foreign objects that
you identify using source keys must have the same SourceSystemOwner value as the record being merged. You must
dene the SourceSystemOwner value by updating the HRC_SOURCE_SYSTEM_OWNER lookup type before you use
source keys.
Specifying Source Keys for Local Records

To identify a local record uniquely using a source key, you supply values for both the SourceSystemId and
SourceSystemOwner source-key aributes. This example shows how to identify a job object using a source key.
METADATA|Job|SourceSystemId|SourceSystemOwner|JobCode|JobName|SetCode|EffectiveStartDate|EffectiveEndDate
MERGE|Job|12349|EBS-UK|SE|Software Engineer|COMMON|2010/01/01|4712/12/31
Specifying Source Keys for Foreign-Object References

To use a source key for a foreign-object reference, you append the hint (SourceSystemId) to the surrogate ID aribute
for the foreign object. This example shows how to identify a Job object in an assignment record using a source key.
JobId is the surrogate ID aribute for the Job object, to which you append the hint (SourceSystemId) in the METADATA
line. You must have created the Job object using HCM Data Loader with the supplied source key.
METADATA|Assignment|SourceSystemId|SourceSystemOwner|JobId(SourceSystemId)|EffectiveStartDate|EffectiveEndDate
MERGE|Assignment|234234|EBS-UK|12349|2013/01/01|4712/12/31
Note: You can use source keys for foreign objects only if those objects are integration-enabled. The
integrated business-object documentation identies which objects are integration enabled.
Default Source Keys

If you specify no source key when you create a record using HCM Data Loader, then a default source key is generated.
The default SourceSystemOwner value is FUSION and the SourceSystemId is the surrogate ID. You can use source keys
to identify records with default source keys. You can also update existing source keys, including default source keys,
using the Source Key object. However, no process exists for extracting source-key information.
Related Topics
• Source Keys
• Dene the Source-System Owner
How You Update Source Keys

When you load data using HCM Data Loader, you can provide a source key. The source key is a value, usually generated
from a legacy environment, that identies the record uniquely in that environment. You can use the source key to refer
to the object both when maintaining it and when referring to it from another object. If you specify no source key, then
a default source key is generated. You can update both default and locally dened source keys for integration-enabled
objects. This topic describes how to update source keys.
49
Loading Updates to Source Keys

To update the source key associated with any record, you load a SourceKey.dat le. In the le, you supply both a
reference to the record to update and the new source-key value.
This example SourceKey.dat le updates the source key for a person address that's identied by its existing source
key. The BusinessObject and Component aributes are used to identify the type of record being updated. For both
aribute values, you supply the relevant le discriminator.
METADATA|SourceKey|BusinessObject|Component|OldSourceSystemId|OldSourceSystemOwner|NewSourceSystemId|
NewSourceSystemOwner
MERGE|SourceKey|Worker|PersonAddress|2342|FUSION|1422-HOME|VISION
How You Supply User Keys

User keys are specic to the business object component that you're loading. The integrated business-object
documentation identies the user-key aributes available for all business-object components and foreign-object
references.
The user-key aributes are required when you create a record. They're also required when you update it, unless you
supply a dierent key type to identify the record uniquely. This topic describes how to use user keys to identify local
records and refer to foreign objects. It also describes how changes to user-key values aect their usefulness as keys.
Specifying User Keys for Local Records

A user key can be made up of multiple aributes. You must supply them all if you're not using another key type, such as
a source key, to identify the record. This example shows how to identify a Job object by its user key, which is made up of
the JobCode and SetCode aributes.
METADATA|Job|JobCode|JobName|SetCode|EffectiveStartDate|EffectiveEndDate
MERGE|Job|SE|Software Engineer|COMMON|2010/01/01|4712/12/31
Specifying User Keys for Foreign-Object References

In this example, an Assignment object is uniquely identied by its source key. However, a user key is used for the
foreign-object reference to the associated Job object.
METADATA|Assignment|SourceSystemId|SourceSystemOwner|JobCode|SetCode|EffectiveStartDate|EffectiveEndDate
MERGE|Assignment|234234|EBS-UK|SE|COMMON|2013/01/01|4712/12/31
Managing Changed User-Key Values

The values of some user keys aren't xed. For example, you can change the name of an organization or location. As
user keys can change, using them for historical references is dicult. If you're loading date-eective history for a
business-object component where the user key has changed, then you must also supply a source key. This approach
enables HCM Data Loader to identify related date-eective records correctly to form the object that you're loading.
Related Topics
• User Keys
50
Examples of Supplying Oracle Fusion Surrogate IDs

An Oracle Fusion surrogate ID is assigned automatically to a new record when you save it to the database. Surrogate
IDs are specic to the business-object component that you're loading. The integrated business-object documentation
identies the surrogate ID aribute for all business-object components and foreign-object references. This topic
describes how to use surrogate IDs to identify local records and provide foreign-object references.
Note: Oracle HCM Cloud customers are unlikely to have access to the Oracle Fusion surrogate ID.
Supplying Surrogate IDs for Local Records

This example shows how to use a surrogate ID to identify a Job component. For this component, the JobId aribute is
its surrogate ID.
METADATA|Job|JobId|JobName|EffectiveStartDate|EffectiveEndDate
MERGE|Job|13413|Software Engineer - Java|2013/01/01|4712/12/31
Supplying Surrogate IDs for Foreign-Object References

This example shows an Assignment component that's uniquely identied using a source key. The record includes a
foreign-object reference to the associated Job object, which is identied by its surrogate ID, JobId.
METADATA|Assignment|SourceSystemId|SourceSystemOwner|JobId|EffectiveStartDate|EffectiveEndDate
MERGE|Assignment|234234|EBS-UK|13413|2013/01/01|4712/12/31
Related Topics
• Oracle Fusion GUIDs and Surrogate IDs
Examples of Supplying Oracle Fusion GUIDs

The Oracle Fusion GUID (Globally Unique Identier) is a hexadecimal value that's assigned automatically to a record
when it's saved to the database. This topic shows how to use GUIDs to identify local records and provide foreign-object
references.
Supplying GUIDs for Local Records

When you supply a GUID value to identify the record being merged or deleted, you use the aribute name GUID,
regardless of the business-object component. This example shows how to specify a GUID value to identify a Job
component.
METADATA|Job|GUID|JobName|EffectiveStartDate|EffectiveEndDate
MERGE|Job|2342UJFHI2323|Software Engineer - Java|2013/01/01|4712/12/31
51
Supplying GUIDs for Foreign-Object References

To use a GUID for a foreign-object reference, you append the hint (GUID) to the surrogate ID aribute for the object to
which you're referring. This example shows an Assignment component that's identied using source keys. The record
includes a foreign-object reference to the associated Job object, which is identied by its GUID. JobId is the surrogate ID
aribute for the Job object.
METADATA|Assignment|SourceSystemId|SourceSystemOwner|JobId(GUID)|EffectiveStartDate|EffectiveEndDate
MERGE|Assignment|234234|EBS-UK|2342UJHFI2323|2013/01/01|4712/12/31
You can use GUIDs for foreign objects only if they're integration enabled. The integrated business-object
documentation identies which foreign objects are integration enabled.
Related Topics
• Oracle Fusion GUIDs and Surrogate IDs
How You Manage Reserved Characters

A few characters are reserved in the context of an HCM Data Loader data le. That is, they have a specic meaning by
default, and you can't include them in aribute values unless you identify them explicitly as data. This topic explains
how to use the reserved characters in data that you're uploading. It also explains how to override the default reserved
characters.
Using Reserved Characters in Aribute Values

By default, these characters are reserved:
• Delimiter (vertical bar |)
• Newline character (n)
• Escape (backslash \)
To include the newline (n) and vertical bar (|) characters in aribute values, you precede them immediately with the
escape character (backslash \). For example:
METADATA|Address|AddressLine1
MERGE|Address|The Stables\|Main Allan
This entry enables the vertical bar to appear in the aribute value for address line 1:
The Stables|Main Allan
To include the newline character in a value, you specify \n. For example:
METADATA|Address|AddressLine1
MERGE|Address|The Stables\nMain Allan
This entry results in the following value for address line 1:
The Stables
Main Allan
52
Overriding the Reserved Characters

You can override the reserved characters for a le using the SET le-line instruction, which must appear before any
METADATA lines in the le. The SET commands for overriding reserved characters have this format:
SET FILE_ESCAPE <new_value>
SET FILE_DELIMITER <new_value>
SET FILE_NEW_LINE <new_value>
The new value can be up to 10 characters. For example, you could set the newline character to newline and the le
delimiter to comma (,) using the following SET commands:
SET FILE_DELIMITER ,
SET FILE_NEW_LINE newline
In this case, METADATA and MERGE lines could appear as follows:

METADATA,Address,AddressLine1
MERGE,Address,TheSteading\newlineKier Allan
Tip: You can also override the reserved characters for the enterprise by seing relevant conguration
parameters. For example, set the File Delimiter conguration parameter to override the default le delimiter
for the enterprise.
Related Topics
How You Load and Maintain Translated Objects

In environments where multiple languages are enabled, you can use HCM Data Loader to upload translated objects.
You specify the character set of the data le by naming any Java-supported character set on the File Character Set
conguration parameter. The default character set is UTF-8.
Loading Translated Objects

Loading translated objects is a two-stage process:
1. You create the object by loading the base-language version. At this stage, translation records are created for all
enabled languages, but they hold base-language versions of any translatable values. For example, if US English
is your base language, then translation records hold US English versions of translatable values.
2. You load the translated values as corrections to the base-language object. To perform this step, you use data-
le templates that are provided specically for translation. One translation data-le template is provided for
each business-object component that includes translatable values.
For example, you may create the Sales Manager job in an environment where US English is the base language. If
French, German, and Spanish are also enabled, then the object is created as shown in this table.
Language Source Language Job Name
US English US English Sales Manager

53
Language Source Language Job Name
French US English Sales Manager

German US English Sales Manager

Spanish US English Sales Manager

Once this object exists, you can load a single translation data le (JobTranslation.dat) to correct the French, German,
and Spanish versions of the job name. Alternatively, you can load a translation le for each language if you prefer. You
can deliver translation les either in the same .zip le as the original object or separately. However, you can't deliver
them before the base-language object exists.
Updating Translated Data

To update existing translated data, you can upload just the relevant translation le, provided that the object isn't date
eective.
You must also update the base-language object if:
• The object is date eective.

• The object currently has no date-eective record with the same eective start date as the new translation value.
This requirement exists to ensure that the eective dates of the base-language and translation objects remain the
same.
You can't delete translation objects in isolation. Translation objects are deleted automatically when you delete the
associated object. For example, when you delete a Job Family object any associated translation objects are deleted
automatically.
Translation-File Discriminators
Unique le discriminators exist for the translation les and are identied in relevant les. For example, the le
discriminator for the le JobTranslation.dat is JobTranslation.
This example shows a Job.dat le followed by the associated JobTranslation.dat le.
METADATA|Job|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|JobCode|Name|ActiveStatus
MERGE|Job|EBS-UK|JB2ACC44|2010/01/01|2014/04/04|ACADM|Accounts Administrator|A
MERGE|Job|EBS-UK|JB2ACC44|2014/04/05|4712/12/31|ACADM|Accounts Clerk|A
METADATA|JobTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|Language|Name
MERGE|JobTranslation|EBS-UK|JB2ACC44|2010/01/01|2014/04/04|ES|Administrador de Cuentas
MERGE|JobTranslation|EBS-UK|JB2ACC44|2014/04/05|4712/12/31|ES|Cuentas Clerk
Related Topics
54
How You Include Source-System References in Data

Files
You can include source-system references in each data line in a le. They enable you to record the database-table
name, column names, and aribute values from the source system. You can see these values on the Object Errors page
for an object that fails to load. Therefore, you can easily identify the data source. Source-system references are optional.
This topic describes how to construct source-system references, which are made up of a name and a value.
Source-System Names
You specify source-system database-table and column names in the relevant METADATA line. To specify the source-
system database-table name, you add the following entry to the METADATA line:
SourceRefTableName=<table name>
You can specify up to 10 source-system column names in the same METADATA line using the SourceRef001 to
SourceRef010 tags. For example:
METADATA|Job|SourceRefTableName=PER_JOBS|SourceRef001=JOB_ID|SourceRef002=EFFECTIVE_START_DATE|
SourceRef003=EFFECTIVE_END_DATE
Source-system references can appear anywhere in the METADATA line after the instruction and discriminator values.
Source-System Values
Supply the source-system values on each data line, ensuring that they appear in the order specied on the METADATA
line. In data lines, you must leave the source-system database-table name blank. This value appears in the METADATA
denition only. For example:
METADATA|Job|SourceRefTableName=PER_JOBS|SourceRef001=JOB_ID|SourceRef002=EFFECTIVE_START_DATE|
SourceRef003=EFFECTIVE_END_DATE
MERGE|Job||135|2010/01/01|4712/12/31
MERGE|Job||136|2010/01/01|4712/12/31
Related Topics
• How You Review and Correct Errors
Data Deletion Using HCM Data Loader

You can delete many objects using HCM Data Loader, regardless of whether they were loaded using HCM Data Loader.
This topic explains how to delete an object or its components and identies any restrictions.
Tip: As you can't recover a deleted object, try to correct your data instead of deleting and recreating it.
55
What You Can and Can't Delete

You can delete:
• Most complete business objects, except Worker.

• Most individual business-object components.
• Some child components of the Worker object. For example, you can delete the Person Email component of a
worker object.
When you delete a parent object, its child components and any translation objects are also deleted. For example, to
delete a Grade object and its child components, you create a DELETE instruction for the Grade discriminator. To delete
only a Grade Rate Value child component, you create a DELETE instruction for the GradeRateValue discriminator.
You can't delete:
• Individual date-eective records

• Individual translation objects
• Worker objects
Note: Before you delete an object, ensure that other business objects don't refer to it.
For information about whether you can delete a component, see the business-object details on the View Business
Objects page in the Data Exchange work area.
DELETE Instructions
To delete an object, include the DELETE instruction in the relevant data le. For example, you could delete a Job Family
object by including these lines in the JobFamily.dat le:
METADATA|JobFamily|EffectiveStartDate|EffectiveEndDate|JobFamilyName
DELETE|JobFamily|2012/10/01|4712/12/31|Sales01
These rules apply:
• You can't include DELETE instructions in translation data les.

• You must not supply a DELETE instruction for a record that has a MERGE instruction in the same le. HCM Data
Loader doesn't know which instruction to process rst.
Deleting Date-Eective Objects

To delete a date-eective object identied by user keys, you must supply both the eective start and eective end
dates. If the object is identied using any of the other key types, then the eective start and end dates are optional.
56
Integrating with HCM Loading Date-Eective Data
6 Loading Date-Eective Data
Overview of Loading Date-Eective Objects

Many Oracle HCM Cloud objects are date-eective. That is, they retain a history of changes, each of which has eective
start and end dates. Professional users can retrieve and edit the version of an object as of a specied date. You can load
date-eective objects and their date-eective history using HCM Data Loader. This topic provides some general rules
about loading date-eective objects.
Aributes of Date-Eective Records

This table introduces the aributes that occur in date-eective records.
Aribute Description
The start date for the aribute values. This value is required for all date-eective records.
EectiveStartDate
The end date for the aribute values. If you leave this value blank, then the date-eective
EectiveEndDate record continues by default to the end of time.

When multiple changes per day occur, this aribute identies their order.
EectiveSequence
For objects with multiple changes per day, this aribute identies the latest record for the
EectiveLatestChange eective start date.

Supplying Date-Eective History

You can decide how much history to load for new objects, but the history that you provide must be complete and valid.
Although you can supply date-eective records in any order in the .dat le, no break in the dates can occur. When you
create a date-eective object, only the rst date-eective record is processed as a new record. Later-dated records are
updates to the rst record. To retain values from the previous date-eective record, you can either leave those aribute
values blank or repeat the value that's to continue.
Note: Leaving an aribute value blank doesn't set the aribute to null. To change a value to null, you must
supply the #NULL token as the aribute value.
57
Key Values
HCM Data Loader groups records into logical objects, where a logical object is one occurrence of the business object,
such as a Worker. The records belonging to a logical object are identied by the unique key for the component.
Therefore, the key value must be the same throughout the date-eective history. You can use any of the four key types.
Creating Date-Eective Objects

When you create business objects containing date-eective components using HCM Data Loader:
• Include the SET PURGE_FUTURE_CHANGES Y instruction at the start of the data le. This instruction sets the HCM
Data Loader date-eective maintenance mode to Replace. In this mode, which is the default, the contents of
the data le replace any existing data.
• If you're including object history, then supply the #NULL token for all aributes that must have null values.
Updating Date-Eective Objects

When you load updates to objects that contain date-eective components:
• Include the SET PURGE_FUTURE_CHANGES N instruction at the start of the data le. This instruction sets the HCM
Data Loader date-eective maintenance mode to Retain. In this mode, existing future-dated changes are
retained. If you don't include this instruction, then any existing future-dated changes for the date range of your
updates are purged.
• Always supply the eective start date of each change. The eective end date is optional. However, you must set
the eective end date to #RETAIN if you don't want to correct any future-dated records. Leave the eective end
date null if you want a change to apply until the end of time.
Note: When you update date-eective objects, the values that you supply are applied to every record in the
specied date-range. However, some aributes, such as ActionCode, are protected from update.
How You Load Objects with Multiple Changes per Day

For most date-eective objects, only one record exists for a specic date. Therefore, the object history shows only
the last update to each aribute on any day. However, for some objects, such as Assignment, a record exists for each
update in a day. Such objects include an eective sequence number to show the update order. Changes are cumulative,
and the record with the highest eective sequence number is available to transactions for that date. This topic describes
how to load and maintain objects that support multiple changes per day.
Eective Sequence Number

When you load date-eective history for an object with multiple changes on a single date, the EectiveSequence
value must start at 1 and increase sequentially. You can't repeat an EectiveSequence value for the same logical
58
object on the same date, nor can gaps exist in the sequence. If only one change exists for an eective start date, then
EectiveSequence must be 1.
Note: Don't leave EectiveSequence blank when you're loading multiple changes for a single day. Without
this information, the order in which records with the same eective start date are processed is undened.
Eective Latest Change

When you report multiple changes on the same eective start date, the EectiveLatestChange aribute of the last
record in the sequence must be Y. For all earlier records, the aribute must be N. EectiveLatestChange is a required
aribute for records that support multiple changes per day. If only one change exists on an eective start date, then
EectiveLatestChange must be Y.
Eective Start and End Dates

The eective end date of any record with EectiveLatestChange set to N must be the same as its eective start date.
Loading Date-Eective History with Multiple Changes Per Day: Example

This example loads date-eective history for an Assignment object.
METADATA|Assignment|SourceSystemId|EffectiveStartDate|EffectiveSequence|EffectiveLatestChange|
EffectiveEndDate|...
MERGE|Assignment|2724|2010/06/08|1|Y|2012/03/03|...
MERGE|Assignment|2724|2012/03/04|1|N|2012/03/04|...
MERGE|Assignment|2724|2012/03/04|3|Y|2012/06/01|...
MERGE|Assignment|2724|2012/06/02|1|Y||...
This example observes these rules:

• No gaps exist in the dates.
• The unique key is identical for all date-eective records.
• EectiveSequence starts at 1 for all new eective start dates and is sequential for matching eective start
dates.
• EectiveLatestChange is Y when the record is the last change on an eective start date. Otherwise,
EectiveLatestChange is N.
• The EectiveEndDate matches the EectiveStartDate when EectiveLatestChange is N.
Updating Objects with Multiple Changes Per Day

When updating an existing object with multiple changes per day, you may not know the next available sequence
number. In this case, leave the EectiveSequence aribute blank. The next number in the existing sequence is
generated automatically.
To correct an existing record, you must supply the existing values for these aributes to identify the record correctly:
• Eective Start Date
• Eective End Date
• Eective Sequence
• Eective Latest Change
59
For example:
EffectiveEndDate|...
Options for Updating Date-Eective Objects with Future-

Dated Records
When you update a date-eective object, your changes may aect more than one of its existing date-eective records.
Also, some of the aected records may have eective start dates that are later than the eective start date of the
update. Such records are known as future-dated records. This topic describes how updates to future-dated records are
processed in each of the maintenance modes. It also shows how to set the maintenance mode.
This table shows the date-eective history of a Job object.
Eective Start Eective End Job Code Job Name Regular Full Part Time Active Status
Date Date Temporary
2010/06/08 2012/01/09 ACC1 Accounts Clerk T PART_TIME A

2012/01/10 2012/03/03 ACC1 Accounts Clerk T FULL_TIME A

2012/03/04 4712/12/31 ACC1 Accounts T FULL_TIME A

Administrator

If you update the object specifying an eective start date of 2011/01/01, then a new date-eective record is generated
for 2011/01/01. This update changes the eective end date of the 2010/06/08 record. It also aects both the 2012/01/10
and 2012/03/04 records. The exact eect on these existing future-dated records depends on:
• The maintenance mode, which can be either Retain or Replace

• The eective end date value, if any, that you supply
Retain Mode or Replace Mode

This table summarizes the combined eects of the maintenance mode and eective end date on existing future-dated
records.
Mode Eective End Date Value Description
Retain #RETAIN Existing aribute values in future-dated

records are retained. Your updates don't
aect these values. All existing records are
retained.

60
Mode Eective End Date Value Description
Retain #ALL Changed aribute values are carried

forward to all future-dated records until
the end of time. All existing records are
retained.

Note: Leaving the eective
end date blank or seing it to
4712/12/31 has the same eect
as specifying the #ALL token.
However, you must use the #ALL
token to carry forward changes
for objects that have a specic end
date.

Retain Specic date other than 4712/12/31 Changed aribute values are carried
forward to future-dated records until the
specied end date. All existing records are
retained.

Replace Specic date or blank A single record replaces existing date-

eective records for the date range
specied on the update.

Retain mode is recommended when you're applying an incremental update to an existing record. Replace mode, which
is the default mode, is useful during data migration, when you're uploading the complete data for a record.
Note: Replace mode may have unexpected consequences if you upload less than the complete data for a
record.
In both modes:
• A new date-eective record is generated for the object if you specify an eective start or end date for which no
date-eective record currently exists.
• Only the aributes for which you supply values are updated.
Seing the Maintenance Mode

Use the SET command to set the maintenance mode for a date-eective object. This table shows the set command to
include in the data le.
Mode SET Command
Retain SET PURGE_ FUTURE_CHANGES N

Replace SET PURGE_ FUTURE_CHANGES Y

61
If you include neither of these SET commands in a data le, then the default mode is Replace. The default mode can be
overridden for the enterprise using the Date-Eective Update Mode conguration parameter.
Example of Retaining Aribute Values in Future-Dated

Records
When you update a date-eective object, you can leave aribute values in future-dated records unchanged. To retain
these values, you set the maintenance mode to Retain and specify the #RETAIN token instead of an eective end date.
This token ensures that your changes take eect from the supplied eective start date to the start of the next record. If
no future-dated records exist, then your changes apply until the end date of the record. This topic provides an example
showing the eects of Retain mode.
Retaining Future-Dated Aribute Values in an Assignment Object

Consider the date-eective history of the Assignment object shown in this table.
Eective Eective Eective Action Code Job Code Grade Location Hours
Start Date Sequence End Date
2010/06/08 1 2012/03/03 HIRE ACC1 IC2 HQ 40

2012/03/04 1 2012/03/04 PROMOTION ACC1 IC4 HQ 40

2012/03/04 2 2012/03/04 TRANSFER ACC1 IC4 LVP 40

2012/03/04 3 2012/06/01 JOB_CHANGE ACC3 IC4 LVP 40


To change the working hours to 37.5 from 2012/01/10 without aecting future-dated records, you use this data le:
EffectiveEndDate|ActionCode|NormalHours
MERGE|Assignment|2724|2012/01/10||Y|#RETAIN|ASG_CHANGE|37.5
After update, the Assignment object is as shown in this table.
2010/06/08 1 2012/01/09 HIRE ACC1 IC2 HQ 40
62

2012/01/10 1 2012/03/03 ASG_CHANGE ACC1 IC2 HQ 37.5





Aributes in records with eective start dates after 2012/01/10 retain their current values.
Note: As recommended, the data le includes no eective sequence number. Therefore, the next available
number in the sequence is allocated automatically.
Options for Carrying Forward Changed Aribute Values

in Retain Mode
When you update a date-eective object in Retain mode, you may want to carry changes forward to future-dated
records. In this case, you can either specify an eective end date or carry the changes forward to all existing future-
dated records. This topic describes how to achieve each outcome and what to consider when deciding how to proceed.
Specifying an Eective End Date

This table shows the date-eective history of a Job object.
Date Date Temporary

2012/01/10 2012/03/03 ACC1 Accounts Clerk T FULL_TIME A


Administrator

63
To change the Regular Temporary value from T to R for the period from 2011/03/04 to 2014/04/04, you include these
instructions in the .dat le:
METADATA|Job|SourceSystemId|EffectiveStartDate|EffectiveEndDate|ReqularTemporary
MERGE|Job|45346|2011/03/04|2014/04/04|R
After update, the Job object is as shown in this table.
Date Date Temporary

2011/03/04 2012/01/09 ACC1 Accounts Clerk R PART_TIME A

2012/01/10 2012/03/03 ACC1 Accounts Clerk R FULL_TIME A

2012/03/04 2014/04/04 ACC1 Accounts R FULL_TIME A

Administrator


Administrator

A new date-eective record is created for both the start and end dates of the change. The Regular Temporary aribute
is updated for the specied period. All other aributes keep their existing values.
Applying Changes to All Future-Dated Records

You can use the #ALL token in place of an eective end date. This token species explicitly that your changes apply to
all future-dated records, regardless of the object's end date.
For example, you want to make these changes to the Job object:
• Change the Regular Temporary value from T to R.
• Set the eective start date of the change to 2011/03/05.
• Apply the changes to all future-dated records.
You include these instructions in the data le:

METADATA|Job|SourceSystemId|EffectiveStartDate|EffectiveEndDate|ReqularTemporary
MERGE|Job|45346|2011/03/04|#ALL|R
After update, the Job object is as shown in this table.
Date Date Temporary
64
Date Date Temporary

2011/03/04 2012/01/09 ACC1 Accounts Clerk R PART_TIME A

2012/01/10 2012/03/03 ACC1 Accounts Clerk R FULL_TIME A

2012/03/04 4712/12/31 ACC1 Accounts R FULL_TIME A

Administrator

You can achieve the same result by leaving the eective end date in the .dat le blank or seing it explicitly to
4712/12/31. However, you must use the #ALL tag for any object that has an explicit end-date.
Example of Replacing Aribute Values in Future-Dated

Records
When you update a date-eective object in Replace mode, you replace all existing, future-dated records with the
uploaded data. You're recommended to use Replace mode only when the contents of the .dat le must replace the
existing data rather than update it.
Replace mode is the default maintenance mode. However, you can use this SET command to select Replace mode
explicitly and record the seing in the .dat le:
Updating Only Selected Aributes of an Object in Replace Mode

This table shows the date-eective history of an Assignment object.
Eective Eective Eective Action Code Job Grade Location Normal

Start Date Sequence End Date Hours
2010/06/08 1 2012/03/03 HIRE ACC1 IC2 HQ 40




65


To update the working hours to 37.5 from 2012/01/10 in Replace mode, you create the following data le:
EffectiveEndDate|ActionCode|NormalHours
MERGE|Assignment|2724|2012/01/10||Y||ASG_CHANGE|37.5
After update, the Assignment object is as shown in this table.

2010/06/08 1 2012/01/09 HIRE ACC1 IC2 HQ 40

2012/01/10 1 4712/12/31 ASG_CHANGE ACC1 IC2 HQ 37.5

In Replace mode, records with eective start dates that are later than the eective start date of the update are purged.
Aribute values that predate the change and for which you supply no values in the data le appear in the new record.
This update isn't reversible.
Caution: You're recommended to supply values for all aributes that currently exist on the object when
updating in Replace mode. In this example, you could have provided values for job, grade, and location. As
you didn't supply those values, the values that are current on the eective start date of the update remain in
eect.
Examples of Changing First Eective Start Date and Last

Eective End Date
For some objects, you can change the rst eective start date or last eective end date. This topic provides examples
showing how to make these changes.
To change an object's rst eective start date, you include the ReplaceFirstEectiveStartDate aribute in the .dat le
and set it to Y. To change an object's last eective end date, you include the ReplaceLastEectiveEndDate aribute
in the .dat le and set it to Y. You supply the revised dates on the EectiveStartDate or EectiveEndDate aribute, as
appropriate. You can make these changes at the same time as other changes. For example, you can change both the
start date of an object and its name.
Note: The ReplaceFirstEectiveStartDate and ReplaceLastEectiveEndDate parameters don't appear in

object template les or on the Aributes tab of the Business Object Details page. However, you can add them
to .dat les for date-eective objects that support these changes.
66
These restrictions apply to changing rst eective start date and last eective end date:
• For some objects, the last eective end date must be 4712/12/31. Any aempt to change this date causes an
error.
• You can't change the rst eective start date of the Worker object in this way. Instead, you must use the
NewStartDate aribute.
• When you include the ReplaceLastEectiveEndDate aribute in a .dat le, you must specify a date value
for the EectiveEndDate aribute. You must not supply a #RETAIN, #ALL, or #NULL token in place of the
eective end date.
Tip: On the Component Details tab of the Business Object Details page, identify whether you can change a
component's rst eective start or last eective end date. For example, in the Date Eectivity section on the
Component Details tab for the Job object, the First start date option is selected. Therefore, you can include
the ReplaceFirstEectiveStartDate parameter in the .dat le.
Changing the First Eective Start Date of a Job Object

This example shows how to include the ReplaceFirstEectiveStartDate aribute in a .dat le.
METADATA|Job|JobId|EffectiveStartDate|EffectiveEndDate|ReplaceFirstEffectiveStartDate
MERGE|Job|23452|1950/01/01|4712/12/31|Y
Changing the Last Eective End Date of a Recurring Element Entry

This example shows how to include the ReplaceLastEectiveEndDate aribute in a .dat le.
METADATA|ElementEntry|ElementEntryId|EffectiveStartDate|EffectiveEndDate|ReplaceLastEffectiveEndDate
MERGE|ElementEntry|4634|2014/01/01|2014/04/05|Y
67
68
Integrating with HCM Loading Flexeld Data
7 Loading Flexeld Data
Guidelines for Loading Flexeld Data

Using HCM Data Loader, you can load data for both descriptive exelds and extensible exelds. This topic explains
concepts that are common to both types of exelds.
Conguring Flexelds
Before you generate template les for objects with exelds, you must congure the exelds in Oracle HCM Cloud.
After the exelds are congured, the METADATA lines in generated template les include all aributes that are
required to load the exeld data. You also see a Flexeld Aributes tab for relevant object components on the Business
Object Details page in the Data Exchange work area.
Flexeld Codes
When loading exeld data, you must supply the exeld code in the METADATA line in this format:
FLEX:<flexfield code>
For example, to load data for the job descriptive exeld, the exeld code is:
FLEX:PER_JOBS_DFF
Relevant exeld codes appear in the generated template le and on the Flexeld Aributes tab for the business object.
Flexeld Aributes
Flexeld aribute names are those that you specify when conguring the exeld. Both descriptive and extensible
exelds have one or more contexts. When you include a exeld aribute name on the METADATA line for an object,
you must also identify the context. You provide a hint value in the following format to identify both the exeld and the
context to which the aribute belongs:
<flexfield attribute name>(<flexfield code>=<context code>)
For example, for the _MAIN_CONTRACT aribute of the PER_CONTRACT_LEG_DDF descriptive exeld with the CN
context code, the entry on the METADATA line is:
_MAIN_CONTRACT(PER_CONTRACT_LEG_DDF=CN)
Business Objects with Multiple Descriptive Flexelds

Some business object components support multiple descriptive exelds. You can include all descriptive exeld
aributes for every exeld and congured context on a single METADATA line. This approach is possible because you
supply both the exeld code and the context for each aribute.
69
Lookup-Validated Flexeld Values

For exeld values that are validated by lookups, you can supply either the lookup code or the lookup value. To supply
the value, you must append the sux _Display to the aribute name in the METADATA line.
For example, for a congured gender exeld aribute, you can supply either the lookup code (M or F) or the value
(Male or Female). To supply the value, use the aribute name gender_Display, as shown in this example:
METADATA|Job|FLEX:PER_JOBS_DFF|gender_Display(PER_JOBS_DFF=JOBCONTEXT1)|...
MERGE|Job|JOBCONTEXT1|Male|...
MERGE|Job|JOBCONTEXT1|Female|...
Secured Value Sets

A value set is a group of values that validate the content of a exeld segment. If the value set is security
enabled, then it's available to specic users or processes only. You must ensure that the predened
FUSION_APPS_HCM_ESS_LOADER_APPID user has access to any security-enabled value sets that your exelds
reference. Otherwise, the load fails. For more information about enabling access to secured value sets, see the Securing
HCM guide.
Deleting Flexeld Segments

Let's say, for GDPR or other compliance purposes, you need to remove values from a exeld segment and disable it.
First, enable the segment if it's currently disabled. Next, change the values for the segment in your HCM Data Loader le
to empty. Don't use spaces, and make sure the values are empty. Upload your HCM Data Loader le and conrm that
the segments appear empty. Finally, disable the segment.
Related Topics
• Generate and Use Template Files
• Enable Security for Value Sets
• Secure Access to Value Sets
How You Load Data for Descriptive Flexelds

This topic describes how to construct METADATA and MERGE lines in a .dat le to supply descriptive exeld data.
Constructing the METADATA Line

Descriptive exelds extend a business object. You can supply the aributes of the descriptive exeld on the same
MERGE line as the core aributes of the business-object component. On the METADATA line, you must include both
the exeld code and the descriptive exeld aributes for which you want to load data. In a generated business-
object template, the METADATA line automatically includes the exeld code and aributes for congured descriptive
exelds.
This example shows the METADATA line for the Job business object with entries for the PER_JOBS_DFF descriptive
exeld:
METADATA|Job|FLEX:PER_JOBS_DFF|JobCode|ActiveStatus|FullPartTime|MedicalCheckupRequired|RegularTemporary|
EffectiveStartDate|EffectiveEndDate|Name|SetCode|JobFamilyName|_JOB_LEVEL(PER_JOBS_DFF=US)
70
The descriptive exeld aributes can appear anywhere on the line. You don't have to append them at the end.
Constructing the MERGE Lines

For each descriptive exeld for a business-object component, a single MERGE record can have only one context. You
specify the context value on the MERGE line against the exeld code for the descriptive exeld in the METADATA
line.
For example:
METADATA|Job|FLEX:PER_JOBS_DFF|JobCode|ActiveStatus|FullPartTime|MedicalCheckupRequired|RegularTemporary|
EffectiveStartDate|EffectiveEndDate|Name|SetCode|JobFamilyName|_JOB_LEVEL(PER_JOBS_DFF=US)
MERGE|Job|US|ACC|A|F|N|R|2000/01/01|4712/12/31|Accountant|COMMON|Finance|1
On the MERGE line, the context value (US) appears in the same position as the exeld code (FLEX:PER_JOBS_DFF) on
the METADATA line.
Supplying MERGE Lines for Multiple Flexeld Codes and Contexts

When a single business object component supports multiple descriptive exelds, you can load all of the exeld data
at once. The following example shows METADATA and MERGE lines for the Contract component of the Worker object.
Each MERGE line is for a single context.
METADATA|Contract|AssignmentId|ContractId|EffectiveStartDate|EffectiveEndDate|
FLEX:PER_CONTRACT_DF|FLEX:PER_CONTRACT_LEG_DDF|_CONTRACT_GLB(PER_CONTRACT_DF=Global Data
Elements) |_Currency(PER_CONTRACT_DF=CONTRACT_DF) |_MAIN_CONTRACT(PER_CONTRACT_LEG_DDF=CH)|
_CONST_PROB_DATE(PER_CONTRACT_LEG_DDF=CN)|_NDA(PER_CONTRACT_LEG_DDF=CN)|
_COMPETETION_CLAUSE(PER_CONTRACT_LEG_DDF=CN)|_NOTICE_DURATION_UNIT(PER_CONTRACT_LEG_DDF=CN)
MERGE|Contract|E8732|39987|2013/12/14|2014/03/04|CONTRACT_DF|CN|Contract Glb value|USD|Contract Data|||
MERGE|Contract|E8732|39987|2014/03/05|4712/12/31|CONTRACT_DF|CH|Contract Glb value|USD||31/03/2015|NDA Value|
Competition Clause Value
Updating Global Segments

You can congure both global and context-specic segments for a exeld. When updating global segments in records
that have context-specic segments, set the context value to the existing context value, not Global Data Elements. If you
set the context value to Global Data Elements, then existing context-specic values are set to null because the context
has changed. For example, consider these two segments of a exeld record:
Segment Global Context
Segment 1 Yes Not applicable

Segment 2 No CN

If you update segment 1, which is a global segment, then you must set the context to CN, not Global Data Elements.
Otherwise, the existing contents of segment 2 are set to null.
71
Example of Loading Data for Descriptive Flexelds

This topic shows how to construct the METADATA line for the Contract component of the Worker object with multiple
congured descriptive exelds. The METADATA line appears automatically in the generated worker template.
The contract component supports these descriptive exelds:
• PER_CONTRACT_DF
• PER_CONTRACT_LEG_DDF
Constructing the METADATA Line for the Worker Contract

Component
The PER_CONTRACT_DF descriptive exeld is congured in Oracle HCM Cloud with the context and aribute values
shown in this table. The Hint column shows the resulting hint for each aribute.
Context Aribute Hint
Global CONTRACT_GLB (PER_ CONTRACT_ DF=Global Data

Elements)

CONTRACT_DF Currency (PER_ CONTRACT_ DF=CONTRACT_ DF)

The PER_CONTRACT_LEG_DDF descriptive exeld is congured in Oracle HCM Cloud with the context and aribute
values shown in this table. The Hint column shows the resulting hint for each aribute.
CH _MAIN_CONTRACT (PER_ CONTRACT_ LEG_DDF=CH)

CN _ CONST_ PROB_DATE (PER_ CONTRACT_ LEG_DDF=CN)

CN _NDA (PER_ CONTRACT_ LEG_DDF=CN)

CN _ COMPETITION_ CLAUSE (PER_ CONTRACT_ LEG_DDF=CN)

CN _ NOTICE_ DURATION_UNIT (PER_ CONTRACT_ LEG_DDF=CN)

72
In the generated Worker.dat template le, the Contract METADATA line includes these aribute denitions for the
exeld aributes:
METADATA|Contract|...|_CONTRACT_GLB(PER_CONTRACT_DF=Global Data Elements) |
_Currency(PER_CONTRACT_DF=CONTRACT_DF)|_MAIN_CONTRACT(PER_CONTRACT_LEG_DDF=CH)|
_CONST_PROB_DATE(PER_CONTRACT_LEG_DDF=CN)|_NDA(PER_CONTRACT_LEG_DDF=CN)|
_COMPETETION_CLAUSE(PER_CONTRACT_LEG_DDF=CN)|_NOTICE_DURATION_UNIT(PER_CONTRACT_LEG_DDF=CN)
As each aribute has a hint that identies both the descriptive exeld and the context, you can dene aributes for
multiple exelds on the same METADATA line.
How You Load Data for Extensible Flexelds

This topic describes how to construct METADATA and MERGE lines in a data le to supply extensible exeld data.
Category Code
Extensible exelds have both a exeld code and a category code. The category code is provided automatically in
generated template les and has the aribute name EFF_CATEGORY_CODE.
Constructing the METADATA Line

Unlike descriptive exelds, extensible exelds aren't an extension of a business-object component. Rather, they're
separate components in the business object hierarchy. To supply data for an extensible exeld, you simply include the
METADATA line for the extensible exeld component in the data le. Remove the names of any aributes for which
you aren't supplying data.
This example shows a METADATA line for the JobLegislative extensible exeld.
METADATA|JobLegislative|EFF_CATEGORY_CODE|FLEX:PER_JOBS_LEG_EFF|JobId(SourceSystemId)|
JobCode|SetCode|EffectiveStartDate|EffectiveEndDate|SourceSystemOwner|
SourceSystemId|LegislationCode|_EEO1_CATEGORY(PER_JOBS_LEG_EFF=HRX_US_JOBS)|
_FLSA_STATUS(PER_JOBS_LEG_EFF=HRX_US_JOBS)|_INSEE_PCS_CODE(PER_JOBS_LEG_EFF=FR)|
_ECAP_JOB(PER_JOBS_LEG_EFF=FR)|_LINE_OF_PROGRESSION(PER_JOBS_LEG_EFF=HRX_US_JOBS)
Constructing the MERGE Lines

Each MERGE line for an extensible exeld record can have only one context. In the METADATA line, you specify the
context value against the exeld code for the extensible exeld.
This example shows a METADATA line and two MERGE lines for the JobLegislative extensible exeld:
METADATA|JobLegislative|EFF_CATEGORY_CODE|FLEX:PER_JOBS_LEG_EFF|JobId(SourceSystemId)|
JobCode|SetCode|EffectiveStartDate|EffectiveEndDate|SourceSystemOwner|
SourceSystemId|LegislationCode|_EEO1_CATEGORY(PER_JOBS_LEG_EFF=HRX_US_JOBS)|
_FLSA_STATUS(PER_JOBS_LEG_EFF=HRX_US_JOBS)|_INSEE_PCS_CODE(PER_JOBS_LEG_EFF=FR)|
_ECAP_JOB(PER_JOBS_LEG_EFF=FR)|_LINE_OF_PROGRESSION(PER_JOBS_LEG_EFF=HRX_US_JOBS)
MERGE|JobLegislative|JOB_LEG|HRX_US_JOBS|OCT18EFF1|OCT18EFF1|COMMON|1990/01/01|4712/12
MERGE|JobLegislative|JOB_LEG|FR|OCT18EFF1|OCT18EFF1|COMMON|1990/01/01|4712/12/31|VISION|OCT18EFF1_LEG2|FR|||
387b|N|
Note: Unlike other components of the business-object hierarchy, extensible exelds can't be supplied in
isolation. They must be accompanied by a parent record.
73
Multirow Extensible Flexeld Contexts

You can congure an extensible exeld context with multiple rows. In this case, you congure one or more of the
exeld segments as the key that uniquely identies a single row of the multirow context. HCM Data Loader treats these
exeld segments as user-key aributes. Therefore, you can uniquely identify a single exeld record using user keys.
You must supply a value for the user-key exeld-segment aributes when creating an extensible exeld record.
When updating a multirow extensible-exeld record, you must supply either the source key or the complete user key,
including the exeld segments dened as the unique key. You can identify which exeld segments form the unique
key by reviewing the exeld-segment conguration on the Manage Extensible Flexelds page. All exeld segments
for which Unique Key is selected are user-key aributes.
Example of Loading Data for Extensible Flexelds

This topic shows how the METADATA line is constructed for a Job business object component with the congured
JobLegislative extensible exeld. The METADATA line appears automatically in the generated job template.
Constructing the METADATA Line for the JobLegislative

Extensible Flexeld
The PER_JOBS_LEG_EFF extensible exeld is congured in Oracle HCM Cloud with the context and aribute values
shown in this table. The Hint column shows the resulting hint for each aribute.
CA _EE0G (PER_ JOBS_ LEG_EFF=CA)

CA _NOC_CODE (PER_ JOBS_ LEG_EFF=CA)

CH _POSITION_TYPE (PER_ JOBS_ LEG_EFF=CH)

FR _ECAP_JOB (PER_ JOBS_ LEG_EFF=FR)

FR _ INSEE_ PCS_EXT_CODE (PER_ JOBS_ LEG_EFF=FR)

In the generated Job.dat template le, the JobLegislative METADATA line includes these aribute denitions for the
exeld aributes:
METADATA|JobLegislative|...|EFF_CATEGORY_CODE|FLEX:PER_JOBS_LEG_EFF|_EEOG(PER_JOBS_LEG_DFF=CA)|
_NOC_CODE(PER_JOBS_LEG_DFF=CA)|_POSITION_TYPE(PER_JOBS_LEG_DFF=CH)|_ECAP_JOB(PER_JOBS_LEG_DFF=FR)|
_INSEE_PCS_EXT_CODE(PER_JOBS_LEG_DFF=FR)
74
Integrating with HCM Loading Setup Objects
8 Loading Setup Objects
Guidelines for Loading Absence Cases

You use absence cases to group related absences, typically those having the same cause. For example, a worker may
take two periods of sickness absence after sustaining an injury at work. In this case, you can associate the two absences
with the same absence case for ease of management. This topic describes how to load Absence Case objects for a
worker using HCM Data Loader. Use the AbsenceCase.dat le
Absence Categories
If you associate an absence case with an absence category, then all absences in the case must have the same category.
If you specify no category for the absence case, then you can associate any type of absence with the absence case. You
dene absence categories using the Manage Absence Categories task in the Absence Administration work area.
Loading Absence Cases

These records must exist in Oracle HCM Cloud before you can create an absence case that refers to them:
• Absence category, if you're using categories

• Worker and work relationship
• Worker assignment, if absences are specic to the assignment
• Absence records
Deleting Absence Cases

You can delete Absence Case objects using HCM Data Loader. To identify the record to be deleted, supply the
AbsenceCaseCode aribute.
Examples of Loading Actions

Actions classify changes to data such as employment and compensation records. When you create or update a record,
the action value species the reason for the change. For example, the associated action for an assignment change may
be promotion or transfer. Action reasons, which are optional, provide additional information about a change. The Action
Reason Usage component of an Actions object species the relationship between an action and an existing action
reason. This topic shows how to load Actions objects and their Action Reason Usage components using HCM Data
Loader.
75
Creating Actions
This example Actions.dat le creates an Actions component and associates it with an Action Reason Usage component.
Both components are identied by source keys.
METADATA|Actions|SourceSystemOwner|SourceSystemId|ActionCode|ActionName|ActionTypeCode|StartDate|EndDate
MERGE|Actions|VISION|VISION_ACT_PROM|VISION_PROM|Vision Promotion|EMPL_PROMOTION|2000/01/01|
METADATA|ActionReasonUsage|SourceSystemOwner|SourceSystemId|ActionCodeId(SourceSystemId)|
ActionReasonId(SourceSystemId)|StartDate|EndDate
MERGE|ActionReasonUsage|VISION|VISION_PROM_PERF|VISION_ACT_PROM|VISION_PERF|2000/01/01|
Loading Translated Action Names and Descriptions

Supply action names and descriptions in the language of the user who's loading them. You supply an
ActionsTranslation.dat le to translate action names and descriptions into other enabled languages once the actions
exist. This example ActionsTranslation.dat le translates an action name and its description. The action is identied by
its source key.
METADATA|ActionsTranslation|SourceSystemOwner|SourceSystemId|Language|ActionName|Description
MERGE|ActionsTranslation|VISION|ACT_VISION_PROM|FR|Performance|Changement est survenu en raison de la
performance des employes
Deleting Actions
You can delete Actions and Action Reason Usage components using HCM Data Loader. This example Actions.dat le
deletes an Action Reason Usage component. It must include a reference to the action to which it belongs. The Action
Reason Usage component is identied by its source key.
METADATA|ActionReasonUsage|SourceSystemOwner|SourceSystemId|ActionId(SourceSystemId)
DELETE|ActionReasonUsage|VISION|ARU_VISION_PROM_PERF|ACT_VISION_PROM
Note: You can't use user keys when deleting individual Action Reason Usage components.
When you delete an Actions component, you must also delete its Action Reason Usage component explicitly.
This example Actions.dat le deletes an Actions component and its Action Reason Usage component. All DELETE
instructions are in the same le. Both components are identied by source keys.
METADATA|Actions|SourceSystemOwner|SourceSystemId
DELETE|Actions|VISION|ACT_VISION_PROM
METADATA|ActionReasonUsage|SourceSystemOwner|SourceSystemId|ActionId(SourceSystemId)
DELETE|ActionReasonUsage|VISION|ARU_VISION_PROM_PERF|ACT_VISION_PROM
Examples of Loading Action Reasons

Action reasons, which are optional, provide additional information about an action. For example, the reason for
promoting a worker may be good performance or seniority. This topic shows how to load action reasons using HCM
Data Loader.
76
Creating Action Reasons

This example ActionReasons.dat le creates two Action Reasons components. The components are identied by source
keys.
METADATA|ActionReasons|SourceSystemOwner|SourceSystemId|ActionReasonCode|ActionReason|StartDate|EndDate
MERGE|ActionReasons|VISION|AR_VISION_PERF|VISION_PERF|Performance|2000/01/01|4712/12/31
MERGE|ActionReasons|VISION|AR_VISION_TXFR|VISION_TXFR|Internal Transfer|2000/01/01|
Loading Translated Action-Reason Names

Supply action-reason names in the language of the user who's loading them. You supply an
ActionReasonsTranslation.dat le to translate action-reason names into other enabled languages once the action
reasons exist. This example translates the names of existing action reasons. The Action Reasons components are
identied by their source keys.
METADATA|ActionReasonsTranslation|SourceSystemOwner|SourceSystemId|ActionReason|Language
MERGE|ActionReasonsTranslation|VISION|AR_VISION_PERF|Accomplissement|FR
MERGE|ActionReasonsTranslation|VISION|AR_VISION_TXFR|Transfert interne|FR
Deleting Action Reasons

You can delete Action Reasons components using HCM Data Loader. This example ActionReasons.dat le deletes two
action reasons. It identies the components using source keys.
METADATA|ActionReasons|SourceSystemOwner|SourceSystemId
DELETE|ActionReasons|VISION|AR_VISION_PERF
DELETE|ActionReasons|VISION|AR_VISION_TXFR
Guidelines for Loading Calendar Events

A calendar event is an event, such as a public holiday or plant closure, on which working time may be aected. Calendar
events are optional. You specify the geographical or organizational hierarchy to which workers aected by the calendar
event must belong. The hierarchy must exist before you load the associated calendar events. This topic describes
aspects of calendar events that you must understand to load them successfully using HCM Data Loader. It also provides
examples showing how to load calendar events.
Calendar Event Lookup Categories

Calendar events have categories, which are dened in the PER_CAL_EVENT_CATEGORY lookup type. This lookup type
has one delivered value, PH, for public holidays. If you use additional categories, then you must dene them before you
load calendar events. In the Setup and Maintenance work area, use the following:
• Functional Area: Workforce Information

• Task: Manage Availability Lookups
77
Calendar Event Coverage

The Calendar Event Coverage component identies the branch of the geographical or organizational hierarchy to which
the associated calendar event applies. You identify the top node of the hierarchy branch. The event applies to that node
and its child nodes. You can also:
• Exclude from the coverage individual nodes that appear in the specied hierarchy branch.
• Override the calendar event name and its category for individual nodes in the hierarchy.
In a geographical hierarchy, the calendar event applies to all workers with assignments in the locations that you
include in the calendar event coverage. In an organizational hierarchy, the calendar event applies to all workers with
assignments in the departments that you include in the calendar event coverage. The aected workers may also have
work schedules assigned to them. In this case, the event applies to the workers only if you add it as a resource exception
to the work schedule or work schedule assignment.
Creating Calendar Events

This example CalendarEvent.dat le creates both a public holiday for Christmas Day and a half-day event for elapsed
work schedules. It identies the calendar events by their source keys.
METADATA|CalendarEvent|Name|Description|Category|CoverageType|ShortCode|StartDateTime|EndDateTime|TreeCode|
TreeStructureCode|TreeVersionName|HalfDayForElapsed
MERGE|CalendarEvent|CPTAS6||PH|G|TAS6|2017/07/11 08:00:00|2017/07/11 12:30:00|WFMTL_Global|
PER_GEO_TREE_STRUCTURE|WFMTL Bank Geography Version 1|Y
MERGE|CalendarEvent|Christmas Day 2017||PH|G|XMAS2017|2017/12/25 08:00:00|2017/12/25 18:00:00|WFMTL_Global|
PER_GEO_TREE_STRUCTURE|WFMTL Bank Geography Version 1|N
METADATA|CalendarEventCoverage|ShortCode|CoverageScope|TerritoryCode|TreeStructureCode|TreeCode|
TreeVersionName
MERGE|CalendarEventCoverage|TAS6|I|US|PER_GEO_TREE_STRUCTURE|WFMTL_Global|WFMTL Bank Geography Version 1
MERGE|CalendarEventCoverage|XMAS2017|I|US|PER_GEO_TREE_STRUCTURE|WFMTL_Global|WFMTL Bank Geography Version 1
Deleting Calendar Events

You can delete a calendar event unless it's assigned to a work schedule. This example CalendarEvent.dat le deletes a
calendar event. It identies the calendar event by its source key.
METADATA|CalendarEvent|SourceSystemOwner|SourceSystemId
DELETE|CalendarEvent|VISION|XMAS2017
Guidelines for Loading Checklist Templates

You use a checklist template to dene a sequence of related tasks with multiple performers, such as those for
onboarding a new worker. For example, you can create a checklist template for new hires, with tasks for providing
system access, issuing badges, allocating parking space, and so on. This topic describes how to create and maintain
Checklist Template objects using HCM Data Loader.
78
Checklist Categories
The checklist category must exist in the CHECKLIST_CATEGORY lookup for the target environment. In the Setup and
Maintenance work area, use the following to manage checklist categories:

• Task: Manage Checklist Lookups
The combination of checklist name and checklist category must be unique. Enterprise Onboarding Step checklists
must either already exist in the target environment or be in the same .dat le as Enterprise Onboarding checklists that
reference them.
Checklist Tasks
These rules apply to checklist tasks:
• Checklist task names must be unique for the checklist.

• If the current task has a preceding task, then the preceding task must be loaded before the current task can be
created.
• When you create tasks of the type Congurable Form, the descriptive exeld context must have been
congured in the target environment.
Checklist Actions, Areas of Responsibility, and Eligibility Proles

If you plan to use actions in the checklist template, then those actions must exist in the target environment.
If you plan to use areas of responsibility to identify task performers, then responsibility types must exist in the
PER_RESPONSIBILITY_TYPES lookup in the target environment. Alternatively, you can use one of the values shown in
this table.
Value Meaning
ORA_LN_MGR Line manager

ORA_WORKER Worker

ORA_INITIATOR Initiator

The default performer is the line manager.
If you plan to use eligibility proles in the checklist tasks, then those eligibility proles must exist in the target
environment.
79
Examples of Loading Checklist Templates

This topic provides examples showing how to create checklist templates using HCM Data Loader. These examples
reference all components using user keys.
Creating Enterprise Onboarding Checklists

This example Checklist.dat le creates:
• A parent enterprise onboarding checklist template. It has:
◦ A child checklist template

◦ A single task
◦ A Contents component
• A child enterprise onboarding checklist template. It has:
◦ Two tasks, which must be performed in the specied order

◦ A notication override for one task
◦ A Contacts component
COMMENT Create child and parent checklist templates

METADATA|Checklist|ChecklistName|Country|ChecklistCategory|AllocatedOn|CompletedOn|OffsetDays
MERGE|Checklist|Checklist_Child_1|United States|ORA_ONB_ENT_ONBOARDING_STEP|ORA_CHK_ALLOCATION_DT|
ORA_CHK_MAND_TASK_COMPLETE|0
MERGE|Checklist|Checklist_Parent_1|United States|ORA_ONB_ENT_ONBOARDING|ORA_CHK_ALLOCATION_DT|
ORA_CHK_MAND_TASK_COMPLETE|0
COMMENT Create checklist tasks for the parent and child checklist templates
METADATA|ChecklistTask|ChecklistName|Country|ChecklistCategory|ChecklistTaskName|MandatoryFlag|
DetailChecklistName|DetailChecklistCategory|DetailChecklistCountry|ActionType|PerformerRole|OwnerRole
MERGE|ChecklistTask|Checklist_Parent_1|United States|ORA_ONB_ENT_ONBOARDING|Task_Parent_1|Y|Checklist_Child_1|
ORA_ONB_ENT_ONBOARDING_STEP|United States|ORA_CHK_CHECKLIST|ORA_WORKER|ORA_CHK_INITIATOR
MERGE|ChecklistTask|Checklist_Child_1|United States|ORA_ONB_ENT_ONBOARDING_STEP|Task_Child_1|Y|||||ORA_WORKER|
ORA_CHK_INITIATOR
MERGE|ChecklistTask|Checklist_Child_1|United States|ORA_ONB_ENT_ONBOARDING_STEP|Task_Child_2|Y|||||ORA_WORKER|
ORA_CHK_INITIATOR
COMMENT Create the checklist task dependencies
METADATA|ChecklistTaskDependencies|DependencyType|ChecklistTaskName|ChecklistName|ChecklistCategory|Country|
DepenChecklistTaskName
MERGE|ChecklistTaskDependencies|ORA_DEPENDS_ON|Task_Child_2|Checklist_Child_1|ORA_ONB_ENT_ONBOARDING_STEP|
United States|Task_Child_1
COMMENT Create a checklist task notification override
METADATA|ChecklistTaskNotifications|NotifyOwner|NotifyPerformer|TaskEvent|ChecklistTaskName|ChecklistName|
ChecklistCategory|Country
MERGE|ChecklistTaskNotifications|Y|Y|ORA_CHK_TASK_ASSIGN|Task_Child_1|Checklist_Child_1|
ORA_ONB_ENT_ONBOARDING_STEP|United States
COMMENT Create a checklist contact
METADATA|ChecklistContacts|ContactTitleCode|ContactType|ChecklistName|ChecklistCategory|Country
MERGE|ChecklistContacts|ORA_ONB_ONBOARDING_SPONSOR|ORA_ONB_LN_MGR|Checklist_Child_1|
ORA_ONB_ENT_ONBOARDING_STEP|United States
COMMENT Create checklist contents
METADATA|ChecklistContents|ContentType|ChecklistName|Country|ChecklistCategory|ContentDefnCode
80
MERGE|ChecklistContents|ORA_ONB_EVENT|Checklist_Parent_1|United States|ORA_ONB_ENT_ONBOARDING|
CHKLIST_CONT_DEF67
This example ChecklistContentDetails.dat le creates the content details for the Contents component of the parent
checklist template.
COMMENT Create checklist content details
METADATA|ChecklistContentDetails|ContentCategory|ContentDefnCode|ContentSubtype|ContentType|Title|Status
MERGE|ChecklistContentDetails|ORA_ONB_INSIGHT|CHKLIST_CONT_DEF67|ORA_ONB_EVENT_STANDARD|ORA_ONB_EVENT|Event65|
A
Creating Standard Onboarding Checklists

This example Checklist.dat le creates a standard onboarding checklist template. It has:
• Two tasks, which must be performed in the specied order
• A notication override for one of the tasks
• A Contact component
COMMENT Create the checklist template
METADATA|Checklist|ChecklistName|Country|ChecklistCategory|AllocatedOn|CompletedOn|OffsetDays
MERGE|Checklist|Checklist_Onboard_1|United States|ONBOARD|ORA_CHK_ALLOCATION_DT|ORA_CHK_MAND_TASK_COMPLETE|0
COMMENT Create the checklist tasks
METADATA|ChecklistTask|ChecklistName|Country|ChecklistCategory|ChecklistTaskName|MandatoryFlag|PerformerRole|
OwnerRole
MERGE|ChecklistTask|Checklist_Onboard_1|United States|ONBOARD|Task_Child_ONB_1|Y|ORA_WORKER|ORA_CHK_INITIATOR
MERGE|ChecklistTask|Checklist_Onboard_1|United States|ONBOARD|Task_Child_ONB_2|Y|ORA_WORKER|ORA_CHK_INITIATOR
COMMENT Create the checklist task dependencies
METADATA|ChecklistTaskDependencies|DependencyType|ChecklistTaskName|ChecklistName|ChecklistCategory|Country|
DepenChecklistTaskName
MERGE|ChecklistTaskDependencies|ORA_DEPENDS_ON|Task_Child_ONB_2|Checklist_Onboard_1|ONBOARD|United States|
Task_Child_ONB_1
COMMENT Create a task notification override
METADATA|ChecklistTaskNotifications|NotifyOwner|NotifyPerformer|TaskEvent|ChecklistTaskName|ChecklistName|
ChecklistCategory|Country
MERGE|ChecklistTaskNotifications|Y|Y|ORA_CHK_TASK_ASSIGN|Task_Child_ONB_1|Checklist_Onboard_1|ONBOARD|United
States
COMMENT Create the checklist contact
METADATA|ChecklistContacts|ContactTitleCode|ContactType|ChecklistName|ChecklistCategory|Country
MERGE|ChecklistContacts|ORA_ONB_ONBOARDING_SPONSOR|ORA_ONB_LN_MGR|Checklist_Onboard_1|ONBOARD|United States
Related Topics
• Enterprise Onboarding Checklists
• Considerations for Creating Checklist Templates
Guidelines for Loading Document Delivery Preferences

Employers periodically deliver documents, such as payslips and year-end tax statements, to workers. Document
delivery preferences specify how workers receive those documents. For example, workers may receive their payslips
online. You can specify a default delivery method for a document type, and you can override the default method
on relevant work structures. For example, delivery preferences for payroll documents can be overridden at Payroll
Statutory Unit level. You can also specify delivery preferences for a person. Preferences specied at person level
override those at all other levels. This topic describes how to load Document Record Delivery Preference objects for a
person using HCM Data Loader.
81
Document Type
Before you can load document delivery preferences for a person:
• The document type must exist in the target environment.

• Document delivery preferences must be enabled for the document type. In the document type denition,
Override Hierarchy must be set to either Payroll or General, as appropriate. For example, if you're loading
delivery preferences for performance documents, then Override Hierarchy must be set to General.
Loading Document Delivery Preferences

You load document delivery preferences for a person in a DocumentDeliveryPreference.dat le.
This example DocumentDeliveryPreference.dat le loads document delivery preference records. These records are for
the document type identied by source key DT1345 and the three people identied by the person number user key.
METADATA|DocumentDeliveryPreference|DocumentTypeId(SourceSystemId)|LevelCode|PersonNumber|OnlineEnabledFlag|
PaperEnabledFlag|AllowWorkerOverrideFlag|OnlineConsentRequiredFlag|InitialConsentFlag|SourceSystemId|
SourceSystemOwner
MERGE|DocumentDeliveryPreference|DT1435|900_PERSON|Z8154257|Y|N|Y|Y|Y|LoadPref1|PSFT-US
MERGE|DocumentDeliveryPreference|DT1435|900_PERSON|Z8154806|N|Y|Y|Y|Y|LoadPref3|PSFT-US
MERGE|DocumentDeliveryPreference|DT1435|900_PERSON|Z8154813|Y|N|Y|Y|Y|LoadPref2|PSFT-US
Guidelines for Loading Document Types

A document type, such as Performance Improvement Plan or Leer of Recognition, denes the purpose and treatment
of documents of that type. When dening a document type, you include aributes, such as the document name, dates,
and issuing authority, and specify whether they're required. You can also specify an expiration notication period,
indicate whether approvals are required, and enable multiple occurrences of the document. This topic describes aspects
of the Document Type object that you must understand to load document types successfully using HCM Data Loader.
Document Categories and Subcategories

Document types belong to a document category and may also belong to a document subcategory. Document
categories, such as Expenses or Payroll, provide a way to group document types for ease of retrieval and management.
Document subcategories, such as Involuntary Deduction or Additional Income in the Payroll category, provide a further
level of detail.
Before loading document types, ensure that referenced document categories and subcategories exist in the target
environment. In the Setup and Maintenance work area, use the following to create document categories:

• Task: Manage Document Lookups
In the Setup and Maintenance work area, use the following to create document subcategories:

• Task: Manage Extended Lookup Codes
82
Document Types
When loading document types, you must provide a unique reference for the record being created. If your document
type isn't country-specic, then you must supply a source key. This rule exists because the Country aribute forms part
of the user key.
If you're loading a Document Type Delivery Preference component, then set the Hierarchy Code aribute of the
Document Type component to either GENERAL or PAYROLL. If you omit this aribute or provide no value, then
document delivery preferences aren't enabled for the document type.
Document Type Delivery Preferences

The Document Type Delivery Preference component enables users to specify delivery preferences for documents of the
associated type. For example, you could enable users to specify that payslips can be delivered both on paper and online.
The delivery preferences for the document type can be overridden. That is, you can specify document delivery
preferences:
• At the payroll statutory unit level, for documents in the PAYROLL category
• At the legal employer level, for documents in all other categories
In both cases, delivery preferences can be further overridden at department and location levels.
83
This gure summarizes the override hierarchy for document delivery preferences. Entries at any level of the hierarchy
override those above them.
Document Type
Legal Employer Payroll Statutory Unit
Department
Location
If you set the Allow Worker Override aribute to Y, then workers can specify document delivery preferences for
themselves. Worker preferences override preferences at all other levels.
Related Topics
• How You Set Preferences for Document Delivery
• Document Types and Categories
84
Examples of Loading Document Types

This topic provides examples showing how to load and manage Document Type objects using HCM Data Loader.
Creating Document Types Using Source Keys

This example DocumentType.dat le creates one global and one country-specic document type. The document types
are identied using source keys.
METADATA|DocumentType|SourceSystemOwner|SourceSystemId|DocumentType|Description| LegislationCode|CategoryCode|
AuthorizationRequiredFlag|MultipleOccurencesFlag|ActiveInactiveFlag|PublishRequiredFlag|HierarchyCode|
DocumentNameRequired|DocumentNumberRequired|DateFromRequired|DateToRequired|IssuingCountryRequired|
IssuingLocationRequired|IssuingAuthorityRequired|IssuedDateRequired|CommentsRequired
MERGE|DocumentType|VISION|DTYPETest001|RS Global DocType1|RS Global DocType1 Description||PAYROLL|Y|Y|N|Y|
GENERAL|R|R|Y|Y|Y|Y|Y|Y|Y
MERGE|DocumentType|VISION|DTYPETest003|RS US DocType1|RS US DocType1 Description|US|AUDIT|Y|Y|N|Y|PAYROLL|R|R|
Y|Y|Y|Y|Y|Y|Y
Creating Document Types Using User Keys

This example DocumentType.dat le creates one country-specic document type. The document type is identied
using user keys.
METADATA|DocumentType|DocumentType|Description|Country|CategoryCode|AuthorizationRequiredFlag|
MultipleOccurencesFlag|ActiveInactiveFlag|PublishRequiredFlag|HierarchyCode|DocumentNameRequired|
DocumentNumberRequired|DateFromRequired|DateToRequired|IssuingCountryRequired|IssuingLocationRequired|
IssuingAuthorityRequired|IssuedDateRequired|CommentsRequired
MERGE|DocumentType|US Audit Doc Type|US Audit Doc Type Description|United States|AUDIT|Y|Y|Y|Y|PAYROLL|R|R|Y|
Y|Y|Y|Y|Y|Y
Note: If the document type were global, you would have to provide a source key rather than a user key. This
requirement exists because Country is a required aribute of the user key.
Creating Document Types with Delivery Preferences

This example DocumentType.dat le creates a country-specic document type with delivery preferences for the
document type, payroll statutory unit, and department. The document type and delivery preferences are identied
using source keys.
METADATA|DocumentType|SourceSystemOwner|SourceSystemId|DocumentType|Description| LegislationCode|CategoryCode|
AuthorizationRequiredFlag|MultipleOccurencesFlag|ActiveInactiveFlag|PublishRequiredFlag|HierarchyCode|
DocumentNameRequired|DocumentNumberRequired|DateFromRequired|DateToRequired|IssuingCountryRequired|
IssuingLocationRequired|IssuingAuthorityRequired|IssuedDateRequired|CommentsRequired
MERGE|DocumentType|VISION|DTYPETest003|RS US DocType1|RS US DocType1 Description|US|AUDIT|Y|Y|N|Y|PAYROLL|R|R|
Y|Y|Y|Y|Y|Y|Y
METADATA|DeliveryPreference|SourceSystemOwner|SourceSystemId|DocumentTypeId(SourceSystemId)|
InitialConsentValueFlag|OnlineConsentRequiredFlag|OnlineEnabledFlag|PaperEnabledFlag|AllowWorkerOverrideFlag|
EmailEnabledFlag|LegislationCode|LevelCodeName|DocumentTypeCountry|DocumentTypeLegislationCode|
PayrollStatutoryUnitName|DepartmentName
85
MERGE|DeliveryPreference|VISION|DTYPETest003_Pref0|DTYPETest003|N|N|Y|Y|N|N|US||US|US||
MERGE|DeliveryPreference|VISION|DTYPETest003_Pref1|DTYPETest003|N|N|Y|Y|N|N|US|Payroll Statutory Unit|US|US|
GBI HCM Widgets USA|
MERGE|DeliveryPreference|VISION|DTYPETest003_Pref2|DTYPETest003|N|N|Y|Y|N|N|US|Department|US|US|GBI HCM
Widgets USA|HCM-1001-Corporate
Loading Translated Document Types and Descriptions

This example DocumentTypeTranslation.dat le translates an existing document type and its description. It identies
the document type using source keys.
METADATA|DocumentTypeTranslation|SourceSystemOwner|SourceSystemId|BaseDocumentType|LegislationCode|SourceLang|
Language|DocumentType|Description
MERGE|DocumentTypeTranslation|VISION|DTYPETest001|RS Global DocType1||US|JP|RS Global DocType1 JP|RS Global
DocType1 DESC JP
MERGE|DocumentTypeTranslation|VISION|DTYPETest003|RS US DocType1|US|US|JP|RS US DocType1 JP|RS US DocType1
DESC JP
Deleting Document Types

You can delete a document type only if no document records of that type exist. When you delete a document type, any
associated delivery preferences are also deleted. This example DocumentType.dat le deletes a document type that's
identied by its source key.
METADATA|DocumentType|SourceSystemOwner|SourceSystemId
DELETE|DocumentType|VISION|DTYPETest001
DELETE|DocumentType|VISION|DTYPETest003
This example DocumentType.dat le deletes a document type that's identied by its user key.
METADATA|DocumentType|DocumentType|Description|Country
DELETE|DocumentType|US Audit Doc Type|US Audit Doc Type Description|United States
Examples of Loading Extended Lookup Codes

You use extended lookup codes to provide subcategories for lookup codes. The associated lookup codes must already
exist when you load Extended Lookup objects using HCM Data Loader. If the lookup codes are for specic legislations,
then you can supply extended lookup codes for those legislations only. For example, if a lookup code has the +FR tag,
then you can supply extended lookup codes for the FR legislation code only. This topic provides examples showing how
to load Extended Lookup objects using HCM Data Loader.
Creating Extended Lookup Codes

This example ExtendedLookupCode.dat le creates extended lookup codes for the CONTRACT_TYPE lookup type. It
identies the extended lookup codes using source keys.
METADATA|ExtendedLookupCode|SourceSystemOwner|SourceSystemId|LookupType|LookupCode|LegislationCode|
ExtendedLookupCode|ExtendedLookupCodeName
MERGE|ExtendedLookupCode|VISION|ELC_CONTRACT_LIMITED|CONTRACT_TYPE|5|NO|L|Limited Contract
86
MERGE|ExtendedLookupCode|VISION|ELC_CONTRACT_DIRECTOR|CONTRACT_TYPE|FR_CEO_MANDATE|FR|DC|Director Contract
Loading Translated Extended Lookup Code Names

Supply the names of extended lookup codes in the language of the user who's loading them. You supply an
ExtendedLookupCodeTranslation.dat le to translate the names of extended lookup codes into other enabled
languages once the codes exist. This example translates the name of an existing extended lookup code. It identies the
code by its source key.
METADATA|ExtendedLookupCodeTranslation|SourceSystemOwner|SourceSystemId|Language|ExtendedLookupCodeName
MERGE|ExtendedLookupCodeTranslation|VISION|ELC_CONTRACT_LIMITED|FR|Contrat a Duree Limitee
Deleting Extended Lookup Codes

You can delete Extended Lookup objects using HCM Data Loader. This example ExtendedLookupCode.dat le deletes
specic extended lookup codes for the CONTRACT_TYPE lookup code. It identies the extended lookup codes using
source keys.
METADATA|ExtendedLookupCode|SourceSystemOwner|SourceSystemId
DELETE|ExtendedLookupCode|VISION|ELC_CONTRACT_LIMITED
DELETE|ExtendedLookupCode|VISION|ELC_CONTRACT_DIRECTOR
Guidelines for Loading Name Formats

A name format is a set of rules for combining individual name components, such as rst name and last name, to form a
complete person name. Name formats are specic to a legislation and name-format type. The name-format types are
display name, list name, order name, and full name. The predened global format is used when no format exists for a
format type and legislation. This topic describes how to load Name Format objects using HCM Data Loader.
Understanding Format Masks

A format mask is a string of codes used to construct a name format. The codes represent the required name
components, symbols, and special characters. Use the codes shown in this table to identify the name components.
Code Name Component
$FIR$ First Name

$LAS$ Last Name

$MID$ Middle Name

$PLN$ Previous Last Name

87
Code Name Component
$KNA$ Known As

$HNS$ Honors

$PNA$ Prex

$SUF$ Sux

$TIT$ Title

$MLR$ Military Rank

$INF1$ through $INF30$ Name Information 1 through Name Information 30

Use the codes shown in this table for symbols and special characters.
Code Description Value
$SPA$ space space character ( )

$COM$ comma ,

$OPE$ left parenthesis (

$CLO$ right parenthesis )

$QUO$ quotation mark "

$DOT$ period .

$SLA$ slash /

$COL$ colon :

$SEM$ semicolon ;

$ATT$ at sign @

88
Constructing a Format Mask

The format mask must:
• Start and end with a vertical bar (|).

• Separate each name component with two vertical bars (||).
The vertical bar is the default delimiter for HCM Data Loader .dat les. If you haven't selected a dierent default
delimiter, then you must prex the vertical bar in the name-format mask with the HCM Data Loader escape character.
The escape character ensures that HCM Data Loader ignores delimiters in the format mask. The default escape
character is the backslash (\). For example, to provide a format mask for the name format Title Last Name, First Name
(Known As), you supply the codes for each element of the name as shown in this table.
Element Codes
Title space $TIT$$SPA$

Last Name, space $LAS$$COM$$SPA$

First Name space $FIR$$SPA$

(Known As) $OPE$$KNA$$CLO$

In the format mask, each name component must be delimited by two vertical bars:
$TIT$$SPA$\|\|$LAS$$COM$$SPA$\|\|$FIR$$SPA$\|\|$OPE$$KNA$$CLO$
In addition, the format mask must start and end with a single vertical bar:
\|$TIT$$SPA$\|\|$LAS$$COM$$SPA$\|\|$FIR$$SPA$\|\|$OPE$$KNA$$CLO$\|
Creating Name Formats

This example NameFormat.dat le creates a display name for France in the format Title First Name Last Name. The
name format is identied by its source key.
METADATA|NameFormat|SourceSystemOwner|SourceSystemId|FormatName|LegislationCode|UserFormatChoice|FormatMask
MERGE|NameFormat|VISION|NF_FR_L_DISP|DISPLAY_NAME|FR|L|\|$TIT$$SPA$\|\|$FIR$$SPA$\|\|$LAS$\|
Deleting Name Formats

You can delete a Name Format object using HCM Data Loader, provided that the name format isn't being used. This
example NameFormat.dat le deletes a name format. It identies the name format by its source key.
METADATA|NameFormat|SourceSystemOwner|SourceSystemId
DELETE|NameFormat|VISION|NF_FR_L_DISP
89
Examples of Loading Person Types

System person types are predened values that identify groups such as employees and contingent workers. You can't
create, edit, or delete system person types. However, each system person type is associated with one or more user
person types, which further categorize the group. You can create, edit, and delete user person types. For example, you
could dene Associate and Remote Worker as user person types of the Employee system person type. For any system
person type, one user person type must be identied as the default value. This topic provides examples showing how to
load and manage user Person Type objects using HCM Data Loader.
Creating Person Types

This example PersonType.dat le creates the Ocer and Rating user person types for the Employee system person
type. It identies the person types using source keys.
METADATA|PersonType|SourceSystemOwner|SourceSystemId|SystemPersonType|UserPersonType|ActiveFlag|DefaultFlag
MERGE|PersonType|VISION|PT_EMP_OFFICER|EMP|Officer|Y|N
MERGE|PersonType|VISION|PT_EMP_RATING|EMP|Rating|Y|N
Loading Translated Person-Type Names

Supply person-type names in the language of the user who's loading them. You supply a PersonTypeTranslation.dat le
to translate person-type names into other enabled languages once the person types exist. This example translates the
name of an existing person type. The person type is identied by its source key.
METADATA|PersonTypeTranslation|SourceSystemOwner|SourceSystemId|Language|UserPersonType
MERGE|PersonTypeTranslation|VISION|PT_EMP_OFFICER|FR|Officier
Deleting Person Types

You can delete Person Type objects using HCM Data Loader, provided that the person type isn't being used. This
example PersonType.dat le deletes person types and any translated versions of the person-type names. It identies
the person types by their source keys.
METADATA|PersonType|SourceSystemOwner|SourceSystemId
DELETE|PersonType|VISION|PT_EMP_OFFICER
DELETE|PersonType|VISION|PT_EMP_RATING
Examples of Loading Resource Exceptions

A resource exception is a deviation in availability from a work schedule or schedule assignment. The resource exception
denes when a resource is unavailable. For example, a worker may be aending training and therefore unavailable
between specied dates. You create resource exceptions, which are optional, for specic work schedules or schedule
90
assignments. The work schedule or schedule assignment must exist before you can create an associated resource
exception. This topic provides examples showing how to load Resource Exception objects using HCM Data Loader.
Creating Resource Exceptions

This example ResourceException.dat le creates a resource exception for a hospital appointment. It identies the
resource exception by its source key.
METADATA|ResourceException|SourceSystemOwner|SourceSystemId|ExceptionName|StartDateTime|EndDateTime
MERGE|ResourceException|VISION|RE_VISION_HOSPITAL|Hospital Appointment|2015/08/15 08:00:00|2015/08/15 17:00:00
Deleting Resource Exceptions

You can delete a Resource Exception object using HCM Data Loader, provided that it's not referred to by a work
schedule. This example ResourceException.dat le deletes an unused resource exception. It identies the resource
exception by its source key.
METADATA|ResourceException|SourceSystemOwner|SourceSystemId
DELETE|ResourceException|VISION|RE_VISION_HOSPITAL
Guidelines for Loading Time and Labor Event Groups

An event group is a group of related events, such as changes to a worker's assignment, that require a retroactive
recalculation of time cards. This topic explains some aspects of event groups that you must understand to load them
successfully using HCM Data Loader.
Loading Event Groups

These rules apply to the Event Group component:
• You can set EventGroupCode and EventGroupName to any user-dened value that identies the purpose of
the group.
• To resubmit time cards, you must set EventGroupType to A (Action).
These rules apply to the Date Tracked Event, Event Value Change, and Event Value Qualier components:
• If you set UpdateType to DT_INSERT, then leave ColumnName blank.

• EventGroupCode identies the group to which the component belongs.
These rules apply to the Event Value Change Component:
• Sequence species the sequence in which qualifying conditions are loaded. The sequence is important, as
conditions can exist in a hierarchical relationship to each other. The sequence number also provides a way for
other nodes in the condition hierarchy to refer to a condition.
• ValidEvent must be Y or N. It species whether the condition qualies or disqualies the event. For example,
your qualifying condition may specify that an event is valid for any location change, except when moving from
New York to San Francisco. In this case, you dene two rows as shown in this table:
91
Condition From Value To Value Valid Event
Parent Any Any Y

Child New York San Francisco N

• FromValue and ToValue can be any valid value for the column or <ANY VALUE> to indicate that any value
can trigger resubmission of time cards.
• ParentEvtValChangeSequence is the sequence number of the parent Event Value Change component in the
condition hierarchy.
These rules apply to the Event Value Qualier component:
• Sequence is the sequence of the topmost Event Value Change component in the value change hierarchy for
given Date Tracked Event and Event Value Qualier components.
• QualierName is the qualier name, which is predened in the PAY_EVENT_QUALIFIERS_F table.
• QualierValue must be Y or N. If you set this value to Y, then updates to the worker's primary assignment
trigger the event. If you set this value to N, then updates to the worker's secondary assignments trigger this
event.
Examples of Loading Time and Labor Event Groups

An event group is a group of related events, such as changes to a worker's assignment, that require a retroactive
recalculation of time cards. This topic shows how to create event groups using HCM Data Loader.
Loading Event Groups

This example EventGroup.dat le creates a single Event Group component, which is identied by its user key. For
resubmiing time cards, the EventGroupType aribute value must be A.
METADATA|EventGroup|EventGroupCode|EventGroupName|EventGroupType
MERGE|EventGroup|JobChangeEventGroup|JobChangeEventGroup|A
Loading Date Tracked Events

The Date Tracked Event component identies the type of event (update, correction, or insert) that triggers resubmission
of time cards. It also identies the aected object and the aected column or value in that object. This example
identies the Date Tracked Event component by its user key.
METADATA|DateTrackedEvent|ColumnName|UpdateType|EventGroupCode|DatedObjectName
MERGE|DateTrackedEvent|JOB_ID|DT_UPDATE_COLUMN|JobChangeEventGroup|
oracle.apps.hcm.employment.core.publicModel.entity.EmployeeAssignmentDEO
92
Loading Event Value Changes

The Event Value Change component species the value changes that can cause time cards to be resubmied. For
example, the Date Tracked Event component may be monitoring changes to a worker's job. In that case, the Event
Value Change component could specify the current and new jobs that trigger resubmission of time cards. This example
identies the Event Value Change component by its user key.
METADATA|EventValueChange|ColumnName|UpdateType|EventGroupCode|DatedObjectName|Sequence|ValidEvent|FromValue|
ToValue|EffectiveStartDate|EffectiveEndDate
MERGE|EventValueChange|JOB_ID|DT_UPDATE_COLUMN|JobChangeEventGroup|
oracle.apps.hcm.employment.core.publicModel.entity.EmployeeAssignmentDEO|1|Y|<ANY_VALUE>|<ANY_VALUE>|
1950/01/01|4712/12/31
Loading Event Value Qualiers

Using the optional Event Value Qualier component, you can qualify an event. For example, when monitoring job
changes, you could use this component to specify that only job changes in primary assignments are of interest. This
example identies the Event Value Qualier component by its user key.
METADATA|EventValueQualifier|ColumnName|UpdateType|EventGroupCode|DatedObjectName|Sequence|EffectiveStartDate|
EffectiveEndDate|QualifierName|QualifierValue
MERGE|EventValueQualifier|JOB_ID|DT_UPDATE_COLUMN|JobChangeEventGroup|
oracle.apps.hcm.employment.core.publicModel.entity.EmployeeAssignmentDEO|1|1950/01/01|4712/12/31|
EmployeeAssignmentDEO Primary Flag|Y
Columns and Event Source Objects for Time and Labor

Events
When dening a Time and Labor event, you must provide values for the Column Name (ColumnName) and Event
Source Object Name (DatedObjectName) aributes. This topic lists the values of these aributes for each Time and
Labor event.
Event Column Name Event Source Object Name
Marital Status MARITAL_STATUS oracle. apps. hcm. people.

core. protectedModel. entity.
PersonLegislativeInfoDEO

Home Location ADDRESS_ID oracle. apps. hcm. addresses. publicModel.

entity. AddressDEO

Eective Start Date EFFECTIVE_ START_DATE oracle. apps. hcm. employment.

core. publicModel. entity.
EmployeeAssignmentDEO
93
Eective End Date EFFECTIVE_ END_DATE oracle. apps. hcm. employment.


Business Unit BUSINESS_ UNIT_ID oracle. apps. hcm. employment.


Grade Ladder GRADE_ LADDER_PGM_ID oracle. apps. hcm. employment.


Working Hours NORMAL_HOURS oracle. apps. hcm. employment.


Standard Working Hours TOTAL_HOURS oracle. apps. hcm. employment.

WorkingHourPaernDEO

Job JOB_ID oracle. apps. hcm. employment.


Grade GRADE_ID oracle. apps. hcm. employment.


Is Manager MANAGER_FLAG oracle. apps. hcm. employment.


Location LOCATION_ID oracle. apps. hcm. employment.


Position POSITION_ID oracle. apps. hcm. employment.


Worker Category EMPLOYEE_ CATEGORY oracle. apps. hcm. employment.


94
Assignment Category EMPLOYMENT_ CATEGORY oracle. apps. hcm. employment.


Regular or Temporary PERMANENT_ TEMPORARY_ FLAG oracle. apps. hcm. employment.


Full-Time or Part-Time FULL_PART_TIME oracle. apps. hcm. employment.


Person Type PERSON_TYPE_ID oracle. apps. hcm. employment.


Hourly Paid or Salaried HOURLY_ SALARIED_CODE oracle. apps. hcm. employment.


Frequency FREQUENCY oracle. apps. hcm. employment.


Working at Home WORK_AT_HOME oracle. apps. hcm. employment.


Legal Employer LEGAL_ ENTITY_ID oracle. apps. hcm. employment.


Department ORGANIZATION_ ID oracle. apps. hcm. employment.


Reporting Establishment ESTABLISHMENT_ ID oracle. apps. hcm. employment.


Bargaining Unit BARGAINING_ UNIT_CODE oracle. apps. hcm. employment.


Collective Agreement COLLECTIVE_ AGREEMENT_ID oracle. apps. hcm. employment.


95
Union Member LABOR_ UNION_ MEMBER_FLAG oracle. apps. hcm. employment.


Overtime Period OVERTIME_ PERIOD oracle. apps. hcm. employment.


Manager MANAGER_ID oracle. apps. hcm. employment.

AssignmentSupervisorDEO

Work Day Denition WORK_ DAY_DEF_ID oracle. apps. hcm. employment.

WorkingHourPaernDEO

Assignment DFFs Provide the column name for the global oracle. apps. hcm. employment.
context DFF. core. publicModel. entity.

Examples of Loading Time and Labor Event Actions

An event action denes how to react to an event, for example, whether to recalculate time cards when a worker's job or
location changes. This topic shows how to create event actions using HCM Data Loader.
Loading Event Actions

This example EventAction.dat le creates a single Event Action component, which is identied by its user key.
METADATA|EventAction|EventActionCode|EffectiveStartDate|EffectiveEndDate|EventActionName|EventActionTypeCode|
LookbackTimeDefinitionCode|ActionSubmission|ProcessMode|AutoApprove
MERGE|EventAction|JobChangeAction|1950/01/01|4712/12/31|JobChangeAction|ORA_HWM_ACTION_TYPE_TC_RESUBMIT|
12_MONTHS_AGO_MONTH_START_DATE|SYNC|MANUAL|Y
These rules apply:
• To resubmit time cards, you must set EventActionTypeCode to ORA_HWM_ACTION_TYPE_TC_RESUBMIT.

• The LookbackTimeDenitionCode value identies a time period before the action execution date. Time cards
from this period are considered for resubmission. Use one of these values:
◦ 3_MONTHS_AGO_MONTH_START_DATE
96
For example, a job change is eective on 1st January 2018 and the time-card resubmission process runs on that
date. If LookbackTimeDenitionCode is 3_MONTHS_AGO_MONTH_START_DATE, then time cards from 1st
October 2017 are considered for resubmission.
ActionSubmission must be SYNC for time-card resubmission.

• ProcessMode determines whether time cards are resubmied automatically by the process or marked for
resubmission but manually resubmied. Set it to AUTO or MANUAL, as appropriate.
• AutoApprove determines whether time cards are approved automatically after they're resubmied. Valid
values are Y and N.
Loading Event Action Criteria

The Event Action Criteria component associates an event action with a specic group of workers. This Event Action
Criteria component is identied by its user key.
METADATA|EventActionCriteria|EventActionCode|EffectiveStartDate|EffectiveEndDate|HCMGroupCode
MERGE|EventActionCriteria|JobChangeAction|1950/01/01|4712/12/31|ABC_GRP
HcmGroupCode values are dened in the GRP_CODE column of the HWM_GRPS_VL table view and can be accessed
using SQL. You can omit the Event Action Criteria component if the action applies to all workers.
Loading Event Group Actions

The Event Group Action component associates an event action with an event group. This Event Group Action
component is identied by its user key.
METADATA|EventGroupAction|EventActionCode|EffectiveStartDate|EffectiveEndDate|EventGroupCode
MERGE|EventGroupAction|JobChangeAction|1950/01/01|4712/12/31|JobChangeEventGroup
Related Topics
• Tables and Views for Oracle HCM Cloud
97
98
Integrating with HCM Loading Workers
9 Loading Workers
Overview of Loading Workers

The Worker object includes all information related to a person and his or her work relationships. This topic describes
some general considerations that apply when you load workers.
The Worker Hierarchy

Select the Worker object on the View Business Objects page to review its component hierarchy:
Using Source Keys

You can't update most components of the worker hierarchy if you supply only a user key. This restriction exists because
the aribute that you want to change is the aribute that's used to identify the record. For example, in the Person
Address component, the AddressLine1 aribute is used both to identify the address to update and to supply the
new value. Therefore, you're recommended always to supply source keys when creating workers and use them when
updating worker records.
Multiple Instances of a Component

A person can have multiple instances of some components, such as Person Address, Person Phone, and Person Email.
When you load multiple instances of a component for a person, you must:
• Identify one of the records as primary using the PrimaryFlag aribute of the component.
• Process the occurrences together and include the parent Worker component in the le. If the worker already
exists in Oracle HCM Cloud, then you can include just the primary-key aributes of the worker.
The Employment Model

You must understand the employment model in the legal employer to which you're loading work relationships and
assignments. In any legal employer, the Employment Model option can be set to one of these values:
• 2 Tier - Single Assignment
• 2 Tier - Multiple Assignment
• 2 Tier - Single Contract - Single Assignment
• 2 Tier - Multiple Contract - Single Assignment
• 3 Tier - Single Employment Terms - Single Assignment
• 3 Tier - Single Employment Terms - Multiple Assignment
99
• 3 Tier - Multiple Employment Terms - Single Assignment

• 3 Tier - Multiple Employment Terms - Multiple Assignment
Regardless of the employment model, an employment terms record is always created for an assignment. Therefore,
you must include an Employment Terms component in the .dat le. When loading multiple work relationships or
assignments for a person, you must identify which is primary using the PrimaryFlag aribute. A person must have only
one primary work relationship at a time and only one primary assignment in each work relationship.
Dening Referenced Values

Many components of the Worker object include values, such as person type and assignment status, that must exist in
the target environment. Perform the tasks shown in this table to dene relevant values before you load data.
Task Description
Manage Actions Denes the actions used to classify changes to employment data

Manage Person Types Denes subcategories of the predened person types, such as Employee and Nonworker

Manage Assignment Status Denes status values, such as active, inactive, or suspended, for assignments

In addition, you must have reviewed and updated lists of values, such as address types, phone types, ethnicity,
and marital status, before loading workers. You may have performed this step during implementation. If you're
synchronizing assignments from positions, then you must enable position synchronization before you load
assignments.
Worker Termination
You terminate work relationships, not workers. When you terminate a work relationship using HCM Data Loader, its
child components, such as Assignment components, are terminated automatically. Don't try to terminate other child
components of the worker object, such as Person Name. The person record must continue to exist and be returned in
search results, for example.
Loading the Person Aributes Descriptive Flexeld

The Person Aributes (PER_PERSONS_DFF) descriptive exeld isn't date-eective, and a person can have only one
context value at a time. If you load a new context value, then it overwrites any existing context value.
Related Topics
• Employment Model
• Source Keys
• How You Review Lists of Values
100
• Position Synchronization
Guidelines for Preparing to Load Workers

Before you load Worker objects, you must decide:
• Whether you want user accounts to be created automatically for those workers.
• Whether user credentials are to be sent automatically to new users.
• Which roles are to be provisioned automatically to new users. User accounts created without at least one role
are automatically suspended.
This topic describes each of these decisions.
Creating User Accounts Automatically

The enterprise option User Account Creation controls whether user accounts are created automatically for new
workers, regardless of how those workers are created. If user accounts are created automatically in your enterprise,
then you can prevent accounts being created for individual workers. To prevent account creation, include the
GeneratedUserAccountFlag aribute of the User Information component and set it to N.
Note: If User Account Creation is set to None, then you can't override it for individual workers.
You can supply a user name in the User Information component of the Worker object that you upload. Otherwise, user
names are in the default format for the default user category, as specied on the Security Console. The default user-
name format is the primary work email. Any changes that you make to the default format for a user category apply to all
new users in the category, regardless of how they're created.
Tip: New users are added to the default user category. You can move an existing user to a dierent user
category by seing the UserCategory aribute of the User object.
Sending User Credentials to New Users

If you create user accounts automatically for uploaded workers, then you can notify the users automatically of their user
names and passwords. Set the SendCredentialsEmailFlag aribute of the User Information component to Y for any
worker who should receive this mail. SendCredentialsEmailFlag is set to N by default.
If you set SendCredentialsEmailFlag to Y for any worker, then you must ensure that a valid notication template is
enabled for the default user category for this event. Two predened templates exist:
• The New Account Template is for notifying the user.
• The New Account Manager Template is for notifying the user's manager.
You can also create notication templates. Notication templates are managed on the Security Console. Any changes
made to notication templates apply to the user category.
Provisioning Roles to New Users

When a user account is created automatically for a worker, roles are provisioned automatically to the user as specied
by current role-provisioning rules. Conrm that appropriate role mappings exist for users created by bulk upload.
101
Note: All user accounts must have at least one role to remain active. If appropriate role mappings don't exist
and you're not loading roles for manual assignment, then the new user account is immediately suspended.
To avoid this automatic suspension of the account, dene role mappings for workers before you load those
workers.
Related Topics
• Role Mappings
Eective Start and End Dates for Worker Components

Many components of the Worker object are date eective. When creating workers, you must ensure that the eective
dates of individual worker components don't conict. This topic suggests an approach to seing the earliest eective
start date and last eective end date for each date-eective component. You don't have to follow this guidance.
However, you must ensure that eective dates are aligned for the complete Worker object.
This table suggests how to set earliest eective start dates and last eective end dates for date-eective worker
components.
Component Earliest Eective Start Date Last Eective End Date
Worker Earliest start date of the worker. The end of time.

Person Address On or after the earliest start date of the The end of time.
worker.

Person Legislative Data Earliest start date of the worker. The end of time.

Person Name Earliest start date of the worker. The end of time.

Person Visa On or after the earliest start date of the The end of time.
worker.

Person Contact Relationship On or after the earliest start date of the The eective end date of the contact
worker. relationship.

Employment Terms The rst employment terms must have an The end of time.
eective start date equal to the start date
of the corresponding work relationship.
Subsequent employment terms can have
an eective start date on or after the
start date of the corresponding work
relationship.

Assignment The rst assignment must have an The end of time.

eective start date equal to the earliest
eective start date of any corresponding
employment terms. Subsequent
102
Component Earliest Eective Start Date Last Eective End Date
assignments can have an eective start

date on or after the earliest eective start
date of the corresponding employment
terms. Further restrictions on the earliest
eective start date may exist, depending
on the employment model being used.

Assignment Extra Information On or after the earliest eective start date The end of time.
of the corresponding assignment.

Assignment Grade Steps On or after the earliest eective start date The eective end date of the grade steps.

Assignment Manager On or after the earliest eective start date The eective end date of the manager
of the corresponding assignment. relationship.

Assignment Work Measure On or after the earliest eective start date The end of time.

Contract The earliest eective start date of the The end of time.
corresponding employment terms.

Worker Extra Information On or after the earliest start date of the The end of time.
worker.

Guidelines for Deleting Worker Components

You can delete some components of the Worker object but not the entire worker. For information about deletion
support for individual Worker components, see the component details on the View Business Objects page. This topic
provides additional information about deleting some of the Worker components using HCM Data Loader.
This table provides information about the circumstances in which you can delete some components of the Worker
object.
Component Deletion Supported Notes
Assignment Grade Steps Yes

If you set the GradeId aribute of
an assignment to #NULL, then any
associated Assignment Grade Steps
component is deleted automatically.
Therefore, if you include a DELETE
instruction for the Assignment Grade
Steps component in the same .dat le as
the assignment, an error occurs.
103
Component Deletion Supported Notes
Person Address Yes Subject to country-specic regulations,

you can delete any address. When
multiple mailing addresses exist, you must
delete all nonprimary mailing addresses
before you can delete the primary mailing
address. Alternatively, identify a new
primary mailing address before you delete
the current primary mailing address.

Person Email Yes When only one email exists, you can
delete it. When multiple emails exist,
you must delete all nonprimary emails
before you can delete the primary email.
Alternatively, identify a new primary email
before you delete the current primary
email.

Person Legislative Data Yes One legislative data record must exist for
a worker. You can't delete the only record.
You can delete additional records.

Person Phone Yes When only one phone exists, you can
delete it. When multiple phones exist,
you must delete all nonprimary phones
before you can delete the primary phone.
Alternatively, identify a new primary
phone before you delete the current
primary phone.

User Information No The User Information component is

available only when you create workers.
This component isn't available when you
update workers.

Person User Manual Roles No The Person User Manual Roles component
is available only when you create workers.
This component isn't available when you
update workers.

To remove a single role from a worker,
you use the User object rather than the
Worker object. To remove multiple roles
from a worker, you use the User Role
component of the User object.

Work Relationship Yes

When deleting a work
relationship, you must include the
CancelWorkRelationshipFlag aribute
with a value of Y.
104
How You Check for Duplicate Person Records

When you load person records using HCM Data Loader, you can request a check for duplicate records. In this case, an
error message is raised if you try to load a duplicate record. This topic describes how to request duplicate checking for
individual person records. It also describes how this option works in conjunction with the enterprise seing for duplicate
checking.
Duplicate Checking for Individual Person Records

To request duplicate checking for a person record, you include the PersonDuplicateCheck aribute of the Worker
object. This aribute can have one of the values shown in this table. The Description column identies the aributes
that the application uses in each case to identify duplicate records.
Value Description
ORA_NONE or a blank value No duplicate checking occurs

ORA_ LN_ FI_ DOB_GEN_NID Either the last name, rst-name initial, date of birth, and gender or the national ID

ORA_ LN_FI_DOB_NID Either the last name, rst-name initial, and date of birth or the national ID

ORA_ LN_ FN_ DOB_GEN_NID Either the last name, rst name, date of birth, and gender or the national ID

ORA_NID_ONLY The national ID

For example, if you set PersonDuplicateCheck to ORA_LN_FI_DOB_NID, then a duplicate record is identied if one of
these situations occurs:
• The last name, rst-name initial, and date of birth all match those of an existing person record.
• The national ID matches that of an existing person record.
Note: National ID values must be formaed. For example, to load the US social security number 987-65-4322,
you must include the hyphens. Don't specify the number as 987654322. If you omit the formaing, which is
country-specic, then duplicate person records aren't found when the checking is based on national identier.
Enterprise Duplicate Checking

The enterprise option Person Creation Service Duplicate Check controls whether checks for duplicate person
records occur by default when you load person records in bulk. If you exclude the PersonDuplicateCheck aribute
of the Worker object, then the current seing of Person Creation Service Duplicate Check applies. If you include the
PersonDuplicateCheck aribute, then the current seing of Person Creation Service Duplicate Check is ignored for
the relevant person record.
105
Person Numbers in Worker Objects

Each person record, regardless of person type or number of work relationships, has a unique person number. Person
numbers can be either generated automatically or entered manually, depending on the seing of the enterprise Person
Number Generation Method option. This topic describes ways of providing person numbers for uploaded Worker
objects.
Automatically Generated Person Numbers

To generate person numbers automatically, you set the Person Number Generation Method option to either
Automatic Prior to Submission or Automatic Upon Final Save. When you load person records to environments where
person numbers are generated automatically, you supply no person number. A number is generated automatically on
upload.
When you load a person record without a person number, you must supply a source key to identify the
person record uniquely. You must use the same key for all child components of the Worker object using the
PersonId(SourceSystemId) aribute and hint.
Manually Entered Person Numbers

When the Person Number Generation Method option is set to Manual, you must supply a person number in the
Worker object.
Loading Legacy Numbers

You can load legacy numbers to environments where person numbers are generated automatically. Set the Initial
Person Number enterprise option to the highest legacy person number plus one so that the legacy sequence continues.
Correcting Person Numbers

You can correct a person number, provided that Person Number Generation Method is set to Manual.
To correct a person number when the enterprise method is automatic generation, you can:
1. Note which of the two automatic methods, Automatic Prior to Submission and Automatic Upon Final Save,
is being used.
2. Change the number-generation method temporarily to Manual.
Note: You're recommended not to hire workers while the correction is being made.
3. Correct the person number.

4. Reinstate the original automatic number-generation method. Consider also whether the value of the Initial
Person Number option must be updated to avoid conict with the correction you made.
5. Run the Update Person Search Keywords process to ensure that person searches with person number as a
keyword value are successful.
When you correct a person number, the correction applies to every date-eective update for the lifetime of the person
record. This rule ensures that a person isn't identied using dierent person numbers at dierent times.
106
To identify the person record to correct, supply the source key, Oracle Fusion GUID, or Oracle Fusion surrogate ID. You
can't supply the user key alone, as the person number is the user key.
Guidelines for Loading External Identiers

The External Identier component of the Worker object holds an identier used by a third-party application, such as a
time device or payroll application. This topic describes how to set some aributes of the External Identier component.
External Identiers at Person or Assignment Level

The external identier can be captured:
• At the person level, by supplying only the person number
• At the assignment level, by supplying both the person number and the assignment number
External Identier Types

The external identier type is dened in lookup type ORA_PER_EXT_IDENTIFIER_TYPES. You can add lookup codes to
this lookup type.
Date Values
The DateFrom and DateTo aributes include a time stamp. The time stamp ensures that you can assign an external
identier of a single type to a worker more than once on any day. For example, a person may be assigned a time-device
badge identier that he or she loses the same day. If you replace the badge identier on the same day, then the time
stamps dierentiate the external identiers.
External Identier Sequence

The ExternalIdentierSequence aribute is a required component of the user key and must be unique. You're
recommended to set this aribute to 1 for the rst record for a worker. Increment it by 1 for subsequent records.
External Identier Example

This example Worker.dat le loads an external identier for a person.
METADATA|ExternalIdentifier|ExternalIdentifierNumber|PersonNumber|ExternalIdentifierType|
ExternalIdentifierSequence
MERGE|ExternalIdentifier|rtyui45678|TestPer0TALTEST_9|Third-Party Payroll ID|1
Guidelines for Loading Person Names

The Person Name component of the Worker object holds both common and legislation-specic components of a
person's name. This topic describes some decisions you must make when loading person names using HCM Data
Loader.
107
Local and Global Names

Person names are always created with both a global and a local version. The name is created based on the name
type that you supply, and the other name is derived automatically. For example, if you set the NameType aribute to
GLOBAL, then the local name is derived. Alternatively, if you set NameType to FR, for example, then the global name
is derived. Typically, only the global name is required and the application copies it to the local name automatically.
However, if the person's name must be held in two dierent character sets, then supply the local name.
A core name eld may not be available for a legislation. For example, Last Name Kanji isn't available for the Japanese
legislation. In this case, the data is stored in one of the NameInformation1 through NameInformation14 aributes.
NameInformation1 through NameInformation14 are reserved for this purpose. The person name styles table stores
the mapping of the name style to the name aributes. The name style is the same for both the global and local-name
records.
Name Aributes for Specic Legislations

To supply a name aribute for a specic legislation, use one of the NameInformation15 through NameInformation30
aributes. For example, to dene the name aribute Doing Business As for the United States, you could use the
NameInformation15 aribute. You don't have to dene exelds for this requirement.
Supplying Date-Eective History

If you're loading date-eective history for a person name, then you must use source keys to identify the component.
Otherwise, you can use the PersonNumber, EectiveStartDate, and NameType user-key components.
Related Topics
• Oracle Fusion HCM: Person Name Validation (2146270.1)
Guidelines for Loading Person Images

The person image appears on various Oracle HCM Cloud application pages to identify a person's record. This topic
describes aspects of loading the Person Image component of the Worker object using HCM Data Loader.
Image Type
You can set the ImageType aribute only to PROFILE. If you omit the ImageType aribute, then the type is PROFILE
by default.
Image Size
The recommended size of the image is 90 pixels by 120 pixels. Images of dierent sizes are supported, but you're
recommended to maintain an aspect ratio of 3 by 4 to reduce any distortion. No recommendation exists for the image
resolution. The maximum size of the image le is 2 GB. However, you're recommended to store images at the smallest
possible size, taking into account the suggested dimensions. The smaller the image, the beer the performance of the
image display in the application. Typically, the le size of an image of the recommended dimensions would be only 2 or
3 MB, even at high resolution.
108
Examples of Loading Work Relationship Changes

The Worker object provides several indicator aributes that simplify maintenance of work relationships. Use these
indicators to request actions such as termination or a change of primary assignment. This topic provides examples of
work-relationship changes that you request using these indicators.
Note: These indicators aren't supported when you're supplying full date-eective history. They're provided
solely for independent actions. Also, you can't provide multiple indicators on the same work relationship
record. For example, you can't both terminate a work relationship (TerminateWorkRelationshipFlag) and
perform a global transfer (GlobalTransferFlag) on the same work relationship at the same time.
Changing the Hire Date

The hire date is the start date of a work relationship. To change the hire date, provide the new date on the
NewStartDate aribute of the Work Relationship component. You can load just the work relationship record. The
employment terms and assignment records are maintained automatically.
This example changes the hire date for an existing worker.

METADATA|WorkRelationship|SourceSystemOwner|SourceSystemId|PersonId(SourceSystemId)|LegalEmployerName|
NewStartDate
MERGE|WorkRelationship|VISION|1009_POS|1009|Cox-6-CWB|2002/02/10
Terminating a Work Relationship

To terminate a work relationship, load the Work Relationship component with the TerminateWorkRelationshipFlag
aribute set to Y. Specify the termination date on the ActualTerminationDate aribute. All associated assignments are
automatically made inactive after the termination date.
This example terminates a work relationship.

TerminateWorkRelationshipFlag|ActualTerminationDate|ActionCode|ReasonCode
MERGE|WorkRelationship|VISION|1009_POS|1009|Cox-6-CWB|Y|2015/10/02|RESIGNATION|RESIGN_PERSONAL
Correcting the Termination Date of a Work Relationship

To correct a work relationship termination date, supply a new ActualTerminationDate and set the
CorrectTerminationFlag aribute to Y.
This example corrects the termination date for a terminated work relationship.
CorrectTerminationFlag|ActualTerminationDate
109
MERGE|WorkRelationship|VISION|1009_POS|1009|Cox-6-CWB|Y|2015/10/08
Reversing a Termination
To reverse a termination, load the Work Relationship component with the ReverseTerminationFlag aribute set to Y.
This example reverses the termination of a work relationship.

ReverseTerminationFlag
MERGE|WorkRelationship|VISION|1009_POS|1009|Cox-6-CWB|Y
Canceling a Work Relationship

To cancel a work relationship, use a DELETE instruction for the work relationship and set the
CancelWorkRelationshipFlag aribute to Y.
This example deletes the specied work relationship and all its child records.
METADATA|WorkRelationship|SourceSystemOwner|SourceSystemId|PersonId(SourceSystemId)|CancelWorkRelationshipFlag
DELETE|WorkRelationship|VISION|1008_POS|1008|Y
Changing the Primary Assignment or Work Relationship

When you load a primary work relationship, the existing primary work relationship automatically becomes nonprimary
on the date that you supply on the DateForPrimaryFlagChange aribute.
To make a nonprimary work relationship primary, you load the work relationship to be made primary with
the PrimaryFlag aribute set to Y. Specify the date when the work relationship becomes primary on the
DateForPrimaryFlagChange aribute. The corresponding changes to employment terms and assignments occur
automatically. The primary indicator for the existing primary work relationship is set to N automatically.
How You Perform a Global Transfer

This topic explains how to perform global transfers for both primary and nonprimary work relationships using HCM
Data Loader. A global transfer is a permanent transfer from one legal employer to another. It results in the termination
of an existing work relationship and the creation of a new one. The termination date of the existing work relationship is
one day prior to the start date of the new work relationship.
110
Performing a Global Transfer on a Primary Work Relationship

By default, the global transfer is applied to the primary work relationship. To perform a global transfer, you simply load
the new Work Relationship component with all its child components. The new work relationship must have:
• A GlobalTransferFlag aribute set to Y

• An action code from the EMPL_GLB_TRANSFER action type
• A start date value that's the date of the global transfer
Don't include the work relationship that you're terminating. That work relationship is terminated automatically.
The termination and creation of the work relationships are validated to ensure data consistency. In particular, a
worker can't be left with only an active, nonprimary work relationship. Therefore, if the worker has two active work
relationships, you can't perform the global transfer on the primary one. You must make the primary work relationship
nonprimary before you aempt the global transfer.
Performing a Global Transfer on a Nonprimary Work Relationship

A worker can have multiple nonprimary work relationships. Therefore, when you perform a global transfer of a
nonprimary work relationship, you must supply additional information so that the correct work relationship is
terminated. To perform the global transfer on a nonprimary work relationship, you must also supply:
• The parent Worker component.

• The nonprimary work relationship that you're terminating. However, don't include:
◦ Any child records for the terminated work relationship

◦ The GlobalTransferFlag aribute
These records are in addition to those that you supply for a global transfer of a primary work relationship.
Updating Person-Name Legislation Codes

When you perform a global transfer, the new work relationship may have a legislation code that's new for the person.
In this case, you may want to update the legislation code for the person name. The person-name legislation code is
validated against all available work-relationship legislation codes. Therefore, the change to the work relationship must
occur before the change to the person name. You can update the legislation code in the person name in one of these
ways:
• Include the Worker object with no change in the same .dat le as the changes to the Person Name and Work
Relationship components. In this case, changes to the work relationship are processed before changes to the
person name.
• Process updates to the work relationship before those to the person name.
Guidelines for Loading Additional Assignments

Whether you can load additional assignments for a worker depends on the employment model. This topic identies, for
each employment model, whether you can perform the Add Assignment action using HCM Data Loader.
111
Employment Model Add Assignment
2 Tier - Single Assignment No

2 Tier - Multiple Assignment Yes

2 Tier - Single Contract - Single No

Assignment

2 Tier - Multiple Contract - Single Yes

Assignment

3 Tier - Single Employment Terms - No

Single Assignment

3 Tier - Single Employment Terms - Yes

Multiple Assignment

3 Tier - Multiple Employment Terms - No

Single Assignment

3 Tier - Multiple Employment Terms - Yes

Multiple Assignment

The following example shows how to load an additional assignment. Both the Employment Terms and Assignment
components are identied by user keys.
METADATA|WorkTerms|ActionCode|AssignmentNumber|AssignmentStatusTypeCode|AssignmentType|BusinessUnitShortCode|
DateStart|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|EffectiveStartDate|LegalEmployerName|
PersonNumber|PrimaryWorkTermsFlag|WorkerType
MERGE|WorkTerms|ADD_ASSIGN|ETTESTASSG03_562|ACTIVE_NO_PROCESS|ET|ZHRX-AE-Starter-BU|2016/01/01|4712/12/31|Y|2|
2017/08/01|CRFL RRF LE 2T|TESTASSG03_56|Y|E
METADATA|Assignment|ActionCode|AssignmentNumber|AssignmentStatusTypeCode|AssignmentType|BusinessUnitShortCode|
EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|EffectiveStartDate|Frequency|LegalEmployerName|
PersonNumber|PrimaryAssignmentFlag|WorkTermsNumber|WorkerType
MERGE|Assignment|ADD_ASSIGN|ETESTASSG03_562|ACTIVE_NO_PROCESS|E|ZHRX-AE-Starter-BU|4712/12/31|Y|2|2017/08/01|
W|CRFL RRF LE 2T|TESTASSG03_56|Y|ETTESTASSG03_562|E
Guidelines for Loading Temporary Assignments

This topic describes restrictions that apply to the loading of temporary assignments using HCM Data Loader.
When you create a temporary assignment in the UI, two data rows are created:
1. One row is created for the temporary assignment.

2. One row is added to the base assignment, which is suspended.
Both rows have the action code TEMP_ASG and the same action occurrence ID, which is dened by the application.
112
When you end the temporary assignment, two further data rows are created:
1. One row is created to end the temporary assignment.
2. One row is added to the base assignment, which becomes active on the day following the end date of the
temporary assignment.
Both rows have the action code END_TEMP_ASG and the same action occurrence ID.
Although you can create temporary assignments using HCM Data Loader, you can't end them using HCM Data Loader.
This restriction exists because no row is added to the base assignment when you load the temporary assignment.
Therefore, no matching row is found in the base assignment when you aempt to end the temporary assignment.
The following example shows how to load a temporary assignment. Both the Employment Terms and Assignment
components are identied by user keys.
METADATA|WorkTerms|ActionCode|AssignmentNumber|AssignmentStatusTypeCode|AssignmentType|BusinessUnitShortCode|
DateStart|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|EffectiveStartDate|LegalEmployerName|
PersonNumber|PrimaryWorkTermsFlag|WorkerType
MERGE|WorkTerms|TEMP_ASG|ETTESTASSG03_59|SUSPEND_PROCESS|ET|ZHRX-AE-Starter-BU|2016/01/01|4712/12/31|Y|1|
2017/08/01|CRFL RRF LE 2T|TESTASSG03_59|Y|E
MERGE|WorkTerms|TEMP_ASG|ETTESTASSG03_59-2|ACTIVE_PROCESS|ET|ZHRX-AE-Starter-BU|2016/01/01|4712/12/31|Y|1|
2017/08/01|CRFL RRF LE 2T|TESTASSG03_59|N|E
METADATA|Assignment|ActionCode|AssignmentNumber|AssignmentStatusTypeCode|AssignmentType|BusinessUnitShortCode|
EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|EffectiveStartDate|Frequency|LegalEmployerName|
PersonNumber|PrimaryAssignmentFlag|WorkTermsNumber|WorkerType
MERGE|Assignment|TEMP_ASG|ETESTASSG03_59|SUSPEND_PROCESS|E|ZHRX-AE-Starter-BU|4712/12/31|Y|1|2017/08/01|W|CRFL
RRF LE 2T|TESTASSG03_59|Y|ETTESTASSG03_59|E
MERGE|Assignment|TEMP_ASG|ETESTASSG03_59-2|ACTIVE_PROCESS|E|ZHRX-AE-Starter-BU|4712/12/31|Y|1|2017/08/01|W|
CRFL RRF LE 2T|TESTASSG03_59|N||ETTESTASSG03_59-2|E
Start Dates for Person Legislative Data

This topic explains how to specify start dates for person legislative data that you load using HCM Data Loader.
Person legislative data must start on the person's earliest eective start date. A person may have multiple work
relationships in dierent legislations. In this case, all person legislative data must start on the person's earliest
eective start date, not the start date of the work relationship. When a person starts a work relationship that's in a new
legislation, the application:
• Creates a person legislative data record as of the person's earliest eective start date with no data.
• Performs an update of the person legislative data record as of the date of the creation of the new work
relationship with the user-provided data. This approach ensures that the data is chronologically correct.
For example, consider the work relationships of the worker in this table.
Date Action
2000 Hired by Vision Corporation in the UK

2005 Left Vision Corporation in the UK

2006 Joined US military

113
Date Action
2009 Left US military and became a US veteran

2010 Hired by Vision Corporation in the US

In this example, in 2010 a US person legislative record is created as of 2000, the person's earliest eective start date.
The US legislative record is updated as of 2010, the start date of the person's US work relationship. The update includes
the descriptive exeld details for US veteran status, as provided by the user.
Employment Terms Override at Assignment

This topic describes how to set aribute values on employment terms and their associated assignments when you load
them using HCM Data Loader.
The enterprise option Allow Employment Terms Override at Assignment controls whether assignment aributes
inherited from employment terms can be overridden on the assignment. However, when you load employment terms,
the associated assignments don't inherit aribute values from the employment terms. This table summarizes how to
set aribute values on employment terms to avoid conicting with the current seing of Allow Employment Terms
Override at Assignment.
Allow Employment Terms Override Aribute Values on Employment Terms

at Assignment
No Must match values on associated assignments

Yes Can dier from values on associated assignments

Automatic Calculation of FTE Values for Workers

The full-time equivalent (FTE) value is the result of dividing assignment working hours by standard working hours,
which are typically those of a full-time worker. For example, if the assignment working hours are 10 and the standard
working hours are 40, then the FTE value is 0.25. When you edit assignment working hours in the user interface, FTE is
calculated automatically. When you load assignment records using HCM Data Loader, you can specify FTE values on the
Assignment Work Measure component. Alternatively, you can request that FTE values be calculated automatically. This
topic describes how to request automatic calculation of FTE values.
Calculating FTE Values Automatically

To request automatic calculation of FTE values for all assignments in a Worker.dat le, include the following SET
instruction in the le:
114
SET CALCULATE_FTE Y
When you include this instruction, the following rules apply:
• You must not include an Assignment Work Measure component for the assignment in the Worker.dat le.
• No more than one assignment work measure record can exist for the assignment in Oracle HCM Cloud.
• Both assignment working hours and standard working hours must exist for the assignment throughout the
relevant time period. Otherwise, no calculation of FTE values occurs for the assignment.
You may nd automatic calculation of FTE values helpful if:
• You're loading many assignment records that include assignment working hours.
• You aren't loading FTE values in the Assignment Work Measure component.
By including the SET CALCULATE_FTE Y instruction in the .dat le, you can generate FTE values for all of the assignments.
Tip: You can perform a data load with the sole purpose of calculating FTE values. Simply include the user
keys of the assignments in a Worker.dat le that includes the SET CALCULATE_FTE Y instruction.
The SET CALCULATE_FTE Y instruction generates FTE values only. It doesn't generate headcount values.
Related Topics
• File Line Instructions and File Discriminators
Create a Default Working-Hour Paern

A working-hour paern denes the working hours, start time, and end time for each day of the week. When you load
assignment records using HCM Data Loader, you can request that a default working-hour paern record be created
automatically.
Creating a Default Working-Hour Paern

To create a default working-hour paern for all assignments in a Worker.dat le, include this instruction in the
Worker.dat le:
SET CREATE_DEFAULT_WORKING_HOUR_PATTERN Y
You may nd automatic creation of default working-hour paerns helpful if you're loading many assignment records
but aren't loading the Working Hour Paern component of the Worker object. Once this default record exists, you can
update it with information for each worker by loading the Working Hour Paern component of the Worker object.
Related Topics
• File Line Instructions and File Discriminators
115
Examples of Loading Worker Working Hour Paern

You can dene shift types and working hours for your workers by loading working hour paerns with HCM Data Loader.
If the daily working hours are a xed number of hours per day, use Elapsed as the Work Shift Type to load. If you need
to track the start and end times per day, use Time as the Work Shift Type to load. Let's look at some Worker.dat les
that create worker hour paerns.
Load Working Hour Paern by Shift Type

To get started with working hour paerns, see the topic Create a Default Working-Hour Paern. Then, you can use the
following examples to load worker hours with the work shift type of your choice.
Let's say you want to dene the specic times of day in a worker's daily shift. To do this, load the Working Hour Paern
using Time as the Work Shift Type.
METADATA|WorkTerms|ActionCode|AssignmentStatusTypeCode|AssignmentType|EffectiveEndDate|EffectiveLatestChange|
EffectiveSequence|EffectiveStartDate|AssignmentNumber|LegalEmployerName|PrimaryWorkTermsFlag|DateStart|
PersonNumber|WorkerType
MERGE|WorkTerms|HIRE|ACTIVE_PROCESS|ET|4712/12/31|Y|1|2019/03/29|E51323|V1_LE0227|Y|2019/03/13|51323|E
METADATA|Assignment|ActionCode|AssignmentStatusTypeCode|AssignmentType|EffectiveEndDate|EffectiveLatestChange|
EffectiveSequence|EffectiveStartDate|WorkTermsNumber|AssignmentNumber|PrimaryFlag|PrimaryAssignmentFlag|
HourlySalariedCode|PersonNumber
MERGE|Assignment|HIRE|ACTIVE_PROCESS|E|4712/12/31|Y|1|2019/03/29|ET966169008889921|E51323|Y|Y|Salaried|51323
METADATA|WorkingHourPattern|Object|AssignmentNumber|EffectiveStartDate|WorkDayDefinitionCode|WorkingHoursType|
WorkShiftType|SatEndTime|SatStartTime|FriStartTime|FriEndTime|MonStartTime|MonEndTime|SunEndTime|SunStartTime|
ThuEndTime|ThuStartTime|TueEndTime|TueStartTime|WedStartTime|WedEndTime
MERGE|WorkingHourPattern|ASSIGNMENT|E51323|2019/03/29|TIME ENTRY STOP DAY|ORA_WORK_WEEK|ORA_TIME|18:00|10:00|
10:00|18:00|10:00|18:00|18:00|10:00|18:00|10:00|18:00|10:00|10:00|18:00
If you would rather record how many hours worked per shift, you can set Work Shift Type as Elapsed.
METADATA|WorkTerms|ActionCode|AssignmentStatusTypeCode|AssignmentType|EffectiveEndDate|EffectiveLatestChange|
EffectiveSequence|EffectiveStartDate|AssignmentNumber|LegalEmployerName|PrimaryWorkTermsFlag|DateStart|
PersonNumber|WorkerType
MERGE|WorkTerms|HIRE|ACTIVE_PROCESS|ET|4712/12/31|Y|1|2019/03/29|E51323|V1_LE0227|Y|2019/03/13|51323|E
METADATA|Assignment|ActionCode|AssignmentStatusTypeCode|AssignmentType|EffectiveEndDate|EffectiveLatestChange|
EffectiveSequence|EffectiveStartDate|WorkTermsNumber|AssignmentNumber|PrimaryFlag|PrimaryAssignmentFlag|
HourlySalariedCode|PersonNumber
MERGE|Assignment|HIRE|ACTIVE_PROCESS|E|4712/12/31|Y|1|2019/03/29|ET966169008889921|E51323|Y|Y|Salaried|51323
METADATA|WorkingHourPattern|Object|AssignmentNumber|EffectiveStartDate|WorkDayDefinitionCode|WorkingHoursType|
WorkShiftType|WedHours|TueHours|ThuHours|SunHours|MonHours|FriHours|SatHours
MERGE|WorkingHourPattern|ASSIGNMENT|E51323|2019/03/29|TIME ENTRY STOP DAY|ORA_WORK_WEEK|ORA_ELAPSED|8|8|8|8|8|
8|8
Examples of Loading Assignment Eligible Jobs

For any worker assignment, you can identify additional jobs for which the worker is eligible. You can use this feature for
workers who must report time for the additional jobs, for example. You can also use it simply to track the additional jobs
of workers who have multiple jobs. This topic provides examples showing how to create and update Assignment Eligible
Job components of the Worker object using HCM Data Loader.
116
Before you load Assignment Eligible Job components:
• The assignment job must exist in the target environment.

• The job family must exist in the target environment if the relief type is Derived.
Relief type can be either Manual or Derived.
◦ When the relief type is Derived, you can add jobs belonging to the job family of the worker's assignment
only. You can specify the ReliefType value using either the meaning Derived or the lookup code ORA_D.
◦ When the relief type is Manual, you can add any job. You must specify ManualRate and Frequency
values. You can specify the ReliefType value using either the meaning Manual or the lookup code
ORA_M.
Also, the start date of the eligible job must not be before the assignment start date.
You load assignment eligible jobs data in the Worker.dat le for processing by HCM Data Loader. You can verify this
data on the Manage Eligible Jobs page for a selected worker.
Creating Assignment Eligible Jobs

This example Worker.dat le creates an assignment eligible job for a worker using source keys. ReliefType is Manual.
METADATA|AssignmentEligibleJob|AssignmentId(SourceSystemId)|JobId(SourceSystemId)|ToDate|FromDate|
SourceSystemOwner|SourceSystemId|ReliefType|ManualRate|Frequency
MERGE|AssignmentEligibleJob|1031101972|100000011571171|2000/04/01|2000/01/01|VISION|TEST_RC_ut0001|ORA_M|11.7|
Hourly
This example Worker.dat le creates an assignment eligible job for a worker using source keys. ReliefType is Derived.
METADATA|AssignmentEligibleJob|AssignmentId(SourceSystemId)|JobId(SourceSystemId)|ToDate|FromDate|
SourceSystemOwner|SourceSystemId|ReliefType
MERGE|AssignmentEligibleJob|1031101860|100000011571171|2000/04/01|2000/01/01|VISION|TEST_RC_ut0002|ORA_D
This example Worker.dat le creates assignment eligible jobs for a worker using user keys. ReliefType is Manual.
The user key aributes for this component are AssignmentNumber, JobCode, BusinessUnitShortCode, and
EectiveStartDate.
METADATA|AssignmentEligibleJob|AssignmentNumber|JobCode|ToDate|FromDate|BusinessUnitShortCode|ReliefType|
ManualRate|Frequency
MERGE|AssignmentEligibleJob|TEST_ASG_ut0001|JOBOPMANCORE|2000/04/01|2000/01/01|Vision Corporation Enterprise|
Manual|11.7|Hourly
Updating Assignment Eligible Jobs

You can update only the value of the ToDate aribute of an assignment eligible job. This example Worker.dat le
updates a worker's assignment eligible job using source keys.
METADATA|AssignmentEligibleJob|AssignmentId(SourceSystemId)|JobCode|ToDate|FromDate|BusinessUnitShortCode|
SourceSystemOwner|SourceSystemId|ReliefType|ManualRate|Frequency
MERGE|AssignmentEligibleJob|1031101972|JOBOPMANCORE|2001/04/01|2000/01/01|Vision Corporation Enterprise|
VISION|TEST_RC_ut0001|Manual|11.7|Hourly
This example Worker.dat le updates a worker's assignment eligible job using user keys.
117
METADATA|AssignmentEligibleJob|AssignmentNumber|JobCode|ToDate|FromDate|BusinessUnitShortCode|ReliefType|
ManualRate|Frequency
MERGE|AssignmentEligibleJob|TEST_ASG_ut0001|JOBOPMANCORE|2001/04/01|2000/01/01|Vision Corporation Enterprise|
Manual|11.7|Hourly
Guidelines for Loading Seniority Dates

A seniority date is the date on which the calculation of a worker's length of service with the enterprise is based. A
worker's status, rank, or entitlement to benets may depend on his or her seniority. The seniority date can be based
on the worker's time in a particular entity, such as a legal employer or job. Therefore, you can congure seniority rules
based on values including collective agreement, country, department, enterprise, grade, job, legal employer, location,
position, and union. This topic describes some factors that aect how you load seniority dates using HCM Data Loader.
Versions of the Seniority Dates Functionality

Three versions of the seniority dates functionality, referred to as V1, V2, and V3, exist. The following table identies:
• The user interface task that you use to manage each version
• Whether you can update the seniority dates for each version using HCM Data Loader
Version User Interface Task Update Using HCM Data Worker Component
Loader
V1 Manage Work Relationship Yes Work Relationship

Note: You can update
only the enterprise and
legal employer seniority
dates.

V2 Manage Seniority Dates, No Not applicable

without fast formula support

V3 Manage Seniority Dates, with Yes Seniority Date

fast formula support

Note: After you migrate to V3 seniority dates, you can't use either V1 or V2. Therefore, you can't load seniority
dates on the Work Relationship component. This topic applies to V3 seniority dates.
For more information, see Comparison Between Dierent Seniority Dates Versions (2414630.1) on My Oracle Support at
hps://support.oracle.com.
Running the Calculate Seniority Dates Process

You can update but not create V3 seniority records for workers using HCM Data Loader. You must run the Calculate
Seniority Dates process to create default seniority records for workers, based on congured seniority date rules, before
118
you update them. After updating seniority records using HCM Data Loader, you can verify them for a worker on the
Manage Seniority Dates page.
Required Aributes
The following table identies aribute values that you must include in the Seniority Date component of the Worker
object to associate it with a seniority date rule. These requirements depend on the level at which the seniority date rule
is congured.
Level of Seniority Date Rule Required Aributes
Work relationship
One of:
• PeriodOfServiceId
• LegalEmployerName, DateStart, and WorkerType
Assignment
One of:
• AssignmentId
• AssignmentNumber
Person
One of:
• PersonId
• PersonNumber
Updating Seniority Dates Using Source Keys

As you can't create V3 seniority records using HCM Data Loader, they have default source keys where the source-
system owner is FUSION. Therefore, to update seniority dates using source keys, you must:
• Extract their default source keys using the HCM extract Integration Object User Key Extract.
• Update them using the Source Key object so that all source-key references for a single Seniority Date
component have the same source-system owner.
Related Topics
• Comparison Between Dierent Seniority Dates Versions
Examples of Loading Seniority Date Adjustments

A seniority date is the date on which the calculation of a worker's length of service with the enterprise is based. This
topic provides examples showing how to update V3 seniority dates using HCM Data Loader.
The following table identies aributes that you can use to identify the entity on which the seniority date is based. You
can use alternative key types, where available. For example, to identify a job you can use the user key (JobCode and
BusinessUnitShortCode) instead of the JobId value.
119
Entity Identifying Aribute
Bargaining unit BargainingUnitCode

Collective agreement CollectiveAgreementId

Department DepartmentId

Enterprise BusinessUnitShortCode

Grade GradeId

Grade step GradeStepId

Job JobId

Legal employer LegalEntityId

Legislation LegislationCode

Location LocationId

Position PositionId

Union membership UnionId

Updating Seniority Dates Using User Keys

The following example Worker.dat les update a worker's seniority date based on various assignment aributes.
They use user keys to reference the Seniority Date component. As these examples show, you must include the
ManualAdjustmentComments aribute when you make a manual adjustment to the seniority date. In these examples,
the seniority date rule is congured at the person level.
This example updates a worker's seniority date based on the assignment.

METADATA|SeniorityDate|SeniorityDateCode|PersonNumber|EntryDate|EffectiveStartDate|EffectiveEndDate|
BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|JobCode|AssignmentNumber
MERGE|SeniorityDate|JUN_A|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data
Correction|JOBCD7|E9990401
This example updates a worker's seniority date based on the department.

BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|DepartmentName
120
MERGE|SeniorityDate|JUN_DEPARTMENT|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|

Data Correction|Commercial Sales
This example updates a worker's seniority date based on the enterprise.

BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments
MERGE|SeniorityDate|JUN_ET|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data
Correction
This example updates a worker's seniority date based on the grade.

BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|GradeCode
MERGE|SeniorityDate|JUN_GRADE|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data
Correction|DHRX-AE-IC1
This example updates a worker's seniority date based on the job.

BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|JobCode
MERGE|SeniorityDate|JUN_JOB|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data
Correction|JOBCD7
This example updates a worker's seniority date based on the job but uses the seniority date rule name rather than its
code.
BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|JobCode
MERGE|SeniorityDate|SeniorityDateJUnit Person Job|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation
Enterprise|20|Data Correction|JOBCD7
This example updates a worker's seniority date based on the legal employer.
BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|LegalEmployerName
MERGE|SeniorityDate|JUN_LEMP|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data
Correction|Vision Corporation
This example updates a worker's seniority date based on the location.

BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|LocationCode
MERGE|SeniorityDate|JUN_LOCATION|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|
Data Correction|V1-_NEW_YORK_CITY_0_2450399170046
This example updates a worker's seniority date based on the position.

BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|PositionCode
MERGE|SeniorityDate|JUN_POSITION|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|
Data Correction|POSCD66
This example updates a worker's seniority date based on the work relationship.
BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|JobCode|WorkerType|LegalEmployerName|
DateStart
MERGE|SeniorityDate|JUN_WR|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data
Correction|JOBCD7|E|Vision Corporation|2001/05/05
121
Examples of Loading Seniority Hours

You calculate seniority in hours for hourly paid workers. So that the application can perform seniority calculations for
these workers, you load their seniority hours using HCM Data Loader. You can obtain the seniority hours from various
sources, such as Oracle Time and Labor, Oracle Global Payroll, or a third-party application. Any worker assignment for
which you load seniority hours must exist and be active as of the start date of the hours that you're loading. It must also
be paid hourly for the entire period for which you're loading data.
Tip: You can verify the loaded data for a worker on the Manage Seniority Dates page. To verify loaded data
for multiple workers, you can query the PER_SENIORITY_HOURS table.
This topic provides examples showing how to create, update, and delete the Seniority Hour component of the Worker
object using HCM Data Loader.
Creating Seniority Hours

This example Worker.dat le shows how to create the Seniority Hour component of the Worker object using source
keys.
METADATA|SeniorityHour|AssignmentId(SourceSystemId)|ToDate|FromDate|Hours|SourceSystemOwner|SourceSystemId
MERGE|SeniorityHour|1031101972|2001/01/01|2000/01/01|500|VISION|UT00214
This example Worker.dat le shows how to create the Seniority Hour component of the Worker object using user keys.
The user key aributes for this component are AssignmentNumber and FromDate.
METADATA|SeniorityHour|AssignmentNumber|ToDate|FromDate|Hours
MERGE|SeniorityHour|E00214|2001/01/01|2000/01/01|500
Updating Seniority Hours

This example Worker.dat le shows how to update the Seniority Hour component of the Worker object using source
keys.
METADATA|SeniorityHour|AssignmentId(SourceSystemId)|ToDate|FromDate|Hours|SourceSystemOwner|SourceSystemId
MERGE|SeniorityHour|1031101972|2001/01/01|2000/01/01|600|VISION|UT00214
This example Worker.dat le shows how to update the Seniority Hour component of the Worker object using user keys.
MERGE|SeniorityHour|E00214|2001/01/01|2000/01/01|600
Deleting Seniority Hours

This example Worker.dat le shows how to delete the Seniority Hour component of a Worker object using source keys.
METADATA|SeniorityHour|AssignmentId(SourceSystemId)|SourceSystemOwner|SourceSystemId
122
DELETE|SeniorityHour|1031101972|VISION|UT00214
This example Worker.dat le shows how to delete the Seniority Hour component of a Worker object using user keys.
DELETE|SeniorityHour|E00214|2001/01/01|2000/01/01|500
Example of Loading a Contract Extension

You supply the Contract component of the Worker object when creating workers, if appropriate. You can't load Contract
components later. However, you can load a contract extension for a worker who has a contract. This topic shows how to
load a contract extension using HCM Data Loader.
Loading a Contract Extension

You can use HCM Data Loader to give an existing worker a contract extension. Keep these rules in mind:
• You must load the relevant Employment Terms, Assignment, and Contract components in the same Worker.dat
le.
• The values of the EectiveStartDate and EectiveEndDate aributes must be the same on all three
components.
• The EectiveStartDate value is the start date of the extension period. This value must be the projected end
date of the last contract period, plus one day, meaning no gaps are permied between contract periods.
• The EectiveEndDate value must be the end of time if this contract record is the latest record. It must not be
the contract end date.
• You can specify the extension period by updating the ExtensionPeriod and ExtensionPeriodUnits aributes
of the Contract component.
In this case, the new projected end date is calculated automatically.

• The value of the ActionCode aribute on the Employment Terms and Assignment components must be
associated with the action type EMPL_CONTRACT_EXTN.
• You can't delete a contract extension record using HCM Data Loader.
The following example shows how to load the Employment Terms, Assignment, and Contract components for a
contract extension.
METADATA|WorkTerms|SourceSystemOwner|PersonId(SourceSystemId)|PeriodOfServiceId(SourceSystemId)|
SourceSystemId|AssignmentId|EffectiveStartDate|EffectiveEndDate|EffectiveSequence|EffectiveLatestChange|
ActionCode
MERGE|WorkTerms|FUSION|300100162474267|300100162474475|300100162474482|300100162474482|2011/01/31|4712/12/31|
1|Y|CONTRACT_EXTENSION
METADATA|Assignment|SourceSystemOwner|PersonId(SourceSystemId)|PeriodOfServiceId(SourceSystemId)|
WorkTermsAssignmentId(SourceSystemId)|SourceSystemId|AssignmentId|EffectiveStartDate|EffectiveEndDate|
EffectiveSequence|EffectiveLatestChange|ActionCode
MERGE|Assignment|FUSION|300100162474267|300100162474475|300100162474482|300100162474487|300100162474487|
2011/01/31|4712/12/31|1|Y|CONTRACT_EXTENSION
METADATA|Contract|SourceSystemOwner|PersonId(SourceSystemId)|PersonNumber|AssignmentId(SourceSystemId)|
SourceSystemId|ContractId|EffectiveStartDate|EffectiveEndDate|ExtensionPeriod|ExtensionPeriodUnits
MERGE|Contract|FUSION|300100162474267|960000000000615|300100162474482|300100162474490|300100162474490|
2011/01/31|4712/12/31|100|D
123
Example of Loading a Default Expense Account for a

Worker
For every worker who uses Oracle Expenses Cloud, a default expense account must be dened. The Default Expense
Account key exeld is available on the Assignment component of the Worker object. This topic shows how to load the
default expense account for a worker on the worker assignment.
Loading the Default Expense Account on the Assignment

If the expense account is congured with multiple segments, then provide the concatenated value. Separate the
segment values using the separator congured for the expense account, as shown in this example.
METADATA|Assignment|AssignmentNumber|EffectiveStartDate|EffectiveEndDate|EffectiveSequence|
EffectiveLatestChange|ActionCode|BusinessUnitId|DepartmentName|LocationCode|PrimaryAssignmentFlag|JobCode|
GradeCode|DefaultExpenseAccount|WorkTermsAssignmentId(SourceSystemId)|SourceSystemOwner|SourceSystemId
MERGE|Assignment|E10020592|2012/08/13|2015/04/30|1|Y|MIGRATED|300000001934525|5005 - ICT|GB|N|ICT Manager|M|
5101.0000.3030.0000.231200.0000.00000000.0000.0000|10020592_WORKTERMS|VISION|10020592_ASSIGNMENT
MERGE|Assignment|E10020592|2015/05/01|4712/12/31|1|Y|MIGRATED|300000001934525|5005 - ICT|GB|Y|ICT Manager|M|
5101.0000.3030.0000.231200.0000.00000000.0000.0000|10020592_WORKTERMS|VISION|10020592_ASSIGNMENT
FAQs for Loading Workers

How do I load person phones?
You must include any formaing characters in the value that you specify on the PhoneNumber aribute of the Person
Phone component. For example, to enter the US phone 650.555.0185 in the UI, you enter 650 in the Area Code eld
and 555-0185 in the Number eld. When loading this number using HCM Data Loader, you must specify the value
555-0185 on the PhoneNumber aribute.
Formaing requirements vary by legislation. Always include the formaing characters, such as hyphen or period,
specied for your legislation when loading person phones using HCM Data Loader.
If you include the LegislationCode aribute, then any CountryCodeNumber value that you supply must be valid for
the specied legislation code.
How do I load person national identiers?

You must include any formaing characters in the value that you specify on the NationalIdentierNumber aribute of
the Person National Identier component. For example, to load the US social security number 987-65-4322, you must
include the hyphens. Don't specify the number as 987654322. If you omit the formaing, which is country-specic, then
duplicate person records aren't found when the checking is based on national identier.
124
How do I specify probation values on an assignment?

You can supply either the ProbationPeriod and ProbationUnit values or the DateProbationEnd value.
• If you supply the ProbationPeriod and ProbationUnit, then the DateProbationEnd value is calculated
automatically.
• If you supply the DateProbationEnd, then the ProbationPeriod and ProbationUnit values are calculated
automatically.
• If you supply values for all three aributes, then an error is raised.
Until update 17D, if you supplied the DateProbationEnd, then the ProbationPeriod and ProbationUnit values
weren't calculated automatically. In addition, if you supplied all three aributes, then the DateProbationEnd value was
calculated automatically and the values you supplied were discarded. These errors are now xed.
How do I load a pending worker without providing a projected

start date?
You can't load a pending worker without providing a projected start date.
125
126
Integrating with HCM Loading Worker-Related Objects
10 Loading Worker-Related Objects
Example of Loading an Allocated Checklist

An allocated checklist is a specic instance of a checklist template that's assigned to one or more workers. The checklist
contains tasks that workers must perform. This topic shows how to load an allocated checklist using HCM Data Loader.
Creating an Allocated Checklist

This example AllocateChecklist.dat le creates two allocated checklists for the same person. Contacts and Contents
components are created for Checklist 1, and a Tasks component with a notication request is created for Checklist 2. All
components are referenced by user keys.
COMMENT Create two allocated checklists
METADATA|AllocateChecklist|ChecklistName|Country|ChecklistCategory|ChecklistInstance|PersonNumber|
AllowAutoAllocation
MERGE|AllocateChecklist|Checklist_1|US|ORA_ONB_ENT_ONBOARDING|1|8153818|N
MERGE|AllocateChecklist|Checklist_2|US|ONBOARD|1|8153818|N
COMMENT Create checklist contacts
METADATA|AllocateChecklistContacts|ContactTitleCode|ContactType|PersonNumber|Country|ChecklistName|
ChecklistCategory|ChecklistInstance
MERGE|AllocateChecklistContacts|ORA_ONB_ONBOARDING_SPONSOR|ORA_ONB_LN_MGR|8153818|US|Checklist_1|
ORA_ONB_ENT_ONBOARDING|1
COMMENT Create checklist contents
METADATA|AllocateChecklistContents|ContentType|ChecklistName|ChecklistCategory|ChecklistInstance|PersonNumber|
ContentDefnCode|Country
MERGE|AllocateChecklistContents|ORA_ONB_EVENT|Checklist_1|ORA_ONB_ENT_ONBOARDING|1|8153818|CHKLIST_CONT_DEF67|
US
COMMENT Create allocated checklist tasks
METADATA|AllocateChecklistTask|TaskName|ChecklistName|Country|ChecklistCategory|ChecklistInstance|
PersonNumber|MandatoryFlag|TaskPerformerPersonNumber|TaskOwnerPersonNumber
MERGE|AllocateChecklistTask|TaskChecklist_2|Checklist_2|US|ONBOARD|1|8153818|Y|8153818|8153818
COMMENT Create allocated checklist task notifications
METADATA|AllocateChecklistTaskNotifications|NotifyOwner|NotifyPerformer|TaskEvent|ChecklistName|
ChecklistCategory|ChecklistInstance|Country|PersonNumber|TaskName
MERGE|AllocateChecklistTaskNotifications|Y|Y|ORA_CHK_TASK_ASSIGN|Checklist_2|ONBOARD|1|US|8153818|
TaskChecklist_2
These rules apply when you load allocated checklists using HCM Data Loader:
• Eligibility proles for checklists and tasks aren't evaluated.

• Workow notications aren't triggered for the checklist tasks.
• The allocation happens immediately, regardless of any allocation date specied in the .dat le.
Related Topics
• Guidelines for Loading Checklist Templates
127
Guidelines for Loading Areas of Responsibility

Areas of responsibility are responsibilities that a worker has as part of his or her job. Such responsibilities have a dened
scope, such as a country or department. For example, a worker may be:
• The Human Resources Representative for a group of organizations
• The Benets Representative for workers with a specied job
• The Union Representative for workers in Germany
Areas of responsibility are a recommended way of securing access to person records. This topic describes how to load
areas of responsibility for a person using HCM Data Loader. Use the AreasOfResponsibility.dat le.
Responsibility Type
Responsibility types must exist in the target environment before you can load areas of responsibility. These ve
responsibility types are available by default, but you can add your own to suit business needs:
• Benets Representative
• Human Resources Representative
• Payroll Representative
• Recruiting
• Union Representative
The responsibility type is validated against the lookup type PER_RESPONSIBILITY_TYPES.
Responsibility Name
The responsibility name must be unique for the combination of person and responsibility type.
Scope of Responsibility
Various aributes available under scope of responsibility, such as business unit, legal employer, department, and
location, must exist before you can load areas of responsibility. For example, a location must exist before you can
identify it as the scope of an area of responsibility.
Deleting Areas of Responsibility

You can delete areas of responsibility using HCM Data Loader. However, ensure that deleting an area of responsibility
doesn't have unintended consequences. For example, a worker's secured access to person records may be lost if you
delete the area of responsibility on which it's based.
Related Topics
• How You Assign Areas of Responsibility
• Guidelines for Securing Person Records
128
Guidelines for Loading Document Records

Document records store information about documents, such as visas, licenses, and medical certicates, for a person.
Document records can include electronic versions of the documents as aachments. This topic describes how to load
Document Record and Document Record Aachment components for a person using HCM Data Loader.
Document Type
Document records exist for a specic document type. You must ensure that the document type exists in the target
environment. The denition of the document type identies supported and required aributes.
Aachment Files
The Document Record Aachment component holds the electronic version of a document for a person. Use the
aribute URLorTextorFilename to supply the:
• URL, if the DataTypeCode is WEB_PAGE

• Text, if the DataTypeCode is TEXT
• File name, if the DataTypeCode is FILE
If you're uploading aachment les, then they must be in the same .zip le as the DocumentsOfRecord.dat le that
contains the related document records. All aachment les must be placed in a subdirectory named BlobFiles. This
subdirectory is named for the BLOB data-type format in which aachment les are held. You specify the name of the
aachment le on the File aribute of the Document Record Aachment component.
Loading Document Records

You supply document record data in a DocumentsOfRecord.dat le. This example DocumentsOfRecord.dat le creates
a passport document for a person and includes a PDF le of the passport as an aachment. It identies both the
document record and the aachment using source keys.
METADATA|DocumentsOfRecord|SourceSystemOwner|SourceSystemId|PersonId(SourceSystemId)|DocumentCode|
DocumentName|DateFrom|DateTo|IssuingAuthority|IssuedDate|IssuingCountry
MERGE|DocumentsOfRecord|VISION|56883|134003891|PASSPORT_2442|UK Passport|2012/04/03|2022/04/03|United Kingdom
Passport Control|2012/04/03|UK
METADATA|DocumentAttachment|SourceSystemOwner|SourceSystemId|DocumentsOfRecordId(SourceSystemId)|DataTypeCode|
URLorTextorFileName|File
MERGE|DocumentAttachment|VISION|90982|56883|FILE|Passport_2442|JSmithPassport.pdf
Deleting Document Records

You can delete Document Record objects using HCM Data Loader. When you delete a document record, any associated
aachment record is deleted automatically. You can delete just the aachment, if appropriate.
This example DocumentsOfRecord.dat le deletes an existing document record. It identies the document record using
its source key.
METADATA|DocumentsOfRecord|SourceSystemOwner|SourceSystemId
DELETE|DocumentsOfRecord|VISION|56883
129
Related Topics
• How You Load Images, Aachments, and Large Strings
Example of Loading PeopleGroup for a Worker

If you want to assign workers to groups, like certain pension plans, you can use the People Group key exeld to do
that. Here's an example on how to load the People Group exeld.
Load a People Group Flexeld

Let's say you want to assign people to pension plans. First, you add the 'PeopleGroup' aribute to a METADATA
Assignment record in your Worker.dat le. Then add a MERGE Assignment record with the value for the people group
that you want. In this example, 'PeopleGroup' and its value appear at the end of the metadata and merge entries,
respectively.
METADATA|Worker|PersonId|EffectiveStartDate|EffectiveEndDate|PersonNumber|BloodType|CorrespondenceLanguage|
StartDate|DateOfBirth|DateOfDeath|CountryOfBirth|RegionOfBirth|TownOfBirth|ApplicantNumber|
WaiveDataProtectFlag|CategoryCode|SourceSystemOwner|SourceSystemId|GUID|ActionCode|ReasonCode|
SourceRefTableName=PER_ALL_PEOPLE_F|SourceRef001=PERSON_ID|SourceRef002=PERSON_NUMBER|
SourceRefName003=START_DATE
MERGE|Worker||2000/01/01|4712/12/31|Worker_DL_101|||2000/01/01|1970/01/01||||||Y||HRC_SQLLOADER|
SSIW_DL_101_1234_1||HIRE||||Worker_DL_101|2000/01/01
METADATA|PersonName|PersonNameId|EffectiveStartDate|EffectiveEndDate|PersonId|PersonNumber|LegislationCode|
NameType|FirstName|MiddleNames|LastName|Honors|KnownAs|PreNameAdjunct|MilitaryRank|PreviousLastName|
Suffix|Title|CharSetContext|SourceSystemOwner|SourceSystemId|GUID|NameInformation1|NameInformation2|
NameInformation3|NameInformation4|NameInformation5|NameInformation6|NameInformation7|NameInformation8|
NameInformation27|NameInformation28|NameInformation29|NameInformation30|SourceRefTableName=PER_PERSON_NAMES_F|
SourceRef001=PERSON_ID|SourceRef002=PERSON_NUMBER|SourceRef003=NAME_TYPE|SourceRef004=LAST_NAME
MERGE|PersonName||2000/01/01|4712/12/31||Worker_DL_101|US|GLOBAL|Worker_DL_101 FName|MN|Worker_DL_101 LName|
Doctor|Worker_DL_101||12|Prev LName|Suffix|Mr.|US|HRC_SQLLOADER|SSIW_DL_101_NAME_1234_1||Worker_DL_101|NI2|
NI3|NI4|NI5|NI6|NI7|NI8|NI9|NI10|NI11|NI12|NI13|NI14|NI15|NI16|NI17|NI18|NI19|NI20|NI21|NI22|NI23|NI24|NI25|
NI26|NI27|NI28|NI29|NI30|||Worker_DL_101|GLOBAL|Worker_DL_101 LName
METADATA|PersonLegislativeData|PersonLegislativeId|EffectiveStartDate|EffectiveEndDate|PersonId|PersonNumber|
LegislationCode|HighestEducationLevel|MaritalStatus|MaritalStatusDate|Sex|SourceSystemOwner|SourceSystemId|
GUID|SourceRefTableName=PER_PEOPLE_LEGISLATIVE_F|SourceRef001=PERSON_ID|SourceRef002=LEGISLATION_CODE
MERGE|PersonLegislativeData||2000/01/01|4712/12/31||Worker_DL_101|US||Married|2002/01/01|Male|HRC_SQLLOADER|
SSIW_DL_101_LEG_1234_1||||US
METADATA|WorkRelationship|LegalEmployerSeniorityDate|ActualTerminationDate|LegalEntityId|Comments|
EnterpriseSeniorityDate|LastWorkingDate|DateStart|NotifiedTerminationDate|OnMilitaryServiceFlag|
PeriodOfServiceId|PersonId|PrimaryFlag|ProjectedTerminationDate|RehireAuthorizerPersonId|RehireAuthorizor|
RehireReason|RevokeUserAccess|WorkerNumber|PersonNumber|LegalEmployerName|RehireRecommendationFlag|
WorkerType|GUID|SourceSystemId|SourceSystemOwner|NewStartDate|SourceRefTableName=PER_PERIODS_OF_SERVICE|
SourceRef001=LEGAL_ENTITY_ID|SourceRef002=LEGISLATION_CODE|SourceRef003=DATE_START
MERGE|WorkRelationship|||||||2000/01/01|||||Y||||||55857|Worker_DL_101|Vision Corporation||E||
SSIW_DL_101_WREL_1234_2|HRC_SQLLOADER||||US|2000/01/01
METADATA|WorkTerms|ActionCode|AssignmentId|AssignmentName|AssignmentNumber|AssignmentStatusTypeCode|
AssignmentStatusTypeId|AssignmentType|BargainingUnitCode|BillingTitle|BusinessUnitId|BusinessUnitShortCode|
ContractId|DateProbationEnd|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|EffectiveStartDate|
WorkerCategory|AssignmentCategory|EstablishmentId|ReportingEstablishment|ExpenseCheckSendToAddress|
GradeId|GradeCode|GradeLadderPgmId|GradeLadderPgmName|HourlySalariedCode|InternalBuilding|InternalFloor|
InternalLocation|InternalMailstop|InternalOfficeNumber|JobId|JobCode|LocationId|LocationCode|
ManagerFlag|NormalHours|Frequency|NoticePeriod|NoticePeriodUOM|OrganizationId|DepartmentName|
PeriodOfServiceId(SourceSystemId)|PersonId|PersonNumber|DateStart|WorkerType|LegalEmployerName|
130
PersonTypeId|PersonTypeCode|PositionCode|PositionOverrideFlag|PrimaryWorkTermsFlag|ProbationPeriod|
ProbationUnit|ProjectedEndDate|ProjectedStartDate|ProposedWorkerType|ReasonCode|RetirementAge|
RetirementDate|SpecialCeilingStepId|SpecialCeilingStep|StepEntryDate|SystemPersonType|TaxAddressId|
EndTime|StartTime|VendorSiteId|WorkAtHomeFlag|WorkTermsAssignmentId|VendorId|FreezeStartDate|
FreezeUntilDate|GUID|SourceSystemOwner|SourceSystemId|CategoryCode|TaxReportingUnitId|TaxReportingUnit|
SourceRefTableName=PER_ALL_ASSIGNMENTS_M|SourceRef001=ASSIGNMENT_NAME|SourceRef002=ASSIGNMENT_NUMBER|
SourceRef003=ASSIGNMENT_TYPE|DefaultExpenseAccount
MERGE|WorkTerms|HIRE||TestWT_Worker_DL_101|TestWTNum_Worker_DL_101|ACTIVE_PROCESS||ET|||202||||
4712/12/31|Y|1|2000/01/01|WC|FR|||||||||||||||||||||||||SSIW_DL_101_WREL_1234_2|||||Vision Corporation||
Employee|||Y|||||||||||||||||||||||HRC_SQLLOADER|SSIW_DL_101_WTERM_1234_1|||||TestWT_Worker_DL_101|
TestWTNum_Worker_DL_101|ET|01-300-1150-00
METADATA|Assignment|ActionCode|AssignmentId|EffectiveStartDate|EffectiveEndDate|EffectiveSequence|
EffectiveLatestChange|AssignmentType|AssignmentName|AssignmentNumber|AssignmentStatusTypeCode|
AssignmentStatusTypeId|BargainingUnitCode|BillingTitle|BusinessUnitId|BusinessUnitShortCode|DateProbationEnd|
WorkerCategory|AssignmentCategory|EstablishmentId|ReportingEstablishment|ExpenseCheckSendToAddress|
GradeId|GradeCode|GradeLadderPgmId|GradeLadderPgmName|HourlySalariedCode|InternalBuilding|InternalFloor|
InternalLocation|InternalMailstop|InternalOfficeNumber|JobId|JobCode|LabourUnionMemberFlag|
LocationCode|LocationId|ManagerFlag|NormalHours|Frequency|NoticePeriod|NoticePeriodUOM|OrganizationId|
PeriodOfServiceId(SourceSystemId)|PersonNumber|PersonId|DateStart|WorkerType|LegalEmployerName|
PersonTypeCode|PersonTypeId|PositionCode|PositionId|PositionOverrideFlag|PrimaryAssignmentFlag|
ProbationPeriod|ProbationUnit|ProjectTitle|ProjectedEndDate|ProjectedStartDate|ProposedWorkerType|ReasonCode|
RetirementAge|RetirementDate|SpecialCeilingStep|SpecialCeilingStepId|SystemPersonType|TaxAddressId|
EndTime|StartTime|VendorSiteId|WorkAtHomeFlag|WorkTermsNumber|WorkTermsAssignmentId(SourceSystemId)|
DepartmentName|VendorId|FreezeStartDate|FreezeUntilDate|GUID|SourceSystemId|SourceSystemOwner|CategoryCode|
SourceRefTableName=PER_ALL_ASSIGNMENTS_M|SourceRef001=ASSIGNMENT_NAME|SourceRef002=ASSIGNMENT_NUMBER|
SourceRef003=ASSIGNMENT_TYPE|DefaultExpenseAccount|PeopleGroup
MERGE|Assignment|HIRE||2000/01/01|4712/12/31|1|Y|E|TestWANM_Worker_DL_101|TestWANum_Worker_DL_101|
ACTIVE_PROCESS||||202|||WC|FR|||||||||||||||||||||||||SSIW_DL_101_WREL_1234_2|||2000/01/01||Vision
Corporation|Employee|||||Y||||||||||||||||||TestWTNum_Worker_DL_101|SSIW_DL_101_WTERM_1234_1||||||
SSIW_DL_101_WASGN_1234_1|HRC_SQLLOADER|||TestWANM_Worker_DL_101|TestWANum_Worker_DL_101|E|01-300-1150-00|A
Delete a People Group Flexeld

Let's say, for GDPR or other compliance purposes, you must remove values from a 'PeopleGroup' exeld segment and
disable it. First, enable the segment if it's currently disabled. Next, change the values for the segment in your HCM Data
Loader le to empty. Don't use spaces, and make sure the values are empty. Upload your HCM Data Loader le and
conrm that the segments appear empty. Finally, disable the segment, if applicable.
Guidelines for Loading Time Record Groups

A time record group includes related time entries, such as all reported time entries in a weekly time card. You can use
HCM Data Loader to load only approved time record groups, meaning historical data. You can't edit time record groups
after upload. This topic describes aspects of the Time Record Group object that you must understand to load time
record groups successfully using HCM Data Loader.
Preparing to Load Time Record Groups

Before you can load time record groups:
• Setup of Oracle Fusion Time and Labor must be complete.

• Relevant person records, each with a valid worker assignment, must exist in the target environment.
131
• A worker time processing prole must exist for each worker whose time card details you're loading. The time
processing prole may identify other consumers of the time card data.
◦ If Oracle Fusion Global Payroll is a consumer of time card data, then the relevant payroll element entries
must exist.
◦ If Oracle Fusion Project Costing is a consumer of time card data, then the relevant Project Costing setup
data must exist.
You may also need:

• Time rules, if the data being loaded required validation and calculation
• A worker time entry prole, if the worker or time and labor manager can view the loaded data in the application
Supplying Keys
The Time Record Group object doesn't support source keys. Therefore, supply user keys when creating time record
groups.
Querying Predened Time Aributes

Predened time aributes and their data types aren't visible on a user interface. To query time aribute names, use this
SQL query:
SELECT ATRB.NAME, ATRB.DISPLAY_NAME, ATRB.CLASS, ATRB.ATTRIBUTE_TYPE
FROM HWM_TM_ATRB_FLDS_VL ATRB
WHERE ATRB.ATTRIBUTE_CATEGORY NOT IN ('TIME_BUILDING_BLOCK', 'TIME_RECORD',
'TIME_RECORD_GROUP');
This table shows example results from this query.
Aribute Name Aribute Display Name Aribute Class Aribute Data Type
PJC_PROJECT_ID Project SIMPLE Number

PayrollTimeType Payroll Time Type MASTER Varchar

Updating Time Record Groups

When updating a time record group, you must supply the complete Time Record Group object in the
TimeRecordGroup.dat le, not just the changed records.
Deleting Time Record Groups

You can delete Time Record Group objects using HCM Data Loader only if you identify them using surrogate IDs. When
you delete a Time Record Group object, its child components are also deleted. You can't delete individual components
of the object. This example TimeRecordGroup.dat le deletes a time record group and its child components. It
references the record by its surrogate ID.
METADATA|TimeRecordGroup|TimeRecordGroupId|ResourceId|ResourceType|TcStartTime|TcStopTime|GroupType|
SubResourceId
132
DELETE|TimeRecordGroup|100000001|100000008153756|PERSON|2010/01/04 00:00:01|2010/01/09 23:59:59|RPTD_TIME|

100000008154060
To obtain the surrogate IDs of existing objects, use the HCM Data Loader extract Integration Object User Key Map
Extract.
Related Topics
• HCM Data Loader Extracts
Examples of Loading Time Record Groups

This topic shows how to create Time Record Group objects using HCM Data Loader.
Creating Time Record Groups

This example TimeRecordGroup.dat le creates two time record groups for the same assignment. It references the
person and assignment by their user keys.
METADATA|TimeRecordGroup|GroupType|ResourceType|PersonNumber|AssignmentNumber|TcStartTime|TcStopTime
MERGE|TimeRecordGroup|RPTD_TIME|PERSON|8153756|EEEE8153756|2010/02/01 00:00:01|2010/02/06 23:59:59
METADATA|TimeRecord|GroupType|ResourceType|PersonNumber|TcStartTime|TcStopTime|OrderEntered|StartTime|
StopTime|TmRecType|AssignmentNumber|Measure|UnitOfMeasure
MERGE|TimeRecord|RPTD_TIME|PERSON|8153756|2010/02/01 00:00:01|2010/02/06 23:59:59|1|2010/02/01 09:00:01|
2010/02/01 13:00:01|RANGE|EEEE8153756|4|HR
2010/02/02 13:00:01|RANGE|EEEE8153756|4|HR
2010/02/03 13:00:01|RANGE|EEEE8153756|4|HR
2010/02/04 13:00:01|RANGE|EEEE8153756|4|HR
2010/02/05 13:00:01|RANGE|EEEE8153756|4|HR
METADATA|TimeRecordGroupAttribute|GroupType|ResourceType|PersonNumber|TcStartTime|TcStopTime|AttributeName|
AttributeDataType|AttributeStringValue
MERGE|TimeRecordGroupAttribute|RPTD_TIME|PERSON|8153756|2010/02/01 00:00:01|2010/02/06 23:59:59|Comment|
String|Create Timecard for 2 week of year 2010
METADATA|TimeRepositoryAttribute|GroupType|ResourceType|PersonNumber|TcStartTime|TcStopTime|OrderEntered|
AttributeName|AttributeDataType|AttributeStringValue|AttributeBigDecimalValue
MERGE|TimeRepositoryAttribute|RPTD_TIME|PERSON|8153756|2010/02/01 00:00:01|2010/02/06 23:59:59|1|
PayrollTimeType|STRING|ZOTL_Regular|
MERGE|TimeRepositoryAttribute|RPTD_TIME|PERSON|8153756|2010/02/01 00:00:01|2010/02/06 23:59:59|1|LDG_ID|
BIG_DECIMAL||202
BIG_DECIMAL||202
BIG_DECIMAL||202
BIG_DECIMAL||202
133

BIG_DECIMAL||202
This example demonstrates that:
• The GroupType aribute value on all components must be RPTD_TIME.

• The ResourceType aribute value on all components must be PERSON.
• The TcStartTime and TcStopTime aribute values on all child components of the object must match those on
the parent Time Record Group object.
• You must supply the same value for the OrderEntered aribute on both the Time Repository Aribute
component and its parent Time Record component.
Guidelines for Loading User-Update Requests

You use the User object to create requests to update existing Oracle HCM Cloud user accounts. This topic describes
when to use each component of the User object. It also describes any restrictions on its use.
The User Component

You can use the User component to create requests to:
• Update a user name.

• Suspend or activate a user.
• Add a single role to or remove a single role from a user.
• Create a user account, in specic circumstances.
• Delete a user account.
You also use this component to update the CredentialsEmailSent value in the PER_USERS table. This value records
whether the account and password details have been sent to the user. Valid values are Y and N. After the email has
been sent, it can't be sent again unless you reset this value. For example, to reset user passwords, you can run the Send
User Name and Password Email Notications process. Before doing so, you can set CredentialsEmailSent to N to
ensure that users are notied of new passwords. Otherwise, they aren't notied.
The User Role Component

The User Role component is a child of the User object. You use the User Role component to add or remove multiple
roles for a user. To add or remove a single role, use the User component.
Creating User Accounts

Depending on the seing of the User Account Creation enterprise option, user accounts can be created automatically
for workers loaded in bulk. However, you may have prevented the user account from being created for an individual
worker. Alternatively, it may have failed to be created for some reason. In these cases, you can use the User object to
request a user account.
Note: Use the User object to request a user account only as an exception. The standard method is to request
the user account when you create the worker.
134
A user account can be created by means of the User object only if the User Account Creation enterprise option enables
automatic creation of user accounts.
Deleting User Accounts

On occasion, you may want to delete a user account. For example, you may have created the user name in the wrong
format. You can delete user accounts in both test and production environments, and the accounts can be in any status.
The User and Role Provisioning options have no eect on user-account deletion. For example, deletion requests can't
be suppressed.
Tip: The user is deleted from both the LDAP directory and the PER_USERS, PER_USER_ROLES, and
PER_USER_HISTORY records. Therefore, you can reuse the user name. You can recreate the user account on
the Security Console, using the Manage Users task, or by loading the User object.
Running Send Pending LDAP Requests

After loading user-update requests, you run the Send Pending LDAP Requests process to deliver them to your LDAP
directory server. The recommendation is to schedule this process to run daily. You don't have to run this process after
updating the CredentialsEmailSent indicator.
Related Topics
• Why You Run the Send Pending LDAP Requests Process
Examples of Loading User-Update Requests

Use the User object to manage existing users and their roles. This topic provides examples showing how to create some
typical user-update requests.
Updating a User
This example creates a request to update the user name for the user identied by the specied person number.
METADATA|User|PersonNumber|Username
MERGE|User|12312|[email protected]
This example creates a request to suspend an active user.

METADATA|User|PersonNumber|Suspended
MERGE|User|12312|Y
This example creates a request to activate a suspended user.

MERGE|User|12312|N
This example updates the CredentialsEmailSent indicator, which determines whether an email containing the user
credentials is sent to the user. If the CredentialsEmailSent indicator is Y, then no email is sent. If the indicator is N, then
an email is sent. In this example, the indicator is changed from Y to N.
METADATA|User|PersonNumber|CredentialsEmailSent
135
MERGE|User|12312|N
Updating User Roles

You use the User component to add a single role. Note that you supply role codes rather than role names. For example,
you specify ORA_PER_EMPLOYEE_ABSTRACT rather than Employee to add the employee role. If you supply an invalid
role code, then the request is created but any aempt to provision the role fails.
This example creates a request to add a single role to the user.

METADATA|User|PersonNumber|RoleCommonName|AddRemoveRole
MERGE|User|12312|ORA_PER_EMPLOYEE_ABSTRACT|ADD
This example creates a request to add multiple roles to the user. You use the User Role component to add multiple
roles.
METADATA|User|PersonNumber
MERGE|User|12312
METADATA|UserRole|PersonNumber|RoleCommonName|AddRemoveRole
MERGE|UserRole|12312|ORA_PER_EMPLOYEE_ABSTRACT|ADD
MERGE|UserRole|12312|ORA_PER_LINE_MANAGER_ABSTRACT|ADD
This example creates a request to remove a single role from the user. You use the User component to remove a single
role.
METADATA|User|PersonNumber|RoleCommonName|AddRemoveRole
MERGE|User|12312|ORA_PER_EMPLOYEE_ABSTRACT|REMOVE
This example creates a request to remove multiple roles from the user. You use the User Role component to remove
multiple roles.
MERGE|User|12312
MERGE|UserRole|12312|ORA_PER_EMPLOYEE_ABSTRACT|REMOVE
MERGE|UserRole|12312|ORA_PER_LINE_MANAGER_ABSTRACT|REMOVE
Creating a User Account

You can use the User object to create a user account in limited circumstances. For example:
• An aempt to request a user account when loading the Worker object has failed.
• The GeneratedUserAccountFlag aribute of the Person User Information component was set to N either by
mistake or intentionally for the loaded worker.
Creating a user account is a two-step process:

1. Create the user.
2. Activate the user and add roles.
This example creates a request to create a user account for the specied person number. You can also supply a user
name if required. If you supply no user name, then the user name is generated in the default format as specied on the
Security Console. Once the account exists, it's suspended immediately as it has no roles.
METADATA|User|PersonNumber|GenerateUserAccount
MERGE|User|12312|Y
136
This example activates the user account and adds roles so that the account remains active.
MERGE|User|12312|N
MERGE|UserRole|12312|ORA_PER_EMPLOYEE_ABSTRACT|ADD
MERGE|UserRole|12312|ORA_PER_LINE_MANAGER_ABSTRACT|ADD
Tip: User-update requests aren't processed until Send Pending LDAP Requests next runs. If the process isn't
scheduled, remember to run it.
Deleting a User Account

This example deletes the user account for the worker with the specied person number.
DELETE|User|12312
Guidelines for Loading Worker Schedules

A worker schedule denes a worker's shift paern for a specied period. To load worker schedules using HCM Data
Loader, use the Schedule Request object. This topic describes some aspects of worker schedules that you must
understand to load them successfully.
Preparing to Load Worker Schedules

Before you load worker schedules, you must dene shift codes and scheduler proles. You can also dene shift layouts,
if required. This table identies the relevant tasks. Perform these tasks in the Time Management work area.
Task Description
Manage Shift Properties Denes shift codes for all shifts

Manage Scheduler Proles Denes scheduler proles. Ensure that each of the workers whose shifts you load appears in a
scheduler prole.

Manage Layout Sets Denes a shift layout for loaded time aributes. This task is optional. If you don't dene the
shift layout, then you can still load time aributes but you can't see them in the application.

You can also set up and enable notications for schedulers and workers. This table identies the notications. Congure
these notications in the Alerts Composer work area.
Notication Description
HTS Worker Shifts Imported Sent to managers and schedulers when a new schedule is loaded
137
Notication Description

HTS Schedule Publication Sent to workers when a new schedule is published

Tip: You can also enable or disable worker notications by seing the WorkerNotication aribute of the
Schedule Event component when you load schedule requests.
How Worker Schedules Are Loaded

Unlike most other HCM Data Loader business objects, worker schedules aren't loaded from the HCM Data Loader stage
tables to the application tables. Instead, worker schedules are loaded from the HCM Data Loader stage tables to the
schedule stage tables. You must then run the Process Imported Shifts process to load worker schedules into either
the planned or the planned and published schedule tables. You run the Process Imported Shifts process using the
Manage Scheduled Processes task in the Time Management work area. This process:
• Merges all schedule events for a worker from HCM Data Loader and REST services
• Consolidates the schedule events for a worker from multiple schedule requests, orders them by request time,
and processes them in this order
This approach to loading Schedule Request objects maintains data integrity. However, you see only basic validation
errors from HCM Data Loader. Most validation is performed when Process Imported Shifts loads Schedule Request
objects into the schedule tables.
Import Modes
When loading Schedule Request objects, you must set the ImportMode aribute of the Schedule Event component to
either FULL or UPDATE. This table describes the import modes.
Import Mode Description
FULL
Use FULL mode when you create worker schedules. For example, use this mode to load worker
schedules during implementation. When the mode is FULL, you must set the ShiftAction
aribute of all Schedule Shift Event components in the Schedule Event to CREATE.
UPDATE
Use UPDATE mode to update or delete existing worker schedules. When the mode is UPDATE,
you can create additional shifts, update existing shifts, or delete existing shifts. You set the
ShiftAction aribute of the Schedule Shift Event component as appropriate.
Verifying Loaded Schedules

Time and labor managers and schedulers verify loaded schedules in the Time Management work area. They verify:
• Planned schedules on the Manage Planned Schedule page
• Published schedules using the View Published Schedule task
Workers view their published schedules using the calendar and Team Schedule pages of the Time work area.
138
Examples of Creating Worker Schedules

This topic provides examples showing how to create worker schedules using HCM Data Loader.
Creating a Schedule for a Worker for a Specic Week

For each worker whose schedule you're creating, you must load Schedule Request, Schedule Event, and Schedule Shift
Event components. On the Schedule Event component, you set the ImportMode aribute to FULL. On the Schedule
Shift Event components, you set the ShiftAction aribute to CREATE.
This example ScheduleRequest.dat le creates a schedule for a worker for a specied week. It uses user keys.
METADATA|ScheduleRequest|ScheduleRequestNumber|RequestSource|RequestTime
MERGE|ScheduleRequest|SR1234501|3RD_PARTY_ABC|2017-01-01T13:25:20.010+01:00
METADATA|ScheduleEvent|ScheduleRequestNumber|ScheduleEventNumber|ImportMode|PersonNumber|PeriodStartDate|
PeriodEndDate|AllowEdits|Publish|WorkerNotification
MERGE|ScheduleEvent|SR1234501|SE001|FULL|955160008182092|2017/01/01|2017/01/07|Y|Y|N
METADATA|ScheduleShiftEvent|ScheduleRequestNumber|ScheduleEventNumber|ScheduleShiftEventNumber|ShiftAction|
ReferenceDay|ShiftStartTime|ShiftEndTime|ShiftTimeNotWorked|ShiftCode|ShiftCategory|ShiftType|AllowEdits
MERGE|ScheduleShiftEvent|SR1234501|SE001|SSE101|CREATE|2017/01/01|2017-01-01T09:00:00+01:00|
2017-01-01T17:00:00+01:00|60|MORNTIME|WORK|TIME|N
METADATA|ScheduleShiftAttribute|ScheduleRequestNumber|ScheduleEventNumber|ScheduleShiftEventNumber|
ScheduleShiftAttributeNumber|AttributeName|AttributeValue
MERGE|ScheduleShiftAttribute|SR1234501|SE001|SSE101|SSA001|PayrollTimeType|WFM_PAY_REGULAR_US
MERGE|ScheduleShiftAttribute|SR1234501|SE001|SSE101|SSA002|GD_Department_CHAR|1000
Creating a Shift for a Worker for a Specic Day

To create a single shift for a worker, you load the Schedule Request, Schedule Event, and Schedule Shift Event
components. On the Schedule Event component, you set the ImportMode aribute to FULL. On the Schedule Shift
Event component, you set the ShiftAction aribute to CREATE.
This example ScheduleRequest.dat le creates a shift for a worker on a specic day. It uses user keys.
139
METADATA|ScheduleShiftEvent|ScheduleRequestNumber|ScheduleEventNumber|ScheduleShiftEventNumber|ShiftNumber|
ShiftAction|ReferenceDay|ShiftStartTime|ShiftEndTime|ShiftDuration|ShiftTimeNotWorked|ShiftCode|ShiftCategory|
ShiftType|AllowEdits
MERGE|ScheduleShiftEvent|SR1234502|SE001|SSE101|SN001|CREATE|2017/01/01|2017-01-01T06:00:00+01:00|
2017-01-01T09:00:00+01:00||60|MORNTIME|WORK|TIME|N
METADATA|ScheduleShiftAttribute|ScheduleRequestNumber|ScheduleEventNumber|ScheduleShiftEventNumber|
ScheduleShiftAttributeNumber|AttributeName|AttributeValue
Note: Shift numbers are optional when you create a schedule. Typically, they're generated by a third-party
scheduling system. You must specify a shift number when updating or deleting a shift.
Examples of Updating Worker Schedules

This topic provides examples showing how to update existing worker schedules using HCM Data Loader.
Updating a Shift
To update an existing shift, you load the Schedule Request, Schedule Event, and Schedule Shift Event components.
On the Schedule Event component, you set the ImportMode aribute to UPDATE. On the Schedule Shift Event
component, you specify the shift number and set the ShiftAction aribute to UPDATE.
This example ScheduleRequest.dat le updates an existing worker shift from a third-party application.
MERGE|ScheduleEvent|SR1234503|SE001|UPDATE|955160008272091|2017/01/01|2017/01/07|Y|Y|N
ShiftAction|ReferenceDay|ShiftStartTime|ShiftEndTime|ShiftTimeNotWorked|ShiftCode|ShiftCategory|ShiftType|
AllowEdits
MERGE|ScheduleShiftEvent|SR1234503|SE001|SSE101|SN001|UPDATE|2017/01/01|2017-01-01T07:00:00+01:00|
Deleting a Shift
To delete a shift, you load the Schedule Request, Schedule Event, and Schedule Shift Event components. On the
Schedule Event component, you set the ImportMode aribute to UPDATE. On the Schedule Shift Event component,
you specify the shift number and set the ShiftAction aribute to DELETE.
This example ScheduleRequest.dat le deletes an existing shift

MERGE|ScheduleEvent|SR1234504|SE001|UPDATE|955160008272091|2017/01/01|2017/01/07|Y|Y|N
140
ShiftAction|ReferenceDay|ShiftStartTime|ShiftEndTime|ShiftDuration|ShiftTimeNotWorked|ShiftCode|ShiftCategory|
ShiftType|AllowEdits
MERGE|ScheduleShiftEvent|SR1234504|SE001|SSE101|SN001|DELETE|2017/01/01|2017-01-01T07:00:00+01:00|
2017-01-01T11:00:00+01:00||60|MORNTIME|WORK|TIME|N
Clearing a Schedule
To clear a worker schedule, load the Schedule Request and Schedule Event components. On the Schedule Event
component, you set the ImportMode aribute to FULL. Because you aren't providing Schedule Shift Event
components, the Process Imported Shifts process deletes all shifts for the given period.
This example ScheduleRequest.dat le clears all existing shifts for a worker for a specied period.
FAQs for Loading Worker-Related Objects

Can I load allocated checklists using HCM Data Loader?
Yes. Both the checklist template and the worker to whom the checklist is allocated must exist in the target environment.
Can checklists be allocated automatically to workers created using

HCM Data Loader?
No. To allocate a checklist to a worker, you can:
• Load an Allocated Checklist object for the worker.
• Allocate the checklist to the worker in the user interface.
141
142
Integrating with HCM Loading Work Structures
11 Loading Work Structures
Overview of Loading Work Structures

The work structures that you can load using HCM Data Loader include grades, grade ladders, grade rates, jobs,
job families, locations, organizations, positions, and HCM position hierarchies. This topic describes some general
considerations that apply to most or all work structures.
Reviewing Component Hierarchies

Select a work structure on the View Business Objects page to review its component hierarchy.
Loading Set-Enabled Work Structures

These work structures are set enabled:
• Departments
• Grades
• Jobs
• Locations
You can create them in a specic reference data set, which restricts their use to an individual business unit. Alternatively,
you can create them in the common set, where they're generally available. You must ensure that referenced sets exist
and are associated with relevant business units, if appropriate.
Using Action Reasons

You can associate action reasons with these work structures:
• Grades
• Grade rates
• Grade ladders
• Jobs
• Locations
• Organizations
• Positions
If you plan to use action reasons, then you must create them before you load work structures. In the Setup and
Maintenance work area, use the following:
• Functional Area: Workforce Structures
143
• Task: Manage Action Reasons
Related Topics
Examples of Loading Collective Agreements

A collective agreement is a wrien agreement between an employer and a union or bargaining unit. It denes terms
and conditions of employment for the represented workers. The terms used to refer to collective agreements may vary
by country. Generally, the agreement is for a specied term. This topic describes aspects of the Collective Agreement
object that you must understand to load them successfully using HCM Data Loader.
Preparing to Load Collective Agreements

A collective agreement is country-specic. Therefore, LegislationCode is a required aribute of the Collective
Agreement object.
You can associate any combination of a union, a bargaining unit, and a legal employer with the collective agreement.
For example, you can associate a collective agreement with a union or with both a union and a legal employer. Any
union, bargaining unit, or legal employer associated with collective agreements must exist in the target environment
before you load those collective agreements.
Creating Collective Agreements

You supply collective agreements data in the CollectiveAgreements.dat le for processing by HCM Data Loader. This
example CollectiveAgreements.dat le creates a collective agreement using source keys. The collective agreement is
associated with a union, a bargaining unit, and a legal employer.
METADATA|CollectiveAgreements|SourceSystemOwner|SourceSystemId|CollectiveAgreementName|UnionName|
EffectiveStartDate|EffectiveEndDate|Status|IdentificationCode|LegalEmployerName|LegislationCode|Description|
BargainingUnitCode|EmployeeOrgName|EmployeeOrgContact|EmployerOrgName|EmployerOrgContact
MERGE|CollectiveAgreements|VISION|VISCAGR01|SEIU UHW Medical Social Workers (California, Northern)|Service
Employees International Union|2010/01/01|4712/12/31|A|SEIU_UHW_MSW_CA_N|Vision Corporation|US|Collective
Agreement covering the medical social workers in northern California affiliated to the Service Employees
International Union.|BU_SEIU_UHW_MSW_CA_N|Vision Corporation|John Gorman|Vision Corporation|Jane Reifer
This example CollectiveAgreements.dat le creates a collective agreement using user keys. The collective agreement is
associated with a union, a bargaining unit, and a legal employer.
METADATA|CollectiveAgreements|CollectiveAgreementName|UnionName|EffectiveStartDate|EffectiveEndDate|
Status|IdentificationCode|LegalEmployerName|LegislationCode|Description|BargainingUnitCode|EmployeeOrgName|
EmployeeOrgContact|EmployerOrgName|EmployerOrgContact
MERGE|CollectiveAgreements|SEIU UHW Medical Social Workers (California, Northern)|Service Employees
International Union|2010/01/01|4712/12/31|A|SEIU_UHW_MSW_CA_N|Vision Corporation|US|Collective Agreement
covering the medical social workers in northern California affiliated to the Service Employees International
Union.|BU_SEIU_UHW_MSW_CA_N|Vision Corporation|John Gorman|Vision Corporation|Jane Reifer
You can't load aachments for collective agreements using HCM Data Loader.
144
Updating Collective Agreements

You can't change either the rst eective start date or last eective end date for an existing collective agreement record.
Therefore, create your collective agreement records with an eective start date on or before the start date of any record
that references them.
If the collective agreement is linked to an assignment, then you can't edit the IdenticationCode, LegislationCode,
BargainingUnitCode, LegalEmployerName, or LegalEntityId aributes.
Loading Translated Collective Agreement Names

This example CollectiveAgreementsTranslation.dat le translates the name of an existing collective agreement. It
identies the existing record using source keys.
METADATA|CollectiveAgreementsTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|
Language|CollectiveAgreementName|Description
MERGE|CollectiveAgreementsTranslation|VISION|VISCAGR01|2001/01/01|4712/12/31|FR|SEIU UHW Travailleurs sociaux
medicaux (Californie, Nord)|Convention collective couvrant les travailleurs sociaux medicaux dans le nord de
la Californie affiliee a l'Union internationale des employes du service.
Related Topics
• How You Manage Collective Agreements
Guidelines for Loading Grades

A grade identies a worker's rank or level of compensation. You can create grades either with or without grade steps.
This topic describes aspects of the Grade object that you must understand to load grades successfully.
Grade Steps
If you're using grade steps, then load one Grade Step component for each grade step.
Changing Logical Start Dates for Grades

You can change the rst eective start date for an existing grade. However, the new eective start date must be before
the existing eective start date. Create Grade objects with eective start dates on or before the start dates of other
objects that refer to your grades.
Loading Translated Grade and Grade-Step Names

Supply grade and grade-step names in the language of the user who's loading them. You supply a
GradeTranslation.dat le to translate grade names into other enabled languages once the grades exist. You supply a
GradeStepTranslation.dat le to translate grade-step names.
This example GradeTranslation.dat le translates the names of existing grades. It identies the grades by their source
keys.
METADATA|GradeTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|GradeName
MERGE|GradeTranslation|VISION|ADMIN|1951/01/01|FR|Administrateur
MERGE|GradeTranslation|VISION|IC1|1951/01/01|FR|Contributeur individuel
145
MERGE|GradeTranslation|VISION|M1|1951/01/01|FR|Superviseur
MERGE|GradeTranslation|VISION|D1|1951/01/01|FR|Directeur
This example GradeStepTranslation.dat le translates the names of existing grade steps. It identies the grade steps by
their source keys.
METADATA|GradeStepTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|GradeStepName
MERGE|GradeStepTranslation|VISION|LT_CDR1|1951/01/01|FR|Niveau 1
Deleting Grades
You can delete a Grade object using HCM Data Loader, provided that it's not referenced by other objects, such as
Assignment, Job, or Grade Rate. This example Grade.dat le deletes existing grades and any associated grade steps. It
identies grades by their source keys.
METADATA|Grade|SourceSystemOwner|SourceSystemId|EffectiveStartDate
DELETE|Grade|VISION|CADET|1951/01/01
DELETE|Grade|VISION|LT_CDR|1951/01/01
Guidelines for Loading Grade Ladders

A grade ladder is a sequence of grades, where the grade order represents a worker's progression. This topic describes
aspects of the Grade Ladder object that you must understand to load grade ladders successfully.
The Grade-Ladder Component Hierarchy

The grade ladder is made up of these components:
• Grade Ladder.
• Grades in Ladder. Include one component of this type for each grade, regardless of the grade ladder type.
• Step Rate. Include at least one component of this type for grade ladders of type STEP.
• Step Rate Value. Include one component of this type for each step in a grade ladder of type STEP.
Loading Translated Grade-Ladder and Step-Rate Names

Supply grade-ladder and step-rate names in the language of the user who's loading them. You supply a
GradeLadderTranslation.dat le to translate grade-ladder names into other enabled languages once the grade ladders
exist. You supply a StepRateTranslation.dat le to translate step-rate names. This example GradeLadderTranslation.dat
le translates the name of an existing grade ladder. It identies the grade ladder by its source key.
METADATA|GradeLadderTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|GradeLadderName
MERGE|GradeLadderTranslation|VISION|GRD_LDR_OFF|1951/01/01|FR|Officier
Deleting Grade Ladders

You can delete a Grade Ladder object using HCM Data Loader, provided that it's not referenced by another object, such
as Assignment. Deleting a grade ladder doesn't delete the associated grades. However, if you delete a grade ladder with
steps, then the associated step rates and step-rate values are deleted automatically. This example GradeLadder.dat le
deletes an existing grade ladder. It identies the grade ladder by its source key.
146
METADATA|GradeLadder|SourceSystemOwner|SourceSystemId|EffectiveStartDate
DELETE|GradeLadder|VISION|GRD_LDR_OFF|1951/01/01
Guidelines for Loading Grade Rates

A grade rate is a collection of general information about a payment type, such as salary, bonus, or overtime. It includes
details such as the currency, frequency of the payment, and annualization factor. For example, the Overtime Rate
Analysts grade rate could provide this information for the overtime payments made to analysts. Grade rates are
associated with grade-rate values. Each associated grade-rate value identies a grade and either a xed payment or
a payment range for the grade. For a payment range, you must supply both the minimum and maximum values. This
topic describes aspects of the Grade Rate object that you must understand to load grade rates successfully.
Loading Referenced Objects

Grade rates and grade-rate values are created for a legislative data group. Therefore, Legislative Data Group objects
must exist before you load grade rates.
Loading Translated Grade-Rate Names

Supply grade-rate names in the language of the user who's loading them. You supply a GradeRateTranslation.dat le to
translate grade-rate names into other enabled languages once the grade rates exist. This example translates the name
of an existing grade rate. It identies the grade rate by its source key.
METADATA|GradeRateTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|GradeRateName
MERGE|GradeRateTranslation|VISION|GR_CIV_SAL|2000/01/01|FR|Salaire civile
Deleting Grade Rates

You can delete a Grade Rate object using HCM Data Loader, provided that it's not referenced by another object, such
as Salary Basis. If you delete a grade rate, then its associated grade-rate values are deleted automatically. This example
GradeRate.dat le deletes an existing grade rate and its grade-rate values. It identies the grade rate by its source key.
METADATA|GradeRate|SourceSystemOwner|SourceSystemId|EffectiveStartDate
DELETE|GradeRate|VISION|GR_CIV_SAL|2000/01/01
Guidelines for Loading Jobs

A job denes the worker's role in an organization in general terms. For example, a worker's job could be payroll
manager, sales consultant, or administrator. This topic describes aspects of the job object that you must understand to
load Job objects successfully.

If you're associating either job families or valid grades with your jobs, then you must load those objects before you load
the jobs.
147
Benchmark Jobs
To use benchmark jobs:
1. Load any benchmark jobs with the BenchmarkJobFlag aribute set to Yes. Benchmark jobs can't refer
to other benchmark jobs. Therefore, you can't load benchmark jobs with either a BenchmarkJobId or
BenchmarkJobCode value.
2. Load the remaining jobs. For those jobs that refer to a benchmark job, use the BenchmarkJobId or
BenchmarkJobCode aribute to identify the relevant benchmark job. A job can't be its own benchmark job.
Therefore, these values must not identify the job that you're loading.
Loading Translated Job Names

Supply job names in the language of the user who's loading them. You supply a JobTranslation.dat le to translate job
names into other enabled languages once the jobs exist. This example translates the names of existing jobs. It identies
those jobs by their source keys.
METADATA|JobTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|Name
MERGE|JobTranslation|VISION|SALES_CONS|2000/01/01|FR|Consultant en Ventes
MERGE|JobTranslation|VISION|SALES_MGR|2000/01/01|FR|Superviseur des Ventes
MERGE|JobTranslation|VISION|SALES_DIR|2000/01/01|FR|Directeur des Ventes
Deleting Jobs
You can't delete Job objects using HCM Data Loader. However, you can make jobs inactive. This example Job.dat le
inactivates an existing job. It identies the job by its source key.
METADATA|Job|SourceSystemOwner|SourceSystemId|EffectiveStartDate|ActiveStatus
MERGE|Job|VISION|MRKT_CONS|2015/01/01|I
Examples of Loading Job Families

A job family groups similar or related jobs for ease of reporting. For example, you could add the Trust Analyst and
Operations Analyst jobs to the Analyst job family. This topic provides some examples showing how to load and manage
Job Family objects.
Creating Job Families Using Source Keys

This example JobFamily.dat le creates several job families that are identied using source keys.
METADATA|JobFamily|SourceSystemOwner|SourceSystemId|EffectiveStartDate|JobFamilyCode|JobFamilyName|
ActiveStatus
MERGE|JobFamily|VISION|ANALYST|2000/01/01|ANALYST|Analyst|A
MERGE|JobFamily|VISION|TECHNICIAN|2000/01/01|TECHNICIAN|Technician|A
MERGE|JobFamily|VISION|CONSULT|2000/01/01|CONSULTANT|Consultant|A
MERGE|JobFamily|VISION|MANAGEMENT|2000/01/01|MANAGEMENT|Management|A
148
Loading Translated Job-Family Names

Job family names must be unique in the enterprise. Supply job family names in the language of the user who's loading
them. You supply a JobFamilyTranslation.dat le to translate job-family names into other enabled languages once the
job families exist. This example translates the names of existing job families. The job families are identied by their
source keys.
METADATA|JobFamilyTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|JobFamilyName
MERGE|JobFamilyTranslation|VISION|ANALYST|2000/01/01|FR|Analyste
MERGE|JobFamilyTranslation|VISION|TECHNICIAN|2000/01/01|FR|Technicien
Deleting Job Families

You can delete a Job Family object using HCM Data Loader, provided that the job family isn't referenced by any job.
This example deletes a job family. It identies the job family by its source key.
METADATA|JobFamily|SourceSystemOwner|SourceSystemId|EffectiveStartDate
DELETE|JobFamily|VISION|TECHNICIAN|2000/01/01
Guidelines for Loading Locations

A location is the physical address of a place where you conduct business or that's of interest to your business. The
Location object records the address and other details, such as the location name, description, phones, and billing and
shipping information. This topic describes aspects of the Location object that you must understand to load locations
successfully.
Changing Logical Start and End Dates for Locations

You can't change either the rst eective start date or last eective end date for an existing location. Create location
records with eective start dates on or before the start dates of other objects, such as Organization, that refer to your
locations.
Loading Translated Location Names

Supply location names and descriptions in the language of the user who's loading them. You supply a
LocationTranslation.dat le to translate location names and descriptions into other enabled languages once the
locations exist. This example translates the name and description of an existing location. It identies the location by its
source key.
METADATA|LocationTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|LocationName|
Description
MERGE|LocationTranslation|VISION|LOC_RD_UK|1951/01/01|FR|Vision Corporation Recherche et Developpement|Centre
de recherche et de developpement
149
Deleting Locations
You can't delete Location objects using HCM Data Loader. However, you can make locations inactive. This example
Location.dat le makes a location inactive as of 01/01/15. The location is identied by its source key.
METADATA|Location|SourceSystemOwner|SourceSystemId|EffectiveStartDate|ActiveStatus
MERGE|Location|VISION|LOC_UK_100|2015/01/01|I
Guidelines for Loading Organizations

An organization can be any organizational unit, such as a department or division, in your enterprise. Organizations
provide the framework for performing legal reporting, nancial control, and management reporting. This topic
describes aspects of the Organization object that you must understand to load organizations successfully.
Organization Components
A single organization can have multiple classications. For example, a division can also be a department. Therefore, you
can load multiple Organization Classication components for a single Organization object.
Note: You must load any Organization Extra Information component with the parent Organization
component in the same Organization.dat le. You can't load Organization Extra Information components
independently of the parent Organization component. You can load other child components either when
creating the organization or once the organization exists.

Before you load organizations, referenced objects must exist in the target environment. In particular:
• If you plan to associate locations with your organizations, then you must load the locations before you load the
organizations.
• To associate a reporting manager with your organization, you must:
a. Load the organization without identifying the reporting manager.

b. Load the worker information for the reporting manager.
c. Update your organization to add the reporting manager.
Tip: As a worker is hired into a legal employer, business unit, and department, you can't load
workers before you load organizations.
Note: Departments are set enabled. You must ensure that relevant reference data sets exist before you load
departments. Other types of organizations aren't set enabled.
Organization Classication Codes

An organization can have one or more classications. You can supply either the code or its name. Valid classications
are shown in this table.
150
Classication Name Classication Code
Department DEPARTMENT

Disability Organization HCM_ DISABILITY_ ORGANIZATION

Division HCM_DIVISION

Reporting Establishment HCM_ REPORTING_ ESTABLISHMENT

Union PER_ WORKER_UNION

You load an Organization Classication component for each of the organization's classications, including the one
identied on the Organization component.
Loading Translated Organization Names

Supply organization names in the language of the user who's loading them. You supply an OrganizationTranslation.dat
le to translate organization names into other enabled languages once the organizations exist. This example
OrganizationTranslation.dat le translates the name of an existing organization. It identies the organization by its
source key.
METADATA|OrganizationTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|Name
MERGE|OrganizationTranslation|VISION|MRKT|2000/01/01|FR|Marketing
Deleting Organizations
You can't delete Organization objects using HCM Data Loader, nor can you make them inactive. However, you can
make an organization classication inactive, provided that it's no longer used. For example, for an organization that's
classied as both a department and a division, you could:
• Make the division inactive but leave the department active, so that you can still continue to use the department.
• Deactivate the whole organization by making both classications inactive.
This example Organization.dat le inactivates an existing organization classication. The organization is identied by its
source key.
METADATA|Organization|SourceSystemOwner|SourceSystemId|EffectiveStartDate
MERGE|Organization|VISION|CLARITY|2015/01/01
METADATA|OrgUnitClassification|SourceSystemOwner|SourceSystemId|EffectiveStartDate|
OrganizationId(SourceSystemId)|Status
MERGE|OrgUnitClassification|VISION|CLARITY_DIS|2015/01/01|CLARITY|I
Note: The le must include an Organization component with an eective start date equal to the date on
which the classication becomes inactive.
151
Guidelines for Loading Positions

A position is a single occurrence of a job in a specied department. Positions may also be restricted by location. For
example, you could create the HR Manager Sales France position for the HR Manager job in the Sales department in
France. This topic describes aspects of the Position object that you must understand to load positions successfully.
Eective Start Dates

A Position object and its child components must have the same eective start date.

Before you load positions, referenced objects must exist in the target environment. In particular:
• Positions exist in business units. Ensure that referenced business units exist.
• Both Job and Department are required aributes of a position. Ensure that referenced jobs and departments
exist.
• You can associate a location and valid grades with a position. Ensure that any referenced locations and grades
exist.
Position Type
When the position type is Single incumbent, you must supply:
• An FTE value. The value must be less than or equal to 1. For example, if the position incumbent works half the
standard working hours, then the full-time equivalent value is 0.5.
• A headcount of 1.
When the position type is Shared, you must supply:

• An FTE value
• A headcount that's equal to or greater than 1
Loading Translated Position Names

Supply position names in the language of the user who's loading them. You supply a PositionTranslation.dat le to
translate position names into other enabled languages once the positions exist. This example PositionTranslation.dat
le translates the name of an existing position. It identies the position by its source key.
METADATA|PositionTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|Name
MERGE|PositionTranslation|VISION|APP_SALES|2015/01/01|FR|Sales Consultant d'application
Deleting Positions
You can delete a Position object using HCM Data Loader, provided that it has never had an incumbent. When you delete
a position, its child components are deleted automatically. This example Position.dat le deletes an existing position.
The position is identied by its source key.
METADATA|Position|SourceSystemOwner|SourceSystemId|EffectiveStartDate
152
DELETE|Position|VISION|APP_SALES|2015/01/01
Examples of Loading HCM Position Hierarchies

An HCM position hierarchy is derived from the relationships between positions and their parent positions. You can
identify a position's parent position on the Manage Positions page if the Use HCM Position Hierarchy option is enabled
for the enterprise. This topic provides examples of how to load Position Hierarchy objects using HCM Data Loader. Each
Position Hierarchy object identies a position and its parent. All positions must exist in the target environment.
This gure shows the position hierarchy that these examples load.
EVP
VP
PM_DIR
PM_MGR_SALES PM_MGR_ACCESS
SNR_PM_SALES PM_SALES SNR_PM_ACCESS PM_ACCESS
Loading HCM Position Hierarchies Using Source Keys

This example PositionHierarchy.dat le loads Position Hierarchy objects using source keys.
METADATA|PositionHierarchy|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|
ParentPositionId(SourceSystemId)|PositionId(SourceSystemId)
153
MERGE|PositionHierarchy|Vision|1|2015/01/01|4712/12/31|PM_MGR_ACCESS|PM_ACCESS
MERGE|PositionHierarchy|Vision|2|2015/01/01|4712/12/31|PM_MGR_ACCESS|SNR_PM_ACCESS
MERGE|PositionHierarchy|Vision|3|2015/01/01|4712/12/31|PM_MGR_SALES|PM_SALES
MERGE|PositionHierarchy|Vision|4|2015/01/01|4712/12/31|PM_MGR_SALES|SNR_PM_SALES
MERGE|PositionHierarchy|Vision|5|2015/01/01|4712/12/31|PM_DIR|PM_MGR_ACCESS
MERGE|PositionHierarchy|Vision|6|2015/01/01|4712/12/31|PM_DIR|PM_MGR_SALES
MERGE|PositionHierarchy|Vision|7|2015/01/01|4712/12/31|VP|PM_DIR
MERGE|PositionHierarchy|Vision|8|2015/01/01|4712/12/31|EVP|VP
Loading HCM Position Hierarchies Using User Keys

This example PositionHierarchy.dat le loads Position Hierarchy objects using user keys.
METADATA|PositionHierarchy|EffectiveStartDate|EffectiveEndDate|ParentBusinessUnitName|ParentPositionCode|
BusinessUnitName|PositionCode
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|PM_MGR_ACCESS|VisionBU|PM_ACCESS
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|PM_MGR_ACCESS|VisionBU|SNR_PM_ACCESS
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|PM_MGR_SALES|VisionBU|PM_SALES
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|PM_MGR_SALES|VisionBU|SNR_PM_SALES
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|PM_DIR|VisionBU|PM_MGR_ACCESS
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|PM_DIR|VisionBU|PM_MGR_SALES
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|VP|VisionBU|PM_DIR
MERGE|PositionHierarchy|2015/01/01|4712/12/31|VisionBU|EVP|VisionBU|VP
Running the Flaen HCM Position Hierarchy Process

Changes to the parent position on the Manage Positions page automatically trigger a process to update the position
hierarchy. This process is also triggered automatically when you load position hierarchies using HCM Data Loader. You
can prevent the Flaen HCM Position Hierarchy process from running automatically by including a SET instruction in
the PositionHierarchy.dat le.
Guidelines for Loading Department Trees

A department tree is a hierarchy of departments. For each tree, you can dene multiple versions. However, only one
version can be active on any date. This topic describes aspects of Department Tree objects that you must understand to
load them successfully using HCM Data Loader.
Key Support
Department Tree is unlike most other objects that you can load using HCM Data Loader, as it doesn't support the
integration-key types. When you load department trees, you must supply the user-key aributes.
How Department Trees Are Implemented

Department trees are implemented using two HCM Data Loader objects. This table introduces those objects.
154
Object Description
Department Tree The denition of a tree and the versions of the tree. A tree version is empty until you load
department tree nodes for the tree version.

Department Tree Node The department tree nodes for a tree version. Each node represents a department.

Preparing Department Trees for Use

After loading department tree nodes, you must aen, audit, and activate your tree version. You can't reference your
tree version from other objects, such as Area of Responsibility, until it's active. You can activate your tree version on the
Manage Department Trees page in the Workforce Structures work area. In summary, you:
1. Search for and select your department tree.

2. Expand the hierarchy and select the version to activate.
3. Select Actions > Set Status > Active to activate the tree version. The tree aening and audit occur
automatically.
For more information about managing hierarchy trees, see the Implementing Global Human Resources guide.
Loading Department Trees

You supply department-tree data in the DepartmentTree.dat le for processing by HCM Data Loader. The
TreeStructureCode aribute of both the department tree and the department tree version must be set to
PER_DEPT_TREE_STRUCTURE for a department tree.
Note: When you load a new department tree version for an existing department tree, you must include the
Department Tree component in the DepartmentTree.dat le. You can't load a new department tree version in
isolation.
This example DepartmentTree.dat le creates a department tree with code Department Tree Code and three versions,
one for each of January, February, and March.
METADATA|DepartmentTree|TreeStructureCode|TreeCode|TreeName|TreeDescription
MERGE|DepartmentTree|PER_DEPT_TREE_STRUCTURE|Department Tree Code|My Tree Name|My Tree Description
METADATA|DepartmentTreeVersion|TreeStructureCode|TreeCode|TreeVersionName|TreeVersionDescription|
TreeVersionStartDate|TreeVersionEndDate
MERGE|DepartmentTreeVersion|PER_DEPT_TREE_STRUCTURE|Department Tree Code|Tree Version Jan|Tree Description
Jan|2015/01/01|2015/01/31
MERGE|DepartmentTreeVersion|PER_DEPT_TREE_STRUCTURE|Department Tree Code|Tree Version Feb|Tree Description
Feb|2015/02/01|2015/02/28
MERGE|DepartmentTreeVersion|PER_DEPT_TREE_STRUCTURE|Department Tree Code|Tree Version Mar|Tree Description
Mar|2015/03/01|2015/03/31
Deleting Department Trees

You can delete Department Tree and Department Tree Version components using HCM Data Loader. When you delete
a department tree, the tree and all of its versions and nodes are deleted.
Note: The departments themselves aren't deleted. Only the relationships dened in the tree structure are
deleted.
155
This example DepartmentTree.dat le deletes a department tree:

METADATA|DepartmentTree|TreeStructureCode|TreeCode
DELETE|DepartmentTree|PER_DEPT_TREE_STRUCTURE|Department Tree Code
If you delete a department tree version, then only the specied version and its nodes are deleted. The tree and its other
versions are retained. This example DepartmentTree.dat le deletes a department tree version:
METADATA|DepartmentTreeVersion|TreeStructureCode|TreeCode|TreeVersionName
DELETE|DepartmentTreeVersion|PER_DEPT_TREE_STRUCTURE|Department Tree Code|Tree Version Feb
Guidelines for Loading Department Tree Nodes

A department is an internal organization to which workers are assigned. You can add any organization that has the
Department classication as a tree node to a department tree version. This topic describes aspects of Department Tree
Node objects that you must understand to load them successfully using HCM Data Loader.
Preparing to Load Department Tree Nodes

Before you load department tree nodes:
• You must create the department tree and department tree version to which the nodes belong. You can either
load them using HCM Data Loader or create them using the Manage Department Trees task in the Workforce
Structures work area.
• The departments that the tree nodes refer to must exist on the start date of the tree hierarchy version. Simply
adding a department to the department tree hierarchy doesn't create the department. Similarly, removing a
department reference from a department tree hierarchy doesn't delete the department record.
Loading Department Tree Nodes

The department tree node records the relationship between a parent department and a child, which can be either a
department or another department tree version. When the child is another department tree version, the department
nodes of that version are included by reference. When you load department tree nodes, these rules apply:
• You must supply a parent department for all nodes except the top-level node of your department tree version.
The parent departments must exist.
• The TreeStructureCode aribute must be set to PER_DEPT_TREE_STRUCTURE.
• To avoid circular relationships, a department can appear only once in each tree version.
• Each tree version can have only one top node. If you need multiple peer departments at the top, then consider
using a dummy department as the top node.
Related Topics
• Processes to Run After Loading Data
156
Examples of Loading Department Tree Nodes

You can load any organization that has the Department classication as a tree node to a department tree version. This
topic shows how to load Department Tree Node objects using HCM Data Loader.
Creating Department Tree Nodes

This example DepartmentTreeNode.dat le loads department tree nodes to an existing department tree version.
METADATA|DepartmentTreeNode|TreeStructureCode|TreeCode|TreeVersionName|DepartmentName|ParentDepartmentName
MERGE|DepartmentTreeVersion|PER_DEPT_TREE_STRUCTURE|Department Tree Code|Tree Version Jan|Vision University|
MERGE|DepartmentTreeVersion|PER_DEPT_TREE_STRUCTURE|Department Tree Code|Tree Version Jan|School of Arts and
Science|Vision University
MERGE|DepartmentTreeVersion|PER_DEPT_TREE_STRUCTURE|Department Tree Code|Tree Version Jan|Drama|School of Arts
and Science
MERGE|DepartmentTreeVersion|PER_DEPT_TREE_STRUCTURE|Department Tree Code|Tree Version Jan|Languages|Vision
University
MERGE|DepartmentTreeVersion|PER_DEPT_TREE_STRUCTURE|Department Tree Code|Tree Version Jan|French|Languages
MERGE|DepartmentTreeVersion|PER_DEPT_TREE_STRUCTURE|Department Tree Code|Tree Version Jan|German|Languages
This gure shows the hierarchy nodes that this DepartmentTreeNode.dat le creates.
Vision University
School of Arts and

Languages
Science
Drama French German
157
Deleting Department Tree Nodes

You can delete Department Tree Node objects using HCM Data Loader. The departments are removed from the
tree version, but the department objects themselves continue to exist. To delete a department tree node and
all nodes below it in the department tree hierarchy, set the DeleteChildNodesFlag aribute to Y. This example
DepartmentTreeNode.dat le deletes a node and its child nodes.
METADATA|DepartmentTreeNode|TreeStructureCode|TreeCode|TreeVersionName|DepartmentName|DeleteChildNodesFlag
DELETE|DepartmentTreeVersion|PER_DEPT_TREE_STRUCTURE|Department Tree Code|Tree Version Jan|Languages|Y
This gure shows the hierarchy after deleting the Languages node and its child nodes.
Vision University
School of Arts and

Science
Drama
To delete a department tree node and promote its child nodes, set the DeleteChildNodesFlag aribute to N. This
example DepartmentTreeNode.dat le deletes a node and promotes its child nodes.
METADATA|DepartmentTreeNode|TreeStructureCode|TreeCode|TreeVersionName|DepartmentName|DeleteChildNodesFlag
DELETE|DepartmentTreeVersion|PER_DEPT_TREE_STRUCTURE|Department Tree Code|Tree Version Jan|Languages|N
This gure shows the hierarchy after deleting the Languages node and promoting its child nodes.
158
Vision University
School of Arts and

French German
Science
Drama
Guidelines for Loading Organization Trees

An organization tree is a hierarchy of organizations of any classication. For each tree, you can dene multiple versions.
However, only one version can be active on any date. This topic describes aspects of Organization Tree objects that you
must understand to load them successfully using HCM Data Loader.
Key Support
Organization Tree is unlike most other objects that you can load using HCM Data Loader, as it doesn't support the
integration-key types. When you load organization trees, you must supply the user-key aributes.
How Organization Trees Are Implemented

Organization trees are implemented using two HCM Data Loader objects. This table introduces those objects.
Object Description
Organization Tree The denition of a tree and the versions of the tree. A tree version is empty until you load
organization tree nodes for the tree version.

Organization Tree Node The organization tree nodes for a tree version. Each node represents an organization.

159
Preparing Organization Trees for Use

After loading organization tree nodes, you must aen, audit, and activate your tree version. You can't reference your
tree version from other objects, such as Area of Responsibility, until it's active. You can activate your tree version on the
Manage Organization Trees page in the Workforce Structures work area. In summary, you:
1. Search for and select your organization tree.

2. Expand the hierarchy and select the version to activate.
3. Select Actions > Set Status > Active to activate the tree version. The tree aening and audit occur
automatically.
For more information about managing hierarchy trees, see the Implementing Global Human Resources guide.
Loading Organization Trees

You supply organization-tree data in the OrganizationTree.dat le for processing by HCM Data Loader. The
TreeStructureCode aribute of both the organization tree and the organization tree version must be set to
PER_ORG_TREE_STRUCTURE for an organization tree.
Note: When you load a new organization tree version for an existing organization tree, you must include the
organization tree component in the OrganizationTree.dat le. You can't load a new organization tree version
in isolation.
This example OrganizationTree.dat le creates an organization tree with code Organization Tree Code and three
versions, one for each of January, February, and March.
METADATA|OrganizationTree|TreeStructureCode|TreeCode|TreeName|TreeDescription
MERGE|OrganizationTree|PER_ORG_TREE_STRUCTURE|Organization Tree Code|My Tree Name|My Tree Description
METADATA|OrganizationTreeVersion|TreeStructureCode|TreeCode|TreeVersionName|TreeVersionDescription|
TreeVersionStartDate|TreeVersionEndDate
MERGE|OrganizationTreeVersion|PER_ORG_TREE_STRUCTURE|Organization Tree Code|Tree Version Jan|Tree Description
Jan|2015/01/01|2015/01/31
MERGE|OrganizationTreeVersion|PER_ORG_TREE_STRUCTURE|Organization Tree Code|Tree Version Feb|Tree Description
Feb|2015/02/01|2015/02/28
MERGE|OrganizationTreeVersion|PER_ORG_TREE_STRUCTURE|Organization Tree Code|Tree Version Mar|Tree Description
Mar|2015/03/01|2015/03/31
Deleting Organization Trees

You can delete Organization Tree and Organization Tree Version components using HCM Data Loader. When you
delete an organization tree, the tree and all of its versions and nodes are deleted.
Note: The organizations themselves aren't deleted. Only the relationships dened in the tree structure are
deleted.
This example OrganizationTree.dat le deletes an organization tree:

METADATA|OrganizationTree|TreeStructureCode|TreeCode
DELETE|OrganizationTree|PER_ORG_TREE_STRUCTURE|Organization Tree Code
If you delete an organization tree version, then only the specied version and its nodes are deleted. The tree and its
other versions are retained. This example OrganizationTree.dat le deletes an organization tree version:
METADATA|OrganizationTreeVersion|TreeStructureCode|TreeCode|TreeVersionName
DELETE|OrganizationTreeVersion|PER_ORG_TREE_STRUCTURE|Organization Tree Code|Tree Version Feb
160
Guidelines for Loading Organization Tree Nodes

You can load an organization of any classication as a tree node to an organization tree version. This topic describes
aspects of Organization Tree Node objects that you must understand to load them successfully using HCM Data Loader.
Preparing to Load Organization Tree Nodes

Before you load organization tree nodes:
• You must create the organization tree and organization tree version to which the nodes belong. You can either
load them using HCM Data Loader or create them using the Manage Organization Trees task in the Workforce
Structures work area.
• The organizations that the tree nodes refer to must exist on the start date of the tree hierarchy version. Simply
adding an organization to the organization tree hierarchy doesn't create the organization. Similarly, removing
an organization reference from an organization tree hierarchy doesn't delete the organization record.
Loading Organization Tree Nodes

The organization tree node records the relationship between a parent organization and a child, which can be either an
organization or another organization tree version. When the child is an organization, you specify its classication on
the ClassicationCode aribute. When the child is another organization tree version, the organization nodes of that
version are included by reference. When you load organization tree nodes, these rules apply:
• You must supply a parent organization for all nodes except the top-level node of your organization tree
version. The parent organizations must exist.
• The TreeStructureCode aribute must be set to PER_ORG_TREE_STRUCTURE.
• To avoid circular relationships, an organization can appear only once in each tree version.
• Each tree version can have only one top node. If you need multiple peer organizations at the top, then consider
using the enterprise as the top node.
Related Topics
• Processes to Run After Loading Data
Examples of Loading Organization Tree Nodes

You can load an organization with any classication as a tree node to an organization tree version. This topic shows how
to load organization tree nodes using HCM Data Loader.
Creating Organization Tree Nodes

This example OrganizationTreeNode.dat le loads organization tree nodes to an existing organization tree version.
METADATA|OrganizationTreeNode|TreeStructureCode|TreeCode|TreeVersionName|OrganizationName|ClassificationCode|
ParentOrganizationName|ParentOrganizationClassificationCode
161
MERGE|OrganizationTreeVersion|PER_ORG_TREE_STRUCTURE|Vision Tree Code|Tree Version 2017|Vision Enterprise|

Enterprise||
MERGE|OrganizationTreeVersion|PER_ORG_TREE_STRUCTURE|Vision Tree Code|Tree Version 2017|US Division|Division|
Vision Enterprise|Enterprise
MERGE|OrganizationTreeVersion|PER_ORG_TREE_STRUCTURE|Vision Tree Code|Tree Version 2017|US LE|Legal Employer|
US Division|Division
MERGE|OrganizationTreeVersion|PER_ORG_TREE_STRUCTURE|Vision Tree Code|Tree Version 2017|EMEA Division|
Division|Vision Enterprise|Enterprise
MERGE|OrganizationTreeVersion|PER_ORG_TREE_STRUCTURE|Vision Tree Code|Tree Version 2017|France LE|Legal
Employer|EMEA Division|Division
MERGE|OrganizationTreeVersion|PER_ORG_TREE_STRUCTURE|Vision Tree Code|Tree Version 2017|Italy LE|Legal
Employer|EMEA Division|Division
This gure shows the hierarchy nodes that this OrganizationTreeNode.dat le creates.
Vision Enterprise
US Division EMEA Division
US LE France LE Italy LE
Deleting Organization Tree Nodes

You can delete organization tree nodes using HCM Data Loader. The organizations are removed from the tree version,
but the organization objects themselves continue to exist. To delete an organization tree node and all nodes below it in
the organization tree hierarchy, set the DeleteChildNodesFlag aribute to Y. This example OrganizationTreeNode.dat
le deletes a node and its child nodes.
DeleteChildNodesFlag
DELETE|OrganizationTreeVersion|PER_ORG_TREE_STRUCTURE|Vision Tree Code|Tree Version 2017|EMEA Division|
Division|Y
162
This gure shows the hierarchy after deleting the EMEA Division node and its child nodes.
Vision Enterprise
US Division
US LE
To delete an organization tree node and promote its child nodes, set the DeleteChildNodesFlag aribute to N. This
example OrganizationTreeNode.dat le deletes a node and promotes its child nodes.
DeleteChildNodesFlag
DELETE|OrganizationTreeVersion|PER_ORG_TREE_STRUCTURE|Vision Tree Code|Tree Version 2017|EMEA Division|
Division|N
This gure shows the hierarchy after deleting the EMEA Division node and promoting its child nodes.
163
Vision Enterprise
US Division France LE Italy LE
US LE
164
Integrating with HCM Loading Compensation Objects
12 Loading Compensation Objects
Guidelines for Loading Market Data Objects

You can load survey data from external suppliers using HCM Data Loader market data objects. The survey data can
include salary, bonuses, benets, and so on. This topic provides some tips for loading market data objects.
Loading Any Type of Market Data

Before you can load any of the market data objects, you must dene the survey data supplier. Let's say you're loading
survey data from Hay. You need a supplier denition for Hay in your environment before you can load the data. Use the
Manage Supplier Structures task in the Compensation work area to dene suppliers of survey data.
Loading Market Data Survey Data

Before you can load a Market Data Survey Data object, you must dene:
• The survey, for example, Hay Professional. Use the Manage Surveys task in the Compensation work area to
dene surveys.
• The value of any CompensationTypeCode aribute that you supply. Use the Manage Compensation Types
task in the Compensation work area to dene compensation types.
• Any of these market data job structures objects that you reference on the Market Data Survey Data object:
◦ Market Data Career Stream

◦ Market Data Career Level
◦ Market Data Other Level
◦ Market Data Job Family
◦ Market Data Job Function
You load just the market data job structures objects that you want to use in your compensation analyses.
• Any of these objects that you reference on the Market Data Survey Data object:
◦ Market Data Job List

◦ Market Data Location List
You need to load any job structures objects before the Market Data Job List object, because the job list refers to the job
structures objects.
Tip: To be sure that all object references can resolve, load the Market Data Survey Data object last.
The objects referenced on the Market Data Survey Data object, such job family, can apply to more than one survey from
the same supplier.
165
Loading Market Data Survey Data from Spreadsheets

You can use HCM Spreadsheet Data Loader to load market data objects. Spreadsheet templates are supplied, and you
can copy them to create your own versions. You can nd the supplied templates:
• In the Compensation work area, for Compensation Analysts

• In the Data Exchange work area, for Human Capital Management Integration Specialists
Examples of Loading Market Data Career Level, Career

Stream, and Other Level
This topic shows how to load the Market Data Career Level, Market Data Career Stream, and Market Data Other Level
objects using HCM Data Loader. A supplier of market data, such as Hay, supplies the object data.
Loading Market Data Career Level

A Market Data Career Level object describes a stage in a career, such as entry level, intermediate, professional, or
executive. This example loads three Market Data Career Level objects. The objects are referenced using source keys.
METADATA|MktCareerLevel|SourceSystemOwner|SourceSystemId|VendorCode|CareerLevelCode|CareerLevelName|
Description|CareerLevelSequence|Status|CareerLevelDescr
MERGE|MktCareerLevel|VISION|CL_HAY_APPR|HAY|APPR|Apprentice|Apprentice|1|A|HAY Apprentice Career Level
Notes.txt
MERGE|MktCareerLevel|VISION|CL_HAY_JRNY|HAY|JRNY|Journeyman|Journeyman|2|A|HAY Journeyman Career Level
Notes.txt
MERGE|MktCareerLevel|VISION|CL_HAY_MSTR|HAY|MSTR|Master|Master|3|A|HAY Master Career Level Notes.txt
You include the .txt les named on the CareerLevelDescr aribute in the ClobFiles folder in the .zip le.
Loading Market Data Career Stream

A Market Data Career Stream object is a model of a career, usually dened for a professional eld. This example loads
three Market Data Career Stream objects. The objects are referenced using source keys.
METADATA|MktCareerStream|SourceSystemOwner|SourceSystemId|VendorCode|CareerStreamCode|CareerStreamName|
Description|CareerStreamSequence|Status|CareerStreamDescr
MERGE|MktCareerStream|VISION|CS_HAY_CONT|HAY|CONT|Contributing|Contributing|1|A|HAY Contributing Career Stream
Notes.txt
MERGE|MktCareerStream|VISION|CS_HAY_JOUR|HAY|JOUR|Journey|Journey|2|A|HAY Journey Career Stream Notes.txt
MERGE|MktCareerStream|VISION|CS_HAY_ADVA|HAY|ADVA|Advanced|Advanced|3|A|HAY Advanced Career Stream Notes.txt
You include the .txt les named on the CareerStreamDescr aribute in the ClobFiles folder in the .zip le.
166
Loading Market Data Other Level

A Market Data Other Level object can be any career stage that isn't dened as a career level or career stream. This
example loads four Market Data Other Level objects. The objects are referenced using source keys.
METADATA|MktOtherLevel|SourceSystemOwner|SourceSystemId|VendorCode|OtherLevelCode|OtherLevelName|Description|
OtherLevelSequence|Status|OtherLevelDescr
MERGE|MktOtherLevel|VISION|OL_HAY_1|HAY|100|Associate|Associate|1|A|HAY Associate Other Level Notes.txt
MERGE|MktOtherLevel|VISION|OL_HAY_2|HAY|200|Analyst|Analyst|2|A|HAY Analyst Other Level Notes.txt
MERGE|MktOtherLevel|VISION|OL_HAY_3|HAY|300|Senior|Senior|3|A|HAY Senior Other Level Notes.txt
MERGE|MktOtherLevel|VISION|OL_HAY_4|HAY|400|Principal|Principal|4|A|HAY Principal Other Level Notes.txt
You include the .txt les named on the OtherLevelDescr aribute in the ClobFiles folder in the .zip le.
Examples of Loading Market Data Job Family and

Function
This topic shows how to load the Market Data Job Family and Market Data Job Function objects using HCM Data
Loader. A supplier of market survey data, such as Hay, supplies the object data.
Loading Market Data Job Family

You group similar jobs in Market Data Job Family objects to make reporting easier. For example, you could group the
Trust Analyst and Operations Analyst jobs into a job family named Analyst. This example creates six Market Data Job
Family objects. The objects are identied using source keys.
METADATA|MktJobFamily|SourceSystemOwner|SourceSystemId|VendorCode|JobFamilyCode|JobFamilyName|Description|
JobFamilySequence|Status|JobFamilyDescr
MERGE|MktJobFamily|VISION|JF_HAY_HR-BEN|HAY|HR-BEN|Benefits|Human Resources - Benefits|1|A|HAY Benefits Job
Family Notes.txt
MERGE|MktJobFamily|VISION|JF_HAY_HR-CMP|HAY|HR-CMP|Compensation|Human Resources - Compensation|2|A|HAY
Compensation Job Family Notes.txt
MERGE|MktJobFamily|VISION|JF_HAY_HR-DEV|HAY|HR-DEV|Organizational Development|Human Resources - OD|3|A|HAY OD
Job Family Notes.txt
MERGE|MktJobFamily|VISION|JF_HAY_AC-REC|HAY|AC-PAY|Accounts Receivable|Accounting - Accounts Receivable|4|A|
HAY AR Job Family Notes.txt
MERGE|MktJobFamily|VISION|JF_HAY_AC-PAY|HAY|AC-PAY|Accounts Payable|Accounting - Accounts Payable|5|A|HAY AP
Job Family Notes.txt
MERGE|MktJobFamily|VISION|JF_HAY_AC-COS|HAY|AC-COS|Cost Accounting|Accounting - Cost Accounting|6|A|HAY Cost
Accounting Job Family Notes.txt
You include the .txt les named on the JobFamilyDescr aribute in the ClobFiles folder in the .zip le.
Loading Market Data Job Function

Market Data Job Function objects are broad categories for jobs, such as Accounting and Engineering. This example
creates three Market Data Job Function objects. The objects are identied using source keys.
167
METADATA|MktJobFunction|SourceSystemOwner|SourceSystemId|VendorCode|JobFunctionCode|JobFunctionName|
Description|JobFunctionSequence|Status|JobFunctionDescr
MERGE|MktJobFunction|VISION|JFN_HAY_ACCT|HAY|ACCT|Accounting|Accounting Jobs|1|A|HAY Accounting Job Function
Notes.txt
MERGE|MktJobFunction|VISION|JFN_HAY_HR|HAY|HR|Human Resources|Human Resources Jobs|2|A|HAY HR Job Function
Notes.txt
MERGE|MktJobFunction|VISION|JFN_HAY_IT|HAY|IT|Information Technology|Information Technology Jobs|3|A|HAY IT
Job Function Notes.txt
You include the .txt les named on the JobFunctionDescr aribute in the ClobFiles folder in the .zip le.
Examples of Loading Market Data Location List and Job

List
This topic shows how to load the Market Data Location List and Market Data Job List objects using HCM Data Loader. A
supplier of market data, such as Hay, provides the object data.
Loading Market Data Location List

A Market Data Location List object is a single location that's included in the survey data. Its child component, Market
Data Location Map, maps the survey location to an internal location. This example creates ve locations with location
mappings. The objects are identied using source keys.
METADATA|MktLocationList|SourceSystemOwner|SourceSystemId|VendorCode|SurveyLocationCode|SurveyLocationName|
Status
MERGE|MktLocationList|VISION|LOC_HAY_AKR|HAY|AKR|Akron, OH|A
MERGE|MktLocationList|VISION|LOC_HAY_ALB|HAY|ALB|Albany, NY|A
MERGE|MktLocationList|VISION|LOC_HAY_ALL|HAY|AKR|Allentown, PA|A
MERGE|MktLocationList|VISION|LOC_HAY_ALQ|HAY|ALQ|Albuquerque, NM|A
MERGE|MktLocationList|VISION|LOC_HAY_CHI|HAY|CHI|Chicago, IL|A
METADATA|MktLocationMapping|SourceSystemOwner|SourceSystemId|SurveyLocationId(SourceSystemId)|
LocationId(SourceSystemId)|VendorCode
MERGE|MktLocationMapping|VISION|LM_HAY_AKR|LOC_HAY_AKR|HAM_OH|HAY
MERGE|MktLocationMapping|VISION|LM_HAY_ALB|LOC_HAY_ALB|ALBANY_NY|HAY
MERGE|MktLocationMapping|VISION|LM_HAY_ALL|LOC_HAY_ALL|BUTLER_PA|HAY
MERGE|MktLocationMapping|VISION|LM_HAY_ALQ|LOC_HAY_ALQ|ALB_NM|HAY
MERGE|MktLocationMapping|VISION|LM_HAY_CHI|LOC_HAY_CHI|CHI_IL|HAY
The mappings between internal and external locations aren't required if they're one-to-one. But, they're needed
if you're mapping multiple internal locations to an external location. You can create the mappings later in the user
interface if you prefer.
Loading Market Data Job List

A Market Data Job List is information about a single job included the survey data. This example creates seven jobs. The
objects are identied using source keys.
METADATA|MktJobList|SourceSystemOwner|SourceSystemId|VendorCode|VendorJobCode|Description|VendorJobTitle|
VendorJobDescrChar|Status|JobId(SourceSystemId)|JobFamilyId(SourceSystemId)|JobFunctionId(SourceSystemId)|
CareerLevelId(SourceSystemId)|CareerStreamId(SourceSystemId)|OtherLevelId(SourceSystemId)
168
MERGE|MktJobList|VISION|HAY-ACCT_CA|HAY|HAY-ACCT_CA|Cost accountant match job notes|Cost Accountant|Cost

Accountant job|A|VIS_PAY_CA|JF_HAY_AC-COS|JFN_HAY_ACCT|||
MERGE|MktJobList|VISION|HAY-ACCT_PA|HAY|HAY-ACCT_PA||Payables Accountant|Payables Accountant job|A|VIS_PAY_PA|
JF_HAY_AC-PAY|JFN_HAY_ACCT|||
MERGE|MktJobList|VISION|HAY-ASSOC_ENG|HAY|HAY-ASSOC_ENG||Associate Engineer|Associate Engineer job|A|
VIS_IT_AENG||JFN_HAY_IT||CS_HAY_CONT|
MERGE|MktJobList|VISION|HAY-ENG|HAY|HAY-ENG||Engineer|Engineer job|A|VIS_IT_ENG||JFN_HAY_IT||CS_HAY_JOUR|
MERGE|MktJobList|VISION|HAY-PLUM|HAY|HAY-PLUM||Plumber 1|Apprentice Plumber 1 job|A||||CL_HAY_APPR||
MERGE|MktJobList|VISION|HAY-ASSOC_CONSLT|HAY|HAY-ASSOC_CONSLT||Associate Consultant|Associate Consultant job|
A|VIS_ASSOC_CONS|||||OL_HAY_1
MERGE|MktJobList|VISION|HAY-CONSLT|HAY|HAY-CONSLT||Consultant|Consultant job|A|VIS_CONS|||||OL_HAY_2
You can use the job list to map survey jobs to internal jobs. Or, you can map the jobs in the user interface if you prefer,
Example of Loading Market Data Survey Data

The Market Data Survey Data object holds raw survey data. This topic shows how to load the Market Data Survey Data
object using HCM Data Loader. A supplier of market survey data, such as Hay, provides the object data.
Loading Market Data Survey Data

This example loads a single Market Data Survey Data object. It has a unique batch name, and it references jobs and
locations that you dened before loading this object. The Market Data Job List, Market Data Job Location, and Market
Data Survey Data objects are referenced using source keys.
METADATA|MktSurveyData|SourceSystemOwner|SourceSystemId|VendorCode|SurveyCode|BatchName|CompensationTypeCode|
JobListId(SourceSystemId)|VendorLocationId(SourceSystemId)|Industry|TenPercent|TwentyPercent|
TwentyFivePercent|ThirtyPercent|FortyPercent|FiftyPercent|SixtyPercent|SeventyPercent|SeventyFivePercent|
EightyPercent|NintyPercent|OneHundredPercent|AverageMean|Currency|CountryCode|ParticipatingIncumbants|
ParticipatingCompanies
MERGE|MktSurveyData|VISION|HAY_ACCT_CA_CHI|HAY|2019|HAY_2019|BAS|HAY-ACCT_CA|LOC_HAY_CHI|All|10000|20000|
25000|30000|40000|55000|60000|70000|75000|80000|90000|100000|50000|USD|US|653|5069
Guidelines for Loading Progression Grade Ladders

A progression grade ladder is a hierarchy of grades in sequence. It can include either grades with steps or grades
without steps, but not both. If your grades have steps, then you dene the grade rate using the Progression Grade
Ladder object. If your grades don't have steps, then you dene the grade rate using the Progression Grade Rate object
after loading your progression grade ladder records. This topic describes aspects of progression grade ladders that you
Preparing to Load Progression Grade Ladders

These referenced objects must exist in the target environment:
• Grade and Grade Set

• Legislative Data Group
In addition, if you're using action reasons, then dene or load them before loading progression grade ladders.
169
Using Grades Without Steps

If the grades don't have steps, then set these aributes of the Progression Grade Ladder object as shown in this table:
Aribute Value
GradeType GRADE

ProgressionStyleCode CMP_GSP_GP

Set both ProgActionCode and SalaryActionCode, which are required aributes, to the predened value
CMP_GRADE_STEP_PROGRESSION.
You load the separate Progression Grade Rate object instead of the Progression Step Rate and Progression Step Rate
Value components of the Progression Grade Ladder object.
Using Grades with Steps

If the grades have steps, then set these aributes of the Progression Grade Ladder object as shown in this table:
Aribute Value
GradeType STEP

ProgressionStyleCode CMP_GSP_GSP

Set both ProgActionCode and SalaryActionCode, which are required aributes, to the predened value
CMP_GRADE_STEP_PROGRESSION.
You load the Progression Step Rate and Progression Step Rate Value components of the Progression Grade Ladder
object. You don't load the Progression Grade Rate object.
Tip: Give the Progression Grade Ladder and Progression Step Rate components the same name, as a one-to-
one relationship exists between them.
Translating Aribute Values

You can translate:
• The name of the progression grade ladder. Use the Progression Grade Ladder Translation object.
• The name of the progression step rate, if you're using grades with steps. Use the Progression Step Rate
Translation object.
• The name of the progression grade rate, if you're using grades without steps. Use the Progression Grade Rate
Translation object.
170
If you're using the same name for the progression grade ladder and progression step rate, as recommended, then use
the same translated value for both.
Using Fast Formulas

Set these aributes to CMP_GSP_DATE_RULE when their value is determined by fast formula:
• ProgressionDateCode
• SalaryChangeDateCode
• RateChangeDateCode
Specify the formula name on the ProgressionDateRuleName, SalaryChangeDateRuleName, or

RateChangeDateRuleName aribute, as appropriate.
Set the SalaryCalculationMethodCode aribute to CMP_GSP_RATE_RULE when its value is determined by fast formula.
Specify the formula name on the SalaryCalculationRuleName aribute.
The fast formulas must exist in the target environment before you load Progression Grade Ladder objects. Date
formulas must have the Salary Progression Date Determination Rule type. Salary calculation formulas must have the
Salary Progression Rate Calculation Rule type.
Deleting Progression Grade Ladders

You can delete a progression grade ladder, provided that it isn't referenced by another object, for example, an
assignment. When you delete a progression grade ladder without steps, you must delete the associated Progression
Grade Rate and Progression Rule objects separately. When you delete a progression grade ladder with steps, the
associated step rates and values are deleted automatically. However, you must delete any associated Progression
Rule object separately. When you delete any progression grade ladder, the associated grades and eligibility proles are
unaected.
Examples of Loading Progression Grade Ladders with

Steps
This topic provides examples showing how to load Progression Grade Ladder objects with steps.
Creating a Progression Grade Ladder with Steps Using Source

Keys
This example ProgressionGradeLadder.dat le creates a progression grade ladder with steps. The le includes
Progression Grade Ladder, Grades In Progression Ladder, Progression Step Rate, and Progression Step Rate Value
components. All components use source keys. As recommended, the progression grade ladder and progression step
rate have the same name.
This excerpt shows the Progression Grade Ladder component.
171
METADATA|ProgressionGradeLadder|SourceSystemOwner|SourceSystemId|EffectiveStartDate|GradeLadderName|GradeType|
ActiveStatus|GradeSetCode|AllowProgOverrideFlag|AllowSalaryOverrideFlag|AutoProgressionCode|AutoSalChangeCode|
ProgressionDateCode|ProgressionStyleCode|RateChangeDateCode|SalaryCalculationMethodCode|SalaryChangeDateCode|
UpdateSalaryFlag|ProgActionCode|SalaryActionCode|LegislativeDataGroupId(SourceSystemId)
MERGE|ProgressionGradeLadder|VISION|GSP_ANALYSTS_PGL|2000/02/15|GSP Analysts|STEP|A|COMMON|N|
N|CMP_GSP_PROG_MANUAL|CMP_GSP_PROG_MANUAL|CMP_GSP_PROCESS_DT|CMP_GSP_GSP|CMP_GSP_PROCESS_DT|
CMP_GSP_GRADE_STEP_RATE|CMP_GSP_ELIGIBILITY_DT|Y|CMP_GRADE_STEP_PROGRESSION|CMP_GRADE_STEP_PROGRESSION|
GSP_US_LDG1
This excerpt shows the Grades In Progression Ladder components.

METADATA|GradesInProgressionLadder|SourceSystemOwner|SourceSystemId|EffectiveStartDate|GradesInLadderSequence|
GradeSetCode|GradeId(SourceSystemId)|GradeLadderId(SourceSystemId)
MERGE|GradesInProgressionLadder|VISION|GSP_ANALYSTS_PGL_GR1|2000/02/15|1|COMMON|ANALYST1_GR|GSP_ANALYSTS_PGL
This excerpt shows the Progression Step Rate component. The RateType value is SALARY and the ProgressionRateFlag
aribute is set to Y to indicate that this rate is to be used for grade step progression.
METADATA|ProgressionStepRate|SourceSystemOwner|SourceSystemId|EffectiveStartDate|
LegislativeDataGroupId(SourceSystemId)|GradeLadderId(SourceSystemId)|RateName|RateType|CurrencyCode|
RateFrequency|AnnualizationFactor|ActiveStatus|ProgressionRateFlag
MERGE|ProgressionStepRate|VISION|GSP_ANALYSTS_PGL_RT|2000/02/15|GSP_US_LDG1|GSP_ANALYSTS_PGL|GSP Analysts|
SALARY|USD|HOURLY|2080|A|Y
This excerpt shows the Progression Step Rate Value components.

METADATA|ProgressionStepRateValue|SourceSystemOwner|SourceSystemId|EffectiveStartDate|
LegislativeDataGroupId(SourceSystemId)|RateId(SourceSystemId)|RateObjectId(SourceSystemId)|StepRateValueAmount
MERGE|ProgressionStepRateValue|VISION|GSP_ANALYSTS_PGL_GR1_S1|2000/02/15|GSP_US_LDG1|GSP_ANALYSTS_PGL_RT|
ANALYST1_GRS1|20.00
ANALYST1_GRS2|22.75
ANALYST2_GRS1|24.20
ANALYST2_GRS2|26.00
ANALYST2_GRS3|28.25
ANALYST2_GRS4|30.25
ANALYST3_GRS1|32.00
ANALYST3_GRS2|34.80
ANALYST3_GRS3|36.15
ANALYST4_GRS1|38.00
ANALYST4_GRS2|40.10
ANALYST4_GRS3|42.00
ANALYST4_GRS4|45.25
ANALYST4_GRS5|48.15
172
Creating a Progression Grade Ladder with Steps Using Fast

Formulas and User Keys
This example ProgressionGradeLadder.dat le creates a progression grade ladder with steps. The le includes
Progression Grade Ladder, Grades In Progression Ladder, Progression Step Rate, and Progression Step Rate Value
components. All components use user keys. As recommended, the progression grade ladder and progression step rate
have the same name.
This excerpt shows the Progression Grade Ladder component. It includes references to four existing fast formulas on
the ProgressionDateCode, RateChangeDateCode, SalaryCalculationMethodCode, and SalaryChangeDateCode
aributes.
METADATA|ProgressionGradeLadder|EffectiveStartDate|GradeLadderName|ActionReasonCode|GradeType|ActiveStatus|
GradeSetCode|AllowProgOverrideFlag|AllowSalaryOverrideFlag|AutoProgressionCode|AutoSalChangeCode|
UpdateSalaryFlag|ProgActionCode|ProgActionReasonCode|SalaryActionCode|LegislativeDataGroup|
ProgressionDateRuleName|SalaryChangeDateRuleName|RateChangeDateRuleName|SalaryCalculationRuleName
MERGE|ProgressionGradeLadder|2016/01/01|GSP Nurses|GSP_NEW|STEP|A|COMMON|N|N|CMP_GSP_PROG_MANUAL|
CMP_GSP_PROG_MANUAL|CMP_GSP_DATE_RULE|CMP_GSP_GSP|CMP_GSP_DATE_RULE|CMP_GSP_RATE_RULE|CMP_GSP_DATE_RULE|Y|
CMP_GRADE_STEP_PROGRESSION|NEW_CONTRACT|CMP_GRADE_STEP_PROGRESSION|GBI United States LDG|GSP Assignment Date|
GSP Salary Date|GSP Rate Sync Salary Date|GSP Rate Calc
This excerpt shows the Grades In Progression Ladder components.

METADATA|GradesInProgressionLadder|EffectiveStartDate|GradesInLadderSequence|GradeSetCode|GradeCode|
GradeLadderName
MERGE|GradesInProgressionLadder|2016/01/01|1|COMMON|NURSE_1|GSP Nurses
This excerpt shows the Progression Step Rate component. The RateType value is SALARY and the ProgressionRateFlag
aribute is set to Y to indicate that this rate is to be used for grade step progression.
METADATA|ProgressionStepRate|EffectiveStartDate|RateName|RateType|CurrencyCode|RateFrequency|
AnnualizationFactor|ActiveStatus|LegislativeDataGroup|GradeLadderName|ProgressionRateFlag
MERGE|ProgressionStepRate|2016/01/01|GSP Nurses|SALARY|USD|Hourly|2080|A|GBI United States LDG|GSP Nurses|Y
This excerpt shows the Progression Step Rate Value components.

METADATA|ProgressionStepRateValue|EffectiveStartDate|StepRateValueAmount|RateName|GradeSetCode|GradeCode|
GradeStepName|LegislativeDataGroup|GradeLadderName
MERGE|ProgressionStepRateValue|2016/01/01|20.00|GSP Nurses|COMMON|NURSE_1|Step 1|GBI United States LDG|GSP
Nurses
Nurses
Nurses
Nurses
Nurses
Nurses
Nurses
Nurses
Nurses
173
Deleting Progression Grade Ladders with Steps

This example ProgressionGradeLadder.dat le deletes the GSP Nurses progression grade ladder. It references the object
by its user key. This le deletes the progression grade ladder, including the step rates and values. You must delete the
associated Progression Rule object separately.
METADATA|ProgressionGradeLadder|GradeLadderName
DELETE|ProgressionGradeLadder|GSP Nurses
Examples of Loading Progression Grade Ladders

Without Steps
This topic provides examples showing how to load Progression Grade Ladder objects without steps.
Creating a Progression Grade Ladder Without Steps Using Source

Keys
This example ProgressionGradeLadder.dat le creates a progression grade ladder where the grades don't have steps.
The le includes Progression Grade Ladder and Grades In Progression Grade Ladder components. Both components
use source keys. The rates are dened separately using Progression Grade Rate objects.

METADATA|ProgressionGradeLadder|SourceSystemOwner|SourceSystemId|EffectiveStartDate|GradeLadderName|GradeType|
ActiveStatus|GradeSetCode|AllowProgOverrideFlag|AllowSalaryOverrideFlag|AutoProgressionCode|AutoSalChangeCode|
UpdateSalaryFlag|ProgActionCode|SalaryActionCode|LegislativeDataGroupId(SourceSystemId)
MERGE|ProgressionGradeLadder|VISION|GSP_DEVELOPMENT|2000/02/15|GSP Development|GRADE|A|COMMON|
N|N|CMP_GSP_PROG_MANUAL|CMP_GSP_PROG_MANUAL|CMP_GSP_PROCESS_DT|CMP_GSP_GP|CMP_GSP_PROCESS_DT|
CMP_GSP_GRADE_STEP_RATE|CMP_GSP_ELIGIBILITY_DT|Y|CMP_GRADE_STEP_PROGRESSION|CMP_GRADE_STEP_PROGRESSION|
GSP_US_LDG1
This excerpt shows the Grades In Progression Grade Ladder components.

METADATA|GradesInProgressionLadder|SourceSystemOwner|SourceSystemId|EffectiveStartDate|GradesInLadderSequence|
GradeSetCode|GradeId(SourceSystemId)|GradeLadderId(SourceSystemId)
MERGE|GradesInProgressionLadder|VISION|GSP_DEVELOPMENT_GIL1|2000/02/15|1|COMMON|DEV1_GSP|GSP_DEVELOPMENT
174
Creating a Progression Grade Ladder Without Steps Using User

Keys
This example ProgressionGradeLadder.dat le creates a progression grade ladder where the grades don't have steps.
The le includes Progression Grade Ladder and Grades In Progression Grade Ladder components. Both components
use user keys. The rates are dened separately using Progression Grade Rate objects.

METADATA|ProgressionGradeLadder|EffectiveStartDate|GradeLadderName|GradeType|ActiveStatus|GradeSetCode|
AllowProgOverrideFlag|AllowSalaryOverrideFlag|AutoProgressionCode|AutoSalChangeCode|ProgressionDateCode|
ProgressionStyleCode|RateChangeDateCode|SalaryCalculationMethodCode|SalaryChangeDateCode|UpdateSalaryFlag|
ProgActionCode|SalaryActionCode|LegislativeDataGroup
MERGE|ProgressionGradeLadder|2010/01/01|GSP Staff|GRADE|A|COMMON|N|N|CMP_GSP_PROG_MANUAL|CMP_GSP_PROG_MANUAL|
CMP_GSP_PROCESS_DT|CMP_GSP_GP|CMP_GSP_PROCESS_DT|CMP_GSP_GRADE_STEP_RATE|CMP_GSP_ELIGIBILITY_DT|Y|
CMP_GRADE_STEP_PROGRESSION|CMP_GRADE_STEP_PROGRESSION|GBI United States LDG
This excerpt shows the Grades in Progression Grade Ladder components.

METADATA|GradesInProgressionLadder|EffectiveStartDate|GradesInLadderSequence|GradeSetCode|GradeCode|
GradeLadderName
MERGE|GradesInProgressionLadder|2010/01/01|1|COMMON|STAFF1|GSP Staff
Deleting Progression Grade Ladders Without Steps

This example ProgressionGradeLadder.dat le deletes a progression grade ladder and references it by its source key.
This progression grade ladder includes grades without steps. Therefore, you must delete any associated Progression
Grade Rate and Progression Rule objects separately.
METADATA|ProgressionGradeLadder|SourceSystemOwner|SourceSystemId
DELETE|ProgressionGradeLadder|VISION|GSP_DEVELOPMENT
Guidelines for Loading Progression Grade Rates

A progression grade rate is a grade rate associated with a progression grade ladder that doesn't use grade steps. The
progression grade rate identies the currency and frequency of payment for its associated grade rate values. The grade
rate values specify the salary ranges and rate values for each grade in the ladder. This topic describes some aspects of
progression grade rates that you must understand to load them successfully using HCM Data Loader.
Preparing to Load Progression Grade Rates

Before you load progression grade rates, these referenced objects must exist in the target environment:
• Grade and Grade Set

• Legislative Data Group
175
• Progression Grade Ladder
Progression Grade Rate Names

When you create a progression grade ladder on the Manage Progression Grade Ladders page, the associated
progression grade rate is created automatically. It has the same name as the progression grade ladder. Only one
progression grade rate can exist for a given progression grade ladder, and both objects have the same legislative
data group. When you create a progression grade rate using HCM Data Loader, give it the same name and LDG as its
associated progression grade ladder.
Progression Grade Rates in the Application

No independent user interface exists for creating and maintaining Progression Grade Rate objects. You create and
maintain progression grade rates in the application using the Manage Progression Grade Ladders page. You can also
view progression grade rates on the Manage Grade Rates page, as progression grade rates and grade rates share the
same underlying tables. However, you must not create progression grade rates on the Manage Grade Rates page. This
restriction exists because the values required for use in grade step progression wouldn't be populated. You can either
create progression grade rates automatically, when you create a progression grade ladder in the application, or load
them using HCM Data Loader.
Examples of Loading Progression Grade Rates

This topic provides examples showing how to load Progression Grade Rate objects using HCM Data Loader.
Creating Progression Grade Rates

In both examples in this section, the progression grade rate:
• Uses grades without grade steps, and the rates are quoted as monthly amounts
• Has the same name as its associated progression grade ladder
• Has a RateType of SALARY, and the ProgressionRateFlag is set to Y to indicate that this rate is to be used for
grade step progression
This example ProgressionGradeRate.dat le creates a Progression Grade Rate object using source keys.
METADATA|ProgressionGradeRate|SourceSystemOwner|SourceSystemId|EffectiveStartDate|GradeRateName|
LegislativeDataGroupId(SourceSystemId)|RateType|CurrencyCode|RateFrequency|ActiveStatus|AnnualizationFactor|
ProgressionRateFlag|GradeLadderId(SourceSystemId)
MERGE|ProgressionGradeRate|VISION|GSP_DEVELOPMENT_GR|2000/02/15|GSP Development|GSP_US_LDG1|SALARY|USD|
MONTHLY|A|12|Y|GSP_DEVELOPMENT
METADATA|ProgressionGradeRateValue|SourceSystemOwner|SourceSystemId|EffectiveStartDate|
LegislativeDataGroupId(SourceSystemId)|RateId(SourceSystemId)|RateObjectId(SourceSystemId)|MinimumAmount|
MaximumAmount|ValueAmount
MERGE|ProgressionGradeRateValue|VISION|GSP_DEVELOPMENT_GRV1|2000/02/15|GSP_US_LDG1|GSP_DEVELOPMENT_GR|
DEV1_GSP|3500|6500|5000
DEV2_GSP|4500|7500|6000
DEV3_GSP|5500|8500|7000
DEV4_GSP|6500|9500|8000
176
DEV5_GSP|7500|10500|9000
DEV6_GSP|8500|11500|10000
This example ProgressionGradeRate.dat le creates a Progression Grade Rate object using user keys.
METADATA|ProgressionGradeRate|EffectiveStartDate|RateType|GradeRateName|GradeLadderName|CurrencyCode|
RateFrequency|AnnualizationFactor|ActiveStatus|LegislativeDataGroup|ProgressionRateFlag
MERGE|ProgressionGradeRate|2010/01/01|Salary|GSP Staff|GSP Staff|USD|Monthly|12|A|GBI United States LDG|Y
METADATA|ProgressionGradeRateValue|EffectiveStartDate|MinimumAmount|MaximumAmount|MidValueAmount|ValueAmount|
GradeRateName|SetCode|GradeCode|LegislativeDataGroup
MERGE|ProgressionGradeRateValue|2010/01/01|2000|5000|3500|3000|GSP Staff|COMMON|STAFF1|GBI United States LDG
Deleting Progression Grade Rates

When you delete a progression grade rate, its grade rate values are also deleted. You can delete a progression grade
rate using HCM Data Loader provided that another object, such as a salary basis, isn't referencing it. If the progression
grade rate is used in a progression grade ladder, then delete it only if you're also deleting the related progression grade
ladder.
This example ProgressionGradeRate.dat le deletes a progression grade rate, which is identied using source keys.
METADATA|ProgressionGradeRate|SourceSystemOwner|SourceSystemId|LegislativeDataGroupId(SourceSystemId)
DELETE|ProgressionGradeRate|VISION|GSP_DEVELOPMENT_GR|GSP_US_LDG1
This example ProgressionGradeRate.dat le deletes a progression grade rate, which is identied using user keys.
METADATA|ProgressionGradeRate|LegislativeDataGroup|GradeRateName
DELETE|ProgressionGradeRate|GBI United States LDG|GSP Staff
Guidelines for Loading Progression Rules

A progression rule denes the conditions that determine whether a worker can move to the next grade or grade step in
a progression grade ladder. If you're using grade step progression for your progression grade ladder, then you load the
progression rules using the Progression Rule object. This topic describes some aspects of progression rules that you
Preparing to Load Progression Rules

Before you can load Progression Rule objects, these referenced objects must exist in the target environment:
• Progression Grade Ladder

• Eligibility Prole
Progression Rules and Eligibility Proles

A progression rule is simply the name of an eligibility prole. The eligibility prole denes the conditions that must be
met for progression to occur. You can associate a progression rule with a progression grade ladder, grade, or grade
177
step. The Progression Rule object loads only the association between the eligibility prole and the progression grade
ladder, grade, or grade step. Multiple progression rules can exist at each level.
Eligibility proles associated with Progression Rule objects:
• Must have a usage of Compensation or Global

• Can't be referenced from the Progression Rule object using source keys
Examples of Loading Progression Rules

This topic provides examples showing how to load Progression Rule objects using HCM Data Loader.
Creating Progression Rules

Typically, you load progression rules for either each step of the progression grade ladder or each grade if your grades
don't have steps. These examples show how to load progression rules for the progression grade ladder, grade, and
grade step. They include the aributes necessary to build the keys at each level. These rules apply to this approach:
• When loading a rule for the progression grade ladder, set the SetCode, GradeId, and GradeStepId or
GradeStepName aributes to #NULL.
• When loading a rule for a particular grade, set the GradeStepId or GradeStepName aribute to #NULL.
• When loading a rule for a step, supply values for all aributes.
• If your grades don't have steps, then remove the GradeStepId or GradeStepName aribute from your le.
Alternatively, you can load the progression rules for each level separately. In this case, you include only the necessary
key aributes. For example, when loading progression rules for only the progression grade ladder, you remove the
SetCode, GradeId, and GradeStepId or GradeStepName aributes. Similarly, when loading progression rules for only
the grades, you remove the GradeStepId or GradeStepName aribute.
This example ProgressionRule.dat le creates progression rules at each level using source keys. Existing eligibility
proles dene the criteria for progression.
Note: You can't reference the eligibility proles using source keys.
METADATA|ProgressionRule|SourceSystemOwner|SourceSystemId|EffectiveStartDate|GradeLadderId(SourceSystemId)|
SetCode|GradeId(SourceSystemId)|GradeStepId(SourceSystemId)|ProgressionRuleName
COMMENT Rule for Progression Grade Ladder
MERGE|ProgressionRule|VISION|GSP_ANALYSTS_PGL_RULE1|2000/02/15|GSP_ANALYSTS_PGL|#NULL|#NULL|#NULL|Active
Employees
COMMENT Rule for Grade
MERGE|ProgressionRule|VISION|GSP_ANALYSTS_PGL_RULE_G1_1|2000/02/15|GSP_ANALYSTS_PGL|COMMON|ANALYST1_GR|#NULL|
26 Weeks of Service
COMMENT Rules for Steps
MERGE|ProgressionRule|VISION|GSP_ANALYSTS_PGL_RULE_G1S1_1|2000/02/15|GSP_ANALYSTS_PGL|COMMON|ANALYST1_GR|
ANALYST1_GRS1|Completed Training
MERGE|ProgressionRule|VISION|GSP_ANALYSTS_PGL_RULE_G1S1_2|2000/02/15|GSP_ANALYSTS_PGL|COMMON|ANALYST1_GR|
ANALYST1_GRS1|Completed Training Level 2
This example ProgressionRule.dat le creates progression rules at each level using user keys. Existing eligibility proles
dene the criteria for progression.
178
METADATA|ProgressionRule|GradeLadderName|SetCode|GradeCode|GradeStepName|ProgressionRuleName|
EffectiveStartDate
COMMENT Rule for Progression Grade Ladder
MERGE|ProgressionRule|GSP Nurses|#NULL|#NULL|#NULL|Active Employees|2016/01/01
COMMENT Rules for Grade
MERGE|ProgressionRule|GSP Nurses|COMMON|NURSE_1|#NULL|26 Weeks of Service|2016/01/01
COMMENT Rules for Steps
MERGE|ProgressionRule|GSP Nurses|COMMON|NURSE_1|Step 1|Completed Training|2016/01/01
MERGE|ProgressionRule|GSP Nurses|COMMON|NURSE_1|Step 1|Completed Training Level 2|2016/01/01
Deleting Progression Rules

You can delete a progression rule record using HCM Data Loader. Deleting a progression rule doesn't delete the
associated eligibility proles.
This example ProgressionRule.dat le deletes three progression rules. It references the progression rules using source
keys.
METADATA|ProgressionRule|SourceSystemOwner|SourceSystemId
COMMENT Delete Rule for Progression Grade Ladder
DELETE|ProgressionRule|VISION|GSP_ANALYSTS_PGL_RULE1
COMMENT Delete Rule for Grade
DELETE|ProgressionRule|VISION|GSP_ANALYSTS_PGL_RULE_G1_1
COMMENT Delete Rule for Step
DELETE|ProgressionRule|VISION|GSP_ANALYSTS_PGL_RULE_G1S1_1
This example ProgressionRule.dat le also deletes three progression rules. It references the progression rules using user
keys. These rules apply when you delete rules at all levels in a single ProgressionRule.dat le:
• When deleting a rule for the progression grade ladder, set the SetCode, GradeCode, and GradeStepName
aributes to #NULL.
• When deleting a rule for a grade, set the GradeStepName aribute to #NULL.
• When deleting a rule for a step, supply values for all aributes.
• If your grades don't have steps, then remove the GradeStepName aribute from your le.
METADATA|ProgressionRule|GradeLadderName|SetCode|GradeCode|GradeStepName|ProgressionRuleName
COMMENT Delete Rule for Ladder
DELETE|ProgressionRule|GSP Nurses|#NULL|#NULL|#NULL|Active Employees
COMMENT Delete Rule for Grade
DELETE|ProgressionRule|GSP Nurses|COMMON|NURSE_1|#NULL|26 Weeks of Service
COMMENT Delete Rule for Step
DELETE|ProgressionRule|GSP Nurses|COMMON|NURSE_1|Step 1|Completed Training
Guidelines for Loading Salary Basis Records

This topic describes aspects of the Salary Basis object that you must understand to load salaries and salary bases
179
Payroll Elements
Elements that you link to salary bases must exist in the target environment before you load salary bases. In addition,
you must create those elements as recurring elements:
• In the same legislative data group as the salary basis
• With a primary classication of either Standard Earnings or Information
• With open eligibility, meaning that no eligibility criteria are dened at the element level
To link the same payroll element to multiple salary bases, you must congure the element to support multiple entries in
the same period.
If any of these conditions for payroll elements isn't met, then your salary bases may not load successfully. For example,
they may not be associated with a legislative data group or linked with a payroll element. In this case, you correct the
salary bases manually in the application. For more information about creating payroll elements, see Conguring Payroll
Elements for Use in Oracle Fusion Compensation (1589502.1) on My Oracle Support at hps://support.oracle.com.
Grade Rates
You can link a grade rate to a salary basis to validate worker salaries against the salary ranges dened for the grade.
These rules apply:
• The worker's grade must be included in the grade rate linked to the worker's salary basis.
• The grade rate currency must match the currency of the payroll element linked to the salary basis.
• The grade rate must be dened in the same legislative data group as the salary basis.
Salary Basis Code

The SalaryBasisCode aribute records the frequency at which base pay is stored and displayed. Valid values
are dened in the CMP_SALARY_BASIS lookup type. The value PERIOD (payroll period) means that the salary
frequency comes from the payroll dened at the payroll-terms level. When Salary Basis Code is PERIOD, leave the
SalaryAnnualizationFactor aribute blank.
Salary Basis Components

Use the ComponentUsage aribute of the Salary Basis object to specify whether you're loading salary basis
components, which itemize salary adjustments. Valid values are dened in the CMP_COMPONENT_USAGE lookup type
and shown in this table.
Value Meaning
NO_COMPONENT Components aren't used and aren't loaded with the Salary Basis object.

SELECTED_ COMPONENTS Components are used and are loaded with the Salary Basis object.

USER_ DECIDES_USAGE Managers select the components to use when adjusting salary. Components aren't loaded with
the Salary Basis object.

180
If you set the ComponentUsage aribute to SELECTED_COMPONENTS, then you load the components using the
SalaryBasisComponent discriminator. If you omit the ComponentUsage aribute, then NO_COMPONENT is assumed.
Tip: If you're unsure about component usage, then specify USER_DECIDES_USAGE. This value is the least
restrictive.
Provide one Salary Basis Component record for each component type. The AributeValue aribute of the Salary Basis
Component record identies the component type, such as PROMOTIONAL, COST_OF_LIVING, or ADJUSTMENT. This
value is validated against the CMP_SALARY_COMPONENTS lookup type.
Deletion of Salary Basis Records

You can delete a Salary Basis object using HCM Data Loader only if it's unassigned and hasn't been used to create salary
records. You can delete individual Salary Basis objects most easily in the application.
Related Topics
• Conguring Payroll Elements for Use in Oracle Fusion Compensation (1589502.1)
Guidelines for Loading Salary Records

A salary record holds a worker's base pay amount for a specied period and currency. It also displays the salary range
used to validate base pay and calculate metrics such as compa-ratio and quartile. Depending on how the associated
salary basis is congured, salary can include zero or more components. This topic describes aspects of the Salary object
that you must understand to load salary records successfully using HCM Data Loader.
Before You Load Salary Records

You must make sure of these conguration conditions before you can load Salary objects:
• Employment records must exist in the target environment.

• Worker assignments must include a grade, and the grade must be included in the grade rate that's linked to
each worker's salary basis. These requirements must be met for salary range to appear and salary metrics to be
calculated correctly on the salary record.
Workers whose salary basis has a frequency of PERIOD must be assigned to a payroll dened at the payroll terms level.
This payroll assignment must be complete before you load salary records.
Load Salary
Supply salary data in the Salary.dat le for processing by HCM Data Loader. If you're loading salary components:
• Set the MultipleComponents aribute of the Salary object to Y. Otherwise, set it to N.

• Set the SalaryAmount aribute of the Salary object to the base salary amount plus the sum of any salary
components.
For terminated assignments, set the Salary object Date To aribute only when the salary to date is earlier than
the assignment end date. Otherwise, the salary end date is set to the assignment end date, and not the date in the
associated element.
181
Set the ActionCode aribute of the Salary object to the action associated with the salary record. This table shows valid
values for the ActionCode aribute.
Action Code Action Name
ALLOCATE_ GRP_CMP Allocate Workforce Compensation

CHANGE_SALARY Change Salary

GLB_TRANSFER Global Transfer

HIRE Hire an Employee

HIRE_ ADD_ WORK_RELATION Add Employee Work Relationship

PROMOTION Promotion

REHIRE Rehire of Worker

TRANSFER Transfer

You can create salary at the assignment level, supply a unique reference to the assignment. Grade and FTE are obtained
from each assignment.
FTE is determined by comparing the standard working hours of the worker's legal employer with the working hours on
the worker's assignment. When a Standard Earnings payroll element is aached to the worker's salary basis, the annual
amount sent in the element entry is adjusted for FTE. Otherwise, the amount sent in the element entry isn't adjusted for
FTE.
Loading Salary Components

Set the ComponentReasonCode aribute. Valid values are dened in the CMP_SALARY_COMPONENTS lookup type.
Use the Manage Base Pay Lookups task in the Setup and Maintenance work area to manage the lookup type. Each
component reason code can be used once only for each salary record.
Specify either a ChangeAmount or a ChangePercentage aribute value for each component record. Don't specify
both. You add the ChangeAmount value to the base pay amount to derive the new salary amount for the salary
record. The ChangePercentage value is a percentage of the base pay amount. The corresponding percentage value is
calculated automatically.
Updating Existing Salary Records

When you update an open-ended salary, the existing salary is automatically end-dated on the day prior to the from date
aribute value supplied for the new salary.
182
Examples of Loading Salary Records

This topic shows how to load and manage salary records for a worker assignment using HCM Data Loader.
Creating a Salary Using Source Keys

This example Salary.dat le creates a Salary object with components against an existing assignment. Source keys are
used to identify both the Salary object and the associated assignment.
METADATA|Salary|SourceSystemOwner|SourceSystemId|AssignmentId(SourceSystemId)|DateFrom|SalaryAmount|
SalaryBasisName|ActionCode|SalaryApproved|MultipleComponents
MERGE|Salary|VISION|1012SAL15|1012_EMP_ASG|2015/01/01|65000|SalBasis_1007|CHANGE_SALARY|Y|N
METADATA|SalaryComponent|SourceSystemOwner|SourceSystemId|SalaryId(SourceSystemId)|DateFrom|
ComponentReasonCode|ChangeAmount|ComponentApproved
MERGE|SalaryComponent|VISION|1012SAL15_COL|1012SAL15|2015/01/01|COST_OF_LIVING|60000|Y
MERGE|SalaryComponent|VISION|1012SAL15_ADJ|1012SAL15|2015/01/01|ADJUSTMENT|5000|Y
Updating a Salary Using Source Keys

This example Salary.dat le updates an existing, open-ended salary record by supplying changes to the Salary object
and its components. Source keys are used to identify all components of the Salary object.
METADATA|Salary|SourceSystemOwner|SourceSystemId|AssignmentId(SourceSystemId)|DateFrom|DateTo|SalaryAmount|
SalaryBasisName|ActionCode|SalaryApproved|MultipleComponents
MERGE|Salary|VISION|1012SAL16|1012_EMP_ASG|2016/01/01||70000|SalBasis_1007|CHANGE_SALARY|Y|N
METADATA|SalaryComponent|SourceSystemOwner|SourceSystemId|SalaryId(SourceSystemId)|DateFrom|
ComponentReasonCode|ChangeAmount|ComponentApproved
MERGE|SalaryComponent|VISION|1012SAL16_COL|1012SAL16|2016/01/01|COST_OF_LIVING|5000|Y
MERGE|SalaryComponent|VISION|1012SAL16_ADJ|1012SAL16|2016/01/01|ADJUSTMENT|0|Y
Creating a Salary Using User Keys

This example Salary.dat le creates a Salary object with components against an assignment. User keys are used to
identify both the Salary object and the associated assignment.
METADATA|Salary|AssignmentNumber|DateFrom|SalaryAmount|SalaryBasisName|ActionCode|SalaryApproved|
MultipleComponents
MERGE|Salary|1014|2015/01/01|53500|SalBasis_1007|CHANGE_SALARY|Y|N
METADATA|SalaryComponent|AssignmentNumber|DateFrom|ComponentReasonCode|ChangeAmount|ComponentApproved
MERGE|SalaryComponent|1014|2015/01/01|COST_OF_LIVING|52000|Y
MERGE|SalaryComponent|1014|2015/01/01|ADJUSTMENT|1500|Y
183
Updating a Salary Using User Keys

This example Salary.dat le updates an existing, open-ended salary record by supplying changes to the Salary object
and its components. User keys are used to identify all components of the Salary object.
METADATA|Salary|AssignmentNumber|DateFrom|DateTo|SalaryAmount|SalaryBasisName|ActionCode|SalaryApproved|
MultipleComponents
MERGE|Salary|1014|2016/01/01||53900|SalBasis_1007|CHANGE_SALARY|Y|N
METADATA|SalaryComponent|AssignmentNumber|DateFrom|ComponentReasonCode|ChangeAmount|ComponentApproved
MERGE|SalaryComponent|1014|2016/01/01|COST_OF_LIVING|300|Y
MERGE|SalaryComponent|1014|2016/01/01|ADJUSTMENT|100|Y
Deleting a Salary
Use HCM Data Loader to delete salary records only if many records were created or loaded incorrectly and must be
deleted in bulk. Unless you're deleting all salary records for an assignment, only the salary record with the latest salary
start date can be deleted. For example, if a salary record has salary start dates of January 1, March 1, and September 1
then you can delete just the September 1 record. Alternatively, you can delete all three records.
This example Salary.dat le deletes an existing salary record. The Salary object is identied by its source key.
METADATA|Salary|SourceSystemOwner|SourceSystemId|AssignmentId(SourceSystemId)|DateFrom
DELETE|Salary|VISION|1012SAL16|EJ1012_EMP_ASG|2016/01/01
This example Salary.dat le deletes an existing salary. The Salary object is identied by its user key.
METADATA|Salary|AssignmentNumber|DateFrom
DELETE|Salary|1014|2016/01/01
Examples of Loading Salary Range Dierential Proles

and Values
Salary range dierential values are multipliers applied to grade rates to adjust them on the basis of worker location. For
example, a dierential value of 1.2 could be applied in one location while a dierential value of 0.80 could be applied
in another. These values vary to reect the cost of living in these locations or the relative ease of hiring, for example.
Salary range dierential values are associated with a salary range dierential prole, which you link to the salary basis.
This topic provides examples showing how to load dierential proles and their dierential values using HCM Data
Loader.
Creating Salary Range Dierential Proles and Values

To create a dierential prole, you load the Salary Range Dierential object and one or more Salary Range Dierential
Value components. Each Salary Range Dierential Value component is for a single location. Dierential proles
reference legislative data groups, and their dierential values reference locations. Referenced legislative data groups
and locations must exist in the target environment before you load Salary Range Dierential objects.
184
This example SalaryRangeDierential.dat le creates a dierential prole with a single dierential value. Both
components are identied using source keys.
METADATA|SalaryRangeDifferential|EffectiveStartDate|Name|Code|Status|Criteria|SourceSystemId|
SourceSystemOwner|LegislativeDataGroupName
MERGE|SalaryRangeDifferential|2000/01/01|SalRangeDiffName333|SalRangeDiffCode333|ACTIVE|LOCATION|
SalRangeDiffSSID_333|VISION|PM DE LDG
METADATA|SalaryRangeDifferentialValue|EffectiveStartDate|SourceSystemId|SourceSystemOwner|
RangeDiffId(SourceSystemId)|LocationCode|LocationSetCode|Differential
MERGE|SalaryRangeDifferentialValue|2000/01/01|SalRangeDiffVal_SSID_333|VISION|SalRangeDiffSSID_333|Atlanta|
Vision Corporation 202|0.2
This example SalaryRangeDierential.dat le creates a dierential prole with a single dierential value. Both
components are identied using user keys.
METADATA|SalaryRangeDifferential|EffectiveStartDate|Name|Code|Status|Criteria|LegislativeDataGroupName
MERGE|SalaryRangeDifferential|2000/01/01|SalRangeDiffName444|SalRangeDiffCode444|ACTIVE|LOCATION|PM DE LDG
METADATA|SalaryRangeDifferentialValue|EffectiveStartDate|RangeDiffCode|LocationCode|LocationSetCode|
Differential
MERGE|SalaryRangeDifferentialValue|2000/01/01|SalRangeDiffCode444|Atlanta|Vision Corporation 202|0.2
Guidelines for Making Date-Eective Changes to Salary

Range Dierentials
The Salary Range Dierential object is date-eective. That is, a history of changes to the Salary Range Dierential object
and its child components is maintained and can be viewed. For example, users can see the date-eective history of a
dierential prole in the Compensation work area. This topic describes how date-eective records are managed for
Salary Range Dierential objects when you use HCM Data Loader.
Creating Date-Eective Records

When you create or update a dierential value, a date-eective record is added to the dierential value. A date-eective
record must also be added to the parent dierential prole if it has no date-eective record for that eective start date.
In this case, you must include the parent Salary Range Dierential component in the .dat le. It must have the same
eective start date as the child dierential value.
This table shows a history of changes to a dierential prole.
RangeDiId EectiveStartDate
EectiveEndDateStatus Criteria LegislativeDataGroupId
Code Name
123 01-01-1951 01-05-2016 Active Location US1 US SRD US Range

123 02-05-2016 31-12-4712 Active Location US1 US SRD US Range

This table shows the related changes to its dierential values.
185
RangeDiValueId EectiveStartDate EectiveEndDate Dierential LocationId
234 01-01-1951 31-12-4712 1.3 A

345 02-05-2016 31-12-4712 0.8 B

456 02-05-2016 31-12-4712 0.9 C

When the location B value was created, a date-eective record with the location B eective start date was also added
to the dierential prole. However, when the location C value was created, no date-eective record was added to the
dierential prole. A record for that eective start date already existed in the dierential prole, so no additional record
was needed. If you create or update multiple dierential values on the same date, then only one date-eective record is
added to the parent dierential prole.
Note: You don't have to include the parent Salary Range Dierential component in the .dat le if it already
has a date-eective record with the required eective start date.
Editing the Salary Range Dierential Component

If you correct or update the parent Salary Range Dierential object, then no date-eective record is added to its child
components. For example, if you make the dierential prole inactive, then a new date-eective record is added to the
parent component. However, no date-eective record is added to the dierential values.
186
Integrating with HCM Loading Payroll Relationships
13 Loading Payroll Relationships
Payroll Information
Overview of Loading Payroll Details
Use HCM Data Loader to load payroll information at the payroll relationship, payroll assignment records, and assigned
payroll levels. For example, you can update the overtime period for employees either at their payroll relationship or
assignment level.
A time period you specify at a lower level, such as assignment level, overrides a period at a higher level, such as payroll
relationship.
This gure shows the payroll information for a person at the Payroll Relationship, Assignment, and Assigned Payroll
levels.
Person
LE Vision US LE Vision Canada

Payroll
Employee Employee Relationship
Project Manager Trainer Trainer Assignment
Assigned
Weekly Monthly Weekly
Payroll
Consider these examples that explain the various actions you can take using HCM Data Loader.
• You manage Carrie Smith who's a part-time temporary employee and is on weekly payroll. Starting one month
from now, Carrie accepted an oer to become a full-time permanent employee in the same position. You
can update Carrie's assignment record and transfer her to a payroll appropriate for a full-time permanent
employee, such as monthly or semimonthly.
187
• Anthony has two assignment records, one on a weekly payroll and one on a monthly payroll. On 10-Jun-18,
you terminated Anthony's assignment record on the weekly payroll. The termination process automatically set
the last standard process date to the end date of the payroll period. Anthony's termination package species
that he should receive compensation payments through the month of June. To ensure that he's paid on both
weekly and monthly payroll through June, you change the LSPD on weekly payroll to 30-Jun-18.
• You wrongly assigned Sophie, who's a new hire, to weekly payroll instead of monthly payroll. Now, you can
delete her weekly payroll record and add the monthly payroll record.
Related Topics
• Overview of Payroll Relationships
Overview of Loading Payroll Relationship Details

Use HCM Data Loader to update payroll details for employees at the payroll relationship level. Payroll relationships
group a person's employment assignment records based on the payroll statutory calculation and reporting
requirements. For example, you can update the overtime period for employees at their payroll relationship.
When an employee is hired, the application automatically creates the payroll relationship details. A person could have
multiple payroll relationships if they're associated with more than one PSU or more than one payroll relationship type.
Element Duration Dates

The element duration dates at the payroll relationship level control the start and end date of earnings and deductions
assigned to the employee's payroll relationship. Examples of payroll relationship elements include tax and social
insurance entries.
See this table for various element duration dates.
Date Description
First Standard Earnings Date The date when standard earnings start accumulating. For example, the start date of the
employee's record for the payroll statutory unit.

Last Standard Earnings Date The date when standard earnings stop accumulating. For example, the termination date of the
employee's record for the payroll statutory unit.

Last Standard Process Date The last date of the payroll period in which the termination of the payroll relationship occurs.

Final Close Date The last date the payroll run will include elements (which are set to use nal close) for
processing. This includes regular and supplemental payroll runs

You can't edit these element duration dates at the payroll relationship level. These dates are populated based on the
date information at the assignment level.
For example, when Joe is terminated on 1-Mar-19, the application sets the last standard earnings date on his
assignment record with this date.
188
As the gure shows, the same date cascades up to the last standard earnings date eld at the payroll relationship level.
Joe
Termination Date
1-Mar-19
Payroll Relationship Level
LSED=1-Mar
Cascades up
Assignment Level
LSED=1-Mar
Assigned Payroll
Example of Loading Assigned Payroll Details
Use HCM Data Loader to assign a payroll to an assignment. Though you can specify the Time card Required and
Overtime Status details at the assigned payroll level, consider dening them for an assignment.
For example, an employee is assigned to the weekly payroll and at the assigned payroll level, you load the overtime
period code. If the employee transfers to the monthly payroll, the overtime period will no longer apply. In this case, you
must dene the overtime period at the assignment level.
Use HCM Data Loader to manage all payrolls for an assignment and for a given payroll relationship.
For example, in this DAT le, you assign a weekly payroll to an employee.
METADATA|AssignedPayroll|EffectiveStartDate|AssignmentNumber|PayrollDefinitionCode|LegislativeDataGroupName|
StartDate
MERGE|AssignedPayroll|2019/03/01|E10001|Weekly Payroll|Vision US LDG|2019/03/01
Related Topics
• Element Duration Dates
189
Example of Loading Element Duration Dates for Assigned Payroll

The element duration dates at assigned payroll level control when the assignment will be processed in a specic payroll
run.
Let's consider this example.
John is on a monthly payroll, but starting 20-Feb-18, he's transferred to a semi-monthly payroll. His monthly and semi-
monthly payroll denitions looks like this. You can update the nal close date as 31-Jul-18.
Time Denition Monthly Payroll Semi-Monthly Payroll
First Standard Earnings Date 01/01/18 02/20/2018

Last Standard Earnings Date 02/19/2018

Last Standard Process Date 02/28/2018

Final Close 07/31/2018

190
This image shows the various time denition dates for monthly and semi-monthly payroll.
19-Feb 28-Feb 31-Jul

1-Jan
20-Feb
Semi- Monthly
John
Monthly Transfer
LSED = 19-Feb
Application FSED = 20-Feb
LSPD = 28-Feb
FC = 31-Jul
Payroll Manager
Use this dat le to set the nal close date as 31-Jul-18.
METADATA|AssignedPayroll|EffectiveStartDate|FinalCloseDate|LegislativeDataGroupName|PayrollDefinitionCode|
AssignmentNumber|StartDate
MERGE|AssignedPayroll|2018/01/01|2018/07/31 00:00:00|Vision US LDG|Monthly Payroll|E10003|2018/01/01
Related Topics
• Element Duration Dates
Payroll Assignments
Example of Loading Element Duration Dates For Payroll
Assignments
Use HCM Data Loader to load payroll related information for an assignment, such as element duration dates. The
element duration dates at assignment level control the start and end date of earnings and deductions assigned to the
employee's assignment, such as salary.
191
Example
On 13-Feb-2019, Maria Peterson who's on weekly payroll terminates her service with your company. The termination
process automatically sets these process dates:
• The last standard earnings date to 13-Feb-19.
• The last standard process date to the end date of her weekly payroll, which is 15-Feb-19.
However, Maria is still eligible to receive outstanding overtime and commission payments, which can be paid up to 6
months in arrears. To ensure that she's paid these payments, you can update the nal close date on the assignment
record to 31-Dec-19.
As this image shows, the termination process sets the process dates for Maria.
Termination Date Maria is eligible to

receive payments
13-Feb
15-Feb 31-Dec
LSED = 13-Feb
Termination
process LSPD = 15-Feb
FC=31-Dec
Payroll
Manager
In this dat le, you update the nal close date to 31-Dec-2019.
METADATA|ElementDurationDate|DateValue|SourceType|AssignmentNumber|TimeDefinitionCode
MERGE|ElementDurationDate|2019/12/31|PA|E10001|Final Close
Update the Time Card Required Option for Assignments

You can use the Time Card Required option to indicate if the assignment is paid by time card or not. At the assignment
level, the time card status applies to the specic assignment record.
Let's consider this example. Tina is on a temporary contract. She submits her time cards every week and receives her
pay checks on a weekly basis. Eective 15-July, the company oers her a permanent contract. Under the new contract,
192
she will become a salaried employee and will be paid on a monthly basis. And she will no longer need to submit the time
card.
1-Mar
Tina
Update the Time Card
Status attribute to No
Oracle HCM Cloud
Temporary Contract Permanent Contract
Time Card = Yes Time Card = No
Use this dat le to set the Time Card Required parameter to No.
METADATA|PayrollAssignmentDetails|EffectiveStartDate|TimecardRequiredFlag|AssignmentNumber
MERGE|PayrollAssignmentDetails|2019/07/15|N|E10002
Update the Last Standard Process Date for Assignments

You can sequence the loading of the element duration dates depending on whether you move the element duration
dates forward or backward.
This table describes the various actions involved in updating the last standard process date.
Action What You Do Example
Move the element duration dates forward. Load the nal close date rst. You update the nal close date from
15-Mar to 15-May and the last standard
process date from 15-Feb to 15-Apr.

Move the element duration dates Load the last standard process date rst. You update the last standard process date
backward. from 15-APR to 15-FEB and the nal close
date from 15-May to 15-Mar.

Let's consider this scenario where you hire an employee on 1-Jan-15 and create their Tax withholding calculation card.
You terminate the employee on 15-Jan-16. Further, you update the nal close date as 15-Mar-16 and the last standard
process date as 15-Feb-16 at the assignment level. At a later point in time, you update the LSPD as 15-Apr-16 and FC as
15-May-16.
193
You must use these two DAT les to load the LSPD and FC date values separately.
MERGE|ElementDurationDate|2016/05/15|PA|E10001|Final Close
MERGE|ElementDurationDate|2016/04/15|PA|E10001|Last Standard Process Date
194
Integrating with HCM Loading Payroll Setup Objects
14 Loading Payroll Setup Objects
Examples of Loading Legislative Data Groups

Legislative data groups are used to partition payroll and related data. At least one legislative data group is required
for each country where the enterprise operates. Each legislative data group holds a legislation code, currency, and
cost allocation key exeld. It's also associated with one or more payroll statutory units. This topic provides examples
showing how to load and manage Legislative Data Group objects using HCM Data Loader.
Creating Legislative Data Groups

This example LegislativeDataGroup.dat le creates a legislative data group for the United Kingdom. It identies the
legislative data group using its source key. Codes are supplied for the currency and legislation.
METADATA|LegislativeDataGroup|SourceSystemOwner|SourceSystemId|Name|LegislationCode|DefaultCurrencyCode
MERGE|LegislativeDataGroup|VISION|LDG_VI_UK|Vision UK|GB|GBP
This example LegislativeDataGroup.dat le creates a legislative data group for the United States and associates it with a
cost allocation key exeld.
METADATA|LegislativeDataGroup|Name|Territory|DefaultCurrency|StructureInstanceName
MERGE|LegislativeDataGroup|Vision US|United States|US Dollar|System Test Costing
Deleting Legislative Data Groups

You can delete Legislative Data Group objects using HCM Data Loader. This example LegislativeDataGroup.dat le
deletes a legislative data group. It identies the legislative data group by its source key.
METADATA|LegislativeDataGroup|SourceSystemOwner|SourceSystemId
DELETE|LegislativeDataGroup|VISION|LDG_VI_UK
Object Groups
Overview
Use HCM Data Loader to dene object groups that dene subsets of people or elements for processing or reporting.
Dene one of these object groups.
• Element Group
• Payroll Relationship Group
• Process Information Group
195
Element Group
An element group denes a group of individual elements for processing payroll runs or reports. Element groups are
static, which means you select each element manually to include in a group.
Let's consider this example. In an o-cycle payroll run, you want to make expense payments that aren't subject to tax
and other deductions. You create an element group for all expense elements. And you submit a payroll run with this
element group as the parameter.
Use this .dat le to create an element group for all your required expenses.
METADATA|ObjectGroup|LegislativeDataGroupName|ObjectGroupCode|ObjectGroupName|ObjectGroupTypeCode|StartDate|
EndDate|StaticDynamicFlag|Description
MERGE|ObjectGroup|US LDG|VIS_EXP_GROUP|EXPENSE_ELEMENT_GRP|ELEGRP|2010/01/01||N|Expense elements group for
off-cycle payments.
METADATA|ObjectGroupAmend|LegislativeDataGroupName|ObjectGroupCode|ObjectGroupLevelName|ObjectCode|
IncludeOrExclude
MERGE|ObjectGroupAmend|US LDG|VIS_EXP_GROUP|Element|Travel_Allowance|I
MERGE|ObjectGroupAmend|US LDG|VIS_EXP_GROUP|Element|Per_Diem|I
Payroll Relationship Group

Use a payroll relationship group to limit the persons that you want to process for payroll, data entry, and reporting.
You can dene your payroll relationship group to be either static or dynamic. In a dynamic group, you select a formula
that determines the people to include in the group. You can use either the Payroll Relationship Number or Assignment
Number or both to create the group.
In this example, Vision Corporation wants to pay bonus to a group of 25 employees in an o-cycle payroll run. Here,
you create a payroll relationship group for these employees. When submiing the payroll run, you select the payroll
relationship group as the parameter.
Use this .dat le to create a payroll relationship group.

METADATA|ObjectGroup|LegislativeDataGroupName|ObjectGroupCode|ObjectGroupName|ObjectGroupTypeCode|StartDate|
EndDate|StaticDynamicFlag|Description
MERGE|ObjectGroup|US LDG|VIS_BONUS0919|Vision Bonus Group|PAYEMP|2019/09/01|2019/10/31|N|Employees who will
get paid the bonus in Sept. 2019.
METADATA|ObjectGroupAmend|LegislativeDataGroupName|ObjectGroupCode|ObjectGroupLevelName|ObjectCode|
IncludeOrExclude
MERGE|ObjectGroupAmend|US LDG|VIS_BONUS0919|Payroll Relationship|8186051|I
Related Topics
• Object Group HCM Data Loader Files for Bank Reprocessing
Example of Loading Object Groups

Rahul has an invalid branch number due to the closure of the bank. And you want to update his bank account details. In
this case, you don't end date the personal payment method, but update the existing personal payment method with the
correct bank details.
To update Rahul's branch number, you do these tasks as shown in the gure.
1. Using HCM Data Loader, load the details returned by the bank.
196
2. Submit the Process Bank Corrections File ow to update his personal payment method.
Load the Bank Account Details

The bank returns a le containing details of the payments that are rejected. To process this bank information, use
these .dat les.
1. ObjectGroup.dat le to create the object group.
METADATA|ObjectGroup|SourceSystemOwner|SourceSystemId|LegislativeDataGroupName|ObjectGroupCode|
ObjectGroupName|ObjectGroupTypeCode|Description|StartDate|EndDate|FormulaName
MERGE|ObjectGroup|VISION|PPM_E8185311|US LDG|PPM_E8185311|PPM Update for 8185311|PROCINFO|PPM update for
employee 8185311|2019/10/01||
2. ObjectGroupStore.dat le to load the bank information returned by the bank
METADATA|ObjectGroupStore|SourceSystemOwner|SourceSystemId|LegislativeDataGroupName|
ObjectGroupId(SourceSystemId)|SequenceNumber|FLEX:PAY_OBJECT_GROUP_STORE_DDF|
amount(PAY_OBJECT_GROUP_STORE_DDF=ORA_PAY_BANK_CORRECTION)|
assignmentNumber(PAY_OBJECT_GROUP_STORE_DDF=ORA_PAY_BANK_CORRECTION)|
checkNumber(PAY_OBJECT_GROUP_STORE_DDF=ORA_PAY_BANK_CORRECTION)|
makeExternalPayment(PAY_OBJECT_GROUP_STORE_DDF=ORA_PAY_BANK_CORRECTION)|
paymentDate(PAY_OBJECT_GROUP_STORE_DDF=ORA_PAY_BANK_CORRECTION)|
paymentReference(PAY_OBJECT_GROUP_STORE_DDF=ORA_PAY_BANK_CORRECTION)|
processDate(PAY_OBJECT_GROUP_STORE_DDF=ORA_PAY_BANK_CORRECTION)|
replacementAccountType(PAY_OBJECT_GROUP_STORE_DDF=ORA_PAY_BANK_CORRECTION)|
replacementBranchNumber(PAY_OBJECT_GROUP_STORE_DDF=ORA_PAY_BANK_CORRECTION)|
returnreasoncode(PAY_OBJECT_GROUP_STORE_DDF=ORA_PAY_BANK_CORRECTION)|
employeeName(PAY_OBJECT_GROUP_STORE_DDF=ORA_PAY_BANK_CORRECTION)|
replacementAccountNumber(PAY_OBJECT_GROUP_STORE_DDF=ORA_PAY_BANK_CORRECTION)
MERGE|ObjectGroupStore|VISION|E8185311_BANK_CORRECTION|US LDG|PPM_E8185311|1|ORA_PAY_BANK_CORRECTION|
5000|E8185311|222324|YES|2019/10/31 00:00:00|185805|2019/10/31 00:00:00|Checking|004|AccountType Chg|
Rahul|00456754231
Submit the Process Bank Corrections File

From the Payroll Checklist work area, submit the Process Bank Corrections File ow. When you load the
ObjectGroupStore.dat le into the Oracle Web Center Content server, a UCM ID is generated. The Process Bank
197
Corrections File ow uses the UCM ID to retrieve and use the bank information necessary for the ow. The ow
updates the Personal Payment Method with the new branch number details.
Related Topics
• Object Group HCM Data Loader Files for Bank Reprocessing
Example of Loading Payroll Consolidation Group

A payroll consolidation group is a grouping of payroll runs within the same time period for the same payroll. For this
group, you can run reporting, costing, and post-run processing. For example, a group might consolidate payroll runs for
dierent work sites into one group for payments and costing.
Supply comments in a separate text le and then pass the text le name to the Comments aribute. Further, place the
comments text le in the ClobFiles folder within the same compressed le as the PayrollConsolidationGroup.dat le
that references it.
Note: Don't supply the text directly in the PayrollConsolidationGroup.dat le.
Use this example dat le to load payroll consolidation groups:

METADATA|PayrollConsolidationGroup|SourceSystemOwner|SourceSystemId|LegislativeDataGroupId(SourceSystemId)|
ConsolidationSetName|Comments
MERGE|PayrollConsolidationGroup|VISION|INFUSION_US_EMP|HDL_LDG_VISION_US|InFusion US Employee Group|
Consolidation group description
Related Topics
• How Pay Frequency Components Work Together
• Consolidation Groups
Payroll Denitions and Time Periods

Payroll Denitions and Time Periods: Overview
Payroll denitions contain calendar and oset information that determine when to calculate and cost payments. It
includes denition of payment frequency, processing schedule, and other parameters for a particular payroll.
For example, to pay employees semimonthly, you can create a payroll denition using the semimonthly payroll period
type, ensuring that tax and other calculations produce correct results for those employees.
You can't change either the rst eective start date or last eective end date for an existing payroll denition. Create
payroll denition objects with eective start dates on or before the start dates of other objects that refer to your
denitions.
Payroll Oset
Payroll osets help you dene your payroll cycle schedule. You can select for your payroll cycle events to occur on
specic dates or be based on osets from period start or end dates. Based on your choices and the number of calendar
years you specify, the complete calendar for your payroll's lifetime is generated.
198
This table describes the predened payroll cycle events that you can oset.
Date Description
Planned Submission Date The date on which the user will submit the payroll run.

Cuto Date The nal date that payroll information can be entered for the payroll period.

Payslip Availability Date The date on which payees can view payslips.

Payroll Run Date The date the payroll calculation process uses to retrieve eective values, such as employee
details.

Date Earned The date on which the payroll process processes element entries for the payroll run. The date
earned must be within the eective dates of the payroll period.

Date Paid The date the employee is marked as paid. For check payments, this is the date that the check is
valid for cash or deposit. For electronic funds transfer (EFT) payments, it's the transfer date.

Valid Payment Methods

You can specify an eective date that determines when your organization payment method will be used for this payroll
denition. This date range must t within both the eective date range of the payroll denition and the eective date
range of the organization payment method.
Payroll Time Periods

Payroll Time periods represent the various dates within each payroll cycle and their frequency. Payroll time periods hold
the payroll denition calendar that's based on the frequency of the payroll, such as weekly and monthly. For example,
you can adjust payroll days to account for a bank holiday.
Related Topics
• Payroll Denitions
• Overview of Payroll Denitions
• Create Payroll Denitions
Examples of Loading Payroll Denitions and Time Periods

In this example, the Vision Corp Company requires payroll denitions for two sets of employees. One set is permanent
salaried employees who are paid on a semimonthly basis, and the other is temporary employees that are paid on a
monthly basis using time card data.
199
Note: The Company hires all employees after the eective start date of this payroll denition, so there is no issue with
loading historical employee data.
Prerequisites
Organization Payment
Consolidation Group
Method
Payroll Denitions
Step in the process
Semi Monthly Monthly
Payroll Process Run Type
Before using the HCM Data Loader to create payroll denitions, ensure that you load the following objects:
• Organization Payment Methods for your payrolls. For more information about loading default payment
methods, refer to the topic: Loading Organization Payment Methods: Explained.
• Consolidation group that processes the results of one or more payroll runs in a single action. For more
information about loading consolidation groups, refer to the topic: Loading Payroll Consolidation Group:
Explained.
This example does these actions:

• Loads the payroll denition that pays employees into their bank accounts on a semimonthly basis.
• Includes dynamically generated oset dates.
• Identies the default payment method for those employees who haven't chosen a personal payment method.
• Adjusts payroll days.
METADATA|PayrollDefinition|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|PayrollCode|
LegislativeDataGroupId(SourceSystemId)|ReportingName|ConsolidationGroupCode|PeriodTypeCode|FirstPeriodEndDate|
DefaultPaymentMethodId(SourceSystemId)|NumberOfYears|CutoffFalls|CutoffDayType|CutoffOffset|CutoffBaseDate|
PlannedSubmissionFalls|PlannedSubmissionDayType|PlannedSubmissionOffset|PlannedSubmissionBaseDate|
200
PayrollRunFalls|PayrollRunDayType|PayrollRunOffset|PayrollRunBaseDate|PayslipAvailabilityFalls|
PayslipAvailabilityDayType|PayslipAvailabilityOffset|PayslipAvailabilityBaseDate|DateEarnedFalls|
DateEarnedDayType|DateEarnedOffset|DateEarnedBaseDate|DatePaidFalls|DatePaidDayType|DatePaidOffset|
DatePaidBaseDate
MERGE|PayrollDefinition|VISION|HDL_INFUSION_USEMP_SEMIMONTH|2011/01/01|4712/12/31|
HDL_INFUSION_US_EMP_SEMIMONTHLY|HDL_LDG_VISION_US|InFusion US Employee Semimonthly|InFusion US Employee Group|
Semi-Month|2012/06/15|HDL_INFUSION_US_EMP_EFT|5|5|W|B|E|4|W|B|E|0|W|B|E|0|W|B|E|0|W|B|E|0|W|B|E
Here, you specify the number of years ahead that the payroll cycle dates will be generated as 5. Also, you load the
following osets to your payroll processing schedule. In this example, the payroll cuto date falls 5 days before the date
earned for the payroll period.
Parameter Falls Value Day Type Value Oset Value Base Data Value
Cuto Date 5 W B E

Planned Submission 4 W B E
Date

Payroll Run Date 0 W B E

Payslip Availability 0 W B E
Date

Date Earned 0 W B E

Date Paid 0 W B E

Load the payroll denition that pays employees by check and by using time card data on a monthly calendar basis.
METADATA|PayrollDefinition|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|PayrollCode|
LegislativeDataGroupId(SourceSystemId)|ReportingName|ConsolidationGroupCode|PeriodTypeCode|FirstPeriodEndDate|
DefaultPaymentMethodId(SourceSystemId)|NumberOfYears|FixedDate|CutoffFixedDate|DateEarnedFixedDate|
PayrollRunFixedDate|DatePaidFixedDate|PayslipAvailabilityFixedDate|PlannedSubmissionFixedDate
MERGE|PayrollDefinition|VISION|HDL_INFUSION_USEMP_MONTH|2011/01/01|4712/12/31|HDL_INFUSION_US_EMP_MONTHLY|
HDL_LDG_VISION_US|InFusion US Employee Monthly|InFusion US Employee Group|Calendar Month|2012/06/30|
HDL_INFUSION_US_EMP_CHECK|5|Y|2012/06/25|2012/06/28|2012/06/28|2012/06/28|2012/06/28|2012/06/28 00:00:00
These payroll denition lines load xed dates to dene osets:
Parameter Value
Number of years 5

Set Date Yes

Cuto Date 2012/06/25

201
Parameter Value
Date Earned 2012/06/28

Payroll Run Date 2012/06/28

Date Paid 2012/06/28

Payslip Availability Date 2012/06/28

Planned Submission Date 2012/06/28

Payroll Time Periods

As payroll time periods are generated when the payroll is dened, reference the payroll and time period to adjust using
user keys. This is because the source key is generated by Oracle HCM cloud. The following DAT les explain how to
adjust a time period for these payroll denitions.
METADATA|PayrollTimePeriod|PayrollCode|LegislativeDataGroupName|PeriodCategory|StartDate|PayrollRunDate|
DatePaid
MERGE|PayrollTimePeriod|HDL_INFUSION_US_EMP_SEMIMONTHLY|HDL Vision Clothing Corporation - US|E|2013/11/16|
2013/11/27|2013/11/27
MERGE|PayrollTimePeriod|HDL_INFUSION_US_EMP_MONTHLY|HDL Vision Clothing Corporation - US|E|2013/11/01|
2013/11/27|2013/11/27
Time Denitions
Example of Loading Time Denitions
Use HCM Data Loader to create time denitions that can be either a date or a span of time. You can dene static
denitions using multiple periods, additional adjustments, or both. Alternatively, you can also dene dates based on
dynamic variables.
For example, you can create multiple time denitions to establish dierent workweeks for dierent facilities or group of
employees.
Later, you use these time denitions in payroll periods, balances, overtime periods, balance dimensions, and so on.
You can load one of these time denitions:
• Static Time Denition

• User-Dened Date
• Time Span
• Retrieval Date
202
This image shows the dierent types of time denition and how and where you can use them.
Type How You Use Where You Use
Static Time Create recurring patterns of

Definition Overtime
dates.
Periods
User Defined Define the last standard

Date process and final close dates. Element
Time Entries
Definitions
Create segments of time that
Time Span
define intervals for scheduled
Payroll Periods
operations.
Retrieval
Rate
Date Retrieve dates from the
Definitions
payroll database items.
Related Topics
• Use Time Denitions for Severance Pay
Example of Loading Static Time Denition

Load static time denitions to create recurring paerns of dates, such as overtime periods. These denitions can be
static periods of unusual length based on a given date or they can generate dates based on dynamic variables.
A company's overtime period is a standard ve day work week. You create a static time denition with a weekly
frequency that generates time periods for 3 years.
METADATA|PayrollTimeDefinition|TimeDefinitionCode|DefinitionName|StartDate|DayAdjustment|DefinitionType|
NumberOfYears|PeriodType|PeriodUnit|BaseTimeDefinitionCode|DatabaseItemCode|PeriodTimeDefinitionCode|
AdjustmentType|LegislativeDataGroupName MERGE|PayrollTimeDefinition|RPGP_HDL_TD_002|RPGP_HDL_TD_002|2016/01/01||
Static time definition|2|Monthly||||||ABC US LDG
Example of Loading User-Dened Date Time Denition

You can use these predened element duration dates to control when element entries for an employee start or end.
203
This gure describes the various types of element duration dates.
Type What Are They
First Standard Date when standard earnings

Earnings Date start accumulating
Last Standard Date when standard earnings stop

Element Earnings Date accumulating
Duration
Dates
Last Standard Last date when element entries
Process Date are considered for a normal
payroll run.
Final Close Date Last date the payroll run to

include elements for processing.
This table provides examples on when you would use the predened element duration dates.
Element Duration Date Type Example
First Standard Earnings Date Start date of the employee's record for the payroll statutory unit.

Last Standard Earnings Date Termination date of the employee's record for the payroll statutory unit.

Last Standard Process Date Last day of the payroll in which termination or payroll transfer occur.

Final Close Date If a nal close date is entered for an assigned payroll record, the employee will no longer be
considered for processing by that specic payroll.

Using HCM Data Loader, you can load your own time denitions that dene the last standard process and nal close
dates. For example, Vision Corp provides housing allowance to its employees and wants the allowance to end 30 days
after the employee is terminated. You dene a user-dened date time denition based on the last standard earnings
date, which is the termination date plus 30 days.
AdjustmentType|LegislativeDataGroupName
MERGE|PayrollTimeDefinition|RPGP_HDL_TD_006|RPGP_HDL_TD_006||-2|User-defined date||User Year||First Standard
Earning Date|||Subtract Days|ABC US LDG
204
Example of Loading Time Span Time Denitions

Use HCM Data Loader to create segments of time that dene intervals for scheduled operations, such as payroll
frequency. You can use these time span denitions within other time denitions.
A company wants to make employee payments on the last day of the month and third-party payments ve days later.
The company creates a time denition of type time span and uses it when dening the payment method for the payee.
Use this PayrollTimeDefinition .dat le to create a time span time denition.
MERGE|PayrollTimeDefinition|RPGP_HDL_TD_005|RPGP_HDL_TD_005||11|Time span||Weekly|2||||Add Days|ABC US LDG
Example of Loading Retrieval Date Time Denitions

Load retrieval date time denition that's based on the payroll database items of date format.
Let's assume that the rate contributor for the severance rate denition uses a balance as of termination date. You can
dene a retrieval date time denition based on a database item that retrieves the termination date. You can then use
this time denition as the reference date for the balance value in the rate contributor.
Use this .dat le to create a retrieval date time denition.

MERGE|PayrollTimeDefinition|RPGP_HDL_TD_001|RPGP_HDL_TD_001|||Retrieval Date|||||ENTRY_USAGE_END_DATE|||ABC US
LDG
Example of Loading Payroll Element Run Usage

Use the payroll element run usage object to identify how an element is used with the run type. Run types control the
elements and payment types to process in a payroll run.
You can't change either the rst eective start date or last eective end date for an existing payroll element run usage
object. Create these objects with eective start dates on or before the start dates of other objects that refer to your
payroll element run usage.
Vision Corp processes and pays the bonus amounts separately from the regular earnings. The organization pays regular
payroll by EFT and issues check bonuses once a year. For this requirement, they create a separate payment for the
bonus element entry, which is marked to pay separately. Using HCM Data Loader, the Payroll Manager creates a bonus
element, Annual Bonus, with Supplemental Earnings classication. She supplies these details.
Element Detail Value
Primary Classication Supplemental Earnings

205
Secondary Classication Bonus

Category Standard

Process and pay element separately Process separately and pay separately
or with other earnings elements?

Further, she loads the run type usage as Separate Payment with Element Usage as Trigger. The application processes
this element as well as makes payments separately.
This example dat le loads the payroll element run usage object:
METADATA|PayrollElementRunTypeUsage|EffectiveStartDate|UsageType|ElementTypeCode|RunTypeCode|
LegislativeDataGroupName
MERGE|PayrollElementRunTypeUsage|2018/02/02|Trigger| ANNUAL_BONUS|Regular|Vision Corporation US
Related Topics
• Elements
• Run Types
User-Dened Tables
Overview
You can set up your own structured tables to maintain a date eective lists of values or data, such as wage codes.
A user-dened table consists of rows and columns and stores the values as cells for a specic row and column
combination. For example, you can dene a table that shows the bonus amounts in the columns, for the years of
services in the rows.
Using HCM Data Loader, you can either create a user-dened table to store a range of values or match a specic value.
You can use this table with a formula to store tabular data.
Rows, Columns, and Values

To start with, you dene the column and row details. Let's understand what user-dened rows and columns are.
• A table row is a denition that stores row details. For example, a row that stores the years of service details for
bonus payments. Dene rows to accept either an exact value, such as a grade value, or a range of values, such
as a range of salary values.
• A table column stores the column details, such as a column could capture bonus amounts. You can also use a
fast formula to validate entries in the user-dened table. For example, you can validate if your bonus entries fall
within a specied range.
Then, you load the values for a date-eective combination of a user-dened row and column.
206
Related Topics
• User Table Validation Formula Type
Example of Loading User-Dened Tables for a Range of Row

Values
Let's consider this example. Each year, your organization oers stock options to its employees. The amount of stocks
depend on the years of service and the job category of the employee receiving them.
As this image shows, the user-dened table contains stock option allocations by job category and years of service. The
rows represent a range of years of service during which employees receive the same number of stock options. The
columns contain the job categories. And the values represent the number of stock options awarded to the specied job
category during the specied years of service.
Use this .dat le to load your stock option allocations.

METADATA|UserDefinedTable|UserTableCode|RangeOrMatch|UserKeyUnits|UserRowTitle|UserTableName|
METADATA|UserDefinedTableColumn|UserColumnCode|DataType|UserColumnName|UserTableCode|LegislativeDataGroupName|
FormulaName
METADATA|UserDefinedTableRow|DisplaySequence|EffectiveEndDate|EffectiveStartDate|RowHighRange|RowLowRangeOrName|
UserTableCode|LegislativeDataGroupName|RowName
METADATA|UserDefinedTableColumnInstance|EffectiveEndDate|EffectiveStartDate|Value|LegislativeDataGroupName|
UserColumnCode|RowLowRangeOrName|UserTableCode
MERGE|UserDefinedTable|VISION_RANGE_OF_ROW_VALUES|R|N|Years of Service.|VISION_Range_of_Row_Values|US
Legislative Data Group
207
MERGE|UserDefinedTableColumn|EXECUTIVE|N|EXECUTIVE|VISION_RANGE_OF_ROW_VALUES|US Legislative Data Group|

MERGE|UserDefinedTableColumn|MANAGER|N|MANAGER|VISION_RANGE_OF_ROW_VALUES|US Legislative Data Group|
MERGE|UserDefinedTableColumn|TECHNICAL|N|TECHNICAL|VISION_RANGE_OF_ROW_VALUES|US Legislative Data Group|
MERGE|UserDefinedTableColumn|CLERICAL|N|CLERICAL|VISION_RANGE_OF_ROW_VALUES|US Legislative Data Group|
MERGE|UserDefinedTableRow|10|4712/12/31|2019/06/14|3|1|VISION_RANGE_OF_ROW_VALUES|US Legislative Data Group|1
MERGE|UserDefinedTableColumnInstance|4712/12/31|2019/06/14|1000|US Legislative Data Group|EXECUTIVE|1|
VISION_RANGE_OF_ROW_VALUES
MERGE|UserDefinedTableColumnInstance|4712/12/31|2019/06/14|500|US Legislative Data Group|MANAGER|1|
MERGE|UserDefinedTableColumnInstance|4712/12/31|2019/06/14|250|US Legislative Data Group|TECHNICAL|1|
MERGE|UserDefinedTableColumnInstance|4712/12/31|2019/06/14|125|US Legislative Data Group|CLERICAL|1|
208

Related Topics
Example of Loading User-Dened Tables for Matched Row Values

Vision Corporation wants to use a user-dened table to dene schedules for their employees. All workers in the
company work on a 10 hour a day, four day in a week rotating schedule. The company has these four schedules.
• Monday - Thursday
• Tuesday - Friday
• Wednesday - Saturday
• Thursday - Sunday
As this image shows, this user-dened table contains the schedules available in the organization. The rows contain the
name of a day of the week and the columns contain the schedule. The values represent the number of hours to work
each day in a schedule.
Use this .dat le to create a user-dened table to store values for worker's schedules.
METADATA|UserDefinedTable|UserTableCode|RangeOrMatch|UserKeyUnits|UserRowTitle|UserTableName|
209
METADATA|UserDefinedTableColumn|UserColumnCode|DataType|UserColumnName|UserTableCode|LegislativeDataGroupName|
FormulaName
METADATA|UserDefinedTableRow|DisplaySequence|EffectiveEndDate|EffectiveStartDate|RowHighRange|RowLowRangeOrName|
UserTableCode|LegislativeDataGroupName|RowName
METADATA|UserDefinedTableColumnInstance|EffectiveEndDate|EffectiveStartDate|Value|LegislativeDataGroupName|
UserColumnCode|RowLowRangeOrName|UserTableCode
MERGE|UserDefinedTable|VISION_UDT_MATCHED_ROW|M|T|Days Of The Week|VISION_UDT_MATCHED_ROW|US Legislative Data
Group
MERGE|UserDefinedTableColumn|MONDAY_TO_THURSDAY|N|Monday_to_Thursday|VISION_UDT_MATCHED_ROW|US Legislative Data
Group|
MERGE|UserDefinedTableColumn|TUESDAY_TO_FRIDAY|N|Tuesday_to_Friday|VISION_UDT_MATCHED_ROW|US Legislative Data
Group|
MERGE|UserDefinedTableColumn|WEDNESDAY_TO_SATURDAY|N|Wednesday_to_Saturday|VISION_UDT_MATCHED_ROW|US Legislative
Data Group|
MERGE|UserDefinedTableColumn|THURSDAY_TO_SUNDAY|N|Thursday_to_Sunday|VISION_UDT_MATCHED_ROW|US Legislative Data
Group|
MERGE|UserDefinedTableRow|10|4712/12/31|2019/06/14||MONDAY|VISION_UDT_MATCHED_ROW|US Legislative Data Group|
Monday
MERGE|UserDefinedTableRow|20|4712/12/31|2019/06/14||TUESDAY|VISION_UDT_MATCHED_ROW|US Legislative Data Group|
Tuesday
MERGE|UserDefinedTableRow|30|4712/12/31|2019/06/14||WEDNESDAY|VISION_UDT_MATCHED_ROW|US Legislative Data Group|
Wednesday
MERGE|UserDefinedTableRow|40|4712/12/31|2019/06/14||THURSDAY|VISION_UDT_MATCHED_ROW|US Legislative Data Group|
Thursday
MERGE|UserDefinedTableRow|50|4712/12/31|2019/06/14||FRIDAY|VISION_UDT_MATCHED_ROW|US Legislative Data Group|
Friday
MERGE|UserDefinedTableRow|60|4712/12/31|2019/06/14||SATURDAY|VISION_UDT_MATCHED_ROW|US Legislative Data Group|
Saturday
MERGE|UserDefinedTableRow|70|4712/12/31|2019/06/14||SUNDAY|VISION_UDT_MATCHED_ROW|US Legislative Data Group|
Sunday
MERGE|UserDefinedTableColumnInstance|4712/12/31|2019/06/14|10|US Legislative Data Group|MONDAY_TO_THURSDAY|
MONDAY|VISION_UDT_MATCHED_ROW
TUESDAY|VISION_UDT_MATCHED_ROW
WEDNESDAY|VISION_UDT_MATCHED_ROW
THURSDAY|VISION_UDT_MATCHED_ROW
FRIDAY|VISION_UDT_MATCHED_ROW
SATURDAY|VISION_UDT_MATCHED_ROW
SUNDAY|VISION_UDT_MATCHED_ROW
MERGE|UserDefinedTableColumnInstance|4712/12/31|2019/06/14|0|US Legislative Data Group|TUESDAY_TO_FRIDAY|MONDAY|
VISION_UDT_MATCHED_ROW
MERGE|UserDefinedTableColumnInstance|4712/12/31|2019/06/14|10|US Legislative Data Group|TUESDAY_TO_FRIDAY|
MERGE|UserDefinedTableColumnInstance|4712/12/31|2019/06/14|0|US Legislative Data Group|TUESDAY_TO_FRIDAY|SUNDAY|
VISION_UDT_MATCHED_ROW
MERGE|UserDefinedTableColumnInstance|4712/12/31|2019/06/14|0|US Legislative Data Group|WEDNESDAY_TO_SATURDAY|
210

MERGE|UserDefinedTableColumnInstance|4712/12/31|2019/06/14|0|US Legislative Data Group|THURSDAY_TO_SUNDAY|
Related Topics
Examples of Loading Payroll Balance Denitions

A balance denition includes a combination of user-dened naming criteria, one or more balance dimensions, and
balance feeds. Most of the balances you require are predened. Depending on your country extension, use HCM Data
Loader to dene additional balances for calculations or reporting.
Let's consider this example. The members of Vision Corps union contribute their union dues that's determined by a
formula. The formula computes the union dues as a percentage of a user-dened Union Dues Basis balance, which
sums up these earnings.
• All earnings in the Standard Earnings classication.
• All earnings in the Imputed Earnings classication.
• A specic car allowance element.
211
This gure includes the balance dimensions that identify the specic value of a balance. Here, the balance is fed by the
element classications and an element.
Balance
Dimensions
Payroll Balances
Balance Feed by Classification Balance Feed by Elements
Standard Inputed
Element Input Value
Earnings Earnings
Payroll balance denitions are made up of these components:
• Balances
• Dened Balance
• Balance Feed
Balances
Payroll balances show the accumulation of values over a period of time. Typically, the global and country-specic rules
create a majority of balances whenever you create an earnings or deductions element. However, you might need to
dene a balance denition outside of the element setup.
You supply balance denitions in the PayrollBalanceDefinition.dat le. Here, you assign a category of Miscellaneous
so that the balance isn't included in the reports. Since the monetary value is fed into the balance, you supply UOM as
Money and the Currency as USD.
METADATA|PayrollBalanceDefinition|SourceSystemOwner|SourceSystemId|LegislativeDataGroupName|BalanceCode|
BalanceName|ReportingName|BalanceCategoryCode|BalanceUOM|CurrencyCode
MERGE|PayrollBalanceDefinition|VISION|UNION_DUES|Vision Corporation US LDG|HDL_UNION_DUES_BASIS|Union Dues
Basis|Union Dues Basis|Miscellaneous|M|USD
212
Dened Balances
Each payroll balance can have multiple dimensions, which dene the specic value to retrieve. The following Dened
Balance lines load these relationship level dimensions for which the balance value is aggregated.
• Relationship Period to Date
• Relationship Month to Date
• Relationship Quarter to Date
• Relationship Year to Date
METADATA|DefinedBalance|SourceSystemOwner|SourceSystemId|BalanceId(SourceSystemId)|LegislativeDataGroupName|
BalanceDimensionCode
MERGE|DefinedBalance|VISION|UNION_DUES_DB_PTD|UNION_DUES|Vision Corporation US LDG|Relationship Period to Date
MERGE|DefinedBalance|VISION|UNION_DUES_DB_MTD|UNION_DUES|Vision Corporation US LDG|Relationship Month to Date
MERGE|DefinedBalance|VISION|UNION_DUES_DB_QTD|UNION_DUES|Vision Corporation US LDG|Relationship Quarter Year
to Date
MERGE|DefinedBalance|VISION|UNION_DUES_DB_YTD|UNION_DUES|Vision Corporation US LDG|Relationship Year to Date
MERGE|DefinedBalance|VISION|UNION_DUES_DB_RUN|UNION_DUES|Vision Corporation US LDG|Relationship Run
Balance Feed
A balance feed contains details of how a given element input value contributes to a specic balance. You can load
element classications and individual elements to feed a balance.
You can't change either the rst eective start date or last eective end date for an existing balance feed. Create
balance feed objects with eective start dates on or before the start dates of other objects that refer to your balance
feed.
Balance Feed by Classication

These balance classication lines create balance classications, which determine the element classications you add to
or subtract from the balance. The direct run result value of every element in the classication feeds the balance. Here,
you load Standard Earnings and Imputed Earnings element classications with Add feed.
METADATA|BalanceClassification|SourceSystemOwner|SourceSystemId|BalanceId(SourceSystemId)|
LegislativeDataGroupName|ElementClassificationCode|AddSubtract
MERGE|BalanceClassification|VISION|UNION_DUES_BC_STD|UNION_DUES|Vision Corporation US LDG|Standard Earnings|1
MERGE|BalanceClassification|VISION|UNION_DUES_BC_TAX|UNION_DUES|Vision Corporation US LDG|Taxable Benefits|1
Balance Feed by Elements

Load individual elements and input values to feed the balance.
These balance feed lines add an element feed from the ZFRC VS USD Car Allowance Element Earnings Results
element and Earnings Calculated input value.
METADATA|BalanceFeed|SourceSystemOwner|SourceSystemId|BalanceId(SourceSystemId)|EffectiveStartDate|
LegislativeDataGroupName|ElementCode|InputValueCode|AddSubtract
MERGE|BalanceFeed|VISION|UNION_DUES_BF_IMP|UNION_DUES|2018/01/01|Vision Corporation US LDG|ZFRC VS USD Car
Allowance Element Earnings Results|Earnings Calculated|1
Related Topics
• Payroll Balance Denitions
• Balance Feeds
213
Payroll Balance Groups

Example of Loading Payroll Balance Aribute Denitions
Use HCM Data Loader to dene balance aribute denitions and add balance denitions to it.
A balance aribute denition is a set of balance denitions that you can include in your balance group. It identies
the criteria for including the balance denitions. Use a balance aribute to associate a balance denition to a balance
aribute denition.
In this example, the Vision Corp Company wants to report a particular statutory deduction balance for employees. To do
this, rst you create a balance aribute denition Employee Taxes Aribute Denition and add these balance denitions
to it.
Balance Type Balance Dimension
FIT Withheld Relationship Tax Unit Period to Date

Medicare Employee Withheld Relationship Tax Unit Period to Date

Social Security Employee Withheld Relationship Tax Unit Period to Date

FIT Withheld Relationship Tax Unit Quarter to Date

Medicare Employee Withheld Relationship Tax Unit Quarter to Date

Social Security Employee Withheld Relationship Tax Unit Quarter to Date

FIT Withheld Relationship Tax Unit Year to Date

Medicare Employee Withheld Relationship Tax Unit Year to Date

Social Security Employee Withheld Relationship Tax Unit Year to Date

214
As this gure shows, you create a balance aribute denition and then add balance denitions to it.
The next step is to create a balance group and add this balance aribute denition to the balance group. Later you
create a report sort type to sort the balance values and then create a balance group usage for your balance group.
Creating a Balance Aribute Denition

In the BalanceAributeDenition.dat le you dene a balance aribute denition and add balance denitions to it.
METADATA|BalanceAttributeDefinition|LegislativeDataGroupName|AttributeCode|UserAttributeName|Alterable|
Description
MERGE|BalanceAttributeDefinition|Vision Corporation US LDG|EMP_TAXES_ATTR_DEFN|Employee Taxes Attribute
Definition|Y|Attribute definition for Employee Taxes reporting
METADATA|BalanceAttribute|LegislativeDataGroupName|AttributeCode|BalanceCode|BalanceDimensionCode
MERGE|BalanceAttribute|Vision Corporation US LDG|EMP_TAXES_ATTR_DEFN|US_FIT_WITHHELD|Core Relationship Tax
Unit Period to Date
Unit Quarter Year to Date
Unit Year to Date
MERGE|BalanceAttribute|Vision Corporation US LDG|EMP_TAXES_ATTR_DEFN|US_MEDICARE_EMPLOYEE_WITHHELD|Core
Relationship Tax Unit Period to Date
Relationship Tax Unit Quarter Year to Date
215

Relationship Tax Unit Year to Date
MERGE|BalanceAttribute|Vision Corporation US LDG|EMP_TAXES_ATTR_DEFN|US_SOCIAL_SECURITY_EMPLOYEE_WITHHELD|
Core Relationship Tax Unit Period to Date
Core Relationship Tax Unit Quarter Year to Date
Core Relationship Tax Unit Year to Date
Related Topics
• Balance Groups and Usages
• Create Balance Groups and Usages
Example of Loading Payroll Balance Groups

Use HCM Data Loader to dene payroll balance groups for viewing and reporting payroll balances. You can dene a
balance group either at the employee level or at group level.
In this example, you dene a payroll balance group Employee Taxes Balance Group and add the balance aribute
denition to it.
Before you do this, ensure that you have created the balance aribute denition Employee Taxes Aribute Denition.
Also, you must have added balances to the aribute denition.
Refer to the topic: Loading Payroll Balance Aribute Denitions for more information on creating a balance aribute
denition.
216
As this gure shows, you dene a balance group and later include the balance aribute denitions to it.
After dening a payroll balance group, the next step is to create a sort list to sort the balance items. Then you create a
balance group usage and add this balance group to a balance group usage.
Creating a Payroll Balance Group

Use the BalanceGroup.dat le to create a payroll balance group and include the balance aribute denition in it.
METADATA|BalanceGroup|LegislativeDataGroupName|BalanceGroupCode|GroupName|Description|
BalanceCategoryRestricted|BalanceDimensionRestricted
MERGE|BalanceGroup|Vision Corporation US LDG|EMP_TAXES_BAL_GRP|Employee Taxes Balance Group|Balance group
for Employee Taxes reporting|N|N
METADATA|BalanceGroupInclusion|LegislativeDataGroupName|BalanceGroupCode|AttributeCode
MERGE|BalanceGroupInclusion|Vision Corporation US LDG|EMP_TAXES_BAL_GRP|EMP_TAXES_ATTR_DEFN
Related Topics
• Rules for Editing Balance Groups and Their Usages
217
Example of Loading Report Sort Type and Report Sort Items

Use HCM Data Loader to create a report sort type and items that denes how balance values are sorted in the report.
Let's look at this example. Vision Corp creates a report sort type and species the sort type as Static Order to dene the
sequence that displays the balance results.
Before You Start
Ensure that you have completed these tasks:
• Created the balance aribute denition Employee Taxes Aribute Denition.
For more information on how to create balance aribute denitions, refer to the topic: Loading Balance
Aribute Denitions.
• Created the balance group Employee Taxes Balance Group and included the balance aribute denitions to it.
For more information on how to create and load a balance group using HCM Data Loader, refer to the topic:
Loading Payroll Balance Groups.
218
As this gure shows, you create a report sort type and add sort items to it.
After creating a report sort type, you create a balance group usage for your balance group and dene the balance group
usage items. For more information on how to create a balance group usage using HCM Data Loader, refer to the topic:
Loading Payroll Balance Groups Usage.
Creating a Report Sort Type

Use the ReportSort.dat le to create a report sort type with sort method as Static Order.
METADATA|ReportSortType|LegislativeDataGroupName|ReportSortCode|SortName|Description|SortMethod|SortLevel|
SortOrder
MERGE|ReportSortType|Vision Corporation US LDG|EMP_TAXES_STATIC_SORT|Employee Taxes Sort|Static sort order
for Employee Taxes|Static Order|Balance Type|Ascending
Creating Report Sort Items

Use the ReportSortItem.dat le to specify the order in which balance types are displayed for the balance group usage.
METADATA|ReportSortItem|LegislativeDataGroupName|ReportSortCode|SequenceNumber|BalanceCode
MERGE|ReportSortItem|Vision Corporation US LDG|EMP_TAXES_STATIC_SORT|10|US_FIT_WITHHELD
MERGE|ReportSortItem|Vision Corporation US LDG|EMP_TAXES_STATIC_SORT|20|US_MEDICARE_EMPLOYEE_WITHHELD
219
MERGE|ReportSortItem|Vision Corporation US LDG|EMP_TAXES_STATIC_SORT|30|US_SOCIAL_SECURITY_EMPLOYEE_WITHHELD
Related Topics
Example of Loading Payroll Balance Group Usages

Use HCM Data Loader to create balance group usages that represent an instance of a balance group, such as report,
extract denition, and so on. For every balance group, you must dene at least one balance group usage. But you can
dene multiple usages for a balance group.
Vision Corp creates a balance group usage to use the Employee Taxes Balance Group balance group for their
employee taxes report. Include your report sort type Employee Taxes Sort to this balance group usage.
Before You Start
Ensure that you have completed these tasks:
• Created the balance aribute denition Employee Taxes Aribute Denition. For more information on how to
create balance aribute denitions, refer to the topic: Loading Balance Aribute Denitions.
• Created the balance group Employee Taxes Balance Group and included the balance aribute denitions to
it. For more information on how to create and load a balance group using HCM Data Loader, refer to the topic:
Loading Payroll Balance Groups.
• Created the Report Sort Type Employee Taxes Sort and added the sort items to it. For more information on
how to create report sort type, refer to the topic: Loading Report Sort.
220
As this gure shows, you create a balance usage for the balance group and dene the balance group usage items.
Creating a Payroll Balance Group Usage

This example BalanceGroupUsage.dat le creates the Employee Period Taxes Balance group Usage in a matrix format.
Each balance group usage item denes a column in the Employee Period Taxes balance results matrix.
METADATA|BalanceGroupUsage|LegislativeDataGroupName|BalanceGroupUsageCode|GroupUsageName|Description|
FormatType|BalanceGroupCode|ReportSortCode
MERGE|BalanceGroupUsage|Vision Corporation US LDG|EMP_PERIOD_TAXES|Employee Period Taxes|Employee taxes
matrix with static sort order|MATRIX|EMP_TAXES_BAL_GRP|EMP_TAXES_STATIC_SORT
METADATA|BalanceGroupUsageItem|LegislativeDataGroupName|BalanceGroupUsageCode|SourceType|Position|
BalanceDimensionCode
MERGE|BalanceGroupUsageItem|Vision Corporation US LDG|EMP_PERIOD_TAXES|Balance Dimension|10|Core
Relationship Tax Unit Period to Date
Relationship Tax Unit Quarter Year to Date
Relationship Tax Unit Year to Date
Related Topics
221
Fast Formulas
Example of Loading Fast Formula
Use HCM Data Loader to create formula that are generic expressions of calculations or comparisons that you want to
repeat with dierent input variables. You can use these predened rules to perform calculations, such as a legislative
specic tax or social insurance calculations. Create formula with eective start dates on or before the start dates of
other objects that refer to your formula.
Supply the fast formula text in a separate text le and then pass the text le name to the Comments aribute. Further,
place the formula text le in the ClobFiles folder within the same compressed le as FastFormula.dat le that references
it. Also, don't supply the text directly in the FastFormula.dat le.
This example loads the fast formula.

METADATA|FastFormula|SourceSystemOwner|SourceSystemId|EffectiveStartDate|FormulaCode|FormulaTypeCode|
FormulaName|FormulaText|LegislativeDataGroupId(SourceSystemId)
MERGE|FastFormula|VISION|MGR_SCHED_HRS|2000/01/01|MGR_RANGE_SCHD_HRS|Range of Scheduled Hours|Manager Range of
Scheduled Hours|ManagerRangeScheduledHrs.txt|
Related Topics
• Overview of Using Formulas
• Overview of Writing Formulas
Example of Loading Fast Formula Globals

Use fast formula globals in multiple formulas to support the Human Capital Management business rules. For example,
the global value could hold tax relief percentages, bonus percentage or overtime rates. Create globals with eective
start dates on or before the formula that refer to them.
This example loads global values using source keys.
METADATA|FastFormulaGlobal|SourceSystemOwner|SourceSystemId|EffectiveStartDate|GlobalCode|GlobalName|DataType|
GlobalValue|LegislativeDataGroupId(SourceSystemId)
MERGE|FastFormulaGlobal|VISION|GBLMAXILLHEALTH|2000/01/01|MAX_ABS_DURATION_ILLHEALTH|Maximum Absence Duration
for Ill Health|N|10|
MERGE|FastFormulaGlobal|VISION|GBLDATEEXAMPLE|2000/01/01|GLOBAL_DATE_EXAMPLE|Fast Formula Global Date Example|D|
2012-01-01|LDG_VI_UK
MERGE|FastFormulaGlobal|VISION|GBLSTRINGEXAMPLE|2000/01/01|GLOBAL_STRING_EXAMPLE|Fast Formula Global String
Example|T|Global Value|LDG_VI_UK
Create the legislative data group using the example provided in the Loading Legislative Data Groups: Examples topic.
Related Topics
• Overview of Using Formulas
• Overview of Writing Formulas
222
Elements
Overview
Use HCM Data Loader to load elements, which determine the payment of base pay, benets, absences, earnings and
deductions. For example, you can load earnings and deduction elements, such as bonuses, overtime earnings, and
involuntary deductions.
You create elements by using the element templates. The design of the template varies depending upon the primary
and secondary classications and the element category. The answers that you load to the template questions determine
the components that are created for the element, such as the balances, balance feeds, and formulas required for
processing.
Refer to the Element Creation: Review page for a specic list of questions that you will need to answer to load your
elements.
This gure illustrates an example of an earnings element for hourly wages. For each component, you will load the
respective value. For example, you load Standard Earnings as the value for the component Classication.
Processing
Classification
Rules
Standard Earnings Processing frequency of

weekly
Input Values Formulas
Element Wage = Hours Worked * Hourly

Hours Worked and Hourly Rate Rate
Wage
Eligibility Balances
Employees on a weekly payroll

and Salary Basis = Hourly Taxable Earnings
This table summarizes the various building blocks of an element:
Component What It Does
Classication Determines the processing order and balance feeds for elements. Elements can belong to
three types of classications - Primary, Secondary, and Subclassications.
223
Component What It Does
Input Values Denes values that hold information to calculate an element's payroll run result.

Eligibility Determines rules that indicate which employees are eligible for an element.

Processing Rules Identies the formula to create and then use when processing element entries. You can load
multiple processing rules if you want to use dierent formulas, such as a rule depending on an
assignment status.

Formulas Species the calculation used to process elements. An element has one or more formula result
rules automatically generated when you create an element.

Balances Accumulates result totals over a period of time.

Related Topics
• Elements
• Primary Element Classications
• How Element Classication Components Work Together
Example of Creating Earnings Element for Payroll

This example shows how to use the element template to create a regular earnings element, such as salary. After you
create the earnings element, you must create at least one eligibility record for it.
Load these details:
Parameter Value
Legislative Data Group Vision Corp

Primary Classication Standard Earnings

Category Standard

Element Name Base Salary

Reporting Name Base Salary

Eective Date 01/01/2010

224
The table shows the responses that you provide to these questions:
Question Answer
What's the input currency? US Dollar

Should every person eligible for the No

element automatically receive it?

What's the earliest entry date for this First Standard Earnings Date
element?

What's the latest entry date for this Last Standard Earning Date
element?

At which employment level should Assignment Level

this element be aached?

Do you want the element to be Yes

processed at Payroll Assignment
level?|

Does the element recur each payroll Recurring

period, or does it require explicit
entry?

Process the element only once in Yes

each payroll period?

Can a person have more than one No

entry of the element in a payroll
period?

Process and pay element separately Process and pay with other earnings

Tax this earning across multiple pay No

periods?

Prorate this earning across all No

periods during which it was
earned, and consider it for
Overtime calculations, such as for
commissions, bonuses, incentives,
and other nondiscretionary earnings?

225
Question Answer
Does this element have a limit on the No

amount which is exempt from Federal
Tax?|

Does this element have a limit on No

the amount which is exempt at state
level?

Do you want to default it to Federal Yes

level?

What's the calculation rule? Flat Amount

What's the default periodicity of the Periodically

element?

What's the periodicity conversion Standard Rate Annualized

rule?

How do you want the work units to be Hours

reported?

What's the work units conversion Standard Rate Annualized

rule?

Is this element subject to proration? Yes

What's the proration group? Entry Changes for Proration

What's the proration rate conversion Periodic Work Schedule Rate Annualized
rule?

What's the proration units? Hourly

Is this element subject to retroactive Yes

changes?

What's the retro group? Entry Change for Retro

Use this element to calculate a gross No

amount from a specied net amount?

226
Question Answer
Should this element reduce regular No

earnings?

Should this element be included in Yes

the earnings calculation of the FLSA
overtime base rate?

Should this element be included in Yes

the hours calculation of the FLSA
overtime base rate?

Use this DAT le to create a regular earnings element.

METADATA|PayrollElementDetails|ElementName|ReportingName|Description|LegislativeDataGroupName|
PrimaryClassificationName|SecondaryClassificationName|Category|ElementStartDate
METADATA|PayrollElementQuestionnaire|ElementName|LegislativeDataGroupName|RuleCode|Rule|Response
MERGE|PayrollElementDetails|Base Salary|Base Salary|Base Salary|Vision Corporation US LDG|Standard Earnings||
Standard|2010/01/01
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|SpecCurrency|Input Currency|US Dollar
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|Availability Rule|Should every person
eligible for the element automatically receive it?|No
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|Hire Process|What is the earliest entry
date for this element?|First Standard Earning Date
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|Terminate Process|What is the latest
entry date for this element?|Last Standard Earning Date
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|Processing Level2Tier|At which
employment level should this element be attached?|Assignment Level
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|Processing Asg Level|Do you want the
element to be processed at Payroll Assignment level?|Yes
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|RecurringOrNonRecurringExcl|Does this
element recur each payroll period, or does it require explicit entry?|Recurring
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|Once Per Period-Earnings|Process the
element only once in each payroll period?|Yes
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|Multiple Entries|Can a person have more
than one entry of this element in a payroll period?|No
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|Process Period|Process and pay element
separately or with other earnings elements?|Process and pay with other earnings
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|AnnualizationRule|Tax this earning
across multiple pay periods?|No
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|AugmentRule|Prorate this earning across
all periods during which it was earned, and consider it for Overtime calculations, such as for commissions,
bonuses, incentives, and other nondiscretionary earnings?|No
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|FedLimitRule|Does this element have a
limit on the amount which is exempt from Federal Tax?|No
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|FedLimitRuleValue|Enter Federal Tax
Limit|0
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|StateLimitRule|Does this element have a
limit on the amount which is exempt at state level?|No
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|StateLimitRule2|Do you want to default
it to Federal level?|Yes
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|CalculationRule|What is the calculation
rule?|Flat amount
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|AugmentCalculationRule|What is the
calculation rule?|Flat amount
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|Periodicity|What is the default
periodicity of this element?|Periodically
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|PeriodConverFormulas|Periodicity
Conversion Rule|Standard Rate Annualized
227
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|ReportUnitRule|How do you want the work

units to be reported?|Hours
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|RateConverFormula|Work Units Conversion
Rule|Standard Rate Annualized
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|Proration|Is this element subject to
proration?|Yes
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|Proration Group|Proration Group|Entry
Changes for Proration
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|ProrateRate|Proration Rate Conversion
Rule|Periodic Work Schedule Rate Annualized
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|ProrationUnit|Proration Units|Hourly
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|Retro|Is this element subject to
retroactive changes?|Yes
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|RetroGroup|Retro Group|Entry Changes for
Retro
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|IterativeInformation|Use this element to
calculate a gross amount from a specified net amount?|No
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|Reduce Regular|Should this element
reduce regular earnings?|No
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|FLSAEarnings|Should this element be
included in the earnings calculation of the overtime base rate?|Yes
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|FLSAHours|Should this element be
included in the hours calculation of the overtime base rate?|Yes
MERGE|PayrollElementQuestionnaire|Base Salary|Vision Corporation US LDG|AugmentFLSAEarnings|Should this element
be included in the earnings calculation of the overtime base rate?|Yes
Related Topics
• Elements
Example of Creating a Loan Deduction Element

In this example, an employee takes a personal loan and the Vision Corp company deducts a stipulated amount from
their pay for each pay period.
When there are no sucient earnings to cover the deduction, then the loan amount goes into the employee's arrears
account.
Using HCM Data Loader, load these details:
Parameter Value

Primary Classication Voluntary Deduction

Category Standard

Element Name Personal Loan

Reporting Name Personal Loan
228
Parameter Value


And this table shows the responses that you provide to these questions:
Question Answer
What's the input currency? US Dollar

Should every person eligible for the No

element automatically receive it?

What's the earliest entry date for this First Standard Earnings Date
element?

What's the latest entry date for this Last Standard Process Date
element?

At which employment level should Payroll relationship Level

this element be aached?


processed at Payroll Relationship
level?

What should happen when there Take a partial deduction, place remaining in arrears
are insucient funds to cover the
deductions?

Does the element recur each payroll Recurring

period, or does it require explicit
entry?

Process the element only once in Yes

each payroll period?

Can a person have more than one No

entry of the element in a payroll
period?


processed at Payroll Relationship
level?
229
Question Answer
What's the calculation rule? Flat amount deduction

Is this element subject to proration? Yes

Proration Group Entry Changes for Proration

Is this element subject to retroactive Yes

changes?

Retro Group Entry Changes for Retro

Processing Stop when the Total is Yes

reached?

Use this DAT le to create a loan deduction element.

METADATA|PayrollElementDetails|ElementName|ReportingName|Description|LegislativeDataGroupName|
PrimaryClassificationName|SecondaryClassificationName|Category|ElementStartDate
METADATA|PayrollElementQuestionnaire|ElementName|LegislativeDataGroupName|RuleCode|Rule|Response
MERGE|PayrollElementDetails|Personal Loan|Personal Loan|Personal Loan|Vision Corporation US LDG|Voluntary
Deductions||Standard|2010/01/01
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|SpecCurrency|Input Currency|US Dollar
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|Availability Rule|Should every person
eligible for the element automatically receive it?|No
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|Hire Process|What is the earliest
entry date for this element?|First Standard Earning Date
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|Terminate Process|What is the latest
entry date for this element?|Last Standard Process Date
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|Processing Level|At which employment
level should this element be attached?|Payroll relationship level
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|Processing Rel Level|Do you want the
element to be processed at Payroll Relationship level?|Yes
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|Arrear Partial Dedn|What should happen
when there are insufficient funds to cover the deductions?|Take a partial deduction, place remaining in arrears
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|Recurring Or NonRecurring|Does this
element recur each payroll period, or does it require explicit entry?|Recurring
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|Once Per Period|Process the element
only once in each payroll period?|Yes
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|Multiple Entries|Can a person have
more than one entry of this element in a payroll period?|No
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|Processing Rel Level Excl|Do you want
the element to be processed at Payroll Relationship level? Exclude|Yes
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|CalculationRuleDedn|What is the
calculation rule?|Fixed amount deduction
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|Proration|Is this element subject to
proration?|Yes
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|ProrationFormula|Proration Formula|
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|Proration Group|Proration Group|Entry
Changes for Proration
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|Retro|Is this element subject to
retroactive changes?|Yes
230
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|RetroGroup|Retro Group|Entry Changes

for Retro
MERGE|PayrollElementQuestionnaire|Personal Loan|Vision Corporation US LDG|Total Reached|Processing Stop when the
Total is reached?|Yes
Related Topics
• Elements
Example of Updating Payroll Element Denitions

Use HCM Data Loader to create and update or delete existing element denitions. Element denitions include
denitions for payroll, human resources, and benets elements, such as earnings, deductions, and taxation.
You can edit the element denition to dene the order in which the elements are processed in the payroll run. These
rules determine whether the elements can be processed more than once in a period.
Let's consider the scenario where you dene a new input value to an existing voluntary deduction element that doesn't
have an element eligibility. You then create an eligibility, eligibility input values, and sub classication rules as shown in
this gure.
These DAT lines update the existing element description and reporting name.
METADATA|PayrollElementDefinition|ElementCode|EffectiveStartDate|EffectiveEndDate|LegislativeDataGroupName|
ReportingName|Description
MERGE|PayrollElementDefinition|Vision Loan Element|2010/01/01|| Vision USA LDG|Car Loan Element|Process car
loan deduction
231
Input Value
An element's input values dene the entry values available on each entry of this element. Each input value has a unit
of measure, such as money or date. Input values can include validations and conditions to control the data entry of the
element entry assigned to a person.
These DAT lines create an input value Loan Reference Number for the element Vision Loan Element.
METADATA|InputValue|EffectiveStartDate|EffectiveEndDate|InputValueCode|ValueRequiredFlag|
CreateDatabaseItemFlag|UOM|DisplayFlag|AllowUserEntryFlag|SourceSystemOwner|SourceSystemId|ElementCode|
DisplaySequence|LegislativeDataGroupName|Name
MERGE|InputValue|2010/01/01||Loan Reference Number|Y|Y|C|Y|Y|||Vision Loan Element|100| Vision USA LDG|Loan
Reference Number
Element Eligibility
Element eligibility determines which people are eligible for an element. To determine eligibility, you select the criteria
that people must have to receive entries of the element.
These DAT lines create the element eligibility Vision Loan Element Eligibility with the criteria Payroll = Vision Monthly
Payroll.
METADATA|ElementEligibility|EffectiveStartDate|EffectiveEndDate|ElementEligibilityName|AutomaticEntryFlag|
ElementCode|LegislativeDataGroupName|PayrollCode
MERGE|ElementEligibility|2010/01/01||HDL Loan Element Eligibility|N|HDL Loan Element|PM US Sun Power|HDL
Monthly Payroll
Formulas
Formulas specify the calculation used to process elements. Dene a fast formula Vision Loan Element Formula that
calculates the amount using various criteria. It returns the amount to a target element that's used to deduct the amount
for an employee.
You associate the fast formula in the status processing rules and the deduction amount to the target element in formula
result rules.
Status Processing Rule

Dene rules for processing elements according to specic assignment statuses. For each assignment status, you can
specify a dierent formula to be run for the same element.
These lines creates a status processing rule.
METADATA|StatusProcessingRule|EffectiveStartDate|EffectiveEndDate|ElementCode|LegislativeDataGroupName|
AssignmentStatusCode|FormulaCode|BalanceAdjustment
MERGE|StatusProcessingRule|2010/01/01||HDL Loan Element|PM US Sun Power|Inactive - No Payroll|HDL LOAN
ELEMENT FORMULA|No
Formula Result Rule

A formula result rule denes the processing rules for each element. Formulas are aached to an element for processing
according to specic assignment statuses. For each assignment status, it's possible to specify a dierent formula to be
red for the same element. For example, salary is calculated dierently when the employee is on leave of absence.
These lines create a formula result rule.
METADATA|FormulaResultRule|EffectiveStartDate|EffectiveEndDate|ElementCode|LegislativeDataGroupName|
AssignmentStatusCode|ResultReturned|ResultRule|TargetElementCode|TargetInputValueCode|BalanceAdjustment
MERGE|FormulaResultRule|2010/01/01||HDL Loan Element|PM US Sun Power|Inactive - No Payroll|L_VALUE|Indirect
Result|SC_HDL_EARN|Pay Value|No
232
Sub Classication Rule

Dene sub classication rules for the elements to control the balance it feeds. An element can have multiple
subclassications.
These lines create a sub classication rule Disposable Income Garnishment for the Standard Earnings element.
METADATA|SubClassificationRule|EffectiveStartDate|EffectiveEndDate|ElementCode|LegislativeDataGroupName |
ClassificationCode
MERGE|SubClassificationRule|2010/01/01|| Disposable Income Garnishment | Vision USA LDG|Standard Earnings
Related Topics
• Elements
• Formula Result Rules for Elements
• Element Input Values
Example of Loading Payroll Element Run Usage

Use the payroll element run usage object to identify how an element is used with the run type. Run types control the
elements and payment types to process in a payroll run.
You can't change either the rst eective start date or last eective end date for an existing payroll element run usage
object. Create these objects with eective start dates on or before the start dates of other objects that refer to your
payroll element run usage.
Vision Corp processes and pays the bonus amounts separately from the regular earnings. The organization pays regular
payroll by EFT and issues check bonuses once a year. For this requirement, they create a separate payment for the
bonus element entry, which is marked to pay separately. Using HCM Data Loader, the Payroll Manager creates a bonus
element, Annual Bonus, with Supplemental Earnings classication. She supplies these details.
Primary Classication Supplemental Earnings

Secondary Classication Bonus

Category Standard

Process and pay element separately Process separately and pay separately

Further, she loads the run type usage as Separate Payment with Element Usage as Trigger. The application processes
this element as well as makes payments separately.
This example dat le loads the payroll element run usage object:
METADATA|PayrollElementRunTypeUsage|EffectiveStartDate|UsageType|ElementTypeCode|RunTypeCode|
233
MERGE|PayrollElementRunTypeUsage|2018/02/02|Trigger| ANNUAL_BONUS|Regular|Vision Corporation US
Related Topics
• Elements
• Run Types
234
Integrating with HCM Loading Payroll Transactional Data
15 Loading Payroll Transactional Data
Example of Loading Payroll Time Cards

Use HCM Data Loader to import time cards from a third-party time collection device to the Payroll cloud. Let's look at
this example. Recently, Vision Corp has acquired a company and imports the acquired employees' approved time to
Payroll for payments.
This PayrollTimeCard.dat le uses source keys to import approved time entries into the Oracle Payroll Cloud.
METADATA|PayrollTimeCard|SourceSystemOwner|SourceSystemId|LegislativeDataGroupName|
AssignmentId(SourceSystemId)|EffectiveStartDate|EffectiveEndDate|TimeCardId
MERGE|PayrollTimeCard|VISION|9999890|Vision Corporation US LDG|HDL034233|2020/01/11|2020/01/18|6
METADATA|TimeEntry|SourceSystemOwner|SourceSystemId|LegislativeDataGroupName|AssignmentId(SourceSystemId)|
EffectiveStartDate|EffectiveEndDate|TimeCardInstanceId(SourceSystemId)|TimeType|Time|UnitOfMeasure|TimeCardId|
TimeEntryId|Periodicity|Factor|RateDefinitionId|RateValue
MERGE|TimeEntry|VISION|8888812|Vision Corporation US LDG|HDL034233|2020/01/11|2020/01/11|9999890|
NB_ZHRX_OTL_CDRM|8.0|H_DECIMAL3|6|6|HOURLY|1.0|300100122876642|7.0
MERGE|TimeEntry|VIRX_OSION|8888813|Vision Corporation US LDG|HDL034233|2020/01/12|2020/01/12|9999890|
MERGE|TimeEntry|VISION|8888814|Vision Corporation US LDG|HDL034233|2020/01/13|2020/01/13|9999890|
MERGE|TimeEntry|VISION|8888815|Vision Corporation US LDG|HDL034233|2020/01/14|2020/01/14|9999890|NB_ZHTL_CDRM|
8.0|H_DECIMAL3|6|9|HOURLY|1.0|300100122876642|7.0
METADATA|TimeEntryProperty|SourceSystemOwner|SourceSystemId|LegislativeDataGroupName|
AssignmentId(SourceSystemId)|EffectiveStartDate|EffectiveEndDate|PayrollTimeItemId(SourceSystemId)|TimeType|
PropertyName|PropertyValue|TimeCardId|TimeEntryId|TimeCardInstanceId(SourceSystemId)
MERGE|TimeEntryProperty|VISION|777712|Vision Corporation US LDG|HDL034233|2020/01/11|2020/01/11|8888812|
NB_ZHRX_OTL_CDRM|NB_ZHRX_OTL_CDRM_State|12|6|6|9999890
This example uses user keys to reference the time card data.
METADATA|PayrollTimeCard|LegislativeDataGroupName|AssignmentNumber|EffectiveStartDate|EffectiveEndDate|
TimeCardId
MERGE|PayrollTimeCard|Vision Corporation US LDG|E15CDRM|2020/01/11|2020/01/18|6
METADATA|TimeEntry|LegislativeDataGroupName|AssignmentNumber|EffectiveStartDate|EffectiveEndDate|TimeType|
Time|UnitOfMeasure|TimeCardId|TimeEntryId|Periodicity|Factor|RateName|RateValue
MERGE|TimeEntry|Vision Corporation US LDG|E15CDRM|2020/01/11|2020/01/11|NB_ZHRX_OTL_CDRM|8.0|H_DECIMAL3|6|6|
HOURLY|1.0|COST_PROCESS_ELEMENT|7.0
METADATA|TimeEntryProperty|LegislativeDataGroupName|AssignmentNumber|EffectiveStartDate|EffectiveEndDate|
PropertyName|PropertyValue|TimeType|TimeCardId|TimeEntryId
MERGE|TimeEntryProperty|Vision Corporation US LDG|E15CDRM|2020/01/11|2020/01/11|NB_ZHRX_OTL_CDRM_State|12|
NB_ZHRX_OTL_CDRM|6|6
Related Topics
• Import Time Card Entries to Payroll
• Process Time Entries in Payroll
235
Guidelines for Loading Calculation Cards

Calculation cards capture values required for payroll calculation of some earnings and deductions, such as absence
payments and involuntary deductions. Various types of calculation cards exist. For example, UK calculation cards
include those for statutory deductions, automatic enrollment in pensions, court orders and student loans, and benets
and pensions. Most legislations support the Calculation Card object. However, the types of calculation cards that are
supported vary by legislation. This topic describes some general considerations that apply to all calculation cards when
you load them using HCM Data Loader. For legislation-specic information, see All White Papers for Oracle Fusion
Applications HCM (Document ID 1504483.1) on My Oracle Support at hps://support.oracle.com.
Each calculation card has one or more components, and each component may have one or more sets of component
details, or value denition overrides. For example, in the UK court orders and student loans calculation card, each
component corresponds to a dierent type of court order. You enter information about that court order in the
component details and value denition overrides.
Calculation cards are used mainly at the level of the payroll relationship. Depending on the legislation, they can also be
used at the level of the payroll statutory unit or tax reporting unit.
Key Support
Calculation Card objects are integration-enabled. They support all key types that HCM Data Loader supports.
Using the Reconcile Integration Keys Process

Source keys are supported for integration-enabled objects only. Any business-object occurrences that were created
before the Calculation Card business object was enabled for integration may not have SourceSystemOwner and
SourceSystemId values. To supply source keys for these objects, run the Reconcile Integration Keys process for
individual components of the Calculation Card business object. This process allocates default source keys to any
instance of a component without a source key.
Tip: If required, you can update these default source keys later using the Source Key object.
Run the Reconcile Integration Keys process once only for each component of the Calculation Card object. This table
lists the components with their integration object names. You select the integration object name when running the
Reconcile Integration Keys process.
Calculation Card Component Integration Object Name
Calculation Card CalculationCard

Card Association CalculationCardAssociations

Component Association

Card Association Detail CalculationCardAssociationDetails

Component Association Detail
236
Calculation Card Component Integration Object Name
Card Component CalculationCardComponents

Calculation Value Denitions ValueDenition

Enterable Calculation Value RangeItem

Component Detail CalculationComponentDetails

Changing Logical Start and End Dates

In general, you can change the rst eective start date and last eective end date of an existing calculation card.
Include the ReplaceFirstEectiveStartDate and ReplaceLastEectiveEndDate aributes in your METADATA line, as
appropriate, and set them to Y. Provide the new values on the EectiveStartDate and EectiveEndDate aributes.
Note: Legislation-specic validations may mean that some changes to logical start and end dates aren't valid.
Deleting Calculation Cards

You can delete all components of the Calculation Card object using HCM Data Loader. When you delete a Calculation
Card component, its child components are deleted automatically. You can also delete individual child components.
Related Topics
• HCM Data Loader: Loading Calculation Cards for Australia (2124649.1)
• HCM Data Loader: Loading Calculation Cards for France (2233630.1)
• HCM Data Loader: Loading Calculation Cards for United Kingdom (2098480.1)
Example of Loading Wage Basis Rules

Use HCM Data Loader to load wage basis rules to determine the earnings that are subjected to a deduction. To illustrate
how wage basis rules aect a tax calculation, let's look at an example where an employee's earnings included in the
wage basis vary, depending upon where the employee lives.
Briany is a salesperson who receives a salary of 2,000 each month. Briany also has a company car she drives. She is
responsible for reporting her personal use of the company car in order to be taxed correctly.
Briany works in her company's East Coast district. She spends 50 percent of her time in New York and 50 percent
of her time in Pennsylvania. The State of New York taxes Briany for her personal use of the company car; however,
Pennsylvania doesn't.
Last month, Briany reported personal use that equated to 100 (50 personal use in New York and 50 personal use in
Pennsylvania).
237
In New York, the imputed earnings, such as personal use of company car amounts are included in the taxable wages.
Whereas, in Pennsylvania, these earnings aren't included in taxable wages.
This table shows the tax calculations that apply for each region.
Region Earnings in Salary Eligible Imputed Taxable Income Deduction Amount

Earnings
New York 1000 50 1050 35

Pennsylvania 1000 50 - Exempt 1000 30

Here are the wage basis rule for this tax calculation.
Region (Reference Value) Primary Classication Secondary Classication Use in Wage Basis?
New York Standard Earnings Regular Y

New York Imputed Earnings Personal Use of Company Car Y

Pennsylvania Standard Earnings Regular Y

Pennsylvania Imputed Earnings Personal Use of Company Car N

Use this TaxabilityRule.dat to load the wage basis rules.

METADATA|TaxabilityRule|EffectiveStartDate|LegislativeDataGroupName|PayrollComponent|PrimaryClassification|
SecondaryClassification|Context1|UsageType
MERGE|TaxabilityRule|2011/1/10|Vision Corp|State Tax|Standard Earnings|Regular|NY|P
MERGE|TaxabilityRule|2011/1/10|Vision Corp|State Tax|Imputed Earnings|Personal Use of Company Car|NY|P
MERGE|TaxabilityRule|2011/1/10|Vision Corp|State Tax|Standard Earnings|Regular|PA|P
MERGE|TaxabilityRule|2011/1/10|Vision Corp|State Tax|Imputed Earnings|Personal Use of Company Car|PA|N
Related Topics
• Wage Basis Rules
Element Entries
Overview of Loading and Rolling Back Element Entries
You use element entries to capture earnings, deductions, absences, and basic benet details for an employee
assignment. For example, you can create element entries for an employee's overtime hours or medical premium
deduction amount.
238
The element entry values hold the necessary values for the element type. For example, a salary entry can contain the
salary value and the salary frequency.
Using HCM Data Loader, you can load element entries and element entry values.
Element Entry Rollback

You can only roll back new element entries where no changes have been made to it since it was created by HCM Data
Loader. If HCM Data Loader identies that the element entry has been updated, the rollback fails. The application
doesn't make an aempt to roll back updates to an existing element entry. Also, it doesn't roll back the deletion of an
existing element entry.
This gure illustrates how you can roll back element entries depending upon whether the entries were loaded using
payroll ows or not.
Use the Import and

Is the element entry Load Data page or
loaded using payroll No HCM Data Loader
flows? Webserivce to roll back
the element entries
Yes
Use the rollback

feature of the flows to
roll back element
entries.
If you submit an element entry using the Initiate Data Loader ow, then you can roll it back using one of the
techniques:
• Payroll Flows
• The Import and Load Data page
• The HCM Data Loader web service
Alternatively, if you didn't submit your element entry using a ow paern, then use the Import and Load Data page to
roll them back.
Rollback and Events

When an element entry is rolled back, the application also rolls back any unprocessed events and notications.
Consider these scenarios that explain the impact of a roll back on events.
• If the event has an unprocessed status, then the application removes the event. If the event is already
processed, then the application lets it stay.
• If you created an element entry, then application removes the event. The application doesn't remove other
types of element entry events, such as an update element entry event.
239
• If you updated an element entry, then the application doesn't delete that event.
Related Topics
• Enable Automatic, Multiple, or Additional Element Entries Options
• Options to Determine an Element's Latest Entry Date
• Default Values for Element Entries
How You Roll Back Element Entries

You can roll back element entries by using payroll ows and the Import and Load Data task.
Use Payroll Flow To Roll Back Entries

If you used payroll ows to load an element entry, then you can roll it back using the ow's rollback feature. Use the
Initiate Data Loader ow paern to roll back element entries that you uploaded using the ow paern.
These steps describe how you initiate a payroll ow to upload element entries.
1. As the rst step, you create the ElementEntry.dat le to load your element entries and its values. Also, you must
compress it to a le name of your choice.
2. Using the File Import and Export task, you upload the dat le to the Oracle Web Center Content Server. Enter
the account as hcm/dataloader/import. You must make a note of the Content ID.
3. From the Checklist or Data Exchange work area, you submit the Initiate Data Loader ow to load and submit
the element entries data set. When submiing the ow, provide the Content ID from the previous step.
To roll back your element entry data, on the Payroll Flow page, select the Initiate Data Loader ow. Select Mark as
Complete from the Actions menu. In the Warning dialog box, click Continue. The application rolls back the newly
created element entries.
Use Import and Load Data Task To Roll Back Entries

1. Navigate to the Data Exchange work area.
2. Select Import and Load Data.
3. Search for and select the data set with the element entries to roll back.
4. Click Total Objects.
5. On the Object Status page, click Schedule Request.
6. In the Schedule Request dialog box, Action eld, select Roll Back.
7. Click Submit.
Related Topics
Example of Loading a Recurring Element Entry With an Open End

Date
Lisa Jones has been asked to work from the company's headquarters from 01-Apr-2019 until further communication. As
part of this assignment, she's paid a Commutation Allowance of 1000 per pay period.
240
Load the element entry details for Lisa, as shown in this table:
Parameter Value

Element Name Commutation Allowance

Assignment Number E3141464

Start Date 01-Apr-2019

Load the element entry values, as shown in these tables:
Entry Value 1
Parameter Value




Input Value Name PRD

Screen Entry Value 1000

Entry Value 2
Parameter Value



241
Parameter Value



This .dat le creates the element entry values.

METADATA|ElementEntry|EffectiveStartDate|EffectiveEndDate|ElementTypeId|EntryType|CreatorType|SourceSystemOwner|
SourceSystemId|HrAssignmentId(SourceSystemId)
MERGE|ElementEntry|2016/11/15|4712/12/31|300100003068055|E|F|HRC_SQLLOADER|12351_ELEM_ENTR|12351_EMP_ASG
METADATA|ElementEntryValue|EffectiveStartDate|EffectiveEndDate|InputValueId|ScreenEntryValue|
ElementEntryId(SourceSystemId)|SourceSystemOwner|SourceSystemId|HrAssignmentId(SourceSystemId)
MERGE|ElementEntryValue|2016/11/15|4712/12/31|300100003068067|20000|12351_ELEM_ENTR|HRC_SQLLOADER
Related Topics
Example of Loading a Recurring Element Entry With a Specic End

Date
Lisa Jones has been asked to work from the company's headquarters from 01-Apr-2019 until further communication.
As part of this assignment, she's paid a Commutation Allowance of 1000 per pay period. The deputation is only for 3
months and hence it has to be end dated as on 30-Jun-2019.
Load these element entry details, as shown in this table:
Parameter Value




This dat le creates a recurring element entry with a specic end date.
METADATA|ElementEntry|CreatorType|EffectiveEndDate|EffectiveStartDate|ElementName|LegislativeDataGroupName|
EntryType|AssignmentNumber|MultipleEntryCount
MERGE|ElementEntry|F|2019/06/30|2019/04/01|Commutation Allowance|Vision Corp|E|E300100003143464|1
242
The MultipleEntryCount aribute is optional when you use source keys to load data.
As these tables show, load the element entry values:
Entry Value 1
Parameter Value




End Date 30-Jun-2019

Input Value Name Periodicity

Screen Entry Value Periodically

Entry Value 2
Parameter Value





Input Value Name Amount


243
This .dat le creates the element entry values.

METADATA|ElementEntry|EffectiveStartDate|EffectiveEndDate|ElementTypeId|EntryType|CreatorType|SourceSystemOwner|
SourceSystemId|HrAssignmentId(SourceSystemId)
MERGE|ElementEntry|2016/11/15|4712/12/31|300100003068055|E|F|HRC_SQLLOADER|12351_ELEM_ENTR|12351_EMP_ASG
METADATA|ElementEntryValue|EffectiveStartDate|EffectiveEndDate|InputValueId|ScreenEntryValue|
ElementEntryId(SourceSystemId)|SourceSystemOwner|SourceSystemId|HrAssignmentId(SourceSystemId)
MERGE|ElementEntryValue|2016/11/15|4712/12/31|300100003068067|20000|12351_ELEM_ENTR|HRC_SQLLOADER|
12351_ELEM_ENTR_VAL|12351_EMP_ASG
Related Topics
Example of How To End Date a Recurring Element Entry

To update the last eective end date, include the ReplaceLastEffectiveEndDate aribute in your METDATA line. Provide
a Y value to indicate that the EffectiveEndDate supplied is a change to the existing logical end date of your record. You
must supply a record for the element entry and every element entry value.
Let's consider the same example where Lisa Jones was asked to work from the company's headquarters from 01-
Apr-2019 until further communication. When Lisa's deputation ended on 30-Jun-2019, the company decides to stop the
allowance that it gave as part of this assignment.
Load these element entry values, as shown in the table.
Parameter Value

Element Commutation Allowance




Multiple Entry Count 1

Load the element entry values, as shown in the tables.
Entry Value 1
244
Parameter Value


Input Value Name Periodicity




Screen Entry Value PRD


Entry Value 2
Parameter Value








Use this dat le to end date the Commutation Allowance eective from 30-Jun-2019 and the element entry values.
245
EntryType|AssignmentNumber|MultipleEntryCount|ReplaceLastEffectiveEndDate
MERGE|ElementEntry|F|2019/06/30|2019/04/01|Commputation Allowance|Vision Corp|E|E3141464|1|Y
METADATA|ElementEntryValue|EffectiveEndDate|EffectiveStartDate|ElementName|LegislativeDataGroupName|
InputValueName|ScreenEntryValue|AssignmentNumber|MultipleEntryCount|ReplaceLastEffectiveEndDate|EntryType
MERGE|ElementEntryValue|2019/06/31|2019/04/01|Commputation Allowance|Vision Corp|Periodicity|Periodically|
E300100003143464|1|Y|E
MERGE|ElementEntryValue|2019/06/30|2019/04/01|Commutation Allowance|Vision Corp|Amount|1000|E300100003143464|1|
Y|E
Related Topics
Example of Deleting an Element Entry

Use HCM Data Loader to delete element entries. As you can't recover deleted records, you must take caution when
deleting them. Don't aempt to delete an element entry and create an entry for the same element, assignment and date
in the same le.
John Gorman is a worker in the Administration Department of Vision Corp. Assuming that he belongs to the Sales
department, the company wrongly awards an incentive to him. Using HCM Data Loader, you can delete the sales
incentive element entry.
This le deletes these element entry values.

DELETE|ElementEntry|F|4712/12/31|2019/04/01|Incentive Compensation|Vision Corp|E|E3141464|1
Related Topics
Example of Loading Multiple Occurrences of the Same Element

Entry in the Same Time Period
Bob traveled from his work location to client's oce on 04-Jun-2019 and 11-Jun-2019 for meetings with clients. He is
reimbursed 40 and 50 respectively as Transport Fare along with his salary on 15-Jun-2019. He is a as part of the semi-
monthly payroll processing cycle.
Using HCM Data Loader, load these element entry values. This is the rst occurrence of the element entry and the
MultipleEntryCount aribute will have value 1.
This table shows the element entry values to load:
Parameter Value
246
Parameter Value

Element Name Transportation Allowance


Start Date 04-Jun-2019


This dat le creates the element entry.

MERGE|ElementEntry|F|2019/06/04|2019/06/04|Transporation Allowance|Vision Corp|E|E3141464|1
These tables show the element entry values to load:
Entry Value 1
Parameter Value







Entry Value 2
Parameter Value
247
Parameter Value







InputValueName|ScreenEntryValue|AssignmentNumber|MultipleEntryCount|EntryType
MERGE|ElementEntryValue|2019/06/04|2019/06/04|Transporation Allowance|Vision Corp|Periodicity|PRD|E3141464|1|E
MERGE|ElementEntryValue|2019/06/04|2019/06/04|Commutation Allowance|Vision Corp|Amount|40|E3141464|1|E
Using HCM Data Loader, load these element entry values. This is the second occurrence of the element entry and the
MultipleEntryCount aribute will have value 2.
This table shows the element entry values to load.
Parameter Value





This dat le creates the element entry.

MERGE|ElementEntry|F|2019/06/11|2019/06/11|Transporation Allowance|Vision Corp|E|E3141464|2
These tables show the element entry values to load.
248
Entry Value 1
Parameter Value







Entry Value 2
Parameter Value







InputValueName|ScreenEntryValue|AssignmentNumber|MultipleEntryCount|EntryType
MERGE|ElementEntryValue|2019/06/04|2019/06/04|Transporation Allowance|Vision Corp|Periodicity|PRD|E3141464|2|E
MERGE|ElementEntryValue|2019/06/04|2019/06/04|Commutation Allowance|Vision Corp|Amount|50|E3141464|2|E
249
Related Topics
250
Integrating with HCM Initializing and Adjusting Balances
16 Initializing and Adjusting Balances
Balance Initializations
Overview
When migrating payroll data from another application into cloud payroll, you might have to set the initial balance
values. To do this, you can use HCM Data Loader to load balance values into batch views.
After loading the balance values, you submit the Load Initial Balances process. The process validates the batch data,
and then processes the batch to load the balance data. It then creates balance adjustments to set the required balance
values.
For each balance to initialize, the Load Initial Balances process denes these elements automatically with Balance
Initialization classication. And adds them to the balance as balance feeds.
Note: You can't initialize balances after the payroll is run for the employee. In such a case, you will have to roll
back the payroll run or do a balance adjustment.
Example
In the middle of the year, your company hired a group of employees as part of an acquisition. The original company
already paid them their earnings and withheld their taxes. In your company's ongoing payroll, you can initialize these
employees' payroll balances for that year. This way, you ensure that all further statutory reports are accurate for the
entire year and not just for the period they worked in your company.
As this image shows, you can initialize the total earnings balances for period-to-date, quarter-to-date, and year-to-date
as of 18-Jun.
Initial balance values in the interface tables HCM Data Loader
Total_Earnings_PTD = 100
18-Jun Total_Earnings_QTD = 250
Total_Earnings_YTD = 500
1-Jun
This image shows the initializing results as of 18-Jun.
251
Initialization Results
1-Jan 1-Apr 1-Jun
Start of the Start of the Start of the

year quarter pay period
Total_Earnings_QTD = 150
Use the InitializeBalanceBatchHeader.dat le to create the VisionBatch batch.

METADATA|InitializeBalanceBatchHeader|LegislativeDataGroupName|BatchName|UploadDate
MERGE|InitializeBalanceBatchHeader|Vision Corporation US LDG|VisionBatch|2018/06/18|
In the InitializeBalanceBatchLine.dat le you initialize these three balance values for the total earnings balance.
Balance Value
Total_ Earnings_PTD 100

Total_ Earnings_QTD 250

Total_ Earnings_YTD 500

METADATA|InitializeBalanceBatchLine|LegislativeDataGroupName|BatchName|LineSequence|UploadDate|
PayrollRelationshipNumber|PayrollName|BalanceName|DimensionName|Value
MERGE|InitializeBalanceBatchLine|Vision Corporation US LDG|VisionBatch|1|2018/06/18|10001|Monthly Payroll|
Total Earnings|Core Relationship Period to Date|100
Total Earnings|Core Relationship Quarter to Date|250
Total Earnings|Core Relationship Year to Date|500
252
When you run the Load Initial Balances process, it sets the values for each balance relative to the upload date. For
example, for an upload date of June 18, the balance values include all payment dates up to and including June 18. The
process creates date-eective balance entries (adjustments) to ensure the legislative balances are correct.
As this table shows, the balance initialization process creates adjustments on the rst day of the time period relevant to
each dimension.
Adjustment Date Adjusted Balances Adjustment Value
1 June (Start of the pay period) • Total_Earnings_PTD 100

• Total_Earnings_QTD
• Total_Earnings_YTD
1 April (Start of the quarter) • Total_Earnings_QTD 150

• Total_Earnings_YTD
1 Jan (Start of the year) Total_ Earnings_YTD 250

Steps to Initialize Balances

You can use HCM Data Loader to load the initial balance values before you process the employee in a payroll. Before
you start initializing the balances, group your employees into batches.
This image shows the steps involved in initializing balances.
Here are the steps that you do to initialize balances.

1. As the rst step, you identify the balances to initialize. You can initialize legislative and user-dened balances.
Each of the balances has its own initialization requirements.
2. Map the balances into the Global Payroll cloud. Remember, one legacy balance can feed one or more cloud
balances. Also, many legacy balances can feed one cloud balance.
3. Extract legacy balances to load into the payroll cloud.
253
4. Load balance values to PAY_BAL_BATCH_HEADERS and PAY_BAL_BATCH_LINES interface tables by using

these two separate HDL les.
◦ InitializeBalanceBatchHeader.dat
◦ InitializeBalanceBatchLine.dat
5. Use the Load Initial Balances process from the Payroll Calculation work area to validate and transfer data
from the batches into Global Payroll. You can also use the process to roll back the batch if you need to correct
and reprocess errors. This process creates date-eective balance entries, or adjustments to ensure that the
balances are correct from the upload date.
6. Check the balance load results to identify and correct any errors in the balances. Use the View Person Process
Results and View Payroll Process Results tasks from the Payroll Calculation work area to reconcile the loaded
balances.
Example of Loading Initial Balances

In this example, you create balance initialization records to initialize an employee's federal and state-level balances.
When initializing year-to-date and quarter-to-date balances, you also initialize any related balances. For example, when
initializing FIT Withheld balance, related balances such as FIT Exempt and FIT Gross too are initialized.
Load the Balance Batch Header

Use the InitializeBalanceBatchHeader.dat le to create the VisionBatch batch.
METADATA|InitializeBalanceBatchHeader|BatchName|UploadDate|LegislativeDataGroupName
MERGE|InitializeBalanceBatchHeader|VisionBatch|2015/02/05|PM US Sun Power
Load Batch Lines Data

Load these details to initialize the YTD salary balance.
Data Column Value
Line Sequence 1

Balance PM US Sun Power Salary

Dimension Assignment Tax Unit Year to Date

Balance Value 6000.00

Load these details to initialize the QTD salary balance.
Data Column Value
Line Sequence 2
254
Data Column Value

Balance PM US Sun Power Salary

Dimension Assignment Tax Unit Quarter to Date


Load these details to initialize the YTD FIT balance.
Data Column Value
Line Sequence 3

Balance FIT Withheld

Dimension Relationship Tax Unit Year to Date


Load these details to initialize the QTD FIT balance.
Data Column Value
Line Sequence 4

Balance FIT Withheld

Dimension Relationship Tax Unit Quarter to Date


Load these details to initialize the YTD Medicare balance.
Data Column Value
Line Sequence 5

255
Data Column Value
Balance Medicare Employee Withheld

Dimension Relationship Tax Unit Year to Date

Balance Value 87.00

Load these details to initialize the QTD Medicare balance.
Data Column Value
Line Sequence 6

Balance Medicare Employee Withheld

Dimension Relationship Tax Unit Quarter to Date

Balance Value 87.00

Load these details to initialize the YTD SIT balance.
Data Column Value
Line Sequence 7

Balance SIT Withheld

Dimension Relationship Tax Unit,State Year to Date


Area One 6 (Colorado)

Load these details to initialize the QTD SIT balance.
Data Column Value
Line Sequence 8
256
Data Column Value

Balance SIT Withheld

Dimension Relationship Tax Unit

State Year to Date


Area One 6 (Colorado)

In the InitializeBalanceBatchLine.dat le, you initialize the YTD and QTD values for these balances.
• Salary
• FIT
• Medicare
• SIT
METADATA|InitializeBalanceBatchLine|BatchName|LineSequence|PayrollName|PayrollRelationshipNumber|TermNumber|
AssignmentNumber|BalanceName|DimensionName|TaxUnitName|AreaOne|Value
MERGE|InitializeBalanceBatchLine|VisionBatch|1|PM US Sun Power Weekly|955160008191951|ET955160008191951|
E955160008191951|PM US Sun Power Salary|Assignment Tax Unit Year to Date|PM US Sun Power Inc||6000
E955160008191951|PM US Sun Power Salary|Assignment Tax Unit Quarter to Date|PM US Sun Power Inc||6000
E955160008191951|FIT Withheld|Relationship Tax Unit Year to Date|PM US Sun Power Inc||954.06
E955160008191951|FIT Withheld|Relationship Tax Unit Quarter to Date|PM US Sun Power Inc||954.06
E955160008191951|Medicare Employee Withheld|Relationship Tax Unit Year to Date|PM US Sun Power Inc||87
E955160008191951|Medicare Employee Withheld|Relationship Tax Unit Quarter to Date|PM US Sun Power Inc||87
E955160008191951|SIT Withheld|Relationship Tax Unit,State Year to Date|PM US Sun Power Inc|6|264.00
E955160008191951|SIT Withheld|Relationship Tax Unit,State Quarter to Date|PM US Sun Power Inc|6|264.00
Balance Adjustments
Overview
For a given worker, you can use HCM Data Loader to adjust payroll balances as of a certain date. The balance
adjustment process creates a run result that adjusts one or more balances depending upon the balance fed by the
element input value.
You can decide whether to cost the balance adjustment results or not. Additionally, you can also decide whether you
want the adjustment results to be paid or not. You can pay the employee when you run the next pre-payment process
257
that includes these adjustment run results. Further, the process assigns the results to the appropriate payment method
as per the worker's payment method setup.
Corrections to Balance Initialization

Recollect the scenario where a group of employees were hired through an acquisition in the middle of a year. The
original company already paid them their earnings and withheld their taxes. In your company's ongoing payroll, you
initialize these employees' payroll balances for that year. As you can't initialize balances after the payroll is run for the
employee, you adjust the balances for them.
These scenarios describe how you can adjust balances after the rst payroll run.
• The FIT Withheld balance for Andrew was initialized 100 less than what it should have been. The Payroll
Manager makes a balance adjustment of 100 for Andrew using the payroll element that feeds the FIT Withheld
balance.
• Jane Reifer was omied during the balance initialization process and none of her balances were loaded. The
Payroll Manager can adjust Jane's omied balances.
Third-Party Gross to Net calculations

There are several kinds of earnings that are managed by a third-party. For example, a company could use a third-party
to handle disability payments, stock option payouts, moving and relocation expenses. In these cases, the employer still
does the reporting of wages or taxes. Also, they adjust the balances by importing the incremental values, which the
third-party calculates and withholds, to the application. The company can cost these balance adjustments as the third-
party has already made payments to the employee.
Let's consider this example. Prasad is on a long term disability leave and his employer uses a third-party to manage his
disability leave payments.
The third-party does these tasks.

• Calculates Prasad's gross disability earnings as 5000 for the pay period.
• Withholds FIT, SS and Medicare taxes as 1000, 500 and 250, respectively.
• Pays him a net amount of 3250.
The Payroll Manager imports these values as balance adjustments for the balances.
Retrospective Changes Not Covered by RetroPay

Typically, you use the retroactive pay process to handle retroactive changes to data that impacts payroll calculation
results. However, not all elements support Retro Pay. For example, tax deductions aren't enabled for retroactive pay.
In such cases, for a retroactive change that impacts tax calculations, you can reect the changes through balance
adjustments.
Let's consider this example. John lives in California and pays his taxes there. He is on a biweekly payroll and is withheld
500 of the State Income Tax for the two weeks of earnings. In the 16 2018 Biweekly period, he worked in Texas, but
didn't report the time on his time card. He should have been withheld SIT for 200 to Texas instead of the 500 to
California.
In John's process results for the 16th payroll run, the payroll manager adjusts the existing SIT Withheld of 500 to
California by doing these actions:
• Make a 200 adjustment to Work State Income Tax for the state of Illinois.
• Negate the original run result for the amount 500.
258
Zeroing out Balances for Terminations

Here's an example where you zero out the balances for a terminated employee.
James Nance is terminated as of 9/15/2018 with a nal close date of 9/30/2018. The payroll manager would like to zero
out all arrears balances for James as of 9/30. Upon termination, the manager runs the deductions report and nds that
James has these arrears balances as of 9/30.
• Car Loan Deduction 2000.00

• Student Loan Deduction 500.00
For the Arrears Adjustment element, the payroll manager loads -2000.00 and -500 as input values. These values zero
out the Inception to Date arrears balances.
Related Topics
• Examples of Balance Exceptions
Steps to Adjust Balances

You can use HCM Data Loader to load balance adjustments in the batch mode.
Before You Begin

Before you adjust balances, do these tasks:
• Create the appropriate eligibility links for the elements that you're adjusting. For example, to adjust base
elements, it must contain an eligibility link.
• Populate the Balance Date column if the balance dimension requires an entry.
259
This image shows the steps involved in adjusting balances.
Determine
Balances to Adjust
Create Batch
Header and Detail
Lines
Import and Load

Data
No
Override Costing
Segments
Yes
Create Cost
Allocation dat Files
Run the Adjust

Multiple Balances
process
Verify the Balance

Adjustment Results
Perform these steps to adjust your balances.
1. Determine the balances that require an adjustment.

2. Create the batch header and detail lines in the dat les. Use the balance adjustment header to adjust balances
in bulk. The balance adjustment lines contain the individual adjustment lines for the balance adjustment group.
3. Import and load the data using the HCM Data Loadprocess. This process creates a run result by adjusting one
or more balances. And this adjustment depends upon the balance fed by the element input value.
4. Decide whether the balance adjustment results must be costed or not. If you want to cost your balance
adjustments, you can create the cost allocation dat les.
260
Note: Not all costed adjustments need the cost allocation les. Only those costed
adjustments that need one or more costing segments to be overridden for the adjustment
element entry need the allocation le
5. From Payroll Calculation work area, run the Adjust Multiple Balances process to create balance adjustment
element entries for each line within the data set. In this process, you provide the batch name that you used in
the HCM Data Loader le.
6. Verify the balance results of adjustments.
Related Topics
Balance Adjustment Record Types

Use the Balance Adjustment Header and the Balance Adjustment Line business objects to upload the balance
adjustment details.
261
This image shows the hierarchy of components that are applicable to the batch data.
Component: Balance Adjustment Header
Component: Balance Adjustment Group
Component: Balance Adjustment Line
Component: Balance Adjustment Value
Component: Balance Adjustment Line repeat as needed
Component: Balance Adjustment Value repeat as needed
This table summarizes the various balance adjustment components:
Component What It's
Balance Adjustment Header The header for the batch process that's used when adjusting balances in bulk. Supply one
batch header record for each group.

Balance Adjustment Group A group of balance adjustments within the batch header that correspond to a unique
combination of payroll, consolidation group, and eective date. Supply one group record for
each batch header. At this time, you may only have one group record per batch.

262
Component What It's
Balance Adjustment Line Individual adjustment lines for the balance adjustment group. Each line corresponds to a
specic adjustment element entry for a worker and the associated contexts for the adjustment
run result.

Balance Adjustment Value Individual adjustment values for each balance adjustment line. Each value corresponds to a
specic adjustment entry value for a worker and adjusts the balances it feeds.

Related Topics
Example of Loading Balance Adjustments

Vision Corp wants to create balance adjustment records to adjust the FIT Withheld balances for two of their employees.
Using HCM Data Loader, they want to increase the withheld balance by 10.
Load the Balance Adjustment Header

Use this BalanceAdjustmentHeader.dat le to create the batch header.
METADATA|BalanceAdjustmentHeader|LegislativeDataGroupName|BatchName
MERGE|BalanceAdjustmentHeader|US LDG|FIT Adjustments
METADATA|BalanceAdjustmentGroup|LegislativeDataGroupName|BatchName|EffectiveDate|PayrollName|
ConsolidationSetName|PrepayFlag|BalanceAdjCostFlag
MERGE|BalanceAdjustmentGroup|US LDG|FIT Adjustments|2019/04/30|Vision US Weekly|Vision Weekly|N|N
Load the Balance Adjustment Line and Value

For Employee 1 with Assignment number E3263769, load these details:
Data Column Value
Line Sequence 1


Payroll Vision US Weekly

Consolidation Group Vision Weekly


Include adjustment in costing process No

263
Data Column Value
Federal Income Tax, Tax Calculated 10.00

Include adjustment in payment No

balance

For Employee 2 with Assignment number E5746169, load these details:
Data Column Value
Line Sequence 2

Eective Date 2010-04-30

Payroll Vision US Weekly

Consolidation Group Vision Weekly


Include adjustment in costing process No

Federal Income Tax, Tax Calculated 10.00

Include adjustment in payment No

balance

Use this BalanceAdjustmentLine.dat le to create the batch lines.

METADATA|BalanceAdjustmentLine|LegislativeDataGroupName|BatchName|PayrollName|ConsolidationSetName|
EffectiveDate|BatchLineSequence|AssignmentNumber|ElementName|TaxReportingUnitName
MERGE|BalanceAdjustmentLine|US LDG|FIT Adjustments|Vision US Weekly|Vision Weekly|2019/04/30|1|E263769|
Federal Income Tax|US Tax Reporting Unit
MERGE|BalanceAdjustmentLine|US LDG|FIT Adjustments|Vision US Weekly|Vision Weekly|2019/04/30|2|E746169|
Federal Income Tax|US Tax Reporting Unit
METADATA|BalanceAdjustmentValue|LegislativeDataGroupName|BatchName|PayrollName|ConsolidationSetName|
EffectiveDate|BatchLineSequence|InputValueName|EntryValue|ElementName
MERGE|BalanceAdjustmentValue|US LDG|FIT Adjustments|Vision US Weekly|Vision Weekly|2019/04/30|1|Tax
Calculated|10|Federal Income Tax
MERGE|BalanceAdjustmentValue|US LDG|FIT Adjustments|Vision US Weekly|Vision Weekly|2019/04/30|2|Tax
Calculated|10|Federal Income Tax
264
Integrating with HCM Loading Payment Methods
17 Loading Payment Methods
Examples of Loading Banks

A bank is a nancial institution that can have multiple branches. External bank accounts are associated with bank
branches. Bank, Bank Branch, and External Bank Account are business objects whose details are stored in non-HCM
tables. However, you can load them using HCM Data Loader. This topic describes aspects of the Bank object that you
must understand to load banks successfully.
Loading Banks
You load bank data in a Bank.dat le for processing by HCM Data Loader. To provide a unique reference to a bank when
you create it, you must supply either the Bank Name or the Bank Number aribute. You must also supply the Country
Code aribute.
This example Bank.dat le creates a Bank object using the Bank Name and Country Code user keys. It also supplies the
Bank Number aribute.
METADATA|Bank|BankName|BankNumber|CountryCode
MERGE|Bank|Vision Bank|100001A|CA
Deleting Banks
You can't delete Bank objects using HCM Data Loader. However, you can inactivate banks that are either no longer
required or were entered in error. This feature, which isn't available on the Manage Banks pages, enables you to
maintain an audit trail.
This example Bank.dat le provides an end date for a Bank object to inactivate it. To identify an existing bank uniquely,
you can use the Country Code and either the Bank Name or the Bank Number.
METADATA|Bank|BankNumber|CountryCode|EndDate
MERGE|Bank|100001A|CA|2016/03/01
Examples of Loading Bank Branches

A bank is a nancial institution that can have multiple branches. External bank accounts are associated with bank
branches. Bank, Bank Branch, and External Bank Account are business objects whose details are stored in non-HCM
tables. However, you can load them using HCM Data Loader. This topic describes aspects of the Bank Branch object that
you must understand to load bank branches successfully.
Loading Bank Branches

Bank branch data must be supplied in a BankBranch.dat le for processing by HCM Data Loader. The Bank Branch
Number aribute, for which the eld name on the Manage Bank Branches page varies by country, uniquely identies
the bank branch. It may be a required aribute, depending on country-specic validations.
265
You must supply one of the following combinations of aributes to provide a unique reference to the bank branch and
the associated bank:
• Bank Branch Name, Country Code, and either Bank Name or Bank Number
• Bank Branch Number, Country Code, and either Bank Name or Bank Number
This example BankBranch.dat le creates a Bank Branch object using the Bank Branch Number, Bank Name, and
Country Code user keys.
METADATA|BankBranch|BankBranchNumber|BankBranchName|BankName|CountryCode|EftSwiftCode
MERGE|BankBranch|111111A|Toronto 3|Vision Bank|CA|12345678
Deleting Bank Branches

You can't delete Bank Branch objects using HCM Data Loader. However, you can inactivate bank branches that are
no longer required or were entered in error. This feature, which isn't available on the Manage Bank Branches pages,
enables you to maintain an audit trail.
This example BankBranch.dat le provides an end date to inactivate a bank branch.
METADATA|BankBranch|BankBranchNumber|BankName|CountryCode|EndDate
MERGE|BankBranch|111111A|Vision Bank|CA|2015/04/01
Examples of Loading External Bank Accounts

An external bank account record holds the details of a bank account at a bank branch. Bank accounts are used by
payment methods to make payments to a person. Bank, Bank Branch, and External Bank Account are business objects
whose details are stored in non-HCM tables. However, you can load them using HCM Data Loader. This topic describes
aspects of the External Bank Account object that you must understand to load external bank accounts successfully.
Bank and Bank Branch

Before you can create an External Bank Account object, you must create both the bank and the bank branch where the
bank account is held.
Loading External Bank Accounts

You supply external bank account data in the ExternalBankAccount.dat le for processing by HCM Data Loader.
Multiple user keys are supported for referencing the external bank account. For details of these user keys, view the
External Bank Account object on the Business Object Details page.
The External Bank Account Owner component identies a person or third party to whom the account belongs. A bank
account can be associated with multiple owners, of whom one must be the primary owner. Use the discriminator
ExternalBankAccountOwner to load External Bank Account Owner components. Set the PrimaryFlag aribute of the
relevant component to Y to identify the primary owner. Multiple user keys are supported for referencing the external
bank account owner. For details of these user keys, view the External Bank Account Owner component on the Business
Object Details page.
Note: You can't load external bank accounts for pending workers.
266
This example ExternalBankAccount.dat le creates an External Bank Account component and associates it with two
owners, one of whom is the primary owner.
METADATA|ExternalBankAccount|BankNumber|BankBranchNumber|CountryCode|AccountNumber|IBAN|AccountName|
CurrencyCode
MERGE|ExternalBankAccount|100001A|111111A|CA|12345678|CA23 ANBK 3350 1234 5678 20|J and P Smith|USD
METADATA|ExternalBankAccountOwner|BankNumber|BankBranchNumber|CountryCode|AccountNumber|CurrencyCode|
PersonNumber|PrimaryFlag
MERGE|ExternalBankAccountOwner|100001A|111111A|CA|12345678|USD|121011|Y
MERGE|ExternalBankAccountOwner|100001A|111111A|CA|12345678|USD|126231|N
Note: You can only load ExternalBankAccount in single threaded mode, even if you provide multiple load
threads.
Inactivating External Bank Accounts

You can delete an External Bank Account object, and recreate it if necessary, using HCM Data Loader. Alternatively,
you can make the bank account inactive. This example ExternalBankAccount.dat le makes an external bank account
inactive by including the InactiveFlag aribute and seing it to Y.
METADATA|ExternalBankAccount|BankNumber|BranchNumber|CountryCode|CurrencyCode|AccountNumber|InactiveFlag
MERGE|ExternalBankAccount|100001A|111111A|CA|USD|12345678|Y
Organization Payment Methods

Overview of Loading Organization Payment Methods
An organization payment method denes the payment methods for a legislative data group. Payment methods specify
a payment type, such as check or direct deposit, a source bank account, and other details.
Using HCM Data Loader, load at least one organization payment method for each combination of legislative data group,
payment type, and currency.
To load an organization payment method, you dene at least one payment source. If you load multiple payment
sources, then you can create payment rules. The payment rules determine which payment source to use for each TRU
and also validate or process the distribution of payments.
Create payment method rules with eective start dates on or before the start dates of other objects that refer to your
payment method rule.
This gure shows the steps to create an Organization Payment Method.
1. Create an Organization Payment Method.

2. Load the payment sources to associate bank accounts and other sources of funds with it.
3. Dene payment rules.
267
Related Topics
• Organization Payment Methods
• How Payment Methods and Payroll Denitions Work Together
Example of Loading Organization Payment Methods

In this example, you create an Organization Payment Method and dene payment sources and payment rules.
You do these steps:
1. Create an Organization Payment Method HDL_OPM_TRU for the Vision Corporation US LDG LDG.
2. Load the two payment sources to associate bank accounts and other sources of funds with it.
3. Dene the payment rules to determine the appropriate payment source based on tax reporting unit.
As this image shows, for your organization payment method, you create the payment sources and rules.
Organization Payment Method

HDL_OPM_TRU
Payment Sources Payment Rules

Sets this payment
HDL_OPM_TRU_PS_DFLT
source as default
HDL_OPM_TRU_DFLT
HDL_OPM_TRU_PS_VISIO
HDL_OPM_TRU_VISION
N
Associates this
payment source with
the Vision Corp TRU
Create an Organization Payment Method

These payment method lines create an organization payment method HDL_OPM_TRU:
METADATA|OrganizationPaymentMethod|SourceSystemOwner|SourceSystemId|LegislativeDataGroupName|
EffectiveStartDate|OrganizationPaymentMethodName|OrganizationPaymentMethodCode|CurrencyCode|PaymentTypeCode
MERGE|OrganizationPaymentMethod|VISION|HDL_OPM_TRU|Vision Corporation US LDG|2018/01/01|HDL Organization
Payment Method with TRU rule|HDL_ORG_PAYMENT_METHOD_TRU|USD|EFT
268
Create Payment Sources

These DAT les to load the two payment sources:
Payment Source Use To
HDL_ OPM_ TRU_PS_VISION Pay workers or third-party people based in the Vision Corporation tax reporting unit.

HDL_ OPM_ TRU_PS_DFLT Pay workers in all other tax reporting units. Set this payment source as the default payment
source.

METADATA|PaymentSource|SourceSystemOwner|SourceSystemId|LegislativeDataGroupName|EffectiveStartDate|
OrganizationPaymentMethodId(SourceSystemId)|PaymentSourceCode|PaymentSourceName|BankAccountName|
BankReferenceEFT|CompanyReferenceEFT
MERGE|PaymentSource|VISION|HDL_OPM_TRU_PS_DFLT|Vision Corporation US LDG|2018/01/01|HDL_OPM_TRU|HDL_DEFLT|

HDL Payment Source|Corporate Payroll Account-202|808123663|456102113
MERGE|PaymentSource|VISION|HDL_OPM_TRU_PS_VISION|Vision Corporation US LDG|2018/01/01|HDL_OPM_TRU|

HDL_VISION|HDL Payment Source Vision|Vision Nacha Account-202|234506332|567890123
Create Payment Rules

Finally, use the DAT le to load these two payment rules.
Payment Rule What It Does
HDL_ OPM_TRU_DFLT Sets the payment source HDL_ OPM_ TRU_PS_DFLT as the default source.

HDL_ OPM_TRU_VISION Associates the payment source HDL_ OPM_ TRU_ PS_VISION with the Vision Corporation TRU.

METADATA|PaymentMethodRule|SourceSystemOwner|SourceSystemId|LegislativeDataGroupName|EffectiveStartDate|
PaymentSourceId(SourceSystemId)|DefaultFlag|TaxReportingUnitName
MERGE|PaymentMethodRule|VISION|HDL_OPM_TRU_DFLT|Vision Corporation US LDG|2018/01/01|HDL_OPM_TRU_PS_DFLT|Y|
MERGE|PaymentMethodRule|VISION|HDL_OPM_TRU_VISION|Vision Corporation US LDG|2018/01/01|

HDL_OPM_TRU_PS_VISION|N|Vision Corporation
Note: When updating these existing components, you can't change either the rst eective start date or last
eective end date:
• Organization payment method
• Payment source
• Payment method rule
Related Topics
• Organization Payment Methods
• Set Up Payment Sources in Organization Payment Methods
269
Example of Loading Personal Payment Methods

Use HCM Data Loader to load payment method details for a person. Personal payment methods associate people to
specic payment method, currency, and payment source.
In this example, Jane signed up for direct deposit of her pay check. Eective January 1, 2016, you create a payment
method for her.
As this image shows, loading a personal payment method is a four step process.
Prerequisites
Associate Load Organization

Load Organization
Employee With Payment Method
Payment Method
Payroll
Load Bank Account

Details For
Employee
Before creating a personal payment method, do these tasks:
• Associate Jane with a payroll.

• Load the organization payment method.
• Create the bank account the personal payment method will pay into.
As Jane's payment type is Direct Deposit, load these bank account details for her account:
Bank Account Value
Account Number 1265896441

Bank Name Bank of America

Routing Transit Number (Bank 122122125

Branch Number)
270
Bank Account Value
Use the PersonalPaymentMethod.dat le to create a personal payment method. This le deposits only the rst
$10000 into the bank account.
METADATA|PersonalPaymentMethod|LegislativeDataGroupName|AssignmentNumber|PersonalPaymentMethodCode|
EffectiveStartDate|PaymentAmountType|Amount|ProcessingOrder|OrganizationPaymentMethodCode|Percentage|BankName|
BankBranchNumber|BankCountryCode|BankAccountNumber
MERGE|PersonalPaymentMethod|Vision Corporation US LDG|234299A|PPM3_HDL_NO_PO|2016/01/01|M|10000||PM US Sun
Power Check||Bank of America|511000025|US|1265896441
Related Topics
• Congure Payment Method Preferences
Example of Loading Third-Party Organization Payment

Method
Create payment methods to make payments to external organizations, such as pension providers or professional
bodies. These payment methods include details, such as the type of payment and the bank account details.
271
Example
This image shows how you associate a third-party organization representing a Texas Court to a payment method. This
enables the payment of child support deductions that are deducted through the payroll to be paid to the court. Also,
you add a calculation card to an employee for the involuntary deduction for the child support payment.
Before You Begin

Do these steps:
1. Create a third-party organization.
2. Load the Organization Payment Methods for your payroll.
3. Load the external bank account.
Load the External Bank Account

You can use the External Bank Account Owner component to identify the third-party to whom the account belongs to.
272
This example ExternalBankAccount.dat le creates an External Bank Account component and associates it with a third-
party organization.
METADATA|ExternalBankAccount|BankNumber|BankBranchNumber|CountryCode|AccountNumber|IBAN|AccountName|
CurrencyCode
MERGE|ExternalBankAccount|100001A|111111A|CA|12345678|CA23 ANBK 3350 1234 5678 20|J and P Smith|USD
METADATA|ExternalBankAccountOwner|BankNumber|BankBranchNumber|CountryCode|AccountNumber|CurrencyCode|
ThirdPartyNumber|PrimaryFlag
MERGE|ExternalBankAccountOwner|100001A|111111A|CA|12345678|USD|68299|Y
Use this dat le to associate a payment method with the third-party organization HDL_Texas_ORG and organization
payment method Direct Deposit. Additionally, as the payment type is Direct Deposit, you load these bank account
details.
Bank Account Component Value
Account Number 1265896441

Bank Name Bank of America

Bank Branch Name New York

Routing Transit Number 511000025

Account Type Checking

METADATA|ThirdPartyOrganizationPaymentMethod|EffectiveStartDate|EffectiveEndDate|LegislativeDataGroupName|
TimeDefinitionCode|PartyNumber|BankName|BankBranchNumber|BankAccountNumber|BankCountryCode|
OrganizationPaymentMethodCode
MERGE|ThirdPartyOrganizationPaymentMethod|2016/01/01||USA LDG||68299|Bank of America|511000025|1265896441|US|
OPM_US_Nacha
Related Topics
Example of Loading Third-Party Personal Payment

Method
Use HCM Data Loader to create payment methods to people who aren't on your payroll. When loading such payment
methods, associate the third-party persons directly with the employee whose pay is subjected to deduction by
supplying the assignment number. A third-party person can receive payments from more than one employee too.
273
Example
John Smith is an employee at your organization. Mary Smith is his former spouse and receives a child-support payment
for each payroll period that's deducted from John's salary. You want to set up payments for Mary.
Before You Begin

Do these steps:
1. Create Mary as a third-party person.
2. Create the external bank account details.
Then, you create Mary's third-party payment method and associate the payroll relationship for John by supplying a
reference to his assignment. Finally, add the child support to John's involuntary deduction calculation card and supply
Mary's name as Order Amount Payee.
This gure shows how you can pay a third-party person using payment methods and calculation cards.
Use this example dat le to associate a payment method with the third-party person Mary Smith. The payment type for
Mary is Check. The association with John's payroll relationship is achieved by supplying a reference to his assignment.
274
METADATA|ThirdPartyPersonalPaymentMethod|EffectiveStartDate| LegislativeDataGroupName|
OrganizationPaymentMethodCode|AssignmentNumber|PartyNumber|BankName|BankBranchNumber|BankCountryCode|
BankAccountNumber
MERGE|ThirdPartyPersonalPaymentMethod|2016/01/01|USA LDG|Vision US1|E95516|395077|HSBC|568793|US|12345678
Related Topics
• Create Third Parties Options
275
276
Integrating with HCM Loading Payroll Costing
18 Loading Payroll Costing
Overview of Loading Payroll Costing

Using HCM Data Loader, you can create payroll costing setup information for the dierent payroll accounts. For
example, cost, oset, suspense, default, payroll liability, cash clearing, and cash accounts. You can dene costing at
various levels, such as Payroll, Element Eligibility, Department, Job, Position, Person, and Payment Source.
This gure shows the dierent levels of the costing hierarchy.
You enter the account information and any overrides for the dierent levels of the cost hierarchy. The application builds
the account number, starting with the lowest level (element entry) of the cost hierarchy and ending with the highest
277
level (payroll). It checks each level sequentially until it nds a value. If it nds an invalid cost combination, it places the
costing result in a suspense account.
Before You Begin

To load payroll costing records, do these tasks:
• Create Cost Allocation key exeld. This exeld creates a structure to capture the account codes used to
create accounting entries and to track and report labor costs.
• Enable cost hierarchy with levels to support each cost allocation key exeld cost account segment.
• Assign cost Allocation key exeld to a legislative data group.
Payroll Costing Accounts

Load accounts to cost payroll run and payment results, and to store invalid and accounts that aren't allocated.
Using HCM Data Loader, you can do all of these tasks.

• Load cost accounts that store expenses and employer liabilities and charges.
• Create overrides by entering cost account numbers at lower levels of the cost hierarchy.
• Use priority accounts to cost elements that require the same account combination. For example, you use a
priority account for an hourly earning element for laboratory work that's charged to a grant fund.
• Allocate a cost to more than one account by creating several accounts for an object. Specify the percentage
to charge to each account. For example, allocate costs to split salary costs for a job shared between two cost
centers.
• Load Oset accounts that create balancing entries required for double-entry bookkeeping.
• Set up suspense and default accounts at the payroll level and override them if required, with suspense and
default accounts at the department level.
Related Topics
• Payroll Cost Allocation Key Flexeld Setup
• How Payroll Costing Components Work Together
• Payroll Setup Tasks for Costing Accounts
Example of Loading Element Eligibility Costing

Use HCM Data Loader to assign costing information at the element level. You cost the element's eligibility records when
the results for the element aect net pay or employer liabilities. When costing an element, you specify the values to
cost, the type of costing to use, and then you oset the cost entries.
You can load the priority account that species the accounting at the element level. For example, your company funds
the entire hourly earning element for work performed in a lab from a single account. In such a case, you can create a
priority account and specify 100 for the percentage.
278
Let's suppose you cost a value for the same segment at higher levels in the costing hierarchy. In this case, though the
value is dened at the element eligibility level, the application considers the higher segment value.
Example
The Payroll Manager of the Vision Corp organization wants to set up costing for the Employer Union Pension Expense
element and distribute its costs to the earning elements of a distribution group.
Before You Begin
Before loading element costing, ensure that you do these steps:

1. Set up the Cost Allocation key exeld.
2. Create costing for element eligibility records for each of the pensionable earnings elements, such as the regular
wages and overtime wages.
3. Create the distribution group, Pensionable Wages that carries the costs of the distributed element. This group
includes the employee's wage elements.
After seing up these prerequisites, you cost the employer portion of the pension liability by creating an Employer
Union Pension Expense element.
For Distributed costing types, the calculation for distributed costing starts with the values loaded in the element
eligibility costing record. The calculation derives values for other segments from the costing values on the associated
entries of the distribution group. Further, it generates one costing result for each entry in the distribution group. Finally,
you transfer the costing entries for the payroll run results to the General Ledger.
This gure shows how you cost details for an element.
Set Up Cost Create Costing For

Allocation Key Flex Create Distribution
Element Eligibility
Field Group
Records
Transfer Costing
Entries to General Create Element
Ledger
Load these details for the Employer Union Pension Expense element:
Parameter Value
Costing Type Distributed
279
Parameter Value

Transfer to General Ledger Yes

Distribution Group Pensionable Wages

Costed Input Value Pay Value

Costed Yes

When you're loading costing details for element eligibility, you must specify the costed input values.
METADATA|CostInfoV3|EffectiveEndDate|EffectiveStartDate|SourceType|ElementEligibilityName|ElementCode|
LinkInputName|LegislativeDataGroupName|CostableType|CostedFlag|TransferToGlFlag
MERGE|CostInfoV3|4712/12/31|2015/01/01|EL|Employer Union Pension Expense|Employer Union Pension Expense||
Vision_Corp_LDG|F||N
MERGE|CostInfoV3|4712/12/31|2015/01/01|LIV|Employer Union Pension Expense|Employer Union Pension Expense|Pay
Value|Vision_Corp_LDG||Y|
METADATA|CostAllocationV3|EffectiveEndDate|EffectiveStartDate|SourceType|ElementEligibilityName|ElementCode|
MERGE|CostAllocationV3|4712/12/31|2015/01/01|EL|Employer Union Pension Expense|Employer Union Pension Expense|
Vision_Corp_LDG
Load these cost account values for segments that you don't want the costing calculation to derive from distributed
costing:
Parameter Value
Fund (Segment3) 5220 Employer Union Pension Expense account

Appropriation (Segment 4) 1001

Funding Source (Segment 5) 1010

Load these values for segments in Oset Accounts. Here, the oset account is the payable liability account, and the
balance sheet account numbers are for the Division and Department segments:
Parameter Value
Division (Segment1) 00

Department (Segment2) 000

280
Parameter Value
Natural Account (Segment6) 2152

METADATA|CostAllocationAccountV3|SourceType|ElementEligibilityName|ElementCode|LegislativeDataGroupName|
EffectiveDate|SourceSubType|Proportion|SubTypeSequence|ConcatenatedSegment|Segment3|Segment4|Segment5 MERGE|
CostAllocationAccountV3|EL|Employer Union Pension Expense|Employer Union Pension Expense|Vision_Corp_LDG |
2015/01/01|BAL|1|1|00.000....2152||| MERGE|CostAllocationAccountV3|EL|Employer Union Pension Expense|Employer
Union Pension Expense|Vision_Corp_LDG |2015/01/01|COST|1|1||5220|1001|1010
Related Topics
• Element Costing Options
• How Distributed Costing Is Calculated
Example of Loading Costing of Payroll

Use HCM Data Loader to assign account information to payrolls. You can select this highest level for segments that
seldom change for the people assigned to the payroll, such as company and line of business. As a best practice, set up a
suspense and default account at the payroll level. Otherwise, you must set up a suspense and default account for every
department to ensure you charge invalid costs to an account.
Example
Vision Corp has multiple payrolls, such as weekly and monthly and loads costing details at the payroll level. And they
use the costing information to report labor cost and generate journal entries for all their employees for the specied
payroll.
Load these costing details for the monthly payroll Vision Corp Monthly.
Parameter Value
Fund (Segment1) All Funds; 0001

Appropriation (Segment2) Salaries Appropriation;1001

Funding Source(Segment3) Original Funding Source;1010

Department(Segment4) General Government Agencies;1000

Organization(Segment5) Payroll; 1003

Program(Segment6) Balance Sheet; 0000
281
Parameter Value

Object (Segment7) Unspecied;0000

Project(Segment8) Unspecied; 0000

Load values for both suspense and default accounts.
Parameter Value
Fund(Segment1) Unspecied; 0000

Appropriation(Segment2) Balance Sheet; 0000

Funding Source(Segment3) Balance Sheet; 0000

Department(Segment4) Balance Sheet; 0000

Organization (Segment5) Balance Sheet; 0000

Program(Segment6) Balance Sheet; 0000

Object (Segment7) Unspecied; 0000

Project(Segment8) Unspecied; 0000

This example .dat le loads the costing details for the monthly payroll.
METADATA|CostAllocationV3|EffectiveEndDate|EffectiveStartDate|SourceType|PayrollCode|LegislativeDataGroupName
MERGE|CostAllocationV3|4712/12/31|2010/01/01|PAY|Vision Corp Monthly| Vision Corp
METADATA|CostAllocationAccountV3|SourceType|PayrollCode|LegislativeDataGroupName|EffectiveDate|SourceSubType|
Proportion|SubTypeSequence|ConcatenatedSegment|Segment1|Segment2|Segment3|Segment4|Segment5|Segment6|Segment7|
Segment8
MERGE|CostAllocationAccountV3|PAY|Vision Corp Monthly|Vision Corp|2010/01/01|COST|1|1||0001|1001|1010|1000|
1003|0000|0000|0000
MERGE|CostAllocationAccountV3|PAY|Vision Corp Monthly|Vision Corp|2010/01/01|SUSP|1|1|
0000.0000.0000.0000.0000.0000.0000.0000||||||||
MERGE|CostAllocationAccountV3|PAY|Vision Corp Monthly|Vision Corp|2010/01/01|DFLT|1|1|
0000.0000.0000.0000.0000.0000.0000.0000||||||||
Related Topics
282
Example of Loading Costing of Departments

Use HCM Data Loader to dene payroll costing rules at the Department level. For example, in a large enterprise you
might set up default accounts for departments where the managers commonly review and resolve their department's
expenses.
When you load costs at the department level, you can specify the percentage each account receives of the cost. If the
total allocation isn't 100 percent, then the application places the invalid cost in a default account.
Example
Vision Corporation's Payroll Manager wants to allocate costing at the department level to two cost centers.
As this gure shows, she allocates 35 percent of the costs of the Administration department to the Eastern District
Oce. She allocates the remainder to the Western District Oce.
Cost Centers
35% Eastern 65% Western

District Office District Office
The Payroll Manager loads these costing details for the Administration department to two district ocers as below:
Parameter Eastern District Oce Western District Oce
Percentage 35 65

283
Parameter Eastern District Oce Western District Oce
Fund (Segment1) Pooled Cash Fund: 0900 Pooled Cash Fund: 0901

Appropriation (Segment2) 1001 1001

Funding Source (Segment3) 1010 1011

Further, she uses the payroll suspense account to store costed payroll run results and prepayment results with invalid
account combinations. She loads these suspense account details.
Parameter Value
Fund (Segment1) All Funds; 0001

Appropriation (Segment2) Balance Sheet; 0000

Funding Source (Segment3) Balance Sheet; 0000

Department (Segment4) Balance Sheet; 0000



Project (Segment8) Unspecied; 0000

As Vision Corporation's department managers review and resolve their department expenses, the Payroll Manager sets
up default accounts for the Administration department. She loads these values for the default account.
Parameter Value
Fund (Segment1) Unspecied; 0000


Funding Source (Segment3) Balance Sheet; 0000

Department (Segment4) Balance Sheet; 0000

284
Parameter Value

Program (Segment6) Balance Sheet; 0000


Project (Segment8) Unspecied; 0000

This example dat le loads the costing details for the two departments.
METADATA|CostAllocationV3|EffectiveEndDate|EffectiveStartDate|SourceType|DepartmentName|
MERGE|CostAllocationV3|4712/12/31|2010/01/01|ORG|Administration|Vision Corp
METADATA|CostAllocationAccountV3|SourceType|DepartmentName|LegislativeDataGroupName|EffectiveDate|
SourceSubType|Proportion|SubTypeSequence|ConcatenatedSegment|Segment1|Segment2|Segment3|Segment4|Segment5|
Segment6|Segment7|Segment8
MERGE|CostAllocationAccountV3|ORG|Administration|Vision Corp|2010/01/01|COST|0.35|1||0900|1001|1010|||||
MERGE|CostAllocationAccountV3|ORG|Administration|Vision Corp|2010/01/01|COST|0.65|2||0901|1333|220|||||
MERGE|CostAllocationAccountV3|ORG|Administration|Vision Corp|2010/01/01|SUSP|1|1|
0001.0000.0000.0000.0000.0000.0000.0000||||||||
MERGE|CostAllocationAccountV3|ORG|Administration|Vision Corp|2010/01/01|DFLT|1|1|
0000.0000.0000.0000.0000.0000.0000.0000||||||||
Related Topics
• Allocate Costs to Accounts
Example of Loading Costing of Jobs

Use HCM Data Loader to dene payroll costs based upon the job category, such as cost centers or project funds. Let's
assume that you want to compare cost results for jobs in dierent cost centers. Then, you allocate costs at the job level
to generate the cost results based on the job.
You can load cost account segments to override those segments dened at other levels. If you divide costs among
accounts, you can specify the percentage each account receives of the cost. If the total allocation isn't 100 percent, then
the application places the costs that aren't allocated to a default account.
Example
Assume that you want to cost accounts to store expenses and employer liabilities and charges for the job Senior
Manager.
This table shows the job details that you want to cost for the employee.
285
Parameter Value
Percentage 100

Fund (Segment1) Pooled Cash Fund: 0900

Appropriation (Segment2) 1001

Use these dat les to load the cost segments for the job Senior Manager:
METADATA|CostAllocationV3|EffectiveEndDate|EffectiveStartDate|SourceType|JobCode|SetCode|
MERGE|CostAllocationV3|4712/12/31|2010/01/01|JOB|Senior Manager|COMMON|Vision Corp
METADATA|CostAllocationAccountV3|SourceType|JobCode|SetCode|LegislativeDataGroupName|EffectiveDate|
SourceSubType|Proportion|SubTypeSequence|Segment1|Segment2
MERGE|CostAllocationAccountV3|JOB|Senior Manager|COMMON|Vision Corp|2010/0101|COST|1|0900|1001
Related Topics
• How to Allocate Costs to Several Accounts
Example of Loading Costing of Positions

If you're using position management at your enterprise to track the cost of turnover to the enterprise, then you allocate
costs at the position level. For example, you want to compare cost results for positions in dierent cost centers. So, you
allocate the costs at the position level to generate cost results based on the position.
Let's consider this example. Vision Corp uses position management and wants to cost these account details for the
position Senior Product Manager in Utilities business unit.
Parameter Value
Percentage 100

Fund (Segment1) Government Fund;1000


Funding Source (Segment3) Funding Source; 2000

Use this dat le to cost the position details.

METADATA|CostAllocationV3|EffectiveEndDate|EffectiveStartDate|SourceType|PositionCode|
LegislativeDataGroupName|BusinessUnitName
286
MERGE|CostAllocationV3|4712/12/31|2010/01/01|POS|Senior Product Manager|Vision Corp|Utilities

METADATA|CostAllocationAccountV3|SourceType|PositionCode|LegislativeDataGroupName|EffectiveDate|SourceSubType|
Proportion|SubTypeSequence|Segment1|Segment2|Segment3|BusinessUnitName
MERGE|CostAllocationAccountV3|POS|Senior Product Manager|Vision Corp|2010/01/01|COST|1|1|100|0000|2000|
Utilities
Related Topics
• How to Allocate Costs to Several Accounts
Example of Loading Payment Source Costing

Use HCM Data Loader to enter account information for your payment sources. Imagine a scenario where a delay exists
between the date the payment is issued by using a cheque and the date the cheque is cleared. In such a case, your
company wants to create a cash clearing account to track payments.
Using HCM Data Loader, you load a payment source and create liability, cash clearing, and cash accounts for it.
Note: You load the same account information that you use for the cash and cash clearing account that you created in
the General Ledger.
This table summarizes the values that you load for the various accounts:
Parameter Cash Account Cash Clearing Account Liability Account
Fund (Segment1) All Funds; 0001 Pooled Cash Fund;0900 All Funds; 0001

Appropriation (Segment2) Salaries Appropriation ; 1001 Salaries Appropriation; 1002 Salaries Appropriation; 1002

Funding Source (Segment3) Original Funding Source; 1010 Funding Source; 1999 Balance Sheet; 0000

Department (Segment4) Progress Top Level; 0001 General Government Balance Sheet; 0000
Agencies; 1000

Organization (Segment5) Administration; 1001 Administration; 1001 Payroll; 1003

Program (Segment6) Programs; 0001 Programs; 0001 Legislative;1100

Object (Segment7) Cash; 11110 Object; 11140 On Account Cash; 11150

Project (Segment8) Administrative Projects; Capital Project; 100001 Broadway Extension; 100004
100000

287
This dat le loads these account values for the payment source Vision Corp Check PS in Vision Corp Check PM payment
method:
METADATA|CostInfoV3|EffectiveEndDate|EffectiveStartDate|SourceType|PaymentSourceCode|
OrganizationPaymentMethodCode|LegislativeDataGroupName|CostableType|CostedFlag|TransferToGlFlag|GUID|
SourceSystemId|SourceSystemOwner
MERGE|CostInfoV3|4712/12/31|2010/01/01|PM|Vision Corp Check PS|Vision Corp Check PM|Vision Corp|Y|Y|Y|||
METADATA|CostAllocationV3|EffectiveEndDate|EffectiveStartDate|SourceType|PaymentSourceCode|
OrganizationPaymentMethodCode|LegislativeDataGroupName|GUID|SourceSystemId|SourceSystemOwner
MERGE|CostAllocationV3|4712/12/31|2010/01/01|PM|Vision Corp Check PS|Vision Corp Check PM|Vision Corp|||
METADATA|CostAllocationAccountV3|SourceType|PaymentSourceCode|OrganizationPaymentMethodCode|
LegislativeDataGroupName|EffectiveDate|SourceSubType|Proportion|SubTypeSequence|ConcatenatedSegment| GUID|
MERGE|CostAllocationAccountV3|PM|Vision Corp Check PS|Vision Corp Check PM|Vision Corp|2010/01/01|CLRNG|1|1|
0900.1002. 1999.1000.1001.0001.11140.100001|||
MERGE|CostAllocationAccountV3|PM|Vision Corp Check PS|Vision Corp Check PM|Vision Corp|2010/01/01|CASH|1|1|
0001.1001.1010.0001.1001.0001.11110.100000|||
MERGE|CostAllocationAccountV3|PM|Vision Corp Check PS|Vision Corp Check PM|Vision Corp|2010/01/01|LBLTY|1|1|
0001.1002.0000.0000.1003.1100.11150.100004|||
Related Topics
• How Payroll Cost Results are Calculated
• Payroll Setup Tasks to Transfer Costs to General Ledger
Example of Loading Person Costing

Use HCM Data Loader to manage costing at the person level to track costs for people in your enterprise. You can either
cost all the elements that the person is eligible to receive or cost individual elements. You allocate costs to single or
multiple accounts.
Let's suppose you start a new project and want to track the costs incurred by the employees reassigned temporarily to
the project. To monitor these costs, you can set up costing at the person level for these employees.
When you load costs at the person level, you can specify the percentage each account receives of the cost. If the total
allocation isn't 100 percent, then the application places the cost that's not allocated in a default account.
Using HCM Data Loader, you can load costing for a person at the assignment and payroll relationship levels. Further,
you can allocate costing for an element at the assignment or payroll relationship level for a person.
Example of Loading Person Costing at Payroll

Relationship Level
Let's consider this example where you cost Vijay's elements to the Special Revenue Fund. When you dene the costs at
the payroll relationship level, you need not dene the costs at each element level for these segments.
Load these details to allocate costs for Vijay (Payroll Relationship Number: 12345678) at the payroll relationship level.
288
Parameter Value
Percentage 100

Fund (Segment1) Special Revenue Fund (1100)

Appropriation (Segment2) Salary Appropriation (1002)

Funding Source (Segment3) 2000


Organization (Segment5) Payroll (1003)

This example dat le loads the costing details for the person at the payroll relationship level.
METADATA|CostAllocationV3|EffectiveEndDate|EffectiveStartDate|SourceType|PayrollRelationshipNumber|
MERGE|CostAllocationV3|4712/12/31|2010/01/01|PREL|12345678|Vision Corp
METADATA|CostAllocationAccountV3|SourceType|PayrollRelationshipNumber|LegislativeDataGroupName|EffectiveDate|
SourceSubType|Proportion|SubTypeSequence|Segment1|Segment2|Segment3|Segment4|Segment5
MERGE|CostAllocationAccountV3|PREL|12345678|Vision Corp|2010/01/01|COST|1|1|1100|1002|2000|2000|1003
Example of Loading Person Costing at Assignment Level

As Vision Corp encourages employees to work across multiple projects, employee's costs should be allocated in the
same way. In this example, you allocate costing at the assignment level for a person who divides the time worked
between two managers at dierent cost centers. Further, you override costing for a specic element at the assignment
level.
Lynda Jones writes advertisements for the Advertising division. For the next few months, she will spend 40 percent
of his time in designing customer preference surveys for the Market Research division. Now, you split Lynda's cost
between Advertising and Market Research divisions, which belong to dierent cost centers.
Assign these percentages to the two departments:
Percent Department
40 3180 (Market Research)

60 3190 (Advertising)

The assignment number of Lynda is 12345.
289
This example .dat le loads the costing details for a person at the assignment level:
METADATA|CostAllocationV3|EffectiveEndDate|EffectiveStartDate|SourceType|AssignmentNumber|
MERGE|CostAllocationV3|4712/12/31|2010/01/01|ASG|12345|Vision Corp
METADATA|CostAllocationAccountV3|SourceType|AssignmentNumber|LegislativeDataGroupName|EffectiveDate|
SourceSubType|Proportion|SubTypeSequence|Segment4
MERGE|CostAllocationAccountV3|ASG|12345|Vision Corp|2010/01/01|COST|0.4|1|3180
MERGE|CostAllocationAccountV3|ASG|12345|Vision Corp|2010/01/01|COST|0.6|2|3190
Example of Loading Person Element Costing at

Assignment Level
In this example, all elements of the employee John go to the cost center Payroll and are dened at the payroll
relationship level. However, in a particular period, the Vision Corp pays a bonus to John and the costs of the bonus
should go to his home department, which is Finance.
Here, you dene the Finance cost center for the Bonus element using the assignment costing element.
Parameter Value
Element Name Vision_ Corp_Bonus

Percentage 100

Funding Source 1010

Department 3120 Finance Department

The employee's assignment number is 12345 and the Payroll Relationship number is 12345678.
This .dat le loads the costing details for the two departments.
METADATA|CostAllocationV3|EffectiveEndDate|EffectiveStartDate|SourceType|AssignmentNumber|
PayrollRelationshipNumber|ElementCode|LegislativeDataGroupName
MERGE|CostAllocationV3|4712/12/31|2010/01/01|AET|12345|12345678|Vision_Corp_Bonus|Vision Corp
METADATA|CostAllocationAccountV3|SourceType|AssignmentNumber|ElementCode|PayrollRelationshipNumber|
LegislativeDataGroupName|EffectiveDate|SourceSubType|Proportion|SubTypeSequence|Segment3|Segment4
MERGE|CostAllocationAccountV3|AET|12345|Vision_Corp_Bonus|12345678|Vision Corp|2010/01/01|COST|1|1|1010|3120
Example of Loading Person Element Costing at Payroll

Relationship Level
In this example, you update the funding source for the ANC_ELE_COMP_VISION Entitlement element of Mandy
Steward as University Grants for research. The application derives the funding source and department for all other
290
elements from element eligibility costing and department level costing. Then, you can dene these segments at payroll
relationship element level.
For the ANC_ELE_COMP_VISION Entitlement element, load these costs at the payroll relationship level for Mandy.
Parameter Value
Percentage 100

Funding Source University Grants for research 2003

Department Education 2110

Organization Payroll (1003)

The employee's payroll relationship number is 12345678.
This example .dat le loads the costing details at the payroll relationship level for the person.
METADATA|CostAllocationV3|EffectiveEndDate|EffectiveStartDate|SourceType|PayrollRelationshipNumber|
ElementCode|LegislativeDataGroupName
MERGE|CostAllocationV3|4712/12/31|2010/01/01|PRET|12345678|ANC_ELE_COMP_VISION Entitlement element|Vision Corp
METADATA|CostAllocationAccountV3|SourceType|PayrollRelationshipNumber|ElementCode|LegislativeDataGroupName|
EffectiveDate|SourceSubType|Proportion|SubTypeSequence|Segment3|Segment4|Segment5
MERGE|CostAllocationAccountV3|PRET|12345678|ANC_ELE_COMP_VISION Entitlement element|Vision Corp|2010/01/01|
COST|1|1|2003|2110|1003
Example of Loading Element Entry Costing

David works for Vision Corp and all of his elements go to his home department Payroll (3001). However, last Monday,
David has provided services to HR department (3002) for 8 hours. Now, these hours should be costed to the HR
department. The services are categorized as consulting (4001).
Using HCM Data Loader, load these element entry costing values.
Parameter Value
Eective Start Date 01-Jan-2011

Payroll Relationship Number 955160008175766

Person Number 955160008175766

Element Hourly Salary

291
Parameter Value

Program (Segment6) 4001

The employee's assignment number is 12345 and the payroll relationship number is 12345678.
This example .dat le loads the element entry level costing details for David.
METADATA|CostAllocationV3|EffectiveEndDate|EffectiveStartDate|SourceType|AssignmentNumber|ElementCode|
MultipleEntryCount|LegislativeDataGroupName|EntryType
MERGE|CostAllocationV3|4712/12/31|2010/01/01|EE|12345|Hourly Salary|1|Vision Corp|E
METADATA|CostAllocationAccountV3|SourceType|AssignmentNumber|ElementCode|MultipleEntryCount|
LegislativeDataGroupName|EffectiveDate|SourceSubType|Proportion|SubTypeSequence|Segment4|Segment6|EntryType
MERGE|CostAllocationAccountV3|EE|12345|Hourly Salary|1|Vision Corp|2010/01/01|COST|1|1|3002|4001|E
Related Topics
292
Integrating with HCM Loading Payroll Data Using Transformation Formula
19 Loading Payroll Data Using Transformation

Formula
Payroll Transformation Formula for HCM Data Loader

Overview
Often times, your existing data or the payroll data that you upload might not be in the format recognized by HCM
Data Loader. In such cases, you can use a payroll transformation formula to transform your data into a format that's
supported by HCM Data Loader.
Let's consider these examples.

• An inbound le contains data that needs to be loaded using dierent payroll business objects in HCM Data
Loader. Here, the content of the le needs to be split across more than one HCM Data Loader le.
• You might create a transformation formula to convert an aribute value in the le to another value that you
derive using value sets.
• You want to change a person number into an assignment number. In this case, you will use a more complex
formula to convert the aributes.
You use the Load Data From File ow to transform your data into the HCM Data Loader le format using your
transformation formula.
As this table shows, the two ow paerns are secured using these privileges:
Flow Paern Privileges
Submit Payroll Flow PAY_ SUBMIT_ PAYROLL_ FLOW_PRIV

Load HCM Data HRC_ LOAD_ HCM_DATA_PRIV

This example species the le name in the formula as PersonalPaymentMethod, the le discriminator as
PersonalPaymentMethod, and the business operation as MERGE.
/*HDL Related Outputs*/

FileName = 'PersonalPaymentMethod'
BusinessOperation = 'MERGE'
FileDiscriminator = 'PersonalPaymentMethod'
To view details about the le name, le discriminator, and a list of supported business operations, use the View
Business Objects task in the Data Exchange work area.
1. On the View Business Objects page, search for and select your business object. In this example, the business
object is Personal Payment Method.
2. On the Component Details page, you can nd the name of the le, and the le discriminator and a list of
supported actions for the object.
293
How You Transform Data Using Payroll Transformation Formula

for HCM Data Loader
Use the Load Data From File ow to transform data in the source le into a format that's supported by HCM Data
Loader. You can submit this ow independently or include it in a ow that you create for automating data loads on a
periodic basis. When you submit the ow, either manually or using a web service, you must specify a transformation
formula to transform the data, as needed.
The ow contains these two tasks that help you to transform data into a HCM Data Loader format:
• Generate Data Loader File
• Initiate Data Loader Task
As this gure shows, the rst step is to submit the Load Data From File ow. This ow takes data from the at le and
generates an equivalent le format for the data present in the input le.
Load Data From File

Flow Pattern
Start 1
UCM
Payroll
Data File 2 Transformation
Generate Data
DataLine1|xx|11
Loader File
Formula for
DataLine2|yy|22 HCM Data
DataLine3|zz|33
Loader
3
Zip File
4
HDL dat file Initiate Data Loader
End
Perform these steps to transform data using Payroll Transformation Formula for HCM Data Loader:
1. From the Checklist or Data Exchange work area, submit the Load Data From File ow paern.
2. The ow invokes the Payroll Transformation Formula for the Content ID. Typically, you create your
transformation formula for HCM Data Loader on the Manage Fast Formulas page. The type of the formula
should be HCM Data Loader.
3. The Generate Data Loader File task reads the data le line by line, producing an equivalent HCM Data Loader
format for each line. Finally, it creates a compressed le of all of the transformed data les and uploads to the
Oracle WebCenter Content server. Also, the task records the Content ID.
294
4. The Initiate Data Loader task takes the Content ID for the le generated by the Generate Data Loader File
task. And it invokes HCM Data Loader. HCM Data Loader validates the data and creates valid records in the
HCM cloud.
The table shows the tasks and the privileges that they're secured with:
Task Privilege
Submit Payroll Flow PAY_ SUBMIT_ PAYROLL_ FLOW_PRIV

Load HCM Data HRC_ LOAD_ HCM_DATA_PRIV

How To Create Program for Automation

You can submit the Load Data from File ow by using a web service.
As this gure shows, your program uploads the source le to content server, and retrieves the content ID for the Flow
Actions Service web service. Then, the program calls the Flow Actions web service by supplying certain parameters.
Flat File
Upload File to Content Content ID

Server
Invoke
FlowsActionsService
Submit the Load Data from

File flow
When calling the web service, your program supplies these parameters.
• Name of the ow paern, which is Load Data from File

• Content ID of the uploaded le
295
• Unique name to identify the ow instance being submied

• Process conguration group name for special processing (optional)
• Transformation formula name (mandatory)
For more information about the Flow Actions Service web service, refer to the SOAP Web Services for Oracle HCM Cloud
guide. For examples of its usage for automating le uploads, refer to the aachment for HCM Data Loader User Guide
(1664133.1) on My Oracle Support at hps://support.oracle.com.
Submit The Load Data From File Flow

From the Checklist or Data Exchange work area, use the Load Data from File ow paern to transform data in your
source le into the HDL format.
Assumptions
This procedure has these assumptions.
• You have the Human Capital Management Integration Specialist role.
• You have the source le ready to upload to Oracle WebCenter Content.
• If you have already uploaded the source le, you have the content ID handy.
Note: To upload les to the content server, browse to the source le on your le system, check it in to the
content server, and retrieve its Content ID. For more information, see Oracle Fusion Middleware Using Oracle
WebCenter Content guide.
Before You Begin

Before you submit the ow, ensure that you meet these prerequisites.
Characteristics What You Should Do
Data transformation
If the data in the source le requires transformation, create and compile a transformation
formula using the HCM Data Loader formula type.
Use the Manage Fast Formulas task in the Payroll Calculation work area to do this
compilation.
File encryption
Before loading encrypted les, ensure that the encryption keys exist for the secure le transfer.
This process involves creating a service request, generating PGP key pairs, and sharing the
encryption keys.
Specify the Payroll Batch Loader Encryption Type parameter value for the process
conguration group you select when running the ow or the web service. Valid values are
PGPSIGNED, PGPUNSIGNED, and NONE.
In the Setup and Maintenance work area, use the Manage Payroll Process Conguration task
to specify processing parameters for your process conguration group.
• Oering: Workforce Deployment

• Functional Area: Payroll
296
Characteristics What You Should Do
• Task: Manage Payroll Process Conguration
Other processing parameters

In the Setup and Maintenance work area, use Manage Payroll Process Conguration task to
add parameters for the process conguration group.
• Oering: Workforce Deployment

• Functional Area: Payroll
• Task: Manage Payroll Process Conguration
Examples of processing parameters include Batch Error Mode, Logging Area, Logging
Category, and Threads.
1. Click the Submit a Payroll Flow task.

2. In the Legislative Data Group option, select a legislative data group.
3. Search for and select the Load Data from File ow paern.
4. Click Next.
5. Enter the parameters, as shown in this table.
Field Value
Payroll Flow Descriptive name for this specic ow process.

Content Id Enter the Content Id. The source le must already exists on the content server.

Transformation Formula
Select the required transformation formula. The type of the formula should be HCM Data
Loader.
Process Conguration Group Select your process conguration group.

6. On the Enter Parameters page, click Next.

7. On the Enter Flow Interaction page, click Next.
8. On the Schedule page, click Next.
9. On the Review page, click Submit.
10. In the conrmation dialog box, click OK and View Checklist.
11. On the Payroll Flow page, Task Details tab you should see a green check mark in the Generate Data
Loader File and Initiate Data Loader rows, Task Type column. If not, on the toolbar, click the Refresh icon
intermiently until you do.
12. Close the Payroll Flow page.
13. On the Overview page, search for and click your payroll ow.
14. View the process results.
15. Check for any errors or warnings.
297
Transformation Formula Input Variables

Variables, such as FileName, FileDiscriminator and LINEREPEATNO, are available for all formulas of HCM Data Loader
Transformation formula type. Additional variables may be available depending on the selected business object.
Positions
Using the transformation formula, you can assign aributes to the required position. Positions can range from 1 to N.
Depending upon the business object, the positions can be either optional or mandatory.
Example:
This gure shows the dierent aributes for positions 2 through 8 for Balance Adjustments.
LegislativeDataGroup
BalAdjBatchId SourceSystemOwner
Name
1 2 3 4 5 6 7
EffectiveDate PayrollName ConsolidationSetName SourceSystemId
Positions 2-8
In this example, you assign aributes to positions 2 through 8.

• POSITION2: EffectiveDate
• POSITION3: PayrollName
• POSITION4: LegislativeDataGroupName
• POSITION5: ConsolidationSetName
• POSITION6: BalAdjBatchId
• POSITION7: SourceSystemId
• POSITION8: SourceSystemOwner
FileName, FileDiscriminator, and BusinessOperation

FileName, FileDiscriminator, and BusinessOperation variables are required for all transformations.
Here are the details of these variables.
• FileName is the name of the le for the business object.
• FileDiscriminator is the le discriminator for the business object.
• BusinessOperation refers to the operation, such as Merge or Delete that are performed by the HCM Data Loader
process on the transformed le.
Here's an example of values that you can supply for the input variables: FileName, FileDiscriminator, and
BusinessOperation.
FileName = 'BalanceAdjustmentHeader'
298
FileDiscriminator = POSITION1
LINEREPEAT And LINEREPEATNO

LINEREPEAT allows a single line of input to be processed multiple times. And LINEREPEATNO indicates the number of
repetitions.
For example, for time entry, there might be a regular time entry wage followed by a premium time entry wage.
Example: The Element Entry le contains these details.

Update|ElementEntryValue|Vision Corporation US LDG|WLM_Salary|2019/04/15|4712/12/31|E955160008191355-2|
Amount|1002|2|E
Update|ElementEntryValue|Vision Corporation US LDG|WLM_Salary|2019/04/15|4712/12/31|E955160008191355-2|
Amount|1003|3|E
The input line can be processed twice. The output le contains the element entry and element entry value as shown in
this sample code snippet.
ELSE IF OPERATION='MAP' THEN
(
LegislativeDataGroupName=POSITION3
ElementName=POSITION4
EffectiveStartDate=POSITION5
EffectiveEndDate=POSITION6
AssignmentNumber=POSITION7
InputValueName=POSITION8
ScreenEntryValue=POSITION9
MultipleEntryCount=POSITION10
EntryType=POSITION11
IF LINEREPEATNO=1 THEN
(
BusinessOperation='MERGE'
BusinessObject='Element Entry'
FileName = 'ElementEntry'
FileDiscriminator ='ElementEntry'
LINEREPEAT = 'Y'
RETURN BusinessOperation,FileDiscriminator,FileName
)
ELSE
(
BusinessOperation='MERGE'
BusinessObject='Element Entry Value'
FileName = 'ElementEntry'
FileDiscriminator = 'ElementEntry'
LINEREPEAT = 'N'
RETURN BusinessOperation,FileDiscriminator,FileName
)
Payroll Transformation Formula Operations

The transformation formula is invoked several times to derive dierent components that are required for processing the
incoming data.
This table explains the various operations that you can do with the formula.
299
Operation Type Return Value Example
FILETYPE OUTPUTVALUE DELIMITED

DELIMITER OUTPUTVALUE |

READ OUTPUTVALUE NONE

MAP Business Object Aributes NA

NUMBEROFBUSINESSOBJECTS OUTPUTVALUE 2

METADATALINEINFORMATION METADATAn METADATA1

Delimiter
The default delimiter that separates values is a pipe character. If your le uses a dierent delimiter, you must set the
delimiter you want your formula.
This example species a comma character as the delimiter.
/* Calculations */
IF OPERATION='FILETYPE' THEN
OUTPUTVALUE='DELIMITED'
ELSE IF OPERATION='DELIMITER' THEN
OUTPUTVALUE=','
Note: Ensure that the delimiter you enter in the formula is a single non-ASCII character and not part of any of
the values to upload.
MAP
The MAP operation denes the return values related to a particular object. The return values must have the same
names as the aributes specied in the application for that object.
For example, these RETURN values can be used to generate an Element Entry dat le.
RETURN
BusinessOperation,FileDiscriminator,FileName,AssignmentId,AssignmentNumber,CreatorType,DateEarned,EffectiveEndDate,
Here, the BusinessOperation is set to MERGE and the BusinessObject is set to Element Entry.
METADATALINEINFORMATION
The application generates the le either with all dened aributes or with only specied aributes, depending on
whether you specify a value for METADATALINEINFORMATION or not.
1. If you don't specify a value for METADATALINEINFORMATION, then the application generates METADATLINE in the
transformed le with all dened aributes for the business object.
2. If you specify a value, then the transformed le will contain only the aributes that you specied.
300
For the METADATALINEINFORMATION operation, you specify an array per business object being processed in the formula.
The number of arrays should match the number specied in the NUMBEROFBUSINESSOBJECTS operation. The name
of the array should be METADATA with the number as sux . For example, RETURN METADATA1, METADATA2 when the
NUMBEROFBUSINESSOBJECTS is 2.
Note: The rst two entries in the array are reserved to specify the FileName and FileDiscriminator of the business object.
Additionally, for METADATALINEINFORMATION, you can specify aributes with special characters for that business objects.
Notice that in this example BalAdjBatchId(SourceSystemId) has parenthesis.
If the le contains either Flexeld or SourceSystem references, then the application can't resolve the default mapping of
output parameter names and aributes.
Let's consider this syntax: jobEffSegment1(PER_JOBS_EIT_EFF=context). To allow this construct to be generated in the
HCM Data Loader le, you dene the METADATA line in the transformation formula. For each business object that appears
in the output, you must dene the METADATA content in an array.
Example:
METADATA2[1] = 'Job' /*FileName*/
METADATA2[2] = 'JobExtraInfo' /*FileDiscriminator*/
METADATA2[3] = 'EffectiveStartDate'
METADATA2[4] = 'EffectiveEndDate'
METADATA2[5] = 'JobCode'
METADATA2[6] = 'SetCode'
METADATA2[7] = 'FLEX:PER_JOBS_EIT_EFF'
METADATA2[8] = 'EFF_CATEGORY_CODE'
METADATA2[9] = 'InformationType'
METADATA2[10] = 'JeiInformationCategory'
METADATA2[11] = 'LegislationCode'
METADATA2[12]= 'SequenceNumber'
METADATA2[13]= 'jobEffSegment1(PER_JOBS_EIT_EFF=job-eff-context)'
Here's how the generated HCM Data Loader le looks like.
METADATA|JobExtraInfo|EffectiveStartDate|EffectiveEndDate|JobCode|SetCode|FLEX:PER_JOBS_EIT_EFF|
EFF_CATEGORY_CODE|InformationType|JeiInformationCategory|LegislationCode|SequenceNumber|
jobEffSegment1(PER_JOBS_EIT_EFF=job-eff-context)
NUMBEROFBUSINESSOBJECTS
This operation indicates the number of business objects being processed in the formula.
Return Values for Payroll Transformation Formula for HCM Data

Loader
The return values for HCM Data loader formulas vary based on the business object and task action. They are the same
as the aribute names and must include BusinessOperation, FileName, and FileDiscriminator.
Here's an example of return values.
/*Return Values*/
RETURN BusinessOperation,FileName,FileDiscriminator,Attribute1,Attribute2,...,Attributen
/*Attributes for a particular Business Object can be found from the View Business Objects UI under the HCM Data
Loader task in the Data Exchange Work Area */
301
For the NUMBEROFBUSINESSOBJECTS and METADATALINEINFORMATION operations, the RETURN statement is as follows.
/*Return Values for NUMBEROFBUSINESSOBJECTS and METADATALINEINFORMATION Operation*/
OUTPUTVALUE='|'
ELSE IF OPERATION='READ' THEN
OUTPUTVALUE='NONE'
ELSE IF OPERATION = 'NUMBEROFBUSINESSOBJECTS' THEN(
OUTPUTVALUE = '2'
RETURN OUTPUTVALUE
)
ELSE IF OPERATION = 'METADATALINEINFORMATION' THEN
(
METADATA1[1] = 'BalanceAdjustmentHeader' /*FileName*/ /*Reserved*/
METADATA1[2] = 'BalanceAdjustmentHeader' /*FileDiscriminator*/ /*Reserved*/
METADATA1[3] = 'LegislativeDataGroupName'
METADATA1[4] = 'BatchName'
METADATA1[5] = 'SourceSystemId'
METADATA1[6] = 'SourceSystemOwner'
METADATA2[1] = 'BalanceAdjustmentHeader' /*FileName*/ /*Reserved*/

METADATA2[2] = 'BalanceAdjustmentGroup' /*FileDiscriminator*/ /*Reserved*/
METADATA2[3] = 'EffectiveDate'
METADATA2[4] = 'PayrollName'
METADATA2[6] = 'ConsolidationSetName'
METADATA2[7] = 'BalAdjBatchId(SourceSystemId)'
METADATA2[8] = 'SourceSystemId'
METADATA2[9] = 'SourceSystemOwner'
RETURN METADATA1, METADATA2 /*Only two as Return value for NUMBEROFBUSINESSOBJECTS is 2*/
)
You can dene variables with special characters. For example, use this structure to return the
BalAdjBatchId(SourceSystemId) Source ID.
/*Return Values for the MAP Operation*/

FileName = 'BalanceAdjustmentHeader'
FileDiscriminator = POSITION1
EffectiveDate = POSITION2
PayrollName = POSITION3
LegislativeDataGroupName = POSITION4
ConsolidationSetName = POSITION5
"BalAdjBatchId(SourceSystemId)"= POSITION6
SourceSystemId = POSITION7
SourceSystemOwner = POSITION8
RETURN BusinessOperation, FileDiscriminator, FileName, EffectiveDate, PayrollName, LegislativeDataGroupName,

ConsolidationSetName, "BalAdjBatchId(SourceSystemId)", SourceSystemId, SourceSystemOwner
/*Note BalAdjBatchId(SourceSystemId) is enclosed by double quotes while assigning value as well as while putting
it in the return values list */
302
Sample Payroll Transformation Formula for Multiple Business

Objects
In this example, the formula uses the user dened tables and personal payment method business objects. It
converts the Person Number in the at le into Assignment Number and uses the METADATALINEINFORMATION and
NUMBEROFBUSINESSOBJECTS operations.
Here's the sample of the raw input le.

PPM|2018/04/04|1|ZHRX_VS_US_TPPI_LDG_ONE|955160008191423|ZHRX_VS_US_TPPI_Check|PPM1|M|10
UDT|SM_UDT_4|Range|Number|Test UDT|USA LDG
And this code snippet has the formula for this example.
/**********************************************************
FORMULA NAME: Load User Defined Table and Personal Payment Method
FORMULA TYPE: HCM Data Loader
*************************************************************/
/* Inputs */
INPUTS ARE OPERATION (text), LINENO (number), LINEREPEATNO (number),POSITION1 (text), POSITION2 (text),
POSITION3 (text), POSITION4 (text), POSITION5 (text), POSITION6 (text), POSITION7 (text), POSITION8
(text),POSITION9 (text)
DEFAULT FOR POSITION1 IS 'NO DATA'
DEFAULT FOR POSITION4 IS '2'
DEFAULT FOR LINEREPEATNO IS 1
OUTPUTVALUE='|'
OUTPUTVALUE='NONE'
ELSE IF OPERATION = 'NUMBEROFBUSINESSOBJECTS' THEN
(
OUTPUTVALUE = '2'
RETURN OUTPUTVALUE
)
(
METADATA1[1] = 'UserDefinedTable' /*FileName*/
METADATA1[2] = 'UserDefinedTable' /*FileDiscriminator*/
METADATA1[3] = 'UserTableCode'
METADATA1[4] = 'RangeOrMatch'
METADATA1[5] = 'UserKeyUnits'
METADATA1[6] = 'UserRowTitle'
METADATA1[7] = 'UserTableName'
METADATA2[1] = 'PersonalPaymentMethod' /*FileName*/
METADATA2[2] = 'PersonalPaymentMethod' /*FileDiscriminator*/
METADATA2[3] = 'EffectiveStartDate'
METADATA2[4] = 'PersonalPaymentMethodCode'
METADATA2[5] = 'AssignmentNumber'
METADATA2[6] = 'Amount'
METADATA2[7] = 'ProcessingOrder'
METADATA2[8] = 'OrganizationPaymentMethodCode'
303
METADATA2[9] = 'PaymentAmountType'
RETURN METADATA1, METADATA2
)
IF POSITION1='UDT' THEN
(
FileName = 'UserDefinedTable'
FileDiscriminator = 'UserDefinedTable'
UserTableCode = POSITION2
IF POSITION3='Range' THEN
(
RangeOrMatch = 'R'
)
IF POSITION4='Number' THEN
(
UserKeyUnits = 'N'
)
UserRowTitle = POSITION5
UserTableName = POSITION2
LegislativeDataGroupName = POSITION6
RETURN
BusinessOperation,FileDiscriminator,FileName,UserTableCode,RangeOrMatch,UserKeyUnits,UserRowTitle,UserTableName,Legisla
)
IF POSITION1='PPM' THEN
(
ProcessingOrder=POSITION3
AssignmentNumber=GET_VALUE_SET('SAMPLE_GET_ASG_NUM','|=PERSON_NUMBER='''||POSITION5||'''')
OrganizationPaymentMethodCode=POSITION6
PersonalPaymentMethodCode=POSITION7
PaymentAmountType=POSITION8
Amount=POSITION9
RETURN
BusinessOperation,FileName,FileDiscriminator,EffectiveStartDate,PersonalPaymentMethodCode,AssignmentNumber,Amount,Proce
)
ELSE
OUTPUTVALUE='NONE'
RETURN OUTPUTVALUE
/* End Formula Text */
Note: To debug value sets, create a BI report with this query to return the required data.
SELECT pay_ff_functions.gvs ('SAMPLE_GET_ASG_NUM','|=PERSON_ID=100000012092216') value FROM dual;
Sample Payroll Transformation Formula for HCM Data Loader

In this example, the transformation formula species the transformation mechanism for an incoming comma separated
delimited le. The formula's return values are the same as the list of aributes for the personal payment method object.
Here's the sample raw le for personal payment method, with comma as the delimiter.
2018/04/04,1,ZHRX_VS_US_TPPI_LDG_ONE,E955160008191423,ZHRX_VS_US_TPPI_Check,PPM1,M,10
304
/******************************************************************
FORMULA NAME: Load Personal Payment Method
FORMULA TYPE: HCM Data Loader
******************************************************************/
/* Inputs */
POSITION3 (text), POSITION4 (text), POSITION5 (text), POSITION6 (text), POSITION7 (text), POSITION8 (text)

OUTPUTVALUE=','
OUTPUTVALUE='NONE'
/*HDL Related Outputs*/
(
ProcessingOrder=POSITION2
AssignmentNumber=POSITION4
OrganizationPaymentMethodCode=POSITION5
PersonalPaymentMethodCode=POSITION6
PaymentAmountType=POSITION7
Amount=POSITION8
RETURN
BusinessOperation,FileName,FileDiscriminator,EffectiveStartDate,PersonalPaymentMethodCode,AssignmentNumber,Amount,Proce
)
ELSE
OUTPUTVALUE='NONE'
RETURN OUTPUTVALUE
Payroll Transformation Formula for HCM Spreadsheet

Data Loader
Overview
You can use HCM Spreadsheet Data Loader to load all payroll objects that HCM Data Loader supports. As the rst step,
you create a spreadsheet template for the required object from the Data Exchange Work area and further download
the template in CSV format. You can download CSV and XML le templates from a spreadsheet template. The Payroll
Transformation Formula for HCM Spreadsheet Data Loader transforms the raw delimited le to a format that suits the
template.
305
This gure summarizes the process of transforming data that's uploaded using HCM Spreadsheet Data Loader.
Load Spreadsheet
Data From File
Start 1
UCM
Payroll
Data File 2 Transformation
DataLine1|xx|11
Generate Data Formula for
DataLine2|yy|22
Loader HCM
DataLine3|zz|33 Spreadsheet
Data Loader
3
Zip File
Initiate Spreadsheet 4
HCM Spreadsheet
Data Loader
Data Loader dat file
End
Here's a summary of how the transformation process works.

1. From the Checklist or Data Exchange work area, submit the Load Spreadsheet Data from File ow paern.
The ow is secured using these privileges:
Flow Privilege
Submit Payroll PAY_ SUBMIT_ PAYROLL_ FLOW_PRIV

Load Data using HCM Spreadsheet HRC_ LOAD_ DATA_ USING_ HSDL_PRIV
Data Loader

2. This ow paern invokes the transformation formula for the Content ID and has these tasks:
a. Generate Data Loader File
b. Initiate Spreadsheet Data Loader
3. The Generate Data Loader File task reads the data le line by line, producing an equivalent HCM Spreadsheet
Data Loader format for each line. Finally, it creates a compressed le of all of the transformed data les and
uploads it to Oracle WebCenter Content server.
4. The Initiate Spreadsheet Data Loader task takes the compressed le generated by the Generate Data Loader
File task and invokes the HCM Spreadsheet Data Loader. The HCM Spreadsheet Data Loader creates the
required data in the HCM Cloud.
306
Related Topics
• HCM Spreadsheet Data Loader Templates
• Create and Edit Spreadsheet Templates
• Guidelines for Designing Spreadsheet Templates
Sample Payroll Transformation Formula for HCM Spreadsheet

Data Loader
In this example, the transformation formula species the transformation mechanism for an incoming pipe separated
delimited le. The formula's return values are the same as the list of aributes in the template le for the User Dened
Table business object.
/* Inputs */
POSITION3 (text), POSITION4 (text), POSITION5 (text), POSITION6 (text), POSITION7 (text), POSITION8 (text)
OUTPUTVALUE='|'
OUTPUTVALUE='NONE'
ELSE IF OPERATION = 'NUMBEROFBUSINESSOBJECTS' THEN
(
OUTPUTVALUE = '1'/*Always be 1*/
RETURN OUTPUTVALUE
)
(
METADATA1[1] = 'SMUDT' /*TemplateName*/
METADATA1[2] = 'UserDefinedTable' /*FileDiscriminator*/
METADATA1[3] = 'UserDefinedTable_UserTableCode'
METADATA1[4] = 'UserDefinedTable_LegislativeDataGroupName'
METADATA1[5] = 'UserDefinedTable_UserTableName'
METADATA1[6] = 'UserDefinedTable_RangeOrMatch'
METADATA1[7] = 'UserDefinedTable_UserRowTitle'
METADATA1[8]= 'UserDefinedTable_UserKeyUnits'
RETURN METADATA1 /*You can return only one METADATA for the respective template*/
)
(
FileName = 'SMUDT'
BusinessOperation = 'HSDL'
FileDiscriminator = 'UserDefinedTable'
UserDefinedTable_UserTableCode = POSITION1
UserDefinedTable_LegislativeDataGroupName = POSITION2
UserDefinedTable_UserTableName = POSITION1
307
UserDefinedTable_RangeOrMatch = POSITION3
UserDefinedTable_UserRowTitle = POSITION4
UserDefinedTable_UserKeyUnits = POSITION5
RETURN
BusinessOperation,FileDiscriminator,FileName,UserDefinedTable_UserTableCode,UserDefinedTable_LegislativeDataGroupName,U
)
ELSE
OUTPUTVALUE='NONE'
RETURN OUTPUTVALUE
Related Topics
• Create and Edit Spreadsheet Templates
• Guidelines for Designing Spreadsheet Templates
308
Integrating with HCM Loading Talent Objects
20 Loading Talent Objects
Overview of Loading Goals, Goal Plans, and Goal Plan

Sets
You can load Goal, Goal Plan, and Goal Plan Set objects using HCM Data Loader. Most of these objects have
dependencies on other objects. This table identies the other objects that must exist in the target environment. If you're
loading some or all of those objects with goals, goal plans, or goal plan sets, then follow the load order shown in the
table.
Object Object Load Order Notes
Goal Plan 1. Worker and primary assignment • Review periods must exist in the
2. Eligibility prole target environment before you
upload associated goal plans.
3. Organization
• Organizations are required for
4. Goal plan document type
organization goal plans.
5. Goal plan
• A Goal Plan Document Types
component is required when the
IncludeInPerfDoc aribute is set to
Y.
Goal Plan Set 1. Goal plan • Review periods must exist in the
2. Worker and primary assignment target environment before you
upload associated goal plan sets.
3. Eligibility prole
• Goal Plan Set objects can refer to
4. Goal plan set
goal plans.
Goal (library) 1. Content item Library goals are loaded as content items.

Goal (organization) 1. Worker (line manager)

For organization goals:
2. Organization
3. Goal plan • The line manager is the
4. Goal organization owner.
• Goal plans are required.
Goal (template) 1. Worker (human resource specialist) Goal plans are required.
and assignment
2. Goal plan
3. Goal
Goal (worker development) 1. Worker Worker development goals aren't

2. Content item associated with goal plans.

3. Goal
Goal (worker performance) 1. Worker and assignment Worker performance goals must be
2. Goal plan associated with goal plans.

309
Object Object Load Order Notes
3. Content item
4. Goal
Related Topics
• Overview of Goal Management
Guidelines for Loading Goals

Goals represent the objectives of employees and organizations. This topic describes aspects of the Goal object that you
must understand to load goals successfully.
Goal Types
This table identies the types of goals that you can load using HCM Data Loader.
Goal Type Description
Organization goal Created by a manager for a specic organization.

Template goal Used in goal plans.

Worker goal
Assigned to a worker by a manager or human resource specialist. Two types of worker goals
exist:
• Development goals
• Performance goals
Note: You can also load library goals using HCM Data Loader. You load library goals as prole content items.
You can refer to library goals from other goal objects.
When you load goals in the Goal.dat le, you can include the GoalTypeCode aribute. This value is validated using the
HRG_GOAL_TYPE lookup type. For organization goals, GoalTypeCode must be PERFORMANCE, which is the default
value.
Goal Components
The components that you can supply when loading goals depend on the goal type. This table identies when you can
provide each component.
Goal Component Goal Type
Goal All
310
Goal Component Goal Type

Goal Action All

Goal Plan Goal • Worker performance goals

• Organization goals
• Template goals
Goal Target Outcome • Worker goals

• Template goals
Goal Measurement All

Note: You can specify only one Goal Measurement component for a development
goal.

Goal Access • Worker goals

Goal Alignment • Worker performance goals

• Organization goals
Prole Options
This table identies prole options that must be both enabled and set to Y for successful loading of goal components.
Prole Option What the Option Enables
HRG_ ENABLE_ GOAL_ALIGN Alignment of goals in the Goal Alignment component

HRG_ ENABLE_ GRANT_ACCESS Shared goals in the Goal Access component

HRG_ ENABLE_ OUTCOMES Creation of goal target outcomes in the Goal Target Outcome component

HRG_ ENABLE_TASK Creation of goal tasks in the Goal Action component

• To enable prole options, use the Manage Prole Options task.

• To set the value of a prole option, use the Manage Administrator Prole Values task.
Perform both tasks in the Setup and Maintenance work area.
311
Deleting Goals
You can delete Goal objects using HCM Data Loader. When you delete a parent Goal object, these child components are
also deleted automatically:
• Goal Access
• Goal Action
• Goal Alignment, where GoalId or AlignedGoalId identies the goal that you're deleting
• Goal Plan Goal
• Goal Target Outcome
You can also delete child components individually, if required.
Goal Measurement components aren't deleted automatically when you delete the parent goal using HCM Data Loader.
You must delete Goal Measurement components explicitly before deleting the parent goal. This example Goal.dat le
deletes a Goal Measurement component. The parent goal is identied by its source key.
METADATA|GoalMeasurement|SourceSystemId|SourceSystemOwner|GoalId(SourceSystemId)
DELETE|GoalMeasurement|GoalMeasurement_001_SSID|VISION|WorkerGoal_001_SSID
This example Goal.dat le deletes a goal and its child components, other than Goal Measurement. The goal is identied
by its source key.
METADATA|Goal|SourceSystemId|SourceSystemOwner
DELETE|Goal|WorkerGoal_001_SSID|VISION
Examples of Loading Goals

This topic provides examples showing how to load worker goals and organization goals using HCM Data Loader.
Creating a Worker Goal

This example Goal.dat le creates an active performance goal for a worker. In this le:
• The user-key aributes WorkerPersonNumber and WorkerAssignmentNumber identify the worker and the
relevant assignment.
• The user-key aribute AssignedByPersonNumber identies the human resource specialist or line manager
who's creating the goal.
• A Goal Plan Goal component must be provided.
Note: For development goals, a Goal Plan Goal component isn't required.
METADATA|Goal|SourceSystemId|SourceSystemOwner|GoalName|Description|StartDate|TargetCompletionDate|
WorkerPersonNumber|WorkerAssignmentNumber|StatusCode|GoalSourceCode|AllowKeyAttrUpdateFlag|
IncludeInPerfdocFlag|AssignedByPersonNumber
MERGE|Goal|WorkerGoal_001_SSID|VISION|WorkerGoal_001|WorkerGoal_001_Desc|2015/01/01|2015/12/31|8153787|
EEEE8153787|Not started|HR|Y|Y|8153756
METADATA|GoalPlanGoal|SourceSystemId|SourceSystemOwner|GoalId(SourceSystemId)|GoalPlanName|GoalPlanStartDate|
GoalPlanEndDate|PriorityCode
312
MERGE|GoalPlanGoal|GoalPlanGoal_001_SSID|VISION|WorkerGoal_001_SSID|GP_009_01|2015/01/01|2015/12/31|Medium
Creating a Worker Goal Against a Library Goal

This example Goal.dat le creates an active performance goal against a library goal for a worker. HCM Data Loader
doesn't take values from the library goal. Instead, you must supply these values when you load the worker goal. The
ReferenceContentItemName aribute is the user key for the library goal, which must exist.
WorkerPersonNumber|WorkerAssignmentNumber|StatusCode|GoalSourceCode|AllowKeyAttrUpdateFlag|
IncludeInPerfdocFlag|AssignedByPersonNumber|ReferenceContentItemName
MERGE|Goal|WorkerGoal_002_SSID|VISION|WorkerGoal_002|WorkerGoal_002_Desc|2015/01/01|2015/12/31|8153787|
EEEE8153787|Not started|HR|Y|Y|8153756|ZHRG-Completing Learning Path
Creating an Organization Goal

This example Goal.dat le creates and publishes an organization goal for a line manager. In this le:
• The user-key aribute AssignedByPersonNumber identies the line manager who owns the organization goal.
To publish the organization goal to the organization, set the PublishedFlag aribute to Y.
• The GoalSourceCode aribute is set to Organization owner. This value is required for organization goals.
• A Goal Plan Goal component must be provided.
OrganizationName|StatusCode|GoalSourceCode|AllowKeyAttrUpdateFlag|AssignedByPersonNumber|PublishedFlag
MERGE|Goal|OrganizationGoal_001_SSID|VISION|OrganizationGoal_001|OrganizationGoal_001_Desc|2015/01/01|
2015/12/31|Vision Corporation Enterprise|Not started|Organization owner|Y|8153786|Y
METADATA|GoalPlanGoal|SourceSystemId|SourceSystemOwner|GoalId(SourceSystemId)|GoalPlanName|GoalPlanStartDate|
GoalPlanEndDate|PriorityCode
MERGE|GoalPlanGoal|GoalPlanGoal_002_SSID|VISION|OrganizationGoal_001_SSID |GP_009_01|2015/01/01|2015/12/31|
Medium
Creating a Library Goal

Here's how to create library goals that can be referenced by other goal objects. You use ContentItem.dat, as in the
following example, to add library goals.
METADATA|ContentItem|Name|ContextName|DateFrom|ItemDescription|ItemDate1|ItemDate2|ItemText1|ItemText2|
ItemText3|ItemText5|ItemText6|ItemText7|ItemText8|ItemText9|ItemText10|ItemText11|ItemText12|ItemNumber1|
ItemNumber2|ItemNumber3|ItemNumber4|ItemNumber5|ItemNumber6|ItemTextTl2|ItemTextTl11|ItemTextTl14|
MERGE|ContentItem|HL Goal Library 2016|GOAL|2016/04/01|HL Goal Library 2016 Item Description|2016/04/01|
2016/04/30|A|LOW|STRETCH|QUANTITATIVE|MIN|PERCENT|SHORT_TERM|DEVELOPMENT|ALL|FINANCE|HLGoal2016|10|10|20|
50|50|50|ZHRA-TST-Measurement|<p>Comment for the goal category</p>|Testing Goal Library HDL|SSIDGL2016HL001|
HCMQA-001
HCMQA-001
HCMQA-001
313

HCMQA-001
After you import the .zip le containing the content items, verify you can add the new goal libraries to a user by
navigating to Me > Career and Performance > Career Development. In the Development Plan: Active Goals section,
click the Add Goal menu and select Library Goal. Conrm that the recently imported library goals appear in the
selection list.
Guidelines for Loading Goal Plans

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

When you load a Goal Plan object, the plan isn't automatically assigned to workers. You can assign the goal plan to
workers in either of these ways:
• Schedule goal plan assignments using the Manage Goal Plans task.
• Load the Goal Plan Assignment component of the goal plan.
The Mass Request Component

The Mass Request component identies who's requesting the goal plan. You can identify the plan requester on the goal
plan itself by supplying the RequestSubmissionDate and ReqSubmiedByPersonNumber aributes, for example. In
this case, the Mass Request component is created automatically and you don't have to supply it. However, you must
supply a Mass Request component when you create a goal plan:
• If you don't identify the plan requester on the Goal Plan object.
• To associate a source key with the Mass Request record.
Alternatively, you can update the default source key later using the Source Key object.
• If you're loading child components of the Mass Request component.
The child components of the Mass Request component identify the employee population to which the goal
plan is to be assigned.
Deleting Goal Plans

You can delete Goal Plan objects using HCM Data Loader. However, don't delete goal plans that have been assigned to
workers. When you delete a parent Goal Plan object, these child components are also deleted automatically:
• Goal Plan Document Types
• Mass Request
Note: When you delete a Mass Request component, its child components are deleted automatically.
314
You can also delete child components individually, if required.
Goal Plan Goal and Goal Plan Assignment components aren't deleted automatically when you delete the parent Goal
Plan component using HCM Data Loader. You must delete those components explicitly before you delete the parent
goal plan. This example GoalPlan.dat le deletes the Goal Plan Goal component that links goal plan GP_001_01 with
template goal TemplateGoal_001.
METADATA|GoalPlanGoal|SourceSystemId|SourceSystemOwner|GoalPlanExternalId
DELETE|GoalPlanGoal|GPG_001_01_SSID|VISION|GP_001_01
This example Goal.dat le deletes the template goal TemplateGoal_001 (SourceSystemId: TemplateGoal_001_SSID).
METADATA|Goal|SourceSystemId|SourceSystemOwner
DELETE|Goal|TemplateGoal_001_SSID|VISION
This example GoalPlan.dat le deletes the goal plan GP_001_01 and relevant child records.
METADATA|GoalPlan|GoalPlanExternalId
DELETE|GoalPlan|GP_001_01
Related Topics
• Goal Plans
Examples of Loading Goal Plans

This topic provides examples showing how to load Goal Plan objects using HCM Data Loader.
Creating a Goal Plan

This example GoalPlan.dat le loads a goal plan without a Mass Request component. In this case, a mass request
record for the goal plan is created automatically using the values passed for the ReqSubmiedByPersonNumber and
RequestSubmissionDate aributes.
METADATA|GoalPlan|GoalPlanExternalId|GoalPlanName|GoalPlanTypeCode|GoalPlanActiveFlag|EnableWeightingFlag|
StartDate|EndDate|EnforceGoalWeightFlag|GoalAccessLevelCode|IncludeInPerfdocFlag|ReqSubmittedByPersonNumber|
RequestSubmissionDate|ReviewPeriodName
MERGE|GoalPlan|GP_001_01|GP_001_01|ORA_HRG_WORKER|A|Y|2015/01/01|2015/12/31|Y|HR specialist and manager|N|
8153756|2015/09/20|Default Review Period - Vision Corporation Enterprise
Creating a Goal Plan with Document Types

This example GoalPlan.dat le creates a goal plan with the IncludeInPerfdocFlag aribute set to Y and assigns a
document type.
StartDate|EndDate|EnforceGoalWeightFlag|GoalAccessLevelCode|IncludeInPerfdocFlag|ReqSubmittedByPersonNumber|
RequestSubmissionDate|ReviewPeriodName
MERGE|GoalPlan|GP_001_02|GP_001_02|ORA_HRG_WORKER|A|Y|2016/01/01|2016/12/31|Y|HR specialist and manager|Y|
8153756|2016/10/04|Default Review Period - Vision Corporation Enterprise
METADATA|GoalPlanDocTypes|GoalPlanExternalId|DocTypeName
MERGE|GoalPlanDocTypes|GP_001_02|Annual Evaluations
315
Creating a Goal Plan with Eligibility Criteria

This example GoalPlan.dat le creates a goal plan with Mass Request and Eligibility Prole Object components.
StartDate|EndDate|EnforceGoalWeightFlag|GoalAccessLevelCode|IncludeInPerfdocFlag|ReviewPeriodName
MERGE|GoalPlan|GP_001_04|GP_001_04|ORA_HRG_WORKER|A|Y|2016/01/01|2016/12/31|Y|HR specialist and manager|N|
Default Review Period - Vision Corporation Enterprise
METADATA|MassRequest|GoalPlanExternalId|ReqSubmittedByPersonNumber
MERGE|MassRequest|GP_001_04|8153756
METADATA|EligibilityProfileObject|GoalPlanExternalId|EligibilityProfileName|RequiredFlag
MERGE|EligibilityProfileObject|GP_001_04|Goals_EligibilityProfile_Software Developer 4|Y
Guidelines for Loading Goal Plan Sets

Goal plan sets are used for the mass assignment of related goal plans to worker populations. This topic describes
aspects of the Goal Plan Set object that you must understand to load goal plan sets successfully.
Assigning Goal Plan Sets to Workers

When you load a goal plan set, it's not automatically assigned to workers. You can assign the goal plan set to workers in
either of these ways:
• Schedule goal plan set assignments using the Manage Goal Plan Sets task.
• Load the Goal Plan Assignment component of the Goal Plan object. You may use this approach, for example, to
assign goals following the transfer of workers from one legal entity to another.
The Mass Request Component

The Mass Request component identies who's requesting the goal plan set. You can identify the plan requester on the
goal plan set itself by supplying the RequestSubmissionDate and ReqSubmiedByPersonNumber aributes, for
example. In this case, the Mass Request component is created automatically and you don't have to supply it. However,
you must supply a Mass Request component when you create a goal plan set:
• If you don't identify the plan requester on the Goal Plan Set object.
• To associate a source key with the mass request record.
Alternatively, you can update the default source key later using the Source Key object.
• If you're loading child components of the Mass Request component.
The child components of the Mass Request component identify the employee population to which the goal
plan set is to be assigned.
316
Deleting Goal Plan Sets

You can delete Goal Plan Set objects using HCM Data Loader. When you delete a parent goal plan set, these child
components are also deleted automatically:
• Goal Plan Set Plan

• Mass Request
Note: When you delete a Mass Request component, its child components are deleted automatically.
Don't delete goal plan sets that have already been assigned to workers.
This example GoalPlanSet.dat le deletes a goal plan set and its child components.
METADATA|GoalPlanSet|GoalPlanSetExternalId
DELETE|GoalPlanSet|GPS_006_01
Related Topics
• Goal Plan Sets
Examples of Loading Goal Plan Sets

This topic provides examples showing how to load Goal Plan Set objects using HCM Data Loader.
Creating a Goal Plan Set with Goal Plans

This example GoalPlanSet.dat le creates a goal plan set and includes two goal plans.
METADATA|GoalPlanSet|GoalPlanSetExternalId|GoalPlanSetName|Description|GoalPlanSetActiveFlag|StartDate|
EndDate|ReqSubmittedByPersonNumber|RequestSubmissionDate| ReviewPeriodName
MERGE|GoalPlanSet|GPS_002_01|GPS_002_01|GPS_002_01|A|2015/01/01|2015/12/31|8153756|2015/09/28|Default Review
Period - Vision Corporation Enterprise
COMMENT Assign two goal plans without worker or eligibility profile assignment to the goal plan set
METADATA|GoalPlanSetPlan|GoalPlanSetExternalId|GoalPlanExternalId|Weighting
MERGE|GoalPlanSetPlan|GPS_002_01|GP_001_02|60
MERGE|GoalPlanSetPlan|GPS_002_01|GP_001_03|40
In this example, the goal plan set has no Mass Request component. Therefore, the mass request record for the goal
plan set is created automatically using the ReqSubmiedByPersonNumber and RequestSubmissionDate aribute
values.
Creating a Goal Plan Set with a Mass Request Component

This example GoalPlanSet.dat le creates a goal plan set with a Mass Request component. You don't provide the
ReqSubmiedByPersonNumber and RequestSubmissionDate aributes for the Goal Plan Set component in this case.
EndDate|ReviewPeriodName
317
MERGE|GoalPlanSet|GPS_001_02|GPS_001_02|GPS_001_02|A|2016/01/01|2016/12/31|Default Review Period - Vision

Corporation Enterprise
METADATA|MassRequest|GoalPlanSetExternalId|ReqSubmittedByPersonNumber
MERGE|MassRequest|GPS_001_02|8153756
Creating a Goal Plan Set with Mass Request and Mass Request
Hierarchy Components
This example GoalPlanSet.dat le creates a goal plan set with Mass Request and Mass Request Hierarchy components.
EndDate|ReviewPeriodName
MERGE|GoalPlanSet|GPS_001_04|GPS_001_04|GPS_001_04|A|2016/01/01|2016/12/31|Default Review Period - Vision
Corporation Enterprise
METADATA|MassRequest|GoalPlanSetExternalId|ReqSubmittedByPersonNumber
MERGE|MassRequest|GPS_001_04|8153756
COMMENT Assigning goal plan set GPS_001_04 to manager and reports
METADATA|MassRequestHierarchy|GoalPlanSetExternalId|ManagerAssignmentNumber|CascadingLevel
MERGE|MassRequestHierarchy|GPS_001_04|EEEE8153786|999999
Examples of Loading Mass Actions for Performance

Documents
Using HCM Data Loader, you can create performance documents in bulk. This topic provides examples showing how
to load Mass Actions for Performance Documents objects with Aachment and Participants components. In these
examples, all components are referenced by their user keys.
Loading Mass Actions for Performance Documents

This example PerfDocComplete.dat le creates a performance document for a specied worker assignment.
METADATA|PerfDocComplete|AssignmentNumber|CustomaryName|StartDate|EndDate|Operation|ManagerAssignmentNumber
MERGE|PerfDocComplete|EEEEE100000017121468|zhra-kudosintegration2018|2018/01/01|2018/12/31|ORA_CREATE_PD|
EEEE8153756
The Operation aribute identies the action to be performed. The following table lists valid operation values, indicates
whether they're dened in the Performance Administration Action lookup (ORA_HRA_ADMIN_ACTION), and provides
information about any dependencies.
Note: If you need to mass update participants or aachments, you must delete and load them again via HCM
Data Loader.
Operation Value Dened in Lookup Notes
ORA_CREATE_PD Yes Creates a performance document. The

performance template period and worker
assignment must exist.
318
Operation Value Dened in Lookup Notes
ORA_ COMPLETE_PD Yes Completes a performance document. The

performance document must exist.

ORA_CANCEL_PD Yes Cancels a performance document. The

performance document must exist.

ORA_DELETE_PD Yes
Deletes a performance document. The
performance document must exist and its
status must be Canceled.
ORA_ ADD_ PARTICIPANT No Use this value for all supported actions on
performance document participants.

ORA_ATTACH_PD No Use this value for all supported actions on

performance document aachments.

Specify dates and a manager assignment number for the performance document only to override the default values
from the performance template.
Loading Aachments
This example PerfDocComplete.dat le loads an aachment to an existing performance document.
METADATA|PerfDocComplete|AssignmentNumber|CustomaryName|Operation
MERGE|PerfDocComplete|EEEE8153772|zhra-kudosintegration2018|ORA_ATTACH_PD
METADATA|Attachment|CustomaryName|AssignmentNumber|Title|DataTypeCode|URLorTextorFileName|MimeType|File|
Description
MERGE|Attachment|zhra-kudosintegration2018|EEEE8153772|JBlum Resume|FILE|jblum.txt|text/plain|jblum.txt|Jorge
Blum Resume
These rules apply when you load aachments:

• You must include the parent performance document in the PerfDocComplete.dat le. Set the Operation
aribute to ORA_ATTACH_PD for both MERGE and DELETE instructions for the Aachment component.
• The MimeType value is the Multipurpose Internet Mail Extensions (MIME) value, as dened and standardized
by the Internet Engineering Task Force in RFC 6838.
• The aachment itself is a binary large object, referenced by the File aribute. You include the aachment in the
BlobFiles folder in the .zip le that you upload.
• You can only bulk delete aachments and load them again. Update action isn't supported.
Loading Participants
This example PerfDocComplete.dat le deletes a participant record from an existing performance document.
319
METADATA|PerfDocComplete|AssignmentNumber|CustomaryName|Operation
MERGE|PerfDocComplete|EEEE8153772|FY2018 Annual Performance Evaluation with Participant Feedback|
ORA_ADD_PARTICIPANT
METADATA|Participant|AssignmentNumber|CustomaryName|ParticipantRoleTypeCode|ParticipantPersonNumber
DELETE|Participant|EEEE8153772|FY2018 Annual Performance Evaluation with Participant Feedback|Colleague|
ZHRA-8154961
These rules apply when you load participants:

• When you create participants, the parent performance document must already exist. You can't both create a
performance document and add a participant in the same PerfDocComplete.dat le.
• You must include the parent performance document in the PerfDocComplete.dat le. Set the Operation
aribute to ORA_ADD_PARTICIPANT for both MERGE and DELETE instructions for the Participants
component.
• The participant person record, as identied by the ParticipantPersonNumber aribute value, must exist.
• The ParticipantRoleTypeCode value must have been selected in the performance template.
• You can only bulk delete participants and load them again. Update action isn't supported.
Related Topics
• Options for Creating Performance Documents
• Complete Performance Documents Task
• Delete Performance Documents Task
• Participant Feedback Requests in Performance Documents
Examples of Loading Succession Plans

A succession plan identies a group of workers as candidates to replace key personnel in an organization. The workers
are those who are ready now, or can develop the necessary skills, for jobs and positions that aren't currently vacant.
Succession plans include assessments of a worker's readiness to move into a vacancy and the risk and impact of the
worker's loss. This topic provides some examples showing how to load succession plans.
Creating Succession Plans

This example SuccessionPlan.dat le creates an incumbent succession plan using source keys.
METADATA|SuccessionPlan|SourceSystemOwner|SourceSystemId|PlanName|PlanType|Status|AccessTypeCode|
IncumbentPersonId(SourceSystemId)
MERGE|SuccessionPlan|VISION|SP816003|Name of the incumbent succession plan|INCUMBENT|ACTIVE|PRIVATE|VISION006
METADATA|SuccessionPlanOwner|SourceSystemOwner|SourceSystemId|PlanId(SourceSystemId)|OwnerTypeCode|
PersonId(SourceSystemId)
MERGE|SuccessionPlanOwner|VISION|SPO816003|SP816003|ADMINISTRATOR|VISION013
METADATA|SuccessionPlanCandidate|SourceSystemOwner|SourceSystemId|PlanId(SourceSystemId)|
PersonId(SourceSystemId)|Status|CandidateReadiness
MERGE|SuccessionPlanCandidate|VISION|SPC816003|SP816003|VISION014|ACTIVE|READY_NOW
This example SuccessionPlan.dat le creates a job succession plan. It uses user keys to reference the job to which the
succession plan relates, the succession plan owner, and its candidates.
METADATA|SuccessionPlan|SourceSystemOwner|SourceSystemId|PlanName|PlanType|Status|AccessTypeCode|JobCode|
JobSetCode
MERGE|SuccessionPlan|VISION|SP_MRKT_DIR|Name of the job succession plan|JOB|ACTIVE|PRIVATE|HSDL_MRKT_DIR|
COMMON
320
METADATA|SuccessionPlanOwner|SourceSystemOwner|SourceSystemId|PlanId(SourceSystemId)|OwnerTypeCode|
PlanOwnerPersonNumber
MERGE|SuccessionPlanOwner|VISION|SPO_MRKT_DIR|SP_MRKT_DIR|ADMINISTRATOR|1023853
METADATA|SuccessionPlanCandidate|SourceSystemOwner|SourceSystemId|PlanId(SourceSystemId)|
PlanCandidatePersonNumber|Status|CandidateReadiness
MERGE|SuccessionPlanCandidate|VISION|SPC009_MRKT_DIR|SP_MRKT_DIR|1023119|ACTIVE|READY_NOW
These rules apply when you create a succession plan using HCM Data Loader:
• You must supply a Success Plan Owner component, and the OwnerTypeCode aribute must be
ADMINISTRATOR. A succession plan must always have an administrator owner.
• Incumbents, plan owners, and plan candidates must have active assignments.
Examples of Loading Talent Pools

A talent pool is a group of workers. You use talent pools to manage the development of the pool members for specic
purposes. For example, you can track potential candidates for a succession plan in a talent pool or create a talent review
meeting based on a talent pool. This topic provides examples showing how to create and manage talent pools using
HCM Data Loader.
Creating a Talent Pool

A talent pool can reference any combination of job, job family, model prole, position, department, and grade. These
objects, which can dene the purpose of the talent pool, have no eect on its processing. However, they must exist in
the target environment before you load a talent pool that references them. This example TalentPool.dat le creates a
talent pool for a job. Source keys are used to identify both the talent pool and the associated job.
METADATA|TalentPool|SourceSystemOwner|SourceSystemId|PoolName|PoolTypeCode|Description|
OwnerPersonId(SourceSystemId)|Status|JobId(SourceSystemId)
MERGE|TalentPool|VISION|TP_T1|Job Chief Exec|TALENT|Talent pool description|1008|A|93079
Always set the PoolTypeCode aribute to TALENT. You must include the Status aribute. If you supply no value, then
the default status is A (Active). Set the status to I (Inactive) to inactivate the talent pool.
The Talent Pool component denes the talent pool and the initial pool owner. To identify additional pool owners, you
use the Talent Pool Owner component. Additional pool owners are optional, but multiple owners are recommended.
Talent pool owners can see talent pools in the application. Use the Talent Pool Member component to dene the pool
members. This example TalentPool.dat le creates a talent pool with pool members. Source keys are used to identify
the talent pool and reference foreign objects.
METADATA|TalentPool|SourceSystemOwner|SourceSystemId|PoolName|PoolTypeCode|Description|
OwnerPersonId(SourceSystemId)|Status
MERGE|TalentPool|VISION|TP_T2|Member Talent Pool|TALENT|Talent pool description|1011|A
METADATA|PoolMember|SourceSystemOwner|SourceSystemId|PoolId(SourceSystemId)|MemberId(SourceSystemId)
MERGE|PoolMember|VISION|TP_PM_T2_1012|TP_T2|1012
MERGE|PoolMember|VISION|TP_PM_T2_1013|TP_T2|1013
321
Translating a Talent Pool Name

This example TalentPoolTranslation.dat le translates the name of an existing talent pool. It identies the existing
record by its source key.
METADATA|TalentPoolTranslation|SourceSystemOwner|SourceSystemId|PoolName|Language
MERGE|TalentPoolTranslation|VISION|TP_T1|Spanish Translated Pool Name|ES
MERGE|TalentPoolTranslation|VISION|TP_T1|French Translated Pool Name|FR
This example TalentPoolTranslation.dat le translates the name of an existing talent pool. It identies the existing
record by its user key.
METADATA|TalentPoolTranslation|BasePoolName|PoolStatus|PoolName|Language
MERGE|TalentPoolTranslation|Job Chief Exec|A|Spanish Translated Pool Name|ES
MERGE|TalentPoolTranslation|Job Chief Exec|A|French Translated Pool Name|FR
Deleting Talent Pools

You can delete a talent pool using HCM Data Loader. You can also:
• Make the talent pool inactive.

• Delete talent pool owners, provided that at least one pool owner remains.
• Delete Talent Pool Member components.
This example TalentPool.dat le deletes an existing Talent Pool Owner component. It identies the pool owner record
by its source key.
METADATA|PoolOwner|SourceSystemOwner|SourceSystemId
DELETE|PoolOwner|VISION|TP_PO_T2_3423
This example deletes the Talent Pool, itself. When you delete this parent object, you also delete its children, such as
Talent Pool Owner.
METADATA|TalentPool|PoolName|PoolTypeCode|Status
DELETE|TalentPool|Test KV 3|TALENT|A
Related Topics
• Talent Pools
Guidelines for Loading Talent Prole Data

The talent prole objects are Talent Prole, Content Item, Content Items Relationship, Education Establishment,
and Rating Model. This topic describes aspects of the talent prole objects that you must understand to load them
322
Loading Talent Proles

Talent proles include person proles and model proles. A person prole contains information about a worker's skills,
qualications, accomplishments, and career preferences. A model prole contains information about the skills and
qualications required for a job or position. You can load both person and model proles using HCM Data Loader.
The following table summarizes key information about some components of the Talent Prole object.
Prole Item Holds the data for a content item. Content items are skills, qualications, and qualities
belonging to content types in the content library. For example, Communication Skills may be
a content item in the Competencies content type. Prole Item components must be unique in
the prole.

Note: Duplicate prole items have the same qualiers and overlapping start and
end dates.

Prole Keyword Holds keywords for areas of expertise and areas of interest in person proles.

Not valid for model proles.

Prole Relation
Links a model prole to a job or position. These rules apply:
• You can't link a model prole to a job family or organization when you upload the
prole using HCM Data Loader. Any model prole that you load for those structures is
therefore for information purposes only.
• You can't associate a job or position more than once with the same prole.
Not valid for person proles.
A person can have only one person prole. You must supply a reference to the person for whom you're creating the
person prole. You must not supply a person reference for a model prole.
Note: The Description aribute of the Talent Prole object isn't required. However, you're recommended
always to provide it for a person prole and include the worker name. Otherwise, the person prole doesn't
appear in search results when you perform a basic search on the Search: Proles page.
Loading Content Items

A content item is a specic occurrence of a content type. The associated content types and their eld properties must
exist in the target environment before you load content items to the content library. The eld properties of the content
type represent the information that you can capture for the content item.
323
Loading Content Items Relationships

A content items relationship denes the relationship between two content items. A content item can be either the
parent or the child of another content item. These rules apply:
• The two content items must belong to dierent content types.

• You can't create more than one relationship between the same two content items. For example, content item A
can't be both the parent and the child of content item B.
• You can't create a relationship between a content item and itself.
• The start and end dates of the content items relationship must not be outside the date ranges of the associated
content items.
• The relationship between the associated content types must exist in the target environment before you load
the related content items.
Loading Education Establishments

An education establishment is a school, college, university, or other organization that workers select when they add
education information to their proles. You may obtain a list of education establishments from a third party, for
example. You can upload this information using HCM Data Loader.
These geography structures must exist in the target environment before you load education establishments that refer
to them:
• Country
• State or Province
Loading Rating Models

You use rating models to rate workers on their performance and prociency in the skills and qualities in the person
prole. You can also use rating models to specify target prociency levels for items in a model prole. You must include
the parent Rating Model component in the same le as any child Rating Level and Rating Category components that
you're loading.
Related Topics
• Oracle Fusion Prole Management Components: How They Work Together
Examples of Loading Talent Review Meetings

Talent review meetings are the main component of the talent review process, which evaluates trends, assesses
strengths, and addresses areas of risk for the organization. Participants in the talent review meeting review worker
prole, performance, goals, and compensation data. This topic shows how to create a talent review meeting using HCM
Data Loader and how to update the facilitator for an existing meeting.
324
Creating a Talent Review Meeting

This example TalentReviewMeeting.dat le creates a Talent Review Meeting object. The meeting has Facilitator,
Participant, Reviewee, Review Content, Talent Pool, and Succession Plan components.
Note: Source keys identify each record. You must use source keys if you plan to update the facilitator,
participant, or reviewee records later. The user key for these records includes the person number. Therefore,
you can't update the person number to refer to a dierent person if you're identifying the record by the user
key alone. You're recommended always to use source keys when creating talent review meetings so that you
can update the meetings as necessary.
COMMENT * Talent Review Meeting *
METADATA|TalentReviewMeeting|SourceSystemOwner|SourceSystemId|DashboardTemplateName|DataSubmitDate|
MeetingDate|MeetingInstructions|MeetingLeaderId(SourceSystemId)|MeetingStatusCode|MeetingSubmitStatusCode|
MeetingTitle|DataValidityCode
MERGE|TalentReviewMeeting|VISION|MrktMgr071018|ZHRR Overall Talent Review Meeting Template|2019/01/01|
2020/07/02|Instructions for Meeting|HDL010|NOT_STARTED|DRAFT|HDL Marketing Talent Review Meeting 0710 1300|
ONE_MONTH
COMMENT * Prior Rating Date Range *
METADATA|PriorRatingDateRange|SourceSystemOwner|SourceSystemId|MeetingId(SourceSystemId)|FromDate|ToDate
MERGE|PriorRatingDateRange|VISION|MrktMgr071018_PDR|MrktMgr071018|2019/01/01|2019/08/04
COMMENT * Facilitator *
METADATA|Facilitator|SourceSystemOwner|SourceSystemId|MeetingId(SourceSystemId)|
FacilitatorPersonId(SourceSystemId)
MERGE|Facilitator|VISION|MrktMgr071018_Fac1|MrktMgr071018|HDL013
COMMENT * Participant *
METADATA|Participant|SourceSystemOwner|SourceSystemId|MeetingId(SourceSystemId)|DataSubmissionStatusCode|
ParticipantPersonId(SourceSystemId)|ParticipantTypeCode
MERGE|Participant|VISION|MrktMgr071018_Part|MrktMgr071018|NOT_STARTED|HDL003|PARTICIPANT
COMMENT * Reviewees *
METADATA|Reviewee|SourceSystemOwner|SourceSystemId|MeetingId(SourceSystemId)|RevieweePersonId(SourceSystemId)
MERGE|Reviewee|VISION|MrktMgr071018_Rev1|MrktMgr071018|HDL009
MERGE|Reviewee|VISION|MrktMgr071018_Rev2|MrktMgr071018|HDL007
COMMENT * Review Content *
METADATA|ReviewContent|SourceSystemOwner|SourceSystemId|MeetingId(SourceSystemId)|MeetingTitle|Rating|
UseAsAxisFlag
MERGE|ReviewContent|VISION|MrktMgr071018_Rate_Perf|MrktMgr071018|HDL Marketing Talent Review Meeting 0710
1300|Performance|Y
MERGE|ReviewContent|VISION|MrktMgr071018_Rate_Pot|MrktMgr071018|HDL Marketing Talent Review Meeting 0710 1300|
Potential|N
MERGE|ReviewContent|VISION|MrktMgr071018_Rate_Impct|MrktMgr071018|HDL Marketing Talent Review Meeting 0710
1300|Impact of Loss|Y
MERGE|ReviewContent|VISION|MrktMgr071018_Rate_Risk|MrktMgr071018|HDL Marketing Talent Review Meeting 0710
1300|Risk of Loss|N
MERGE|ReviewContent|VISION|MrktMgr071018_Rate_Comp|MrktMgr071018|HDL Marketing Talent Review Meeting 0710
1300|Overall Competencies Rating|Y
MERGE|ReviewContent|VISION|MrktMgr071018_Rate_Goals|MrktMgr071018|HDL Marketing Talent Review Meeting 0710
1300|Overall Goals Rating|Y
MERGE|ReviewContent|VISION|MrktMgr071018_Rate_Talent|MrktMgr071018|HDL Marketing Talent Review Meeting 0710
1300|Talent Score|N
COMMENT * Talent Pool *
METADATA|TalentPool|SourceSystemOwner|SourceSystemId|MeetingId(SourceSystemId)|PoolId(SourceSystemId)
MERGE|TalentPool|VISION|MrktMgr071018_TP|MrktMgr071018|HDLTP_MKTMGR
COMMENT * Succession Plan *
METADATA|SuccessionPlan|SourceSystemOwner|SourceSystemId|MeetingId(SourceSystemId)|PlanId(SourceSystemId)
MERGE|SuccessionPlan|VISION|MrktMgr071018_SP|MrktMgr071018|SP_MRKT_MGR
325
These rules apply to Talent Review Meeting objects that you create using HCM Data Loader:
• The DashboardTemplateName aribute identies the conguration template used for the meeting. The
template is created in the Setup and Maintenance work area using the Congure Talent Review Dashboard
Options task. The referenced template must exist before you load the talent review meeting record.
• Any facilitator, participant, reviewee, talent pool, and succession plan records that are referenced by the talent
review meeting record must already exist. Alternatively, you can include them in the same .zip le.
• You must identify at least one facilitator.
• The MeetingStatusCode aribute must be set to NOT_STARTED and the MeetingSubmitStatusCode
aribute can be set to either DRAFT or SCHEDULED for new talent review meetings.
Updating a Talent Review Meeting

The following table lists actions that you can perform when updating a talent review meeting using HCM Data Loader.
Permied actions depend on the meeting status.
Meeting Status Permied Actions
Not started • Change the meeting template.

• Change the meeting status to In progress or Canceled.
• Add or remove reviewees, participants, and facilitators.
In progress • Change the meeting status to Not started or Canceled.

• Add or remove reviewees, participants, and facilitators.
Complete Update the facilitator.

Canceled
Change the meeting status to Not started.
Process job in progress None.

Process job error None.

Updating the Facilitator

This example TalentReviewMeeting.dat le updates the facilitator for an existing meeting. This example uses source
keys. You can't use user keys alone to update the facilitator, as the FacilitatorPersonNumber aribute that identies
the new facilitator also identies the record to update.
METADATA|Facilitator|SourceSystemOwner|SourceSystemId|MeetingId(SourceSystemId)|
FacilitatorPersonId(SourceSystemId)
MERGE|Facilitator|VISION|MrktMgr071018_Fac1|MrktMgr071018|HDL014
326
Tip: If you're making multiple changes to the same talent review meeting, then include the Talent Review
Meeting record in the same .dat le to ensure that all changes are processed together.
Related Topics
• Talent Review
• Talent Review Template
FAQs for Loading Talent Objects

How can I transfer two performance documents in HCM Data
Loader from an employee's old assignment to the new assignment
when the performance documents are associated with dierent
review periods?
Create one le including both performance documents for the employee, but don't add the review period and then both
the performance documents will be loaded. Or create a dierent le for each performance document and include the
specic review period.
Can I load any type of requisition using the Requisition object?

No. You can load:
• Vacancies, which are placeholders for future headcount. Use vacancies if you don't have a dedicated recruiting
application.
• Oracle Talent Acquisition Cloud requisitions.
You can't load Oracle Recruiting Cloud requisitions using the Requisition object. To load Oracle Recruiting Cloud
requisitions, use the Job Requisition object.
327
328
Integrating with HCM Loading Learning Objects
21 Loading Learning Objects
Examples of Loading Classroom Resources

A classroom resource is the location of an on-site, instructor-led activity. This topic shows how to load Classroom
Resource objects using HCM Data Loader.
Creating Classroom Resources

This example ClassroomResource.dat le shows how to create a Classroom Resource object using source keys.
COMMENT Create a Classroom Resource object using source keys
METADATA|ClassroomResource|SourceSystemOwner|SourceSystemId|ClassroomResourceNumber|Title|Description|
Capacity|ContactId(SourceSystemId)|LocationId(SourceSystemId)|OwnedByPersonId(SourceSystemId)
MERGE|ClassroomResource|VISION|201803081352|RSC-201803081352-HDL|Title:RSC 201803081352 HDL|Desc:RSC
201803081352 HDL|30|300213211235|StLouisMO|300213211235
This example ClassroomResource.dat le shows how to create a Classroom Resource object using user keys.
COMMENT Create a Classroom Resource object using user keys
METADATA|ClassroomResource|ClassroomResourceNumber|Title|Description|Capacity|ContactNumber|LocationCode|
SetCode|OwnedByPersonNumber
MERGE|ClassroomResource|RSC-201803081355-HDL|Title:RSC 201803081355 HDL|Desc:RSC 201803081355 HDL|30|8153757|
DDT_US_Allenton _St Louis_MO|COMMON|8153757
Examples of Loading Course Oering Pricing Defaults

Course Oering Pricing Defaults objects are the default pricing-rule values for a course oering. This topic shows how
to load Course Oering Pricing Defaults objects using HCM Data Loader.
Creating Course Oering Pricing Defaults

This example CourseOeringPricingDefaults.dat le identies the Course Oering Pricing Defaults object by its user
key.
METADATA|CourseOfferingPricingDefaults|EffectiveStartDate|PricingRuleNumber|CurrencyCode|OfferingType|
CourseNumber
MERGE|CourseOfferingPricingDefaults|2018/02/04|PR-201802041720-HDL|USD|ORA_SP|COURSE-201802041711-HDL
329
Creating Course Oering Pricing Components

You can create one or more Course Oering Pricing Components for a Course Oering Pricing Defaults object. This
example CourseOeringPricingDefaults.dat le creates two Course Oering Pricing Components, which are identied
by their user keys.
METADATA|CourseOfferingPricingComponent|EffectiveStartDate|PricingComponentNumber|PricingComponentType|Price|
IncludeInSelfServicePricing|Required|PricingRuleNumber
MERGE|CourseOfferingPricingComponent|2018/02/04|PC-201802041721-HDL|ORA_LIST_PRICE|100|N|N|PR-201802041720-HDL
MERGE|CourseOfferingPricingComponent|2018/02/04|PC-201802041722-HDL|ORA_LIST_PRICE_ADJ|200|N|N|
PR-201802041720-HDL
Guidelines for Loading Courses

A course is teaching on a single subject with specic outcomes. A course has oerings that the learner can take to
achieve the course outcomes. For example, a course may have one oering that's instructor led and another that's self-
paced with an associated video. A Course object provides administrative information about the course. It includes one
or more Oering components, each of which provides administrative information about a single oering. This topic
describes aspects of the Course object that you must understand to load courses successfully using HCM Data Loader.
Oering Components
These rules apply to Oering components that you load using HCM Data Loader:
• Valid values of the Oering Type aribute are dened in the ORA_WLF_LEARN_DELIVERY_MODE lookup type.
Supply one of these values:
Oering Type Value Meaning
ORA_BLENDED Blended

ORA_SP Self-paced

ORA_ILT Instructor-led

You can't update the oering type of an existing oering.

• The Oering component references an evaluation using the Questionnaire object named on the
QuestionnaireCode aribute. To identify the default evaluation, set the aribute to -1.
330
Instructor Led Activity Components

You must supply a value for either the VirtualClassroomURL or the ClassroomResourceNumber aribute. If you
supply:
• A VirtualClassroomURL value, then the current activity is an online activity

• A ClassroomResourceNumber value, then the current activity is an on-site activity
• Both VirtualClassroomURL and ClassroomResourceNumber values, then the current activity is an on-site
activity
The Instructor Led Activity component has child components that identify resources required for the activity.
• You can identify a single classroom resource on the Instructor Led Activity component itself. To identify
additional classroom resources, use the Classroom Reservation component. The Classroom Resource object
referenced from the Classroom Reservation component must exist.
• To add instructors, use the Instructor Reservation component. The Instructor Resource object referenced from
the Instructor Reservation component must exist
Self-Paced Activity Components

If you supply a value for the ContentNumber aribute, then the activity is classied as a self-paced, online activity.
Otherwise, the activity is classied as a self-paced, oine activity.
Related Topics
• Programmatic Loading of Rich Media Content (2374277.1)
Examples of Loading Courses

This topic provides examples showing how to load Course objects and their components using HCM Data Loader.
Loading Course Objects

This example Course.dat le shows how to load a Course object using user keys.
METADATA|Course|EffectiveStartDate|CourseNumber|Title|ShortDescription|PublishStartDate|PublishEndDate|
MinimumExpectedEffort|MaximumExpectedEffort|CurrencyCode|MinimumPrice|MaximumPrice|TrailerLiNumber|
OwnedByPersonNumber|SourceType|SourceId|SourceInfo
MERGE|Course|2018/02/04|COURSE-201802041711-HDL|Title:COURSE 201802041711|ShortDesc:COURSE201802041711|
2018/02/04|2019/02/03|0|1|USD|0|0|OLC103778|8153757|FUSION_HCM_LEARNING|201802041711|HCM Learning Source Info
for 201802041711 HDL Update
Loading Oering Components

This example Course.dat le shows how to load Oering components using user keys.
331
METADATA|Offering|EffectiveStartDate|OfferingNumber|Title|OfferingType|PublishStartDate|PublishEndDate|
LanguageCode|MinimumCapacity|MaximumCapacity|QuestionnaireCode|QstnrRequiredForCompletion|CourseNumber|
OwnedByPersonNumber|SourceType|SourceId|SourceInfo
MERGE|Offering|2018/02/04|OFFERING-201802041712-HDL|Title:Offering 201802041712|ORA_BLENDED|2018/02/04|
2019/02/03|US|5|30|-1|N|COURSE-201802041711-HDL|8153757|FUSION_HCM_LEARNING|201802041712|HCM Learning Source
Info for 201802041712
Loading Instructor Led Activity Components

This example Course.dat le shows how to load Instructor Led Activity components using user keys. It shows how to
load child components of the Instructor Led Activity, such as Classroom Reservation and Instructor Reservation, to
support the activity.
METADATA|InstructorLedActivity|EffectiveStartDate|ActivityNumber|Title|ActivityDate|ActivityStartTime|
ActivityEndTime|TimeZone|ExpectedEffort|SelfCompleteFlag|OfferingNumber|VirtualClassroomUrl|
ClassroomResourceNumber|SourceType|SourceId|SourceInfo
MERGE|InstructorLedActivity|2018/02/04|ILT-ACT-201802041713-HDL|Title:ILT ACT 201802041713|2018/02/04|
10:00:00|19:00:00|America/Los_Angeles|30|Y|OFFERING-201802041712-HDL|http://www.example.com|RSC-201802041710-
HDL|FUSION_HCM_LEARNING|201802041713|HCM Learning Source Info for 201802041713
COMMENT Load two Ad Hoc Resource components
METADATA|AdhocResource|AdhocResourceNumber|Name|Description|Quantity|ActivityNumber
MERGE|AdhocResource|ADHOC-201802041714-HDL|SS-ADHOC-RESOURCE-1|SS-ADHOC-RESOURCE-1 DESC|30|ILT-
ACT-201802041713-HDL
MERGE|AdhocResource|ADHOC-201802041715-HDL|SS-ADHOC-RESOURCE-2|SS-ADHOC-RESOURCE-2 DESC|30|ILT-
ACT-201802041713-HDL
COMMENT Load one Classroom Reservation component
METADATA|ClassroomReservation|ClassroomReservationNumber|ClassroomResourceNumber|ActivityNumber
MERGE|ClassroomReservation|CRSV-201802041716-HDL|OLC136311|ILT-ACT-201802041713-HDL
COMMENT Load two Instructor Reservation components
METADATA|InstructorReservation|InstructorReservationNumber|InstructorResourceNumber|ActivityNumber
MERGE|InstructorReservation|INSTR-201802041717-HDL|8153762|ILT-ACT-201802041713-HDL
MERGE|InstructorReservation|INSTR-201802041718-HDL|8153771|ILT-ACT-201802041713-HDL
Loading Self-Paced Activity Components

This example Course.dat le shows how to load Self-Paced Activity components using user keys.
METADATA|SelfPacedActivity|EffectiveStartDate|ActivityNumber|ActivityPosition|Title|ExpectedEffort|
SelfCompleteFlag|ContentNumber|OfferingNumber|SourceType|SourceId|SourceInfo
MERGE|SelfPacedActivity|2018/02/04|SP-ACT-201802041719-HDL|1|Title:SP ACT 201802041719|8|N|OLC103580|
OFFERING-201802041712-HDL|FUSION_HCM_LEARNING|201802041719|HCM Learning Source Info for 201802041719
Examples of Associating Global Access Groups

You can create Global Access Groups to classify groups of students by a common characteristic, such as their major.
Then you can assign the Global Access Group group to one or more learning items within the catalog. Students can
view the learning items for their Global Access Groups. This topic shows how to associate a Global Access Group with a
learning item.
332
Assigning Global Access Groups to Learning Items

This example GlobalAccessGroupRelation.dat le associates a learning item in the catalog with a Global Access Group.
METADATA|GlobalAccessGroupRelation|EffectiveStartDate|RelationNumber|GlobalAccessGroupNumber|
LearningItemNumber|Priority
MERGE|GlobalAccessGroupRelation|2019/06/13|Rel 1433|OLC143231|OLC901136|2
Example of Loading a Learning Record Activity Aempt

A learning record activity aempt records a learner's aempt to complete an activity, such as a self-paced activity, in an
oering assignment. This topic shows how to load Learning Record Activity Aempt objects using HCM Data Loader.
Creating a Learning Record Activity Aempt

In this example, the learning record and activity are referenced by user keys.
METADATA|LearningRecordActivityAttempt|LearningRecordNumber|ActivityNumber|ActivityAttemptStatus|
ActivityAttemptNote
MERGE|LearningRecordActivityAttempt|OLC109470|ILT-ACT-201802041713-HDL|ORA_ASSN_TASK_COMPLETED|Note for ILT
Onsite activity
Examples of Loading Legacy Learning Items

A legacy learning item represents a completed course or oering for inclusion in a learner's learning history. Legacy
learning items have no supporting content, and you can't assign them to other learners. This topic provides examples
showing how to load Legacy Learning Item objects using HCM Data Loader.
Creating Legacy Learning Items

This example LegacyLearningItem.dat le creates a legacy learning item to appear in a learner's learning history. This
example identies the legacy learning item by its source key.
COMMENT: Data for Business Object LegacyLearningItem
METADATA|LegacyLearningItem|EffectiveStartDate|LearningItemNumber|Title|ShortDescription|OwnedByPersonNumber|
SourceType|SourceId|SourceInfo|SourceSystemOwner|SourceSystemId
MERGE|LegacyLearningItem|2017/07/26|LEGACY-201710161121-HDL|Title:Legacy LI 201710161121|
DescShort:LEGACY-201710161121|8153756|FUSION_HCM_LEARNING|201710161121|HCM Learn 201710161121 Source Info|
VISION|201710161121
These rules apply when you create Legacy Learning Item objects using HCM Data Loader:
• The person identied by the OwnedbyPersonNumber aribute must exist in the target environment.
333
• LearningItemNumber is a required, alphanumeric value that identies this record uniquely. It must not start
with the characters OLC, which are reserved for Oracle Learning Cloud catalog items.
• The eective start date must be on or before the start date of any eective-dated record, such as a learning
record, that references the legacy learning item record. By default, the eective end date is the end of time. You
can't change the eective start and end dates of an existing Legacy Learning Item object.
Loading Translated Names and Descriptions for Legacy Learning

Items
You can translate legacy learning item names and their descriptions. Supply translation data in the
LegacyLearningItemTranslation.dat le after the legacy learning items exist in the target environment. This example
LegacyLearningItemTranslation.dat le provides translations of the name and description of an existing Legacy
Learning Item object. It references the object by its source key.
COMMENT: Data for Business Object LegacyLearningItemTranslation
METADATA|LegacyLearningItemTranslation|EffectiveStartDate|Language|LearningItemNumber|Title|ShortDescription|
SourceSystemOwner|SourceSystemId
MERGE|LegacyLearningItemTranslation|2017/07/26|FR|LEGACY-201710161121-HDL|French Title:Legacy LI 201710161121|
French ShortDesc:LEGACY-201710161121|VISION|201710161121
Examples of Loading Oering Custom Pricing Objects

Oering Custom Pricing objects are custom pricing rules for a course oering. This topic shows how to load Oering
Custom Pricing objects using HCM Data Loader.
Creating Oering Custom Pricing Objects

This example OeringCustomPricing.dat le identies the Oering Custom Pricing object by its user key.
METADATA|OfferingCustomPricing|EffectiveStartDate|PricingRuleNumber|CurrencyCode|OfferingNumber
MERGE|OfferingCustomPricing|2018/02/04|PR-201802041723-HDL|USD|OFFERING-201802041712-HDL
Creating Oering Custom Pricing Components

This example OeringCustomPricing.dat le loads two Oering Custom Pricing Components, which are identied by
their user keys.
METADATA|OfferingCustomPricingComponent|EffectiveStartDate|PricingComponentNumber|PricingComponentType|Price|
IncludeInSelfServicePricing|PricingRuleId|PricingRuleNumber
MERGE|OfferingCustomPricingComponent|2018/02/04|PC-201802041724-HDL|ORA_LIST_PRICE|100|N|PR-201802041723-HDL
MERGE|OfferingCustomPricingComponent|2018/02/04|PC-201802041725-HDL|ORA_LIST_PRICE_ADJ|200|N|PR-201802041723-
HDL
Valid PricingComponentType values are dened in the ORA_WLF_PRICING_TYPE lookup type. The following values
are predened:
334
Value Meaning
ORA_LIST_PRICE List price

ORA_ LIST_ PRICE_ADJ List price adjustment

Example of Loading a Specialization

A specialization groups multiple courses together to help learners achieve goals that a single course can't deliver. It
contains one or more specialization sections, which group related courses, or activities, in the specialization. This topic
shows how to load Specialization objects using HCM Data Loader.
Creating Specializations
This example Specialization.dat le creates a Specialization object, two Specialization Section components, and two
Specialization Section Activity components. The Specialization object is identied using source keys.
COMMENT Specialization object
METADATA|Specialization|EffectiveStartDate|SpecializationNumber|Title|ShortDescription|SourceType|SourceId|
SourceInfo|OwnedByPersonNumber|SourceSystemOwner|SourceSystemId
MERGE|Specialization|2018/03/05|DSS-2018043009000-HDL|Title: DSS HDL Specialization 2018043009000|SD: DSS
HDL Specialization 2018043009000 Short Description|FUSION_HCM_LEARNING|2018043009000|HCM Learning Source
Information for 2018043009000|8153756|VISION|2018043009000
COMMENT Specialization Section components

METADATA|SpecializationSection|EffectiveStartDate|SpecializationSectionNumber|Title|SectionPosition|
NumberOfActivitiesToComplete|InitialAssignmentStatusOfActivities|SpecializationNumber
MERGE|SpecializationSection|2018/03/05|Sec-2018043009000-HDL|Title: DSS HDL Section# 1|1|0|
ORA_ASSN_REC_ACTIVE|DSS-2018043009000-HDL
MERGE|SpecializationSection|2018/03/05|Sec-2018043009001-HDL|Title: DSS HDL Section# 2|2|0|
ORA_ASSN_REC_ACTIVE|DSS-2018043009000-HDL
COMMENT Specialization Section Activity components

METADATA|SpecializationSectionActivity|EffectiveStartDate|ActivityNumber|ActivityPosition|
SpecializationSectionNumber|LearningItemNumber
MERGE|SpecializationSectionActivity|2018/03/05|SecAct-2018043009000-HDL|1|Sec-2018043009000-HDL|OLC900002
MERGE|SpecializationSectionActivity|2018/03/05|SecAct-2018043009001-HDL|1|Sec-2018043009001-HDL|
COURSE-2018040910351-HDL
These rules apply:
• By default, the NumberOfActivitiesToComplete aribute of the Specialization Section component is -1, which
means that all activities in the section must be completed.
• Specialization objects that you create using HCM Data Loader have default access values as dened in the
application on the Manage Default Access page.
Related Topics
• Specializations
335
336
Integrating with HCM Loading Absences Topics
22 Loading Absences Topics
Example of Loading Accrual Plan Enrollments

You can load absence data for plan enrollment details, such as new enrollments or updates to existing enrollments. Use
the Accrual Plan Enrollment business object to:
• Enroll all employees of an organization into an accrual plan in bulk, instead of individually.
• Update employee details when there is a change in their work schedule. You can terminate their enrollment for
the previous plan and enroll them into new plans according to the changed work schedule.
• Delete an employee's plan enrollment if there is no accrual record for the corresponding plan.
Preparing to Load Accrual Plan Enrollment Object

Before you load accrual plan enrollment, you must:
• Verify that there are no overlapping enrollment records for the same assignment and plan
• Ensure that the start date is within the employment dates for the employer
• Ensure that both the unit of measure and number of units are specied
• Verify that the plan type is Accrual. This loader does not support other plan types
Loading an Accrual Plan Enrollment

This example PersonAccrualPlanEnrollment.dat le uses user keys to enroll an employee into an accrual plan.
METADATA|PersonAccrualPlanEnrollment|PersonNumber|WorkTermAsgNum|PlanName|ManualEnrollment|RunAccruals|
EnrtEndDt|EnrtStDt
MERGE|PersonAccrualPlanEnrollment|955160008177403|ET955160008177403|JL_PLAN_UOM_HRS|N|Y|2018/01/01|2017/01/01
Example of Loading Absence Qualication Plan

Entitlement
Using HCM Data Loader, you can load absence entitlement for qualication plans using the Absence Qualication Plan
Entitlement business object:
Preparing to Load Absence Qualication Plan Entitlement

Before you load accrual balance details, you must:
• Ensure that the start date and end date are provided because the start and end dates determine entitlement
calculation.
• Ensure that the value is negative when loading used entitlements.
337
Loading an Absence Qualication Plan Entitlement

This example PersonEntitlementDetail.dat le uses source keys to load employee used entitlement details of 5 hours for
a sick leave qualication plan.
METADATA|PersonEntitlementDetail|SourceSystemOwner|SourceSystemId|PersonId(SourceSystemId)|PlanName|
WorkTermsId(SourceSystemId)|ProcdDate|StartDate|EndDate|PayFactor|Value
MERGE|PersonEntitlementDetail|VISION|ABS02220160411|3423322|SICK_LEAVE|3423322WT|2016/04/11|2016/04/11|
2016/12/31|100|-5
Guidelines for Loading Absence Entry

Using HCM Data Loader, you can load data for the following components of the Absence Entry business object:
Absence Entry
You can load absences for:
• A time-based schedule: A time-based work schedule has a xed work day paern. For
example, you dene an 8-hour schedule, 5 days a week. You can create a time-based
work schedule that starts at 8:00 a.m. and ends at 5:00 p.m. A worker assigned to a
time-based work schedule is considered to be available for a xed number of hours each
day.
• An elapsed schedule: In an elapsed work schedule, workers don't have a xed start or
end time. For example, some workers may start work at 9.00 a.m., and some at 11.00
a.m. A worker assigned to an elapsed work schedule is considered to be available for a
number of hours in a day. The StartDateDuration and EndDateDuration values must
be provided.
Person Childbirth or Placement You can load absence records associated with the birth or placement of a child or children in
Absence Record the worker's household. This record captures planned and actual absence dates, as well as
dates associated with the event, such as expected date of childbirth.

Advanced Absence Entry You can load advanced absence entries when there is a breakdown of absences into specic
dates. This is used when an absence is taken against dierent assignments or if the absence
is intermient. For example, a weekly recurring absence scheduled for a weekly visit to the
doctor.

Preparing to Load Absence Entry Objects

Before you load absence records:
• Ensure you provide the name of the employer to verify the employment is valid as of the start date of the
absence. The employee's start date determines validation of the absence entry for the legal employer.
• Ensure that the absence type is valid as of the start date of the absence and belongs to the same legislative
data group as the person the absence is for.
• Ensure that the absence reason is dened, if it's specied as a required aribute in the absence type.
338
Deleting Absence Entry Records

You can also delete the Absence Entry business object using HCM Data Loader. When you delete an Absence Entry
record, the child records are also deleted.
Examples of Loading Absence Entry

These example AbsenceEntry.dat les show how to load absence entries using HCM Data Loader for:
• A time based absence entry

• An elapsed absence entry
• A maternity absence entry
• An advanced absence entry
Loading Absence Entry

Example 1: Time Based Absence Entry
This example uses user keys to create an absence entry for two days sick leave.
METADATA|PersonAbsenceEntry|Employer|PersonNumber|AbsenceType|AbsenceStatus|ApprovalStatus|StartDate|
StartTime|EndDate|EndTime|Comments|AbsenceReason
MERGE|PersonAbsenceEntry|Vision Corporation|300100005197277|SICK_LEAVE|SUBMITTED|APPROVED|2018/09/24|8:30|
2018/09/25|17:00|SICK LEAVE|SICK_REASON
Example 2: Elapsed Absence Entry
This example uses user keys to create an absence entry for two days sick leave.
METADATA|PersonAbsenceEntry|PersonNumber|AbsenceType|AbsenceStatus|ApprovalStatus|StartDate|StartTime|EndDate|
EndTime|Comments|StartDateDuration|EndDateDuration|AbsenceReason
MERGE|PersonAbsenceEntry|40010|10026712115|BAT_ABS_TL_Sick|SUBMITTED|APPROVED|2018/01/22||2018/01/23||Sick
Comments|8|8
Loading Person Maternity Absence Entry

This example uses source keys to create an absence entry for maternity leave.
METADATA|PersonAbsenceEntry|SourceSystemOwner|SourceSystemId|Employer|PersonId(SourceSystemId)|AbsenceType|
AbsenceStatus|ApprovalStatus|StartDate|StartTime|EndDate|EndTime
MERGE|PersonAbsenceEntry|VISION|AbsMaternity_HDL022|Vision Corporation|HDL022|Maternity Type|SUBMITTED|
APPROVED|2018/01/26|08:00|2018/02/14|17:00
METADATA|PersonMaternityAbsenceEntry|SourceSystemOwner|SourceSystemId|PerAbsenceEntryId(SourceSystemId)|
PlannedStartDate|PlannedReturnDate|LeaveDuration|IntendToWork|ExpectedDateOfChildBirth|ExpectedEndDate|
ActualStartDate|ActualReturnDate|ActualDuration|ActualChildBirthDate|OpenEndedFlag
MERGE|PersonMaternityAbsenceEntry|VISION|AbsMaternityDet_HDL022|AbsMaternity_HDL022|2018/01/26|2018/02/14|||
2018/01/26|2018/02/14|2018/01/25|2018/02/14||2018/01/27|
339
Loading Person Absence Entry Detail

This example uses source keys to create an advanced absence entry.
METADATA|PersonAbsenceEntry|Employer|PersonNumber|AbsenceType|AbsenceStatus|ApprovalStatus|StartDate|
StartTime|EndDate|EndTime|Comments|SourceSystemId|SourceSystemOwner|AbsenceReason
MERGE|PersonAbsenceEntry|Vision Corporation|955160008192206|#SK_QUAL_HRS|SUBMITTED|APPROVED|2018/11/06|21:00|
2018/11/07|05:00|Adv night shift|1SCH_SEMP_001111121|VISION|
METADATA|PersonAbsenceEntryDetail|Employer|PersonNumber|AbsenceType|PerAbsEntryDtlId|
PerAbsenceEntryId(SourceSystemId)|AbsenceDate|StartTime|EndDate|EndTime|RowSeq|AbsenceStartDate|
AbsenceStartTime|SourceSystemId|SourceSystemOwner
MERGE|PersonAbsenceEntryDetail|Vision Corporation|955160008192206|#SK_QUAL_HRS||1SCH_SEMP_001111121|
2018/11/06|21:00|||1|2018/11/06|21:00|HDLERDTL05011121|VISION
340
Integrating with HCM Loading Benets Objects
23 Loading Benets Objects
Example of Loading Beneciary Enrollments

Use the Beneciary Enrollment business object to designate beneciaries of multiple employees into a benet oering.
You typically designate beneciaries for benet plans that have payouts in the event of a death or an accident. Similar
to participant enrollment, you can load beneciary data in bulk when you are migrating from a legacy system during a
merger or acquisition.
Considerations
You must consider the following points before you load beneciary enrollment.
• You can load the Beneciary Enrollment object using either the default benets relationship or the unrestricted
benets relationship. However, you cannot use both relationships simultaneously.
• You can create and update records using Beneciary Enrollment HCM Data Loader. You can't delete records.
Preparing to Load Beneciary Enrollment Object

Before you can load beneciary enrollment, you must:
• Verify that the data required for enrollment such as employee name, address, salary, and contact details are
available in the HR application. It might be dicult to verify errors in HR data after the upload.
• Ensure that you do not include certications when you are migrating data from a legacy system. This might
cause completed enrollments to be suspended again. Avoiding certications also improves performance and
reduces pending action items.
• Determine the number of unique employees and the total number of enrollments that you plan to load into the
application. You can obtain this information from the extracted source data.
• Ensure that the total payout percentage assigned to the beneciaries add up to 100%. Both primary and
contingent beneciaries must have 100% assigned to them.
• Create electable choices on the basis of eligibility rules. To verify whether your electable choices follow eligibility
rules, use random checks based on eligibility criteria.
• Create benets relationships for all the employees whose data you want to load.
• Ensure that the benet relationships are properly aligned with the hire and assignment dates. For instance, the
date on which the life event is processed must follow benet relationship date, and the benet relationship date
must be the same as or follow the hire date.
• Verify that the total number of potential life events is equal to the total number of employees whose data you
want to upload. In the Evaluation and Reporting work area, Processes tab, use the Assign Corrective Life Event
process to create the data related to potential life events.
• Run the participation evaluation process without applying the defaults and ensure that the number of started
events match with the number of employees you determined in the previous task. You must x any errors you
encounter at this stage.
• Ensure that values are not added to the CloseLifeEvent aributes in the .dat le. You must rst verify the
enrollment data and then use the Close Life Event process to close a life event.
341
Generating the .dat File

This example BeneciaryEnrollment.dat le designates a beneciary into a benets program.
METADATA|BeneficiaryEnrollment|PersonNumber|BenefitRelationship|EffectiveDate|LifeEvent|LifeEventOccuredDate
MERGE|BeneficiaryEnrollment|300100010469441|Default|2015/01/01|PAN_DESG_LE|2015/01/01
METADATA|DesignateBeneficiary|Plan|Program|Option|BeneficiaryPercentage|BeneficiaryPersonNumber|
BeneficiaryType|LineNumber|PersonNumber
MERGE|DesignateBeneficiary|BASIC_LIFE_PLAN|VISION_BENEFITS_PROGRAM|1xSALARY|100|300100010472847|Primary|1|
300100010469441
Example of Loading Person Beneciary Organizations

You can use the Person Beneciary Organization business object to load details of organizations or trusts in bulk. You
can use this object to upload new organizations and trusts or modify existing ones.
Considerations for Using the .dat File

Before you use the .dat le, consider these points:
• In the .dat le, BnfTypCd stands for beneciary type code. For trusts, use TTEE as the value for BnfTypCd. For
organizations, use ORG as the value for BnfTypCd.
• Each row in the .dat le can contain either a beneciary organization or a trust that you want to link with a
participant.
• You can link the same beneciary organization to more than one participant. To do this, just create a new row
in the .dat le with the same details for another participant. Trusts are usually unique for each participant.
• Use PersonNumber to identify the participant.
Examples of Loading Trusts and Organizations

You can use the PersonBeneciaryOrganization.dat le to load details of trusts and organizations for participants. Let's
look at some sample .dat les for loading trusts and organizations.
This example PersonBeneciaryOrganization.dat le loads details of a trust for the participant:
METADATA|PersonBeneficiaryOrganization|StartDate|EndDate|BnfTypCd|TrusteeOrgName|TrusteeOrgRegCd|
TrusteeOrgDescription|TrusteeAddlDetails|TrusteeExecutorName|OrganizationName|PersonNumber
MERGE|PersonBeneficiaryOrganization|2018/05/05||TTEE|This is Duprey Trust|TOR111|TOD|TAD|TEN||10026712115
This example PersonBeneciaryOrganization.dat le loads details of an organization for the participant:
METADATA|PersonBeneficiaryOrganization|StartDate|EndDate|BnfTypCd|TrusteeOrgName|TrusteeOrgRegCd|
TrusteeOrgDescription|TrusteeAddlDetails|TrusteeExecutorName|OrganizationName|PersonNumber
MERGE|PersonBeneficiaryOrganization|2019/07/07||ORG||||||UnitedWay|10026712115
342
Example of Loading Dependent Enrollments

Use the Dependent Enrollment business object to designate dependents of multiple employees into a benet oering.
You typically perform this task when you are migrating from a legacy system during a merger or acquisition. You can
also use the data loader if you want to move dependents in bulk from one plan to another.
Considerations
You must consider the following points before you load dependent enrollment.
• You can load the Dependent Enrollment object using either the default benets relationship or the unrestricted
• You can create and update records using Dependent Enrollment HCM Data Loader. You can't delete records.
• Dependent Enrollment processing does not depend on Eective date, but on Life Event date.
Preparing to Load Dependent Enrollment Object

Before you can load dependent enrollment, you must:
343
Generate the .dat File

This example DependentEnrollment.dat le designates a dependent into a benets program.
METADATA|DependentEnrollment|PersonNumber|BenefitRelationship|EffectiveDate|LifeEvent|LifeEventOccuredDate
MERGE|DependentEnrollment|10026712115|Default|2016/10/28|NewHire|2016/10/28
METADATA|DesignateDependent|Plan|Program|Option|DependentPersonNumber|LineNumber|PersonNumber
MERGE|DesignateDependent|GlobalPlan|Green Company Full Benefits|Employee plus Family|100010026713030|1|
10026712115
Example of Loading Participant Enrollments

Use the Participant Enrollment business object to enroll participants into a benet oering in bulk.
Considerations
You must consider the following points before you load participant enrollment.
• You can load the Participant Enrollment object using either the default benets relationship or the unrestricted
• You can create records using Participant Enrollment HCM Data Loader. You can't update or delete records.
• In order to update a record, de-enroll the participant rst and then re-enroll the participant with the new
value. Refer to the example ParticipantEnrollment.dat les provided in this topic to de-enroll and re-enroll a
participant.
Preparing to Load Participant Enrollment Object

Before you can load participant enrollment, you must:
344

This example ParticipantEnrollment.dat le enrolls a participant into a benets program.
METADATA|ParticipantEnrollment|PersonNumber|ParticipantLastName|ParticipantFirstName|BenefitRelationship|
LifeEvent|LifeEventOccuredDate|EffectiveDate
MERGE|ParticipantEnrollment|10026712115|Duprey|Luis|Default|NewHire|2016/10/28|2016/11/05
METADATA|CompensationObject|Program|OriginalEnrollmentDate|PersonNumber|LineNumber
MERGE|CompensationObject|Green Company Full Benefits|2014/10/28|10026712115|1
Note: It is not necessary to supply the ParticipantLastName and ParticipantFirstName aributes. The
application does not perform any validation to cross check the name against the person number. These
aributes are for provided only for your information.
De-enrolling from an Existing Option in the Plan and Enrolling in a Waive

Option
You can de-enroll employees from a plan and enroll them into the waive option of same plan type. For instance,
consider an employee who is enrolled in the Healthy HMO plan with the Employee Plus Family option. You can de-enroll
the employee from the Employee Plus Family option and enroll the employee in the Waive Coverage option using the
following example ParticipantEnrollment.dat le.
METADATA|ParticipantEnrollment|PersonNumber|ParticipantLastName|ParticipantFirstName|BenefitRelationship|
LifeEvent|LifeEventOccuredDate|EffectiveDate
MERGE|ParticipantEnrollment|10026712115|Duprey|Luis|Default|Gain Dependent|2016/10/28|2016/10/28
METADATA|CompensationObject|Plan|Program|Option|OriginalEnrollmentDate|PersonNumber|DenrollPlan|DenrollOption|
LineNumber
MERGE|CompensationObject|Healthy HMO|Healthy Benefits|Waive Coverage|2016/10/28|10026712115|Healthy HMO|
Employee plus Family|1
Example of Loading Person Benet Group

You create a benet group to determine a specic set of people who are eligible for a benet object. Use the Person
Benet Group business object to load multiple benets groups simultaneously using HCM Data Loader.
Preparing to Load Person Benet Group Object

Verify that the data required for loading a business group, such as the person name, is available in the HR application. It
might be dicult to verify errors in HR data after the upload.

This example PersonBenetGroup.dat le loads multiple benet groups.
METADATA|PersonBenefitGroup|SourceSystemOwner|SourceSystemId|BenefitGroupName|EffectiveStartDate|PersonId
MERGE|PersonBenefitGroup|VISION|GROUP955160008173169|VISION_BENEFIT_GROUP|2019/01/01|955160008173160
MERGE|PersonBenefitGroup|VISION|GROUP100000012556816|VISION_BENEFIT_GROUP|2019/01/01|100000012556816
345
Example of Loading Person Benet Balance

Use the Person Benet Balance business object to load multiple benets balances using HCM Data Loader. You typically
use benets balances to store benet amounts from an external system, or as a workaround for a calculation to bridge
disparate systems.
Preparing to Load Person Benet Balance Object

Verify that the data required for uploading benet balances such as benet balance, legal entity, and assignment details
are available in the HR application. It might be dicult to verify errors in HR data after the upload.
Generate the .DAT File

This example PersonBenetBalance.dat le loads a person benet balance.
METADATA|PersonBenefitBalance|SourceSystemOwner|SourceSystemId|PersonId|BenefitBalanceName|
BenefitRelationName|EffectiveStartDate|UOM|Val|
MERGE|PersonBenefitBalance|VISION|BALANACE955160008173169|955160008173169|SICK_LEAVE_BALANCE|DFLT|2009/01/01|
USD|2200
Example of Loading Person Habits

Use the Person Habits business object to load details of habits and disability statuses of employees in bulk using HCM
Data Loader.
Preparing to Load Person Habits

Before you can load person habits, you must:
• Verify that the objects referenced by Person Habits exists in the target environment. If they do not exist, the
load will fail.
• Create electable choices on the basis of eligibility rules. Lack of eligibility causes a data roll back for
corresponding employees. To verify whether your electable choices follow eligibility rules, use random checks
based on eligibility criteria.

This example PersonHabits.dat le loads the person habits for an employee who is a full time student, smokes and is
registered as disabled.
METADATA|PersonHabits|SourceSystemOwner|SourceSystemId|PersonNumber|EffectiveStartDate|LegalEmployer|
DisabilityStatus|RegisteredDisabledFlag|StudentStatus|TobaccoTypeUsage
MERGE|PersonHabits|VISION|HABIT955160008173169|955160008173169|2015/01/01|Vision_Corporation|A|Y|FULL_TIME|Y
346
Integrating with HCM Importing and Loading Data Using HCM Data Loader
24 Importing and Loading Data Using HCM

Data Loader
How Data Is Imported and Loaded

HCM Data Loader imports data initially to stage tables, where some validation occurs. HCM Data Loader then loads
valid logical objects from the stage tables to the application tables. You can perform the import and load steps either
separately or as one step. This topic summarizes the processing that occurs in each step. It also describes how you
specify import and load options.
Importing Records to the Stage Tables

In the import stage, HCM Data Loader:
• Extracts the business-object data from your .zip le on the Oracle WebCenter Content server and decrypts it, if
the le is encrypted.
• Validates the business-object le name and METADATA denitions and raises any errors.
• Imports records from the data les into the HCM Data Loader stage tables.
• Validates the data against aribute data types and raises any errors.
• Groups the data by local key values to form logical records of related date-eective le lines. For example, all
date-eective le lines supplied for a Job object are grouped into a logical occurrence of a job, such as the
Accountant job.
• Forms logical objects by resolving references to parent components. For example, the logical record for a valid
grade is associated with its parent Job object.
• Records the status of all imported objects. View the status when you click the Total Objects count from the
Import and Load status page.
Loading Objects to the Application Tables

HCM Data Loader doesn't load valid logical objects directly into the application tables. Instead, it passes valid object
data to business-object-specic services. For example, to load Worker objects, HCM Data Loader passes them to the
worker service. These services perform the validation that's specic to the business object, raise any errors, and load
valid objects to the application tables.
Seing the File Action Parameter

When you import a le on the Import and Load data page, you can set the File Action parameter on the Schedule
Request page. The value that you specify here overrides the enterprise default seing. This table describes how the File
Action parameter controls import and load.
347
File Action Value Description
Import and load HCM Data Loader imports the contents of the .zip le to the stage tables and calls object
services to load valid logical objects to the application tables.

Import only
HCM Data Loader imports the contents of the .zip le to the stage tables but doesn't pass valid
logical objects to the relevant object service. Instead, you perform that step separately on the
Import and Load data page by selecting the Load action for each business object.
You may want to select Import only when you start to load data so you can x import errors before aempting to load
objects. Once your data loading is routine, use Import and load to run them both with one job submission.
Tip: You can validate your data le before you load it. Use the Data File Validator tool for HCM Data Loader.
For more information, see Data File Validator Tool for HCM Data Loader (2022617.1) on My Oracle Support at
hps://support.oracle.com.
Automating Data Loading

When you automate data loading using the HCM Data Loader web service, you can set File Action to Import only or
Import and load. If you select Import only, then you load the imported objects manually on the Import and Load Data
page.
Reviewing Object History

For some object components, such as Assignment, you can review the object history to see who last
updated the object. When the object was last updated using HCM Data Loader, the Last Updated By value is
FUSION_APPS_HCM_ESS_LOADER_APPID. You don't see the user name of the user who uploaded the changes.
Import and Load Data

The le of data that you're preparing to import and load using HCM Data Loader may exist locally on your desktop. Or,
you may already have loaded it to the Oracle WebCenter Content server. This topic provides steps for importing and
loading your data interactively on the Import and Load Data page. It also describes how to load data to the application
tables if you imported it separately to the stage tables.
Import and Load a Local File

1. On the Tasks panel tab of the Data Exchange work area, select Import and Load Data to open the Import and
Load Data page.
2. Click Import File.
3. In the Import File dialog box, click Browse to search for and select your le. Alternatively, drag the le from
your local le browser to the Browse buon.
4. Click Submit to upload your le to the Oracle WebCenter Content server. The le is loaded automatically to the
HCM Data Loader import account hcm/dataloader/import and allocated a unique content ID.
348
5. In the Parameters section of the Import and Load Data page, review the parameter values and update them as
required. Most of these values are set for the enterprise on the Congure HCM Data Loader page and can be
left unchanged. The parameters are shown in this table.
Parameter Description
File Name The name of the le on the WebCenter Content server.

Content ID The WebCenter Content ID for the le on the WebCenter Content server.

File Action
The Import only option imports the business object data into the stage tables but doesn't
load it to the application tables. You can start the load process manually from the user
interface.
The Import and load option automatically loads to the application tables any business
object that loads successfully to the stage tables.
File Encryption The encryption type for the le.

Maximum Percentage of Import The percentage of le lines in error that can occur in a business object before the import
Errors process stops for the object.

Maximum Percentage of Load Errors The percentage of business-object instances in error that can occur for a business object
before the load process stops.

Delete Source File Indicates whether the source le is to be purged from the WebCenter Content server after
processing.

Maximum Concurrent Threads for The maximum number of concurrent process threads to use for importing your data set.
Import

Maximum Concurrent Threads for The maximum number of concurrent process threads to use for loading your data set.
Load

Load Group Size

The number of objects to process at a time on each thread. The record counts are updated
only when processing completes for each group.
Note: This parameter appears on the Schedule Request page only if the
Enable Load Group Size Calculation conguration parameter is set to No.
Otherwise, the load-group size is calculated automatically.

6. Click Submit. A conrmation message showing the process ID appears.

7. Note the process ID and click OK to close the Conrmation dialog box.
349
Import a File from the Oracle WebCenter Content Server

You can load a .zip le to the Oracle WebCenter Content server if you prefer. Select Navigator > Tools > File Import
and Export and upload the le to the hcm/dataloader/import account. To import and load a le that's already on the
WebCenter Content server:
1. On the Tasks panel tab in the Data Exchange work area, select Import and Load Data to open the Import and
Load Data page.
2. On the Import and Load Data page, click Import File.
In the Import File dialog box, select Oracle WebCenter Content Files. Any les in the hcm/dataloader/import
account that haven't been processed are listed. You can lter the list to reduce it. For example, you can enter
the le creation date.
3. Select your le in the Import File dialog box and click Submit.
4. In the Parameters section of the Import and Load Data page, review the parameters, edit them as necessary,
and click Submit.
Start or Resubmit a Load

You can start the load process directly for a business object. You may want to do this because you submied your data
set in Import only mode. Or, you may want to resubmit a failed load process.
1. In the Business Objects table on the Import and Load Data page, select the business object and click Load.
Note: The Load buon is enabled only for business objects with a Loaded status of Ready,
Error, or Stopped.
2. On the Schedule Request page, review the parameter values, edit them if necessary, and click Submit.
Upload Data Using HCM Data Loader

In this example, you learn how to import and load objects manually to Oracle HCM Cloud. Import and load are
performed separately in this example.
This table summarizes key decisions for this scenario.
Decisions to Consider In This Example
Which business object am I loading?

Job. The child components of the Job object aren't being loaded.
These components are:
• Job Evaluation
• Job Extra Information
• Job Legislative Extra Information
• Job Valid Grade
What's the template name? Job.dat

350
What's the name of the le that I am uploading? Sales_Jobs.zip

What's the value of the File Action parameter? Import only. You have decided to manage the load step
separately.
Summary of Tasks
Upload the jobs data by:
1. Generating the jobs template
2. Editing the template le
3. Importing jobs to the stage tables
4. Loading jobs to the application tables
Generate the Job Template

1. On the Tasks panel tab of the Data Exchange work area, select View Business Objects.
2. On the View Business Objects page, enter Job in the Business Object query-by-example eld and press Enter.
Select the row for the Job object in the Search Results section.
3. Click Refresh Object on the table toolbar.
4. In the Schedule Request dialog box, click Submit.
5. Click OK to close the conrmation message.
6. Click Refresh on the table toolbar to view the Download File icon in the File column for the job row.
You may have to refresh more than once before the icon appears.
Tip: If the icon already exists, then you can download the existing template. The Last
Refreshed column shows when the template was generated.
7. Click the Download File icon in the File column.
8. Save the Job.dat template locally.
Edit the Template File

1. Open the Job.dat template.
2. Edit the template le as follows:
◦ Remove METADATA lines for these unwanted child components: Job Evaluation, Job Extra Information,
Job Legislative Extra Information, and Job Valid Grade.
◦ Edit the job METADATA line to remove unwanted aributes.
◦ Make any required changes to the aribute order.
351
3. Enter jobs data in the congured template. For example:

METADATA|Job|SourceSystemOwner|SourceSystemId|EffectiveStartDate|SetCode|JobCode|Name|ActiveStatus|
FullPartTime|RegularTemporary|JobFamilyId(SourceSystemId)|JobFunctionCode|ManagerLevel
MERGE|Job|VISION|SALES_CONS|2000/01/01|COMMON|SALES_CONS|Sales Consultant|A|FULL_TIME|R|CONSULT||9
MERGE|Job|VISION|SALES_MGR|2000/01/01|COMMON|SALES_MGR|Sales Manager|A|FULL_TIME|R|MANAGEMENT|MANAG|6
MERGE|Job|VISION|SALES_DIR|2000/01/01|COMMON|SALES_DIR|Sales Director|A|FULL_TIME|R|MANAGEMENT|MANAG|1
MERGE|Job|VISION|MRKT_CONS|2000/01/01|COMMON|MRKT_CONS|Marketing Consultant|A|FULL_TIME|R|CONSULT||9
MERGE|Job|VISION|MRKT_MGR|2000/01/01|COMMON|MRKT_MGR|Marketing Manager|A|FULL_TIME|R|MANAGEMENT|MANAG|6
MERGE|Job|VISION|MRKT_DIR|2000/01/01|COMMON|MRKT_DIR|Marketing Director|A|FULL_TIME|R|MANAGEMENT|MANAG|1
4. Save and close the template le.

5. Compress the template le, name it Sales_Jobs.zip, and save it locally.
Import Data to the Stage Tables

1. On the Tasks panel tab in the Data Exchange work area, select Import and Load Data.
2. On the Import and Load Data page, select Import File.
3. In the Import File dialog box, click Browse.
4. Select the Sales_Jobs.zip le.
5. Click Submit.
6. On the Schedule Request page, select Import only in the File Action eld.
7. Click Submit.
9. On the Import and Load Data page, click Refresh in the Data Sets table.
10. Review the status and details of the Sales_Jobs.zip data set that you uploaded. When the Total Objects count is
greater than zero you can click the new count to review the objects found in your le and their status. Refresh
the page if the data set is still in progress. Click Object Details to review the object hierarchy and the values of
aributes supplied for the logical object.
Return to the Data Sets table on Load and Import Data page. When the Import Status column shows Success
and the Import Success (%) column displays 100, you're ready to load the data to the application tables.
Load Data to the Application Tables

1. In the Data Sets table on the Import and Load page, select the Sales_Jobs.zip data set.
2. In the Business Objects table on the Import and Load Data page, select the Job object row and click Load.
3. In the Schedule Request dialog box, click Submit.
5. Click Refresh on the Business Objects table toolbar to check the status of the load.
When the Load Status column shows Success and the Load Success (%) column displays 100, the job data has
loaded successfully to the application tables.
How You Review and Correct Errors

Errors that occur during the import and load stages of data loading are reported automatically on the Import and Load
Data page. This topic describes how to review and correct reported errors.
352
Reviewing Import Errors

The Failed Lines column in both the Data Sets and Business Objects tables shows the number of records that failed to
import. When the number in the Failed Lines column is greater than zero, clicking it opens the Failed Lines page. When
you open the Failed Lines page from the Data Sets table, it lists:
• The METADATA line for each component

• All messages and the le lines in error for the selected data set
You can:
• Filter the list to show the METADATA lines and the le lines in error for the components of a single business
object.
• Use Query by Example elds to show specic le lines or messages.
When you open the Failed Lines page from the Business Objects table, you see details for the selected object by default.
You can lter the list to show failed lines for dierent objects from the same data set.
Examples of physical row errors are:
• The instruction or discriminator isn't recognized.

• The number of values in a data line doesn't match the number in the METADATA line.
• You didn't supply a unique reference for the component.
• The parent of a child component wasn't found, either in the le or in Oracle HCM Cloud.
• A required aribute is missing.
To correct import errors, you correct the source data before importing and loading it again. You need to add the
corrected data le to a new .zip le. You can't process the existing le again.
Reviewing Load Errors

The Failed Objects column in both the Data Sets and Business Objects tables shows the number of objects that failed
to load. When the number in the Failed Objects column is greater than zero, clicking it opens the Failed Objects page.
When you open the Failed Objects page from the Data Sets table, it includes for each object in error:
• Its user keys and any source key

• The error message
• A link to the object details, which opens the Object Hierarchy page
You can:
• Filter the list to show error details for a specic object in the data set.
• Use Query by Example elds to show specic keys or messages.
When you open the Failed Objects page from the Business Objects table, you see details for the selected object by
default. You can lter the list to show failed lines for dierent objects from the same data set.
353
Reviewing Messages
To review the messages for an import or load failure, click the icon in the Messages column of the Data Sets or
Business Objects table. When you open the Messages page for a data set, you see for each message:
• The process where the message occurred, which can be Import or Load
• The message location
• The message itself, with the number of occurrences of the message
When you click the message link, you open the Message Details page. It provides details of the message with the
information from the Failed Lines or Failed Objects page, as appropriate.
Tip: Messages appear in the session language if the HCM Data Loader conguration parameter Enable UI
Message Translation is set to Yes in your environment.
Correcting Objects in Error

On the Object Hierarchy page, which you open from the Failed Object, Message Detail or Object Status page, you can
expand object folders to see error details. When you click the name of a component entry, the Aribute Details dialog
box opens. It shows the original and current values of each aribute. For components in error, you can edit an aribute
to correct it before loading the object again on the Import and Load Details page. You can see how many objects you
corrected in the Objects Corrected columns of the tables on the Import and Load Data page. When you click the
number in the Objects Corrected column, the Failed Objects page opens for the corrected object.
If you prefer to correct object errors in the source data, then you need to import and load the corrected data again. You
must add the corrected data le to a new .zip le. You can't process the existing le again.
Stop HCM Data Loader Processing

You can stop the processing of either a data set or an individual business object. This topic explains how to stop
processing.
Stop the Processing of a Data Set

Follow these steps:
1. In the Search Results section of the Import and Load Data page, select the data set that you want to stop.
2. Click Refresh to update the status and conrm that the data set is still processing.
3. Click Stop.
Tip: The Stop buon is active only if either the import or the load is still in progress.
4. In the Warning dialog box, click Yes to conrm the stop request.
The status of the import or load process that was stopped is updated to Stopped. A large data set may take a few
minutes to stop processing completely. For eciency in import and load processing, HCM Data Loader checks at
intervals for stop requests.
354
Stop the Processing of a Business Object

Follow these steps:
1. In the Details section of the Import and Load Data page, select the business object that you want to stop
processing.
2. Click Refresh to update the status and conrm that the business object is still processing.
3. Click Stop.
4. In the Warning dialog box, click Yes to conrm the stop request.
The status of the import or load process that was stopped is updated to Stopped.
Restart Stopped Processes

You can't restart a stopped import process for a business object. However, you can restart a stopped load process for
a business object. Select the stopped business object in the Details section of the Import and Load Data page and click
Load. The status of both the business object and the associated data-set load processes changes to In Progress.
Overview of Automating Data Loading

You can automate HCM Data Loader processes to load data to Oracle HCM Cloud and extract both status and error
information. This topic provides an introduction to the automation processes.
The processes that you can automate are:

• Delivery of .zip les to the Oracle WebCenter Content server
• Initiation of HCM Data Loader to process les on the WebCenter Content server
• Initiation of the HCM Data Loader Data Set Summary extract and retrieval of its output
Complete instructions are provided in Automating HCM Data Loader (1664133.1) on My Oracle Support at hps://
support.oracle.com.
Delivering Files to Oracle WebCenter Content Automatically

To automate the delivery of .zip les to the WebCenter Content server, you can use:
• The WebCenter Content Document Transfer Utility, a feature-rich Java library that provides content import and
export capabilities
• WebCenter Content Generic SOAP Web Service, which exposes a SOAP web service interface (GenericSoapPort)
that supports various operations, including le upload
Initiating HCM Data Loader Automatically

You can initiate HCM Data Loader automatically to process multiple les on the Oracle WebCenter Content server using
the HCM Data Loader Integration Service. This web service provides the two methods shown in this table.
355
Method Description
importAndLoadData Initiates the processing of a data le

getDataSetStatus Returns the current status of a data le

Several ways exist of running the web service. For example, you can use generated proxy classes.
Initiating the HCM Data Loader Data Set Summary Extract

Automatically
HCM Extracts is a tool for reporting and outbound integrations. When you use HCM Extracts as part of an integrated
process, you can initiate it automatically from an automated ow. The Payroll Flow Engine is the generic processing
engine that you use for this purpose.
When you save a copy of the predened HCM Data Loader Data Set Summary extract, you also create a payroll ow of
type Extract. You can initiate this payroll ow using the FlowActionsService, which you use to automate and monitor the
extract. You use the payrollProcessingActionService.fetchExtractOutput method to download the extract output. When
the extract is associated with a BI template, the payroll ow ensures that the BI report is generated and wrien to the BI
server.
Related Topics
• Automating HCM Data Loader (1664133.1)
• HCM Data Loader Extracts
How to Review the Objects Processed in a Data Set

The Total Objects column in both the Data Sets and Business Objects tables shows the number of objects processed.
When the number is greater than zero, clicking it opens the Object Status page.
When you open the page it includes for each object:
• Its user key and source key.

• The error message for objects in error.
• A link to the object details, which opens the Object Hierarchy page.
You can lter the list to show:
• The objects for a specic object in the data set.

• The objects with a specic Load status.
356
FAQs for Importing and Loading Data Using HCM Data

Loader
What's an HCM Data Loader data set?
A set of data supplied together to be loaded into Oracle HCM Cloud. The source of a data set is either a compressed
data le containing delimited business-object-specic data les or an HCM Spreadsheet Data Loader spreadsheet.
What happens in the import stage ?

The application imports individual le lines from your compressed data le to the HCM Data Loader stage tables.
Related le lines are grouped to form logical business objects, and some preliminary validation occurs. Errors reported
at this stage are specic to the object itself. The object's dependencies on other objects aren't assessed.
What happens in the load stage?

The application validates foreign-object references and applies business-object-specic validation rules. If the object
passes all validation, then it's loaded to the Oracle HCM Cloud application tables. If any component of the object fails
validation, then the whole logical object fails to load. You can monitor object status on the Import and Load Data page.
Errors reported at this stage may relate to either the object itself or its dependencies on other objects.
How can I review the status of the objects in my le?

When you import data into the stage tables, HCM Data Loader records the status of all imported objects. On the Import
and Load status page, the Total Objects count increases as the import process progresses. Click the count to open
the Object Status page and review your objects. If the process hasn't nished, refresh the Object Status page until all
imported objects appear.
How can I view the data in error for a data set or business object?
If your data le import encounters errors, then the Failed Lines and Failed Objects columns on the Import and Load
Data will become active links. Click the number to open the Failed Lines or Failed Objects page, as appropriate, to see
error details. From the Failed Objects page, you can link to the Object Hierarchy page and correct individual aribute
values.
Or, you can click the Messages icon on the Import and Load Data page to open the Messages page. From the Messages
page, you can navigate to error details. For failed objects, you can open the Object Hierarchy page.
357
How do I x HCM Data Loader errors?

You need to x import errors in the source data and upload the corrected data again in a new .zip le. You can't process
the existing .zip le again.
You can also x load errors in the source data and upload the corrected data again. Or, you can correct aribute values
in the Aribute Details dialog box on the Object Hierarchy page for a failed object. In this case, you can resubmit the
load process for corrected objects on the Import and Load Data page.
358
Integrating with HCM Data Loading Using Spreadsheets
25 Data Loading Using Spreadsheets
Spreadsheet Data Loaders

In this topic, you learn about using the spreadsheet data loader provided with Oracle HCM Cloud. To use this tool, you
must install the Oracle ADF Desktop Integration Add-in for Excel.

You can use HCM Spreadsheet Data Loader to load most objects that HCM Data Loader supports. The exceptions are
components, such as Document Record Aachment and Person Image, that load content like PDF les and images into
the Cloud. Here's how the spreadsheet gets processed:
• Rows in the spreadsheet are initially saved to the HCM Spreadsheet Data Loader stage tables
• Stage table data is reformaed to the hierarchical shape supported by HCM Data Loader
• Reformaed stage table data gets saved to the HCM Data Loader staging table
You can nd HCM Spreadsheet Data Loader in the Data Exchange work area.
Single-Object Spreadsheet Loaders

Oracle Fusion HCM provides many spreadsheet loaders for specic object types.
In most cases, you:

• Create the spreadsheet on the page where you manage the object.
• Load the objects directly to the application tables.
• Correct any errors in the spreadsheet.
In many cases, you can both create and update the object in a spreadsheet.
Single-object spreadsheets are most useful for users such as human resource specialists and benets specialists,
who are creating objects of a specic type in bulk. You're less likely to use these types of spreadsheet loaders for
integrations.
This table shows some key objects that you can create in bulk using this type of spreadsheet. It also identies the page
or tab where you generate the spreadsheet.
Note: Some of these are HCM Spreadsheet Data Loader spreadsheets embedded in the relevant page or tab.
Business Object Page or Tab
Benet Enrollment Evaluation and Reporting work area, Enrollment Uploads tab

Benet Plan Manage Benet Plans page

359
Business Object Page or Tab
Benet Program Manage Benet Programs page

Competency Manage Content Items page

Department Manage Departments page

Job Manage Jobs page

Location Manage Locations page

Performance Rating Manage Content Items page

Postal Code Range and Service Area Manage Postal Code Ranges and Service Areas page

Regulation Manage Regulations page

Reporting Group Manage Reporting Groups page

Stock Grant Manage Stock Grants page

Variable Rate Prole Manage Benet Rates page

Work Paern Manage Work Schedules page

Work Schedule Assignment Manage Work Schedule Assignment Administration page

Work Schedule Manage Work Schedules page

Worker Goal Administer Goals page

For some objects, such as Benet Rate and Assignment, you can perform a mass update in a spreadsheet. To update
these objects, you download existing objects to a generated spreadsheet, edit the objects, and upload the changes.
Set Up Desktop Integration for Excel

You can create or edit records that you can upload to the application using integrated Excel workbooks. To use these
workbooks, you must install an Excel add-in.
360
Note: Every release of Oracle Fusion Applications is likely to have a new version of the Oracle ADF Desktop
Integration add-in. When prompted, install the latest version of the add-in. For more information, see Add-In
Upgrade Policy for ADF Desktop Integration (2242879.1) on My Oracle Support at hps://support.oracle.com.
Before You Start

• Make sure you have an Excel and Windows version that's listed in Supported Platforms for ADF Desktop
Integration (2242428.1) on My Oracle Support at hps://support.oracle.com.
• Optionally install the following from the Microsoft website.
◦ Microsoft .NET Framework 4.5.2

◦ Microsoft Visual Studio 2010 Tools for Oce Runtime (VSTO Runtime)
The add-in installer does check if you have these already, and would download and install them if needed. But,
you can manually install them rst, especially if you run into issues installing them as part of installing the Excel
add-in.
Install the Desktop Add-In

To install the Oracle ADF 11g Desktop Integration Add-In for Excel:
1. Make sure you are signed in to your computer with your account. For example, you can't have someone else
sign in as an administrator and make the installation available for everyone using your computer.
2. Click Navigator > Tools > Download Desktop Integration.
3. Run the adfdi-excel-addin-installer.exe installer as you would run any program that you install on your
computer.
Related Topics
• Guidelines for Using Desktop Integrated Excel Workbooks
Troubleshoot Desktop Integration for Excel

The application is integrated with Microsoft Excel so that, where available, you can work with records in a desktop
integrated workbook. You might run into issues with the integration, for example, if you can't open the workbook that
you downloaded or the workbook doesn't look right. You can use the Client Health Check Tool. For more information
see Information Center: Troubleshooting Oracle ADF Desktop Integration (2012600.2) on My Oracle Support at hps://
support.oracle.com.
Use the Client Health Check Tool

Use the health check tool to nd out what integration issues you might have and how to resolve them. Ask your help
desk if you are unable to nd or use the tool.
1. Download the latest version of the health check tool from How to use ADF Desktop Integration Client Health
Check Tool (2010222.1) on My Oracle Support at hps://support.oracle.com.
2. Run ClientHealthCheck.exe as you would other programs on your computer, and review the result for each
checked item.
3. Select any item that has a problem, and read the help text.
361
4. Fix some of the problems by clicking the Fix Problems buon. Otherwise, follow the instructions in the help
text.
5. If you need more assistance, click the Save Report As buon to prepare information for your help desk.
6. Review the report and remove any sensitive information.
7. Contact your help desk and provide your report.
362
Integrating with HCM Introduction to HCM Spreadsheet Data Loader
26 Introduction to HCM Spreadsheet Data

Loader
Guidelines for Using HCM Spreadsheet Data Loader

You can load data to the HCM Data Loader stage tables from either a data (.dat) le or a spreadsheet. Your approach
depends largely on how often you load data and the complexity of the data that you're loading. This topic describes
some key features of data loading from spreadsheets. This information helps you to identify the best approach for your
business case.
Spreadsheet Templates
You must generate the spreadsheet from a spreadsheet template. Some spreadsheet templates are predened. To
create templates, you can either copy a predened template and edit it or create a template from scratch.
When to Use Spreadsheets

Spreadsheets oer many advantages. For example:
• Spreadsheets are easy to use.
• You can create spreadsheet templates and generate spreadsheets tailored to your business case. For example,
you can omit aributes, change aribute order, change aribute labels, and add help text. You can also dene
dierent templates for creating and maintaining the same business objects.
• You can enable business users to load data for selected spreadsheet templates.
• You can save data periodically from a spreadsheet to the stage tables. Therefore, you can load large volumes of
records without being prevented by limits on spreadsheet size.
• Errors are reported in the spreadsheet, and you can correct them there.
• You can mix your use of spreadsheets with use of .dat les. For example, you can load data from a spreadsheet
but maintain it using .dat les.
• You can use spreadsheets to delete data.
• In specic cases, spreadsheets are the simpler option. For example, to load an element entry for an element
with 5 lines from a .dat le, you supply:
◦ 1 record for the element entry
◦ 1 record for each name and value
In a spreadsheet, you supply just 1 spreadsheet line where the values are individual columns on the same line.
Spreadsheet Restrictions
When loading data from a spreadsheet:
• You can't upload data to aributes whose data type is binary large object or character large object, like images
and le aachments.
363
• HCM Spreadsheet Data Loader doesn't recognize source keys. Therefore, objects that you load from a
spreadsheet have default source keys. To maintain such objects using .dat les, you supply user keys.
• You can't create objects or object components, such as Prole Item, that don't supply user keys. However, you
can update such objects if you dene a list of values on the local surrogate ID aribute to identify the record to
update.
• If an object has more than one user key, then one is selected automatically when you include a user-key
aribute in the spreadsheet template. You can't select a dierent user key from the one that's selected
automatically. The default user key may include aributes that you don't want to include in your spreadsheet
template. If those aributes appear in all other user keys, then you must include them and specify a valid value.
Otherwise, you can set them to #NULL.
Tip: View the object on the View Business Objects page. When an object has multiple user keys,
a link replaces the list of aributes in the User Keys column. The link opens a dialog box. The rst
user key in the dialog box is the one that's used automatically in spreadsheet templates.
• You can't update the values of the user-key aributes if they identify the record to update. Therefore, you're
recommended to dene separate spreadsheets for creating and updating objects. In the spreadsheet for
updating an object, you can identify the record to update in one of these ways:
◦ Include the local surrogate ID aribute, which has a predened LOV.

◦ Include the primary user key aribute, but congure an LOV for the aribute value. With this approach,
the user sees a recognizable value in the spreadsheet.
Note: Whether you load data from a spreadsheet or a .dat le, no approval processes exist for loaded objects.
Setup Requirements
All users must set up desktop integration for Microsoft Excel to use HCM Spreadsheet Data Loader.
Related Topics
• Set Up Desktop Integration for Excel
• Congure Lists of Values for Aribute Validation
How Data Is Uploaded Using HCM Spreadsheet Data

Loader
When you click Upload in a spreadsheet, your data is uploaded to Oracle HCM Cloud. Behind the scenes, upload is a
two-stage process. In the rst stage, HCM Spreadsheet Data Loader imports the data to the HCM Data Loader stage
tables. In the second stage, HCM Data Loader loads valid business objects to the application tables.
364
This gure summarizes the process of uploading data using HCM Spreadsheet Data Loader.
Run Spreadsheet
Data Loader
Generate Spreadsheet
Import Errors
Business Object
Spreadsheet HCM Data Loader
Stage Tables
Import
Load
Load Errors
Oracle HCM Cloud

Application Tables
How Spreadsheet Data Is Loaded

The details of this process are:
1. You use the Run Spreadsheet Data Loader task in the Data Exchange work area to generate a spreadsheet
for a business object from a spreadsheet template directly. You can also access spreadsheet templates directly
from the business objects pages, such as Job, Location, Position.
2. You click Create Data Set in the spreadsheet to create a data set for the data that you want to load.
3. You enter data in the spreadsheet and click Upload. This action imports the spreadsheet data set to the HCM
Data Loader stage tables.
4. Some validation occurs in the stage tables. Any import errors are reported in the Progress and Message
columns of the Spreadsheet Line Status section of the spreadsheet when you click Refresh.
Errors at this stage are rare, as the spreadsheet format enforces business-object structure and rules.
5. As each object loads successfully to the stage tables, HCM Data Loader calls the relevant object service to load
the object to the application tables.
6. The object service validates the object. Any errors are reported in the Progress and Message columns of the
Spreadsheet Line Status section of the spreadsheet when you click Refresh.
365
7. You correct any import or load errors in the spreadsheet and click Upload again. This action imports the
corrected data to the stage tables again.
Tip: You can review the status of an HCM Spreadsheet Data Loader data set on the HCM Data Loader Import
and Load Data page. Search for data sets by le type to list those loaded from spreadsheets.
The Instruction worksheet of the spreadsheet may contain instructions on how to use the spreadsheet, while the
Messages worksheet holds a summary of all import and load messages generated for this data set.
Related Topics
• Upload Data Using HCM Spreadsheet Data Loader
How You Test the HCM Spreadsheet Data Loader

Process Flow and Connections
Before you aempt to load your own data, you may want to test HCM Spreadsheet Data Loader end-to-end processing
without creating unwanted data. This topic describes how to test HCM Spreadsheet Data Loader end-to-end processing.
Testing End-to-End Processing

To test end-to-end processing, you use:
• A process, Test HCM Data Loader Process Flow and Connections
• An object, Example Object
When you run the Test HCM Data Loader Process Flow and Connections process, you set the Action parameter to
Test HCM Spreadsheet Data Loader. The process:
1. Generates a .csv le of data for the example object
2. Initiates HCM Spreadsheet Data Loader to import and load the le
3. Creates a log le, which you can access on the Scheduled Processes page
Approximately 200 hundred records of example data are imported and loaded to the object's own tables. No data is
saved to the application tables.
The Example Object

The example object:
• Has child and grandchild components
• Supports create and update actions
• Has aributes of most data types
A predened spreadsheet template is provided for the example object. The generated .csv le is based on this template.
Deleting the Test Data

You're recommended to run the Test HCM Data Loader Process Flow and Connections process periodically to
delete the test data and associated data sets. When you run the process, you set the Action parameter to Delete
test data. The process deletes all example data, regardless of whether the data was created by HCM Data Loader
366
or HCM Spreadsheet Data Loader. It generates a le of HCM Data Loader DELETE instructions, adds the le to the
DeleteExampleObject||<date and time>||.zip le, and uploads it.
Spreadsheet Business Object Access

Users who have the predened Human Capital Management Integration Specialist job role can create and maintain
spreadsheet templates for any business object. They can also generate spreadsheets from templates and perform all
data-set operations, such as create and upload. By default, no other role has this access. This topic describes how to
enable other roles to:
• Create and import spreadsheet templates.
• Maintain spreadsheet templates.
• Generate spreadsheets and create, save, and upload data sets from those spreadsheets.
• View all data sets in spreadsheets generated from a specic template.
It also introduces some security setup that you must perform to enable users to access relevant tasks in the Data
Exchange work area.
Creating and Importing Spreadsheet Templates

To enable users to create and import spreadsheet templates, you perform the Manage Spreadsheet Business Object
Access task. Using this task, you can:
• Select a role and assign one or more business objects to it.
For example, you can select a custom Compensation Administrator job role and assign all compensation
objects to the role. Users who have the job role can create and import spreadsheet templates for all
compensation objects.
• Select a single business object and assign one or more custom roles to it.
For example, you can select the Job object and assign custom Human Resource Specialist and Human Capital
Management Application Administrator job roles to it. Users who have either role can create and import
spreadsheet templates for the Job object.
In both cases, users can't create and import spreadsheet templates for other business objects, unless they have other
custom roles that provide that access.
Tip: When you assign business objects individually, you must assign the translation objects explicitly, if
required. They're not assigned by default with the base object.
Maintaining Spreadsheet Templates

While spreadsheet templates are in Draft status, the users who created them can maintain them. When a spreadsheet
template is in other statuses, then only the roles listed in the Template Maintenance section of the spreadsheet
template can maintain it.
367
Generating Spreadsheets and Performing Data Set Operations

Users who can create and import spreadsheet templates determine who can generate spreadsheets and perform data
set operations. On the Manage Role Access tab of the spreadsheet template, they identify the roles that can:
• Create, save, and upload data sets from spreadsheets generated from the template.
• View all data sets in spreadsheets generated from the spreadsheet template.
For example, a user with a custom Compensation Administrator job role may create a spreadsheet template named
US Compensation Grades for loading Grade objects. On the Manage Role Access tab of the template, that user selects
a custom Compensation Analyst role and selects the Create, Save, and Upload options. Therefore, any user with the
custom Compensation Analyst job role can:
• Generate spreadsheets for the Grade object from the US Compensation Grades spreadsheet template.
• Create, save, and upload data sets from the generated spreadsheets.
Note: The Manage Role Access tab of the spreadsheet template is enabled only if the Assign Roles to
Template eld is set to Enabled. This eld appears in the Template Security section of the Dene page of the
spreadsheet template.
Enabling Task Access

Users who have the predened Human Capital Management Integration Specialist job role can access the Data
Exchange work area and perform these tasks:
• Manage Spreadsheet Templates
• Run Spreadsheet Data Loader
Other users need access to the same tasks so that they can:
• Create, import, and maintain spreadsheet templates.
• Generate spreadsheets and perform permied data set operations.
To provide this access, you add relevant privileges to the custom roles that are authorized to use HCM Spreadsheet
Data Loader. You must have the IT Security Manager job role or privileges to perform this task.
Related Topics
• How You Associate a User Name with a Data Upload
Manage Spreadsheet Business Object Access

Perform the Manage Spreadsheet Business Object Access task to enable selected roles to create and import
spreadsheet templates for selected business objects. You can secure this access by either role or business object:
• To secure access by role, you select a single role and assign one or more business objects to it.
• To secure access by business object, you select a single business object and assign one or more roles to it.
This topic describes both methods. In the Setup and Maintenance work area, go to the following for your oering:
• Functional Area: HCM Data Loader
• Task: Manage Spreadsheet Business Object Access
368
Securing Access by Role

To secure access by role, follow these steps:
1. On the Manage Spreadsheet Business Object Access page, select the By Role option in the page title.
2. In the Job and Abstract Roles section of the page, enter the name of the role in the Role query-by-example eld
and press Enter. For example, enter Compensation Administrator Custom.
3. In the results, select the role.
The Assigned Business Objects section title is updated automatically to include the role name.
4. In the Assigned Business Objects section, select an entry in the Assign menu.
If you select Assign Individual Business Objects, then:
a. Search for and select the business objects in the Search and Select Business Objects dialog box. For
example, search by the Compensation product area and select specic objects.
b. Click Add to add the selected business objects to the role. An entry appears in the Assigned Business
Objects section for each selected business object.
5. If you select Assign All Business Objects in a Product Area, then:
a. Select the product area in the Select Product Area dialog box. For example, select Compensation.
b. Click Add. A single entry appears for all compensation objects in the Assigned Business Objects section.
6. If you select Assign All Business Objects, then a warning message appears. Click Add to close the warning and
continue. A single entry appears for all business objects in the Assigned Business Objects section.
7. Click Save.
Users who have the selected role can now create and import spreadsheet templates for the selected business objects.
Securing Access by Business Object

To secure access by business object, follow these steps:
1. On the Manage Spreadsheet Business Object Access page, select the By Business Object option in the page
title.
2. In the Business Object section of the page, enter the name of the business object in the Business Object query-
by-example eld and press Enter. For example, enter Job.
3. In the results, select the business object.
The Assigned Roles section title is updated automatically to include the object name.
4. In the Assigned Roles section, click the Add icon.
5. In the Search and Select Roles dialog box, search for and select one or more roles. For example, select Human
Resource Specialist Custom.
6. Click Add.
An entry appears in the Assigned Roles section for each of the selected roles.
7. Click Save.
Users who have the selected roles can now create and import spreadsheet templates for the selected business object.
369
How You Enable Access to HCM Spreadsheet Data

Loader Tasks
You can perform the following tasks in the Data Exchange work area using the predened job roles Human Resource
Specialist and Human Capital Management Integration Specialist:
• Manage Spreadsheet Templates
• Run Spreadsheet Data Loader
• Delete Spreadsheet Stage Table Data
This topic explains how to give other roles access to these tasks. You must have the IT Security Manager job role or
privileges.
Access to the Manage Spreadsheet Templates Task

On the Manage Spreadsheet Business Object Access page, you can authorize selected custom roles to create and
import spreadsheet templates for selected business objects. You must also enable those custom roles to perform the
Manage Spreadsheet Templates task in the Data Exchange work area. To enable this access, you edit the custom roles
to add the following aggregate privileges:
Aggregate Privilege Name Aggregate Privilege Code
Load Data Using HCM Spreadsheet ORA_ HRC_ LOAD_ DATA_ USING_HSDL
Data Loader

Manage HCM Spreadsheet Data ORA_ HRC_ MANAGE_ HSDL_ TEMPLATES

Loader Templates

In addition, if the Manage Data Exchange Work Area (HRC_MANAGE_DATA_EXCHANGE_PRIV) function security privilege isn't
already granted to the role, then you must grant it.
Access to the Run Spreadsheet Data Loader Task

On the Manage Role Access tab of a spreadsheet template, you can authorize selected custom roles to generate
spreadsheets and perform data-set actions. You must also enable those custom roles to perform the Run Spreadsheet
Data Loader task in the Data Exchange work area. To enable this access, you edit the custom roles to add the following
aggregate privileges:
Access HCM Spreadsheet Data ORA_ HRC_ ACCESS_ HSDL_ TEMPLATES

Loader Templates

370
Load Data Using HCM Spreadsheet ORA_ HRC_ LOAD_ DATA_ USING_HSDL
Data Loader

In addition:
• Roles that are authorized to maintain a spreadsheet template must have the Manage HCM Spreadsheet Data
Loader Templates (ORA_HRC_MANAGE_HSDL_TEMPLATES) aggregate privilege. You authorize a role to maintain a
spreadsheet template on the Manage Role Access tab of the template.
• If the Manage Data Exchange Work Area (HRC_MANAGE_DATA_EXCHANGE_PRIV) function security privilege isn't
Access to the Delete Spreadsheet Stage Table Data Task

To enable custom roles to perform the Delete Spreadsheet Stage Table Data task in the Data Exchange work area, add
the following function security privilege:
Function Security Privilege Name Function Security Privilege Code
Delete HCM Spreadsheet Data Loader HRC_ DELETE_ HSDL_ STAGE_ DATA_PRIV
Stage Data

In addition, if the Manage Data Exchange Work Area (HRC_MANAGE_DATA_EXCHANGE_PRIV) function security privilege isn't
Related Topics
• Edit Job and Abstract Roles
FAQs for HCM Spreadsheet Data Loader

Why can't I access HCM Spreadsheet Data Loader?
You may not have the correct permissions. You must have the Human Capital Management Integration Specialist job
role or privileges.
In addition, the HCM Data Loader Scope conguration parameter must be set to Full.
Can I delete data using a spreadsheet?

Yes. In the spreadsheet template, you set the Supported Action value to Delete only. If the action isn't available, then
the selected object doesn't support deletion of any of its components. On the Design page of a template for deleting
objects, only those components that can be deleted appear.
371
372
Integrating with HCM HCM Spreadsheet Data Loader Templates
27 HCM Spreadsheet Data Loader Templates
HCM Spreadsheet Data Loader Templates

HCM Spreadsheet Data Loader loads HCM business objects from spreadsheets, which you generate from spreadsheet
templates. A spreadsheet template for a business object or business object component contains selected aributes
in a specied order. Every spreadsheet generated from the template has the same structure and organization as the
template. This topic describes spreadsheet templates.
Spreadsheet Template Features

You can congure many components of the spreadsheet template. Therefore, you can create spreadsheet templates to
suit business requirements. For example, you can:
• Select aributes to include.
• Specify aribute order and column headings.
• Enable and disable aributes for data entry.
• Hide aributes that are included.
• Provide default values.
• Make optional values required.
• Create instruction text for the spreadsheet.
• Congure Lists of Values to provide aribute validation.
Managing Spreadsheet Templates

To create a spreadsheet template, you can:
• Copy an existing spreadsheet template and edit the copy.
• Create a spreadsheet template from scratch.
• Import a spreadsheet template that was exported from a dierent environment or from Oracle Cloud Customer
Connect.
Predened Spreadsheet Templates

Predened spreadsheet templates may exist for commonly loaded objects. These templates contain columns for all
supported components and aributes. Search for predened spreadsheet templates, which have codes beginning
ORA_, on the Manage Spreadsheet Templates page.
Tip: Copy the predened templates and edit the copies to suit business requirements.
Spreadsheet Template Status

The status of a spreadsheet template determines whether you can edit it, delete it, or generate spreadsheets from it.
This table summarizes the template status values.
373
Spreadsheet Template Edit Delete Generate Spreadsheets

Status
Draft Yes Yes No

Active Yes No Yes

See note.

Inactive Yes No No

Note: You can disable aributes in an active spreadsheet template but you can't remove them.
To make an active spreadsheet template unavailable to users, you change its status to Inactive. You can't change it
back to Draft.
Access to Templates and Generated Spreadsheets

Users who have the predened Human Capital Management Integration Specialist job role can create and maintain
spreadsheet templates for any business object. They also perform the Manage Spreadsheet Business Object Access
task to enable other roles to create and import spreadsheet templates for selected objects.
On the Manage Role Access tab of the template, users who can create and import spreadsheet templates identify
custom roles that can:
• Create, save, and upload data sets from spreadsheets generated from the template.
• View all data sets in spreadsheets generated from the template.
• Maintain the template.
Note: The Manage Role Access tab is enabled in spreadsheet templates for unsecured objects and objects
where the application data security is available in HSDL. You can't manage role access for templates based on
secured objects where the data security isn't yet available with HCM Spreadsheet Data Loader.
In generated spreadsheets:
• Users see only data sets that they created, unless their role is associated with the spreadsheet template with the
View All option.
• Users can perform the data-set operations that are enabled for their roles.
• Users with the Human Capital Management Integration Specialist job role can perform all actions and view all
data sets.
Translating Spreadsheet Templates

You can provide translated versions of these text entries in a spreadsheet template:
• The template name and description
• Template instructions
• Column headings and descriptions
374
Set the session language to the target language before editing the spreadsheet template to enter translated text.
Related Topics
• Spreadsheet Business Object Access
Dene Categories for Spreadsheet Templates

If you dene many spreadsheet templates, then you may want to group them by category to make retrieval easy. No
categories are predened. This topic describes how to dene template categories.
Follow these steps:
1. In the Setup and Maintenance work area, go to the Manage Common Lookups task.
2. On the Manage Common Lookups page, search for the lookup type ORA_HRC_DL_TEMPLATE_CATEGORY.
3. In the search results, select ORA_HRC_DL_TEMPLATE_CATEGORY to display its lookup codes.
4. Click the New icon to add a row to the lookup codes table.
5. Dene the lookup codes for your categories. For example, to create a category for worker templates:
a. Enter WORKER_TEMPLATES in the Lookup Code eld.

b. Enter Worker in the Meaning eld. This value appears in the list of categories on the Manage
Spreadsheet Templates page, for example.
Tip: The Display Sequence value is a number that species the position of this
category in the list of categories.

You can now select your category on the Manage Spreadsheet Templates and Manage Template Denition pages.
You can also search by category when you perform an advanced search for a spreadsheet template on the Load
Spreadsheet Data page.
Create and Edit Spreadsheet Templates

Creating a spreadsheet template is a ve-step process. You:
1. Dene general information for the template.
2. Design the template's contents and layout.
3. Include template instructions, if required.
4. Specify who can perform data set operations and who can maintain the template.
5. Review the design and generate a test spreadsheet from the template.
This topic provides instructions for the ve steps of this process and describes how to edit an existing spreadsheet
template.
375
Dene the Template

Follow these steps:
1. On the Tasks panel tab of the Data Exchange work area, select Manage Spreadsheet Templates to open the
Manage Spreadsheet Templates page.
2. Click Create.
3. In the Create Template dialog box:
a. Enter a name for the template. By default, generated spreadsheets have the name of the template with a
date and time stamp.
b. The Code value is generated automatically based on the Name value. You can overwrite the code.
c. Select the business object for which you're creating the template.
d. Select a legislative data group (LDG), if appropriate. Typically, the LDG is relevant for Global Payroll
objects.
e. Select a value in the Supported Action eld. If you select a business object that doesn't support deletion
for any of its components, then Create and update appears by default.
f. Enter a description and select a category, if required.
g. Click OK.
The Dene page opens. Some elds contain values that you entered in the Create Template dialog box.
The template is in draft status by default. Spreadsheet users can generate spreadsheets from active
templates only. Leave the template in draft status until it's ready for use.
4. If the spreadsheet template is for an unsecured object, such as Job, or for an object where data security is
supported by HCM Spreadsheet Data loader, then set the Upload Data As value in the Template Security
section. This value determines which user name appears in the object's history. You can't set this value for
secured objects. This step is optional.
5. In the Template Parameters section, set parameter values to apply to all spreadsheets generated from this
template. This step is optional.
6. Click the Design tab to open the Design page.
Design the Template

The Available Aributes panel lists all aributes for the top-level component of the object. Use the Available Aributes
menu to select a dierent component. If you selected the Delete only value in the Supported Action eld, then only
those components that can be deleted appear.
Follow these steps:
1. Add aributes from the Available Aributes panel to the Selected Aributes panel. When you select any
aribute, all aributes that are required to identify the object move automatically to the Selected Aributes
panel.
2. Either edit individual aributes, as required, or manage all aributes at once by selecting Advanced Options
for Aribute Denition.
3. When the template design is complete, click the Add Instructions tab to enter instructions, if required.
Otherwise, click the Manage Role Access tab.
4. Reorder the aributes in the Selected Aributes panel to specify the order you require in generated
spreadsheets.
376
Enter Template Instructions

On the Add Instructions page, you can enter instructions to appear on a separate Instructions worksheet in
spreadsheets generated from the template. These instructions could describe how loaded objects are to be validated,
for example. To enter instructions:
1. Click Add.
2. In the Create Instruction dialog box, enter a heading and the instruction text.
3. Repeat steps 1 and 2 to create additional sections of instruction text, as required. You can reorder and delete
sections.
4. Click the Manage Role Access tab. The Manage Role Access page opens.
Manage Role Access

On the Manage Role Access tab, you specify which roles can:
• Create, save, or upload data sets created in spreadsheets generated from the template.
• View all data sets created in spreadsheets generated from the template.
• Maintain the template.
Note: Manage Role Access actions are enabled only if the Assign Roles to Template eld is set to Enabled.
Assign Roles to Template, which is read only, appears in the Template Security section of the Dene page.
This eld is set automatically based on the object for which the template is dened. It's set to Disabled for
secured objects.
Follow these steps:

1. In the Permied Data Set Operations section of the Manage Role Access page, click the Add icon.
2. In the Search and Select Roles dialog box, search for and select one or more custom roles and click Add.
The roles appear in the Permied Data Set Operations section. By default, the selected roles can create and
save data sets. You can select the Upload and View All options for any of the roles, if required.
Tip: The actions that you authorize on the Manage Role Access tab are enabled by default.
You can deselect the Enabled option for any role to disable the role's access temporarily.
3. In the Template Maintenance section of the page, click the Add icon.
4. In the Search and Select Roles dialog box, search for and select one or more custom roles and click Add.
The roles appear in the Template Maintenance section.
5. Click Save.
6. Click the Review tab. The Review page opens.
Review the Template

On the Review page, your template design appears.
1. To validate the template, click Validate.
2. To generate a sample spreadsheet, click Preview.
Tip: You can click Preview on any page to generate a sample spreadsheet. However, the
spreadsheet shows only the conguration that you have saved so far.
377
The default le name is GenericHdlSpreadsheet.xlsx.

3. Either save the le locally or open it. When you open it, you're prompted to sign in.
4. Review the spreadsheet.
5. Save the template.
When you're ready to make the template available, edit it and set its status to Active.
Edit the Template

To edit a spreadsheet template, search for it on the Manage Spreadsheet Templates page and click its name in the
search results. You can edit an existing spreadsheet template in any status, but you can't change its code or type. In
addition, you can't remove aributes from an active template, but you can disable them.
Related Topics
How You Associate a User Name with a Data Upload

For some object components, you can review the object history to see who last updated the object. This topic explains
how to specify which user name appears in the object history when you upload data using HCM Spreadsheet Data
Loader.
Seing Template Security

When you create a spreadsheet template, you select a value for the Upload Data As eld in the Template Security
section of the Dene page. This value determines what appears in an object's history when data is uploaded from
spreadsheets generated from the template.
When you create a spreadsheet template for an object that can be loaded by a business user, such as Job or Grade:
• You can select either Session User or Elevated User in the Upload Data As eld. When you select Session
User, the user name of the signed-in user who uploaded the data appears in the object history. If you select
Elevated User, then the user name is always FUSION_APPS_HCM_ESS_LOADER_APPID. For objects that
don't use data security, or where data security is available for spreadsheet bulk data loading, Upload Data As is
set to Session User by default.
• If you set the Upload Data As eld to Session user, then you can assign roles to the template. These steps are
required to allow business users to upload data with spreadsheets generated from the template.
When you create a spreadsheet template for an object that uses data security in the application, but that data security
isn't available yet for spreadsheet loading, such as Worker:
• Upload Data As is set to Elevated User and can't be changed. The user name in object history is always
FUSION_APPS_HCM_ESS_LOADER_APPID.
• It isn't possible to share such templates with other roles. Only users who have the predened Human Capital
Management Integration Specialist job role or privileges can upload data from a spreadsheet for objects that
use data security in the application where that data security isn't available for spreadsheet data loading.
Related Topics
378
Set Spreadsheet Template Parameters

In a spreadsheet template, you can set parameters that control the processing of all spreadsheets generated from the
template. Any values that you specify in a spreadsheet template override equivalent enterprise seings. This topic
explains how to set spreadsheet template parameters.
Follow these steps:
1. Open the Dene page in the Manage Spreadsheet Templates task ow.
2. In the Template Parameters section, click the Add icon.
3. In the Search Template Parameters dialog box, either enter a parameter name or select a category and click
Search. This table lists the parameters and their categories.
Parameter Category Description Enterprise Default Value
Enable Audit Data Availability Species whether audit No

data is captured when
audit is congured for
business objects loaded from
generated spreadsheets.

Enable Incremental Load Availability Enable events to be triggered No

Events for the data supplied.

Caution: Enabling load
events will signicantly
increase the time it
takes for your data to
load.

Purge Audit Data File Denition Species whether audit No

data is purged for objects
successfully loaded
or updated from the
spreadsheet.

Maximum Concurrent Performance The maximum number 8

Threads for Load of threads to be used
concurrently to load
spreadsheet data.

Calculate Worker Full-Time Scheduling Default Species whether to calculate No

Equivalent automatically the full-time
equivalent value of the
working hours on a worker
assignment.

This parameter applies to
templates for the Worker
object only.
379
Parameter Category Description Enterprise Default Value
Create Worker Default Work Scheduling Default Species whether to create No

Hour Paern default working hour paerns
automatically for workers
loaded without working hour
paerns.

This parameter applies to
templates for the Worker
object only.

Date-Eective Update Mode Scheduling Default Retain

When set to Replace,
species that the data in
spreadsheets replaces any
existing data in Oracle HCM
Cloud. When set to Retain,
species that any existing
future-dated changes are
retained.
Initiate Business Object Post Scheduling Default Species whether to run Yes
Processing processes that are congured
to run automatically after the
object is loaded.

Maximum Percentage of Scheduling Default The percentage of business 100

Load Errors object instances in error that
can occur for a business
object before the validation
and load processes stop.

4. In the search results, select a parameter and click OK. The selected parameter appears in the Template
Parameters section.
5. Enter or select a value for the parameter, as appropriate.
6. Repeat from step 2 for additional parameters.
7. Either click Save and Close or select a dierent page in the task ow.
You can set parameters to support each template's use case. For example, you can set Date-Eective Update Mode to:
• Replace, in a spreadsheet template for loading new hires

• Retain, in a spreadsheet template for updating worker records
Tip: You can set spreadsheet parameter values for the enterprise on the HCM Spreadsheet Data Loader
Parameters tab of the Congure HCM Data Loader page.
Related Topics
380
Spreadsheet Template Design

Creating a spreadsheet template is a ve-step process. You:
1. Dene general information for the template.
2. Design the template's contents and layout.
3. Specify instruction text, if required.
4. Identify the roles that can perform data set operations, such as create and upload, and the roles that can
maintain the template
5. Review the design and generate a test spreadsheet from the template.
This topic describes the design step of this process.
Available Aributes Panel

The Available Aributes panel lists all aributes of the selected component of the object. You can:
• Set the Show eld to lter the aributes.
• Select a dierent component or all components.
• Switch to a tree view to see the component hierarchy. For each component of the object, you see separate
entries in the hierarchy for aributes, exeld aributes, and child components.
• Click an aribute name to view the aribute details.
• Move aributes from the Available Aributes panel to the Selected Aributes panel. When you move the rst
aribute, any required aributes for the component move automatically to the Selected Aributes panel.
Aributes that are required conditionally don't move. You must add them explicitly to include them.
Note: On occasion, you may see two aributes with the same name in the Available Aributes panel.
Typically, this duplication occurs for foreign object references. It enables you to choose between entering free
text and selecting a value from an LOV. The icons that precede each name show the aribute type.
Selected Aributes Panel

In the Selected Aributes panel, aributes appear in the order in which you added them. You can:
• Edit the details of an aribute. For example, you can:
◦ Change the column heading.
◦ Make an optional value required.
◦ Specify a default value. You can also make aributes, such as those with default values, read-only.
◦ Specify whether the aribute is visible in the generated spreadsheet.
◦ Disable optional aributes. These aributes appear but can't be updated.
◦ Enter a description to appear as help text in the generated spreadsheet.
◦ Congure a list of values to validate the aribute.
• Create Note aributes. Use Note aributes to return values from a list of values for information only. For
example, you may have a list of values for the PersonNumber aribute that returns the person number to
this aribute. It can also return the person's last and rst names in the Note column. You can make the Note
column read-only, and multiple Note columns can have values returned from the same list of values. Data
381
in Note columns isn't passed to the application, but can be used in the data set for information purposes or
coordination of multiple contributors.
You can also use Note aributes to communicate information that doesn't need to be uploaded. For example,
the Human Resources Specialist may have submied overtime information in a spreadsheet for the Payroll
Administrator to action.
• Change the aribute order. After you determine if any aributes are hidden, click the Reorder icon to open the
Reorder Aributes dialog box.
• Duplicate a component. This option exists for any component that can appear more than once in an object,
such as Person Phone or Location Legislative Extra Information.
Tip: Edit the selected aributes of the component before creating additional instances.
Advanced Seings
To manage all aributes at once, click the Advanced Options for Aribute Denition icon. On the Advanced Options
for Aribute Denition page, you can manage:
• Basic information, exeld aributes, and lists of values.

• Aribute keys. When you import data to a spreadsheet from a le, you can include a header. The aribute
names used in the import le can be dierent from those in the spreadsheet. In this case, the Aribute
Key elds must include the names from the import le. For example, you can import a location code to a
spreadsheet from a le where it's known as the location ID. To ensure that the data imports successfully, you
must set the Aribute Key value to Location ID for the Location Code aribute.
Guidelines for Designing Spreadsheet Templates

Spreadsheet templates are highly congurable. Therefore, you can design them to support specic business use cases.
This topic provides some guidelines to help you create spreadsheet templates that minimize the scope for error and are
easy to use.
Supported Actions
Depending on the business object, you can use HCM Spreadsheet Data Loader to either create and update or
delete object components. You can design a single spreadsheet for both creating and updating an object. However,
spreadsheet templates that support a single action are beer for users and easier for you to manage. For example:
• In templates for creating objects, you can mark as required all aributes that must be supplied for new objects.
Typically, the same aributes aren't required when updating objects, so you can mark dierent aributes as
required in templates for updating objects.
Tip: To mark an aribute as required, edit the aribute in the Selected Aributes panel on the
Design page and select Required.
• In templates for updating objects, you can congure lists of values to identify records to update.
382
Lists of Values
For many aributes, you can ensure that users enter only valid data by providing choice lists and searchable lists of
values. Some aributes have lists of values by default. In particular:
• Some lookup-validated aributes are automatically congured with choice lists. A list of values is displayed
when the user clicks in the cell.
• To reference a foreign object from your template, you can include the Oracle Fusion Surrogate ID aribute.
Aributes like this are automatically congured with searchable lists of values, and the selected aribute is
returned to the spreadsheet. While a surrogate ID itself may not be meaningful, you can also congure your
own lists of values for aributes included in a spreadsheet. These aributes can be validated using a lookup
type, value set, or view object.
For example, you can return additional values to other aributes, such as Person Number, instead of just
returning the person ID. You can also copy the list of values conguration to another aribute that is typically
used to identify a record, such as the Name or Number identier. You congure the list of values to return the
recognizable number.
Tip: Aributes with lists of values have the List of values icon before their names in the Available Aributes
panel of the spreadsheet template.
Default Values
You can congure default values for aributes in spreadsheet templates. You may want to exclude aributes with
default values so that you can enforce their values. Alternatively, you can include the aribute so that users can enter a
value, which overrides the default value.
Date Editors
A date editor is provided automatically for all date aributes. However, the user must click in the spreadsheet row
to initialize date editors. Therefore, you're recommended not to make a date value the rst column in the row. This
approach ensures that date editors in the row are initialized before they're used.
How You Congure Default Values for Spreadsheet

Aributes
When you design a spreadsheet template for bulk data loading using HCM Spreadsheet Data Loader, you can specify
default values for aributes. This topic describes the ways in which you can specify default values.
Specifying Default Values for Date Aributes

This table describes the options for specifying default date values.
383
Option Description
Specied date Using the date editor, select a date.

Load date Use the date when the spreadsheet row is loaded.

Existing selected aribute Select another date aribute to supply the default value. The aribute must be in the Selected
Aributes section of the Design page.

Use expression Supply a Groovy expression to derive the default value.

For example, to set the default value of a date aribute to the load date:
1. Select the aribute in the Selected Aributes section of the Design page of Manage Spreadsheet Templates and
click Edit.
2. In the Edit dialog box, set Default Value to Value and select Load date from the list.
Specifying Default Values for Aributes Other Than Dates

This table describes the options for specifying default values for aributes other than dates.
Option Description
Constant value Enter the default value.

Existing selected aribute Select another aribute of the same data type to supply the default value. The aribute must
be in the Selected Aributes section of the Design page.

Use expression Supply a Groovy expression to derive the default value.

Supplying Groovy Expressions

Using Groovy expressions enables you to manipulate other aribute values to provide a default value. To specify a
Groovy expression to derive a default value:
1. Select the aribute in the Selected Aributes section of the Design page and click Edit.
2. In the Edit dialog box, set Default Value to Value and select Use expression from the list.
3. Enter the expression in the text area and click Validate to ensure the expression is valid.
Hiding Aributes
You may want to hide aributes that have default values so that spreadsheet users aren't aware of them. To hide an
aribute, edit it in the Selected Aributes panel on the Design page of the template. In the Edit dialog box, deselect the
Visible option.
384
Congure Lists of Values for Aribute Validation

Some types of aributes are congured automatically with choice lists or searchable lists of values in spreadsheets. For
such aributes, spreadsheet users can select only valid values, which simplies data loading. You can congure lists of
values for other aributes to make populating spreadsheets easier. This topic describes how to congure lists of values.
Select the LOV Source for an Aribute

To validate an aribute using a list of values, you must identify the list source. It can be one of:
• Lookup
• Value set
• View object
Select View object to include user key values in a spreadsheet in place of a surrogate ID to reference a foreign object.
Having user keys helps the spreadsheet user, who sees recognizable values in the spreadsheet. For example, in a
spreadsheet to create positions you include a reference to a department. You could just include the Department ID
aribute in the spreadsheet, as it's automatically congured with a searchable list of values. However, when the user
selects a value from the list, the surrogate ID is returned to the spreadsheet. Instead, you could include the Department
user key aribute in the spreadsheet. Using a view object, you congure the Department aribute with a searchable list
of values to return the department name to the spreadsheet.
Validate Aributes Using Lookups or Value Sets

Follow these steps:
1. On the Design page of the Manage Spreadsheet Templates task ow, move aributes to the Selected Aributes
pane.
2. In the Selected Aributes pane, select the aribute to be validated with a lookup type or value set and click Edit.
3. Complete the details on the main tab of the Edit dialog box, as appropriate.
When you're editing the details of an existing list of values, you can change the list display type on the main
tab, if required.
4. Click the List of Values tab.
5. Set the LOV Source value to Lookup or Value set, as appropriate.
6. Select the name of the lookup type or value set.
7. Specify whether the LOV is to appear as a choice list or a searchable list of values in generated spreadsheets.
Tip: If the list of values has more than 20 entries, then a searchable list of values is beer for
the spreadsheet user. Use choice lists only when the number of choices is limited.
8. Select aributes to appear in the LOV.
9. Identify the values to be returned to the spreadsheet from the choice list or search.
If the LOV is a searchable list of values, then you can add lter and search criteria.
• Add lter criteria to enable the user to lter the returned list of aribute values.
• Add search criteria to enable the user to search the returned list of aribute values.
385
To add lter criteria, in the Filter Criteria section:

1. Select a value in the Filter Criteria eld and click Add. The View Criteria and Bind Variable values are
completed automatically.
2. Set the Expression Type value for each of the view criteria to one of the following values:
◦ Constant
◦ Expression
◦ Aribute
3. If the Expression Type is set to Constant or Expression, then enter the constant or expression in the Value
eld. If the Expression Type is set to Aribute, then select the aribute in the Value eld.
To add search criteria, in the Search Criteria section:
1. Select a value in the Search Criteria eld and click Add. The Search Criteria and Aribute elds are
completed automatically.
2. Repeat step 1 for additional search criteria.
Click OK to close the Edit dialog box.
Validate Aributes Using View Objects

Follow these steps:
1. On the Design tab of the Manage Spreadsheet Templates task ow, move both the surrogate ID and user key
aributes to the Selected Aributes pane.
2. Edit the surrogate ID aribute. On the List of Values tab in the Edit dialog box, the LOV Source eld shows the
full path to the view object. For example, for the Department ID aribute you would see the following value:
oracle.apps.hcm.organizations.publicView.DepartmentPVO
Copy this path and close the Edit dialog box.

3. Edit the primary user-key aribute and set LOV Source to View object.
4. In the LOV Source eld, paste the full path to the view object that you copied from the surrogate ID aribute.
5. Leave Displayed As set to Searchable list of values.
6. Select the aributes to appear in the searchable list.
7. Identify the aribute values to be returned to the spreadsheet from the search. Usually, you include both
the surrogate ID and one or more user key values. The user key values are for the spreadsheet user, and the
surrogate ID is used to load the data. You can hide the surrogate ID aribute in generated spreadsheets by
deselecting the Visible option in the Edit dialog box for the aribute.
8. Enter lter and search criteria, as required.
9. Click OK to close the Edit dialog box.
Autogenerated Aribute Values in Spreadsheet

Templates
In spreadsheet templates for the Worker object you can specify that values for some aributes, such as Person Number
and Assignment Number, are generated automatically. For example, on the Design page in a Worker spreadsheet
template, you edit the Person Number aribute in the Selected Aributes panel and select Autogenerate. In this case,
386
users don't have to supply the person number value in generated spreadsheets. However, so that related records can be
identied and processed together, a unique identier must still be supplied. Therefore, Person Number must appear in
generated spreadsheets and its value must be a unique identier. This value isn't used as the person number, which is
generated on successful creation of the worker record.
To ensure that users supply this unique identier for a logical object, these rules apply to the template denition:
• If you select the Autogenerate option for an aribute, then the Required option is selected automatically and
made read-only.
• If the Required option is selected and the Default Value eld is set to None, then the Visible option is selected
automatically and made read-only.
• A default column heading is dened. For example, for the Person Number aribute the column heading is
Person Unique Identier. For the Assignment Number aribute, the column heading is Assignment Unique
Identier. You can change the default column heading.
• The default description of the aribute explains that a unique identier must be supplied. You can edit this
description.
Spreadsheets generated from the template include the Person Number or Assignment Number aribute, as
appropriate, with its new column heading and description. For the aribute value, users must enter a unique identier
to ensure that records are loaded successfully.
Copy Spreadsheet Templates

Copying a spreadsheet template and editing the copy is an ecient way to create a new spreadsheet template. This
topic describes how to copy spreadsheet templates. You perform this task in the Data Exchange work area.
Follow these steps:
1. On the Tasks panel tab of the Data Exchange work area, select Manage Spreadsheet Templates.
2. On the Manage Spreadsheet Templates page, search for the spreadsheet template to copy.
3. Select the spreadsheet template in the search results and select Copy from the template Actions menu.
4. In the Copy Template dialog box:
a. Enter a unique name for the spreadsheet template in the Name eld.
b. A Code value is created automatically based on the name value. You can overwrite the code value.
c. Select a legislative data group, if the template is legislation-specic.
Note: You can't change the Supported Action value. For example, if Supported
Action is set to Delete only in the source spreadsheet, then copies of that spreadsheet
have the same value.
d. Enter a description and select a category, if required.
e. Click OK.
5. Click OK to close the Conrmation dialog box.
6. On the Manage Spreadsheet Templates page, search for the new spreadsheet template.
7. In the search results, click the name of the spreadsheet template to open it for editing.
You can copy a spreadsheet template in any status, but the status of the new spreadsheet template is always Draft.
Change the status to Active when the template is ready to use. Active spreadsheet templates are available on the Run
Spreadsheet Data Loader page.
387
Export and Import Spreadsheet Templates

You can import spreadsheet templates to other environments to avoid having to recreate them. For example, you
can export spreadsheet templates from a test environment and import them to a production environment. This topic
describes how to export and import spreadsheet templates. You perform these tasks in the Data Exchange work area.
Export Spreadsheet Templates

Follow these steps in the source environment:
2. On the Manage Spreadsheet Templates page, search for and select the spreadsheet template that you want to
export.
3. From the Actions menu for the spreadsheet, select Export.
4. In the Opening dialog box, select Save le and click OK.
5. In the le-name dialog box, select a location for the le and click Save.
The le is exported to the specied location in XML format. Deliver the le to the target environment.
Import Spreadsheet Templates

Follow these steps in the target environment:
2. On the Manage Spreadsheet Templates page, click Import.
3. In the Import dialog box:
a. Enter a unique name for the spreadsheet template. This name applies in the target environment.
b. The Code eld is completed automatically based on the name value. You can overwrite the value.
c. If your template is legislation-specic, then select the legislative data group.
d. Click Choose File to select the template le.
e. Enter a description and select a category, if required.
f. Click OK in the Import dialog box to import the template.
Click OK to close the Conrmation dialog box.

4. On the Manage Spreadsheet Templates page, search for the imported template.
The status of an imported spreadsheet template is always Draft. Change the status to Active when the
template is ready for use.
How You Enable Business Users with Custom Roles to

Load Spreadsheet Data
Business users can load data for objects such as jobs and locations from HCM Spreadsheet Data Loader spreadsheets
in their work areas. These business users can generate spreadsheets and load data from them because they have
388
predened roles that provide the access they need. This topic explains how to give the same access to business users
with custom roles.
For example, let's say that your human resource specialists create job denitions in bulk. They load them from a
spreadsheet on the Manage Jobs page in the Workforce Structures work area. They can generate the spreadsheet and
load the data because:
• They have the predened Human Resource Specialist job role. This job role inherits the Workforce Structures
Management duty role, which inherits the Load Data Using HCM Spreadsheet Data Loader aggregate privilege.
• The Job (ORA_PER_JOB) spreadsheet template behind the Manage Jobs page lists the predened Human
Resource Specialist job role on its Manage Role Access page. Users with the role can create, save, and upload
data.
Human resource specialists who use a custom role can't load data from a spreadsheet by default. To let them load data,
you:
• Add the Load Data Using HCM Spreadsheet Data Loader aggregate privilege to their custom role. You need the
IT Security Manager job role or privileges to update custom roles.
• List the custom role on the Manage Role Access page in the predened spreadsheet template for the object.
You need the Human Capital Management Integration Specialist job role or privileges to update predened
templates.
You can make these changes for custom versions of any predened role that can load data from HCM Spreadsheet
Data Loader spreadsheets.
Related Topics
• Edit Job and Abstract Roles
Add a Custom Role to a Predened Spreadsheet

Template
Your business users may need to load data in bulk from HCM Spreadsheet Data Loader spreadsheets in their
work areas. If they're using custom roles, then you need to give those roles permissions to generate and use the
spreadsheets. This topic describes how to add custom roles to predened spreadsheet templates.
Suppose you want users with the Human Resource Specialist Custom role to load grades on the Manage Grades page in
the Workforce Structures work area. Follow these steps:
1. Sign in with the Human Capital Management Integration Specialist job role or privileges.
2. Select Navigator > My Client Groups > Data Exchange
3. In the Data Exchange work area, select the Manage Spreadsheet Templates task on the Tasks panel tab.
4. On the Manage Spreadsheet Templates page, search for the Grade (ORA_PER_GRADE) spreadsheet template.
Tip: The codes of predened spreadsheet templates begin with the characters ORA_.
5. Click the template name in the search results to open the spreadsheet template for editing.
6. Click the Manage Role Access tab in the spreadsheet template.
7. Click the Add icon in the Permied Data Set Operations section of the Manage Role Access page.
389
8. Select the Human Resource Specialist Custom role in the Search and Select Roles dialog box and click Add.
Your custom role appears in the Permied Data Set Operations section. The Create and Save options are
selected automatically. They mean that users with this role can create data sets in spreadsheets generated from
the template and save them.
9. Select Upload to let users upload their data. Select View All to let users view spreadsheets generated by other
users from the template.
10. Click Save then Done.
Tip: You can't change the aributes in a predened spreadsheet template, but you can set the template
parameters and manage role access.
FAQs for HCM Spreadsheet Data Loader Templates

Can I hide aributes in spreadsheet templates?
Yes. In the Selected Aributes panel on the Design tab of the template, edit the aribute. In the Edit dialog box, deselect
the Visible option.
Why can't I manage role access for some objects?

For secured objects where data security isn't yet available for spreadsheet data loading you can't manage role access
in the spreadsheet template. You can manage role access only for unsecured objects and objects where data security is
implemented for spreadsheet bulk loading.
Check the read-only Assign Roles to Template eld on the Dene page of the template. If it's set to Disabled, then you
can't manage role access for the object.
Can I load data from a spreadsheet as the session user?

Yes. In the spreadsheet template from which you generate the spreadsheet, Upload Data As must be set to Session
User. This seing is for unsecured objects and those secured objects where data security is implemented for
spreadsheet data loading.
Why can't I delete an existing spreadsheet template?

You can only delete a template if it has a draft status and has no data sets associated with it.
390
Integrating with HCM Importing and Loading Data Using HCM Spreadsheet Data
Loader
28 Importing and Loading Data Using HCM

Generate Spreadsheets
To load data using HCM Spreadsheet Data Loader, you must rst generate a spreadsheet from a spreadsheet template.
This topic describes how to generate a spreadsheet and save it locally. You perform this task in the Data Exchange work
area, or directly in the page that maintains the object, such as Jobs.
Follow these steps:
1. On the Tasks panel tab of the Data Exchange work area, select Run Spreadsheet Data Loader.
2. On the Run Spreadsheet Data Loader page, the saved search runs automatically. If the template that you want
to use doesn't appear, then click Show Filters, enter search terms for the template, and click Search.
Tip: In the search results, click the Template Overview icon for a template. The Template
Overview dialog box provides a list of the aributes that the template supports.
3. Click the name of the template that you want to use.

4. In the Opening GenericHdlSpreadsheet.xlsx dialog box, you will be prompted to log in. You should log in before
saving the le, otherwise the Save File won't have the columns generated for the template shape.
5. In the le-name dialog box, select a location and save the spreadsheet.
You can now enter data in the spreadsheet and upload it.
Related Topics
Import Data to a Spreadsheet

To populate a spreadsheet with data for upload, you can either enter the data manually or import it from a le. This
topic describes how to import data to a spreadsheet from a le.
Follow these steps:
1. If the spreadsheet isn't already open, then open it and sign in when prompted.
2. You import data to a data set. You can either create the data set or use an existing data set.
◦ To create a data set, click Create Data Set on the Spreadsheet Loader toolbar. A name is assigned
automatically to this new data set. You can overwrite the data set name.
◦ To use an existing data set, select its name in the Search section of the spreadsheet and select a Search
Mode value. Click Search in the Spreadsheet Loader toolbar.
3. On the Spreadsheet Loader toolbar, click Import File. The Import from File dialog box opens.
4. In the Import from File dialog box, select one of File Type values shown in this table.
391
Loader
File Type Description
Comma separated values Comma-separated (.csv) le

Pipe separated values Delimited data (.dat) le

Other le type Text le (.txt) with a user-specied separator

XML le type XML le

Tip: You can download CSV and XML le templates from a spreadsheet template. Use them
to load data to a spreadsheet generated from the same template.
5. For le types other than XML le type, indicate whether the le contains a header.
The header provides the names of the aributes for which the le contains values. In this case, the aribute
order in the le doesn't have to match the spreadsheet column order. If you deselect Header included, then
the order of the values in the le must match the order of the columns in the spreadsheet.
In an XML le, the XML tags used for the aribute values must use the aribute keys congured in the
spreadsheet template.
6. Click Browse to select the le to import.
7. For le types other than XML le type, expand the Advanced File Options section. Complete the options as
shown in this table for the selected le type. You can use the default values where supplied.
File Type File Separator Escape Indicator Newline Indicator
Comma separated values Not applicable 1 - 10 characters 1 - 10 characters

Pipe separated values Not applicable 1 - 10 characters 1 - 10 characters

Other le type 1 - 10 characters 1 - 10 characters 1 - 10 characters

The Newline Command eld shows the newline command constructed from the supplied Escape Indicator
and Newline Indicator values.
8. Click OK to import the data from the selected le. After the data is imported, you can edit any of the imported
aribute values.
Note: Some validation of the imported data occurs. Any errors appear automatically in the Progress and
Message columns of the Spreadsheet Line Status section of the spreadsheet. Correct any errors before you
aempt to upload the data.
392
Loader
Manage Spreadsheet Data Sets

A data set is all data loaded from an instance of the same spreadsheet and identied by the same data-set name. You
can load the data from a spreadsheet all at once. Alternatively, you can add data rows to an existing spreadsheet and
upload them to the existing data set. This topic describes how to create and manage spreadsheet data sets.
Create a Data Set

Follow these steps:
1. Open the generated spreadsheet.
2. In the Connect dialog box, click Yes and sign in when prompted. After a few seconds, the spreadsheet shows all
aributes from the selected spreadsheet template.
3. Click the Spreadsheet Loader tab in the spreadsheet toolbar.
4. Click Create Data Set and click OK to close the dialog box. A data set name is generated automatically, based
on the template name, date, and time, but you can overwrite it. The name must be unique for the spreadsheet
template.
5. Click OK to close the conrmation dialog box.
You can either enter data manually in the spreadsheet or import it from a le.
Update a Data Set

To retrieve an existing data set, follow these steps:
1. Either open the original spreadsheet or generate a new spreadsheet from the same template as the original
spreadsheet.
2. In the Data Set Name eld under the Search header, select the name of the data set that you want to update.
Available data sets:
◦ Were uploaded from a spreadsheet that was generated from the same spreadsheet template as the
current spreadsheet.
◦ Still exist in the stage tables. You can't update a data set after you have deleted it from the stage tables.
3. Select a Search Mode value. You can retrieve either all records in the data set or only those that failed to load.
4. In the Spreadsheet Loader toolbar, click Search. The specied data-set records are downloaded to the
spreadsheet.
You can correct failed rows and add new rows, but you can't update any row that loaded successfully. Rows that you
add belong to the data set that you're updating. When you upload the data, only new and updated rows are imported to
the stage tables.
Save a Data Set

You can import a data set periodically to the HCM Data Loader stage tables by clicking Save on the Spreadsheet Loader
toolbar. The data isn't loaded to the application tables until you click Upload. The Save action lets you:
• Import data to the stage tables over a period of time. For example, you can enter and save payroll adjustments
throughout the week but upload them only at the end of the week.
• Create large volumes of data that you save regularly to a single data set. You don't have to manage those
volumes all at once in the spreadsheet.
393
Loader
• Allow multiple users to supply data for processing in the same data set.
Related Topics
• Maintain the HCM Spreadsheet Data Loader Stage Tables
Upload Data Using HCM Spreadsheet Data Loader

In this example, you learn how to upload jobs for the Sales Department using HCM Spreadsheet Data Loader.
This table summarizes key decisions for this scenario.
Which business object am I loading? Job

Which spreadsheet template am I using? Sales Jobs

How do I populate the spreadsheet? Import the le Sales_ Jobs.csv which is a comma-separated le
that contains a header and uses the \n newline command.

Will I create a data set or import the le to an existing data set? Create a data set.

Summary of the Tasks

Upload the jobs by:
1. Generating the spreadsheet

2. Importing Job objects to the spreadsheet
3. Uploading jobs and correcting errors
Prerequisites
Before you can complete this task:
1. You must have installed the desktop client Oracle ADF 11g Desktop Integration Add-in for Excel.
2. You must have enabled the Trust Center seing Trust access to the VBA project object model in Microsoft
Excel.
3. The Sales Jobs spreadsheet template must exist and be active.
4. The Sales_Jobs.csv le must exist.
394
Loader
Generating the Spreadsheet

1. On the Tasks panel tab of the Data Exchange work area, select Run Spreadsheet Data Loader.
2. On the Run Spreadsheet Data Loader page, click Show Filters.
3. Enter Sales Jobs in the Name eld and click Search
4. In the search results, click the name of the Sales Jobs template.
5. In the spreadsheet dialog box, select Save File and click OK.
6. In the le-name dialog box, select a location. Enter SalesJobs.xlsx in the File name eld and click Save.
Importing Job Objects to the Spreadsheet

1. Open the SalesJobs.xlsx spreadsheet and sign in when prompted.
2. On the Spreadsheet Loader toolbar, click Create Data Set. Click OK to close the warning message, and click OK
to close the conrmation message.
The data set is created with a generated name.
3. On the Spreadsheet Loader toolbar, click Import File.
4. Complete the elds of the Import from File dialog box as shown in this table.
Field Value
File Type Comma separated values

Header Included Yes

File Sales_Jobs.csv

Escape Indicator \

Newline Indicator n

5. Click OK.
6. Correct any Import File Errors reported in the Progress and Message columns of the Spreadsheet Line Status
section of the spreadsheet.
Uploading Jobs and Correcting Errors

1. On the Spreadsheet Loader toolbar, click Upload.
Data is imported to the stage tables. Objects that import successfully are loaded automatically to the
application tables.
2. Click Refresh.
395
Loader
Errors from both import and load are reported automatically in the Progress and Message columns of the
Spreadsheet Line Status section of the spreadsheet.
3. Correct any errors in the spreadsheet.
4. Repeat from step 1 of Uploading Jobs and Correcting Errors until all rows are imported and loaded successfully.
5. Close the spreadsheet.
Related Topics
• Set Up Desktop Integration for Excel
How You Delete Data Using HCM Spreadsheet Data

Loader
You can delete business objects using HCM Spreadsheet Data Loader, regardless of how they were created. This topic
describes how to delete data using HCM Spreadsheet Data Loader.
Designing the Spreadsheet Template

To delete data, you create a spreadsheet template and set the Supported Action value to Delete only. You can use
spreadsheets generated from that template to delete specied objects. The Delete only option for the Supported
Action eld is available only for objects with at least one component that can be deleted. The object components that
appear on the Design tab of the Manage Spreadsheet Templates page are those that you can delete. For example, for
the Job object you see the Job Evaluation, Job Valid Grade, Job Extra Information, and Job Legislative Extra Information
components. You don't see the parent Job component, because you can't delete it.
When you move an aribute to the Selected Aributes panel of the Design page, all aributes required for deleting the
component move across simultaneously.
Copying Spreadsheet Templates

When you copy a spreadsheet template, you can't change the supported action. Therefore, if the source template has
Delete only as its supported action, then the copy has the same supported action.
Uploading the Spreadsheet

To delete object components using a spreadsheet, you enter aribute values to identify the components and upload the
spreadsheet. When you delete a parent component, its child components are deleted automatically.
Tip: You can monitor progress on the Import and Load Data page. Search for data sets by le type to list
those loaded from spreadsheets.
FAQs for Importing and Loading Data Using HCM

396
Loader
How do I x HCM Spreadsheet Data Loader errors?

You x errors in the spreadsheet from which you uploaded the data. Errors are reported in the Progress and Message
columns of the Spreadsheet Line Status section of the spreadsheet when you click Refresh. After correcting any errors,
click Upload again.
Can I load date-eective data?

Yes. You can create, update, and correct date-eective objects. To load date-eective history, you provide a separate
row for each date range.
Can I change rst and last eective dates?

Yes. Include the Replace First Eective Start Date and Replace Last Eective End Date aributes in the spreadsheet
template, as appropriate. Spreadsheet users set these aributes to Y and provide revised dates on the Eective Start
Date and Eective End Date aributes.
For some objects, you can change only one of these dates.
Can I load translated objects?

Yes. You don't have to create a separate spreadsheet template for the translation object. Instead, include translation
aributes, such as Language, in the spreadsheet template for the base object. You can use spreadsheets generated
from the template to maintain both base-object and translation data.
397
Loader
398
Integrating with HCM Postload Processing
29 Postload Processing
Processes to Run After Loading Data

After a successful data migration or incremental update, you must run processes to complete the setup of some
business objects. This topic describes these processes.
This table identies processes to run after loading Worker objects. The table also suggests the order in which to run the
processes when you're running them all manually. By default, these two processes run automatically when a load of
Worker objects completes:

You can prevent either or both of these processes from running automatically using a SET instruction in the Worker.dat
le. Alternatively, you can prevent the processes from running for the enterprise by seing conguration parameters.
Process Order
Synchronize Person Records 1

Refresh Manager Hierarchy 2

Update Person Search Keywords 3

Optimize Person Search Keywords 4

Index

Autoprovision Roles for All Users 5

Send Pending LDAP Requests 6

Send Personal Data for Multiple Users 7

to LDAP

Apply Name Formats to Person Not applicable

Names

Run these processes in the Scheduled Processes work area. Select Navigator > Tools > Scheduled Processes.
399
Process Descriptions
Apply Name Formats to Person Names
Applies the Display Name, List Name, Full Name, or Order Name format to denormalized person-name data when you
add or update a name format. Optionally, you can run the process for a single country.
Autoprovision Roles for All Users
Generates requests to provision and remove roles based on current role-provisioning rules.
Optimize Person Search Keywords Index
Optimizes the index of the PER_KEYWORDS table to improve search performance. By default, the process runs for a
maximum of 180 minutes and performs a full optimization. You can enter a dierent Maximum Optimization Time. If
you select the Rebuild the index option, then the Maximum Optimization Time value is ignored. Rebuilding the index
can be time consuming.
Run this process whenever you run Update Person Search Keywords. Run it after that process completes.
Refresh Manager Hierarchy
For performance reasons, the complete manager hierarchy for each person is extracted from active data tables.
The hierarchy is stored in a separate manager hierarchy table, known as the denormalized manager hierarchy
(PER_MANAGER_HRCHY_DN). This approach ensures that a person's manager hierarchy is both easily accessible and
up to date. The Refresh Manager Hierarchy process populates the denormalized manager hierarchy table with latest
information after each data load.
If this process isn't enabled to run automatically, then run it manually after all data loads.
Send Pending LDAP Requests
Sends user-account and role-provisioning requests to your LDAP directory.
Send Personal Data for Multiple Users to LDAP
Ensures that personal data held in your LDAP directory matches that held by Oracle HCM Cloud.
Synchronize Person Records
Noties consuming Oracle Cloud applications, such as Oracle Fusion Trading Community Model, of changes to person
and assignment details since the last data load.
For a once-only load, submit this process with the After Batch Load parameter set to Yes. In the From Date eld, enter
the start date of the load. In the To Date eld, enter the end date of the load. For ongoing updates with daily changes to
person records, schedule the process without specifying start and end dates.
Update Person Search Keywords
Several aributes of person, employment, and prole records are used as person-search keywords. This process copies
keyword values in all installed languages from the originating records to the PER_KEYWORDS table, where they're
indexed to improve search performance.
400
Select a person name in the Name eld to run the process for a single worker. If you leave the eld blank, then the
process runs for all workers, which can be time consuming. To avoid performance problems, submit the process with
the After Batch Load parameter set to Yes. In this case, the process creates keywords for new records but doesn't
update those for existing records. Leave the Batch ID eld blank.
Actions to Perform After Loading Trees

After loading department or organization tree nodes, you must activate your tree version. For more information, see the
Implementing Global Human Resources guide.
Related Topics
• Why You Run the Send Pending LDAP Requests Process
• Autoprovisioning
Guidelines for Running Postload Processes

This topic provides additional guidance for some postload processes. In particular, it identies when the processes are
required and when they're optional.
Send Pending LDAP Requests

You must always run Send Pending LDAP Requests after loading worker records. When you run Send Pending LDAP
Requests:
• User accounts are created for new workers.

• Roles are provisioned to user accounts as specied by current role mappings.
If appropriate role mappings don't exist when you load new workers, then user accounts are created but no roles are
provisioned. User accounts without roles are automatically suspended when Send Pending LDAP Requests completes.
Also, subsequent role-provisioning requests to the suspended user accounts may be slow to process. To avoid this
scenario:
1. Create a role mapping to provision at least one role, for example, Employee, to every current worker before you
load worker records.
2. Prevent the creation of user accounts for terminated workers. Set the User Account Creation for Terminated
Workers option to No using the following in the Setup and Maintenance work area:
◦ Functional Area: Workforce Structures

◦ Task: Manage Enterprise HCM Information
3. Load worker records.
Note: Always create a role mapping for the workers you're loading before you load them. Having this role-
provisioning rule in place prevents new user accounts from being suspended unnecessarily.
401
Autoprovision Roles for All Users

You don't have to run this process after the initial or only load of worker records if you create role mappings to
autoprovision roles before you load workers. However, if you load the workers before creating the role mapping, then
you must run this process followed by Send Pending LDAP Requests for the loaded workers.
You don't have to run this process after an incremental update. However, you're recommended to run this process
whenever a change is made to the autoprovisioning rules.
Send Personal Data for Multiple Users to LDAP

Run this process after the initial or only load of worker records. Run it after an incremental load:
• For changed users only
• If you're loading workers separately from their managers
• If updates were made to personal data by means of SQL scripts
Related Topics
• Role Mappings
• Create a Role Mapping
How You Validate Loaded Data

Once HCM Data Loader loads your data successfully, you're recommended to validate that the loaded objects appear as
expected. This topic identies some of the ways in which you can validate loaded data. These include use of:
• Manual testing
• Oracle Transactional Business Intelligence (OTBI) reports
• HCM Extracts
Using Manual Testing

You can:
• Validate data interactively by searching for a representative sample. For example, you can search for workers
in the Directory or Manage Person work area. If a worker is also a manager, then you can explore the manager
hierarchy.
• Validate work structures by searching for them. For example, you can search for jobs on the Manage Job page
and locations on the Manage Locations page. Alternatively, you can test that they're available for selection. For
example, you can update a worker's assignment to select a dierent job or location.
Using Oracle Transactional Business Intelligence Reports

You can use predened OTBI reports to validate some uploaded data. To run these reports:
1. Open the Reports and Analytics work area.
402
2. In the Contents pane of the work area, open the folder Shared Folders > Human Capital Management. Many
subfolders of the Human Capital Management folder contain a Transactional Analysis Samples folder,
which contains the predened reports.
To list the predened reports for an area, select the relevant Transactional Analysis Samples folder in the Contents
pane and click the Browse Catalog icon. A list of predened reports for the selected area, such as Workforce
Management, appears in the work area. For example, you can run the Job Details report to list active jobs and the
Location Details report to list active locations.
You can also design your own reports using Oracle BI Publisher. To open Oracle BI Publisher, select Create > Report in
the Contents pane of the Reports and Analytics work area.
Using HCM Extracts

You can use HCM Extracts to extract data from Oracle HCM Cloud and deliver it in various formats. These formats
include CSV, XML, Microsoft Excel, HTML, RTF, and PDF.
Disable Postload Processing

When you upload a large number of smaller les each day, disable the automatic initiation of the postload processing.
This avoids queuing up too many processes for the scheduler. Schedule these processes at the end of the day or as
required.
To disable the postload processing, include the SET instruction at the top of each .dat le you want to disable the
postload processing for. Change the default value from Y to N:
Alternatively, go to Congure HCM Data Loader Parameters and change the Override value to No for the parameter
Initiate Business Object Postload Processing. You need to be aware that this step will disable the automated postload
processing for all business objects.
403
404
Integrating with HCM Purging Person Data from Test Environments
30 Purging Person Data from Test

Environments
Enable the Purge Person Data in Test Environments

Process
During implementation and testing, you may want to load, test, purge, and reload HCM data. To purge person data
from test environments, use the Purge Person Data in Test Environments process. This topic explains how to enable
the process and identies the data that it purges.
Enabling the Purge Process for Person Data

To use the Purge Person Data in Test Environments process, you must raise a service request (SR). In response,
Oracle Support supplies a key to enable the process. When you have the key, which is specic to your environment,
follow these steps:
1. In the Setup and Maintenance work area, go to the following for your oering:
◦ Functional Area: HCM Data Loader
◦ Task: Congure HCM Data Loader
2. On the Congure HCM Data Loader page, enter the key from Oracle Support in the Value eld for the Purge
Person Enabled Key parameter.
You can now run the Purge Person Data in Test Environments process.
Note: You can't run the Purge Person Data in Test Environments process in production environments.
Purging Person Data

The Purge Person Data in Test Environments process purges person records, including passports, citizenship records,
licenses, emails, addresses, national identiers, and extra information type data. It also purges dependent data of the
following types:
• Absences
• Assignments, including extra information type data
• Benets
• Calculation cards
• Compensation
• Contacts and contact relationships
• Documents and aachments
• Element entries
• Goals
405
• Payroll relationships
• Performance records
• Roles and user details
• Talent proles
• Work relationships
Deletion requests are generated for user accounts in the test environment. To process these requests, you must run the
Send Pending LDAP Requests process when Purge Person Data in Test Environments completes.
Exclusions from the Purge Process

The Purge Person Data in Test Environments process doesn't purge data of the following types:
• Predened person data.
• Person data that was loaded using HCM File-Based Loader.
• Oracle Trading Community Architecture (TCA) data.
The process inactivates dependent TCA records in the TCA tables but doesn't purge them.
If processed payroll actions are associated with a worker, then the worker isn't purged. You must roll back relevant
payroll processes before you can purge such workers.
Disable Postload Processing

When you upload a large number of smaller les each day, disable the automatic initiation of the postload processing.
This avoids queuing up too many processes for the scheduler. Schedule these processes at the end of the day or as
required.
To disable the postload processing, include the SET instruction at the top of each .dat le you want to disable the
postload processing for. Change the default value from Y to N:
Alternatively, go to Congure HCM Data Loader Parameters and change the Override value to No for the parameter
Initiate Business Object Postload Processing. You need to be aware that this step will disable the automated postload
processing for all business objects.
Purge Person Data from Test Environments

This topic describes how to run the Purge Person Data in Test Environments process. The process must be enabled
for use in your test environment. This topic also describes how to run Send Pending LDAP Requests to process user-
deletion requests generated by the Purge Person Data in Test Environments process.
Run the Purge Person Data in Test Environments Process

You must have the Purge Person Data in Test Environments function security privilege to run this process. The
predened Human Capital Management Integration Specialist job role has this privilege.
406
Sign in and follow these steps:
1. Select Navigator > Tools > Scheduled Processes.

2. In the Scheduled Processes work area, click Schedule New Process.
3. In the Schedule New Process dialog box, search for and select the Purge Person Data in Test Environments
process.
4. In the Process Details dialog box, set one of the following parameters to identify the person data to purge.
Person ID Provide one or more person IDs. Separate multiple IDs with commas, for example,
100010034148157, 100010034148169, 100010034148181, 100010034148192.

Person Number Provide one or more person numbers. Separate multiple numbers with commas. You can
use the wildcard character to supply partial values, for example, PER%, Test%,%abc%.

Person Query Enter a SQL query to return the person IDs of all persons whose data you want to purge.

To return the person IDs of all person records where the last name starts with the characters John, you could
use the following SQL query:
SELECT papf.person_id FROM per_all_people_f papf, per_person_names_f ppnf WHERE

ppnf.last_name like 'John%' and ppnf.person_id = papf.person_id
To return all person IDs in the test environment, use the following SQL query:
SELECT person_id FROM per_all_people_f
5. Set the Save parameter, as follows.
Save Value Description
N Lists the persons whose data would be purged by the process. No data is purged.

Y Purges the person data.

6. Click Submit.
Tip: The time this process takes depends on the amount of data to be purged. Don't cancel the process, as its
nal stages include clean-up operations. If you cancel the process, then the clean-up operations resume when
you next run the process.
407
Run the Send Pending LDAP Requests Process

Purge Person Data in Test Environments generates requests to delete user accounts from your LDAP directory. To
process these requests, run the Send Pending LDAP Requests process. If this process isn't scheduled to run in the test
environment, then follow these steps when Purge Person Data in Test Environments completes:
1. In the Scheduled Processes work area, click Schedule New Process.
2. In the Schedule New Process dialog box, search for and select the Send Pending LDAP Requests process.
3. In the Process Details dialog box:
a. Set User Type to All.
b. Leave Batch Size set to A, which means that the processing batch size is calculated automatically.
4. Click Submit.
Tables Purged by the Purge Person Data in Test

Environments Process
This topic lists the tables that are purged when you run the Purge Person Data in Test Environments process.
Product Table
Absence Management • ANC_PER_ABS_CERTS

• ANC_PER_ABS_ENTRIES
• ANC_PER_ABS_ENTRY_DTLS
• ANC_PER_ABS_MATERNITY
• ANC_PER_ABS_PLAN_ENTRIES
• ANC_PER_ABS_PLN_SUMM_ENT
• ANC_PER_ABS_TYP_LNKG
• ANC_PER_ABS_TYPE_ENTRIES
• ANC_PER_ACCRUAL_ENTRIES
• ANC_PER_ACRL_ENTRY_DTLS
• ANC_PER_EVENTS
• ANC_PER_PLAN_ENROLLMENT
Benets • BEN_BATCH_ACTN_ITEM_INFO
• BEN_BATCH_BNFT_CERT_INFO
• BEN_BATCH_COMMU_INFO
• BEN_BATCH_DPNT_INFO
• BEN_BATCH_ELCTBL_CHC_INFO
• BEN_BATCH_ELIG_INFO
• BEN_BATCH_LER_INFO
• BEN_BATCH_RATE_INFO
• BEN_BENEFIT_ACTIONS
• BEN_BENEFIT_RELATIONS_F
• BEN_CVRD_DPNT_CTFN_PRVDD
• BEN_ELCTBL_CHC_CTFN
• BEN_ELIG_CVRD_DPNT
• BEN_ELIG_DPNT
408
Product Table
• BEN_ELIG_FLX_CRDT_POOL_CHC
• BEN_ELIG_PER_ELCTBL_CHC
• BEN_ELIG_PER_F
• BEN_ELIG_PER_OPT_F
• BEN_ELIG_RSLT_F
• BEN_ENRT_BNFT
• BEN_ENRT_RT
• BEN_EXTRACT_DETAILS_ARCH
• BEN_EXTRACT_REQ_DETAILS
• BEN_FLEX_CRDT_LDGR
• BEN_PER_BENEFIT_GROUP_F
• BEN_PER_BNF_ORG
• BEN_PER_BNFTS_BAL_F
• BEN_PER_IN_LER
• BEN_PER_LE_HABITS_COV_F
• BEN_PERSON_ACTIONS
• BEN_PIL_ELCTBL_CHC_POPL
• BEN_PL_BNF
• BEN_PL_BNF_CTFN_PRVDD
• BEN_PRTT_ENRT_ACTN
• BEN_PRTT_ENRT_CTFN_PRVDD
• BEN_PRTT_ENRT_RSLT
• BEN_PRTT_LEG_DISCMR_ACTN
• BEN_PRTT_RT_VAL
• BEN_PTNL_LER_FOR_PER
• BEN_REL_ASSIGNMENTS_F
• BEN_REPORTING
Compensation Management • CMP_BUDGET_AUDIT

• CMP_BUDGET_USAGES
• CMP_CWB_ALERTS
• CMP_CWB_APPROVAL_HISTORY
• CMP_CWB_AUDIT
• CMP_CWB_FEEDBACK
• CMP_CWB_HRCHY
• CMP_CWB_INTCPT_APPR_DTLS
• CMP_CWB_MODEL_B
• CMP_CWB_MODEL_DTL
• CMP_CWB_MODEL_TL
• CMP_CWB_PERF_RATINGS
• CMP_CWB_PERSON_DEFAULTS
• CMP_CWB_PERSON_ELEMENTS
• CMP_CWB_PERSON_INFO
• CMP_CWB_PERSON_RATES
• CMP_CWB_POST_LOG
• CMP_CWB_POST_PERSON
• CMP_CWB_PROMOTIONS
• CMP_CWB_RANKS
• CMP_CWB_SUMMARY
• CMP_CWB_SWITCH_MANAGERS
• CMP_DYNAMIC_FILTER
• CMP_INTERCEPT_APPROVERS
409
Product Table
• CMP_PERSON_BUDGETS
• CMP_PROCESS_DATA
• CMP_PROCESS_RUN_INFO
• CMP_SALARY
• CMP_SALARY_COMPONENTS
• CMP_SALARY_EXPORT
• CMP_STOCK_DETAILS
• CMP_TCS_PER_ITEM_VALUE
• CMP_TCS_PER_PERD
• CMP_TCS_PER_PERD_STMT
• CMP_TCS_PER_PERD_STMT_CAT
• CMP_TCS_PER_ROW_VALUES
• CMP_TCS_REPORT_DETAILS
• CMP_VC_PER_ELIG_PLANS
Oracle Middleware Extensions for • FND_ATTACHED_DOCUMENTS

Applications • FND_DOCUMENTS
• FND_DOCUMENTS_TL
• FND_SESSION_USERS
Workforce Modeling • HMO_MODEL_PLAN_DETAILS

• HMO_MODEL_PLANS_B
• HMO_MODEL_PLANS_TL
Performance Management • HRA_EVAL_ITEMS

• HRA_EVAL_PARTICIPANTS
• HRA_EVAL_RATINGS
• HRA_EVAL_ROLE_ACTIONS
• HRA_EVAL_ROLES
• HRA_EVAL_SECTIONS
• HRA_EVAL_STEPS
• HRA_EVALUATIONS
Goal Management • HRG_GOAL_ACCESS

• HRG_GOAL_ACTIONS
• HRG_GOAL_ALIGNMENTS
• HRG_GOAL_TARGET_OUTCOMES
• HRG_GOALS
Succession Management • HRM_PLANS

• HRM_PLAN_CANDIDATES
• HRM_PLAN_OWNERS
Talent Review • HRR_DASHBOARDS

• HRR_MEETINGS
• HRR_MEETING_FACILITATORS
• HRR_MEETING_PARTICIPANTS
• HRR_MEETING_REVIEWEES
Questionnaire • HRQ_QSTN_RESPONSES
• HRQ_QSTNR_PARTICIPANTS
410
Product Table
• HRQ_QSTNR_RESPONSES
Prole Management • HRT_NOTES

• HRT_POOL_MEMBERS
• HRT_POOL_OWNERS
• HRT_PROFILE_INTERESTS
• HRT_PROFILE_ITEMS
• HRT_PROFILE_KEYWORDS
• HRT_PROFILE_MATCH_CRIT
• HRT_PROFILE_RELATIONS
• HRT_PROFILES_B
• HRT_PROFILES_TL
Workforce Management • HWM_TM_REC

• HWM_TM_REC_GRP
• HWM_TM_REC_GRP_SUM
• HWM_TM_REC_GRP_USAGES
• HWM_TM_REP_ATRB_USAGES
Workforce Predictions • HWP_ARCH_DATA_MINING_REASONS

• HWP_ARCH_DATA_MINING_RESULTS
• HWP_DATA_INPUT_VALUES
• HWP_DATA_MINING_REASONS
• HWP_DATA_MINING_RESULTS
• HWP_WHATIF_PRED_DETAILS
Global Payroll • PAY_ASSIGNED_PAYROLL

• PAY_ASSIGNED_PAYROLLS_DN
• PAY_ASSIGNED_PAYROLLS_DN_
• PAY_ASSIGNED_PAYROLLS_F
• PAY_ASSIGNED_PAYROLLS_F_
• PAY_DATES
• PAY_DIR_CARD_COMPONENTS_F
• PAY_DIR_CARD_COMPONENTS_F_
• PAY_DIR_CARDS_F
• PAY_DIR_CARDS_F_
• PAY_DIR_COMP_DETAILS_F
• PAY_DIR_COMP_DETAILS_F_
• PAY_DIR_REP_CARD_USAGES_F
• PAY_DIR_REP_CARD_USAGES_F_
• PAY_DIR_REP_CARDS_F
• PAY_DIR_REP_CARDS_F_
• PAY_ELEMENT_ENTRIES_F
• PAY_ELEMENT_ENTRIES_F_
• PAY_ELEMENT_ENTRY_VALUES_F
• PAY_ELEMENT_ENTRY_VALUES_F_
• PAY_ENTRY_PCT_DIST
• PAY_ENTRY_PROC_DETAILS
• PAY_ENTRY_USAGES
• PAY_PAY_RELATIONSHIPS_DN
• PAY_PAY_RELATIONSHIPS_F
411
Product Table
• PAY_PERSON_PAY_METHODS_F_
• PAY_RANGE_ITEMS_F
• PAY_RANGE_ITEMS_F_
• PAY_REL_GROUPS_DN
• PAY_REL_GROUPS_F
• PAY_RETRO_ENTRIES
• PAY_VALUE_DEFINITIONS_F
• PAY_VALUE_DEFINITIONS_F_
Global Human Resources • HR_DOCUMENT_DELIVERY_PREFS

• HR_DOCUMENTS_OF_RECORD
• PER_ABSENCE_CASES
• PER_ACTION_OCCURRENCES
• PER_ADDRESSES_F
• PER_ALL_ASSIGNMENTS_M
• PER_ALL_PEOPLE_F
• PER_ALLOCATED_CHECKLISTS
• PER_ALLOCATED_TASKS
• PER_ASG_RESPONSIBILITIES
• PER_ASSIGN_GRADE_STEPS_F
• PER_ASSIGN_WORK_MEASURES_F
• PER_ASSIGNMENT_EXTRA_INFO_M
• PER_ASSIGNMENT_SUPERVISORS_F
• PER_CITIZENSHIPS
• PER_CONTACT_EXTRA_INFO_F
• PER_CONTACT_RELSHIPS_F
• PER_CONTRACTS_F
• PER_DELEGATED_ROLES
• PER_DISABILITIES_F
• PER_DRIVERS_LICENSE_TYPES
• PER_DRIVERS_LICENSES
• PER_EMAIL_ADDRESSES
• PER_ETHNICITIES
• PER_IMAGES
• PER_KEYWORDS
• PER_LDAP_REQUESTS
• PER_LDAP_ROLE_MEMBERSHIPS
• PER_LDAP_USERS
• PER_MANAGER_HRCHY_DN
• PER_NATIONAL_IDENTIFIERS
• PER_PASSPORTS
• PER_PEOPLE_EXTRA_INFO_F
• PER_PEOPLE_LEGISLATIVE_F
• PER_PERIODS_OF_SERVICE
• PER_PERSON_ADDR_USAGES_F
• PER_PERSON_DLVRY_METHODS
• PER_PERSON_NAMES_F
• PER_PERSON_TYPE_USAGES_M
• PER_PERSONS
• PER_PHONES
• PER_PORTRAIT_CARD_CONFIG
• PER_PORTRAIT_PREFERENCES
412
Product Table
• PER_RELIGIONS
• PER_SCHEDULE_ASSIGNMENTS
• PER_SHARE_INFORMATION
• PER_USER_HISTORY
• PER_USER_ROLES
• PER_USERS
• PER_VISAS_PERMITS_F
413
414
Integrating with HCM HCM Extracts and Diagnostics for HCM Data Loader and
31 HCM Extracts and Diagnostics for HCM

Data Loader and HCM Spreadsheet Data
Loader
HCM Data Loader Extracts

HCM Extracts provides four extracts for HCM Data Loader, as shown in this table.
Extract Name Description
HCM Data Loader Data Set Summary Provides status values and record counts for both a specied data set and each business object
in the data set. It reports all error messages and identies all records aected by each error.

Compensation Changes Extract For a specied compensation run, extracts assignment, salary, and bonus changes made by
the run. This extract is most useful if you're implementing a coexistence scenario.

Integration Object User Key Refresh Retrieves latest user key values. Run this extract before running the Integration Object User
Key Map Extract.

Integration Object User Key Map Extracts GUIDs, source keys, surrogate IDs, and user keys for a specied business object
Extract hierarchy.

The output from all extracts is in XML format by default. You can provide a BI Publisher layout to reformat the output.
You can also dene options to automate delivery of the output.
Before users can run any of these extracts, you:
1. Copy the predened extract, specify a delivery option, and compile the formulas for your copy of the extract.
2. Congure your copy of the extract.
Once the extract is congured, users can run it and view the output.
Seing Up HCM Data Loader Extracts

Manage an HCM Data Loader Extract Denition
HCM Extracts provides four predened extracts for HCM Data Loader:
• HCM Data Loader Data Set Summary
• Compensation Changes Extract
415
• Integration Object User Key Refresh
• Integration Object User Key Map Extract
This topic explains how to copy a predened extract, specify a delivery option, and compile the formulas for the copied
extract. You can follow these instructions for any of the HCM Data Loader extracts.
Copy the Extract

Follow these steps to copy an HCM Data Loader extract:
1. On the Tasks panel tab of the Data Exchange work area, select Manage Extract Denitions.
2. On the Manage HCM Extract Denitions page, search for the extract.
3. Select the extract in the search results and click Copy.
4. In the Copy Extract Denition dialog box, enter a name for your copy of the extract and click OK.
A conrmation message appears when the copy is complete.
Specify a Delivery Option for the Copied Extract

Follow these steps to specify a delivery option:
1. On the Manage HCM Extract Denitions page, search for your copy of the extract.
2. Click the extract name in the search results to display the extract denition on the Manage HCM Extract
Denitions page.
3. Click Deliver.
4. In the Extract Delivery Options section, click Add.
5. Specify a delivery option. To keep the default XML output, set the Output Type to Data.
6. For the XML delivery option, specify Delivery Option Name, Output Name, and Delivery Type values.
Tip: The values that you must specify vary by output type.
7. Click Save.
For more information, see Oracle Fusion HCM Extracts: Delivery Options (document ID 1573099.1) on My Oracle Support
at hps://support.oracle.com.
Compile the Formulas for the Copied Extract

Follow these steps to compile the formulas:
1. On the Manage HCM Extract Denitions page, click Validate.

2. In the Extract Execution Tree section, click Compile All Formula to compile the formulas.
3. Refresh the table periodically until all formulas are successfully compiled. A check mark means success.
4. Click Submit.
Once these steps are complete, perform the Rene HCM Extracts task in the Data Exchange work area to congure the
copied HCM Data Loader extract.
Related Topics
• Oracle Fusion HCM Extracts: Delivery Options
416
Congure a Copied HCM Data Loader Extract

This topic explains how to congure an extract after copying it, specifying a delivery option, and compiling its formulas.
Follow these steps:
1. On the Tasks panel tab of the Data Exchange work area, select Rene Extracts to open the Manage Payroll
Flow Paerns page.
2. On the Manage Payroll Flow Paerns page, enter the name of your copy of the extract in the Flow Paern eld
and click Search.
3. In the search results, select your extract and click Edit.
4. Click the Parameters tab to review the parameter denitions.
5. Edit the Display, Sequence, Parameter Basis, and Basis Value for each parameter. You can also edit the
parameter names, if required.
6. Save your changes.
Users can now run the extract.
HCM Data Loader Data Set Summary Extract Parameters

This topic describes how to congure the parameters of the HCM Data Loader Data Set Summary extract.
To congure the parameters, you perform the Rene Extracts task in the Data Exchange work area.
Conguring the Parameters

This table shows the parameters that you must edit and the required values for the HCM Data Loader Data Set
Summary extract. You can ignore parameters not shown here.
Parameter Display Sequence Parameter Basis Basis Value
Eective Date No 3 Context Binding System Date

Start Date No 9 Not applicable Not applicable

Content ID Yes 12 Not applicable Not applicable

Data Set Name Yes 13 Not applicable Not applicable

Process ID Yes 11 Not applicable Not applicable
417

Show Messages No 14 Constant Bind Y

Show Stack Trace No 15 Constant Bind N

Compensation Changes Extract Parameters

This topic describes how to congure the parameters of the Compensation Changes Extract for HCM Data Loader.

This table shows the parameters that you must edit and the required values for the Compensation Changes Extract. You
can ignore parameters not shown here.
Eective Date No 3 Context Binding System Date


Extract Target No 15 Constant Bind HDL

Period Name Yes 12 Not applicable Not applicable

Plan Yes 11 Not applicable Not applicable

Process Id Yes 13 Not applicable Not applicable

Run Id Yes 14 Not applicable Not applicable

418
Integration Object User Key Refresh and Integration Object User

Key Map Extract Parameters
This topic describes how to congure the parameters of these HCM Data Loader extracts:


This table shows the parameters that you must edit and the required values for the Integration Object User Key Refresh
extract.
Eective Date Mandatory 3 Context Binding System Date


Process Conguration Yes 17 Not applicable Not applicable

Group

Business Object Yes 76 Not applicable Not applicable

Component Yes 81 Not applicable Not applicable

Discriminator

Include Child Yes 91 Not applicable Not applicable

Components

Note: You’re recommended to change the name of the Business Object parameter to Business Object
Discriminator.
This table shows the parameters that you must edit and the required values for the Integration Object User Key Map
Extract.
Eective Date Mandatory 3 Context Binding System Date

419

Process Conguration Yes 17 Not applicable Not applicable

Group

Business Object Yes 22 Not applicable Not applicable

Component Yes 23 Not applicable Not applicable

Discriminator

Include Child Yes 24 Not applicable Not applicable

Components

Source System Owner Yes 25 Not applicable Not applicable

Baseline Only No 81 Not applicable Not applicable

Changes Only No 91 Not applicable Not applicable

Delete Archive No 101 Not applicable Not applicable

Note: You're recommended to change the name of the Business Object parameter to Business Object
Discriminator.
Running HCM Data Loader Extracts

Submit an HCM Data Loader Extract
This topic explains how to submit a congured HCM Data Loader extract.
420
Select the Extract

Follow these steps:
1. On the Tasks panel tab of the Data Exchange work area, select Submit Extracts to open the Submit a Process
or Report page.
2. Using the query by example elds, nd your extract and click Next.
The Enter Parameters page opens.

3. In the Payroll Flow eld, enter a ow name for this run of the extract.
4. Enter the parameter values for your extract.
Enter Parameters for the HCM Data Loader Data Set Summary Extract
This table shows the parameters for the HCM Data Loader Data Set Summary extract. Enter any one of the Content ID,
Process ID, and Data Set Name parameters. You can nd all of these values for a specic data set on the Import and
Load Data page.
Content ID The content ID associated with the data set. This ID was assigned when you uploaded your
source le to the Oracle WebCenter Content server.

Data Set Name The data set name, which is also your source le name.

Process Conguration Group Leave blank.

Process ID The process ID of the process that created the data set. This ID was assigned when you
submied your source le for processing by HCM Data Loader.

Enter Parameters for the Compensation Changes Extract

This table shows the parameters of the Compensation Changes Extract. To identify the compensation run to report on,
use one of the following parameters or pairs of parameters:
• Plan and Period Name
• Process Id
• Run Id
Plan The compensation plan name

Period Name The period name for the compensation run

Process Id The process ID for the compensation run
421

Run Id The run ID for the compensation run

Enter Parameters for the Integration Object User Key Refresh Extract
This table shows the parameters of the Integration Object User Key Refresh Extract.
Business Object
The le discriminator of the business object for which you want to refresh keys. For example,
for some or all components of the Worker object, set this parameter to Worker. You can nd
the le discriminator values on the Business Object Details page for the object in the Data
Exchange work area.
Component Discriminator
The le discriminator of the business object component. For example, to refresh keys for the
Work Relationship component of the Worker object, set this parameter to WorkRelationship.
You can nd the le discriminator values on the Business Object Details page for the object in
the Data Exchange work area.
Include Child Components

Set to Yes to include the child components of the business object or component in the refresh.

Enter Parameters for the Integration Object User Key Map Extract
This table shows the parameters of the Integration Object User Key Map Extract.
Business Object
The le discriminator of the business object for which you want to extract keys. For example,
for some or all components of the Worker object, set this parameter to Worker. You can nd
the le discriminator values on the Business Object Details page for the object in the Data
Exchange work area.
Component Discriminator
The le discriminator of the business object component. For example, to extract keys for the
Work Relationship component of the Worker object, set this parameter to WorkRelationship.
You can nd the le discriminator values on the Business Object Details page for the object in
the Data Exchange work area.
Include Child Components

Set to Yes to include the child components of the business object or component in the extract.
422
Tip: If you're extracting a large number of records, then you're

recommended to set this parameter to No and extract each component
separately.


Source System Owner If required, select a value to extract the keys for a specied source system owner. The extract
includes all types of keys, but only for those object instances with this source system owner.

Submit the Extract

Follow these steps:
1. Click Next until you reach the Review page.
2. Click Submit.
A conrmation message appears when your extract is submied successfully.
3. Close the Conrmation dialog box.
You can now view the extract output.
View the Results of an HCM Data Loader Extract

This topic explains how to view the output from an HCM Data Loader extract. Follow these steps:
1. On the Tasks panel tab of the Data Exchange work area, select View Extract Results to open the View Extract
Run Details page.
2. Search for the extract.
3. In the search results, click the name of the extract to open the View Extract Results tab.
4. In the Extract Runs section, use the query by example elds to nd the extract run for which you want the
results.
5. In the Details section, click the Extract Delivery Options tab. This tab appears only if a delivery option was
specied when the extract was congured.
6. Click Download to download the extract results.
Diagnostic Tests for HCM Data Loader
423
HCM Data Loader Error Analysis Report

The HCM Data Loader Error Analysis Report is a diagnostic test. It provides technical information that can help to
resolve data-loading errors. Run this diagnostic test when error messages don't supply enough information for you to
identify a solution. You can send the test output to Oracle Support, if necessary.
To run the HCM Data Loader Error Analysis Report test, select Seings and Actions > Run Diagnostic Tests.
Diagnostic Test Parameters

Content ID
A unique reference to a single data set. You can nd the content ID in the Content ID column of the Search Results
table on the Import and Load Data page. You must specify either the content ID or the process ID to identify the data
set.
Process ID
A unique reference to a single data set. You can nd the process ID in the Process ID column of the Search Results table
on the Import and Load Data page. You must specify either the content ID or the process ID to identify the data set.
Business Object Name
The name of a business object in the data set, such as Worker or Job. You can nd the business object name in the
Business Object column of the Details table on the Import and Load Data page. This parameter is optional, but you're
recommended to supply it if your data set contains multiple business objects.
Detailed Mode
Set this parameter to Y to include the details of any reported errors in the output, including message stack trace for the
records in error.
Diagnostic Test Results

The diagnostic test output is in user-readable HTML format. It provides:
• Status information
• Details of every process submied to process your data set
• All errors raised for each business object in the data set
• Message stack trace and nonsensitive aribute values for the records in error, if you set the Detailed Mode
parameter to Y
No sensitive data appears in the test results.
Run the HCM Data Loader Error Analysis Report

The HCM Data Loader Error Analysis Report is a diagnostic test that provides technical information about data loads to
help you resolve errors. To submit this diagnostic test, you must have access to the Diagnostic Dashboard.
424
Follow these steps:
1. Select Seings and Actions > Run Diagnostic Tests to open the Diagnostic Dashboard.
2. In the Search for Tests section of the Diagnostic Dashboard, enter HCM Data Loader Error Analysis Report in
the Test Name eld and click Search.
3. In the search results, select the check box next to the test name and click Add to Run. The test appears in the
Choose Tests to Run and Supply Inputs section of the page.
4. To review the parameters, click the Click to Supply or Edit Input Parameters icon in the Status column.
5. In the Input Parameters dialog box, select parameters to include in this test run and supply values for the
selected parameters.
Note: Use the parameters to restrict the output from the test to those errors that need
investigation. For example, don't run the test for an entire data set if the errors relate to a
single business object.
6. Click OK.
7. If required, enter a name for the test run in the Run Name eld. The name can help you to locate your results
easily. If you leave the eld blank, then a name is generated.
8. Click Run to run the test and click OK to close the conrmation dialog box.
9. In the Diagnostic Test Run Status section, click the Display Latest Test Run Status Information icon to see the
results of this test.
10. Expand the test hierarchy for your run to see the results. Click the Report icon to open the report.
You can save the output and aach it to a service request if required.
Diagnostic Tests for HCM Spreadsheet Data Loader

HCM Spreadsheet Data Loader Diagnostic Report
The HCM Spreadsheet Data Loader Diagnostic Report provides a detailed analysis of a spreadsheet template or
associated data sets to help you resolve template errors. Run this report when error messages don't supply enough
information for you to resolve any errors. You can send the report output to Oracle Support, if necessary.
To run the HCM Spreadsheet Data Loader Diagnostic Report, select Seings and Actions > Run Diagnostic Tests.
Diagnostic Test Parameters

Data Set Name
To report on a specic data set, enter its name. You must provide a value for either the Data Set Name or the Template
Name parameter.
Template Name
To report on a spreadsheet template, enter its name. You must provide a value for either the Data Set Name or the
Template Name parameter.
Number of Data Sets to Include
425
Enter the number of data sets most recently created in spreadsheets generated from the spreadsheet template to
include in the report. The default value is 5. This parameter applies only when you also specify a value for the Template
Name parameter.
Include Error Details
Set this parameter to Y to provide details, including stack trace, of the most frequent import and load errors in the
report output.
Diagnostic Report Contents

The report is in user-readable HTML format. It includes the following sections:
Report Section Section Content
Parameters Lists all report parameters with the values that you supplied

Template Details The values held for the template denition

Template Business Objects Details of the business objects that the template supports

Template Aribute Details Details of the aributes selected in the template, regardless of whether they're visible in
generated spreadsheets

Map Table Details of the template map

Aribute Map Table The business object map information

Flexeld Contexts Flexeld contexts in the spreadsheet template

Flexeld Aributes Flexeld aributes in the spreadsheet template

Data set Name: <data set name> One section for each data set in the report

The Data Set Name: <data set name> section includes the following information for each data set in the report:
• A summary of all errors raised for the data set

• The status and record counts
• Details of the Import and Load process that created the data set
• All parameters to the Import and Load process and its child processes
• Detailed information about each business object in the spreadsheet, including:
◦ Object status
426
◦ Details of the import and load processes
◦ SET commands
◦ The 25 most frequent import errors
◦ The 25 most frequent load errors
◦ Object and component counts
Run the HCM Spreadsheet Data Loader Diagnostic Report

The HCM Spreadsheet Data Loader Diagnostic Report is a diagnostic test that enables you to analyze problems in
custom spreadsheet templates. To run this report, you must have access to the Diagnostic Dashboard.
Follow these steps:
1. Select Seings and Actions > Run Diagnostic Tests to open the Diagnostic Dashboard.
2. In the Search for Tests section of the Diagnostic Dashboard, enter HCM Spreadsheet Data Loader Diagnostic
Report in the Test Name eld and click Search.
3. In the search results, select the check box next to the test name and click Add to Run. The test appears in the
Choose Tests to Run and Supply Inputs section of the page.
4. To review the parameters, click the Click to Supply or Edit Input Parameters icon in the Status column.
5. In the Input Parameters dialog box, select parameters to include in this test run and supply values for the
selected parameters.
Note: Use the parameters to restrict the output from the test to those errors that need
investigation. For example, don't run the test for multiple data sets if the errors relate to a
single data set.
6. Click OK.
7. If required, enter a name for the test run in the Run Name eld. The name can help you to locate your results
easily. If you leave the eld blank, then a name is generated.
8. Click Run to run the test and click OK to close the conrmation dialog box.
9. In the Diagnostic Test Run Status section, click the Display Latest Test Run Status Information icon to see the
results of this test.
10. Expand the test hierarchy for your run to see the results. Click the Report icon to open the report.
You can save the output and aach it to a service request if required.
427
428
Integrating with HCM Best Practices for HCM Data Loader and HCM Spreadsheet
Data Loader
32Best Practices for HCM Data Loader and

HCM Data Loader Best Practices

This topic highlights some best practices for data loading. Follow these recommendations to ensure successful creation
and maintenance of data using HCM Data Loader.
Source Keys
The source key is the recommended key type to use for all implementations. If you supply a source key when you create
your data, then you can also update or simply reference that data using source keys.
You can't update some objects if you identify them using only user keys. For example, you can't update most
components of the Worker object if you supply only a user key. The aribute that you want to change is often the
aribute that's used to identify the record. For example, in the Person Address component, the AddressLine1 aribute
is used both to identify the address to update and to supply the new value. Therefore, you're recommended to use
source keys whenever possible.
Data Migration
When creating business objects using HCM Data Loader:
• Deliver one object type in each .zip le. For example, create one .zip le for jobs, one for grades, one for
workers, and so on. To avoid data-reference errors, you must ensure that you load .zip les in the correct order
and x any errors before loading the next le.
• Purge the stage table data regularly for data sets that you no longer need, especially if you're loading large
volumes of data.
• Understand and follow the rules for creating date-eective data.
Tip: HCM Data Loader can load very large volumes of data from a single le. However, do consider the
practical challenges, such as error management and the length of the transition period, associated with large
data loads. Best practice is to split large loads into logical groupings so that you can extract, transform, and
load the data more easily. For example, when loading workers you could load ex-employees separately from
current, active employees. If this grouping still leaves you with very large data loads, then you could dene
subgroups of records based on other signicant criteria.
Updating Objects
When updating business objects using HCM Data Loader:
• Understand and follow the rules for maintaining date-eective data. In particular, always include the SET
PURGE_FUTURE_CHANGES N instruction in the .dat le to ensure that any existing future-dated changes are retained.
• Supply all business-object les in the same .zip le. HCM Data Loader processes them in the correct order.
Referenced data is loaded before the data that references it.
429
Data Loader
Note: If a dependency exists between business-object les, then include the surrogate ID aribute
that references the dependent object in the METADATA line. For example, you may be loading both
Worker.dat and Job.dat les together. If the Worker object includes references to a new job, then
you must include the JobId aribute in the METADATA line of the Worker.dat le. This rule applies
even if you're also supplying user keys. You don't have to supply a value for the JobId aribute.
Having it in the METADATA line enables HCM Data Loader to identify the dependency.
• Supply any changed aribute values and a unique reference to the record that you're updating. Also, if a
dependency exists between the objects in the le, then include the surrogate ID aribute in the METADATA
line. Otherwise, don't include unchanged, optional aributes in the METADATA line of your .dat le. HCM
Data Loader validates every aribute name in the METADATA line. Including aributes for which you aren't
providing data has a negative eect on performance.
• Never include both DELETE and MERGE instructions for the same record in the same le. HCM Data Loader
doesn't guarantee the order in which the le lines are processed.
Related Topics
• Source Keys
• Overview of Loading Date-Eective Objects
Overview of Maintaining the Stage Tables

When you load large volumes of data into Oracle HCM Cloud, the stage tables can grow rapidly. You're recommended
to create a schedule to delete processed data sets that you no longer need in the stage tables. How often you delete
processed data sets from the stage tables depends on the volume and frequency of your data loads. During data
migration, consider deleting every large data set as its processing completes. This topic describes the role of stage
tables in data loading and explains how the deletion process maintains the stage tables automatically.
How Data Is Loaded to Oracle HCM Cloud

This gure shows how data is loaded to the application tables.
Data that you load using either HCM Data Loader or HCM Spreadsheet Data Loader is imported rst to stage tables,
where some validation occurs. HCM Spreadsheet Data Loader has its own stage tables, from where valid data is loaded
430
Data Loader
to the HCM Data Loader stage tables. Valid data is loaded from the HCM Data Loader stage tables to the application
tables.
HCM Spreadsheet
HCM Spreadsheet
Data Loader
Data Loader
Stage Tables
HCM Data Loader

HCM Data Loader Application Tables
Stage Tables
How Processed Data Sets Are Deleted from Stage Tables

You can delete processed data sets from both sets of stage tables.
• To delete data sets from the HCM Spreadsheet Data Loader stage tables, use the Delete Spreadsheet Stage
Table Data task. It runs the Delete HCM Spreadsheet Data Loader Stage Table Data process.
• To delete data sets from the HCM Data Loader stage tables, use the Delete Stage Table Data task. It runs the
Delete HCM Data Loader Stage Table Data process.
Perform both tasks in the Data Exchange work area.
You can delete:
• Individual data sets

• All data sets that currently match specied criteria
Tip: You can schedule a recurring deletion request. For example, you can schedule weekly deletion
of all data sets that haven't been updated in the last 7 days.
When you run the Import and Load Data process, it determines whether a schedule exists for the Delete HCM Data
Loader Stage Table Data process. If no schedule exists, then the process creates one to run Delete HCM Data Loader
Stage Table Data nightly.
When you delete processed data sets from the HCM Spreadsheet Data Loader stage tables, they're deleted
automatically from the HCM Data Loader stage tables. You can also delete spreadsheet data sets explicitly from the
HCM Data Loader stage tables. In this case, they remain available in the HCM Spreadsheet Data Loader stage tables.
You can't recover deleted data sets. So, don't delete data sets that you want to report on or that you want to extract
error information for.
431
Data Loader
How Delete HCM Data Loader Stage Table Data Works

The Delete HCM Data Loader Stage Table Data process deletes data sets from the HCM Data Loader stage tables.
Whenever it runs, the process:
1. Purges automatically from the stage tables any data set that hasn't been updated in the last 30 days. You can
specify a dierent number of days by seing the Days to Retain Data Sets Before Deleting conguration
parameter.
2. Reviews the number of data lines still in the stage tables. If the number exceeds a specied maximum value,
then data sets may be backed up automatically in archive stage tables. You specify:
◦ The maximum number of data lines on the Maximum Data Lines Before Archiving conguration
parameter.
◦ The number of days since a data set was last updated before it can be backed up. Specify this value on
the Days to Retain Data Sets Before Archiving conguration parameter.
Therefore, a data set is a candidate for automatic backup only if:
• The number of data lines in the stage tables exceeds the value specied on the Maximum Data Lines Before
Archiving parameter.
• The data set hasn't been updated in the number of days specied on the Days to Retain Data Sets Before
Archiving parameter.
The backup starts with the oldest data set and continues until the number of data lines in the stage tables drops below
the specied maximum.
Backed-Up Data Sets

These values remain in the stage tables when a data set is backed up:
• The statuses of the data set and business objects

• The record count
• Any error messages
All other data from the data set is moved to the archive stage tables. After a data set is backed up:
• You can't open error management pages for that data set.
• It doesn't appear in search results when you search for data sets to purge.
• You can access the data using a custom query only.
You can back up data sets manually by running the Delete HCM Data Loader Stage Table Data process with the
Action parameter set to Archive. You can't create a schedule when the action is Archive.
Related Topics
432
Data Loader
Example of the Automatic Deletion and Backup of Stage

Table Data
When you perform the Delete Stage Table Data task, it runs the Delete HCM Data Loader Stage Table Data
process. This process maintains the HCM Data Loader stage tables automatically. This example shows how automatic
maintenance of the stage tables works in conjunction with a user request to delete stage table data.
Maintaining the Stage Tables Automatically

The user performs the Delete Stage Table Data task on 9 May 2018 to purge any data sets:
• That weren't updated in the last 5 days
• Whose Import and Load statuses are both Success
Conguration parameters have their default values, as follows:
Conguration Parameter Value
Days to Retain Data Sets Before 5

Archiving

Days to Retain Data Sets Before 30

Deleting

The following table shows the status of recent import and load processes when the user performs Delete Stage Table
Data.
Data Set Imported Status Loaded Status Last Updated
1 Success Success 9 May 2018

2 Success Error 7 May 2018

3 Success Success 1 May 2018

4 Success Error 28 April 2018

5 Success Success 8 April 2018

6 Success Error 8 April 2018
433
Data Loader
Data Set Imported Status Loaded Status Last Updated

These data sets are either purged or backed up as follows:

1. Data sets 3 and 5 are purged by the user's process, based on the user's parameters.
2. Data set 6 is purged automatically because it hasn't been updated in the last 30 days.
3. Data set 4 is backed up automatically. The backup occurs because the number of data lines in the stage tables
still exceeds the congured Maximum Data Lines Before Archiving value.
Maintain the HCM Data Loader Stage Tables

This topic explains how to maintain the stage tables for HCM Data Loader by either deleting data sets immediately or
scheduling a recurring deletion request.
Delete a Single Data Set on the Import and Load Data Page
Follow these steps to delete a single data set from the stage tables on the Import and Load Data page:
1. On the Tasks panel tab of the Data Exchange work area, select Import and Load Data.
2. Search for and select the data set that you want to delete.
3. In the Search Results section, click the Delete icon for the selected data set.
4. In the Schedule Request dialog box, set the Delete Source File parameter to Yes to delete the source le from
the Oracle WebCenter Content server.
Note: You can delete the data from the stage tables without also deleting the source le. If
you loaded this data set with the Delete Source File parameter set to Yes, then the source
le has already been deleted. In this case, selecting Yes in the Schedule Request dialog box
has no eect.
5. Click Submit. The ID of the deletion process appears.
6. Click OK to close the Conrmation dialog box.
Delete Multiple Data Sets on the Delete Stage Table Data Page
You can delete one or more data sets immediately from the stage tables. Alternatively, you can schedule a recurring
deletion process. Follow these steps:
1. On the Tasks panel tab of the Data Exchange work area, select Delete Stage Table Data.
2. On the Delete Stage Table Data page, set the data set criteria to identify the data sets you that you want to
delete. This table describes the main criteria.
Field Description
Days Since Last Updated

Specify the number of days since the data set was last updated. For example, to identify
any data set not updated in the last week, set this eld to 7. The default value is 30, the
maximum value is 60, and the minimum value is 1.
434
Data Loader
Field Description
File Type
Select one of:
◦ Compressed DAT le
◦ Spreadsheet
Import Status
Select a status. For example, set to Success to list data sets that imported successfully.
Data Set Specify a particular data set.

Created By Enter the user name of the user who created the data set.

Load Status
Select a status. For example, set to Success to list data sets that loaded successfully.
Content ID Enter the Oracle WebCenter Content ID.

3. Click Show Current Results.

4. To delete all data sets in the Data Sets table immediately:
a. Click Schedule Deletion.
b. On the Parameters tab of the Schedule Request page, the data set criteria from the Delete Stage Table
Data page appear. You can't edit these values on the Schedule Request page.
Tip: To change the data set criteria, edit them on the Delete Stage Table Data page,
click Show Current Results, and click Schedule Deletion again. You must click Show
Current Results before clicking Schedule Deletion. Otherwise, the parameters aren't
updated on the Parameters tab of the Schedule Request page.
c. Source les for the data sets are deleted from the Oracle WebCenter Content server by default. To retain
the source les, set the Delete Source File parameter to No.
d. Click Submit. The ID of the deletion process appears.
5. To schedule a recurring deletion process for all data sets that match the specied criteria:
a. Click Schedule Deletion on the Delete Stage Table Data page.
b. On the Schedule Request page, click the Schedule tab.
c. Set Run to Using a schedule.
d. Specify the frequency of the deletion process. For example, you could schedule the process to run weekly
to delete any data set that hasn't been updated in the last 7 days.
e. Enter start and end dates.
Note: If the start date is tomorrow's date, then the process runs tomorrow and at the
specied interval (for example, weekly) until the end date. If the start date is today's
date, then the process runs for the rst time in one week's time, assuming a weekly
frequency.
435
Data Loader
f. Click Submit.
You can review the status of any deletion process by clicking Review Processes on the Delete Stage Table Data page.
On the Processes page:
• You can see the parameters for any process by clicking the contextual action icon next to the process name.
If the process was scheduled, then the Parameters dialog box also includes the schedule details. Scheduled
processes are identied by an icon in the Schedule column.
• Recurring deletion requests appear on the Processes page with a parent process in Wait status. The parent
process starts a child process for each scheduled deletion request. The ID of the parent process appears in the
Scheduling Process ID column.
• The log le for a process includes the request parameters and identies the data sets that were deleted.
Delete Spreadsheet Data Sets

On the Delete Stage Table Data page, your search results include spreadsheet data sets if you set File Type to
Spreadsheet. You can delete these data sets from the HCM Data Loader stage tables. But, the spreadsheet data sets
remain in the HCM Spreadsheet Data Loader stage tables. So, you can continue to edit and upload these spreadsheet
data sets after you have deleted them from the HCM Data Loader stage tables. Such a spreadsheet is reloaded from the
HCM Spreadsheet Data Loader stage tables when you next save or upload it. To delete spreadsheet data sets from both
sets of stage tables, use the Delete Spreadsheet Stage Table Data task.
Maintain the HCM Spreadsheet Data Loader Stage

Tables
This topic explains how to maintain the stage tables for HCM Spreadsheet Data Loader. You can either delete data sets
immediately or schedule a recurring deletion request.
Delete Data Sets from the HCM Spreadsheet Data Loader Stage Tables
Follow these steps:
1. On the Tasks panel tab of the Data Exchange work area, select Delete Spreadsheet Stage Table Data.
2. On the Delete Spreadsheet Stage Table Data page, set the data set criteria to identify the data sets that you
want to delete. This table describes the criteria:
Field Description
Days Since Last Updated

Specify the number of days since the data set was last updated. For example, to identify
any data set not updated in the last week, set this eld to 7. The default value is 30, the
maximum value is 60, and the minimum value is 1.
Template Select an HCM Spreadsheet Data Loader template to identify any data set created in
spreadsheets generated from the template.

Data Set Specify a particular data set. If multiple spreadsheets have been used to load the data set,
then they're all listed.
436
Data Loader
Field Description
Status
Select one of:
◦ Import completed with errors
◦ Load completed with errors
◦ Load successful
◦ Ready to process
Last Updated By Enter the user name of the user who last updated the data set.

Created By Enter the user name of the user who created the data set.

3. Click Show Current Results.

4. To delete a single data set, select the data set in the Data Sets table and click the Delete icon.
5. To delete all data sets in the Data Sets table immediately:
a. Click Schedule Deletion.

b. On the Parameters tab of the Schedule Request page, the data set criteria from the Delete Spreadsheet
Stage Table Data page appear. You can't edit these values on the Schedule Request page.
Tip: To change the data set criteria, edit them on the Delete Spreadsheet Stage Table
Data page, click Show Current Results, and click Schedule Deletion again. You must
click Show Current Results before clicking Schedule Deletion. Otherwise, the criteria
aren't updated on the Parameters tab of the Schedule Request page.
c. Click Submit.
6. To schedule a recurring deletion process for all data sets that match the specied criteria:
a. Click Schedule Deletion on the Delete Spreadsheet Stage Table Data page.
b. On the Schedule Request page, click the Schedule tab.
c. Set Run to Using a schedule.
d. Specify the frequency of the deletion process. For example, you could schedule the process to run weekly
to delete any data set that hasn't been updated in the last 7 days.
e. Enter start and end dates.
Note: If the start date is tomorrow's date, then the process runs tomorrow and at the
specied frequency (for example, weekly) until the end date. If the start date is today's
date, then the process runs for the rst time in one week's time, assuming a weekly
frequency.
f. Click Submit.
437
Data Loader
You can review the status of any deletion process by clicking Review Processes on the Delete Spreadsheet Stage Table
Data page. On the Processes page:
• You can see the parameters for any process by clicking the contextual action icon next to the process name.
If the process was scheduled, then the Parameters dialog box also includes the schedule details. Scheduled
processes are identied by an icon in the Schedule column.
• Recurring deletion requests appear on the Processes page with a parent process in Wait status. The parent
process starts a child process for each scheduled deletion request. The ID of the parent process appears in the
Scheduling Process ID column.
• The log le for a process includes the request parameters and identies the data sets that were deleted.
When you delete data sets from the HCM Spreadsheet Data Loader stage tables, they're also deleted from the HCM
Data Loader stage tables.
438
Integrating with HCM Time, Absence, and Pension Data for Payroll
33 Time, Absence, and Pension Data for

Payroll
Overview
You can automate the regular import of time card entries, absence entries, and pension enrollments. Use predened
ows where you specify the interface type and XML le containing the data to load, unless the application pushes
the data directly to payroll. For example, recording an absence in Oracle Fusion Absence Management automatically
transfers the data to payroll.
This topic covers these sections:
• Load data options

• Use an XML le to load data
Load Data Options

The application that you use to record time, absences, and pensions determines options for importing data to payroll.
This table lists the applications for transferring data to payroll.
Source Application Data Load Options
Time card • For Oracle Fusion Time and Labor, submit the Load Time Card Batches process.
• For a third-party time application, submit the Load Time Card Batches process and load
an XML le.
Absences • For Absence Management, use the Manage Absence Records task to record an absence
and transfer it directly to the person's absence calculation card.
When you set up the plan in Absence Management, select the Transfer absence
payment information for payroll processing check box. Find this seing in the Payroll
Integration section of the Entries and Balances tab on the Create Absence Plan page.
• For third-party absence applications, submit the Load Absence Batches process and
load an XML le.
Pensions • Submit the Load Benet Batches process and load an XML le.
The availability of this process depends on the implementation for your country or
territory.
Use an XML File to Load Data

Perform these actions to load data by submiing a process to transfer data using an XML le format:
1. Extract your data into an XML le, using the required XML le format and tags.
439
For time card entries, if your le is over 2 MB, stage the le on the Oracle WebCenter Content Server and note
the Content Id.
2. Select the Submit a Payroll Flow task from the Payroll Checklist work area and select the appropriate process:
Load Time Card Batches, Load Absences Batches, or Load Benets Batches.
3. On the Enter Parameters page, enter a name to identify the ow.
4. In the Interface eld, select the option to import an XML le.
5. For time card entries, if your le is over 2 MB, specify the number for the Content ID submission parameter.
6. Optionally, specify a process conguration group.
7. Optionally, schedule the process to transfer the time card entries, absences, or benet enrollments to payroll.
8. Click the Submit buon on the Review page. In the Conrmation window, click the Ok and View Checklist
buon.
9. On the Task Details tab of the payroll ow, click the Go To Task buon for the Upload File task.
If your le is over 2 MB, skip the Upload File task. The load batches tasks starts automatically.
10. On the Upload File page in the File eld, click the Add buon to display the Manage Aachments window.
11. In the Type eld, select File.
12. Search for and select your XML le. Click the OK buon.
The load batches task starts automatically after the Upload File task completes.
When the process is complete, a calculation card for each person included in the XML le is created or updated. Use the
Manage Calculation Cards task in the Payroll Calculation work area to view the new entries on the cards.
Related Topics
• File Format for Importing Time Entries to Payroll
Prerequisite Payroll Setup for Importing Time Entries

Before you can import time card entries to process in a payroll run or extract for a third-party payroll provider, complete
payroll setup tasks. These tasks vary depending on your conguration, specically whether your enterprise:
• Uses Oracle Fusion Time and Labor or a third-party time provider
• Uses Oracle Fusion Global Payroll or a third-party payroll provider
• Requires workers to submit a time card if their pay is calculated using time entries
440
This gure and table lists the tasks that depend on each of these conguration choices.
Create Elements for

Time Card Entries
Determine which
Workers enter
cost segments
costing on time Yes
workers complete on
cards?
their time cards
Create an HCM Determine process to

Use Oracle Fusion
Time an Labor?
No extract definition of transfer time card
time card elements entries to payroll
Schedule process to
transfer time card
entries
(optional)
Create an HCM
Use Oracle Fusion extract definition that
No includes the time
Global Payroll?
entries
Workers must Notify HR to select

complete time Yes Time Card Required
cards? field for new hires
All congurations create elements for use with time cards. This table describes the remaining setup tasks and processes
that vary based on your conguration.
Task Applies To
Create elements for time card entries All congurations

Determine which cost segments Optional for all congurations

workers complete on their time cards.

441
Task Applies To
Record costing overrides at the

element entry level by having workers
specify the account to charge on their
time cards.

Note: If you enable costing
overrides, ensure that you're
using the segments that are
enabled for element entry level
costing in the Cost Allocation
key exeld.

Create an HCM extract denition of Third-party time provider

time card elements

Third-party time provider

Determine process to transfer time
card entries to payroll:
• Use the Load Time Card

Batches process to upload
time entries in an XML le to
calculation cards.
• Use the Payroll Batch Loader
to load element entries.
Optional for all congurations

Schedule process to transfer time
card entries
As an example, schedule the Load

Time Card Batches process:
• After normal working hours to

distribute the load on server
• To run more frequently during
time periods when most
employees submit their time
cards
Create an HCM extract denition that Third-party payroll provider

includes time entries

Notify HR to select Time Card Optional for all congurations

Required eld at the Terms or
Assignment level when a new hire's
pay calculations depend on time
cards.

Related Topics
• Schedule Flows
• Extract Components
442
• Time Card Required Option
Create Elements for Time Card Entries

You create nonrecurring elements to process pay based on time card entries, such as elements for regular, overtime,
double-time, and shift pay. Creating a time card element generates all the related elements, balances, formulas, and
calculation components. You then transfer the elements to your time provider.
You do these tasks:
• Create earnings elements

• Create calculation components for standard-category elements
• Convert elements for use in time cards
• Set up area overrides
• Set up costing overrides
Create Earnings Elements

The steps for creating a time card element depend on whether the time card template is available for your country. If
the template is available, follow the steps in this section. Otherwise, create an earnings element using the Standard
category, and specify an hours multiplied by rate calculation rule.
Complete these steps to create an element using the time card template:
1. Create an earnings element on the Manage Elements page of the Payroll Calculation work area.
2. Select a primary classication of standard or supplemental earnings.
3. For Global Payroll, select the Time Card category.
4. Complete the information on the Basic Details page.
5. On the Additional Details page:
a. Select the calculation units to use in reports.
Typically, you select time units that match the time units entered on time cards for that element. If you
select dierent units, the application uses 8 hours to convert days to hours.
b. Optionally, select a default rate to calculate time.
When calculating the run result for the element entry, the formula uses the default rate unless a rate is
entered on the person's time card.
6. Complete the element eligibility information for the new time element, and its associated retroactive and
related elements, such as the result and calculation elements.
Note: If the straight time portion of overtime is reported separately from regular time, create two elements,
such as overtime and overtime premium elements. If the regular and straight time portions of overtime are
reported together, you might use straight time instead of regular time, and create a separate element for the
overtime premium.
443
Create Calculation Components for Standard-Category Elements

You can create calculation components for elements created with the Standard category rather than the Time Card
category. Complete these steps for each existing element:
1. Submit the Create Time Card Calculation Components process from the Payroll Checklist or Payroll
Administration work area.
These elements must have a calculation rule of hours multiplied by rate.

2. Complete the element eligibility information for the element and its associated retroactive and related
elements.
3. After you run the process to convert your elements, submit the Compile Formula process in the Manage
Payroll Calculations work area. Perform a bulk compile by entering wild cards in the Formula and Formula Type
parameters.
Generate Time Card Fields for Your Elements

After creating elements, generate time card elds for them. Complete the processes in this table using the Time and
Labor functional area in the Setup and Maintenance work area, Workforce Deployment oering:
Process What It Does
Generate Data Dictionary Time Creates dependent payroll aributes for all element input values, such as hours and rate.
Aributes
You must run the Generate Data Dictionary Time Aributes process after making any changes
to time elements. Such changes include adding or deleting elements, editing input values, or
editing element eligibility records.

Caution: Failure to run the process might negatively impact the setup of time card
elds, the validation of payroll time types, or the transfer of time to payroll.

Generate Time Card Fields Creates time card elds using the data dictionary time aributions for the specied legislative
data group.

You can use the Manage Time Card Fields task to create time card elds for single and multiple
aributes.

If you're using a third-party time provider, create an HCM extract for the time card elements. The extract includes the
element's mapping ID that you specify in the XML le when you transfer the time entries to payroll.
Set Up Area Overrides

Some countries or territories create time card elements with area input values for use as overrides. The overrides
enable employers to tax employees based on where they work. For example, employees specify the area information
where they worked on temporary assignment while away from their normal work location. These area entries are then
included in the time card records transferred to payroll by the Load Time Card Batches process.
444
Set Up Costing Overrides

You can specify additional aributes in Time and Labor to enter costing segment values on time cards. The segments
must match the segments that you can enter on element entries. Use the Manage Element Entries task in the Payroll
Calculation and search for a person's record. View the available segments on the Costing tab of the Manage Person
Details page. Costing is dened on the element eligibility record of the results element. When you transfer time entries,
the transfer process displays the costing on the calculation element.
As an example, the structure of your cost allocation key exeld might specify that the department segment is entered
at the element entry level. You could specify this additional aribute on the time card. Your employees can then specify
the department to charge for overtime hours worked while on loan to a dierent department. After you transfer the
time entries, the payroll calculation uses the department specied for the overtime hours to derive the costing results.
To view the results of the costing overrides transferred to payroll, perform these steps:
1. On the Accounting Distribution work area, select Search Person.
2. On the Search Person page, search for a person.
3. Click the Actions down arrow and select View Person Process Results in the Process Results option.
4. Go into a person's statement of earnings.
5. Select Costing Results.
Related Topics
• Time Card Required Option
Import Time Card Entries to Payroll

Submit the Load Time Card Batches process from the Payroll Checklist or Payroll Administration work areas to import
time card entries to payroll. The process creates a calculation card or updates an existing card for each person with time
entries included in the batch.
Use the same process to import time entries from Oracle Fusion Time and Labor and from a third-party time provider.
You would require an additional step to create an XML le that contains the time entries for submiing the time entries
for a third-party. This topic covers both the procedures:
• Import time entries from Time and Labor
• Import time entries from a third-party time provider
Import Time Entries from Time and Labor

Complete these steps to import your time entries
1. On the Payroll Checklist work area, Tasks panel tab, click Submit a Payroll Flow.
a. On the Submit a Payroll Flow: Select Flow Paern page, select the legislative data group.
b. In the Flow Paern section, select Load Time Card Batches.
2. Click Next.
3. On the Submit a Payroll Flow: Enter Parameters page, in the Payroll Flow eld, enter a name to identify the
ow.
4. In the Interface Type eld, search for and select ORACLE FUSION TIME AND LABOR.
5. Optionally, specify a process conguration group. Click Next.
445
Note: If you don't need to connect, schedule, or review the ow parameters, skip these pages
and submit the ow.
6. On the Enter Flow Interaction page, complete the optional parameters. Click Next.
7. On the Schedule page, complete the optional parameters. Click Next.
8. On the Review page, click Submit. In the Conrmation dialog box, click OK and View Checklist.
9. On the Payroll Flow page, Task Details tab, you should see a green check mark in the Upload File row, Task
Type column. If not, click the Refresh icon intermiently on the toolbar until you do.
10. Right-click the Upload File row and select Mark as Complete.
You don't need to upload a le for Time and Labor. The Upload task is only used to upload an XML le from a
third-party time provider.
The View Person Process Results page lists the time card IDs included in the batch of transferred time cards. View
the time entries for each person's time included in the batch using the Manage Calculation Cards task in the Payroll
Calculation work area.
Import Time Entries from a Third-Party Provider

Complete these steps to transfer your time card entries from a third-party provider:
1. On the Payroll Checklist work area, Tasks panel tab, click Submit a Payroll Flow.
2. On the Submit a Payroll Flow: Select Flow Paern page, select the legislative data group.
3. In the Flow Paern section, select Load Time Card Batches.
4. Click Next.
5. On the Submit a Payroll Flow: Enter Parameters page, in the Payroll Flow eld, enter a name to identify the
ow.
6. In the Interface Type eld, search for and select Import Time XML.
8. If your le is over 2 MB, specify the number for the Content ID submission parameter.
9. Click Next.
10. On the Enter Flow Interaction page, complete the optional parameters. Click Next.
11. On the Schedule page, complete the optional parameters. Click Next.
buon.
13. If your le is over 2 MB and you have already provided the Content ID during submissions, skip the Upload File
task.
To skip the task, right-click on the row and select Mark as Complete. The load batches tasks starts
automatically.
If not, then follow the below steps to upload the XML le:
a. On the Payroll Flow page, Task Details tab, you should see a green check mark in the Upload File row,
Task Type column. If not, click the Refresh icon intermiently on the toolbar, until you do.
b. Click the Go to Task icon.
c. On the Upload File page in the File eld, click Add to display the Manage Aachments dialog box.
d. In the Type eld, select File.
e. Search for and select your XML le. Click OK .
f. On the Upload File page, click Done to complete the submission and initiate the time data transfer.
446
The View Person Process Results page lists the time card IDs included in the batch of transferred time cards. View
the time entries for each person's time included in the batch using the Manage Calculation Cards task in the Payroll
Calculation work area. Entries transferred from third-party providers only display on the calculation cards, and not in the
Oracle Fusion Time and Labor time cards.
Related Topics
• File Format for Importing Time Entries to Payroll
• Options to Connect Flows
File Format for Importing Time Entries

You import time entries from a third-party provider by submiing the Load Time Card Batches process from the Payroll
Checklist or Payroll Administration work areas. When you submit the process, you specify the batch XML le that
includes your time entries. This topic explains the XML le format and XML tags you must use in the le.
XML File Format for Importing Time Entries

When you create a le to transfer time card entries to payroll, use the following structure.
<TIME_CARD_LIST>
<TIME_CARD>..
<ACTION>
<TIME_CARD_ID>
<ACTION>
<TIME_CARD_ID>
<MAPPING_NAME>
<LDG_ID>
<LDG_NAME>
<HR_TERM_ID>
<TERM_NUMBER>
<HR_ASSIGNMENT_ID>
<ASSIGNMENT_NUMBER>
<LEGAL_EMPLOYER_ID>
<LEGAL_EMPLOYER_NAME>
<TIME_CARD_START>
<TIME_CARD_END>
<TIME_ITEM_LIST>..
<TIME_ITEM>
<TIME_TYPE>
{
<PAYMENT_RATE_ID>
<PAYMENT_RATE_NAME>
<RATE_AMOUNT>
<PERIODICITY>
<FACTOR>
<AMOUNT>
<PERIODICITY>
}
<TIME_UNIT>
<TIME_UOM>
<TIME_ITEM_START>
<TIME_ITEM_END>
<COST_SEGMENTS>
447
<SEGMENT1..30>
</COST SEGMENTS>
<PROPERTIES LIST>..
<PROPERTY_ITEM>
<NAME>
<VALUE>
</PROPERTY_ITEM>
</PROPERTY_LIST>
</TIME_ITEM>
</TIME_ITEM_LIST>
</TIME_CARD>
</TIME_CARD_LIST>
XML Tags
This table describes the purpose of the tags used in the XML le.
XML Tag Purpose
TIME_CARD_LIST Parent tag that contains a set of time cards.

TIME_CARD Object that contains the information about a specic time card.

ACTION Action to perform, such as CREATE, REMOVE, MODIFY.

TIME_CARD_ID Unique identier for this time card.

MAPPING_ID Identier for the payroll component denition.

Specify the Mapping ID or the Mapping Name. If none is included, the process uses the default
interface type Import Time XML and aempts to nd a mapping.

MAPPING_NAME Name used for the mapping.

Specify the mapping name or the mapping ID. If none is included, the process uses the default
interface type Import Time XML and aempts to nd a mapping.

LDG_NAME Name of the legislative data group (LDG) for this record.

Specify the identier or name of the LDG. All the records in the XML le must belong to
the same LDG. If you don't include the LDG_ID or the LDG_NAME, the application uses the
legislative data group you entered for the Load Time Card Batches process.

LDG_ID Identier for the LDG for this record.

Specify the identier or name of the LDG. All the records in the XML le must belong to the
same LDG. If you don't include the LDG_ID or the LDG_NAME, the application uses the LDG
you entered for the Load Time Card Batches process.

448
XML Tag Purpose
TERM_NUMBER Number that identies the term for the time entry.

ASSIGNMENT_ NUMBER Number that identies the assignment for the time entry.

TIME_ CARD_START Start date of the time card.

TIME_CARD_END End date of the time card.

TIME_ITEM_LIST Tag that contains a set of time items.

TIME_ITEM Object that contains information about a specic hour item.

TIME_TYPE Name that the time application supplies and which maps to the payroll element and calculation
component.

PAYMENT_ RATE_ID Identier for the rate denition used to calculate the payment amount.

PAYMENT_ RATE_NAME Name of the rate denition used to calculate the payment amount.

RATE_AMOUNT Actual rate used to calculate the payroll amount.

AMOUNT Flat amount used to calculate the rate based on periodicity.

PERIODICITY Frequency that determines the rate value, used with amount or rate amount.

FACTOR Multiplier applied to the derived rate to calculate the payment amount.

TIME_UNIT Number of units for the Unit of Measure specied in TIME_UOM. For example, if the UOM is
hours, 8 units is 8 hours worked.

TIME_UOM Unit of measure for specifying time unit, such as hours.

TIME_ ITEM_START Start time for the time entry.

TIME_ITEM_END Ending time for the time entry.

COST_SEGMENTS List of the costing segments.

PROPERTY_LIST Set of properties for the time item.
449
XML Tag Purpose

PROPERTY_ITEM Additional information that's captured. For example, a value denition for the property item
State would return State and the name of the State.

NAME Name of a property for the time item.

VALUE Value of a property for the time item.

Integrate Absence Management with Global Payroll

Use Oracle Fusion Absence Management to set up and enroll persons in absence plans. Transfer absence information
to Oracle Fusion Global Payroll for processing and paying absences.
Integrating Absence Management with payroll requires that you complete steps in dierent work areas for Absence
Management, Human Resources, and payroll. This table displays the sequence of tasks to perform in each work area.
Steps Absences work area Person Management work Set Up and Maintenance
area work area
Create an absence plan, such Manage Absence Plans task NA NA

as an Accrual, Qualication, or
No Entitlement plan.

Create absence types based Manage Absence Types task NA NA

on predened absence
paerns and associate them to
the absence plans.

Create rate denitions to use NA NA Manage Rate Denitions task

in calculating accrual and
liability balances.

Create absence elements. NA NA Manage Elements task

450
Steps Absences work area Person Management work Set Up and Maintenance
area work area
Manage Absence Plans task NA NA

Complete these payroll
integration information:
Note: Find these
• Select the Transfer seings in the Payroll
absence payment Integration section of
information for payroll
the Entries and Balances
processing check box.
tab on the Create
• Select the element for
the plan in the Element Absence Plan page.
eld. The element links
the absence plan to the
calculation component
shown on the person's
calculation card.
• Optionally, specify
rates. These rates
override rates specied
elsewhere.
NA Manage Absence Records task NA

Enroll persons in the absence
plan:
• Add the plan and

provide the entitlement
date information.
• For accrual plans, select
the Run Accruals for
Selected Plan task
action.
After the information is set up, you can record an absence using the Manage Absence Records task in the Person
Management work area. When the absence is approved, the daily and summary breakdown information is automatically
transferred to payroll.
You can then process the payroll that includes these absence entries and view the resulting absence balances on the
person's Statement of Earnings. After you process and archive payments, you can view the resulting absence balances
on the person's payslip.
Related Topics
• How Many Salary Bases to Create
• Rates Used to Calculate Absences in Payroll
Dene Payroll Elements to Process Absences

You dene elements to calculate and process absence payments in Oracle cloud. When you dene an absence element,
your responses to the element template questions determine which elements, balances, formulas, and calculation
components the template generates.
451
Dening an absence element involves these steps:

• Dene an absence element
• Complete absence detail questions
• Complete accrual liability and balance payment questions
• Complete absence payment questions
• Submit the element
• Dene element eligibility records and cost distributions
Dene an Absence Element

Use the Manage Elements task in the Payroll Calculation work area to dene an absence element, selecting a primary
classication of Absence, and a secondary classication. Typically, the predened values include vacation, maternity,
and sickness.
Complete Absence Detail Questions

The questions you complete in the Absence Details section determine which subsequent questions the template
displays. You enter these information in the Absence Details section:
1. Specify the calculation units to use when reporting the absence, for example that's shown on the payslip, and
statement of earnings. Typically, you select Days or Hours for your reports that correspond to the units for your
absence plan. When creating an absence element, select the work calculation rule to calculate the absence rate.
2. Select the absence information to transfer to payroll based on the type of absence management plan.
Absence Management Plan Type Absence Information to Transfer
Accrual Accrual Balances

Accrual, Leave Donation, Accrual Balances and Absences

Compensatory

Qualication Qualication Absences

No Entitlement No Entitlement Absences

Complete Accrual Liability and Balance Payment Questions

If you transfer accrual balances, complete these questions.
Question Steps
Calculate absence liability? 1. Select Yes, if you calculate liability.

2. Select a liability rate.
452
Question Steps
Usually the rate is the same as the absence payment rate. You might select a dierent
rate when estimating liability for billing purposes.
Does this plan enable balance 1. Select Yes to congure a nal disbursement element and to maintain balances for the
payments when enrollment ends? disbursement hours and payments.
2. Optionally, select a rate to use for the calculation.
Does this plan enable partial payment 1. Select Yes to congure a discretionary disbursement element and to maintain balances
of balance? for disbursement hours and payments.
2. Optionally, select a rate to use for the calculation.
Complete Absence Payment Questions

Complete these questions:
1. Select a method to reduce regular earnings if employees don't complete a time card.:
◦ Reduce regular earnings by absence payment (entitlement payment balance)

◦ Select rate to determine absence deduction amount (entitlement deduction balance)
You might select one of these options:
• The Reduce regular earnings option to reduce regular earnings by the absence payment. This
means that the employee is paid the same net amount as if they weren't absent.
• The Select rate to determine deduction amount option when the employee isn't due to be paid
for the absence at the same rate as their regular earnings. In this case, the absence deduction rate
that you select will be a rate that deducts 100% of the regular earnings. However, the absence
payment rate would be a dierent rate, for example 50%.
2. Optionally, select a rate to calculate the absence payment.
If you have standard earnings and absence elements in the same payroll run that reduce regular earnings, the
payroll calculation reduces earnings in this sequence:
a. Using absence element entries

b. Using any standard earnings elements that reduce regular earnings
The salary balance isn't reduced beyond zero.

3. You can now ensure that absence entitlement payments are made to employees after terminations. Use the
Does this plan enable entitlement payments after termination? question on the absence element template
to set the entitlement element to Final Close.
Example: Amelia is due to be paid maternity payments after her termination. Select Yes in this question to set
the latest entry date of the entitlement elements to nal close. With this, the absence entitlement payments are
made to Amelia after her termination. When Amelia is terminated, change her employment assignment status
to Process When Earning. Also, set the TERM_INCLUDE_PR_LEVEL action parameter to Y, so that payroll
relationship level entries are considered for processing.
453
Submit the Element

When you submit the element, the template automatically congures a base pay element, balances, formulas, and
calculation components.
The template also congures additional elements, depending on the options selected in the template to transfer
absence information, as shown in this table.
Type of Absence Information to Optional Balance Payments Selected Additional Elements Congured
Transfer
Accrual Balances • Discretionary Disbursements • Accrual

• Final Disbursements • Discretionary Disbursement
• Final Disbursement
Accrual Balances and Absences • Discretionary Disbursements • Accrual

• Final Disbursements • Entitlement
• Discretionary Disbursement
• Final Disbursement
Qualication Absences none Entitlement

No Entitlement Absences none Entitlement

Dene Element Eligibility Records and Cost Distributions

Dene element eligibility records for all the elements generated by the template, for example for your accrual,
entitlement, discretionary and nal disbursement elements.
If your enterprise calculates cost distributions, specify costing for all the element eligibility records. For example, for an
accrual element, you do these steps
1. Dene element eligibility records for the accrual, accrual results, accrual retroactive, and accrual retroactive
results elements.
2. Specify costing for the accrual results and retroactive results elements.
The costing process costs the change in the liability balance since the last payroll period, debits the expense account
and credits the liability account.
Related Topics
• Element Costing Options
• Dene Payroll Elements for an Absence Accrual Plan
• Rates Used to Calculate Absences in Payroll
454
Importing Absence Entries to Payroll: Procedure

You can import worker absences from Oracle Fusion Absence Management or another absence application to Oracle
Fusion Global Payroll to process absence payments. When you set up an absence plan, you associate an absence
element to transfer the absence information to a person's calculation card. Processing absence information for payroll
includes the following aspects.
• Importing absence entries
• Processing absence entries
• Validating absence results
• Correcting absence results
Importing Absence Entries from Absence Management

Recording an absence in Absence Management transfers a summary record and a daily breakdown for each day the
person is absent to the person's calculation card. The summary record contains information such as the start and end
date of the absence, the absence rate, the units. The daily breakdown shows the absence date and any factor to be
applied, such as a percentage to use when calculating the absence payment.
Importing Absence Entries from a Third-Party

If you use a third-party absence application, you create an XML le for the absence entries and transfer it to payroll
using the Load Absence Batches process. Complete the following steps:
1. Extract your absence data into an XML le. You must use the required le format and XML tags.
2. Use the Submit a Payroll Flow task to submit the Load Absence Batches ow from the Payroll Administration or
Payroll Checklist work areas.
4. In the Interface eld, select Import Absence XML.
6. Optionally, complete the parameters on the Flow Interaction page.
7. Optionally, complete the parameters on the Scheduling page.
buon.
The View Person Process Results page lists the absence IDs included in the batch of transferred absences. View the
absence entries for each person included in the batch using the Manage Calculation Cards task in the Payroll Calculation
work area.
455
Processing Absence Entries

Transferring the absence information to a calculation card creates an element entry for the element associated to the
absence plan. The payroll run processes this entry using the formula aached to the element and values from the
calculation card. The resulting values are then passed back to the element entry and stored as run results and balances.
Validating Absence Results

You can verify the results of absences after calculating run results by using payroll reports or the statement of earnings.
After archiving payment results, validate absence information on the Payroll Register Report or the person's payslip.
Review absence results on the following payroll reports:

• Element Result Report
• Gross-to-Net Report
• Payroll Activity Report
• Payroll Balance Report
• Payroll Register Report
Use the View Person Process Results task in the Payroll Calculation work area or click the person's record on the Person
Process Results page of the payroll calculation ow to go to the person's statement of earnings. The following table lists
the absence information displayed on the statement of earnings.
Statement of Earnings Sections Information Displayed
Absences Accrual tab in the Quick Accrual balances for accrual days and accrual hours
Reference Summary

Absences • Total for the entitlement, discretionary disbursement, nal disbursement payment
• Absence deductions made for that period
Use the View Payslip task to view the person's absence information in the Person Management work area. The following
table lists the absence information displayed on the payslip.
Payslip Sections Information Displayed
Summary Total amount for the following balances: entitlement payment, entitlement deduction, nal
disbursement payment, and discretionary disbursement payment

Absence Payment balances that contribute to the total absence balance shown in the Summary region

Note: Subregions display hours and rate, and days and rate details for these
balances

Absence Accrual Balances for accrual days and accrual hours

456
For accrual liabilities, the Employer Charges section of the Statement of Earnings page and payslip display the
dierence for liability balance since the last payroll.
Correcting Absence Results

You can continue to transfer updated absence entries to a person's calculation card until the payroll calculation starts.
Any further updates are then processed as retroactive absences entries in the following payroll run.
File Format for Importing Absence Entries

When you submit the Load Absence Batches process, specify the aachment for the XML le that contains the absence
data. This topic explains the XML le format and XML tags you must use in the le.
You submit the Load Absence Batches process from the Payroll Administration work area. The process creates a
calculation card or updates an existing card for each worker whose absence information is transferred.
XML File Format for Importing Absence Information to Payroll

When you create a le to transfer absence information to payroll, use this format.
<ABSENCE_LIST>
<ABSENCE>
<ABSENCE_TYPE>
<ACTION>
<ABSENCE_ID>
<MAPPING_ID>
<MAPPING_NAME>
<LDG_ID>
<LDG_NAME>
<HR_TERM_ID>
<TERM_NUMBER>
<HR_ASSIGNMENT_ID>
<ASSIGNMENT_NUMBER>
<ABSENCE_RATE_ID>
<ABSENCE_RATE_NAME>
<ABSENCE_UNIT>
<ABSENCE_UOM>
<ADJUSTMENT_UNIT>
<FACTOR>
<CALCULATION_DATE>
<PERIODICITY>
<ABSENCE_START>
<ABSENCE_END>
<ABSENCE_DATE_LIST>
<ABSENCE_DATE>
<LEAVE_DATE>
<ACCRUED_DATE>
<OVERRIDING_FACTOR>
<OVERRIDING_RATE_ID>
<OVERRIDING_RATE_NAME>
<OVERRIDING_UOM>
<OVERRIDING_UNIT>
<\ABSENCE_DATE>
<\ABSENCE_DATE_LIST>
<\ABSENCE>
457
<\ABSENCE_LIST>
XML Tags
XML Tag Purpose
ABSENCE_LIST Outermost tag that contains a set of absences.

ABSENCE Tag containing information about a particular absence.

ABSENCE_TYPE Type of absence that's being transferred to payroll, such as accrual, accrual with entitlement, or
entitlement.

ACTION Type of action that would be performed, such as CREATE, REMOVE, and MODIFY.

ABSENCE_ID Unique identier for the absence from the source application. Never use the same ID twice to
identify another absence.

MAPPING_ID Identier for the payroll component denition, which is used to create the absence in payroll.

MAPPING_NAME Name used for the mapping.

LDG_ID ID of the legislative data group associated with the record.

LDG_NAME Name of the legislative data group associated with the record.

HR_TERM_ID Unique ID for the HR period.

You can provide either the TERM_NUMBER or the HR_ TERM_ID. If you provide the
TERM_NUMBER, you must also provide the legal employer details.

TERM_NUMBER Number that identies the employment periods for the absence.

HR_ ASSIGNMENT_ID This is the HR Assignments unique ID.

You can provide either the ASSIGNMENT_ NUMBER or the HR_ ASSIGNMENT_ID. If you
provide the ASSIGNMENT_ NUMBER then you must also provide the legal employer details.

ASSIGNMENT_ NUMBER Number that identies the employment assignment for the absence.

ABSENCE_ RATE_ID Unique identier for the absence rate.
458
XML Tag Purpose

ABSENCE_ RATE_NAME Name of the rate used to calculate the payment amount.

ABSENCE_UNIT Unit of time in which the absence is recorded.

ABSENCE_UOM Unit of measure being used for the absence (for example, days, hours or weeks).

ADJUSTMENT_ UNIT Unit of time in which an adjustment is being made to the absence.

FACTOR Factor that's used in the calculation of the absence.

CALCULATION DATE Date used for payroll calculations, such as the payment calculation for maternity leave based
on the baby's due date.

PERIODICITY Used with the amount or rate, the periodicity is the frequency that determines the absence
rate.

ABSENCE_START Date the absence started.

ABSENCE_END Date the absence ended.

ABSENCE_ DATE_LIST List of dates in which the absence occurred.

ABSENCE_DATE Date the absence is being reported.

LEAVE_DATE Date on which the leave of absence occurred.

ACCRUED_DATE Date on which the absence was accrued.

OVERRIDING_ FACTOR Factor that's being used to override the calculation of the absence.

OVERRIDING_ RATE_ID Unique identier for the rate being used to override the absence.

OVERRIDING_ RATE_NAME Name of the overriding rate that would be used to calculate the absence.

OVERRIDING_UOM Unit of measure being used to override the absence (for example, days, hours or weeks).

OVERRIDING_ UNIT Unit of time in which an override is being made to the absence.

459
Run the Load Benet Batches Process

Use the Load Benet Batches process to transfer pension deduction information from a benets application to benets
and pensions calculation cards for payroll processing.
Submit the Process

You can submit the process from the Payroll Checklist or Payroll Administration work areas. Alternatively, you can add it
to a payroll ow paern so that it runs as part of your regular payroll ow.
To submit the process, do these steps:

1. Extract your pension data into an XML le, which must use the required le format and XML tags.
2. Use the Submit a Payroll Flow task to submit the Load Benet Batches ow from the Payroll Administration or
Payroll Checklist work areas.
4. In the Interface eld, select Import Benet XML.
6. Optionally, complete the parameters on the Flow Interaction page.
7. Optionally, complete the parameters on the Scheduling page.
buon.
Resolve Transfer Errors

When you load a benets batch, the application validates the entries to conrm that the worker isn't terminated and is
eligible for the deduction. The application rejects entries for any date beyond the worker's termination date.
If the process ends in error, you can roll it back, resolve the error in the source application, and resubmit the Load
Benet Batches process.
View and Correct Entries

When the process completes successfully, it creates or updates a calculation card for each person included in the XML
le. Use the Manage Calculation Cards task in the Payroll Calculation work area to view the new entries on the cards.
You can enter or update these values on the cards, if required:

• Payee
• Reference Number
• Employee Additional Contribution
The other values are view-only and must be maintained in the source application.
460
Related Topics
• Considerations to Enter Calculation Values for Pensions
File Format for Importing Pension Deductions

When you submit the Load Benet Batches process, specify the aachment for the XML le that contains the benet
data. This topic explains the XML le format and XML tags you must use in the le. Submit the Load Benet Batches
process from the Payroll Checklist or Payroll Administration work areas. The process creates a calculation card or
updates an existing card for each worker whose pension information is transferred.
XML File Format for Importing Pension Deductions to Payroll

When you create a le to transfer pension deduction information to payroll, use this format.
<BENEFIT LIST>
<BENEFIT>...
<ACTION>
<BENEFIT_ID>
<MAPPING_ID>
<LDG_ID>
<LDG_NAME>
{
<HR_TERM_ID>
<TERM_NUMBER>
<HR_ASSIGNMENT_ID>
<ASSIGNMENT_NUMBER>
}
<LEGAL_EMPLOYER_ID>
<LEGAL_EMPLOYER_NAME>
<BENEFIT_START>
<BENEFIT_END>
{
<BENEFIT_RATE_ID>
<BENEFIT_RATE_NAME> |
<AMOUNT>
<PERIODICITY>
<BENEFIT_MAX_ELECTION>
<BENEFIT_REF_NUMBER>
}
</BENEFIT>
</BENEFIT_LIST>
XML Tags
XML Tag Purpose
BENEFIT_LIST Outermost tag that contains a set of benets.
461
XML Tag Purpose

BENEFIT Tag containing information about a particular benet.

ACTION The type of action that would be performed, such as CREATE, REMOVE, and MODIFY.

BENEFIT_ID Unique identier for the benet from the source application. Never use the same ID twice to
identify another benet.

MAPPING_ID Identier for the payroll component denition, which is used to create the benet in payroll.

LDG_ID ID of the legislative data group associated with the record.

LDG_NAME Name of the legislative data group associated with the record.

HR_TERM_ID Unique ID for the employment period.

You can provide either the TERM_NUMBER or the HR_ TERM_ID. If you provide the
TERM_NUMBER, you must also provide the legal employer details.

TERM_NUMBER Number that identies the employment period for the pension deduction.

HR_ ASSIGNMENT_ID Unique ID for the assignment.

You can provide either the ASSIGNMENT_ NUMBER or the HR_ ASSIGNMENT_ID. If you
provide the ASSIGNMENT_ NUMBER you must also provide the legal employer details.

ASSIGNMENT_ NUMBER Number that identies the employment assignment for the pension deduction.

LEGAL_ EMPLOYER_ID ID of the legal employer name that the assignment belongs to.

LEGAL_ EMPLOYER_NAME Legal employer name that the assignment belongs to.

BENEFIT_START Start date of the benet.

BENEFIT_END End date of the benet.

BENEFIT_ RATE_ID ID of the rate that would be used to calculate the payment amount.

BENEFIT_ RATE_NAME Name of the rate that would be used to calculate the payment amount.

AMOUNT Amount that's used to calculate the rate using the periodicity.
462
XML Tag Purpose

PERIODICITY Used with the amount or rate, the periodicity is the frequency that determines the rate value.

BENEFIT_ MAX_ELECTION Annual maximum election amount that can be processed.

BENEFIT_ REF_NUMBER Employee's reference number with the provider of the pension (benet organization).

463
464
Integrating with HCM Managing HCM Extracts
34 Managing HCM Extracts
Extract Components
The HCM Extracts feature is a exible tool for generating data les and reports. This topic covers how you can use the
extract components to dene what information you want the application to extract and report on. It also explains how
the application displays, formats, and delivers the information.
Extract Denitions
An extract denition refers to the complete setup of an extract, that consists of extract data groups, criteria, records,
aributes, advanced conditions and output delivery options. An extract denition consists of:
• One or more extract data groups, depending on how many logical entities you want to extract.
• One or more extract records depending on how many groups of information you want to collect.
• One or more aributes depending on how many individual elds of data you want to collect.
You use HCM extracts to extract, archive, transform, report, and deliver high volumes of HCM data from the Oracle
Fusion HCM database. You can generate the output in the following formats:
• CSV
• XML
• Excel
• HTML
• RTF
• PDF
You can distribute the extracted information by email, fax and other delivery modes. Some common examples of
extracts are: PDF payslips delivered to employees' mailboxes, payroll or benets data transferred to third-party service
providers, HR and talent data exchange between Oracle Fusion and legacy applications, for example in a coexistence
scenario.
Data Groups
Extract data groups represent a business area or logical entity, for example person, assignment, or benets. The
application uses this information to retrieve the database item groups. You dene one data group as the primary or root
data group and this data group is the starting point of the data extraction.
Extract data group connections capture the association details between the current data group and the parent data
group. The data group connections form the hierarchical relationship among the data groups.
You can dene a set of ltering conditions the application must perform on an extract data group using the extract data
group criteria. You specify the criteria conditions using an expression or fast formula.
465
Extract Records
Extract records represent a grouping of related data or a physical collection of all elds required in the extract. For
example, the Employee data group can have records such as Basic Details, Pay Details, Location Details, and Primary
Contact. An extract record is a collection of aributes which you can organize in a required sequence. For example, if a
data group has 3 records, then you can specify the sequence in which the application processes the records. You can
also select the next data group to identify which data group the application processes next.
Aributes
Aributes are the individual elds inside the extract record. An aribute is the lowest aribute level of a HCM extract
and represents a piece of information, for example, person rst name, person last name or person date of birth.
This gure demonstrates the hierarchy of information within a data group denition.
Extract Definition
Department
(Data Group)
Department Department Other

Information Information
(Record) (Record)
Department Department Department

Department
ID Name Start Date
Location (Attribute)
(Attribute) (Attribute) (Attribute)
Related Topics
• Overview of Generating Flexeld Database Items
HCM Extract Types

The type of extract you select determines the purpose of the extract. It also determines the parameters that are
automatically generated. For example, if you select the Payroll Interface extract type, then the application creates a
466
changes only parameter, as well as the other parameters. You can select the extract type on the Manage HCM Extract
Denitions page.
This table lists the dierent extract types and why you select them.
Extract Type Purpose
Full Prole Use for complete employee and payroll data archives.

Payroll Interface Use for providing data to third party payroll service providers.

Payments Use for salary payment method archives. For example, Paid through cheque or bank transfer.

Benet Carrier Use for providing data to third party benets service providers.

Archive Retrieval Use for reports based on permanently archived data, for example, payslip.

EOY Archive Use for end of year archives (HR, Benets).

HR Archive Use for all HR archives.

Payroll Archive Use for all payroll or payslip archives.

Other Payroll Archive Use for all payroll archives.

Overview of Payroll Interface Extract Denitions

The extract denitions of the Payroll Interface extract type determine the data you send your third-party payroll
provider. This table lists the predened Payroll Interface extract denitions that you can use or dene to meet your
business-specic extract requirements.
Extract Denition Purpose Output
Global Payroll Interface Derives payroll data either from element eText and XML
entry values or from balance results that
the Calculate Gross Earnings process
creates.

Payroll Interface for NGA Extracts general-purpose HR and XML

payroll-related data to integrate with
Payroll Exchange for third-party payroll
processing by NGA Human Resources.
467
Extract Denition Purpose Output
This extract transforms the data into

an HR-XML format compliant with NGA
Human Resources standards.

Use the predened Run Payroll Interface
Report for NGA process if you don't
require special modications.

US ADP PayForce Third-Party Ad-Hoc Derives payroll data from element entries, eText and XML
Extract including common HR and payroll data for
a date range or a payroll period. Output
format is compliant with Automatic Data
Processing (ADP) PayForce standards.

US ADP PayForce Third-Party Periodic Derives payroll data from balance results eText and XML
Extract that the Calculate Gross Earnings process
creates for a payroll period. Output format
is compliant with ADP PayForce standards.

Related Topics
• Options to Extract Payroll-Related Data
• Example to Extract Payroll Data for Third-Party Processing
Best Practices for Viewing User Entity Details

When creating an extract denition, you need user entity details to create data groups. You can access the View User
Entity Details UI using the Data Exchange tasks pane or when you create a data group in the Design tab of the Manage
Extract Denitions task.
Using the View User Entity Details page, you can:
• View the database items available in a user entity.
• Validate user entities for use with root data groups.
• Review the type of user entity, for example, single row, multiple rows, historic, or eective dated.
• Review the SQL query the user entity uses.
• Calculate the number of rows in a data set.
• Review the contexts used and set by the user entity.
• Verify the extracts that are using the user entity.
The following sections detail the information that you can derive from the View User Entity Details UI.
Reviewing the User Entity Details

Search for a user entity in the View User Entity Details UI and click the User Entity Details tab.
If the value of Valid for Root Data Group is Yes, the user entity can be used as a root data group. You can also determine
if a user entity is valid for use as a root data group, if the value of Multiple Rows is Yes and Context Required is No. For
468
example, the PER_EXT_SEC_PERSON_UE user entity can be used as a root data group, as the value of Multiple Rows is
Yes and Context Required is No.
If a user entity is not a multiple row user entity, you must not use it as the root data group. If a multiple row user
entity sets the contexts required for a single row user entity, the database item groups from the single row user
entity are generally included as derived database item groups to the multiple row user entity. For example, the
PER_PER_PERSON_DETAILS_UE user entity is not a multiple row user entity.
If a user entity is historic, it retrieves data irrespective of the eective date. For example, the
PER_EXT_ASSIGNMENT_BASIC_HISTORY_UE user entity retrieves the entire historic details of an assignment.
If a user entity is not historic, it retrieves data as of the eective date. For example, the PER_EXT_PAY_EMPLOYEES_UE
user entity retrieves Person, Assignment, and Payroll details as of the eective date.
Reviewing the SQL query

In the View User Entity Details UI, search for a user entity and click the Query tab. This tab lists the SQL query that the
user entity uses to extract data. You can review the table structure and aliases which is useful for creating advanced
lter criteria. If the user entity is valid as a root data group, you can calculate the rows that the SQL query will return.
However, the number of rows returned is an estimate and may not match the exact number of rows the extract will
return. The actual extract output depends on the lter criteria, expressions, and fast formulas used in the extract.
Reviewing the User Entity Contexts

In the View User Entity Details UI, search for a user entity and click the Context tab. The Contexts Required section
lists the contexts that you have to set to use the user entity in the extract. For example, the PER_PER_PHONES_UE
user entity requires the PERSON_ID context; therefore, you must set the PERSON_ID context to use this user entity.
Generally, the user entities that are not historic require the EFFECTIVE_DATE context. However, the EFFECTIVE_DATE
context is set by default, so you do not have to set this context explicitly. The Contexts Set section lists the contexts
that are set by the user entity. For example, the PER_EXT_SEC_PERSON_UE user entity sets the PERSON_ID,
ORGANIZATION_ID, and ENTERPRISE_ID contexts that can be used by other user entities.
Verifying Extracts Using the User Entity

In the View User Entity Details UI, search for a user entity and click the Extracts Using User Entity tab. If another extract
is using the user entity, you can review the extract design to understand how the user entity is being used. You can also
copy the extract design and then modify it to suit your needs.
User Entities in HCM Extracts

A user entity is a logical entity associated with a data group dened using HCM extracts. This topic describes the
frequently used user entities and the type of data you can extract by using those user entities. You select user entities in
the application when you dene a data group.
The following table lists the most frequently used user entities.
User Entity Name and Code Description
Person (PER_ EXT_ SEC_ Retrieves all persons across the enterprise and all person related aributes.
PERSON_UE)
469
User Entity Name and Code Description
Worker Payroll (PER_ EXT_ PAY_ Retrieves all workers and their payrolls across the enterprise, all person, worker, payroll related
EMPLOYEES_UE) aributes, and element entry data.

Extract Assignment Basic History Retrieves assignment history as on the assignment eective start date.
(PER_ EXT_ ASSIGNMENT_ BASIC_
HISTORY_UE)

Extract Assignment Basic Information Retrieves assignment data as on the eective date.
(PER_ EXT_ SEC_ ASSIGNMENT_
BASIC_UE)

Assignments Range (PER_ EXT_ SEC_ Retrieves assignment history as on the eective date.
ASSIGNMENT_ RANGE_UE)

Extract Current and Future Persons Retrieves current and future person details. Specify advanced lter criteria to restrict person
(PER_ EXT_ SEC_ PERSON_ NOW_ types.
FUTURE_UE)

Extract Current and Future Retrieves current and future assignments.

Assignments (PER_ EXT_ SEC_
ASSIGNMENT_ NOW_ FUTURE_UE)

Reset Context (PER_ EXT_RESET_UE)

Use the Reset Context user entity in two ways:
1. Reset the eective date contexts set dynamically by a parent data group using a runtime
input parameter for the eective date. For example, the Extract Assignment Basic
History user entity sets the assignment eective start date as eective date rst and
then retrieves the data, unlike other user entities which use the eective date only. If
you want to use the Extract Assignment Basic History user entity to include the historical
data but also want to change the eective date, then include the Reset Context user
entity to reset this date using input parameters.
2. Set up the Reset Context user entity as the root user entity to be a container or header.
For example, the following work structure elements: locations, positions, and legal
employers are not related to each other. If you want to extract all of them in one single
extract, then you can add them as child elements to the Reset Context user entity used
as the root in the extract denition. Adding this user entity as the root to these elements
enables you to retrieve this data separately because the elements are not linked to a
hierarchy.
You can view more details about the user entities using the View User Entity Details task.
Related Topics
• Example of Generating Flexeld Database Items
470
HCM Extracts Templates

Use the predened Work Structure and Worker extract templates to quickly set up extracts that generate work
structure and worker details. The Work Structure extract generates details of business units, legal entities, departments,
grades, jobs, locations, and positions. The Worker extract generates details of person names, phones, emails,
national identiers, address, legislative data, accruals, absences, work relation, work term, assignment, work measure,
supervisor, and salary.
To use these extracts, copy and congure them to suit your needs. You must not run the extract template directly.
These extracts are complex and detailed. They can extract a huge volume of data and can be time consuming as they
are designed on historic user entities to return all the details irrespective of the eective date.
When using these extract templates, ensure the following to avoid unneeded and time consuming data retrieval:
• Dene lter criteria. For example, if you want to extract data related to specic locations, include an expression
or fast formula in the data group lter conditions.
• Remove unwanted data groups. For example, if you are not interested in positions, then you can remove the
positions data group.
• Review all the details to ensure all the information is relevant to your needs.
Using Work Structure and Worker Extract Templates

To use the Worker or Work Structure extract templates:
1. Copy the Worker or Work Structure extract denition to create a new extract.
2. Update the copied extract.
3. Generate and compile fast formulas.
4. Validate the extract design.
5. Rene the parameters.
Dene Extracts
This example demonstrates the steps required to create an extract denition using the Desktop interface. You can
access the Desktop interface by clicking the Switch Layout buon on the Manage HCM Extract Denitions page. Before
you create an extract denition, you should understand the following details:
• Information that you want to extract

• Structure in which the data must be extracted
• How you want to deliver this data (including le format, delivery mechanism, and frequency information)
FAST bank is a global organization with subsidiaries all over the world. As part of an external business reporting
requirement, FAST bank is required to extract the department and employee details (grouped by department) across
the entire company. This information must be sent to a third party in an XML le and to HR Managers in a PDF le using
email. The following table summarizes the key decisions in this scenario:
471
How many extracts do I create to You create one extract denition to dene a headcount report.
produce this type of report?

How many data groups do I create? There are 2 functional groups of information, therefore you create two data groups, one for
department and one for employees.

How many records do I create?

You decide the number of records based on the subgroup of aributes within a data group. In
this example, you create two records for the department data group:
• Department Details
• Department Summary
You create one record for the employees data group: Employee Details.
How many aributes do I create?

You decide the number of aributes based on the specic information required for that report.
Create the following aributes for the Department Details record:
• Department Name
• Department Location
For the Department Summary record, create the following aributes:
• Record Code
• Report Date
• Employee Count
For the Employees Details record, create the following aributes:
• Full Name
• Gender
• Date of Birth
• Salary
• Bonus
• Tax Rate
Do I create any fast formulas?

You can use fast formulas at the following levels:
• Extract Criteria level to determine certain conditions.

• Extract Rule level to derive aribute values.
• Extract Advanced Condition level to specify complex conditions.
• Extract Record level to automatically generate formulas when you use the Generate
Formula option.
Creating an Extract Denition

1. On the Manage HCM Extract Denitions page, click Create.
2. Use the Switch Layout buon to open the extract in the Desktop interface.
472
3. Enter 01-Jan-2000 as the Session Eective Date.

The session eective date is an eective start date that applies to all date-eective interactions in the current
session.
4. Enter FAST Bank Extract as the name and select HR Archive as the type. The application automatically creates
the tag name based on the extract name and uses this name to generate the XML output le.
5. Click Save. The application saves the extract denition and automatically generates the parameters based on
the type of extract. The parameters control the output of an extract. In this example, the application creates the
following parameters:
◦ Eective Date
◦ Legislative Data Group
◦ Parameter Group
◦ Report Category
◦ Request ID
◦ Start Date
Creating Extract Data Groups

1. Select the Extract Data Group link from the navigation tree to open the Extract Data Groups region.
2. Click on Create to dene a new data group. A data group represents data that belongs to one or more logical
data entities.
3. Complete the elds to create a data group, as shown in this table:
Field Name Entry
Name Departments

User Entity PER_ EXT_ SEC_ ORGANIZATION_ UE

Root Data Group Yes (By selecting this option you select this data group as the starting point for the extract
execution.)

4. Select Save and Create Another to create a data group for Employees.
5. Complete the elds to create a data group, as shown in this table:
Field Name Entry
Name Employees

User Entity PER_ EXT_ SEC_ ASSIGNMENT_UE

Root Data Group No

473
Creating Extract Data Group Connections

1. Select Extract Data Group in the navigation tree to display the data groups in a table.
2. Select the Employees Data Group and dene the data group connection details.
3. Complete the elds to create a data group connection, as shown in this table:
Field Name Entry
Parent Data Group Departments

Parent Data Group Database Item PER_ EXT_ ORG_ ORGANIZATION_ ID

Data Group Database Item PER_ EXT_ ASG_ORG_ID

4. Dene the data group criteria for each data group.
Creating Extract Records

1. Select the Departments Data Group from the navigation tree and select the Create icon in the Extract Records
region. Extract records represent a physical collection of all required elds. If a data group has 3 records, then
you can specify the sequence in which the application processes the records using the sequence eld. You can
also select the Next Data Group to identify which data group the application processes next.
2. Create two records for the Departments data group.
3. Complete the elds to create two records for the Departments data group, as shown in this table:
Field Department Summary Department Details
Name Department Summary Department Details

Eective Start Date 1/1/00 1/1/00

Sequence 20 10

Type Trailer Record Header Record

Process Type Fast Formula Fast Formula

Next Data Group NA Employees

474
4. Save the records, then select the Employees Data Group and select the Create icon in the Extract Records
region.
5. Create one record for the Employees Data Group.
6. Complete the elds to create a record for the Employees data group, as shown in this table:
Field Name Entry
Name Employee Details

Eective Start Date 1/1/00

Sequence 10

Type Detail Record

Process Type Fast Formula

Creating Aributes
1. Select the Departments Data Group from the navigation tree and select the Department Details record.
An extract aribute is an individual eld of a record.

2. Create the following extract aributes for the Department Details record and select Save.
3. Complete the elds to create extract aributes for the Department Details record, as shown in this table:
Field Name Aribute Entry Aribute Entry
Name Department Name Department Location

Type Database item group Database item group

Database Item Group Organization Name Organization Location Country

4. Save the record, then select the Department Summary record.

5. Select the Create icon in the Extract Aributes region.
6. Create the following extract aributes for the Department Summary record and select Save.
7. Complete the elds to create extract aributes for the Department Summary record, as shown in this table:
Field Name Aribute Entry Aribute Entry Aribute Entry
Name Record Code Report Date Employee Count
475

Data Type Text Date Number

Type String Parameter Element Summary Element

String Value 999 NA NA

Parameter Eective Date NA NA

Aggregate Function NA NA Count

Aggregate Record Name NA NA Employees Employee Details

8. Select the Employees Data Group from the navigation tree and select the Employee Details record.
9. Create the following extract aributes for the Employee Details record and select Save.
10. Complete the elds to create extract aributes for the Employee Details record, as shown in this table:
Name Full Name Gender Date of Birth

Start Date 1/1/00 1/1/00 1/1/00

Data Type Text Text Date

Type Database Item Group Decoded database item Database item group
group

Database Item Group Person Full Name Person Gender Person Date of Birth

11. Complete the elds to create more extract aributes for the Employee Details record, as shown in this table:
Name Salary Bonus Tax rate

Start Date 1/1/00 1/1/00 1/1/00

Data Type Number Number Text
476

Type Database item group Record Calculation Rule

Database Item Group Assignment Salary Amount NA NA

Calculation Expression NA Salary * 0.5 NA

Rule NA NA FAST Bank Tax Rule

Dening the Delivery Options

1. Navigate to the Extract Execution Tree to validate the extract denition setup.
2. Select Export XSD to download the XML Schema Denition (.XSD) le for this extract setup. This exported le
contains the structure of the extract denition: the data groups, records, and aributes.
3. Select the Extract Delivery Options region to dene the formaing and layout options for the extract denition.
4. Complete the elds for the delivery options, as shown in this table:
Field Value Value
Start Date 1/1/00 1/1/00

End Date 12/31/12 12/31/12

BI Publisher Template ReportLayout EFTLayout

Output Type PDF EFT

Delivery Type Email FTP

Delivery Option Name Email to HR FTP to 3rd Party

Output Name HeadcountReport EFTReport

5. Dene further information for each delivery option in the Additional Details region. For example, add the
server, username and password for the FTP delivery type.
6. Enter FAST Bank Extract as the reporting category and click Submit.
477
Submiing an Extract
An extract denition automatically creates an extract process (payroll ow) with the same name as the extract. The
extract process enables you to dene an execution sequence of multiple tasks, including before and after tasks.
1. Select the Submit Extracts task and select the FAST Bank Extract process.
2. Select Next.
3. Enter FAST Bank Extract - Jan 2012 as the Payroll Flow (extract process).
4. Enter 1/1/15 as the End Date.
5. Select Next. You can specify interaction details if the task is dependent on other tasks with dierent extract
processes. For example, this task must wait because another task is running.
6. Select Next and review the extract. You can schedule the extract, or run it immediately.
7. Select Submit.
8. Select OK and View Checklist to view the status of the process.
9. Select the View Extract Results task to review the results of the extract run. Search for the FAST Bank Extract
process.
10. Select Go to Task for FAST Bank Extract - Jan 2012, click the eyeglasses, and view the report output by selecting
the report name.
Related Topics
• Guidelines for Delivering Extracts
• How do I create a BI Publisher template for HCM extract
Dene Extracts in the Simplied Interface

This example topic demonstrates how to create a HCM extract including creating data groups, records, and aributes
using the Simplied interface. FAST Bank is a global organization with subsidiaries all over the world. As part of an
external reporting requirement, FAST Bank must obtain the department and employee details across the entire
company. This information must be sent to a third party in an XML le and to the HR manager with employee details
grouped by department as a Headcount Report.
The following table summarizes the key decisions in this scenario:
How many extracts do I create to You create one extract denition to dene a headcount report.
produce this type of report?

How many data groups do I create? There are 2 functional groups of information, therefore you create two data groups, one for
department and one for employees.

How many records do I create?

You decide the number of records based on the subgroup of aributes within a data group. In
this example, you create two records for the department data group:
• Department Details
• Department Summary
478
You create one record for the employees data group: Employee Details.
How many aributes do I create?

You decide the number of aributes based on the specic information required for that report.
Create the following aributes for the Department Details record:
• Department Name
• Department Location
For the Department Summary record, create the following aributes:
• Record Code
• Report Date
• Employee Count
For the Employees Details record, create the following aributes:
• Full Name
• Gender
• Date of Birth
• Salary
• Bonus
• Tax Rate
Do I create any fast formulas?

You can use fast formulas at the following levels:
• Extract Criteria level to determine certain conditions.

• Extract Rule level to derive aribute values.
• Extract Advanced Condition level to specify complex conditions.
• Extract Record level to automatically generate formulas when you use the Generate
Formula option.
Creating an Extract Denition

1. On the Manage Extract Denitions page, click Create.
2. Enter FAST Bank Extract as the name, 01-JAN-2010 as the Start Date, and select HR Archive as the type. The
application uses this name to generate the XML output le.
3. Click Save. The application saves the extract denition and automatically generates the parameters based on
the type of extract. The parameters control the output of an extract.
Use the Switch Layout buon to open the extract in the Desktop interface. Use the Desktop interface to create
and dene HCM extracts without using a drag and drop system. You can perform most of the tasks for dening
the extract in the Simplied interface.
479
Creating Extract Data Groups and Records

1. Select the Design icon to create the data groups and records.
2. Select the Create icon or use the HCM Data Objects tree to drag and drop a data group into the local area.
3. Using the drag and drop action, drag the Organizations object into the local area. This action automatically
creates an associated record object.
4. Update the data group with the following information:
Field Name Entry
Name Departments

User Entity PER_ EXT_ SEC_ ORGANIZATION_ UE

Root Data Group Yes (By selecting this option you select this data group as the starting point for the extract
execution.)

5. Update the record object and create another using the following information.
6. Complete the elds to create two records for the Departments data group, as shown in this table:
Field Department Summary Department Details
Name Department Summary Department Details

Eective Start Date 1/1/00 1/1/00

Sequence 20 10

Type Trailer Record Header Record

Process Type Fast Formula Fast Formula

Next Data Group NA Employees

7. Select Save and create another data group by dragging the Employees data object to the local area. This action
automatically creates an associated record object.
8. Update the data group with the following information:
Field Name Entry
Name Employees
480
Field Name Entry

User Entity PER_ EXT_ SEC_ ASSIGNMENT_UE

Root Data Group No

9. Update the record object with the following information.

10. Complete the elds to create a record for the Employees data group, as shown in this table:
Field Name Entry
Name Employee Details

Eective Start Date 1/1/00

Sequence 10

Type Detail Record

Process Type Fast Formula

Creating Extract Data Group Connections

1. Select the Link icon on the Employees data group, and select the Add icon to add a connection.
2. Complete the elds to create a data group connection, as shown in this table:
Field Name Entry
Parent Data Group Departments

Parent Data Group Database Item PER_ EXT_ ORG_ ORGANIZATION_ ID

Data Group Database Item PER_ EXT_ ASG_ORG_ID

3. Dene the data group lter criteria for each data group by selecting the Filter icon.
481
Creating Aributes
1. Select the Departments Details record in the Department data group, and within the Congure icon select the
Create Aribute option.
2. Complete the elds to create extract aributes for the Department Details record, as shown in this table:
Field Name Aribute Entry Aribute Entry
Name Department Name Department Location

Type Database item group Database item group

Database Item Group Organization Name Organization Location Country

3. Select the Department Summary record, and using the above method enter the following extract aribute
details.
4. Complete the elds to create extract aributes for the Department Summary record, as shown in this table:
Name Record Code Report Date Employee Count

Data Type Text Date Number

Type String Parameter Element Summary Element

String Value 999 NA NA

Parameter Eective Date NA NA

Aggregate Function NA NA Count

Aggregate Record Name NA NA Employees Employee Details

5. Select the Employee Details record within the Employees data group and using the same method enter the
following extract aribute details.
6. Complete the elds to create extract aributes for the Employee Details record, as shown in this table:
Name Full Name Gender Date of Birth
482

Start Date 1/1/00 1/1/00 1/1/00

Data Type Text Text Date

Type Database Item Group Decoded database item Database item group
group

Database Item Group Person Full Name Person Gender Person Date of Birth

Dening the Delivery Options

1. Select the Deliver icon and then the Add icon to dene the delivery options.
2. Complete the elds for the delivery options, as shown in this table:
Field Value Value
Start Date 1/1/00 1/1/00

End Date 12/31/12 12/31/12

BI Publisher Template ReportLayout EFTLayout

Output Type PDF EFT

Delivery Type Email FTP

Delivery Option Name Email to HR FTP to 3rd Party

Output Name HeadcountReport EFTReport

3. Ensure you enter the additional information such as, the server, username, and password for the FTP delivery
type.
4. Enter FAST Bank Extract as the reporting category and click Submit.
5. View the extract denition details and ensure the structure is valid in the Validate page by selecting the Validate
icon.
6. Select Export XSD to download the XML Schema Denition (.XSD) le for this extract setup. This exported le
contains the structure of the extract denition: the data groups, records, and aributes.
483
Submiing an Extract
An extract denition automatically creates an extract process (payroll ow) with the same name as the extract. The
extract process enables you to dene an execution sequence of multiple tasks, including before and after tasks.
1. Select the Submit Extracts task and select the FAST Bank Extract process.
2. Select Next.
3. Enter FAST Bank Extract - Jan 2012 as the Payroll Flow (extract process).
4. Enter 1/1/15 as the End Date.
5. Select Next. You can specify interaction details if the task is dependent on other tasks with dierent extract
processes. For example, this task must wait because another task is running.
6. Select Next and review the extract. You can schedule the extract, or run it immediately.
7. Select Submit.
8. Select OK and View Checklist to view the status of the process.
9. Select the View Extract Results task to review the results of the extract run. Search for the FAST Bank Extract
process.
10. Select Go to Task for FAST Bank Extract - Jan 2012, click the eyeglasses, and view the report output by selecting
the report name.
Related Topics
• Guidelines for Delivering Extracts
How Extracts are Validated

Use the Validate feature in the Manage Extract Denitions task to ensure the data you enter in the Design tab is valid
and there are no issues when you submit. After creating an extract, go to the Validate tab and click Validate. If there are
any issues in the extract design, validation messages are displayed.
Validating Extracts
When you validate an extract, the application performs validations on the extract design to ensure that:
• The root data group is dened.

• All non-root data groups are linked to the root data group directly or indirectly (for example, through another
non-root data group that is linked to the root data group).
• If a sequence of data groups is dened, then the next data group is also dened for processing.
• All Fast Formulas used in the extract exist and are compiled or valid.
• There are no issues detected during BI Publisher validations.
If the validation is successful, the application marks the extract as valid. However, if the validation fails, the application
marks the extract as invalid and submiing the extract results in errors.
484
Review Extract Run Details

Using the View Extract Run Details task, you can review extract run information and troubleshoot extract runs that are
unsuccessful or have not produced the expected results. In the Search area, use the various lters available to search
the extract or extract run. In the Search Results area, click the extract run that you want to analyze.
In the View Extract Run Details page, you can review the following information:
• Parameters
• Archive details
• Process details
• Changes Only Details
• Delivery options
Parameters
The Parameters tab displays the parameters set for the extract run. For example, Baseline Only, Changes Only, Process
Start Date, Process End Date, Process Conguration Group, and so on. You can also export these parameters to an Excel
Spreadsheet.
Archive Details
The Archive Details tab displays the number of records that were extracted by the extract run.
Process details
The Process Details tab lists the processes and their hierarchy. You can view the process status, start and nish time,
and the elapsed time. You can also download the process log les, which can help you troubleshoot failed or time
consuming extract runs.
Extract Delivery Options

The Delivery Options tab is visible only if you have set the delivery option in the Manage Extract Denitions task as
WebCenter Content or Inbound Interface. If the extract run is submied and completed successfully, you can also
download the output le.
Changes Only Details

Use the Changes Only Details tab to review the change in an aribute from the last successful run. This tab is visible
only when the extract is run in the Changes Only mode. You can verify if the Changes Only parameter was set in the
Parameters tab. Select the aribute and enter the aribute value to check the change in the aribute from the last
successful run.
485
Purge Extracts Archive Information

You can remove redundant archive data to free up space and improve overall performance in your database. Use the
Purge Extracts Archive Data process to remove the unnecessary information.
Here's how you can purge the redundant extracts archive information:
1. Select and search Purge Extracts Archive Data job under Scheduled Processes. The archive data includes the
associated payroll actions, object actions, and action information rows generated by extracts.
2. In the Process Details page, dene the criteria for the purge process by selecting the appropriate values for the
process parameters.
Parameter Name Values Default Value
Report Mode Yes

Yes/No
◦ Yes: Provides details of the archive

data you want to purge
◦ No: Purges the archive data
generated by the selected Extract
List
Extract List Lists the extracts to purge or generate a N/A

report

3. Click Submit.
4. You can search for the job and check the completion status with any scheduled processes.
5. If you execute the process in Report Mode, the output le provides a report including these details:
◦ Extract denition Name

◦ Extract Type
◦ Archive data count
◦ Storage recovered by the purge process
6. Use the details in the report to identify data that you want to clean up from the application.
Note: You can run only one instance of this ESS job at any time.
Related Topics
• Overview of Scheduled Processes
FAQs for Managing Extracts

486
How can I create a changes only extract?

When you create or import an extract, make sure you keep the Changes Only check box selected. This option creates an
extract that captures the incremental changes only and not a full extract. The Changes Only option automatically adds
the Changes Only parameter to the extract. When you run the extract, you can set the value of the parameter to capture
changes. The extract generates the current status of the data, compares it with the baseline data from previous runs
and identies anything new and any modications.
Remember that you also need to set up threading database details to fully implement the changes only behavior.
Related Topics
• What's a threading database item and what is its connection to the extract data group
What's the Simplied interface in HCM Extracts?

The Simplied interface is an easy-to-use graphical interface for dening and designing HCM extracts. You can perform
most of the tasks for dening the extract in the Simplied interface, however to enter an eective date, you must use
the Desktop interface.
What's an extract data group connection?

Data group connections enable you to dene the master-detail of parent-child relationship between the entities. For
example, the Employees and Departments data groups are linked with Department ID.
What's the dierence between the Always Display and the Mark as
Changed aributes?
You can see the dierence between the Always Display and the Mark as Changed aributes when you have a parent
child relationship in the extract. If an aribute is set as Mark as Changed, and a change occurs on the same record, then
the application includes this aribute in the output. If no aributes change on the record, but an aribute changes in
another record, for example a parent or sibling record, then the application does not include the aribute in the output.
If an aribute is set as Always Display and a change occurs on the record or in the hierarchy below the record, then the
application includes this aribute in the output. The application includes the aribute even if there are no changes in
the aribute's record. If there is a change beneath the record, then it's included.
Related Topics
• Guidelines for Using Dierent Modes for HCM Extracts
How can I disable an extract?

You can disable an extract by using the Manage Extract Denitions task in the Data Exchange area. Search for and open
the extract that you want to disable. Change the status of the extract to Inactive. After disabling an extract, you cannot
submit the extract run again. The previous submied runs of a disabled extract are stored and are available for review.
487
Why can't I nd an extract?

Probably because it's a payroll or seeded localization extract which is Legislative Data Group (LDG) enabled and you're
looking in the Data Exchange work area. Search for your extract by LDG using the Show Filters option in the Extracts
Denitions UI. You need to use the Payroll>Checklist work area to submit these types of extracts.
How can I keep an extract safe from unwanted edits?

Keep an extract locked to ensure no edits are made while the extract is in use. The lock feature can help you avoid
situations such as a Changes Only extract being edited while in use and resulting in a full run extract.
Find the Lock Denition option and the Unlock Comments eld on the Dene page. The extract denition must be
valid before you lock it and you must provide a reason before you can unlock it. Unlock the extract denition if it does
require a change by providing a justication.
Why can't I submit an extract run?

You can't submit an extract run when:
• The status of the extract is inactive. An inactive extract indicates that it's disabled. To submit an extract run, the
status must be Active. Inactive extracts are not available for submission in the Submit Extracts task.
• The extract is invalid. After creating an extract, if you validate it and there are some validation errors, the extract
is marked as invalid. If you try to submit an invalid extract, the process fails and errors are displayed. Resolve
the validation errors and validate the extract. Then submit the extract run again.
Why can't I nd my inactive extracts?

You can't nd the inactive extracts because by default, the search results display active extracts only. To view inactive
extracts, use the Manage Extract Denitions task in the Data Exchange work area. In the Search page, select Inactive in
the Status drop-down list and click Search.
If you want the search results to display both active and inactive extracts, select the blank option in the Status drop-
down list.
Do I have to validate existing extracts?

No. It's not required to validate existing extracts. Extracts that are not validated are marked as Not Yet Validated. You
can submit extracts that are not validated. However, if there are issues with the extract design, then errors may occur or
the result data may be incorrect. To avoid any errors, ensure that you validate the extract before submiing.
488
How can I download log les for the extract run processes?
Use the View Extract Results task. Search for the extract and select an extract run. In the Details area, the Process Details
tab lists the extract run processes. You can download the log le for any process using the Log column. You can review
the log les to identify the records that did not retrieve the expected data and to identify time consuming processes.
Can I use a user entity as a root data group?

Search for the user entity in the View User Entity Details UI. If it is a multiple row user entity and does not require any
context, you can use this user entity as the root data group.
You can access the View User Entity Details UI:
• From the Data Exchange tasks pane.

• When creating a data group in the Design tab of the Manage Extracts Denitions task.
Can I run a changes only extract with successful runs only?

Yes. Use the Include changes from last successful run option to exclude the extract runs that did not complete
successfully when you run a changes only extract. Leave the option unchecked if you want the application to include
both the archives from extract runs that completed successfully and those that completed unsuccessfully when you run
a changes only extract.
How can I create and run a baseline extract?

Use the Baseline Only parameter in your extract to create a baseline for which you can run all subsequent changes only
extracts against. This parameter can save time when running the extract because it doesn't generate an XML le and it
doesn't deliver any output. You set the Display option to Yes or Mandatory for the Baseline Only parameter. It creates a
full extract in less time and uses less storage in your application.
Can I create an extract and delete the archives?

Yes. When you create a full extract of data, use the Delete Archive parameter to give you the exibility of deleting
archive and XML les at a later date. Set the Display option to Yes or Mandatory for the Delete Archive parameter. The
application generates the archive and XML les and delivers them to the destination, for example, WebCenter Content.
The Delete Archive parameter provides you with options to delete the archives and XML les after the application
delivers the extract data to its destination. After the application delivers the output, for example, to WebCenter Content,
you have the option to discard the archive data and XML les, therefore reducing storage consumption by deleting
these extract archives.
You also have the exibility to choose whether you discard all the data an extract generates, for example, use the Delete
archive information and generated XML option to remove all unnecessary data. Or you can choose the Delete archive
information only option to remove the archive data and retain the generated XML data. You may want to keep the XML
data for reporting purposes or for future references.
489
How can I improve the performance of the application during

integration testing or when bulk data loads run?
Contact your support representative and request them to manually gather the database table statistics for your
pod. You may experience slow HCM Extract operations during certain testing phases of your implementation cycle,
especially when the application tests bulk data loads at the same time. During regular operations the collection of
statistics is scheduled to run weekly. However, if the data volume is high due to bulk data loads, then you should
request this process to run manually.
490
Integrating with HCM Filtering and Delivering HCM Extracts
35 Filtering and Delivering HCM Extracts
Guidelines for Using Dierent Modes for HCM Extracts

You can create an extract to output data in dierent modes in the Manage Extract Denitions page. Use modes to
extract data that has changed since the previous extract runs. For example, you can extract employee details whenever
there is a change in the employee's location. The processing engine generates the current status of the data, compares
it with the base-lined data of the previous runs, and identies the new as well as any modications. The output from
such changes-only extract has the incremental data only.
You can manipulate the output in a changes-only extract to either exclude or include certain aributes, regardless of
whether the aribute has changed or not. For example, by selecting an option to exclude an aribute from comparison,
you can ensure that that aribute is not compared while identifying changes to include in the generated output of the
next extract run. Therefore, even if the aribute has changed since the previous extract run, it will not be included in the
output. You can also select an option to always include an aribute in the generated output of an extract run, even if the
aribute has not changed.
Extract Modes
To enable dierent modes in an extract, you include the CHANGES_ONLY parameter and set up threading details in
the extract denition. While running the extract you can use the CHANGES_ONLY parameter to control the extract
mode. For example, to nd out if the job name has changed on a person's assignment, set up multi-threading database
items at assignment level and include the CHANGES_ONLY parameter. When you run the extract in the ATTRIBUTE
mode, the extract compares data from the multi-threading level and outputs the incremental changes. You can link the
PER_EXT_CHANGES_ONLY lookup or the ORA_HRY_CHANGES_ONLY lookup to the CHANGES_ONLY parameter so
that you can select a mode when you submit the extract.
The following table describes the dierent extract modes, their lookup values and descriptions.
Mode Lookup Value Description
N All aributes Includes all data in the extract. A full

extract is run which produces the full data
output at that point of time. The archived
data is utilized as a baseline.

Y Changed aributes Compares this extract run with the

previous extract runs and by comparing
against the baseline (to identify the
incremental data), displays the data that
has changed only.

ATTRIBUTE Changed and marked aributes Includes elements that have changed or
marked as mandatory

491
Mode Lookup Value Description
ATTRIB_OLD Changed and marked aributes with Displays elements that have changed or
previous values marked as mandatory plus their previous
value

Note: You must run the Payroll
Interface with the Arib_ Old mode
whenever you use the US ADP
PayForce Third-Party Periodic
Extract.

BLOCK_OLD Changed, marked aributes, previous data Displays the following data under
under threading group threading data group:

Changed data

Data marked as mandatory

Previous values

Parent data group values

BLOCK Changed and marked aributes under Displays the following data under
threading group threading data group:

Changed data

Data marked as mandatory

Parent data group values

Filter Extracts Using Advanced Filter Criteria

Use advanced lter criteria to lter and extract data using complex SQL queries. You can also lter data using
expressions or fast formulas. When using expressions, the available operators may not be sucient to build complex
expressions. You can use fast formulas to build complex lter criteria. However, using advanced lter criteria can
improve the performance of the extract run. To use advanced lter criteria, you must have good understanding of the
table aliases and writing SQL constructs.
Extracting Employees on Leave

This example explains how to use advanced lter criteria to extract employees who are going on leave in the next seven
days. Managers can use this information to nd the list of employees who have approved leaves starting in the next
seven days.
1. On the Manage HCM Extract Denitions page, create an extract denition and use the Switch Layout buon to
open the extract in the Professional interface.
492
2. Select the Data Group link from the navigation tree to open the Data Groups page, and click Create.
3. Select the user entity PER_EXT_SEC_PERSON_UE and click Advanced.
4. In the Query tab, review the user entity tables and aliases that you want to use, and click OK.
5. In the Data Group Filter Criteria area, click Add.
6. Click the Edit icon in the Filter Criteria column.
7. In the Edit Filter Criteria Condition window, create the following expression for retrieving only employees:
Extract Person System Person Type = 'EMP'
8. Click Advanced. The application converts the expression in the basic mode to the following SQL construct:
(pptum.system_person_type='EMP')
9. You can now append new SQL construct by using the EXISTS clause. Entering the following SQL construct will
extract employees who are going on approved leave in the next seven days:
((pptum.system_person_type='EMP') and EXISTS
(
select 1 from fusion.ANC_PER_ABS_ENTRIES abs
where
abs.person_id = pptum.person_id and abs.start_datetime between
pay_report_utils.get_parameter_value_date('EFFECTIVE_DATE') and
(pay_report_utils.get_parameter_value_date('EFFECTIVE_DATE')+7)
and abs.approval_status_cd = 'APPROVED'
)
)
When writing an SQL query, if you want to retrieve any parameter value at run time, use the
'pay_report_utils.get_parameter_value_date('ESS PARAMETER')' function. The ESS Parameter is typically,
unless explicitly modied, the capitalized parameter name where any space is replaced by an underscore. For
example, the ESS Parameter of Eective Date is EFFECTIVE_DATE.
Note: You cannot use more than 2000 characters to write the SQL query.
10. To validate the SQL construct for any syntactical errors, click Validate.
11. Click OK.
12. To verify if the advanced SQL criteria is applied correctly, run the extract in GMZFT logging mode and check the
logs.
HCM Extract Formula Types

You can launch the Manage Fast Formulas UI from the Navigator Menu Payroll Calculation work area Clicking on the
task Manage Fast Formulas.
The following table lists the dierent types of formula you can use for extracts:
Formula Type Description
Extract Criteria Formulas of this type are listed in the Data Group Criteria Fast Formula list. Use this type to
specify complex criteria and to indicate if record should be extracted or not.

Extract Rule Formulas of this type are listed in the Rule Type Aributes Fast Formulas list. Use this type to
calculate and derive the aribute value if based on complex logic or business rules.
493
Formula Type Description
Extract Advanced Condition Formulas of this type are listed in the Record Aribute Fast Formulas list. Use this type to
specify complex conditions to indicate if an action should be raised (for example, a log or
warning).

Extract Record Formulas of this type are generated automatically when using the Generate Formula option in
Extract Records.

Guidelines for Delivering Extracts

You specify delivery options as part of the extract denition. Delivery option parameters specify the output format, the
delivery method (email, FTP), and other parameters required for integration with BI Publisher layer.
How Delivery Options Work

HCM Extracts archives the extracted data into result tables and stores it as an XML output in the database. The
application transforms the XML output into a formaed output such as HTML, PDF, EDT, or XLS. The formaed output
is then delivered through email, fax, FTP, or print, depending on the delivery options you set in the extract denition.
You can dene delivery options for an extract using a BI Publisher template, with the following delivery le output types:
PDF, XLS, XML, DOC, and the following delivery modes: FTP, email, and fax.
Using Delivery Types

The type of delivery you select determines the destination of the extract. Some delivery types require additional
information. You can select Documents of Record as the delivery mode to store the output in the database and allow
employees to view the output from document of records. An example of a document is a payslip. If the XML output is
split and burst as separate les, then you can select the bursting node. For example, if you want all employees to receive
an email with their payslip, then set the bursting node to Employee_ID. Select the WebCenter Content delivery type to
create extracts with encrypted or non-encrypted data and transmit them to Oracle WebCenter Content. You can then
transfer the data manually or using your own scripts to your own server. For more information, see Oracle Fusion File
Transfer Automation and Data Security on My Oracle Support.
Dene the BI Publisher Template in HCM Extracts

This example shows you how to set up a BI Publisher template and create a document in the required format, using the
extracted data. You can nd BI Publisher using the Reports and Analytics link from the navigator. When the Reports and
Analytics page is accessible, you can browse through the catalog.
FAST bank must send an XML le on their employees and departments to a third party and the HR Manager with
employee details grouped by departments as a Headcount Report.
The following table summarizes some key decisions:
494
Decisions to Consider In this Example
Why do I have to set up BI Publisher? You set up BI Publisher to format the extracted XML data into the required format and to
deliver the report or business document to the appropriate destination.

How does BI Publisher connect to You install the Template Builder for Word plug-in.
HCM extracts?

Do I need a separate license? No, BI Publisher is included with Core HR.

Tasks
1. Seing up the Data Model

2. Creating the BI Publisher Report Template
3. Uploading the Report
Seing up the Data Model

1. Select the Reports and Analytics option from the navigator.
2. Select the Browse Catalog icon.
3. Select the New menu option, and under the Published Reporting section, select Report.
4. Select the Use the existing data model option to create a report using the existing data model.
5. In the window that displays, select the data model and select Next.
6. Select the Report Editor option and select Finish to complete the data model setup.
7. Save the report as HR Data Report in the following folder: /Shared Folders/Custom/Human Capital
Management/
Creating the BI Publisher Report Template

1. Install the Template Builder for Word plug-in from the BI Publisher Enterprise Home page.
This plug-in provides sample documents, demos, templates and Template Viewer. Use these samples to help
you understand the concepts and to create templates such as EFT and RTF to view the formaed XML output.
2. Create a BI Publisher template using the Export XSD option in the extract execution tree.
3. Open MS Word and locate the Add-Ins tabbed region to view the Oracle BI Publisher option.
4. Select the Load XML Schema option. After the XML schema has loaded, you can arrange the elds and alter the
layout, if required.
Uploading the Report

1. Select the Upload option from the Upload or Generate Layout region and enter the following information:
495
Parameters Details
Layout Name RTF Layout

Template File Select the le name of the RTF template saved on your local drive.

Type RTF Template

Locale English (United States)

2. Save the BI report in the following location: /Shared Folders/Custom/Human Capital Management/.
This BI Publisher report template is now ready for you to select in the Delivery Options section when creating
the extract denition.
Related Topics
• Dene Extracts in the Simplied Interface
Best Practices for Delivering Encrypted Data Using HCM

Extracts
You can deliver encrypted les using HCM Extracts to Oracle WebCenter Content. You use the WebCenter Content
delivery type in the Deliver page of the Manage Extract Denitions task to create an encrypted extract. HCM Extract
transfers the encrypted le to Oracle WebCenter Content. You can then transfer the les manually, or write scripts to
perform the transfer. By selecting the WebCenter Content delivery type you can enter additional details to ensure the
extract is identiable in Oracle WebCenter Content. For example, specify the integration name, select whether you want
to encrypt the le using the encryption mode, and a le name for your reference. This additional setup ensures the
document has the correct encryption mode and is stored in Oracle WebCenter Content with a specic le name. For
more information, see Oracle Fusion File Transfer Automation and Data Security on My Oracle Support.
FAQs for Filtering and Delivering HCM Extracts

How can I restrict the records to be extracted?
You can use extract data group criteria to dene a set of ltering conditions the application performs on an extract data
group. For example, you can use database items in the fast formula to represent the town_or_city and primary_ag
columns in the per_addresses table to restrict the data to people living in London only. The extract denition would then
exclude people with a primary address of anywhere other than London. You can specify the criteria conditions using an
expression or fast formula.
496
Related Topics
• Dene Extracts
What's a threading database item and what is its connection to the

extract data group?
A threading database item is required for implementing the Changes Only feature. The threading database item is a
unique ID in the chosen user entity. Generally, for Pay Employee user entity and Assignment user entity it would be
DBI with %ASSIGNMENT%ID. For Person user entity, it would be DBI with paern %PERSON%ID. You can declare one
threading database item at the root data group or any child data group level. For example, you declare the threading
database item from the location where you need changes only.
What's a conditional action?

A conditional action identies the action to perform, and optionally, a message based on the outcome of a conditional
expression or a predened fast formula. Conditional actions are applied on the extracted data similar to criteria
conditions that are applied prior to extraction. Actions and messages are predened in lookups, and you can add your
own messages by creating new values for the lookup.
When a condition is satised, you can use this feature to perform certain predened actions. For example, you can
exclude employees that satisfy a condition, such as all employees from a predened country. You can also congure
this feature to raise a warning when an employee's salary is blank or beyond a specic level.
What's an exclusion rule?

You can't exclude or override a record that doesn't suit your requirements with your own record by using an exclusion
rule. The extract process doesn't process excluded records based on the legislative data group.
What is extract data group ltering?

Extract data group ltering lters data extracted in the data group. You can specify to lter data group as an expression
or as fast formula, and you can choose one or both. You can build criteria using the available database items,
parameters and operators (conditional and logical). The lter criteria will be more ecient as it gets appended to the
User Entity SQL at the time of execution. If you can't specify the criteria as an expression, then you can place logic inside
a fast formula and select here. Fast formulas return values of Y or N to indicate if you must extract the record or not. If
both criteria and formula are specied, then both the conditions are applied.
What are extract data group criteria?

You can specify the lter conditions of what data you want to archive by using the data group criteria. You can specify
the lter conditions as an expression or fast formula.
497
Can I use Oracle Fusion Transactional Business Intelligence (OTBI)

with HCM Extracts?
Yes. You have two options:
HCM Extracts can extract the data and produce an output using CSV, XML, or PDF. OTBI can then accept a data source
in Excel or XML format.
BI Publisher can also accept a data source in Excel or XML format. HCM Extracts has integration with BI Publisher.
What's BI Publisher and how does it work with HCM extracts?

BI Publisher is a set of tools you use to create highly-formaed reports based on data models. With BI Publisher, you
can:
• Author, manage, and deliver documents
• Create interactive management reports
• Create highly-formaed, customer-facing documents
• Create government documents
• Create electronic funds transfer (EFT) documents
BI Publisher transforms the extracted data from the database and presents that data into a report.
How do I create a BI Publisher template for HCM extract?

You create a BI Publisher template using the Export XML Schema option in the extract execution tree and saving the
le to your local computer. You can then load the downloaded XSD le to the BI Publisher word plug-in using the XML
Schema option. If you require a report in a specic format, then you can create a template and save it by arranging the
elds in the required format. Otherwise, you can create a default RTF template using the All Fields option.
How can I disable bursting?

To disable the bursting feature in the BIP report and deliver a consolidated output:
• Select None as the delivery type on the Deliver page when creating a delivery option for the HCM extract.
• Select Disable in the Bursting eld to disable the bursting options associated with the BIP template.
How can I reduce the size of my extract output?

You can use the compress feature to reduce the size of your output and encrypt your extracts more eciently.
Compressing the extract speeds up large le transfers, uploads, downloads, and uses less disk space. With the
WebCenter Content delivery option, select a compression option that works for you:
498
• Yes Compress First. This is the most ecient way to ensure the extract runs quicker. The compression results
in a smaller le, which reduces the overall time it takes to transmit the le to its destination. With this option,
the application compresses the le rst and then encrypts it.
• Yes Encrypt First. Select this option for the application to encrypt the le rst and then compress it.
• No. This option doesn't compress or encrypt the le.
Does a delivery option have to complete for an extract to run

successfully?
No. Use the Required option in the Extract Delivery Option table to specify which delivery options you need to run
successfully in order for the extract run to succeed. For example, use the Required option for critical delivery options
such as payroll bursting. If this delivery option fails, then the extract run will also fail because it is dependent on the
delivery option completing successfully.
You can also use the Required option for any delivery options you deem as not critical for the extract to run
successfully. For example, deselect the Required option for a delivery option such as an email notication to yourself.
If this delivery option fails, then the extract run will complete successfully because it is not dependent on the delivery
option.
Why does my extract show a dierent time zone?

HCM Extracts uses the eective date to dene the session date for a given extract run. The application uses this
eective date to compare the eective start and eective end date aributes to lter the data it needs to process.
The eective date (the session date) is the date set with the user time zone preferences. For example, if you run an
extract with an eective date of 02-Jan-2018, with user time zone preference set to BST time zone, then the application
retrieves the records created with an eective start date of 02-Jan-2018. Even if you create the data or perform a
transaction on 01-Jan-2018 (or other dates), the eective start date here determines whether or not the transaction
qualies for the extract processing. The database stores the date with the time stamp in the UTC time zone for the
aributes of the standard WHO columns. The date eective aributes (eective start date and eective end date used
by the date eective feature in HCM Cloud) store the time without any time zone information.
Related Topics
• Can I add or edit time zones
• Set General Preferences for All Users
499
500
Integrating with HCM Flow Paerns
36 Flow Paerns
Flow Paerns for Extracts and Reports

A ow paern exists for each extract or report process. Flow paerns for extracts and reports typically contain a single
ow task and they dene the submission parameters. Use the Manage Payroll Flow Paern task from the Payroll
Checklist work area or the Rene Extract task in the Data Exchange work area to edit ow paerns. You can edit a ow
paern to add additional tasks. Each ow paern you create must be associated with a security prole.
Checklist and Flow Tasks

When you submit a ow paern it creates an instance of the ow. For every submied ow, the application generates a
checklist by default. The ow can be a task ow, process, or report.
Here's what the checklist might include, depending on the ow paern.
• Automatic tasks, such as extracts, reports, and processes

• Manual tasks, such as the Verify Payroll Process verication task, required to complete a ow
Here's what you can do with checklists.
• Monitor the status of the ow tasks

• Manage the ow tasks, such as reassigning tasks, marking tasks as completed, and performing corrective
actions
• View task details, such as a list of records processed by the ow
While working on a task in the ow, you can remain in the Payroll Checklist work area or go to a related work area that
includes tasks in the regional area. For example, while reviewing the results for the Calculate Payroll task, you can go to
the Payroll Calculation work area to review the person's calculation card or element entries.
How Flow Paerns are Edited

You can create or copy a ow paern and then edit add, delete, or move a task in the ow paern. This topic provides
examples of edits you can perform to tasks in a ow paern or checklist.
Perform these edits on the Task Sequence tab of the Manage Payroll Flow Paerns page. For payroll ow paerns, use
the Manage Payroll Flow Paerns task. For extract ow paerns, use the Rene Extracts task.
Edit Tasks
Here's a list of examples of edits you can perform and the probable impact the edits can have on the ow.
501
Edits Impact Examples
Add a task You add a task to position it as the last You add a manual verication task after
task in the activity or task group. Update each report. You rename each task with
the task sequence. the report name.

If you repeat a task, rename it to make
clear its purpose on the checklist.

Delete a task When you delete a task you may impact You delete a task. The Parameter Basis of
subsequent tasks in the ow that depend the next task is Bind to Task and its Basis
on its results. Review the subsequent Value is the value of the deleted task.
tasks. You update the Parameter Basis of the
subsequent task as required, for example,
to Bind to Flow.

Move a task to a dierent activity The activity determines the work areas You move a task in a payroll ow paern
where you can submit the ow paerns for a report from the Payments activity to
you dene, and controls how the checklist the Statutory activity.
displays.

Reorder the list of tasks displayed in a The sequence specied for the task
checklist further determines the task order within You decide to aen the checklist
an activity on the checklist. sequence to group all the tasks within a
single activity.
1. On the Tasks page, you conrm

that each task belongs to the same
activity and task group.
2. You edit each task, specifying a
value in the Sequence column on
the Edit Task Details Owners and
Details page.
The lowest number is used for
the rst task in the checklist. For
example, you might specify a
sequence of 10 for the payroll
calculation task and 20 for the
prepayments calculation task.
Flow Paern Parameters

Each task in a ow paern supports task actions, such as submit, roll back, mark for retry, retry, and view. Task action
parameters control how the application processes a task and how the task relates to other tasks in the ow paern.
Flow parameters are a subset of task action parameters. They supply the information required to successfully complete
the tasks in the ow paern.
• When you create a ow paern, review and edit the task parameters for the Submit and Initialize task actions.
• Before you submit a ow, review and edit the task action parameters and the ow parameters for each task
within the ow. Task action parameters control task interactions.
502
• After you submit the ow paern, edit the parameters for the remaining task actions, such as Mark for Retry,
Retry, and Roll Back, as required.
This gure illustrates the relationship of the tasks, task action parameters, and ow parameters in a ow paern.
Flow Pattern
Task Task Task
Task Action Task Action Task Action
Task Action Task Action Task Action

Parameters Parameters Parameters
Use as Flow
Parameters?
Flow Parameters
Here are the parameter details you can edit:
• Display and display format

• Lookups and value sets
• Usage
• Sequence
• Parameter Basis and Basis Value
503
Display and Display Formats

Display parameters control the format and availability of the ow parameter, as shown in this table.
Parameters Purpose
Display Determines whether the parameter displays on the page when you submit the ow.

Display Format Identies the type of data displayed, such as a date or text, or choice list

Display parameters work with other parameters, such as Parameter Basis and Basis Value. For example, most task
action parameters don't display the Request parameter because the application obtains the value for this parameter
from the context.
Lookups and Value Sets

Use lookups and value sets for descriptive exelds to control and validate the data used in the payroll ow paern.
This table lists the methods by which the lookup values are derived and the corresponding parameter basis you can use.
Lookup Value Parameter Basis
Entered when submiing a ow Bind to Flow

The application derives the value SQL Bind or Bind to Flow Task or Context Binding
during ow submission and presents
it. The value is derived from existing
tables, such as the value for the
payroll statutory unit. During ow
submission, you can either use the
value presented to you or override it.

The application derives the value Post SQL Bind

from a Post SQL process

Usage
A parameter can receive information or generate information that subsequent tasks can use. For example, for the
Calculate Payroll task, the Payroll Process parameter for the Submit task action generates an output value for the payroll
action ID. The Retry task action can use this payroll action ID.
Here's the typical seings for a parameter whose usage is output. For output usage parameters the parameter isn't
displayed and its value is derived using the parameter basis.
504
Parameter Option Seing
Display No

Parameter Basis • Bind to Flow, the application derives the value from the ow parameter and then
updates the ow parameters table with the output value
• If you select no value, the output value results from the task's output
Sequence
Sequence numbers control the order in which the application processes and displays the parameters by specifying the
sequence. For example, if you have two lookups and the values of the second lookup depends on the rst lookup. You
must set the rst lookup to a lower sequence number than the second one.
Parameter Basis and Basis Value

The parameter basis controls how the application derives the value for the parameter. The basis value further species
the value the application uses for the parameter.
Here's the list of values to select parameter basis and basis values when you dene payroll ows. The table provides
examples when you can select them and describes how the values are assigned.
Parameter Basis Description Basis Value Available Example
Use Specied Value Assigns a specic value to the Enter the text as a constant or Specify a constant if the value
parameter. value, when you submit the is the same for all tasks, such
ow. as the payroll statutory unit.

Bind to Context Derives the value from the Select ow, task, or the If the task includes a Request
context of the current ow Request. The application parameter, bind it to the ow
instance or the task instance automatically generates the context. Tasks in the ow
of the ow paern. parameter value. reference this task using the
Request ID generated by the
application.

Bind the legislative data group
parameter to a task parameter
that supplies the legislative
data group.

For example, the legislative
data group for prepayments
uses the payroll as context,
because it's already associated
with the legislative data group.

Bind to Flow Parameter Derives the value from one of Application automatically Bind a parameter to the ow
the ow parameter values. derives the parameter value. that several tasks share to
avoid multiple occurrences of
the same parameter.

505
Parameter Basis Description Basis Value Available Example
Bind to Flow Task Parameter Binds the value to the output Select a value from the Bind a parameter to a task,
of the previous task. previous task's parameters. such as Retry corrective
action. When the ow owner
resubmits the task to retry
it, the application uses the
output of the Submit task
parameter.

Bind to Task Parameter Resolves the value for the task Select a value from the current Bind a parameter to the
parameter. task's parameters. task if several tasks share a
parameter, such as a start
date, but one task requires a
dierent date.

No value specied Stops the application from Application generates a blank Not applicable
generating a parameter value value.
when the task executes.

Post SQL Bind Calculates the parameter but SQL statement calculates the Bind a parameter using the
doesn't display it on the user parameter value. Post SQL bind to generate
interface. data.

For example, use a post SQL
process to use the payroll
period and payroll parameters
and generate the process date.

SQL Bind Calculates and displays value SQL statement calculates the Bind a parameter using SQL
on the user interface, prior to parameter value and display
submission. it on the user interface, before For example use SQL Bind to
submission. calculate the payment type
parameter for the Generate
Check Payment task. The
application obtains the
payment type ID for the check
payment record.

Use SQL Bind to prompt the
task owner to enter a reason
for a corrective action, such as
a QuickPay.

Flow Task Start and Due Dates

Use duration dates and notication options in the payroll ow paern to give ow owners adequate time before a task
starts, to prepare and address any issues.
506
Task Start and Due Dates

Let's look at the duration dates you can enter on the Tasks page of the Manage Payroll Flow Paerns page:
• Start date, the date the task owner should start the task.
Note: The start date applies to notications only. Enter the ow start date on the Scheduling page
when you schedule the ow.
• Due date, the date the task owner should complete the task.
To specify duration dates:

1. Select the ow parameter date to use as the basis for the duration date.
2. Optionally, oset the date by specifying a plus or minus value depending on whether the date falls before or
after the duration date.
Notications
Notications are error and warning messages to inform the task owner when a task starts or ends. The receipt of
notications depends on the duration dates and their osets.
1. Specify the notications the task owner receives.
2. Optionally, specify the number of days before the application automatically deletes a notication from storage.
Use the Manage Payroll Process Conguration task to complete the Notication Expiration Oset parameter.
Examples of Editing Flow Paerns

Review these scenarios to understand how you can edit ow paerns to meet the requirements of your enterprise. Use
the Manage Payroll Flow Paern task or the Rene Extracts task to edit these scenarios.
Update a Parameter to Use a Specied Value

Your payrolls use a single process conguration group named InFusion Consolidation Group A. You want to specify
a constant for the conguration group task action parameter and hide the parameter to avoid data entry mistakes.
Perform these steps.
1. Query the ow paern you dened for the payroll cycle.
2. On the Parameters tab of the Manage Payroll Flow Paern page, edit the Process Conguration Group
parameter.
Enter these values to maintain a constant value for the Process Conguration Group task action parameter and
avoid data entry mistakes.
Parameter Detail Value
Display No

507
Display Format Text

Lookup No value

Usage Input Parameter

Parameter Basis Constant Bind

Basis Value InFusion Conguration Group A

Supply a Reason for a Corrective Action

Your enterprise typically issues electronic funds transfer payments. You dened a ow paern to issue check payments
and you want to verify and track the reason managers issue checks. You can add a ow parameter to capture that
information.
1. Query the payments ow paern you dened.

2. On the Parameters tab of the Manage Payroll Flow Paern page, Select and Add the Reason parameter to
include the parameter as a ow submission parameter. Enter these details.
Display Yes

Display Format Text

Lookup No value

Usage Input Parameter

Parameter Basis Context Binding

Basis Value Payroll Flow

508
Add Tasks and Reorder the Task Sequence

Your ow paern includes the Calculate Gross Earnings process and the Element Results Register Report. Perform these
steps to run the two extract reports concurrently, and add a verication task, to simplify the checklist to a single list.
1. From the Data Exchange work area, select the Rene Extracts task.
2. On the Rene HCM Extracts page, query the ow paern.
3. On the Tasks tab of the Manage Payroll Flow Paerns page:
a. Add the rst extract report, specifying the same Activity and Task Group as the Calculate Gross Earnings.
b. Add the second extract report, specifying the same Activity and Task Group as the Calculate Cross
Earnings.
c. Add a manual verication task, specifying the same Activity and Task Group as the Calculate Cross
Earnings.
4. Edit each task, specifying a sequence number on the Edit Task Details Owners and Details page.
The lowest number is used for the rst task in the checklist. For example, you might specify a sequence of:
◦ 10 for the Calculate Gross Earnings task

◦ 20 for the rst extract report
◦ 30 for the second extract report
◦ 40 for the manual verication task
5. On the Tasks Sequence tab, reorder the sequence of reporting tasks in this order to run the two reports
concurrently.
Task Following Task
Start Flow Calculate Gross Earnings

Calculate Gross Earnings First extract report

Calculate Gross Earnings Second extract report

First extract report Manual verication task

Second extract report Manual verication task

Manual verication task End Flow

509
Automatically Increment Dates in the Scheduled Extract

You create a ow paern to extract weekly payroll data that requires the user to enter a process date parameter. You
schedule the extract to run weekly. The application evaluates the ow parameters at the time of submission, and the
task parameters at the beginning of task execution. You edit the task parameters to automatically increment the date
eld. The date values are derived from the default date parameter values.
You use the Rene Extracts task or the manage Flow Paerns task. Perform these actions to edit the task parameters on
the task's Basic Information page.
1. Select the Process Date parameter.
2. Select Context binding from the Parameter Basis eld.
3. Select System Date from the Basis Value eld.
Add a BI Publisher Report to a Flow

Add single or multiple BI Publisher reports to your copied or user-dened ow paern. When you submit the ow, the
report automatically generates an output le that you can view. The output le is based on the template used for the BI
Publisher report, such as an html template. The Run BI Publisher Report task belongs to the Statutory activities in the
ow paern.
Add Your Report to a Flow

Follow these steps to add the BI Publisher report to an existing extract ow.
1. Use the Manage Flow Paerns task or the Rene Extracts task.
2. Search and select the ow that you want to congure.
3. On the Manage Flow Paern page, on the Tasks tab, click Edit.
4. Click Select and Addon the menu bar. In the Search Tasks dialog, search for and select Run BI Publisher
Report. Click Done.
5. On the Task Sequence page, conrm the sequence is correct.
6. On the Flow Parameters page, add a required parameter for the rst argument of the BI Publisher report.
The ow parameters map to the BI Publisher arguments. For example, if your report is based on a SQL query,
the rst argument is the rst bind variable of a SQL query data model.
Tip: To easily determine the sequence of arguments, view the list of parameters for the
generated report in BI Publisher.
7. Optionally, rename the parameter to a more meaningful name.
8. On the Task parameters page, in the Parameter Details section, complete these steps:
a. Conrm that the Parameter Basis for the First Argument value is Bind to Flow.
b. Specify a value for the Report Name and Report Path parameters.
For example, if the BI Publisher data model is saved to the Custom folder in Shared Folders you would
specify /Custom/yourBIreport.xdo.
c. Specify values for other arguments if required.
510
9. Review the ow and submit it.
Create a Flow within a Flow

In this example you copy the Transfer Batch ow and modify it to include a predened report ow paern you created
earlier. The predened ow you add submits a report to check for any batch line errors during the Transfer Batch
process. If the transfer fails, you can skip the transfer process or mark it as complete, and then view the report for error
details.
Create the Parent Flow Paern

1. In the Payroll Checklist work area, select the Manage Payroll Flow Paerns task.
2. Search for and select the row for Transfer Batch, and then click Copy.
3. Enter the name of the new ow paern, such as Transfer Batch with Error Report.
4. Enter a description, such as "Transfer a batch and view any batch line errors that occurred." and then click Save
and Close.
5. Search for and select the Transfer Batch with Error Report ow paern, and then click Edit.
6. Here's the list of tasks to add the parameter that derives batch name from the batch ID.
a. On the Parameters tab, click Add.
b. Select the added row and click Edit.
c. Add these values.
Field Value
Flow Parameter Batch Name

Use for Searches No

Display No

Display Format Text

Sequence 3

Usage Input parameter

Parameter Basis Post SQL Bind

Basis Value select batch_name from pay_ batch_ headers where batch_id = :BATCH

7. Click Save.
511
Add the Report to the Parent Flow

1. On the Tasks tab, click Select and Add.
2. In the Search window, search for and select Submit Another Flow, and then click Done.
3. In the row for Submit Another Flow, click Edit on the menu bar and set these values to dene the task you have
added to generate the batch lines error report.
Field Value
Task Run Batch Lines Report

Activity Statutory

Task Group Reporting

Description Submit the batch lines error report for the specied batch.

4. Edit task parameters as follows:

a. In the row for Run Batch Lines Report, click Edit Task.
b. Congure these predened task parameters. Select a parameter and the corresponding parameter basis
and basis value.
Parameter Parameter Basis Basis Value
Flow Name Constant Bind The name of the ow, for example
Batch Lines Report. This value is case-
sensitive. Enter the name exactly.

From Flow Instance ID Context Binding Payroll ow

From Flow Task Instance ID Context Binding Payroll task

Use to Calculate Results Constant Bind Y

Parameter Name 1 Constant Bind Batch Name

Parameter Value 1 Bind To Flow Batch Name

c. Click Next, and optionally complete the owner and checklist information.
d. Click Next, and optionally complete the duration and notication information.
e. Click Submit.
512
5. Perform these steps to edit the task sequence:

a. On the Task Sequence tab, edit these two rows to enter the ow tasks and sequence in the ow.
Start Flow Following Task
Transfer Batch Run Batch Lines Report

Run Batch Lines Report End Flow

b. Click Submit.
Test the Flow

1. Create and save a test batch that should cause an error.
Alternatively, you can search for an existing batch that was transferred with errors using this SQL query:
select * from pay_batch_headers where batch_status = 'E';
2. On the Submit a Process or Report page, select a legislative data group.

3. Select the Transfer Batch with Error Report task, and then click Next.
4. Enter a unique name for the current ow instance.
5. Enter the name of the batch with errors that you saved or queried, and then click Submit.
6. Click OK and View Checklist, and then click the Refresh icon until the Transfer Batch task shows as in
progress with error.
7. View the report in the ow as follows:
a. Select the row with the Transfer Batch task, and then select Skip Task in the Actions menu.
b. In the row for Run Batch Lines Report, click Go to Task.
c. In the Processes and Results section, click the name of the report.
d. In the row for Run BI Publisher Report, click Go to Task.
e. On the Process and Reports tab, click View Results.
f. Click the PDF le name to open the report.
FAQs for Flow Paerns

What happens if I don't enter a task owner in a ow paern?
The person who submits the ow becomes the ow owner and the task owner. The person's security privileges
determine whether the person can submit the ow.
How can I rearrange tasks in a ow paern?

Every ow paern begins with a Start Flow task, which doesn't belong to an Activity or Task Group, and concludes with
an End Flow task. Edit the task sequence by selecting a dierent task in the Following Task column.
513
When you create a ow, use the Task Sequence page to rearrange the tasks. When you edit a ow, select the task and
edit its sequence on the Create Flow Paern: Basic Information page. When you submit a ow, processes in the ow use
and build upon the results of the previous processes. To maintain data integrity, ensure the sequenced tasks follow a
consecutive order.
What happens if I change a due date for a task in a ow?

It doesn't aect the status or progress information for the ow displayed on the checklist.
You must complete a ow task before beginning the next task. Before updating a due date beyond the next task's start
date, consider whether you have adequate time to perform the next task.
Only ow owners and task owners can update the due date.
Why don't the duration dates in the ow paern display?

The start and end dates and their osets display after you complete the ow parameter dates. Enter the ow
parameters on the Parameters page, and then return to the Tasks page to enter the duration dates.
If your ow paern doesn't specify dates as ow parameters, the duration list of values is blank. Change the values for
the Duration list by displaying the date parameters for tasks in your ow paern.
How can I improve performance and troubleshoot ows?

Add parameters to a payroll process conguration group to optimize performance and troubleshoot your payroll
processes. To process large volumes of records, use the Threads and Chunk Size parameters. To troubleshoot
processes, add the Logging Category or Formula Execution Logging parameters to a conguration group and rerun the
process using that conguration group. Using these parameters enables you to investigate formula code problems.
How can I run tasks concurrently in a ow?

Use the Manage Payroll Flow Paerns task in the Payroll Checklist. Search for and open your ow paern. Click the Task
Sequence tab. Specify that each concurrent task follows the same previous task.
For example, you create a ow paern with a payroll calculation task and two reports. The ow ends when both reports
complete. You can use these actions to run the payroll calculation task and the two reports run concurrently.
1. For the rst row, specify the Start Flow task with the Calculate Payroll as the following task.
2. For the second row, specify Calculate Payroll as the task, and the rst report as the following task.
3. For the third row, specify Calculate Payroll as the task, and the second report as the following task.
4. For the fourth row, specify the rst report as the task and End Flow as the following task.
5. For the last row, specify the second report as the task and End Flow as the following task.
514
Integrating with HCM Benets Data Extract
37 Benets Data Extract
Guidelines for Extracting Benets Data Using HCM

Extracts
You can extract worker enrollment results, designated dependents and beneciaries, and corresponding rates and
coverages. You create an extract denition using the Manage Extract Denitions task in the Data Exchange work area.
Consider these aspects before you create an extract denition for benets data:
• Extract type
• Data groups
• Extract record sequence
Extract Type
When you create an extract denition, ensure that you select Benets Carrier from the Extract Type list.
Data Groups
Create a PER_EXT_SEC_PERSON_UE (Person) data group and select it as the root data group. The following benets
data groups are available:
• BEN_EXT_ENRT_RSLT_UE (Enrollment Results)
• BEN_EXT_ENRT_DPNT_UE (Dependents)
• BEN_EXT_ENRT_BNF_UE (Beneciaries)
• BEN_EXT_ENRT_RTCVG_UE (Rates and Coverages)
Extract Record Sequence

After you create the data groups, ensure that you sequence the data groups to identify which data group the application
processes next:
• Person
• Dependents
• Beneciaries
• Enrollments
• Rates and coverages
Related Topics
515
Congure Benets for Extracting Data

This topic covers how to set up benet plan carriers and oerings so that you can then generate and transmit
enrollment data extracts. You extract benets enrollment information into a single XML le for each benets carrier.
To congure the benets data extract, you complete these tasks in the Plan Conguration work area:
1. Create the plan carrier and congure extract seings.

2. Add the benets extract plan type name.
3. Add the benets extract plan code.
4. Add the benets extract option name.
Creating Plan Carrier

Set up carrier data and congure extract options in the Plan Conguration work area that apply whenever you run the
extract for that carrier.
1. In the Tasks panel drawer, click Manage Plan Carriers to open the Manage Plan Carriers page. On the Mapping
tab, you can view the mapping of lookup codes to the lookup value that you transmit to carriers. Edits to
mapping values aect all plan carriers that use the lookup.
2. On the Search Results toolbar, click the Create buon.
3. Enter the carrier information. In the Active eld, select Active.
4. Enter the extract options.
The following table provides comments to help you with your extract eld entries and selections.
Field Comments
Select whether to run a full extract or extract only the changes since the previous extract.
Extract Type
Generally, you run a full extract after an enrollment period closes and enrollments are
completed. You run subsequent extracts on a periodic or scheduled basis, in either full or
changes only mode.

Obtain the value that you enter here from the extract le recipient.
Output File Name
A common practice is to schedule your extracts to run after your regular payroll runs. You
Processing Frequency might want to set the processing frequency accordingly.

By default, all extracts have the same format, regardless of which carrier receives the
Processing Type extract. You can contract with Oracle's partner, BenetsXML, to have a carrier's extract
data transformed and delivered to the carrier, according to its specications. For more
information about BenetsXML, see hp://www. benetsxml. com.

If you don't use this partner, you can transform and deliver the extract data le directly to
each of your plan carriers, according to their specications.

516
Field Comments
Upload Custom Layout This buon is available if you select the Custom layout processing type.
◦ Specify the layout for the individual carrier. For details, see the Benets Extract: User-
Dened Layout topic
5. Enter the le transfer details, which you obtained from the extract le recipient. You can transmit extract les
directly to the recipient. Alternatively, you can transmit extract les to the Oracle cloud, using its le transfer
details, and have your recipient download its extract from there.
Field Comments
The name of the server to which you transmit the recipient's extract les.
Host
Path on the host to the location where your transmission places the extract le.
Remote Folder
Part of the sign-in credentials required for your transmission to access the host.
User Name
Part of the sign-in credentials required for your transmission to access the host.
Password
6. Click Save and Close to return to the Manage Plan Carriers page.
Adding Benets Extract Plan Type Name

Complete these steps in the Plan Conguration work area to identify each type of plan included in the extract le for the
recipient.
1. In the Tasks panel drawer, click Manage Plan Types to open the Manage Plan Types page.
2. Search for and click the plan type, for example, Medical.
3. On the Plan Type Denition section Actions menu, select Update.
4. Enter the valid benets extract plan type name, for example, Health.
5. Click Save and Close to return to the Manage Plan Types page.
Adding Benets Extract Plan Code

Complete these steps in the Plan Conguration work area to link the plan to the extract le recipient.
1. In the Tasks panel drawer, click Manage Benets Plan Details to open the Manage Benets Plan Details page.
2. Search for and click the plan that you want to link to the extract le recipient.
3. Click Next to open the Edit Plan Additional Conguration page.
4. On the Conguration Details section Actions menu, select Update.
5. Enter the benets extract plan code, which the extract le recipient provided to you for this specic plan.
6. Click Save and Close to return to the Plans tab.
517
Adding Benets Extract Option Name

Complete these steps in the Plan Conguration work area to identify each option included in the extract le for the
recipient.
1. In the Tasks panel drawer, click Manage Benet Options to open the Manage Benet Options page.
2. Search for and click the participant option, for example, Participant Only.
3. On the Basic Details section Actions menu, select Update.
4. Enter the valid benets extract option name, for example, Employee Only.
5. Click Save and Close to return to the Manage Benet Options page.
Next Steps
After you complete the previous tasks, you're ready to generate and transmit the extract data. The details of this
process are covered in the Generating and Transmiing Benets Data Extract for Plan Carriers: Procedure topic.
Valid Extract Names

Oracle partner BeneX provides valid extract names that you can enter for benets plan types and options. You can add
values to this list, as required.
Benet Extract Plan Type Names

Valid benets extract names for plan types:
• 24 Care
• Dental
• Dental Capitation
• Exclusive Provider Organization
• Health
• Health Maintenance Organization
• Hearing
• Long Term Care
• Long Term Disability
• Mail Order Drug
• Major Medical
• Medicare Risk
• Mental Health
• Point of Service
• Preferred Provider Organization
• Prescription Drug
• Preventative Care
• Short Term Disability
518
• Utilization Review
• Vision
Benets Extract Option Names

Valid benets extract names for options
• Children Only
• Dependents Only
• Employee and Children
• Employee and Five or More Dependents
• Employee and Four or More Dependents
• Employee and One Dependent
• Employee and One or More Dependents
• Employee and Spouse
• Employee and Three Dependents
• Employee and Three or More Dependents
• Employee and Two Dependents
• Employee and Two or More Dependents
• Employee Only
• Family
• Individual
• Not Applicable
• Spouse and Children
• Spouse Only
• Two Party
• Employee and Domestic Partner
• Domestic Partner and Children
• Domestic Partner Only
• Employee and Spouse or Domestic Partner
• Child or Children of a Domestic Partner
Generate and Transmit Benet Extracts

You can extract benets enrollment information into a single XML le for each benets carrier and transmit it to the
carrier. This topic covers how to generate and transmit the extract le.
Note: If a carrier provides more than one plan, the single extract contains information related to all plans
provided by that carrier. Example: Four dierent carriers provide ten plans. You run four separate extracts, one
for each carrier.
To generate and view the extract, you complete these tasks in the Evaluation and Reporting work area.
1. Submit the extract request.
519
2. View and transmit the extract details.
Prerequisites
You must rst congure your plan carriers, or extract recipients, and add the relevant extract data to the appropriate
plan types, plans, and options. The details of this process are covered in the Conguring Benets Data Extract for Plan
Carriers: Procedure topic.
Submiing Extract Request

To run and monitor extracts, in the Evaluation and Reporting work area:
1. In the Tasks panel drawer, click Extract Benets Data to open the Extract Benets Data page.
2. On the Search Results toolbar, click Submit.
3. Enter the extract request options.
Field Comments
Extract Type
For a particular carrier, you can select whether to run a full extract or extract only the
changes since you ran the previous extract.
◦ Generally, you run a full extract after an enrollment period closes and enrollments are
completed.
◦ You run subsequent extracts on a periodic or scheduled basis, in either full or changes
only mode. Common practice is to schedule your extracts to run after your regular
payroll runs.
Transmit You can transmit the extract as part of the extract request, or after the requested extract
completes and before or after you view the extract details.

4. Click Submit to submit your process and return to the Extract Benets Data page.
Viewing and Transmiing Extract Details

You can view, query, and download extracted records for a specic extract run after it completes. You can also transmit
the extract after the requested extract completes and before or after you view the extract details.
1. In the Search Results section of the Extract Benets Data page, click the Request ID for the most recent extract
request for the plan carrier.
2. Review, query by example, and download to a spreadsheet the extracted data, as appropriate.
3. Click Done to return to the Extract Benets Data page.
4. In the Search Results section, click the Transmit icon buon for the most recent extract request.
Example of a Custom Layout for Benets Extract

An implementor or developer can create a custom layout to transform the format of extracted benets enrollment data
to match the specications of a particular carrier. This topic provides:
• Descriptions of the tags that you require to create the custom layout
• Table aliases and a sample custom layout
520
The custom layout becomes the default layout for the plan carrier after you upload it to the plan carrier's
extract options.
The following code shows the structure of the XML tags in the custom layout.
<Layout
<Table
Record Type
<Field
Name
Source
Width
Padding
Field>
Table>
<Table
<Field
Name
Source
Width
Padding
Field>
-----------
More fields
-----------
Table>
<Table
-----------
More tables
-----------
Table>
Layout>
The data source for a eld on the custom layout can be a:
• Column on the benets extract staging tables

• Column on one of the other tables listed in the Source tag description
• Constant into which you enter the exact value
Tip: To identify table column names, you can use the data model query builder in Oracle BI Publisher. Search
for the table name and view the columns.
XML Tag Descriptions

This section describes each XML tag and lists its aributes, elements (subtags), and parent tags.
Layout
Description: Root tag.
Aributes: None
521
Elements (Subtags) Parent Tag
Table None

Table
Description: Species the database table from which to extract the data.
Aributes: 1. tableName: Supported values = {BEN_EXTRACT_REQ_DETAILS,BEN_EXTRACT_REQUEST,

DUAL,PER_ALL_PEOPLE_F,PER_PERSONS,PER_ALL_ASSIGNMENTS_M,PER_PEOPLE_LEGISLATIVE_F,BEN_PL_F,BEN_PL_TYP_
1. RecordType Layout

2. Field: See Field tag description

Record Type
Description: Species how to delimit or lay out the data in the extract le.
Aributes: Supported values: FIXEDWIDTH, CSV
Note: Anything other than CSV is delimited as FIXEDWIDTH by default.
None Table

Field
Description: Corresponds to one column in the extracted document. Source the text in this column from a database
table, an SQL function, or a constant.
522
Aributes: None
1. Name Table
2. Source
3. Width
4. Padding
Name
Description: Name of the eld
Aributes: None
None Field

Source
Description: Species the source of data for the current eld.
• If the source is a table, the value passed is the column name.
• If multiple tables are involved, use a fully qualied column name.
The list of allowed tables includes the table aliases.
SQL functions in place of column names: Values in this tag are treated as column names if the type is set to TABLE. The
column name is used directly while constructing a query, so an SQL function can be used on a column.
• Example 1
<Source type="TABLE">GENDER_FLAG</Source>
• Example 2
<Source type="TABLE">DECODE(GENDER_FLAG,'F',1,2)</Source>
Aributes:
1. type:
◦ Supported values = {TABLE, CONSTANT}
• TABLE species that the data comes from a database table.
• CONSTANT species that the data is given in the value column of this tag.
523
2. table: Use this tag only if the intended column isn't from the table given in the tableName aribute of this Table
tag. If this tag isn't used, the column is searched for in the table given in tableName.
◦ Supported values:
• {BEN_EXTRACT_REQ_DETAILS
• PER_ALL_PEOPLE_F
• PER_PERSONS
• PER_ALL_ASSIGNMENTS_M
• PER_PEOPLE_LEGISLATIVE_F
• BEN_PL_F
• BEN_PL_TYP_F
• BEN_OPT_F
• BEN_PGM_F
None Field

Width
Description: Species the intended width of this eld in the extract le. The number passed is the number of character
spaces on the le.
Aributes: Supported values are positive integers.
None Field

Padding
Description: Species the alignment of data in each column.
Aributes: Supported values: {LEFT, RIGHT}
None Field

524
Table Aliases
Allowed Table Alias
BEN_ EXTRACT_ REQ_DETAILS REQ

PER_ ALL_PEOPLE_F PEO

PER_PERSONS PER

PER_ ALL_ ASSIGNMENTS_M ASG

PER_ PEOPLE_ LEGISLATIVE_F LEG

BEN_PL_F PLN

BEN_PL_TYP_F TYP

BEN_OPT_F OPT

BEN_PGM_F PGM

Sample XML Layout

<?xml version="1.0" encoding="utf-8"?>
<Layout>
<Table tableName="DUAL">
<RecordType>FIXEDWIDTH</RecordType>
<Field>
<Name>"Record Type"</Name>
<Source type="CONSTANT">001</Source>
<Width>3</Width>
<Padding>Left</Padding>
</Field>
</Table>
<Table tableName="BEN_EXTRACT_REQ_DETAILS">
<RecordType>CSV</RecordType>
<Field>
<Name>"Last Name"</Name>
<Source type="TABLE">LAST_NAME</Source>
<Width>25</Width>
</Field>
<Field>
525
<Name>"First Name"</Name>
<Source type="TABLE">FIRST_NAME</Source>
<Width>50</Width>
</Field>
<Field>
<Name>"Filler"</Name>
<Source type="CONSTANT">XXXXXXXXXX</Source>
<Width>10</Width>
<Padding>None</Padding>
</Field>
<Field>
<Name>"Plan Name"</Name>
<Source type="TABLE">PLAN</Source>
<Width>70</Width>
</Field>
<Field>
<Name>"Coverage Start Date"</Name>
<Source type="TABLE">COVERAGE_START_DATE</Source>
<Width>15</Width>
</Field>
<Field>
<Name>"SSN"</Name>
<Source type="TABLE">NATIONAL_IDENTIFIER</Source>
<Width>12</Width>
</Field>
<Field>
<Name>"Gender"</Name>
<Source type="TABLE">DECODE(GENDER_FLAG,'F',1,2)</Source>
<Width>1</Width>
</Field>
<Field>
<Name>"Person Number"</Name>
<Source type="TABLE" table="PER_ALL_PEOPLE_F">PERSON_NUMBER</Source>
<Width>30</Width>
</Field>
<Field>
<Name>"Country of Birth"</Name>
<Source type="TABLE" table="PER_PERSONS">COUNTRY_OF_BIRTH</Source>
<Width>30</Width>
</Field>
<Field>
<Name>"Assignment type"</Name>
<Source type="TABLE" table="per_all_assignments_m">assignment_type</Source>
<Width>30</Width>
</Field>
<Field>
<Name>"Legislation code"</Name>
<Source type="TABLE" table="per_people_legislative_f">LEG.LEGISLATION_CODE</Source>
<Width>30</Width>
</Field>
<Field>
<Name>"Legislation code"</Name>
<Source type="TABLE" table="ben_pl_f">PLN.PL_ID</Source>
<Width>30</Width>
</Field>
</Table>
526
<Table tableName="DUAL">
<RecordType>FIXEDWIDTH</RecordType>
<Field>
<Source type="CONSTANT">999</Source>
<Width>3</Width>
</Field>
<Field>
<Source type="SYSTEM">RECORDCOUNT</Source>
<Width>3</Width>
</Field>
</Table>
</Layout>
527
528
Integrating with HCM Talent Review and Succession Management Data Extract
38 Talent Review and Succession

Management Data Extract
Guidelines for Extracting Talent Review Data Using HCM

Extracts
You can use HCM Extracts to extract Talent Review data.
Here's the data that you can extract with a few examples of the aributes that you can extract for each:
• Meeting details: Meeting ID, meeting dashboard template ID, meeting date
• Facilitators' details: Facilitator ID, facilitator person number, facilitator creation date
• Participants' details: Participant ID, participant business group ID, participant person number
• Talent pools' details: Talent pool ID, talent pool meeting ID, talent pool creation date
• Prior rating details: Prior rating date range ID, prior rating date range meeting ID, prior rating date range
creation date
• Reviewees' details: Reviewee ID, reviewee meeting ID, reviewee person number
• Review content details: Review content ID, review content meeting ID, review competencies
• Succession plans' details: Succession Plan ID, succession plan meeting ID, succession plan creation date
In this topic, we discuss only the information that you need for extracting Talent Review data. For more information
about creating an extract denition and publishing the extract results, see the related topics.
Create Talent Review Extract Denition

To create an extract denition, you must determine these details:
• The user entity details to create data groups
• The database item group details to create aributes
• The extract denition type
You create an extract denition using the Manage Extract Denitions task in the Data Exchange work area.
This table lists the Talent Review related user entities and the starting characters of the database items that correspond
to these user entities. You can search the Talent Review related database items using these characters.
Talent Review Data to Extract User Entity Database Items Start With
Meeting details HRR_ EXT_MEETINGS HRR_MEETINGS_

Meeting facilitators HRR_ EXT_ MEETING_ FACILITATORS HRR_ MEETING_ FACILITATORS_

Meeting participants HRR_ EXT_ MEETING_ PARTICIPANTS HRR_ MEETING_ PARTICIPANTS_
529
Talent Review Data to Extract User Entity Database Items Start With

Associated talent pools HRR_ EXT_ MEETING_ TALENTPOOLS HRR_ MEETING_ TALENTPOOLS_

Meeting prior rating date ranges HRR_ EXT_ PRIOR_ RATING_ HRR_ PRIOR_ RATING_ DATE_RANGES_
DATE_RANGES

Meeting review population HRR_ EXT_ MEETING_ REVIEWEES HRR_ MEETING_ REVIEWEES_

Meeting review content HRR_ EXT_ MEETING_ REVW_CONTENT HRR_ MEETING_ REVW_CONTENT_

Associated succession plans HRR_ EXT_ MEETING_ SUCCPLANS HRR_ MEETING_ SUCCPLANS_

While creating the Talent Review extract denition, select the extract denition type as HR Archive.
With the information in this topic, you're now ready to extract Talent Review data.
Related Topics
• HCM Extract Types
• Filter Extracts Using Advanced Filter Criteria
• Dene the BI Publisher Template in HCM Extracts
Guidelines for Extracting Succession Management Data

Using HCM Extracts
You can use HCM Extracts to extract Succession Management data.
Here's the Succession Management data that you can extract with a few examples of the aributes that you can extract
for each:
• Plan details: Plan type, status, incumbent ID
• Candidate details: Candidate person number, status, readiness value
• Owner details: Owner person number, meaning of the owner type code
In this topic, we discuss only the information that you need for extracting Succession Management data. For more
information about creating an extract denition and publishing the extract results, see the related topics.
Create Succession Management Extract Denition

To create an extract denition, you must determine these details:
• The user entity details to create data groups
530
• The database item group details to create aributes

• The extract denition type
You create an extract denition using the Manage Extract Denitions task in the Data Exchange work area.
This table lists the Succession Management related user entities and the starting characters of the database items that
correspond to these user entities. You can search the related database items using these characters.
Succession Management Data to Extract User Entity Database Items Start With
Plan details HRM_ EXT_PLANS_UE HRM_PLANS_

Plan candidates HRM_ EXT_ PLAN_ CANDIDATES_UE HRM_ PLAN_ CANDIDATES_

Plan owners HRM_ EXT_ PLAN_ OWNERS_UE HRM_ PLAN_OWNERS_

While creating the Succession Management extract denition, select the extract denition type as HR Archive.
With the information in this topic, you're now ready to extract Succession Management data.
Related Topics
• HCM Extract Types
• Filter Extracts Using Advanced Filter Criteria
• Dene the BI Publisher Template in HCM Extracts
531
532
Integrating with HCM Transferring Encrypted Data
39 Transferring Encrypted Data
Set up Encryption for File Transfer

You use encryption keys to encrypt les for secure transfer between Oracle HCM Cloud and your own servers through
the Oracle WebCenter Content server. This PGP-based encryption support is available for secure le transfer using HCM
Data Loader and HCM Extracts.
The process for inbound les (into Oracle HCM Cloud) is:
1. You encrypt les using the Oracle HCM Cloud public key.
2. The data-loading process decrypts les using the Oracle HCM Cloud private key.
The process for outbound les (generated by Oracle HCM Cloud) is:
1. Oracle HCM Cloud encrypts les using your public key.
2. You decrypt les using your private key.
Therefore, before you can encrypt or decrypt les, you must:
1. Import your public key to Oracle HCM Cloud.
2. Generate the PGP encryption key pair and download the Oracle HCM Cloud public key.
You can also sign the les, as follows:
• Outbound les are signed using the HCM Cloud private key. You verify these les using the HCM Cloud public
key.
• Inbound les are signed using your private key. The data-loading process veries inbound les using your
public key.
This topic describes how to set up encryption, decryption, and signing of les.
Encryption and Signature Keys

This table shows you the keys that are used for encryption, decryption, signing, and verication in each supported
encryption mode.
Encryption Mode Encryption Key Decryption Key Signing Key Verication Key
Outbound PGP Signed customer-key_ pub customer-key_ priv fusion-key_ priv fusion-key_pub

Outbound PGP customer-key_ pub customer-key_ priv N/A N/A

Unsigned

Inbound PGP Signed fusion-key_pub fusion-key_ priv customer-key_ priv customer-key_ pub

Inbound PGP Unsigned fusion-key_pub fusion-key_ priv N/A N/A

533
Importing Your Public Key

You use your public key (customer-key_pub) for encrypting outbound les. You can decrypt the les using your private
key (customer-key_priv). If you also want outbound les to be signed, then use the HCM Cloud private key (fusion-
key_priv) for signing. You can verify signed outbound les using the HCM Cloud public key (fusion-key_pub).
To import the customer public key:

1. Sign in to Oracle HCM Cloud with the IT Security Manager job role or privileges.
2. Select Navigator > Tools > Security Console to open the Security Console.
3. Click the Certicates tab to open the Certicates page.
4. Click Import to open the Import page.
5. Set Certicate Type to PGP.
6. In the Alias eld, enter customer-key.
Note: You must enter customer-key in this eld. Otherwise, the encryption APIs can't use
this key for encrypting outbound les.
7. Click Browse to identify the location of the customer public key.
8. Click Import and Close to import the public key into the Oracle HCM Cloud keystore.
Your public key now appears on the Security Console Certicates page.
Generating the PGP Encryption Key Pair

You generate the PGP key pair on the Security Console. You download the public key to encrypt les that are inbound
into HCM Cloud (for example, input data les for HCM Data Loader). To sign these inbound les, you can use your
private key (customer-key_priv), which is veried using your public key (customer-key_pub) in Oracle HCM Cloud. You
must have imported the customer public key.
To generate the PGP Encryption Key Pair:

1. Sign in to Oracle HCM Cloud with the IT Security Manager job role or privileges.
2. Select Navigator > Tools > Security Console to open the Security Console.
3. Click the Certicates tab to open the Certicates page.
4. Click Generate to open the Generate dialog box.
5. In the Generate dialog box, set Certicate Type to PGP.
6. In the Alias eld, enter fusion-key.
Note: You must enter fusion-key in this eld. Otherwise, the encryption APIs can't use this
key to decrypt all encrypted inbound les.
7. In the Passphrase eld, enter a passphrase for the private key. This passphrase is needed when you edit,
delete, or download the private key.
Note: If you forget the passphrase, then you may have to raise a service request for help
to delete the private key. Once the old key is deleted, you can generate a new key using the
process described here.
8. In the Key Algorithm eld, select RSA.
534
9. In the Key Length eld, select either 1024 or 2048.

10. Click Save and Close. The fusion-key pair is generated and ready for download. You can see the fusion-key
pair on the Certicates page of the Security Console.
11. In the Status actions for the fusion-key pair on the Certicates page, select Export > Public key. Save the
HCM Cloud public key (fusion-key_pub.asc) to your desktop. Use the downloaded key to encrypt les that are
inbound to Oracle HCM Cloud.
Encrypt and Upload Files Automatically

Encrypt les of data with PGP encryption and transfer them automatically between your servers and Oracle WebCenter
Content using APIs and web services. For example, you can encrypt and decrypt les that contain sensitive employee
data or condential documents. You write programs to collect the encrypted les from your le server. You then place
them on the Oracle WebCenter Content server and call a data loader to decrypt and load the data to Oracle HCM Cloud.
Note: You must set up your encryption keys before you perform these tasks.
Supported Encryption Algorithms

Oracle HCM Cloud supports the following encryption algorithms. You must ensure that you use only supported
encryption algorithms.
• Cipher: AES-128, Blowsh, CAST5, 3DES
Note: These cipher algorithms aren't supported: Twosh, IDEA, AES-192, and AES-256
• Compression: bzip2, zlib, .zip, uncompressed

• Hash: SHA-1, SHA-256, SHA-224, SHA-512, MD5, SHA-384, RIPEMD-160
Encrypting Files
This section provides the commands to encrypt les in Microsoft Windows and Linux environments using the GnuPG
encryption tool. For other tools and platforms, work with your suppliers to nd the necessary commands for seing the
cipher algorithm.
• Gpg4win, the ocial GnuPG distribution for Microsoft Windows, provides both a command-line interface and a
graphical user interface for encryption, decryption, signing, and verication. For encryption, use the command-
line interface. You can nd Gpg4win here: https://www.gpg4win.org/about.html.
• You can download GnuPG for Linux from various sources, depending on the Linux distribution that you're
using. Commonly used GnuPG versions can be found here: https://www.gnupg.org/index.html.
After installing the Gpg4win or GnuPG tool, follow these steps to encrypt or encrypt and sign a le:
1. Import the HCM Cloud public key (downloaded from the Security Console) using this command at the
command prompt:
gpg --import <fusion public key file>
2. Perform one of these steps.

◦ To encrypt a le without signing, use this command:
535
gpg --cipher-algo <one_of_the_supported_algorithms> -r fusion-key --encrypt <inbound_file_name>
◦ To both encrypt and sign a le, use this command:

gpg --cipher-algo <one_of_the_supported_algorithms> -r fusion-key -se <inbound_file_name>
Note: When signing les, ensure that your private key is imported into the keystore
that's used for signing.
Loading Encrypted Files

Perform the following steps to load encrypted les to Oracle HCM Cloud from the Oracle WebCenter Content server.
1. Write programs to send your encrypted les to Oracle WebCenter Content, using the Oracle WebCenter Content
Web Services. If your home page is: hps://Hostname/homePage/faces/AtkHomePageWelcome, then the
Oracle WebCenterContent Server WSDL is: hps://Hostname/idcws/GenericSoap?wsdl.
2. Call the loader program to pass the encryption parameter with other required parameters. The
loaderIntegrationService uses the submitEncryptedBatch method, which has an additional
parameter named encryptType. This parameter has the following values, which are dened in the
ORA_HRC_FILE_ENCRYPT_TYPE lookup type:
◦ NONE
◦ PGPSIGNED
◦ PGPUNSIGNED
Transfer Files Automatically from HCM Extracts with PGP

Encryption
Transfer encrypted les to Oracle WebCenter Content using HCM Extracts and your encryption key. HCM Extracts can
generate encrypted output and store it on the WebCenter Content server. For example, you can encrypt and decrypt
les that contain sensitive employee data or condential documents. Use HCM Extracts to generate encrypted les and
deliver them to the WebCenter Content server. You write your own programs to collect the les.
Note: You must set up your encryption keys before you try to encrypt or decrypt data.
Outbound Integrations
Set up the following information to use HCM Extracts with your outbound integrations:
1. In the Data Exchange work area, select the Manage Extract Denitions task.
2. Select the WebCenter Content delivery type on the Deliver page.
3. Enter an Integration Name. The application uses this name to create the title of the entry in WebCenter
Content.
4. Select an Encryption Mode. The encryption mode is one of the values from the
ORA_HRC_FILE_ENCRYPT_TYPE lookup type. It determines how the application encrypts the le before loading
it to WebCenter Content. When HCM Extracts transfers the le to WebCenter Content it generates a content ID
automatically with the following format: UCMFAnnnnnn.
536
The le includes the following properties:
Field Name Value
Author FUSION_ APPS_ HCM_ESS_APPID

Security Group FAFusionImportExport

Account hcm/ dataloader/ export

Title HEXTV1CON_ {Integration Name}_ {Encryption Type}_ {Date Time Stamp}

For example: HEXTV1CON_ ExtractConn1_ PGPUNSIGNED_ 17-11-2014 14-16-44

5. Congure the HCM Extract delivery option to output an XML (data) le directly to WebCenter Content without
formaing it in BI Publisher. You can achieve this by selecting Data as the output format, omiing a template
name, and selecting the WebCenter Content Delivery Type.
6. Download the encrypted les from WebCenter Content using client command-line tools or a web service call.
Decryption of Outbound Files

Using your private key, you can decrypt encrypted les that are generated from Oracle HCM Cloud. To verify signed
les, you use the Oracle HCM Cloud public key. Ensure that these two keys are imported into the keystore. For both
Microsoft Windows and Linux, use this command to decrypt both signed and unsigned les:
gpg --decrypt <inbound_file_name> --output <output_file_name>
Related Topics
• For more information see HCM Extracts: Changes Only (Document ID 1964920.1.) on My Oracle Support at
hps://support.oracle.com
537
538
Integrating with HCM Oracle Taleo Recruiting Cloud Service Integration
40 Oracle Taleo Recruiting Cloud Service

Integration
HCM and Oracle Taleo Recruiting Cloud Service

Components: How They Work Together
The integration between HCM and Oracle Taleo Recruiting Cloud Service facilitates seamless ow of the recruitment
process from creating a job requisition to hiring a worker.
HCM and Oracle Taleo Recruiting Cloud Service Integration

The integration between HCM and Oracle Taleo Recruiting Cloud Service involves the following stages:
1. HCM
Exporting work structures and worker data to Oracle Taleo Recruiting Cloud Service.
2. Oracle Taleo Recruiting Cloud Service
a. Creating a job requisition using the data imported from HCM

b. Selecting candidates for a job requisition
c. Hiring a candidate
d. Importing candidate data from Oracle Taleo Recruiting Cloud Service
3. HCM
a. Creating a pending worker

b. Converting the pending worker to an employee
c. Exporting changed data to Oracle Taleo Recruiting Cloud Service
Importing Data From Oracle Taleo Recruiting Cloud

Service: Explained
Once a candidate is selected in Oracle Taleo Recruiting Cloud Service, you must import the candidate data to HCM to
facilitate hiring the candidate as an employee or contingent worker in HCM.
Selected Candidates
When ready-to-be-hired candidates are imported from Oracle Taleo Recruiting Cloud Service you can view notications:
• On the Selected Candidates tab of the New Workers to Process page

• In the Worklist notications, if you are the hiring manager
539
Click the notication task to process the selected candidate as a pending worker. You must ensure that all information
is correct before submiing the candidate for approval. Successfully processed pending workers appear on the Pending
Workers tab. From that tab, you can convert them into employees.
Imported Data
The data that is imported from Oracle Taleo Recruiting Cloud Service to HCM includes the following:
• Candidate data, including:
◦ Person and employment data

◦ Compensation and payroll data
◦ Education, certication, and previous experience details, which are captured as a part of HCM Talent
• Requisition data
Scheduled Processes
You can access the Import Oracle Taleo Recruiting Cloud Service Data process from the Scheduled Processes work area.
You can run this process manually or schedule it to run at regular intervals (for example, weekly at a specied time). The
likely volume and frequency of hiring persons in your enterprise determines how often you run this process.
After you run the import process, you can view the selected candidates in the New Person Overview page. The Selected
Candidates page displays a list of candidates ready to be added as pending workers. Once you add a candidate as a
pending worker, the candidate appears in the Pending Workers list. You can then convert the pending worker to an
employee or a contingent worker. The imported person, payroll, compensation, and talent (education, certication, and
previous experience) details appear by default in the Convert Pending Worker ow.
Note: After you import a candidate from Oracle Taleo Recruiting Cloud Service to HCM, if you make any
changes to the candidate or requisition in Oracle Taleo Recruiting Cloud Service, these changes aren't
included in the subsequent import runs.
Exporting Data to Oracle Taleo Recruiting Cloud Service:

Explained
Oracle Taleo Recruiting Cloud Service uses HCM work structures and worker data to create and process job requisitions.
You can export this data from HCM to Oracle Taleo Recruiting Cloud Service.
HCM and Oracle Taleo Recruiting Cloud Service Mapping

The following table lists the business objects that HCM exports and the corresponding business objects that they are
mapped to in Oracle Taleo Recruiting Cloud Service.
HCM Oracle Taleo Recruiting Cloud Service
Departments Departments
540
HCM Oracle Taleo Recruiting Cloud Service

Jobs Requisition Templates

Business Units Organizations

Users Users

Employees Candidates

Locations Locations

Positions Large user-dened selection

Grades Large user-dened selection

Legal Employers Large user-dened selection

Job Families Job Fields

Employees and Users Export

As a part of the integration, HCM exports employees and users such as Managers, Hiring Managers, and Recruiters,
who have the privilege to create requisitions in Oracle Taleo Recruiting Cloud Service. From the HCM perspective,
user and employee data are the same, and use the same data mapping. The employee or user creation process relies
on certain default user types provisioned in Oracle Taleo Recruiting Cloud Service. The following table lists the roles
exported from HCM, and the user types they are mapped to in Oracle Taleo Recruiting Cloud Service.
HCM Role Oracle Taleo Recruiting Cloud Service Oracle Taleo Recruiting Cloud Service
User Type Code User Type Name
PER_ RECRUITING_ ADMINISTRATOR_ 01-RecruitingAdmin Recruiting - Administrator

JOB

PER_ POWER_ RECRUITER_ ABSTRACT 02-PowerRecruiter Recruiting - Power Recruiter

PER_ BASIC_ RECRUITER_ ABSTRACT 03-BasicRecruiter Recruiting - Basic Recruiter

PER_ LINE_ MANAGER_ ABSTRACT 04-PowerManager Recruiting - Power Manager

PER_ EMPLOYEE_ ABSTRACT 10-Employee Recruiting - Employee
541
HCM Role Oracle Taleo Recruiting Cloud Service Oracle Taleo Recruiting Cloud Service
User Type Code User Type Name

Scheduled Processes
You can schedule the following process in the Scheduled Processes work area:
• Export All Oracle Taleo Recruiting Cloud Service Data
Exports all work structures and worker data from HCM to Oracle Taleo Recruiting Cloud Service. You must run
this process typically only once, in the beginning, to send all HCM data to Oracle Taleo Recruiting Cloud Service
to enable creation of job requisitions.
• Export Changed Oracle Taleo Recruiting Cloud Service Data
Exports any changed work structures and worker data from HCM to Oracle Taleo Recruiting Cloud Service.
You can run this process manually or schedule it to run at regular intervals (for example, weekly at a specied
time). The likely volume and frequency of hiring persons in your enterprise determines how often you run this
process.
FAQs for Oracle Taleo Recruiting Cloud Service and HCM

Integration
What are Large User Dened Selections (LUDS)?
Some business objects in HCM don't map directly to any business objects in Oracle Taleo Recruiting Cloud Service,
when exporting data from HCM to Oracle Taleo Recruiting Cloud Service. These business objects (for example, legal
employers, jobs, and positions) are mapped to Large User Dened Selections (LUDS) instead. LUDS are custom, user-
dened elds in Oracle Taleo Recruiting Cloud Service, specically congured for the integration with HCM. The
mappings are dened in the Oracle Taleo Recruiting Cloud Service application.
542
Integrating with HCM Web Services
41 Web Services
Overview of Web Services

Use web services to integrate web-based applications with Oracle Human Capital Management (HCM) Cloud. Web
services expose business objects and processes to other applications through the use of open standards-based
technologies. For more information about web services, see:
• SOAP Web Services for Oracle HCM Cloud

• SOAP Web Services for Common Features in Oracle Applications Cloud.
543
Integrating with HCM Web Services
544
Oracle Human Capital Management Cloud Glossary
Glossary
absence case
A grouping of related absences that result from the same cause used for reporting purposes.
absence category
A group of related absence types for reporting purposes.
action reason
Action reasons provide further explanation to actions, for example, an action of transfer could have reasons such as
reorganization or career progression.
annualization factor
Multiplication factor used to convert base salary to an annualized amount
assignment
A set of information, including job, position, pay, compensation, managers, working hours, and work location, that
defines a worker's or nonworker's role in a legal employer.
business unit
A unit of an enterprise that performs one or many business functions that can be rolled up in a management hierarchy.
Calculation Card
Captures values required for payroll calculations for some earnings and deductions, such as absence payments and
involuntary deductions. You can also create various types of cards to hold default values for tax reporting units or
payroll statutory units for some countries.
compa-ratio
Salary as a percentage of salary range midpoint. 100 denotes salary at midpoint.
content item
An individual quality, skill, or qualification within a content type that you track in profiles.
content library
A repository of the content types and individual content items that can be associated with person profiles and profiles
for workforce structures such as jobs and positions.
545
content type
An attribute such as a skill, quality, or qualification that is added to a profile.
date-effective object
An object with a change history. Professional users can retrieve the object as of a current, past, or future date.
descriptive flexfield
Expandable fields used for capturing additional descriptive information or attributes about an entity, such as a customer
case. You may configure information collection and storage based on the context.
development goal
A goal that is geared toward facilitating the career growth of individuals so that they can perform better in their current
job or prepare themselves for advancement.
division
A business-oriented subdivision within an enterprise. Each division is organized to deliver products and services or
address different markets.
document category
A high level grouping of person documents such as visas, licenses, and medical certificates. Document subcategories
provide further grouping of document categories.
document type
A categorization of person documents that provides a set of options to control what document information to retain,
who can access the documents, whether the documents require approval, and whether the documents are subject to
expiry. A document type exists for a combination of document category and subcategory.
effective end date

For a date-effective object, the end date of a physical record in the object's history. A physical record is available to
transactions between its effective start and end dates.
effective sequence number

A number that identifies the order of changes made to a date-effective object in one day. On any day, the physical
record with the highest number is the current record.
effective start date

For a date-effective object, the start date of a physical record in the object's history. A physical record is available to
transactions between its effective start and end dates.
element
Component in the calculation of a person's pay. An element may represent a compensation or benefit type, such as
salary, wages, stock purchase plans, pension contributions, and medical insurance.
546
element entry
The record controlling an employee's receipt of an element, including the period of time for which the employee
receives the element and its value.
eligibility profile
A user-defined set of criteria used to determine whether a person qualifies for a benefits offering, variable rate or
coverage, compensation plan, checklist task, or other object for which eligibility must be established.
extensible flexfield
Expandable fields that you can use to capture multiple sets of information in a context or in multiple contexts. Some
extensible flexfields let you group contexts into categories.
fast formula
A simple way to write formulas using English words and basic mathematical functions. Formulas are generic
expressions of calculations or comparisons that repeat with different input values.
flexfield
A flexible data field that you can configure such that it contains one or more segments or stores additional information.
Each segment has a value and a meaning.
flexfield segment
An extensible data field that represents an attribute and captures a value corresponding to a predefined, single
extension column in the database. A segment appears globally or based on a context of other captured information.
flow
An occurrence or instance of a flow pattern that you manage from a payroll work area or from the Data Exchange work
area using the View Extracts task. The data security for your role determines which flows you can submit and access.
flow checklist
A sequence of automatic and manual flow tasks grouped into activities, such as extract reports and processes, or tasks
related to payroll processing. Submitting a flow generates a checklist. Use the checklist to monitor the flow and manage
its tasks.
flow pattern
A series of tasks performed in a predefined order, which are grouped into activities, such as extract reports and
processes, or tasks that cover a phase of the payroll process. The flow pattern is used to generate a flow, which you can
manage from its checklist.
547
FTE
Abbreviation for full-time equivalent, such as .5 for half-time work.
global name
A person's name in a format and language that can be understood throughout a multinational enterprise.
global transfer
The transfer of a person to another legal employer.
goal plan
A collection of performance goals that are grouped by common characteristics, such as a specified time frame or a
particular department that must work on them.
goal plan set

One or more performance goal plans that you assign as a group to a population set.
grade
A component of the employment model that defines the level of compensation for a worker.
grade ladder
A hierarchy used to group grades and define their sequence.
grade rate
Used to define pay values for grades in a legislative data group.
grade step
A level of increment within a grade.
grade step progression

The advancement of workers through a sequence of grades or steps within a progression grade ladder, according to
progression rules.
Groovy
An object-oriented programming language for the Java Platform used as an alternative to the Java programming
language. Groovy can also be used dynamically as a scripting language.
HCM Data Loader data set

A set of data supplied together in either compressed data (.dat) files or a spreadsheet to be uploaded to Oracle HCM
Cloud.
548
HR
Abbreviation for human resource.
job
A generic role that's independent of any single department or location. For example, the jobs Manager and Consultant
can occur in many departments.
job family
A group of jobs having different but related functions, qualifications, and titles. For example, you may group a trust
analyst and an operations analyst into the Analyst job family.
job role
A role, such as an accounts payable manager or application implementation consultant, that usually identifies and
aggregates the duties or responsibilities that make up the job.
key flexfield
Configurable flexfield comprising multiple parts or segments, each of which has a meaning either individually or in
combination with other segments. Examples of key flexfields are part numbers, asset category, and accounts in the
chart of accounts.
LDAP
Abbreviation for Lightweight Directory Access Protocol.
legal employer
A legal entity that employs people.
legislative data group

A means of partitioning payroll and related data. At least one legislative data group is required for each country where
the enterprise operates. Each legislative data group is associated with one or more payroll statutory units.
local name
A person's name in a format and language that are readily understood by users in a single country but that may not be
understood throughout a multinational enterprise.
549
lookup code
An option available within a lookup type, such as the lookup code BLUE within the lookup type COLORS.
lookup type
The label for a static list that has lookup codes as its values.
model profile
A collection of the work requirements and required skills and qualifications of a workforce structure, such as a job or
position.
offering
A comprehensive grouping of business functions, such as Sales or Product Management, that is delivered as a unit to
support one or more business processes.
organization goal
A performance goal that specifies the overall objectives of the organization.
payroll relationship
Defines an association between a person and a payroll statutory unit based on payroll calculation and reporting
requirements.
payroll statutory unit

A legal entity registered to report payroll tax and social insurance. A legal employer can also be a payroll statutory unit,
but a payroll statutory unit can represent multiple legal employers.
performance goal
A results-oriented goal, often using specific targets, to assess the level of a worker's achievement.
person number
A person ID that is unique in the enterprise, allocated automatically or manually, and valid throughout the enterprise for
all of a person's work and person-to-person relationships.
person type
A subcategory of a system person type, which the enterprise can define. Person type is specified for a person at the
assignment level.
position
A specific occurrence of one job that's fixed within a department. It's also often restricted to one location. For example,
the position Finance Manager is an instance of the job Manager in the Finance Department.
550
progression grade ladder

A hierarchy used to group grades and define their sequence. It includes the associated rates and progression rules for
each grade and step within the ladder.
progression rule
A set of criteria used to determine whether a worker is eligible to advance to a specific grade or step within a
progression grade ladder.
quartile
Salary range divided into four equal parts. Quartile 1 is the lowest.
reference data set

Contains reference data that can be shared across a number of business units or other determinant types. A set
supports common administration of that reference data.
role mapping
A relationship between one or more roles and one or more assignment conditions. Users with at least one assignment
that matches the conditions qualify for the associated roles.
role provisioning
The automatic or manual allocation of a role to a user.
salary basis
Defines validation and payroll details for worker base pay. It identifies the currency and period of the quoted base
pay and the factor used to annualize base pay. It optionally identifies components or rates used to itemize salary
adjustments and the grade rate used to validate salary.
salary component
Change reasons that enable itemization of salary adjustments by entering amounts or percentages for one or more
components, such as merit or cost of living adjustment.
set
Classified and grouped reference data that organizational entities share.
specialization
A logical grouping of courses aimed to help learners achieve learning goals that a single course can't achieve. A
specialization contains one or more sections, which are containers for the courses.
stage table
An intermediate table to which records are loaded from a spreadsheet or file and where some validation occurs.
551
succession plan
A plan that identifies candidates for a role or position or to succeed a named incumbent.
succession plan owner

A person who can manage succession plans. Valid actions depend on the owner's administrator type, which can be
Administrator, Candidate Manager, or Viewer.
talent pool
A selected group of workers for whom you track training, readiness, or development.
talent pool owner

A human resource specialist who can manage a talent pool.
talent review
A series of meetings where organization managers evaluate trends, assess strengths, and address areas of risk for the
organization.
talent review facilitator

Human resource specialist who manages talent review meetings. A talent review meeting can have multiple facilitators.
talent review participant

Person who's invited to attend a talent review meeting.
temporary assignment
The transfer of a person for a limited term. You terminate the temporary assignment at the end of a term, facilitating
the person's return to the source assignment.
time attribute
A qualifier associated with a time event or time entry that reflects how the time is paid, costed, billed, or recorded as an
information entry. For example, the payroll time type attribute indicates whether time for payroll consumers should be
paid as Regular, Overtime, or Vacation.
tree node
One of the branching points in a tree structure. It corresponds to a primary key in the view object of data.
tree version
An instance of a tree that includes life cycle elements such as start and end dates, and indicates whether the tree is
active. If a tree is associated with a reference data set, all tree versions belong to one set.
552
URL
Abbreviation for Uniform Resource Locator.
view object
A component that simplifies querying and working with business object rows.
work relationship
An association between a person and a legal employer, where the worker type determines whether the relationship is a
nonworker, contingent worker, or employee work relationship.
worker time entry profile

A collection of layout rules and specifications that determine the time card appearance and control when employees
can take action on their time cards.
worker time processing profile

A collection of the time card period and the time entry and time calculation rule sets for both the employee and the time
consumer.
XML
Abbreviation for Extensible Markup Language.
553
554

Integrating With HCM PDF

Uploaded by

Copyright:

Available Formats

Integrating With HCM PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Integrating With HCM PDF

Uploaded by

Copyright:

Available Formats

What are some examples of reference data mentioned?

What are some examples of reference data mentioned?

What are some of the main concepts discussed in the glossary?

What are some of the main concepts discussed in the glossary?

Oracle Human Capital

Integrating with HCM

1 Introduction to Integrating with Oracle HCM Cloud 1

2 Introduction to HCM Data Loader 9

3 Data File Instructions and Delivery 19

4 Preparing to Use HCM Data Loader 31

6 Loading Date-Eective Data 57

7 Loading Flexeld Data 69

8 Loading Setup Objects 75

10 Loading Worker-Related Objects 127

11 Loading Work Structures 143

12 Loading Compensation Objects 165

13 Loading Payroll Relationships 187

14 Loading Payroll Setup Objects 195

15 Loading Payroll Transactional Data 235

16 Initializing and Adjusting Balances 251

17 Loading Payment Methods 265

18 Loading Payroll Costing 277

19 Loading Payroll Data Using Transformation Formula 293

20 Loading Talent Objects 309

21 Loading Learning Objects 329

22 Loading Absences Topics 337

23 Loading Benets Objects 341

24 Importing and Loading Data Using HCM Data Loader 347

25 Data Loading Using Spreadsheets 359

26 Introduction to HCM Spreadsheet Data Loader 363

27 HCM Spreadsheet Data Loader Templates 373

29 Postload Processing 399

30 Purging Person Data from Test Environments 405

33 Time, Absence, and Pension Data for Payroll 439

34 Managing HCM Extracts 465

35 Filtering and Delivering HCM Extracts 491

36 Flow Paerns 501

37 Benets Data Extract 515

38 Talent Review and Succession Management Data Extract 529

39 Transferring Encrypted Data 533

40 Oracle Taleo Recruiting Cloud Service Integration 539

41 Web Services 543

Using Oracle Applications

• Training: Take courses on Oracle Cloud from Oracle University.

> Greater than symbol separates elements in a navigation path.

Access to Oracle Support

Comments and Suggestions

1 Introduction to Integrating with Oracle HCM

Overview of Integrating with Oracle HCM Cloud

Chapter Title Contents

1 Introduction to Integrating with Oracle An introduction to this guide and an

Data Loading Using HCM Data Loader

Chapter Title Contents

2 Introduction to HCM Data Loader An introduction to HCM Data Loader and

4 Preparing to Use HCM Data Loader Seing conguration parameters, dening

Chapter Title Contents

5 Data Preparation General guidance for preparing various

6 Loading Date-Eective Data How to load date-eective objects

7 Loading Flexeld Data How to load data for descriptive and