PAYABLES

AGENDA
1. Overview
2. Supplier Added to Trading Community
Architecture
3. Invoice Line
4. Centralized Bank and Bank Accounts
5. Integration with Oracle E-business Tax
6. Multiple Organizations Access Control

Overview
In Release 12, the Oracle E-Business
Suite introduces Subledger Accounting,
E-Business Tax, Ledgers, Banks and
other common data model components
that are used by Oracle Payables.

SUPPLIER
11i

R12

Suppliers defined in AP.

Supplier becomes as TCA

Party

Supplier contacts replicated for

each supplier site.

Suppliers Sites as TCA Party

Site for each distinct address.

Contacts for each

supplier/address , it means
Single supplier address and
contact can be leveraged by
multiple sites, for each OU

Comparison between 11i & R12

Defining Supplier
Through Web based Application

Quick Update
Company Profile
Terms and
Control

Suppliers in Trading Community

Architecture
Payables
Purchasing

Suppliers

Payments

Global Tax

Geographies

Party
Information

Cash
Management

Banks and
Branches

Trading
Community
Architecture
Oracle Fusion Middleware
ERP

CRM

3rd Party

Diagrammatic view of Supplier Contact with respect to OU

11i

R12

INVOICE LINE
11i

R12

Had only distributions line .

Allocation of freight and

special charges are captured
at the distribution level only .

Invoice Lines as a new

additional line accommodated
in Invoice data model.

Allocate freight and special

charges are captured to the
lines on the invoice

Invoice distributions created at

the maximum level of detail
similar to 11i.

Tax payment and Project

accounting Payment was
captured through global
Descriptive Flexfields .

View Comparison Between

11i&R12
11i
R12

Operating Unit

Invoice
Lines

Invoice Lines and Enhanced Asset

Asset Tracking
Tracking
Info.

Invoice Lines are introduced as an entity between the invoice header and
invoice distributions in order to better match the structure of invoice
documents and improve the flow of information like manufacturer, model,
and serial number from Purchasing through to Assets.

Bank Accounts
11i

We have seen internal

Banks defined in AP and
that is shared by
AP/AR/CE, Payroll and
Treasury and they are
bank accounts often
replicated in multiple
Operating Units.

R12

Bank and Branch become

part of TCA Parties.
Internal Bank Account in
Cash Management which
is owned by a Legal
Entity. Here the
Operating units have
granted by usage rights.

View Comparison Between 11i & R12

11i

R12

TAX

11i
Oracle standard functionality was
based out of User which
determines tax by assigning Tax
Codes at line level of invoice and
Tax rules was controlled at
underline code.

The global descriptive flex fields

were captured for country-specific
tax attributes

R12
A new module E-Business Tax
determines tax based on facts
about each transaction, this is
reason why Oracle has introduced
additional line information at
invoice level.

The module E-business Tax set

and configure Tax rules which can
be viewed.

Tax attributes collected in fields on

key entities

Configure tax rules once per

regime and share with your legal
entities.

Multi Org Access Control

This feature enables user to access data from one or
many Operating Units while within a set given
responsibility. Due to this change, all processing and
some Reporting in Oracle Payables is available across
Operating Units from a single Applications responsibility.
Hence you can isolate your transaction data by Operating
unit for security and local level compliance while still
enabling shared Service center Processing.Data security
is maintained using the Multiple Organizations Security
Profile, defined in Oracle HRMS, which specifies a list of
operating units and determines the data access privileges
for a user.

Access Comparison Between 11i&R12

In 11i performing multiple

tasks across operating
units requires changing
responsibilities.

Where as in R12 we can perform

multiple tasks across operating
units without changing
responsibilities.

THANK YOU