Oracle Accounts Payables R12 New Features

Major initiatives enhancing Payables in R12:

 SLA - Sub-ledger Accounting
 Enchanced TCA model
 Multi-org Access Control - MOAC
 New Payments and Bank Model
 Ebusiness Tax
Sub-legder Accounting (SLA)
 Centralized accounting engine and data model
 Full drill down capabilities
 Draft and Final accounting from the invoice workbench. (You can accept create post
accounting from the invoice workbench.)
TCA is a centralized data model:
 TCA is now part of the supplier integration
 You can also use the geographically within TCA to validate and calculation tax based on the
hierarchy.
Oracle Payments
 Stores all of the payments related to a party
 Centralized bank model
 Centralized payment model
 Complete payment and receipt processing engine
 Supports multiple tranmission protocols
 Payment batch can pay across ou's
 Ability to configure as many payment methods as required based on rules
 Enhanced disbursement process
E-business Tax
 Tax is not longer based on tax codes
 A tax simulator we allow you to confirm the rate/setups
 Self-service for tax managers
Payables Module enhancements:
 Invoice lines table is added to join with invoice distributions
 Track complex contracts execution (used for large projects.)
 It will account for any advances when trying to Pay an invoice. (Research how this is different
from AR/AP netting.)
 Also handles any retainer amounts entered into the applications.
 Workflows are atvailable to handle hold dispues
Reference: Oracle OpenWorld 2008 Session: Accounts Payables Get a Makeover in R12
Oracle Accounts Receivables R12 New Features

1. Revenue Recognition
In R12 revenue recognition is based on Rules and Events, and they are:
 Time-Based Revenue Recognition
 Ratably Over Time
 Upon Expiration of Contingencies
 Event-Based Revenue Recognition
 Payment
 Customer Acceptance
 Rule-Based Revenue Recognition
 Payment Term Thresholds
 Refund Policy Thresholds
 Customer Credit worthiness
2. Global Architecture
As we know, with in global architecture , these new things has
been introduced.

 Sub ledger Accounting - Journal Creation takes place

prior to GL.
 Bank Model - This unified model enables to park
customer Bank as well as Internal bank information
into there new model, so that working capital cash
flow should be enhanced.
 EBusiness Tax - Oracle E-Business Tax is a new product that uniformly delivers tax
services to all Oracle EBusiness Suite business flows. In Release 12, Receivables is
enhanced to support
integration with the E-Business Tax product.
 Intercompany - This is enhanced by automatic balancing,

3. MOAC Control
This enhance you by enabling and performing
tasks across operating Units (OUs), where you
have access to without changing
responsibilities.As we know , MOAC enables
companies that have implemented a Shared
Services operating model to efficiently process
business transactions by allowing them to access,
process, and report on data for an unlimited
number of operating units within a single applications responsibility.

In nutshell, once MOAC is enabled, then you can:

 Perform Setups for any OU

  Enter invoices across OUs
 Receive Cash for any OU
 Manage Customer Credit across all OU
 Run reports across OUs

Because of this greatly enhanced Role based security options, the ability to access multiple
operating units with a single responsibility can simplify SOX compliance monitoring from
finance controller side.

4. Line Level Cash Applications

The Line Level Cash Applications solution allows the application of receipts to specific
transaction items
such as individual
lines, groups of lines,
or tax or freight
buckets. From the
receipt
workbench,you are
able choose whether
to allocate cash to the
entire transaction or
to apply amounts
against specific items
according to the
customer remittance.

 Apply to specific lines or groups of lines

 Indicate when tax, freight or finance charges only are paid
 Make changes as needed
 Easily view activity against receipts
 Know what historical activity affects your receipt
 See what prior activity affects a new application

5. Enhanced Customer Screen

We have seen 11i Customer standard forms makes easier by simple navigation. This times
there is clearer separation of the party and account layers, which makes a consist ant look
and feel.More over full backward compatibility with 11i UI Bill Presentment Architecture
has been provided.

The AR Create Customer page in R12 has eliminated the navigation to separate windows.
Now, users can specify the following on a single page:

 Customer Information
 Account Details
 Address
 Account Site Details
 Business Purpose
6. Refunds
Oracle Receivables is fully integrated with Oracle Payables to deliver a seamless,
automated process to generate check and bank account transfer refunds for eligible receipts
and credit memos.

7. Late Charges
As we know oracle receivables delivers enhanced Late Charges functionality enabling the
creation of standard late charge policies that can be assigned to customer accounts or
account sites.Flexible policy configurations include multiple interest calculation formulas,
transaction and account balance thresholds, and currency-level rate setups. With new
changes these are the enhanced functionality:

 Expanded assessment and calculation capabilities

 Tiered charge schedules
 Penalty charge calculation
 Integration with Balance Forward Billing
 Centralized setup and maintenance of late charge policies
 Calculation performed independent of Dunning and Statement processing

8. AR-AP Netting
The matching of open receivables and open payables is automated.

9. Balance Forward Billing

This makes easy transaction processing.

Balance Forward Billing is an enhanced version of the existing consolidated billing

functionality for industries where customers are billed for all their account activity on a
regular, cyclical basis.

Balance Forward Billing provides the ability to setup cycle-based billing at the account or
account site levels, enable event based billing, and leverage user configurable billing
formats provided by Oracle Bill Presentment Architecture.

A typical case can be best understood as

 Payment Term defaults

 from Site profile if Bill Level = Site
 from Account profile if Bill Level = Account
 Billing Date derived from transaction date and billing cycle
 Due Date derived from billing date and payment term
 Optionally select non-Balance Forward term if Override Terms = Yes

Oracle Cash Management R12 New Features

I. Bank Account Balances and Interest Calculations:

In prior releases, bank account balances were only available as a part of the bank account
statement. The bank account interest calculation was only available for bank accounts set up in
Treasury. In Release 12, the functionality to keep track of the multiple bank account balance
types and calculate accrued interest is available to all internal bank accounts set up in the
centralized bank account model.

Not only can you enter the balances manually, but also you can import them automatically at
the same time when the bank statement is imported. In addition to the actual historic balances,
you can keep track of the projected balances. Such balances can be entered manually or copied
over from the Cash Position. You can then create reports that will compare the actual balances
versus projected, and you can accomplish it in either an onscreen report or via XML Publisher.
Finally, to simplify the bank account interest calculation, you can create reusable interest rate
schedules that will contain the interest rates and other interest calculation parameters. Interest
calculation features will work not only for stand-alone bank accounts but also for the notional
cash pools as well.

Bank Account Balances and Interest Calculations - Benefits:

The new bank account model allows you to view bank account balances independent of the
bank statement, calculate accumulated interest on the fly, and create customized balance
reports.

Bank Account Balances and Interest Calculations Maintenance:

Once you have defined your bank accounts in the centralized bank account model, query them
in the bank account balance page and manage historical or projected amounts.

Bank Account Balances and Interest Calculations Setup:

To obtain a balance report, create a report layout or a view and generate a report based on that.
To calculate interest on the bank account balance, create the interest rate schedules, tie them to
the bank accounts and use the interest calculator page to view the accumulated interest.

II. Bank Account Transfers:

In Release 12, you are able to create bank account transfers in Cash Management. The transfers
can be initiated, approved, settled and accounted for. The settlement is done through the
Payments application, while the accounting is done though the Subledger Accounting engine.

Bank Account Transfers Description:

Bank Account Transfers can be created manually by the user in the system. In addition, if there
are any physical cash pools defined in the system, the transfers can be created automatically
when the cash leveling process is run or when a bank statement with ZBA sweep lines is
processed.

With manual transfers, you have the option of creating and using a payment template. The
template will default the transfer information, such as the source and destination bank accounts,
currency, and payment method, and can be used in the same fashion as a repetitive or semi-
repetitive wire template created by your bank.
In cases when the settlement of the bank account transfer does not have to be initiated by the
system (for example, for ZBA bank account transfers that the bank processes on its own), there
is an option to exclude such a transfer from the settlement process and only create the
accounting entries.

Finally, the UMX security model lets you define who can create bank account transfers for
which legal entities. The settlement authorization function is also separate from the transfer
creation, so you can implement the separation of duties for bank account transfer management.

Bank Account Transfers - Benefits:

The bank account transfer functionality enriches the Cash Management functionality so that you
could take action on the projected closing balances calculated by the system. The seamless
integration with the Payments application allows you to send payment instructions to the bank
in a variety of payment formats and the integration with the Subledger Accounting allows you
to use flexible journal creation rules.

Bank Account Transfers Process:

•Responsibility: Cash Management
•Navigation: Cash Management > Bank Account Transfers
Once the setup is in place, you can start creating the bank account transfer. If the system
parameter requires authorization, the bank account transfer must be authorized before it is
available for settlement or journal creation. Otherwise, you can proceed to settle or journalize
the bank account transfer immediately after creation and validation.

The Payments application formats your payment request and sends it to the bank. Any
exceptions in the payment process are communicated back in the form of an error status. If
settlement of the bank account transfer errors out, you can see the reason so that the cause of the
error can be rectified and the bank account transfer recreated. If the payment is processed
without any exception, you see a successful payment status returned.

The subledger accounting process creates journal entries according to your setup and you can
drill down to view these journal entries.

Bank Account Transfers – Dependencies and Interactions:

The bank account transfer feature depends on Payments application in cases where the
settlement of the bank account transfers is required. There is also a dependency on the
Intercompany setup when funds are transferred between different legal entities. Finally, all of
the accounting activity for bank account transfers happens in the Subledger Accounting
framework.

Bank Account Transfers Setup:

•Responsibility: Cash Management
•Navigation: Setup:System Parameters > (T) Cash Management Transactions
If you are using the cash leveling or ZBA features, the setup starts with the new system profile.
Then, optionally, you can set up Transaction Subtypes and Payment Templates for bank account
transfers. The Payment Templates are required if you intend to send the payment instructions to
the bank to process the bank account transfer. The Transaction Subtypes are optional and can be
used for reporting purposes.
Bank Account Transfers Setup – Set System Profile:
The new system profile option CE: Bank Account Transfers defines where the cash transfers
will be created as a result of the cash pool activity. If you choose Cash Management, then the
cash transfers created by the cash leveling or ZBA sweep activity are created in Cash
Management using the Bank Account Transfer framework. If you choose Treasury, then these
cash transfers are created in Treasury using Inter-Account Transfers (if both bank accounts
belong to the same legal entity) or Intercompany Funding transactions (if bank accounts belong
to different legal entities). Before Release 12, Bank Account Transfers could only be created in
Treasury. This functionality is preserved but now you have a choice.

III. Subledger Accounting:

Subledger Accounting provides a common flexible framework for creating journal entries for
Bank Account Transfers and Bank Statement Cash Flows in Cash Management. Prior to Release
12, Cash Management produced journal entries for bank statement activity based on simple
rules and sent them to the General Ledger interface. In Release 12, in addition to the bank
statement activity, a new source of accounting entries is available – bank account transfers –
and the rules for journal entry creation are more flexible and sophisticated. Finally, you can now
view all the journal entries produced by Cash Management events in Cash Management.

Subledger Accounting for Cash Management:

In Cash Management Release 12, bank account transfers and bank statement cash flows are the
two objects that can produce accounting events. Once the events are created and the accounting
program is run, the journal entry setup and the accounting configurations are referenced to
produce journal entries. The journal entries are then transferred to GL. GL has visibility into the
source transactions and Cash Management users can drill down from the transaction level to the
journal entry details.

Subledger Accounting - Benefits:

The Subledger Accounting feature allows multiple accounting representations for a single
business event, resolving conflicts between corporate and local fiscal accounting requirements.
In addition, with subledger accounting you retain the most granular level of detail in the journal
entries, with different summarization options in the General Ledger, allowing full audit and
reconciliation

Subledger Accounting Key Concepts :

Here are some key subledger accounting concepts:
•Event model is defined in SLA for each subledger represents the transaction/document types
and the lifecycle of each transaction:
-Event class classifies transaction types
-Event type defines possible actions on each event class with possible accounting significance.

The journal creation rules are defined per event class/event type. In Cash Management, there
are two event classes: Bank Account Transfer and Bank Statement Cash Flow. An accounting
event for a Bank Account Transfer, for example, would be the creation or cancellation of a bank
account transfer. So, any time a bank account transfer is created, an accounting event is created
as well. Based on the rule setup, there may or may not be a resulting journal entry. You may set
up rules to generate journal entries for some events, but not for others.
 Transaction object and sources are the data model for each subledger that contains the
transaction attributes/information made available to be used during journal rule setup and
journal entry generation.

Oracle Fixed Assets R12 New Features

Payables to Assets Integration

Payables now has a new level of detail between Invoice Header and Invoice Distribution. The new
level is Invoice Lines. At this new level, new field are available to enter details that will integrate to
Assets, these fields are:
• Manufacturer
• Model
• Serial Number
• Warranty Number
• Asset Book
• Asset Category

Event Accounting
Assets now has event accounting, meaning that every transaction is treated as a new event to the assets.
The impact on assets are as follows:
• Audit trail will no longer show voided transaction types if changes occur in the month an asset was
added.
• No longer forced to delete assets in the period it was added, due to the event accounting – Oracle
treats the addition and retirement as two separate events, so now Oracle allows assets to be retired in
the period added.
• Event accounting also allows for transferring accounting to GL multiple times in a period.
Auto Prepare Mass Additions
New APIs and Quick Codes are available to automate the Prepare Mass Additions process. There are
default rules available, you can accept the defaults or choose to create custom rules. These APIs and
Quick Codes will automatically process data and assign the required data attributes, such as:
Depreciation Expense Account
Asset Category
Default rules:

Asset Category – this is derived from the asset cost clearing account, as long as there is one to one
relationship between the account and asset category. This process will only impact items in the ‘New’
and ‘On Hold’ queue names.
Expense Account – this is derived from the clearing account combination and overlaying the natural
account segment with the value of the natural account segment of the depreciation expense defined in
the asset category. If the program cannot derive an expense combination, the queue name is set to ‘On
Hold’.
This should minimize the amount of manual efforts involved in the Prepare Mass Additions process.
Manual updating is still required – some required fields may not be populated.
Asset Category – a one to one relationship between cost clearing account and asset category – this will
expand the Chart of Accounts of many companies.
Expense Account – the expense combination is going to be derived from a Balance Sheet account.
Oracle will simply overlay the natural account segment, replacing the cost clearing account leaving all
other segment values alone. If there are certain requirements for P&L accounts versus Balance Sheet
accounts, i.e. cost center required for P&L, this may present issues.
Manual efforts are required to perform Merging, Splitting, Add to Assets and Merge then Split
functionality.
Auto Depreciation Rollback

In Release 12, you will no longer be required to run the Rollback Depreciation process in order to make
corrections to assets. After running depreciation when a correction or change is required, simply choose
the asset to modify. Oracle will automatically rollback depreciation for this single asset. Make your
modifications and when you re-run depreciation, Oracle will re-calculate depreciation based on the
modifications made to the asset.
The features to rollback depreciation and rollback journal entries that are in R11i are no longer
available in R12.
Month End Close

Create Accounting process is now used in Assets – journals are created not by a period, but by events
and a date. This means that one can create accounting on the 15th of a month for all transactions
performed at the end of the month. This allows for clients to view accounting prior to month end for
events that will greatly impact the books(i.e. mass retirements, transfers, etc.)

Oracle General Ledger R12 New Features

Accounting Setup Manager
The ledger is a basic concept in Release 12. The ledger replaces the 11i concept of a set of books. It
represents an accounting representation for one or more legal entities or for a business need such as
consolidation or management reporting. Companies can now clearly and efficiently model its legal
entities and their accounting representations in Release 12. This seems to be a major area in getting
success of the shared service center and single instance initiatives where many or all legal entities of an
enterprise are accounted for in a single instance, and data, setup, and processing must be effectively
secured but also possibly shared.
Now, legal Entities can be mapped to entire Ledgers or if you account for more than one legal entity
within a ledger, you can map a legal entity to balancing segments within a ledger.
While a set of books is defined by 3 C’s,
1. chart of accounts
 2. functional currency
3. accounting calendar,
The addition in this list the ledger is defined by a 4th C: the accounting method,
This 4th C allows you to assign and manage a specific accounting method for each ledger. Therefore,
when a legal entity is subject to multiple reporting requirements, separate ledgers can be used to record
the accounting information.
Accounting Setup Manager is a new feature that allows you to set up your common financial setup
components from a central location.
What is Accounting Setup Manager

Accounting Setup Manager is a new feature that streamlines the setup and implementation
of Oracle Financial Applications. The Accounting Setup Manager will facilitate the setup
required for simultaneous accounting for multiple reporting requirements.

With the Accounting Setup Manager, you can perform and maintain the following common
setup components from a central location:

 Legal Entities
 Ledgers, primary and secondary
 Operating Units, which are assigned to primary ledgers
 Reporting Currencies, which is an enhanced feature
 Subledger Accounting Options. This is where you define the accounting methods for
each legal entity subledger transaction and associate them to the ledger where the
accounting will be stored.
 Intercompany Accounts and Balancing Rules
 Accounting and Reporting Sequencing
 Both Intercompany and Sequencing

Will discuss some more granular details in some other post.

Subledger Accounting (SLA)

As discussed in couple of earlier post GL is integrated with SLA to enable a unified process to
account for subledger transactions and post data to GL, and to provide a consistent view when drilling
down from GL to subledger transactions. You can read here.

Enhanced Foreign Currency Processing by Reporting Made easy

GL has added new features and enhanced existing features to support foreign currency processing ,
they are mainly as:
 In R12, MRC feature is enhanced with a feature call Reporting Currencies. That mean it will
now support multiple currency representations of data from any source, including external
systems, Oracle or non-Oracle subledgers, and Oracle General Ledger journals and balances.
 The second one is in reporting to view balances view balances that were entered in your ledger
currency separate from those balances that were entered and converted to the ledger
currency.The change in R12 is that balances entered in the ledger currency are maintained
 separately from balances converted to the ledger currency for use in Reporting and Analysis.
Here’s an example. Assume we have a ledger and the ledger currency is USD.
I enter and post two journals; one in 1,000 US Dollars, and another in 500 British Pounds that gets
converted to 1200 US Dollars.
In Release 11i, I can review the 500 GBP and the 1200 USD that results from converting the 500 GBP,
and the total 2200 USD which is the USD balance in the Cash Account. The $2200 is the sum of the
$1000 entered in USD and the $1200 converted from the 500 British Pounds. However, I view that a
1000 USD were entered directly in USD.
In Release 12, I can view the 1000 USD by performing an account inquiry on the Cash account for
balances entered only in the ledger currency. The amounts entered in foreign currencies that were
converted to the ledger currency will not be included in the balance. Of course, if I want to retrieve all
balances in USD, both the entered as well and the converted, I can still do that in Release 12.

Creating foreign currency recurring journals

In Release 11i, you could define recurring journals using the functional currency or STAT currency.
Now in Release 12, you can create recurring journals using foreign currencies. This is particularly
useful if you need to create foreign currency journals that are recurring in nature. For example, assume
a subsidiary that uses a different currency from its parent borrows money from the parent. The
subsidiary can now generate a recurring entry to record monthly interest payable to the parent company
in the parent’s currency.
Data Access to Multiple Legal Entities and Ledgers
You no longer have to constantly switch responsibilities in order to access the data in a different ledger.
You can access multiple ledgers from a single responsibility as long as all ledgers share the same chart
of accounts and calendar.
Simultaneous Opening and Closing of Periods for Multiple Ledgers
You no longer have to open and close periods for each ledger separately. You can now open and close
periods across multiple ledgers simultaneously by submitting Open and Close Periods programs from
the Submit Request form.
Simultaneous Currency Translation of Multiple Ledgers
You can run the Translation program for multiple ledgers simultaneously, if you are managing multiple
ledgers.
Financial Reporting for Multiple Ledgers
Now with this feature you can run Financial Statement Generator (FSG) reports for multiple ledgers
simultaneously. This is useful if you manage multiple ledgers and want to run a balance sheet or
income statement report for all of your ledgers at the same time.
Cross-Ledger and Foreign Currency Allocations
You are able to allocate financial data from one or more ledgers to a different target ledger. This
enables you to perform cross-ledger allocations, which is useful for purposes such as allocating
corporate or regional expenses to local subsidiaries when each entity has its own ledger
 Streamlined Automatic Posting
You can now share AutoPost Criteria sets across multiple ledgers that share the same chart of accounts
and calendar and use the AutoPost Criteria sets to post journals across multiple ledgers simultaneously.
Streamlined AutoReversal Criteria Setup Integrated Web-based
AutoReversal Criteria Sets can also be shared across ledgers to reverse journals across multiple ledgers.
This is enhanced by integrated Web-based Spreadsheet Interface.
Journal Copy
Now we can now copy entire journal batches. You can copy journal batches with any status. The
system will create a new journal batch containing the same journal entries.You may also change the
batch name, period, and/or effective date while copying the journal batch. After copying the journal
batch, you may modify the unposted journals in the same manner as any manually created journals.
Streamlined Consolidation Mappings
You are able to define Chart of Accounts Mappings (formerly known as Consolidation Mappings)
between two charts of accounts. Therefore, if you have multiple Consolidation Definitions for parent
and subsidiary ledgers that share the same chart of accounts pair, and their mapping rules are the same,
you only have to define a single Chart of Accounts Mapping.
The enhancement in R12 allows you to define mappings between charts of accounts instead of between
sets of books, so that they can be shared across multiple Consolidation Definitions.
Therefore, if you have multiple Consolidation Definitions for parent and subsidiary ledgers that share
the same chart of accounts pair, and their mapping rules are the same, you only have to define a single
Chart of Accounts Mapping.
You can also secure access to chart of accounts mappings using definition access set security. This
allows you to secure which users can view, modify, and/or use chart of account mappings in
consolidation definitions.
Replacement for Disabled Accounts
Normally when an account is disabled, you can prevent transactions that include the account from
erroring during journal import by defining a replacement account for the disabled account. Journal
import replaces the disabled account with the replacement account and continue the journal import
process if the replacement account is valid. This improves processing efficiency by preventing the
journal import process from erroring and enabling the successful creation of the journal with minimal
user intervention when an account has been disabled.
Data Access Security for Legal Entities and Ledgers
In R12, since you can access multiple legal entities and ledgers when you log into Oracle General
Ledger using a single responsibility, Oracle General Ledger provides you with flexible ways to secure
your data by legal entity, ledger, or even balancing segment values or management segment values. You
are able to control whether a user can only view data, or whether they can also enter and modify data
for a legal entity, ledger, balancing segment value or management segment value.
Management Reporting and Security
This can be best understood as:You can designate any segment (except the natural account segment) of
your chart of accounts to be your management segment and use Oracle GL security model to secure the
management segment for reporting and entry of management adjustments.
 Prevent Reversal of Journals with Frozen Sources
You can no longer reverse journals from frozen sources defined in the journal sources form.

If the journal is created from a frozen source, the journal cannot be modified even if the
source is subsequently unfrozen in the future.
This provides streamlined data reconciliation with subsystems. Not being able to reverse
journals that originated in subledgers will ensure that the account balances will always tie
out with General Ledger. If you need to reverse a subledger journal, then you should do so
in Subledger Accounting or the subledger application.

Prevent Reversal of Unposted Journals

You also can no longer reverse unposted journals. This ensures data integrity and better auditability.
In the past when we allowed you to reverse unposted journals, there was a risk that the original journal
could be deleted so you could end up reversing something that didn't exist. Now, all reversals can be
tied back to the original posted journal.
Integrated Web-based Spreadsheet Interface
Through the integration with Web ADI, users can now leverage spreadsheet functionality in Oracle
General Ledger via a web-based interface. The spreadsheet interface can be conveniently launched
from a GL responsibility.
Using the Journal Wizard, we can leverage spreadsheet functionality to create actual, budget, or
encumbrance journals. You can take advantage of spreadsheet data entry shortcuts such as copying and
pasting or dragging and dropping ranges of cells, or even using formulas to calculate journal line
amounts. You can then upload your journals to Oracle General Ledger. Before uploading, you can save
and distribute your journal worksheets for approval.
We can also import data from text files into spreadsheets, where it can be further modified before
uploading to Oracle. This functionality is useful when migrating data from legacy systems, or from any
source that can produce delimited files.
Using the Budget Wizard, you can download budget amounts to a spreadsheet, modify the amounts,
and then upload them back. You can also choose to download the actual amounts to compare it with the
budget amount. Budget Wizard also allows you to plot graphs and do a graphical comparison on the
amounts. Budget Wizard also provides budget notes. You can add descriptions to accounts and amounts
in your budget and explain your budget within the budget worksheet, avoiding the clutter of external
documentation.
Control Accounts
You are able to control data entry to an account by ensuring it only contains data from a specified
journal source and to prevent users from entering data for the account either in other journal sources or
manually within general ledger.
Security for Definitions
You can secure your setup and definitions by granting specific privileges to users to view, modify,
and/or execute a definition. This enables you to control which of your users can view a definition, but
not modify or execute it, or execute a definition without modifying it, or vice versa.
Following is a list of definitions that have this security available for:
1. MassAllocation and MassBudget Formulas
 2. FSG Reports and Components
3. Accounting Calendars
4. Transaction Calendars
5. AutoPost Criteria Sets
6. AuoReversal Criteria Sets
7. Budget Organizations
8. Chart of Accounts Mappings
9. Consolidation Definitions
10. Consolidation Sets
11. Elimination Sets
12. Ledger Sets
13. Recurring Journals and Budget Formulas
14. Rate Types
15. Revaluations
Sequence for Reporting
Maintaining two sequnces have been introduced, accounting and reporting sequencing.

Read my earlier post for more details:

Journal Line Reconciliation

Journal Line Reconciliation enables you to reconcile journal lines that should net to zero,
such as suspense accounts, or payroll and tax payable accounts for countries, such as
Norway, Germany, or France.

In R12, we’ve made many improvements to intercompany accounting. R11i’s

Global Intercompany System (GIS) has been replaced with an exciting new product called
Advanced Global Intercompany System (AGIS). We also extended intercompany balancing
support to include encumbrance journals.

Enhanced Intercompany
For more deatils , read this
Some of the GL Standard Reports converted into XML Publisher
Oracle General Ledger's Account Analysis, General Journals and Trial Balance standard reports are
now integrated with XML Publisher.