Why should I use the Maintain Party and Location Current Record Information process?
You can use this Maintain Party and Location Current Record scheduled process to sync worker records in Human Capital Management (HCM) to person parties and to update the current profile record for people, organizations, and locations based on today's date.
Syncing worker records to person party records helps in managing applications such as HR Help Desk, HCM Payroll, Expense, and so on. This scheduled process creates or updates person party records with party usage of HR_EMPLOYEE or HR_CONTINGENT_WORKER that are defined as workers in HCM such as pending worker, employee, contingent worker, nonworkers, and so on. This scheduled process updates person party records with party usage of HR_EMPLOYEE or HR_CONTINGENT_WORKER that are defined in HCM as canceled hire or purged worker.
In HCM, active workers are workers who are continuing in the organization. For example, employee and contingent worker. Future workers are workers who aren’t currently part of the organization. For example, pending worker.
- Normal Mode: All the person types listed in the table below except for employee and contingent worker who were hired in the past or current date are synchronized.
- Full Mode: Employee and contingent worker who were hired in the past or current date
are synchronized in addition to the person types processed in the normal mode.The following table lists the person types that are supported for synchronization in this scheduled process:
List of person types supported for synchronization in this scheduled process
Person Type Hire Date Sync in Normal Mode Sync in Full Mode Employee Past Date/ Current Date No Yes Employee Future Date Yes Yes Contingent Worker Past Date/ Current Date No Yes Contingent Worker Future Date Yes Yes Pending Worker Past Date/Current Date /Future Date Yes Yes Nonworker Past Date/Current Date /Future Date Yes Yes Ex-Employee Past Date/Current Date /Future Date Yes Yes Ex-Contingent Worker Past Date/Current Date /Future Date Yes Yes Ex-Pending Worker Past Date/Current Date /Future Date Yes Yes Ex-Nonworker Past Date/Current Date /Future Date Yes Yes Purged Worker Past Date/ Current Date Yes Yes
Prerequisites
This scheduled process syncs active workers only when the profile option Enable Current Active Worker Sync For MPLCRI Job (ORA_HZ_ENABLE_MPLCRI_ACTIVE_WORKER) is set to yes (Y), and HRC_DISABLE_HCM_EVENTS_PROCESSING profile option is set to yes. This setting is named as Full mode. When the HRC_DISABLE_HCM_EVENTS_PROCESSING profile option is set to yes, Change Person Details events aren't published. Therefore, both the profile options (ORA_HZ_ENABLE_MPLCRI_ACTIVE_WORKER and HRC_DISABLE_HCM_EVENTS_PROCESSING) must be set to yes to avoid creating duplicate person parties while syncing active HCM worker records.
Profile Option | Normal Mode | Full Mode |
---|---|---|
ORA_HZ_ENABLE_MPLCRI_ACTIVE_WORKER | No | Yes |
HRC_DISABLE_HCM_EVENTS_PROCESSING | N | Y |
This setting is only applicable to active workers and not applicable to other person records such as nonworkers, contingent workers, and so on.
When to Use
This scheduled process is used to:
-
De-normalize the future dated current location profile, party sites, and contact points based on today's date with extended support to future end-dated records.
-
Create a party record for a Human Capital Management person record, if the party doesn't exist.
-
Synchronize the first name, middle name, the last name, the title of the person, work phone, and work email attributes of the person records.
- When you purge the employee record of a purged worker, run this scheduled process to purge the corresponding person details. This scheduled process end dates the person usage assignment and synchronizes the deleted details of the purged worker.
Privileges Required
Verify that you have the following privileges or roles:
-
Application Implementation Consultant
-
Master Data Management Application Administrator
Before You Start
Review the following before scheduling this scheduled process:
-
Recommended Frequency:
-
When there is a requirement to create or update worker records as person parties to complete business flows such as setting up direct payment methods, then run this scheduled process.
-
The scheduled process can be run when HCM workers are created or updated from HCM interfaces like HDL loader and then to sync workers into person parties.
-
-
Compatibility:
-
This scheduled process is self-incompatible. If multiple instances are submitted, the first instance runs, and subsequent instances remain in Wait status.
-
Ensure that you don't schedule this process and the Synchronize Person Records process at the same time.
-
Parameters
Parameter |
Optional or Mandatory |
Description |
Parameter Values |
Special Combinations Required |
None |
---|---|---|---|---|---|
Synchronization Type |
Optional |
Specify the object to be synchronized. You can specify Worker (HR Persons) or Party and location (De-normalize Parties). If you don't select anything, both objects are synchronized. |
|
Not applicable |
None |
Person Type |
Optional |
Specify the type of person records to be synchronized. |
|
Synchronization Type must be Worker. |
None |
From Date |
Optional |
Specify the from date in the date range during which employee records were created or updated. |
Select a date. |
Synchronization Type must be Worker. |
None |
To Date |
Optional |
Specify the to date in the date range during which the employee records were created or updated. |
Select a date. |
Synchronization Type must be Worker. |
None |
Person Number |
Optional |
Specify the person number to be synchronized. |
Specify a valid person number. |
Synchronization Type must be Worker. |
None |