Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.

Fusion Global Payroll: Payroll Batch Loader (PBL) FAQ and Troubleshooting Guide (Doc ID
2016702.1)

In this Document

Purpose
Questions and Answers
What is Payroll Batch Loader (PBL)?
Where can one find documentation on PBL and Initial Balance Upload?
What needs to be installed prior to using PBL?
What objects can be loaded via PBL?
What templates to use for which element classification?
How to Load Batch from File / Automation?
Can size limit be increased for Upload Batch from File?
How can a line in a file be skipped?
How do I create and transfer a batch?
How messages from custom fast formulas can be shown in PBL load log file?
PBL workbooks for Payroll Definitions, Payroll Relationships, Bank data, Globals, UDTs and Balance Groups
What tables hold PBL batches data?
SQL to validate payroll batch information including errors
SQL to validate bank load
SQL to validate bank branch load
SQL to validate external account load
SQL to validate personal payment method (PPM) load
How to migrate objects from one pod to another?
What documentation is available for Kronos and Ceridian time card integration?
Why Transformation formulas can be slow?
Can GET_TABLE_VALUE function be used in a Batch Loader type formulas?
Initial Balance Upload
Guides
How to undo Initial Balance Upload?
How to run several batches in parallel?
What type of encoding does PBL expect: UTF-8 or Windows-1252?
Does PBL support multithreading?
Troubleshooting Tips
Error: ADFDI-07528: An unexpected exception has occured. The UI Controller cannot initialize. The runtime session
will now abort.
Error: ORA-01841: (full) year must be between -4713 and +9999, and not be 0
Error: Formula ELEMENTENTRIES_BATCHLOADER_FF, line 46, either function GET_TABLE_VALUE does not exist or
the combination of parameter types does not match the statement
Error: PLS-00306: wrong number or types of arguments in call to 'CREATE_BANK_BRANCH' ORA-06550: line 1,
column 98
Errors when attempting to initiate the PBL spreadsheet by clicking Download button
Error: RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1: 10.4.4 403 Forbidden
 Error: ADFDI-05587: The client and server versions do not match
Slow Performance issue
Slow performance while trying to load Federal Tax withholding for employees
How to troubleshoot Initial Balance Upload performance issues
Initial Balance Upload errors
Error: The combination of balances is invalid for the load date
Error: The legislative data group specified for the batch does not exist
Errors loading Element Eligibility
Error: Failed to lock the record in table PAY_ELEMENT_TYPES_F with key oracle.job.Key[300000096957475 1900-
01-01 4712-12-31 ], another user holds the lock
Errors loading Element Entries
Error: Access denied (oracle.wsm.security.WSFunctionPermission)
Error: JBO-27019 or JBO-29000 The get method for attribute InputValue1
Errors loading Personal Payment Method
Error: JBO-Provide PayrollRelationshipNumber or PayrollRelationshipName
Error: JBO-Provided OrgPaymentMethodName is invalid for the Payroll Relationship
Error: JBO-27014: Attribute DataType in GlobalDEO is required
How to delete incorrectly loaded data?
How to get ADFDI diagnostics if none of the above works?
References

APPLIES TO:

Oracle Fusion Global Payroll - Version 11.1.8.0.0 and later

Oracle Fusion Global Payroll Cloud Service - Version 11.1.8.0.0 and later
Information in this document applies to any platform.

PURPOSE

<p >*Purpose
<span >Explain to the reader the purpose of the FAQ. Enter a clear description of what the questions and answers are trying
to achieve. Be precise. It is this section that will guide the reader to decide whether the document is applicable.

This document is designed to provide answers to some of the most frequently asked questions and troubleshooting tips
regarding Payroll Batch Loader within Oracle Fusion Applications.

QUESTIONS AND ANSWERS

If you are a Software-as-a-Service (SaaS) customer, there may be sections in this document that need not be
performed by you. Please log a Service Request in My Oracle Support for Oracle to do this for you.

What is Payroll Batch Loader (PBL)?

Oracle offers the Payroll Batch Loader (PBL) as the solution for loading Payroll data. This is an Excel spreadsheet with an
Oracle Web ADF Desktop Integration (ADF DI) add in for Excel.

The Desktop Integration must be downloaded prior to loading data.

The workbook itself must also be downloaded from the specific pod. These workbooks can be renamed for the specific code
levels.

The spreadsheet is able to connect to the server and maintain data in the Oracle Fusion Payroll batch tables. The batch lines
created are associated with ‘Task Actions’ that allow the ‘Transfer Batch’ process (available from the Payroll Checklists work
area), to identify the Payroll entity stored in the batch line and apply the appropriate API to create or update the entity in
Fusion. It is good practice only to work with one entity per batch. Since no data is ever stored in the spreadsheet (all the data
is saved to the server), there should never be a requirement to save the workbook locally. Consequently the same workbook
can be used for many batch loads.

For more information please refer to Note 1679257.1 How To download and Install ADF DI Excel Add-in for Fusion
Applications?

Back to Top

Where can one find documentation on PBL and Initial Balance Upload?

Integrating with Oracle HCM Cloud online user guide,

Oracle Global Human Resources Cloud Using Global Payroll guide, chapter 3 Manage Batch Uploads

Note 2030268.1 Oracle Fusion Payroll Batch Loader User Guide for Release 10

Note 2014778.1 Fusion Payroll: Payroll Batch Loader - Documentation about Load Batch from File
Note 1590004.1 Loading data using the Batch Loader – Technical Essay,
Note 2022585.1 Fusion US Payroll: How To Load Involuntary Deductions via Payroll Batch Loader
Note 2022994.1 Fusion Payroll: How to Create, Correct, Update, Delete and Zap Employee Tax Cards via Payroll Batch Loader
(PBL) for Release 9 and Higher

Note 1436612.1 Balance Initialization in Oracle Fusion Global Payroll

Note 1912298.1 Oracle Fusion HRMS (US): Balance Initialization
Note 1993400.1 Oracle Fusion HRMS (CA): Balance Initialization
Note 2000651.1 Oracle Fusion HRMS (UK): Balance Initialization

and Fusion Online Help.

Back to Top

What needs to be installed prior to using PBL?

The Payroll Batch loader uses a Microsoft Excel spreadsheet downloaded from the Fusion cloud to populate the Fusion Payroll
interface tables. Before using this you must have installed the Oracle ADF Desktop Integration add-in that enables the
workbook to send data to and from the database. For step-by-step instructions you should first read White Paper on PBL in
Note 1590004.1 Loading data using the Batch Loader – Technical Essay.

Rows that have been inserted via the PBL can then be transferred from the interface tables to the appropriate payroll entity
(See the Task Action Names and explanations below for the different Payroll entities).

This process must be submitted from the Payroll Checklists work area.

Back to Top

What objects can be loaded via PBL?

Objects that can be loaded via PBL are listed in below table. Please note that each task action has mandatory parameters. In
the loader spreadsheet mandatory parameters are marked with the star. Please check the white paper and PBL workbooks for
all mandatory fields for each task name. Please see online documentation for updated list of available tasks.

Task Name Task Action Name Notes

Bank Create Bank

This only loads Country Code, Bank
Name and Bank Number.

Refer to Payroll Batch Loader

Workbooks for Bank Data.

Bank Inactivate Bank

Delivered in release 10 February
Monthly Release Update (MRU).

Refer to Payroll Batch Loader

Workbooks for Bank Data.

Bank Branch Create Bank Branch

This only loads Country Code, Branch
Name, Branch Number and BIC / Swift
Code

The validation on BIC is as follows:

The number of characters entered must

be either 8 or 11. Enter a valid BIC
code.

The Branch Number is the Routing

Number in the US and must be a valid
routing number (length 9). If this is not
the case the following error occurs:

The Routing transit number is invalid.

Enter a correct value for the Routing
transit number. ORA-06512: at
"FUSION.PAY_BATCH_LDR_PKG", line
1542 ORA-.

Refer to Payroll Batch Loader

Workbooks for Bank Data.

Bank Branch Inactive Bank Branch

Delivered in release 10 February MRU.

Refer to Payroll Batch Loader

Workbooks for Bank Data.

External Bank Account Create External Bank Account

This entity has the following required
keys: Bank, Bank Branch and Person
Number.

NOTE: The account type value must be

from the lookup_code of
IBY_BANKACCT_TYPES lookup_type:
CHECKING, MONEYMRKT, SAVINGS,
UNKNOWN.
 Refer to Payroll Batch Loader
Workbooks for Bank Data.

External Bank Account Inactivate External Bank Account

Delivered in release 10 February MRU.

Refer to Payroll Batch Loader

Workbooks for Bank Data.

External Bank Account Add Person to Existing Account

Delivered in release 10 February MRU.

Refer to Payroll Batch Loader

Workbooks for Bank Data.

Payroll Personal Deduction Create Statutory Deduction Cards Delivered in release 10 February MRU.

Element Quick Create

Element Create Element Do not use Quick Create task for

element creation. Download Supported
via Create Batch for an Object process.

Element Update Element

Element Delete Element Note 1999279.1 Fusion Payroll: Need to

End Date the Element via the PBL and
There Is No End Date Column in The
Update Task.

Element Download Supported via Create Batch

Create Input Value for an Object process.

Element Update Input Value

Element Delete Input Value

Element Entry Create Element Entry

These Pay Batch Loads when used
manually from the Work Book are
straightforward as they are directly
linked to the element. Hence the PBL
rows are specific to that element.

TIP: Make sure it is possible to assign

the element entry to the person via the
application first. In other words the
Eligibility Criteria are being satisfied for
the employee.

Refer to Creating Element Entries Using

the Batch Loader: Worked Example.

Element Entry Update Element Entry This supports the correction and update
of element entries.

Element Entry This supports the purge or end dating

Delete Element Entry
of element entries. Please enter
mandatory parameters like Element,
Person number. For more information
please see Note 2093263.1 Fusion
Global Payroll: How to End Date or
 Delete Element Entry Via Payroll Batch
Loader.

Element Eligibility -
This task is a part of the configuration
and relatively low volume. This task can
be done manually in the Manage
Elements screen.

Payment Method Create Personal Payment Method

Effective Start should be employee's
latest hire date.

Values for Amount Type are P and M.

For more complex personal payment

method combinations, for example,
where a certain percentage goes to
savings and the remainder to Checking
the remainder must always be the last
payment method in the sequence. This
final payment method must have a
value of 100 for Percentage and a value
of P for Amount Type. This will appear
within the application without any
percentage but with a label of
‘Remaining Pay’.

There is no validation of percentages

adding to 100 as the percentages are
applied in sequence to whatever pay is
remaining after earlier methods have
been applied.

Payment Method Delete Personal Payment Method

Delivered in release 10 February
Monthly Release Update (MRU).

Payment Method End-Date Personal Payment Method

Payroll Definition Create Payroll Definition

Payroll Definition Update Payroll Definition Currently this only allows the correction
of existing records, where by the user
needs to pass the Effective Start Date
and Effective End Date of the existing
record.

Payroll Definition Delete Payroll Definition Currently this only allows the deletion of
existing records, where by the user
needs to pass the Effective Start Date
and Effective End Date of the existing
record.

Payroll Relationship Add Payroll

This task requires Assignment Number,
Payroll and effective date.

Note 1581723.1 Load and end date

payroll relationship: Fusion Global
Payroll: How To Load Payroll

Payroll Relationship
Balance
Balance Group
Balance Group
Cost Allocation
Fast Formula
Fast Formula
Fast Formula
Fast Formula Global
Object Group
Object Group
HCM User Defined Table
HCM User Defined Table
HCM User Defined Table
HCM User Defined Table
HCM User Defined Table
HCM User Defined Table
HCM User Defined Table
HCM User Defined Table
Upload Calculation Rules for Tax
Reporting and Payroll Statutory Unit
Upload Calculation Rules for Tax
Reporting and Payroll Statutory Unit
Upload Calculation Rules for Tax
Reporting and Payroll Statutory Unit
Upload Calculation Rules for Tax
Reporting and Payroll Statutory Unit
US Employee Earnings Distribution
Overrides
End Payroll
Initialize Balance
Add a Defined Balance
Remove a Defined Balance
Create Cost Allocation
Delete Cost Allocation
Create
Update
Delete
Create
Create
Delete
Create User-Defined Table
Update User-Defined Table
Create User-Defined Column
Create User-Defined Column Instance
Create User-Defined Row
Update User-Defined Column
Update User-Defined Column Instance
Update User-Defined Row
Update City Calculation Rules
Update County Calculation Rules
Update Federal Calculation Rules
Update State Calculation Rules
Upload Employee Earnings Distribution
Overrides
Relationship Data Via Payroll Batch
Loader.
Note 1581723.1 Load and end date
payroll relationship: Fusion Global
Payroll: How To Load Payroll
Relationship Data Via Payroll Batch
Loader.
NOTE: This is not a Batch Loader
object. This object is used in connection
with Balance Initialization feature.
Please refer to Balance Initialization
documentation for more information.
Note 1990913.1 How to Load, Update
and Delete Cost Allocation Data?
Note 1990913.1 How to Load, Update
and Delete Cost Allocation Data?
Organization calculation card load. Used
for loading SUI rates for US legislation.
Organization calculation card load. Used
for loading SUI rates for US legislation.
Organization calculation card load. Used
for loading SUI rates for US legislation.
Organization calculation card load. Used
for loading SUI rates for US legislation.
Employee Earnings Distribution card
load
US Employee Withholding Federal Card Upload Federal Association Details
This task action is used for loading the
TRU associations.

See Note 2022994.1 Fusion Payroll:

How to Load Employee Tax Cards via
Payroll Batch Loader (PBL) for Release
9 and Higher.

US Employee Withholding Federal Card Upload Federal Component Details

This task action creates and updates
the federal component.

See Note 2022994.1 Fusion Payroll:

How to Load Employee Tax Cards via
Payroll Batch Loader (PBL) for Release
9 and Higher.

US Employee Withholding Regional Upload Common State Component

Card Details The loading of State Regional cards
requires the employee’s Payroll
Relationship Number, Tax Reporting
Unit and State.

See Note 2022994.1 Fusion Payroll:

How to Load Employee Tax Cards via
Payroll Batch Loader (PBL) for Release
9 and Higher.

US Employee Withholding Regional Upload Common County Component See Note 2022994.1 Fusion Payroll:
Card Details How to Load Employee Tax Cards via
Payroll Batch Loader (PBL) for Release
9 and Higher.

US Employee Withholding Regional Upload Common City Component See Note 2022994.1 Fusion Payroll:
Card Details How to Load Employee Tax Cards via
Payroll Batch Loader (PBL) for Release
9 and Higher.

US Employee Withholding Regional Upload State XX Component Details

Card This task action is delivered only for the
states that have unique state specific
fields on the withholding certificate: AL,
AR, DC, GA, IA, IN, KY, LA, MA, MD,
ME, MO, MS, NC, NY, OH, PA, VA, WI,
WV.

See Note 2022994.1 Fusion Payroll:

How to Load Employee Tax Cards via
Payroll Batch Loader (PBL) for Release
9 and Higher.

US Employee Involuntary Deduction Upload Bankruptcy Order Involuntary See Note 2022585.1 Fusion US Payroll:
Card Details Upload Deduction Data for US Legislation How To Load Involuntary Deductions
via Payroll Batch Loader

US Employee Involuntary Deduction Upload Child Support Involuntary See Note 2022585.1 Fusion US Payroll:
Card Details Upload Deduction Data for US Legislation How To Load Involuntary Deductions
via Payroll Batch Loader

US Employee Involuntary Deduction Upload Creditor Debt Involuntary See Note 2022585.1 Fusion US Payroll:
 Card Details Upload Deduction Data for US Legislation How To Load Involuntary Deductions
via Payroll Batch Loader

US Employee Involuntary Deduction Upload Educational Loan Involuntary See Note 2022585.1 Fusion US Payroll:
Card Details Upload Deduction Data for US Legislation How To Load Involuntary Deductions
via Payroll Batch Loader

US Employee Involuntary Deduction Upload Garnishment Involuntary See Note 2022585.1 Fusion US Payroll:
Card Details Upload Deduction Data for US Legislation How To Load Involuntary Deductions
via Payroll Batch Loader

US Employee Involuntary Deduction Upload Spousal Support Involuntary See Note 2022585.1 Fusion US Payroll:
Card Details Upload Deduction Data for US Legislation How To Load Involuntary Deductions
via Payroll Batch Loader

US Employee Involuntary Deduction Upload Tax Levy Involuntary Deduction See Note 2022585.1 Fusion US Payroll:
Card Details Upload Data for US Legislation How To Load Involuntary Deductions
via Payroll Batch Loader

Back to Top

What templates to use for which element classification?

Please refer to chapter 2.2 in PBL White Paper Note <1590004.1> Loading data using the Batch Loader – Technical Essay.

Back to Top

How to Load Batch from File / Automation?

The Payroll batch loader is only suitable for loading low volumes of data since each additional rows must be manually created
in the workbook. Loading Volume data is accomplished using the ‘Load Batch from File’ payroll flow (also available from the
Payroll Checklists work area). This allows the user to directly populate the batches from a flat file without using the Payroll
Batch Loader. The loader workbook can be used to review these batches once loaded.

The ‘Load Batch from File’ flow allows the user to populate these batches directly, without using the Excel workbook, by
reading rows from a flat file uploaded to the server. The process uses a ‘Transformation’ Fast Formula to specify the record
format to expect in the flat file. It also enables the manipulation of the information read from the file in the formula before
creating the batch line.

For example, this could be useful loading element entries. One could pass the legacy Earnings or Deduction Code and the
formula could translate this to the corresponding Oracle name.

The instructions in the PBL White Paper (see the Appendix) are thorough. All the Transformation formulae (formula of type
‘Batch Loader’ ) can be found in the Appendix.

For more information please refer to:

Note 1590004.1 Loading data using the Batch Loader – Technical Essay

Note 2014778.1 Fusion Payroll: Payroll Batch Loader - Documentation about Load Batch from File

Note 1918254.1 Fusion Global Payroll: How Can I Load Payroll Relationship automatically Via Payroll Batch Loader?

Back to Top
Can size limit be increased for Upload Batch from File?

Q: When load any file size above 2 MB get error:

"Error: Selected file is too large. Please select a smaller file"

A: The size limit of the file for the Upload File cannot be increased. Please upload the file having size greater than 2 MB to
UCM and pass the Content Id as a parameter to the process Load Batch from File.

How can a line in a file be skipped?

If you want to skip a line then return the Task as "--". This will skip the given line.

Back to Top

How do I create and transfer a batch?

Please review the following notes notes:

Note 1590004.1 Loading data using the Batch Loader – Technical Essay

Note 1581723.1 Fusion Global Payroll: How To Load Payroll Relationship Data Via Payroll Batch Loader

Back to Top

How messages from custom fast formulas can be shown in PBL load log file?

You need to have the Logging configuration set at least as 'G' or 'F' for the log message to be displayed in Log files. Review
the Note 1536245.1 How to Enable Logging for Oracle Fusion Global Payroll.

Back to top

PBL workbooks for Payroll Definitions, Payroll Relationships, Bank data, Globals, UDTs and Balance Groups

Integrating with Oracle HCM Cloud guide has sections on loading the following Payroll Batch Loader workbooks:

Balance Adjustments Workbook

Balance Groups Workbook
Bank Data Workbooks
Costing Setups Workbook
Element Entries Workbook
Elements Workbook
Globals Workbook
Payment Methods Workbook
Payroll Definitions Workbook
Payroll Relationships Workbook
Third-Party Organizations Workbook
User-Defined Tables Workbooks

Back to Top
What tables hold PBL batches data?

The Oracle ADF Desktop Integration workbook (to give it its full name) maintains the three payroll interface tables. NOTE:
Workbook tab names in parentheses.

PAY_BATCH_HEADERS (Batch Header Sheet)

PAY_BATCH_LINES (Batch Content Sheet)

PAY_MESSAGE_LINES (Batch Message Sheet)

To synchronize the workbook with the database and populate fields there are two key areas where you must get used to
double clicking to refresh the workbook.

Back to Top

SQL to validate payroll batch information including errors

One can run this sql in BI:

SELECT
bh.batch_name, bh.batch_status, bl.batch_line_status ln_status, bl.*, pml.line_text message_Text
FROM
pay_batch_headers bh,
pay_batch_lines bl,
pay_message_lines pml
WHERE
bh.batch_name like 'GPM_INIT_EE_BAL_TEST_XI'
AND bl.batch_id (+) = bh.batch_id
AND pml.source_type (+) = 'G' AND
pml.source_id (+) = bl.batch_line_id
ORDER BY
bl.batch_line_id, NVL(pml.line_sequence,1)

or use this sql producing cleaner list:

select pbh.batch_name,pbl.line_sequence,status.meaning batch_line_status,pt.task_name,pta.action_name,

max(decode(ppp.task_property_value,to_char(ptp.ELEMENT_NAME),pblv.action_parameter_value,to_char(null))
reference,
rtrim(xmlserialize(content extract(xmlagg(xmlelement("e",
ptp.parameter_name||'='||pblv.action_parameter_value||',')
order by
pt.task_name,pta.action_name,pbl.batch_line_id,ptp.PARAM_SEQUENCE),
'//text()')), ',' ) Line_details,
(select LISTAGG(pml.line_text , ',') WITHIN GROUP (ORDER BY pml.line_sequence)
from FUSION.PAY_MESSAGE_LINES pml
where pml.source_type in ('G','L') and pml.source_id = pbl.batch_line_id) messages
from fusion.pay_batch_headers pbh,
fusion.pay_batch_lines pbl,
fusion.pay_batch_line_values pblv,
fusion.pay_task_parameters_vl ptp,
fusion.pay_tasks_vl pt,
fusion.pay_task_actions_vl pta,
FUSION.HCM_LOOKUPS status,
fusion.pay_task_properties_vl ppp
where pbh.batch_id=pbl.batch_id
and pbh.batch_id = 300000031103218 -- change this value to your batch id specified in the log file
for patch transfer or use the batch name below
-- and pbh.batch_name = 'Delete All Personal Payment Method - JAD' -- Batch name having errors.
and pblv.batch_line_id = pbl.batch_line_id
and pta.task_action_id = pbl.task_action_id
and pt.task_id =pta.base_task_id
 and ptp.task_parameter_id = pblv.action_parameter_id
and status.lookup_type='PAY_BATCH_STATUS'
and status.lookup_code=pbl.batch_line_status
and (ptp.display_flag!='N' or ppp.task_property_value=ptp.ELEMENT_NAME)
and ppp.base_task_action_id (+) = pbl.task_action_id
and ppp.task_property_type (+) ='BL_KEY_PARAMETER'
group by pbh.batch_name,pbl.line_sequence,pbl.batch_line_id,status.meaning,
pt.task_name,pta.action_name;

Back to Top

SQL to validate bank load

SELECT
bankparty.party_id bank_id
, bankparty.party_name bank_name
, bankorgprofile.home_country bank_home_country
, TO_CHAR(bankorgprofile.effective_start_date,'DD-MON-YYYY') bank_start_date
, TO_CHAR(bankorgprofile.effective_end_date,'DD-MON-YYYY') bank_end_date
, bankorgprofile.bank_or_branch_number bank_number
FROM
hz_parties bankparty
, hz_organization_profiles bankorgprofile
, hz_code_assignments BankCA
WHERE
BankCA.CLASS_CATEGORY = 'BANK_INSTITUTION_TYPE'
AND BankCA.CLASS_CODE IN ('BANK', 'CLEARINGHOUSE')
AND BankCA.OWNER_TABLE_NAME = 'HZ_PARTIES'
AND BankCA.OWNER_TABLE_ID = BankParty.PARTY_ID
AND bankorgprofile.party_id = BankParty.PARTY_ID
AND bankparty.party_type = 'ORGANIZATION'
AND trunc(SYSDATE) BETWEEN TRUNC(bankorgprofile.effective_start_date) AND
NVL(TRUNC(bankorgprofile.effective_end_date),trunc(SYSDATE) + 1)

Back to Top

SQL to validate bank branch load

SELECT
branchorgprofile.bank_code bank_code
, branchorgprofile.effective_start_date branch_start_date
, branchorgprofile.effective_end_date branch_end_date
, branchparty.party_id branch_id
, branchparty.party_name bank_branch_name
, branchorgprofile.bank_or_branch_number branch_number
, branchparty.mission_statement mission_statement
, branchcp.eft_swift_code eft_swift_code
, branchcp.eft_user_number eft_user_number
, branchcp.start_date eft_contact_start_date
, branchcp.end_date eft_contact_end_date
, edicp.edi_id_number edi_id_number
, edicp.edi_ece_tp_location_code edi_location
, edicp.start_date edi_start_date
, edicp.end_date edi_end_date
, rfcca.class_code rfc
, rfcca.start_date_active rfc_start_date
, rfcca.end_date_active rfc_end_date
FROM
 hz_parties branchparty
, hz_organization_profiles branchorgprofile
, hz_contact_points branchcp
, hz_contact_points edicp
, hz_code_assignments rfcca
WHERE
branchparty.party_type = 'ORGANIZATION'
AND branchparty.status = 'A'
AND branchorgprofile.party_id = branchparty.party_id
AND branchcp.owner_table_name (+) = 'HZ_PARTIES'
AND branchcp.owner_table_id (+) = branchparty.party_id
AND branchcp.contact_point_type (+) = 'EFT'
AND edicp.owner_table_name (+) = 'HZ_PARTIES'
AND edicp.owner_table_id (+) = branchparty.party_id
AND edicp.contact_point_type (+) = 'EDI'
AND rfcca.owner_table_id = branchparty.party_id
AND trunc(SYSDATE) BETWEEN TRUNC(branchorgprofile.effective_start_date) AND
NVL(TRUNC(branchorgprofile.effective_end_date), trunc(SYSDATE) + 1)
AND rfcca.class_code = 'BANK_BRANCH'

Back to Top

SQL to validate external account load

SELECT
ba.bank_account_name
, ba.bank_branch_name
, ba.bank_name
, ba.bank_account_type
, TO_CHAR(ba.start_date,'DD-MON-YYYY') acc_start
, TO_CHAR(ba.branch_start_date,'DD-MON-YYYY') branch_start
, TO_CHAR(ba.branch_end_date,'DD-MON-YYYY') branch_end
, TO_CHAR(ba.bank_start_date,'DD-MON-YYYY') bank_start
, TO_CHAR(ba.bank_end_date,'DD-MON-YYYY') bank_end
FROM
pay_bank_accounts ba
ORDER BY
ba.bank_account_name

Back to Top

SQL to validate personal payment method (PPM) load

SELECT
pn.display_name
, p.person_number
, ppm.name ppm_name
, ba.bank_account_name account_name
, ba.bank_account_type account_type
, ppr.payroll_relationship_number
, ppm.*
from pay_personal_payment_methods_f ppm
, pay_bank_accounts ba
, pay_pay_relationships_dn ppr
, per_person_names_f pn
, per_all_people_f p
WHERE
p.person_number = 'GPM_MANG_2'
AND
ppm.bank_account_id = ba.bank_account_id
AND
 ppr.payroll_relationship_id = ppm.payroll_relationship_id AND
TRUNC(SYSDATE) BETWEEN ppm.effective_start_date AND ppm.effective_end_date
AND
pn.person_id = ppr.person_id AND
TRUNC(SYSDATE) BETWEEN pn.effective_start_date AND pn.effective_end_date AND
pn.name_type = 'US'
AND
p.person_id = pn.person_id AND
TRUNC(SYSDATE) BETWEEN p.effective_start_date AND p.effective_end_date
ORDER BY
pn.display_name
, ppm.priority

Back to Top

How to migrate objects from one pod to another?

Process 'Create Batch for an Object' is used to download the content of an object into a batch, which can be copied to another
batch in the target system, such that record and its date effective history can be created.

Process Name: Create Batch for an Object

Parameters:
Batch : Name of a group of entries, or batch of data, to load into certain records based on predefined template.
Object : The object to download into the batch, such as Fast Formula or Element.
Record : Filter the download by the given name. It can be the exact or partial, such as %My%.
Legislative Data Group Level : Where applicable only download the object for the given Legislative Data Group. For example, to
download all Fast Formulas at enterprise level then the value for this would be No, but to download Fast Formulas for a given
Legislative Data Group of the batch then it will be Yes.

Please refer to PBL white paper chapter 3.3 (Note 1590004.1 Loading data using the Batch Loader – Technical Essay) for
instructions on example where a user created an element via the user interface (UI), created few input values on testing
environment and wanted to recreate the same in the production.

Also export and import can be done via Functional Setup Manager. For more information please review Note 1905704.1
Functional Setup Manager (FSM): Export and Import Best Practices.

Back to Top

What documentation is available for Kronos and Ceridian time card integration?

Please review Note 1590004.1 Loading data using the Batch Loader – Technical Essay.

Back to Top

Why Transformation formulas can be slow?

Poor performance is a likely symptom resulting from design choices used to address certain business requirements.

The Batch Loader formula type for transformation fast formulas does not support database items. Users can (and do) use
database items in their batch loader formulas by calling a formula within their main formula. The technique to retrieve this
information when a database item isn't available is to use the GET_VALUE_SET function. GET_VALUE_SET is inefficient
because it executes a different SQL statement each time because the bind variable values are pasted directly into the value-
set SQL. Also, GET_VALUE_SET SQL does not show up in AWR reports on top N worst performing SQL statements either
because each GET_TABLE_VALUE statement is different. GET_TABLE_VALUE statements are especially problematic if the
columns being bound to are not indexed.
Ideally, consider the possibility of extracting the Kronos data via its supported tools and perform the scrubbing, manipulation,
determine rates, validation there to create a summarized flat file as input to the transformation formula. This would allow the
formula to more efficiently transform / map the Kronos data into the PBL format for loading the batches.

Back to Top

Can GET_TABLE_VALUE function be used in a Batch Loader type formulas?

GET_TABLE_VALUE function cannot be used in a Batch Loader type formula because GET_TABLE_VALUE requires formula
contexts. To use GET_TABLE_VALUE, the formula type must support the LEGISLATIVE_DATA_GROUP_ID and
EFFECTIVE_DATE contexts.

There are two calling modes of this function:

1. A = GET_TABLE_VALUE(TABLE, COLUMN, ROW)

In this mode a formula error is raised if there is no user table value for the TABLE, COLUMN, ROW combination.

2. A = GET_TABLE_VALUE(TABLE, COLUMN, ROW, DEFAULT_VALUE)

In this mode DEFAULT_VALUE is returned if there is no user table value for the TABLE, COLUMN, ROW combination.

Both versions of GET_TABLE_VALUE require context for LEGISLATIVE_DATA_GROUP_ID.

The Batch Loader formula type cannot use either GET_TABLE_VALUE function because the Batch Loader formula type does
not support any contexts.

Enhancement Request bug 18268913 is logged for this issue.

Back to Top

Initial Balance Upload

Guides

Note 1436612.1 Balance Initialization in Oracle Fusion Global Payroll

Note 1912298.1 Oracle Fusion HRMS (US): Balance Initialization
Note 1993400.1 Oracle Fusion HRMS (CA): Balance Initialization
Note 2000651.1 Oracle Fusion HRMS (UK): Balance Initialization

How to undo Initial Balance Upload?

Rollback the balance initialization using the Undo operation.

How to run several batches in parallel?

Running batches sequentially is a safe way. In order to run many batches in parallel, please use the following workaround:
1.Create a dummy Balance Initialization batch, which is for 1 person (can be a dummy person) but contains batch lines for all
the combinations of balance types and balance dimensions to be used in actual BI batches, and set the balance values to 0.

2.Run the Balance Initialization process with the dummy batch with the validation mode.
This will complete all the initial balance feed set up.

3.Once this is done, run actual batches in parallel.

Back to Top

What type of encoding does PBL expect: UTF-8 or Windows-1252?

PBL expects UTF-8 encoding.

Back to Top

Does PBL support multithreading?

If same task and task action is used in the same batch, then PBL will load in multithreading mode in accordance of number of
threads set in the system.

If multiple tasks and task actions are included in a single batch, it does default to single threading. This currently occurs due
to any data dependencies and may cause slow performance.

Enhancement Request (ER) 21091384 - 'Payroll batch loader: defaults to single thread with multi task action' with Oracle
Fusion Development. This ER will be reviewed and considered by Fusion Development for a future release. It will remain open
until it is either incorporated into the product, or it is deemed not feasible. Due to the fact that this decision can occur over an
extended period of time, this originating SR will be inactivated and the ER will thus need to be monitored via My Oracle
Support).

Progress on your ER can be monitored via My Oracle Support at (https://support.oracle.com) by following the steps outlined in
note: How To Monitor Bugs And Enhancement Requests Via My Oracle Support Note 841907.1.

Back to Top

Troubleshooting Tips

Error: ADFDI-07528: An unexpected exception has occured. The UI Controller cannot initialize. The runtime session
will now abort.

Please see solution in Note 1567771.1 Error ADFDI-00134 / ADFDI-00500 When Using Payroll Batch Loader

Error: ORA-01841: (full) year must be between -4713 and +9999, and not be 0

Issue: When load Time card details with PBL, getting the error "ORA-01841: (full) year must be between -4713 and +9999,
and not be 0"

Solution: There were hidden spaces that needed to be removed. Check for and remove any hidden spaces in spreadsheet.
Back to Top

Error: Formula ELEMENTENTRIES_BATCHLOADER_FF, line 46, either function GET_TABLE_VALUE does not exist
or the combination of parameter types does not match the statement

Issue: When using Transformation formula loading element entries, there is a requirement to skip loading some elements.
Element names are listed in a UDT and trying to access that list from transformation formula. Getting the error when we try to
compile the modified formula.
Error: "Formula ELEMENTENTRIES_BATCHLOADER_FF, line 46, either function GET_TABLE_VALUE does not exist or the
combination of parameter types does not match the statement."

The Batch Loader formula type has no context usages hence functions like GET_TABLE_VALUE can not be used in Batch
Loader type fast formulas.

Enhancement Request (ER) bug 18268913 has been logged with Oracle Fusion Development. This ER will be reviewed and
considered by Fusion Development for a future release. It will remain open until it is either incorporated into the product, or it
is deemed not feasible.

Progress on this ER can be monitored via My Oracle Support at (https://support.oracle.com).

Back to Top

Error: PLS-00306: wrong number or types of arguments in call to 'CREATE_BANK_BRANCH' ORA-06550: line 1,
column 98

Issue: Get error when loading bank branches with apostrophes.

ERROR
-----------------------
Sql exception while calling
PAY_BATCH_LDR_PKG.PLSQL_BATCH_LINE_TRANSFERjava.sql.SQLException:
ORA-06550: line 1, column 98:
PLS-00306: wrong number or types of arguments in call to 'CREATE_BANK_BRANCH'
ORA-06550: line 1, column 98:
PL/SQL: Statement ignored
ORA-06512: at "FUSION.PAY_BATCH_LDR_PKG", line 1798
ORA-06512: at line 1

This affects most, but not all, branches. The branches which fail have a ' (apostrophe) in the name, for example BANQUE
POPULAIRE D'ALSAC.
Solution: As a workaround, change the bank name to BANQUE POPULAIRE D''ALSACE by putting in a second single quote.
This will allow the record to be uploaded. Also do not load branches with same name: duplicate names are not allowed. This
issue is aimed to be resolved in release 10.

Back to Top

Errors when attempting to initiate the PBL spreadsheet by clicking Download button

Error: RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1: 10.4.4 403 Forbidden

Issue: When attempting to click on Payroll Batch Loader and click on Download get the below error:
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1: 10.4.4 403 Forbidden
Solution: To implement the solution for either cause, the following steps needs to be done:
1. Assign the PAY_BATCH_LOAD_VIEW_DUTY job role to the user
2. Navigator > Payroll > Administration
3. Select the "Batch Loader" task
4. Click on the Download button
Reference: Note 1956087.1 Fusion Global Payroll: Payroll Batch Loader gets Hypertext Transfer Protocol -- HTTP/1.1: 10.4.4
403 Forbidden

Back to Top

Error: ADFDI-05587: The client and server versions do not match

Issue: Unable to upload the data using ADF Di spreadsheet. Get the following error after entering authentication details in the
spreadsheet:
ADFDI-05587: The client and server versions do not match. Using this version of the client may result in unexpected behavior
or errors.

Solution: Install an ADF Di client that matches the server version.1. Remove existing version of ADFDi Client using control
panel and re-boot the machine. Refer to Note
Fore more infromatio please refer to Note 1670607.1 ADFDI-05587: The client and server versions do not match.

Back to Top

Slow Performance issue

Slow performance while trying to load Federal Tax withholding for employees

Issue: While trying to load Federal Tax withholding for employees , severe performance issues are seen.

Solution: Disable the HCM Events:

1. Log in to the application
2. Navigate to “Manage Administrator Profile Values” .
3. Search for the profile option “HRC_DISABLE_HCM_EVENTS_PROCESSING”
4. For the user FUSION_APPS_HCM_ESS_APPID set the value of the profile to “Y”. This should be done at the user level.

Reference: Note 2006129.1 Severe Performance Issue - Federal Tax Withholding.

How to troubleshoot Initial Balance Upload performance issues

1. Issues like this are resolved case by case for each pod. These issues arise from the size of loads being done so every
case/pod/client has different issues.

2. Stats are gathered daily based on the change in the table data so until large loads like these trigger an issue the gathering
of stale stats don't become an issue.

3. When implementation team is ready to load the balance initialization batch the action plan is as follows before trying upload
big batches:
a. Upload a small batch (e.g. with few 100's lines).
b. Support opens collab SR with request for Cloud Ops to Gather Schema Statistics.
c. Performance Team would then pull the explain plan/report of SQL ID causing the issue to ensure that the DB optimizer is
using PAY_ENTRY_USAGES_N1, instead of PAY_ELEMENT_ENTRIES_F_FK1.

4. Use multi-threading. Reference Note 2067180.1 Optimize Configuration for Payroll, HCM Extract and Benefits Performance.
Back to Top

Initial Balance Upload errors

Error: The combination of balances is invalid for the load date

Issue: When attempting to load initial balance via Payroll Batch Loader (PBL) Initialize Balance task the following error is
displayed:
"The combination of balances is invalid for the load date"

Solution: The user must decide which line is correct, what the balance should actually be and delete the incorrect line (or
update its value to match the intended value).

Reference: Note 1969511.1 Fusion Global Payroll: Error Loading Initial Balance Using Payroll Batch Loader "The combination of
balances is invalid for the load date".

Back to Top

Error: The legislative data group specified for the batch does not exist

Issue: Whenattempting to load initial balance via Payroll Batch Loader (PBL) Initialize Balance task the following error is
displayed:
"The combination of balances is invalid for the load date"

Solution: The user must decide which line is correct, what the balance should actually be and delete the incorrect line (or
update its value to match the intended value).

Reference: Note 1969511.1 Fusion Global Payroll: Error Loading Initial Balance Using Payroll Batch Loader "The combination of
balances is invalid for the load date".

Back to Top

Errors loading Element Eligibility

Error: Failed to lock the record in table PAY_ELEMENT_TYPES_F with key oracle.job.Key[300000096957475 1900-01-
01 4712-12-31 ], another user holds the lock

Cause:

Multi-threading was set.

Solution:

Use single threading to load batches to create element eligibility. For more information please refer to Note 2010833.1 Fusion
Global Payroll:Payroll Batch Loader (PBL) Load/Transfer: ORA-00054: Resource Busy and Acquire with NOWAIT Specified or
Timeout Expired.

Back to Top

Errors loading Element Entries

Error: Access denied (oracle.wsm.security.WSFunctionPermission)

Cause:
1) The cause of this issue, if attempting to load element entries through the Payroll Batch Loader, is that the the task action
of "Quick Create" was used and is no longer valid.
2) However, if trying to load PPM or any other entity that in turn invokes a web service and, you are using Transfer Batch
with multiple threads, then,this security error is expected.

Solution:
To implement the solution, for cause #1, use the "Create Element Entry" task action in the Batch loader rather than "Quick
Create".
For cause # 2, the workaround is to run the Transfer Batch in a single thread. The fix for this issue was delivered inMay PB 9.5
through the bug 20508421.

Reference: Note 1997926.1 Fusion Global Payroll: Access denied (oracle.wsm.security.WSFunctionPermission) error in Payroll
Batch Loader or tasks invoking a Web Service.

Back to Top

Error: JBO-27019 or JBO-29000 The get method for attribute InputValue1

Issue: Get errors when loading element entries:

a) soapFaultException :oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : JBO-

27019: The get method for attribute "InputValue1" in ElementEntrySvc cannot be resolved.: java.lang.String

b) JBO-25072: Applying List binding LOV_AssignmentDetails with given set of values leads to no matching row for a row of
type :ElementEntrySvc
Solution: Please use Create Element Entry task rather than Quick Create as an alternative. When searching for the Task
Action, search for:

Task Action: Element Entry

Task Action Name: Create Element Entry

Reference: Note 1668583.1 Fusion Global Payroll: Getting JBO-27019 or JBO-29000 error in Payroll Batch Loader for Element
Entries.

Back to Top

Errors loading Personal Payment Method

Error: JBO-Provide PayrollRelationshipNumber or PayrollRelationshipName

Issue: When attempting to create personal payment methods via payroll batch loader (PBL)
the following error occurs.

ERROR
-----------------------
JBO-Provide PayrollRelationshipNumber or PayrollRelationshipName: Provide PayrollRelationshipNumber or
PayrollRelationshipName.oracle.apps.fnd.applcore.messages.FndMessagesUtil$FndMapResourceBundle

Solution:
- Remove SPACE from assignment number field and populate Payroll Relationship number instead
- Either the Assignment Number or the Payroll relationship number can be used to derive the payroll relationship ID , which is
what is required to create the Personal Payment Methods
- If you are using Payroll Relationship Number , there is no need to enter the assignment number
- if you do decide to enter the assignment number as well , provide a valid value for the assignment number field

Reference: Note 1990103.1 Payroll Batch Loader Error: JBO-PROVIDE PAYROLLRELATIONSHIPNUMBER OR

PAYROLLRELATIONSHIPNAME.

Back to Top
Error: JBO-Provided OrgPaymentMethodName is invalid for the Payroll Relationship

When attempting to create Personal Payment Method (PPM) using Payroll Batch Loader (PBL) the following error occurs.

ERROR
-----------------------
JBO-Provided OrgPaymentMethodName is invalid for the Payroll Relationship: Provided OrgPaymentMethodName is invalid for
the Payroll

Solution:
Change the Payment Source name so that it will be different from the corresponding Organizational Payment Method name.

Reference: Note 1981937.1 Oracle Fusion Global Payroll: Unable To Load Personal Payment Methods Via Payroll Batch Loader.

Back to Top

Error: JBO-27014: Attribute DataType in GlobalDEO is required

Errors generate when attempting to load global values for use in fast formulas via Payroll Batch Loader (PBL):

JBO-27023: Failed to validate all rows in a transaction.JBO-27024: Failed to validate a row with key
oracle.jbo.Key[300000012018320 1951-01-01 4712-12-31 ] in GlobalDEOJBO-27010: Attribute set with value Number for
DataType in GlobalDEO has invalid precision/scaleJBO-27014: Attribute DataType in GlobalDEO is required.

Solution:
Use "T" for "Text" or "N" for "Number" it should use "N".

Reference: Note 1907242.1 Fusion Global Payroll: Not Able to Load Global Value for Fast Formula via Payroll Batch (PBL).
Error: JBO-27024.

Back to Top

How to get ADFDI diagnostics if none of the above works?

1. Run the ADFdi Client Health Check (Note 2010222.1)

2. Run the ADFdi Diagnostic Report (Note 2012576.1)

Back to Top

REFERENCES

NOTE:1670607.1 - ADFDI-05587: The Client And Server Versions Do Not Match Error During User Authentication To Fusion
Applications
NOTE:2022585.1 - Fusion US Payroll: How To Load Involuntary Deductions via Payroll Batch Loader
NOTE:1999279.1 - Fusion Payroll: Need to End Date the Element via the PBL and There Is No End Date Column in The Update
Task
BUG:21091384 - PAYROLL BATCH LOADER: DEFAULTS TO SINGLE THREAD WITH MULTI TASK ACTIONS
NOTE:2022994.1 - Fusion Payroll: How to Create, Correct, Update, Delete and Zap Employee Tax Cards via Payroll Batch
Loader (PBL) for Release 9 and Higher
BUG:18268913 - GETTING FAST FORMULA COMPILE ERROR WHEN USING GET_TABLE_VALUE FUNCTION
NOTE:1436612.1 - Balance Initialization in Oracle Fusion Global Payroll
NOTE:1993400.1 - Oracle Fusion HRMS (CA): Balance Initialization
NOTE:2000651.1 - Oracle Fusion HRMS (UK): Balance Initialization
NOTE:1590004.1 - Loading Data using Payroll Batch Loader - Technical Essay
NOTE:2014778.1 - Fusion Payroll: Payroll Batch Loader - Documentation about Load Batch from File

NOTE:1990913.1 - Fusion Payroll: How to Load, Update and Delete Cost Allocation Data?
NOTE:1581723.1 - Fusion Global Payroll: How to Load Payroll Relationship Data from Spreadsheet via Payroll Batch Loader
NOTE:2030268.1 - Oracle Fusion Payroll Batch Loader User Guide for Release 10
NOTE:1956087.1 - Fusion Global Payroll: Payroll Batch Loader gets Hypertext Transfer Protocol -- HTTP/1.1: 10.4.4 403
Forbidden
http://docs.oracle.com/cloud/latest/common/FAIHM/F1415466AN17E14.htm#F1173458AN17E42
NOTE:1918254.1 - Fusion Global Payroll: How Can I Load Payroll Relationship Automatically from File via Payroll Batch Loader?
NOTE:2093263.1 - Fusion Global Payroll: How to End Date or Delete Element Entry Via Payroll Batch Loader
NOTE:1905704.1 - Functional Setup Manager (FSM): Export and Import Best Practices
NOTE:1567771.1 - Error ADFDI-00134 / ADFDI-00500 When Using Payroll Batch Loader

NOTE:1504483.1 - All White Papers for Fusion Applications HCM

NOTE:1912298.1 - Oracle Cloud Human Capital Management for the United States: Balance Initialization
Didn't find what you are looking for?