Oracle Workforce Rewards Cloud 19C What's New

SEPTEMBER MAINTENANCE PACK FOR 19C

Revision History
Overview
Feature Summary
Payroll
1. Payroll for the United States
  1. 1. Enable Mid-Day Overtime Period at the LDG Level

AUGUST MAINTENANCE PACK FOR 19C

Revision History
Overview
Feature Summary
Payroll
1. Payroll for the United Kingdom
  1. 1. Average Weekly Earnings for Absences

Update 19C

Revision History
Overview
Feature Summary
Benefits
1. Benefits
  1. 1. Set Up User Enterable Vacation or Sick Time Sell Plans
    2. Use the Multi-Threaded Assign Corrective Potential Life Event Process
Compensation and Total Compensation Statement
1. Compensation
Payroll
HR Optimization
1. Workforce Rewards Transactional Business Intelligence
  1. Compensation
  2. 1. OTBI Additional Percentage Columns - Workforce Compensation Budget Subject Area

September Maintenance Pack for 19C

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	Feature	Notes
30 AUG 2019		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 (19A, 19B, 19C, and 19D)
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.

This document outlines the information you need to know about new or improved functionality in Oracle HCM Cloud. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

In addition to this document you will also want to review the 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 HCM Cloud release documents are delivered in five functional groupings:

Field Name	What you Enter
From Value	0
To Value	999999
Text	Y

Field Name	What you Enter
From Value	0
To Value	999999
Text	Y

Date	Feature	Notes
26 JUL 2019		Created initial document.

Date	Feature	Notes
27 SEP 2019	Compensation: Disable Edit Button in BI Publisher Notifications	Updated document. Delivered feature in update 19C.
27 SEP 2019	Compensation: Enable Disclosure in Approval Details Section of the BI Publisher Notifications	Updated document. Delivered feature in update 19C.
30 AUG 2019	Compensation: Sort Visible Worksheet Rows	Updated document. Delivered feature in update 19C.
30 AUG 2019	Compensation: Mark Assignments as Processed or Partially Processed	Updated document. Delivered feature in update 19C.
26 JUL 2019	Compensation: Apply User Preference Only if Action Is Available in Task	Updated document. Delivered feature in update 19C.
26 JUL 2019	Compensation: Change to Cross Plan Updates in The Start and Refresh Processes	Updated document. Delivered feature in update 19C.
26 JUL 2019	Compensation: Limit Simple Export Option in Tree View When Team Size Is Greater Than 500	Updated document. Delivered feature in update 19C.
26 JUL 2019	Compensation: Limit Use of Expand or Collapse All in Tree View When Team Size Is Greater Than 500	Updated document. Delivered feature in update 19C.
26 JUL 2019	Compensation: Receive Warning When Changing Currency Conversion Rates	Updated document. Delivered feature in update 19C.
26 JUL 2019	Compensation: Validate Element Input Values in Individual Compensation Pages	Updated document. Delivered feature in update 19C.
26 JUL 2019	Compensation: Total Compensation Statement Printable Statement Enhancements	Updated document. Revised feature information.
26 JUL 2019	Global Payroll: Quick Retroactive Pay for Single Worker	Updated document. Revised feature information.
07 JUN 2019		Created initial document.

Suggested Reading for all HCM Products:

HCM Cloud Common Features (This document pertains to all HCM applications. It is the base human resource information for all products and HCM Tools.)
Global Human Resources Cloud (Global Human Resources contains the base application in which other application use for common data such as workforce structures and person information. Regardless of what products you have implemented you may want to see the new features for Global Human Resources that could impact your products.)

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

Optional Reading for HCM Products (Depending on what products are in your cloud service):

Talent Management Cloud (All Talent applications)
Workforce Rewards Cloud (Compensation, Benefits, Payroll and Global Payroll Interface)
Workforce Management Cloud (Absence Management and Time and Labor)

Additional Optional Reading:

Common Technologies and User Experience (This documents the common features across all Cloud applications and is not specific to HCM)

NOTE: All of these documents can be found on the Oracle Help Center at: https://cloud.oracle.com/saasreadiness/hcm under Human Capital Management Release Readiness.

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.			Customer Must Take Action before Use by End Users (Feature Delivered Disabled) Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.
Feature	Report	UI or Process-Based: Small Scale	UI or Process-Based: Larger Scale*	Customer Action Required
Benefits
Benefits
Set Up User Enterable Vacation or Sick Time Sell Plans
Use the Multi-Threaded Assign Corrective Potential Life Event Process
Compensation and Total Compensation Statement
Compensation
Quick Action Introduction for Team Compensation Page Used by Line Managers
New Personal Contribution Submission While an Existing Contribution Is Pending Approval
Configurable Salary Error Conditions for Grade Step Progression Batch Processes
Transactions Pending Approval Checked While Loading Salary
Post Compensation Allocations Separately by Type
Restrict Performance Documents by Period
Update Development Goal Rating Within a Compensation Cycle
Use Amount or Percent in the Downloaded Workbook
Total Compensation Statement Printable Statement Enhancements
Configure Workforce Compensation Administration Reports
Apply User Preference Only if Action Is Available in Task
Limit Simple Export Option in Tree View When Team Size Is Greater Than 500
Limit Use of Expand or Collapse All in Tree View When Team Size Is Greater Than 500
Change to Cross Plan Updates in The Start and Refresh Processes
Sort Visible Worksheet Rows
Validate Element Input Values in Individual Compensation Pages
Receive Warning When Changing Currency Conversion Rates
Mark Assignments as Processed or Partially Processed
Disable Edit Button in BI Publisher Notifications
Enable Disclosure in Approval Details Section of the BI Publisher Notifications
Payroll
Global Payroll
Quick Retroactive Pay for Single Worker
Support for Latest Person Search on Payroll Pages
Read-Only Version of Manage Payroll Relationship
Security Enhancement for Manage Calculation Entries
Display Person Number on Personal Payment Method, Payslip and Year-End Documents
Removal of Unprocessed Payroll Element Batches Created by HCM Data Loader Will Remove Notifications
Display All Hours in Payroll Reports
Data Security in Payroll Data Validation Report
Payroll and Time Definition List of Values REST API
Payroll for Canada
Iterative Pretax Deduction Calculation Enhancement
Upgrade Process for Pretax and Involuntary Deduction Elements
User-Defined Absence Secondary Classifications
Year-End Documents Publish Date
Payroll for China
Updated Tax Calculation to Support 2019 Tax Reform
Enhanced Voluntary Deduction Element Template
Payroll for Kuwait
Auto Calculation Cards - Missing TRU Message
Global HR Contract End Date Uptake
Delete Archive and Retention Period Uptake
Payroll for Qatar
Auto Calculation Cards - Missing TRU Message
Qatar Retro for Social Insurance and Gratuity
Delete Archive and Retention Period Uptake
Payroll for the United Arab Emirates
Global HR Contract End Date Uptake
Auto Calculation Cards - Missing TRU Message
Data Validation Report Update
Delete Archive and Retention Period Uptake
Payroll for the United Kingdom
FPS Process to Update Tax Code For Payments Made After Termination
Pensions Automatic Enrolment Enhancement to Support Multiple Assignments
LGPS - Additional Pension Contributions
Payroll for the United States
Enhanced Federal Tax Withholding for Supplemental Earnings
Periodic Archive and Payslip Enhancement for Overtime Calculation
HR Optimization
Workforce Rewards Transactional Business Intelligence
Compensation
OTBI Additional Percentage Columns - Workforce Compensation Budget Subject Area

Benefits

Oracle Benefits is a complete, configurable and flexible global solution that enables organizations to successfully evolve and adapt to the unique needs of their workforce. The solution enables setup of traditional 'one-size fits all' plans to highly complex plans that selectively target different workforce segments with different benefit packages. Self-service capabilities present the user with an out of the box intuitive guided enrollment process with contextual information and embedded analytics.

Set Up User Enterable Vacation or Sick Time Sell Plans

Benefits administrators can now offer greater flexibility for participants to sell their sick or vacation time during open enrollment or during an annual anniversary. When you configure these sell plans, you can now enable participants to enter the number of hours or days that they want to sell instead of having to select from a list.

Previously, the only configuration option available was that participants could select from a predefined list. You can continue to configure predefined lists of values, but remember, you can’t have a mix of both systems. For example, you could configure a vacation sell plan that allows participants to enter an amount, or select from a list of values, but not both.

There is no change to the rest of the integration with Absence Management in terms of defining user values as list value items that users can select during enrollment.

Sick Sell Plan During an Enrollment Window

In addition, you can also have participants sell partial days by including decimals in values in a predefined list. For example, participants can select 2.5 days to sell.

If you’re selling time off on behalf of participants in the Enrollment work area, you have the same flexibility to enter values instead of selecting from a list.

Plans in the Enrollment Work Area

Steps to Enable

You need to do the following setup before using this feature:

Set up enterable user values in the existing Manage Rate and Coverage User Values page. To add a new user enterable value, you enter the name and description as usual, but you also need to select the new Enter amount at enrollment check box. That's the option that enables participants to enter a value instead of selecting from a list.

When you select this check box, three new fields appear. These fields enable you to enter the minimum, maximum and incremental user values. For example, you can have the participant sell 2 to 8 days of time off, in increments of 2, as shown in this screen image.

How You Set Up User Enterable Values

If you want participants to be able to sell partial time off days, just enter the amounts in the Minimum Value and Maximum Values fields. For example, you can enter 0.5 as the minimum value and 7.5 as the maximum value. During enrollment, participants can enter a value, such as 1.5.

When you select the Enter amount at enrollment check box, the Create option for the user values region below is unavailable, preventing you from entering non enterable user values.

Tips And Considerations

For a given plan that you want to enable for selling time off, you need to configure its user values to either allow user entry, or prevent user entry. You can’t have a mix of both configurations. When you associate a variable rate profile with a rate, you need to ensure that the rate’s user value configuration (to enable or disable user entry during enrollment) is the same as that of the variable rate’s user value configuration.

When you associate a variable rate with a rate, ensure that both their calculation methods are of type User Values.

Key Resources

Watch Benefits Administrative Enhancements Readiness Training

Use the Multi-Threaded Assign Corrective Potential Life Event Process

Take advantage of the performance improvements that the multi-threaded Assign Corrective Life Events Process now offers. Previously, the single-threaded Assign Corrective Potential Life Event process took longer to finish, especially with large organizations when a person selection formula was used.

Plans in the Enrollment Work Area

Steps to Enable

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

Key Resources

Watch Benefits Administrative Enhancements Readiness Training

Compensation and Total Compensation Statement

Compensation

Oracle Compensation enables your organization to plan, allocate, and communicate compensation using the most complete solution in the market. Make better business decisions using embedded analytics and a total compensation view of workers, regardless of geographic location or pay package components.

Quick Action Introduction for Team Compensation Page Used by Line Managers

Open the compensation details page of My Team using the new My Team Compensation quick action.

Quick Action

My Team Compensation

Team Compensation Deep Link

Steps to Enable

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

New Personal Contribution Submission While an Existing Contribution Is Pending Approval

You now have the flexibility to allow or disallow an employee to submit a new personal contribution when they have an earlier contribution pending approval.

Steps to Enable

To enable this functionality, you need to enable the profile option CMP_DISABLE_PENDING_APPROVALS_CHECK_IN_MANAGE_CONTRIBUTION and disallow updates and deletions by employees, to prevent any potential conflicts. Line managers, compensation managers, compensation administrators, and HCM specialists can still make updates or deletions using the Manage Compensation or Administer Compensation action.

For the Manage Personal Contribution action, never allow update allocations or discontinue allocations. These options prevent employees from changing or deleting existing contributions when they use the Manage Personal Contribution action. We recommend this configuration because changes and deletions can lead to conflicts.
Individual Compensation Olan Access Configuration
- To enable the profile option CMP_DISABLE_PENDING_APPROVALS_CHECK_IN_MANAGE_CONTRIBUTION, in the Setup and Maintenance work area:

Search for and click the Manage Administrator Profile Values task.
Search for and select the profile option.
Select the Level as Site.
Enter a Y in the Profile Value field.
Click Save and Close.

CMP_DISABLE_PENDING_APPROVALS_CHECK_IN_MANAGE_CONTRIBUTION Profile Option Configuration

Tips And Considerations

The profile option can be set at only the site level.

Configurable Salary Error Conditions for Grade Step Progression Batch Processes

You can now configure two of the batch error conditions for grade step progression processes so that either or both of these two conditions don't result in an error. Previously, an error message was created when there was an existing salary record on the same or future date relative to the date of the proposed salary update. Here's an example of the old error message.

Salary Error Conditions Before This Update

With this update, you can choose to allow salary updates on the same date as an existing salary record. In this case, the existing salary record will be updated with the new information. You can review the information on the Review Proposed Progressions and Salary Updates page. When you drill down to look at the details for an assignment, you see the current and proposed values. The Salary Start Date value can now be the same for the current and proposed salary. You can see an example of this scenario in the following image. When the transaction is accepted, the proposed salary amount, salary action, and salary action reason replace the current values on the salary record. You can use the salary audit record to see the original values, as needed. In this example, after accepting the transaction, the salary history no longer shows the Promotion row with a salary of 29.00. It has a March 31 salary row showing the Automated Grade Step Progression action and a salary amount of 30.00.

Proposed Salary on Same Date as Existing Salary Record

Also with this update, you can choose to allow salary updates if there is an existing future-dated salary record. In this case, the new salary record is inserted and the end date is automatically aligned with the future-dated salary record's start date. It's important to note that the salary amount is not adjusted in the future-dated salary record. Also, the new salary record is inserted in the middle of the stack, even if the future-dated salary amount is a lower amount. In the example shown here, there's an existing future-dated salary record effective April 15. The process inserted the March 31 salary record and adjusted its end date to April 14. It didn't update the April 15 record.

Salary Inserted When a Future-Dated Record Exists

If you choose to continue treating these two scenarios as errors, you see improved error messages that now identify whether the salary exists on the same date or a future date. Previously, there was a single error message covering both scenarios.

Enhanced Error Messages When Salary Exists with Same or Future Date

Watch a Demo

Steps to Enable

In Setup and Maintenance, click the Configure Global Compensation Settings task:
- Offering: Compensation
- Functional area: Workforce compensation.
Scroll to the Grade Step Progression section of the page
The new configuration options are listed under the heading Batch Salary Date Error Conditions
- If you want the batch processes to overwrite the salary record if a record already exists on the same date as the proposed salary date, deselect the Error when salary exists with the same date check box.
- If you want the batch processes to insert a new salary record even if a salary record exists on a future date, deselect the Error when salary record exists with a future date check box

Make the feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role Information section below.

Tips And Considerations

When you choose to allow updates to a salary record that exists on the same date, you are correcting the salary record that already exists.
- The new salary amount may be greater or less than the salary amount that already exists on the same date.
- The new salary amount may not be less than the salary amount that exists on a prior date. If this situation occurs, you get an error message.
- When viewing the details on the Review Proposed Progressions and Salary Updates page, you see the current salary details, which reflect the values of the existing salary record for the same date, that is, the record being corrected.
When you choose to allow updates to a salary record when future-dated records exist, you are inserting a new record in the middle of the historical sequence.
- The salary amount for the inserted salary record may be greater or less than any salary amounts in future-dated records.
- The salary amount for the inserted salary record may not be less than the salary amount on the record that exists on the previous date. If this situation occurs, you get an error message.
- When viewing the details on the Review Proposed Progressions and Salary Updates page, you see the current salary details, which reflect the prior salary record, that is, the one with an effective date prior to the effective date of the record being inserted.
These new configuration settings have no affect when you change the grade ladder, grade, or step during an online transaction. The new configuration settings only affect the behavior of the batch processes. Date handling in online transactions aren't affected with this update. Specifically:
- If your online transaction date is the same as an existing salary record start date, the salary record is updated with the new amount, as long as the new amount is greater than the existing salary amount. If the new salary is less than the existing salary amount, you get a warning message during the transaction. It worked this way prior to this update, and hasn't changed.
- If there is a future-dated salary, relative to your online transaction date, the salary isn't updated. You get a warning message during the transaction, indicating that the salary can't be updated because of the future-dated salary record. It worked this way prior to this update, and hasn't changed.

Key Resources

Implementing Workforce Compensation Guide - Grade Step Progression Batch Processing: Explained
Readiness Training: Grade Step Progression Enhancements (update 19C)

Role Information

This table lists the privileges necessary to access the Configure Global Compensation Settings task in the Setup and Maintenance work area, Compensation offering, Workforce Compensation functional area.

Privilege Name and Code
Manage Compensation Plan Global Options for Group Compensation CMP_MANAGE_COMPENSATION_PLAN_GLOBAL_OPTIONS_FOR_GROUP_COMPENSATION
Functional Setups ORA_ASM_FUNCTIONAL_SETUPS_DUTY

Privilege Name and Code

Manage Compensation Plan Global Options for Group Compensation

CMP_MANAGE_COMPENSATION_PLAN_GLOBAL_OPTIONS_FOR_GROUP_COMPENSATION

Functional Setups

ORA_ASM_FUNCTIONAL_SETUPS_DUTY

This table lists the predefined job roles that inherit both of these privileges. If you're using the predefined roles, no action is necessary. But, if you're using custom versions of these roles, you need to add these privileges to your custom roles to set up the feature. See the Release 13 Oracle Human Capital Management Cloud Security Upgrade Guide on My Oracle Support (Document ID 2023523.1) for instructions on implementing new functions in existing roles.

Job Roles
Compensation Administrator
Human Capital Management Application Administrator

Transactions Pending Approval Checked While Loading Salary

Specify whether to include or exclude a salary record in the salary HCM Data Load process, when related salary is pending approval either in a standalone salary transaction or as part of Global HR transactions, such as Promote or Transfer, that include salary changes.

Steps to Enable

The existing Global HR profile option HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER will also control salary updates. If this profile option is already set, then there is no further action needed.

HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER Profile Option Configuration

To enable the profile option, complete these tasks in the Setup and Maintenance work area:

Search for and click the Manage Administrator Profile Values task.
Search for and select the profile option HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER.
Select the Level as Site.
Enter a Y in the Profile Value field.
Click Save and Close.

Post Compensation Allocations Separately by Type

We enhanced the Transfer Workforce Compensation Data to HR process to allow you to post compensation allocations separately by type. The types are: elements, salary, stock, and promotions. You must post everything of a type for a worker at the same time.

Steps to Enable

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

Tips And Considerations

When transferring data to HR, you simply choose which compensation allocation type you want to transfer and proceed.

If a worker is eligible for more than one compensation allocation that uses elements, you must post all elements for that worker at the same time. The same requirement applies to salary, stock, and assignment changes.

Restrict Performance Documents by Period

You can now configure the workforce compensation plan to pull performance ratings by review period. Previously, the application pulled the most recent performance rating for the worker regardless of review period.

Steps to Enable

To configure a review period, navigate to Configure Performance Ratings in plan setup. To use this feature, you must select the Integrate with Oracle Fusion Performance Management option.

Configure Performance Ratings

Select a Review Period and save.

Review Period List of Values

Tips And Considerations

This feature only limits which performance ratings are pulled to the selected period. If a worker has a rating prior to this period, it doesn't appear in the worksheet.

Update Development Goal Rating Within a Compensation Cycle

We enhanced the worksheet to include the new Performance Management Development Goal Rating. There are two new columns available in worksheet configuration:

Performance Management Overall Development Goal Rating
Performance Management Calculated Development Goal Rating

These new columns work the same as the other Performance Management Rating columns. To make the use of the columns more clear, we have renamed:

Performance Management Overall Goal Rating
Performance Management Calculated Goal Rating

to:

Performance Management Overall Performance Goal Rating
Performance Management Calculated Performance Goal Rating

Previously, you were only able to see the performance goal rating in the worksheet.

Steps to Enable

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

Use Amount or Percent in the Downloaded Workbook

You can now allow line managers to choose to use either the Percentage of Eligible Salary or Amount column in the downloaded workbook by plan component. Previously, this was not an option.

Steps to Enable

To allow line managers to use this feature, Administrators must enable the new Configure Workbook action in plan setup. You find this action in the Configure Worksheet Display>Compensation task type> Action subtab> Actions region.

Configure Workbook Setup Option

When you enable this option, the manager has a new action in the worksheet actions:

New Worksheet Action

The manager can choose either percentage or amount.

Configuration Option for Downloaded Workbook

Tips And Considerations

Managers can choose either percentage or amount in the downloaded workbook, not both.

Total Compensation Statement Printable Statement Enhancements

We've enhanced the printable Total Compensation Statements with a new feature that uses anchors in the template to create drill down functionality. Use the new Previous and Top links to help you return after drilling. Previously, drill down was unavailable in the printable statement.

Printable Statement with Drill Down and Return

Steps to Enable

The default value for the new configuration check box is set to the off position. You must select the check box to show detail sections.

Key Resources

Watch Configurable Salary Error Conditions for Grade Step Progression Batch Processes Readiness Training

Configure Workforce Compensation Administration Reports

You can now enable or disable administration reports, add your own OTBI reports, and make them available in the View Administration Reports task. Previously, you could do neither.

Steps to Enable

To enable or disable a report, navigate to Configure Reports in plan setup, choose the new Administration Reports subtab, make your changes, and save. You can also update the name and description:

Administration Reports Configuration

To add an OTBI report to a plan, you must first create and save the report in the correct folder. It's then available for you to select. You can also add a more meaningful name and description for the report.

OTBI Reports Configuration

Tips And Considerations

You must add the OTBI reports before you start the plan cycle.

Key Resources

For more information, see the following topic in Applications Help: OTBI Reports in Compensation

Apply User Preference Only if Action Is Available in Task

Previously set manager preferences or defaults are now only applied in a new plan cycle if you enable the personalize layout action and individual options in a task.

Steps to Enable

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

Limit Simple Export Option in Tree View When Team Size Is Greater Than 500

When you use the tree view on the worksheet, the simple export option doesn't appear if the team member size is greater than 500.

Steps to Enable

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

Limit Use of Expand or Collapse All in Tree View When Team Size Is Greater Than 500

The options to use Expand All or Collapse All on the worksheet won't appear when the a manager's team size is greater than 500 members.

Steps to Enable

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

Change to Cross Plan Updates in The Start and Refresh Processes

When you run the Start Compensation Cycle or Refresh Data batch processes for a master plan, the application updates only the direct child plans.

For example, you have three plans named A,B,C. A is parent of B and B is parent of C (A->B->C). B has cross reference attributes from A and C has cross reference attributes from B.

When you run the Start Compensation Cycle or Refresh batch processes for A, it updates Plan A's and Plan B's attributes only. However, any updates from the worksheet of Plan A continues to update two levels down. Similarly, running these batch processes for Plan B updates the attributes of Plan C.

Steps to Enable

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

Sort Visible Worksheet Rows

Sort visible worksheet rows by currency. If the user selects worker local currency and sorts the worksheet, rows are sorted as per local currency. If the user selects corporate, or their preferred currency, and sorts the worksheet, rows are sorted as per the selected.

Steps to Enable

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

Validate Element Input Values in Individual Compensation Pages

You now run validations defined for the input values when you enter values on individual compensation pages and click OK.

Here's a sample element setup that shows the validation formula for the input value.

Sample Element Setup

Here's a sample fast formula that enforces the condition where only when the service is greater than 10 years, can the proposed amount be more than $10. Otherwise it must be less than $10.

Sample Fast Formula Associated with an Element Amount Input Value

Here's the error message that appears on responsive pages when the employee has more than 10 years service and the proposed amount is less than $10.

Responsive Page Error Message When Service Is More Than 10 Years and Proposed Amount Is Less Than $10

Here's the error message that appears on classic pages when the employee has more than 10 years service and the proposed amount is less than $10.

Classic Page Error Message When Service Is More Than 10 Years and Proposed Amount Is Less Than $10

Here's the error message that appears on responsive pages when the employee has less than 10 years service and the proposed amount is more than $10.

Responsive Page Error Message When Service Is Less Than 10 Years and Proposed Amount Is More Than $10

Here's the error message that appears on classic pages when the employee has less than 10 years service and the proposed amount is more than $10.

Classic Page Error Message When Service Is Less Than 10 Years and Proposed Amount Is More Than $10

Steps to Enable

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

Tips And Considerations

The validations run on all new proposals, and any changes to existing personal contributions and additional compensation awards.

Affected pages:

Manage Personal Contribution
Manage Compensation
Administer Individual Compensation

Receive Warning When Changing Currency Conversion Rates

We made it easier for you to remember to run the required refresh process after you make changes to the currency conversion rates in Manage Plans. Now you receive a warning message after you make the changes and save. Due to a scheduling issue, this feature did not make it in to release 11.13.19.04.0.

Steps to Enable

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

Mark Assignments as Processed or Partially Processed

Administrators can now mark assignments as processed as a part of the Transfer Compensation Data to HR process. The options are:
Yes locks all the successfully processed assignments and they're not considered for processing for subsequent Transfer Compensation Data to HR runs.
No classifies successfully processed assignments as available for processing for subsequent runs, until a Transfer Compensation data to HR run with option Yes successfully processes those workers.

New Parameter in Other Details in the Transfer Process

Previously, all the posting types (Salary, Element ,Stock, and Assignment Changes) were transferred at single run because a worker could only be processed once for a compensation plan cycle. This new feature gives you the ability to process these posting types in different Transfer Compensation Data to HR runs.

Processing Status in Administer Workers

Administrators can also update an individual worker's processing status in the Status and Hierarchy tab in the Administer Workers task. Administrator can select from: Unprocessed, Partially Processed, Processed. Partially Processed indicates that the worker might have additional items posted to HR.

Steps to Enable

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

Disable Edit Button in BI Publisher Notifications

You can now hide the Edit button in salary and individual compensation approval notifications.

Notification Without the Edit Button

Notification With the Edit Button

Steps to Enable

You need to create these profile options:

Profile Option Code	Profile Display Name	Application	Module	Description	Start Date
BIP_ONLINE_HIDE_EDIT_HCM	Enable Hiding of Edit Button at Family Level	Global Human Resources	Global Human Resources	To control edit button at the product family level.	1/1/1951
BIP_ONLINE_HIDE_EDIT_HCM_COMPENSATION	Enable Hiding of Edit Button at Compensation Product Level	Global Human Resources	Global Human Resources	To control edit button at the compensation product level.	1/1/1951
BIP_ONLINE_HIDE_EDIT_HCM_COMPENSATION_CHANGESALARYAPPROVALTASK	Enable Hiding of Edit Button for Salary Approval Tasks	Global Human Resources	Global Human Resources	To control edit button display in notifications generated for Change Salary and Manage Salary.	1/1/1951
BIP_ONLINE_HIDE_EDIT_HCM_COMPENSATION_VARIABLEALLOCATIONTASK	Enable Hiding of Edit Button for Individual Compensation Tasks	Global Human Resources	Global Human Resources	To control edit button display in notifications generated for Manage Personal Contribution, Manage Individual Compensation and Administer Individual Compensation tasks.	1/1/1951

In the Setup and Maintenance work area:

Search for and click the Manage Profile Options task.
Select New on the Manage Profile Options page, Actions menu.

On the Create Profile Option page:

Complete all required fields.
Click Save and Close.

On the Manage Profile Options page, in the Profile Option Levels section:

Select the check box levels to enable at the profile option at the Site level:

Select the Enabled check box, to enable the feature.
Select the Updateable check box, to allow users update privileges.

NOTE: The profile values appear in read-only mode if deselected.

Click Save and Close.

To enable the profile option just created, navigate to the Setup and Maintenance work area:

Search for and click the Manage Administrator Profile Values task.
Search for and select the newly created profile option.
Click to add a new Profile Value.
Select the Level as Site.
Enter a true in the Profile Value field.
Click Save and Close.

Tips And Considerations

These profile options effect all of the existing notifications too. After they're enabled, people who view the notification on their Worklist page will see the change; even though the notifications were generated before the profile options were enabled.
BIP_ONLINE_HIDE_EDIT_HCM_COMPENSATION_CHANGESALARYAPPROVALTASK: Controls the Edit button in notifications generated for the Change Salary and Manage Salary tasks.
BIP_ONLINE_HIDE_EDIT_HCM_COMPENSATION_VARIABLEALLOCATIONTASK: Controls the Edit button in notifications generated for Manage Personal Contribution, Manage Individual Compensation and Administer Individual Compensation tasks.

Key Resources

For more information, see the following topics in the Help Center:

Creating and Editing Profile Options: Procedure
HCM Email and In-App Notifications Based on Reports: Overview
Templates and Data Models Used for HCM Notifications Based on Reports
Configuring Workforce Deployment Notifications Using Reports: Worked Example

For more information on enabling BI Publisher Notifications see release notes.

Enable Disclosure in Approval Details Section of the BI Publisher Notifications

You can now determine how the Approver details section shows the approval details. When you enable disclosure, by default the section has a show details link instead of the approvers details. You can see the details when you click the show details link.

Notification with Disclosure Enabled

Notification with Approver Details After Clicking Show Details

Steps to Enable

You need to create these profile options:

Profile Option Code	Profile Display Name	Application	Module	Description	Start Date
BIP_ONLINE_DISCLOSE_HISTORY_HCM	Enable disclosure behavior at Family Level	Global Human Resources	Global Human Resources	To control disclosure at the product family level.	1/1/1951
BIP_ONLINE_DISCLOSE_HISTORY_HCM_COMPENSATION	Enable disclosure behavior at Compensation Product Level	Global Human Resources	Global Human Resources	To control disclosure at the product level.	1/1/1951
BIP_ONLINE_DISCLOSE_HISTORY_HCM_COMPENSATION_CHANGESALARYAPPROVALTASK	Enable disclosure behavior for salary approval tasks	Global Human Resources	Global Human Resources	To control disclosure in notifications generated for Change Salary and Manage Salary.	1/1/1951
BIP_ONLINE_DISCLOSE_HISTORY_HCM_COMPENSATION_VARIABLEALLOCATIONTASK	Enable disclosure behavior for individual compensation tasks	Global Human Resources	Global Human Resources	To control disclosure in notifications generated for Manage Personal Contribution, Manage Individual Compensation and Administer Individual Compensation tasks.	1/1/1951

In the Setup and Maintenance work area:

Search for and click the Manage Profile Options task.
Select New on the Manage Profile Options page, Actions menu.

On the Create Profile Option page:

Complete all required fields.
Click Save and Close.

On the Manage Profile Options page, in the Profile Option Levels section:

Select the check box levels to enable at the profile option at the Site level:

Select the Enabled check box, to enable the feature.
Select the Updateable check box, to allow users update privileges.

NOTE: The profile values appear in read-only mode if deselected.

Click Save and Close.

To enable the profile option just created, navigate to the Setup and Maintenance work area:

Search for and click the Manage Administrator Profile Values task.
Search for and select the newly created profile option.
Click to add a new Profile Value.
Select the Level as Site.
Enter a true in the Profile Value field.
Click Save and Close.

Tips And Considerations

These profile options effect all of the existing notifications too. After they're enabled, people who view the notification on the Worklist page will see the change; even though the notifications were generated before these profile options were enabled.
BIP_ONLINE_DISCLOSE_HISTORY_HCM_COMPENSATION_CHANGESALARYAPPROVALTASK: Controls disclosure in notifications generated for the Change Salary and Manage Salary tasks.
BIP_ONLINE_DISCLOSE_HISTORY_HCM_COMPENSATION_VARIABLEALLOCATIONTASK: Control disclosure in notifications generated for Manage Personal Contribution, Manage Individual Compensation and Administer Individual Compensation tasks.

Key Resources

For more information, see the following topics in the Help Center:

Creating and Editing Profile Options: Procedure
HCM Email and In-App Notifications Based on Reports: Overview
Templates and Data Models Used for HCM Notifications Based on Reports
Configuring Workforce Deployment Notifications Using Reports: Worked Example

For more information on enabling BI Publisher Notifications see release notes.

Payroll

Global Payroll

Oracle Global Payroll is a high-performance, graphical, rules-based payroll management application. It’s designed to keep pace with the changing needs of your enterprise and workforce in order to reduce setup costs, administration, and processing time. It operates globally and consistently in every country supported by Oracle. It uses a highly scalable processing engine that takes advantage of the features of the Oracle database for parallel processing, resulting in optimal performance. In countries with payroll extensions delivered and supported by Oracle, the application delivers the calculations, tax reporting, and regulatory rules required to accurately process payroll and remain in compliance.

Quick Retroactive Pay for Single Worker

You can now use the Run Quick Retroactive Pay for Single Worker task to calculate retroactive pay for a single employee for prior period adjustments. Add this task to an existing flow or a new flow.

You can run the retroactive pay and verify that the retroactive element entries are added to the employee for the period for which the retroactive pay is processed. You can verify the values in the employees Statement of Earnings, payslip, and the retroactive payroll reports.

Steps to Enable

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

Tips And Considerations

Add this task to an existing flow or a new flow.

Support for Latest Person Search on Payroll Pages

Now, the latest person search feature is available on the classic payroll pages to ensure a consistent user experience across HCM products. When you search for an employee, the application displays a list of values. You can select a value from the list.

This feature is available for tasks through the Quick Actions menu.

Steps to Enable

In order to enable the new feature, you must enable the following profile option and have enabled the HCM_RESPONSIVE_PAGES_ENABLED profile option. If you have not enabled the HCM_RESPONSIVE_PAGES_ENABLED profile option, please see following white paper: HCM Responsive User Experience Setup Information (Document 2399671.1).

Field	Value
Profile Option Code	PAY_RESPONSIVE_PERSON_SEARCH_CLASSIC_ENABLED

To enable the profile option, navigate to the Setup and Maintenance work area:

Search for and click the Manage Administrator Profile Values task.
Search for and select the profile option.
Click to add a new Profile Value.
Select the Level as Site.
Enter a Y in the Profile Value field.
Click Save and Close.

Tips And Considerations

The latest person search is always enabled on the responsive payroll pages. This feature supports the latest person search on the classic payroll pages, such as Manage Element Entries and Manage Calculation Entries.

Read-Only Version of Manage Payroll Relationship

You can now access the Manage Payroll Relationship UI in a read only mode.

Steps to Enable

Make this feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role Information section.

Key Resources

For instructions on implementing new features in existing roles, refer to My Oracle Support for the following document:

Upgrade Guide for Oracle HCM Cloud Applications Security (Document ID 2023523.1)

Role Information

The following table shows the aggregate privileges that support this feature and the predefined roles that inherit them.

Aggregate Privilege Name and Code	Job Role Name
View Payroll Relationship ORA_PAY_PERSONAL_PAYROLL_RELATIONSHIP_VIEW_DUTY	Human Resource Analyst

Aggregate Privilege Name and Code

Job Role Name

View Payroll Relationship

ORA_PAY_PERSONAL_PAYROLL_RELATIONSHIP_VIEW_DUTY

Human Resource Analyst

If you are using the predefined roles, no action is necessary. However, if you are using custom versions of these roles, you must add these aggregate privileges to your custom roles to use this feature. See the Release 13 Oracle Human Capital Management Cloud Security Upgrade Guide on My Oracle Support (Document ID 2023523.1) for instructions about implementing new functions in existing roles.

Security Enhancement for Manage Calculation Entries

You can now access same workers list of values for the Manage Calculation Entries Quick Actions as Manage Element Entries, which uses the same data security privilege.

Steps to Enable

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

Tips And Considerations

NOTE: Please regenerate any Payroll data roles that have got access to the "Manage Calculation Entries" Quick Action.

Key Resources

For instructions on implementing new features in existing roles, refer to My Oracle Support for the following document:

Upgrade Guide for Oracle HCM Cloud Applications Security (Document ID 2023523.1)

Display Person Number on Personal Payment Method, Payslip and Year-End Documents

Use personalizations to display person number on the personal payment method, payslip and year-end document personal information page headers. A simple two-step process to first create a page composer personalization that references the person number binding parameter then to second publish the personalization.

Steps to Enable

In personalizations menu, follow these steps to create a page composer personalization that references the person number binding parameter:

Settings and Actions > Administration > Customize Page

Select the layer and click OK.

Once in the personalization page composer mode, choose to view the source code.

NOTE: Use split screen to view entire source.

Choose person's name, scroll up to simple panel in the source and click the Close link to display the universal panel

Select the universal panel and click the edit icon to open the component properties.

Scroll down to the sub Header field, click the dropdown menu and choose Expression Builder.

Choose Type a value or expression and enter the value to display the person name and the person number and click OK.

NOTE: Above example will display person name and the person number delimited by " - ".

Verify the text below the Sub Header field displays the correct value.

Scroll to the bottom of the Expression Editor and click OK. The page header will immediately reflect the changes and display {Person Name} - {Person Number}.

Make the feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role Information section below.

Tips And Considerations

It is best practice to perform these personalizations in a sandbox instance and then publish to other instances.

Role Information

A new function security role provides access to the Manage HCM Exclusion Rules task. This table identifies the function security predefined job role to which it's granted.

Job Role
IORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB

If you're using the predefined IT Security Manager job role, then no action is necessary. If you're using a custom version of the IT Security Manager job role, then you must add the new privilege to your custom role to manage HCM exclusion rules. For information about adding new roles and privileges to custom roles, see the Release 13 Security Upgrade Guide on My Oracle Support (Document ID 2023523.1)

Removal of Unprocessed Payroll Element Batches Created by HCM Data Loader Will Remove Notifications

When an element entry created by HCM Data Loader is rolled back, the application also rolls back events and notifications that are not consumed or processed based on the following:

If the event has an unprocessed status, then the event is removed. However, the event is not removed if it has been already processed, such as by retroactive pay.
If the batch action created an element entry, then the event is removed. Other types of element entry events, such as an update element entry event, are not supported.
If the element entry has not been updated, then the event is removed. However, the batch event is not deleted if the element entry has been updated, such as a change in input value.
If the element entry is created by HCM Data Loader.

Steps to Enable

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

Display All Hours in Payroll Reports

You can now report hours from Supplemental Earnings and other element classifications on the following payroll reports:

Gross-to-Net Report
Payroll Activity Report
Payroll Register Report
Payroll Balance Report

By default, these reports were displaying only hours from Regular or Standard Earnings and Absence Earnings.

A new parameter ‘Display All Hours’ has been added on the report submission page for these reports. When the parameter value is ‘Yes’, the report provides hours from Supplemental Earnings and other element classifications. The default value is ‘No’ and only hours from Regular or Standard Earnings and Absence Earnings are shown in the payroll reports to match with the standard working hours.

Steps to Enable

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

Data Security in Payroll Data Validation Report

The Payroll Data Validation report is ran before you run the payroll or any other statutory processes or reports to identify details of missing or statutorily noncompliant data at the worker and organization level. Like most payroll reports and processes, the report is secured using functional privileges and through the secured list of values on the report parameters. However, by default, the report is submitted through an elevated user that has full data access.

You can now configure the Payroll Data Validation Report to run based on the data security of the user who submits the report. For example, if a user has access to only employees within a specific payroll or department, as defined by the data security profile attached to the user’s role, the report can be configured to report data only for those employees.

Steps to Enable

The report could be configured to run as the submitting user, instead of the elevated user, using the steps below:

Navigate to the Checklist work area under Payroll.
Select the Manage Payroll Flow Patterns menu option.
Search for the Run Payroll Data Validation Report flow pattern and the required Legislative Data Group.
Click Edit.
Click Go to Task and click Edit.
Select the row and click the Edit on the tool bar for the row.
Select the Secure Process or Report check box and click Save.
Alternately, you can click on Remove all Updates.
Repeat these steps for each Legislative Data Group, where the setting must apply. This configuration, although done on the seeded flow pattern, is preserved during patching and upgrades.

Tips And Considerations

The Payroll Statutory Unit (PSU) report parameter is required by default and must be selected from a secured List of Values (LOV) before submitting the report. If the user’s data security is restricted by PSU, then the user can only run the report for the PSU that they has access to, even when the report is run as the elevated user by default.
However, if the user’s data access is restricted based on other attributes such as department or payroll and the Payroll Data Validation report must restrict itself accordingly, then the report must be configured as explained above.
Although the ‘Secure Process or Report’ check box is available on flow patterns for other reports and processes, not all reports and processes are secured using this configuration, unless stated otherwise.

Key Resources

Refer to the following topics on the Help Center:

Payroll Data Validation Report: Explained
Payroll Data Validation Report
Validation Rules for Data Validation Report: Explained
Adding Rules to Data Validation Reports: Worked Example
Setting up a Lookup Code for Controlling the Rules for Data Validation Reports: Procedure

Payroll and Time Definition List of Values REST API

Select a payroll or an overtime period using a REST API. For example, your organization is acquiring another company and has built a custom application to merge employee data into Oracle HCM Cloud. You can provide users with a real-time and up-to-date list of values for payroll and overtime period that the employee from the acquired company must be assigned to. The following REST APIs can be used to configure such a list of values.

Payroll Definition LOV

Use the payrollDefinitionsLOV resource to display a list of payroll definitions that are allocated to an employee or used to submit a payroll flow

Time Definition LOV

You can use the payrollTimeDefinitions resource to display a list of overtime periods that you can assign to an employee

NOTE: These REST services are view-only. You can only select a payroll or time definition from an LOV, but you can’t create or edit payroll or time definitions.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > REST API). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Make the feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role section below.

Key Resources

For more information on the REST API signature, refer to the REST API for Oracle HCM Cloud guide.

Role Information

You require these aggregate privilege to use these payroll REST APIs. Assign these privileges to your custom roles as appropriate.

Payroll Definition

Aggregate Privilege	Description
PAY_REST_SERVICE_ACCESS_PAYROLL_LOV_PRIV	Contains all functional and data security privileges required to view a list of payroll definitions.

Time Definition

Aggregate Privilege	Description
PAY_REST_SERVICE_ACCESS_PAYROLL_REFERENCE_DATA_LOVS_PRIV	Contains all functional and data security privileges required to view a list of time definitions.

For instructions on implementing new features in existing roles, refer to My Oracle Support for the following document:

Upgrade Guide for Oracle HCM Cloud Applications Security (Document ID 2023523.1)

Payroll for Canada

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

Iterative Pretax Deduction Calculation Enhancement

The application now processes pretax deductions iteratively when the employee’s pretax deductions result in insufficient net pay, which could cause taxes or involuntary deductions not to be deducted fully. Payroll calculates the pretax deductions using the new iterative process to reduce the pretax amount enough such that the employee’s taxes and involuntary deductions are withheld. The statutory deductions (taxes) and involuntary deductions are deducted in priority when an employee has insufficient earnings.

Use the Manage Elements task to enable this feature for the appropriate pretax deduction elements. A new question to enable iterative processing for the pretax element is presented to the user during element creation. This question is only presented for pretax elements when the element is not subject to proration (Is this element subject to proration? = No). The default value of the new iterative processing rule is No.

Pretax Element Special Rules

The following new balances hold the “tax not taken” amounts for the various taxes:

Federal Tax Not Taken
Provincial Tax Not Taken
CPP Not Taken
EI Not Taken
Payroll Tax Not Taken
QPP Not Taken
QPIP Not Taken

The following existing balance holds the amount for all taxes “not taken”:

Tax Not Taken

When multiple elements exist, the pretax deductions are reduced in the following order:

User-defined secondary classifications (default iterative order = 300)
Registered Retirement Plan (default iterative order = 200)
Union Dues (default iterative order = 100)

NOTE: If you create a user-defined secondary classification for a pretax element, you may need to change the iterative order of the element because the default is set to 300. To change the iterative order of the element, update the Iterative Order property under the Advanced Rules section of the base element.

Steps to Enable

For new elements, enable this option during element creation.

For existing elements, use the Element Upgrade Process to upgrade existing pretax elements. Refer to the next topic (Upgrade Process for Pretax and Involuntary Deductions) for information.

Tips And Considerations

In order for iteration processing to occur, you must designate one of the “partial deduction” options for the element’s standard rule:

Pretax Element Partial Deduction Standard Rule

It is strongly suggested to keep the default of Clear Arrears = No. If it is set to Yes, iteration processing performance is impacted. This setting is in element entry.

Pretax Element Clear Arrears Entry Value

Key Resources

Refer to the document below on the Canada Information Center for additional information.

Canada Information Center

https://support.oracle.com/rs?type=doc&id=2102586.2

Welcome tab > Product Documentation > White Papers > Implementation and Use

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.

See My Oracle Support Document ID 2102586.2 (Information Center: Fusion Human Capital Management - Canada) for further details, and access the content at the location below.

CA – Welcome tab > Other Documents > How To Use My Oracle Support Hot Topics Email Subscription Feature

Upgrade Process for Pretax and Involuntary Deduction Elements

When you create an element through the element template, it creates child objects, such as input values, formulas, and balances. When Oracle HCM Cloud Applications delivers changes to these child objects as part of an enhancement to existing functionality, those changes are reflected in new elements you create after the new functionality is delivered. However, new changes are not available in existing elements. Therefore, you can use the Run Element Upgrade process to upgrade your existing elements with the new features.

Access the Run Element Upgrade task from the Checklists work area. When you run this process, it performs different actions upon the objects related to the elements. This process generates an output report in Microsoft Excel format that describes these changes.

Steps to Enable

To upgrade your existing pretax elements to support the new iterative calculation processing:

Navigate to the Checklists work area.
Click Submit a Process or Report, and select an LDG.
Search for and select the Run Element Upgrade process, and click Next.
Enter the parameters, for those pretax elements that require iteration. For example, to run the process in draft mode for all pretax deductions:

Run Element Upgrade Process Parameters

NOTE: Alternatively you can specify a secondary classification and/or element name to narrow the scope of processing.

Review the output of the report to ensure the pretax elements you want to upgrade are displayed on the report.
If satisfied with the results, run the process again in Final mode.
Next, submit the Compile Formula process to recompile all impacted formulas. Use % as a wild card entry for the formula and Oracle Payroll for the Formula Type parameter.

Compile Formula Process Parameters

Run payroll and verify the results.
Once you have tested all of your pretax iteration scenarios and ensured they process correctly in payroll, repeat these steps in your production environment.

NOTE: You must also upgrade your existing involuntary deduction elements (and recompile the formulas) if you have:

Created a new pretax element requiring iterative processing
Upgraded an existing pretax element requiring iterative processing

If you create new involuntary deduction elements, you do not need to run the upgrade process.

Tips And Considerations

Review the following critical points prior to running the upgrade process:

This process is only required to upgrade your existing elements that require iteration. If you create new pretax elements (where elements are defined with iteration processing = Yes), this process is not necessary. Do not use the process to upgrade new pretax elements that are defined with iteration processing = No.
Before you perform any action in a production environment, run this process in a test environment. This process performs changes to your elements that cannot be rolled back. You must first thoroughly test your scenarios to ensure they will perform correctly during payroll processing after the upgrade. Only after you have verified your scenarios in a test environment should you run this process in a production environment.
Regardless of whether you are in the test environment or production, run this process initially in Draft mode, and use the output report to review the changes to be made. Once your evaluation is complete, and you approve of the changes, perform it in Final mode to implement the element upgrade.
By default, when you enter the primary classification, this process runs against all eligible secondary classifications and elements. To limit the scope of the output, run it against specific secondary classification and element combinations.
When this process updates formula objects, it overrides any manual configurations you may have made to the formulas. Check the Oracle Delivered Modified Formula column of the Draft mode output report to identify these formula objects. Use the Formula Upgrade Option parameter to replace or preserve these formulas.
If you have enabled proration on a pretax element, you cannot upgrade it using this process.
To upgrade the pretax element for iteration functionality, you should first set the date in process configuration parameter “Date used by the element upgrade process for iteration flag”. This indicates the effective date used by the element upgrade process to update the iteration indicator for the pretax element. It is suggested to use the next date of the latest payroll process. For example, if the latest payroll process completion date is November 15, 2018, then it is suggested to set this parameter to November 16, 2018 to avoid the retro processing effect because of pretax iteration. Please note the entry format for the date is YYYY-MM-DD (2018-11-16).

Key Resources

Refer to the document below on My Oracle Support (MOS) for additional information.

Oracle Fusion Human Capital Management: Global Payroll Element Upgrade Process (Doc ID 2502724.1)

User-Defined Absence Secondary Classifications

You can now create user-defined secondary classifications for absence elements if the pre-configured secondary classifications for absences do not meet your needs. This allows you to use the new secondary classification to create default mappings for Record of Employment Reasons for absences.

To create a new secondary classification for absence elements:

Select the Manage Element Classifications task in the Payroll Calculations work area.
Select the appropriate LDG, and click Search.
Select the Absence primary classification in the search results.
Select Actions > Edit.
In the Secondary Classifications section, select Actions > Create.
Enter the new name and start date.
Select a Year End Forms value.
Click OK.
Click Submit.

For example, a new secondary classification for Paternity is illustrated below.

Create Secondary Classification

Steps to Enable

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

Tips And Considerations

Create wage basis rules for the new secondary classification. For additional information, refer to the Implementation and Use Guide, Creating Wage Basis Rules section.

For additional information on configuring the Record of Employment default mappings for absences, refer to the Record of Employment Processing white paper.

Key Resources

Refer to the documents below on the Canada Information Center for additional information.

Canada Information Center

https://support.oracle.com/rs?type=doc&id=2102586.2

Welcome tab > Product Documentation > White Papers > Implementation and Use
CA – Payroll tab > Product Documentation > White Papers > Record of Employment 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.

See My Oracle Support Document ID 2102586.2 (Information Center: Fusion Human Capital Management - Canada) for further details, and access the content at the location below.

CA – Welcome tab > Other Documents > How To Use My Oracle Support Hot Topics Email Subscription Feature

Year-End Documents Publish Date

You can now specify the day and month when employees can view their year-end documents in employee self-service for the following document types:

T4
T4A
RL-1
RL-2

The configuration addresses original, amended, and cancelled form types.

The publish day and month determines the date the documents are published to Document Records (DOR). It must be on or before the system date. Also, in order to publish these documents to Document Records (DOR), you must submit the Run End-of-Year Reports task in final mode. The PDF Final option generates a final version of the individual year-end slips and publishes them to the DOR, if the publish date is on or before the system date. Once these two conditions are met, the employee can view their document in employee self-service and the professional user will be able to access the final document in the DOR.

You can configure the day and month for the Payroll Statutory Unit (PSU) and/or Tax Reporting Unit (TRU) levels. If you configure the date at the PSU level, all TRUs belonging to that PSU will adhere to the same date. You may override the configuration at the TRU level, if needed.

To configure the date for the PSU, use the Manage Legal Entity HCM Information task. To configure the date for a TRU, use the Manage Legal Reporting Unit HCM Information task. The fields are located in the Year-End Reporting Rules section, as illustrated below. Once you configure the publish day and month, this controls both the federal and provincial form types.

Year-End Reporting Rules

Steps to Enable

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

Tips And Considerations

If the publish dates are left blank, the documents are available once final mode is processed.

It is not necessary to update the date every year, as the configuration persists for subsequent years. You only need to update if you want to change the month and/or day to publish the documents.

The following must ensue to display the documents in employee self-service:

Publish Day/Month on or before today’s date
Run End-of-Year Reports task in PDF Final mode
Document Type Delivery Method = Online
Document Type Publish Required = Yes

NOTE: The year-end document types are preconfigured to Yes and cannot be changed.

Refer to the End-of-Year Guide for additional information.

Key Resources

Refer to the documents below on the Canada Information Center for additional information.

Canada Information Center

https://support.oracle.com/rs?type=doc&id=2102586.2

CA – Payroll tab > End-of-Year Processing > End-of-Year Processing Guide

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.

See My Oracle Support Document ID 2102586.2 (Information Center: Fusion Human Capital Management - Canada) for further details, and access the content at the location below.

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

Updated Tax Calculation to Support 2019 Tax Reform

Effective from January 1, 2019, China adopted the accumulative tax withholding method in regular tax calculation. This new method uses year-to-date values in monthly tax calculation and uses a new tax table as shown in this screenshot.

This figure shows the logic that’s followed when calculating tax.

Calculate the YTD Taxable Income by subtracting YTD Nontaxable Income from YTD Income.
Calculate the YTD Reduced Taxable Income by subtracting YTD Tax Exemption and YTD Taxable Benefits 2 from YTD Taxable Income.
Use the YTD Reduced Taxable Income to derive Tax Rate and Quick Deduction amount.
Calculate YTD Tax Payable by multiplying the Derived Tax Rate with the YTD Reduced Taxable Income and by subtracting the Quick Deduction Amount.
Apply Special Tax Deduction calculation, if required.
Calculate the actual tax payment for current payroll run by deducting the YTD Final Tax withheld as of last run from the YTD Final Tax Withheld.

Balance Calculations

Now, the tax reporting context is added to almost all of the balances used in tax calculation. So, whenever there’s a tax reporting update, the calculation considers only the balances accumulated year-to-date under the unit.

In this example, an employee transferred from Beijing to Tianjin. Though the year-to-date standard earnings accumulated for Beijing has reached 150,000 Yuan, when calculating the tax under Tianjin tax reporting unit for the first time, the application uses 50,000 as the year-to-date standard earnings.

Balance Initialization

Recollect that China’s tax year is the same as calendar year. But if you are going live with Fusion China Payroll in the middle of a year, and if you don’t want to run payroll from the beginning of the year, then you can initialize the balances that you want to use in tax calculation.

Let’s consider these scenarios.

Scenario 1: Run payroll once in a pay period for a normal employee

If you run payroll once in a pay period, then you initialize these balances for calculating tax for a normal employee.

Regular Tax Income
Regular Tax Tax Income
Regular Tax Nontaxable Income
Regular Tax Taxable Income
Regular Tax Monthly Tax Exemption
Taxable Benefits 2
Regular Tax Reduced Taxable Income
Regular Tax Tax Payable
Regular Tax Reduced Tax Payable
Regular Tax Pay Value

Initialize the relationship, tax unit, and year to date dimension.

Scenario 2: Run payroll once in a pay period for an employee who is entitled to special reduction

If you run payroll once in a pay period for an employee who is entitled to special tax reduction, in addition to the ten balances that you initialized in scenario 1, you must initialize the regular tax special tax reduction amount with the relationship, tax unit, and year-to-date dimension.

Scenario 3: Run payroll twice in a pay period

In this case, you want to run the payroll twice in a period by going live after the first run is complete. To run your payroll run starting from the second run of the pay period, initialize the additional balances with the relationship, tax unit, and period to date dimension. This ensures that neither the tax exemption amount for the month is granted again nor the social security deductions are deducted again in the second run.

You can use HCM Data Loader and HCM Spreadsheet Data Loader to do balance initialization in bulk. Loading initial balance values using HCM Data Loader is a two-step process.

Load balance values to PAY_BAL_BATCH_HEADERS and PAY_BAL_BATCH_LINES interface tables by using these two separate HDL files.

InitializeBalanceBatchHeader.dat
InitializeBalanceBatchLine.dat

Submit the Load Initial Balances process from the Payroll Calculation work area to validate and process the initial balance values.

Annual Bonus Tax Calculation

The new logic for calculating the annual bonus tax is same as the existing one except that it doesn’t take tax exemption into account. As of special tax reduction calculation, the new logic only covers the tax reduction by rate and not the tax reduction by fixed amount.

Example

In addition to regular earnings, an employee also receives annual bonus in the pay period, subject to the annual bonus tax calculation rule. The annual bonus amount is 120,000, which is divided by 12 to get 10000. Use the 10000 to derive tax rate and quick deduction amount using the tax table in monthly amounts. Calculate the tax payable as 120,000 x 10% - 210 to get 11,790.

Severance Payments Tax Calculation

Here’s the logic to calculate tax calculations for severance payments.

(Severance Payments Amount – Severance Payments Tax Exemption) x Tax Rate – Quick Deduction Amount

If applicable, you may calculate tax reduction by percentage. Don’t apply fixed monthly tax reduction amounts. Finally, use the tax table in annual amounts.

Steps to Enable

Specify the Accumulative Withholding Method

Use the Manage Legal Entity Calculation Cards task to do these steps.

In the Components Groups section, select Taxes.
Specify the effective start date.
Add the Individual Income Tax per territory.
Add the Individual Income Tax Generic Rules component details.
In the Calculation Method to Apply option, select Accumulative Withholding Method.

Create the Element

Use the Manage Elements task to do these steps.

In the Create Element dialog box, Legislative Data Group option, select a China legislative data group.
In the Primary Classification option, select Taxable Benefits. This creates the elements for special additional deductions.
Click Continue.

Add Elements to Taxable Benefits 2

Use the Manage Balance Definitions task to do these steps.

Search for and select the Taxable Benefits 2 balance.
In the Effective As-of Date, specify the effective start date.
Click Balance Feeds.
In the Balance Feeds by Element, add the elements that you created for special additional deductions.

Add Elements to Taxable Benefits 1

Use the Manage Balance Definitions task to do these steps.

Search for and select the Taxable Benefits 1 balance.
In the Effective As-of Date, specify the effective start date.
Click Balance Feeds.
In the Balance Feeds by Element, add the elements that you created to increase taxable income.

Update the Balance Group

Use the Manage Balance Groups task to do these steps, to show additional information on payslips.

Search for and select the Chinese Payroll Archive Other Balances balance group.
In the Balance Group Overview section, click Balance Definitions.
Click Select and Add.
Add the balances with Relationship, Tax, Unit, and Year to Date dimension.

Create Element Entry

Use the Manage Element Entries option to create an element entry.

On the Search page, search for and select an employee.
Select the employee and click the Actions menu.
Select Manage Element Entries.
On the Manage Element Entries page, click Create.
In the Create Element Entry dialog box, Effective Date field, select a date.
In the Element Name field, select an element.
Click Continue.
Enter the details.
Click Save.

Enhanced Voluntary Deduction Element Template

You can automate the way you handle a voluntary deduction in the pay periods when there are insufficient funds. When creating the element using the enhanced element template, you can choose either to make partial deductions or not. If you choose to place any undeducted amount in arrears, then the amount will be processed in subsequent pay periods when there are sufficient funds.

Steps to Enable

Use the Manage Elements task to do create an element.

On the Manage Elements page, click Create.
In the Create Element dialog box, Legislative Data Group field, select a China LDG.
In the Primary Classification option, select Voluntary Deductions.
Click Continue.
In the Standard Rules section, for the question What should happen when there are insufficient funds to cover the deductions?, select the required option.

Click Next.
In the Special Rules section, for the question Processing Stop when the Total is reached?, select the required option.

Click Next.
For the employees who need to make this voluntary deduction, you need to create an element entry. Navigate to the Manage Element Entries page.
In the Amount field, enter 3000.
In the Total Owed field, enter 30,000.
In the Maximum Amount field, enter 5000.

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's business practices and comply with its statutory requirements.

Auto Calculation Cards - Missing TRU Message

At the time of new hire or termination, when an automatic calculation card is generated, if a valid tax reporting unit does not exist for an employee, the application generates a message to highlight the missing data. This is usually because you have not marked the legal reporting unit as a tax reporting unit using the task Manage Legal Reporting Unit HCM Information.

If you see this message, navigate to Setup and Maintenance and find the task Manage Legal Reporting Unit HCM Information. Search for the legal reporting unit that has not been marked as a tax reporting unit. With the name of the legal reporting unit highlighted, click on the Manage Legal Reporting Unit Classification tab, where you can now classify the legal reporting unit as required.

Manage Legal Reporting Unit HCM Information

Steps to Enable

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

Key Resources

Watch United Kingdom and GCC Countries Localizations Readiness Training

Global HR Contract End Date Uptake

We are currently using the PER_ASG_PROJECTED_ASSIGNMENT_END_DATE DBI for returning the contract information for fixed term contracts, when calculating gratuity payments. The data model structure has now changed and a new DBI has been created: PER_ASG_CONTRACT_END_DATE. The gratuity functionality has been updated to use this new DBI for improved performance.

Contract Details

Steps to Enable

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

Key Resources

Watch United Kingdom and GCC Countries Localizations Readiness Training

Delete Archive and Retention Period Uptake

When you run an extract, the application generates XML files and archive data, and delivers these outputs to a defined destination. You now have the option to discard them, thus reducing storage consumption.

The delete archive extract parameter automatically deletes the data when the extract has completed successfully, unless the information needs to be retained for statutory reasons.

When you cannot delete the archive because of legislative requirements, or because it's a changes-only extract, these parameters in the extract definition table will purge the data to avoid abnormal database growth:

Retention History: The minimum number of historical changes for every multi-threading object to be maintained.
Retention Period: The number of days the internal archive data needs to be retained. Only the archive data which has met both the Retention Period and Retention History conditions is purged.
Output Retention Period: The minimum period for which Output Attachments or Web Center Connect Data needs to be retained.

The extract definition for all delivered statutory reports, including HR disability reports, has been updated to include:

Retention History: Two historical changes.
Retention Period: 30 days (1 month).
Output Retention Period: 2555 days (7 years).

Steps to Enable

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

Key Resources

Watch United Kingdom and GCC Countries Localizations Readiness Training

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's business practices and comply with its statutory requirements.

Auto Calculation Cards - Missing TRU Message

Manage Legal Reporting Unit HCM Information

Steps to Enable

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

Key Resources

Watch United Kingdom and GCC Countries Localizations Readiness Training

Qatar Retro for Social Insurance and Gratuity

To simplify retroactive calculations for both social insurance and gratuity, the existing elements have been updated to include:

Retroactive components on all social insurance and gratuity elements previously delivered.
Retroactive elements equivalent to all social insurance and gratuity elements previously delivered.
Balance feeds to include the new retroactive elements.

Manage Elements

Steps to Enable

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

Key Resources

Watch United Kingdom and GCC Countries Localizations Readiness Training

Delete Archive and Retention Period Uptake

The delete archive extract parameter automatically deletes the data when the extract has completed successfully, unless the information needs to be retained for statutory reasons.

Retention History: The minimum number of historical changes for every multi-threading object to be maintained.
Retention Period: The number of days the internal archive data needs to be retained. Only the archive data which has met both the Retention Period and Retention History conditions is purged.
Output Retention Period: The minimum period for which Output Attachments or Web Center Connect Data needs to be retained.

The extract definition for all delivered statutory reports, including HR disability reports, has been updated to include:

Retention History: Two historical changes.
Retention Period: 30 days (1 month).
Output Retention Period: 2555 days (7 years).

Steps to Enable

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

Key Resources

Watch United Kingdom and GCC Countries Localizations Readiness Training

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 HR Contract End Date Uptake

Contract Details

Steps to Enable

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

Key Resources

Watch United Kingdom and GCC Countries Localizations Readiness Training

Auto Calculation Cards - Missing TRU Message

Manage Legal Reporting Unit HCM Information

Steps to Enable

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

Key Resources

Watch United Kingdom and GCC Countries Localizations Readiness Training

Data Validation Report Update

Data validation reports help you identify employees whose data may not be statutorily compliant, so that you can fix these before running any dependent process or report.

An additional UAE specific validation has been added in the Payroll Data Validation Report to identify if the tax reporting unit associated to an employee is missing or invalid. This would impact the automatic creation of a social insurance or gratuity calculation card. The application generates a message to highlight the missing or invalid data.

Manage Legal Reporting Unit HCM Information

Steps to Enable

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

Key Resources

Watch United Kingdom and GCC Countries Localizations Readiness Training

Delete Archive and Retention Period Uptake

The delete archive extract parameter automatically deletes the data when the extract has completed successfully, unless the information needs to be retained for statutory reasons.

Retention History: The minimum number of historical changes for every multi-threading object to be maintained.
Retention Period: The number of days the internal archive data needs to be retained. Only the archive data which has met both the Retention Period and Retention History conditions is purged.
Output Retention Period: The minimum period for which Output Attachments or Web Center Connect Data needs to be retained.

The extract definition for all delivered statutory reports, including HR disability reports, has been updated to include:

Retention History: Two historical changes.
Retention Period: 30 days (1 month).
Output Retention Period: 2555 days (7 years).

Steps to Enable

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

Key Resources

Watch United Kingdom and GCC Countries Localizations Readiness Training

Payroll for the United Kingdom

FPS Process to Update Tax Code For Payments Made After Termination

The Full Payment Summary (FPS) process automatically updates the tax code and the tax basis to the same values used during the PAYE calculation of a payment, when a payment is made after employee termination and a P45 has been issued.

The application will reverse the changes for the tax code and the tax basis to their original values, if you perform the FPS rollback. However, this is not possible once the FPS is submitted.

Steps to Enable

You can use the new field Enable FPS to update tax code if payment after P45 to set this option on the PSU and TRU Statutory Deduction calculation card.

Key Resources

Watch United Kingdom and GCC Countries Localizations Readiness Training

Pensions Automatic Enrolment Enhancement to Support Multiple Assignments

You can define pension elements to allow for multiple entries. This means that you can create multiple components of the same type, one for each assignment.

Use the Manage Element task in the Payroll Administration work area to set this value when you create the pension element, under Standard Rules on the Create Element page.

The element template creates a new calculation component attribute for a Pension Payroll ID on the Benefits and Pension Calculation Card. This applies to elements with these secondary classifications:

Pre-Statutory Deductions Pension Plan Pre-Statutory
Voluntary Deductions Pension Plan After Tax

This ID must be unique, and is automatically generated by the Pensions Automatic Enrolment process. Or, you can enter this manually when adding a new pensions component on the Benefits and Pension card.

On the Benefits and Pensions calculation card, you can select the assignment number and the appropriate Payroll Pension ID to associate the same pension with multiple assignments. When you create the association detail, the list of values displays both the component and Pension Payroll ID.

On the Pensions Automatic Enrolment calculation card, the list of values to select the Qualifying Scheme component also displays both the component and Pension Payroll ID.

Steps to Enable

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

Key Resources

Watch United Kingdom and GCC Countries Localizations Readiness Training

LGPS - Additional Pension Contributions

Use the enhanced element template for the primary classification Pre-Statutory Deductions with a new secondary classification Additional Pension Contributions Pre-Statutory.

You can create the required elements and associated objects for LGPS-specific additional pension contributions such as:

Additional Pension Contributions
Additional Regular Contributions
Additional Survivor Benefit Contributions
Additional Voluntary Contributions
Added Years
Preston Part-Time Buy-Back Contributions
Stakeholder Pension

If you select the value Not Applicable, the application creates an element and associated objects. But this includes only the minimum information required, for example, basic input values on the element.

Steps to Enable

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

Key Resources

Watch United Kingdom and GCC Countries Localizations Readiness Training

Payroll for the United States

Enhanced Federal Tax Withholding for Supplemental Earnings

We have made it easier to perform Federal Income Tax (FIT) withholding calculations for supplemental earnings. The payroll process now evaluates an employee’s FIT withholding across the prior and current years. If it finds the person does not have FIT withheld from their wages, it taxes their supplemental earnings using the aggregate tax method instead of the flat 22 percent rate. Use the new Enforce Federal Income Tax Look-Back Rule calculation value to enable these calculations.

Enforce Federal Income Tax Look-Back Rule Calculation Value

Steps to Enable

To enable this at the payroll statutory unit level:

Start the Manage Legal Entity Calculation Cards task and select the Calculation Rules for Tax Reporting card for editing.

Create it if it doesn’t exist.

Enter an effective date, and select the Federal component.
Select the Federal Income Tax calculation component.
Click the Enterable Calculation Values on Calculation Cards tab.
Click Create.
For Name, select Enforce Federal Income Tax Look-Back Rule.

Edit Calculation Values

Enter Y as the value.
Click OK.
Click Save and Close.

Tips And Considerations

To override this setting at the tax reporting unit level, use the Manage Legal Reporting Unit Calculation Cards task.

To override this at the employee level:

From the Payroll Calculation work area, search for your employee.
Start the Manage Calculation Cards task, and open their Tax Withholding card for editing.
Select the Federal component.
Click Edit and then Update.
For Enforce Federal Income Tax Look-Back Rule, select Yes or No as appropriate.

Enforce Federal Income Tax Look-Back Rule

Click Save and Close.

Periodic Archive and Payslip Enhancement for Overtime Calculation

We have improved the capture and display of employee overtime information. You can now choose to capture employee overtime rate calculation information on the periodic archive and then display it on the enhanced payslip template. When running the periodic archive process, use the new Archive Overtime Rate Calculation Information field. If you select Yes, the person’s overtime hours and rate displays in the Overtime Rate Calculation Information section of their payslip.

Archive Overtime Rate Calculation Information Field

Steps to Enable

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

Tips And Considerations

This applies to nonexempt employees only.

This does not apply to retirees.

HR Optimization

Workforce Rewards Transactional Business Intelligence

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.

Compensation

OTBI Additional Percentage Columns - Workforce Compensation Budget Subject Area

We have made it easier for you to report on Workforce Compensation Budget with the addition of Percentage columns.

Previously we offered these amount columns:

Published Distribution Budget Amount
Published Worksheet Budget Amount
Unpublished Distribution Budget Amount
Unpublished Worksheet Budget Amount

These percentage columns were added:

Published Distribution Budget Percent
Published Worksheet Budget Percent
Unpublished Distribution Budget Percent
Unpublished Worksheet Budget Percent

Steps to Enable

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