Sets-of-Books Changes

Sets-of-Books Changes:-
---------------------------

All set of books' options will be copied over to ledger options in Release 12. All Release
11i functionality, with exceptions noted in the following sections, will be migrated to
Release 12.

Set of Books Profile Option

In Release 11i, the GL: Set of Books profile option controlled the set of books that a
responsibility could access. In Release 12, the GL: Data Access Set profile option
replaces the GL: Set of Books profile option. All responsibilities previously assigned to a
set of books using the GL: Set of Books profile option will be assigned to a data access
set using the GL: Data Access Set profile option. The data access set will provide full
read and write access to the upgraded ledger allowing you to continue to use the ledger
the same way as you did in Release 11i.

Secondary Tracking

This section describes the upgrade impact for the secondary tracking option.

In Release 11i, the set of books form had two check boxes to support secondary
tracking; one for revaluation and another for closing and translation.

In Release 12, the ledger definition only has one check box to enable the secondary
tracking segment for revaluation and closing and translation. For upgrade cases, Oracle
will preserve the Release 11i settings. However, when you update the ledger options for
upgraded ledgers the Track by Secondary Segment check box may or may not be
checked but your Release 11i settings will be preserved behind the scenes.

The following describes when the Track by Secondary Segment check box will be
checked after the upgrade:

• If Secondary Tracking was enabled for both Revaluation and Closing and
Translation in Release 11i, then the single check box will be checked in Release 12
and secondary tracking will continue to perform for all three features.

• If Secondary Tracking was enabled for Closing and Translation but not for
Revaluation in Release 11i, then the check box will be checked in Release 12. Behind
the scenes, secondary tracking will be off for Revaluation.

• If Secondary Tracking was enabled for Revaluation only in Release 11i, then the ledgers will have the US Federal Accounting subledger accounting method assigned.
You will be able to use the ledger immediately after the upgrade.

You cannot delete the subledger accounting method but you can change the subledger
accounting method and subledger accounting options at any time. If you are not
integrating Oracle General Ledger with Oracle Subledgers, then you do not need to
change the assigned subledger accounting method because it will be ignored for
General Ledger processing purposes.

The following lists the subledger accounting options that will be automatically assigned
to upgraded ledgers:

• Subledger Accounting Method: For non-public-sector ledgers, Standard Accrual
will default unless the upgrade detects that the ledger is a cash-basis ledger, in
which case, Standard Cash will be assigned. For public sector ledgers, Encumbrance
Accrual will default unless the upgrade detects that the ledger is a cash-basis
ledger, in which case, Encumbrance Cash will be assigned. You can change the
subledger accounting method at any time but you cannot delete it.

• Subledger Accounting Method Owner: Oracle defaults for all upgraded ledgers. If
you change the subledger accounting method, then the owner of that method will
default.

• Journal Entry Language: The base language installed for the instance defaults.

• Entered Currency Balancing Account: If a suspense account was assigned to the set subledger level secondary ledger. If, however, the Allow GL Posting option was not
enabled, then accounting entries will not be automatically created for the upgraded
subledger level secondary ledger.

If you used the General Ledger Consolidation functionality to map and transfer
subledger transactions into the set of books linked to the tax book, then you can
continue to do so in Release 12. With the new features in Release 12, however, you have
the following two options to automate this process:

• Subledger Accounting (SLA)

• The General Ledger Posting Program

Option 1: Using Subledger Accounting (SLA)

You can use Subledger Accounting (SLA) to automatically create the accounting entries
for all subledger transactions in both the primary ledger and the subledger level
secondary ledger. Thus, every subledger transaction can be accounted in both ledgers
simultaneously. To do this, perform the following steps after upgrade:

1. Query the Accounting Setup by the primary ledger or secondary ledger using
General Ledger's Accounting Setup Manager.

2. Update the Subledger Accounting Options for the secondary ledger, and then
update the Accounting Options for the subledger applications. Enable Subledger
Accounting for each subledger application by selecting Yes in the Subledger Accounting Enabled box.

3. For the Secondary Ledger's Subledger Accounting Method, verify the Application
Accounting Definitions for all subledgers to ensure that the accounting rules meet
your needs.

Option 2: Using the General Ledger Posting Program

You can use the General Ledger Posting program to automatically transfer journals
from subledger sources to the subledger level secondary ledger. To do this, perform the
following steps after upgrade:

1. Query the Accounting Setup by the primary ledger or secondary ledger using
General Ledger's Accounting Setup Manager.

2. Update the Primary to Secondary Ledger Mapping step for the secondary ledger. In
the Journal Source and Category Conversion region, select Yes in the Transfer
Journals to this Secondary Ledger box for the subledger source and category that
you want General Ledger Posting to transfer.

Note: You can use a combination of both options. For example, you can
use Subledger Accounting to handle some subledgers and General
Ledger Posting to handle other subledger transactions. Journals that are
entered directly in the primary ledger, such as manual journals, will be
transferred to the secondary ledger by the General Ledger Posting
program.

Secondary Sets of Books in Payables and Receivables

If you are using secondary sets of books in Oracle Payables and Receivables, the
secondary sets of books become subledger-level, secondary ledgers in Release 12. In
Release 12, Subledger Accounting (SLA) will automatically create the accounting for
Payables and Receivables transactions in both the primary ledger and the subledger
level secondary ledger simultaneously.

If you used the General Ledger Consolidation functionality to map and transfer
subledger transactions into these secondary set of books, then you can continue to do so
in Release 12. With the new features in Release 12, however, you have two options to
automate this process.