docs.oracle.com€¦ · Oracle Global Human Resources Cloud Implementing Global Payroll Interface Contents Preface i 1Payroll Interface 1 Overview

Oracle Global Human ResourcesCloudImplementing Global Payroll Interface

19C

Oracle Global Human Resources CloudImplementing Global Payroll Interface

19CPart Number F18843-01Copyright © 2011, 2019, Oracle and/or its affiliates. All rights reserved.

Author: Ravikumar Iyer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected byintellectual property laws. Except as expressly permitted 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, ordecompilation 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 find any errors, please report them tous 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 thefollowing 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 Regulationand agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operatingsystem, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictionsapplicable 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 inany inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerousapplications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. OracleCorporation and its affiliates 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 affiliates. 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 orregistered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks ofAdvanced 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. OracleCorporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, andservices unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for anyloss, 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 agreementbetween you and Oracle.

The business names used in this documentation are fictitious, and are not intended to identify any real companies currently or previously in existence.


Contents

Preface i

1 Payroll Interface 1Overview ................................................................................................................................................................... 1

Implementing Global Payroll Interface: Overview ....................................................................................................... 2

Payroll Employment Model: Explained ....................................................................................................................... 3

Payroll Relationship Rules: Explained ........................................................................................................................ 5

Payroll Relationships: Explained ................................................................................................................................ 5

2 Payroll Interface Extracts 7How Extract Components Work Together ................................................................................................................ 7

Extracting Payroll-Related Data ................................................................................................................................. 8

3 Set up Payroll Interface 13Setting up License Type for Country or Territory: Procedure ................................................................................... 13

Defining Enterprise Structures ................................................................................................................................. 13

Loading Geographies .............................................................................................................................................. 14

Legislative Data Groups .......................................................................................................................................... 15

Payroll Legislative Data ........................................................................................................................................... 15

Creating a PSU and Associating it with a LDG ....................................................................................................... 17

Creating Payroll Definitions ...................................................................................................................................... 18

Creating a Payment Method ................................................................................................................................... 19

Managing Configuration Groups .............................................................................................................................. 20

Creating Payroll Elements ....................................................................................................................................... 21

Associating Employees with Payroll ........................................................................................................................ 24

Managing Payroll and Salary Definitions .................................................................................................................. 25

Managing Salary for Payroll Interface ...................................................................................................................... 25

Extracting Terminated Employees: Critical Choices ................................................................................................. 27


4 Global Payroll Interface Extract 29Overview ................................................................................................................................................................. 29

Payroll Interface Extract Flow Parameters ............................................................................................................... 30

Effective Dates ........................................................................................................................................................ 31

Setting up Object Groups ....................................................................................................................................... 32

Action Indicators for Payroll Interface ...................................................................................................................... 33

Creating Rate Definitions ......................................................................................................................................... 37

Transactional and Operational Recommendations ................................................................................................... 38

Copy Delivered Extract Definitions .......................................................................................................................... 39

Use Extensible Fields to Include Additional Attributes .............................................................................................. 39

Submit the Global Payroll Interface Process ........................................................................................................... 40

Global Payroll Interface Extract FAQs ...................................................................................................................... 41

5 Payroll Interface for ADP Global Payroll 43Overview ................................................................................................................................................................. 43

Salary History Information for ADP Global Payroll Interface: Overview ..................................................................... 44

Additional Payroll Interface Data Elements .............................................................................................................. 45

Running Global Payroll Interface Processes ............................................................................................................ 47

Configuring Prior Values .......................................................................................................................................... 48

Setting up Additional Elements ............................................................................................................................... 49

Managing Payroll Interface Data Values for ADP Global Payroll: Procedure ............................................................. 51

Override the Cost Center Using Configurable Cost Center Override Attribute .......................................................... 52

Configuring Dynamic File Names for global interface for ADP Global Payroll : Procedure ......................................... 53

Transactional Recommendations ............................................................................................................................. 56

Operational Recommendations ............................................................................................................................... 57

Increment Process Dates Automatically .................................................................................................................. 58

Payroll Interface for US ADP Payforce .................................................................................................................... 59

6 Payroll Interface for ADP Workforce Now 121ADP Workforce: Overview ..................................................................................................................................... 121

Delivered Contexts and Segments ........................................................................................................................ 121

Delivered Lookups ................................................................................................................................................ 123

Creating Payroll Elements ..................................................................................................................................... 125

Business Requirements for ADP-WFN .................................................................................................................. 129

Termination and Rehire Requirements for ADP WFN ............................................................................................ 131

How You Split Personal Payment Methods ........................................................................................................... 132


7 Payroll Interface Inbound Records 135Overview ............................................................................................................................................................... 135

Managing Inbound Records .................................................................................................................................. 137

Processed Payroll Values ...................................................................................................................................... 137

Configuring Extensible Flexfields and Lookups ...................................................................................................... 138

8 Data Validation and Data Deletion Reports for Payroll Interface 141Generating Data Validation Report ........................................................................................................................ 141

Generating Deleted Data Report ........................................................................................................................... 142



Preface

i

PrefaceThis preface introduces information sources that can help you use the application.

Using Oracle Applications

Using Applications HelpUse help icons to access help in the application. If you don't see any help icons on your page, click your user imageor name in the global header and select Show Help Icons. Not all pages have help icons. You can also access OracleApplications Help.

Watch: This video tutorial shows you how to find help and use help features.

You can also read Using Applications Help.

Additional Resources

• Community: Use Oracle Cloud Customer Connect to get information from experts at Oracle, the partnercommunity, and other users.

• Guides and Videos: Go to the Oracle Help Center to find guides and videos.

• Training: Take courses on Oracle Cloud from Oracle University.

ConventionsThe 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 file, folder, and directory names, code examples, commands, and URLs.

> Greater than symbol separates elements in a navigation path.

Documentation AccessibilityFor 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.

https://fusionhelp.oracle.com/

https://fusionhelp.oracle.com/

https://apex.oracle.com/pls/apex/f?p=44785:265:0::::P265_CONTENT_ID:10552

https://apex.oracle.com/pls/apex/f?p=44785:265:0::::P265_CONTENT_ID:10552

http://www.oracle.com/pls/topic/lookup?ctx=cloud&id=OACPR2531440

https://appsconnect.custhelp.com/

http://docs.oracle.com/

http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=906

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc


Preface

ii

Contacting Oracle

Access to Oracle SupportOracle customers that have purchased support have access to electronic support through My Oracle Support. Forinformation, visit My Oracle Support or visit Accessible Oracle Support if you are hearing impaired.

Comments and SuggestionsPlease give us feedback about Oracle Applications Help and guides! You can send an e-mail to:[email protected].

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

mailto:[email protected]


Chapter 1Payroll Interface

1

1 Payroll Interface

OverviewOracle Global Payroll Interface supports features to send personal payroll information to third-party payroll providers andto import processed payroll data into Global HR. You can copy and modify predefined extract definitions to meet therequirements of your third-party payroll provider.

In a legislative data group that uses the Payroll Interface, you can do the following:

• Extract employment, salary, and compensation details from HCM to send to a third-party payroll provider.

• Import payroll processed data, payslips, and messages to flexfields. This processed payroll data is available withinthe application for further reporting and analysis.

This figure shows the inbound and outbound interfaces that enable applications to interact with third-party payroll serviceproviders.

Customer Specific Output File

Result File

Payslip

Tax Card

Elements

Balances

DOR Documents OTBI Reports

HCM Extract

Fusion HR XML

Export

BI Publisher Reporting

Global Payroll Interface

TemplateSolution

Predefined

HDL

Backfeed

Transform

Calculation Engine

Extract Data from HCMUse these predefined extract definitions.

Note: Create a copy of the delivered extract definition for additional configurations.



2

Extract Description

Global Payroll Interface Extracts information required by any global payroll provider, such as the name, address, salary, and

deductions details of your employees. For more information, see Section Global Payroll InterfaceExtract.

US ADP PayForce Third-Party PeriodicExtract

Extracts payroll data to transform it into HR-XML format for for ADP PayForce and ADP Connectionfor PayForce users. For more information, see Section US ADP PayForce Third-Party PeriodicExtract Definition.

US ADP PayForce Third-Party Ad-HocExtract

Extracts payroll data to transform it into HR-XML format for for ADP PayForce and ADP Connectionfor PayForce users. For more information, see Section US ADP PayForce Third-Party Ad-HocExtract Definition.

Payroll Interface for ADP Global Payroll Extracts information, such as the salary and earnings details of employees in the format required by

ADP Global Payroll. For more information, see Section Payroll Interface for ADP Global Payroll.

Import Third-Party Payroll Processed Data and Pay slipsUse HCM Data Loader to import the following 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 thepractices of your payroll provider.

• Notification messages, such as confirmation of number of transactions received or processed, or warninginformation.

• Pay slips, for example in PDF format.

The application associates each imported record with a master record that specifies a payroll name and payroll period. Itstores the imported data in inbound tables and pay slips as document of records.

Related Topics

• Extract Components

• Extracting Payroll-Related Data: Critical Choices

• Overview of HCM Data Loader

• Payroll Interface Inbound Records: Explained

• Implementing Payroll Interface: Procedure

Implementing Global Payroll Interface: OverviewUse the Workforce Deployment and Compensation Management offerings to configure and manage Payroll Interface.Use predefined payroll interface extract definitions to send payroll-related employee information to a third-party payrollprovider. The setup steps required for payroll interface vary depending on your business requirements.

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=3F4AB5B1B8751345E05362C3F00AE24B

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=BE75B61810E2354EE040D30A6881734A



3

Workforce Deployment OfferingThe following table specifies the functional areas of the Workforce Deployment offering that you use to set up payrollinterface. For the full list of functional areas and features in this offering, use the Associated Features report.

Functional Area Description

Payroll

Create payroll definitions, payment methods, and LDGs, define an element, manage salary, set upsalary basis and object groups. For more information, refer to the Implementing Global Payroll guide.

Enterprise Profile

Load geographies to create the geography structure for each country. For more information, 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, refer to the Implementing Global Human Resources guide.

Organization Structures

Create business units to associate with other objects. For more information, refer to the Implementing Global Human Resources guide.

HCM Data Extract

Configure Process Configuration Group profile options. For more information, refer to the Implementing Global Human Resources guide.

Elements and Formula

Define payroll elements. For more information, refer to the Implementing Global Payroll guide.

Compensation Management OfferingUse the Workforce Compensation functional area to configure salary basis and to associate it base pay element.

Related Topics

• Plan Your Implementation

Payroll Employment Model: ExplainedIn the payroll employment model, each person has a payroll relationship to a payroll statutory unit (PSU), and one or moreassignments to a payroll and other employment structures. Some element entries, typically deductions, are held at the payrollrelationship level, and others at lower employment levels.

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=4C96E4A198901E46E05362C3F00AB2A8



4

Comparing the HR and Payroll Employment ModelsThe following figure contrasts the HR employment model and the payroll employment model in an example where two legalemployers belong to one PSU. In this example, David Ellis has two assignments. The resulting structure creates two workrelationships in the HR model and one payroll relationship in the payroll model.

Sun PowerPayroll Statutory Unit

Manufacturing InstallationLegal Employers

David Ellis David Ellis

Work Relationship Manufacturing

Work Relationship Installation

Payroll Relationship Payroll Statutory Unit

Sun Power

Assignment Project Manager

Assignment Trainer

Assignment Project Manager

Assignment Trainer

Related Topics• Payroll Employment Hierarchy Profile Option: Critical Choices

• Employment Level for Elements: Critical Choices

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=BB3C51943C4578C5E040D30A688173A1

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=0683AA73D5CD5582E05362C3F00A8167



5

• How do I diagnose payroll employment model setup issues

Payroll Relationship Rules: ExplainedThe payroll relationship rule determines what happens when you terminate the last active employment assignment recordfor a payroll relationship. The rule also determines whether the application creates a payroll relationship when you add a newassignment record for an employee. This topic describes the following predefined rules that localizations can use.

Lifetime RuleWhen a work assignment is terminated, the associated payroll relationship continues to remain active. When you create anassignment, 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 attached to the existing active payroll relationship. If not, a new payroll relationship isgenerated.

Continuous Period of Service RuleWhen 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 samePSU. If a payroll relationship exists, date validation occurs to determine whether to use the existing payroll relationship or tocreate a new one. The application compares the start date of the new assignment to the last standard earnings date of theexisting payroll relationship. If the start date is before the last standard earnings date, the application uses the existing payrollrelationship, otherwise, it creates a new one.

Independent RuleWhen a work assignment is terminated, the associated payroll relationship becomes inactive and is terminated. When youcreate an assignment, a new payroll relationship is created. Each payroll relationship is associated with one work assignment.

Related Topics

• Terminations: How They Affect Payroll Processing

Payroll Relationships: ExplainedA payroll relationship represents the association between a person and a payroll statutory unit (PSU), which is the legal entityresponsible for employee payment. Payroll relationships group a person's employment assignment records based on thepayroll statutory calculation and reporting requirements. Payroll relationships facilitate the capture and extraction of HR andpayroll-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 first 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 canaggregate balances for multiple assignment records. Balances don't span payroll relationships.

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=1B6BEB6AB6303036E05362C3F00A7116

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=C1D3F552AAAA5C5CE040D30A68813939



6

Creating Payroll Relationship Records and Mapping RulesFor certain processes, such as the rehire process, to automatically create a payroll relationship record, the mapping betweenthe system person type and the payroll relationship type must exist. You must use the payroll relationship types predefined inthe application. You cannot create your own.

The table below shows the predefined 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 themand are excluded from payroll processing.

Relationship mapping rules, which map system person types to payroll relationship types, can vary by country or territory. Themapping rules are predefined for each legislation.

The table below shows the mapping between system person types and payroll relationship types applicable for Canadawhere 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 cannot end while there are active employment assignments. When all employment assignments areended for a payroll relationship, it could either remain active or become end dated. It depends on the legislation and thepayroll 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 payrollrelationship and PSU, for the rehire.

Related Topics

• Element Duration Dates in Payroll : Explained

• Setting End Dates for Terminations: Examples

• Time Card Required Option: Critical Choices

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=C1D3F552AAAB5C5CE040D30A68813939

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=C1D3F552AAA95C5CE040D30A68813939

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=0F79CCB1F9EB5C21E05362C3F00A0D26


Chapter 2Payroll Interface Extracts

7

2 Payroll Interface Extracts

How Extract Components Work TogetherThe HCM Extracts feature is a flexible tool for generating data files and reports. This topic covers how you can use the extractcomponents to define what information you want the application to extract and report on. It also explains how the applicationdisplays, formats, and delivers the information.

Extract DefinitionsAn extract definition refers to the complete setup of an extract, that consists of extract data groups, criteria, records,attributes, advanced conditions and output delivery options. An extract definition 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 attributes depending on how many individual fields 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 FusionHCM 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 benefits data transferred to third-party service providers, HR andtalent data exchange between Oracle Fusion and legacy applications, for example in a coexistence scenario.

Data GroupsExtract data groups represent a business area or logical entity, for example person, assignment, or benefits. The applicationuses this information to retrieve the database item groups. You define one data group as the primary or root data group andthis 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 define a set of filtering conditions the application must perform on an extract data group using the extract data groupcriteria. You specify the criteria conditions using an expression or fast formula.

Extract RecordsExtract records represent a grouping of related data or a physical collection of all fields 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



8

extract record is a collection of attributes which you can organize in a required sequence. For example, if a data group has 3records, then you can specify the sequence in which the application processes the records. You can also select the next datagroup to identify which data group the application processes next.

AttributesAttributes are the individual fields inside the extract record. An attribute is the lowest attribute level of a HCM extract andrepresents a piece of information, for example, person first name, person last name or person date of birth.

This figure demonstrates the hierarchy of information within a data group definition.

Department(Data Group)

Department Information

(Record)

Department Other Information

(Record)

Department ID

(Attribute)

Department Name

(Attribute)

Department Location (Attribute)

Department Start Date(Attribute)

Extract Definition

Related Topics

• HCM Extract Types

• Define Extracts

• Overview of Generating Flexfield Database Items

• How Extracts are Validated

Extracting Payroll-Related Data

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=F234A211C22FE101E040D30A6881794E

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=C11A5F07B0B668E7E040D30A688110C8

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=E01816674B301ACBE040D30A68815636

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=3213F3656E7E249FE05362C3F00A23A0



9

User Entities in HCM ExtractsA user entity is a logical entity associated with a data group defined using HCM extracts. This topic describes the frequentlyused user entities and the type of data you can extract by using those user entities. You select user entities in the applicationwhen you define a data group.

The following table lists the most frequently used user entities.

User Entity Name and Code Description

Person (PER_ EXT_ SEC_ PERSON_UE)

Retrieves all persons across the enterprise and all person related attributes.

Worker Payroll (PER_ EXT_ PAY_EMPLOYEES_UE)

Retrieves all workers and their payrolls across the enterprise, all person, worker, payroll relatedattributes, and element entry data.

Extract Assignment Basic History(PER_ EXT_ ASSIGNMENT_ BASIC_HISTORY_UE)

Retrieves assignment history as on the assignment effective start date.

Extract Assignment Basic Information(PER_ EXT_ SEC_ ASSIGNMENT_BASIC_UE)

Retrieves assignment data as on the effective date.

Assignments Range (PER_ EXT_ SEC_ASSIGNMENT_ RANGE_UE)

Retrieves assignment history as on the effective date.

Extract Current and Future Persons(PER_ EXT_ SEC_ PERSON_ NOW_FUTURE_UE)

Retrieves current and future person details. Specify advanced filter criteria to restrict person types.

Extract Current and Future Assignments(PER_ EXT_ SEC_ ASSIGNMENT_NOW_ FUTURE_UE)

Retrieves current and future assignments.

Reset Context (PER_ EXT_RESET_UE) Use the Reset Context user entity in two ways:

1. Reset the effective date contexts set dynamically by a parent data group using a runtimeinput parameter for the effective date. For example, the Extract Assignment Basic Historyuser entity sets the assignment effective start date as effective date first and then retrievesthe data, unlike other user entities which use the effective date only. If you want to use theExtract Assignment Basic History user entity to include the historical data but also want tochange the effective date, then include the Reset Context user entity to reset this date usinginput parameters.

2. Set up the Reset Context user entity as the root user entity to be a container or header. Forexample, the following work structure elements: locations, positions, and legal employers arenot related to each other. If you want to extract all of them in one single extract, then you canadd them as child elements to the Reset Context user entity used as the root in the extractdefinition. Adding this user entity as the root to these elements enables you to retrieve thisdata 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.



10

Related Topics• Example of Generating Flexfield Database Items

• Best Practices for Viewing User Entity Details

Extracting Payroll-Related DataThe payroll interface supports different methods for defining extracts that enable you to extract payroll-related data.

The following 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 payrollrelationship.

Payroll Run Result Values

PAY_ EXTRACT_ RUN_ RESULT_VALUES_UE

All run results for a payroll relationship action.Includes calculation card information ifconfigured.

Balance Values

Base name of the database item groupfor the balance (direct) or balance group(indirect)

All balance values for the specified balanceor balance group for a payroll relationshipaction.

Element EntriesTo extract element entry values, include the ELEMENT ENTRIES user entity in the payroll interface extract. This user entityis available for all element classifications and returns all element entry values for a given payroll relationship. Use extract datagroup criteria to further filter the records.

To retrieve element entry values, set the following context in the extract definition:

• EFFECTIVE_DATE

• PAYROLL_RELATIONSHIP_ID

• DATE_EARNED

Payroll Run ResultsTo extract values from the results of processes, include the PAY_EXTRACT_RUN_RESULT_VALUES_UE user entity in yourextract definition. This user entity is available only for element classifications used by the Calculate Gross Earnings process,such as standard and supplemental earnings. It returns all the run results for a payroll relationship action.

If you use the Calculate Gross Earnings process and have defined regular or supplemental earnings elements, set thePAY_REL_ACTION_ID context in the extract definition. 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 deductioninformation for child support payments.

BalancesExtract balance values directly by using the database item group name generated for the balance or indirectly by using abalance group.

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=E0A3618E7911CC6FE040D30A68811FAB

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=OAPFF1081776



11

Note: Balances are created and maintained as result of processed element entries. Balance values are onlyavailable when you process element entries in a payroll run or use the Calculate Gross Earnings process.

To use balance groups, include one of the following record types and context in your extract definition.

Record Type Context

Balance Group

Ensure that all contexts are available in the current data group.

Balance Group with AutomatedResolution of References

Ensure that PAYROLL_ REL_ACTION_ID is set in the current or parent data group so that context isderived.

Extracting Calculation Card ValuesYou can add CIR data groups in your copied extract.

1. Navigate to the Data Exchange work area and select Manage Extract Definitions.2. Search for and select the copied extract.3. Click Switch Layout.4. Change the Effective 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 Definition

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.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



12

Field Value

Type

Hierarchy Traverse Only

14. Click Save and Close.15. Validate the extract.


Chapter 3Set up Payroll Interface

13

3 Set up Payroll Interface

Setting up License Type for Country or Territory: ProcedureUse the Manage Feature by Country or Territory task to set up Payroll Interface as the Selected Extension.

Complete the following steps:

1. Sign in as administrator.2. From the Navigator menu, select Setup and Maintenance.3. Search for and select Manage Features by Country or Territory to open the Manage Features by Country or

Territory page.4. For the country for which you are performing the implementation, in the column Selected Extension, select Payroll

Interface.5. Click Save.

Defining Enterprise StructuresYou can model the enterprise to meet legal and management objectives. Include the enterprise structures that are required tosupport payroll relationships for your workers. Use the Manage Enterprise HCM Information task to configure implementationspecific details at the enterprise level.

To confirm your enterprise structures setup, perform these actions.

Verify predefined geographies

Define legal jurisdiction

Create Legislative Data Group

Associate each PSU with LDG

Create Tax Reporting Units

Create Business Units



14

In the Setup and Maintenance work area:

1. Go to the following task to verify the predefined geographies and to load any additional local geographies:

◦ Offering: Workforce Deployment

◦ Functional Area: Enterprise Profile

◦ Task: Manage Geographies

2. Go to the Define Legal Jurisdictions and Authorities task list to create the following:

◦ A legal jurisdiction if not already created or predefined 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 Offering and Functional Area to go to the Define Legal Jurisdictions and Authorities tasklist.


◦ Functional Area: Legal Structures

3. Go to the Manage Enterprise HCM Information task to create a legislative data group (LDG) for each country ofoperation 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 Offering 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

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=8E7E6AEB45E50DB3E040D30A688137C4

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=13D98109B8975768E05362C3F00A8AE1



15

Loading GeographiesLoad geographies to create the structure for each country. In turn, a geography structure defines the geography types thatare part of the country structure. Also, it describes how the geography types are hierarchically related within the countrystructure. For example, you can create geography types called State, City, and Postal Code. Use the Load Geographies forUS 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


1. In the Setup and Maintenance work area, go to the following:


◦ 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 LoadGeography Information job.

3. In the Data Source field, ensure that you have selected Vertex.4. Click Submit and monitor the process to completion.

Related Topics

• Geography Hierarchy


Legislative Data GroupsLegislative data groups are a means of partitioning payroll and related data. At least one legislative data group is required foreach 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 flexfield 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 are within one country.

• Can contain many legal entities that act as payroll statutory units.

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=9C802E62DF0EEDC2E040D30A6881601C




16

Payroll Legislative DataUse the Configure Legislations for Human Resources task in the Setup and Maintenance work area to create and edit payrollrules for countries or territories not initially provided by Oracle.

Objects you configure include:

• Legislative rules

• Element classifications

• Valid payment types

• Component groups

• Balance dimensions

• Legislative data groups

Legislative RulesLegislative 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 priordata, such as all year-to-date balances. Yet for other countries, a rehire creates a new payroll relationship record with noaccess to prior data. The statutory rules for your country or territory would determine the selections you make, such as thestarting month of the tax year.

The legislative rules you can configure include mappings between system person types and payroll relationship types. Thismapping controls which person types can be included in payroll calculation processing, such as the Calculate Gross Earningsprocess.

Note: You can't undo payroll relationship type mapping. If you select an element entries only option for a persontype and then at a later date decide to use the Calculate Gross Earnings process, the process won't generateresults for that person type. Consider using a standard option to provide more flexibility.

Element ClassificationsElement classifications are collections of related elements. You select the primary classifications you want to include for yourelements. You can provide new display names for element classifications to match the terminology that's most appropriatefor the country or territory.

Valid Payment TypesPayment types are the means by which you issue payments to workers. The predefined payment types are Check Cash,EFT (electronic funds transfer), and International Transfer. You can provide new display names for payment types to matchterminology that's most appropriate for the country or territory.

Component GroupsComponent groups are logical sets of payroll components, which are the rates and rules that determine calculated values forsome earnings and deduction elements. You can provide new display names for the component groups you want to supportto match terminology that's most appropriate for the country or territory.



17

The Configure Legislations for Human Resources task creates a calculation card definition and payroll components foreach component group you enable. When you create elements in certain classifications and categories, the elementtemplate 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 elementtemplate then associates these components with the statutory elements you create. Ensure that you associate thesecomponents 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 countryextension on the Manage Features by Country or Territory page to Payroll Interface for this country or territory, hiring workersautomatically creates a statutory deduction calculation card for them. Ensure that you create eligibility records for yourstatutory deduction elements before hiring any workers.

Balance DimensionsBalance dimensions identify the specific 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 thebalance dimensions you want to support to match terminology that's appropriate for the country or territory.

The Configure Legislations for Human Resources task creates some predefined balances that the application uses withinthe statement of earnings, such as Gross Earnings and Net Pay. Additionally, the Net Payment balance is required to set uporganization payment methods.

Legislative Data GroupsUse the Manage Legislative Data Groups task in the Setup and Maintenance work area to define at least one legislative datagroup for each country or territory where your enterprise operates.

Creating a PSU and Associating it with a LDGUse the Manage Legal Entity task to create a Payroll Statutory Unit and associate it with a LDG.


1. In the setup and maintenance work area, go to the following:


◦ Functional Area: Payroll

◦ Task: Manage Legal Entity

2. On the Create Legal Entity page, Name field, enter InFusion USA West.3. In the Legal Entity Identifier field, enter US0033.4. Optionally, enter Start Date. When the start date is blank the legal entity is effective 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 field, search for and select a legal address. The legal address must have been entered

previously using the Manage Legal Address task.10. In the EIN or TIN field, enter either the EIN or TIN.11. In the Legal Reporting Unit Registration Number field, enter the registration number.



18

12. Click Save and Close.

Related Topics• Update Existing Setup Data

Creating Payroll DefinitionsPayroll definitions indicate the payment frequency and processing schedule. Use payroll definitions to group employees withsimilar pay characteristics. You can associate employees with payroll through payroll relationships.

To pay employees, define one payroll for each payment frequency, which the enterprise can use to pay its employees. Youcan use three pay frequencies, namely Monthly, Bi-weekly, and Weekly to process payments for the different categories ofyour employees.

For specifying payroll details when creating payroll definitions, use the following definitions:

• Effective Start Date

• First Period End Date

• Number of Years

Effective Start DateThe effective start date is the first date when the payroll definition is available for employee data. The start date must be on orbefore the earliest date of any historical data that you want to load.

For example, for a payroll starting on 1/1/2013 with five years of historical payroll data to load, set the start date of the payrolldefinition to 1/1/2008.

The effective start date does not affect the generated calendar of payroll periods. The start date for the first payroll period isbased on the first period end date.

First Period End DateThe first period end date is the end date of the first payroll period that the application generates for a payroll definition. It isbased on the date of implementation, tax year, benefits enrollments, or a particular payment cycle.

For example, if your weekly payroll work week is Saturday through Friday and your first payment date is on 1/6/12, use12/30/11 as the first period end date.

Number of YearsThe number of years represents how many years of time periods to generate starting from the beginning of the first payrollperiod, which is determined by the first period end date.

After you save a payroll definition, you can only increase, but cannot decrease this parameter. This is because the applicationwould have already generated a calendar of time periods.




19

To create payroll definitions, 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 field, enter a name.4. In the Legislative Data Group field, 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 Definitions task to open the Manage Payroll Definitions page.8. In the Search Results section, click Create from the Actions menu.9. In the Legislative Data Group field, 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.13. Repeat the above steps to create other payroll definitions.

Related Topics• Creating Payroll Definitions: Worked Example


Creating a Payment MethodPayment methods indicate the method of payment, such as check, cash, or credit. They associate a source bank accountwith each such payment types. Do not specify a run type when creating a personal payment method because it does nothold any significance in a payroll interface scenario.

To create a payment method and associate it to a payment source, perform the following steps:




◦ Task: Manage Organization Payment Methods

2. On the Manage Organization Payment Methods page, click Create to create a new payment method under the USlegislative data group.

3. In the Payment Type field, 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 field in order, as shown in the table:

Field Value

Name

Payroll EFT Source US

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=B48ED9A7B38931B4E040D30A688101BC




20

Field Value

Bank Account Name

Bank A

Bank Reference

123456789

Company Reference

456789012

7. Submit the changes.


Managing Configuration GroupsPayroll process configuration groups provide sets of processing parameters related to logging and performance.

Use the Manage Default Process Configuration Group Profile Option Values task to select the default group value forthe Process Configuration Group profile option.

• Offering: Workforce Deployment

• Functional Area: HCM Data Extract

In the Setup and Maintenance page, use the Manage Payroll Process Configuration task to review the default settings inthe default configuration group. For example, you might change the values for chunk size or number of threads to optimizeperformance when calculating gross earnings.


• Functional Area: Payroll

Managing Personal Payroll InformationA payroll manager performs the following steps to optionally upload personal payroll information, such as initial balance valuesor employee bank details.

1. 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 theManage Personal Payment Methods task in the Payment Distribution work area (for individual employees) to migratebank data.

Related Topics• Setting Up Payment Sources in Organization Payment Methods: Worked Example



http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=A0BA2D9D56E85CF9E040D30A68810C45




21

Creating Payroll ElementsThis example shows how to define elements for a US legislative data group where the country extension is set to PayrollInterface.

The following table summarizes key decisions for each element that you define and provides the selections for this example.

Decision to Consider In This Example

What is the primary classification? One of these choices:

• Standard Earnings• Supplemental Earnings• Taxable Benefits• Pretax Deductions• Voluntary Deductions

Information elements aren't supported.

At which employment level should this element be attached? Select the appropriate level. Typical examples are:

• Payroll relationship level for deductions and benefits elements• Assignment or terms level for salary, pension, and social

insurance elements• Assignment level for overtime rules, rates, and bonus elements

Check whether your third-party payroll provider can handle terms-levelinformation.

Does this element recur each payroll period, or does it require explicitentry?

Select Recurring or Nonrecurring.

What are the values to enter for deduction elements?

Period Deduction Amount Goal Amount

Defining an ElementBefore defining an element, confirm that your country extension is set to Payroll Interface on the Manage Features byCountry or Territory page. This setting controls the behavior of important payroll-related features, such as element templates.



◦ Functional Area: Elements and Formulas

◦ Task: Manage Elements

2. On the Manage Elements page, Search Results section, click Create.



22

3. Select your legislative data group.4. Select the primary classification that matches the purpose or use of the payroll element.

Element Example Primary Classification

Recurring base pay

Annual salary, hourly earnings

Standard Earnings

Recurring payments

Allowance

Standard Earnings

Nonrecurring payments

Bonus

Supplemental Earnings

Recurring or nonrecurring voluntarydeductions

Savings plans, charitable contributions, oruniform deposit

Voluntary Deductions

5. In the Category field, select Standard.6. Select the secondary classification that corresponds to the selected primary classification.

Example Purpose or Use Secondary Classification

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 the fields as shown in this table, and then 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.

Effective 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 theelement automatically receive it?

No



23

Field Sample Value

What is the earliest entry date for thiselement?

First Standard Earnings Date

What is the latest entry date for thiselement?

Last Standard Process Date

At which employment level should thiselement be attached?

Select the appropriate level, such as terms or assignment level for salary.

Does this element recur each payrollperiod, or does it require explicit entry?

Recurring or Nonrecurring

Process the element only once in eachpayroll period?

Yes

Can a person have more than oneentry of this element in a payrollperiod?

No

Process and pay element separately orwith other earnings elements?

Does this element have a limit on the amount which is exempt from Federal Tax?

Does this element have a limit on theamount which is exempt from FederalTax?

No

Does this element have a limit on theamount which is exempt at state level?

No

9. Click Next.10. On the Additional Details page, complete the details as shown in the following table:

Field Value

What is the default periodicity of thiselement?

Bimonthly

Periodicity Conversion Rule

Standard Rate Annualized

11. Verify the information is correct, and then click Submit.

Setting Up Values for Deduction ElementsConfigure values for deductions and select the special purpose Primary Input Value as one of the values.



24

Optionally, for recurring elements, specify a value that limits the amount deducted for a value using a goal amount.

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 the following 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 Amount5. Click Save.6. Click Submit.

Setting Up Element EligibilityOn the Element Summary page, update the newly defined 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 field, enter the element name with the suffix: Open.5. In the Eligibility Criteria section, select All payrolls eligible.6. Save and submit the element.


Associating Employees with PayrollYou can associate new and existing employees to provide additional assignment information.

New EmployeesWhen hiring an employee using the HCM hire flow, specify the payroll to which the employee must be mapped in the PayrollDetails sub section of the Assignment section.




25

Existing EmployeesOn 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.

Managing Additional Employee InformationManage additional employment information for payroll interface for ADP in one of the following 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 provided by ADP into the HCMapplication before you map employees with those values.

Managing Payroll and Salary DefinitionsUse the Manage Payroll Definitions task in the Payroll Calculation work area to specify payment frequency, processingschedule for a particular payroll. Create at least one payroll definition for each payroll period type that you use to payemployees.

Use payroll definitions to group employees with similar pay characteristics so that reporting and processing of payroll by thethird party payroll application becomes efficient.

Offering/Functional Area/Task Description

Compensation Management /Workforce Compensation / ManageSalary Basis

Configure salary basis that specifies the frequency of amount sent to payroll and stored as salary.For more information about salary basis, see Section: Managing Salary for Payroll Interface for ADPGlobal Payroll: Procedure.

Workforce Deployment/ Payroll/ ManageObject Groups

Extract data for either one payroll or multiple payrolls that are defined within a legislative data group.You can also group employees. For more information about setting up object groups, see Section:Setting up Object Groups.

Workforce Deployment/ Payroll/ ManageRate Definitions

Convert the salary defined in one frequency to equivalent value in another frequency. For moreinformation about creating rate definitions, see Section: Create Rate Definitions.



26

Managing Salary for Payroll InterfaceSalary components itemize new or adjusted salary into one or more components that reflect different reasons for theallocation, such as merit, adjustment, and location. To configure the use of salary components, use the Manage Salary Basistask in the Compensation work area.

The salary basis specifies the frequency of the amount sent to payroll and stored as salary, such as annual or hourly amount.Use the Manage Elements task to define salary basis, which holds the payroll element for base pay.

Managing salary involves the following steps

Identify salary components

Define base pay element Define salary basis

Associate salary basis to base pay

element

Administer salary for employees

Perform the following 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 the following details:

Parameter Value

Legislative Data Group

Legislative Data Group under which you want to create the element

Primary Classification

Standard Earnings

4. Click Continue to open the Create Element: Basic Information page.5. Enter the following basic details:

Parameter Value

Name

Annual Salary

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



27

Parameter Value

Effective Date

1/1/1951. Enter an early date so that the payroll element is available for use immediately in yoursalary bases.


First Standard Earning Date




Match the employment level to the level at which the salary basis is associated with workers,either Assignment Level or Term Level.


For base pay, use Recurring.

6. Complete the additional details as appropriate. Click Next.7. Click Next to open the Create Element: Review page. Review the element definition.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 defined.

Setting up Salary BasisThe salary basis type specifies 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 theemployee pay frequency.

To set up salary basis, perform the following steps

1. In the setup and maintenance work area, go to the following:

◦ Offering: 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





28

Extracting Terminated Employees: Critical ChoicesThe application continues to process a terminated employee in payroll and make payments even after the employee leavesthe company or after their last regular salary has been processed.

The following 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 DateThe date till which the employee can be paid his regular salary. This is the employee's actual termination date.

Last Standard Process DateThe date on which the last regular payroll for the employee is processed. This is the period end date of the payroll to whichthe employee is terminated.

Final Close DateThe date on which all settlements to the employee are expected to complete. No payments can be processed for theterminated employee after the final 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 manuallyas required. For example, if an employee is terminated in June, the application processes employee's last regular payroll inJune. To make the full settlement 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 theterminated employees till the employee's Final Close Date. For example, if the bonus element is defined with thelast entry date as Final Close date, this element can be used for paying bonus to the terminated employee till31st October.


Chapter 4Global Payroll Interface Extract

29

4 Global Payroll Interface Extract

OverviewUse 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 extractdefinition to generate a custom flow with the same name as the extract.

You can add custom fields to the extract definition. The extracted data includes global and country specific data. Dependingupon the LDG, the application copies country specific data. For example, when you copy a GPI extract definition within thecontext of an Australian LDG, global and Australia specific data is copied to the new extract.

Payroll Interface uses the HCM Extracts infrastructure. All delivery options available within HCM Extracts are available forGlobal Payroll Interface. For example, the output file can either be sent across through SFTP or using HCM Connect over topre-specified destinations.

When configuring the payroll interface for ADP Global Payroll, set up certain prerequisite elements including license type forcountry and territory. Use the Manage Feature by Country or Territory task to set up Payroll Interface as the SelectedExtension.

Geographies and Legislative Data GroupUse the Load Geographies for US task in the setup and maintenance work area to load geographies and create thegeography structure for each country. Ensure that you have selected the Data Source as Vertex.

Use the Manage Legislative Data Group task in the setup and maintenance work area to define the legislative data groups toidentify the country and its currency. Define at at least one legislative data group for each country and associate it with a PSUto provide the payroll information for workers.

Legal EmployerA legal employer is a legal entity that employs workers. Depending on the structure of the organization, define one of thefollowing:

• One legal entity that is also a payroll statutory unit and a legal employer.

• Multiple legal entities which are children of one payroll statutory unit.

Payment MethodsUse the Manage Organization Payment Methods task in the Setup and Maintenance work area to create at least onepayment method for each combination of legislative data group, payment type, and currency. You can also create rules forvalidating or processing the distribution of payments.



30

When creating a payment method, select the Payment Type as Electronic funds transfer (EFT).

Related Topics

• Loading Geographies: Procedure

Payroll Interface Extract Flow ParametersYou can include flow parameters in your extract that are based on the Payroll Interface extract definitions.

This table describes the flow parameters that you can include in your extract::

Flow Parameter Description

Changes Only A list of values that enables selection of different extract modes to filter data in the output file. For

example, to extract only data that has changed since the previously run extract process.

In the extract definition, 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

A list that enables search and selection of a specific payroll. Payrolls define the list of employees toretrieve in the extract process. In the extract definition, this parameter is mapped to the Payroll lookup.

Payroll Period

A list that enables search and selection of a specific payroll period for which data is to be reported. In the extract definition, this parameter is mapped to the Payroll Period lookup.

Process Start Date

An optional date parameter to provide a date as of when to get data from outside the range of thepayroll period. In the extract definition, the name of this parameter is Start Date.

Process End Date

The required date parameter, typically the end date of the payroll period. The application can'tderive this date from the selected payroll period, so it must be provided when submitting the extractprocess. In the extract definition, the name of this parameter is Effective Date.

Suppress Zero Balance

Provides the option to suppress zero values in case Calculate Gross Earnings process was run andthe balance value is 0. This parameter is only applicable if you are calculating gross earnings as partof your Payroll Interface implementation. In the extract definition, this parameter is mapped to the HRC_YES_NO lookup.

Process Configuration Group

Provides the option to search for and select a run-time profile, for example to run the process indebugging mode. In the extract definition, this parameter is named Parameter Group and is mapped to ProcessConfiguration Group lookup.



31

Flow Parameter Description

Related Topics

• Guidelines for Using Different Modes for HCM Extracts

• Payroll Process Configuration Parameters

Effective DatesThe payroll interface extract uses the effective start date and end date features to manage the data elements. The two dataelements EffectiveStartDate and EffectiveEndDate contain the start and end date of the records extracted.

For extracting data, the interface uses the Process End Date parameter specified at the time of submitting the payrollinterface as the effective date.

For example, consider these set of date effective assignment data records for an employee:

Record ID Start Date End Date Description

1

1-Jan-17

31-May-17

The worker is hired asConsultant.

2

1-Jun-17

30-Nov-17

The worker gets promoted asSenior Consultant.

3

1-Dec-17

End of time

The worker gets a change inlocation.

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=F4E3FFB4DA6B521FE040D30A688176A0

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=C128E0C3C95BDB7FE040D30A68812330



32

Scenario 1When you run the extract process with effective date as 10-Dec-2017, the application extracts Record 3.

This figure shows which record is extracted when the extract process is run with effective date as 10-Dec-17:

1/1/17 7/1/17 11/30/17

Record 1:Worker hired as Consultant

Record 2: Promoted to senior

consultant.

5/31/17 12/1/17

Record 3:Location change

12/10/17

Extract process is run with effective date as 12/10/17

The application extracts Record 3

Scenario 2When you run the extract process with effective date as 10-June-2017, the application extracts Record 2.

This figure shows which record is extracted when the extract process is run with effective date as 10-June-17:

1/1/17 7/1/17 11/30/17

Record 1:Worker hired as Consultant

Record 2: Promoted to senior

consultant.

5/31/17

12/1/17

Record 3:Location change

The application extracts Record 2

When the extract process is run with effective date as 6/10/17

6/10/17



33

Setting up Object GroupsAn 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 defined within alegislative data group. You can also group employees.

For example, group those employees for whom the regular extraction process was not complete for further processing.

Note: This configuration 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 fields:

Field Description

Name

ADP_ US_ PAY_OBJ_GRP


US Legislative Data Group

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 Definition 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





34

Action Indicators for Payroll InterfaceIndicators identify and indicate the transactions that cause change in the employment.

Action indicators include hire, termination, and rehire values.

Indicators

Salary ChangeValues: Y, N, Null

HireValue: H

Action Indicator

RehireValue: R

Payroll TransferValues: TI, TO, Null

TerminationValue: T

The table describes the indicators:

Indicator Description

Hire, Termination, Rehire

• Located within the Service data.• Represented by values H, T, R respectively.• If the employee record has been 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 the value TO on the

data corresponding to the payroll from which the employee has moved out and the value TIon the data corresponding to the payroll into which the employee has moved in.

The below table summarizes the behavior of the indicators for various scenarios:

Indicator Name Action EffectiveDate

1-Mar to 31-Mar Any period after31-Mar (PeriodicExtract)

Daily Extract for4-Mar )

Daily Extract for5-Mar


New Hire

Hire Date = 5-Mar-2017

ActionIndicator= H

ActionIndicator= O.

The applicationdoes not

ActionIndicator= H

ActionIndicator= O



35






The applicationincludes allattributes forthe person asthe person isextracted forthe first time. Allprior value mustbe null.

Prior value forNew Hire = HThe applicationretrieves thechangedattributes withprior values. Itdoes not includepersons thatdo not haveany changedattribute.

generate anyreports for theemployee.

The applicationincludes allattributes forthe person asthe person isextracted forthe first time. Allprior value mustbe null.

Prior value forActionIndicator= H. The applicationretrieves thechangedattributes withprior values. Itdoes not includeany person thatdoes not haveany changedvalue.

Terminate

ATD = 20-Mar-2017 The date onwhich theemployee wasterminated - 5-Mar-2017.

ActionIndicator= T The applicationretrieves allterminationdetails and theattributes thathave changed inthe period.

ActionIndicator= O The applicationretrieves theHR data foremployeesthat are nolonger with thecompany. Thestatus of suchemployees isInactive. If thereare payroll datachanges, theapplicationwill continueto extract theemployee till theFinal close date.

ActionIndicator= O Prior Value = N/Blank. The applicationretrieves allchangedor markedattributes.

ActionIndicator= T Prior Value = O The applicationretrieves allchangedor markedattributes. The applicationextracts theterminationdetails withthe actualterminationdate as 31-Mar-2017 in theassignment data. The prior valuefor terminationdate is blank

ActionIndicator= O. Prior Value = T The applicationretrieves allchangedattributes. The applicationdoes not retrievethe employeeeven though noattribute haschanged.

Rehire

Rehire Date = 5-Mar-2017

Same as newHire except thatfor rehire theActionIndicatorwill have thevalue as R.





Payroll Transfer

Payroll Transferdate = 5-Mar-2017

In the firstpayroll: Payrolltransfer = TO(= transfer out)the employee isavailable underthe first payrolltill 4-Mar. In thesecond payroll:Payroll transferTI (=Transfer In),

The employee isavailable in thesecond payroll. Payroll transfer =blank

The employee isavailable in thefirst payroll. Payroll transfer =TO

In the secondpayroll: Payrolltransfer = TI,the employee isavailable in thesecond payrollfrom 5-Mar.

The employee isavailable in thesecond payroll. Payroll transfer =blank



36






the employee isavailable in thesecond payrollfrom 5-Mar.

Salary change

Salary changedate = 5-Mar-2017

Salary change =Y Prior Value = N/Blank. The salaryrecord showsthe latest salaryrecord basedon the currentdesign withthe effectivedates startingfrom 5-Mar. Theelement entriesdisplay the salaryelement entryrecords endingon 4-Mar andstarting on 5-Mar

Salary change =N/Blank Prior Value = Yif the applicationextracts theemployee.

Salary Change =N/Blank Prior Value =N/Blank if theapplicationextracts theemployee.

Salary Change =Y Prior value = N/Blank. The salaryrecord showsthe latest salaryrecord based oncurrent designwith effectivedates startingfrom 5-Mar. Theelement entriesdisplay the salaryelement entryrecord startingon 5-Mar.

Salary Change= N/Blank ifapplicationextracts theemployee.

Salary Change= N/Blank if theemployee isextracted.

Hire Date = 5-Mar-2017. Terminationrecorded on 5-Mar-2017 ATD =20-Mar-2017.

ActionIndicator= H The applicationpopulates theterminationdetails for theemployee withATD as 20-Mar-2017.

The applicationextracts theemployee dueto the elementchanges. ActionIndicator= O.

The applicationdoes not extractthe employee.


ActionIndicator= O The applicationreports otheremployee dataas appropriate.

Hire Date = 5-Mar-2017. Terminationrecorded on 6-Mar-2017 ATD =20-Mar-2017.


The applicationextracts theemployee dueto the elementchanges. ActionIndicator= O.

The applicationdoes not extractthe employee.

ActionIndicator= H The applicationreports otheremployee dataas appropriate.

ActionIndicator= T The applicationpopulates theterminationdetails for theemployee withATD as 20-Mar-2017.

Terminate andRehire in theextraction period

Mar-2017 Dateon which theterminationwas recorded= 5-Mar-2017Rehire Date =21-Mar-2017.

If the samepayrollrelationship ID isused for rehireActionIndicator= R, theapplicationpopulates the

ActionIndicator= O

ActionIndicator= O

ActionIndicator= T. Theapplicationpopulates theterminationdetails for theemployee with

When extractis run for 21-Mar-2017:ActionIndicator= R.



37






terminationdetails with ATDas 20-Mar-2017.

ATD as 20-Mar-2017.

Hire, Terminateand Rehire in thesame period

Hire Date = 1-Mar-2017. Terminationrecorded on 5-Mar-2017 ATD= 20-Mar-2017Rehire Date =21-Mar-2017

If the samepayrollrelationship isused for rehireActionIndicator =R the applicationpopulates theterminationdetails. Also, itpopulates theprevious hiredetails.

ActionIndicator= O

When runningthe extract for1-Mar-2017,ActionIndicator =H From 2-Mar to4-Mar, it will beO.

ActionIndicator= T. Theapplicationpopulates theterminationdetails for theemployee withATD as 20-Mar-2017.

When extractis run for 21-Mar-2017:ActionIndicator= R.

Creating Rate DefinitionsOptionally, you can create rate definitions to calculate compensation rates and other rates. For example, accrual rates, usingpayroll balances, element entry values, or values defined by criteria.

Use the Manage Rate Definitions task to convert the base salary defined in one pay frequency to multiple frequencies. Inthe Setup and Maintenance work area, navigate to these tasks:


• Functional Area: Payroll

• Task: Manage Rate Definition

Here's how you can create a rate definition:

1. In the Create Rate Definition dialog box, complete these fields:

Field Value

Category

Element


US

Storage Type

Amount This value must be the same as the Input Value chosen when you defined the Salary Basis.

Element Name

Select the required value.

2. Click OK.



38

3. On the Create Rate Definition page, consider these points:

◦ The Overall salary check box is selected.

◦ The periodicity of this rate definition matches up with the periodicity of the salary basis to which the underlyingelement is mapped.

◦ The Rate Contributor is defaulted to the same input value that was specified in the corresponding salarybasis.

4. Click Submit.

Related Topics• Create Rate Definitions for Leave

• Create Rate Definitions for Overall Salary

Transactional and Operational RecommendationsTransfer employees as close as possible to the process period end date of the source payroll while performing transactionson the HCM cloud. Sometimes, the payroll to which the employee is transferred could belong to a different country. In suchcases, update the Final Close Date for the source payroll as the process period end date.

Transactional RecommendationsDo not purge data. To delete data, use the end date of the business object. However, in unavoidable circumstances, if youdelete the data, use the Deleted Data Report to extract the deleted data.

For terminations, specify the Notified Termination Date as the date on which the termination is recorded. The terminationindicator 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 thetermination details of the employee whenever payment related information is updated till you make the full settlementto the employee. Set the Final Close Date of the payroll relationship for the terminated employee to a future date.Till this final 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, do not extract the employeedetails after the termination date. Set the Final Close date as the actual termination date, so that the applicationdoes not extract the employee details after the termination date.

Operational RecommendationsHere are few recommendations while you submit the Global Payroll Interface:

• Use the delivered Run Global Payroll Interface flow 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 files sent to the third-party payroll application.

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=E015EDB7F7E94DA3E040D30A688147B4

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=120B9CB31C165252E05362C3F00AD9BD



39

◦ 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 GlobalPayroll 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 optionto nullify failed extraction runs or extractions that contain erroneous data. When you roll back an extraction, you bringthe application back to how it was before you extracted data. You can roll back extractions at process level and forselected employees within a process. To roll back an entire payroll interface process, specify the name of the payrollinterface 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 submitted process first.

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 are not 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 DefinitionsUse the delivered extract definition and flow if these considerations apply to your current implementation. Otherwise, create acopy of the delivered extract definition and update that copy.

• The data defined in the delivered extract meets your interfacing requirements.

• Few or no additional configurations are required on the delivered extract definition.

• The report output template meets the reporting requirements.

Here's an approach to reduce the configuration effort in implementations involving multiple countries, for changes that arecommon to all countries.

• Create a copy of the delivered extract definition at the Enterprise level (without specifying a LDG).

• Update this copy at the enterprise level that are common across all countries.

• For making country specific changes, search for the extract definition by specifying the respective LDG and make thecountry specific changes. Repeat this step for individual countries.



40

Use Extensible Fields to Include Additional AttributesUse the configurable extensible fields to include additional attributes in your extract definition. You can include up to fiveadditional attributes. You can configure fast formulas to determine the values for these attributes and map these formulas tothe extensible fields.

To use the configurable extensible fields, do these actions:

1. Create a rule formula of type Extract Rule for each extensible attribute that you want to extract.2. Map the rule formula to the extensible attributes using the delivered lookup type

ORA_HRY_EXTND_DATA_FORMULA_MAP.

Map the Rule Formula to the Lookup TypeDo 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 field, 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 field 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 thevalue for the attribute Extensible Field 1.

Enter a valid description. For example: Thisattribute is being extracted through thisextensible field.



Enter a valid description.











Related Topics

• Overview of Using Formulas

• Overview of Writing Formulas

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=955E31483F2F136EE040D30A68814644

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=1C95BBB4A9951982E05362C3F00AA864



41

Submit the Global Payroll Interface ProcessUse the Submit a Process or Report task from the Payroll Checklist work area to submit the global payroll interfaceprocess.

1. On the Select Flow Pattern 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.

Field Description

Payroll Flow

Enter a meaningful name.

Changes Only

All attributes

Object Group The application extracts data depending on the conditions mentioned in the selected object

group.

◦ If the object group consists of payrolls, then the application extracts all employees thathave been mapped to this object.

◦ If the object group consists of payroll relationships, then the application extracts only thosepayroll relationships mapped to the object group.

Payroll

Use this optional parameter if you don't want to group payroll. If you specify payroll, theapplication 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.


Select the required process configuration group.

4. Click Submit. Monitor the status of the process to successful completion.

Global Payroll Interface Extract FAQs



42

Does the Global Payroll Interface output files contain future datechanges?Depending upon the extract window, the output file contains future dated changes.

What happens if you delete data in the Global Payroll InterfaceOutbound file?If you delete data before sending it to the payroll provider, then it's not available to the payroll provider. Do not delete any datathat has been sent out to the payroll provider.

Can the Global Payroll Interface include Terminated employees?The TerminationDetail section of Global Payroll Interface includes terminated employees details, such as action reason andaction code.

Can I add an additional BI Publisher template on top of existingGlobal Payroll Interface?You can add a BI publisher to global payroll interface as long as it works with the raw xml generated by HCM Extract.


Chapter 5Payroll Interface for ADP Global Payroll

43

5 Payroll Interface for ADP Global Payroll

OverviewThe Payroll Interface for ADP Global Payroll integrates the HCM cloud with the ADP Global Payroll application. Use thisinterface to extract information, such as the salary and earnings details of employees in the format required by ADP GlobalPayroll.

When configuring the payroll interface for ADP Global Payroll, set up the following prerequisite elements:

Offering / Functional Area/Task Description

Offering: Workforce Deployment Functional Area: Workforce Structures Task: Manage Enterprise HCMInformation

Configure any implementation specific details at the enterprise level.

Offering: Workforce Deployment Functional Area: Enterprise Profile Task: Load Geographies for US

Load geographies to create the geography structure for each country. For example, creategeography types called State, City, and Postal Code. Ensure that you have selected Data Source asVertex.

Offering: Workforce Deployment Functional Area: Workforce Structures Manage Legislative Data Group

Define legislative data groups to identify the country and its currency.

Offering: Workforce Deployment Functional Area: Legal Structures Task: Manage Legal Entity

Enter the details for the new entry. Ensure that both Payroll Statutory Unit and Legal Employercheck boxes are selected.

Offering: Workforce Deployment Functional Area: Payroll Manage Organization Payment Methods

Create a payment method and associate it with a payment source.

Offering: Workforce Deployment Functional Area: Payroll Manage Consolidation Groups

Define at least one payroll for each payment frequency. For example, you can use three payfrequencies, namely Monthly, Bi-weekly, and Weekly to process payments for different categories ofits employees.



44

Offering / Functional Area/Task Description

Offering: Workforce Deployment Functional Area: Payroll Manage Elements and Manage SalaryBasis Offering: Compensation Management Functional Area: WorkforceCompensation Task: Manage Salary Basis

Perform the following tasks:

• Identify a base pay element• Define salary basis• Associate salary basis with base pay element

Salary History Information for ADP Global Payroll Interface:OverviewThe ADP Global Payroll interface extracts history information for salary. The HCM Cloud supports date effective managementof salary. It records all date effective changes made to the salary information as date effective records.

The interface extracts all the salary records that are effective within and overlap the start and end date.

The salary records for an employee is as shown in the table below:

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

When the extraction start and end date is 1-Jun-17 to 30-Jun-17, the application extracts the salary records as shown in thetable below:


1-Jan-17

10-Jun-17

Hire

120,000

11-Jun-17

30-Jun-17

Correction

140,000

When the extraction start and end date is 1-Jun-17 to 31-Jul-17, the application extracts the salary records as shown in thetable below:



45


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

Additional Payroll Interface Data ElementsUse the Manage Value Sets for Global Human Resources tasks to identify and manage additional data elements and listof 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 offering in theWorkforce Information work area.

Include the following 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

Work Contract

Assignment

Organizational Key

Assignment

HR Administrator

Assignment

Payroll Administrator

Assignment

Time Administrator

Assignment

Work Schedule Rule Assignment



46

Data Element Name Level

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

The following 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

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



47

Data Element Name Data Type Code

Work Schedule Rule

Lookup

ORA_ GPY_ WRK_SCHD_RULE

Employment Percentage

Free text

Numeric field

Weekly Workdays

Free text

Numeric field

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 field

Working Hours Per Payroll Period

Free text

Numeric field

Number of Dependents

Free text

Numeric field

Distance in Kilometers

Free text

Numeric field

Running Global Payroll Interface ProcessesThe Standard Payroll Interface for ADP Global Payroll flow in the Payroll Checklist work area includes the following processes:

Process Description

Data Validation Report

Validates the data available on the HCM cloud before passing them on to ADP. It takes into accountstatutory requirements and helps identify missing or non-compliant data. You can then takenecessary action to fix the data before passing the data over to ADP.

Payroll Interface for ADP Global Payroll

Submits the ADP Global Payroll interface process and generates the output file that must passed toADP.

Deleted Data Report

Reports data belonging to a specified set of business objects that have been deleted from theHCM Cloud system during the extraction period. This report serves as a supplement to the ADPGlobal Payroll Interface output xml file to account for complete set of data changes within the givenextraction period.

Note: Do not delete any data in the HCM application. End date any incorrect data thatshould not be used for processing.



48

Running the Payroll Interface Process for ADP Global PayrollUse 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 the parameters as shown in the following table:

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, then the application considers all employeesassociated with the payrolls that have been mapped to this object group for extraction.This enables data corresponding to multiple payrolls being reported in a single output file.

◦ If the object group is a group of payroll relationships created for the purpose of exceptionreporting, then the application extracts only those payroll relationships (employees)mapped to this object group.

Payroll

Payroll is an optional parameter provided to support customers who do not want to grouppayrolls. If you specify a payroll, then the application extracts only those employees that are mapped tothat particular payroll.

Note: It is mandatory to provide either an Object Group or a Payroll or a combination ofboth.

Process Start Date

Start date of the extraction period.

Process End Date

End date of the extraction period. The application considers this as the effective date and extractsthose records that are effective as on this date.

5. Click Submit.6. Monitor the status of the process to successful completion.

Configuring Prior ValuesUse the BLOCK_OLD mode on the Payroll Interface for ADP Global Payroll to identify the employment and payment datachanges. The application displays the updated data as on the effective date as the current value and the previous value of theattribute as prior value.

In the below example, an employee moves from the Consulting department to Development department changing theirposition 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>



49

<gpi:ReportingEstablishment> Development </gpi:ReportingEstablishment> <gpi:WorkerCategory> White Collar </gpi:WorkerCategory> <gpi:WorkingHours> 40 </gpi:WorkingHours> <gpi:Frequency> W </gpi:Frequency>

The table below summarizes the behavior of the PriorValue attribute in response to the type of change that the data elementundergoes.

Scenario Prior Value AttributePresent

Prior Value AttributePopulated

Element Populated Sample Output

Initial Extracts All Attributes Run with Changes Only= N

Yes/No = No

Yes/No = No

Yes/No = Yes

Change: Initial Extract. Alldata reported.

First Snapshot Run with Changes Only =BLOCK_OLD An object or entityreported for the first time. Includes New Hire andPayroll Transfer as a newentity.

Yes/No = Yes

Yes/No = Prior value willbe NULL

Yes/No = Yes

Change: Available datais reported and thecorresponding prior valueshows NULL.

Element changes from novalue to a value.

Yes/No = Yes



Change: Address 2changed from no valueto a value and has aprior value NULL. Theother attributes have notchanged and so they donot contain a prior value.

Element changes fromvalue to no value.

Yes/No = Yes

Yes/No = Yes

Yes/No = Yes

Change: Address 2changed from valueto no value and hasa prior old value. Theother attributes have notchanged and so they donot contain a prior value.

Element does not change

Yes/No = No

Yes/No = No

Yes/No = No

Change: No changes. Allvalues are shown as theyare without prior values.

Element changes fromone non-null value toanother non-null value.

Yes/No = Yes

Yes/No = Yes

Yes/No = Yes

Change: Elementchanges from one non-null value to anothernon-null value. Addresschanges from Belmont toJersey city.



50

Setting up Additional ElementsWhen configuring the global payroll interface for ADP Global Payroll, use the Submit a Payroll Flow task to configure additionaldata elements.

Enable the following predefined contexts:

• Additional Assignment Details for ADP Global Payroll Interface

• Additional Person Details for ADP Global Payroll Interface

Enabling Predefined ContextsUse the Submit a Payroll Flow task in the Payroll Checklist work area to complete the steps:

1. On the Submit a Payroll Flow: Select Flow Pattern page, search for the Manage Global Payroll Interface FeaturesUsage flow.

2. Select the flow and click Next.3. On the flow parameter page, enter the following details:

Parameter Value

Payroll Flow Name

Meaning name to the current flow.

Activate Usage

Yes

Feature

Search for Assignment EIT Information EFF.

Component

Search for Additional Assignment Details for ADP Global Payroll.

4. Submit the flow.5. To enable the additional data available under Person, repeat the above steps using the following 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 therecommendation given by ADP. Consult with ADP before enabling the features and sub components.





51


◦ Task: Manage Extensible Flexfields for Payroll

7. Search for the Assignment Extensible flexfield by entering Assignment EIT Information value in the Name field.8. In the Search Results section, select the Assignment EIT Information EFF row and click Deploy Flexfield.9. Ensure that the deployment completes successfully.

10. Ensure that the Deployment Status column shows a green tick mark.

Related Topics


Managing Payroll Interface Data Values for ADP GlobalPayroll: ProcedureUse the Manage Common Lookups task to create a lookup for managing additional data values, such as Company Code andPersonnel Area. You can also manage these data values by using the Manage Value Sets task to create a value set.

Creating Lookups for Data ValuesUse 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 field, enter ORA_GPY_BUSINESS_AREA and clickSearch.

2. In the ORA_GPY_BUSINESS_AREA: Lookup Codes section, click New from the Actions menu.3. In the row, enter the following details:

Field Description

Lookup Code

BA1

Display Sequence

10

Start Date

01/01/2000

End Date

12/31/4712

Meaning

Business Area

Description

Business Area





52

Creating Value sets for Data ValuesUse the Manage Value Sets task in the Setup and Maintenance work area to complete these steps:

1. On the Manage Value Sets page, Value Set Code field, 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.5. Click Save and Close.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.8. Click Manage Values.9. On the Manage Values page, click Create.

10. On the Create Value page, enter each sub area as a new value. Ensure that the area to which this sub-area belongsto is chosen under the Independent Value column.


Override the Cost Center Using Configurable Cost CenterOverride AttributeUse the configurable Cost Center Override attribute to include a logically determined overriding cost center in the ADP GlobalPayroll interface. You can use fast formulas to determine the value for the overriding cost center and map it to the CostCenter Override attribute using the delivered lookup type.

To use the configurable Cost Center Override attribute, 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 TypeDo 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 field, 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 field to enable this feature.4. In the ORA_HRY_EXTND_DATA_FORMULA_MAP: Lookup Codes section, add this lookup code:

Lookup Code Meaning Description


Valid rule formula name to return the valueof the override cost center.

Enter a valid description. For example,the cost center override attribute is beingextracted through this extensible field.



53


Related Topics

• Overview of Using Formulas

• Overview of Writing Formulas

Configuring Dynamic File Names for global interface forADP Global Payroll : ProcedureThe global interface for ADP Global Payroll generates the output file names dynamically. The name of the file generatedcorresponds to the format

ORA_PQX148_YYYYMMDDHHMMSS_USOGPI_HRMD01_DUT8G2I.XML

To generate ADP Global Payroll interface files with the above file name configure lookup types, value sets, and fast formula.

Lookup TypeConfigure a new lookup type to hold implementation specific values for some of the components in the dynamic file name.For example, the Client Number might vary between different customers. Create a new lookup type to use it in a file name.

Follow these steps to 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 the values as shown in the table:

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 file name.

Module

Oracle Fusion Middleware Extensions for Applications

4. In the Lookup Codes section, click New.5. Enter the values as shown in the table:

Parameter Value 1 Value 2

Lookup Code

ADP_ GPY_ SYSTEM_NUMBER

ADP_ SAP_ CLIENT_NUMBER

Enabled

Yes

Yes

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=955E31483F2F136EE040D30A68814644

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=1C95BBB4A9951982E05362C3F00AA864



54

Parameter Value 1 Value 2

Meaning

Actual value

Actual value

Description

ADP Global Payroll System Number

ADP Global Payroll Client Number

6. Click Save.

Value SetsUse value sets to extract various values required to form the dynamic output file name.

Define new value sets as shown in the below table:

To Derive FROM Clause ID Column Name WHERE Clause

Legislation Code

PER_ LEGISLATIVE_ DATA_GROUPS_VL

LEGISLATION_ CODE

LEGISLATIVE_ DATA_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 FormulaA fast formula combines the various file name components in the correct sequence and returns the final file name.

Create fast formula of type Extract Rule as shown in the table below:

Formula Parameter Value

Formula name

ADP_ GPY_ OUT_ FILENAME_ FORMULA

Description

Formula to consolidate various file name components and return the final output file namedynamically.

Formula text

------FORMULASTARTS-------------------------------------------------------------------------------------------- DEFAULTFOR RULE_VALUE IS ' ' ----- GET THE INSTANCE NAME FROM THE INTERFACE PROCESSPARAMETER L_ FINAL_ VALUE='ORC_P' + GET_ PARAMETER_ VALUE('INSTANCE_ NAME')----- GET THE SYSTEM NUMBER FROM THE LOOKUP AND CONCATENATE TO FINALFILENAME 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 LOOKUPAND 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 THECOUNTRY CODE FROM THE LDG AND CONCATENATE TO FINAL FILENAME L_LEG_PARAM



55

Formula Parameter Value

= 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 OTHERHARD 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_ VALUEVARIABLE RULE_VALUE = L_FINAL_VALUE RETURN RULE_VALUE -------FORMULAENDS------------------------------------------------------------------------------------------

Save and compile this formula.

Update Extract StructureSave the generated file name in one of the attributes in the extract. The application uses the attribute in the delivery options togenerate the file with the dynamic file name.

1. Navigate to the Data Exchange work area. Select Manage Extract Definitions.2. Search for the extract definition specifying Name as Payroll Interface for ADP Global Payroll.3. Create a new record in the extract.4. Add an attribute of type Rule to this record and attach the rule formula created above.5. Specify Type as Rule and Rule as ADP_file_name_rule.6. Submit the changes and ensure that the validations are successful.

Additional Details Reported in the FileThe payroll interface includes the following additional details:

• Extract Version Number

• Extract Instance Name

• Employees Reported in the File

Extract Version NumberUse the version number of the payroll interface extract definition to troubleshoot and diagnose issues. The extract versionnumber 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 there are major changes to the extractdefinition including its structure or critical data inclusion on the global data section.

• Y is the medium release and tracks changes, such as inclusion of new legislations, changes to existing legislationdata, 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 first release of the interface has the version number 1.0.0.



56

Extract Instance NameThe source instance type, such as Production, Development, or Test from which an extract output file is produceddetermines the destination ADP instance.

Employees Reported in the FileThe individual payroll relationships reported in the file appear to wards the end of the file to help record count reconciliation.

Note: The count displayed in the file is the count of distinct payroll relationships. For example, an employee withtwo payroll relationships is reported as two in the record count.

Transactional RecommendationsFollow certain recommendations when performing 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, then notify ADP bysending the output of the Deleted Data Report that contains the deleted data details.

Payroll TransfersTransfer employees as close as possible to the process period end date of the destination payroll. Update the Final CloseDate of the source payroll as the process period end date.

In the output file, for transferred employees, Indicate the following:

• 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 enddate, which is also the Final Close Date.

Employee TerminationsThe Notified Termination Date is the date on which the employee is terminated.

The interface supports the following two approaches for paying terminated employees:

• Update the payments on the HCM cloud and send the details to Payroll for processing.

◦ Until you make the final settlement for the employee, extract the terminated employee's details whenever thereis a change in employee's 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 final settlement.

After the Final Close Date, the application does not extract the employee.



57

• Process the payroll details directly on the Global Payroll application. In this case, the application does not extractthe terminated employee after the terminated date. Set the Final Close Date as the actual termination date of theemployee so that the application doesn't extract the employee after the termination date.

Update the Final Close DateUse the Person Management task in the My Client Groups work area to set the final close date. For example, forterminated 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 field, enter the required date. Click Save.

Cost Center AllocationsThe Interface supports cost allocation only to department cost centers that the assignment belongs to. It does not supportsplitting of costs across multiple cost centers.

Operational RecommendationsFollow certain recommendations when submitting the payroll interface for ADP Global Payroll,on the HCM cloud. Forexample, for processing the ADP Global Payroll interface, use the delivered Run Payroll Interface for ADP Global Payrollflow. This flow when run from a specific LDG extracts the global data and the legislative data pertaining to the country towhich that LDG is associated.

Initial ExtractExtract all information pertaining to all employees identified based on process parameters. Since this information is availableon the ADP Global Payroll application, the application does not use the output file of the initial extract for any processing.

Run the following:

• Initial extract in the baseline mode by specifying the baseline parameter as Yes. The application extracts and keepsthe extract without generating any output file.

• Subsequent extracts by specifying the baseline parameter as No.

Extraction WindowThe time interval between the Process Start Date and Process End Date parameters is referred to as the extractionwindow.

• Choose the extraction window and do not change it at a later point in time.

• Run the extraction on a daily basis, typically at the end of the day's work.

When choosing the extraction window, consider the following:

• Frequencies of payments supported. For example, Monthly, Weekly, Bi-weekly.

• How often interface files are sent to the ADP Global Payroll application.



58

• When the application records the data. For example, as and when the changes happen, after the changes happenwith 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 as follows:

• Extraction start date to a date sufficiently earlier than the current date.

• Extraction end date to a date sufficiently later than the current date.

Extraction ScheduleSchedule the regular ADP Global Payroll interface processes like any other process within the HCM cloud. The applicationsupports all options, such as dynamic (fast formula based) date parameter setting.

When scheduling this process, do not set the Process End Date parameter to a date earlier than the end date of anyprevious runs.

Unplanned RunsThe payroll interface for ADP Global Payroll supports unplanned runs to address exception scenarios that result in transactionchanges. 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 theextraction end date same as the end date of the immediate last regular interface run.

Extraction RollbackRoll back nullifies 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 and addthe payroll relationships of employees for whom the process must be rolled back. When rolling back multiple processes, rollback the last submitted process first.

Increment Process Dates AutomaticallyThe data that the ADP Global Payroll Interface reports depends on the extract start and end dates that you select when yousubmit 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.



59

Before you BeginConsider these points when automatically incrementing 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 offset values, the application uses the default value of 0. This means that the start date and end dateboth 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 offsets are applied on the extract execution date, which is actually the system date. If you don't specify theoffsets, the application will use the system date.

• When scheduling the extraction for the first time, enter all other parameters except for Process Start Date andProcess End Date.

To automatically increment the extract start and end date parameters, you follow these steps.

1. Navigate to the Payroll Calculation work area.2. In the Tasks pane, select the Manage User-Defined Tables task.3. In the Name field, enter Profile Options For Payroll Interfaces.4. Select your required Legislative Data Group and click Search.5. In the Search Results section, select the Profile Options For Payroll Interfaces row.6. On the Profile Options For Payroll Interfaces page, click Edit.7. In the Effective As-of Date field, select an effective date.8. Click Next to open the User Defined Table Values page.9. In the User-Defined Table Values section, click Create.

10. In the Add User-Defined Table Values dialog box, select ADP Global Payroll Interface Flow Parameter StartDate Offset.

11. Click OK.12. In the Value field, enter the number of days by which you need to offset the start date.Typically, you 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 dateinto the past, prefix the value with a minus sign. To move the start date forward, prefix the value either with a + signor don't provide any sign. For example, to set the start date 14 days into the past, set the value as -14. Repeat thisstep for Exact ADP Global Payroll Interface Flow Parameter End Date Offset.

13. Click Submit.

Payroll Interface for US ADP Payforce

OverviewThe setup steps required for the Oracle Fusion Global Payroll Interface for the United States can vary depending on:

• The Oracle Fusion products and features that are already configured in your enterprise

• The data 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 configurationrequirements exist for your ADP solutions in the following areas:

• Organizations and Locations



60

• US Geographies

• Person Information

• Element Management

• Payroll Definitions

• ADP Configuration

Organizations and LocationsWhen setting up your organizations and locations, consider the following:

• A one-to-one mapping must exist between a legal employer and a payroll statutory unit (PSU).

• When defining locations, you must use the United States tax address format.

US GeographiesYou must consider the following requirements:

• To properly populate the geographies information, you must run the Load Geographies for US task from theFunctional Setup Manager.

• A valid Vertex Geocode license is required for employees to receive their default tax card.

Person InformationWhen managing employee information, consider the following:

• Each employee in the payroll must have a default tax card associated with a tax reporting unit (TRU).

• You cannot use commas in any part of any address, as ADP Connection for PayForce does not 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 thePER_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 ADPPayForce file number.

Element ManagementWhen defining the elements for your earnings and deductions, consider the following:

• Employee Work Relationships

• Payment Methods

• Element Termination Rules

• Piece-Rate Elements

• Recurring Elements

• Nonrecurring Deduction Elements

• Nonrecurring Earnings Elements



61

Employee Work RelationshipsADP Connection for PayForce does not support multiple terms, so employees should not have multiple terms in a singlework relationship. Any earnings you define at the terms level, including salary, is passed on to the primary assignment. If anemployee has multiple terms with earnings at the terms level, ADP Connection for PayForce may not correctly interpret thevalues passed to the primary assignment.

Payment MethodsWhen defining payment methods, consider the following:

• Employees cannot have both check and direct deposit payment methods.

• Personal payment methods for direct deposit payments must be either set to 100 percent or use fixed dollaramounts.

• When defining Personal Payment Methods, do not select a run type. Leave this field blank.

Element Termination RulesADP PayForce does not support earnings proration. Therefore, all earnings elements other than salary earnings must use aLast Standard Process Date or Final Close termination rule. Do not use Last Standard Earning Date.

Piece-Rate ElementsADP Connection for PayForce does not support piece-rate earnings. Do not pass any elements of this type through thePayroll Interface.

Recurring ElementsWhen defining recurring elements, consider the following:

• Employees cannot have more than one of same recurring element (deductions or earnings). When defining yourrecurring elements, you must prohibit multiple entries.

• When creating a recurring deduction element, and you want the deductions to stop after a set goal amount, youmust create an input value for that element and provide the amount. This input value must be named "Goal Amount".

• When defining deduction elements with a different periodicity than your payroll period, you must:

a. Assign the elements an input value with the special purpose of Periodicity.b. Set the periodicity.

For example, to take a deduction monthly with a weekly payroll, you set the element's periodicity to monthly.

Any earnings elements have the Periodicity input value created automatically.

Note: This information is included in the extract, but it is not used by ADP Connection for PayForce.

Nonrecurring Deduction ElementsThe US ADP PayForce third-party periodic extract pulls only nonrecurring voluntary deductions. Nonrecurring pretaxdeductions are not included.

When defining nonrecurring deductions, you must create and set the following input values for each deduction element:



62

Input Value Special Instructions

Deduction Value

You must identify whether this element is deducting either as a flat amount or a percentage. Use thisinput value to track the amount of the deduction. For this input value, set the Special Purpose field 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

Define 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 ElementsThe US ADP PayForce third-party periodic extract pulls the following nonrecurring earnings types only:

• Supplemental earnings (such as bonuses and commissions)

Nonrecurring regular and imputed earnings are not included.

• Flat amount earnings

Hours * Rate earnings elements are not included.

When defining nonrecurring earnings, you must create and set the following input values for each earnings element:

Input Value Special Instructions

Third-Party Earnings Type Create the following 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

Define values for each of the valid 3-character ADP PayForce earnings codes. During element entry, select the appropriate code for the earnings code.

Payroll DefinitionsWhen creating payroll definitions, consider the following:

• Do not use the bimonthly, lunar monthly, or semiannual payroll frequencies.

• Specify your ADP PayForce Company Code as the first three characters of the payroll reporting name.



63

ADP ConfigurationPrior to running your first extract, consider the following:

• You must perform a mapping exercise with ADP Connection for PayForce. This establishes the baseline between thedata in ADP and Oracle Fusion Human Capital Management for the United States. Refer to your ADP documentationfor more information.

• Existing ADP Connection for PayForce users would already have identification numbers for their employees recordedin ADP's system. However, all persons reported through the Payroll Interface must have their own Oracle employeeIDs. You must use ADP's conversion utilities to convert your employees' legacy IDs into the new ones generated bythe payroll interface.

Alternatively, the user can modify the extract to pass the legacy ADP employee ID dependent upon where customerstores the value.

Related Topics

• Implementing Payroll Interface: Procedure

• Defining Payroll Elements for Payroll Interface: Worked Example

• Manage Payroll Interface: Overview

Third-Party Periodic Extract DefinitionThis topic describes the various component data groups of the US ADP PayForce third-party periodic extract definition for theOracle Fusion Global Payroll Interface for the United States.

This extract has been provided for ADP PayForce and ADP Connection for PayForce users. You must modify this extractthrough the Manage HCM Extract Definitions task if:

• Your payroll installation requires additional information be sent to ADP Connection for PayForce

• You are using a different third-party provider

Use the provided tree structure to configure the data groups, extract records, and data elements as needed. You define whatyou want to extract, how it's extracted, and how you want to deliver the extracted data.

The US ADP PayForce third-party periodic extract definition consists of the following data groups:

Main BlockThis data group contains the four primary groups of the extract definition. To view its specific parameters, you must select theappropriate 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

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=BE75B61810E2354EE040D30A6881734A



64

Contains parameters related to HR data.

Job Data

Contains parameters related to jobs.

Earnings RecordsContains 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_ELEMENT_NAME

PRIME_ BASE_ELEMENT_NAME

Procedure element

Text

PRIME_ ELEMENT_NAME

PRIME_ ELEMENT_NAME

Procedure element

Text

PRIME_ ELEMENT_ REL_LEVEL

PRIME_ ELEMENT_ REL_LEVEL

Procedure element

Text

PRIME_ ELEMENT_TERM_LEVEL

PRIME_ ELEMENT_TERM_LEVEL

Procedure element

Text

PRIME_ ELEMENT_ ASG_LEVEL

PRIME_ ELEMENT_ ASG_LEVEL

Rule

Text

RULE_ PROCESSING_ TYPE

RULE_ PROCESSING_ TYPE

Rule

Text


RULE_ EARNING_CODE

Rule

Text

Third-Party Earnings Type

RULE_ EARNING_TYPE

Rule

Text



65


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 identification number. Not passed on the extract.

BASE_BALANCE_NAME

User-defined name of the balance.

BASE_CATEGORY_NAME

Name of the balance category. Not passed on the output file to third party.

CALC_BREAKDOWN_ID

Internal identification 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 onthe extract

PRIME_BASE_ELEMENT_NAME

Base element name, as defined on the Manage Elements page.

PRIME_ELEMENT_ID


PRIME_ELEMENT_ASG_LEVEL

Indicates if this element was created at the assignment level.

PRIME_ELEMENT_NAME

User-defined element name, as defined on the Manage Elements page.

PRIME_ELEMENT_REL_LEVEL

Indicates if this element was created at the payroll relationship level.



66

PRIME_ELEMENT_TERM_LEVEL

Indicates if this element was created at the terms level.

REPORTING_NAME

Balance's reporting name, as defined in the Reporting Name field in the Manage Balance Definitions task.

RULE_EARNING_END_DATE

End date of the earnings element.

RULE_HOURLY_RATE

Salary amount.

RULE_PERIODICTY

Element frequency.

RULE_PROCESSING_TYPE

Identifies the element as recurring or nonrecurring.

RUN

Value of the balance.


Three-character code used by ADP PayForce for the nonrecurring earning. Defined in an input value on the deductionelement.


ADP PayForce earning code type assigned to this earning. Defined in an input value on the earnings element.

Earnings and Deductions BalancesThis node contains four subordinate data nodes for earnings and deductions. To view its specific parameters, you must selectthe appropriate subordinate nodes elsewhere in the tree.

Earnings Data

Contains internal identifiers related to earnings records.

Taxable Benefits Data

Contains internal identifiers related to taxable benefits.

Pre-Statutory Deductions Data

Contains internal identifiers related to prestatutory deduction records.



67

Voluntary Deductions Data

Contains internal identifiers related to voluntary deduction records.

Earnings and Deductions RecordsEarnings and deductions information derived from user-defined 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_ Identifier_ Number

Database item group

Text

Assignment ID

Internal ID for the employee's assignment. Not passed on the extract and is not used by ADP.

Company

Tax reporting unit responsible for the employee's tax and regulatory reporting, as defined on their tax card.

Employee ID

For new ADP customers, this 11-character value uses the following pattern: AABB3456789

Where:

• AA are the first two characters of the employee's first name. If the first name is missing, "FF" is used instead.

• BB are the first two characters of the employee's last name.

• 3456789 are the third through ninth digits of the employee's national identifier, rearranged to maintain privacy.

For example: "John Smith 123-45-6789" could become "JOSM5398647".

Payroll

Name of the payroll definition, as defined in the Manage Payroll Definitions task.



68

Payroll Frequency

Frequency of the payroll definition, as defined in the Manage Payroll Definitions 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 different assignment identifiers compliant with theirown formatting.

Record Type

Identifies this record as delivering earnings and deductions-specific information about the extract. For use by the third-partyprovider only.

Third-Party ID

ADP PayForce 6-digit file number. Defined as a different lookup under the national identifier.

Pre-Statutory Deductions RecordsThe 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

Effective Date

Effective_Date

String

Text

Deduction Code

Deduction_Code

Database item group

Text

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



69

Deduction Code

Name of the element.

Deduction End Date

End data of the element entry.

Effective Date

Not used and not passed to the third-party provider.



Element Entry ID

Internal ID for the element entry.

Element Frequency

Periodicity of the earning or deduction, as defined by the element's input value identified with the Periodicity special purpose.

Entry Value

Represents the earning or deduction amount, as defined by the element's input value identified with the Primary Input Valuespecial purpose.

Indirect Only

Identifies direct or indirect entries at the element level. Elements marked as indirect are excluded from the extract.

Processing Type

Identifies the element as recurring or nonrecurring, as defined during element definition.

Reserve Value

Input value specified during element entry.

Usage Level

Indicates the level where the element is assigned. Valid values are Payroll Relationship, Assignment, and Term.

Taxable Benefits RecordsThis data group contains information derived from Imputed Earnings elements. Some of these parameter values are derivedfrom the element definition, and some are from the employees' element entry.


Reserve Value

Reserve_Value

Database item group

Text



70


Entry Value

Entry_Value

Database item group

Text

Deduction End Date

Deduction_ End_Date

Database item group

Date

Effective Date

Effective_Date

String

Text

Deduction Code

Deduction_Code

Database item group

Text

Indirect Only

Indirect_Only

Database item group

Text

Processing Type

Processing_ Type

Database item group

Text

Usage Level

Usage_Level

Database item group

Text



Database item group

Number

Element Entry ID

Element_ Entry_Id

Database item group

Number

Element Frequency

Element_ Frequency

Rule

Text

Deduction Code


Deduction End Date

End date of the element entry.

Effective Date




Element Entry ID


Element Frequency


Entry Value



71


Indirect Only


Processing Type


Reserve Value


Usage Level

Identifies the level at which the element is assigned. Valid values are Payroll Relationship, Assignment, and Term.

Voluntary Deductions Goal Amount RecordsThis data group contains information in the Goal Amount special input value. This parameter is used when the deductionelement has a maximum threshold.

Goal Amount

Defines the maximum amount accrued before the deduction stops. Set as an input value during element entry.

HR RecordsThis data group contains HR-specific information about the employer and employees.


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

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 Suffix

Name_Suffix

Database item group

Text

Name Prefix Name_Prefix Database item group Text



72


Preferred Name

Preferred_Name

Database item group

Text

Street 1

Street1

Database item group

Text

Street 2

Street2

Database item group

Text

Street 3

Street3

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

Street 2 Other

Street2_Other

Database item group

Text

Street 3 Other

Street3_Other

Database item group

Text

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



73


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

Employee ID

Employee_ID

Database item group

Text

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


Database item group

Text

Birth Date

Employee's date of birth, as defined in the Person Information page.

Citizenship

Employee's national citizenship, as defined in the Documents tab of the Person Information page.

Citizenship Status

Employee's national citizenship status, as defined in the Documents tab of the Person Information page.

City

City of the employee's home address, as defined in the Person Information page.

City Other

City of the employee's mailing address, as defined in the Person Information page.

Company




74

Country

Country of the employee's home address, as defined in the Person Information page.

Country Other

Country of the employee's mailing address, as defined in the Person Information page.

Date of Death

Employee's date of death, as defined in the Person Information page.

E-Mail Address

Employee's email address, as defined in the Person Information page.

Employee ID


Where:





Ethnicity

Employee's ethnicity, as defined in the Person Information page.

First Name

Employee's first name, as defined in the Person Information page.

Gender

Employee's gender, as defined in the Person Information page.

Home Phone

Employee's home phone number, as defined in the Person Information page.


Area code of employee's home phone number, as defined in the Person Information page.

Last Name

Employee's last name, as defined in the Person Information page.

Marital Status



75

Employee's marital status, as defined in the Person Information page.

Middle Name

Employee's middle name, as defined in the Person Information page.

Name Prefix

Employee's name prefix, as defined in the Person Information page.

Name Suffix

Employee's name suffix, as defined in the Person Information page.

Original Hire Date

Employee's original date of hire, as defined in the Enterprise section of the Service Dates region of the Manage WorkRelationship page.

Payroll

Name of the payroll definition assigned to the employee, as defined in the Manage Payroll Definitions page.

Payroll Frequency

Frequency of the payroll definition assigned to the employee, as defined in the Manage Payroll Definitions page.

Postal Code

Postal code of the employee's home address, as defined in the Person Information page.

Postal Code Other

Postal code of the employee's mailing address, as defined in the Person Information page.

Preferred Name

Employee's preferred name, as defined in the Person Information page.

Record Type

Identifies this record as delivering HR-specific information about the extract. For use by the third-party provider only.

SSN

Employee's social security number, as defined in the Person Information page.

State

Two-letter postal abbreviation of the employee's state, based on their home address, as defined in the Person Informationpage.

State Other



76

Two-letter postal abbreviation of the employee's state, based on their mailing address, as defined in the Person Informationpage.

Street 1

Street 1 field of the employee's home address, as defined in the Person Information page.

Street 1 Other

Street 1 field of the employee's mailing address, as defined in the Person Information page.

Street 2


Street 2 Other


Street 3


Street 3 Other


Work Phone

Employee's work phone number, as defined in the Person Information page.


Area code for employee's work phone number, as defined in the Person Information page.

Visa Number

Employee's visa number, as defined in the Documents tab of the Person Information page.

Visa Expiry Date

Expiration date of the employee's visa, as defined in the Documents tab of the Person Information page.

Visa Type

Type of employee's visa, as defined in the Documents tab of the Person Information page.

Job RecordsThis data group contains job-specific information for the employer and employees.


Record Type Record_Type String Text



77


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

Payroll

Payroll

Database item group

Text

Payroll Frequency

Payroll_ Frequency

Database item group

Text

Record Number

Record_Number

Database item group

Number

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

Company

Company

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

Employee ID Employee_ID Database item group Text



78


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



Employee's seniority date, as defined in the Legal Employer section of the Service Dates region of the Manage WorkRelationship page.

Employee ID


Where:





Employee Type

Employee exemption status, as defined in the Hourly Paid or Salaried fields of the Job Details section of the AssignmentDetails region of the Manage Employment page.

Employment Category

Employee employment category, as defined in the Assignment Category field of the Job Details section of the AssignmentDetails region of the Manage Employment page.

Employment Status

Employee's employment status (full time, part time, regular or temporary, and so on). Defined in the Assignment Categoryfield of the Job Details section of the Assignment Details region of the Manage Employment page.

First Name


Hire Date

Employee's hire date, as defined in the Work Relationship section of the Manage Employment task.



79

Home Department

Employee's home department, as defined on the employee's assignment or term.

Job Code

Job code assigned to the employee's job, as defined in the Manage Jobs page.

Job Title

Employee's job title, as defined in the Job field of the Job Details section of the Assignment Details region of the ManageEmployment page.

Last Name


Location Code

Code assigned to the employee's work location, as defined in the Manage Locations page.

Location Name

Name of the employee's work location, as defined in the Manage Locations page.

Payroll


Payroll Frequency


Record Number

Identifies the employee's assignment, with 0 representing the primary assignment, and increments by 1 for each subsequentassignment.


Record Type

Identifies this record as delivering job-specific information about the extract. For use by the third-party provider only.

Retirement Date

Employee's date of retirement, as defined in the Retirement section of the Assignment Details region of the PersonInformation page.

Salary Basis Amount

Employee's salary amount, as defined in the Salary Details section of the Manage Salary page.



80


Employee's salary basis, as defined in the Salary Details section of the Manage Salary page.

SSN


Standard Hours

Employee's standard number of work hours per period, as defined in the Working Hours field of the Job Details section ofthe Assignment Details region of the Manage Employment page.


Period set for the employee's working hours, as defined in the Frequency field of the Assignment Details region of theManage Employment page.

Supervisor ID

Employee's supervisor, as defined in the Name field of the Manager Details subsection of the Job Details section of theAssignment Details region of the Manage Employment page.

This 11-character value uses the following pattern: AABB3456789

Where:





Termination Date

Employee's termination date, as defined through the Terminate Work Relationship task.

Job Extra BlockThis data group contains FLSA information related to the employees.

FLSA Status

Employee's overtime exemption status, as defined in the FLSA Status field of the United States Job Information section ofthe Manage Jobs task.

Pre-Statutory Deductions Goal Amount RecordsThis data group contains information in the Goal Amount special input value. This parameter is used when the deductionelement has a maximum threshold.

Goal Amount




81

Taxable Benefits Goal Amount RecordsThis data group contains information in the Goal Amount special input value. This parameter is used when the deductionelement has a maximum threshold.

Goal Amount


Direct Deposit RecordsThis data group contains information about personal payment methods.


Record Type

Record_Type

String

Text

Employee ID

Employee_ID

Database item group

Text

Company

Company

Database item group

Text

Payroll

Payroll

Database item group

Text

Payroll Frequency

Payroll_ Frequency

Database item group

Text

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

Effective Date

Effective_Date

String

Text

Maximum Payment Priority

Maximum_ Payment_ Priority

Database item group

Number

Account Number

Employee's bank account number for direct deposit, as defined in the Bank Accounts table of the Manage Personal PaymentMethods task.

Account Type



82

Identifies the account as either checking or savings. Defined in the Manage Personal Payment Methods task.

Company


Deposit Amount

Amount of each direct deposit, as defined in the personal payment method.

Effective Date


Employee ID


Where:






While not passed on the extract, this parameter is used to derive the Full Deposit value on the extract.


Effective end date of the direct deposit.

Payment Priority

Processing order of the personal payment method. While this parameter is not passed on the extract, it's used to derive theFull Deposit value on the extract.

Payroll


Payroll Frequency


Record Type

Identifies this record as delivering information specific to direct deposits on the extract. For use by the third-party provideronly.

Transit Number



83

Employee's personal bank transit number.

Voluntary Deductions RecordsThe values for these parameters are derived from the input values for voluntary 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

Effective Date

Effective_Date

String

Text

Deduction Code

Deduction_Code

Database item group

Text

Indirect Only

Indirect_Only

Database item group

Text

Processing Type

Processing_ Type

Database item group

Text

Usage Level

Usage_Level

Database item group

Text



Database item group

Number

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_ Type

Rule

Text

Third-Party Deduction Code

Third_ Party_ Deduction_ Rule

Rule

Text

Element Entry ID

Element_ Entry_Id

Database item group

Number

Element Frequency

Element_ Frequency

Rule

Text

Deduction Code


Deduction End Date




84

Effective Date

Start date of the element entry.



Element Entry ID


Element Frequency


Element Type ID

Internal ID used to identify the element definition.

Entry Value


Indirect Only


Input Value Name

Name of the input value.

Processing Type


Reserve Value



Three-character code used by ADP PayForce for the nonrecurring deduction. Defined in an input value on the deductionelement.


Used as a column header in the output file. Value must be "Adjust Ded Code" and is defined in an input value on thededuction element.

Usage Level




85

Extract Delivery OptionsDefines the extract output, such as PDF, XML file, 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 file containing recurring element data.

US ADP PayForce Nonrecurring

Name of the ADP Connection for PayForce output file containing nonrecurring element data.

US ADP PayForce XML

Name of the XML file. For use in cases where you want to use a third-party provider other than ADP.

Third-Party Ad-Hoc Extract DefinitionThis topic describes the various component data groups of the US ADP PayForce third-party ad hoc extract definition for theOracle Fusion Global Payroll Interface for the United States.

This extract has been provided for ADP PayForce and ADP Connection for PayForce users. You must modify this extractthrough the Manage HCM Extract Definitions task if:

• Your payroll installation requires additional information be sent to ADP Connection for PayForce

• You are using a different third-party provider

Use the provided tree structure to configure the data groups, extract records, and data elements as needed. You define whatyou want to extract, how it is extracted, and how you want to deliver the extracted data.

The US ADP PayForce third-party ad hoc extract definition consists of the following data groups:

Main BlockThis data group contains the four primary groups of the extract definition. To view its specific parameters, you must select theappropriate 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.

Job Data

Contains parameters related to jobs.



86

Direct Deposit RecordsThis data group contains information about personal payment methods.


Record Type

Record_Type

String

Text

Employee ID

Employee_ID

Database item group

Text

TRU

TRU

Database item group

Text

Payroll

Payroll

Database item group

Text

Payroll Frequency

Payroll_ Frequency

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


Deduction_ End_Date

Database item group

Date

Account Type

Account_Type

Database item group

Text

Effective Date

Effective_Date

String

Text


Maximum_ Payment_ Priority

Database item group

Number

Previous Payment Method EndDate

Previous_ Payment_ Method_End_Date

Rule

Date

Account Number


Account Type


Deposit Amount




87

Effective Date


Employee ID


Where:

• AA are the first two characters of the employee's first name. If the first name is missing, FF is used instead.



For example: "John Smith 123-45-6789" could become JOSM5398647.


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 is not passed on the extract, it is used to derive theFull Deposit value on the extract.

Payroll


Payroll Frequency


Previous Payment Method End Date

Date when a payment method's bank account is changed, as defined through the Manage Personal Payment Methods task.

Record Type




TRU




88

Earnings RecordsContains parameters related to earnings records.


Element Entry End Date

Element_ Entry_ End_Date

Database item group

Date

Entry Value

Entry_Value

Database item group

Text

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

Rule

Number


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

Database item group

Number

Usage Level

Usage_Level

Database item group

Text

Converted Value

Calculates element entries based on the element's periodicity.


Internal assignment ID of the employee attached to the element entry. Not passed to the third-party provider.

Element Entry End Date

End date of the element entry, as defined through the Manage Element Entries task.

Element Entry ID

Internal ID of the element entry.



89

Element ID


Element Name

User-defined element name, as defined on the Manage Elements page.


Identifies the element as recurring or nonrecurring.

Entry Value

Value passed on the element entry.

Periodicity

Element frequency.

Salary Conversion Rule

Salary amount.


Three-character code used by ADP PayForce for the nonrecurring earning. Defined in an input value on the deductionelement.


ADP PayForce earning code type assigned to this earning. Defined in an input value on the earnings element.

Usage Level

Identifies the level at which the element was entered: payroll relationship, employment terms, and assignment.

Earnings and Deductions Element EntriesThis node contains four subordinate data nodes for earnings and deductions element entries. To view its specific parameters,you must select the appropriate subordinate nodes elsewhere in the tree.

Earnings Data

Contains internal identifiers related to earnings records.

Taxable Benefits Data

Contains internal identifiers related to taxable benefits.

Pre-Statutory Deductions Data

Contains internal identifiers related to prestatutory deduction records.



90

Voluntary Deductions Data

Contains internal identifiers related to voluntary deduction records.

Earnings and Deductions RecordsContains parameters related to earnings and deductions record details.


Record Type

Record_Type

String

Text

TRU

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

Third_Party_ID

Database item group

Number

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 is not used by ADP.

Employee ID


Where:





Payroll


Payroll Frequency



91



Reporting name of the payroll definition, as defined in the Manage Payroll Definitions 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


HR RecordsThis data group contains HR-specific information about the employer and employees.


Record Type

Record_Type

String

Text

TRU

TRU

Database item group

Text

Payroll

Payroll

Database item group

Text

Payroll Frequency

Payroll_ Frequency

Database item group

Text

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 Suffix

Name_Suffix

Database item group

Text

Name Prefix Name_Prefix Database item group Text



92


Preferred Name

Preferred_Name

Database item group

Text

Address Line 1

Address_Line1

Database item group

Text

Address Line 2

Address_Line2

Database item group

Text

Address Line 3

Address_Line3

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


Address_ Lin2_Other

Database item group

Text


Address_ Lin3_Other

Database item group

Text

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



93


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

Employee ID

Employee_ID

Database item group

Text

Citizenship Status

Citizenship_ Status

Database item group

Text

Citizenship

Citizenship

Database item group

Text



Database item group

Text



Database item group

Text

Address Line 1




Address Line 2




Address Line 3






94

Birth Date


Citizenship


Citizenship Status


City


City Other


Country


Country Other


Date of Death


E-Mail Address

Employee's email address, as defined in the Person Information page.

Employee ID


Where:





Ethnicity


First Name



95


Gender


Home Phone



Area code of employee's home phone number, as defined in the Person Information page.

Last Name


Marital Status


Middle Name


Name Prefix


Name Suffix


Original Hire Date

Employee's original date of hire, as defined in the Enterprise section of the Service Dates region of the Manage WorkRelationship page.

Payroll


Payroll Frequency


Postal Code


Postal Code Other




96

Preferred Name


Record Type


SSN


State


State Other


TRU


Work Phone



Area code for employee's work phone number, as defined in the Person Information page.

Visa Number


Visa Expiration Date


Visa Type


Voluntary Deductions RecordsThe values for these parameters are derived from the input values for voluntary deduction elements.


Reserve Value

Reserve_Value

Database item group

Text



97


Entry Value

Entry_Value

Database item group

Text

Deduction End Date

Deduction_ End_Date

Database item group

Date

Effective Date

Effective_Date

String

Date

Reporting Name

Reporting_Name

Database item group

Text

Autoindirect Only

Autoindirect_ Only

Database item group

Text



Database item group

Text

Usage Level

Usage_Level

Database item group

Text



Database item group

Number

Element Entry ID

Element_ Entry_ID

Database item group

Number

Element Frequency

Element_ Frequency

Rule

Text


Third_ Party_ Deduction_ Type

Rule

Text


Third_ Party_ Deduction_ Rule

Rule

Text

Autoindirect Only


Deduction End Date


Effective Date




Element Entry ID


Element Frequency




98



Entry Value


Reporting Name

Element's reporting name, as defined on the Manage Elements task.

Reserve Value



Three-character code used by ADP PayForce for the nonrecurring deduction. Defined in an input value on the deductionelement.


Used as a column header in the output file. Value must be Adjust Ded Code and is defined in an input value on thededuction element.

Usage Level


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

Goal Amount


Pre-Statutory Deductions RecordsThe 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

Effective Date Effective_Date String Text



99


Reporting Name

Reporting_Name

Database item group

Text

Autoindirect Only

Autoindirect_ Only

Database item group

Text



Database item group

Text

Usage Level

Usage_Level

Database item group

Text



Database item group

Number

Element Entry ID

Element_ Entry_Id

Database item group

Number

Element Frequency

Element_ Frequency

Rule

Text

Autoindirect Only


Deduction End Date

End data of the element entry.

Effective Date




Element Entry ID


Element Frequency




Entry Value


Reporting Name



100


Reserve Value


Usage Level


Taxable Benefits Goal Amount RecordsThis data group contains information in the Goal Amount special input value. This parameter is used when the deductionelement has a maximum threshold.

Goal Amount


Taxable Benefits RecordsThis data group contains information derived from Imputed Earnings elements. Some of these parameter values are derivedfrom the element definition, 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

Effective Date

Effective_Date

String

Text

Reporting Name

Reporting_Name

Database item

Text

Autoindirect Only

Autoindirect_ Only

Database item

Text


Processing_ Type

Database item

Text

Usage Level

Usage_Level

Database item

Text



Database item

Number

Element Entry ID

Element_ Entry_Id

Database item

Number

Element Frequency

Element_ Frequency

Rule

Text



101

Autoindirect Only


Deduction End Date


Effective Date




Element Entry ID


Element Frequency



***Identifies the element as recurring or nonrecurring, as defined during element definition.

Entry Value


Reporting Name


Reserve Value


Usage Level

Identifies the level at which the element is assigned. Valid values are Payroll Relationship, Assignment, and Term.

Voluntary Deductions Goal Amount DetailsThis data group contains information in the Goal Amount special input value. This parameter is used when the deductionelement has a maximum threshold.

Goal Amount




102

Job Extra BlockThis data group contains FLSA information related to the employees.

FLSA Status


Job RecordsThis data group contains job-specific information for the employer and employees.


Record Type

Record_Type

String

Text

Hire Date

Hire_Date

Database item group

Date



Database item group

Date

Termination Date

Termination_ Date

Database item group

Date

Home Department

Home_ Department

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

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


Database item group

Text

Employee Type

Employee_Type

Database item group

Text

Standard Hours Standard_Hours Database item group Text



103


TRU

TRU

Database item group

Text



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

Employee ID

Employee_ID

Database item group

Text

Supervisor ID

Supervisor_ID

Database item group

Text

Salary Basis Amount


Database item group

Number



Database item group

Text



Employee ID


Where:





Employee Type


Employment Category

Employee employment category, as defined in the Assignment Category field of the Job Details section of the AssignmentDetails region of the Manage Employment page.

Employment Status



104

Employee's employment status (full time, part time, regular or temporary, and so on). Defined in the Assignment Categoryfield 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


Payroll


Payroll Frequency


Record Number



Record Type



105

Identifies this record as delivering job-specific information about the extract. For use by the third-party provider only.

Retirement Date


Salary Basis Amount




SSN


Standard Hours




Supervisor ID



Where:





Termination Date


TRU




106

Extract Delivery OptionsDefines the extract output, such as PDF, XML file, 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 file containing recurring ad hoc element data.

US ADP PayForce Ad-Hoc Nonrecurring

Name of the ADP Connection for PayForce output file containing nonrecurring ad hoc element data.

US ADP PayForce XML

Name of the XML file. For use in cases where you want to use a third-party provider other than ADP.

Recurring Periodic Output FileThis topic describes the format of the recurring periodic output file for the US ADP Connection for PayForce third-partyperiodic extract.

The output file consists of the following sections:

HR RecordsContains HR-specific 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

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 Suffix

Name_Suffix

NAME_PREFIX

Name Prefix

Name_Prefix



107


PREFERRED_NAME

Preferred Name

Preferred_Name

STREET1

Street 1

Street1

STREET2

Street 2

Street2

STREET3

Street 3

Street3

CITY

City

City

STATE

State

State

ZIP

Postal Code

Zip

COUNTRY

Country

Country

STREET1_OTHER

Street 1 Other

Street1_Other

STREET2_OTHER

Street 2 Other

Street2_Other

STREET3_OTHER

Street 3 Other

Street3_Other

CITY_OTHER

City Other

City_Other

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



108


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

BIRTHDATE


CITIZENSHIP


CITIZENSHIP_STATUS


CITY


CITY_OTHER


Company


COUNTRY


COUNTRY_OTHER


DT_OF_DEATH



109


EMAIL_ADDRESS

Employee's work email address, as defined in the Person Information page.

EMPLID


Where:





FIRST_NAME


HOME_PHONE


LAST_NAME


MAR_STATUS


MIDDLE_NAME


NAME_PREFIX


NAME_SUFFIX


ORIG_HIRE_DT

Employee's original date of hire, as defined in the Legal Employer section of the Service Dates region of the Manage WorkRelationship page.

PAY FREQUENCY




110

PAYROLL


PREFERRED_NAME


RACE_ETHNICITY


Record Type


SEX


SSN


STATE


STATE_OTHER


STREET1


STREET1_OTHER


STREET2


STREET2_OTHER


STREET3




111

STREET3_OTHER


VISA_EXPIRE_DT


VISA_NBR


VISA_TYPE


WORK_PHONE


ZIP


ZIP_OTHER


Job RecordsContains job-specific information for the employer and employees.


Record Type

Record Type

Record_Type

EMPLID

Employee ID

Employee_ID

Company

Company

Company

PAYROLL

Payroll

Payroll

PAY FREQUENCY

Payroll Frequency

Payroll_ Frequency

EMPL_RCD_NBR

Record Number

Record_Number

HIRE_DT

Hire Date

Hire_Date

CMPNY_ SENIORITY_DT



TERMINATION_DT Termination Date Termination_ Date



112


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

LOCATION

Location Code

Location_Code

ASSIGN_CATG

Employment Category


FLSA_STATUS

FLSA Status

FLSA Status

EMPL_TYPE

Employee Type

Employee_Type

STD_HOURS

Standard Hours

Standard_Hours

STD_ HOURS_ FREQUENCY






Salary Basis Amount

Salary Basis Amount


HOME_ DEPARTMENT

Home Department

Home_ Department

WORKERS_ COMP_CD

intentionally left blank


ASSIGN_CATG

Designates the employee's employment status (full time, part time, regular or temporary, and so on). Defined in theAssignment Category field of the Job Details section of the Assignment Details region of the Manage Employment page.

CMPNY_SENIORITY_DT


Company



113


EMPL_RCD_NBR



EMPL_STATUS

Employee's status, as defined in the Assignment Status field of the Assignment Details region of the Manage Employmentpage.

EMPL_TYPE


EMPLID


Where:





FLSA_STATUS


HIRE_DT


HOME_DEPARTMENT


JOBCODE


JOBTITLE




114

LOCATION


LOCATION_NAME


PAY FREQUENCY


PAYROLL


Record Type

Identifies this record as delivering jobs-specific information about the extract. For use by the third-party provider only.

RETIRE_DT


Salary Basis Amount




STD_HOURS


STD_HOURS_FREQUENCY


SUPERVISOR_ID



Where:





115



TERMINATION_DT


WORKERS_COMP_CD

Placeholder for future functionality. Intentionally left blank.

Earnings and Deductions RecordsContains earnings and deductions-specific information for the employer and employees. This includes recurring earnings.


Record Type

Record Type

Record_Type

EMPLID

Employee ID

Employee_ID

Company

Company

Company

PAYROLL

Payroll

Payroll

PAY FREQUENCY

Payroll Frequency

Payroll_ Frequency

EMPL_RCD_NBR

Record Number

Record_Number

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 defined in the Manage Legal Reporting Unittask.

Element Amount



116

Represents the earning or deduction amount, as defined by the element's input value identified with the Primary Input Valuespecial purpose. Either this value or the Element Percentage value is populated in the file, but not both.

Element End Date


Element Name


Element Percentage

Represents the earning or deduction percentage, as defined by the element's input value identified with the Primary InputValue special purpose. Either this value or the Element Amount value is populated in the file, but not both.

ELEMENT FREQUENCY

Periodicity of the earning or deduction, as defined by the element's input value identified with the Periodicity special purpose.ADP does not use this value.

EMPL_RCD_NBR



EMPLID


Where:





GOAL_AMT


PAY FREQUENCY


PAYROLL




117

Record Type


Direct Deposit RecordsContains direct deposit-specific information for the employer and employees.


Record Type

Record Type

Record_Type

EMPLID

Employee ID

Employee_ID

TRU

Company

Company

PAYROLL

Payroll

Payroll

PAY FREQUENCY

Payroll Frequency

Payroll_ Frequency

EMPL_RCD_NBR

Record Number

Record_Number

FULL_DEPOSIT

derived

derived

TRANSIT_NBR


Transit_Number

ACCOUNT_NBR

Account Number

Account_Number

DEPOSIT_AMT

Deposit Amount

Deposit_Amount


Deduction End Date

Deduction_ End_Date

ACCOUNT_TYPE

Account Type

Account_Type

ACCOUNT_NBR


ACCOUNT_TYPE


DEPOSIT_AMT




118

Note: If this attribute is set to any value greater than zero, the FULL_DEPOSIT attribute cannot be set to Yes.For example, the employee wants 100 USD to be deposited into a savings account and the rest into a checkingaccount. Therefore, for their first 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


Where:





FULL_DEPOSIT

Identifies which direct deposit record is the last one that receives all remaining money.

Note: If this attribute is set to Yes, the DEPOSIT_AMT attribute cannot 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 first direct deposit record, set DEPOSIT_AMT to "100" and FULL_DEPOSIT to "N". For thesecond 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



119


TRANSIT_NBR


TRU


Nonrecurring Periodic Output FileThis topic describes the format of the nonrecurring periodic output file for the US ADP PayForce third-party periodic extract.

The output file consists of the following section:

Nonrecurring RecordsContains information for the employees' nonrecurring earnings and deductions.

Note: The US ADP PayForce third-party periodic extract pulls the following nonrecurring earnings anddeductions types only:

• Voluntary deductions Nonrecurring pretax deductions are not included.• Supplemental earnings Nonrecurring regular and imputed earnings are not included.• Flat amount earnings Hours * rate earnings elements are not included.


CoCode


Payroll_ Reporting_ Name

Batch Id



File #

Third-Party ID

Third_Party_ID

Earnings 3 Code


RULE_ EARNING_CODE

Earnings 3 Amount

RUN

RUN

Earnings 4 Code


RULE_ EARNING_CODE

Earnings 4 Amount

RUN

RUN

Earnings 5 Code


RULE_ EARNING_CODE

Earnings 5 Amount

RUN

RUN



120


Adjust Ded 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 Codeinput value.

Adjust Ded Amount

Amount of the deduction.

Batch Id

This field is intentionally left blank and is automatically populated by the ADP for PayForce External Paydata Interface Programprocess upon receipt.

CoCode

First three characters of the payroll reporting name as defined in the Manage Payroll Definitions 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


File #



Chapter 6Payroll Interface for ADP Workforce Now

121

6 Payroll Interface for ADP Workforce Now

ADP Workforce: OverviewTo set up payroll interface for ADP-WFN, define the value sets and the object group for payroll relationship. Once you definethe requirements for payroll relationship, associate the employees to payroll. Use the delivered Run Payroll Interface forADP Workforce Now flow pattern to run the payroll interface extract process.

Define Value SetsCreate value sets for multiple company details. The application delivers theORA_HRY_PAYROLL_COMPANY_CODE_VALUESET value set.

Enter values for ORA_HRY_PAYROLL_COMPANY_CODE_VALUESET company code value set.

1. Navigate to the Setup and Maintenance work area.2. Search for and select the Manage Value Sets task.3. Search for the ORA_HRY_PAYROLL_COMPANY_CODE_VALUESET value set.4. Click Manage Values.5. On the Manage Values page, click Create.6. Enter each company code as a new value.7. Click Save and Close.

Define Object GroupsExtract the multiple payroll group employee data in a single file and use the Manage Object Groups task to group thepayroll 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 were not included in the extract or that must be extracted again.

Associate Employees to PayrollSpecify the payroll to which the employee must be mapped in the Payroll Details sub section of the Assignment section whilehiring an employee using the Oracle Fusion HCM hire flow. On the Manage Payroll Relationships page, you can associatenewly-hired employees to the respective payroll.

Run the ADP Workforce Now Interface ProcessUse the Submit HCM Extract Task from the Data Exchange work area to execute Run Payroll Interface for ADP WorkforceNow extract process.



122

Delivered Contexts and SegmentsUse the ORA_HRY_GPI_WFN_EMP_INFO context to capture employment details of employees at the assignment level. Alternatively,you can use the ORA_HRY_GPI_WFN_PAYROLL_ADDL_INFO context accommodate additional payroll agreement custom fieldattributes.

This table shows the contexts that are available under the Assignment EIT Information EFF flexfield, which is associated withthe respective PER_ASSIGNMENT_EXTRA_INFO_M table.

You can enable and deploy these contexts.

FLEXFIELD NAME PER_ASSIGNMENT_EIT_EFF PER_ASSIGNMENT_EIT_EFF

Flexfield 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 EmploymentInformation

GPI Workforce Now Extended PayrollAdditional Information

Behavior

Single Row

Single Row

Enabled

Yes

Yes

1. Navigate to the Payroll work area.2. Click Checklist.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 flow.6. Click Next.7. On the Enter Parameters page, enter 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 Employment Information.

Subcomponent

Select the required subcomponent.

8. Click Submit.9. You can repeat these steps to enable Extended Payroll Additional Information.



123

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.

Enable the ContextBefore you enable the context, consult ADP.

1. Navigate to the Setup and Maintenance work area.2. Search for and select the Manage Extensible Flexfields task.3. On the Manage Extensible Flexfields page, search for the Assignment EIT Information EFF flexfield.4. Click Deploy Flexfield.5. Ensure that the deployment completes successfully and the deployment status column displays a green tick mark.

Delivered LookupsThe delivered LOVs are either lookup codes with specific lookup types or value sets. For example, Pay Frequency Code is alookup code, but Company Code and Client Code are value set values.

Attribute WFN-LOVs GPI-LOVs Description Remarks

Gender

• M- MALE• F- FEMALE• N- Not Specified

• F• M

• Female• Male

If you do not specifya value, the ADPapplication translates itas N.

Pay Frequency Code

• B-Biweekly• D-Daily• M-Monthly• S-Semimonthly• W-Weekly

• Bi-Monthly• Bi-week• Calendar Month• Quarter• Semi-Month• Semi-Year• Week• Year

• Bimonthly• Biweekly• Monthly Calendar• Quarterly• Semimonthly• Semiannually• Weekly

The application createsthese time periods.

• Bimonthly: Timeperiods occurringonce in twomonths.

• Biweekly: Timeperiods every 14days.



124


• Semimonthly:Time periodsoccurring twice amonth.

• The applicationdoes not supportDaily.

Education Level

• ASC- Associate• DOC- Doctorate

and above• DPL- Diploma• GRD- Graduate• MS- **• NI- Not Indicates• UGR - Under

Graduate

• BACHELOR• CA_10• CA_20• CA_80• DOCTORAL

MASTERS

• Bachelor Degree• High school

graduate• Associate degree• Other education

level• Doctorate Master

Degree

This is a 3 character field.

EEO Ethnic Code

• White• African American• Hispanic or Latino• Asian• Indian or Alaskan• Hawaiian/Pacific

Islander• Two or more

races

• 1• 2• 3• 4• 5• 6• 7• 8

• White• Two or more

races• Black or African• American• Hispanic or Latino

Asian• Native Hawaiian

or other PacificIslander

• American Indian orAlaska Native

• Not disclosed

The application translates'2' to '9', '3' to '2', '4' to'3', '5' to '4', '7' to '5'.

Salutation

• Dr.• Hon.• Miss.• Mrs.• Mr.• Ms.• Msgr.• Rabbi.

• DR.• MS.• MISS• MRS.• MR.

• Doctor.• Ms.• Miss.• Mrs.• Mr.

The application checksif upper or lower casemakes a difference.

EEOC Job Code

• 1- First/Mid-Level Officials andManagers

• 2- Professionals• 3- Technicians• 4- Sales Workers• 5- Administrative

Support Workers• 7- Operatives• 8- Laborers and

Helpers• 9- Service

Workers• A- Executive/

Senior Level

• FIR/MIDOFFICIAL• PROFESSIONAL• TECHNICIAN• SALES• ADMIN• CRAFTWORKER• OPERATIVE• LABOURER• SERVICE EXECS• MIDLEVEL

• First, middlelevel officials andmanagers

• Professionals• Technicians• Sales workers• Administrative

support workers• Craft workers• Operatives• Laborers and

helpers• Service workers• Executive or

senior level

If you do not specifya value, the ADPapplication translates itas N.



125


Officials andManagers

officials andmanagers

• First or mid levelofficials andmanagers

Employee Type

• Full Time• Part Time

• PR• PT• FT• FR

• Part-time regular• Part-time• Temporary• Full-time

temporary• Full-time regular

User defined. 4characters. Theapplication does nottranslate. Ensure that thevalues are in the ADPtable.

Hire Reason

• CDD• CDI• NEWHIRE

• Fixed-term - CDD• Permanent - CDI

Hire to fill vacantposition.

Pass the Action Codeand Action Reason toWFN for reference.

Termination Reason

• WORK_RELATED• DISMISSAL

WORK_RELATED• REDUND_ECONOMIC• RESIGNATION• RESIGN_PERSONAL• RETIRE_VOLUNTARY• RETIRE_UNVOLUNTARY• WORK_RELATED• TERMINATE_END_CDD• TERMINATE_MUTUAL

• Work Incidentor Work RelatedIllness Dismissal

• Work Incidentor Work RelatedIllness

• Redundancyfollowingeconomicrecovery

• Resignation• Personal Reasons• Voluntary

retirementInvoluntaryretirement

• Work Incidentor Work RelatedIllness

• End of fixed termcontract Contractbreach by mutualagreement

Bank Deposit DeductionType

• S-Saving• C-Checking

CHECKINGMONEYMRKT SAVINGS

Checking Money marketSavings

The applicationtranslates Checking toC and Savings to S.MONEYMRKT is invalid.

Creating Payroll ElementsThis example shows how to define elements for a US legislative data group where the country extension is set to PayrollInterface.

The following table summarizes key decisions for each element that you define and provides the selections for this example.



126

Decision to Consider In This Example

What is the primary classification? One of these choices:

• Standard Earnings• Supplemental Earnings• Taxable Benefits• Pretax Deductions• Voluntary Deductions

Information elements aren't supported.

At which employment level should this element be attached? Select the appropriate level. Typical examples are:

• Payroll relationship level for deductions and benefits elements• Assignment or terms level for salary, pension, and social

insurance elements• Assignment level for overtime rules, rates, and bonus elements

Check whether your third-party payroll provider can handle terms-levelinformation.

Does this element recur each payroll period, or does it require explicitentry?

Select Recurring or Nonrecurring.

What are the values to enter for deduction elements?

Period Deduction Amount Goal Amount

Defining an ElementBefore defining an element, confirm that your country extension is set to Payroll Interface on the Manage Features byCountry or Territory page. This setting controls the behavior of important payroll-related features, such as element templates.



◦ 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 classification that matches the purpose or use of the payroll element.


Recurring base pay

Annual salary, hourly earnings

Standard Earnings

Recurring payments

Allowance

Standard Earnings



127


Nonrecurring payments

Bonus

Supplemental Earnings

Recurring or nonrecurring voluntarydeductions

Savings plans, charitable contributions, oruniform deposit

Voluntary Deductions

5. In the Category field, select Standard.6. Select the secondary classification that corresponds to the selected primary classification.

Example Purpose or Use Secondary Classification

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 the fields as shown in this table, and then 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.

Effective 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 theelement automatically receive it?

No


First Standard Earnings Date





128

Field Sample Value


Select the appropriate level, such as terms or assignment level for salary.


Recurring or Nonrecurring

Process the element only once in eachpayroll period?

Yes

Can a person have more than oneentry of this element in a payrollperiod?

No

Process and pay element separately orwith other earnings elements?

Does this element have a limit on the amount which is exempt from Federal Tax?

Does this element have a limit on theamount which is exempt from FederalTax?

No

Does this element have a limit on theamount which is exempt at state level?

No

9. Click Next.10. On the Additional Details page, complete the details as shown in the following table:

Field Value

What is the default periodicity of thiselement?

Bimonthly

Periodicity Conversion Rule

Standard Rate Annualized

11. Verify the information is correct, and then click Submit.

Setting Up Values for Deduction ElementsConfigure values for deductions and select the special purpose Primary Input Value as one of the values.

Optionally, for recurring elements, specify a value that limits the amount deducted for a value using a goal amount.

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 the following values.

Field Value

Name Name of the value, such as Period Deduction Amount



129

Field Value

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 Amount5. Click Save.6. Click Submit.

Setting Up Element EligibilityOn the Element Summary page, update the newly defined 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 field, enter the element name with the suffix: Open.5. In the Eligibility Criteria section, select All payrolls eligible.6. Save and submit the element.

Related Topics


Business Requirements for ADP-WFNSome features, such as File ID and Position ID don't require any specific data set up or configuration.

Paid and NonPaid EmployeeThe application extracts both employee categories in the same file. However, the required attributes have certain limitations.

This table describes these employee categories

Employee Category Description

Paid Employee

Configured with payroll relationship and element mapping. The extraction passes the element entryvalues and payment details. Such details are used in third-party payroll system for processing andmaking payment.




130

Employee Category Description

Nonpaid Employee

The cloud HR application maintains nonpaid employees by assigning them to a payroll relationship.However, the application does not maintain the Compensation, Statutory, and Bank related details.

File IDEach employee has a unique File ID for their employment record. The application stores this information in the AssignmentNumber field too. You can store the File ID into the person number. In such a case, the application automatically generatesthe Assignment Number and also restricts the field as non-editable. Use the File ID to derive the position ID.

Scenario 1

If you enter File ID in the Person Number field, then the application automatically generates the Assignment Number byadding Employee Type with Person Number.

Scenario 2

When you enter File ID in the Assignment Number field, do not start with alphabets. The application supports multipleassignments

Position IDThe Position ID is a unique 9 character attribute that is derived from the combination of Company Code and File ID. Note: ThePosition ID is derived from File ID.

You can identify the File ID in two ways

• Consider the File ID from the Assignment Number field if Assignment Number does not start with alphabets.

• Consider the Person Number as File ID if the Assignment Number field start with alphabets.

The first 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 file ID is less than 6 digit, then pad with leading zeros)

• Position 10 => 'N' if the assignment status is Active- no payroll else blank.

Then the derived Position ID is T24000786N.

During extraction, the application derives the Position ID from the Company Code, Assignment Number, and AssignmentStatus. If Assignment Status = Active-No Payroll, the application does not either display or store the Position ID.

Element MappingThe application maps elements based on the on the standard element template delivered for US localization. When creatingelements:

• Add the additional input value to attach the goal limit and goal number to the deduction element.



131

• Enter the element name to extract to the third-party payroll supplier in the Reporting Name field.

Element Eligibility and Input ValuesWhen defining a deduction element, create and provide these input values for each deduction element.

Input Value Description

Deduction value

• Identify whether the element is deducting a flat amount or percentage.• Use this input value to track the amount of the deduction.• For this input value, set the special purpose field as Primary Input Value.

Third-Party Goal Limit

• Define values for each of the Goal Limit associated WFN deduction codes.• This is optional for deduction element.

Third-Party Goal Number

• Define values for each of the Goal Number associated WFN deduction codes.• This is optional for deduction element.

Termination and Rehire Requirements for ADP WFNWhen you terminate an employee, the application updates the employee's payroll records accordingly. These scenariosexplain the impact of a termination.

HR Records

• Till and including the actual termination date, the status of the employee records remains Active.

• From the next day after the termination date, the status of the employee records becomes Inactive.

Payroll Records

The duration until which the payroll relationship remains open depends on the payroll relationship rule that is defined by therespective country.

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 toan employee till the Final Close date. This means that the application processes the employee in a payroll till their Final Closedate.



132

When terminating employees, choose the final close date in such a way that the application can process employee'sseverance 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 cannot reverse the termination process as the integration supports only deleted transactions forElements and Bank accounts. Reversing a termination process might be considered in future releases.

RehireIf the hire date is within the current extract period, the application extracts the employee. In case of rehire, the applicationconsiders the work relationship of that rehire process. If the hire date of this work relationship is within the current extractperiod, then the application includes the employee in the extract. The application retains the employee's person number ifthey are rehired within the Legal Employer.

Note: You must enter the employee's prior employment final close date before you rehire employees.

TransferIn case of a transfer of an employee, the application terminates the current work relationship and creates a new workrelationship. In this case, the extraction file has two records.

Leave InformationThough the Absence application records the leave information as a single record, when the interface application extracts thedetails, it separates them as a separate transaction.

Rate Type ChangeThe 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 fieldblank.

• 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 existingrate type has a delete record and a new record for the proposed change rate type in the extractions.



133

How You Split Personal Payment MethodsBy default, on the Manage Personal Payment Methods page, you can enter bank account details for existing banks andbranches, but you cannot create new banks and branches. Similarly payroll managers, payroll administrators, and payrollcoordinators can enter account details for the employees they handle, but they cannot create new banks and branches.

Note:• To enable the create option for any of these roles, add the Bank and Branch Management duty role to the

relevant role.• You cannot 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.

Using Fixed Amount PaymentsBarbara Franklin wants to save 600 before the next holiday season and wants the money transferred electronically as part ofher regular payroll payment processing. She is paid semimonthly and can afford 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 hersavings account and sets the amount to 100 . Because Barbara's net payment amount is approximately 1,000 each payrollperiod, the remaining amount of approximately 900 will be paid using her default payment method, which transfers her payrollpayment to her checking account. Before the holiday season, when Barbara decides to stop the transfers to her savingsaccount, she deletes the payment method.

Using Percentage PaymentsTerry Smith has a college fund set up for his children and wants to contribute to it each payroll period. Because Terryfrequently receives bonuses and sales commissions, his net payment amount is always changing. So, he decides to add apayment method that allocates four percent of his pay to the fund. By using a percentage rather than a fixed amount, Terrycan contribute to the fund at the same rate that he earns.



134


Chapter 7Payroll Interface Inbound Records

135

7 Payroll Interface Inbound Records

OverviewUse the HCM Data Loader to import processed payroll data and payslips from third-party payroll providers. Each importrecord is associated with a master record that specifies a payroll name and payroll period. The Inbound table stores theimported payroll information, while the document record stores payslips.

You can create your own reports using Oracle Fusion Transactional Business Intelligence (OTBI). Use the mentioned Subjectarea 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 specific messages

• Details of earnings and elements processed for employees

• Final payments made to employees

• Details of bank accounts to which payments are made

Extensible FlexfieldsOracle provides an extensible flexfield 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

Predefined segments are associated with these contexts. In addition to this extensible flexfield, you can also use extensibleand user-defined lookups to configure your inbound payroll interface with the third-party payroll provider.

Use the Manage Payroll Interface Extensible Flexfields task in the Setup and Maintenance work area to edit the PayrollInterface Inbound Record EFF flexfield. Contexts with predefined segments capture specific processed payroll values.

Payroll Interface Inbound RecordAfter a payroll is processed by your third-party payroll provider, the application extracts the results and configures them into adata file. Convert this data file to the HCM Data Loader required format.

This table shows the list of files to import your payroll data:



136

File Name Content

PayrollInterfaceInboundRecord. dat You must use this file name as the HCMData Loader recognizes only this filename.

Includes processed payroll information for employees included in the payroll run

PayrollInterfaceInboundRecord. zip After you create the data file, compressthe file with the .zip file extension. In thisscenario, you can create your own filename.

Compressed file that contains the data file

On the Manage Payroll Interface Inbound Records page, you can do these actions:

• Filter imported data by using one or more of the following criteria:

◦ Payroll Name

◦ Batch Name

◦ Name

◦ Record Type

◦ Person Number

◦ Record Owner Type

• Select Payroll Data in the Record Type field to view, add, edit, and delete these details:

◦ Payroll

◦ Payment

◦ Leave

◦ Messages received from third-party payroll providers

Payslip FilesUse the HCM Data Loader to import payslips as PDF files into your Oracle Fusion HCM application.

This table shows the list of files to import payslips:

File Name Content

DocumentsOfRecord. dat You must use this file name. The HCMData Loader utility recognizes only thisfile name.

Data file listing employees for whom payslips are being provided PDF file names

BlobFiles You must use this folder name. TheHCM Data Loader utility recognizes onlythis file name.

Folder that contains all the PDF payslip files



137

File Name Content

DocumentsOfRecord. zip In this scenario, you can create yourown file name.

Compressed file that contains both the data file and PDF payslip files

The import process looks for the PDF files based on the information contained in the data file. After you complete the importprocess, 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 field to view payslip data.

Related Topics

• Importing Payroll Data From Third-Party Payroll Providers: Procedure

• Overview of HCM Data Loader

• How Data Is Imported and Loaded

Managing Inbound RecordsUse 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. ClickView Payslips.

View Inbound Records1. 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 field, select the required batch.4. In the Record Type field, select Payroll Data.5. In the Record Owner Type field, 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.

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=23D32B32804017E5E05362C3F00AE8EF

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=3F4AB5B1B8751345E05362C3F00AE24B

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=34AD26A6331F6284E05362C3F00A1023



138

Processed Payroll ValuesThe 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 instandardized data from Payroll provider that is used for further reporting and analysis.

Context Segment Description

Absence Information

• Absence Name• Accrual Balance• Absence Unit• Absence Message

• Name of absence for the employee.• Number of leaves in balance.• Number of absences taken.

Configuring Extensible Flexfields and LookupsConfigure extensible flexfields for your inbound payroll interface to your third-party payroll processor.

Configure Payroll Interface Extensible FlexfieldsUse the predefined Payroll Interface Inbound Record EFF extensible flexfield to import processed payroll data from your third-party payroll provider. Use contexts with predefined segments to capture specific payroll values.

1. In the Setup and Maintenance work area, navigate to these tasks:



◦ Task: Manage Extensible Flexfields for Payroll

2. On the Manage Extensible Flexfields 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 EFFflexfield.

Context Context Sensitive Segments

Absence Information

Absence Name Absence Balance Absence Unit Absence Unit of Measure



139

Context Context Sensitive Segments

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 Classification Element Name Cost Center Current Amount Quarter-To-Date Amount Year-To-Date Amount Currency General Ledger Credit Account General Ledger Debit Account

Payslip Information

Net Payment Payslip View Date



140

6. Enter and search for the context name in the Display Name field.7. To edit Context Sensitive Segments, select Edit from the Actions menu.8. To create a context, select Create from the Actions menu.9. Click Save and Close.

10. Click Done.

Note: If you add any segments or contexts, save and deploy the flexfield on the main page.

Related Topics

• Overview of Extensible Flexfields

• Overview of Flexfield Deployment

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=98B7FA567B2B6126E040D30A68815145

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=98B7FA567B266126E040D30A68815145


Chapter 8Data Validation and Data Deletion Reports for Payroll Interface

141

8 Data Validation and Data Deletion Reportsfor Payroll Interface

Generating Data Validation ReportRun the Data Validation Report for Payroll Interface either in a stand-alone mode or as a consolidated process before youextract 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 singlepayroll as a parameter.

The Data Validation Report for Payroll Interface includes validations for both HR and payroll data.

Data GroupsThe 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 InterfaceUse 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.

Field Value to Enter

Payroll Flow An identifier for the process that is run. Choose any format to describe the payroll flow.



142

Field Value to Enter

Object Group

A predefined object group for which the report is run. The process retrieves a set of payrolls or payroll relationships that belong to the object group andperforms the defined validation for each relationship.

Payroll

Object group, Payroll, or Both.

Effective Date

An effective date for process.


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, on the toolbar, click the Refresh icon intermittently until you do.12. Click the Go to Task icon.13. On the Run Data Validation Report for Payroll Interface page, click Done to complete the submission.

Related Topics

• Adding Rules to Data Validation Reports: Worked Example

Generating Deleted Data ReportUse the Deleted Data report to report data that have been deleted from the HCM Cloud during the extraction period. Youcan use this report as a supplement to the ADP Global Payroll Interface output xml file to account for data changes for anextraction period.

This report is a part of the Standard ADP Global Payroll Interface consolidated flow and is automatically submitted when yousubmit the consolidated flow. You can run the report independently too.

Before You BeginThe Deleted Data Report is based on the Audit functionality. Enable audit on all objects that must be tracked for deletions.

Do these steps to enable audit.



◦ Functional Area: Application Extensions

http://www.oracle.com/pls/topic/lookup?ctx=fa19c&id=FA8F28D1C4566702E043B69BF40AFB77



143

◦ Task: Manage Audit Policies

2. On the Manage Audit Policies page, click Configure Business Object Attributes .3. On the Configure Business Object Attributes page, select HCM Payroll.4. Select Personal Payment Method. The attributes available for auditing are displayed on the right hand side of the

page under Audited Attributes section.5. In the Audited Attributes section, click Create.6. In the Select and Add Audit Attributes dialog box, search for the attributes that you want to audit and click OK.7. Click Save and Close.

Generate Deleted Data ReportUse 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 flow.

Process Start Date

Start date of the extraction window. Typically, this should be the same as the ADP Global PayrollInterface extraction window.

Process End Date

End date of the extraction window. Typically, this date should be the same as the ADP GlobalPayroll Interface extraction window.

Object Group

Identifies the payroll relationships to consider and should be same as the object group used in theADP Global Payroll Interface.

5. Click Submit.6. Monitor the process to completion and view the report output.

Related Topics





144


Glossary

145

Glossary

assignment

A set of information, including job, position, pay, compensation, managers, working hours, and work location, that defines aworker'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 theenterprise 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 payrollrelationship type in the same PSU, such as employee and contingent worker, multiple payroll relationships exist for thatperson.

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 apayroll 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, paymentsare 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 orthe employee's element eligibility ceases.


Glossary

146

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 anonworker, contingent worker, or employee work relationship.