Implementing Global Payroll Interface

Oracle Global Human
Resources Cloud
Implementing Global Payroll

Interface
19D
Oracle Global Human Resources Cloud
Implementing Global Payroll Interface
19D
Part Number F22113-02
Copyright © 2011, 2019, Oracle and/or its aliates. All rights reserved.
Author: Ipsita Mohanty
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 Payroll Interface 1
Overview .......................................................................................................................................................................................... 1
Implement Global Payroll Interface ........................................................................................................................................... 2
Payroll Employment Model ........................................................................................................................................................ 4
Payroll Relationship Rules ........................................................................................................................................................... 5
Payroll Relationships .................................................................................................................................................................... 6
2 Payroll Interface Extracts 9

How Extract Components Work Together .............................................................................................................................. 9
Extract Payroll-Related Data ..................................................................................................................................................... 10
3 Set up Payroll Interface 15

Set up License Type for Country or Territory ....................................................................................................................... 15
Dene Enterprise Structures for Payroll Interface ............................................................................................................... 15
Load Geographies ....................................................................................................................................................................... 16
Legislative Data Groups ............................................................................................................................................................. 17
Payroll Legislative Data .............................................................................................................................................................. 17
Create a PSU and Associate it with a LDG ............................................................................................................................ 19
Creating Payroll Denitions ...................................................................................................................................................... 19
Create a Payment Method ........................................................................................................................................................ 21
Managing Conguration Groups .............................................................................................................................................. 21
Creating Payroll Elements ......................................................................................................................................................... 22
Associate Employees with Payroll ........................................................................................................................................... 27
Manage Payroll and Salary Denitions .................................................................................................................................. 27
Manage Salary for Payroll Interface ....................................................................................................................................... 28
Options to Extract Terminated Employees ........................................................................................................................... 30
4 Global Payroll Interface Extract 31

Overview ........................................................................................................................................................................................ 31
Payroll Interface Extract Flow Parameters ............................................................................................................................ 32
Eective Dates ............................................................................................................................................................................. 33
Set up Object Groups ................................................................................................................................................................. 35
Action Indicators for Payroll Interface ................................................................................................................................... 36
Create Rate Denitions ............................................................................................................................................................. 40
Transactional and Operational Recommendations ............................................................................................................. 41
Copy Delivered Extract Denitions ......................................................................................................................................... 42
Use Extensible Fields to Include Additional Aributes ....................................................................................................... 42
Submit the Global Payroll Interface Process ........................................................................................................................ 43
Global Payroll Interface Extract FAQs .................................................................................................................................... 44
5 Payroll Interface for ADP Global Payroll 47

Overview ....................................................................................................................................................................................... 47
Salary History Information for ADP Global Payroll Interface ............................................................................................ 48
Additional Payroll Interface Data Elements .......................................................................................................................... 49
Run Global Payroll Interface Processes .................................................................................................................................. 51
Congure Prior Values ............................................................................................................................................................... 53
Set up Additional Elements ...................................................................................................................................................... 54
Manage Payroll Interface Data Values ................................................................................................................................... 56
Override the Cost Center Using Congurable Cost Center Override Aribute .............................................................. 57
Congure Dynamic File Names for Global Interface .......................................................................................................... 57
Transactional Recommendations ............................................................................................................................................ 61
Operational Recommendations ............................................................................................................................................... 62
Increment Process Dates Automatically ................................................................................................................................ 63
Enable Access to Global Payroll Local Data in ADP ............................................................................................................ 64
Payroll Interface for US ADP Payforce .................................................................................................................................. 66
6 Payroll Interface for ADP Workforce Now 133

Overview of ADP Workforce ................................................................................................................................................... 133
Delivered Contexts and Segments ........................................................................................................................................ 133
Delivered Lookups .................................................................................................................................................................... 136
Create Payroll Elements ........................................................................................................................................................... 138
Business Requirements ............................................................................................................................................................ 142
Termination and Rehire Requirements ................................................................................................................................ 144
How You Split Personal Payment Methods ........................................................................................................................ 146
7 Payroll Interface Inbound Records 149

Overview ...................................................................................................................................................................................... 149
Manage Inbound Records ........................................................................................................................................................ 151
Processed Payroll Values ......................................................................................................................................................... 151
Congure Extensible Flexelds and Lookups ..................................................................................................................... 152
8 Data Validation and Data Deletion Reports for Payroll Interface 155
Generating Data Validation Report ....................................................................................................................................... 155
Generating Deleted Data Report ............................................................................................................................................ 156
Oracle Global Human Resources 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 Global Human Resources 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:
oracle_fusion_applications_help_ww_grp@oracle.com.
ii
Oracle Global Human Resources Cloud Chapter 1
Implementing Global Payroll Interface Payroll Interface
1 Payroll Interface
Overview
Oracle Global Payroll Interface sends personal payroll information to third-party payroll providers and imports
processed payroll data into Global HR. You can copy and modify predened extract denitions to meet the
requirements of your third-party payroll provider.
In a legislative data group that uses the Payroll Interface, you can do these actions:
• Extract employment, salary, and compensation details from HCM to send to a third-party payroll provider.
• Import payroll processed data, pre-generated payslips, and messages to exelds. This processed payroll data
is available within the application for further reporting and analysis.
This gure shows the inbound and outbound interfaces that enable applications to interact with third-party payroll
service providers.
Calculation Engine Fusion HR XML
HCM Extract Transform Customer Specific

Output File
Export
Tax Card
BI Publisher
Elements Reporting Result File
Balances
Template
Solution Backfeed
Predefined
DOR Documents OTBI Reports HDL
Payslip
Global Payroll Interface
Extract Data from HCM

Use these predened extract denitions.
Note: Create a copy of the delivered extract denition for additional congurations.
1
Extract Description
Global Payroll Interface

Extracts information that any global payroll provider requires, such as the name, address,
salary, and deductions details of your employees. For more information, see Section Global
Payroll Interface Extract.
US ADP PayForce Third-Party

Periodic Extract Extracts payroll data to transform it into HR-XML format for ADP PayForce and ADP
Connection for PayForce users. For more information, see Section US ADP PayForce Third-
Party Periodic Extract Denition.
US ADP PayForce Third-Party Ad-Hoc

Extract Extracts payroll data to transform it into HR-XML format for ADP PayForce and ADP
Connection for PayForce users. For more information, see Section US ADP PayForce Third-
Party Ad-Hoc Extract Denition.
Payroll Interface for ADP Global

Payroll Extracts information, such as the salary and earnings details of employees in the format that
ADP Global Payroll requires. For more information, see Section Payroll Interface for ADP
Global Payroll.
Payroll Interface for ADP Workforce

New Extracts payroll data for ADP Workforce New. For more information, see Section Payroll
Interface for ADP Workforce New.
Import Third-Party Payroll Processed Data and Payslips

Use HCM Data Loader to import these categories of data from third-party payroll providers on a periodic basis:
• Processed payroll data, such as net pay, general ledger account codes, cost center codes, depending on the
practices of your payroll provider.
• Notication messages, such as conrmation of number of transactions received or processed, or warning
information.
• Pay slips, for example in PDF format.
The application associates each imported record with a master record that species a payroll name and payroll period. It
stores the imported data in inbound tables and pay slips as document of records.
Related Topics
• Extract Components
• Options to Extract Payroll-Related Data
• Overview of HCM Data Loader
• Overview of Payroll Interface Inbound Records
• Implement Payroll Interface
2
Implement Global Payroll Interface

Use the Workforce Deployment and Compensation Management oerings to congure and manage Payroll
Interface. Use predened payroll interface extract denitions to send payroll-related employee information to a third-
party payroll provider. The setup steps required for payroll interface vary depending on your business requirements.
Workforce Deployment Oering

This table species the functional areas of the Workforce Deployment oering that you use to set up payroll interface.
For the full list of functional areas and features in this oering, use the Associated Features report.
Functional Area Use To
Payroll Create payroll denitions, payment methods, and LDGs, dene an element, manage salary, set
up salary basis and object groups.

For more information about Payroll, refer to the Implementing Global Payroll guide.

Enterprise Prole Load geographies to create the geography structure for each country.

For more information about Enterprise Prole, refer to the Implementing Global Human
Resources guide.

Legal Structures Create legal jurisdiction for your country or territory and additional Tax Reporting Units.

For more information about Legal Structures, refer to the Implementing Global Human
Resources guide.

Organization Structures Create business units to associate with other objects.

For more information about Organization Structures, refer to the Implementing Global Human
Resources guide.

HCM Data Extract Congure Process Conguration Group prole options.

For more information about HCM Data Extract, refer to the Implementing Global Human
Resources guide.

Elements and Formula Dene payroll elements.

For more information about Elements and Formula, refer to the Implementing Global Payroll
guide.

3
Compensation Management Oering

Use the Workforce Compensation functional area to congure salary basis and to associate it base pay element.
Related Topics
• Plan Your Implementation
Payroll Employment Model

In the payroll employment model, each person has a payroll relationship to a payroll statutory unit (PSU), and one or
more payroll assignments and other employment structures.
Comparing the HR and Payroll Employment Models

This diagram shows the human resource (HR) employment model and the payroll employment model contrast where
two legal employers, Manufacturing and Installation belong to one PSU, Sun Power. As you can see, David Ellis has two
4
assignments where the HR model creates two work relationships and the payroll employment model creates one payroll
relationship.
Payroll Statutory Unit Sun Power
Legal Manufacturing Installation

Employers
David Ellis David Ellis
Payroll Relationship
Work Relationship Work Relationship
Payroll Statutory Unit
Manufacturing Installation
Sun Power
Assignment Assignment Assignment Assignment

Project Manager Trainer Project Manager Trainer
Related Topics
• Payroll Employment Hierarchy Prole Options
• Employment Level Options for Elements
• How do I diagnose payroll employment model setup issues
5
Payroll Relationship Rules

The payroll relationship rule determines what happens when you terminate the last active employment assignment
record for a payroll relationship. The rule also determines whether the application creates a payroll relationship when
you add a new assignment record for an employee. This topic describes the following predened rules that localizations
can use.
Lifetime Rule
When a work assignment is terminated, the associated payroll relationship continues to remain active. When you create
an assignment, the application searches for an active payroll relationship of the same type and for the same payroll
statutory unit (PSU). If found, the new assignment is aached to the existing active payroll relationship. If not, a new
payroll relationship is generated.
Continuous Period of Service Rule

When a work assignment is terminated, the associated payroll relationship becomes inactive and is terminated.
Subsequently, when you create an assignment, the application searches for an active payroll relationship of the same
type and for the same PSU. If a payroll relationship exists, date validation occurs to determine whether to use the
existing payroll relationship or to create one. The application compares the start date of the new assignment to the last
standard earnings date of the existing payroll relationship. If the start date is before the last standard earnings date, the
application uses the existing payroll relationship, otherwise, it creates one.
Independent Rule
When a work assignment is terminated, the associated payroll relationship becomes inactive and is terminated. When
you create an assignment, a new payroll relationship is created. Each payroll relationship is associated with one work
assignment.
Related Topics
• How Terminations Aect Payroll Processing
Payroll Relationships
A payroll relationship represents the association between a person and a payroll statutory unit (PSU), which is the legal
entity responsible for employee payment. Payroll relationships group a person's employment assignment records
based on the payroll statutory calculation and reporting requirements. Payroll relationships facilitate the capture and
extraction of HR and payroll-related data sent to a third party, such as a payroll provider for payroll processing.
Payroll processing always occurs at the payroll relationship level. When you display the payroll process results for a
person, you rst select the person's payroll relationship record and then drill down to view details.
Payroll relationships aggregate balances at the payroll relationship level. Within a payroll relationship, payroll processes
can aggregate balances for multiple assignment records. Balances don't span payroll relationships.
6
Create Payroll Relationship Records and Mapping Rules

The mapping between the system person type and the payroll relationship type must exist for certain processes. For
example, to create a payroll relationship record automatically during the rehire process. You must use the payroll
relationship types predened in the application. You can't create your own.
This table shows the predened payroll relationship type.
Payroll Relationship Type Description
Standard Person types mapped to this payroll relationship type are included in payroll runs.

Element Entry Only Person types mapped to this payroll relationship type have only element entries created for
them and are excluded from payroll processing.

Relationship mapping rules, which map system person types to payroll relationship types, can vary by country or
territory. The mapping rules are predened for each legislation.
This table shows the mapping between system person types and payroll relationship types applicable for Canada where
Contingent Worker type, Retiree, and Nonworker Unpaid type are excluded from payroll processing.
System Person Type Payroll Relationship Type
Contingent Worker Element Entry Only

Employee Standard

Nonworker Paid Standard

Nonworker Unpaid Element Entry Only

Retiree Element Entry Only

A payroll relationship can't end while active employment assignments are present. When all employment assignments
are ended, a payroll relationship could either remain active or become end dated. A payroll relationship depends on the
legislation and the payroll relationship rules applicable for the legislation. For example:
• For the US, relationships that remain active enables future rehire within the same payroll relationship and PSU.
• For the UK, for a relationship that gets terminated, a new payroll relationship is created within the same payroll
relationship and PSU, for the rehire.
Related Topics
• Element Duration Dates
• How to Set End Dates for Terminations
7
• Time Card Required Option
8
Implementing Global Payroll Interface Payroll Interface Extracts
2 Payroll Interface Extracts
How Extract Components Work Together

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.
9
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
• HCM Extract Types
• Dene Extracts
• Overview of Generating Flexeld Database Items
• How Extracts are Validated
Extract Payroll-Related Data

10
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)

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
11
User Entity Name and Code Description
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
• Best Practices for Viewing User Entity Details
Options to Extract Payroll-Related Data

The payroll interface supports dierent methods for dening extracts that enable you to extract payroll-related data.
This table summarizes these methods, the user entities they use, and what values they return.
Method User Entity Returns
Element Entries ELEMENT ENTRIES All element entry values for a payroll
relationship.

Payroll Run Result Values PAY_ EXTRACT_ RUN_ RESULT_ All run results for a payroll relationship
VALUES_UE action. Includes calculation card
information if congured.

Balance Values Base name of the database item group All balance values for the specied
for the balance (direct) or balance group balance or balance group for a payroll
(indirect) relationship action.

Element Entries
To extract element entry values, include the ELEMENT ENTRIES user entity in the payroll interface extract. This user
entity is available for all element classications and returns all element entry values for a given payroll relationship. Use
extract data group criteria to further lter the records.
To retrieve element entry values, set these context in the extract denition:
• EFFECTIVE_DATE
• PAYROLL_RELATIONSHIP_ID
• DATE_EARNED
Payroll Run Results

To extract values from the results of processes, include the PAY_EXTRACT_RUN_RESULT_VALUES_UE user entity in
your extract denition. This user entity is available only for element classications that the Calculate Gross Earnings
process uses, such as standard and supplemental earnings. All the run results for a payroll relationship action is
returned.
12
If you use the Calculate Gross Earnings process and have dened regular or supplemental earnings elements, set the
PAY_REL_ACTION_ID context in the extract denition. Use the PAY_INTERFACE_PAYROLL_REL_UE to set this context.
Include this user entity and context if your extract must include informational values from calculation cards, such as
deduction information for child support payments.
Balances
Extract balance values directly by the database item group name generated for the balance or indirectly through a
balance group to extract balance values.
Note: Balances are created and maintained as result of processed element entries. Balance values are only
available when you process element entries in a payroll run or use the Calculate Gross Earnings process.
To use balance groups, include one of these record types and context in your extract denition.
Record Type Context
Balance Group Ensure that all contexts are available in the current data group.

Balance Group with Automated Ensure that PAYROLL_ REL_ACTION_ID is set in the current or parent data group so that
Resolution of References context is derived.

Extracting Calculation Card Values

You can add CIR data groups in your copied extract.
1. Navigate to the Data Exchange work area and select Manage Extract Denitions.
2. Search for and select the copied extract.
3. Click Switch Layout.
4. Change the Eective Date to 01/01/0001 and click Data Group.
5. Delete the NL Statutory Deductions and Reporting data group and click Save.
6. Click Create Data Group (Template) to create the new data group.
7. Enter these details.
Field Value
Name NL Statutory Deductions and Reporting

Template Extract Denition Statutory Deductions and Reporting

Template Data Group Statutory Deductions and Reporting (Payroll Relationship)

8. Click Save and Close.

9. Click Connect Data Groups for the NL Statutory Deductions and Reporting data group.
10. Click Save.
13
11. Add Hierarchical record for the NL Legislative Information data group.
12. Click Data Group NL Legislative and add a hierarchical record to it.
13. Enter these hierarchical record details.
Field Value
Sequence 30

Name NL Statutory Deductions and Reporting

Tag Name StatutoryDeductionsandReporting

Type Hierarchy Traverse Only


15. Validate the extract.
14
Implementing Global Payroll Interface Set up Payroll Interface
3 Set up Payroll Interface
Set up License Type for Country or Territory

Use the Manage Feature by Country or Territory task to set up Payroll Interface as the Selected Extension.
Complete these steps:
1. Sign in as an administrator.
2. Search for and select Manage Features by Country or Territory to open the Manage Features by Country or
Territory page.
3. For the country you're performing the implementation,, select Payroll Interface in the Selected Extension
column.
4. Click Save.
Dene Enterprise Structures for Payroll Interface

You can model the enterprise to meet legal and management objectives. Include the enterprise structures that are
required to support payroll relationships for your workers. Use the Manage Enterprise HCM Information task to
congure implementation specic details at the enterprise level.
To conrm your enterprise structures setup, perform these actions.
Verify predefined Define legal Create Legislative

geographies jurisdiction Data Group
Create Business Create Tax Associate each

Units Reporting Units PSU with LDG
In the Setup and Maintenance work area:

1. Go to the following task to verify the predened geographies and to load any additional local geographies:
◦ Oering: Workforce Deployment
15
◦ Functional Area: Enterprise Prole

◦ Task: Manage Geographies
2. Go to the Dene Legal Jurisdictions and Authorities task list to create the following:
◦ A legal jurisdiction if not already created or predened for your country or territory.
◦ A legal authority for each government body that you interact with.
◦ Addresses for legal entities and legal authorities.
You can use the following Oering and Functional Area to go to the Dene Legal Jurisdictions and Authorities
task list.
◦ Functional Area: Legal Structures
3. Go to the Manage Enterprise HCM Information task to create a legislative data group (LDG) for each country
of operation to partition your payroll data.
◦ Functional Area: Workforce Structures
4. Go to the Manage Legal Entity task to do the following:
◦ Functional Area: Legal Structures
You can use the following Oering and Functional Area to go to the Manage Legal Entity task.
◦ Create at least one legal entity designated as a payroll statutory unit (PSU) for each LDG.
◦ Associate each PSU with one LDG.
◦ Optionally, create calculation cards for statutory deductions for each PSU, if supported by the LDG.
5. Use the Manage Legal Reporting Unit to do the following:
◦ Create any additional tax reporting units (TRU) that you need.
◦ Optionally, create calculation cards for statutory deductions for each TRU, if supported by the LDG.
6. Use the Manage Business Unit task list to create business units that you use to associate other objects.
◦ Functional Area: Organization Structures
Related Topics
• What's a payroll statutory unit
• Update Existing Setup Data
Load Geographies
Load geographies to create the structure for each country. In turn, a geography structure denes the geography types
that are part of the country structure. Also, it describes how the geography types are hierarchically related within the
country structure. For example, you can create geography types called State, City, and Postal Code. Use the Load
Geographies for US task to load geographies.
Note: For United States and Canada, use these two tasks for loading geography data from Vertex:
• Load Geographies for United States
• Load Geographies for Canada
16

1. Go to these areas:
◦ Functional Area: Workforce Structures
◦ Task: Load Geographies for US
2. On the Load Geographies for US page, Processes tab, select the Validate Input Parameters and Load
Geography Information job.
3. In the Data Source eld, ensure that you have selected Vertex.
4. Click Submit and monitor the process to completion.
Related Topics
• Geography Hierarchy
Legislative Data Groups

Legislative data groups are 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. Each payroll statutory unit can belong to only one legislative data group.
Payroll-related information, such as elements, is organized by legislative data group. Each legislative data group:
• Marks a legislation in which payroll is processed.
• Is associated with a legislative code, currency, and its own cost allocation key exeld structure.
• Is a boundary that can share the same set up and still comply with the local laws.
• Can span many jurisdictions as long as they're within one country.
• Can contain many legal entities that act as payroll statutory units.
Payroll Legislative Data

Use the Congure Legislations for Human Resources task in the Setup and Maintenance work area to create and edit
payroll rules for countries or territories not initially provided by Oracle.
Objects you congure include:
• Legislative rules
• Element classications
• Valid payment types
• Component groups
• Balance dimensions
• Legislative data groups
17
Legislative Rules
Legislative rules govern how to manage employee records when you rehire employees into your organization. For
example, for some countries, a rehire continues to be associated with the earlier payroll relationship, thereby having
access to prior data, such as all year-to-date balances. Yet for other countries, a rehire creates a new payroll relationship
record with no access to prior data. The statutory rules for your country or territory would determine the selections you
make, such as the starting month of the tax year.
The legislative rules you can congure include mappings between system person types and payroll relationship types.
This mapping controls which person types can be included in payroll calculation processing, such as the Calculate Gross
Earnings process.
Note: You can't undo payroll relationship type mapping. If you select an element entries only option for a
person type and then at a later date decide to use the Calculate Gross Earnings process, the process won't
generate results for that person type. Consider using a standard option to provide more exibility.
Element Classications
Element classications are collections of related elements. You select the primary classications you want to include
for your elements. You can provide new display names for element classications to match the terminology that's most
appropriate for the country or territory.
Valid Payment Types

Payment types are the means by which you issue payments to workers. The predened payment types are Check Cash,
EFT (electronic funds transfer), and International Transfer. You can provide new display names for payment types to
match terminology that's most appropriate for the country or territory.
Component Groups
Component groups are logical sets of payroll components, which are the rates and rules that determine calculated
values for some earnings and deduction elements. You can provide new display names for the component groups you
want to support to match terminology that's most appropriate for the country or territory.
The Congure Legislations for Human Resources task creates a calculation card denition and payroll components for
each component group you enable. When you create elements in certain classications and categories, the element
template associates the element with a payroll component and creates calculation components that you can add to
workers' calculation cards. The calculation card creates the components for the component groups you selected. The
element template then associates these components with the statutory elements you create. Ensure that you associate
these components with your employees through element eligibility for calculation to be processed.
Depending on the legislative rules, if you enable the Federal or Social Insurance component groups and set your
country extension on the Manage Features by Country or Territory page to Payroll Interface for this country or territory,
hiring workers automatically creates a statutory deduction calculation card for them. Ensure that you create eligibility
records for your statutory deduction elements before hiring any workers.
Balance Dimensions
Balance dimensions identify the specic value of a balance at a particular point in time, based on a combination of
criteria, including time, employee relationship level, jurisdiction, and tax reporting unit. You can provide new display
names for the balance dimensions you want to support to match terminology that's appropriate for the country or
territory.
18
The Congure Legislations for Human Resources task creates some predened balances that the application uses
within the statement of earnings, such as Gross Earnings and Net Pay. Additionally, the Net Payment balance is required
to set up organization payment methods.
Legislative Data Groups

Use the Manage Legislative Data Groups task in the Setup and Maintenance work area to dene at least one legislative
data group for each country or territory where your enterprise operates.
Create a PSU and Associate it with a LDG

Use the Manage Legal Entity task to create a Payroll Statutory Unit and associate it with a LDG.
◦ Functional Area: Payroll
◦ Task: Manage Legal Entity
2. On the Create Legal Entity page, Name eld, enter InFusion USA West.
3. In the Legal Entity Identier eld, enter US0033.
4. Optionally, enter Start Date. When the start date is blank, the legal entity is eective from the creation date.
5. Optionally, enter an End Date.
6. Select the Payroll statutory unit check box.
7. Select the Legal employer check box.
8. Enter the registration information.
9. In the Legal Address eld, search for and select a legal address. Ensure that the legal address is entered
previously using the Manage Legal Address task.
10. In the EIN or TIN eld, enter either the EIN or TIN.
11. In the Legal Reporting Unit Registration Number eld, enter the registration number.
Related Topics
Creating Payroll Denitions

Payroll denitions indicate the payment frequency and processing schedule. Use payroll denitions to group employees
with similar pay characteristics. You can associate employees with payroll through payroll relationships.
Dene one payroll for each payment frequency to pay employees, which the enterprise can use to pay its employees.
You can use three pay frequencies, namely Monthly, Bi-weekly, and Weekly to process payments for the dierent
categories of your employees.
While you create payroll denitions, use these denitions to specify payroll details:
• Eective Start Date
19
• First Period End Date

• Number of Years
Eective Start Date

The eective start date is the rst date when the payroll denition is available for employee data. The start date must be
on or before the earliest date of any historical data that you want to load.
For example, for a payroll starting on 1/1/2013 with ve years of historical payroll data to load, set the start date of the
payroll denition to 1/1/2008.
The eective start date doesn't aect the generated calendar of payroll periods. The start date for the rst payroll period
is based on the rst period end date.
First Period End Date

The rst period end date is the end date of the rst payroll period that the application generates for a payroll denition.
It is based on the date of implementation, tax year, benets enrollments, or a particular payment cycle.
For example, if your weekly payroll work week is Saturday through Friday and your rst payment date is on 1/6/12, use
12/30/11 as the rst period end date.
Number of Years
The number of years represents how many years of time periods to generate starting from the beginning of the rst
payroll period, which the rst period end date determines.
After you save a payroll denition, you can only increase, but can't decrease this parameter. This is because the
application would have already generated a calendar of time periods.
To create payroll denitions, perform the following steps:

◦ Task: Manage Consolidation Group
2. On the Manage Consolidation Groups page, Search Results section, click Add Row from the Actions menu.
3. In the Name eld, enter a name.
4. In the Legislative Data Group eld, select a US Legislative Data Group.
5. Click Save.
6. Click Done to return to the Search page.
7. Search for and select the Manage Payroll Denitions task to open the Manage Payroll Denitions page.
8. In the Search Results section, click Create from the Actions menu.
9. In the Legislative Data Group eld, select a LDG.
10. Click Continue to open the Create Payroll: Basic Details page.
11. Enter the details and click Next.
12. Click Next to open the Payroll Calendar page.
20
13. Repeat the above steps to create other payroll denitions.
Related Topics
• Create Payroll Denitions
Create a Payment Method

Payment methods indicate the method of payment, such as check, cash, or credit. They associate a source bank
account with each such payment types. Do not specify a run type while you create a personal payment method because
it doesn't hold any signicance in a payroll interface scenario.
To create a payment method and associate it to a payment source, perform these steps:

◦ Task: Manage Organization Payment Methods
2. On the Manage Organization Payment Methods page, click Create to create a payment method under the US
legislative data group.
3. In the Payment Type eld, select Check.
4. In the Payment Sources section, select Create from the Actions menu to open the Create Payment Source
page.
5. Provide the bank account and payment information details.
6. On the Create Payment Source page, complete the eld in order as shown in the table:
Field Value
Name Payroll EFT Source US

Bank Account Name Bank A

Bank Reference 123456789

Company Reference 456789012

7. Submit the changes.
Related Topics
21
Managing Conguration Groups

Payroll process conguration groups provide sets of processing parameters related to logging and performance.
Use the Manage Default Process Conguration Group Prole Option Values task to select the default group value
for the Process Conguration Group prole option.
• Oering: Workforce Deployment

• Functional Area: HCM Data Extract
Use the Manage Payroll Process Conguration task to review the default seings in the default conguration
group. For example, you might change the values for chunk size or number of threads to optimize performance when
calculating gross earnings.

• Functional Area: Payroll
Manage Personal Payroll Information

A payroll manager performs these steps to optionally upload personal payroll information, such as initial balance values
or employee bank details.
1. Follow these steps to load initial balances:
◦ Create balance initialization elements.

◦ Use the HCM Data Loader to load the initial values to the staging tables.
◦ Submit the Load Initial Balances task to initialize the balances in the Payroll Calculation work area.
2. To load personal bank information for EFT payments using any existing organization payment methods, use
the Manage Personal Payment Methods task in the Payment Distribution work area (for individual employees)
to migrate bank data.
Related Topics
• Set Up Payment Sources in Organization Payment Methods
Creating Payroll Elements

This example shows how to dene elements for a US legislative data group where the country extension is set to Payroll
Interface.
This table summarizes the key decisions for each element that you dene and provides the selections for this example.
22
Decision to Consider In This Example
What is the primary classication?

One of these choices:
• Standard Earnings
• Supplemental Earnings
• Taxable Benets
• Pretax Deductions
• Voluntary Deductions
Information elements aren't supported.
At which employment level should this element be aached?

Select the appropriate level. Typical examples are:
• Payroll relationship level for deductions and benets

elements
• Assignment or terms level for salary, pension, and social
insurance elements
• Assignment level for overtime rules, rates, and bonus
elements
Verify whether your third-party payroll provider can handle terms-

level information.
Does this element recur each payroll period, or does it require

explicit entry? Select Recurring or Nonrecurring.

What are the values to enter for deduction elements? Period Deduction Amount

Goal Amount

Dene an Element
Before you dene an element, ensure that your country extension is set to Payroll Interface on the Manage Features
by Country or Territory page. This seing controls the behavior of important payroll-related features, such as element
templates.
1. Navigate to these tasks:

◦ Functional Area: Elements and Formulas
◦ Task: Manage Elements
2. On the Manage Elements page, Search Results section, click Create.
3. Select your legislative data group.
4. Select the primary classication that matches the purpose or use of the payroll element.
23
Element Example Primary Classication
Recurring base pay Annual salary, hourly earnings Standard Earnings

Recurring payments Allowance Standard Earnings

Nonrecurring payments Bonus Supplemental Earnings

Recurring or nonrecurring voluntary Savings plans, charitable contributions, Voluntary Deductions

deductions or uniform deposit

5. In the Category eld, select Standard.

6. Select the secondary classication that corresponds to the selected primary classication.
Example Purpose or Use Secondary Classication
Recurring base pay Regular

Nonrecurring payment Bonus

Recurring voluntary deduction Select the relevant choice. If there is none, leave it blank.

7. Click Continue.
8. On the Basic Information page, complete these elds. Click Next.
Field Sample Value
Name Annual Salary

Hourly Wages

Allowance

Spot Bonus

Red Cross Contribution

Reporting Name Enter the name that you want to display on reports for this earnings or deduction payroll
element.

Eective Date 1/1/1951

Enter an early date so that the payroll element is available for use immediately.

24
Field Sample Value
Currency US Dollar

Should every person eligible for the No

element automatically receive it?

What is the earliest entry date for First Standard Earnings Date
this element?

What is the latest entry date for this Last Standard Process Date
element?

At which employment level should Select the appropriate level, such as terms or assignment level for salary.
this element be aached?

Does this element recur each payroll Recurring or Nonrecurring

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 this element in a payroll
period?

Process and pay element separately Does this element have a limit on the amount which is exempt from Federal Tax?
or with other earnings elements?

Does this element have a limit on No

the amount which is exempt from
Federal Tax?


the amount which is exempt at state
level?

9. Click Next.
10. On the Additional Details page, complete these details:
Field Value
What is the default periodicity of this Bimonthly

element?

25
Field Value
Periodicity Conversion Rule Standard Rate Annualized

11. Verify whether the information is correct, click Submit.
Set Up Values for Deduction Elements

Congure values for deductions and select the special purpose Primary Input Value as one of the values.
Specify a value that limits the amount deducted for a value using a goal amount for recurring elements.
1. On the Element Summary page, Element Overview hierarchy, select Input Values.
2. From the Actions menu, select Create Input Values.
3. For all deduction elements, enter these values:
Field Value
Name Name of the value, such as Period Deduction Amount

Display Sequence 1

Special Purpose Primary input value or Percentage

Unit of Measure Money

Create a Database Item Yes

4. For recurring deduction elements with a goal amount, name the value Goal Amount
5. Click Save.
6. Click Submit.
Set Up Element Eligibility

On the Element Summary page, update the newly dened element detail for eligibility.
1. From the Edit menu, select Update.

2. In the Element Overview hierarchy, select Element Eligibility.
3. From the Actions menu, select Create Element Eligibility.
4. In the Element Eligibility name eld, enter the element name with the sux as Open.
5. In the Eligibility Criteria section, select All payrolls eligible.
6. Save and submit the element.
26
Related Topics
Associate Employees with Payroll

You can associate new and existing employees to provide additional assignment information.
New Employees
When you hire an employee using the HCM hire ow, specify the payroll to which the employee must be mapped in the
Payroll Details sub section of the Assignment section.
Existing Employees
On the Manage Payroll Relationships page, you can associate newly-hired employees to the respective payroll.
1. On the Person Management page, search for the employee.
2. Click the employee name to open the Manage Employment page.
3. From the task pane, select the Manage Payroll Relationships task.
4. On the Manage Payroll Relationships page, add a payroll in the Payroll Details section.
Manage Additional Employee Information

You can manage additional employment information for payroll interface for ADP in one of these ways:
1. Use the New Person task when you hire an employee.
2. Use the Person Management task for existing employees.
Note: Ensure that you have loaded the master list of applicable values that ADP provides into the HCM
application before you map employees with those values.
Manage Payroll and Salary Denitions

Use the Manage Payroll Denitions task in the Payroll Calculation work area to specify payment frequency, processing
schedule for a particular payroll. Create at least one payroll denition for each payroll period type that you use to pay
employees.
Use payroll denitions to group employees with similar pay characteristics so that reporting and processing of payroll
by the third party payroll application becomes ecient.
27
Oering/Functional Area/Task Use To
Compensation Management / Congure salary basis that species the frequency of amount sent to payroll and stored
Workforce Compensation / Manage as salary. For more information about salary basis, see Section: Manage Salary for Payroll
Salary Basis Interface for ADP Global Payroll.

Workforce Deployment/ Payroll/ Extract data for either one payroll or multiple payrolls that are dened within a legislative data
Manage Object Groups group. You can also group employees. For more information about seing up object groups,
see Section: Set up Object Groups.

Workforce Deployment/ Payroll/ Convert the salary dened in one frequency to equivalent value in another frequency. For
Manage Rate Denitions more information about creating rate denitions, see Section: Create Rate Denitions.

Manage Salary for Payroll Interface

Salary components itemize new or adjusted salary into one or more components that reect dierent reasons for the
allocation, such as merit, adjustment, and location. To congure the use of salary components, use the Manage Salary
Basis task in the Compensation work area.
The salary basis species the frequency of the amount sent to payroll and stored as salary, such as annual or hourly
amount. Use the Manage Elements task to dene salary basis, which holds the payroll element for base pay.
Managing salary involves these steps
Identify salary Define base pay

Define salary basis
components element
Associate salary
Administer salary
basis to base pay
for employees
element
Perform these steps to create an element to use with salary basis.

◦ Functional Area: Elements and Formula
2. In the Search Results section, select Create from the Actions menu.
3. In the Create Element dialog box, enter these details:
28
Parameter Value
Legislative Data Group Legislative Data Group under which you want to create the element

Primary Classication Standard Earnings

4. Click Continue to open the Create Element: Basic Information page.

5. Enter these basic details:
Parameter Value
Name Annual Salary

Reporting Name Enter the name that you want to display on reports for this element.

Eective Date 1/1/1951. Enter an early date so that the payroll element is available for use immediately in
your salary bases.

What is the earliest entry date for First Standard Earning Date
this element?

element?

At which employment level should Match the employment level to the level at which the salary basis is associated with workers,
this element be aached? either Assignment Level or Term Level.

Does this element recur each payroll For base pay, use Recurring.
entry?

6. Complete the additional details as appropriate. Click Next.

7. Click Next to open the Create Element: Review page. Review the element denition.
8. Click Submit to open the Element Summary page.
9. In the Elements Overview section, select Element Eligibility. Select Create Element Eligibility from the
Actions menu. Create an open element eligibility for the element just dened.
Set up Salary Basis

The salary basis type species how to determine the salary amount for a worker.
Note: When managing salary for employees, use the salary basis with the frequency that matches up with the
employee pay frequency.
29
Here's how you can set up salary basis:
◦ Oering: Compensation
◦ Functional Area: Basic Payroll
◦ Task: Manage Salary Basis
2. On the Manage Salary Basis page, click Create.
3. On the Create Salary Basis page, specify the details.
4. Click Save and Close to return to the Manage Salary Basis page.
Related Topics
Options to Extract Terminated Employees

The application continues to process a terminated employee in payroll and make payments even after the employee
leaves the company or after their last regular salary has been processed.
These dates determine till when the application processes an employee in payroll.
• Last Standard Earning Date

• Last Standard Process Date
• Final Close Date
Last Standard Earning Date

The date till which the employee can be paid his regular salary. This date is the employee's actual termination date.
Last Standard Process Date

The date on which the last regular payroll for the employee is processed. This date is the period end date of the payroll
to which the employee is terminated.
Final Close Date

The date on which all selements to the employee are expected to complete. No payments can be processed for the
terminated employee after the nal close date.
By default, the application sets the Final Close Date to end of time, which is 31-Dec-4712. You can modify the date
manually as required. For example, if an employee is terminated in June, the application processes employee's last
regular payroll in June. To make the full selement in October, set the Final Close Date as 31st October.
Note: Payroll elements that have Final Close Date as their latest Entry Date remain available for payment to
the terminated employees till the employee's Final Close Date. For example, if the bonus element is dened
with the last entry date as Final Close date, you can use this element for paying bonus till 31st October.
30
Implementing Global Payroll Interface Global Payroll Interface Extract
4 Global Payroll Interface Extract
Overview
Use the Global Payroll Interface report to extract payroll and employee details, such as the salary and deduction details.
You can use Business Intelligence Publisher templates to send the extracted data to the payroll provider. Copy this
extract denition to generate a custom ow with the same name as the extract.
You can add custom elds to the extract denition. The extracted data includes global and country specic data.
Depending upon the LDG, the application copies country specic data. For example, when you copy a GPI extract
denition within an Australian LDG context, global and Australia specic data is copied to the new extract.
Payroll Interface uses the HCM Extracts infrastructure. All delivery options available within HCM Extracts are available
for Global Payroll Interface. For example, the output le can either be sent across through SFTP or using HCM Connect
over to pre-specied destinations.
Before You Begin

Set up certain elements including license type for country and territory while you congure the ADP Global Payroll
interface. Use the Manage Feature by Country or Territory task to set up Payroll Interface as the Selected
Extension.
Geographies and Legislative Data Group

Use the Load Geographies for US task to load geographies and create the geography structure for each country.
Ensure that you have selected the Data Source as Vertex.
Use the Manage Legislative Data Group task to dene the legislative data groups to identify the country and its
currency. Dene at at least one legislative data group for each country and associate it with a PSU to provide the payroll
information for workers.
Legal Employer
A legal employer is a legal entity that employs workers. Dene the legal entity type depending on the organization
structure as follows:
• One legal entity that's also a payroll statutory unit and a legal employer.
• Multiple legal entities which are children of one payroll statutory unit.
31
Payment Methods
Use the Manage Organization Payment Methods task to create at least one payment method for each combination of
legislative data group, payment type, and currency. You can also create rules to validate or process the distribution of
payments.
When creating a payment method, select the Payment Type as Electronic Funds Transfer (EFT).
Related Topics
• Load Geographies
Payroll Interface Extract Flow Parameters

You can include ow parameters in your extract that are based on the Payroll Interface extract denitions.
This table describes the ow parameters that you can include in your extract::
Flow Parameter Use To What This Parameter Is Mapped To
Changes Only NA
Select dierent extract modes to lter
data in the output le. For example, to
extract only data that has changed since
the previously run extract process.
In the extract denition, this parameter is

mapped to one of these two lookups:
• ORA_HRY_CHANGES_ONLY for
Global Payroll Interface extracts
• PER_EXT_CHANGES_ONLY for all
other Payroll Interface extracts
Payroll Name Search for and select a payroll. Payrolls NA

dene the list of employees to retrieve in
the extract process.

mapped to the Payroll lookup.

Payroll Period Search for and select a payroll period for NA

the reported data.

mapped to the Payroll Period lookup.

Process Start Date Provide an optional start date parameter NA

outside the range of the payroll period.

32
Flow Parameter Use To What This Parameter Is Mapped To
In the extract denition, the name of this

parameter is Start Date.

Process End Date Provide a mandatory date parameter NA

that's the end date of the payroll period.
Because the application can't derive this
date from the selected payroll period, you
must provide the date while you submit
the extract process.

In the extract denition, the name of this
parameter is Eective Date.

Suppress Zero Balance Provide an option to suppress zero values NA

in case Calculate Gross Earnings process
was run and the balance value is 0. This
parameter is only applicable if you're
calculating gross earnings as part of your
Payroll Interface implementation.

mapped to the HRC_YES_NO lookup.

Process Conguration Group Provide an option to search for and select NA

a run-time prole, for example to run the
process in debugging mode.

named Parameter Group and is mapped
to Process Conguration Group lookup.

Related Topics
• Guidelines for Using Dierent Modes for HCM Extracts
• Payroll Process Conguration Parameters
Eective Dates
The payroll interface extract uses the eective start date and end date features to manage the data elements. The two
data elements EectiveStartDate and EectiveEndDate contain the start and end date of the records extracted.
For extracting data, the interface uses the Process End Date parameter specied at the time of submiing the payroll
interface as the eective date.
For example, consider these set of date eective assignment data records for an employee:
33
Record ID Start Date End Date Description
1 1-Jan-17 31-May-17 The worker is hired as

Consultant.

2 1-Jun-17 30-Nov-17 The worker gets promoted as

Senior Consultant.

3 1-Dec-17 End of time The worker gets a change in

location.

Scenario 1
When you run the extract process with eective date as 10-Dec-2017, the application extracts Record 3.
This gure shows which record is extracted when the extract process is run with eective date as 10-Dec-17:
Extract process is run with

effective date as 12/10/17
12/10/17
12/1/17 The application
5/31/17 extracts Record 3
1/1/17 7/1/17 11/30/17

Record 1: Record 2: Record 3:
Worker hired as Consultant Promoted to senior Location change
consultant.
34
Scenario 2
When you run the extract process with eective date as 10-June-2017, the application extracts Record 2.
This gure shows which record is extracted when the extract process is run with eective date as 10-June-17:
When the extract process is run

with effective date as 6/10/17
6/10/17 12/1/17
The application
5/31/17 extracts Record 2
1/1/17 7/1/17 11/30/17

Record 1: Record 2: Record 3:
Worker hired as Consultant Promoted to senior Location change
consultant.
Set up Object Groups

An object group clusters payroll or employees together. For example, you can group employees to process their
extraction. Use the Manage Object Groups task to extract data for either one payroll or multiple payrolls that are dened
within a legislative data group. You can also group employees.
For example, group those employees for whom the regular extraction process wasn't complete for further processing.
Note: This conguration is optional.
1. In the Setup and Maintenance work area, navigate to these tasks:

◦ Task: Manage Object Groups
2. Click Create for a new object group.
3. Complete these elds:
Field Description
Name ADP_ US_ PAY_OBJ_GRP

Legislative Data Group US Legislative Data Group

35
Field Description
Type Payroll Relationship Group

Static or Dynamic Dynamic

4. Click Continue.
5. In the Create Object Group page, Basic Data section, enter the Start Date and End Date as applicable.
6. In the Object Group Parameter section, click the Search icon.
7. In the Object Group Parameter dialog box, search for and select the value for usage as Reports.
8. On the Create Object Groups page, click Next.
9. In the Payroll Denition Inclusion and Exclusions section, add a new record.
10. Select the payrolls to be grouped together using the Lens icon.
11. Click Submit.
Related Topics
Action Indicators for Payroll Interface

Indicators identify and indicate the transactions that cause change in the employment.
Action indicators include hire, termination, and rehire values.
Indicators
Salary Change Payroll Transfer

Action Indicator
Values: Y, N, Null Values: TI, TO, Null
Hire Termination Rehire

Value: H Value: T Value: R
This table describes the indicators:
Indicator Description
Hire, Termination, Rehire • Located within the Service data.

• Represented by values H, T, R respectively.
36
Indicator Description
• If the employee record is extracted for a change other than these, such as, an
assignment change, the action indicator shows the value O - Other Changes.
• Reported only once for an employee.
Salary Change • Indicates whether a salary change has happened during extraction.
• Located within the Assignment data.
• Represented by values Y, N, and Null.
Payroll Transfer • Located within the Payroll Relationship details.

• Represented by values TI (Transfer In), TO (Transfer Out) and Null.
• When a payroll transfer happens, the payroll transfer indicator shows these values:
• TO on the data corresponding to the payroll from which the employee has moved out.
• TI on the data corresponding to the payroll into which the employee has moved in.
This table summarizes the behavior of the indicators for various scenarios:
Indicator Action 1-Mar to 31- Any period Daily Extract Daily Extract Daily Extract
Name Eective Date Mar after 31-Mar for 4-Mar ) for 5-Mar for 6-Mar
(Periodic
Extract)
New Hire Hire Date = 5- ActionIndicator ActionIndicator The application ActionIndicator ActionIndicator
Mar-2017 =H = O. doesn’t =H =O
generate any
The application Prior value for reports for the The application Prior value for
includes all New Hire = H employee. includes all ActionIndicator
aributes for The application aributes for = H.
the person as retrieves the the person as
the person is changed the person is The application
extracted for aributes with extracted for retrieves the
the rst time. prior values. It the rst time. changed
All prior value doesn’t include All prior value aributes with
must be null. persons that must be null. prior values.
don’t have It doesn’t
any changed include any
aribute. person that
doesn’t have
any changed
value.

Terminate ATD = 20- ActionIndicator ActionIndicator ActionIndicator ActionIndicator ActionIndicator

Mar-2017 =T =O =O =T = O.

The date on The application The application Prior Value = Prior Value = O Prior Value = T
which the retrieves all retrieves the N/Blank.
employee was termination HR data for The application The application
terminated - 5- details and the employees The application retrieves all retrieves all
Mar-2017. aributes that that are no retrieves all changed changed
have changed longer with the changed or marked aributes.
in the period. company. The or marked aributes.
status of such aributes. The application
employees The application doesn’t retrieve
is Inactive. extracts the the employee
If there are termination even though
37
(Periodic
Extract)
payroll data details with no aribute

changes, the the actual has changed.
application termination
continues to date as 31-
extract the Mar-2017 in
employee till the assignment
the Final close data.
date.
The prior value
for termination
date is blank

Rehire Rehire Date = Same as Same as Same as Same as Same as

5-Mar-2017 new Hire new Hire new Hire new Hire new Hire
except that except that except that except that except that
for rehire the for rehire the for rehire the for rehire the for rehire the
ActionIndicator ActionIndicator ActionIndicator ActionIndicator ActionIndicator
will have the will have the will have the will have the will have the
value as R. value as R. value as R. value as R. value as R.

Payroll Payroll In the rst The employee The employee In the second The employee
Transfer Transfer date = payroll: Payroll is available in is available in payroll: Payroll is available in
5-Mar-2017 transfer = TO the second the rst payroll. transfer = TI, the second
(= transfer out) payroll. the employee payroll.
the employee Payroll transfer is available in
is available Payroll transfer = TO the second Payroll transfer
under the = blank payroll from 5- = blank
rst payroll Mar.
till 4-Mar. In
the second
payroll: Payroll
transfer TI
(=Transfer In),
the employee
is available in
the second
payroll from 5-
Mar.

Salary change Salary change Salary change Salary change Salary Change Salary Change Salary Change
date = 5- =Y = N/Blank = N/Blank =Y = N/Blank if
Mar-2017 application
Prior Value = Prior Value Prior Value = Prior value = extracts the
N/Blank. = Y if the N/Blank if the N/Blank. employee.
application application
The salary extracts the extracts the The salary
record shows employee. employee. record shows
the latest the latest
salary record salary record
based on based on
the current current design
design with with eective
the eective dates starting
dates starting from 5-Mar.
from 5-Mar. The element
The element entries display
38
(Periodic
Extract)
entries display the salary

the salary element entry
element entry record starting
records ending on 5-Mar.
on 4-Mar and
starting on 5-
Mar

Salary Change Hire Date = 5- ActionIndicator The application The application ActionIndicator ActionIndicator
= N/Blank if Mar-2017. =H extracts the doesn’t extract =H =O
the employee employee due the employee.
is extracted. Termination The application to the element The application The application
recorded on 5- populates the changes. populates the reports other
Mar-2017 ATD termination termination employee data
= 20-Mar-2017. details for the ActionIndicator details for the as appropriate.
employee with = O. employee with
ATD as 20- ATD as 20-
Mar-2017. Mar-2017.

Hire Date = 5- ActionIndicator The application The application ActionIndicator ActionIndicator

Mar-2017. =H extracts the doesn’t extract =H =T
employee due the employee.
Termination The application to the element The application The application
recorded on 6- populates the changes. reports other populates the
Mar-2017 ATD termination employee data termination
= 20-Mar-2017. details for the ActionIndicator as appropriate. details for the
employee with = O. employee with
ATD as 20- ATD as 20-
Mar-2017. Mar-2017.

Terminate Mar-2017 Date If the same ActionIndicator ActionIndicator ActionIndicator When extract
and Rehire in on which the payroll =O =O = T. The is run for 21-
the extraction termination relationship application Mar-2017:
period was recorded ID is used populates the ActionIndicator
= 5-Mar-2017 for rehire termination = R.
Rehire Date = ActionIndicator details for the
21-Mar-2017. = R, the employee with
application ATD as 20-
populates the Mar-2017.
termination
details with
ATD as 20-
Mar-2017.

Hire, Hire Date = 1- If the same ActionIndicator When running ActionIndicator When extract
Terminate and Mar-2017. payroll =O the extract for = T. The is run for 21-
Rehire in the relationship is 1-Mar-2017, application Mar-2017:
same period Termination used for rehire ActionIndicator populates the ActionIndicator
recorded on 5- ActionIndicator = H From 2- termination = R.
Mar-2017 ATD = R the Mar to 4-Mar, details for the
= 20-Mar-2017 application it will be O. employee with
Rehire Date = populates the ATD as 20-
21-Mar-2017 termination Mar-2017.
details. Also, it
39
(Periodic
Extract)
populates the
previous hire
details.

Create Rate Denitions

Optionally, you can create rate denitions to calculate compensation rates and other rates. For example, accrual rates,
using payroll balances, element entry values, or values dened by criteria.
Use the Manage Rate Denitions task to convert the base salary dened in one pay frequency to multiple frequencies.
In the Setup and Maintenance work area, navigate to these tasks:
• Functional Area: Payroll
• Task: Manage Rate Denition
Here's how you can create a rate denition:

1. In the Create Rate Denition dialog box, complete these elds:
Field Value
Category Element

Legislative Data Group US

Storage Type Amount

This value must be the same as the Input Value chosen when you dened the Salary Basis.

Element Name Select the required value.

2. Click OK.
3. On the Create Rate Denition page, consider these points:
◦ The Overall salary check box is selected.
◦ The periodicity of this rate denition matches up with the periodicity of the salary basis to which the
underlying element is mapped.
◦ The Rate Contributor is defaulted to the same input value that was specied in the corresponding salary
basis.
4. Click Submit.
40
Related Topics
• Create Rate Denitions for Leave
• Create Rate Denitions for Overall Salary
Transactional and Operational Recommendations

Transfer employees as close as possible to the process period end date of the source payroll while performing
transactions on the HCM cloud. Sometimes, the payroll to which the employee is transferred could belong to a dierent
country. In such cases, update the Final Close Date for the source payroll as the process period end date.
Transactional Recommendations
Do not purge data. To delete data, use the end date of the business object. However, in unavoidable circumstances, if
you delete the data, use the Deleted Data Report to extract the deleted data.
For terminations, specify the Notied Termination Date as the date on which the termination is recorded. The
termination indicator is based on this date.
Your organization could use one of these approaches when handling payments to terminated employees.
1. Continue to make payments on the HCM cloud and send them to payroll for processing. In such a case, extract
the termination details of the employee whenever payment related information is updated till you make the full
selement to the employee. Set the Final Close Date of the payroll relationship for the terminated employee to
a future date. Till this nal close date, the application extracts the employee details for any update.
2. Enter the post termination payment information directly in the application. In this case, don't extract the
employee details after the termination date. Set the Final Close date as the actual termination date, so that the
application doesn't extract the employee details after the termination date.
Operational Recommendations
Here are few recommendations while you submit the Global Payroll Interface:
• Use the delivered Run Global Payroll Interface ow to process the Global payroll interface.
• Specify the baseline parameter as Yes to run the initial extract in the baseline mode.
• Specify the baseline parameter as No to run the subsequent extracts.
• Consider these points while you select the extraction window:
◦ Frequency of payments.
◦ Frequency of the interface les sent to the third-party payroll application.
◦ Data entry business practice.
• Run the extraction on a daily basis.
• Do not set Process End Date to a date earlier than the end date of any previous runs while scheduling the
Global Payroll Interface process.
• For any unplanned runs, push the extraction start date back to cover all retrospective data changes.
• To perform a roll back for selected employees, create a payroll relationship group with the usage type as
Process. Add the payroll relationships of employees for whom the process needs to be rolled back. Use the roll
back option to nullify failed extraction runs or extractions that contain erroneous data. When you roll back an
41
extraction, you bring the application back to how it was before you extracted data. You can roll back extractions
at process level and for selected employees within a process. To roll back an entire payroll interface process,
specify the name of the payroll interface process to be rolled back as the parameter.
To roll back extractions for selected employees, do these actions:
a. Create a payroll relationship group without selecting Advanced Options check box.
b. Add the payroll relationship of employees for whom you want to roll back the process.
c. Submit the rollback process by specifying the name of the payroll interface process and the payroll
relationship group as parameter.
• When rolling back multiple processes, roll back the last submied process rst.
To verify if the rollback was successful, do these steps:
a. In the Payroll Checklist work area, search for and select the payroll interface process.
b. If the entire process was rolled back, employee records aren't displayed on the Details page. If the
process was rolled back for some employees, details of only those employees are displayed on this page.
Copy Delivered Extract Denitions

Use the delivered extract denition and ow if these considerations apply to your current implementation. Otherwise,
create a copy of the delivered extract denition and update that copy.
• The data dened in the delivered extract meets your interfacing requirements.
• Few or no additional congurations are required on the delivered extract denition.
• The report output template meets the reporting requirements.
Here's an approach to reduce the conguration eort in implementations involving multiple countries, for changes that
are common to all countries.
• Create a copy of the delivered extract denition at the Enterprise level (without specifying a LDG).
• Update this copy at the enterprise level that are common across all countries.
• For making country specic changes, search for the extract denition by specifying the respective LDG and
make the country specic changes. Repeat this step for individual countries.
Use Extensible Fields to Include Additional Aributes

Use the congurable extensible elds to include additional aributes in your extract denition. You can include up to
ve additional aributes. You can congure fast formulas to determine the values for these aributes and map these
formulas to the extensible elds.
To use the congurable extensible elds, do these actions:
1. Create a rule formula of type Extract Rule for each extensible aribute that you want to extract.
2. Map the rule formula to the extensible aributes using the delivered lookup type
ORA_HRY_EXTND_DATA_FORMULA_MAP.
42
Map the Rule Formula to the Lookup Type

Do these steps to map the rule formula to the lookup type:
1. In the Setup and Maintenance work area, search for and select the Manage Common Lookups task.
2. On the Manage Common Lookups page, in the Lookup Type eld, enter
ORA_HRY_EXTND_DATA_FORMULA_MAP and click Search.
3. In the ORA_HRY_EXTND_DATA_FORMULA_MAP: Lookup Codes section, for the
ORA_HRY_ENABLE_EXTND_VALUES lookup code, enter Y in the Meaning eld to enable this feature.
4. In the ORA_HRY_EXTND_DATA_FORMULA_MAP: Lookup Codes section, add these lookup codes:
Lookup Code Meaning Description
ASG_ EXTENDED_ FIELD_1 Valid rule formula name to populate the Enter a valid description. For example:
value for the aribute Extensible Field 1. This aribute is being extracted through
this extensible eld.

ASG_ EXTENDED_ FIELD_2 Valid rule formula name to populate the Enter a valid description.
value for the aribute Extensible Field 2.




Related Topics
• Overview of Using Formulas
• Overview of Writing Formulas
Submit the Global Payroll Interface Process

Use the Submit a Process or Report task from the Payroll Checklist work area to submit the global payroll interface
process.
1. On the Select Flow Paern page, select the legislative data group.
2. Search for and select the Run Global Payroll Interface V2 process. Click Next.
3. On the Enter Parameters page, enter these parameters.
43
Field Use To
Payroll Flow Enter a meaningful name.

Changes Only All aributes

Object Group
The application extracts data depending on the conditions mentioned in the selected object
group.
◦ If the object group consists of payrolls, the application extracts all employees that
have been mapped to this object.
◦ If the object group consists of payroll relationships, the application extracts only those
payroll relationships mapped to the object group.
Payroll Use this optional parameter if you don't want to group payroll. If you specify payroll, the
application extracts only those employees that are mapped to a particular payroll.

Note: You must select either an object group or a payroll to extract data.
Process Start Date Enter the start date of the extraction period.

Process End Date Enter the end date of the extraction period.

Process Conguration Group Select the required process conguration group.

4. Click Submit. Monitor the status of the process to successful completion.
Global Payroll Interface Extract FAQs

Does the Global Payroll Interface output les contain future date
changes?
Depending upon the extract window, the output le contains future dated changes.
What happens if you delete data in the Global Payroll Interface

Outbound le?
If you delete data before sending it to the payroll provider, then it's not available to the payroll provider. Do not delete
any data that has been sent out to the payroll provider.
44
Can the Global Payroll Interface include Terminated employees?

The TerminationDetail section of Global Payroll Interface includes terminated employees details, such as action reason
and action code.
Can I add an additional BI Publisher template on top of existing

Global Payroll Interface?
You can add a BI publisher to global payroll interface as long as it works with the raw xml that the HCM Extract
generates.
45
46
Implementing Global Payroll Interface Payroll Interface for ADP Global Payroll
5 Payroll Interface for ADP Global Payroll
Overview
The Payroll Interface for ADP Global Payroll integrates the HCM cloud with the ADP Global Payroll application. Use this
interface to extract information, such as the salary and earnings details of employees in the format required by ADP
Global Payroll.
Set up these prerequisite elements while you congure the payroll interface for ADP Global Payroll:
Oering / Functional Area/Task Description
Oering: Workforce Deployment Congure any implementation specic details at the enterprise level.

Functional Area: Workforce
Structures

Task: Manage Enterprise HCM
Information

Oering: Workforce Deployment Load geographies to create the geography structure for each country. For example, create
geography types called State, City, and Postal Code. Ensure that you have selected Data Source
Functional Area: Enterprise Prole as Vertex.

Task: Load Geographies for US

Oering: Workforce Deployment Dene legislative data groups to identify the country and its currency.

Structures

Manage Legislative Data Group

Oering: Workforce Deployment Enter the details for the new entry. Ensure that both Payroll Statutory Unit and Legal Employer
check boxes are selected.
Functional Area: Legal Structures

Task: Manage Legal Entity

Oering: Workforce Deployment Create a payment method and associate it with a payment source.

Functional Area: Payroll

Manage Organization Payment
Methods

Oering: Workforce Deployment Dene at least one payroll for each payment frequency. For example, you can use three
pay frequencies, namely Monthly, Bi-weekly, and Weekly to process payments for dierent
Functional Area: Payroll categories of its employees.

47
Oering / Functional Area/Task Description
Manage Consolidation Groups

Oering: Workforce Deployment

Perform these tasks:
Functional Area: Payroll
• Identify a base pay element
Manage Elements and Manage Salary • Dene salary basis
Basis • Associate salary basis with base pay element

Oering: Compensation Management

Compensation

Task: Manage Salary Basis

Salary History Information for ADP Global Payroll

Interface
The ADP Global Payroll interface extracts salary history information. The HCM Cloud supports date eective salary
management. HCM Cloud records all date eective changes made to the salary information as date eective records.
The interface extracts all the salary records that are eective within and overlap the start and end date.
This table summarizes salary records for an employee:
Start Date End Date Reason Salary
1-Jan-17 10-Jun-17 Hire 120,000

11-Jun-17 30-Jun-17 Correction 140,000

1-Jul-17 EOT Promotion 200,000

This table shows the salary records when the extraction start and end date is 1-Jun-17 to 30-Jun-17:
1-Jan-17 10-Jun-17 Hire 120,000

48

This table shows the salary records when the extraction start and end date is 1-Jun-17 to 31-Jul-17:
1-Jan-17 10-Jun-17 Hire 120,000


1-Jul-17 EOT Promotion 200,000

Additional Payroll Interface Data Elements

Use the Manage Value Sets for Global Human Resources tasks to identify and manage additional data elements and
list of values. For example, you can create Business Area as a lookup code and Employee Group and Sub-Group as value
set.
The Manage Value Sets for Global Human Resources task is part of the Workforce Deployment oering in the
Workforce Information work area.
Include these additional data elements for the payroll interface for ADP Global Payroll:
Data Element Name Level
Assignment Assignment

Company Code Assignment

Personnel Area Assignment

Personnel Subarea Assignment

Employee Group Assignment

Employee Subgroup Assignment

Business Area Assignment

49
Data Element Name Level
Work Contract Assignment

Organizational Key Assignment

HR Administrator Assignment

Payroll Administrator Assignment

Time Administrator Assignment

Work Schedule Rule Assignment

Employment Percentage Assignment

Weekly Workdays Assignment

Pay Scale Type And Area Assignment

Pay Scale Group And Level Assignment

Capacity Utilization Level Assignment

Working Hours Per Payroll Period Assignment

Number of Dependents Person

Distance in Kilometers Person

This table details the data type and code for the data elements.
Data Element Name Data Type Code
Type Of Transfer Lookup ORA_ GPY_ TRANSFER_TYPE

Company Code Lookup ORA_ GPY_ COMPANY_CODE

Personnel Area Value set ORA_ GPY_PER_AREA

50
Data Element Name Data Type Code
Personnel Subarea Value set ORA_ GPY_ PER_SUB_AREA

Employee Group Value set ORA_ GPY_EMP_GRP

Employee Subgroup Value set ORA_ GPY_ EMP_SUB_GRP

Business Area Lookup ORA_ GPY_ BUSINESS_AREA

Work Contract Lookup ORA_ GPY_ WORK_CONTRACT

Organizational Key Lookup ORA_ GPY_ORG_KEY

HR Administrator Lookup ORA_ GPY_HR_ADMIN

Payroll Administrator Lookup ORA_ GPY_PY_ADMIN

Time Administrator Lookup ORA_ GPY_TM_ADMIN

Work Schedule Rule Lookup ORA_ GPY_ WRK_SCHD_RULE

Employment Percentage Free text Numeric eld

Weekly Workdays Free text Numeric eld

Pay Scale Type And Area Lookup ORA_ GPY_ PSCALE_ TYPE_AREA

Pay Scale Group And Level Lookup ORA_ GPY_ PSCALE_ GRP_LEVEL

Capacity Utilization Level Free text Numeric eld

Working Hours Per Payroll Period Free text Numeric eld

Number of Dependents Free text Numeric eld

Distance in Kilometers Free text Numeric eld

51
Run Global Payroll Interface Processes

The Standard Payroll Interface for ADP Global Payroll ow in the Payroll Checklist work area includes these processes:
Process Description
Data Validation Report Validates the data available on the HCM cloud before passing them on to ADP. It takes into
account statutory requirements and helps identify missing or non-compliant data. You can act
necessarily to x the data before passing the data over to ADP.

Payroll Interface for ADP Global Submits the ADP Global Payroll interface process and generates the output le that must
Payroll passed to ADP.

Deleted Data Report Reports data belonging to a specied set of business objects that have been deleted from the
HCM Cloud system during the extraction period. This report serves as a supplement to the
ADP Global Payroll Interface output xml le to account for complete set of data changes within
the given extraction period.

Note: Don't delete any data in the HCM application. End date any incorrect data
that should not be used for processing.

Use the Submit a Process or Report task in the Payroll Checklist work area to complete these steps:
1. In the Legislative Data Group choice list, select the legislative data group.
2. Search for the Run Payroll Interface for ADP Global Payroll process.
3. Select the required process and click Next.
4. On the Enter Parameters page, enter these parameters:
Parameter Description
Object Group
The application extracts data pertaining to the conditions mentioned in the selected Object
group.
◦ If the object group is a group of payrolls, the application considers all employees
associated with the payrolls that are mapped to this object group for extraction. This
enables data corresponding to multiple payrolls being reported in a single output le.
◦ If the object group is a group of payroll relationships created for exception reporting,
the application extracts only those payroll relationships (employees) mapped to this
object group.
Payroll Payroll is an optional parameter that you can use if you don't want to group payrolls.

If you specify a payroll, the application extracts only those employees that are mapped to
that particular payroll.

Note: Provide either an Object Group or a Payroll or a combination of both.
52
Parameter Description
Process Start Date Start date of the extraction period.

Process End Date End date of the extraction period. The application considers this date as the eective one
and extracts those records eective as on this date.

5. Click Submit.
6. Monitor the status of the process to successful completion.
Congure Prior Values

Use the BLOCK_OLD mode on the Payroll Interface for ADP Global Payroll to identify the employment and payment
data changes. The application displays the updated data as on the eective date as the current value and the previous
value of the aribute as prior value.
For example, an employee moves from the Consulting department to Development department changing their
position from Consultant to Developer.
<gpi:JobDetails>
<gpi:Position PriorValue="Consultant">Developer </gpi:position>
<gpi:JobCode> JOB3 </gpi:JobCode>
<gpi:Department PriorValue="Consulting">Development </gpi:Department>
<gpi:ReportingEstablishment> Development </gpi:ReportingEstablishment>
<gpi:WorkerCategory> White Collar </gpi:WorkerCategory>
<gpi:WorkingHours> 40 </gpi:WorkingHours>
<gpi:Frequency> W </gpi:Frequency>
This table summarizes the PriorValue aribute behavior to the type of change that the data element undergoes.
Scenario Prior Value Aribute Prior Value Aribute Element Populated Sample Output
Present Populated
Initial Extracts Yes/No = No Yes/No = No Yes/No = Yes Change: Initial Extract.

All data reported.
All Aributes

Run with Changes Only
=N

First Snapshot Yes/No = Yes Yes/No = Prior value Yes/No = Yes Change: Available data
will be NULL is reported and the
Run with Changes Only corresponding prior
= BLOCK_OLD value shows NULL.

An object or entity
reported for the rst
time.

53
Scenario Prior Value Aribute Prior Value Aribute Element Populated Sample Output
Present Populated
Includes New Hire and

Payroll Transfer as a
new entity.

Element changes from Yes/No = Yes Yes/No = Prior value Yes/No = Prior value Change: Address 2
no value to a value. will be NULL will be NULL changed from no value
to a value and has a
prior value NULL. The
other aributes haven't
changed and so they
don't contain a prior
value.

Element changes from Yes/No = Yes Yes/No = Yes Yes/No = Yes Change: Address 2
value to no value. changed from value
to no value and has
a prior old value. The
other aributes haven't
changed and so they
don't contain a prior
value.

Element doesn't Yes/No = No Yes/No = No Yes/No = No Change: No changes.

change All values are shown as
they're without prior
values.

Element changes from Yes/No = Yes Yes/No = Yes Yes/No = Yes Change: Element
one non-null value to changes from one non-
another non-null value. null value to another
non-null value. Address
changes from Belmont
to Jersey city.

Set up Additional Elements

Use the Submit a Payroll Flow task to congure additional data elements while you congure the global payroll interface
for ADP Global Payroll.
Enable these predened contexts:
• Additional Assignment Details for ADP Global Payroll Interface

• Additional Person Details for ADP Global Payroll Interface
54
Enable Predened Contexts

Use the Submit a Payroll Flow task in the Payroll Checklist work area:
1. On the Submit a Payroll Flow: Select Flow Paern page, search for Manage Global Payroll Interface
Features Usage ow.
2. Select the ow and click Next.
3. On the ow parameter page, enter these details:
Parameter Value
Payroll Flow Name Meaning name to the current ow.

Activate Usage Yes

Feature Search for Assignment EIT Information EFF.

Component Search for Additional Assignment Details for ADP Global Payroll.

4. Submit the ow.

5. To enable the additional data available under Person, repeat the above steps using these details:
Parameter Value
Feature Person EIT Information

Component Additional Person Details for ADP Global Payroll

Sub component Select the sub components as applicable.

Note: Features and the sub components that you can enable for implementation depends
on the ADP recommendation. Consult with ADP before you enable the features and sub
components.

◦ Task: Manage Extensible Flexelds for Payroll
7. Search for the Assignment Extensible exeld by entering Assignment EIT Information value in the Name
eld.
8. In the Search Results section, select the Assignment EIT Information EFF row and click Deploy Flexeld.
9. Ensure that the deployment completes successfully.
55
10. Ensure that the Deployment Status column shows a green tick mark.
Related Topics
Manage Payroll Interface Data Values

Use the Manage Common Lookups task to create a lookup for managing additional data values, such as Company Code
and Personnel Area. You can also manage these data values by using the Manage Value Sets task to create a value set.
Create Lookups for Data Values

Use the Manage Common Lookups task in the Setup and Maintenance work area to complete these steps:
1. On the Manage Common Lookups page, Lookup Type eld, enter ORA_GPY_BUSINESS_AREA and click
Search.
2. In the ORA_GPY_BUSINESS_AREA: Lookup Codes section, click New from the Actions menu.
3. Enter these details in the row:
Field Description
Lookup Code BA1

Display Sequence 10

Start Date 01/01/2000

End Date 12/31/4712

Meaning Business Area

Description Business Area

Create Value Sets for Data Values

Use the Manage Value Sets task in the Setup and Maintenance work area to create value sets for data values:
1. On the Manage Value Sets page, Value Set Code eld, enter ORA_GPY_PER_AREA_VS. Click Search.
2. Click Manage Values.
3. On the Manage Values page, click Create.
4. Enter each personal area as a value.
56

6. On the Manage Values page, click Save and Close to return to the Manage Value Sets page.
7. In the Search Results section, ensure that ORA_GPY_PER_AREA_VS is selected.
10. On the Create Value page, enter each sub area as a new value. Ensure that you choose the area to which this
sub-area belongs to is under the Independent Value column.
Override the Cost Center Using Congurable Cost Center

Override Aribute
Use the congurable Cost Center Override aribute to include a logically determined overriding cost center in the ADP
Global Payroll interface. You can use fast formulas to determine the value for the overriding cost center and map it to
the Cost Center Override aribute using the delivered lookup type.
To use the congurable Cost Center Override aribute, do these actions:
1. Create a rule formula of type Extract Rule to extract the logically determined override cost center value.
2. Map the rule formula to the delivered lookup type ORA_HRY_EXTND_DATA_FORMULA_MAP.
Map the Rule Formula to the Lookup Type

Do these steps to map the rule formula to the lookup type:
1. In the Setup and Maintenance work area, search for and select the Manage Common Lookups task.
2. On the Manage Common Lookups page, in the Lookup Type eld, enter
ORA_HRY_EXTND_DATA_FORMULA_MAP and click Search.
3. In the ORA_HRY_EXTND_DATA_FORMULA_MAP: Lookup Codes section, for the
ORA_HRY_ENABLE_EXTND_VALUES lookup code, enter Y in the Meaning eld to enable this feature.
4. In the ORA_HRY_EXTND_DATA_FORMULA_MAP: Lookup Codes section, add this lookup code:
Lookup Code Meaning Description
ASG_ EXTENDED_ FIELD_5 Valid rule formula name to return the Enter a valid description. For example,
value of the override cost center. the cost center override aribute is being
extracted through this extensible eld.

Related Topics
• Overview of Using Formulas
• Overview of Writing Formulas
57
Congure Dynamic File Names for Global Interface

The global interface for ADP Global Payroll generates the output le names dynamically. The name of the le generated
corresponds to this format:
ORA_PQX148_YYYYMMDDHHMMSS_USOGPI_HRMD01_DUT8G2I.XML
Congure lookup types, value sets, and fast formula to generate ADP Global Payroll interface les with this le name.
Lookup Type
Congure a new lookup type to hold implementation specic values for few components in the dynamic le name. For
example, the Client Number might vary between dierent customers. Create a lookup type to use it in a le name.
Here's how you can create a lookup type:
1. On the Setup and Maintenance page, search for and select the Manage Common Lookups task.
2. On the Manage Common Lookups page, click New.
3. Enter these values:
Parameter Value
Lookup Type ADP_ GPY_OUT_FILE NAME_COMP

Meaning File name component values

Description Holds values for components in the ADP Global Payroll Interface output le name.

Module Oracle Fusion Middleware Extensions for Applications

4. In the Lookup Codes section, click New.

5. Enter these values:
Parameter Value 1 Value 2
Lookup Code ADP_ GPY_ SYSTEM_NUMBER ADP_ SAP_ CLIENT_NUMBER

Enabled Yes Yes

Meaning Actual value Actual value

Description ADP Global Payroll System Number ADP Global Payroll Client Number

58
6. Click Save.
Value Sets
Use value sets to extract various values required to form the dynamic output le name.
This table shows how to dene new value sets:
To Derive FROM Clause ID Column Name WHERE Clause
Legislation Code PER_ LEGISLATIVE_ DATA_ LEGISLATION_ CODE LEGISLATIVE_ DATA_

GROUPS_VL GROUP_ ID= :{PARAMETER.
LEGISLATIVEDATAGROUP_ID

File Name Component HCM_LOOKUPS MEANING lookup_ type='ADP_

GPY_OUT_FILE NAME_COMP'
and lookup_ code= :
{PARAMETER. LOOKUPCODE}

Fast Formula
A fast formula combines the various le name components in the correct sequence and returns the nal le name.
This table shows how to create fast formula of type Extract Rule:
Formula Parameter Value
Formula name ADP_ GPY_ OUT_ FILENAME_ FORMULA

Description Formula to consolidate various le name components and return the nal output le name
dynamically.

Formula text ------FORMULA

STARTS--------------------------------------------------------------------------------------------
DEFAULT FOR RULE_VALUE IS ' ' ----- GET THE INSTANCE NAME FROM THE INTERFACE
PROCESS PARAMETER L_ FINAL_ VALUE='ORC_P' + GET_ PARAMETER_ VALUE('INSTANCE_
NAME') ----- GET THE SYSTEM NUMBER FROM THE LOOKUP AND CONCATENATE
TO FINAL FILENAME L_PARAM ='|=LOOKUP_ CODE=''ADP_ GV_ SYSTEM_ NUMBER'''
L_VALUE_1 = GET_ VALUE_ SET('ADP_ GPY_ OUT_ FILENAME_ COMP_VS'L_PARAM) L_
FINAL_VALUE = L_FINAL_VALUE + L_VALUE_1 ----- GET THE CLIENT NUMBER FROM THE
LOOKUP AND CONCATENATE TO FINAL FILENAME L_PARAM ='|=LOOKUP_ CODE=''ADP_
SAP_ CLIENT_ NUMBER''' L_ VALUE_1 = GET_ VALUE_ SET('ADP_ GPY_ OUT_ FILENAME_
COMP_VS'L_ PARAM) L_ FINAL_VALUE = L_FINAL_VALUE + L_VALUE_1 ----- GET THE
COUNTRY CODE FROM THE LDG AND CONCATENATE TO FINAL FILENAME L_LEG_PARAM
= GET_ PARAMETER_ VALUE_ NUMBER('LEGISLATIVE_ DATA_ GROUP_ ID') L_PARAM
= '|=LEGISLATIVEDATA_ GROUP_ ID='+TO_ CHAR(L_ LEG_PARAM) L_VALUE_1 = GET_
VALUE_ SET('ADP_ LEGISLATION_ CODE_VS'L_PARAM) ----- CONCATENATE THE OTHER
59
Formula Parameter Value
HARD CODED COMPONENTS TO THE FILENAME L_FINAL_VALUE = L_ FINAL_ VALUE

+GET_ VALUE_ SET('SYSTEM_ TIME_ STAMP_ VS')+L_ VALUE_ 1+'ORCL_ '+'HRMD'+'01_
'+'D' +'UT8'+'G2I'+'. SAP' ------ RETURN THE FINAL FILENAME THROUGH RULE_ VALUE
VARIABLE RULE_VALUE = L_FINAL_VALUE RETURN RULE_VALUE -------FORMULA
ENDS------------------------------------------------------------------------------------------

Save and compile this formula.
Update Extract Structure

Save the generated le name in one of the aributes in the extract. The application uses the aribute in the delivery
options to generate the le with the dynamic le name.
1. Navigate to the Data Exchange work area. Select Manage Extract Denitions.
2. Search for the extract denition specifying Name as Payroll Interface for ADP Global Payroll.
3. Create a record in the extract.
4. Add an aribute of type Rule to this record and aach the rule formula created above.
5. Specify Type as Rule and Rule as ADP_le_name_rule.
6. Submit the changes and ensure that the validations are successful.
Additional Details Reported in the File

The payroll interface includes these additional details:
• Extract Version Number

• Extract Instance Name
• Employees Reported in the File
Extract Version Number

Use the version number of the payroll interface extract denition to troubleshoot and diagnose issues. The extract
version number is of the format x.y.z (example 1.0.0) where
• X is the major release number of the extract. This number changes when major changes to the extract
denition including its structure or critical data inclusion on the global data section occurs.
• Y is the medium release and tracks changes. For example, inclusion of new legislations, changes to existing
legislation data, or minor changes to global data section.
• Z is the minor release and tracks minor changes to the extract, such as inclusion of one or two data elements.
The rst release of the interface has the version number 1.0.0.
60
Extract Instance Name

The source instance type, such as Production, Development, or Test from which an extract output le is produced
determines the destination ADP instance.
Employees Reported in the File

The individual payroll relationships reported in the le appear at the end of the le to help record count reconciliation.
Note: The count displayed in the le is the count of distinct payroll relationships. For example, an employee
with two payroll relationships is reported as two in the record count.
Transactional Recommendations
Follow certain recommendations while you perform transactions on the HCM cloud. For example, you must not purge
data. To delete data, use the end date option of the business object. In an exceptional case if you delete data, send the
Deleted Data Report output to notify ADP. The output of this report contains the deleted data details.
Payroll Transfers
Transfer employees as close as possible to the process period end date of the destination payroll. Update the Final
Close Date of the source payroll as the process period end date.
Indicate these details in the output le for transferred employees:
• TO (transfer out) on the source payroll.

• TI (transfer in) on the destination payroll.
The application reports transferred employees under both source and destination payroll until the source payroll's
period end date, which is also the Final Close Date.
Employee Terminations
The Notied Termination Date is the date on which the employee is terminated.
The interface supports these two approaches to pay terminated employees:
• Update the payments on the HCM cloud and send the details to Payroll for processing.
◦ Until you make the nal selement for the employee, extract details of the terminated employee for any
update in the employee information.
◦ Update the Final Close Date of the payroll relationship of the terminated employee.
◦ Set the date into a future period in time so that the organization can process the nal selement.
After the Final Close Date, the application doesn't extract the employee.
61
• Process the payroll details directly on the Global Payroll application. In this case, the application doesn't extract
the terminated employee details after the terminated date. Set the Final Close Date as the actual termination
date of the employee so that the application doesn't extract the employee details after the termination date.
Update the Final Close Date

Use the Person Management task in the My Client Groups work area to set the nal close date. For example, for
terminated employees, you can set the date to complete all of their payroll related activities.
1. On the Person Management page, ensure that the Include terminated work relationships check box is
selected.
2. Search for and select the terminated employee.
3. On the Manage Employment page, click Tasks and select Manage Payroll Relationships task.
4. In the Assignment section, Element Duration section, select the Final Close row and click Edit.
5. In the Date eld, enter the required date. Click Save.
Cost Center Allocations

The Interface supports cost allocation only to department cost centers that the assignment belongs to. The interface
doesn't support spliing of costs across multiple cost centers.
Operational Recommendations
Follow certain recommendations while you submit the payroll interface for ADP Global Payroll on the HCM cloud.
For example, use the delivered Run Payroll Interface for ADP Global Payroll ow to process the ADP Global Payroll
interface. This ow when run from a specic LDG extracts the global data and the legislative data pertaining to the
country to which that LDG is associated.
Initial Extract
Extract complete information pertaining to all employees that are identied based on the process parameters. Since this
information is available on the ADP Global Payroll application, the application doesn't use the output le of the initial
extract for any processing.
• Specify the baseline parameter as Yes to execute the initial extract in the baseline mode. The application
extracts and keeps the extract without generating any output le.
• Specify the baseline parameter as No to execute the subsequent extracts.
Extraction Window
The time interval between the Process Start Date and Process End Date parameters is referred to as the extraction
window.
• Choose the extraction window and don't change it later.
• Run the extraction on a daily basis, typically at the end of the day's work.
Consider these points while you select the extraction window:

• Frequencies of payments supported. For example, Monthly, Weekly, Bi-weekly.
62
• How often interface les are sent to the ADP Global Payroll application.
• When the application records the data. For example, as and when the changes happen, after the changes
happen with a past date, or in advance before the actual changes happen.
To ensure that you address the retrospective data entries and future dated changes, set the extraction dates:
• Extraction start date to a date suciently earlier than the current date.
• Extraction end date to a date suciently later than the current date.
Extraction Schedule
Schedule the regular ADP Global Payroll interface processes like any other process within the HCM cloud. The
application supports all options, such as dynamic (fast formula based) date parameter seing.
When scheduling this process, don't set the Process End Date parameter to a date earlier than the end date of any
previous runs.
Unplanned Runs
The payroll interface for ADP Global Payroll supports unplanned runs to address exception scenarios that result in
transaction changes. For example, retrospective changes to the employees' salary.
For such unplanned runs, set the extraction start date as early as needed to cover all retrospective data changes. Set the
extraction end date same as the end date of the immediate last regular interface run.
Extraction Rollback
Roll back nullies the extraction runs that failed or contain erroneous data.
Note: Use the roll back process only when required.
Note: You can perform rollback at both the process level and within the process.
To perform a roll back for selected employees, create a payroll relationship group with the usage type as Process. Add
the payroll relationships of employees for whom the process must be rolled back. When rolling back multiple processes,
roll back the last submied process rst.
Increment Process Dates Automatically

The data that the ADP Global Payroll Interface reports depends on the extract start and end dates that you select when
you submit the interface.
The recommended extraction window is 21 days with this requirement:
• The start date is 14 days before the current system date.

• The end date is 7 days after the current system date.
63
Before you Begin

Consider these points while you automatically increment process dates:
• Ensure that the end date is later than the start date. Otherwise, the process doesn't return any records.
• If you don't set oset values, the application uses the default value of 0. This means that the start date and end
date both are the system date and this amounts to daily extraction.
• When you schedule extractions to run daily, the start and end dates change relative to the system date.
• The osets are applied on the extract execution date, which is actually the system date. If you don't specify the
osets, the application uses the system date.
• Enter all other parameters except for Process Start Date and Process End Date while you schedule the
extraction for the rst time.
Use these actions to automatically increment the extract start and end date parameters:
1. Navigate to the Payroll Calculation work area.

2. In the Tasks pane, select the Manage User-Dened Tables task.
3. In the Name eld, enter Prole Options For Payroll Interfaces.
4. Select your required Legislative Data Group and click Search.
5. In the Search Results section, select the Prole Options For Payroll Interfaces row.
6. On the Prole Options For Payroll Interfaces page, click Edit.
7. In the Eective As-of Date eld, select an eective date.
8. Click Next to open the User Dened Table Values page.
9. In the User-Dened Table Values section, click Create.
10. In the Add User-Dened Table Values dialog box, select ADP Global Payroll Interface Flow Parameter Start
Date Oset.
11. Click OK.
12. In the Value eld, enter the number of days by which you need to oset the start date. Typically, set this value
to the number of days by which you want to move the start date from the date of execution. To move the start
date into the past, prex the value with a minus sign. To move the start date forward, prex the value either
with a + sign or don't provide any sign. For example, to set the start date 14 days into the past, set the value as
-14. Repeat this step for Exact ADP Global Payroll Interface Flow Parameter End Date Oset.
13. Click Submit.
Enable Access to Global Payroll Local Data in ADP

Use the HCM Cloud to maintain payroll data in Global Payroll Local Data in ADP. For example, bank account and loan
details, tax le number, and so on.
HCM secures data access for creation and maintenance of this data. Congure the data sent to ADP using this
integration, based on your implementation and the data that you capture in HCM Cloud.
For the data that's entered directly in ADP systems, enable access to the Global Payroll Local Data in ADP from HCM
Cloud.
64
Before You Start

• Set a prole option to enable ADP integration at the site level.
• Ensure that the Payroll Administrators are granted the required security privileges. Payroll Administrators must
also have the Payroll Interface Coordinator job role with the appropriate data roles granted.
• Use the Payroll Integrations task to enable the integration setup.
• Congure federation SSO between HCM Cloud and external IdP, and also between the external IdP and ADP's
Global Payroll Local Data in ADP Payroll systems.
Set Prole Option

Set the prole option at the site level to enable or disable the integration with ADP for payroll processing.
Prole Name Role Values
ORA_ PAY_ ENABLE_ EXT_ PAY_ Payroll Administrator • YES: Enables the integration and
INTEGRATION the associated task ows.
• NO: Disables the integration.
Security Privileges
This table shows the security privilege and the predened role that inherit it.
Privilege Name Role Use To
ORA_ HRY_ MANAGE_ EXTERNAL_ Payroll Interface Coordinator Congure payroll data maintained in
PAYROLL_ INFORMATION the Global Payroll Local Data in ADP
for employees using payroll interface
coordinator task ow.

65
Enable Payroll Integrations

Use the Payroll Integrations task to provide details for the setup.
On the Dene Integration Setup page, provide the direct access URL for accessing the Global Payroll Local Data page
in ADP.
• Deep Link URL: Provides the link for navigating to Global Payroll Local Data in ADP from HCM Cloud to
manage payroll data. You must enter the encoded URL here. Here's a sample URL while you use Microsoft
ADFS for federation SSO:
https://<ExternalIDPHOST>/adfs/ls/IDPInitiatedSignon.aspx?RelayState=RPID%3Dhttps%253A
%252F%252Fportal0023.globalview.adp.com%252Ffederate2%26RelayState%3Dhttps%253A%252F
%252Fportal0023.globalview.adp.com%252FadminCentral%252Foracle.home%253F
Note: Other aributes, such as Audience, Tenant, and REST Endpoint will be supported in the future releases.
Enable the Access to Global Payroll Local Data in ADP

Every employee in an organization belongs to a payroll group.
Administrators can manage data for employees administered by them by using the Payroll Administrator task ow.
1. Navigate to Payroll work area.
2. Search for and select Payroll Information in ADP.
3. Search for an employee record to view the Global Payroll Local Data in ADP launched in the HCM Cloud.
Payroll Interface for US ADP Payforce

Overview
The setup steps required for the Oracle Fusion Global Payroll Interface for the United States can vary depending on
these prerequisites:
• The Oracle Fusion products and features that are already congured in your enterprise
• The data that you want to make available to ADP PayForce and ADP Connection for PayForce
In addition to the setup points described for the Global Payroll Interface, the following assumptions and conguration
requirements exist for your ADP solutions in these areas:
• Organizations and Locations
• US Geographies
• Person Information
• Element Management
• Payroll Denitions
66
• ADP Conguration
Organizations and Locations

Consider these points while you set up your organizations and locations:
• A one-to-one mapping must exist between a legal employer and a payroll statutory unit (PSU).
• When dening locations, you must use the United States tax address format.
US Geographies
You must consider these requirements:
• To properly populate the geographies information, you must run the Load Geographies for US task from the
Functional Setup Manager.
• A valid Vertex Geocode license is required for employees to receive their default tax card.
Person Information
Consider these points while you manage employee information:
• Each employee in the payroll must have a default tax card associated with a tax reporting unit (TRU).
• Don't use commas in any address, as ADP Connection for PayForce doesn't support their usage.
• You must use the United States tax address format for employee addresses.
• ADP PayForce users must use the Manage Common Lookups task to update the
PER_NATIONAL_IDENTIFIER_TYPE lookup type with the following new lookup code:
Lookup Code Meaning Tag
PAYINT_ EMPLOYEEID Employee ID for ADP PayForce +US

• For each employee you want to report, use the National IDs region in the Manage Person page to add their ADP
PayForce le number.
Element Management
Consider these points while you dene the elements for your earnings and deductions:
• Employee Work Relationships
• Payment Methods
• Element Termination Rules
• Piece-Rate Elements
• Recurring Elements
• Nonrecurring Deduction Elements
• Nonrecurring Earnings Elements
Employee Work Relationships

ADP Connection for PayForce doesn't support multiple terms, so employees should not have multiple terms in a single
work relationship. Any earnings you dene at the terms level, including salary, is passed on to the primary assignment.
67
If an employee has multiple terms with earnings at the terms level, ADP Connection for PayForce may not correctly
interpret the values passed to the primary assignment.
Payment Methods
Consider these points while you dene payment methods:
• Employees can't have both check and direct deposit payment methods.
• Personal payment methods for direct deposit payments must be either set to 100 percent or use xed dollar
amounts.
• Don't select a run type while you dene Personal Payment Methods. Leave this eld blank.
Element Termination Rules

ADP PayForce doesn't support earnings proration. Therefore, all earnings elements other than salary earnings must use
a Last Standard Process Date or Final Close termination rule. Do not use Last Standard Earning Date.
Piece-Rate Elements
ADP Connection for PayForce doesn't support piece-rate earnings. Do not pass any elements of this type through the
Payroll Interface.
Recurring Elements
Consider these points while you dene recurring elements:
• Employees can't have more than one of same recurring element (deductions or earnings). When you dene
your recurring elements, prohibit multiple entries.
• When creating a recurring deduction element, and you want the deductions to stop after a set goal amount,
you must create an input value for that element and provide the amount. This input value must be named
"Goal Amount".
• When you dene deduction elements with a dierent periodicity than your payroll period, perform these
actions:
a. Assign the elements an input value with the special purpose of Periodicity.
b. Set the periodicity.
For example, set the element's periodicity to monthly to take a deduction monthly with a weekly payroll.
Any earnings elements have the Periodicity input value created automatically.
Note: This information is included in the extract, but ADP Connection for PayForce doesn't use it.
Nonrecurring Deduction Elements

The US ADP PayForce third-party periodic extract pulls only nonrecurring voluntary deductions. Nonrecurring pretax
deductions aren't included.
When you dene nonrecurring deductions, create and set these input values for each deduction element:
68
Input Value Special Instructions
Deduction Value You must identify whether this element is deducting either as a at amount or a percentage.
Use this input value to track the amount of the deduction.

For this input value, set the Special Purpose eld to "Primary Input Value".

Third-Party Deductions Type Set the only valid value as "Adjust Ded Code", and select this value during element entry.

Third-Party Deductions Code Dene values for each of the valid 3-character ADP PayForce deduction codes.

During element entry, select the appropriate code for the deduction code.

Nonrecurring Earnings Elements

The US ADP PayForce third-party periodic extract pulls these nonrecurring earnings types only:
• Supplemental earnings (such as bonuses and commissions)
Nonrecurring regular and imputed earnings aren't included.

• Flat amount earnings
Hours * Rate earnings elements aren't included.
When you dene nonrecurring earnings, create and set these input values for each earnings element:
Input Value Special Instructions
Third-Party Earnings Type

Create these values, based on the ADP earnings codes:
• Earnings 3 Code
• Earnings 4 Code
• Earnings 5 Code
During element entry, select the appropriate code for the earnings type.
Third-Party Earnings Code Dene values for each of the valid 3-character ADP PayForce earnings codes.

During element entry, select the appropriate code for the earnings code.

Payroll Denitions
Consider these points while you create payroll denitions:
• Don't use the bimonthly, lunar monthly, or semiannual payroll frequencies.
• Specify your ADP PayForce Company Code as the rst three characters of the payroll reporting name.
69
ADP Conguration
Consider these points prior to your rst extract execution:
• You must perform a mapping exercise with ADP Connection for PayForce. This establishes the baseline
between the data in ADP and Oracle Fusion Human Capital Management for the United States. Refer to your
ADP documentation for more information.
• Existing ADP Connection for PayForce users would already have identication numbers for their employees
recorded in ADP's system. However, all persons reported through the Payroll Interface must have their own
Oracle employee IDs. You must use ADP's conversion utilities to convert your employees' legacy IDs into the
the new ones that the payroll interface generates..
Alternatively, you can modify the extract to pass the legacy ADP employee ID dependent upon where customer
stores the value.
Related Topics
• Implement Payroll Interface
• Create Payroll Elements
• Manage Payroll Interface
Third-Party Periodic Extract Denition

This topic describes the various component data groups of the US ADP PayForce third-party periodic extract denition
for the Oracle Fusion Global Payroll Interface for the United States.
This extract is provided for ADP PayForce and ADP Connection for PayForce users. You must modify this extract
through the Manage HCM Extract Denitions task in these scenarios:
• Your payroll installation requires additional information be sent to ADP Connection for PayForce
• You are using a dierent third-party provider
Use the provided tree structure to congure the data groups, extract records, and data elements as needed. You dene
what you want to extract, how it's extracted, and how you want to deliver the extracted data.
The US ADP PayForce third-party periodic extract denition consists of these data groups:
Main Block
This data group contains four primary groups of the extract denition. To view its specic parameters, select the
appropriate subordinate data groups in the tree.
Direct Deposit Data
Contains parameters related to personal payment methods.
Earnings and Deductions Data
Contains parameters related to earnings and deductions.
HR Records Data
Contains parameters related to HR data.
70
Job Data
Contains parameters related to jobs.
Earnings Records
This table shows the parameters related to earnings records:
Name Tag Name Type Data Type
PAYROLL_ REL_ACTION_ID PAYROLL_ REL_ACTION_ID Procedure element Number

PAYROLL_ ASSIGNMENT_ID PAYROLL_ ASSIGNMENT_ID Procedure element Number

CALC_ BREAKDOWN_ID CALC_ BREAKDOWN_ID Procedure element Number

BALANCE_ TYPE_ID BALANCE_ TYPE_ID Procedure element Number

BASE_ BALANCE_NAME BASE_ BALANCE_NAME Procedure element Text

RUN RUN Procedure element Text

REPORTING_NAME REPORTING_NAME Procedure element Text

BASE_ CATEGORY_NAME BASE_ CATEGORY_NAME Procedure element Text

PRIME_ ELEMENT_ID PRIME_ ELEMENT_ID Procedure element Number

PRIME_ BASE_ PRIME_ BASE_ Procedure element Text

ELEMENT_NAME ELEMENT_NAME

PRIME_ ELEMENT_NAME PRIME_ ELEMENT_NAME Procedure element Text

PRIME_ ELEMENT_ PRIME_ ELEMENT_ Procedure element Text

REL_LEVEL REL_LEVEL

PRIME_ ELEMENT_ PRIME_ ELEMENT_ Procedure element Text

TERM_LEVEL TERM_LEVEL

PRIME_ ELEMENT_ PRIME_ ELEMENT_ Rule Text

ASG_LEVEL ASG_LEVEL

RULE_ PROCESSING_ TYPE RULE_ PROCESSING_ TYPE Rule Text
71

Third-Party Earnings Code RULE_ EARNING_CODE Rule Text

Third-Party Earnings Type RULE_ EARNING_TYPE Rule Text

RULE_ EARNING_ END_DATE RULE_ EARNING_ END_DATE Rule Date

RULE_ HOURLY_RATE RULE_ HOURLY_RATE Rule Number

RULE_ PERIODICITY RULE_ PERIODICITY Rule Text

BALANCE_TYPE_ID
Internal balance identication number. Not passed on the extract.
BASE_BALANCE_NAME
User-dened name of the balance.
BASE_CATEGORY_NAME
Name of the balance category. Not passed on the output le to third party.
CALC_BREAKDOWN_ID
Internal identication number. Not passed to the third-party provider.
PAYROLL_ASSIGNMENT_ID
PAYROLL_REL_ACTION_ID
Internal ID generated from the Calculate Gross Earnings process. Used for the calculation of earnings only and not
passed on the extract
PRIME_BASE_ELEMENT_NAME
Base element name, as dened on the Manage Elements page.
PRIME_ELEMENT_ID
PRIME_ELEMENT_ASG_LEVEL
72
Indicates if this element was created at the assignment level.
PRIME_ELEMENT_NAME
User-dened element name, as dened on the Manage Elements page.
PRIME_ELEMENT_REL_LEVEL
Indicates if this element was created at the payroll relationship level.
PRIME_ELEMENT_TERM_LEVEL
Indicates if this element was created at the terms level.
REPORTING_NAME
Balance's reporting name, as dened in the Reporting Name eld in the Manage Balance Denitions task.
RULE_EARNING_END_DATE
End date of the earnings element.
RULE_HOURLY_RATE
Salary amount.
RULE_PERIODICTY
Element frequency.
RULE_PROCESSING_TYPE
Identies the element as recurring or nonrecurring.
RUN
Value of the balance.
Third-Party Earnings Code
Three-character code used by ADP PayForce for the nonrecurring earning. Dened in an input value on the deduction
element.
ADP PayForce earning code type assigned to this earning. Dened in an input value on the earnings element.
Earnings and Deductions Balances

This node contains four subordinate data nodes for earnings and deductions. To view its specic parameters, select the
appropriate subordinate nodes elsewhere in the tree.
Earnings Data
73
Contains internal identiers related to earnings records.
Taxable Benets Data
Contains internal identiers related to taxable benets.
Pre-Statutory Deductions Data
Contains internal identiers related to prestatutory deduction records.
Voluntary Deductions Data
Contains internal identiers related to voluntary deduction records.
Earnings and Deductions Records

Earnings and deductions information derived from user-dened deduction element entries and earnings balances.
Record Type Record_Type String Text

Company Company Database item group Text

Payroll Payroll Database item group Text

Payroll Frequency Payroll_ Frequency Database item group Text

Record Number Record_Number Database item group Number

Employee ID Employee_ID Database item group Text

Assignment ID Assignment_Id Database item group Number

Third-Party ID National_ Identier_ Number Database item group Text

Assignment ID
Internal ID for the employee's assignment. Not passed on the extract and ADP doesn’t use it.
Company
Tax reporting unit responsible for the employee's tax and regulatory reporting, as dened on their tax card.
Employee ID
74
For new ADP customers, this 11-character value uses the AABB3456789 paern, where:
• AA are the rst two characters of the employee's rst name. If the rst name is missing, "FF" is used.
• BB are the rst two characters of the employee's last name.
• 3456789 are the third through ninth digits of the employee's national identier, rearranged to maintain privacy.
For example: "John Smith 123-45-6789" could become "JOSM5398647".
Payroll
Name of the payroll denition, as dened in the Manage Payroll Denitions task.
Payroll Frequency
Frequency of the payroll denition, as dened in the Manage Payroll Denitions task.
Record Number
Record number derived and passed to ADP on the job, deductions, and direct deposit records. Automatically generated,
based on the employee's assignments.
Note: Third-party providers other than ADP may require dierent assignment identiers compliant with
their own formaing.
Record Type
Identies this record as delivering earnings and deductions-specic information about the extract. For use by the third-
party provider only.
Third-Party ID
ADP PayForce 6-digit le number. Dened as a dierent lookup under the national identier.
Pre-Statutory Deductions Records

The values for these parameters are derived from the input values for prestatutory deduction elements.
Reserve Value Reserve_Value Database item group Text

Entry Value Entry_Value Database item group Text

Deduction End Date Deduction_ End_Date Database item group Date

Eective Date Eective_Date String Text

Deduction Code Deduction_Code Database item group Text
75

Indirect Only Indirect_Only Database item group Text

Processing Type Processing_ Type Database item group Text

Usage Level Usage_Level Database item group Text

Element Assignment ID Element_ Assignment_Id Database item group Number

Element Entry ID Element_ Entry_Id Database item group Number

Element Frequency Element_ Frequency Rule Text

Deduction Code
Name of the element.
Deduction End Date
End data of the element entry.
Eective Date
Not used and not passed to the third-party provider.
Element Assignment ID
Element Entry ID
Internal ID for the element entry.
Element Frequency
Periodicity of the earning or deduction, as dened by the element's input value identied with the Periodicity special
purpose.
Entry Value
Represents the earning or deduction amount, as dened by the element's input value identied with the Primary Input
Value special purpose.
Indirect Only
Identies direct or indirect entries at the element level. Elements marked as indirect are excluded from the extract.
76
Processing Type
Identies the element as recurring or nonrecurring, as dened during element denition.
Reserve Value
Input value specied during element entry.
Usage Level
Indicates the level where the element is assigned. Valid values are Payroll Relationship, Assignment, and Term.
Taxable Benets Records

This data group contains information derived from Imputed Earnings elements. Some of these parameter values are
derived from the element denition, and some are from the employees' element entry.











Deduction Code
77
Deduction End Date
End date of the element entry.
Eective Date
Element Entry ID
Element Frequency
purpose.
Entry Value
Indirect Only
Processing Type
Reserve Value
Usage Level
Identies the level at which the element is assigned. Valid values are Payroll Relationship, Assignment, and Term.
Voluntary Deductions Goal Amount Records

This data group contains information in the Goal Amount special input value. This parameter is used when the
deduction element has a maximum threshold.
Goal Amount
Denes the maximum amount accrued before the deduction stops. Set as an input value during element entry.
HR Records
This data group contains HR-specic information about the employer and employees.
78




First Name First_Name Database item group Text

Middle Name Middle_Name Database item group Text

Last Name Last_Name Database item group Text

Name Sux Name_Sux Database item group Text

Name Prex Name_Prex Database item group Text

Preferred Name Preferred_Name Database item group Text

Street 1 Street1 Database item group Text



City City Database item group Text

State State Database item group Text

Postal Code Zip Database item group Text

Country Country Database item group Text

Street 1 Other Street1_Other Database item group Text


79

City Other City_Other Database item group Text

State Other State_Other Database item group Text

Postal Code Other Zip_Other Database item group Text

Country Other Country_Other Database item group Text

SSN SSN Database item group Text

Original Hire Date Original_ Hire_Date Database item group Date

Gender Sex Database item group Text

Marital Status Marital_Status Database item group Text

Birth Date Birth_Date Database item group Date

Date of Death Date_of_Death Database item group Date

Visa Number Visa_Number Database item group Text

Visa Expiry Date Visa_ Expiry_Date Database item group Date

Visa Type Visa_Type Database item group Text

E-Mail Address Email_Address Database item group Text

Ethnicity Race_Ethnicity Database item group Text

Home Phone Home_Phone Database item group Text

Work Phone Work_Phone Database item group Text


80
Citizenship Status Citizenship_ Status Database item group Text

Citizenship Citizenship Database item group Text

Home Phone Area Code Home_ Phone_ Area_Code Database item group Text

Work Phone Area Code Home_ Phone_ Area_Code Database item group Text

Birth Date
Employee's date of birth, as dened in the Person Information page.
Citizenship
Employee's national citizenship, as dened in the Documents tab of the Person Information page.
Citizenship Status
Employee's national citizenship status, as dened in the Documents tab of the Person Information page.
City
City of the employee's home address, as dened in the Person Information page.
City Other
City of the employee's mailing address, as dened in the Person Information page.
Company
Country
Country of the employee's home address, as dened in the Person Information page.
Country Other
Country of the employee's mailing address, as dened in the Person Information page.
Date of Death
Employee's date of death, as dened in the Person Information page.
E-Mail Address
Employee's email address, as dened in the Person Information page.
81
Employee ID
Ethnicity
Employee's ethnicity, as dened in the Person Information page.
First Name
Employee's rst name, as dened in the Person Information page.
Gender
Employee's gender, as dened in the Person Information page.
Home Phone
Employee's home phone number, as dened in the Person Information page.
Home Phone Area Code
Area code of employee's home phone number, as dened in the Person Information page.
Last Name
Employee's last name, as dened in the Person Information page.
Marital Status
Employee's marital status, as dened in the Person Information page.
Middle Name
Employee's middle name, as dened in the Person Information page.
Name Prex
Employee's name prex, as dened in the Person Information page.
Name Sux
Employee's name sux, as dened in the Person Information page.
Original Hire Date
82
Employee's original date of hire, as dened in the Enterprise section of the Service Dates region of the Manage Work
Relationship page.
Payroll
Name of the payroll denition assigned to the employee, as dened in the Manage Payroll Denitions page.
Payroll Frequency
Frequency of the payroll denition assigned to the employee, as dened in the Manage Payroll Denitions page.
Postal Code
Postal code of the employee's home address, as dened in the Person Information page.
Postal Code Other
Postal code of the employee's mailing address, as dened in the Person Information page.
Preferred Name
Employee's preferred name, as dened in the Person Information page.
Record Type
Identies this record as delivering HR-specic information about the extract. For use by the third-party provider only.
SSN
Employee's social security number, as dened in the Person Information page.
State
Two-leer postal abbreviation of the employee's state, based on their home address, as dened in the Person
Information page.
State Other
Two-leer postal abbreviation of the employee's state, based on their mailing address, as dened in the Person
Information page.
Street 1
Street 1 eld of the employee's home address, as dened in the Person Information page.
Street 1 Other
Street 1 eld of the employee's mailing address, as dened in the Person Information page.
Street 2
Street 2 Other
83
Street 3
Street 3 Other
Work Phone
Employee's work phone number, as dened in the Person Information page.
Work Phone Area Code
Area code for employee's work phone number, as dened in the Person Information page.
Visa Number
Employee's visa number, as dened in the Documents tab of the Person Information page.
Visa Expiry Date
Expiration date of the employee's visa, as dened in the Documents tab of the Person Information page.
Visa Type
Type of employee's visa, as dened in the Documents tab of the Person Information page.
Job Records
This data group contains job-specic information for the employer and employees.

Hire Date Hire_Date Database item group Date

Company Seniority Date Company_ Seniority_ Date Database item group Date

Termination Date Termination_ Date Database item group Date

Home Department Home_ Department Database item group Text


84


Retirement Date Retirement_ Date Database item group Date

Job Title Job_Title Database item group Text

Job Code Job_Code Database item group Text

Employment Status Employment_ Status Database item group Text

Location Name Location_Name Database item group Text

Location Code Location_Code Database item group Text

Employment Category Employment_ Category Database item group Text

Employee Type Employee_Type Database item group Text

Standard Hours Standard_Hours Database item group Text


Standard Hours Frequency Standard_ Hours_ Frequency Database item group Text

First Name FIRST_NAME_J Database item group Text

Last Name LAST_NAME_J Database item group Text

SSN SSN_J Database item group Text


Supervisor ID Supervisor_ID Database item group Text

Salary Basis Amount Salary_ Basis_Amount Database item group Number

85
Salary Basis Frequency Salary_ Basis_ Frequency Database item group Text

Company
Company Seniority Date
Employee's seniority date, as dened in the Legal Employer section of the Service Dates region of the Manage Work
Relationship page.
Employee ID
Employee Type
Employee exemption status, as dened in the Hourly Paid or Salaried elds of the Job Details section of the
Assignment Details region of the Manage Employment page.
Employment Category
Employee employment category, as dened in the Assignment Category eld of the Job Details section of the
Employment Status
Employee's employment status (full time, part time, regular or temporary, and so on). Dened in the Assignment
Category eld of the Job Details section of the Assignment Details region of the Manage Employment page.
First Name
Hire Date
Employee's hire date, as dened in the Work Relationship section of the Manage Employment task.
Home Department
Employee's home department, as dened on the employee's assignment or term.
Job Code
86
Job code assigned to the employee's job, as dened in the Manage Jobs page.
Job Title
Employee's job title, as dened in the Job eld of the Job Details section of the Assignment Details region of the
Manage Employment page.
Last Name
Location Code
Code assigned to the employee's work location, as dened in the Manage Locations page.
Location Name
Name of the employee's work location, as dened in the Manage Locations page.
Payroll
Payroll Frequency
Record Number
Identies the employee's assignment, with 0 representing the primary assignment, and increments by 1 for each
subsequent assignment.
Record Type
Identies this record as delivering job-specic information about the extract. For use by the third-party provider only.
Retirement Date
Employee's date of retirement, as dened in the Retirement section of the Assignment Details region of the Person
Information page.
Salary Basis Amount
Employee's salary amount, as dened in the Salary Details section of the Manage Salary page.
Salary Basis Frequency
Employee's salary basis, as dened in the Salary Details section of the Manage Salary page.
SSN
87
Standard Hours
Employee's standard number of work hours per period, as dened in the Working Hours eld of the Job Details section
of the Assignment Details region of the Manage Employment page.
Standard Hours Frequency
Period set for the employee's working hours, as dened in the Frequency eld of the Assignment Details region of the
Supervisor ID
Employee's supervisor, as dened in the Name eld of the Manager Details subsection of the Job Details section of the
This 11-character value uses the AABB3456789 paern, where:
Termination Date
Employee's termination date, as dened through the Terminate Work Relationship task.
Job Extra Block

This data group contains FLSA information related to the employees.
FLSA Status
Employee's overtime exemption status, as dened in the FLSA Status eld of the United States Job Information section
of the Manage Jobs task.
Pre-Statutory Deductions Goal Amount Records

Goal Amount
Taxable Benets Goal Amount Records

Goal Amount
88
Direct Deposit Records

This data group contains information about personal payment methods.





Payment Priority Payment_ Priority Database item group Number

Transit Number Transit_Number Database item group Text

Account Number Account_Number Database item group Text

Deposit Amount Deposit_Amount Database item group Text

Payment Method End Date Deduction_ End_Date Database item group Date

Account Type Account_Type Database item group Text


Maximum Payment Priority Maximum_ Payment_ Priority Database item group Number

Account Number
Employee's bank account number for direct deposit, as dened in the Bank Accounts table of the Manage Personal
Payment Methods task.
Account Type
Identies the account as either checking or savings. Dened in the Manage Personal Payment Methods task.
89
Company
Deposit Amount
Amount of each direct deposit, as dened in the personal payment method.
Eective Date
Employee ID
Maximum Payment Priority
While not passed on the extract, this parameter is used to derive the Full Deposit value on the extract.
Payment Method End Date
Eective end date of the direct deposit.
Payment Priority
Processing order of the personal payment method. While this parameter isn’t passed on the extract, it's used to derive
the Full Deposit value on the extract.
Payroll
Payroll Frequency
Record Type
Identies this record as delivering information specic to direct deposits on the extract. For use by the third-party
provider only.
Transit Number
Employee's personal bank transit number.
90
Voluntary Deductions Records

The values for these parameters are derived from the input values for voluntary deduction elements.









Input Value Name Input_ Value_Name Database item group Text

Element Type ID Element_ Type_ID Database item group Number

Third-Party Deduction Type Third_ Party_ Deduction_ Rule Text

Type

Third-Party Deduction Code Third_ Party_ Deduction_ Rule Rule Text



Deduction Code
91
Deduction End Date
Eective Date
Start date of the element entry.
Element Entry ID
Element Frequency
purpose.
Element Type ID
Internal ID used to identify the element denition.
Entry Value
Indirect Only
Input Value Name
Name of the input value.
Processing Type
Reserve Value
Third-Party Deduction Code
Three-character code used by ADP PayForce for the nonrecurring deduction. Dened in an input value on the
deduction element.
Third-Party Deduction Type
92
Used as a column header in the output le. Value must be "Adjust Ded Code" and is dened in an input value on the
deduction element.
Usage Level
Extract Delivery Options

Denes the extract output, such as PDF, XML le, CSV, Excel, and so on. ADP Connection for PayForce requires text
format.
US ADP Connection for PayForce Recurring
Name of the ADP Connection for PayForce output le containing recurring element data.
US ADP PayForce Nonrecurring
Name of the ADP Connection for PayForce output le containing nonrecurring element data.
US ADP PayForce XML
Name of the XML le. For use in cases where you want to use a third-party provider other than ADP.
Third-Party Ad-Hoc Extract Denition

This topic describes the various component data groups of the US ADP PayForce third-party ad hoc extract denition
for the Oracle Fusion Global Payroll Interface for the United States.
This extract has been provided for ADP PayForce and ADP Connection for PayForce users. Modify this extract through
the Manage HCM Extract Denitions task in these scenarios:
• Your payroll installation requires additional information be sent to ADP Connection for PayForce
• You are using a dierent third-party provider
Use the provided tree structure to congure the data groups, extract records, and data elements as needed. You dene
what you want to extract, how it's extracted, and how you want to deliver the extracted data.
The US ADP PayForce third-party ad hoc extract denition consists of these data groups:
Main Block
This data group contains the four primary groups of the extract denition. To view its specic parameters, select the
appropriate subordinate data groups in the tree.
Direct Deposit Data
Contains parameters related to personal payment methods.
Earnings and Deductions Data
Contains parameters related to earnings and deductions.
93
HR Records Data
Contains parameters related to HR data.
Job Data
Contains parameters related to jobs.

This data group contains information about personal payment methods.


TRU TRU Database item group Text



Payment Priority Payment_ Priority Database item group Number

Routing Transit Number Routing_ Transit_ Number Database item group Text

Account Number Account_Number Database item group Text

Deposit Amount Deposit_Amount Database item group Text

Payment Method End Date Deduction_ End_Date Database item group Date

Account Type Account_Type Database item group Text


Maximum Payment Priority Maximum_ Payment_ Priority Database item group Number

Previous Payment Method Previous_ Payment_ Method_ Rule Date

End Date End_Date

94
Account Number
Account Type
Deposit Amount
Eective Date
Employee ID
• AA are the rst two characters of the employee's rst name. If the rst name is missing, FF is used.
For example: "John Smith 123-45-6789" could become JOSM5398647.
Maximum Payment Priority
While not passed on the extract, this parameter is used to derive the Full Deposit value on the extract.
Payment Priority
Processing order of the personal payment method. While this parameter isn't passed on the extract, it's used to derive
the Full Deposit value on the extract.
Payroll
Payroll Frequency
Previous Payment Method End Date
Date when a payment method's bank account is changed, as dened through the Manage Personal Payment Methods
task.
95
Record Type
provider only.
Routing Transit Number
TRU
Earnings Records
Contains parameters related to earnings records.
Element Entry End Date Element_ Entry_ End_Date Database item group Date


Element Name Element_Name Database item group Text

Element ID Element_ID Database item group Number

Element Entry ID Element_ Entry_ID Database item group Number

Third-Party Earnings Code Third_ Party_ Earnings_Code Rule Number

Third-Party Earnings Type Third_ Party_ Earnings_Type Rule Number

Salary Conversion Rule Hourly_Rate Rule Text

Periodicity Periodicity Rule Text

Element Processing Type Element_ Processing_ Type Database item group Text

Converted Value Converted_ Value Rule Text

Element Assignment ID Element_ Assignment_ID Database item group Number

96

Converted Value
Calculates element entries based on the element's periodicity.
Internal assignment ID of the employee aached to the element entry. Not passed to the third-party provider.
Element Entry End Date
End date of the element entry, as dened through the Manage Element Entries task.
Element Entry ID
Internal ID of the element entry.
Element ID
Element Name
User-dened element name, as dened on the Manage Elements page.
Element Processing Type
Identies the element as recurring or nonrecurring.
Entry Value
Value passed on the element entry.
Periodicity
Element frequency.
Salary Conversion Rule
Salary amount.
Third-Party Earnings Code
Three-character code used by ADP PayForce for the nonrecurring earning. Dened in an input value on the deduction
element.
ADP PayForce earning code type assigned to this earning. Dened in an input value on the earnings element.
97
Usage Level
Identies the level at which the element was entered: payroll relationship, employment terms, and assignment.
Earnings and Deductions Element Entries

This node contains four subordinate data nodes for earnings and deductions element entries. To view its specic
parameters, you must select the appropriate subordinate nodes elsewhere in the tree.
Earnings Data
Contains internal identiers related to earnings records.
Taxable Benets Data
Contains internal identiers related to taxable benets.
Pre-Statutory Deductions Data
Contains internal identiers related to prestatutory deduction records.
Voluntary Deductions Data
Contains internal identiers related to voluntary deduction records.

Contains parameters related to earnings and deductions record details.

TRU Company Database item group Text





Assignment ID Assignment_ID Database item group Number

Third-Party ID Third_Party_ID Database item group Number

98
Payroll Reporting Name Payroll_ Reporting_ Name Database item group Text

Assignment ID
Internal ID for the employee's assignment. Not passed on the extract and isn't used by ADP.
Employee ID
Payroll
Payroll Frequency
Payroll Reporting Name
Reporting name of the payroll denition, as dened in the Manage Payroll Denitions task.
Record Number
Record number derived and passed to ADP on the job, deductions, and direct deposit records. Automatically generated,
based on the employee's assignments.
Record Type
Third-Party ID
TRU
99
HR Records
This data group contains HR-specic information about the employer and employees.




First Name First_Name Database item group Text

Middle Name Middle_Name Database item group Text

Last Name Last_Name Database item group Text

Name Sux Name_Sux Database item group Text

Name Prex Name_Prex Database item group Text

Preferred Name Preferred_Name Database item group Text

Address Line 1 Address_Line1 Database item group Text



City City Database item group Text

State State Database item group Text

Postal Code Postal_Code Database item group Text

Country Country Database item group Text

Address Line 1 Other Address_ Lin1_Other Database item group Text
100



City Other City_Other Database item group Text

State Other State_Other Database item group Text

Postal Code Other Postal_ Code_Other Database item group Text

Country Other Country_Other Database item group Text

SSN SSN Database item group Text

Original Hire Date Original_ Hire_Date Database item group Date

Gender Sex Database item group Text

Marital Status Marital_Status Database item group Text

Birth Date Birth_Date Database item group Date

Date of Death Date_of_Death Database item group Date

Visa Number Visa_Number Database item group Text

Visa Expiration Date Visa_ Expiration_ Date Database item group Date

Visa Type Visa_Type Database item group Text

E-Mail Address Email_Address Database item group Text

Ethnicity Race_Ethnicity Database item group Text

Home Phone Home_Phone Database item group Text

Work Phone Work_Phone Database item group Text
101


Citizenship Status Citizenship_ Status Database item group Text

Citizenship Citizenship Database item group Text

Home Phone Area Code Home_ Phone_ Area_Code Database item group Text

Work Phone Area Code Home_ Phone_ Area_Code Database item group Text

Address Line 1
Address Line 1 Other
Address Line 2
Address Line 3
Birth Date
Citizenship
Citizenship Status
102
City
City Other
Country
Country Other
Date of Death
E-Mail Address
Employee's email address, as dened in the Person Information page.
Employee ID
Ethnicity
First Name
Gender
Home Phone
Home Phone Area Code
Area code of employee's home phone number, as dened in the Person Information page.
103
Last Name
Marital Status
Middle Name
Name Prex
Name Sux
Original Hire Date
Employee's original date of hire, as dened in the Enterprise section of the Service Dates region of the Manage Work
Relationship page.
Payroll
Payroll Frequency
Postal Code
Postal Code Other
Preferred Name
Record Type
SSN
State
104
Information page.
State Other
Information page.
TRU
Work Phone
Work Phone Area Code
Area code for employee's work phone number, as dened in the Person Information page.
Visa Number
Visa Expiration Date
Visa Type
Voluntary Deductions Records

The values for these parameters are derived from the input values for voluntary deduction elements.



Eective Date Eective_Date String Date

Reporting Name Reporting_Name Database item group Text

Autoindirect Only Autoindirect_ Only Database item group Text
105




Element Entry ID Element_ Entry_ID Database item group Number


Third-Party Deduction Type Third_ Party_ Deduction_ Rule Text

Type

Third-Party Deduction Code Third_ Party_ Deduction_ Rule Rule Text

Autoindirect Only
Deduction End Date
Eective Date
Element Entry ID
Element Frequency
purpose.
106
Entry Value
Reporting Name
Element's reporting name, as dened on the Manage Elements task.
Reserve Value
Third-Party Deduction Code
Three-character code used by ADP PayForce for the nonrecurring deduction. Dened in an input value on the
deduction element.
Third-Party Deduction Type
Used as a column header in the output le. Value must be Adjust Ded Code and is dened in an input value on the
deduction element.
Usage Level
Pre-Statutory Deductions Goal Amount Records

This data group contains information in the Goal Amount special input value. Use this parameter when the deduction
element has a maximum threshold.
Goal Amount
Pre-Statutory Deductions Records

The values for these parameters are derived from the input values for prestatutory deduction elements.




107
Reporting Name Reporting_Name Database item group Text

Autoindirect Only Autoindirect_ Only Database item group Text






Autoindirect Only
Deduction End Date
End data of the element entry.
Eective Date
Element Entry ID
Element Frequency
purpose.
Entry Value
108
Reporting Name
Reserve Value
Usage Level
Taxable Benets Goal Amount Records

Goal Amount
Taxable Benets Records

This data group contains information derived from Imputed Earnings elements. Some of these parameter values are
derived from the element denition, and some are from the employees' element entry.
Reserve Value Reserve_Value Database item Text

Entry Value Entry_Value Database item Text

Deduction End Date Deduction_ End_Date Database item Date


Reporting Name Reporting_Name Database item Text

Autoindirect Only Autoindirect_ Only Database item Text

Element Processing Type Processing_ Type Database item Text

Usage Level Usage_Level Database item Text

109
Element Assignment ID Element_ Assignment_Id Database item Number

Element Entry ID Element_ Entry_Id Database item Number


Autoindirect Only
Deduction End Date
Eective Date
Element Entry ID
Element Frequency
purpose.
***Identies the element as recurring or nonrecurring, as dened during element denition.
Entry Value
Reporting Name
Reserve Value
Usage Level
110
Identies the level at which the element is assigned. Valid values are Payroll Relationship, Assignment, and Term.
Voluntary Deductions Goal Amount Details

Goal Amount
Job Extra Block

This data group contains FLSA information related to the employees.
FLSA Status
Job Records
This data group contains job-specic information for the employer and employees.

Hire Date Hire_Date Database item group Date

Company Seniority Date Company_ Seniority_ Date Database item group Date

Termination Date Termination_ Date Database item group Date

Home Department Home_ Department Database item group Text




Retirement Date Retirement_ Date Database item group Date

Job Title Job_Title Database item group Text

111
Job Code Job_Code Database item group Text

Employment Status Employment_ Status Database item group Text

Location Name Location_Name Database item group Text

Location Code Location_Code Database item group Text

Employment Category Employment_ Category Database item group Text

Employee Type Employee_Type Database item group Text

Standard Hours Standard_Hours Database item group Text


Standard Hours Frequency Standard_ Hours_ Frequency Database item group Text

First Name FIRST_NAME_J Database item group Text

Last Name LAST_NAME_J Database item group Text

SSN SSN_J Database item group Text


Supervisor ID Supervisor_ID Database item group Text

Salary Basis Amount Salary_ Basis_Amount Database item group Number

Salary Basis Frequency Salary_ Basis_ Frequency Database item group Text

Company Seniority Date
Relationship page.
Employee ID
112
Employee Type
Employment Category
Employee employment category, as dened in the Assignment Category eld of the Job Details section of the
Employment Status
Employee's employment status (full time, part time, regular or temporary, and so on). Dened in the Assignment
Category eld of the Job Details section of the Assignment Details region of the Manage Employment page.
First Name
Hire Date
Home Department
Job Code
Job Title
Last Name
Location Code
Location Name
113
Payroll
Payroll Frequency
Record Number
Record Type
Identies this record as delivering job-specic information about the extract. For use by the third-party provider only.
Retirement Date
Information page.
Salary Basis Amount
SSN
Standard Hours
Standard Hours Frequency
Supervisor ID
114
Termination Date
TRU
Extract Delivery Options

Denes the extract output, such as PDF, XML le, CSV, Excel, and so on. ADP Connection for PayForce requires TXT
format.
US ADP Connection for PayForce Ad-Hoc Recurring
Name of the ADP Connection for PayForce output le containing recurring ad hoc element data.
US ADP PayForce Ad-Hoc Nonrecurring
Name of the ADP Connection for PayForce output le containing nonrecurring ad hoc element data.
US ADP PayForce XML
Name of the XML le. For use in cases where you want to use a third-party provider other than ADP.
Recurring Periodic Output File

This topic describes the format of the recurring periodic output le for the US ADP Connection for PayForce third-party
periodic extract.
The output le consists of these sections:
HR Records
Contains HR-specic information about the employer and employees.
Field Name Extract Node Name Extract Tag Name
Record Type Record Type Record_Type

EMPLID Employee ID Employee_ID

Company Company Company
115

PAYROLL Payroll Payroll

PAY FREQUENCY Payroll Frequency Payroll_ Frequency

FIRST_NAME First Name First_Name

MIDDLE_NAME Middle Name Middle_Name

LAST_NAME Last Name Last_Name

NAME_SUFFIX Name Sux Name_Sux

NAME_PREFIX Name Prex Name_Prex

PREFERRED_NAME Preferred Name Preferred_Name

STREET1 Street 1 Street1



CITY City City

STATE State State

ZIP Postal Code Zip

COUNTRY Country Country

STREET1_OTHER Street 1 Other Street1_Other



CITY_OTHER City Other City_Other
116

STATE_OTHER State Other State_Other

ZIP_OTHER Postal Code Other Zip_Other

COUNTRY_OTHER Country Other Country_Other

SSN SSN SSN

ORIG_HIRE_DT Original Hire Date Original_ Hire_Date

SEX Gender Sex

MAR_STATUS Marital Status Marital_Status

BIRTHDATE Birth Date Birth_Date

DT_OF_DEATH Date of Death Date_of_Death

CITIZENSHIP Citizenship Citizenship

CITIZENSHIP_ STATUS Citizenship Status Citizenship_ Status

VISA_NBR Visa Number Visa_Number

VISA_EXPIRE_DT Visa Expiry Date Visa_ Expiry_Date

VISA_TYPE Visa Type Visa_Type

EMAIL_ADDRESS E-Mail Address Email_Address

RACE_ETHNICITY Ethnicity Race_Ethnicity

HOME_PHONE Home Phone Home_Phone

WORK_PHONE Work Phone Work_Phone

117
BIRTHDATE
CITIZENSHIP
CITIZENSHIP_STATUS
CITY
CITY_OTHER
Company
COUNTRY
COUNTRY_OTHER
DT_OF_DEATH
EMAIL_ADDRESS
Employee's work email address, as dened in the Person Information page.
EMPLID
FIRST_NAME
118
HOME_PHONE
LAST_NAME
MAR_STATUS
MIDDLE_NAME
NAME_PREFIX
NAME_SUFFIX
ORIG_HIRE_DT
Employee's original date of hire, as dened in the Legal Employer section of the Service Dates region of the Manage
Work Relationship page.
PAY FREQUENCY
PAYROLL
PREFERRED_NAME
RACE_ETHNICITY
Record Type
SEX
SSN
119
STATE
Information page.
STATE_OTHER
Information page.
STREET1
STREET1_OTHER
STREET2
STREET2_OTHER
STREET3
STREET3_OTHER
VISA_EXPIRE_DT
VISA_NBR
VISA_TYPE
WORK_PHONE
ZIP
120
ZIP_OTHER
Job Records
Contains job-specic information for the employer and employees.





EMPL_RCD_NBR Record Number Record_Number

HIRE_DT Hire Date Hire_Date

CMPNY_ SENIORITY_DT Company Seniority Date Company_ Seniority_ Date

TERMINATION_DT Termination Date Termination_ Date

SUPERVISOR_ID Supervisor ID Supervisor_ID

RETIRE_DT Retirement Date Retirement_ Date

JOBTITLE Job Title Job_Title

JOBCODE Job Code Job_Code

EMPL_STATUS Employment Status Employment_ Status

LOCATION_NAME Location Name Location_Name

121
LOCATION Location Code Location_Code

ASSIGN_CATG Employment Category Employment_ Category

FLSA_STATUS FLSA Status FLSA Status

EMPL_TYPE Employee Type Employee_Type

STD_HOURS Standard Hours Standard_Hours

STD_ HOURS_ FREQUENCY Standard Hours Frequency Standard_ Hours_ Frequency

Salary Basis Frequency Salary Basis Frequency Salary_ Basis_Amount

Salary Basis Amount Salary Basis Amount Salary_ Basis_ Frequency

HOME_ DEPARTMENT Home Department Home_ Department

WORKERS_ COMP_CD intentionally left blank intentionally left blank

ASSIGN_CATG
Designates the employee's employment status (full time, part time, regular or temporary, and so on). Dened in the
Assignment Category eld of the Job Details section of the Assignment Details region of the Manage Employment
page.
CMPNY_SENIORITY_DT
Relationship page.
Company
EMPL_RCD_NBR
122
EMPL_STATUS
Employee's status, as dened in the Assignment Status eld of the Assignment Details region of the Manage
Employment page.
EMPL_TYPE
EMPLID
FLSA_STATUS
HIRE_DT
HOME_DEPARTMENT
JOBCODE
JOBTITLE
LOCATION
LOCATION_NAME
PAY FREQUENCY
123
PAYROLL
Record Type
Identies this record as delivering jobs-specic information about the extract. For use by the third-party provider only.
RETIRE_DT
Information page.
Salary Basis Amount
STD_HOURS
STD_HOURS_FREQUENCY
SUPERVISOR_ID
TERMINATION_DT
WORKERS_COMP_CD
Placeholder for future functionality. Intentionally left blank.
124

Contains earnings and deductions-specic information for the employer and employees. This includes recurring
earnings.






Element Name Deduction Code Deduction_Code

Element Amount Entry Value Entry_Value

Element Percentage Entry Value Entry_Value

GOAL_AMT Goal Amount Goal Amount

Element End Date Deduction End Date Deduction_ End_Date

ELEMENT FREQUENCY Element Frequency Element_ Frequency

Company
Tax reporting unit responsible for the employee's tax and regulatory reporting, as dened in the Manage Legal
Reporting Unit task.
Element Amount
Value special purpose. Either this value or the Element Percentage value is populated in the le, but not both.
Element End Date
125
Element Name
Element Percentage
Represents the earning or deduction percentage, as dened by the element's input value identied with the Primary
Input Value special purpose. Either this value or the Element Amount value is populated in the le, but not both.
ELEMENT FREQUENCY
purpose. ADP doesn't use this value.
EMPL_RCD_NBR
EMPLID
GOAL_AMT
PAY FREQUENCY
PAYROLL
Record Type
126

Contains direct deposit-specic information for the employer and employees.


TRU Company Company




FULL_DEPOSIT derived derived

TRANSIT_NBR Routing Transit Number Transit_Number

ACCOUNT_NBR Account Number Account_Number

DEPOSIT_AMT Deposit Amount Deposit_Amount

Payment Method End Date Deduction End Date Deduction_ End_Date

ACCOUNT_TYPE Account Type Account_Type

ACCOUNT_NBR
ACCOUNT_TYPE
DEPOSIT_AMT
127
Note: If this aribute is set to any value greater than zero, the FULL_DEPOSIT aribute can't be set to
Yes. For example, the employee wants 100 USD to be deposited into a savings account and the rest
into a checking account. Therefore, for their rst direct deposit record, set DEPOSIT_AMT to "100"
and FULL_DEPOSIT to "N". For the second record, set FULL_DEPOSIT to "Y" and pass nothing in
DEPOSIT_AMT.
EMPL_RCD_NBR
EMPLID
FULL_DEPOSIT
Identies which direct deposit record is the last one that receives all remaining money.
Note: If this aribute is set to Yes, the DEPOSIT_AMT aribute can't be greater than zero. For example,
the employee wants 100 USD to be deposited into a savings account and the rest into a checking
account. Therefore, for their rst direct deposit record, set DEPOSIT_AMT to "100" and FULL_DEPOSIT
to "N". For the second record, set FULL_DEPOSIT to "Y" and pass nothing in DEPOSIT_AMT.
This value is derived and not set on the extract.
PAY FREQUENCY
PAYROLL
Record Type
128
provider only.
TRANSIT_NBR
TRU
Nonrecurring Periodic Output File

This topic describes the format of the nonrecurring periodic output le for the US ADP PayForce third-party periodic
extract.
The output le consists of these sections:
Nonrecurring Records
Contains information for the employees' nonrecurring earnings and deductions.
Note: The US ADP PayForce third-party periodic extract pulls the following nonrecurring earnings and
deductions types only:
• Voluntary deductions Nonrecurring pretax deductions aren't included.
• Supplemental earnings Nonrecurring regular and imputed earnings aren't included.
• Flat amount earnings Hours * rate earnings elements aren't included.
CoCode Payroll Reporting Name Payroll_ Reporting_ Name

Batch Id intentionally left blank intentionally left blank

File # Third-Party ID Third_Party_ID

Earnings 3 Code Third-Party Earnings Code RULE_ EARNING_CODE

Earnings 3 Amount RUN RUN



129


Adjust Ded Code Third-Party Deduction Code Third_ Party_ Deduction_ Code

Adjust Ded Amount Entry Value Entry_Value

Adjust Ded Code
ADP PayForce deductions code for the employee's deduction, as set through the element's Third-Party Deductions
Code input value.
Adjust Ded Amount
Amount of the deduction.
Batch Id
This eld is intentionally left blank and is automatically populated by the ADP for PayForce External Paydata Interface
Program process upon receipt.
CoCode
First three characters of the payroll reporting name as dened in the Manage Payroll Denitions task.
Earnings 3 Code
ADP PayForce earnings code for the employee's earning, as set through the element's Earnings 3 Code input value.
Earnings 3 Amount
Amount of this Earnings 3 type earning. The Third-Party Earnings Type determines whether this value is populated.
Earnings 4 Code
Earnings 4 Amount
Earnings 5 Code
Earnings 5 Amount
130
File #
131
132
Implementing Global Payroll Interface Payroll Interface for ADP Workforce Now
6 Payroll Interface for ADP Workforce Now
Overview of ADP Workforce

To set up payroll interface for ADP-WFN, dene the value sets and the object group for payroll relationship. Once you
dene the requirements for payroll relationship, associate the employees to payroll. Use the delivered Run Payroll
Interface for ADP Workforce New ow paern to run the payroll interface extract process.
Dene Value Sets

Create value sets for multiple company details. The application delivers the
ORA_HRY_PAYROLL_COMPANY_CODE_VALUESET value set.
Here's how you can enter values for ORA_HRY_PAYROLL_COMPANY_CODE_VALUESET company code value set:
1. Navigate to the Manage Value Sets task..

2. Search for the ORA_HRY_PAYROLL_COMPANY_CODE_VALUESET value set.
5. Enter each company code as a new value.
Dene Object Groups

Extract the multiple payroll group employee data in a single le and use the Manage Object Groups task to group
the payroll in a single extract. Run the extract process for each object group to extract data belonging to the grouped
payrolls. Use the same approach to group employees that weren't included in the extract or that must be extracted
again.
Associate Employees to Payroll

Specify the payroll to which the employee must be mapped in the Payroll Details sub section of the Assignment section
while hiring an employee using the Oracle Fusion HCM hire ow. On the Manage Payroll Relationships page, you can
associate newly-hired employees to the respective payroll.
Run the ADP Workforce New Interface Process

Use the Submit HCM Extract Task from the Data Exchange work area to execute Run Payroll Interface for ADP
Workforce New extract process.
133
Delivered Contexts and Segments

The context and segments are delivered to accommodate the additional aributes.
This table shows the contexts that are available under the Assignment EIT Information EFF exeld, which is associated
with the respective PER_ASSIGNMENT_EXTRA_INFO_M table.
Context Name Use To
ORA_ HRY_ GPI_ WFN_EMP_INFO Capture employment details of employees at the assignment level

ORA_ HRY_ GPI_ WFN_ PAYROLL_ Accommodate additional payroll agreement custom eld aributes.
ADDL_INFO

ORA_ HRY_ GPI_ WFN_JOB_INFO Create the Compensation Defaulting Values, which is used for NAICS Compensation code at
Employee level in Assignment UI.

You can enable and deploy these contexts.
FLEXFIELD NAME PER_ASSIGNMENT_EIT_EFF PER_ASSIGNMENT_EIT_EFF
Flexeld Code Assignment EIT Information EFF Assignment EIT Information EFF

Context Code (Code) ORA_ HRY_ GPI_ WFN_EMP_INFO ORA_ HRY_ GPI_ WFN_ PAYROLL_INFO

Context Name (Display Name) GPI Workforce Now Extended GPI Workforce Now Extended Payroll
Employment Information Additional Information

Behavior Single Row Single Row

Enabled Yes Yes

Enable the Context

Here's how you can enable the delivered exeld context:
Note: Before you enable the context, consult with ADP.
1. Navigate to the Payroll work area.

2. Click Checklist.
134
3. Select Submit a Process or Report from the Payroll Flow.

4. Select a US Legislative Data Group.
5. Search for and select the Manage Global Payroll Interface Feature Usage ow.
6. Click Next.
7. On the Enter Parameters page, complete these elds:
Flow Parameter Value
Payroll Flow Name Meaningful name

Activate Usage Yes

Feature
Search for and select Assignment EIT Information EFF.
Component Search for and select GPI Workforce Extended Employment Information.

Subcomponent Select the required subcomponent.

8. Click Submit.
9. You can repeat steps 3 through 7 to enable Extended Payroll Additional Information.
10. Select these parameters.
Flow Parameter Value
Payroll Flow Name Meaningful name

Activate Usage Yes

Feature
Search for and select Assignment EIT Information EFF.
Component
Search for and select GPI Workforce Extended Payroll Additional Information.
Subcomponent Select the required subcomponent.

11. Click Submit.
Deploy Extensible Flexelds

Here's how you can deploy extensible exelds:
Note: Before you deploy the extensible exelds, consult with ADP.
1. Navigate to the Setup and Maintenance work area.
135
2. Search for and select the Manage Extensible Flexelds task.

3. On the Manage Extensible Flexelds page, search for the Assignment EIT Information EFF exeld.
4. Click Deploy Flexeld.
5. Ensure that the deployment completes successfully and the deployment status column displays a green tick
mark.
Delivered Lookups
The delivered LOVs are either lookup codes with specic lookup types or value sets. For example, Pay Frequency Code
is a lookup code, but Company Code and Client Code are value set values.
Aribute WFN-LOVs GPI-LOVs Description Remarks
Gender • M- MALE • F • Female If you don't specify

• F- FEMALE • M • Male a value, the ADP
application translates it
• N- Not Specied
as N.

Pay Frequency Code • B-Biweekly • Bi-Monthly • Bimonthly

The application creates
• D-Daily • Bi-week • Biweekly these time periods.
• M-Monthly • Calendar Month • Monthly
• S-Semimonthly • Quarter Calendar • Bimonthly:
• W-Weekly • Semi-Month • Quarterly Time periods
• Semi-Year • Semimonthly occurring once
• Semiannually in two months.
• Week
• Weekly • Biweekly: Time
• Year periods every 14
days.
• Semimonthly:
Time periods
occurring twice a
month.
• The application
doesn't support
Daily.
Education Level • ASC- Associate • BACHELOR • Bachelor Degree This is a 3 character

• DOC- Doctorate • CA_10 • High school eld.
and above graduate
• CA_20
• DPL- Diploma • CA_80 • Associate
• GRD- Graduate degree
• DOCTORAL
• MS- ** MASTERS • Other education
level
• NI- Not Indicates
• Doctorate
• UGR - Under
Master Degree
Graduate
EEO Ethnic Code • White • 1 • White The application

• African • 2 • Two or more translates '2' to '9', '3' to
American races '2', '4' to '3', '5' to '4', '7'
• 3
to '5'.
• Hispanic or • 4 • Black or African

Latino • American
• 5
• Asian • 6
136
• Indian or • 7 • Hispanic or
Alaskan • 8 Latino Asian
• Hawaiian/Pacic • Native Hawaiian
Islander or other Pacic
• Two or more Islander
races • American Indian
or Alaska Native
• Not disclosed
Salutation • Dr. • DR. • Doctor. The application checks

• Hon. • MS. • Ms. if upper or lower case
makes a dierence.
• Miss. • MISS • Miss.

• Mrs. • MRS. • Mrs.
• Mr. • MR. • Mr.
• Ms.
• Msgr.
• Rabbi.
EEOC Job Code • 1- First/Mid- • FIR/ • First, middle If you don't specify
Level Ocials MIDOFFICIAL level ocials and a value, the ADP
and Managers • PROFESSIONAL managers application translates it
• 2- Professionals • Professionals as N.
• TECHNICIAN

• 3- Technicians • SALES • Technicians
• 4- Sales Workers • ADMIN • Sales workers
• 5- • CRAFTWORKER • Administrative
Administrative support workers
• OPERATIVE
Support Workers • Craft workers
• LABOURER
• 7- Operatives • Operatives
• SERVICE EXECS
• 8- Laborers and • Laborers and
Helpers • MIDLEVEL
helpers
• 9- Service • Service workers
Workers • Executive or
• A- Executive/ senior level
Senior Level ocials and
Ocials and managers
Managers • First or mid level
ocials and
managers
Employee Type • Full Time • PR • Part-time User dened. 4

• Part Time • PT regular characters. The
• Part-time application doesn't
• FT
translate. Ensure that
• FR • Temporary
the values are in the
• Full-time ADP table.
temporary
• Full-time regular
Hire Reason • CDD • Fixed-term - Pass the Action Code

• CDI CDD and Action Reason to
WFN for reference.
• NEWHIRE

137
• Permanent - CDI
Hire to ll vacant
position.
Termination Reason • WORK_RELATED • Work Incident

• DISMISSAL or Work Related
WORK_RELATED Illness Dismissal
• REDUND_ECONOMIC • Work Incident
or Work Related
• RESIGNATION
Illness
• RESIGN_PERSONAL
• Redundancy
• RETIRE_VOLUNTARY following
• RETIRE_UNVOLUNTARY economic
• WORK_RELATED recovery
• TERMINATE_END_CDD • Resignation
• TERMINATE_MUTUAL • Personal
Reasons
• Voluntary
retirement
Involuntary
retirement
• Work Incident
or Work Related
Illness
• End of xed
term contract
Contract breach
by mutual
agreement
Bank Deposit • S-Saving CHECKING Checking Money The application

Deduction Type • C-Checking MONEYMRKT market Savings translates Checking
SAVINGS to C and Savings to
S. MONEYMRKT is
invalid.

Create Payroll Elements

This example shows how to dene elements for a US legislative data group where the country extension is set to Payroll
Interface.
This table summarizes the key decisions for each element that you dene and provides the selections for this example.
What is the primary classication?

One of these choices:
• Standard Earnings
• Supplemental Earnings
• Taxable Benets
138
• Pretax Deductions
• Voluntary Deductions
Information elements aren't supported.
At which employment level should this element be aached?

Select the appropriate level. Typical examples are:
• Payroll relationship level for deductions and benets

elements
• Assignment or terms level for salary, pension, and social
insurance elements
• Assignment level for overtime rules, rates, and bonus
elements
Verify whether your third-party payroll provider can handle terms-

level information.
Does this element recur each payroll period, or does it require

explicit entry? Select Recurring or Nonrecurring.

What are the values to enter for deduction elements? Period Deduction Amount

Goal Amount

Dene an Element
Before you dene an element, ensure that your country extension is set to Payroll Interface on the Manage Features
by Country or Territory page. This seing controls the behavior of important payroll-related features, such as element
templates.
1. Navigate to these tasks:

◦ Functional Area: Elements and Formulas
2. On the Manage Elements page, Search Results section, click Create.
3. Select your legislative data group.
4. Select the primary classication that matches the purpose or use of the payroll element.
Recurring base pay Annual salary, hourly earnings Standard Earnings

Recurring payments Allowance Standard Earnings

139
Nonrecurring payments Bonus Supplemental Earnings

Recurring or nonrecurring voluntary Savings plans, charitable contributions, Voluntary Deductions

deductions or uniform deposit

5. In the Category eld, select Standard.

6. Select the secondary classication that corresponds to the selected primary classication.
Example Purpose or Use Secondary Classication
Recurring base pay Regular

Nonrecurring payment Bonus

Recurring voluntary deduction Select the relevant choice. If there is none, leave it blank.

7. Click Continue.
8. On the Basic Information page, complete these elds. Click Next.
Field Sample Value
Name Annual Salary

Hourly Wages

Allowance

Spot Bonus

Red Cross Contribution

Reporting Name Enter the name that you want to display on reports for this earnings or deduction payroll
element.

Eective Date 1/1/1951

Enter an early date so that the payroll element is available for use immediately.

Currency US Dollar

Should every person eligible for the No

element automatically receive it?

140
Field Sample Value
What is the earliest entry date for First Standard Earnings Date
this element?

element?

At which employment level should Select the appropriate level, such as terms or assignment level for salary.
this element be aached?

Does this element recur each payroll Recurring or Nonrecurring

entry?

Process the element only once in Yes

each payroll period?

Can a person have more than one No

entry of this element in a payroll
period?

Process and pay element separately Does this element have a limit on the amount which is exempt from Federal Tax?
or with other earnings elements?


the amount which is exempt from
Federal Tax?


the amount which is exempt at state
level?

9. Click Next.
10. On the Additional Details page, complete these details:
Field Value
What is the default periodicity of this Bimonthly

element?

Periodicity Conversion Rule Standard Rate Annualized

11. Verify whether the information is correct, click Submit.
141
Set Up Values for Deduction Elements

Congure values for deductions and select the special purpose Primary Input Value as one of the values.
Specify a value that limits the amount deducted for a value using a goal amount for recurring elements.
1. On the Element Summary page, Element Overview hierarchy, select Input Values.
2. From the Actions menu, select Create Input Values.
3. For all deduction elements, enter these values:
Field Value
Name Name of the value, such as Period Deduction Amount

Display Sequence 1

Special Purpose Primary input value or Percentage

Unit of Measure Money

Create a Database Item Yes

4. For recurring deduction elements with a goal amount, name the value Goal Amount
5. Click Save.
6. Click Submit.
Set Up Element Eligibility

On the Element Summary page, update the newly dened element detail for eligibility.
1. From the Edit menu, select Update.

2. In the Element Overview hierarchy, select Element Eligibility.
3. From the Actions menu, select Create Element Eligibility.
4. In the Element Eligibility name eld, enter the element name with the sux as Open.
5. In the Eligibility Criteria section, select All payrolls eligible.
6. Save and submit the element.
Related Topics
142
Business Requirements
Some features, such as File ID and Position ID don't require any specic data set up or conguration.
Paid and Nonpaid Employee

The application extracts both employee categories in the same le. However, the required aributes have certain
limitations.
This table describes these employee categories
Employee Category Description
Paid Employee Congured with payroll relationship and element mapping. The extraction passes the element
entry values and payment details. Such details are used in third-party payroll system for
processing and making payment.

Nonpaid Employee The cloud HR application maintains nonpaid employees by assigning them to a payroll
relationship. However, the application doesn't maintain the Compensation, Statutory, and Bank
related details.

File ID
Each employee has a unique File ID for their employment record. The application stores this information in the
Assignment Number eld too. You can store the File ID into the person number. In this scenario, the application
automatically generates the Assignment Number and also restricts the eld as non-editable. Use the File ID to derive the
position ID.
Scenario 1
If you enter File ID in the Person Number eld, the application automatically adds Employee Type with Person Number
and generates the Assignment Number.
Scenario 2
When you enter File ID in the Assignment Number eld, don't begin the entry with alphabets. The application supports
multiple assignments
Position ID
The Position ID is a unique 9 character aribute. The combination of Company Code and File ID derives the Position ID.
Note: The Position ID is derived from File ID.
143
You can identify the File ID in two ways

• If Assignment Number doesn't start with alphabets, consider the File ID from the Assignment Number eld
• If the Assignment Number eld start with alphabets, consider the Person Number as File ID.
The rst 3 positions is Company Code and the next 6 positions is File ID.
• Position 1 to 3 => Company Code (Say 'T24')
• Position 4 to 9 => File ID (say 786, if the le ID is less than 6 digit, then pad with leading zeros)
• Position 10 => 'N' if the assignment status is Active- no payroll else blank.
The derived Position ID is T24000786N.
The application derives the Position ID from the Company Code, Assignment Number, and Assignment Status during
extraction. If Assignment Status = Active-No Payroll, the application doesn't either display or store the Position ID.
Element Mapping
The application maps elements that are based on the standard element template delivered for US localization. Consider
these points while you create elements:
• Add the additional input value to aach the goal limit and goal number to the deduction element.
• Enter the element name to extract to the third-party payroll supplier in the Reporting Name eld.
Element Eligibility and Input Values

Create and provide these input values for each deduction element while you dene a deduction element.
Input Value Description
Deduction value • Identify whether the element is deducting a at amount or percentage.
• Use this input value to track the amount of the deduction.
• For this input value, set the special purpose eld as Primary Input Value.
Third-Party Goal Limit • Dene values for each of the Goal Limit associated WFN deduction codes.
• This input value is optional for deduction element.
Third-Party Goal Number • Dene values for each of the Goal Number associated WFN deduction codes.
• This input value is optional for deduction element.
Termination and Rehire Requirements

When you terminate an employee, the application updates payroll records of the employee accordingly. These
scenarios explain the impact of a termination.
144
HR Records
• The status of the employee records remains Active on and before the actual termination date.
• The status of the employee records becomes Inactive from the next day of the termination date.
Payroll Records
The duration until which the payroll relationship remains open depends on the payroll relationship rule that the
respective country denes.
For countries that have the rule:
• "I", the payroll relationship ends on the next day after the actual termination date.
• "L", the payroll relationship remains active endlessly.
• "C", the payroll relationship becomes inactive from the next day after the ATD.
The application end dates the regular earnings on the ATD (=LSED). However, you can add severance pay related
element to an employee till the Final Close date. The application processes the employee in a payroll till their Final Close
date.
When terminating employees, choose the nal close date in such a way that the application can process employee's
severance pay a few days or months after their last working day.
Note: You can re-extract the updated termination details after the initial extraction to the third-party
application. However, you can't reverse the termination process as the integration supports only deleted
transactions for Elements and Bank accounts. Reversing a termination process might be considered in future
releases.
Rehire
If the hire date is within the current extract period, the application extracts the employee. In case of rehire, the
application considers the work relationship of that rehire process. If the hire date of this work relationship is within the
current extract period, the application includes the employee in the extract. The application retains person number of
the employee if they're rehired within the Legal Employer.
Note: You must enter the employee's prior employment nal close date before you rehire employees.
Transfer
In case of a transfer of an employee, the application terminates the current work relationship and creates a new work
relationship. In this case, the extraction le includes two records.
145
Leave Information
The Absence application records the leave information as a single record. But when the interface application extracts
the details the Absence application separates the leave information as a separate transaction.
Rate Type Change

The application supports Hourly and Salaried (monthly) Rate types.
• For Hourly basis, enter the scheduled hours with the rate 1 amount for hourly rate. Leave the Standard Hour
eld blank.
• For Salaried Rate type, enter the standard hours with the rate 1 amount for month frequency.
In case of any change in the rate type, change the respective standard or schedule hours automatically. Hence the
existing rate type has a delete record and a new record for the proposed change rate type in the extractions.
How You Split Personal Payment Methods

By default, you can enter bank account details for existing banks and branches on the Manage Personal Payment
Methods page. But you can't create any banks and branches details. Similarly payroll managers, payroll administrators,
and payroll coordinators can only enter account details for the employees they handle.
Note:
• To enable the create option for any of these roles, add the Bank and Branch Management duty role to the
relevant role.
• You can't edit bank and branch details on the Manage Personal Payment Methods page.
• Use the Set Up Bank, Branches, and Accounts task list to edit existing banks and branches.
These scenarios illustrate multiple ways to split up payment methods.
Use Fixed Amount Payments

Barbara Franklin wants to save 600 before the next holiday season and wants the money transferred electronically as
part of her regular payroll payment processing. She is paid semimonthly and can aord to put aside 100 each payroll
period.
At the time when Barbara wants the transfers to start, she adds an electronic funds transfer (EFT) payment method for
her savings account and sets the amount to 100 . Because Barbara's net payment amount is approximately 1,000 each
payroll period, the remaining amount of approximately 900 would be paid using her default payment method, which
transfers her payroll payment to her checking account. Before the holiday season, when Barbara decides to stop the
transfers to her savings account, she deletes the payment method.
146
Use Percentage Payments

Terry Smith has a college fund set up for his children and wants to contribute to it each payroll period. Because Terry
frequently receives bonuses and sales commissions, his net payment amount is always changing. So, he decides to add
a payment method that allocates four percent of his pay to the fund. By using a percentage rather than a xed amount,
Terry can contribute to the fund at the same rate that he earns.
147
148
Implementing Global Payroll Interface Payroll Interface Inbound Records
7 Payroll Interface Inbound Records
Overview
Use the HCM Data Loader to import processed payroll data and payslips from third-party payroll providers. Each import
record is associated with a master record that species a payroll name and payroll period. The Inbound table stores the
imported payroll information, while the document record stores payslips.
You can create your own reports using Oracle Fusion Transactional Business Intelligence (OTBI). Use the mentioned
Subject area and Fact data Data to create reports:
• Subject area: Payroll Interface Inbound Record - Real Time

• Fact Data: Payroll Interface Inbound Records and Payroll Interface Inbound Record Information
You can obtain these details from a typical data import:
• Absence entries of employees

• Employee specic messages
• Details of earnings and elements processed for employees
• Final payments made to employees
• Details of bank accounts to which payments are made
Extensible Flexelds
Oracle provides an extensible exeld called Payroll Interface Inbound Record EFF
(ORA_HRY_PI_INBD_RECORDS_INFO_EFF) to capture inbound payroll data from your third-party payroll processor.
These are the delivered contexts:
• Absence Information
• Message Information
• Payment Information
• Payroll Information
Predened segments are associated with these contexts. In addition to this extensible exeld, you can also use
extensible and user-dened lookups to congure your inbound payroll interface with the third-party payroll provider.
Use the Manage Payroll Interface Extensible Flexelds task to edit the Payroll Interface Inbound Record EFF exeld.
Contexts with predened segments capture specic processed payroll values.
Payroll Interface Inbound Record

After your third-party payroll provider processes a payroll, the application extracts the results and congures them into
a data le. Convert this data le to the HCM Data Loader required format.
This table shows the list of les to import your payroll data:
149
File Name Content
PayrollInterfaceInboundRecord. dat Includes processed payroll information for employees included in the payroll run

You must use this le name as the
HCM Data Loader recognizes only
this le name.

PayrollInterfaceInboundRecord. zip Compressed le that contains the data le

After you create the data le,
compress the le with the .zip le
extension. In this scenario, you can
create your own le name.

On the Manage Payroll Interface Inbound Records page, you can do these actions:
• Use one or more of these criteria to lter imported data:
◦ Payroll Name
◦ Batch Name
◦ Name
◦ Record Type
◦ Person Number
◦ Record Owner Type
• Select Payroll Data in the Record Type eld to view, add, edit, and delete these details:
◦ Payroll
◦ Payment
◦ Leave
◦ Messages received from third-party payroll providers
Payslip Files
Use the HCM Data Loader to import payslips as PDF les into your Oracle Fusion HCM application.
This table shows the list of les to import payslips:
File Name Content
DocumentsOfRecord. dat Data le listing employees for whom payslips are being provided.

You must use this le name. The PDF le names
HCM Data Loader utility recognizes
only this le name.

BlobFiles Folder that contains all the PDF payslip les.
150
File Name Content

You must use this folder name. The
HCM Data Loader utility recognizes
only this le name.

DocumentsOfRecord. zip Compressed le that contains both the data le and PDF payslip les.

In this scenario, you can create your
own le name.

The import process looks for the PDF les based on the information contained in the data le. After you complete the
import process, employees can view their payslips from the My Portrait work area.
On the Manage Payroll Interface Inbound Records page, select Payslip Data in the Record Type eld to view payslip
data.
Related Topics
• Import Payroll Data From Third-Party Payroll Providers
• Overview of HCM Data Loader
• How Data Is Imported and Loaded
Manage Inbound Records

Use the Manage Payroll Interface Inbound Records task in the Payroll work area to view, edit, and delete imported data.
Imported data includes information about payroll, payment, leave, and messages from third-party payroll providers.
You can also view the net payment and payslip dates. To view the payslips that you imported, select the Pay work area.
Click View Payslips.
View Inbound Records

1. On the Payroll work area, select Administration task.
2. On the Payroll Administration page, click the Tasks panel tab and select Manage Payroll Interface Inbound
Records.
3. In the Batch Name eld, select the required batch.
4. In the Record Type eld, select Payroll Data.
5. In the Record Owner Type eld, select Payroll Relationship.
6. Click Search.
7. In the Search Results section, select Update from Edit menu.
8. On the Manage Payroll Interface Inbound Records page, you can view, edit, and delete Payroll, Payment,
Absence, and Messages information.
9. Click Submit.
151
Processed Payroll Values

The Inbound payroll interface also supports processed payroll data from the payroll provider.
Enable the following contexts and segments to manage processed payroll information. This process helps to bring in
standardized data from Payroll provider that's used for further reporting and analysis.
Context Segment Description
Absence Information • Absence Name • Name of absence for the employee.

• Accrual Balance • Number of leaves in balance.
• Absence Unit • Number of absences taken.
• Absence Message
Congure Extensible Flexelds and Lookups

Congure extensible exelds for your inbound payroll interface to your third-party payroll processor.
Congure Payroll Interface Extensible Flexelds

Use the predened Payroll Interface Inbound Record EFF extensible exeld to import processed payroll data from your
third-party payroll provider. Use contexts with predened segments to capture specic payroll values.

◦ Task: Manage Extensible Flexelds for Payroll
2. On the Manage Extensible Flexelds page, search for and select Payroll Interface Inbound Record EFF
(ORA_HRY_PI_INBD_RECORDS_INFO_EFF).
3. Select Edit from the Actions menu.
4. Select the Inbound Record category.
5. Click Manage Contexts to search for any contexts that you want to review.
Oracle delivers these contexts and context sensitive segments with the Payroll Interface Inbound Record EFF
exeld.
Context Context Sensitive Segments
Absence Information Absence Name

Absence Balance

Absence Unit
152

Absence Unit of Measure

Absence Message

Message Information Message Type

Message ID

Message Text

Outbound File Received Date

Outbound File Name

Payment Information Bank Name

Branch Name

Branch Number

IBAN

Payment Type

Account Name

Account Number

Check Number

Amount

Currency

Payment Date

Payroll Information Payroll Run Type

Payroll Run Sequence

Element Classication

Element Name

Cost Center

Current Amount

Quarter-To-Date Amount

Year-To-Date Amount

Currency

General Ledger Credit Account

General Ledger Debit Account
153
Payslip Information Net Payment

Payslip View Date

6. Enter and search for the context name in the Display Name eld.
7. To edit Context Sensitive Segments, select Edit from the Actions menu.
8. To create a context, select Create from the Actions menu.
10. Click Done.
Note: If you add any segments or contexts, save and deploy the exeld on the main page.
Related Topics
• Overview of Extensible Flexelds
• Overview of Flexeld Deployment
154
Implementing Global Payroll Interface Data Validation and Data Deletion Reports for Payroll
Interface
8 Data Validation and Data Deletion Reports

for Payroll Interface
Generating Data Validation Report

Run the Data Validation Report for Payroll Interface either in a stand-alone mode or as a consolidated process before
you extract data from HCM cloud.
Use this report to validate a set of payroll relationships and its associated data. This report supports the object group or
single payroll as a parameter.
The Data Validation Report for Payroll Interface includes validations for both HR and payroll data.
Data Groups
The data groups that you select when adding validation rules to the report determines the level of validation.
Add validation rules to these data groups to report worker and payroll related data validation.
• Payroll Group
• Payroll Relationship Group
• Legal Employers
• Reporting Establishments
• Work Relationships
• Employment Terms
• Assignments
• Payroll Relationships
• Payroll Assignments
• Payroll Terms
Run the Data Validation Report for Payroll Interface

Use the Checklist work area to run the Data Validation Report for Payroll Interface report.
1. Click the Tasks pane and select the Submit a Process or Report task.
2. Select a US Legislative Data Group.
3. Search for and select the Run Data Validation Report for Payroll Interface process.
4. Click Next.
5. Enter the parameters as shown in the table.
155
Interface
Field Value to Enter
Payroll Flow An identier for the process that's run. Choose any format to describe the payroll ow.

Object Group A predened object group for which the report is run.

The process retrieves a set of payrolls or payroll relationships that belong to the object group
and performs the dened validation for each relationship.

Payroll Object group, Payroll, or Both.

Eective Date An eective date for process.

Process Conguration Group The Payroll Statutory Unit for which the report is run.

6.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. Click OK and View Checklist.
11.On the Payroll Flow page, Task Details tab you should see a green check mark in the Run Data Validation
Report for Payroll Interface row, Status column. If not, click the Refresh icon on the toolbar intermiently
until you do.
12. Click the Go to Task icon.
13. On the Run Data Validation Report for Payroll Interface page, click Done to submit.
Related Topics
• Add Rules to Data Validation Reports
Generating Deleted Data Report

Use the Deleted Data report to report data that have been deleted from the HCM Cloud during the extraction period.
You can use this report as a supplement to the ADP Global Payroll Interface output xml le to account for data changes
for an extraction period.
This report is a part of the Standard ADP Global Payroll Interface consolidated ow and is automatically submied when
you submit the consolidated ow. You can run the report independently too.
Before You Begin

The Deleted Data Report is based on the Audit functionality. Enable audit on all objects that must be tracked for
deletions.
156
Interface
Do these steps to enable audit.

◦ Functional Area: Application Extensions
◦ Task: Manage Audit Policies
2. On the Manage Audit Policies page, click Congure Business Object Aributes .
3. On the Congure Business Object Aributes page, select HCM Payroll.
4. Select Personal Payment Method. The aributes available for auditing are displayed on the right hand side of
the page under Audited Aributes section.
5. In the Audited Aributes section, click Create.
6. In the Select and Add Audit Aributes dialog box, search for the aributes that you want to audit and click OK.
Generate Deleted Data Report

Use the Submit a Process or Report task in the Payroll Checklist work area to complete the steps.
1. Select the appropriate Legislative Data Group.
2. In the Process or Report section, search for and select Run Deleted Data Report.
3. Click Next.
4. On the Parameters page, enter values for these parameters.
Field What it Means
Flow Name Meaningful name of the ow.

Process Start Date Start date of the extraction window. Typically, this should be the same as the ADP Global
Payroll Interface extraction window.

Process End Date End date of the extraction window. Typically, this date should be the same as the ADP Global
Payroll Interface extraction window.

Object Group Identies the payroll relationships to consider and should be same as the object group used
in the ADP Global Payroll Interface.

5. Click Submit.
6. Monitor the process to completion and view the report output.
Related Topics
157
Interface
158
Oracle Global Human Resources Cloud Glossary
Glossary
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.
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.
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.
payment method
Indicates the method of payment, such as check, cash, or credit.
payroll relationship
Defines an association between a person and a payroll statutory unit based on payroll calculation and reporting
requirements.
payroll relationship type

A predefined value that controls and groups person records into payroll relationships. If a person has more than one
payroll relationship type in the same PSU, such as employee and contingent worker, multiple payroll relationships exist
for that person.
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.
personal payment method

Method of payment to a person for a particular payroll. When an administrator assigns a person to a new payroll,
payments are made using the default organization payment method for the new payroll until a personal payment
method exists.
recurring element entry

An entry that processes regularly at a predefined frequency. The entry exists from the time you create it until you delete
it or the employee's element eligibility ceases.
159
Oracle Global Human Resources Cloud Glossary
system person type

A fixed name that the application uses to identify a group of people.
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.
160

Implementing Global Payroll Interface

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Implementing Global Payroll Interface

Загружено:

Авторское право:

Доступные форматы

Oracle Global Human

Implementing Global Payroll

Author: Ipsita Mohanty

2 Payroll Interface Extracts 9

3 Set up Payroll Interface 15

4 Global Payroll Interface Extract 31

5 Payroll Interface for ADP Global Payroll 47

6 Payroll Interface for ADP Workforce Now 133

7 Payroll Interface Inbound Records 149

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

Calculation Engine Fusion HR XML

HCM Extract Transform Customer Specific

DOR Documents OTBI Reports HDL

Extract Data from HCM

Global Payroll Interface

US ADP PayForce Third-Party

US ADP PayForce Third-Party Ad-Hoc

Payroll Interface for ADP Global

Payroll Interface for ADP Workforce

Import Third-Party Payroll Processed Data and Payslips

Implement Global Payroll Interface

Workforce Deployment Oering

Functional Area Use To

Organization Structures Create business units to associate with other objects.

HCM Data Extract Congure Process Conguration Group prole options.

Elements and Formula Dene payroll elements.

Compensation Management Oering

Payroll Employment Model

Comparing the HR and Payroll Employment Models

Payroll Statutory Unit Sun Power

Legal Manufacturing Installation

David Ellis David Ellis

Assignment Assignment Assignment Assignment

Payroll Relationship Rules

Continuous Period of Service Rule

Create Payroll Relationship Records and Mapping Rules

This table shows the predened payroll relationship type.

Payroll Relationship Type Description

System Person Type Payroll Relationship Type

Contingent Worker Element Entry Only

Nonworker Paid Standard

Nonworker Unpaid Element Entry Only

Retiree Element Entry Only

• Time Card Required Option

2 Payroll Interface Extracts

How Extract Components Work Together

Department Department Other

Department Department Department

Extract Payroll-Related Data

User Entities in HCM Extracts

User Entity Name and Code Description

Extract Current and Future Retrieves current and future assignments.

Reset Context (PER_ EXT_RESET_UE)

User Entity Name and Code Description

Options to Extract Payroll-Related Data

Method User Entity Returns

Payroll Run Results

Record Type Context

Extracting Calculation Card Values