What’s New in 23C: Core HR

What’s New in 23C: Core HR

Autor: Sobitha Venkatraman, Solutions Architect – HCM, Namos Solutions

Among all of the features that were released in the 23C quarterly update in environments from August 2023, the following features will bring some breather to implementers for Core HR. This blog is aimed at providing an insight into how some key enhancements can aid your operational requirements and bring improved business outcomes for your HR Operations.

Core HCM Enhancements – Core HR Module

Operational Requirement – Tags to Support Document Type classification/grouping and Multiple Occurrences check for document records at assignment level.

Document Records (DoRs) already bring rich functionality whereby the business operations use the DoRs to store all the documents related to e.g.; Employment, Legal, Identification Category groupings. Now we can use the Tag capability to group by other types of dimensions/groupings – a good example of this is based by Business Processes. This can be leveraged further by using the Business Process Tag groupings in your Business as Usual (BAU) reporting.

As with the Tag functionality we also now have the option to enable Multiple Occurrence DoRs at the assignment level rather than person level.  This further capability allows Document Records to be stored as singulars or multiples based at Assignment or Person level. This better meets the needs of organisations giving full flexibility to store as many occurrences of Documents of the same Type, as is necessary at Assignment level.

23C Release Solution – With 23C we now have the option to Classify document types using tags from a user-defined list. You can add additional values to the user lookup type ORA_PER_DOC_TYPE_TAGS. Once the look up is configured with the Tags list of values you can then select the available Tags on the Redwood Document Records landing page to filter records in a future release.

In 23C we now also have the option to Check for multiple occurrences of document records based on assignment, and not person. When creating document records, the multiple occurrences check is done at the assignment level and not the person, thereby allowing users to create a document record per assignment when the Allow Multiple Occurrences flag is set to ‘No’ and the Document Type Level is Assignment. With this feature, you can now create one document record per assignment instead of one document record per person when Document Type Level is Assignment. This is an out-of-box available and no steps are involved to enable this feature.

Operational Requirements: External URL on same Assigned Journey Page – 

Journeys are collections of tasks and ‘experience’ items, grouped and assigned to employees by managers or HR teams, who then monitor an employee’s progress. When we have employees who need to access an external link from the task page then we can achieve this now in 23C. This is beneficial to customers where the end user needs to open hyperlinks where they need to fill in various forms, update a questionnaire, or any type of form input which has an external link.  This enables them to complete the full suite of tasks on the same Journey page. This will enable the employees to complete the task immediately once the URL is completed with details rather than going back to Assigned journeys and open the task to complete the step.

23C Release Solution – In 23C now we can configure the option to open the hyperlink of an External URL task type on the same Journey page instead of a new browser tab. This can be achieved by enabling the Open URL on the same page check box in the External URL area, on the Journey Task configuration page so the user can open the URL on the same page.

Operational Requirement – Route Position Approvals to the AOR of the Parent Position incumbent

Approvals form a major part in operational business and daily BAU so an audit is maintained when the process needs approval. Earlier you can route approvals to parent position incumbent. With AOR to Route position approvals where the Transactions such as Request a New Position or Request a Position Change will send a notification to the AOR of the incumbent of the parent position for approval. This enhancement is very beneficial to customers where the position create or update is managed by Finance/HR team and requires approval from the Parent position incumbent. We can then assign AOR to the Parent position and then route approvals which will limit the process of using Approval groups or any offline process.

23C Release Solution – The approvals can now be routed to the representatives of the incumbents in the parent position for these processes:

  • Request New Position
  • Request Position Change
  • Edit Position
  • Delete Position
  • Delete Date Effective Position Record

When you want to create a new position first, we need to set the Representative Type and assign this to the Parent Position incumbent and then select the value of the representative from the LOV on the approvals.

Operational Requirement – Redwood experience for Pending Workers

While using Oracle Recruiting or Oracle Human Resources, Pending Workers who are hired in Oracle from a major part in New Person hiring. If we can consume a dashboard which can give us an entire overview of the name, person number and planned start date that will benefit the HR users to see all the information and edit pages as a one stop page for Pending Workers rather than running a report separately, edit the pending worker or convert a pending worker. This saves time on a day-to-day basis, particularly so, where volumes of Pending Workers and hiring is high. Thus, all changes can be made available on a dashboard and perform actions under a single dashboard. You also can customise the dashboard to suit your needs to either add new fields or hide any unwanted fields.

23 Release Solution – Enrich the user experience with the new Pending Workers dashboard developed using the Redwood tool set. The dashboard is built from the ground up using Visual Builder Studio (VBS) to give you a unique experience of Oracle applications. You can search for a pending worker based on the name or person number. You can also sort the search results based on the name and planned start date.

Human Resource Specialists and Line Managers can also do the following using this dashboard:

  • Add Pending Worker
  • Convert Pending Worker
  • Include or exclude a Pending Worker for Auto-conversion
  • Edit Pending Worker
  • Perform all actions on a Pending Worker record

In order to work with the new Pending Workers page, you must first enable the ORA_HCM_VBCS_PWA_ENABLED profile option. In addition, check if the ORA_PER_PWK_DASHBOARD_REDWOOD_ENABLED profile option is also enabled.

There are also some privileges which need consideration, if you’re an existing customer, then there are no changes to be made to your custom roles. New customers will have to assign the privileges (As mentioned in the 23C Release) to their custom roles to access and work with the new Pending Workers page.

Namos Solutions

Namos Solutions is an Oracle partner that can implement, support, and review your Oracle investment. Oracle HCM unlocks the power of one system, one point of truth and a unified experience. If you need any help, advice or would like to talk to us about implementing Oracle or reviewing the system you already have please get in touch with our Business Development Team, you can find their information on our website – www.namossolutions.com.