Deprecated - Incrementally Loads HCM Person Mapping Data for Reporting
Use the ‘Deprecated - Incrementally Loads HCM Person Mapping Data for Reporting - Deprecated’ scheduled process to create BI reports involving Helpdesk Contact (Worker) Business Unit and Organization.
note that beginning with 24B, this process is replaced with the customer scheduled ‘Loads HCM Person Mapping Data’. At some point in the future, ‘Deprecated - Execute Incremental Load of HCM Person Mapping Data for Reporting - Deprecated’ will be removed, so customers should begin using ‘Loads HCM Person Mapping Data’.
Incrementally loads HCM person mapping data making it easier for reporting Worker related dimensions Business Unit and Organization. The goal of the process is to provide a consolidation of the assignment information per person (a person has associated only one assignment).
When to Use
This process needs to be executed when there are new or updated assignments for person records.
Privileges Required
- To administer the job the following roles are required with delete, execute,
read and update:
- ORA_SVC_HELPDESK_ADMINISTRATION
- ORA_SVC_SR_ADMINISTRATOR
- To schedule the job the following privilege is required
- SVC_SCHEDULE_SERVICE_JOBS_PRIV
Before You Start
- Beginning with 24B this scheduled process is replaced with ‘Loads HCM Person Mapping Data’. Customers should schedule that process rather than this one. ‘Deprecated - Execute Incremental Load of HCM Person Mapping Data for Reporting – Deprecated’ is automatically scheduled by the system, but if the customer has also manually scheduled the process, they should unscheduled it before scheduling ‘Loads HCM Person Mapping Data’.
- The recommended frequency is daily;
- Execution Time:
- For single data record, the estimated execution time is less than 1 sec;
- For batch job on volume of 10K records, the estimated execution time is less than 1 minute;
- Compatibility:
- Before scheduling this job it is recommend that the job “Execute Full Load of HCM Person Mapping Data for Reporting” is run once in order to fully populate the data;
- No other processes are triggered when this job runs;
- No potential impact on the server performance while this job is running;
- There can be only one instance of the job running at any one time, otherwise there will be issues. A built-in locking mechanism prevents a second instance of the job from being started before the current instance has finished. The job itself parallelizes the gathering of the data.
- There are no issues with business processes executing in parallel with this job;
- This scheduled process is incompatible with itself, therefore only one instance of the job should be running at any particular time;
Parameters
None.
Troubleshooting Information
- Notification of job completion would be using the standard ESS job notification system;
- If the scheduled job does not run successfully, the next scheduled instance will process data from both jobs;
- This scheduled process idempotent, and no cleanup activity is required if the job fails;
- When the scheduled process starts it will attempt to obtain a process lock. If no other instance of the process is running, it will be successful. Upon successful completion or in the event the process fails gracefully, the lock will be released.
- If the scheduled process is unable to obtain a process lock, the lock will automatically expire after 24 hours.
- To verify this scheduled process is running successfully, perform a BI report dimensional query on Helpdesk Contact Business Unit and/or Organization from any subject area that has these dimension. Commonly if the process has never run, the report will return no data; or if not run recently, then the data reported will be stale. For example, in the Help Desk – HR Service Requests Real Time subject area, select elements from HR Service Request Contact > Contact Business Unit and/or HR Service Request Contact > Contact Organization.