Objective:

In order to have a successful ERP Implementation all the three perspectives (Operational, Managerial and Financial) has to be addressed. Operational perspective is addressed during the initial requirement gathering phases and while addressing the reporting needs – managerial perspective is covered.  Most often financial requirements (SCM related) are never fully addressed as it always falls under the Financial Consultant’s radar.

I’m writing this article as guidance for consultants with non accounting background to have an overview of the underlying accounting entries. 

Note: This is not an exhaustive list of entries within SCM 

Content:

Assumptions:

SLA is defined to default

Projects is not involved 

Objective :

Most often you come across an requirement of  search panel in OIM , for user search which is already available in OIM .   Let’s say we have a requirement of searching a particular employee or listing all the employees and clicking on the employee id it should allow to edit the employee details .We will implement the same thing using ADF as follows .In the previous article we have seen how to implement UI page in ADF. 

1) Go to adfc-config.xml under Web Content>WEB_INF folder



2) Drag and drop View  from the components Palette




We will create one more page View2 .We will change the name of View1 to Search and View2 to as Edit .



Also the warning is shown that the page is not created only the icon is available here .We need to double click to create the page before that we will complete the navigation . we need navigation from Search page to Edit page whenever there is a action called edit . Also we will have navigation from Edit page to Search page whenever there is action called Search . THis will complete the navigation as shown in below screenshot.



3)Double  Click on the Search icon Search page will be created .






4) From the Data Controls if you expand VO you will see Named Criteria . In Named Criteria you will see All Queryable Attributes , drag and drop it on the Search page



5) It will ask what you want to create . We will select ADF Quick Query with Table



6) Now it will ask what all columns you want to display in the table . We will also check the Enable String , Enable Filtering options and select the Single Row selection . We will keep all the columns to be displayed and click on OK .



Once you click on OK the search panel and results table  will be added





7) You can see that all the fields are as Output Text , but we want when the user clicks on Employee ID he should be  navigated to Edit page



So we will replace Output Text with a link . You can see in the right panel  that each column has Output Text which we don’t want




So we will search for link in Search panel .




Select the ADF link , drag it and drop it on the column in Search panel  as shown in below screenshot .




8) Copy the value of the Output Text and paste it in the command link text so that it displays Employee ID






9) Delete the Output Text . Now we have only link




We did it only for the first row it automatically copies to all the rows , so no need to repeat . This feature is know as auto-stamping .


10) Select adf command link . In properties window  there is an Action drop down list , select the action edit  so that it goes to edit page .





We are done with first page now .


11) Double click on Edit page and click on OK







12) Right click on edit page and Select ADF Form




13) Uncheck Include Navigation Controls button and click on OK



14) Also we need a button that will take us back to the Search page . So search for a button in search panel



15) Drag and drop the adf button the page



Change the text of the command button to Back and set the Action to search page .




16) Save and go to adf-config.xml file . Right click and select Run option .







17) After it’s Successfully deployed the Search page will be displayed on the browser





18) In the Search panel it will ask you you want to search records based on which field .




Also you can perform the blank search .All the employee details will be listed  on  blank search based on Employee id.





19) You can sort , filter the records also . For example if you want to know employees whose first name is starting with D, then enter the character D in the firstName column, all employees with First name starting with D will be listed .




20) To edit a particular record click on the EmployeeId listed . For example click on 115 ( Employee Id)




It will take you to the Edit page .You can do the changes required and click on Submit . It gets saved to the database .If you want to come back the search page click on Back button





So it’s simple to develop the application using ADF  wherein not much coding is required everything is UI based .





FAQ’s :

Q:While filtering in UI does it makes a call to the server  or there is one time server call and it does everything on the UI .

Answer: It makes one time call to server & everything is done within UI itself , there is no frequent calls to the server .

This tutorial is a continuation of Fusion Payroll and how it functions.
The topics covered in this tutorial are:

• Payroll Statutory Units
  
  
• Legal Employers
  
  
• Tax Reporting Units
  
  
• Creating a Legal Entity
  
  
• Selecting the Scope of the Legislative Data Groups
  
  
• Defining Legal Reporting Units
  
  
• Creating Business Units
  
  

While we must have been used to creating DRAG and DROP reports using OTBI we might have missed the option of
‘Create Direct Database Query’ . In this article let’s try to explore the same.

Navigation:
Login to Fusion Applications -> Click on Reports and Analytics -> Click on BI Catalog ( Book Icon) and you reach on this page
Click on Create Direct Database Query

Step 2 :
Provide following details :


select papf.person_number as PersonNumber
from per_all_people_f papf
where rownum< 10
order by papf.person_number desc




Click on Results Tab as shown











Click on ‘Archive’ option as shown.



Click Save. And save the file in a specific location. ( Desktop in this example).

   

Save in Desktop

Login to Target Instance and Navigate to
Navigator->Reports and Analytics -> BI Catalog -> Shared Folders-> Custom -> <Your Specific Folder where you want to keep this analysis, for this example
Screenshot Before Unarchiving the CATALOG File


Then Click on Unarchive Option as shown.

A Popup window appears as shown below


Locate your file and Click Ok

You can import the file by clicking on DirectDatabaseOTBIQuery

Objective:

In this article we will learn about the Introduction of Middleware and different types of Web services.


Middleware:

It is a connector or a common bridge.

Middleware was first introduced in RPC to Web services.

RPC--------------->Web services

Different types of web services:

1. RPC
   
   
2. CORBA
   
   
3. COM/DCOM
   
   
4. RMI
   
   
5. SOA
   
   
6. AJAX
   
   

1. RPC (Remote Procedure Call):
   
   

• Different operating system
  
  
• Different programming language
  
  

• Language Independency
  
  
• Platform Independency
  
  

• Language Independency
  
  
• VC++, VB, VB script
  
  

• Platform Independency
  
  

CoExistence is the new Existence

Its coexistence or no existence - Bertrand Russell

Earlier this year Oracle’s C Class, Larry Ellison and Mark Hurd shared their Vision, Strategy and released 10-Point Plan to be #1 In the Cloud.

Oracle’s Strategic focus-shift in product building from EBS to Fusion Applications on cloud with plans to stall SOME of the acquired and EBS products, who knew Bertrand Russell quote’s relevance would rock in Fusion world too.

A Great number of Oracle’s customer is still on core Applications like EBS, PeopleSoft, Siebel or JD Edwards.

Customers who made huge IT investments and I-AM-HAPPY with my current system are less likely to replace existing systems, yet want to adopt new Fusion features and enhancements.

Oracle offers the approach of CoExistence to such business scenarios, wherein Existing ERP & Fusion solution co-exists to deliver Business Value and customers can continue to leverage the returns from existing investments.
3 ways to Fusion Adoption –

    1, Module Co-Existence – Existing customer implements Single Fusion Application module to extend the functionality in the current applications.

    2, Pillar Co-Existence: Customers choose to replace a suite of applications in a functional area with Oracle Fusion Application.

    3. Applications Unlimited: Customers who will continue on Oracle’s current applications.
2 ways to CoExistence and Integration -

1. Packaged /Out of the Box CoExistence Scenarios

2. Enabled Coexistence and Integrations

Inbound Integrations to Oracle Fusion HCM

1. HCM Data Loader
   
   
2. HCM File-Based Loader(High Volume CSV,XML,DAT Data Load)
   
   
3. HCM Spreadsheet Data Loader(Low Volume Spreadsheet data Load)
   
   
4. Payroll Batch Loader
   
   

Outbound Integrations from Oracle Fusion HCM

Objective: 

In the previous article we seen the Introduction of Middleware and different types of Web services. In this article we will learn about the Oracle Fusion Middleware architecture.

Oracle FMW Architecture:

It mostly comprises of Fusion Application and Fusion Middleware

Fusion Middleware:
It comprises of oracle application server. Middleware is a family of middleware products covering all the areas such as: BI(Business Inclusion), IDM(Identity Management), Content, SOA, BPEL.


Fusion Application:
Fusion application is build on top of Fusion middleware technology.
It uses Fusion architecture as the Blueprint.
Modules of Fusion Applications are:



While installing we can face some issues in any of these applications so we should install HCM (Human Capital Management) if we want to avoid those issues.


Simplified Architecture of Fusion Middleware:


This is a 3-tier architecture:

• Database tier:
  
  

• Oracle Weblogic Server
  
  

• Web tier
  
  

Before we start to understand How to create an Absence Plan first try to understand what an Absence Plan is and why is it required.

In real life Absence Plan holds a different meaning than that of the one meant in Fusion Applications.

In real life Absence Plan for an individual (or for that matter for a Working individual) relates more to a question which is generally asked by his Manager

What are your Absence Plans?

and he would generally respond stating I will be on leave on so and so dates.

But in context with Fusion Applications an Absence Plan (I feel the naming convention isn’t correct it should have been called Accrual Plan but that again is incorrect as Absence Plans are even those which are of qualification and No-Entitlement Type, details about the same in Absence Plan Types Section) could be imagined as a Bucket.

Yes, I mean a Bucket as we know.

Let’s for time being say an Absence Plan is an Absence Bucket and I call it as a Bucket as it is supposed to hold:

1. Leave / Absence Balance

Anything and everything around the Entire Absence Plan surrounds around this single piece of information usually called ‘Absence Balance’

Different Items related with an Absence Plan and their association with Absence Balance follows:

Absence Plan

A name given to a set of rules / guidelines which define how the absence balance will be assigned and maintained

Legislation

Geography / Country where this Absence Balance is Maintained. For Example, if we are doing Absence Plan setup for India Legislation would be India, if we are doing for USA it would be United States and so on....

Plan Type

An attribute which defines how the Absence Balance would be calculated / paid.

For example:

                       If Absence / Leave Balance is paid to employees as a result of an event such as childbirth, illness or injury it is called Qualification Plan Type Absence Plan

                   Typical Example Being Hospitalization Leave.

                   If Absence / Leave Balance is paid to employees as a result of accumulation / accrual it is called Accrual Plan Type Absence Plan

                   Leaves like Annual Leave, Vacation Leave fall into this category

                   If Absence / Leave Balance is paid without having any track, then we referred to them as No-Entitlement Plan Type Absence Plan

                   Marriage Leave, Compassionate Leave. fall into this category

Plan Term

This is basically the entire time period for which the absence balance has the validity.

For Example

                   Plan Term: Calendar Year

                   Start Day: 01

                   Start Month: 1

                       Means the Absence Plan will start on 1st day of 1st month (i.e. 1st January) and run till the end of calendar year i.e. 31-Dec

                   Plan Term: Calendar Year

                   Start Day:  01

                   Start Month:  2

                   Means the Absence Plan will start on 1st day of 2nd month (i.e. 1st February) and run till the end of calendar year i.e. 31-Dec

                   Plan Term:  Calendar Year

                   Start Day:  05

                   Start Month:  10

                   Means the absence Plan will start on 5th day of 10th month (i.e. 5th October) and run till the end of calendar year i.e. 31-Dec   

Absence Plan UOM

Unit of Measure which states in which unit (either of Days / Calendar Days / Hours) will this Absence Balance will get measured

Accrual Method

Method of accruing Absence / Leave Balance.

It is of two types:

1. Frontloaded

The Entire Absence Balance is allocated at the beginning of the plan term

2. Incremental

The Absence Balance are accrued at regular intervals

Accrual Frequency

Frequency at which accrual happens. It is of two types Person Primary Frequency and Repeating Period.

If person gets his absence / leave balance at the start of payroll period, then the Accrual Frequency is of Person Primary Frequency Type

            For Example:

            Person Primary Frequency: Weekly

            Means he gets paid every week (Employee has a Weekly Payroll Assigned / Attached to him) and same is true for his absence balance too i.e. absence balance is

            received every week (in synchronization with his person primary payroll payment frequency).        

            Person Primary Frequency: Bi-Weekly

            Means he gets paid once in row weeks (Employee has a Bi-Weekly Payroll Assigned / Attached to him) and same is true for his absence balance too i.e. absence

            balance is received once in two weeks (in synchronization with his person primary payroll payment frequency).

            Person Primary Frequency: Monthly

            Means he gets paid once a month (Employee has monthly payroll assigned / attached to him) and same is true for his absence balance too i.e. absence balance is

            received once a month (in synchronization with his person primary payroll payment frequency).

            Person Primary Frequency: Quarterly

            Means he gets paid once in quarter (Employee has a Quarterly Payroll Assigned / Attached to him) and same is true for his absence balance too i.e. absence balance

            is received once each quarter (in synchronization with his person primary payroll payment frequency).

If person gets his absence / leave balance at the start of each instance of a Specific Repeating Time Period, then Accrual Frequency is of Repeating Time Period

           For Example:

           Repeating Time Period: Every Quarter of a Calendar year

           Means he will accrue this leave once every 3 months in the Calendar Year.

           Repeating Time Period: Bi Monthly

           Means he will accrue this leave 2 times in a month.  

           Repeating Time Period: Every Quarter of a Calendar year

           Means he will accrue this leave once every 3 months in the Calendar Year.

           Repeating Time Period: Monthly

           Means he will accrue this leave once a month.  

Ceiling

This means the maximum Accrual / Leave Balance an employee can accrue / store within a particular accrual term

         For Example:

        If for a particular Absence Plan the ceiling value is 10

        It means that the employee can accrue at max 10 leaves per year. If his balance becomes more than 10 then the same will be forfeited.

        If for a particular Absence Plan the ceiling value is 20

        It means that the employee can accrue at max 20 leaves per year. If his balance becomes more than 10 then the same will be forfeited.

Carryover

This means the Absence / Leave Balance an employee can carry forward (take along with him) to next accrual term

         For Example:

        If for a particular Absence Plan has carryover as 50

        It means that the employee can carry forward 50 leaves per year. This carry forward value would keep accumulating until ceiling value is reached

        So if ceiling is 100 and employee has already carried forward 50 leaves from first year and again 50 from next year then he cannot carry forward leaves for 3rd year.  

        If for a particular Absence Plan the carryover as 60

        It means that the employee can carry forward 60 leaves per year. This carry forward value would keep accumulating until ceiling value is reached

        So if ceiling is 100 and employee has already carried forward 50 leaves from first year and again 50 from next year then he cannot carry forward leaves for 3rd year

Vesting Period

This is the Time Period during which Employees can accrue leave but cannot apply leave

For example, if a Plan starts on 1st January and has a vesting period of 1 month then the first leave which an employee can take would be a date after 1st February (1st January + 1 month). He would anyways be allowed to accrue during the entire January Month

Absence Payment Rate Rule

Method to calculate payment during an Absence Period. (a period when employee is absent from work, but still needs to be paid)

For Example, if a Female Employee is on Maternity Leave for 6 months then at what rate should she be paid.

Final Disbursement Rate Rule

Method to calculate payment of accruals when plan participation ends (An Employee became a Contractor from Regular Employee so his eligibility for Annual Leave comes to an end, but he has already had a positive balance of say 10. Now if the payroll is integrated with absence then employee needs to be paid for this accrued balance. This rate talks about the same Disbursement Rate Rule).

Discretionary Disbursement Rate Rule

Method to calculate payment when paying out part of accrual balance (An Employee resigns a company and he has a notice period of 30 days, he has served 25 days of notice period and he has an accrual balance of 10 days. Due to some emergency he has to go to his hometown and he seeks immediate relieving. In this case the company may decide to deduct his 5 days from Accrual balance and pay for the rest 5 at a discretionary rate).

Liability Rate Rule

Method to calculate cost of accrual balance to determine employer liability (An Employee resigns a company and he has a notice period of 30 days, he has served 25 days of notice period and he has an accrual balance of 10 days. Due to some emergency he has to go to his hometown and he seeks immediate relieving. In this case the company may decide to deduct his 5 days from Accrual balance and pay for the rest 5 at a discretionary rate and the rest 5 days will be paid at the Liability Rate).

Now since we are aware of some of the most commonly used terms for an absence plans we should try to create one absence plan. Requirement is to create an Absence Plan with Absence Plan type as Accrual and Accrual Method as Incremental

We have the following requirement:

Absence Plan Type: Accrual

Accrual Method: Incremental

Accrual UOM: Days

Accrual Values: If Length of Service is < 3 years then Accrue 10 days, have a ceiling of 100 days and carryover of 50 days.

                                                                If Length of Service is < 3 years and Length of Service >= 5 years then Accrue 12 days, ceiling of 120 days and carryover of 60 days

                                                                If Length of Service is > 5 then Accrue 15 days, have a ceiling of 150 days and carryover of 75 days                                    

Vesting Period: If Legal Employer is Vision Corporation Then Vesting Period is 90 Calendar Days Else Vesting Period is 30 Calendar Days

Absence Payment Rate Rule: Provide a Sickness Rate If the Employee is taking a Leave of Type Sick and Flu else use Hourly Rate

Final Disbursement Rate Rule: If Employee is of Hourly Salaried type use Hourly rate, if he is Regular Employee provide Annual Salary Rate

Discretionary Disbursement Rate Rule: If Employee is of Hourly Salaried type use Hourly rate, if he is Regular Employee provide Annual Salary Rate

Liability Rate Rule: If Employee is of Hourly Salaried type use Hourly rate, if he is Regular Employee provide Annual Salary Rate

We would be using Fast Formula (reasons supporting the same provided alongside) for the following attributes:

**Accrual Values: This can be achieved using an Accrual Matrix but we would like provide maximum flexibility and hence Fast Formula

Vesting Period: This requirement can only be achieved using Fast Formula

**Absence Payment Rate Rule: This requirement could have been met using the ‘Rate Definition’ option but for flexibility we have used Fast Formula  

**Final Disbursement Rate Rule: This requirement could have been met using the ‘Rate Definition’ option but for flexibility we have used Fast Formula

**Discretionary Disbursement Rate Rule: This requirement could have been met using the ‘Rate Definition’ option but for flexibility we have used Fast Formula

**Liability Rate Rule:  This requirement could have been met using the ‘Rate Definition’ option but for flexibility we have used Fast Formula

**Note: By Allowing Flexibility we mean in case there are additional complex logic in future then we can add the Fast Formula Code in the existing FF defined.

While some might debate that the entire absence plan could well have been setup using standard setups / configurations (and I do agree to that) but the below are specific reasons for using Fast Formula here:

1. Allows Flexibility of Adding Custom Logic (If required by customer at a Future Date)

Fast Formulas (Details in a separate article) generally allows us to add conditional logics (IF-ELSE constructs) and provide a way to customize the seeded solution.

For Example

Say currently we want to have a condition that if

Employee Category is Hourly then use RateCode as ‘Hourly Rate’

Employee Category is Salaried then use RateCode as ‘Salaried’

But after few days customer has changed the requirement and now they even want to ensure that any Salaried Employee who has been on leave for most of time during the year would rather be paid in terms of hours worked (typical example being someone on Leave Without Pay)

IF

    Employee Category is Hourly then use RateCode as ‘Hourly Rate’

Else if

                      Employee Category is Salaried and Employee Payroll Status is Currently on Leave without Pay then ‘Hourly Rate’ ------ new requirement

Else

                      Employee Category is Salaried and Employee Payroll Status is Active Payroll Eligible then ‘Salaried’

end if

Now in order to accommodate the new requirement you would need to create a completely new Absence Plan with new setups and that would have many implications but if we use Fast Formula this can be achieved by just adding a piece of if-else construct.

2. Absence Plan Migration becomes a little easier

In all implementation projects setups needs to be once done in a Development POD (in EBS we referred them as INSTANCE) , and then the same is migrate to SIT, UAT , PRE-PROD and then PROD.

IF we use Fast Formula approach migration becomes simpler.

You need to create multiple custom fast formula in the system (your POD) in the legislation where you want to create the absence plan.

There are 4 types of Fast Formula used in this example namely

1. Global Absence Plan Duration   

2. Global Absence Accrual

3. Global Absence Vesting Period

4. Global Absence Plan Use Rate

There are 5 Fast Formula used in this example which are:

1. AH Global Absence Plan Duration Formula

2. AH Global Absence Accrual Formula

3. AH Global Absence Vesting Period Formula

4. AH Global Absence Plan Use Rate Selection Formula 1

5. AH Global Absence Plan Use Rate Formula2

/************************************************************************************

FORMULA NAME: AH Global Absence Plan Duration Formula

FORMULA TYPE: Global Absence Plan Duration

DESCRIPTION: This sample formula returns the duration based on effective date falls on Sunday.

Change History:

Name                 Date        Comments

--------------------------------------------------------------------------------------------

XXXXXXX             DD-MM-YYYY   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

--------------------------------------------------------------------------------------------

************************************************************************************/

/*================ FORMULA SECTION BEGIN =======================*/

l_date=GET_CONTEXT (EFFECTIVE_DATE,'4712/12/31 00:00:00' (date))

l_weekday=to_char(l_date,'DAY')

If (l_weekday= '7')

then (

duration=0

)

else (

duration=8.5

)

/*================ FORMULA SECTION END =======================*/

return duration

/*****************************************************************

FORMULA NAME: AH Global Absence Accrual Formula

FORMULA TYPE: Global Absence Accrual

DESCRIPTION: This sample formula applies the Accrual, Ceiling, CarryOver, Proration Factor, Vesting Units, Vesting UOM, CarryOver Proration and Ceiling Proration

based on Length of Service and Accrual Plan the person enrolled into.

Change History:

Name                 Date        Comments

------------------------------------------------------------------------------------------------------------

XXXXXXX             DD-MM-YYYY   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

------------------------------------------------------------------------------------------------------------

*****************************************************************/

/*=========== DATABASE ITEM DEFAULTS BEGIN =====================*/

DEFAULT for PER_ASG_REL_ORIGINAL_DATE_OF_HIRE is '4712/12/31 00:00:00' (date)

DEFAULT for ANC_ABS_PLN_NAME is 'A'

DEFAULT for ANC_ABS_PLN_PLAN_UOM is 'H'

/*=========== DATABASE ITEM DEFAULTS ENDS======================*/

/*================ FORMULA SECTION BEGIN =======================*/

l_no_of_days=DAYS_BETWEEN(GET_CONTEXT(EFFECTIVE_DATE,'4712/12/31 00:00:00' (date)),PER_ASG_REL_ORIGINAL_DATE_OF_HIRE)

l_length_of_service=(l_no_of_days/365)

/* check if employee enrolled into this plan or not */

if (ANC_ABS_PLN_NAME='BM_US_ABSENCE_ACCRUAL_PLAN')

then(

    if(ANC_ABS_PLN_PLAN_UOM ='H')

    then(

        if(l_length_of_service <3)

        then(

            accrual =10   

            ceiling = 100

            carryover=50

            prorationFactor=0.25

            vestingUnits=40

            vestingUOM='C'

            carryOverProration=0.25

            ceilingProration=0.25

            )

        else if ((l_length_of_service =>3) and (l_length_of_service<5))

        then (

                 accrual =12  

                 ceiling = 120

                 carryover=60

                 prorationFactor=0.25

                 vestingUnits=30

                 vestingUOM='C'

                carryOverProration=0.25

                ceilingProration=0.25

               )

        else if (l_length_of_service =>5)

         then (

                  accrual =15  

                  ceiling = 150

                  carryover=75

                  prorationFactor=0.25

                  vestingUnits=30

                  vestingUOM='C'

                  carryOverProration=0.25

                  ceilingProration=0.25

            ) )

        else if (ANC_ABS_PLN_PLAN_UOM ='D')

        then(

            if (l_length_of_service <3)

               then(

               accrual =round(10/24,3)   

                ceiling = round(100/24,3)

                carryover=round(50/24,3)

                prorationFactor=0.25

               vestingUnits=40

               vestingUOM='C'

               carryOverProration=0.25

               ceilingProration=0.25

            )

        else if ((l_length_of_service =>3) and (l_length_of_service<5))

                    then (

                                                                                                                                accrual =round(12/24,3)  

                 ceiling = round(120/24,3)

                 carryover=round(60/24,3)

                 prorationFactor=0.25

                 vestingUnits=30

                 vestingUOM='C'

                carryOverProration=0.25

                ceilingProration=0.25

            )  

              else if (l_length_of_service =>5)

        then (

            accrual =round(15/24,3)  

                     ceiling =round(150/24,3)

                     carryover=round(75/24,3)

                     prorationFactor=0.25

                     vestingUnits=30

                    vestingUOM='C'

                    carryOverProration=0.25

                    ceilingProration=0.25

                )

           )

        else if (ANC_ABS_PLN_PLAN_UOM ='W')

        then(

            if (l_length_of_service <3)

               then(

                accrual =round(10/120,3)   

                ceiling = round(100/120,3)

                carryover=round(50/120,3)

                 prorationFactor=0.25

                vestingUnits=40

                vestingUOM='C'

                carryOverProration=0.25

                ceilingProration=0.25

            )

        else if ((l_length_of_service =>3) and (l_length_of_service<5))

                    then (

                 accrual =round(12/120,3)  

                 ceiling = round(120/120,3)

                 carryover=round(60/120,3)

                 prorationFactor=0.25

                 vestingUnits=30

                 vestingUOM='C'

                 carryOverProration=0.25

                 ceilingProration=0.25

            )  

              else if (l_length_of_service =>5)

        then (

            accrual =round(15/120,3)  

                  ceiling =round(150/120,3)

                  carryover=round(75/120,3)

                  prorationFactor=0.25

                  vestingUnits=30

                  vestingUOM='C'

                  carryOverProration=0.25

                  ceilingProration=0.25

                )))

    if (ANC_ABS_PLN_NAME='Sickness')

then(

    if(ANC_ABS_PLN_PLAN_UOM ='H')

    then(

        if(l_length_of_service<3)

        then(

            accrual =12   

            ceiling = 120

            carryover=60

            prorationFactor=0.25

            vestingUnits=40

            vestingUOM='C'

            carryOverProration=0.25

            ceilingProration=0.25

            )

        else if ((l_length_of_service =>3) and (l_length_of_service<5))

        then (

                 accrual =13  

                 ceiling = 130

                 carryover=70

                 prorationFactor=0.25

                 vestingUnits=30

                 vestingUOM='C'

                 carryOverProration=0.25

                 ceilingProration=0.25

               )

        else if (l_length_of_service =>5)

         then (

                  accrual =14  

                  ceiling = 160

                  carryover=80

                  prorationFactor=0.25

                  vestingUnits=30

                  vestingUOM='C'

                  carryOverProration=0.25

                  ceilingProration=0.25 ))

        else if (ANC_ABS_PLN_PLAN_UOM ='D')

        then(

            if (l_length_of_service <3)

               then(

                accrual =round(12/24,3)   

                ceiling = round(120/24,3)

                carryover=round(60/24,3)

                prorationFactor=0.25

                vestingUnits=40

                vestingUOM='C'

                carryOverProration=0.25

                ceilingProration=0.25

            )

        else if ((l_length_of_service =>3) and (l_length_of_service<5))

                    then (

             accrual =round(13/24,3)  

                    ceiling = round(130/24,3)

                     carryover=round(70/24,3)

                     prorationFactor=0.25

                     vestingUnits=30

                     vestingUOM='C'

                    carryOverProration=0.25

                    ceilingProration=0.25

            )  

              else if (l_length_of_service =>5)

        then (

                      accrual =round(14/24,3)  

                     ceiling =round(160/24,3)

                     carryover=round(80/24,3)

                     prorationFactor=0.25

                     vestingUnits=30

                     vestingUOM='C'

                       carryOverProration=0.25

                       ceilingProration=0.25

                ))

        else if (ANC_ABS_PLN_PLAN_UOM ='W')

        then(

            if (l_length_of_service <3)

               then(

                                                                                                                             accrual =round(12/120,3)   

            ceiling = round(120/120,3)

                                                                                                                              carryover=round(60/120,3)

                                                                                                                              prorationFactor=0.25

                                                                                                                              vestingUnits=40

                                                                                                                              vestingUOM='C'

                                                                                                                                carryOverProration=0.25

                                                                                                                           ceilingProration=0.25

        )

        else if ((l_length_of_service =>3) and (l_length_of_service<5))

                    then (

         accrual =round(13/120,3)  

                      ceiling = round(130/120,3)

                      carryover=round(70/120,3)

                      prorationFactor=0.25

                      vestingUnits=30

                      vestingUOM='C'

                      carryOverProration=0.25

                      ceilingProration=0.25

                             )  

              else if (l_length_of_service =>5)

    then (

        accrual =round(14/120,3)  

                     ceiling =round(160/120,3)

                     carryover=round(80/120,3)

                     prorationFactor=0.25

                     vestingUnits=30

                     vestingUOM='C'

                    carryOverProration=0.25

                    ceilingProration=0.25

                )))      

Return accrual, ceiling, carryover, prorationFactor, vestingUnits, vestingUOM, carryOverProration,ceilingProration

/********************************************************************

FORMULA NAME: AH Global Absence Vesting Period Formula

FORMULA TYPE: Global Absence Vesting Period

DESCRIPTION: This sample formula applies the vesting period based on employment category.

            If the Employee belongs to a specific Legal Employer (Vision Corporation for this example)

            then his Vesting Period (Number of Days after which he is allowed to use his accrued leaves) is 90 Calendar Days for any other Legal Employer it is 30 Days

Change History:

Name                 Date        Comments

-----------------------------------------------------------------------------------------------------------------

XXXXXXX             DD-MM-YYYY   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

----------------------------------------------------------------------------------------------------------------

********************************************************************/

/*==============DATABASE ITEM DEFAULTS BEGIN =====================*/

DEFAULT for PER_ASG_ORG_LEGAL_EMPLOYER_NAME is 'Vision'

/*==============DATABASE ITEM DEFAULTS ENDS======================*/

/*================== FORMULA SECTION BEGIN =======================*/

If (PER_ASG_ORG_LEGAL_EMPLOYER_NAME='Vision Corporation')

then (

 vestingUOM = 'C'

  vestingUnits=90

)

else(

  vestingUOM = 'C'

  vestingUnits=30)

/*=================== FORMULA SECTION END =======================*/

return vestingUOM,vestingUnits

/***********************************************************************

FORMULA NAME: AH Global Absence Plan Use Rate Selection Formula 1  

FORMULA TYPE: Global Absence Plan Use Rate

DESCRIPTION: This sample formula returns the rate code.

            We have defined two different rate codes namely Sickness Rate and Hourly Rate.

            If an individual chooses either an Absence Type of Sick or Flu the RateCode is Sickness Rate else its Hourly Rate.  

Change History:

Name                 Date        Comments

---------------------------------------------------------------------------------------------------------------------

XXXXXXX             DD-MM-YYYY   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

--------------------------------------------------------------------------------------------------------------------

***********************************************************************/

/*=========== DATABASE ITEM DEFAULTS BEGINS======================*/

DEFAULT for ANC_ABS_TYP_NAME is 'Sick'

DEFAULT for ANC_ABS_RSN_NAME is 'Cough'

/*=========== DATABASE ITEM DEFAULTS ENDS======================*/

/*================ FORMULA SECTION BEGIN =======================*/

if ((ANC_ABS_TYP_NAME='Sick’) AND (ANC_ABS_RSN_NAME='Flu'))

then (

rateCode='Sickness Rate'

)

else (

rateCode='Hourly Rate')

/*================ FORMULA SECTION END =======================*/

return rateCode

/***********************************************************************

FORMULA NAME: AH Global Absence Plan Use Rate Formula2

FORMULA TYPE: Global Absence Plan Use Rate

DESCRIPTION: This sample formula returns the Plan Use Rate. If an Individual is Paid on Hourly Basis his RateCode will be Hourly else, it would be Annual Salary

Change History:

Name                 Date        Comments

--------------------------------------------------------------------------------------------

XXXXXXX             DD-MM-YYYY   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

--------------------------------------------------------------------------------------------

***********************************************************************/

/*=========== DATABASE ITEM DEFAULTS BEGIN =====================*/

DEFAULT for PER_ASG_HOURLY_SALARIED_CODE is 'H'

/*=========== DATABASE ITEM DEFAULTS ENDS======================*/

/*=========== FORMULA SECTION BEGIN======================*/

if (PER_ASG_HOURLY_SALARIED_CODE='H')

then (

  rateCode='Hourly Rate'

)

else (

  rateCode='Annual Salary Rate'

)

/*=========== FORMULA SECTION END======================*/

RETURN rateCode

Each absence plan setup requires four Tabs to be filled namely:

1. PLAN ATTRIBUTES

Contains Details about Plan Name, Description, Legislative Data Group, Processing Level, Conversion Formula Attached (used for Absence Duration calculation)

2. PARTICIPATION

Contains Details about Basic Plan Details, Enrollment and Termination Rules

3. ACCRUALS

Contains Details about Accrual Attributes like Accrual Formulas, Payment Percentage, Accrual Method, Accrual Frequency.

4. ENTRIES AND BALANCES

Contains Details about Balance Updates, Rates and Payroll Integrations

You may populate the following screen with above details

Populate Plan Attributes Tab:

This Tab Consists of 4 parts which are:

1. General Attributes

2. Plan Term

3. Legislative Information (Optional Used for Populating Legislative Specific Absence Information. Not Applicable in this example)

4. Descriptive Information (Optional Used for Populating DFF Fields If Created for Absence Plan. Not Applicable in this example)

Populate the following details in General Attributes Section as shown below:

Populate the following details in Plan Term Section as shown below:

Use the above details and populate the Plan Attributes Tab and the screenshot would look like:

Populate Participation Tab:

This Tab Consists of 2 parts which are:

1. Enrollment Rules

2. Termination Rules

Populate the following details in Enrollment Rules Section as shown below:

Populate the following details in Termination Rules Section as shown below:

Use the above details and populate the Participation Tab and the screenshot would look like:

Populate Accruals Tab which consists of Accrual Attributes Section only.

Populate the following details in Accrual Attributes Section as shown below:

Use the above details and populate the Accruals Tab and the screenshot would look like:

Populate Entries and Balances Tab.This Tab Consists of 3 Sections which are:

1. Balance Updates

2. Rates

3. Payroll Integration

Populate the following details in Balance Updates Section as shown below:

Populate the following details in Rates Section as shown below:

Populate the following details in Payroll Integration Section as shown below:

Use the above details and populate the Entries and Balances Tab and the screenshot would look like:

Once all the above setup is done Absence Plan Creation is complete.

In the previous article we have learned about the Oracle Fusion Application architecture. In this article we will learn about the Oracle Fusion Middleware products, Tools and Metadata Repository.

Oracle Fusion Middleware products:

Before we start to understand How to create an Absence Plan first try to understand what an Absence Plan is and why is it required.

In real life Absence Plan holds a different meaning than that of the one meant in Fusion Applications.

In real life Absence Plan for an individual (or for that matter for a Working individual) relates more to a question which is generally asked by his Manager

What are your Absence Plans?

and he would generally respond stating I will be on leave on so and so dates.

But in context with Fusion Applications an Absence Plan (I feel the naming convention isn’t correct it should have been called Accrual Plan but that again is incorrect as Absence Plans are even those which are of qualification and No-Entitlement Type, details about the same in Absence Plan Types Section) could be imagined as a Bucket.

Yes, I mean a Bucket as we know.

Let’s for time being say an Absence Plan is an Absence Bucket and I call it as a Bucket as it is supposed to hold:

1. Leave / Absence Balance

Anything and everything around the Entire Absence Plan surrounds around this single piece of information usually called ‘Absence Balance’

Different Items related with an Absence Plan and their association with Absence Balance follows:

Absence Plan

A name given to a set of rules / guidelines which define how the absence balance will be assigned and maintained

Legislation

Geography / Country where this Absence Balance is Maintained. For Example, if we are doing Absence Plan setup for India Legislation would be India, if we are doing for USA it would be United States and so on....

Plan Type

An attribute which defines how the Absence Balance would be calculated / paid.

For example:

                       If Absence / Leave Balance is paid to employees as a result of an event such as childbirth, illness or injury it is called Qualification Plan Type Absence Plan

                   Typical Example Being Hospitalization Leave.

                   If Absence / Leave Balance is paid to employees as a result of accumulation / accrual it is called Accrual Plan Type Absence Plan

                   Leaves like Annual Leave, Vacation Leave fall into this category

                   f Absence / Leave Balance is paid without having any track, then we referred to them as No-Entitlement Plan Type Absence Plan

                   Marriage Leave, Compassionate Leave. fall into this category

Plan Term

This is basically the entire time period for which the absence balance has the validity.

For Example

                   Plan Term: Calendar Year

                   Start Day: 01

                   Start Month: 1

                       Means the Absence Plan will start on 1st day of 1st month (i.e. 1st January) and run till the end of calendar year i.e. 31-Dec

                   Plan Term: Calendar Year

                   Start Day:  01

                   Start Month:  2

                       Means the Absence Plan will start on 1st day of 2nd month (i.e. 1st February) and run till the end of calendar year i.e. 31-Dec

                   Plan Term:  Calendar Year

                   Start Day:  05

                   Start Month:  10

                   Means the absence Plan will start on 5th day of 10th month (i.e. 5th October) and run till the end of calendar year i.e. 31-Dec   

Absence Plan UOM

Unit of Measure which states in which unit (either of Days / Calendar Days / Hours) will this Absence Balance will get measured

Accrual Method

Method of accruing Absence / Leave Balance.

It is of two types:

1. Frontloaded

The Entire Absence Balance is allocated at the beginning of the plan term

2. Incremental

The Absence Balance are accrued at regular intervals

Accrual Frequency

Frequency at which accrual happens. It is of two types Person Primary Frequency and Repeating Period.

If person gets his absence / leave balance at the start of payroll period, then the Accrual Frequency is of Person Primary Frequency Type

            For Example:

            Person Primary Frequency: Weekly

            Means he gets paid every week (Employee has a Weekly Payroll Assigned / Attached to him) and same is true for his absence balance too i.e. absence balance is

            received every week (in synchronization with his person primary payroll payment frequency).        

            Person Primary Frequency: Bi-Weekly

            Means he gets paid once in row weeks (Employee has a Bi-Weekly Payroll Assigned / Attached to him) and same is true for his absence balance too i.e. absence

            balance is received once in two weeks (in synchronization with his person primary payroll payment frequency).

            Person Primary Frequency: Monthly

            Means he gets paid once a month (Employee has monthly payroll assigned / attached to him) and same is true for his absence balance too i.e. absence balance is

            received once a month (in synchronization with his person primary payroll payment frequency).

            Person Primary Frequency: Quarterly

            Means he gets paid once in quarter (Employee has a Quarterly Payroll Assigned / Attached to him) and same is true for his absence balance too i.e. absence balance

            is received once each quarter (in synchronization with his person primary payroll payment frequency).

If person gets his absence / leave balance at the start of each instance of a Specific Repeating Time Period, then Accrual Frequency is of Repeating Time Period

           For Example:

           Repeating Time Period: Every Quarter of a Calendar year

           Means he will accrue this leave once every 3 months in the Calendar Year.

           Repeating Time Period: Bi Monthly

           Means he will accrue this leave 2 times in a month.  

           Repeating Time Period: Every Quarter of a Calendar year

           Means he will accrue this leave once every 3 months in the Calendar Year.

           Repeating Time Period: Monthly

           Means he will accrue this leave once a month.  

Ceiling

This means the maximum Accrual / Leave Balance an employee can accrue / store within a particular accrual term

         For Example:

        If for a particular Absence Plan the ceiling value is 10

        It means that the employee can accrue at max 10 leaves per year. If his balance becomes more than 10 then the same will be forfeited.

        If for a particular Absence Plan the ceiling value is 20

        It means that the employee can accrue at max 20 leaves per year. If his balance becomes more than 10 then the same will be forfeited.

Carryover

This means the Absence / Leave Balance an employee can carry forward (take along with him) to next accrual term

         For Example:

        If for a particular Absence Plan has carryover as 50

        It means that the employee can carry forward 50 leaves per year. This carry forward value would keep accumulating until ceiling value is reached

        So if ceiling is 100 and employee has already carried forward 50 leaves from first year and again 50 from next year then he cannot carry forward leaves for 3rd year.  

        If for a particular Absence Plan the carryover as 60

        It means that the employee can carry forward 60 leaves per year. This carry forward value would keep accumulating until ceiling value is reached

        So if ceiling is 100 and employee has already carried forward 50 leaves from first year and again 50 from next year then he cannot carry forward leaves for 3rd year

Vesting Period

This is the Time Period during which Employees can accrue leave but cannot apply leave

For example, if a Plan starts on 1st January and has a vesting period of 1 month then the first leave which an employee can take would be a date after 1st February (1st January + 1 month). He would anyways be allowed to accrue during the entire January Month

Absence Payment Rate Rule

Method to calculate payment during an Absence Period. (a period when employee is absent from work, but still needs to be paid)

For Example, if a Female Employee is on Maternity Leave for 6 months then at what rate should she be paid.

Final Disbursement Rate Rule

Method to calculate payment of accruals when plan participation ends (An Employee became a Contractor from Regular Employee so his eligibility for Annual Leave comes to an end, but he has already had a positive balance of say 10. Now if the payroll is integrated with absence then employee needs to be paid for this accrued balance. This rate talks about the same Disbursement Rate Rule).

Discretionary Disbursement Rate Rule

Method to calculate payment when paying out part of accrual balance (An Employee resigns a company and he has a notice period of 30 days, he has served 25 days of notice period and he has an accrual balance of 10 days. Due to some emergency he has to go to his hometown and he seeks immediate relieving. In this case the company may decide to deduct his 5 days from Accrual balance and pay for the rest 5 at a discretionary rate).

Liability Rate Rule

Method to calculate cost of accrual balance to determine employer liability (An Employee resigns a company and he has a notice period of 30 days, he has served 25 days of notice period and he has an accrual balance of 10 days. Due to some emergency he has to go to his hometown and he seeks immediate relieving. In this case the company may decide to deduct his 5 days from Accrual balance and pay for the rest 5 at a discretionary rate and the rest 5 days will be paid at the Liability Rate).

Now since we are aware of some of the most commonly used terms for an absence plans we should try to create one absence plan. Requirement is to create an Absence Plan with Absence Plan type as Accrual and Accrual Method as Incremental

We have the following requirement:

Absence Plan Type: Accrual

Accrual Method: Incremental

Accrual UOM: Days

Accrual Values: If Length of Service is < 3 years then Accrue 10 days, have a ceiling of 100 days and carryover of 50 days.

                                                                If Length of Service is < 3 years and Length of Service >= 5 years then Accrue 12 days, ceiling of 120 days and carryover of 60 days

                                                                If Length of Service is > 5 then Accrue 15 days, have a ceiling of 150 days and carryover of 75 days                                    

Vesting Period: If Legal Employer is Vision Corporation Then Vesting Period is 90 Calendar Days Else Vesting Period is 30 Calendar Days

Absence Payment Rate Rule: Provide a Sickness Rate If the Employee is taking a Leave of Type Sick and Flu else use Hourly Rate

Final Disbursement Rate Rule: If Employee is of Hourly Salaried type use Hourly rate, if he is Regular Employee provide Annual Salary Rate

Discretionary Disbursement Rate Rule: If Employee is of Hourly Salaried type use Hourly rate, if he is Regular Employee provide Annual Salary Rate

Liability Rate Rule: If Employee is of Hourly Salaried type use Hourly rate, if he is Regular Employee provide Annual Salary Rate

We would be using Fast Formula (reasons supporting the same provided alongside) for the following attributes:

**Accrual Values: This can be achieved using an Accrual Matrix but we would like provide maximum flexibility and hence Fast Formula

Vesting Period: This requirement can only be achieved using Fast Formula

**Absence Payment Rate Rule: This requirement could have been met using the ‘Rate Definition’ option but for flexibility we have used Fast Formula  

**Final Disbursement Rate Rule: This requirement could have been met using the ‘Rate Definition’ option but for flexibility we have used Fast Formula

**Discretionary Disbursement Rate Rule: This requirement could have been met using the ‘Rate Definition’ option but for flexibility we have used Fast Formula

**Liability Rate Rule:  This requirement could have been met using the ‘Rate Definition’ option but for flexibility we have used Fast Formula

**Note: By Allowing Flexibility we mean in case there are additional complex logic in future then we can add the Fast Formula Code in the existing FF defined.

While some might debate that the entire absence plan could well have been setup using standard setups / configurations (and I do agree to that) but the below are specific reasons for using Fast Formula here:

1. Allows Flexibility of Adding Custom Logic (If required by customer at a Future Date)

Fast Formulas (Details in a separate article) generally allows us to add conditional logics (IF-ELSE constructs) and provide a way to customize the seeded solution.

For Example

Say currently we want to have a condition that if

Employee Category is Hourly then use RateCode as ‘Hourly Rate’

Employee Category is Salaried then use RateCode as ‘Salaried’

But after few days customer has changed the requirement and now they even want to ensure that any Salaried Employee who has been on leave for most of time during the year would rather be paid in terms of hours worked (typical example being someone on Leave Without Pay)

IF

    Employee Category is Hourly then use RateCode as ‘Hourly Rate’

Else if

                      Employee Category is Salaried and Employee Payroll Status is Currently on Leave without Pay then ‘Hourly Rate’ ------ new requirement

Else

                      Employee Category is Salaried and Employee Payroll Status is Active Payroll Eligible then ‘Salaried’

end if

Now in order to accommodate the new requirement you would need to create a completely new Absence Plan with new setups and that would have many implications but if we use Fast Formula this can be achieved by just adding a piece of if-else construct.

2. Absence Plan Migration becomes a little easier

In all implementation projects setups needs to be once done in a Development POD (in EBS we referred them as INSTANCE) , and then the same is migrate to SIT, UAT , PRE-PROD and then PROD.

IF we use Fast Formula approach migration becomes simpler.

You need to create multiple custom fast formula in the system (your POD) in the legislation where you want to create the absence plan.

There are 4 types of Fast Formula used in this example namely

1. Global Absence Plan Duration   

2. Global Absence Accrual

3. Global Absence Vesting Period

4. Global Absence Plan Use Rate

There are 5 Fast Formula used in this example which are:

1. AH Global Absence Plan Duration Formula

2. AH Global Absence Accrual Formula

3. AH Global Absence Vesting Period Formula

4. AH Global Absence Plan Use Rate Selection Formula 1

5. AH Global Absence Plan Use Rate Formula2

/************************************************************************************

FORMULA NAME: AH Global Absence Plan Duration Formula

FORMULA TYPE: Global Absence Plan Duration

DESCRIPTION: This sample formula returns the duration based on effective date falls on Sunday.

Change History:

Name                 Date        Comments

--------------------------------------------------------------------------------------------

XXXXXXX             DD-MM-YYYY   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

--------------------------------------------------------------------------------------------

************************************************************************************/

/*================ FORMULA SECTION BEGIN =======================*/

l_date=GET_CONTEXT (EFFECTIVE_DATE,'4712/12/31 00:00:00' (date))

l_weekday=to_char(l_date,'DAY')

If (l_weekday= '7')

then (

duration=0

)

else (

duration=8.5

)

/*================ FORMULA SECTION END =======================*/

return duration

/*****************************************************************

FORMULA NAME: AH Global Absence Accrual Formula

FORMULA TYPE: Global Absence Accrual

DESCRIPTION: This sample formula applies the Accrual, Ceiling, CarryOver, Proration Factor, Vesting Units, Vesting UOM, CarryOver Proration and Ceiling Proration

based on Length of Service and Accrual Plan the person enrolled into.

Change History:

Name                 Date        Comments

------------------------------------------------------------------------------------------------------------

XXXXXXX             DD-MM-YYYY   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

------------------------------------------------------------------------------------------------------------

*****************************************************************/

/*=========== DATABASE ITEM DEFAULTS BEGIN =====================*/

DEFAULT for PER_ASG_REL_ORIGINAL_DATE_OF_HIRE is '4712/12/31 00:00:00' (date)

DEFAULT for ANC_ABS_PLN_NAME is 'A'

DEFAULT for ANC_ABS_PLN_PLAN_UOM is 'H'

/*=========== DATABASE ITEM DEFAULTS ENDS======================*/

/*================ FORMULA SECTION BEGIN =======================*/

l_no_of_days=DAYS_BETWEEN(GET_CONTEXT(EFFECTIVE_DATE,'4712/12/31 00:00:00' (date)),PER_ASG_REL_ORIGINAL_DATE_OF_HIRE)

l_length_of_service=(l_no_of_days/365)

/* check if employee enrolled into this plan or not */

if (ANC_ABS_PLN_NAME='BM_US_ABSENCE_ACCRUAL_PLAN')

then(

    if(ANC_ABS_PLN_PLAN_UOM ='H')

    then(

        if(l_length_of_service <3)

        then(

            accrual =10   

            ceiling = 100

            carryover=50

            prorationFactor=0.25

            vestingUnits=40

            vestingUOM='C'

            carryOverProration=0.25

            ceilingProration=0.25

            )

        else if ((l_length_of_service =>3) and (l_length_of_service<5))

        then (

                 accrual =12  

                 ceiling = 120

                 carryover=60

                 prorationFactor=0.25

                 vestingUnits=30

                 vestingUOM='C'

                carryOverProration=0.25

                ceilingProration=0.25

               )

        else if (l_length_of_service =>5)

         then (

                  accrual =15  

                  ceiling = 150

                  carryover=75

                  prorationFactor=0.25

                  vestingUnits=30

                  vestingUOM='C'

                  carryOverProration=0.25

                  ceilingProration=0.25

            ) )

        else if (ANC_ABS_PLN_PLAN_UOM ='D')

        then(

            if (l_length_of_service <3)

               then(

               accrual =round(10/24,3)   

                ceiling = round(100/24,3)

                carryover=round(50/24,3)

                prorationFactor=0.25

               vestingUnits=40

               vestingUOM='C'

               carryOverProration=0.25

               ceilingProration=0.25

            )

        else if ((l_length_of_service =>3) and (l_length_of_service<5))

                    then (

                                                                                                                                accrual =round(12/24,3)  

                 ceiling = round(120/24,3)

                 carryover=round(60/24,3)

                 prorationFactor=0.25

                 vestingUnits=30

                 vestingUOM='C'

                carryOverProration=0.25

                ceilingProration=0.25

            )  

              else if (l_length_of_service =>5)

        then (

            accrual =round(15/24,3)  

                     ceiling =round(150/24,3)

                     carryover=round(75/24,3)

                     prorationFactor=0.25

                     vestingUnits=30

                    vestingUOM='C'

                    carryOverProration=0.25

                    ceilingProration=0.25

                )

           )

        else if (ANC_ABS_PLN_PLAN_UOM ='W')

        then(

            if (l_length_of_service <3)

               then(

                accrual =round(10/120,3)   

                ceiling = round(100/120,3)

                carryover=round(50/120,3)

                 prorationFactor=0.25

                vestingUnits=40

                vestingUOM='C'

                carryOverProration=0.25

                ceilingProration=0.25

            )

        else if ((l_length_of_service =>3) and (l_length_of_service<5))

                    then (

                 accrual =round(12/120,3)  

                 ceiling = round(120/120,3)

                 carryover=round(60/120,3)

                 prorationFactor=0.25

                 vestingUnits=30

                 vestingUOM='C'

                 carryOverProration=0.25

                 ceilingProration=0.25

            )  

              else if (l_length_of_service =>5)

        then (

            accrual =round(15/120,3)  

                  ceiling =round(150/120,3)

                  carryover=round(75/120,3)

                  prorationFactor=0.25

                  vestingUnits=30

                  vestingUOM='C'

                  carryOverProration=0.25

                  ceilingProration=0.25

                )))

    if (ANC_ABS_PLN_NAME='Sickness')

then(

    if(ANC_ABS_PLN_PLAN_UOM ='H')

    then(

        if(l_length_of_service<3)

        then(

            accrual =12   

            ceiling = 120

            carryover=60

            prorationFactor=0.25

            vestingUnits=40

            vestingUOM='C'

            carryOverProration=0.25

            ceilingProration=0.25

            )

        else if ((l_length_of_service =>3) and (l_length_of_service<5))

        then (

                 accrual =13  

                 ceiling = 130

                 carryover=70

                 prorationFactor=0.25

                 vestingUnits=30

                 vestingUOM='C'

                 carryOverProration=0.25

                 ceilingProration=0.25

               )

        else if (l_length_of_service =>5)

         then (

                  accrual =14  

                  ceiling = 160

                  carryover=80

                  prorationFactor=0.25

                  vestingUnits=30

                  vestingUOM='C'

                  carryOverProration=0.25

                  ceilingProration=0.25 ))

        else if (ANC_ABS_PLN_PLAN_UOM ='D')

        then(

            if (l_length_of_service <3)

               then(

                accrual =round(12/24,3)   

                ceiling = round(120/24,3)

                carryover=round(60/24,3)

                prorationFactor=0.25

                vestingUnits=40

                vestingUOM='C'

                carryOverProration=0.25

                ceilingProration=0.25

            )

        else if ((l_length_of_service =>3) and (l_length_of_service<5))

                    then (

             accrual =round(13/24,3)  

                    ceiling = round(130/24,3)

                     carryover=round(70/24,3)

                     prorationFactor=0.25

                     vestingUnits=30

                     vestingUOM='C'

                    carryOverProration=0.25

                    ceilingProration=0.25

            )  

              else if (l_length_of_service =>5)

        then (

                      accrual =round(14/24,3)  

                     ceiling =round(160/24,3)

                     carryover=round(80/24,3)

                     prorationFactor=0.25

                     vestingUnits=30

                     vestingUOM='C'

                       carryOverProration=0.25

                       ceilingProration=0.25

                ))

        else if (ANC_ABS_PLN_PLAN_UOM ='W')

        then(

            if (l_length_of_service <3)

               then(

                                                                                                                             accrual =round(12/120,3)   

            ceiling = round(120/120,3)

                                                                                                                              carryover=round(60/120,3)

                                                                                                                              prorationFactor=0.25

                                                                                                                              vestingUnits=40

                                                                                                                              vestingUOM='C'

                                                                                                                                carryOverProration=0.25

                                                                                                                           ceilingProration=0.25

        )

        else if ((l_length_of_service =>3) and (l_length_of_service<5))

                    then (

         accrual =round(13/120,3)  

                      ceiling = round(130/120,3)

                      carryover=round(70/120,3)

                      prorationFactor=0.25

                      vestingUnits=30

                      vestingUOM='C'

                      carryOverProration=0.25

                      ceilingProration=0.25

                             )  

              else if (l_length_of_service =>5)

    then (

        accrual =round(14/120,3)  

                     ceiling =round(160/120,3)

                     carryover=round(80/120,3)

                     prorationFactor=0.25

                     vestingUnits=30

                     vestingUOM='C'

                    carryOverProration=0.25

                    ceilingProration=0.25

                )))      

Return accrual, ceiling, carryover, prorationFactor, vestingUnits, vestingUOM, carryOverProration,ceilingProration

/********************************************************************

FORMULA NAME: AH Global Absence Vesting Period Formula

FORMULA TYPE: Global Absence Vesting Period

DESCRIPTION: This sample formula applies the vesting period based on employment category.

            If the Employee belongs to a specific Legal Employer (Vision Corporation for this example)

            then his Vesting Period (Number of Days after which he is allowed to use his accrued leaves) is 90 Calendar Days for any other Legal Employer it is 30 Days

Change History:

Name                 Date        Comments

-----------------------------------------------------------------------------------------------------------------

XXXXXXX             DD-MM-YYYY   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

----------------------------------------------------------------------------------------------------------------

********************************************************************/

/*==============DATABASE ITEM DEFAULTS BEGIN =====================*/

DEFAULT for PER_ASG_ORG_LEGAL_EMPLOYER_NAME is 'Vision'

/*==============DATABASE ITEM DEFAULTS ENDS======================*/

/*================== FORMULA SECTION BEGIN =======================*/

If (PER_ASG_ORG_LEGAL_EMPLOYER_NAME='Vision Corporation')

then (

 vestingUOM = 'C'

  vestingUnits=90

)

else(

  vestingUOM = 'C'

  vestingUnits=30)

/*=================== FORMULA SECTION END =======================*/

return vestingUOM,vestingUnits

/***********************************************************************

FORMULA NAME: AH Global Absence Plan Use Rate Selection Formula 1  

FORMULA TYPE: Global Absence Plan Use Rate

DESCRIPTION: This sample formula returns the rate code.

            We have defined two different rate codes namely Sickness Rate and Hourly Rate.

            If an individual chooses either an Absence Type of Sick or Flu the RateCode is Sickness Rate else its Hourly Rate.  

Change History:

Name                 Date        Comments

---------------------------------------------------------------------------------------------------------------------

XXXXXXX             DD-MM-YYYY   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

--------------------------------------------------------------------------------------------------------------------

***********************************************************************/

/*=========== DATABASE ITEM DEFAULTS BEGINS======================*/

DEFAULT for ANC_ABS_TYP_NAME is 'Sick'

DEFAULT for ANC_ABS_RSN_NAME is 'Cough'

/*=========== DATABASE ITEM DEFAULTS ENDS======================*/

/*================ FORMULA SECTION BEGIN =======================*/

if ((ANC_ABS_TYP_NAME='Sick’) AND (ANC_ABS_RSN_NAME='Flu'))

then (

rateCode='Sickness Rate'

)

else (

rateCode='Hourly Rate')

/*================ FORMULA SECTION END =======================*/

return rateCode

/***********************************************************************

FORMULA NAME: AH Global Absence Plan Use Rate Formula2

FORMULA TYPE: Global Absence Plan Use Rate

DESCRIPTION: This sample formula returns the Plan Use Rate. If an Individual is Paid on Hourly Basis his RateCode will be Hourly else, it would be Annual Salary

Change History:

Name                 Date        Comments

--------------------------------------------------------------------------------------------

XXXXXXX             DD-MM-YYYY   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

--------------------------------------------------------------------------------------------

***********************************************************************/

/*=========== DATABASE ITEM DEFAULTS BEGIN =====================*/

DEFAULT for PER_ASG_HOURLY_SALARIED_CODE is 'H'

/*=========== DATABASE ITEM DEFAULTS ENDS======================*/

/*=========== FORMULA SECTION BEGIN======================*/

if (PER_ASG_HOURLY_SALARIED_CODE='H')

then (

  rateCode='Hourly Rate'

)

else (

  rateCode='Annual Salary Rate'

)

/*=========== FORMULA SECTION END======================*/

RETURN rateCode

Each absence plan setup requires four Tabs to be filled namely:

1. PLAN ATTRIBUTES

Contains Details about Plan Name, Description, Legislative Data Group, Processing Level, Conversion Formula Attached (used for Absence Duration calculation)

2. PARTICIPATION

Contains Details about Basic Plan Details, Enrollment and Termination Rules

3. ACCRUALS

Contains Details about Accrual Attributes like Accrual Formulas, Payment Percentage, Accrual Method, Accrual Frequency.

4. ENTRIES AND BALANCES

Contains Details about Balance Updates, Rates and Payroll Integrations

You may populate the following screen with above details

Populate Plan Attributes Tab:

This Tab Consists of 4 parts which are:

1. General Attributes

2. Plan Term

3. Legislative Information (Optional Used for Populating Legislative Specific Absence Information. Not Applicable in this example)

4. Descriptive Information (Optional Used for Populating DFF Fields If Created for Absence Plan. Not Applicable in this example)

Populate the following details in General Attributes Section as shown below:

Populate the following details in Plan Term Section as shown below:

Use the above details and populate the Plan Attributes Tab and the screenshot would look like:

Populate Participation Tab:

This Tab Consists of 2 parts which are:

1. Enrollment Rules

2. Termination Rules

Populate the following details in Enrollment Rules Section as shown below:

Populate the following details in Termination Rules Section as shown below:

Use the above details and populate the Participation Tab and the screenshot would look like:

Populate Accruals Tab which consists of Accrual Attributes Section only.

Populate the following details in Accrual Attributes Section as shown below:

Use the above details and populate the Accruals Tab and the screenshot would look like:

Populate Entries and Balances Tab.This Tab Consists of 3 Sections which are:

1. Balance Updates

2. Rates

3. Payroll Integration

Populate the following details in Balance Updates Section as shown below:

Populate the following details in Rates Section as shown below:

Populate the following details in Payroll Integration Section as shown below:

Use the above details and populate the Entries and Balances Tab and the screenshot would look like:

Once all the above setup is done Absence Plan Creation is complete.

In this article, we will learn about Accrual Accounting in Oracle Apps and also we will see Accrual Accounting Entries along with setups for the same.  

What Are these Accrual Accounts?

·         Principle of accrual accounting

·         Timing difference between receiving and invoicing

·         Represents the accrued liability from your vendors

·         Periodic accruals occurs at month-end

·         Perpetual accruals ensure that valued quantities equals accounting entries

·         Don’t accrue expenses upon receipt

AP Accrual Accounts-

·         May have multiple lines per PO

·         May have multiple PO distributions per line

·         Four stored accounts per PO distribution


Accrual Accounting Entries-

PO Receipt   

      Receiving Account                        XXX

                A/P Accrual Account                                   XXX


PO Return to Vendor

      A/P Accrual Account         XXX

               Receiving Account                           XXX


Invoice Correction

     New Charge Account          XXX

               Old Charge Account                         XXX

 
Receipt Deliveries –

Delivery to stock inventory

     Sub inventory Account         XXX

Receiving Account                              XXX

Delivery to WIP inventory

      Job OSP Account               XXX

            Receiving Account                              XXX

Month-End Period Accruals

Expense Item

       Charge Account                XXX

              Expense A/P Accrual Account                      XXX

In Oracle General Ledger, reverse the accrual entry in the following month.


Setup in Oracle Purchasing- Navigate to Purchasing Options Form

·         Set Accrue Expense Items to Period End

·         Set the Expense A/P Accrual Account

·         Use the Define Receiving Options form

·         Set the Receiving Account for each inventory organization


When Defining Purchase Orders

·         Never manually set the Accrue on Receipt Flag

·         For expense destinations, the flag should be No

·         For inventory and shop floor (OSP) destinations, the field should be Yes


Setup in Oracle Inventory

·         Use the Define Organization Parameters Form

Ø  Set the Inventory A/P Accrual Account

Ø  Use the same Inventory A/P Accrual Account for all organizations

·         Use separate accounts for each type of system account:

Ø  Expense A/P Accrual Account

Ø  Inventory A/P Accrual Account

Ø  Receiving Account(s)

Ø  Expense Purchase Order Charge Accounts

Ø  Other inventory, WIP and price variance accounts

 Objective:

In the previous article Oracle Fusion Middleware products, Tools and Metadata Repository we have learned about the the products and the tools used in Fusion Middleware. In this article we will learn about the Oracle SOA suite, Oracle webcentre Portal Schema, Oracle Webcentre Content Schema, Oracle Identity Management Schema, Understanding Creation screen. 

SOA Suite Schemas:




Oracle Webcentre Portal Schemas:




Oracle Webcentre Content Schema:




Oracle Identity Management Schemas:




Understanding Creation screen:

Objective:

This article is intended to provide an overview of Self Service Procurement and how it works.

Self Service Procurement:

Oracle Fusion self service procurement cloud enables the end user to quickly request for products and services he requires, with minimum support, at the best possible price. The user experiences like shopping online with any e-business portal.  Fusion Self Service Procurement provides online assistance at the point where it is needed. Training videos are available at the click of a mouse. For example, how to place an order with Self Service procurement can be launched right from the home page. Self Service Procurement Cloud provides intuitive navigation and rich information. It is just like shopping online.

How it works:

Please refer to the below image



There are 3 main areas of the purchase requisition window:

* Search Catalog: There are three types of catalog a) Local Catalogwhere administrators or suppliers on behalf of the buying organization can upload local catalog content either online or in batch. b) Punchout Catalogwhich can be a direct link to the store, where the requester searches, shops, and returnsitems to Oracle Fusion Self Service Procurement, and c)Informational Catalogcontains instructions or links for ordering other items or services at your company.

In the search area we can enjoy the features of advance search wherein you can type any feature of the product known to you. For example if you don’t know the model number of the laptop but you remember that the laptop has 14’’ screen. In that case you can simply type 14’’ laptop to get the options.

*Browse Catalog: It is used for category browsing. In this area you can sort out in details about your requirements. It also helps in comparing the products alongwith its features in detail.



My Requisitions: This keeps an easy tracking of all our activities. Depending on your company’s business process, this will complete your transaction and your requisition will be routed for approval.

Customer has a requirement where-in they will allow 2 days of Accrual Leave to all eligible employees ( eligibility being checked via a separate Eligibility Fast Formula).
If the employee has joined in the same year in which he/she is trying to apply leave and Hire Month is before the 7th month of the year then he gets balance of 2 leaves for the year
If the employee has joined in the same year in which he/she is trying to apply leave and Hire Month is after the 7th month of the year then he gets balance of 1 leave for the year
If the employee has been serving the company from anytime before this year  then he gets balance of 2 leave for the year
VestingUnits
Vesting Units as defined is a numeric value which determines after how much time period (this being measured by VestingUOM will a individual be able to apply leave)
For this example the VestingUnits is 3 while VestingUOM is Months meaning Employee will be capable of applying leave after 3 months, till that period he/she anyhow would keep on accruing the leaves if eligible .

This tutorial is a continuation of Fusion Payroll and how it functions.
The topics covered in this tutorial are:

• Payroll Statutory Units
  
  
• Legal Employers
  
  
• Tax Reporting Units
  
  
• Creating a Legal Entity
  
  
• Selecting the Scope of the Legislative Data Groups
  
  
• Defining Legal Reporting Units
  
  
• Creating Business Units
  
  

Business Requirement

Global Absence Vesting Period Formula is used when want to ensure what type of vesting ( how long will an employee accrue leave balance ) but will not be allowed to apply for a leave.

For this specific example requirement is :

We have a DFF ( Descriptive Flex Field) defined at the assignment screen which holds employee assignment type namely 'Assignee', 'OTP' , 'Resident', 'Resident -Home'.....

The Requirement is :

A) There will be no Vesting Period if

1) the current assignment is First assignment and DFF value is either 'Assignee' , 'OTP' or 'Resident'

                                         OR

2) the current assignment is Global Temporary Assignment and DFF value is either 'Assignee' , 'OTP' or 'Resident'

B) There will be  Vesting Period if

1) the current assignment is NOT First assignment and DFF value is neither of 'Assignee' , 'OTP' or 'Resident'

                                         OR

2) the current assignment is NOT Global Temporary Assignment and DFF value is neither of  'Assignee' , 'OTP' or 'Resident'

Formula Code :

/********************************************************************

FORMULA NAME: A2F_ANC_AssigneeOTPResident_VESTING_1MONTH

FORMULA TYPE: Global Absence Vesting Period

DESCRIPTION: This sample formula removes the vesting period for Assignee/OTP/Resident

Name Date Comments

-----------------------------------------------------------------------------------------------------------------

Ashley Hardy 15-Jun-2015 Initial Version

Ashley Hardy 06-Jul-2015 Incorporate Changes Required for 'Global Temporary Assignment'

----------------------------------------------------------------------------------------------------------------

********************************************************************/

/*==============DATABASE ITEM DEFAULTS BEGIN =====================*/

DEFAULT for PER_ASG_REL_DATE_START is '1951/01/01 00:00:00' (date)

DEFAULT for PER_ASG_REL_ORIGINAL_DATE_OF_HIRE is '1951/01/01 00:00:00' (date)

DEFAULT for PER_PERSON_ENTERPRISE_HIRE_DATE is '1951/01/01 00:00:00' (date)

DEFAULT FOR PER_ASG_ATTRIBUTE5 IS ' '

DEFAULT FOR PER_ASG_ACTION_CODE is ' '

/*==============DATABASE ITEM DEFAULTS ENDS======================*/

/*================== FORMULA SECTION BEGIN =======================*/

IF ((PER_ASG_REL_DATE_START = PER_ASG_REL_ORIGINAL_DATE_OF_HIRE) OR (PER_ASG_ACTION_CODE = 'GLB_TEMP_ASG'))

THEN (

If (PER_ASG_ATTRIBUTE5 = 'Assignee')

OR (PER_ASG_ATTRIBUTE5 = 'OTP')

OR (PER_ASG_ATTRIBUTE5 = 'Resident')

then(

vestingUOM = 'M'

vestingUnits= 0

)

else(

vestingUOM = 'M'

vestingUnits=1

)

) else

(vestingUOM = 'M'

vestingUnits=1 )

/*=================== FORMULA SECTION END =======================*/

return vestingUOM,vestingUnits

Screenshot :

Click on Edit Button and then select Correct as shown :

SUMMARY

This section explains how to work with objects in the Business Model and Mapping (BMM) layer which is the backbone of an OBIEE application. It also explains other BMM layer concepts like logical tables, joins, and columns.

This section comprises following topics:

Building the BMM layer of a Repository

BMM layer – Physical layer Relation

1. BMM Layer

BMM layer defines the business or logical model of the data. In BMM layer the actual modelling will be started according to the user requirement. Once we create the presentation layer then we do a consistency check. Anytime we create changes in the repository, we do consistency check that tries to find any error in your modelling or something which is not according to the OBIEE principle through a warning or error. If it is error definitely we have to come with the solution to get rid of the error in order to deploy the rpd.

• The BMM layer specifies the mapping between the business model and physical layer schemas.

• Business models are always dimensional, unlike physical layer objects that reflect the organization of the data sources.

• This layer can contain one or more business models. Each business model consists of logical dimensions, facts, hierarchies and metrics. For e.g. the time dimension can have different levels or hierarchies like month, quarter or year.

Note: Oracle recommends is even though the hierarchy is flat, also then you better create a hierarchy so that the join conditions will be properly ordered. 

• BMM layer-Physical layer relation

Business model objects map to the source data objects in the physical layer. Typically, business models map to physical schemas, logical tables map to physical tables, logical columns map to physical columns and so on.

Mapping between business model objects and physical objects do have one-to-one and many-to-many relationship. So one BMM layer can correspond to many physical objects.

One column in the BMM layer can refer multiple attributes in the physical layer

• Objects in BMM layer

• The BMM layer contains the business model definitions as per the user requirement.

• It is the highest level object in the BMM layer.

• Simplifies the physical schema.

• Captures how user thinks about their businesses by their own vocabulary.

1. In the Admin Tool, right-click in the BMM layer below any objects.

2. Select New Business Model from shortcut menu.

3. Provide a name for the business model.

4. New business models are disabled by default. If you want to make the presentation layer available for queries, select disabled.

5. Specify description of the business model which is optional.

6. Click OK.

After you create a business model, you can create business model objects by dragging and dropping objects from the physical layer.

• Creating Logical table and Columns

When you create the logical table in the BMM layer it will be always displayed with the icon . The logical fact table can be represented by with # symbol included.

• Logical Table

• Represent fact or dimension data.

• Can be created automatically by dragging tables from the physical layer.

Note: You must include the table with foreign keys if you want to preserve the keys and joins from the physical layer

• If a table does not exist in your physical schema, the logical table can be created manually by right-clicking the business model and selecting new object-> Logical Table.

• If the table is a lookup table, select the option Lookup table. A Lookup table stores multilingual data corresponding to the rows in the base tables.

• Can be modified without affecting the physical layer objects. Dimension table should have a key whether the fact table contains metrics.

Logical Table Sources (LTS)

• LTS defines the mapping between BMM layer to the physical layer.LTS will correspond to physical table definitely. For e.g. the tables dim-time and dim-products can correspond to multiple physical tables but one LTS corresponds to one physical table.

• Logical tables can, and routinely do, have many physical table sources. For e.g. revenue information may come from multiple data sources like for e.g., manually entered spreadsheet in a business.

• A single logical column can map to many physical columns from multiple physical tables including aggregate tables.

• You may have three different business units (each with its own order system) from which you get the revenue information and each business unit revenues goes to different table.

LTS: Column Mapping

• Double-click a logical table source to open the LTS dialog box

• Click the column mapping tab to build, view, or modify logical-to-physical column mapping

• A mapping can be used to specify transformations that occur between the physical layer and the BMM layer

  • The transformations can be simple, such as changing integer datatype to a character type

  • The transformations can be complex, such as applying a formula to find a percentage of sales per unit of population.

• The data type of a logical column is determined by its logical table source mappings.

• To map logical columns to physical columns

• In BMM layer of the Admin Tool, double –click LTS.

• The logical column can also be mapped to physical column. LTS relates to one physical table while one logical column relate to one or many physical columns.

• Logical columns can be created automatically by dragging tables from the physical layer to the BMM layer

• You can manually create logical columns that involve calculations based on other logical columns. To create a logical column manually, right-click a logical table and select New Object->Logical Column

• A single logical column may map to many physical columns in the physical layer. For example, a logical column may map to both physical column in a detailed table and a physical column in aggregate table

Logical Primary Key

After creating tables in the Business Model and Mapping layer, you specify a primary key for each dimension table. Logical dimension tables must have a logical primary key.

• Logical primary keys define unique identifiers for logical tables. For a business model to be valid, each logical dimension table must have a logic primary key.

• Logical fact table do not require keys for a business model to be valid. Logical primary keys consist of one or more logical columns.

• The logical key defines the lowest level (most detailed level) of information of any source in the logical table.

• After creating tables in the BMM layer, you can manually specify a primary key for each table by right-clicking the table and selecting New Object->Logical Key, or double-clicking a table and clicking the key

• Every logical column should have unique key otherwise the rpd will be invalid. Because everything is logical and nothing exists physically then it will be difficult for OBIEE server to identify the granularity and joint condition index.

Logical Joins

• Logical joins express the cardinality relationships between logical tables and are a requirement for the valid business model.

• Specifying the logical table joins is required so that Oracle BI server has the necessary metadata to translate logical requests again the business model into SQL queries against the physical data sources.

• Logical joins help Oracle BI server understand the relationships between the various pieces of the business model.

• Creating Logical Joins

In OBIEE10g there are two types of joins namely simple join and complex join. Simple join is used for physical tables whereas complex join is used for logical tables.

1. Click the New Join button on the Administration Tool toolbar:

2. In the Business Model Diagram, left-click the first table in the join (the table representing many in the one-to-many join) to select it.

3. Move the cursor to the table to which you want to join (the table representing one in the one-to-many join), and then left-click the second table to select it.The Logical Join dialog appears.

4. To specify a driving table for the key, select a table from the Driving table list, and an applicable cardinality.

Measures

Measures are the facts that a business uses to evaluate its performance in a business model.

A measure column is a logical column with an aggregate function. Any column with an aggregation rule is a measure. Examples include Revenue or Units Sold.

Measures need to be defined in a logical fact and to be computed correctly from the base physical data when Oracle BI server receives a logical query from end-user tool.

{jcomments off}

SUMMARY

This section explains how to use the Oracle BI Administration Tool to create, edit, and maintain objects in the Presentation layer of the Oracle BI repository.

This section contains following topics:

• About the presentation layer

• Working with Subject Areas

• Working with Presentation tables and columns

Presentation layer

• The presentation layer provides a way to present customized, secure, role-based views of a business model to users.

• The presentation layer is built after the physical layer and the business model and mapping layer and adds a level of abstraction over the BMM layer.

• It is the view of the data seen by the end users so that the business users create reports according to that.

• In the presentation layer we don’t want to show few of the attributes in the BMM layer like key columns.

• It is important in BMM layer to define the key but for an end user it is not required. So you can hide key columns or recognize the data into presentation views (catalogs) and folders depending on the user requirement.

• Simplifying the view of the data for users makes it easier to craft queries based on their business needs thus making it user friendly.

• Proper naming conventions are provided in the presentation layers.

2. Subject Area

Subject areas (formerly called presentation catalogs) allow you to show different views of a business model to different sets of users.

Subject areas have to be populated with content from single business model. They cannot span business models.

Multiple subject areas can refer to the same business model.

Base measure is something which directly maps to the physical layer attribute. Calculated measure is the calculations performed on the BMM layer.

The existing subject area and its corresponding business model can be duplicated.

3. Presentation Tables

• Each subject area has the presentation table containing multiple presentation columns from one or more logical tables.

• Use presentation table to organize columns into categories that make sense to business users

• The names and object properties of the presentation tables are independent of the logical table properties.

4. Presentation Table Operations

Creating Alias Name

Each presentation object can have list of aliases for its name that can be used in logical SQL queries. To create the list of aliases, use the Alias tab for the appropriate presentation object.

When you change the name of a presentation column, an alias is automatically created for the old name, so the compatibility of the old name is preserved.

Note: You cannot rename a presentation layer object to a name that is already in use as alias for an object of the same type

5. Presentation column

Presentation columns define the columns that are used to build analyses in the Oracle BI interface.

When presentation columns are dragged from the BMM layer, presentation column names are, by default, identical to the logical names in the BMM layer.

To provide a convenient organization for your end users, you can drag a column from a single logical table in the BMM layer to multiple presentation tables.

Caution: When you drag columns to a presentation tables, make sure that the columns with the same name or an alias of the same name do not already exist.

1. Presentation column operations

To delete columns

To rename columns

To reorder columns

6. Presentation Layer Mappings

Presentation layer objects map to objects in the BMM layer.

Subject areas map to business model, presentation tables typically map to logical tables, and presentation columns map to logical columns.

7. Connection between UI and Presentation Layer

The UI and presentation layer are close in execution and are related with each other. The User Interface shows you the data once the presentation layer has done any translation it needs to.