R12: How to Handle Subledger Data Conversion When Primary

and Secondary Ledgers Have Different Calendars (Doc ID

1100093.1)

To
Bottom

In this Document
Goal
Solution

APPLIES TO:
Oracle General Ledger - Version 12.1.1 and later
Oracle Payables - Version 12.1.1 and later
Information in this document applies to any platform.
GOAL
Is it possible to create a Secondary Ledger with a Subledger Data Conversion and a Different
Calendar?
If yes, then how do you create a data access set so that create accounting can be run, while
bringing in data from the subledger to the primary ledger and secondary ledger.
SOLUTION
Yes, it is possible to create a Secondary Ledger with a Subledger Data Conversion and a
Different Calendar.
Review the Oracle General Ledger Implementation Guide Release 12.1 and the Oracle
Financials Implementation Guide for Release 12
The documentation states the following:
(i) Secondary ledgers can have a different calendar than the Primary Ledger
Secondary ledgers represent the Primary Ledger's accounting data in another accounting
representation that differs in one or more of the following ways:
chart of accounts
accounting calendar/period type combination

 currency
subledger accounting method
ledger processing options
(ii) Subledger Data Conversion Level
This data conversion level uses both Subledger Accounting and the General Ledger Posting
program to create the necessary journals in both the primary and secondary ledgers
simultaneously. Subledger Accounting creates the journal entries from subledger transactions if
the subledger integrates with Subledger Accounting.
General Ledger Posting creates the journal entries for all other transactions that do not integrate
with Subledger Accounting, including manual journal entries
(iii) How data is converted if the calendar is different:
The following conversion rules are used to convert data from the primary ledger to the secondary
ledger:
Calendar Conversion: If the secondary ledger uses a different accounting calendar from the
primary ledger, the journal effective date determines the corresponding non-adjusting period in
the secondary ledger.
However, when running create accounting from the subledger, user gets the following error
message: "The access set Vision Operations Primary Ledger assigned to the system profile
option GL: Data Access Set does not include read and write privileges for the ledger Vision
operations Secondary Ledger and the balancing or management segment value.
Please use the Data Access Sets window in General Ledger to include read and write privileges
for the ledger and segment values or assign a different ledger access set to the system profile
option."
Per the Oracle Financials Implementation Guide for Release 12, when creating a data access set,
all ledgers and ledger sets assigned to a data access set must share the same chart of accounts and
accounting calendar/period type combination.
The way to provide the subledger access to both the primary ledger and secondary ledger, while
running create accounting, is to set the following system profile options:

GL: Data Access Set -- to point to the primary ledger

SLA: Additional Data Access Set -- to point to the secondary ledger

REFERENCE:
SLA: Additional Data Access Set
The SLA: Additional Data Access Set profile option, in conjunction with the GL: Data Access
Set profile option controls which ledgers and balancing or management segment values you can
access when logging onto a responsibility.

If SLA: Enable Data Access Security in Subledgers is enabled for the responsibility, you have
access only to the ledgers and balancing or management segment values included in the data
access sets assigned.