Schedule Processes in HCM

List of process to Schedule in Core HCM Implementation

It is important to schedule the Core HCM Process during and after the implementation for required data updates and synchronize view. Following process you must schedule to meet regular data process need of Core HR.  

#	Process Name	Purpose
1	Update Person Search Keywords	Several attributes of person, employment, and profile records are used as person-search keywords. Keyword values are copied automatically from the originating records to the PER_KEYWORDS table, where they are indexed to improve search performance.
2	Populating Location Latitude and Longitude Information	Once Geo coding is enabled, you can schedule this feature to run at regular time intervals so that newly created or updated locations are picked up and Geo Coded.
3	Geography Name Referencing	The GNR (Geography Name Referencing) process validates address elements in location tables, such as HZ_LOCATIONS, against the master geography data.
4	Refresh Manager Hierarchy	The Refresh Manager Hierarchy process populates the denormalized manager hierarchy table when person records are migrated from other applications. Whenever a change is made to a person's manager hierarchy, the change is reflected automatically in the denormalized manager hierarchy table.
5	Calculate Seniority Dates	The process calculates the seniority date as per the seniority dates you have setup for person records. It's easy to tabulate the seniority dates for more than one person when you use the Scheduled Processes work area. You can schedule and run this calculation process for everyone, just select people, an individual employer's workers or for a worker union. You can set some parameters if you want to run the process for multiple people. Simply enter their person numbers (located on their profile in the Person Management work area) and separate each number by a comma. Points to Remember -        Don't put any leading or trailing spaces or special characters -        The format should look like this: Person Number 1, Person Number 2, Person Number 3. -        To run this process for all persons, don't enter a value that will limit the scope (like selecting a worker union or particular employer) You'll also see assignment changes by looking at the number days in the past period since you last ran the process.
6	Update Person Names	When you update a name format, you must run the process so that the application updates the stored names according to the updated format type rules. You can run the process for a specific name format and legislation combination.
7	Send User Name and Password E-Mail Notifications	You can run the process Send User Name and Password E-Mail Notifications from the Scheduled Processes work area. For users for whom you haven't so far requested an e-mail, this process resets passwords and sends out user names and passwords. The e-mail goes to the primary work e-mail of the user or the user's line manager. You can send the user name and password once only to any user.
8	Reassign Pending Approvals and Direct Reports	Run the Reassign Pending Approvals for Terminations and Correct Invalid Supervisor Assignments process to reassign the direct reports and any pending approval notifications of a manager who is either terminated or globally transferred. You can manually run the process or schedule it to run automatically at a specific time in the Scheduled Processes work area. The process reassigns the direct reports of a terminated manager to that person's line manager. Similarly, it assigns any pending approval notifications to the line manager. You can either reallocate pending notifications or skip this step when you run the process. If you choose to reassign pending notifications, then you must specify the number of days to be considered for reassigning the pending approvals.

Default Time Zone For all Users

Commonly ask question - How to set the default Time Zone For all Users in Oracle Cloud Applications. 

Login to the application using Super user, normally a user with all admin rights.

- Navigate to setup and maintenance.
- At the left hand corner bottom select “ search Tasks .
- In the search filed enter “set user general preferences “ as mentioned below .
- Click on the task.
- Change the time zone to desired region and hit save .
- Once saved , Logout and login and the time zone will be set as desired time zone for all users.

Use can still change his own preferences which will override the system setting for individual employee.

Future dated Hire User account creation

User account creation and Security future dated hire not have a user account.


The user creation request sits in 'User Role Provisioning' queue till the future date occurs, at which point it will be submitted to OIM by the 'Send Pending LDAP Requests' ESS job.

If you want future dated hires to have user accounts prior to their hire date, then you should add them as Pending Workers.

Employee Hires with Future date:
Hire an Employee with Hire Date = 12/31/2020
Person gets created in the Database as soon as all the approvals are complete with a Start date of 12/31/2020.
Employment Records also get created with a Start Date of 12/31.
User (account) will get created on 12/31.

[PENDING WORKER CASE]
Add a Pending Worker with Proposed Start Date = 12/31
Person gets created in the Database as soon as all the approvals complete with a start Date of 8/22.
User (account) will get created on 8/22.
When the Pending worker is converted to Employee, Employee Work Relationship will get created with a Start Date of 9/2

Note: Year assume to be same foe all dates in the example

Payroll Tracing for debugging and error correction

What is Logging in payroll?

In Payroll it is very normal that you come across the issue and the resolution varies based on type of issues such as Data, Configuration or technical reason. However, figuring the root cause of the problem is covered underneath how you troubleshoot the issue. Here, we are going to discuss the how you can enable logging, running trace and turning off logging in Oracle Fusion Global Payroll, for PeopleSoft folks this exactly means “How to enable trace on the Payroll program and review the trace file”. The logging process uses a series of pay action parameter settings to debug different issues with certain payroll processes, such as Payroll run, Quick Pay, and Costing. The parameter values are set by a user in the application. The payroll process affected will be run to capture the debugging information in a log file. The logging action should be turned off after the process completes and the user will provide the process id to Oracle Support to retrieve the log file and begin to troubleshoot the reported issue.

Details of Turn On, Run and Turn Off the tracing or logging.

Setup a Oracle Fusion Global Payroll configuration group. Once you sign in to the Oracle Fusion Global Payroll application using an account that has the Manage Payroll Process Configuration privilege. Typically the account that have access are Payroll Manager, Human Capital Management Application Administrator, and Payroll Administrator.

Navigate Setup and Maintenance, In the Overview screen that appears, click the All Tasks tab. In the Search field, select Task Lists and Tasks. In the Name field, enter Manage Payroll Process Configuration.

Click Search. In the Search Results panel, click the Go to Task icon for Manage Payroll Process Configuration.

In the Manage Payroll Process Configuration screen, click the Group Overrides tab and then Configuration Groups panel, click the Create icon to display the Create Configuration Group dialog.

In the Name field, enter a name of your own choosing for the new configuration group.

Click Save and Close to return to the Group Overrides tab of the Manage Payroll Process Configuration screen.

In the Configuration Groups panel, select the configuration group you just created.

In the Configuration Group Details: panel, select the "Logging Category Detailed information that is used for investigating problems. Default: no logging" parameter and click the Edit icon to display the Edit Parameters dialog box.

In the Override Value field, enter the parameter values as a continuous string of characters, in any order. Do not use spaces or other characters as delimiters between parameter values

Note: For processes that do not provide a Configuration Group parameter, the logging will need to be set on the Default Group (such as QuickPay).  It is therefore imperative that the parameter be removed immediately after retrieving the log.

 The parameter that you can use for logging in Oracle Fusion Global Payroll

B-Balance maintenance information: Provides output information that show the creation and maintenance of balances used during Oracle Fusion Global Payroll processing.

C-Cache structures information: Provides output information that shows details of the Oracle Fusion global Payroll cache structures and changes to the entries within the structures.

E-Element entry information: Provides output information that shows the state of the element entries in the process memory after the entries are retrieved from the database.  The information is provided whenever data for an entry is changed during processing.

F-Formula information: Provides output information that shows details of formula execution, including formula contexts, input, and output.

G-General logging information: Provides general information, rather than a specific information type.  This parameter does not provide sorted output.  In general, it is recommended that you choose parameters that provide specific types of information.

I-Balance output information: Provides output information that shows details of values written to the database from balance buffers.

L-Balance fetching information: Provides output information that shows the balances retrieved from the database and whether or not the process will use those balances.  (If balances such as Year to Date totals have expired because the year has changed, the process resets them and uses the new balance.)

M-Entry or exit routing information: Provides output information that shows when any function is entered or exited, using messages such as the following:

In: pyippee Out: pyippee - The information is indented to show the call level, and can be used to trace the path taken through the code at the function call level.  This parameter is typically used when trying to diagnose a problem such as a core dump.

P-Performance information: Provides output information that shows the number of times certain operations take place at the assignment and run levels, and why those operations took place.  For example, this parameter provides information about the balance buffer array write operations.

Q-Cache query information: Provides output information that shows the queries being performed on the Oracle Fusion Global Payroll cache structures.

R-Run results information: Provides output information that shows details of run results and run result values just as they are about to be written to the database from the Run Results buffer or the Values buffer, to allow verification that buffer contents were correct.

S-Cache ending status information: Provides output information that shows the state of the Oracle Fusion Global Payroll cache before the process exits, whether that process ends with success or an error.

V-Generate Vertex logging, including data file version and location and geocode processing information.

T/Z-PL/SQL detail and PL/SQL output: To obtain detailed information about the PL/SQL calls made by the Oracle Fusion Global Payroll application use the combination of the T parameter and the Z parameter.  This combination is typically used to obtain information about Oracle Fusion Global Payroll processes that use a large amount of PL/SQL code, such as prepayments and Archive.  The output from using these parameters is buffered while the process is running and is placed at the end of the log file after processing is complete.

Each Oracle Fusion Global Payroll process instance has its own log file, located under the log sub-directory for the particular Process Id. Click Save and Close. Click Save.

Sign in to the Oracle Fusion Global Payroll application using the account that was previously used for running the job in which the problem occurred.

From the Payroll section of the Navigator menu, choose Payroll Calculations.

In the Payroll Flows section of the Tasks panel, click Submit a Process or Report.

From the Legislative Data Group drop-down list in the Submit a Process or Report: Select Flow Pattern screen, select the appropriate value for the job you are about to run.

In the Process or Report table, select the Flow Pattern for the job, such as Calculate Payroll.

Click Next to display the Submit a Process or Report: Enter Parameters screen.

In the Parameter Details panel, click the Search icon to the right of the Process Configuration Group field to display the Search and Select dialog.

Click Search to display a list of available Process Configuration Group values.

Select the Process Configuration Group value that has the logging parameter values you want to use.

Enter any other appropriate parameters for the job, and complete the process of submitting the job as it would usually be done.

Make a note of the ProcessId value for each process you execute.

You may find the ProcessId value useful when you are ready to view the logged results.

What should be done when the process completes?

You will need to capture the log for the process id from within the application to provide to Oracle Support:

From the Payroll section of the Navigator menu, choose Payroll Calculations

In the Search panel of the Overview tab, specify the appropriate information about the processes for which you want to view logs, and then click Search.

In the Search Results panel, click the Payroll Process Flow Name value of the process for which you want to view log entries.

Click the Payroll Flow: FlowInstanceName tab.

Click the Processes and Reports tab.

Make a note of the value that appears after the word Process. For example, if the page shows Process 10483, record the value 10483. This is the process number of the Oracle Enterprise Scheduler job. Click the link for the process number to display the ESS Output: Process Number tab. If no details appear, click the Refresh icon.

Select the appropriate Search Results listing.

Scroll down to the Log section of the detailed information about the selected process.

 Click the LogFileName link in the Attachment field to display the log file.

Upload the log file to the Service Request and provide the process id

Note: After you finish troubleshooting, you must disable the logging functionality for Oracle Fusion Cloud Global Payroll processes that are submitted using configuration group.

Basics of Fusion Cloud - FSM - Functional Setup Manager

What if you get guided implementation method? Well, Fusion Functional Setup Manager (FSM) is a one- stop shop for all implementation activities from planning to Deployment and hand over to the client. FSM is a module within Fusion, which manages all setups and all the various branches of products houses. It helps implementation consultant, client, new to fusion folks also Fusion FSM allow implementation by others than the IT department or consultancies. FSM includes various checklists and allows a project manager to monitor the actual setup tasks as identified by Fusion product for implementation of the desired module. FSM help users to easily migrate configurations from one instance to another which includes T2P and P2T.

FSM is the feature for rapid and standard setup implementation. The Key features of the FSM include:

• Generates the customizable list of setup tasks based on selected offerings, options, and features.
• Identifies pre-requisites, dependencies, and required setups.
• Launches individual setup pages.
• Tracks progress with assignments and task statuses.
• Moves data between environments.
• Supports initial installation as well as ongoing maintenance

Setup of Oracle Fusion Payroll

Summary of Setup of Oracle Payroll

Oracle Fusion payroll is rule based solution, which allows your organization’s unique payroll management requirements demand the ability to configure a payroll solution without losing the benefits of a standard, supported, easily upgraded package. You lose certain report extension or modification but core remain due to MSD.

Yes, the Payroll do provides a unique, data-driven approach that enables you to define and manage your diverse payroll requirements that reflect your business policies, with optional employees and managers easy to use self-service capabilities delivered in the core solution.

In order to keep the length of the post smaller, in this post let us answer two major questions.  I will follow up with series of payroll related post and its integration with Payroll, Absence Management and Time and Labor.

-          What you need before you start configure payroll? 

-          How to setup Oracle Fusion Payroll?

What you need before you start configure payroll? 

Before you configure payroll, you need to perform following task. The pre requisite task listed can be found in Define Common Applications Configuration for Human Capital Management

·         Configure Offering

·         Define Geographies

·         Define Enterprise Structures for HCM

·         Define Features by Country or Territory

Oracle Fusion Cloud Absence Management Setup

   The Oracle has delivered the absence management functionality in Oracle Fusion. This write-up throws some light on how to setup the absence Management as delivered in release 12. The setup can be primarily divided in four base steps with multiple configuration items group together in sequence on dependency.  It’s not mandatory to have all of them however you need to gather the data collection requirement in order to determine what configuration items you need.

Step 1: In this step one you need to configure

   1a. Extend lookups: The extended Lookups are lists of values in applications in PeopleSoft term “Translate Values”. You define a list of values as a lookup type consisting of a set of lookup codes with the translated meaning if you want you can set a tag. User is shown with the list of translated meanings as the available values for an object. It is mean which assures valid values are accepted in the system from the user interface. The kinds of lookup are available in Fusion cloud standard, common, and set enabled.

  1b. Value sets: 1c. Flexfields: Value set and flexfield works together. Flexfield allows you extended business object without adding altering the data model or performing any database programming. A flexfield is an extensible set of placeholder fields associated with business objects and placed on the application pages. The closest you can compare this with “User fields” in PeopleSoft.  Oracle Fusion application have 3 types of field.
I.          Descriptive
II.          Extensible
III.         Key

How to define value set and Flexfield and make them work together? You can search for task “Define Flexfield” in the Setup and Maintenance work area to define and   use the flexfield. You need to perform following task to complete the setup of flexfield.
Manage Descriptive Flexfields: Expand the forms on the application page to accommodate additional information that is important and unique to your business. In Oracle Fusion Payables, you can use a descriptive flexfield to collect custom invoice details on a page displaying invoices.
Manage Extensible Flexfields: Establish one-to-many data relationships and make application data context-sensitive. The flexfields appear only when the contextual data conditions are fulfilled. Thus, extensible flexfields provide more flexibility than the descriptive flexfields.
Manage Key Flexfields: Store information combining several values, such as a number combination. In Oracle Fusion Financials, key flexfields represent objects such as accounting codes and asset categories.
Manage Value Sets: Use a group of values to validate the data entered in the flexfields.

  1d. Fast Formula: fast formulas are very important in absence management. They allow us to   write all logic the absence accrual needs. You can compare this in formula in PeopleSoft Absence management.

Step 2: In this step you configure
-Absence plans to define rules for time accruals or entitlements.  In PeopleSoft it’s achieved with the help of all supporting element like Formula, Arrays, GC etc.
-Create certification requests that you want workers to complete to continue receiving entitlements during absence periods.
-Absence Reasons: Create Absence reasons that you want workers to select while recording absences. In PeopleSoft term it’s exactly have same name “Absence Reason” like Sick may have

Step 3:  The key element of absence management “Absence Type” is configured in this step (In PeopleSoft absence management term its called “Absence Takes”). The most common example of Absence types are Sick or Vacation or PTO-Paid Time Off.


Step 4: Create absence categories, such as personal leave or medical leave, and associate them with the relevant absence types for reporting purposes.