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.