UPGRADE 11i to R12: Oracle General

Ledger
24 juin 2014

2 244 vues

3 jaime

1 commentaire

Partager sur LinkedIn

Partager sur Facebook

Partager sur Twitter

Release 12 brought in plethora of new functionalities along with it. We had the SLA concept
being introduced and the experts said Set of Books was gone. In the following lines, we have
tried to highlight these functionalities
1. Ledgers:
Ledger is the new name for traditional Set Of Books that existed in 11i. If you recollect, the
Set of Books comprised of three essential components: 3 Cs. These were Chart of Accounts,
Calendar and Currency. Ledgers, however, are made up of four such C components normally
termed as Four Cs - Chart of Accounts, Calendar and Currency and Subledger Accounting
Method (SLAM). SLAM is a rule based accounting engine that helps a user have the
representation of the accounting entries in a manner required by his company and/or the local
law. The user may choose to record only the Cash entries or the Accruals as well by choosing an
available value from the list of Standard SLAMs provided. Users can also create their own
Subledger accounting methods.
In Release 11i, one responsibility could be assigned to one Set of Book Only. Release 12 brought
in an addition here. Now, one can assign multiple ledgers to a single responsibility in R12 using
the Ledger Sets and Data Access Sets. Of course, one mandation is that only those ledgers can be
grouped that share same Chart of Accounts and Calendar.
2. Data Access Set:

As we discussed earlier, Release 12 allows one to assign multiple ledgers to a responsibility.

Alongside, one would also be able to choose the level of privileges that one could provide for
each of these ledgers. For example, I may want my user to have complete Read Write privileges
for Ledger A, but he should be able to only View the data that exists in Ledger B. Data Access
Set also makes this kind of a combination possible.
The General Ledger Accounting Setup Program automatically creates a data access set for each
ledger and reporting currency (journal level or subledger level) assigned to a completed
accounting setup. The system-generated data access sets created for each ledger and reporting
currency provide full read and write access to the ledger and all of its balancing segment values
and management segment values.
3. Accounting Setup Manager : Centralized Setup
Accounting Setup Manager is a new feature that streamlines the setup and implementation of
Oracle Financial Applications. With the Accounting Setup Manager, one 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

Subledger Accounting Options. This is where you define the accounting methods for each
submodule and associate them to the ledger where the accounting is stored.

Intercompany Accounts and Balancing Rules

Accounting and Reporting Sequencing

As part of pre-upgrade process, one should run the Accounting Setup Manager Pre-Update
Diagnosis Report. This report identifies potential incompatibilities that would prevent you from
using some new features in R12.
The report also details what changes, if any, the upgrade will have on certain objects.
4. Definition Access Sets
Definition Access Sets are an optional security feature that allows one to control access to your
General Ledger definitions. For example, one can prevent certain users from viewing, making
changes, or using your recurring journal, FSG or any other setup for that matter.

This Security can be set at three levels:

Use

View

Modify

If you do not enable security, all users will be able to use, view, and modify your definition.
Following Steps will assist you set the definition:

Navigate to the function to be secured ( eg. Calendar, Budget Organization etc)

Check the enable security checkbox.

Hit the Assign Security button to assign the Definition Access Set.

Grant Privileges as desired.

Note: Please be careful while setting up these definitions. Though the security is assigned at the
responsibility level, the user logging in gets the privileges that are a consolidations of all the
responsibilities assigned to him.
Lets take an example. Say User has the following three responsibilities assigned:
ResponsibilityA View Budget Organization
ResponsibilityB Use Budget Organization
ResponsibilityC Modify Budget Organization
The user would now get all the three privileges whichever responsibility he logs in from
5. Multi-Ledger Processing
Introduction of Ledger sets in R12 facilitates the following accounting operations across ledgers:

Open / close periods for multiple ledgers simultaneously

Submit concurrent programs for all ledgers in a ledger set

Cross ledger allocations, recurring journals and year-end closing journals

currency translation for multiple ledgers simultaneously

Financial reporting (FSGs) across ledgers

Account inquiry across ledgers

Create Balance Sheet Closing Journals

Create Income Statement Closing Journals

6. Alternate Accounts
It is a regular practice amongst users to disable code combinations where they do not require any
further activity to take place. Hence in 11i if there was a case where users were importing the
existing data with one such code combination, the import program would error flagging invalid
code combination. This would hold up the entire group of transactions from getting imported.
Release 12 provides a solution to such an issue. When an account is disabled, users 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 continues the 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 when an account has been disabled.
7. Sequencing
In Release 12, in order to cater to the need for Legal compliance for countries like Europe and
Latin America, two more sequencing options have been introduced as a part of standard
application apart from existing Document Sequences. These Sequences can be assigned not only
to journals in General Ledger module but also to those created in SLA:
Accounting Sequence:
Accounting Sequences are assigned to GL journals when they are posted and to Subledger
Journals once they complete accounting.
Reporting Sequence :
Reporting Sequences are assigned to journals in GL and Subledger journals upon GL period
closure. Once a period is closed, the close period program fires a Create Reporting Sequences
program as a shoot off. This program assigns reporting sequences to journals.
This is one of the replacement for Accounting Engine (AX) Legal Sequencing.
You could refer the following note for the details on this functionality:
8. Line Level Reconciliation

General Ledger Reconciliation allows users to reconcile transactions in General Ledger and
ensure that the sum of these set of transactions is zero. An example where this functionality
would be required is the VAT control account.
One can enable reconciliation either for Natural Account Values for specific code combinations.
Using this new functionality, one can selective cross reference transactions by entering a
"Reconciliation Reference" at the Journals Line level. One can perform account reconciliation
either automatically with the General Ledger Automatic Reconciliation report, or manually in the
Reconciliation Lines window.
Use automatic reconciliation to reconcile journal lines that have matching balancing segments,
account segments, and reconciliation references, or optionally where the reconciliation reference
is blank.
Use manual reconciliation to reconcile journal lines with different code combinations
(including different balancing segments or account segments) or different reconciliation
references.
For both automatic and manual reconciliation, the balance for the journal lines that you want to
reconcile must be zero. Reconciliations can be performed between transactions entered in the
same or different currencies.
9. Third Party Control Accounts
The Third Party Control Account feature in the Oracle E-Business Suite enables organizations to
maintain detailed balances by third party for an account code combination. Subledger
Accounting checks that valid third party information is associated with the journal line if the
account code combination is a Third Party Control Account. If it is not, then Subledger
Accounting rejects the journal line.
For example, when the unidentified receipts account code in the Oracle Receivables is defined as
a Third Party Control Account, accounting for the unidentified receipts will fail because no third
party information is available for such receipts. Similar issues are observed with the rounding
account and intercompany accounts.
General Ledger prevents manual journal entries from posting to the Third Party Control
Accounts. This ensures that journal lines that post to the control account codes such as Supplier
Liability Account, Customer Receivables Account are associated with the valid third party
information in the respective subledger modules.
Note: this feature was implemented starting 12.1.3 only as a result of an Enhancement Request
evaluated by development and approved for implementation. This will not be backported to
previous versions and the only way to get this feature is to implement or upgrade to 12.1.3
version.