New and Enhanced Features in Oracle R12
New and Enhanced Features in Oracle R12
New and Enhanced Features in Oracle R12
Features in Oracle
R12
GL changes in Terminology
Release 11i Release 12
With the Accounting Setup Manager, you can perform and maintain the following
common setup components from a central location:
Legal Entities
Reporting Currencies
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.
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. 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.
In Release 11i, a user assigned to an Operating Unit (OU) would process data from the
products deployed in that OU. To process data for another OU, a user would log out of the
first and into the second.
In Release 12.0, by contrast, users can be assigned to multiple operating units, and are
supported by processes and transactions that can span operating units. Their data is book-
kept according to rules stored in a single accounting engine,and the accounting is stored in
subledger tables that are standard across all products.
New Features in Accounts
Payable
Supplier
We have seen in 11i
Suppliers defined in AP.
Supplier contacts replicated for
each supplier site.
Where as in R12
Supplier becomes as TCA Party.
Suppliers Sites as TCA Party
Site for each distinct address.
But in R12,
1. Invoice Lines as a new additional line accommodated in Invoice data model.
In 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.
There was global descriptive flex fields were captured for country-specific tax attributes.
More importance most of the setup performed at OU level.
In R12
A new module eBusinessTax determines tax based on facts about each transaction, this is
reason why Oracle has introduced additional line information at invoice level.
The module "ebusiness 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
Differences In Assets
I-setups