Cloud Readiness / Oracle HCM Cloud Common
What's New
Expand All


  1. APRIL MAINTENANCE PACK FOR 21A
  1. Revision History
  2. Overview
  3. Feature Summary
    1. HCM Data Loader
        1. Business Object Enhancements
  1. MARCH MAINTENANCE PACK FOR 21A
  1. Revision History
  2. Overview
  3. Feature Summary
    1. HCM Data Loader
        1. Business Object Enhancments
  1. Update 21A
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Applications Security
        1. Hide Candidate Security Profile When Candidate Security Is Not Enabled
    2. HCM Data Loader
        1. Visibility of Objects that Support Being Rolled Back
        2. Business Object Enhancements
        3. Remove Person Information Enhancements
        4. Processed Source Files Automatically Deleted
    3. HCM Spreadsheet Data Loader
        1. Roll Back Spreadsheet Data
        2. Secured Business Objects Now Available to Business Users
        3. Reduced Maximum Days Retention for Extended Data Sets
    4. HCM Extract
        1. Purge HCM Extracts Archive Data Using Remove Person Information Feature
        2. Protect Oracle Delivered HCM Extracts from Edits
    5. HCM Common Features
        1. Hidden Attributes in Business Objects for Configure Business Objects and Autocomplete Rules
        2. Secure Access for Workers with Multiple Assignments
    6. HCM Common Architecture
        1. Atom Feeds for Additional HCM Transactions
  4. IMPORTANT Actions and Considerations
  5. Controlled Availability
    1. Controlled Availability Features
        1. Autocomplete Rules for HCM Experience Design Studio Enhancements
        2. Oracle Search-Based Global Search
        3. Oracle Search for HCM

April Maintenance Pack for 21A

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 Product Feature Notes
26 MAR 2021     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 (21A, 21B, 21C, and 21D)
  • 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:

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 in Release Readiness under Human Capital Management or via the Oracle Help Center under Cloud Applications > Human Capital Management.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com. Indicate you are inquiring or providing feedback regarding the HCM Cloud What’s New in the body or title of the email.

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.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

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*

HCM Data Loader

Business Object Enhancements

HCM Data Loader

HCM Data Loader provides a flexible and efficient method of bulk loading business object data for data-migration and on-going incremental updates to Oracle Human Capital Management Cloud.

Business Object Enhancements

Extend your data loading capabilities with these extended business objects:

Compensation

Business Object New Component Description
Salary Salary Simple Component Specifies the adjustment to salary simple components as an amount or percentage, when the work salary basis is based on simple components.

Recruiting

Business Object New Component Description
Job Requisition Tax Credit Configuration Specifies screening services added to a job requisition for work order tax credits.
Job Requisition Tax Credit Screening Package Specifies screening packages added to a job requisition for work order tax credits.
Job Requisition Template Tax Credit Configuration Specifies screening services added to a job requisition template for work order tax credits.
Job Requisition Template Tax Credit Screening Package Specifies screening packages added to a job requisition template for work order tax credits.

You can extend your integration coverage and bulk loading capabilities.

Steps to Enable

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

Key Resources

Use the View Business Objects task to review the latest business object information.

March Maintenance Pack for 21A

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 Product Feature Notes
26 MAR 2021     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 (21A, 21B, 21C, and 21D)
  • 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:

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 in Release Readiness under Human Capital Management or via the Oracle Help Center under Cloud Applications > Human Capital Management.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com. Indicate you are inquiring or providing feedback regarding the HCM Cloud What’s New in the body or title of the email.

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.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

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*

HCM Data Loader

Business Object Enhancments

HCM Data Loader

HCM Data Loader provides a flexible and efficient method of bulk loading business object data for data-migration and on-going incremental updates to Oracle Human Capital Management Cloud.

Business Object Enhancments

You can now roll back records created for the following Payroll business objects:

Object File Name
Costing Options CostInfoV3.dat
Cost Allocation CostAllocationV3.dat
Cost Allocation Account CostAllocationAccountV3.dat
Element Entry with Costing ElementEntryWithCosting.dat

You can now roll back records created for the following Payroll business objects: Costing Options, Cost Allocation, Cost Allocation Account, and Element Entry with Costing.

Steps to Enable

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

Tips And Considerations

Only newly created records can be rolled back. You can't roll back records that have been updated since they were created.

Key Resources

  • Use the View Business Objects task to review the latest business object information.

Update 21A

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 Product Feature Notes
26 MAR 2021

HCM Common Features

Enhanced Rich Text Editor

Removed feature from update 21A.

29 JAN 2021 Controlled Availability Controlled Availability Features

Updated document. Revised feature information.

29 JAN 2021 HCM Data Loader Business Object Enhancements

Updated document. Revised feature information.

29 JAN 2021

HCM Common Features

Enhanced Rich Text Editor

Updated document. Revised feature information.

18 DEC 2020 HCM Common Features Enhanced Rich Text Editor

Updated document. Delivered feature in update 21A.

18 DEC 2020

HCM Common Features

Secure Access for Workers with Multiple Assignments

Updated document. Delivered feature in update 21A.

18 DEC 2020

HCM Data Loader Processed Source Files Automatically Deleted

Updated document. Delivered feature in update 21A.

18 DEC 2020

HCM Data Loader

Reduced Maximum Days Retention for Extended Data Sets

Updated document. Delivered feature in update 21A.

04 DEC 2020     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 (21A, 21B, 21C, and 21D)
  • 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:

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 in Release Readiness under Human Capital Management or via the Oracle Help Center under Cloud Applications > Human Capital Management.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com. Indicate you are inquiring or providing feedback regarding the HCM Cloud What’s New in the body or title of the email.

Feature Summary

Column Definitions:

Features Delivered Enabled

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.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Features 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.

Action is Needed BEFORE Use by End Users
(Features 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*

Applications Security

Hide Candidate Security Profile When Candidate Security Is Not Enabled

HCM Data Loader

Visibility of Objects that Support Being Rolled Back

Business Object Enhancements

Remove Person Information Enhancements

Processed Source Files Automatically Deleted

HCM Spreadsheet Data Loader

Roll Back Spreadsheet Data

Secured Business Objects Now Available to Business Users

Reduced Maximum Days Retention for Extended Data Sets

HCM Extract

Purge HCM Extracts Archive Data Using Remove Person Information Feature

Protect Oracle Delivered HCM Extracts from Edits

HCM Common Features

Hidden Attributes in Business Objects for Configure Business Objects and Autocomplete Rules

Secure Access for Workers with Multiple Assignments

HCM Common Architecture

Atom Feeds for Additional HCM Transactions

>>Click for IMPORTANT Actions and Considerations

Controlled Availability

Controlled Availability Features

Autocomplete Rules for HCM Experience Design Studio Enhancements

Oracle Search-Based Global Search

Oracle Search for HCM

Applications Security

Oracle Applications Security provides a single console where IT Security Managers and Administrators can perform various functions including user lifecycle management, role definition, security policy management(both functional and data), role hierarchy maintenance, username and password policy administration, and certificate management. The console also enables users to simulate the effect of security changes, to run security reports, and download a connector for integration with Microsoft Active Directory.

Hide Candidate Security Profile When Candidate Security Is Not Enabled

You can see the Candidate Security Profile in the Manage Data Roles and Security Profiles page for Recruiting data roles only when the Oracle Recruiting Candidate Security profile option (ORA_IRC_CANDIDATE_SECURITY_ENABLED) is enabled. This security profile won’t appear either on the sub-train stop or on the Review page.

This profile option is disabled by default.

This feature simplifies the definition of Recruiting data roles when candidate security is not enabled.

Steps to Enable

The Candidate Security profile option (ORA_IRC_CANDIDATE_SECURITY_ENABLED) is disabled by default. Enable this profile option if you want to see the Candidate Security Profile on the Manage Data Roles and Security Profiles page. Let’s look at the steps to enable the profile option.

1. Navigate to the Setup and Maintenance work area and search for the Manage Administrator Profile Values task.

2. Search for the ORA_IRC_CANDIDATE_SECURITY_ENABLED profile option.

3. Select the Level as Site.

4. Change N to Y for the site level row.

5. Click Save and Close.

Tips And Considerations

When migrating data roles between environments, ensure that the Candidate Security Profile option setting is configured to be the same on both environments.

Key Resources

For more details and related information, please refer to the following feature within this document:

  • HCM Common What's New for 20D, the feature is Candidate Security

HCM Data Loader

HCM Data Loader provides a flexible and efficient method of bulk loading business object data for data-migration and on-going incremental updates to Oracle Human Capital Management Cloud.

Visibility of Objects that Support Being Rolled Back

Understand which HCM Data Loader objects support their data being rolled back from the application tables. The business object table in the View Business Objects task now includes the Roll Back Supported column:

Roll Back Supported on the Business Objects Table

Drilling down to the Business Object details page, the Component Details tab displays the level of roll back support:

Roll Back Support on the Component Details Tab

The Overview spreadsheet, downloaded from the Business Object table also displays the level of roll back support:

Roll Back Support in the Overview Spreadsheet

You can now identify which business objects support being rolled back. The View Business Objects task and Overview spreadsheet, available from this task, have been enhanced to include the roll back support available for each object.

Steps to Enable

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

Business Object Enhancements

Extend your data loading capabilities with these new and enhanced business objects

New Business Objects

Global Payroll

Business Object Description
Payroll Retro Component Usage

Defines processing rules that define an element's behavior when processed by the retroactive process.

Business Object Hierarchy Changes

Global HR - Checklists

Business Object Component Description
Allocated Checklist Allocate Checklist Display Property

A reference to the allocated checklist display property. The default value can be overridden by passing an appropriate property and property value.

Allocated Checklist

Allocate Checklist Task Display Property

A reference to the allocated checklist task display property. The default value can be overridden by passing an appropriate property and property value.

Checklist Template Checklist Display Property A reference to the checklist display property. The default value can be overridden by passing an appropriate property and property value.

Checklist Template

Checklist Task Display Property A reference to the checklist task display property. The default value can be overriden by passing an appropriate property and property value.

Checklist Template

Checklist Actions A checklist action stores event and action configurations based on which a checklist can be triggered.
Task Library Task Library Notification Notification overrides for tasks in the task library.

Task Library

Task Library Display Property A reference to the task library display property. The default value can be overridden by passing an appropriate property and property value.

Global Payroll

Business Object Component Description
Event Group Event Group Action A group of related events, such as changes to an employee's assignment, monitored for features such as the retroactive recalculation of payroll and time cards, or the generation of HCM rates.
Event Action Event Group Action The Event Group Action component has been decommissioned from the Event Action hierarchy and is now available under the Event Group hierarchy.

Recruiting

Business Object New Component Description
Candidate Candidate National Identifier A unique alpha-numeric value assigned by a legal authority to represent a person. For example, this can be the social security number in the US and the national insurance number in the UK.
Candidate Job Application Questionnaire Response Participant Candidates responses to a questionnaire.
Candidate Job Application Questionnaire Response Responses provided by a participant for the questions from a specific version of a questionnaire.
Candidate Job Application Question Response Responses provided by a participant to a specific question in a questionnaire.

Business Object Attribute Changes

Absence Management

Business Object Component New Attributes
Absence Entry Advanced Absence Entry
  • ParentAssignmentNumber
Absence Entry Absence Entry Attachment
  • AssignmentId
  • AssignmentNumber

Compensation

Business Object Component New Attributes Decommissioned Attributes
Salary Salary Component
  • AssignmentId
  • ElementEntryId
Salary Basis Salary Basis  
  • LegalEntityId
  • Language

Global HR

Business Object Component New Attributes Decommissioned Attributes
Allocated Checklist Allocated Checklist
  • BackgroundImageURL
 

Allocated Checklist

Contents
  • Sequence
 

Allocated Checklist

Tasks
  • SaveAttachmentsDORFor
  • SaveTaskDORFor
 

Checklist Template

Checklist Template
  • BackgroundImageURL

 

Checklist Template

Contents
  • Sequence
 

Checklist Template

Tasks
  • SaveAttachmentsDORFor

  • SaveTaskDORFor

 
Document Type Document Type
  • DocumentTypeLevel
  • RestrictCreateAttach
  • RestrictDeleteAttach
  • RestrictUpdateAttach
Document Type Document Type Delivery Preference  
  • EmailEnabledFlag
Document Record Document Record
  • AssignmentId
  • AssignmentNumber
  • AttachmentEntityName
Document Record Document Record Attachment  
  • EntityName
Document Record Delivery Preference Document Record Delivery Preference  
  • EmailEnabledFlag
Task Library Task Library
  • SaveAttachmentsDORFor
  • SaveTaskDORFor
 
Worker Assignment
  • ContractId
  • ContractNumber
 
Worker Contract
  • ContractNumber
 

Global Payroll

Business Object Component New Attributes Decommissioned Attributes
Event Action Event Action  
  • AlertId
  • AlertCode
  • AlertTemplateId
  • AlertTemplateCode
  • EventActionTypeId
  • AutoApprove
  • ProcessMode
Costing Options Costing Options
  • OrganizationPaymentMethiodId
 
Cost Allocation Cost Allocation
  • OrganizationPaymentMethiodId
 
Cost Allocation Account Cost Allocation Account
  • OrganizationPaymentMethiodId
 
Calculation Card Card Association Detail  
  • RelationshipGroupId
Calculation Card Component Association Detail  
  • RelationshipGroupId
Rate Definition Rate Contributor  
  • ContributorInputValueId
  • FactorValueInputValueId

Recruiting

Business Object Component New Attributes
Candidate Candidate
  • PhoneVerifiedFlag
Content Library Content Library
  • CaptureInteraction
  • InteractionContent
Content Library Translation Content Library Translation
  • InteractionContent
Job Requisition Template Job Requisition Template
  • AutomaticFillFlag
  • DisplayInOrgChartFlag
  • ApplyWhenNotPostedFlag

Talent Management

Business Object Component New Attributes
Succession Plan Succession Plan
  • EnabledIncumbentJobChangeAlert
  • EnabledMovedToDiffRoleAlert
  • EnableSuccessorAlert
  • IncumbentRoleChangeFlag
Succession Plan Succession Plan Candidate
  • ShowSuccessionStatusFlag
  • SuccessionStatus
Talent Review Meeting Talent Review Meeting
  • IncludeMatrixMgmt

You can extend your integration coverage and bulk loading capabilities.

Steps to Enable

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

Tips And Considerations

Use the View Business Objects task to review the latest business object information.

Remove Person Information Enhancements

We now have a separate privilege for the Report mode (ORA_HRC_GENERATE_REMOVE_PERSON_INFORMATION_FILE). Having this privilege alone grants the user access to the Report mode only. The existing privilege, ORA_HRC_REMOVE_PERSON_INFORMATION grants access to both remove and report modes.

Granting access to the report mode only lets you have flexibility over the user's privileges.

Steps to Enable

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

  1. Create a new job role.
  2. Add the policy "Configure Person Information Removal Policies" (HRC_CONFIGURE_PERSON_INFO_REMOVAL_POLICIES_PRIV) under Function Security Policies to access the Configure Person Information Removal Policies page to this new role.
  3. Add the "Remove Person Information" (ORA_HRC_REMOVE_PERSON_INFORMATION) role under Role Hierarchy for accessing both Report and Remove modes under the Remove Person Information page.
  • To access the Report mode alone, add the ORA_HRC_GENERATE_REMOVE_PERSON_INFORMATION_FILE role under Role Hierarchy instead.
  1. Create a Person Security Profile to restrict access to workers if needed.
  2. Create a Data role and to it, assign the new job role. Assign the appropriate Person Security Profile.
  3. Add the new data role to the appropriate user. Add the new data role to the appropriate user.

Role Information

Any implementation user who can grant access and privileges can assign the requisite permissions for the role.

Processed Source Files Automatically Deleted

When you load files, even those selected from your desktop, the file is placed on the WebCenter Content server in the HCM Data Loader import account. By default, the file is deleted from the WebCenter Content server once the data has been transferred to the HCM Data Loader staging tables.  The Delete Source File parameter controls this behavior when you import and load the file.

Each file loaded from the WebCenter Content server creates a data set in the HCM Data Loader staging tables. If the source file still remains, it will be deleted when the data set is deleted. When submitting the deletion of a data set, the Delete Source File parameter can be overridden to retain the source file.

Source files that remain will now be automatically deleted from the WebCenter Content server once they have expired. The Delete Stage Table Data process will first delete expired data sets, then remove expired source files.

Your processed source files will now automatically be deleted from the Oracle WebCenter Content server, once they have expired.

Steps to Enable

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

Tips And Considerations

By default, source files expire 30 days after they were used to create a data set. You can override the default retention period using the Days to Retain Processed Source Files Before Deleting parameter in the Configure HCM Data Loader task.

If you have a large number of expired source files, the Delete Stage Table Data process will delete the first 1000 files. Removing a large number of source files will occur over a number of iterations of the process.

Key Resources

For more information, see the following help topics in the Integrating with HCM guide located in the Oracle Help Center:

  • HCM Data Loader Configuration Parameters

HCM Spreadsheet Data Loader

HCM Data Loader provides a flexible and efficient method of bulk loading business object data for data-migration and on-going incremental updates to Oracle Human Capital Management Cloud.

Roll Back Spreadsheet Data

Roll back the spreadsheet data you have loaded, using the new Roll Back button available on the Spreadsheet Loader toolbar:

Roll Back Button

You can now roll back data loaded directly from the spreadsheet used to load the data.

Steps to Enable

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

Tips And Considerations

You can only roll back data that hasn't been updated since it was loaded and only for the objects which support being rolled back.

Key Resources

Use the View Business Object task to identify which objects support being rolled back.

Secured Business Objects Now Available to Business Users

Extend your business users' bulk-loading capabilities for an object. Spreadsheets based on these objects now implement the user's data security and can be shared with business users.

Global Payroll

  • Calculation Card

Your business users can bulk load data for these objects using spreadsheets.

Steps to Enable

When creating a new spreadsheet template, the template security automatically defaults to the setting where data is uploaded as the session user. For existing templates based on these objects, you can update the template configuration and set the user type to session user.

Key Resources

For more information, see the following help topics in the Integrating with HCM guide located in the Oracle Help Center:

  • HCM Spreadsheet Data Loader Templates
  • How You Associate a User Name with a Data Upload

Reduced Maximum Days Retention for Extended Data Sets

Data sets containing data for business objects supporting roll back can be retained for an extended period of time. The maximum duration has been reduced to 60 days since the data set was last processed.

Data sets are automatically deleted after they expire.

Steps to Enable

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

Tips And Considerations

The Days to Preserve Extended Retention Data Sets parameter, available in the Configure HCM Data Loader task controls the duration to retain data sets for the purposes of roll back.

The Enable Automatic Extended Data Set Retention parameter determines whether data sets containing objects that support roll back are automatically retained for an extended period, the default is No. You can manually extend the duration of data set retention from the Import and Load Data task. 

Key Resources

For more information, go to the Oracle Help Center for the following help topics:

  • HCM Data Loader Configuration Parameters
  • Extending the Retention Period of a Data Set

HCM Extract

HCM Extracts provide a method for extracting data from your HCM applications that can be used for interfacing data to another source or extracting data to integrate reporting across systems.

Purge HCM Extracts Archive Data Using Remove Person Information Feature

You can clean-up the extracts generated archive data, when running the Remove Person Information process for an ex-employee, by selecting the 'Extracts Archive' from the list of available business objects.

Purge process relies on the threading database item defined for an extract to determine the archive data for a given ex-employee to be purged. Following threading DBIs, if defined for an extract, will facilitate associating the archive data to the person number passed to the process.

  • Person Id
  • HR Assignment Id
  • Work Relationship Id
  • Payroll Relationship Id 
  • Payroll Assignment Id

You no longer need to retain data for terminated or canceled employees.

Steps to Enable

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

Tips And Considerations

  • When extracts are run again for the purged ex-employees, any leftover data that remain in the system may still get reported in the extracts and archived. You should consider excluding these purged employees from your extracts run.
  •  You can run Purge Extracts Archive Data to purge archive data generated by specific extracts and archives that are older than 90 days.

Protect Oracle Delivered HCM Extracts from Edits

For delivered or seeded extracts, users cannot edit the extract. Make a copy of the delivered extract to change or add a parameter. 

Instead of creating the extract definition again, you can now make a copy of the seeded or delivered extract and make your changes.

Steps to Enable

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

HCM Common Features

This section covers features used across all HCM Applications.

Hidden Attributes in Business Objects for Configure Business Objects and Autocomplete Rules

The Configure Business Objects and Autocomplete Rules tasks have been streamlined with changes in the business objects and related attributes. Deprecated business objects are removed and a few attributes are hidden in the respective business objects. The attributes won't be available in manual groovy in the Configure Business Objects task and logic rules in Autocomplete Rules pages. Hence, manual groovy and logic rules must be reviewed for each impacted business object.

This table lists the previous and current names for each business object..

Business Object Name Until 20D Action in 21A

Business Object Name from 21A

Action Occurrences Business object renamed and attributes cleaned up When and Why
Address Business object renamed and attributes cleaned up Address
AssignedPayrollDVO Business object renamed and attributes cleaned up Assigned Payroll
AssignedPayrollVO Business object renamed and attributes cleaned up Assigned Payroll Additional Info
DIRComponentDetailDVO Business object removed -
Deprecated ActionOccurrencesBOVO Business object removed -
Deprecated Address Business object removed -
Deprecated AssignmentBOVO Business object removed -
Deprecated AssignmentSupervisorBOVO Business object removed -
Deprecated AssignmentWorkMeasureBOVO Business object removed -
Deprecated ContractsBOVO Business object removed -
Deprecated Person Address Business object removed -
Deprecated Person Citizenship Business object removed -
Deprecated Person Contact Relationship Business object removed -
Deprecated Person Detail Business object removed -
Deprecated Person Email Business object removed -
Deprecated Person Legislative Information Business object removed -
Deprecated Person Name Business object removed -
Deprecated Person National Identifier Business object removed -
Deprecated Person Passport Business object removed -
Deprecated Person Phone Business object removed -
Deprecated Person Visa Business object removed -
Deprecated Work Relationship Business object removed -
Document Records Attributes cleaned up Document Records
- New business object in 21A Person Profile Education
- New business object in 21A Goals
 

New business object in 21A

Goal Measurements
 

New business object in 21A

Goal Tasks
 

New business object in 21A

Goal Relations with Goal Plan

- New business object in 21A Person Profile Certification
PayDateVO Business object removed -
PayMassGLBTransferConfigVO Business object renamed and attributes cleaned up Payroll Global Transfer
PayrollAssignmentDVO Business object renamed and attributes cleaned up Payroll Assignment
PayrollRelationshipDVO Business object renamed and attributes cleaned up Payroll Relationship
PayrollTermsVO Business object renamed and attributes cleaned up Payroll Terms
People Group Business object renamed and attributes cleaned up Employment People Group
Person Attributes cleaned up Person
Person Address Attributes cleaned up Person Address
Person Citizenship Attributes cleaned up Person Citizenship
Person Contact Relationship Attributes cleaned up Person Contact Relationship
Person Delivery Method Attributes cleaned up Person Delivery Method
Person Detail Attributes cleaned up Person Detail
Person Driver License Attributes cleaned up Person Driver License
Person Email Attributes cleaned up Person Email
Person Ethnicity Attributes cleaned up Person Ethnicity
Person Identifier Attributes cleaned up Person Identifiers for External Applications
Person Legislative Information Attributes cleaned up Person Legislative Information
Person Name Attributes cleaned up Person Name
Person National Identifier Attributes cleaned up Person National Identifier
Person Passport Attributes cleaned up Person Passport
Person Phone Attributes cleaned up Person Phone
Person Religion Attributes cleaned up Person Religion
Person Visa Attributes cleaned up Person Visa
Position Business object removed  
PositionBOVO Business object renamed and attributes cleaned up Position
PositionHierarchyVO Business object removed -
SalaryBOVO Unchanged in 21A Salary
SalaryVO Business object renamed Deprecated Salary (new name effective 21A)
Work Assignment Business object renamed and attributes cleaned up Work Assignment
Work Relationship Business object renamed and attributes cleaned up Worker Work Relationship
Work Term Contract Business object renamed and attributes cleaned up Worker Employment Contract
Worker Assignment Supervisor Business object renamed and attributes cleaned up Worker Assignment Supervisor
Worker Assignment Work Measure Business object renamed and attributes cleaned up Worker Assignment Work Measure

Hidden Attributes in Business Objects

Some attributes are hidden from a list of business objects and won't be available in manual groovy in Configure Business Objects and Autocomplete Rules tasks. Manual groovy in Configure Business Objects and logic rules in Autocomplete Rules must be reviewed for each impacted business object.

The following attributes are hidden in HCM Cloud from release 21B. It's strongly recommended to remove these attributes from Manual Groovy in Configure Business Objects in release 21A.

Hidden Attributes for Employment

Business Object Attribute
Work Assignment APPLICANT_RANK
Work Assignment AUTO_END_FLAG
Work Assignment BILLING_TITLE
Work Assignment CAGR_GRADE_DEF_ID
Work Assignment CAGR_ID_FLEX_NUM
Work Assignment DUTIES_TYPE
Work Assignment FREEZE_START_DATE
Work Assignment FREEZE_UNTIL_DATE
Work Assignment JOB_POST_SOURCE_NAME
Work Assignment LINKAGE_TYPE
Work Assignment PERSON_REFERRED_BY_ID
Work Assignment PO_HEADER_ID
Work Assignment PO_LINE_ID
Work Assignment POSTING_CONTENT_ID
Work Assignment PROJECT_TITLE
Work Assignment RECRUITER_ID
Work Assignment RECRUITMENT_ACTIVITY_ID
Work Assignment SAL_REVIEW_PERIOD
Work Assignment SAL_REVIEW_PERIOD_FREQUENCY
Work Assignment SOFT_CODING_KEYFLEX_ID
Work Assignment SOURCE_ORGANIZATION_ID
Work Assignment SOURCE_TYPE
Work Assignment SPECIAL_CEILING_STEP_ID
Work Assignment STEP_ENTRY_DATE
Work Assignment VENDOR_ASSIGNMENT_NUMBER
Work Assignment VENDOR_EMPLOYEE_NUMBER
Work Assignment VENDOR_ID
Work Assignment VENDOR_SITE_ID
Work Relationship ACCEPTED_TERMINATION_DATE
Work Relationship COMMENTS
Work Relationship DATE_EMPLOYEE_DATA_VERIFIED
Work Relationship FAST_PATH_EMPLOYEE
Work Relationship ON_MILITARY_SERVICE
Work Relationship REHIRE_AUTHORIZOR
Work Relationship TERMINATION_ACCEPTED_PERSON_ID
Work Relationship WORKER_COMMENTS
Work Term Contract CONTRACTUAL_JOB_TITLE
Work Term Contract DOC_STATUS
Work Term Contract DOC_STATUS_CHANGE_DATE
Work Term Contract END_REASON
Work Term Contract EXTENSION_REASON
Work Term Contract PARTIES
Work Term Contract REFERENCE
Work Term Contract START_REASON
Work Term Contract STATUS
Work Term Contract STATUS_REASON
Work Term Contract WORK_TERMS_TYPE
Worker Assignment Supervisor FREEZE_START_DATE
Worker Assignment Supervisor FREEZE_UNTIL_DATE
Worker Assignment Supervisor PRIMARY_FLAG
Worker Assignment Supervisor SUP_ATTRIBUTE_CATEGORY
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE1
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE10
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE11
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE12
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE13
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE14
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE15
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE2
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE3
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE4
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE5
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE6
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE7
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE8
Worker Assignment Supervisor SUP_ATTRIBUTE_DATE9
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER1
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER10
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER11
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER12
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER13
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER14
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER15
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER16
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER17
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER18
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER19
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER2
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER20
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER3
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER4
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER5
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER6
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER7
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER8
Worker Assignment Supervisor SUP_ATTRIBUTE_NUMBER9
Worker Assignment Supervisor SUP_ATTRIBUTE1
Worker Assignment Supervisor SUP_ATTRIBUTE10
Worker Assignment Supervisor SUP_ATTRIBUTE11
Worker Assignment Supervisor SUP_ATTRIBUTE12
Worker Assignment Supervisor SUP_ATTRIBUTE13
Worker Assignment Supervisor SUP_ATTRIBUTE14
Worker Assignment Supervisor SUP_ATTRIBUTE15
Worker Assignment Supervisor SUP_ATTRIBUTE16
Worker Assignment Supervisor SUP_ATTRIBUTE17
Worker Assignment Supervisor SUP_ATTRIBUTE18
Worker Assignment Supervisor SUP_ATTRIBUTE19
Worker Assignment Supervisor SUP_ATTRIBUTE2
Worker Assignment Supervisor SUP_ATTRIBUTE20
Worker Assignment Supervisor SUP_ATTRIBUTE21
Worker Assignment Supervisor SUP_ATTRIBUTE22
Worker Assignment Supervisor SUP_ATTRIBUTE23
Worker Assignment Supervisor SUP_ATTRIBUTE24
Worker Assignment Supervisor SUP_ATTRIBUTE25
Worker Assignment Supervisor SUP_ATTRIBUTE26
Worker Assignment Supervisor SUP_ATTRIBUTE27
Worker Assignment Supervisor SUP_ATTRIBUTE28
Worker Assignment Supervisor SUP_ATTRIBUTE29
Worker Assignment Supervisor SUP_ATTRIBUTE3
Worker Assignment Supervisor SUP_ATTRIBUTE30
Worker Assignment Supervisor SUP_ATTRIBUTE4
Worker Assignment Supervisor SUP_ATTRIBUTE5
Worker Assignment Supervisor SUP_ATTRIBUTE6
Worker Assignment Supervisor SUP_ATTRIBUTE7
Worker Assignment Supervisor SUP_ATTRIBUTE8
Worker Assignment Supervisor SUP_ATTRIBUTE9
Worker Assignment Supervisor WORKING_PERCENTAGE
Worker Assignment Work Measure ADDS_TO_BUDGET
Worker Assignment Work Measure AWM_Attribute _CATEGORY
Worker Assignment Work Measure AWM_Attribute 1
Worker Assignment Work Measure AWM_Attribute 10
Worker Assignment Work Measure AWM_Attribute 11
Worker Assignment Work Measure AWM_Attribute 12
Worker Assignment Work Measure AWM_Attribute 13
Worker Assignment Work Measure AWM_Attribute 14
Worker Assignment Work Measure AWM_Attribute 15
Worker Assignment Work Measure AWM_Attribute 16
Worker Assignment Work Measure AWM_Attribute 17
Worker Assignment Work Measure AWM_Attribute 18
Worker Assignment Work Measure AWM_Attribute 19
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE1
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE10
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE11
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE12
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE13
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE14
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE15
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE2
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE3
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE4
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE5
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE6
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE7
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE8
Worker Assignment Work Measure AWM_ATTRIBUTE_DATE9
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER1
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER10
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER11
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER12
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER13
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER14
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER15
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER16
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER17
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER18
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER19
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER2
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER20
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER3
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER4
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER5
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER6
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER7
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER8
Worker Assignment Work Measure AWM_ATTRIBUTE_NUMBER9
Worker Assignment Work Measure AWM_ATTRIBUTE2
Worker Assignment Work Measure AWM_ATTRIBUTE20
Worker Assignment Work Measure AWM_ATTRIBUTE21
Worker Assignment Work Measure AWM_ATTRIBUTE22
Worker Assignment Work Measure AWM_ATTRIBUTE23
Worker Assignment Work Measure AWM_ATTRIBUTE24
Worker Assignment Work Measure AWM_ATTRIBUTE25
Worker Assignment Work Measure AWM_ATTRIBUTE26
Worker Assignment Work Measure AWM_ATTRIBUTE27
Worker Assignment Work Measure AWM_ATTRIBUTE28
Worker Assignment Work Measure AWM_ATTRIBUTE29
Worker Assignment Work Measure AWM_ATTRIBUTE3
Worker Assignment Work Measure AWM_ATTRIBUTE30
Worker Assignment Work Measure AWM_ATTRIBUTE4
Worker Assignment Work Measure AWM_ATTRIBUTE5
Worker Assignment Work Measure AWM_ATTRIBUTE6
Worker Assignment Work Measure AWM_ATTRIBUTE7
Worker Assignment Work Measure AWM_ATTRIBUTE8
Worker Assignment Work Measure AWM_ATTRIBUTE9
Worker Assignment Work Measure FREEZE_START_DATE
Worker Assignment Work Measure FREEZE_UNTIL_DATE

 Hidden Attributes in Document Records in Global Human Resources

Business Object Attribute
DocumentsOfRecord

VerifiedBy

DocumentsOfRecord

VerifiedDate

DocumentsOfRecord

LastUpdateDate

DocumentsOfRecord

LastUpdatedLogin

DocumentsOfRecord

LastUpdatedBy

DocumentsOfRecord

CreatedBy

DocumentsOfRecord

CreationDate

DocumentsOfRecord

EnterpriseId

DocumentsOfRecord Status
DocumentsOfRecord

RelatedObjectId

DocumentsOfRecord

RelatedObjectIdCol

DocumentsOfRecord RelatedObjectName

Hidden Attributes for Salary

Business Object Atribute
alaryBOVO ObjectVersionNumber
SalaryBOVO ActionOccurrenceld
SalaryBOVO Assignmentld
SalaryBOVO Salaryld

Hidden Attributes for Workforce Structures

Business Object Attribute
LocationPVO LocationId
LocationPVO BusinessGroupId
LocationPVO SetName
LocationPVO SetCode
LocationPVO Description2
LocationPVO GeoHierarchyNodeId
LocationPVO GeoHierarchyNodeValue
LocationPVO Geometry
LocationPVO AddInformation11
LocationPVO AddInformation12
LocationPVO AddInformation13
LocationPVO AddInformation14
LocationPVO AddInformation15
LocationPVO AddInformation16
LocationPVO AddInformation17
LocationPVO AddInformation18
LocationPVO AddInformation19
LocationPVO AddInformation20
LocationPVO ObjectVersionNumber
LocationPVO CreatedBy
LocationPVO CreationDate
LocationPVO LastUpdatedBy
LocationPVO LastUpdateDate
LocationPVO LastUpdateLogin
LocationPVO LocLongitude
LocationPVO LocLatitude
LocationPVO FormattedMultiLineAddress
LocationPVO SetId1
LocationPVO Description1
LocationPVO LanguageCode
LocationPVO FormattedFaxPhoneNumber
LocationPVO FormattedMainPhoneNumber
LocationPVO FormattedOtherPhoneNumber
LocationPVO InventoryOrganizationName
LocationPVO OrganizationId
LocationPVO EffectiveStartDate2
LocationPVO EffectiveEndDate2
LocationPVO ObjectVersionNumber1
LocationPVO Language
LocationPVO SysEffectiveDate
LocationPVO InventoryOrganizationCode
LocationPVO OrganizationId1
 LocationLegislativePVO LocationLegislativeId
 LocationLegislativePVO LocationId
 LocationLegislativePVO BusinessGroupId
 LocationLegislativePVO ObjectVersionNumber
 LocationLegislativePVO CreatedBy
 LocationLegislativePVO CreationDate
 LocationLegislativePVO LastUpdatedBy
 LocationLegislativePVO LastUpdateLogin
 LocationLegislativePVO SysEffectiveDate
LocationExtraInfoPVO SysEffectiveDate
LocationExtraInfoPVO LocationExtraInfoId
LocationExtraInfoPVO LocationId
LocationExtraInfoPVO BusinessGroupId
LocationExtraInfoPVO ActionOccurrenceId
LocationExtraInfoPVO ObjectVersionNumber
LocationExtraInfoPVO CreatedBy
LocationExtraInfoPVO CreationDate
LocationExtraInfoPVO LastUpdatedBy
LocationExtraInfoPVO LastUpdateDate
LocationExtraInfoPVO LastUpdateLogin
OrganizationPVO ObjectVersionNumber
OrganizationPVO CreatedBy
OrganizationPVO CreationDate
OrganizationPVO LastUpdatedBy
OrganizationPVO LastUpdateDate
OrganizationPVO LastUpdateLogin
OrganizationPVO SysEffectiveDate
OrganizationInformationPVO SysEffectiveDate
OrganizationInformationPVO ActionOccurrenceId
OrganizationInformationPVO BusinessGroupId
OrganizationInformationPVO CreatedBy
OrganizationInformationPVO CreationDate
OrganizationInformationPVO LastUpdateDate
OrganizationInformationPVO LastUpdateLogin
OrganizationInformationPVO LastUpdatedBy
OrganizationInformationPVO ModuleId
OrganizationInformationPVO ObjectVersionNumber
OrganizationInformationPVO OrgInformationId
OrganizationInformationPVO OrganizationId
LegalEmployerLOVPVO OrganizationId
LegalEmployerLOVPVO SysEffectiveDate
LegalEmployerLOVPVO EffectiveStartDate1
LegalEmployerLOVPVO EffectiveEndDate1
LegalEmployerLOVPVO OrganizationId1
LegalEmployerLOVPVO EffectiveStartDate2
LegalEmployerLOVPVO EffectiveEndDate2
JobPVO BusinessGroupId
JobPVO ObjectVersionNumber
JobPVO CreatedBy
JobPVO CreationDate
JobPVO LastUpdatedBy
JobPVO LastUpdateLogin
JobPVO SysEffectiveDate
JobPVO SetId1
JobPVO JobFamilyName
JobPVO JobFamilyId1
JobPVO EffectiveStartDate1
JobPVO EffectiveEndDate1
JobPVO ObjectVersionNumber1
JobLegislativePVO CreatedBy
JobLegislativePVO CreationDate
JobLegislativePVO LastUpdateDate
JobLegislativePVO LastUpdateLogin
JobLegislativePVO JobLegId
JobLegislativePVO ObjectVersionNumber
JobLegislativePVO LastUpdatedBy
JobExtraInformationPVO CreatedBy
JobExtraInformationPVO CreationDate
JobExtraInformationPVO JobExtraInfoId
JobExtraInformationPVO LastUpdateDate
JobExtraInformationPVO LastUpdateLogin
JobExtraInformationPVO LastUpdatedBy
JobExtraInformationPVO ObjectVersionNumber
JobFamilyPVO BusinessGroupId
JobFamilyPVO CreatedBy
JobFamilyPVO CreationDate
JobFamilyPVO LastUpdatedBy
JobFamilyPVO LastUpdateDate
JobFamilyPVO LastUpdateLogin
JobFamilyPVO ObjectVersionNumber
JobFamilyPVO SysEffectiveDate
PositionPVO BusinessGroupId
PositionPVO HiringStatusMeaning
PositionPVO PositionSynchronizationFlag
PositionPVO ObjectVersionNumber
PositionPVO CreatedBy
PositionPVO CreationDate
PositionPVO LastUpdatedBy
PositionPVO LastUpdateDate
PositionPVO LastUpdateLogin
PositionPVO LookupType
PositionPVO LookupCode
PositionPVO LocationDetailsId
PositionPVO EffectiveStartDate4
PositionPVO EffectiveEndDate4
PositionPVO LocationName
PositionPVO LocationId1
PositionPVO BUName
PositionPVO OrganizationId
PositionPVO OrganizationId1
PositionPVO EffectiveStartDate3
PositionPVO EffectiveEndDate3
PositionPVO Language2
PositionPVO EffectiveStartDate5
PositionPVO EffectiveEndDate5
PositionPVO Language3
PositionPVO EffectiveStartDate1
PositionPVO EffectiveEndDate1
PositionPVO SysEffectiveDate
PositionPVO JobDPEO.JobName
PositionPVO ObjectVersionNumber1
PositionPVO JobId1
PositionPVO EffectiveStartDate2
PositionPVO EffectiveEndDate2
PositionPVO ObjectVersionNumber3
PositionPVO ObjectVersionNumber4
PositionLegislativePVO ActionOccurrenceId
PositionLegislativePVO PositionId
PositionLegislativePVO CreatedBy
PositionLegislativePVO CreationDate
PositionLegislativePVO LastUpdateDate
PositionLegislativePVO LastUpdateLogin
PositionLegislativePVO LastUpdatedBy
PositionLegislativePVO ObjectVersionNumber
PositionLegislativePVO PositionLegId
PositionExtraInformationPVO PositionId
PositionExtraInformationPVO ActionOccurrenceId
PositionExtraInformationPVO CreatedBy
PositionExtraInformationPVO CreationDate
PositionExtraInformationPVO LastUpdateDate
PositionExtraInformationPVO LastUpdateLogin
PositionExtraInformationPVO LastUpdatedBy
PositionExtraInformationPVO ObjectVersionNumber
PositionExtraInformationPVO PositionExtraInfoId
PositionBOVO BusinessGroupId
PositionBOVO CreatedBy
PositionBOVO CreationDate
PositionBOVO LastUpdateDate
PositionBOVO LastUpdateLogin
PositionBOVO LastUpdatedBy
PositionBOVO ObjectVersionNumber
PositionBOVO SysEffectiveDate
GradeAllPVO BusinessGroupId
GradeAllPVO SetName
GradeAllPVO ObjectVersionNumber
GradeAllPVO CreatedBy
GradeAllPVO CreationDate
GradeAllPVO LastUpdatedBy
GradeAllPVO LastUpdateDate
GradeAllPVO LastUpdateLogin
GradeAllPVO SetId1
GradeExtraInfoPVO GradeExtraInfoId
GradeExtraInfoPVO GradeId
GradeExtraInfoPVO ActionOccurrenceId
GradeExtraInfoPVO ObjectVersionNumber
GradeExtraInfoPVO CreatedBy
GradeExtraInfoPVO CreationDate
GradeExtraInfoPVO LastUpdatedBy
GradeExtraInfoPVO LastUpdateDate
GradeExtraInfoPVO LastUpdateLogin
GradeExtraInfoPVO SysEffectiveDate
GradeLadderLegislativePVO GradeLadderLegId
GradeLadderLegislativePVO GradeLadderId
GradeLadderLegislativePVO ActionOccurrenceId
GradeLadderLegislativePVO ObjectVersionNumber
GradeLadderLegislativePVO CreatedBy
GradeLadderLegislativePVO CreationDate
GradeLadderLegislativePVO LastUpdatedBy
GradeLadderLegislativePVO LastUpdateDate
GradeLadderLegislativePVO LastUpdateLogin
GradeLadderLegislativePVO SysEffectiveDate
GradeLadderPVO GradeLadderId
GradeLadderPVO BusinessGroupId
GradeLadderPVO ActionOccurrenceId
GradeLadderPVO ObjectVersionNumber
GradeLadderPVO CreatedBy
GradeLadderPVO CreationDate
GradeLadderPVO LastUpdatedBy
GradeLadderPVO LastUpdateDate
GradeLadderPVO LastUpdateLogin
GradeLadderPVO SysEffectiveDate
GradeLadderPVO StepDeterminationCode
GradeLadderPVO ProgActionOccurrenceId
GradeLadderPVO SalaryUpdMethodCode
GradeLadderPVO SalaryElementTypeId
GradeLadderPVO SalaryInputValueId
GradeLadderPVO AllowProgOverrideFlag
GradeLadderPVO AllowSalaryOverrideFlag
GradeLadderPVO SetIdSetPEO.SetCode
GradeLadderPVO SetIdSetPEO.SetName
GradeLadderPVO SetIdSetPEO.SetId
GradeLadderPVO RateSyncActionId
GradeLadderPVO RateSyncActionReasonId
GradeLegislativePVO GradeLegId
GradeLegislativePVO GradeId
GradeLegislativePVO ActionOccurrenceId
GradeLegislativePVO ObjectVersionNumber
GradeLegislativePVO CreatedBy
GradeLegislativePVO CreationDate
GradeLegislativePVO LastUpdatedBy
GradeLegislativePVO LastUpdateDate
GradeLegislativePVO LastUpdateLogin
GradeLegislativePVO SysEffectiveDate
GradePVO GradeId
GradePVO BusinessGroupId
GradePVO SetIdSetPEO.SetName
GradePVO ObjectVersionNumber
GradePVO CreatedBy
GradePVO CreationDate
GradePVO LastUpdatedBy
GradePVO LastUpdateDate
GradePVO LastUpdateLogin
GradePVO SysEffectiveDate
GradePVO SetId1
GradePVO SetIdSetPEO.SetCode
GradePVO Description
GradeRatePVO RateId
GradeRatePVO Name2
GradeRatePVO ActionOccurrenceId
GradeRatePVO Name1
GradeRatePVO ObjectVersionNumber
GradeRatePVO CreatedBy
GradeRatePVO CreationDate
GradeRatePVO LastUpdatedBy
GradeRatePVO LastUpdateDate
GradeRatePVO LastUpdateLogin
GradeRatePVO SysEffectiveDate
GradeRatePVO CurrencyCode1
GradeRatePVO LegislativeDataGroupId1
GradeRatePVO ObjectVersionNumber1
GradeRatePVO Meaning
GradeRatePVO LookupType
GradeRatePVO LookupCode
GradeRatePVO Meaning1
GradeRatePVO LookupType1
GradeRatePVO LookupCode1
GradeRatePVO ProgressionRateFlag
 GradeRateValuePVO RateValueId
 GradeRateValuePVO ObjectVersionNumber
 GradeRateValuePVO CreatedBy
 GradeRateValuePVO CreationDate
 GradeRateValuePVO LastUpdatedBy
 GradeRateValuePVO LastUpdateDate
 GradeRateValuePVO LastUpdateLogin
 GradeRateValuePVO SysEffectiveDate
 GradeRateValuePVO EffectiveStartDate1
 GradeRateValuePVO EffectiveEndDate1
 GradeRateValuePVO ObjectVersionNumber1
 GradeRateValuePVO Minimum_t
 GradeRateValuePVO Maximum_t
 GradeRateValuePVO MidValue_t
 GradeRateValuePVO Value_t
 GradeRateValuePVO CurrencyCode_t
StepRateValuePVO ObjectVersionNumber
StepRateValuePVO CreatedBy
StepRateValuePVO CreationDate
StepRateValuePVO LastUpdatedBy
StepRateValuePVO LastUpdateDate
StepRateValuePVO LastUpdateLogin
StepRateValuePVO SysEffectiveDate
StepRateValuePVO EffectiveStartDate1
StepRateValuePVO EffectiveEndDate1
StepRateValuePVO ObjectVersionNumber1
StepRatePVO Name2
StepRatePVO Name1
StepRatePVO ObjectVersionNumber
StepRatePVO CreatedBy
StepRatePVO CreationDate
StepRatePVO LastUpdatedBy
StepRatePVO LastUpdateDate
StepRatePVO LastUpdateLogin
StepRatePVO CurrencyCode1
StepRatePVO SysEffectiveDate
StepRatePVO LookupType
StepRatePVO LookupCode
StepRatePVO Meaning
StepRatePVO Meaning1
StepRatePVO LookupType1
StepRatePVO LookupCode1
StepRatePVO LegislativeDataGroupId1
StepRatePVO ObjectVersionNumber1
GradesInLadderPVO ObjectVersionNumber
GradesInLadderPVO CreatedBy
GradesInLadderPVO CreationDate
GradesInLadderPVO LastUpdatedBy
GradesInLadderPVO LastUpdateLogin
GradesInLadderPVO SysEffectiveDate
GradesInLadderPVO LastUpdateDate
GradeStepPVO ObjectVersionNumber
GradeStepPVO CreatedBy
GradeStepPVO CreationDate
GradeStepPVO LastUpdatedBy
GradeStepPVO LastUpdateLogin
GradeStepPVO SysEffectiveDate
GradeStepLegislativePVO GradeStepLegId
GradeStepLegislativePVO GradeStepId
GradeStepLegislativePVO ActionOccurrenceId
GradeStepLegislativePVO ObjectVersionNumber
GradeStepLegislativePVO CreatedBy
GradeStepLegislativePVO CreationDate
GradeStepLegislativePVO LastUpdatedBy
GradeStepLegislativePVO LastUpdateDate
GradeStepLegislativePVO LastUpdateLogin
GradeStepLegislativePVO SysEffectiveDate

The Configure Business Object task is streamlined by the most current attributes.

Steps to Enable

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

Secure Access for Workers with Multiple Assignments

We continue to enhance the HCM footprint for securing user access for workers by using assignment-level security, if your organization allows them to have multiple assignments. The current out-of-the-box behavior supports person-based security access, which means a user having access to a person has access to all assignments and personal information for that person. The new assignment-level security restricts a user's access to a person's assignment based on the user's area of access. By enabling a new assignment-level security profile option and regenerating your data grants and security profiles, your organization opts into this feature for your HCM Cloud implementation.

This is the second feature release of a multi-phased implementation for HCM Cloud customers. This release provides further enhancements to Absence Management, Document Records, Global HR OTBI Reporting, Performance, and Personal Payment Methods from the Payroll product area.  The respective HCM quick actions and person searches have been modified to provide a broader and more consistent user experience for organizations with multiple assignments. The users will be restricted to only those assignments to which they have access and not all assignments of the person just because they can access that person. These are a few examples to explain this functionality:

Scenario 1: A line manager and HR specialist are responsible for a worker who is both a registered nurse in the emergency room (ER) department and also has a different assignment as a senior citizens memory ward coordinator. This worker may have two different line managers, and each should only see the worker's single assignment in their respective organizations. The line managers should not see assignments for different departments, in this case ER department and memory ward. Likewise, there may be two HR representatives supporting each department (or business unit). The HR representative should not be able to access the assignment in an organization that they don't have access to.

Scenario 2: Harry is a manager with multiple concurrent assignments. He also has a direct report, Jane who has two assignments herself with two different managers. In this scenario, Harry should only be able to access Jane's primary assignment and Franco (Jane's direct report). However, Harry should not be able to access Jane's second assignment, and certainly not Kyle.

Example of Intended Line Manager Access for a Worker with Multiple Concurrent Assignments

Scenario 3: Lisa works at a school and has two assignments, one as an academic counselor and as a sports coach. As an academic counselor, Lisa reports to Dave. Dave should be able to see Lisa's absence plan balances, cash disbursements, leave donations, and her work schedules specifically for the academic counselor assignment. Dave should also be able to access Lisa's absences that impact this assignment, and be asked to approve any absences from this assignment only. Dave should not be able to access absence plan balances for the sports coach assignment, and must not be able to view or approve absences that only impact the sports coach assignment.

Several quick action search results are now modified in HCM to restrict user access to the assignments that they have access to. Here's an example, of before and after turning on assignment-level security.

Manager Accessing the My Team Work Area with Person-Based Security Enabled

Manager Accessing the My Team Work Area with Assignment-Based Security Enabled

If you turn on this feature you can lock down security to the assignment level. This allows managers and organizations to only see information that is within their area of responsibility.

Steps to Enable

  1. Prerequisites:

    1. Enable approvals for transactions that use assignment-level security. For example, transactions, such as Administer Individual Compensation, Administer Salary, Manage Salary, Person External Identifiers, Salary History, Approve Performance Document, and Work-Schedule Assignments.

      • For information on enhancements to the approval rule page, refer to the 20C HCM Common What's New for the Enhancements to the Human Capital Management Approval Rules UI feature.

      • For information on enhancements to the transaction approvals supporting multiple assignments in HCM, refer to the Global HR 20D What's New for the Enhanced Transaction Approvals Support Multiple Assignments in Global Human Resources feature.

    2. Manually update security for custom roles using instructions from Implementing Assignment-Level Security in HCM (Document ID 2700661.1) on My Oracle Support. Note: Our regeneration processes will not alter any custom criteria. You must manually update security for custom roles because it is not a delivered functionality.

    3. Enable the responsive pages for the transactions by enabling the HCM_RESPONSIVE_PAGES_ENABLED profile option. See step 3 on how to enable this profile option. Note: You don’t need to enable for these classic payroll pages because they have no responsive pages: Payroll Relationship, Element Entries, Calculation Entries, and Costing for a Person.

  2. To secure access for workers with multiple assignments, you must enable this profile option:  

    Field Value
    Profile Option Code

    ORA_PER_ASSIGNMENT_LEVEL_DATA_SECURITY_ENABLED

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

    1. Search for and click the Manage Administrator Profile Values task.

    2. Search for and select the profile option.

    3. Click to add a new Profile Value.

    4. Select the Level as Site.

    5. Enter a Y in the Profile Value field.

    6. Click Save and Close.

Enabling Assignment-Level Security Profile Option

  1. Run the Regenerate Data Security Profiles and Grants ESS job set to convert person security profile grants and update data roles. These 2 processes are run as part of the job set:

    1. Regenerate Data Security Grants

    2. Regenerate Data Security Profiles

Run Regenerate Data Security Profiles and Grants Job Set

NOTE: Cloud Operations will initiate the Regenerate Data Security Profiles and Grants job set as part of your upgrade to customer environments. After receiving your environment back after the Update, your IT Security Manager user will have the ability to view the status of the job set. The IT Security Manager must verify that the job set is successfully run to completion. Depending on the size of your organization, the job set process may still be running when your environment is returned. Please ensure that you don't release to your user population without testing your custom data roles. If the job set fails for some reason, your IT Security Manager must manually run the job set, and make sure it completes successfully. On-premise HCM customers will still need to run the job set manually before beginning upgrade testing.

  1. To enable assignment-level security in the employment contract, you must run the Migrate Employment Data process by selecting this run mode: Enhance contract data to enable its use in the responsive pages. For more information about the Migrate Employment Data process, see the Process to Migrate Contract Data topic under the Hire and Manage Workers chapter of the Using Global Human Resources guide. You can access the guide from Oracle Help Center.

Person Security Profile Displays a Blue Banner Message to Confirm that the Assignment-Level Security is Enabled

  1. Assignment-level security will work automatically for plan balances, disbursements, donations, and work-schedule assignments when you do the setup steps from 1 through 4. For existing absences and absence entry, assignment-level security is enabled only if Absences are entered at the assignment-level. To understand how this works, refer to the Absence Management 21A What's New features: Prevent Absences from Impacting Multiple Assignments and Enhanced Absence Security for Workers with Multiple Assignments

  2. Enable approvals for impacted transactions.

    1. Absence Management flows:

      1. Absences: On the absence type setup page, set the value for the Approvers field to: Managers of all relevant assignments. To do this, follow these steps:

        1. Click Navigator > My Client Groups > Absences > Absence Type. Create or edit an existing absence type

        2. You can select the approvers from the Approvers list in the Absence Record Maintenance section.

        3. The default value is Manager of employee’s primary assignment. Select Managers of all relevant assignments to set up approvals for managers of all assignments the employee is involved in.

      2. Disbursements and donations: You can configure the approval task in the Transaction Console to send the approval request either to just the primary assignment manager or to the line manager of the assignment from which employee is requesting the cash disbursement or initiating the donation. For example, you can configure the approval rule to seek approval from the manager of the transaction’s assignment. Now, if an employee tries to initiate a donation from a specific assignment, the approval request goes to the line manager of that assignment.

      3. Work-schedule assignments: Here’s how you can configure the work schedule assignment approvals so that the approval notifications for work-schedule assignment changes go to the relevant assignment’s manager of the employee instead of the primary assignment manager: For more information, refer to the Absence Management 21A What's New feature: Route Work Schedule Assignment Approvals to the Appropriate Manager

        1. Click Tools > Transaction Console in the Home Page.

        2. Click Approval Rules.

        3. Search Manage Work Schedule Assignment and click edit to configure approval rules.

        4. Select the relevant component from the chain of approval.

        5. Set the Approval Chain Of field to Requester and set assignment type to Use current assignment hierarchy. Note: When you pick "Requester" in the Approval Chain of field, the application assumes that this means the "employee". So, the approval will be routed to the employee's manager.

    2. Document Records flows: Approvals will now route to the manager of the appropriate assignment, if configured to do so.

    3. Performance Management flows:

      1. Run the Approve Performance Document approval task.

      2. Select the assignment type configuration option (Use primary assignment or Use current assignment) in the approval rule definition.

  3. Enable the responsive user interface, except for these classic user interfaces as there are no responsive equivalents for them:

    1. Absences:

      1. There is no enabling responsive user interface because all classic pages which have a responsive equivalent have been removed in release 20D. All customers see responsive pages where responsive pages exist, otherwise, they see classic pages. The classic pages that we still support, and have been enhanced to support assignment-level security are:

        1. Absence Records

        2. Work Schedule Assignments

These classic pages will support assignment-level security when accessed only through the quick actions, and not through the Person Management page. Enable the responsive user interface using instructions from HCM Responsive User Experience Setup Information (Doc ID 2399671.1) on My Oracle Support.

Tips And Considerations

  • You can't enable the assignment-level security profile option with the Oracle Search profile option. You can enable only one of these profile options in this release.

  • The custom criteria on the Person Security Profile won't be modified by any Oracle processes, and you need to manage your custom criteria. To update your custom criteria, refer to the MOS Doc ID listed in the Key Resources section.

  • The Share Data Access action doesn't yet support assignment-level security. If you use the action in your organization, your users will continue to have access to all assignments for a shared person.

  • Employment:

    • After you enable assignment-level security, you can’t use this navigation to manage assignment data for an assignment that you don’t have access to: Person Management work area > Classic Manage Employment page

    • The employment tree icon on the classic manage employment page won’t be visible after you enable assignment level security.

  • Talent Management:

    • The Talent Review, Succession, and Talent Pools features don’t support multiple assignments. The worker list of values (LOVs) only allow the user to select a primary assignment.

    • Succession Quick Actions: Although the quick action supports assignment-level security, if the user selects a nonprimary assignment from the quick actions search page, it’s the primary assignment information that will be displayed and saved in the succession plan.

    • Career Development Quick Actions: Although the quick action supports assignment-level security, the user will be able to view all development goals for the employees, irrespective of the assignment. This means a user, such as a line manager having access to a person has access to all development goals of that person.

    • Career Development Admin pages: The search results include all development goals for employees who meet the user's security profile definition. This means an HR specialist having access to a person has access to all development goals of that person.

  • Absence Management:

    • HCM Assignment security does not work on person-level absences, meaning any manager or HR administrator who has access to the employee can access all absences of this type. Any manager or administrator can view and manage advanced entries belonging to all assignments, even those that they are not authorized to see.
    • HCM Assignment Security, if enabled, applies only to absences entered at assignment-level. Such an absences is visible only to managers or administrators who are authorized to access the specific assignment for which the absence was created. Managers and administrators can enter assignment-level absences only for assignments that they have the authority to access.
    • If “Allow one assignment per absence” is selected, and the employee wants to take time off from all assignments using this type, the employee must enter separate absences for each assignment.
    • If you use absence approvals and implement HCM Assignment Security, you must configure the absence type to set the approvers to “Managers of relevant assignments”. This ensures that the notifications do not go to managers who don’t have access to the assignment for which the absence was created.
    • Once the absence is saved, the business title or assignment can’t be changed. If you want to change the business title, you need to withdraw the absence and create a new one.
    • If you enable HCM Assignment security and use absence approvals, you must configure the absence types to send approval requests to managers of relevant assignments. This ensures that absences are routed to the correct manager for approval.
    • Absences impacting multiple assignments are considered absences entered at person level. These absences will continue to be secured at person level. This means that any manager or administrator who has access to this employee will be able to view and manage all such absences.
    • Qualification plan entitlements and Entitlement Agreements are at the person-level. Therefore, this information will be visible to all administrators who have access to the person. 
    • If you want the absences to be fully secured, you need to ensure that they are entered at assignment level. This means that you need to ensure that a specific assignment is selected when entering an absence.
    • If you use absence approvals and implement HCM Assignment Security, you must configure the absence type to set the approvers to “Managers of relevant assignments”. This ensures that the notifications do not go to managers who don’t have access to the assignment for which the absence was created.
    • Absences data loaders do not support Assignment Security because they run with super user privileges.
    • Assignment-level security doesn’t work when using the classic Person Management page. It will only work through the quick actions. Administrators need to ensure that they access Absence Records page or Work Schedule Assignments page using the quick actions only.
  • Document Records:

    • Document Record Approval Routing:

      • This feature will not replace your existing application behavior, but if you want to leverage the feature, you have to make the necessary configuration changes.

      • This feature is applicable only to document record related approvals.

      • The default approval rule is set to primary assignment hierarchy.

      • If the approval rule is set to primary assignment hierarchy, irrespective of which assignment you select, the approval always goes to the line manager of the primary assignment.

      • If the approval rule is set to current assignment hierarchy, the approval always goes to the line manager of the assignment you selected.

    • Document Record:

      • Use of Document Records in the Benefits area remains at the person-level access only.

    • Global HR OTBI Reporting:
      • With assignment-level security enabled, either of these conditions apply:

        • A manager can only see the assignments they have access to, but can't see person level document records.

        • A manager can see all assignments and then see document records for their assignment and the person level assignments.

  • These HCM flows have no enhancements in 21A, but are planned for a future release:

    • Areas of Responsibility (AOR)
    • Global HR - Mass Assignments
    • Global HR - Share Data Access - remains at person-level
    • Global HR - Share Information - remains at person-level
    • Global HR - My Team - Displaying Vacancies
    • Health & Safety
    • Learning
    • Oracle Recruiting
    • Oracle Search (elastic search - limited/controlled-availability)
    • OTBI - Absences
    • OTBI - Document Records (planned for release 21B)
    • REST Services:
      • Global HR APIs:
        • areasofResponsibility
        • publicWorkers
        • workerConnections
    • Risk Management - Access Certification
    • Risk Management - Advanced Access Controls
    • Time & Labor
    • Workforce Structures - Department
    • Workforce Structures - Position
    • Workforce Structures - Other than Position & Department
    • Workforce Modeling
  • These HCM flows have no enhancements, and are not currently planned at this time:

    • Benefits (Benefits document records will remain at the person level)
    • Global HR - Add Person
    • HCM Extracts
    • Absence Cases
    • Total Compensation Statement
    • Talent Review
    • Succession work area (Note: assignment-level security search is supported in Quick Actions)
    • Talent Pools work area (Note: assignment-level security search is supported in Quick Actions)
  • These HCM flows have limited enhancements:  

    Product area Task flow Enhancement

    Global Human Resources

    Local and Global Transfer

    If there are multiple assignments in the selected assignment's work relationship, then all those assignments are listed in a banner on this task flow page, regardless of the user's access to those assignments.

    Global Human Resources

    Edit Work Relationship

    If there are multiple assignments in the selected assignment's work relationship, then all those assignments are listed in a banner on this task flow page, regardless of the user's access to those assignments.

    Global Human Resources

    Change Legal Employer

    If there are multiple assignments in the selected assignment's work relationship, then all those assignments are listed in a banner on this task flow page, regardless of the user's access to those assignments.

    Global Human Resources

    Cancel Work Relationship

    If there are multiple assignments in the selected assignment's work relationship, then all those assignments are listed in a banner on this task flow page, regardless of the user's access to those assignments.

    Global Human Resources

    Seniority Dates

    Quick Action worker search only.

    Global Human Resources

    Checklists and Onboarding

    Quick Action worker search only.

    Global Human Resources

    Document Delivery Preferences

    Quick Action worker search only.

    Global Human Resources

    Termination, Resignation, and End Assignment

    Quick Action worker search only.

    Global Human Resources

    Manage User Account

    Quick Action worker search only.

    Talent

    Profiles

    Changes to the consistency search in the Quick Action. Quick Action worker search only.

    Talent

    Succession

    Support only for searching people in the Succession Quick Action.

    Talent

    Talent Pools

    Support only for searching people in the Talent Pools Quick Action.

    Talent

    Feedback

    Support only for searching people in the Feedback and Request Feedback Quick Actions.

    Talent

    Career Development

    Quick Action worker search only, and worker lists for Assign and Share actions.

Key Resources

See the following for more information on:

  • Implementing assignment-level security in HCM, see this document on My Oracle Support: Implementing Assignment-Level Security in HCM (Document ID 2700661.1)
  • Displaying document records based on assignment access when assignment-level security Is configured, refer to the Global HR 21A What's New feature: Document Records Displayed Based on Assignment Access When Assignment-Level Security Is Configured
  • Routing document record approvals using current assignment hierarchy, refer to the Global HR 21A What's New feature: Route Document Record Approvals Using Current Assignment Hierarchy
  • Regenerating roles, refer to the Regenerating Roles chapter in the Securing HCM guide on Oracle Help Center
  • Guidelines for copying HCM roles, refer to the Guidelines for Copying HCM Roles topic in the Securing HCM guide on Oracle Help Center
  • Enhancing personal payment method for multiple assignments, refer to the Global Payroll 21A What's New feature: Personal Payment Method Enhanced for Multiple Assignments
  • Enhancing performance document approvals, refer to the Performance Management 21A What's New feature: Performance Document Approval Enhancements

HCM Common Architecture

This section covers features used across all HCM Applications.

Atom Feeds for Additional HCM Transactions

The empupdate and empassignment Atom feeds are now triggered when additional person and employment attributes are updated. You can subscribe to these feeds to receive updates for Oracle HCM Cloud transactions. Feeds are triggered when updates are made to any of the following:

  • Person's citizenship, correspondence language, country, or region of birth
  • Additional address elements
  • Person's visa, email, and delivery preference details
  • Disability information
  • Assignment work measures and contract details

Subscribe to Atom feeds that are triggered for additional Oracle HCM Cloud transactions.

Steps to Enable

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

Tips And Considerations

Review the Atom feed examples for the list of attributes and the criteria that trigger the feeds.

Key Resources

For more information about the feeds and the complete list of attributes, see the REST API for Oracle HCM Cloud guide on the Oracle Help Center.

IMPORTANT Actions and Considerations

REPLACED OR REMOVED FEATURES

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

Product Removed Feature Target Removal Replacement Feature Replaced In Additional Information
  Nothing this release        

_________________________

ORACLE HAS DECOMMISSIONED THE HCM CLASSIC SIMPLIFIED USER INTERFACE IN UPDATE 20B

The new and redesigned HCM Responsive User Experience has been available and promoted as our standard since Update 18B. If you are still using the older HCM Classic Simplified User Interface, you must begin transitioning to the HCM Responsive User Experience, as these older pages will no longer be supported.

For information on the Responsive features, see the HCM Common What's New for Update 18B and 18C. The redesigned features are under a heading for Redesigned User Experience and have groupings by product. Features that have come out from 19A onwards will be in their respective solutions: HCM Common, Global Human Resources, Talent Management, Workforce Management and Workforce Rewards What's News. The feature will be under their product headings. You can open one these solutions such as Workforce Rewards and you will see tabs on the left to easily let you open the different releases to view the responsive features.

For consolidated information on generic setup information you can refer to My Oracle Support Document ID 2399671.1 - HCM Responsive User Experience Setup Information.

Highlights of New User Interface:

We’ve taken the employee and manager self-service pages to the next level by redesigning them to look and behave the same on desktop and mobile devices. We’ve also changed the look and feel of the pages to provide a better experience for end users.

Pages and messages look more modern and use simpler, more conversational language so that you can more easily read and understand content across all devices. The pages are clutter-free and clean and display only those fields that are required to complete the task. You can personalize the pages and add more fields that are hidden by default. For most self-service tasks, you’re asked what you want to do, and the task is broken down into a series of steps based on your choice.

_________________________

KNOWN ISSUES / MONTHLY AND STATUTORY MAINTENANCE PACK

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

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

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

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

Controlled Availability

The following is a list of Controlled Availability features that are being offered by our Controlled Availability Program.

NOTE: These features are not generally available for all customers at this time. These are only available through the Controlled Availability Program and will require approval to become a part of the features program. To be a part of these programs you will be required to participate in testing and providing feedback. Some programs may require other participation as well.

Not to worry if you don't have to time to be a part of these early stage programs. You can uptake this feature when it is generally available for all customers. When these features are available for all customers you will see the features under their product headings as usual.

We invite you all to browse through the list of features to see if there are any features you are interested in implementing in advance of the features scheduled release. The table below will provide information on signing up for features. Please sign up soon, as these programs have limited availability and some are designed for specific types of customers.

The table below gives you a brief description of the features available and how to sign up. Some features are bigger than others, so for more information there may be a What's New describing the feature in more detail below this table.

We look forward to hearing your thoughts and ideas as you participate the Controlled Availability programs!

Product Feature Name Feature Description Type of Customer Needed to Test How to Sign Up Controlled Availability Release Is the Program Still Open?

Across All HCM Products

Autocomplete Rules for HCM Experience Design Studio Enhancements

Create your own rules, on the top of the application to default or validate values using Autocomplete Rules. This is part of the HCM Cloud extensibility tools, a new component of HCM Experience Design Studio that is a data model layer extensibility framework. Rules created can be applied everywhere such as: Responsive pages (only), HCM Data Loader, REST Services, Soap Services, etc.…

All HCM Customers using Responsive Pages Create a Service Request on My Oracle Support requesting to be a part on this controlled availability feature. 20B Open

Across All HCM Products

Oracle Search-Based Global Search

New Global Search for HCM provides faster person search experience and introduces new person search capabilities.

It is based on Oracle Search, a dedicated search platform for Oracle Cloud.

It is dependent on the Oracle Search for HCM feature below.

See the following My Oracle Support Document on how to apply:

Fusion Global HR: How to Apply for Oracle Search-Based Global Search Under Controlled Availability (Doc ID 2743208.1)

21A Open

Across All HCM Products

Oracle Search for HCM

Oracle Search is a dedicated search engine available in your Human Capital Management Cloud environments.

Is dependent on Oracle Search-Based Global Search above or Connections that can be found in the 21A Global HR What's New under Controlled Availability Features.

Customers cannot request Oracle Search as a standalone feature. It has to be requested as via specific Oracle Search-dependent feature like Connections (In 21A Global HR What's New Under Controlled Availability Features or Oracle Search-based Global Search (In the 21A HCM Common What's New under Controlled Availability Features:

  • Fusion Global HR: How to Apply for Connections Under Controlled Availability (Doc ID 2743183.1)
  • Fusion Global HR: How to Apply for Oracle Search-Based Global Search Under Controlled Availability (Doc ID 2743208.1)
21A Open

Controlled Availability Features

Features under this heading are under the Controlled Availability Program. The features are here to provide more information than what the table provides.

NOTE: These features are not generally available to customers and customers need to be approved to use these features.

Autocomplete Rules for HCM Experience Design Studio Enhancements

Rule management in Autocomplete Rules for HCM Experience Design Studio is enhanced with new features such as ability to translate messages, convert decimal to long function, and support for list of values (LOVs) for business objects, where applicable. The list of business objects and associated attributes in Autocomplete Rules is more structured now and display functional names, and obsolete business objects and attributes are removed.

Convert Decimal to Long Function

You can now use the new function to convert a decimal variable to a long variable. When using a flex attribute with a value set definition that returns a data type of 'number', the data type of the flex is a 'bigDecimal'. Whenever you associate a valid entity relationship on another entity, such as 'Salary Basis for a Job', 'Business Unit for a Department' or 'Collective agreement for a job', and so on, using a flex attribute on the parent entity, the value stored in the flex attribute is of type bigDecimal. The data type of the identical corresponding entity (Salary Basis, Business Unit, Collective Agreement) stored in any given transaction Business Object such as Salary, Work Assignment, Position) is Long integer. To copy the value from the flex to the field on the transaction business object in Autocomplete you will need this function. For example, you can use this function when you want to default the salary basis with the salary basis stored in the job descriptive flexfield (DFF) for a specific job code while promoting a worker. Using this function, you can get the salary basis ID from the DFF and pass it to the salary basis in the Salary business object.

The new function is available for a variable defined as a Long type under standard functions. First, you need to define a variable with the new Long type:

Convert Decimal To Long Function

Then, use xyz to change this to the long function.

Translate Messages in Autocomplete Rules

You can now translate warning and error messages in all Oracle supported languages. For more details on translated messages, see the Tips and Considerations section and for information on how to translate messages, see the Key Resources section.

Structured List of Business Objects and Attributes

For a better user experience and easy navigation through the data model, most business objects, attributes, and view accessors are renamed to a more functional and user-friendly name.

  • Business Objects

Most business objects have been renamed with a meaningful name, and unused business objects have been removed.

Renamed Business Objects

This table lists the previous and current names of business object available from release 21A. The old objects will be deprecated and will be replaced with the new objects in release 21B.

Previous Name Current Name
Action Occurrences When and Why
Address Address
AssignedPayrollDVO Assigned Payroll

AssignedPayrollVO

Assigned Payroll Additional Info

Document Records Document Records
-

Person Profile Education

- Goals
- Goal Measurements
- Goal Tasks
- Goal Relations with Goal Plan
- Person Profile Certification
PayMassGLBTransferConfigVO Payroll Global Transfer
PayrollAssignmentDVO Payroll Assignment
PayrollRelationshipDVO Payroll Relationship
PayrollTermsVO Payroll Terms
People Group Employment People Group
Person Person
Person Address Person Address
Person Citizenship Person Citizenship
Person Contact Relationship Person Contact Relationship
Person Delivery Method Person Delivery Method
Person Detail Person Detail
Person Driver License Person Driver License
Person Email Person Email

Person Ethnicity

Person Ethnicity
Person Identifier Person Identifiers for External Applications
Person Legislative Information Person Legislative Information
Person Name Person Name
Person National Identifier Person National Identifier
Person Passport Person Passport
Person Phone Person Phone
Person Religion Person Religion
Person Visa Person Visa
PositionBOVO

Position

SalaryBOVO

Salary

SalaryVO Deprecated Salary
- Succession Plans
Work Assignment Work Assignment
Work Relationship Worker Work Relationship
Work Term Contract Worker Employment Contract
Worker Assignment Supervisor

Worker Assignment Supervisor

Worker Assignment Work Measure Worker Assignment Work Measure
  • Attributes

Attributes for most of the business objects have been renamed with a meaningful name, and unused attributes have been removed.

Renamed Attributes

  • View Accessors

View accessors are used to navigate from a business object to another view. View accessors for most business objects have been renamed with a meaningful name.

Renamed View Accessors

Support for Attribute List of Values

For most business objects, attributes supported by a list of values in the page are also supported by a list of values in Autocomplete Rules.

Supported Attribute LOVs

You need to enable a sandbox to access the HCM Experience Design Studio:

  1. Click Navigator > Configuration > Sandboxes
  2. Click Create Sandbox.
  3. Enter the Name.
  4. Select the Active box for HCM Experience Design Studio.
  5. Click Create and Enter.
  6. Navigate to the My Client Groups tab.
  7. Click Show More to open the quick actions.
  8. Select HCM Experience Design Studio in the Employment group.

This feature enhances the rule management capabilities in Autocomplete.

Steps to Enable

To enable this feature you need to log a Service Request (SR).

Tips And Considerations

  • Use only one language when implementing and maintaining messages, otherwise the translation will be overridden. If the rule is edited in another language and saved while the message is already translated, then the message is overridden and translation will be lost.

Key Resources

For more information on translating existing strings using Configuration Tools, see the Configuring and Extending Applications guide on the Oracle Help Center.

Role Information

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

Oracle Search-Based Global Search

Oracle Search-based Global Search provides faster person search experience and introduces new person search capabilities:

  • Improved relevancy of results
    • Fuzzy person name search - search allows for simple mistakes and typos for up to two spelling differences
    • Name synonyms search - many English sounding names have their synonyms defined, it is possible to search by different forms of the name
    • Fields boosting - person name search is the primary use case and person name matches are of highest relevancy
  • Ability to search by more fields
    • Person Display Name
    • Person Number
    • Work Email Address
    • Business Title

Matches among the direct reports are grouped at the top of the results, followed by matches from the other parts of the organization.

With this feature you are getting improved person search performance comparing to the database implementation and also improved quality of person search results.

Steps to Enable

To enable this feature you need to log a Service Request (SR).

Oracle Search for HCM, which is required for Oracle Search-based Global Search, is currently under controlled availability. Follow the process described in the document below to be part of the controlled availability program:

  • Fusion Global HR: How to Apply for Oracle Search-Based Global Search Under Controlled Availability (Document ID 2743208.1)

Tips And Considerations

Upon searching, Oracle Search-based Global Search will return all active employee, contingent worker, and non-worker assignments as of the current date. There is no option to restrict the search results based on the Public Person security profile definition.

Oracle Search for HCM

Oracle Search is a dedicated search engine available in your HCM environment that:

  • Delivers fast search across large volumes of data
  • Significantly faster than relational database searches

With this feature you will get improved performance on search results.

Steps to Enable

To enable this feature you need to log a Service Request (SR).

Oracle Search for HCM is currently under controlled availability and is a prerequisite for features that depend on it - specifically Connections and Oracle Search-based Global Search. Customers cannot request Oracle Search for HCM as a standalone feature. You will need to log an SR for Connections and/or Oracle Search-based Global Search. Please see the following My Oracle Support documents on how to go about signing up for either feature:

  • Fusion Global HR: How to Apply for Connections Under Controlled Availability (Doc ID 2743183.1)
  • Fusion Global HR: How to Apply for Oracle Search-Based Global Search Under Controlled Availability (Doc ID 2743208.1)