Fusion Applications to E-Business Suite Security Mapping

Fusion Applications to E-Business Suite Security Mapping

For some one who is starting to work on Fusion Applications moving from E-Business Suite, initially they may feel it hard to relate to the security components of E-Business Suite to Fusion Applications.

How to relate to E-Business Suite security components to Fusion Applications security components.

By relating it should make the work a bit simpler as the foot print of E-Business Suite is huge part of Applications Unlimited series and Fusion Applications is the latest enterprise applications offering with the use of best of the technologies.

Following Table will give you an insight on how to map Fusion Applications related security components to E-Business Suite security components.This is an effort to give an overview of components which were seen in E-Business Suite to their corresponding equivalents in Fusion Applications.

Oracle Fusion Applications	E-Business Suite
Data Role	Responsibility
Job Role	Top Level Menu
Duty Role	Sub Menu
Privilege	Form Function
Data Security	Form Function
Permission	Executable

Difference Between R12 General Ledger Calendar Definition And Fusion General Ledger Calendar Definition

Difference Between R12 and Fusion General Ledger Calendar Definition

Oracle Fusion General Ledger is a product of Oracle Fusion Applications.This document details out the difference between Oracle EBusiness Suite R12 and Oracle Fusion General Ledger Calendar Setup helping you to better understand the differences.

Calendar Setup Steps in R12 E-Business Suite

Calendar setup is a two step process in E-Business Suite

1) Define Period Types

2) Define Accounting Calendar using the Period Type defined in the earlier step

Once you define your calendar and navigate out of the Accounting Calendar setup screen the Calendar Validation Report will be submitted with an option to validate the current calendar or all the defined calendars.

Calendar Setup Steps in Oracle Fusion General Ledger

Calendar setup in Oracle Fusion General Ledger is a much more simplified process which combines both the steps of Accounting Calendar definition in a single setup flow.

Below screen shots would give an overview of the setup process of Accounting Calendar. Accounting Calendar is available under Define Calendars Task list as Manage Accounting Calendars Task

Click on the Manage Accounting Calendars Task which will take you to the Accounting Calendar setup screen.

This is a simplified screen where you define the details of your Accounting Calendar and default options are provided for making it easy to define calendars based on frequently used period frequency and adjusting period frequency. In case more flexibility is required period and adjusting frequency can be chosen as Other.

Once you fill up the other details then click Next to go on to the screen where you define the period details for your calendar.

After defining the required periods for your calendar you can save the changes. This will fire the calendar validation for the period ranges defined for any overlap of period date ranges and gaps in the period date range definition.

The tables affected while defining calendar in E-Business Suite and Oracle Fusion General Ledger are the same: GL_PERIOD_TYPES for the calendar type definition, GL_PERIOD_SETS for the calendar name details and GL_PERIODS for the individual period details in the calendar.GL_DATE_PERIOD_MAP stores the correlation between dates and non-adjusting periods for each accounting calendar and period type combination.

Details which are entered in the first screen in Fusion Calendar definition like the frequency,adjustment periods etc are stored in GL_CALENDARS a major table addition in Fusion.Also addition of an ENTERPRISE_ID column in Oracle Fusion General Ledger for GL_PERIODS table which provides the Business group details available.

The significant difference between the Accounting Calendar definitions in E-Business Suite and Oracle Fusion General Ledger is that, in Fusion, the definition is greatly simplified.  Fusion General Ledger provides the flexibility of default calendar templates for period frequency (ie Monthly) and online calendar validation while saving the calendar details

For further table related details in Fusion Applications can refer to Fusion Applications OER

Key Payment Terminology in Oracle Payables

Key Concepts related to Payments in Oracle Payables

This post gives a brief overview on the key concepts related to payments which were added in Payables starting from R12 and similarly carried over to Fusion Applications.

Someone who would have worked on 11i Payables could be confused on seeing these terms and concepts used.But once we get the specific understanding on the same it would very easy to relate to on the payment.

Key terms can be summarized as follows:

i) Document Payable

ii) Payment Process Request ( sometimes abbreviated and referred to as PPR)

iii) Payee

iv) Payment Instruction

v) Payment Process Profile

vi) Payment Process Request Template

vii) Payment Format

viii) Payment Method

Let us discuss in detail about the above mentioned terms

Document Payable

A document which is to be paid by a company/organization through payables.This company/organization would generally be referred to as Payer.Examples which could be used from the documents which we create in Payables is a Payables Invoice or Scheduled Payment of the invoice.

Payment Process Request

It is a process by which group of invoices are selected and paid ie. processed for payment.This is similar to 11i Payment Batch, it is famously abbreviated as PPR and also referred to a Pay Run.So if any one is using the term Pay Run or PPR in reference to payments they are referring to Payment Process Request.Well as the name suggests technically PPR is a request raised from a source product to Oracle Payments.So PPR which is initiated from the source product during the invoice selection process contains many documents payable to be paid.During the course of the payment process life cycle these documents payable in payment process request are built into payments.

Payee
Well Payee is nothing but an organization/company/person which is being paid.Supplier,Customer or Employee are examples to whom payment is made.

Payment Instruction
Payment instruction is a collection of payments which have the payment information that is formatted.Payment instruction can be printed on to checks or a file which is transmitted to a payment system for processing and disbursement.

Payment Process Profile
Payment Process Profile is a payment attribute which is assigned to a document payable, having the information on handling of documents payable,payments and payment instructions.
Payment Process Profile has instructions on payment information formatting and transmission.

Following information is available on payment process profile:

• Payment instruction formatting information
• Transmission information
• Payment grouping
• Payment sorting details
• Payment limits

Payment Process Request Template

This template is like a blueprint that simplifies and expedites pay runs by preselecting applicable payment data like the header information,payment selection criteria, processing instructions and how validation failures are handled.

Payment Format

Payment format is a set of instructions/rules that specify on how payment instruction is formatted and converted into a format which is readable by payment system.These are registered and maintained in Oracle XML Publisher in R12 whereas maintained in BI Publisher in Fusion Applications.

Payment Method

Payment Method is an attribute which is attached to a document payable which indicates on how a payer makes a payment to payee (supplier,employee or customer).Example are checks, wire transfer etc.