1. Understanding Scheduled Processes
  2. Fully Loads HCM Person Mapping Data for Reporting

Fully Loads HCM Person Mapping Data for Reporting

Use the ‘Fully Loads HCM Person Mapping Data for Reporting’ scheduled process to create BI reports involving Helpdesk Contact (Worker) Business Unit and Organization.

Fully 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). This process truncates SVC_BI_HCM_PERSON_REF_MAP table and then perform a full load.

When to Use

This process needs to be executed when there are new or updated assignments for person records. This is an on-demand job. You must run this job in the following scenarios:

  • Any time HCM person mapping data needs to be fully refreshed;

Privileges Required

Verify that you have the following privilege:

  • 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

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • Based on need

  • Execution Time:

    • For single data record, the estimated execution time is less than 1 second;

    • For batch job on volume of 10K records, the estimated execution time is less than 1 minute;

  • Compatibility:

    • 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

Use this information to troubleshoot the scheduled process.

  • 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.