End-to-end configuration implementation task for Oracle Fusion cloud Absence Management.

Below are the details of the end-to-end configuration implementation task for Oracle Fusion cloud Absence Management.

 

Sno	Task Name	Functional/Technical
1	Absence Management Implementation Overview	Functional
2	Responsive User Experience Setup	Functional
3	Absence Lookups, Value Sets, and Flexfields	Functional
4	Formula Creation and Error Handling for Absence Management	Functional
5	Eligibility Profiles for Absence Plans	Functional
6	Rate Definitions for Absence Payments	Functional
7	Elements for Absence Management	Functional
8	Effective Dates in Absence Management	Functional
9	Accrual Absence Plans	Functional
10	Qualification Absence Plans	Functional
11	Compensatory Time	Functional
12	Donation	Functional
13	Absence Types, Reasons, and Categories	Functional
14	Absence Certifications	Functional
15	Absence Processes	Functional
16	Integrated Workbooks for Loading(HDL/HSDL) Absence Data	Technical
17	HCM BI Report for Absence Data	Technical
18	HCM OTBI for Absence Data	Technical
19	HCM Extracts for Absence Data	Technical

 

How many types of Absence Plans in Oracle Fusion Absence Module?

 

Types of Absence Plans

Create the following types of plans using the Absence Plans task in the Absences work area:

• Accrual

• Qualification

• No Entitlement

• Agreement

• Compensatory

• Donation

Accrual

Use this type to create absence plans that enable workers to accrue time for taking paid leave, such as a vacation plan. Configure rules that determine various aspects of leave time, such as:

• Length and type of the accrual term in which workers accrue time

• Maximum time that workers can accrue in a term

• Maximum time that workers can carry forward to the next term

Qualification

Use this type to create an absence plan where workers qualify for the plan and receive payments during the absence period. For example, use qualification plans for defining absence rules related to events, such as long term illness or maternity. Configure rules to determine the payment percentages that apply for specific periods during the absence, for specific workers.

No Entitlement

Create absence plans of this type to track unpaid absences without maintaining an accrual balance or providing leave entitlements, such as periodic accruals. Similar to an accrual plan, you can define the length and type of the plan term and determine when eligible workers can enroll in the plan. You can also use plans of this type in combination with a qualification plan. For example, use a no-entitlement plan if a worker isn't eligible for a standard maternity absence qualification plan.

Agreement

Create absence plans of this type in accordance with statutory rules for use under an agreement. For example, create a shared parental leave agreement for a worker and qualified parental partner to allocate paid or unpaid time off among parenting partners.

Compensatory

Create absence plans of this type to track earned compensatory time that can be used for time off. Compensatory time is offered as compensation for working outside of regular work schedules. Instead of paying overtime, an employer can create a policy to give paid time off.

Donation

Create absence plans of this type to track donated time that a worker receives. Workers can donate their accrual plan balance to a coworker who needs additional time off and is eligible to receive the donated time.

Difference between UPDATE and CORRECT modes in Oracle Fusion Cloud

Difference between 'UPDATE’ and 'CORRECT' modes in the Oracle Fusion Application.

Hi Folks,

We are having two types of modes like Correct and Update modes in Oracle Cloud Fusion Application. If you are new to Oracle Cloud Fusion Application Always chose 'Update' while edit the existing record in Fusion cloud screens and might be confused with 'UPDATE' and 'CORRECT' mode Actions. Let's see this with simple example in one Business Object.

UPDATE Mode is for updating the existing record. We will go for 'UPDATE' Mode when the particular record will have update with effective dates change day, Prior to that, that particular record holds the old value in back end tables as per Business Object.

For this Example, we will take 'Job’ object. Create new Job called 'Consultant ' with effective start date as “01/01/1951”

Let's assume, Job Function data is changed blank to 'Administrative' effective 01/01/2023. We need to update the same data in the application. In this case, We will go for 'Update' mode option effective date from 01/01/2023 and click on the submit button.

After the change, The Job Function changed to the 'Administrative' will showing blank on or after effective 01/01/1951

If you change the effective Start date before 01/01/2023, It will show old values

Let's look at the Table, there will be two version of records for the same Job Object with effective start Date and end date.

FYI: SQL Queries to get the table values as per below

SELECT JOB_ID,

to_char(EFFECTIVE_START_DATE,'YYYY/MM/DD') EFFECTIVE_START_DATE,

to_char(EFFECTIVE_END_DATE,'YYYY/MM/DD') EFFECTIVE_END_DATE,

JOB_FUNCTION_CODE

FROM PER_JOBS_F WHERE JOB_CODE='SN_CON'

CORRECT mode is something it was wrong data have entered the data in the application and need to be corrected in the system. Let's say, Job name 'Senior Payroll Consultant', it was wrong mentioned 'Senior Consultant' in the system effective 01/01/1951. Now you need to correct that to 'Senior Payroll Consultant'.

Note : Correct mode option Will not allow you to Correct the record effective after the creation date. For example, with above record created on 01/01/1951, you must chose effective change date as same or before the 01/01/1951

Incorrect Location 'Senior Consultant' created effective 01/01/1951

click Edit button-> Correct mode-> Effective ‘01/01/1951' System must throw the warning.

Change the effective date to 01/01/1951 with Job name as 'Senior Payroll Consultant' and click on the Save button.

Also, Let's look at the data using SQL table, there will no date effective row will be created for the 'Correct' mode.

Note : Object version column tells that this 'Location' record was modified from the first version

Hope this article will clarify the difference between 'UPDATE' and 'CORRECT' modes options in the Oracle Applications..