Oracle Fusion Cloud Payroll 22D What's New

Expand All

FEBRUARY MAINTENANCE PACK FOR 22D

Revision History
Overview
Feature Summary
Payroll
1. Payroll for the United States
  1. 1. Configure Tax Withholding Cards with HCM Design Studio
2. Payroll for Canada
  1. 1. HCM Design Studio for Canada Tax Credit Information

JANUARY MAINTENANCE PACK FOR 22D

Revision History
Overview
Feature Summary
Payroll
1. Payroll for Canada
  1. 1. Enhanced Canada Pension Plan (CPP) and Quebec Pension Plan (QPP)

NOVEMBER MAINTENANCE PACK FOR 22D

Revision History
Overview
Feature Summary
Payroll

Update 22D

Revision History
Overview
Feature Summary
Payroll
IMPORTANT Actions and Considerations for Payroll

February Maintenance Pack for 22D

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Module	Feature	Notes
27 JAN 2023			Created initial document.

Overview

HCM Cloud applications have two types of patches you can receive that are documented in this What’s New:

Release Updates (22A, 22B, 22C, and 22D)
Optional Monthly Maintenance Packs to each update

It is important for you to know what Release Update your environment is on. You can find this in your Cloud Portal.

____________________

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our products better, please let us know. To enter an idea go to the Ideas Lab on Oracle Customer Connect. In this document wherever you see the light bulb icon after the feature name it means we delivered one of your ideas.

____________________

Field label	What you do
Name Description	Enter meaningful values.
Country	Select United States. Note: You can use browser search to help you find it.
Legislative Data Group	Enter the legislative data group you would like to update.
Calculation Card	Select the template you're editing. Tax Withholding Tax Withholding for Pension and Annuity Payments
Calculation Component	Select the component you're editing. Federal Taxes State Taxes County Taxes City Taxes Pennsylvania PSD
Reference 1 - 4	For taxes that require jurisdictions (state, county, city, and Pennsylvania PSD), use these fields to identify the jurisdiction type. For example, if you selected the City calculation component, you would set the following. Reference 1: State Reference 2: County Reference 3: City
Reference Value 1 - 4	Select a jurisdiction for each reference you defined for your tax.
Legal Employer	Select your legal employer. Select All to define this rule for all legal employers.
Role Name	To select if your rule only applies to a specific role. If blank, it will apply to all roles.
Mode	To select if your rule only applies to the Employee Self Service UI or the Payroll Administration UI. If blank, it will apply to both.

Date	Module	Feature	Notes
20 DEC 2022			Created initial document.

Date	Module	Feature	Notes
22 NOV 2022	Payroll for the United States	Routing Number Search for Employee Bank Account Creation	Updated document. Feature delivered in update 22D.
28 OCT 2022			Created initial document.

Lookup type	Lookup code
ORA_IBY_CONTROLLED_FEATURES	IBY_BRANCH_NUM_SELECTION

Date	Module	Feature	Notes
05 DEC 2023	Canada Payroll	Support for Dynamic Payroll Relationship Groups for Canada Reports and Processes	Updated document. Revised feature information.
29 SEP 2023	Canada Payroll	Support for Dynamic Payroll Relationship Groups for Canada Reports and Processes	Updated document. Revised feature information.
20 DEC 2022	Global Payroll/Payroll Input	Copy Future Dated Changes during Global Transfer	Updated document. Revised feature information.
20 DEC 2022	Global Payroll/Payroll Flows	Errors and Warning Report in CSV Format for Calculate Payroll Process	Updated document. Revised feature information.
20 DEC 2022	Global Payroll/Payroll Input	Event Support for HCM Rates	Updated document. Revised feature information.
20 DEC 2022	Global Payroll/Payroll Flows	Logging and Monitoring for the Payroll Background Process	Updated document. Revised feature information.
20 DEC 2022	Global Payroll/Payroll Processing	Optimize Performance of Multi-Threaded Processes	Updated document. Revised feature information.
20 DEC 2022	Payroll for Canada	Annualize Salary for Taxation of Nonperiodic Earnings with no Regular Earnings	Updated document. Revised feature information.
22 NOV 2022	Global Payroll / Payroll Processing	Optimize Performance of Multi-Threaded Processes	Updated document. Revised feature information.
22 NOV 2022	Payroll for Mexico	Economic Zone Override	Updated document. Feature delivered in update 22D.
30 SEP 2022	Global Payroll / Payroll Flows	Errors and Warning Report in CSV Format for Calculate Payroll Process	Updated document. Revised feature information.
30 SEP 2022	Global Payroll / Payroll Inputs	Payroll Tasks in Person Spotlight	Updated document. Revised feature information.
30 SEP 2022	Global Payroll / Payroll Processing	Optimize Performance of Multi-Threaded Processes	Updated document. Revised feature information.
30 SEP 2022	Global Payroll / Payroll Processing	View Run Results with Element Entry Result Identifier	Updated document. Revised feature information.
02 SEP 2022			Created initial document.

SUGGESTED READING FOR ALL HCM PRODUCTS

HCM Common What's New - In this What's New you will find feature that are used across applications.
Human Resources What’s New – In the Global Human Resources section you will find features on the base application in which other application are built upon.

NOTE: Not all Global Human Resource features are available for Talent and Compensation products.

Oracle Human Capital Management Cloud Functional Known Issues and Maintenance Packs (Document ID 1554838.1). These documents identify bug fixes and possible known issues. You will also need to review these documents based in the release update version you are currently on or will be moving to.
Oracle Help Center – Here you will find guides, videos and searchable help.
Release Readiness – New Feature Summary, What’s New, Feature Listing Spreadsheet, Spotlights and Release Training

GIVE US FEEDBACK

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

	Ready for Use by End Users (Feature Delivered Enabled) Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.
Feature	Report	UI or Process-Based: Small Scale	UI or Process-Based: Larger Scale*
Payroll
Global Payroll
Autocomplete
Autocomplete Rules for Final Close Date (Payroll Assignment Object) in the Termination Flow
Autocomplete Rules for Tax Reference Unit (in the Payroll Terms Business Object) in HR Flows
Payroll Security
New Payroll Duty Roles
Payroll Input
Payroll Tasks in Person Spotlight
Copy Future Dated Changes during Global Transfer
Add New Input Values to Unused Elements
Automatically Add Balance Run Dimensions
Calculation Entries Display Reserved Input Values
Event Support for HCM Rates
Payroll Processing
Support for Time Updates in Payroll: Upgrade Time Elements
Optimize Performance of Multi-Threaded Processes
View Run Results with Element Entry Result Identifier
Payroll Flows
New Process Event Action Flow for Manual Event Actions
Errors and Warning Report in CSV Format for Calculate Payroll Process
Cancel Action
Logging and Monitoring for the Payroll Background Process
Payroll Outputs
View Payroll Costing Results for a Subledger Journal Entry
Intermediary Bank Account Details in Payments XML
Preview Payslips and Year-End Documents
Payroll Core
Payroll Core Support for Defaulting Tax Reporting Unit
Payroll for Bahrain
Global Transfer for Social Insurance and Gratuity Components with Future Dated Updates
Payroll for Canada
Global Transfer - Future-Dated Changes
Support for Dynamic Payroll Relationship Groups for Canada Reports and Processes
QTD Dimensions Added to Employee Active Payroll Balance Report
Annualize Salary for Taxation of Nonperiodic Earnings with no Regular Earnings
Payroll for China
Enhanced Tax Component Details Management During Global Transfers and Rehires
Payroll for Kuwait
Global Transfer for Social Insurance and Gratuity Components with Future Dated Updates
Payroll for Mexico
Economic Zone Override
Payroll for Oman
Social Insurance for Oman Citizens
Payroll for Qatar
Global Transfer for Social Insurance and Gratuity Components with Future Dated Updates
Payroll for Saudi Arabia
Global Transfer for GOSI and Gratuity Components with Future Dated Updates
Payroll for the United Arab Emirates
Global Transfer for Social Insurance and Gratuity Components with Future Dated Updates
Payroll for the United Kingdom
Global Transfer for Student Loan and Postgraduate Loan Components with Future-Dated Updates
Payroll for the United States
Start-of-Year Flow Enhancement for Exempt Details Update Options
Start-of-Year Flow Enhancement for 457 Limit Update
Perform Multiple Tax Balance Adjustments for Third-Party Payments Using HCM Data Loader
Periodic Payroll Archive Enhancement to Capture Employer Phone Number
Transactional Business Intelligence for Payroll
Enhancements to Payroll Flows Subject Area
Enhancements to Payroll Run Costing Real Time Subject Area
IMPORTANT Actions and Considerations for Payroll

Payroll

Global Payroll

Autocomplete

Autocomplete Rules for Final Close Date (Payroll Assignment Object) in the Termination Flow Feature is from a customer submitted idea.

You can derive the Final Close date in 2 different ways:

As a predefined (static) date valid for all terminated employee across the enterprise. For example, 31-DEC-2022. In this case, the Business object for Final Close is PayDate.
As a derived date (dynamic), based on the employee termination date + x number of days. For example, if Final Close Date = Termination date (such as 31-JAN-21) + 90 days, Final Close date = 31-APR-21.

Creating the Rule with Auto Complete

Autocomplete rules will be supported in the "Terminate" transaction. This action type is valid for both defaulting options (static and dynamic).

For further information about the related action type codes for the EMP_Groovy_ActionTypeCode HCM Params function, please refer to 21D AutoComplete Rules Published document.

Rule Sample 1 - Static derivation

The Autocomplete rule enables the defaulting of a static date (15-Feb-15).

Rule Sample 1 - Static Derivation

Rule Sample 2 - Dynamic derivation

The Autocomplete rule enables the defaulting of a dynamic Final Close date based on the Termination date + 3 months (90 days). Since you do not have an HcmParam to directly get the termination date, you need to derive the termination date inside our rule through the following logic:

Get all the hrAssignmentRows for the given payroll assignment.
For Each hrAssignmentRow, check if the row is inactive.
If it's Inactive, find the row related to the Action Code.
If the Action Code is EMPL_TERMINATE, derive the termination date as HrRow.EfectiveStartDate -1

Rule Sample 2 - Dynamic derivation

NOTE: It is also possible to derive the Final Close Date based on Person Types. For example, you can set it up so that the Final Close Date for an employee is 12 months after termination, and 0 days after termination for a pending worker.

This feature provides a better user experience while creating the Rule with Auto Complete.

Steps to Enable

To enable Autocomplete Rules in the HCM Experience Design Studio, you need to log a Service Request (SR). Please review and follow the instructions provided in the My Oracle Support document, Enabling Oracle HCM Cloud Autocomplete Rules (Document ID 2767655.1) to get access.

Tips And Considerations

Termination Date correction / update: The following scenario is valid in both cases (static and dynamic). If an employee is terminated at a specific date but the termination date is changed later and that new termination date is later than the Final Close Date entered in the AutoComplete rule, the Final close date will be reset. For example, if the HR user moves the termination date to 1 month later than initially recorded, this will reset the Final Close to Year 4712.

Violation of existing validation rules: If the Final Close Autocomplete rule violates the standard business rule (for example, the defaulted Final Close date is earlier than the Last Standard Process Date), an error message will be displayed and the user will not be able to submit the termination. Given that the defaulted Final Close date will not be visible in HR UIs (Termination flow), it is an important consideration for implementation.

Error message for violation of validation rules

Key Resources

To enable Autocomplete Rules in the HCM Experience Design Studio, you need to log a Service Request (SR). Please review and follow the instructions provided in the My Oracle Support document, Enabling Oracle HCM Cloud Autocomplete Rules (Document ID 2767655.1) to get access.

Access Requirements

You must be granted the Human Capital Management Application Administrator role to work in a sandbox.

Autocomplete Rules for Tax Reference Unit (in the Payroll Terms Business Object) in HR Flows

When you create rules, you must select the Rule Type as "Field Modification Rule Type". The Business Object is "Payroll Terms", and the Field value is "Default Payroll Values Indicator".

Field Modification Rule Type

This feature provides a better user experience while creating the Rule with Auto Complete.

Steps to Enable

Link to the MOS doc - https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=264444337626786&id=2767655.1&_adf.ctrl-state=jpf0ricmi_84

Tips And Considerations

Assumption: HR assignments records must already be available so the TRU can be derived from them. Creating the Rule with Auto Complete

Autocomplete rules will be supported in the following transactions:

Hire an Employee
Add contingent worker
Add Non Worker
Add Pending Worker
Add Assignment
Add Temp Assignment
Create Work Relationship
Add a Pending Worker
Create and Edit Offer

For further information about the related action type codes for the EMP_Groovy_ActionTypeCode HCM Params function, please refer to the 21D AutoComplete Rules Published document.

Rule Sample 1

The Autocomplete rule enables the defaulting of a TRU based on Legal Entity in the New Hire (EMPL_ADD_EMP) Flow.

Defaulting of a TRU based on Legal Entity

Rule Sample 2

The Autocomplete rule enables the defaulting of a TRU based on the Business Unit in the Global Transfer (EMPL_GLB_TRANSFER) Flow.

Defaulting of a TRU based on the Business Unit

Limitations

This feature is not valid for HR Assignment EFFs and DFFs.
It is not possible to derive the payroll attributes based on Salary. Salary basis is not an HR assignment attribute, it's a Salary record.

Access Requirements

You must be granted the Human Capital Management Application Administrator role to work in a sandbox.

Payroll Security

New Payroll Duty Roles

New duty roles, one each to secure different subject areas of payroll are created. With this, customers can provide access to individual subject areas within payroll module. For example: A custom payroll job role can inherit the duty role related to payroll element entries and the users having this job role would have access to only the subject areas related to payroll element entries. The list of duty roles and the subject areas that they secure are as below.

NOTE: All these subject areas are also secured by the existing Payroll Transaction Analysis Duty.

Subject Area	Duty Role
Payroll Element Entries Real Time	Payroll Element Entries Transaction Analysis Duty
Payroll Element Entries History Real Time	Payroll Element Entries Transaction Analysis Duty
Payroll Personal Payment Methods Real Time	Payroll Personal Payment Methods Transaction Analysis Duty
Payroll Calculation Cards Real Time	Payroll Calculation Cards Transaction Analysis Duty
User-Defined Tables Real Time	User-Defined Tables Transaction Analysis Duty
Payroll Run Results Real Time	Payroll Run Results Transaction Analysis Duty
Payroll Balances Real Time	Payroll Balances Transaction Analysis Duty
Payments Distribution Real Time	Payments Distribution Transaction Analysis Duty
Rate Calculation Results Real Time	Rate Calculation Results Transaction Analysis Duty
Retroactive Pay Real Time	Retroactive Pay Transaction Analysis Duty
Payroll Flows Real Time	Payroll Flows Transaction Analysis Duty
Payroll Costing Setup Details Real Time	Payroll Costing Setup Details Transaction Analysis Duty
Payroll Run Costing Real Time	Payroll Run Costing Transaction Analysis Duty
Payments Costing Real Time	Payments Costing Transaction Analysis Duty

This is in addition to the existing Payroll Transaction Analysis Duty role that secures all of the payroll subject areas.

Steps to Enable

Provide the required access before using the feature. Details are in the Access #Requirements section.

Tips And Considerations

The delivered payroll manager job role will have all the new duty roles along with the existing Payroll Transaction Analysis Duty role. If you are creating custom job role to give access to a specific subject area, such as Payroll Run Results Real Time, then you should remove all other individual duty roles including Payroll Transaction Analysis Duty role and include or keep only Payroll Run Results Real Time Duty role.

Access Requirements

Subject Area	Secured By
Payroll Element Entries Real Time	Payroll Element Entries Transaction Analysis Duty
Payroll Element Entries History Real Time	Payroll Element Entries Transaction Analysis Duty
Payroll Personal Payment Methods Real Time	Payroll Personal Payment Methods Transaction Analysis Duty
Payroll Calculation Cards Real Time	Payroll Calculation Cards Transaction Analysis Duty
User-Defined Tables Real Time	User-Defined Tables Transaction Analysis Duty
Payroll Run Results Real Time	Payroll Run Results Transaction Analysis Duty
Payroll Balances Real Time	Payroll Balances Transaction Analysis Duty
Payments Distribution Real Time	Payments Distribution Transaction Analysis Duty
Rate Calculation Results Real Time	Rate Calculation Results Transaction Analysis Duty
Retroactive Pay Real Time	Retroactive Pay Transaction Analysis Duty
Payroll Flows Real Time	Payroll Flows Transaction Analysis Duty
Payroll Costing Setup Details Real Time	Payroll Costing Setup Details Transaction Analysis Duty
Payroll Run Costing Real Time	Payroll Run Costing Transaction Analysis Duty
Payments Costing Real Time	Payments Costing Transaction Analysis Duty

Payroll Input

Payroll Tasks in Person Spotlight

Professional payroll users can see their workers' information in the Person Spotlight Page, and take certain actions depending on the security configuration of their role. For example, they can do these actions:

Adjust Individual Balances
Calculate Quickpay
Access Calculations Cards
Element Entries
Costing for a person
Personal Payment Methods
Payroll Relationship
Payslip

Currently, you can navigate to person spotlight using the following navigation paths:

Global Search field; search and click on the employee > submit, and you will be redirected to the employee Public Info page where the Person Spotlight Menu is available.
Me menu on your Home page (chose the "Directory" or "Public Information" tasks).

Please note these navigation paths are the current available options, but a new "Person Spotlight" dedicated tile will soon be available under the "My Client Groups".

Professional Payroll users can see their workers' information in the Person Spotlight Page, and take certain payroll actions depending on the security configuration of their role.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

For additional information, refer the following resources on the Oracle Help Center: Person Spotlight.

Copy Future Dated Changes during Global Transfer

You can now copy the future dated changes and preserve end dates on calculation cards and person costing overrides during a Global Transfer.

There are two types of future changes:

Future Updates to the Record Created as of the Global Transfer Date
Future Record that begins after the Global Transfer Date

Copying future dated changes for calculation cards is supported by the Local and Global Transfer flow as well as the Mass Change Legal Employer flow. Legislation rules control exactly what type of future dated calculation card changes are copied during a global transfer. Let's take a US example, if you perform a global transfer effective December 1, 2022 for an employee who has already updated the tax card effective January 1, 2023, both the tax card effective December 1, 2022 as well as the future changes are copied to the new payroll relationship created by the global transfer. This is available on both the Local and Global Transfer flow as well as the Mass Change Legal Employer flow. For more details, please refer to the global transfer help documentation for your legislation.

Person Costing overrides are considered as employment data. So future changes to person costing overrides are copied only if you choose to copy the future assignment updates. Use the HR profile option Future Assignment Changes Copy Enabled (ORA_PER_CLE_COPY_FUT_ASG) in the Local and Global Transfer flow and the Copy future assignment updates check box on the Mass Legal Employer Change flow to be able to copy the future changes on employment data.

For example, you may want to select this option for a global transfer that is due to a re-organization, merger, or acquisition, where the employees are expected to continue with the same employment data, even those scheduled for the future.

For calculation cards, the future changes are copied irrespective of what is set on the HR profile option or the check box.

This feature reduces the manual effort in copying future dated payroll information from the source to the target legal employer.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The Tax Reporting Unit (TRU) for the target card and component is determined by the new TRU specified on the global transfer flow and not by what's on the source legal employer. So the new TRU association and association detail would not be end dated even if it is end dated on the source TRU.

Key Resources

For more information see the following topic: Employment Profile Options topic under the Employment chapter of the Implementing Global Human Resources guide in the Oracle Help Center.

Add New Input Values to Unused Elements

You can now add a new input value to an element as long as the entry does not exist or the element is not processed. Previously, if a payroll process was executed after creation of an element, adding a new input value was not allowed even if the element was not used.

With this enhancement, you can add the input values till the element has either an element entry or a run result. The run result scenario is for the indirect elements which do not have entries.

This feature enhances the user experience while adding new input values to unused elements.

Steps to Enable

You don't need to do anything to enable this feature.

Automatically Add Balance Run Dimensions

When you use the Balance Definition page and add or update a group level balance, the associated run dimensions are added automatically. The application checks for all related 'Run' balances and adds them if not included. If the run dimensions aren’t added, downstream issues occur in the payroll run and reporting.

For example, if you add 'Group Tax Unit Fiscal QTD' dimension, run dimensions 'Group Tax Unit Run' and 'Relationship NoCB Tax Unit Run' are automatically added to the balance definition.

This feature is automatically triggered for all balance groups and assignment level balances.

The dimensions are automatically added only if the dimension usage is available for the respective legislation. Only those dimensions for which the localization is enabled are added to the balance (any level dimension).

After the run dimension is added, a confirmation message displays on the page.

When you delete a group level balance dimension, the run dimension is deleted automatically. If you delete only the respective group dimension run balance, then an error message is displayed on the page. For example, you cannot remove the Group Tax Unit Run dimension unless you remove the Group Tax Unit Fiscal QTD dimension.

You cannot delete a of time definition if it’s already used as Overtime Period. Similarly, you cannot remove a Primary balance feed if the primary details exist.

Add associated dimensions automatically to balances defined on the balance definition page.

Steps to Enable

You don't need to do anything to enable this feature.

Calculation Entries Display Reserved Input Values

You can view the following additional reserved input values in the Standard Entries section of the Calculation Entries page:

Primary Input (already displayed)
Percentage
Hours
Days
Units
Rate

This enhancement provides a better user experience while displaying the calculation entries.

Steps to Enable

You don't need to do anything to enable this feature.

Event Support for HCM Rates

With this enhancement, use the new event actions solution to control which employees should have rates calculated. This feature limits the number of employees that have rates recalculated and thereby improves the performance of the rates calculation process.

Use the event action group to define what type of changes should trigger rates to be calculated for an employee. For example, calculate rates for any employee with an assignment update such as a job change or an element entry change such as a salary update.

Define an event action with a submission type as manual to submit the rates process associated with the event action by using the Process Event Action flow. This enables you to use the Process Event Action task to submit the recalculation of rates for all employees with an unprocessed rate event notification. Enter the mandatory fields such as Flow Name, Event Action Type, and Event Action in the flow parameters page.

The Process Event Action flow submits the rates calculation process and generates a report that lists the employees included in the rates process, the status of their rate calculation, and any warning or error messages. It will also produce a report with the rate values calculated for each employee included in the process.

Control which employees have rates calculated using the new events solution.

Steps to Enable

Event Groups and Event Actions

Create the event action using HCM Data Loader for Generate HCM Rates.
Create the event action group using HCM Data Loader for Generate HCM Rates.
Associate the event action to the event action group using HCM Data Loader.

NOTE: Enable event processing using the background flow. Set the action parameter Payroll Continuous for Events Runs continuously to handle periodic requests for event processing to Y. This step is essential if you are monitoring element entry changes in your rates event action group. This setting will move all payroll event processing to a payroll process which continuously runs in the background. The evaluation and generation of all payroll event notifications and actions will no longer be performed as part of the main transactions such as a new hire.

Tips And Considerations

Run the Process Event Action flow on a daily basis to recalculate rates for all employees with a rates event notification.
Before enabling events for rates, run the Generate HCM Rates process to ensure the latest rate information is captured for all employees.

Payroll Processing

Support for Time Updates in Payroll: Upgrade Time Elements

You can now load time card updates to payroll for all time elements created prior to Update 22C. Time card information from Time and Labor or a third-party time product can be loaded into the payroll application for payment. When you make any changes to the time card only the updated time information is sent to payroll.

For example: Employee submits a weekly timecard with 7.5 hours salary per day, Monday to Friday. The time card is loaded into the payroll application. Subsequently, the employee updates the salary hours for Thursday to 8.5 hours. When time is next loaded to payroll only the 8.5 hours update will be included for the time card. If the weekly time card has already been paid, the additional 1 hour will be identified by the retropay process and paid in the next payroll period.

Only updated time entries are created.

Steps to Enable

Upgrade your time elements using the Run Feature Upgrade flow.
- Select the Upgrade Time Element for Time Update Feature.
- Optionally you can enter a Process Configuration Group.
- Enter the name of your time element to be updated in the Additional Information parameter. Alternatively, you can enter ‘%’ to run the upgrade process for all your time elements.

Set the profile option ORA_PAY_INTFC_IN_PLACE_UPDATE to Yes. By default, the profile option is set to No which means Time records are deleted and recreated when updated time card information is loaded. To disable this action, you must set the profile option to Yes so only the updated time information will now be passed to payroll.
When time card information is loaded into the payroll application, the details including costing, are held in the calculation information tables. Expand the retropay event group to include changes to these time details.
- Navigate to My Client Groups and select the Event Group task.
- Add the Calculation Range Item entity to the Entry Change for Retro event group for each type of update such as correction, insert, remove.
Take the same action if you have defined your own event group for retropay purposes.

NOTE: This feature will automatically be enabled for all new time elements created after the 22C update. Please refer to the 22C What’s New ‘ SUPPORT FOR TIME UPDATES IN PAYROLL'

Optimize Performance of Multi-Threaded Processes

The new multi-thread feature automatically identifies and assigns the number of threads and the chunk size to optimize the process.

This automatic multi-thread feature supports all multi-threaded payroll processes such as Calculate Payroll and Make EFT Payments. It also supports predefined HCM Extracts such as the Gross-to-Net report and user-defined extracts.

By default a payroll process executes in a single-threaded mode. Use the Maximum Number of Threads action parameter to enable the automatic multi-threading and chunk size feature. This parameter indicates the maximum, total number of sub-processes dynamically created for a process.

The application automatically assigns the optimum number of threads and generates multiple secondary sub-processes that are executed in parallel to optimize performance.

Here’s a list of features supported by the automatic, multi-threading parameter:

The number of threads is automatically determined based on the Maximum Number of Threads parameter plus the complexity of the process. For example, the Calculate Payroll process is a very complex process and hence the number of employees that can be calculated in each chunk is lower than less complex calculations such as retry or prepayments. As a result, the number of threads automatically assigned to the Calculate Payroll process might be higher than the number of threads used when retrying a process.

The number of threads used will not exceed the maximum number defined on the Threads action parameter. Complex processes such as the Calculate Payroll process may use the maximum number of threads you define. The default value for the number of threads is twenty.

The maximum thread setting applies to all your payrolls such as weekly and semi-monthly. The total number of employees processed in each payroll can vary. The new automatic multi-thread solution dynamically reduces the number of threads used for smaller payroll to ensure more resources are available for any other processes that can be run in parallel.

Check the log file to view the number of threads used by the process. Enable logging to view the log file for the process.

Enable the automatic, multi-thread process to optimize the performance of payroll processes and HCM extracts.

Steps to Enable

To enable the automatic, multi-thread process, perform these steps:

Edit the default process configuration group for the process and:
- Take note of the number of threads set in Threads parameter. Enter this value as the Maximum Number of Threads.
- Remove the action parameter Threads. This determines the total number of sub-processes that run under the concurrent manager.
- Remove action parameter Chunk Size. This is the number of relationship actions that should process together in chunks during the main processing phase.
- Add the action parameter Maximum Number of Threads. This parameter indicates the maximum, total number of sub-processes dynamically created for a process. The default value is 20 but enter the maximum number of threads you noted as the number of Threads value from above. This action parameter enables the automatic multi-thread and chunk size feature.

Note: The value you enter in the new Maximum Number of Threads field must be the same as that given in the Threads field. For example, if ‘20’ was defined in the Threads field, you should enter ‘20’ in the new Maximum Number of Threads field.

The Threads field determines the total number of sub-processes that run under the concurrent manager, and the new Maximum Number of Threads indicates the maximum, total number of sub-processes dynamically created for the process action parameter.

View Run Results with Element Entry Result Identifier

You can now use the new Element Entry Result Identifier attribute to easily identify the results for each entry.

Navigate: My Client Groups > Payroll > Person Results > Enter employee name in Search for Person field.

From Person Results page, choose Run Results from the Actions list for one of the processes listed.

From the Run Results page, expand the element information to view the Element Entry Result Identifier attribute.

NOTE: You must use HCM Experience Design Studio to display the new attribute in the Run Results UI. As part of standard export functionality, when displayed on the UI, the new attribute is included in the export of Run Results. See Steps to Enable below.

Identify the run results generated by a single element entry and view the new element entry result identifier on the responsive run result page.

Steps to Enable

Navigate: My Client Groups > HCM Experience Design Studio
Select Run Results from Action list.
Click Add button to open the Run Results configuration page.
Enter Rule Name and Rule Description.
Choose Role Names and Country affected.
In Page Attributes section, choose Run Results region.
Select Visible from list for the Element Entry Result Identifier attribute.
Click the Save and Close button to exit configuration page.

Verify your rule has been created.

Click Done button to exit HCM Experience Design Studio.

Tips And Considerations

This Element Entry Result Identifier will be useful to distinguish multiple entries of the same element when the export feature for the run results responsive page is delivered in a future release.

Key Resources

For more information refer to the Oracle Help Center Administering Global Payroll guide for the View and Verify Payroll Run Results.

Payroll Flows

New Process Event Action Flow for Manual Event Actions

You can now use event groups and event actions to control which employees are included in the processes, such as to generate HCM Rates and time card reprocessing. When you define an event action, you specify whether the submission of the action is automatic or manual. If the event action is a manual submission type, you can use the ‘Process Event Action’ flow to submit the process associated to the event action.

Use the ‘Process Event Action’ flow to submit all unprocessed events and associated actions with a manual submission type. For example, use the flow to calculate rates for all employees with an unprocessed rate event notification.

You can validate the results of the processes submitted by the ‘Process Event Action’ flow using the generated report. This lists all the employees included in the process, the status of the process, and any warnings or error messages. When you submit this process for HCM Rates, it generates a report with the rate values calculated for each employee included in the process.

Navigate to My Client Groups > Show more > Payroll > Submit a flow

Leave the Legislative Data Group field blank.

Use the Event Action Type field to select the type event action. For example, select the HCM Rates Recalculation event action to calculate rates for all employees with an unprocessed event.

Use the Event Action field to indicate which user-defined event actions should be included in the process event actions flow.

Tip: Leave the Legislative Data Group field blank when submitting the "Process Event Actions" flow.

This feature provides a better user experience as it supports the manual submission of the processes.

Steps to Enable

You don't need to do anything to enable this feature.

Errors and Warning Report in CSV Format for Calculate Payroll Process

When you submit the Calculate Payroll flow, the flow automatically generates the errors and warning messages CSV file. After you submit the flow, navigate to the Process Results Details page from the Checklist or Summary Results page and access the CSV file from the Output and Log Files section. You can view the error and warning messages and take corrective action for the flow.

Use the Auto Generate Errors and Warnings File action parameter to choose whether you want to generate an errors and warning messages file in the Output and Log Files section in the Process Results Details page. Create this parameter in the default group and set it to Y, so that the error and warning messages file is generated automatically after you submit the flow.

The format of the CSV file name is FLOWINSTANCE_TASKNAME_Error_Warning_PROCESSID.csv. The file has these columns.

Column Name	Description
Message Level	Indicates the type of message; Error (Failure) or Warning message.
Message ID	The ID of the warning or error message.
Source Type	The object that triggered the message.
Person Number	The ID of the person included in the report.
Line Text	The text of the error or warning message.

The list of the objects that can trigger a message and the relevant code in the file are listed in this table.

Object Name	Code
Assignment Action	A
Batch Control Level	C
Batch Header Level	H
Batch Line Level	L
Payroll Action	P
Flow Task Exception	R
Element Template Exception	T

The file is generated only if the flow has error or warning messages.

NOTE: The file doesn’t contain information messages.

After you review the error and warning messages, take corrective action, and resubmit the flow, a new output file is generated if errors still persist. If there are no errors, no output is generated.

Submit the Calculate Payroll flow and access the automatically generated error and warning messages CSV file to review the messages and take corrective actions as required.

Steps to Enable

You don't need to do anything to enable this feature.

Cancel Action

Use the Cancel action in the Checklist and Results Summary UIs to cancel all ESS threads of a flow task that are in In Progress status. A process can get stuck and have In Progress status due to various reasons. It could be due to process time lapse, an infrastructure issue such as a network failure, or an ESS failure due to patching, and so on. You would want to cancel the jobs that are stuck, take corrective action, and resubmit the process.

NOTE: Users with this duty role can cancel ESS jobs for all types of flows. For example, a user with this duty role can cancel ESS jobs for the Calculate Payroll flow, even if they don't have access to the Calculate Payroll flow and they haven't submitted the Calculate Payroll flow.

You can also cancel a specific ESS job from the Oracle Enterprise Scheduler Service (ESS) page. However, as a best practice we don't recommend you cancel ESS jobs from the ESS page because using the ESS page doesn't trigger the display of the banner message for the specific task being cancelled.

Use the Cancel action in the Checklist and Results Summary UIs to cancel all ESS threads of a flow task that are stuck or are in In Progress status.

Steps to Enable

Provide the required access before using the feature. Details are in the Access #Requirements section.

In order to allow users to access and cancel ESS jobs for flows that they did not submit, you must ensure that these users are granted with the ORA_PAY_SCHEDULED_PROCESSES_ADMINISTRATION_DUTY duty role. However, users with this role, can cancel ESS jobs of flows they can't access or haven't submitted.

Access Requirements

Users must be granted the ORA_PAY_SCHEDULED_PROCESSES_ADMINISTRATION_DUTY duty role.

Logging and Monitoring for the Payroll Background Process

Use the Payroll Background Logging and Monitoring flow to identify and resolve payroll queries for features that use the payroll background process. This flow is useful for those who manage customer environments, test payroll processes, and troubleshoot issues with payroll processes. For example, your system administer can use this flow to generate log files for features that uses the payroll background flow such as Anytime Pay.

NOTE: Payroll features that use the payroll background flow include Anytime Pay and Event Notification Processing that has rate events enabled.

The payroll background process is an ESS process that runs continuously in the background to improve the performance of payroll features. Since it runs continuously, it’s not required for the ESS server to start or stop whenever you submit a process such as the submission of the QuickPay process for Anytime Pay.

NOTE: Leave the Legislative Data Group field blank when submitting the Payroll Background Logging and Monitoring flow.

Use the Action field to perform these actions on the Payroll Background Logging and Monitoring flow.

Start Process: When called by a feature, the background payroll ESS process starts automatically and will continue to run. You can override this default behavior, by using this option and manually start the process.

Stop Process: Use this option to stop the background payroll ESS process. Any process that's already running using the payroll background process will complete, but the next process in queue will not start.

Report: Use this option to report on the status of the background payroll ESS process.

Resubmit Process: Use this option to resubmit a process submitted using the background payroll ESS process and is in error.

Use the Job Identifier field to identify the process submitted using the payroll background that needs a log file or should be resubmitted. Each background process has a job ID number, similar to an ESS job number.

Use the Report Type field to select the type of report you want to generate using this flow. These reports are intended for users who are trying to identify the root cause of an issue. The types of reports you can generate are:

Processing Report: This report displays all processes that are currently running or are in the payroll background queue for today. For example, a QuickPay has been submitted for Anytime Pay but no results are generated for the employee. Use this report to check if the QuickPay is stuck in a queue of processes waiting to be completed by the payroll background process.

Scheduled Report: This report identifies all pending processes in the payroll background queue for the specified date range.

Error Report: This report identifies all error messages for the payroll background process. For example, a QuickPay has been submitted for Anytime Pay but no results are generated for the employee. Use this report to check if the payroll background process has hit an error that stopped the submission.

Log File: Use this option to enable detailed logging information for a process submitted using the payroll background process.

NOTE: Use the predefined PAY DAEMON GROUP payroll process configuration group for processes submitted using the payroll background process.

Use the Payroll Background Logging and Monitoring flow to identify and resolve payroll queries for features that use the payroll background process.

Steps to Enable

You don't need to do anything to enable this feature.

Payroll Outputs

View Payroll Costing Results for a Subledger Journal Entry

You can now review the payroll costing results for a subledger journal entry from the Subledger Journal Lines page with the general ledger role.

Navigate: General Accounting > Journals

From side task list, select Review Subledger Journals
Use search fields to query the journal details.
Use the Search criteria on the Review Journal Entries page to narrow the entries you want to view.
Click the Search button to query the individual journal entries.
Select the individual journal entry.
Click View Journal Entry button.

From Journal Entry page, click View Transaction button.

From the Subledger Journal Lines page, review the payroll costing results for this subledger journal entry.

Review the payroll costing results for a subledger journal entry from the Subledger Journal Lines page with the general ledger role.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The person information in Costing run results drill down transaction information, such as person number, person name, is controlled by the configuration parameter ORA_PAY_XLA_HIDE_PERSON_DETAIL. If the parameter is set to Y or not set, person details on the Review Journal Entries page and in General Ledger are hidden. If the parameter is set to N, these details are displayed. Default is Y.

Key Resources

For more information on reviewing run results, refer to these resources in the Oracle Help Center:

Intermediary Bank Account Details in Payments XML

You can now include intermediary bank account details, now stored in the Payments XML, in the EFT file when it's required to facilitate an inter-country payment. For example, intermediary bank accounts are used to route payments when an employer's US based bank doesn't have relationships with banks in the developing world. The payments are sent from your company bank account to the intermediary bank account, and onto the employee’s bank account.

Use the Financials SOAP service to load intermediary bank account details for your employees. When using the Financial SOAP service, the intermediary bank accounts must be attached separately for each employee bank account.

Intermediary Bank Account Details are now stored in the Payments XML to include them in the EFT file.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

For more information on the Financial SOAP service, refer to these resources in the Oracle Help Center: SOAP Web Services for Financials guide.

Preview Payslips and Year-End Documents Feature is from a customer submitted idea.

You can now easily preview payslips and year-end PDF documents directly from the Payslip and Year-End Documents pages without having to download.

Use options in payslip preview window to zoom, scroll, print, download or save payslip document. Use back arrow to exit payslip preview window and return to payslip list.

Preview payslips and year-end documents from desktops and IOS tablets when the document type is PDF without having to download.

Steps to Enable

To enable this feature you must set the Enable PDF Document Preview Mode profile option to Y.

In the Setup and Maintenance work area, go to the profile option task that correlates to the product or functionality of the profile option you want to set. If needed, use the Manage Administrator Profile Values task, which provides access to all profile options.
Search for and select the Enable PDF Document Preview Mode profile option.
In the Profile Values section, select or enter a value in the Profile Value column for any default row with a predefined Site level.
Click Save and Close.

NOTE: Changes in the profile values affect users the next time they sign in.

Tips And Considerations

This feature is only supported for viewing PDF documents from desktops and iOS tablets.

Key Resources

For more information viewing payslips or setting profile options, refer to these resources in the Oracle Help Center:

Payroll Core

Payroll Core Support for Defaulting Tax Reporting Unit

Users who have defined an international payroll legislation such as United Nations, can now automatically assign a Tax Reporting Unit (TRU) to newly hired employees. The TRU will trigger the creation of a deduction card for the employee and the necessary TRU and assignment associations. This information ensures the international employee can be successfully processed in the Calculate Payroll process.

You can now assign to all employees, the main TRU defined for your organization. Alternatively, the TRU can be defaulted based on the currency of the salary basis that is assigned to the employee.

For an organization that has employees who are paid in multiple countries and are paid in different currencies but are within a single legislative data group, it’s essential that you define a tax reporting unit (TRU) for each currency within a PSU. This approach ensures you can calculate payroll balances for each different currency and TRU.

Use the Configure Legislations for Human Resources task to control how deduction card and associations are created. This table details the TRU Defaulting Rule options you can select.

TRU Defaulting Rule	Description
Assign employee details using main TRU	The payroll run assigns the main TRU for the organization to the newly hired employee and automatically creates the deduction card and associations at assignment level. Select this option if don't you have a need to calculate employee taxes and you are paying all employees within a legislative data group in the same currency.
Assign employee details using TRU currency	The payroll run uses the salary basis to assign the TRU with the corresponding currency to the newly hired employee and automatically creates the deduction card and associations at assignment level. The salary basis currency of an employee is derived from the input currency of the element associated to the salary basis. For example, when an employee is assigned to a salary basis with a currency of USD, they are assigned to the TRU that also has a USD currency. Select this option if you don’t have a need to calculate employee taxes. However, you have employees who are paid in different currencies within a single legislative data group. This feature enables you to group employees who are paid in the same currency to a TRU. This option facilitates separate payroll reports for each currency. Note: You must only create a single TRU for each currency. Note: When an employee moves country and payment currency you must create a new assignment. A new tax card must also be created for the new assignment.
Enter employee details	During new hire manually assign a TRU, deduction card and assignment associations to an employee. Select this option if you have a need to capture tax reporting information at employee level for tax calculation purposes.

Use the Manage Legal Reporting Unit HCM Information task to define the currency of the TRU.

Users that have defined an international payroll legislation, such as United Nations, can now automatically assign the main TRU defined for your organization, or alternatively, the TRU can be defaulted based on the salary basis that is assigned to the employee.

Users who have defined an international payroll legislation such as United Nations, can now automatically assign the main TRU defined for your organization, or alternatively, the TRU can be defaulted based on the salary basis that is assigned to the employee.

Steps to Enable

Select a ‘Deduction Card – Tax Reporting Unit Association Rule’ for your international payroll legislation.
When you select the ‘Assign employee details using TRU currency’ option you must define currency information for each TRU.

Payroll for Bahrain

Payroll for Oracle Human Capital Management for Bahrain supports country specific features and functions for Bahrain. It enables users to follow Bahrain's business practices and comply with its statutory requirements.

Global Transfer for Social Insurance and Gratuity Components with Future Dated Updates

You can now copy future-dated updates for the Social Insurance and Gratuity calculation cards during the global transfer process.

The application creates Social Insurance or Gratuity components only if the calculation card in the source legal employer contains these components. These components are effective as of the global transfer date or after the global transfer date. But the start date of the new calculation card that's created is as of the transfer date.

All date effective changes on the components such as the start and end dates, and any override amounts are preserved and copied during a change of legal employer.

You can copy future-dated changes on the payroll objects during a Global Transfer. There are two types of future changes:

Future updates to the record created as of the global transfer date.
Future record that begins after the global transfer date.

Steps to Enable

You don't need to do anything to enable this feature.

Payroll for Canada

Global Transfer - Future-Dated Changes

You can now copy future-dated updates and end-dates for Tax Credit Information and Involuntary Deduction cards during a Global Transfer.

For example, if you perform a global transfer effective December 1st, 2022 for an employee who has already updated his Tax Credit Information card effective January 1st, 2023, both the changes effective December 1st, 2022, as well as the future-dated changes are copied to the new payroll relationship created by the global transfer process.

Future-dated changes are any one of these types:

Future end-date of record as of the global transfer date
Future updates of record as of the global transfer date
Future record that begins after the global transfer date

This feature is available on both the Local and Global Transfer flows, as well as the Mass Change Legal Employer flow.

This feature delivers enhanced functionality for global transfer processing.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The Involuntary Deduction card is not copied if the Total Owed amount is already reached prior to the date of the future-dated transfer.

Key Resources

Refer to these documents on the Canada Information Center for additional information:

Canada Information Center: https://support.oracle.com/rs?type=doc&id=2102586.2
- CA – Payroll tab > Product Documentation > Payroll Guides > Administering Payroll for Canada
- CA – Payroll tab > Product Documentation > Payroll Guides > Administering Canada End-of-Year Processing
Hot Topics Email (To Receive Critical Statutory Legislative Product News) To receive important Fusion Canada Legislative Product News, you must subscribe to the Hot Topics Email feature available in My Oracle Support. Refer to the document below on the Canada Information Center for additional information: https://support.oracle.com/rs?type=doc&id=2102586.2
- Welcome tab > Other Documents > How To Use My Oracle Support Hot Topics Email Subscription Feature

Support for Dynamic Payroll Relationship Groups for Canada Reports and Processes Feature is from a customer submitted idea.

You can now use the Payroll Relationship Group parameter to run Canada reports and processes for dynamic groups of employees, rather than just a static group. The dynamic payroll relationship group option is supported by configuring a formula that will dynamically build the list of employees, based on a defined criteria.

For example, you may configure a formula to build a group of terminated employees, union employees, or employees that are on leave. You may then attach those employees to a payroll relationship group.

This feature is available for all Canada reports and processes that have the Payroll Relationship Group parameter, which are:

Archive End-of-Year Payroll Results
Provincial Medical Report
Run Employee Active Payroll Balance Report
Run End-of-Year Reports
Run Record of Employment Archive
Run Record of Employment Interface
Run Tax Overrides Report
Workers Compensation Assessable Wages Report

Additionally, we have enhanced the static payroll relationship group to introduce a new Exclude option for the Inclusion Status rule. This is used during the creation in the Object Group page. The options are:

Include: this option will include only those payroll relationship numbers defined in the object group (this is existing functionality)
Exclude: this option will exclude those payroll relationship numbers defined in the object group (this is a new option)

NOTE: You can use Include and Exclude together, which will exclude those payroll relationship numbers as defined, and only include those payroll relationship numbers defined in the object group.

This feature allows customers to limit the scope of the flow to only select individuals based on a defined criteria, rather than defining and maintaining a static list.

Steps to Enable

To enable and use this feature, do these steps:

Create a value set (this is mandatory in this example, but your use case may not require it)
Create a payroll relationship formula
Create a dynamic object group

To create a value set (using terminated employees as an example):

Navigate to Setup and Maintenance, and search for and select Manage Value Sets.
Click Create.
Enter a value set code.
Select these values to create the value set code:

Field	Value
Module	CA Payroll Archive Results
Validation Type	Table
Validation Data Type	Number

Under Definition, select or enter these values to define the value set code:

Field	Value
FROM Clause	per_periods_of_service
Value Column Name	period_of_service_id
ID Column Name	period_of_service_id
WHERE Clause	period_of_service_id =(select MAX(pps.period_of_service_id) from per_all_assignments_m paa, per_periods_of_service pps,pay_pay_relationships_dn prd where paa.legal_entity_id = prd.PAYROLL_STAT_UNIT_ID AND paa.person_id = (select DISTINCT PERSON_ID from fusion.pay_pay_relationships_dn where PAYROLL_RELATIONSHIP_ID= :{PARAMETER.CA_PAYROLL_RELATIONSHIP_ID}) AND paa.person_id=prd.person_id AND paa.system_person_type != 'PWK' AND pps.person_id = paa.person_id AND pps.period_of_service_id = paa.period_of_service_id AND paa.legal_entity_id = pps.legal_entity_id AND pps.period_type != 'O' AND pps.actual_termination_date IS NOT NULL AND to_date(:{PARAMETER.CURRENT_EFFDATE},'YYYY/MM/DD') >= pps.ACTUAL_TERMINATION_DATE AND pps.date_start = ( SELECT MAX(ppsnew.date_start) FROM fusion.per_periods_of_service ppsnew, fusion.per_all_assignments_m paanew WHERE ppsnew.person_id = pps.person_id AND paanew.person_id = pps.person_id AND ppsnew.period_of_service_id = paanew.period_of_service_id AND ppsnew.period_type != 'O' AND paanew.system_person_type != 'PWK' AND paanew.assignment_type NOT IN ( 'O', 'OT' ) AND to_date(:{PARAMETER.CURRENT_EFFDATE},'YYYY/MM/DD') >= ppsnew.date_start) )

Click Save and Close.

To create a payroll relationship formula (this formula will call the value set to determine if the person is active or not. If the person is terminated, the formula will return a value of ‘Y’):

Navigate to My Client Groups > Payroll > Fast Formulas.
Click Create.
Enter a formula name.
Select or enter these values to define the fast formula:

Field	Value
Type	Payroll Relationship Group
Legislative Data Group	Select the appropriate Canadian LDG
Effective Start Date	Select the start date of the formula
Type of Editor	Text

Click Continue.
Enter the formula text. Using the value set created above (RLH_TERMINATED), use this formula text:

Note: This is simply an example to determine whether an employee is terminated. You can configure different formulas to meet your reporting requirements.

Formula Text
DEFAULT_DATA_VALUE FOR PERSON_GROUP_LEVEL_SUMMARY_FORMULA_NAME is 'null' NEED_CONTEXT(PAYROLL_RELATIONSHIP_ID) NEED_CONTEXT(PAYROLL_TERM_ID) NEED_CONTEXT(PAYROLL_ASSIGNMENT_ID) NEED_CONTEXT(LEGISLATIVE_DATA_GROUP_ID) NEED_CONTEXT(PAYROLL_ID) NEED_CONTEXT(DATE_EARNED) NEED_CONTEXT(EFFECTIVE_DATE) SET_INPUT('level_name', 'PAY_REL') INCLUDE_FLAG = 'N' L_PAYROLL_RELATIONSHIP_ID = GET_CONTEXT(PAYROLL_RELATIONSHIP_ID,0) l_eff_date = GET_CONTEXT(EFFECTIVE_DATE,'0001/01/01' (date)) dummy = PAY_INTERNAL_LOG_WRITE('L EFFECTIVE DATE: '+TO_CHAR(trunc(l_eff_date),'YYYY/MM/DD')) l_person_id = GET_VALUE_SET('RLH_TERMINATED' ,'\|=CA_PAYROLL_RELATIONSHIP_ID='''\|\|to_char(L_PAYROLL_RELATIONSHIP_ID)\|\|''''\|\|'\|CURRENT_EFFDATE='''\|\|TO_CHAR(trunc(l_eff_date),'YYYY/MM/DD')\|\|'''') dummy = PAY_INTERNAL_LOG_WRITE('PERSON ID : '+l_person_id ) IF ISNULL(l_person_id) = 'Y' THEN ( INCLUDE_FLAG = 'Y' dummy = PAY_INTERNAL_LOG_WRITE('ENTERING LOOP : '+INCLUDE_FLAG ) ) dummy = PAY_INTERNAL_LOG_WRITE('INCLUDE FLAG : '+INCLUDE_FLAG ) RETURN INCLUDE_FLAG

Formula Text

DEFAULT_DATA_VALUE FOR PERSON_GROUP_LEVEL_SUMMARY_FORMULA_NAME is 'null'

NEED_CONTEXT(PAYROLL_RELATIONSHIP_ID)

NEED_CONTEXT(PAYROLL_TERM_ID)

NEED_CONTEXT(PAYROLL_ASSIGNMENT_ID)

NEED_CONTEXT(LEGISLATIVE_DATA_GROUP_ID)

NEED_CONTEXT(PAYROLL_ID)

NEED_CONTEXT(DATE_EARNED)

NEED_CONTEXT(EFFECTIVE_DATE)

SET_INPUT('level_name', 'PAY_REL')

INCLUDE_FLAG = 'N'

L_PAYROLL_RELATIONSHIP_ID = GET_CONTEXT(PAYROLL_RELATIONSHIP_ID,0)

l_eff_date = GET_CONTEXT(EFFECTIVE_DATE,'0001/01/01' (date))

dummy = PAY_INTERNAL_LOG_WRITE('L EFFECTIVE DATE: '+TO_CHAR(trunc(l_eff_date),'YYYY/MM/DD'))

l_person_id = GET_VALUE_SET('RLH_TERMINATED' ,'|=CA_PAYROLL_RELATIONSHIP_ID='''||to_char(L_PAYROLL_RELATIONSHIP_ID)||''''||'|CURRENT_EFFDATE='''||TO_CHAR(trunc(l_eff_date),'YYYY/MM/DD')||'''')

dummy = PAY_INTERNAL_LOG_WRITE('PERSON ID : '+l_person_id )

IF ISNULL(l_person_id) = 'Y' THEN

(

INCLUDE_FLAG = 'Y'

dummy = PAY_INTERNAL_LOG_WRITE('ENTERING LOOP : '+INCLUDE_FLAG )

)

dummy = PAY_INTERNAL_LOG_WRITE('INCLUDE FLAG : '+INCLUDE_FLAG )

RETURN INCLUDE_FLAG

Click Submit, then Compile.

To create a dynamic object group:

Navigate to My Client Groups > Payroll > Object Groups.
Click Create.
Enter an object group name.
Select these values to define the dynamic object group:

Field	Value
Legislative Data Group	Select the appropriate Canadian LDG
Type	Payroll Relationship Group
Static or Dynamic	Dynamic

Click Continue.
Under the Payroll Relationship Rules section, click Add.
Select the fast formula created in the previous step.

Click Next, then Submit.

For additional information on creating value sets, fast formulas, or object groups, refer to the Administering Global Payroll guide on the Oracle Help Center.

For additional information on creating fast formulas, refer to the Administering Fast Formulas guide on the Oracle Help Center.

Tips And Considerations

You can configure your own fast formulas to meet your reporting requirements.

Key Resources

Refer to these documents on the Canada Information Center for additional information:

Oracle Help Center: Administering Global Payroll, Administering Fast Formulas

Canada Information Center: https://support.oracle.com/rs?type=doc&id=2102586.2
- CA – Payroll tab > Product Documentation > Payroll Guides > Administering Payroll for Canada
- CA – Payroll tab > Product Documentation > Payroll Guides > Administering Canada End-of-Year Processing

Hot Topics Email (To Receive Critical Statutory Legislative Product News) To receive important Fusion Canada Legislative Product News, you must subscribe to the Hot Topics Email feature available in My Oracle Support. Refer to the document below on the Canada Information Center for additional information: https://support.oracle.com/rs?type=doc&id=2102586.2
- Welcome tab > Other Documents > How To Use My Oracle Support Hot Topics Email Subscription Feature

QTD Dimensions Added to Employee Active Payroll Balance Report Feature is from a customer submitted idea.

You can now run the Employee Active Payroll Balance Report to view quarter-to-date balances. The report now includes these new options for the Balance Dimension parameter:

Quarter
Quarter and Year

Once you select Quarter or Quarter and Year in the Balance Dimension parameter, the values presented to you in the Quarter parameter is dependent on the Start Date and End Date parameters. For example, if the Start Date is 1/1/21 and the End Date is 12/31/21, you will be presented with all four quarters to select, or All.

Similarly, if the Start Date is 1/1/21 and the End Date is 6/30/21, you will be presented with only the quarters applicable to that date range.

Also, if you select Quarter or Quarter and Year in the Balance Dimension parameter, this determines the values presented for selection in the Balance Group Usages parameter. Only the applicable quarter-to-date dimensions are presented for selection.

The amounts are displayed on the report for each quarter selected. If Quarter and Year was selected, the balances are also reported for the year, which is a sum of the quarters reported. As an example, for this report, the parameters were populated as:

Balance Dimension = Quarter and Year
Quarter = Quarter 1, 2
Balance Group Usage = Canadian Employer Liabilities Quarter and Year Balance Group Usage

This feature supports the ability to perform quarterly reconciliation, which will help common customers of US and Canada localizations.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The parameter values presented are dynamic and dependent on the Start and End Date parameters.

Key Resources

Refer to these documents on the Canada Information Center for additional information:

Canada Information Center: https://support.oracle.com/rs?type=doc&id=2102586.2
- CA – Payroll tab > Product Documentation > Payroll Guides > Administering Payroll for Canada
- CA – Payroll tab > Product Documentation > Payroll Guides > Administering Canada End-of-Year Processing
Hot Topics Email (To Receive Critical Statutory Legislative Product News) To receive important Fusion Canada Legislative Product News, you must subscribe to the Hot Topics Email feature available in My Oracle Support. Refer to the document below on the Canada Information Center for additional information: https://support.oracle.com/rs?type=doc&id=2102586.2
- Welcome tab > Other Documents > How To Use My Oracle Support Hot Topics Email Subscription Feature

Annualize Salary for Taxation of Nonperiodic Earnings with no Regular Earnings

An employee’s periodic regular earnings are now derived from the salary basis for federal and provincial tax calculation purposes when nonperiodic earnings are processed in the absence of regular earnings, in the current or previous pay period.

When a nonperiodic payment is processed, the hierarchy of logic is processed in the following order to determine the employee’s regular periodic earnings for tax calculation purposes:

Look for regular earnings in the current pay period. If no, then
Look for regular earnings in the prior pay period. If no, then
Derive the regular periodic earnings from the employee’s salary basis.

This feature provides an additional option to derive the regular pay, when a nonperiodic payment is paid without any regular earnings in the current or previous pay period.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

In order for this feature to work properly, in the absence of regular earnings in the current or prior period, the employee’s salary basis must be configured. This is because the employee’s regular periodic earnings are derived from the salary basis, in the absence of regular earnings.

Key Resources

Hot Topics Email (To Receive Critical Statutory Legislative Product News) To receive important Fusion Canada Legislative Product News, you must subscribe to the Hot Topics Email feature available in My Oracle Support. Refer to the document below on the Canada Information Center for additional information: https://support.oracle.com/rs?type=doc&id=2102586.2
- Welcome tab > Other Documents > How To Use My Oracle Support Hot Topics Email Subscription Feature

Payroll for China

Payroll for Oracle Human Capital Management for China supports country specific features and functions for China. It enables users to follow China's business practices and comply with its statutory requirements.

Enhanced Tax Component Details Management During Global Transfers and Rehires

You can handle the changes during the employee global transfer and rehire process, using the enhanced tax component details management. When employees are transferred to a legal employer within the same payroll statutory unit, or rehired, and a tax reporting unit is specified, the system updates the tax component details on the transfer or rehire date. This happens only when one of the following three attributes is not blank. The attributes include:

Use Annual Exemption in Monthly Calculation
Tax Reporting Unit Hire Date
Tax Reporting Unit Termination Date

There are no values for the three attributes in the update record.

In the rehiring process, you need to specify a tax reporting unit, for the system to create the update records. The system updates the tax component details only if there is a null value for one of the three attributes.

If there are future updates beyond the transfer or rehire date, the system corrects the future records by setting null values for the three attributes.

This feature requires less maintenance, hence increases productivity.

Steps to Enable

You don't need to do anything to enable this feature.

Payroll for Kuwait

Payroll for Oracle Human Capital Management for Kuwait supports country specific features and functions for Kuwait. It enables users to follow Kuwait business practices and comply with its statutory requirements.

Global Transfer for Social Insurance and Gratuity Components with Future Dated Updates

You can now copy future-dated updates for the Social Insurance and Gratuity calculation cards during the global transfer process.

All date effective changes on the components such as the start and end dates, and any override amounts are preserved and copied during a change of legal employer.

You can copy future-dated changes on the payroll objects during a Global Transfer. There are two types of future changes:

Future updates to the record created as of the global transfer date.
Future record that begins after the global transfer date.l transfer date.

Steps to Enable

You don't need to do anything to enable this feature.

Payroll for Mexico

Payroll for Oracle Human Capital Management for Mexico supports country specific features and functions for Mexico. It enables users to follow Mexico's business practices and comply with its statutory requirements.

Economic Zone Override Feature is from a customer submitted idea.

The Employee Tax Card now supports the override of the economic zone in the Employee Social Security section. You can override the economic zone for an individual employee in a tax reporting unit that is located across economic zones.

By default, the economic zone in the Employee Tax Card will show the value defaulted from the tax reporting unit (TRU) or payroll statutory unit (PSU) organization card if it's been entered; otherwise it will show "GMW" for general minimum wage.

Employee Tax Card

The addition of the economic zone override at the employee level provides greater flexibility in the calculation of social security for employees.

Steps to Enable

You don't need to do anything to enable this feature.

Payroll for Oman

Payroll for Oracle Human Capital Management for Oman supports country specific features and functions for Oman. It enables users to follow Oman's business practices and comply with its statutory requirements.

Social Insurance for Oman Citizens Feature is from a customer submitted idea.

With this enhancement, calculate social insurance contributions accurately with the delivered legislative rules and information for the citizens of Oman. In order to calculate the social insurance, information such as the Employer type, the Contributory Salary reference formula, Registered for Social Insurance, and Sector is required.

You can use the Organization Calculation Card to specify the Employer Type, Sector, and any Contributory reference formula. The Person Calculation Card provides details of the Citizenship of the employee, whether registered for Social Insurance and Exempt from SI Contribution Difference. You can also specify Override and Adjustment amounts to update the Contributory Salary.

The Contributory Salary balance is the basis for the calculation of social insurance. The Contributory Salary Override value is considered in the first month of payroll processing for the employee (when a new hire) or in the first month of the year (January). If there is no override specified, then the user-defined formula is used.

If the employee is an Omani citizen, the contributory salary is used as a base to calculate both employee and employer contributions subject to a minimum of 180 OMR (Private Sector) and a maximum of 3000 OMR, and a maximum of 3000 OMR (Government Sector), but no minimum salary range.

The application considers the employee's basic contribution in a private sector as 7% of the contributory salary. For the employer's basic contribution in the Government Sector, the application calculates 17.7% of the contributory salary.

NOTE: For the employer's basic contribution in a Private Sector, the application calculates the employer's basic contribution as 10.5% of the contributory salary and the employer's hazards contribution as 1% of the contributory salary.

The Employee Social Insurance Details calculation card is created automatically and is associated with the TRU for all employees working in Oman when a Payroll Relationship is created.

Calculate social insurance contributions accurately with the delivered legislative rules and information for citizens of Oman.

Steps to Enable

You don't need to do anything to enable this feature.

Payroll for Qatar

Payroll for Oracle Human Capital Management for Qatar supports country specific features and functions for Qatar. It enables users to follow Qatar business practices and comply with its statutory requirements.

Global Transfer for Social Insurance and Gratuity Components with Future Dated Updates

You can now copy future-dated updates for the Social Insurance and Gratuity calculation cards during the global transfer process.

All date effective changes on the components such as the start and end dates, and any override amounts are preserved and copied during a change of legal employer.

You can copy future-dated changes on the payroll objects during a Global Transfer. There are two types of future changes:

Future updates to the record created as of the global transfer date.
Future record that begins after the global transfer date.l transfer date.

Steps to Enable

You don't need to do anything to enable this feature.

Payroll for Saudi Arabia

Payroll for Oracle Human Capital Management for Saudi Arabia supports country specific features and functions for Saudi Arabia. It enables users to follow Saudi Arabia's business practices and comply with its statutory requirements.

Global Transfer for GOSI and Gratuity Components with Future Dated Updates

You can now copy future-dated updates for the GOSI and Gratuity calculation cards during the global transfer process.

All date effective changes on the components such as the start and end dates, and any override amounts are preserved and copied during a change of legal employer.

You can copy future-dated changes on the payroll objects during a Global Transfer. There are two types of future changes:

Future updates to the record created as of the global transfer date.
Future record that begins after the global transfer date.l transfer date.

Steps to Enable

You don't need to do anything to enable this feature.

Payroll for the United Arab Emirates

Payroll for Oracle Human Capital Management for the United Arab Emirates supports country specific features and functions for the United Arab Emirates. It enables users to follow the United Arab Emirates business practices and comply with its statutory requirements.

Global Transfer for Social Insurance and Gratuity Components with Future Dated Updates

You can now copy future-dated updates for the Social Insurance and Gratuity calculation cards during the global transfer process.

All date effective changes on the components such as the start and end dates, and any override amounts are preserved and copied during a change of legal employer.

You can copy future-dated changes on the payroll objects during a Global Transfer. There are two types of future changes:

Future updates to the record created as of the global transfer date.
Future record that begins after the global transfer date.l transfer date.

Steps to Enable

You don't need to do anything to enable this feature.

Payroll for the United Kingdom

Global Transfer for Student Loan and Postgraduate Loan Components with Future-Dated Updates

You can now copy future-dated updates for the Court Order and Student Loans calculation cards during the global transfer process.

The application creates Student Loan or Postgraduate Loan components only if the calculation card in the source legal employer contains these components. The student loan or postgraduate loan components are effective as of the global transfer date or after the global transfer date. But the start date of the new calculation card that's created is as of the transfer date.

All date effective changes on the components such as the start and end dates of the loan deductions, and any override amount are preserved and copied during a change of legal employer. Note that only one student loan component and postgraduate loan component is copied in the new calculation card that's created in the target legal employer.

You can copy future-dated changes on the payroll objects during a Global Transfer. There are two types of future changes:

Future updates to the record created as of the global transfer date.
Future record that begins after the global transfer date.

Steps to Enable

You don't need to do anything to enable this feature.

Payroll for the United States

Start-of-Year Flow Enhancement for Exempt Details Update Options

We have enhanced the Start-of-Year flow with the inclusion of additional options when running the Exempt details update data type.

These new options allow more flexibility when resetting exemptions on the tax card.

All States for SIT
State SIT
All States for SUI
State SUI
All States for SDI
State SDI
All States for FLI/MLI
State FLI/MLI Tax
Federal Income Tax
Medicare
Social Security

This feature expands the exemptions available for reset when you run the Start-of-Year flow.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Administering US End-of-Year Processing guide on Oracle Help Center.

Start-of-Year Flow Enhancement for 457 Limit Update

We have enhanced the Start-of-Year flow when running the 457 limit update data type. The flow now end-dates the Accumulated Under-Utilized Contributions for Special 457 (b) Catch-Up calculation value on the Benefits and Pensions card as of 12/31 for the previous effective year.

This feature will help users ensure they enter the updated under-utilized contribution amount for each eligible employee for the upcoming year.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

For employees eligible for special 457 (b) catch-up, you must enter the current under-utilized contribution amount at the start of each eligible calendar year.

Key Resources

Special 457 (b) Catch-Up Contributions in the Oracle Help Center.

Perform Multiple Tax Balance Adjustments for Third-Party Payments Using HCM Data Loader

We have made it easier for you to perform tax balance adjustments for third-party payments for multiple employees. You can now use HCM data loader (HDL) to perform these balance adjustments in one batch for common payroll transactions, such as third-party sick pay, stock option exercises, and moving and relocation transactions.

To perform these tax balance adjustments:

Use the Load Data from File flow to upload the HDL CSV file.

This flow runs these processes.

Generate Data Loader File

This process uses a new fast formula that uses the data from the CSV to create a batch header and lines in the HDL .dat file format expected by the Adjust Multiple Balances flow.

Initiate Data Loader

Run the Adjust Multiple Balances flow.

This feature enables you to leverage the power of HCM Data Loader to perform multiple tax balance adjustments in one batch.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The sample CSV and fast formula is available for download from the HCM Resource Center on Cloud Customer Connect (Template: Sample CSV and Fast Formula for US Tax Balance Adjustments). Ensure these files meet your business requirements, and adjust them as needed.

The structure of the CSV file is fixed. If you change it, you must also change the fast formula appropriately.

Employees within the batch must be in the same payroll and have the same effective date.

Before you can perform multiple tax balance adjustments with this process, do the following.

Use the Manage Common Lookup task to define a default source system owner.
Edit the new fast formula to replace TESTBA with the name of the source system owner you defined.

Key Resources

HCM Resource Center on Cloud Customer Connect (Template: Sample CSV and Fast Formula for US Tax Balance Adjustments)
US Information Center (2102586.2) on My Oracle Support
Oracle Fusion Cloud HCM: HCM Data Loader guide on the Oracle Help Center

Periodic Payroll Archive Enhancement to Capture Employer Phone Number

We have augmented the Periodic Payroll Archive process to capture your employer phone number defined at the legal reporting unit level. This enables you to include it on your employee payslips.

This feature satisfies the legislative requirements for New York, Hawaii, and Oregon.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

To capture this number on the archive, use the Manage Contact task to update an existing contact with the employer phone number or create one.

This contact must:

Have an effective date early enough to cover any historical reprinting of payslips.
Have a contact point with the following.

Phone contact point type
Land type
Effective from date early enough to cover historical reprinting of payslips

Have a contact role with the Payroll representative legal role.

When you run the Archive Periodic Payroll Results process, it captures the phone number based on the following.

It identifies the contacts having the Payroll representative contact role.
Of those, it identifies the contacts whose primary phone number is associated with a Phone contact point type and Land type.
In cases where there are multiple contacts meeting these criteria, it picks the one with the latest effective date.

When you generate the payslips, it displays the phone number in the Tax Reporting Unit Address section by default. You can change the location by modifying the payslip template.

Key Resources

Administering Payroll for the United States guide in Oracle Help Center.

Transactional Business Intelligence for Payroll

Oracle Transactional Business Intelligence is a real time, self-service reporting solution offered to all Oracle Cloud application users to create ad hoc reports and analyze them for daily decision-making. Oracle Transactional Business Intelligence provides human resources managers and specialists, business executives, and line managers the critical workforce information to analyze workforce costs, staffing, compensation, performance management, talent management, succession planning, and employee benefits.

Don’t want to start from scratch building a report or analytics? Check out the library of sample reports for all products on Customer Connect on the Report Sharing Center.

Enhancements to Payroll Flows Subject Area

There are changes to the subject area Payroll - Payroll Flows Real Time that are detailed below:

Folder	New Attributes
Flow Instance	Flow Group Status Code Flow Group Status Flow Substatus Code Flow Substatus Number of Tasks Completed Tasks
Payroll Task Instance	Flow Task Status Code Flow Task Status Flow Task Substatus Code Flow Task Substatus

Enhance your reporting on payroll flows with the addition of the new attributes and metrics related to flow status and sub statuses.

Steps to Enable

You don't need to do anything to enable this feature.

Enhancements to Payroll Run Costing Real Time Subject Area

The following new dimensions are added in Payroll - Payroll Run Costing Real Time subject area:

Distributed Element : This folder contains Distributed Element details. Similar to existing Element folder, Distributed Element folder is secured to report on payroll element data.
Distributed Input Value : This folder contains Distributed Input Value details. Similar to existing Input Value folder, Distributed Input Value folder is not secured.

Additionally the following attribute has been added in the existing folder Payroll Run Costing Details: Distributed Run Result ID.

Enhance your reporting on the payroll costing results with the addition of new dimensions to report on distributed element details and distributed input values.

Steps to Enable

You don't need to do anything to enable this feature.

IMPORTANT Actions and Considerations for Payroll

REPLACED OR REMOVED FEATURES

From time to time, Oracle replaces existing Cloud service features with new features or removes existing features. When a feature is replaced the older version may be removed immediately or at a future time. As a best practice, you should use the newer version of a replaced feature as soon as the newer version is available.

Product	Removed Feature	Target Removal	Replacement Feature	Replaced In	Additional Information
	Nothing at this time.

_________________________

KNOWN ISSUES / MAINTENANCE PACK SPREADSHEETS

Oracle publishes a Known Issues document for every Update to make customers are aware of potential problems they could run into and the document provides workarounds if they are available.

Oracle also publishes Maintenance Pack and Statutory Maintenance Pack documentation of bugs that are fixed in the monthly or statutory patching.

To review these documents you must have access to My Oracle Support:

Oracle Human Capital Management Cloud Functional Known Issues and Maintenance Packs (Document ID 1554838.1)

Employee	NI Rate
Not-contracted out	12%
Married woman reduced rate	5.85%
Earnings > UEL	2%
Employer	NI Rate
Not-contracted out	13.8%
Not-contracted out: Reduced Under Age 21 up to UST	0%
Not-contracted out: Apprentice Under Age 25 up to AUST	0%
Not-contracted out: Freeports up to FUST	0%
Not-contracted out: Veterans up to VUST	0%

Employee	NI Rate
Not-contracted out for Directors for 2022-23	12.73%
Married woman reduced rate for Directors for 2022-23	6.58%
Earnings > UEL for Directors for 2022-23	2.73%
Employer	NI Rate
Not-contracted out for Directors for 2022-23	14.53%