Processes to Run After Loading Data

After a successful data migration or incremental update, you must run processes to complete the setup of some business objects. This topic describes these processes.

Processes to Run After Loading Worker

This table identifies processes to run after loading Worker objects. The table also suggests the order in which to run the processes when you're running them all manually.

Process	Order
Synchronize Person Records	1
Refresh Manager Hierarchy	2
Update Person Search Keywords	3
Optimize Person Search Keywords Index	4
Autoprovision Roles for All Users	5
Send Pending LDAP Requests	6
Send Personal Data for Multiple Users to LDAP	7
Apply Name Formats to Person Names	Not applicable

Additionally, there are two mandatory processes that are always run automatically that can’t be disabled:

• EMEA Localizaiton Postprocessing
• Global Tax Reporting Unit Maintenance

By default, these two processes also run automatically when a load of Worker objects completes:

• Refresh Manager Hierarchy
• Update Person Search Keywords

You can prevent either or both of these processes from running automatically using a SET instruction in the Worker.dat file. Alternatively, you can prevent the processes from running for the enterprise by setting configuration parameters.

Run these post-processes in the Scheduled Processes work area.

Select Navigator > Tools > Scheduled Processes.

Process Descriptions

Apply Name Formats to Person Names

Applies the Display Name, List Name, Full Name, or Order Name format to denormalized person-name data when you add or update a name format. Optionally, you can run the process for a single country.

Autoprovision Roles for All Users

Generates requests to provision and remove roles based on current role-provisioning rules.

Optimize Person Search Keywords Index

Optimizes the index of the PER_KEYWORDS table to improve search performance. By default, the process runs for a maximum of 180 minutes and performs a full optimization. You can enter a different Maximum Optimization Time. If you select the Rebuild the index option, then the Maximum Optimization Time value is ignored. Rebuilding the index can be time consuming.

Run this process whenever you run Update Person Search Keywords. Run it after that process completes.

Refresh Manager Hierarchy

For performance reasons, the complete manager hierarchy for each person is extracted from active data tables. The hierarchy is stored in a separate manager hierarchy table, known as the denormalized manager hierarchy (PER_MANAGER_HRCHY_DN). This approach ensures that a person's manager hierarchy is both easily accessible and up to date. The Refresh Manager Hierarchy process populates the denormalized manager hierarchy table with latest information after each data load.

If this process isn't enabled to run automatically, then run it manually after all data loads.

Send Pending LDAP Requests

Sends user-account and role-provisioning requests to your LDAP directory.

Send Personal Data for Multiple Users to LDAP

Ensures that personal data held in your LDAP directory matches that held by Oracle HCM Cloud.

Synchronize Person Records

Notifies consuming Oracle Cloud applications, such as Oracle Fusion Trading Community Model, of changes to person and assignment details since the last data load.

For a once-only load, submit this process with the After Batch Load parameter set to Yes. In the From Date field, enter the start date of the load. In the To Date field, enter the end date of the load. For ongoing updates with daily changes to person records, schedule the process without specifying start and end dates.

Update Person Search Keywords

Several attributes of person, employment, and profile records are used as person-search keywords. This process copies keyword values in all installed languages from the originating records to the PER_KEYWORDS table, where they're indexed to improve search performance.

Select a person name in the Name field to run the process for a single worker. If you leave the field blank, then the process runs for all workers, which can be time consuming. To avoid performance problems, submit the process with the After Batch Load parameter set to Yes. In this case, the process creates keywords for new records but doesn't update those for existing records. Leave the Batch ID field blank.

Automated Post-Processing for Other Objects

Other objects automate the submission of post processing. Refer to Business Object Post Processes topic for further information.

Actions to Perform After Loading Trees

After loading department or organization tree nodes, you must activate your tree version. For more information, see the Implementing Global Human Resources guide.

Process Guidelines

Send Pending LDAP Requests:

You must always run Send Pending LDAP Requests after loading worker records. When you run Send Pending LDAP Requests:

• User accounts are created for new workers.

• Roles are provisioned to user accounts as specified by current role mappings.

If appropriate role mappings don't exist when you load new workers, then user accounts are created but no roles are provisioned. User accounts without roles are automatically suspended when Send Pending LDAP Requests completes. Also, subsequent role-provisioning requests to the suspended user accounts may be slow to process. To avoid this scenario:

1. Create a role mapping to provision at least one role, for example, Employee, to every current worker before you load worker records.

2. Prevent the creation of user accounts for terminated workers. Set the User Account Creation for Terminated Workers option to No using the following in the Setup and Maintenance work area:

   • Functional Area: Workforce Structures

   • Task: Manage Enterprise HCM Information

3. Load worker records.

Note: Always create a role mapping for the workers you're loading before you load them. Having this role-provisioning rule in place prevents new user accounts from being suspended unnecessarily.

Autoprovision Roles for All Users:

You don't have to run this process after the initial or only load of worker records if you create role mappings to autoprovision roles before you load workers. However, if you load the workers before creating the role mapping, then you must run this process followed by Send Pending LDAP Requests for the loaded workers.

You don't have to run this process after an incremental update. However, you're recommended to run this process whenever a change is made to the autoprovisioning rules.

Send Personal Data for Multiple Users to LDAP:

Run this process after the initial or only load of worker records. Run it after an incremental load:

• For changed users only

• If you're loading workers separately from their managers

• If updates were made to personal data by means of SQL scripts