Professional Documents
Culture Documents
Modified 15-DEC-2011 Type WHITE PAPER Status PUBLISHED
Modified 15-DEC-2011 Type WHITE PAPER Status PUBLISHED
Impact of R12 Subledger Accounting (SLA) on General Ledger (Drilldown and Journal Import) [ID 434226.1] Modified 15-DEC-2011 Type WHITE PAPER Status PUBLISHED
In this Document Abstract Document History Impact of R12 Subledger Accounting (SLA) on General Ledger (Drilldown and Journal Import) INTRODUCTION OVERVIEW Part I : Impact of SLA on Drilldown in General Ledger Part II : Impact of SLA on Journal Import in General Ledger Part III : Technical Reference Summary Still Have Questions?
Applies to:
Oracle Subledger Accounting - Version: 12.0.0 to 12.1.3 - Release: 12.0 to 12.1 Oracle General Ledger - Version: 12.0.0 to 12.1.3 [Release: 12.0 to 12.1] Information in this document applies to any platform. Subledger Accounting - Release 12
Abstract
This document is created for the users of Oracle Applications Release 12 (R12), in order to explain the Impact of Subledger Accounting on the two main functionalities of General Ledger - Drilldown and Journal Import. The aim is to know the changes brought in by Release 12 and to understand the advantages and effects of the same. The Document discusses the two main functionalities of General Ledger - Drilldown and Journal Import. It also explains some of the SLA setups that need to be done in General Ledger. Some table level details are also provided which may help in customizations or troubleshooting.
Document History
Author : Meenakshi Mehra Create Date 30-May-2007 Updated By: Nuno Mascarenhas Update Date 11-Oct-2011 - Convertion from PDF to HTML standard format
Impact of R12 Subledger Accounting (SLA) on General Ledger (Drilldown and Journal Import)
INTRODUCTION
With the Release 12 of Oracle Applications, Subledger Accounting (SLA) has been introduced. This is a Rule-based accounting engine, toolset & repository supporting Oracle E-Business Suite modules (also called as subledgers). The main idea behind this introduction is to have an option of allowing multiple accounting representations for a single business event, resolving conflicts between corporate and local fiscal accounting requirements. Also this introduces a common data model and user interface (UI) across subledgers, replaces various disparate 11i setups, providing single source of truth for financial and management analysis. Due to SLA, there are some changes in the functionalities of General Ledger. There are also certain setups that need to be done in General Ledger for SLA.
OVERVIEW
For understanding the Impact of SLA on General Ledger, we have divided this document into three parts: 1. Drilldown This will deal with the change in the Drilldown data, which appears now. Also the setups, which decide what data, can be viewed and how data can be secured. 2. Journal Import This will deal with the transfer of data from Subledgers to General Ledger. This will also explain the various setups that are done for the Ledger which govern the import for various applications. 3. Technical Reference This will give the technical references, for journal import and drilldown functionalities, which will help in understanding the architecture and will also help in troubleshooting.
1 of 12
1/24/2012 11:24 PM
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&do...
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. The following screenshots show the Drilldown functionality in Release 12: 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 of 12
1/24/2012 11:24 PM
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&do...
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
3 of 12
1/24/2012 11:24 PM
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&do...
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
4 of 12
1/24/2012 11:24 PM
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&do...
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
5 of 12
1/24/2012 11:24 PM
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&do...
This is the 'Transaction Information' section of Subledger Journal Entry page. The fields here will change based on the transaction and the subledger in which the transaction was entered. Since the example transaction is entered in Payables, it is showing the details of the invoice and the supplier.
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
6 of 12
1/24/2012 11:24 PM
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&do...
This is the last section, 'Lines' of the Subledger Journal Entry page. The important details in this section are: 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
This page gives various details for transaction line from the subledgers side.
7 of 12
1/24/2012 11:24 PM
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&do...
Thus the Drilldown from General Ledger, takes us to the Subledger Journal Entry which shows the details of the Subledger journal. From here we can further drilldown to the Subledger Transaction. 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.
1. When Online Accounting is done for Payables transactions, there are three options available (Refer Screenshot below): a. Draft b. Final c. Final Post
8 of 12
1/24/2012 11:24 PM
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&do...
For any value of the profile option, Draft and Final options work in the same way i.e draft mode creates the SLA journals in Draft mode which can be modified afterwards; Final mode creates 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
9 of 12
1/24/2012 11:24 PM
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&do...
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.
10 of 12
1/24/2012 11:24 PM
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&do...
General Ledger Journal Entry Summarization will determine if the Import for the application is being done in Detail or Summary mode.
(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 languagedependent. 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 provided there is taken from the ledgers in table GL_INTERFACE and the Data Access Set attached to the responsibility has either Full or Read/Write access to the Ledger. Journal -> Import -> Run 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.
11 of 12
1/24/2012 11:24 PM
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&do...
The data in GL_IMPORT_REFERENCES can be mapped to XLA_AE_LINES using the columns gl_sl_link_id and gl_sl_link_table. Data can be transferred from SLA to GL in either Summary or Detail mode. This option is defined for the Event Class, which is attached to the Journal Line Type. Journal Line Type is then attached to the Journal Line Definition, which is finally attached to the Subledger Accounting Method. Please note that if the transfer is done in Summary mode, then the Reference columns will not be populated in either GL_IMPORT_REFERENCES or GL_JE_LINES. Data from SLA, which comes to GL_INTERFACE, can then be imported in either Summary or Detail Mode. This option is set while defining the Ledger in the Accounting Setup Manager. Please note that irrespective of the Mode of Transfer (Detail or Summary), Drilldown will work from GL to all the Subledgers that are using the SLA Engine. The subledger reference information required to drilldown is taken from the SLA tables XLA_AE_HEADERS and XLA_AE_LINES, and not in GL_JE_LINES or GL_IMPORT_REFERENCES. Since Patch 7512923:R12.XLA.A (for R12.0.x), the reference columns REFERENCE5 to REFERENCE10 are populated with entity_id, event_id, ae_header_id, ae_line_num, accounted_cr and accounted_dr.
To identify the mode of Transfer: Column gl_transfer_mode_code in XLA_AE_LINES indicates the transfer mode from SLA to GL. For this column, value S indicates that the transfer is done in Summary mode while D indicates that the transfer is in Detail mode. For the Journal Import mode, the values for specific applications is stored in the table XLA_LEDGER_OPTIONS. This table stores the setup for various applications for the Ledgers defined. The column indicating the Journal Import mode, is transfer_to_gl_mode_code. The values are: P : Summarized by Period A : Summarized by Accounting Date D : No Summarization i.e Detail mode
Summary
The Document thus discusses the following: 1. Drilldown the changes in the Drilldown data, which appears now, the setups that decide what data can be viewed and how data can be secured. 2. Journal Import the transfer of data from Subledgers to General Ledger, various setups that are done for the Ledger which govern the import for various applications. 3. Technical Reference table mapping for journal import and drilldown functionalities.
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support General Ledger Community. To provide feedback on this note, click on the Rate this document link.
Related Products Oracle E-Business Suite > Financial Management > Financials Common Applications > Oracle Subledger Accounting Oracle E-Business Suite > Financial Management > Financial Control and Reporting > Oracle General Ledger Keywords DRILLDOWN; GENERAL LEDGER TRANSFER; GL_IMPORT_REFERENCES; GL_INTERFACE; GL_SL_LINK_ID; IMPORT; INQUIRIES; JOURNAL IMPORT; MO SECURITY PROFILE; ORACLE SUBLEDGER ACCOUNTING (Q169); SLA; SUBLEDGER; SUBLEDGER ACCOUNTING; SUBLEDGERS; TRANSFER TO GL
Back to top Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement
12 of 12
1/24/2012 11:24 PM