R12: How To View Reporting Sequences For Subl edger Journals?

Goal
1. You have defined Sequencing- reporting for both subledger and GL journal entry
event GL period
close.
After closing the period in GL, the Create Reporting Sequence Number program is
automatically launched and completed normally but when checking the reporting
sequence number for Subledger journals and GL journal entries only the reporting
sequence numbers for GL journal entries are shown and no reporting sequences for
Subledger journals are available.
How to view the reporting sequence created and assigned to subledger journals?
Solution
This is the intended functionality.
For subledger journals you can see the reporting sequence in SLA level not in GL. For
subledger journals GL cant transfer the reporting sequence. Only manual journals
which are created in GL will get the reporting sequence. For subledger journals you can
see the reporting sequence in SLA level only .If however a subledger journal is reversed
user will not get a reporting sequence because the reversals do not populate the
xla_seq_je_headers_gt table that gets the sequence
In order to see the reporting sequences for subledger journals in SLA:
Log in with your SLA responsibility;
Check your setup according to Oracle Subledger Accounting Implementation Guide
Release 12 Chapter 7 Reporting Sequence- page 7-4 Reporting Sequence Process
Steps and following.
Navigate to Subledger Journal Entries > Lines > make your query and see the
transactions retrieved.

 In the Transaction information area note the + Show additional information : unhide
the information ; at this step you can see your accounting and reporting sequences
numbers.

Note: In order to have the assigned reporting sequences used you have to:
Check the journal entry status of Final'; draft entries are not assigned a reporting
sequence;
Check that the transactions are posted in GL;
Check that the GL period has been closed and the automatically launched process
Create Reporting Sequence Number has completed normally;
At the time you check your SLA reporting sequences numbers the period in GL has
not been re-opened (the program erases the sequences that are assigned to the journal
entries that belong to the reopened period).

R12 What are the Differences Between Accounting Sequencing and

Reporting Sequencing?
The accounting sequence is assigned to Subledger Accounting journal entries at the
time that the journal entry is completed. The sequence is assigned in the completion
date order using the GL date as the date criterion for determining the sequence to be
used.
The reporting sequence is assigned to both Subledger Accounting journal entries and
General Ledger journal entries when the General Ledger period is closed. This
sequence is used by most of the legal reports required in some countries as the main
sorting criterion to display the journal entries.Reporting sequence is optional.
These two sequences are not mutually exclusive and can coexist in the same journal
entry.

Note: for more details

-Oracle Financials Implementation Guide (Part No. B16386-01) contains a
separate chapter on Accounting and Reporting Sequencing;
-Oracle Subledger Accounting Implementation Guide chapter on Reporting Sequencing;

Setup:
1 Go to Setup > Financials > Sequences >.Assign
2.Select your General Ledger
3.Select Sequence Entity : Subledger Journal Entry
4.Select Sequence Event : GL Period Close': for fiscal reporting during accounting
period close./
Accounting': for fiscal accounting of journal entries originating in the subledgers.
5 .Select Sequence Entity : GL Journal Entry
6. Select Sequence Event: GL Period Close': for fiscal reporting during accounting
period close./
Posting : for fiscal accounting of journal entries originating in the general ledger.

Impact of SLA on Journal Import in General Ledger Setups related to Journal Import
1. Journal Import can be run in Summary or Detail mode. This can be set for each
application, as per the requirement. By default this is set to Summarize by GL Period,
but can be changed as per the requirement. The setup can be changed from:
General Ledger responsibility
Financials -> Accounting Setup Manager -> Accounting Setups
Query for the Ledger being used
Update Accounting Options
Select update for Subledger Accounting Options
Update Accounting Options for the Application
Here there is an option General Ledger Journal Entry Summarization, which can be
set to following values:
i. Summarize by GL Date (Journal Import will create summary journals based
on Acccounting Date)
ii. No Summarization (Journal Import will create journals in Detail mode)
iii. Summarize by GL Period (Journal Import will create summary journals based
on Period to which the Accounting Date falls)
Thus the option General Ledger Journal Entry Summarization will determine if the
Import for the application is being done in Detail or Summary mode.
3

2. Prior to Release 12, it was needed that the Journal Import should be run in the same
language as the language, which was used to transfer data to GL_INTERFACE. Though
this is not much relevant now (the transfer and journal import are triggered together);
still Journal Import can be made independent of the language. This can be achieved by
running journal import using the Source and Category Key. Generally the columns
user_je_source_name and user_je_category_name in gl_interface, correspond to
the columns GL_JE_SOURCES.user_je_source_name
and GL_JE_CATEGORIES.user_je_category_name respectively. These values change
for the different language and thus making journal import language-dependent.
However while defining the sources (General Ledger Responsibility : Setup -> Journal
-> Source), if the option Import Using Key is selected, then import refers
to GL_JE_SOURCES.je_source_key and GL_JE_CATEGORIES.je_category_key.
These being the Key values are common across languages and hence journal import
becomes language independent.
3. While running Journal Import from General Ledger responsibility, the LOV of Ledger
appears provided there is data in the table GL_INTERFACE for the ledger and the Data
Access Set attached to the responsibility has either Full or Read/Write access to the
Ledger.
Journal -> Import -> Run
LOV for Ledger.
In case a different Interface table is being used, the LOV will check for the data in
GL_INTERFACE_CONTROL instead of GL_INTERFACE.
4. Data Access Sets do apply to Journal Import too. To be able to import data, one
should have either Full or Read/Write Access to the ledger and all the
Balancing Segment Values for which data is populated in GL_INTERFACE.
In case one does not have access to the Ledger at all, the LOV for Ledger will not
appear in Journal -> Import -> Run screen and hence he will not be able to
submit Journal Import.
If there are multiple balancing segments in the data in GL_INTERFACE, and the
responsibility has access to a few and not to others, then you will be able to run

Journal Import but it will complete in Warning and data will not be imported. Error shown
in the Journal Import Execution report would be:
EM29 : You do not have access to this ledger and account
combination.

Impact of SLA on Journal Import in General Ledger

The way Journal Import is triggered from the subledgers has undergone a major change
in Release 12. Execution of Journal Import from the Subledgers depends on the setting
of the Profile option SLA: Disable Journal Import.
The profile option SLA: Disable Journal Import can be set only at the Site level and
hence will be applicable to all the subledgers/modules. The default value for this profile
option is No and this should NEVER be changed, unless suggested by Support or
Development. Setting this profile option to Yes breaks the link between SLA and GL, so
GL no longer knows which journals came from SLA. This may cause problems
with inquiry and drilldown on these journals in the future. This option is set to Yes only
in cases where GL is on a separate instance than SLA.
SLA: Disable Journal Import set to No.
Value No for this profile option indicates that Journal Importwill ALWAYS accompany
the transfer of data from Subledger.Another main implication of this value is that, on
failure of Journal Import, the data will be rolled back to SLA tables and hence we will not
have any data in GL_INTERFACE. Note that for this setting of the profile option,
General Ledger will have very little part to play, as any error in Journal Import will
take the data back to SLA tables and GL_INTERFACE will not have any data in it. This
will also mean that Journal -> Import -> Run and Journal -> Import -> Correct forms
will not be used for the Subledger data as GL_INTERFACE will never have any data
for them. However, these forms will continue to be used for the data, which is being
transferred from some other sources such as Legacy or some user defined sources for
which data is populated in GL_INTERFACE table, and then Import is run in
General Ledger.
Whenever data is transferred from the subledgers, the request doing so, will also trigger
the Journal Import program. The name of the program to transfer data to GL, will
change as per the subledger; we have explained the behavior below with respect to the
Payables module. In Payables, there are three options for transferring data to GL:
1. When Online Accounting is done for Payables transactions, there are three options
available:
a. Draft
5

b. Final
c. Final Post
For any value of the profile option, Draft and Final optionswork in the same way i.e draft
mode creates the SLA journalsin Draft mode which can be modified afterwards; Final
modecreates SLA journals and the transaction can not be modified after this. The SLA
journal can then be transferred to General Ledger.
Transfer of the journals created in Final Mode is done using Transfer to General
Ledger concurrent request. However Final Post works differently for the two values
of the Profile option. If profile option is set to No, then Final Post creates the SLA
journals in Final mode, transfers the data to GL_INTERFACE, runs Journal Import and
triggers the General Ledger Posting program too.
2. When Accounting is done from Submit request form i.e by running the request
Create Accounting, it gives the following options:
a. Mode: Draft or Final
b. Transfer to General Ledger
c. Post in General Ledger
If Transfer to General Ledger is selected as Yes, then the data is transferred to
GL_INTERFACE and immediately after that Journal Import request is also triggered. In
case of any errors, the data is rolled back to SLA tables.
3. If Accounting is done in Final Mode and we are transferring the data by running the
request Transfer Journal Entries to GL request, it gives the option of Post in General
Ledger which refers to the Posting program in General Ledger.
Thus there is no option for Journal Import as Journal Import will always be triggered by
the Transfer program. From points 1, 2 and 3, it is evident that Journal Import
has become an inbuilt part of the Transfer Journal Entries program of SLA in Release
12. Thus when the profile option SLA: Disable Journal Import is set to No,
GL_INTERFACE table will never have data for Subledgers.
SLA: Disable Journal Import set to Yes
This setting for the profile option indicates that the transferring of data from Subledgers
will take place in the same manner as it happens in Release 11i. However changing the
value of the Profile option to Yes is strictly not suppported and should NEVER be used
as this may lead to issues related to the linking between SLA and GL journals. For this
value of profile, the Transfer to GL programs of the subledgers, populates the data
in GL_INTERFACE and then Import needs to be run manually from GL. In case the
subledger is providing the option of running the journal import too along with the transfer
to GL, then the request will fire the Journal Import also. However in case of a
Journal Import error, the data will remain in GL_INTERFACE table.
Impact of SLA on Drilldown in General Ledger
Drilldown functionality enables users to navigate from a Journal in General Ledger to
the Subledger Journal Entry in SLA and from there to the transaction which has resulted
into that journal.

To enable Journal drilldown from General Ledger, the Import Journal References
option should be enabled for the Source.
This can be checked under General Ledger Responsibility at Setup -> Journal ->
Sources -> Define.
Only when this is enabled, the reference data is populated by SLA engine.
The Drilldown in Release 12 is different from the prior releases of the Application. R12
drilldown is Web based and not in the Forms.
1- Navigation to perform Drilldown is the same as in Release 11i.
Journals -> Enter -> Review Journal
Select the journal line and click on Lines Drilldown.
2- Drilldown can also be performed from:
Tools -> Drilldown
As mentioned above, Drilldown opens the Web Page instead of Form.
The SLA Page for Drilldown shows the following:
GL Journal Line information
Subledger Journal Line information
There are two Options available on this SLA page:
View Transaction
View Journal Entry
View Transaction will take us to the Subledger Transaction form.
E.g for the current journal line, since the Source was Payables, it opens Invoice
Workbench.
View Journal Entry will take to the Subledger Journal Entry details
View Journal Entry has three parts to it.
1. Transaction Information
2. Additional Information (this is hidden by default)
3. Line Details
Apart from this there are some extra details shown at the top of the page, which is the
header level information for the Subledger Transaction.
Some of the important fields in header part of the Subledger Transaction Journal are:
Ledger Name
Journal Entry Status
Balance Type
GL Date
This is the Additional Information section of Subledger Transaction Entry page.
This section shows the details of
Event
General Ledger
Sequences
Application Accounting Definition
Note that Event and Application Accounting Definition are important from SLA side.
However, from GL perspective the relevant details are Period, Transfer to GL Date and
Transfer to GL status.
This is the last section, Lines of the Subledger Journal Entry page.
The important details in this section are:
7

 Code Combination
Currency
Entered Debits and Credits
Accounted Debits and Credits
Select the link Show for any of the lines to view additional details for the transaction
line
Profile Options related to Drilldown:
SLA: Enable Subledger Transaction Security in GL
This profile option controls whether the drilldown to SLA will enforce the transaction
security of the application owning the Transaction. For example, if one drills down to
Payables, he will only be able to see Journals for transactions belonging to operating
units to which he has access (based on your MO: Security Profile.) Thus drilldown can
be restricted to the Operating Units to which the responsibility has access. In case the
GL responsibility does not have access to a particular Operating Unit, the Drilldown will
not show any data.

XLA_EVENTS:
SELECT * FROM xla_events xe WHERE xe.application_id = 222
AND xe.entity_id IN ( SELECT xte.entity_id FROM xla.xla_transaction_entities xte
WHERE xte.application_id = 222 AND xte.entity_code = TRANSACTIONS
AND xte.source_id_int_1 = 10066)
XLA_AE_HEADERS:
SELECT * FROM xla_ae_headers xah
WHERE xah.application_id = 222 AND xah.entity_id IN ( SELECT xte.entity_id
FROM xla.xla_transaction_entities xte WHERE xte.application_id = 222
AND xte.entity_code = TRANSACTIONS AND xte.source_id_int_1 = 10066)
XLA_AE_LINES:
8

SELECT xal.* FROM xla_ae_lines xal, xla_ae_headers xah

WHERE xal.application_id = xah.application_id AND xal.ae_header_id =
xah.ae_header_id
AND xah.application_id = 222 AND xah.entity_id IN (
SELECT xte.entity_id FROM xla.xla_transaction_entities xte
WHERE xte.application_id = 222 AND xte.entity_code = TRANSACTIONS
AND xte.source_id_int_1 = 10066)
XLA_DISTRIBUTION_LINES:
SELECT xdl.* FROM xla_distribution_links xdl, xla_ae_headers xah
WHERE xdl.application_id = xah.application_id AND xdl.ae_header_id =
xah.ae_header_id
AND xah.application_id = 222 AND xah.entity_id IN ( SELECT xte.entity_id
FROM xla.xla_transaction_entities xte WHERE xte.application_id = 222
AND xte.entity_code = TRANSACTIONS AND xte.source_id_int_1 = 10066);