Login
Register

Home

Trainings

Fusion Blog

EBS Blog

Authors

CONTACT US

Fusion PayRoll
  • Register

Oracle Gold Partners, our very popular training packages, training schedule is listed here
Designed by Five Star Rated Oracle Press Authors & Oracle ACE's.

webinar new

Search Courses

This tutorial deals with Fusion Payroll, and how it functions. In this part, we will discuss about the following topics:

  • Formulas

  • User Defined Tables

Formulas

Formulas are generic expressions of calculations or comparisons that you want to repeat within different input variables. It is a means of defining any business logic for performing functions that may not be provided by the Human Capital Management (HCM) app itself. Formulas are extensively used across HCM.

Formulas are used in the following components of HCM:

  • Payroll - Calculation, input value validations, skip rules for elements, etc.

  • Benefits - Date calculations, eligibility and participation evaluation, etc.

  • Object Groups - Payroll Relationship Groups

  • Compensation - Person selection, currency selection for workforce compensation plans, etc.

  • HCM Extracts

The Formula Type is provided by Global Payroll. Any formula requires specific inputs and outputs (to be generated) for the functioning of the formula.

Formulas can be written either by using the Expression Editor (by using the Fast Formula UI) or through Formula Text (writing the pseudocode). The Expression Editor only has a limited number of Formula Types available, mainly the Payroll Relation Groups. For the other Formula Types, their formula’s pseudocode is written through formula text.

Once a formula is written, it has to be compiled first. Upon successful compilation, the formula can be attached to a business application so that it gets executed when running that particular application.

The task associated with it is Manage Fast Formulas.

Database Items

Database Items are a mechanism used to retrieve a value from the database through a code. These codes are used extensively in formulas to get values required for the output. They are Read-Only variables that are used in formulas.

There are two types of Database Items:

  • Static - They are seeded and predefined, like Birth Date, Payroll Relationship Number, etc. (e.g. PAYROLL_REL_NUMBER)

  • Dynamic - They are created when you create Elements, Input Values, Balances, and Flexfields. In case of flexfields, you need to run the Generate Flexfield Database Items process. In the case of Elements or Input Values, the name yu give to the element or input value gets converted to a dynamic database item; spaces are converted into underscores (e.g. MONTHLY_EARNINGS)

 

Most of the formulas are written through Formula Text. Taking the example of Element Input Validation, the following table explains the field, purpose, and the time of execution of the formula:

Formula Text for Element Input Validation

The following table depicts the formula usage and the input variables required for the formula for Element Input Validation:

Input variables for formula usage

The following table depicts the formula usage and the return variables that the formula produces as output for Element Input Validation:

Return variables

In the following example formula, entry_value is the input variable. The formula is used to identify valid entries in the database based on the entry_value being greater than 2000:

An example formula

Compilation and Execution Errors

Since formulas essentially consist of code, there is the possibility of them throwing up compilation or execution errors.

Compilation Errors

Upon compilation of the formula, the possible compilation errors are:

  • Syntax Error

  • Misuse of the ASSIGNMENT statement

  • Misuse of the DEFAULT statement

Execution Errors

If the formula is compiled successfully, it may have some other type of mistakes that result in execution errors while running the formula:

  • Uninitialised Variable

  • Divide by Zero

  • No Data Found

User Defined Tables

User Defined Tables are a feature by which users can create their own table structure to store values. They are used when a table structure is required for values depending on the user’s needs.

There are four components to a user-defined table: basic details (datatype, unit of measure, etc.), columns (column headings), rows (number of rows in the table), and values (values of the rows).

There are two types of row values: Matched Row Values, where you define a specific value to be matched for each row and column; and Range of Row Values, where you specify a range of values that the rows and columns take.

For example, there might be a hike or bonus applicable for employees depending on their years of service. User defined tables can be used to assign a value for the hike or bonus applicable to a certain range of values for years of service. For instance, a hike of 20% could be applied to the years of service ranging from 3-5.

The values can be validated through User Table Validation Formula.

The task associated with it is Manage User-Defined Tables.

The User Defined Tables UI

 

After performing the various functions related to Payroll, you can visit the Payroll Calculation Work Area to get an overview of all the elements in your Payroll.

 

 


Krishnaa Lakshmanan

Add comment


Security code
Refresh

About the Author

Krishnaa Lakshmanan

Search Trainings

Fully verifiable testimonials

Apps2Fusion - Event List

<<  Mar 2024  >>
 Mon  Tue  Wed  Thu  Fri  Sat  Sun 
      1  2  3
  4  5  6  7  8  910
11121314151617
18192021222324
25262728293031

Enquire For Training

Fusion Training Packages

Get Email Updates


Powered by Google FeedBurner