Oracle General Ledger Standard

Sl Business Process - Standard Features

MULTI-ORG ACCESS CONTROL (MOAC)
1 Accounting Setup Manager
2 Sub Ledger Accounting (SLA)
3 Enhanced Foreign Currency Processing by Reporting Made easy
4 Creating foreign currency recurring journals
5 Data Access to Multiple Legal Entities and Ledgers
6 Simultaneous Opening and Closing of Periods for Multiple Ledgers
7 Simultaneous Currency Translation of Multiple Ledgers
8 Financial Reporting for Multiple Ledgers
9 Cross-Ledger and Foreign Currency Allocations
10 Streamlined Automatic Posting
11 Streamlined AutoReversal Criteria Setup Integrated Web-based
12 Journal Copy
13 Replacement for Disabled Accounts
14 Data Access Security for Legal Entities and Ledgers
15 Prevent Reversal of Journals with Frozen Sources
16 Prevent Reversal of Unposted Journals
17 Control Accounts
18 Enhanced Financial Statement Generator Reporting to Display Content
Set Values
19 Enhanced Financial Statement Generator Reporting to Support Drill-
down for Non-Contiguous Account Ranges
20 Streamlined Excel-based Financial Statement Publishing
21 Synchronize Reversing Journals between Primary and Secondary
Ledgers
22 Limit Accounts in Budget Wizard
Oracle General Ledger Standard Features Differences between 11i and R1
11i
In 11i, when users had to enter or process data for multiple operating units, they
had
Exist with the name “Set of Books”. The ledger replaces the 11i concept of a set of
Books.
GL was not integrated with SLA.
Features mentioned in R12 were either not available or available with a limited
extent
In in 11i.
Release 11i, you could define recurring journals using the functional currency or
STAT
This feature was not available in Release 11i.
This feature was not available in Release 11i.
This feature was not available in Release 11i.
This feature was not available in Release 11i
This feature was not available in Release 11i
This feature was not available in Release 11i
Integrated Web-based Spreadsheet Interface was not available in Release 11i
This feature was not available in Release 11i
This feature was not available in Release 11i.
This feature was not available in Release 11i.
This feature was not available in Release 11i.
This feature was not available in Release 11i.
This feature was not available in Release 11i.
This feature was not available in Release 11i.

This feature was not available in Release 11i.

This feature was not available in Release 11i.

This feature was not available in Release 11i.

This feature was not available in Release 11i.

 R12
Now in Release 12, Multi-Org Access Control enables companies
that have
The ledger is a basic concept in Release 12.
GL is integrated with SLA to enable a unified process to account for
subledger
GL has added transactions
new featuresand postand data
enhanced existing features to
support
In Releaseforeign
12, you currency processing.
can create recurring Theyjournals using foreign
currencies.
You no longerThishaveis particularly
to constantly useful if you
switch responsibilities in order to
access the data in a different ledger.
You no longer have to open and close periods for each ledger
separately.
You can runYou the can now open
Translation and close
program for multiple ledgers
simultaneously,
Now if you you
with this feature are managing multipleStatement Generator
can run Financial
(FSG)
You arereports
able tofor multiple
allocate ledgersdata from one or more ledgers to a
financial
different
You can now share AutoPostenables
target ledger. This Criteria sets across multiple ledgers
that share the same chart of accounts
AutoReversal Criteria Sets can also be shared across ledgers to
reverse
Now wejournals
can copy across
entiremultiple
journal ledgers.
batches. You can copy journal
batches with
Normally whenanyanstatus.
accountTheissystem
disabled,willyou can prevent transactions
that include the account from
In R12, since you can access multiple legal entities and ledgers when
you
Youlog caninto Oraclereverse
no longer Generaljournals
Ledger from frozen sources defined in
the journal
You also can sources
no longerform.reverse
If the journal
unposted journals. This ensures data
integrity
You and better
are able auditdata
to control ability.
entryInto an account by ensuring it only
contains data from a specified
Users can now publish a Financial journal
Statement Generator (FSG) report
with a content set. When the Page
Expand
General option
Ledgerisprovides
selected,a each value indrill
streamlined the path
content setthe
from becomes
monetary
visible as an individual
amounts in financial statements totab in the Microsoft Excel workbook.
the
Usersunderlying
can now detail
publish balances.
FSG reports Afternatively
runningas a FSG
Excelreport, users can
files. Users can
drill from any
create presentation
Oracle summarized
General Ledger templates financial
using
now streamlines balance
the propagation of journalto
in the report directly
the detail account balances
reversals from the primary ledger to that comprise the summary amount, even
if
thethe summary
associated amount
secondary represents
ledgers. multiple non-contiguous account
In prior releases, users could onlyTheuse manual
specific reversal
account of primary
code
ledger journal ranges
combinations entriesin now
theautomatically
Oracle General reverses the corresponding
journal entries in the secondary ledger.
Oracle Payable Standard Features Differences between 11i and R12
Sl Business Process - Standard Features
1 Few Features like invoice Lines, Line level approvals, Matching to a PO
shipment or receipt, Suppliers in TCA makes a complete new look.
2 Invoice
3 Internal Bank Accounts
4 Suppliers Bank Accounts
5 Integration with Oracle E-Business Tax
6 Replace Supplier Bank Accounts on Invoices

7 Business Intelligence Publisher Support for Selected Payables Reports

8 Third Party Payments

9 Supplier Dispute Processing

10 Discount Calculation Enhancements

11i
• Suppliers defined in AP.
• Supplier contacts replicated for each supplier site.
• Had only distributions line.
In 11i we have seen internal Banks defined in AP and that is shared by AP/AR/CE, Payroll and
• Banks/Branches defined in AP
• Oracle standard functionality was based out of User which determines tax by assigning Tax
 efined in AP.
ontacts replicated for each supplier site.
istributions line.
ve seen internal Banks defined in AP and that is shared by AP/AR/CE, Payroll and
nches defined in AP
dard functionality was based out of User which determines tax by assigning Tax
 R12
• Supplier becomes as TCA Party.
• Suppliers Sites as TCA Party Site for each distinct address.
•Invoice
Contacts for as
Lines each supplier/address
a new , itaccommodated
additional line means Single supplier address
in Invoice and contact
data model canof
Because beintroduction
leveraged byof
multiple
invoice
Where as sites,
line for
in there each OU
R12, is significant improvement of data flow with n other oracle modules like
• Suppliers, Banks and Branches are defined as Parties in TCA
• A new module eBusinessTax determines tax based on facts about each transaction, this is
In today’s business environment, it is a common practice to change bank accounts. If
suppliers change their bank accounts, Oracle Payables can now automatically update all unpaid and
partially paid invoices with the new bank account information. When users end date an existing supplier
bank account and provide a new active bank account, Oracle Payables will automatically update the
remit-to bank account information on unpaid and partially paid invoices. This streamlines transaction
processing and prevents the need to update each invoice manually.

The following Oracle Payables reports have been re-written utilizing the Business Intelligence Publisher
(BIP) tool. BIP based reports offer greater flexibility to end users in changing report layouts and formats:
• Withholding Tax by Invoice Report
• Bills Payable Maturity Date Report
• Discounts Available Report
• Payment Audit by Voucher Number
• Prepayments Status Report

Suppliers can specify a related trading partner to be paid on their behalf. The payments made on behalf of
suppliers to other trading partners are termed as third party payments. Oracle Payables has been enhanced
to record third party relationships and to process third
party payments. Withholding and 1099 processing continue to occur for invoicing suppliers.
Supplier invoices may be short paid to expedite dispute settlements. The Payables Invoice Workbench
has been enhanced to capture the invoice amount originally claimed by the supplier and the reason for
short payment.
Suppliers offer discounts for early payment. Early payment discounts can be fixed monetary
amounts or calculated on a percentage basis.
In prior releases, discounts could be defined in percentage terms only. Oracle Payables now allows
discounts to be specified in monetary amounts. When a percentage as well as an amount is available, the
higher or lower of the two can be specified for application.
 Oracle Receivable Standard Features Differences between 11i and R12
Sl Business Process - Standard Features 11i
1 Revenue Recognition Only Rule based Revenue Recognition exists in
11i.
2 Global Architecture Limited integration of E-Business Tax module
3 Enhanced Customer Screen withhave
We Oracle Receivables.
seen 11i Customer standard forms
4 Refunds makes easier
Limited by simple
integration withnavigation. This times
Oracle Payables.
5 Late Charges there is
Does not exist.
6 AP AR Netting Contra Charges functions available in the 11i.
en 11i and R12
R12
In R12 revenue recognition is based on Rules and
Events, and they are:
• EBusiness Tax - Oracle E-Business Tax is a
new AR
The product thatCustomer
Create uniformly delivers
page taxhas
in R12 services
to all Oracle
eliminated
Oracle EBusiness
the navigation
Receivables Suite business
is fullytointegrated with In
flows.
separate windows.
Release
Now,
Oracle
With new 12,changes
users can specify
Payables to these the
deliverareafollowing
seamless,
the on a single
automated
enhanced
page:
process to generate
functionality:
In R12 the check and
Contra Charge bank account
functionality has been
transfer refunds
optimized and therefore changed into the AP/AR
Netting functionality. In the Payables module as
well as the Receivables module, there is a
Oracle Asset Standard Features Differences betw
Sl Business Process - Standard Features 11i
Fixed Assets tied with SLA(Sub Ledger Limited integration.
accounting)

What you will notice create

Journal Entries (FAPOST)
Enhancements In FA_MASS_ADDITIONS process
Does Notfeeding
exist. into
Table.

New Automatic Preparation of Mass Does not exist.

Additions

3
 Flexible Reporting into XML Publisher Does not exist.

Automatic Depreciation Rollback Since release 11i, users have been

able to run depreciation for an
asset book without closing the
5 period. If additional adjustments
are required in the current period,
then the user submits a process to
roll back depreciation for the entire
book, performs the necessary
 R12
• Oracle Assets is fully integrated with SLA, which is a
common accounting platform for Sub Ledgers.
• Customers can use the seeded Account Derivation definitions or
modify them as required.
• Continue to support Account Generator functionality for existing
Asset Books.
New SLA Accounting report and online account inquiry.

This is replaced with the Create Accounting – Assets

process (FAACCPB).
As a result of new enhanced feature, we can populate the values for the new
attributes directly in the FA Mass Additions interface table rather than accepting
default values from the asset category. Legacy conversion can be completely
automated.
Following are the new adds-on:
• Asset Life
• Depreciation Method
• Prorate Convention
• Bonus Rule Ceiling Name
• Depreciation Limit

• This new feature consists of default rules and Public APIs that can be used by
customers to complete the preparation of mass addition lines automatically.
o Auto populate required fields such as Expense Account, Asset Category etc.
o Avoid manual intervention during the Mass Additions prepare process
o Avoid customization and use public APIs to effect custom business logic.
• Assets now uses Flexible Reporting using XML publisher
o Major Asset Transaction reports have been modified to support XML publisher.
o Users can modify or use new templates to view report output
These asset reports have been converted in XML Publisher
based reports:
• Create Accounting Assets
• Transfer Journal Entries to GL Assets
• Journal Entry Reserve ledger Report
• Asset Additions Report
• Asset Transfer Report
• Asset Retirement Report
• Transaction History Report
• Asset Reclassification Report
• Mass Additions Create Report
• Mass Additions Posting Report
• Cost Adjustment Report
• Cost Detail report
• Cost Summary Report
• Reserve summary Report
• Reserve Details Report
• Mass Revaluation Preview Report
• Revaluation Reserve Details Report
• Revaluation Reserve Summary Report
• CIP Capitalization report
• CIP Detail Report
• CIP Summary Report

Depreciation is rolled back automatically by the system when any transaction is

performed on an asset if the following conditions are met:
• Depreciation has been processed in that period
• The period is not closed
In Release 12 the intermediate manual step of rolling back depreciation for the
entire book in order to process further adjustments on selected assets is no longer
necessary
Cash Management Standard Features Differences between 11i and R12
Sl Business Process - Standard Features 11i
1 Banks These are tables which ho
the bank details irrespectiv
of supplier or internal ban
• ap_bank_branches
• ap_bank_accounts_all

2 Comparing the 11i Vs R12 We can notice the bank w

3 International Bank Account Number (IBAN) utilized
Does notinto three
exist differen
in 11i.

4 Bank Identifier Code (BIC) Does not exist in 11i.

5 Payment Group based Bank Statement Reconciliation Does not exist in 11i.

6 Option to Override Country-Specific Validation for Bank Accounts Does not exist in 11i.

7 EDIFACT Bank Statement Format Update Does not exist in 11i.

8 Copy Bank Transaction Codes Does not exist in 11i.

9 Load Bank Statements for the Current Day Does not exist in 11i.

10 Manual Entry in Cash Position Does not exist in 11i.

11i
These are tables which hold
the bank details irrespective
of supplier or internal banks.
• ap_bank_branches
• ap_bank_accounts_all

We can notice the bank was

utilized
Does notinto three
exist different
in 11i.

Does not exist in 11i.

Does not exist in 11i.

Does not exist in 11i.

Does not exist in 11i.

Does not exist in 11i.

Does not exist in 11i.

Does not exist in 11i.

 R12
These changes make easier and more reliable by
• Single access point
• Single Legal Entity ownership
• Usage rights granted to one or more Organizations o Reconciliation option defined at
Bank Account level
o More flexibility and control

These issues has been resolved in R12 release.

International Bank Account Number (IBAN) is an international standard for
identifying bank accounts across national borders in a way that would minimize the risk
of propagating transaction errors. Cash Management now validates IBAN at the time of
recording bank account details.
Bank Identifier Code (BIC) is a unique identification for bank branches. This
code can be 8 or 11 characters in length. Cash Management now validates the length of
BIC when recording bank branch details.
Oracle Cash Management now utilizes the new Payment Group Number
attribute as an optional matching criterion for manual and automated reconciliation of
bank statements.
Sometimes legacy bank account numbers do not conform to modern
country-specific validation rules. Users can now disable the default country- specific
bank validations to migrate legacy bank account information.
The bank statement loader program supports EDIFACT statements. With
this release, the following additional data processing features are addressed:
• Support for non-numeric characters in bank balances. The opening and closing
balance amounts sent in the EDIFACT statements contain non- numeric characters. The
bank statement loader and import program is enhanced to convert the non-numeric
characters into numeric values.
• Support loading and importing the Record 05. The current seeded loader is enhanced
to handle the record type 05. This additional record is defined as part of the EDIFACT
standard and contains the contextual information of Record 04.

Bank transaction codes are used by banks to identify the types of

transactions on bank statements. The codes are set up for each bank account for
reconciliation purposes. For organizations having several bank accounts, it can be a
cumbersome process to manually setup these transaction codes since most bank
accounts for a specific bank use the same transaction codes. A new concurrent program
has been provided to copy the bank transaction codes from one bank account to another
bank account(s).

In previous releases, users could only import bank statements and perform
bank balance maintenance for past dates. Users can now enter or import bank
statements and perform bank balance maintenance for the current date.
The cash position functionality has been enhanced to allow cash managers
the ability to manually enter cash flows into their cash positions allowing for greater
flexibility in their decision making process.