Drill down functionality enables users to navigate from a Journal in General Ledger to the Sub ledger Journal Entry in SLA and from there to the transaction which has resulted into that journal.
To enable Journal drill down from General Ledger, the "Import Journal References" option should be enabled for the Source.
This can be checked under General Ledger Responsibility:
Setup -> Journal -> Sources -> Define.
Only when this is enabled, the reference data is populated by SLA engine.
The Drill down in Release 12 is different from the prior releases of the Application. R12 drill down is Web based and not in the Forms. The following screenshots show the Drill down functionality in Release 12:
Navigation to perform Drill down is the same as in Release 11i:
Only when this is enabled, the reference data is populated by SLA engine.
The Drill down in Release 12 is different from the prior releases of the Application. R12 drill down is Web based and not in the Forms. The following screenshots show the Drill down functionality in Release 12:
Navigation to perform Drill down is the same as in Release 11i:
· Journals -> Enter -> Review Journal
· Select the journal line and click on “Lines Drill down”.
Drill down can also be performed from: Tools -> Drill down
Drill down open the Web page instead of a Form.
The SLA Page for Drill down shows the following:
· GL Journal Line information
· Sub ledger Journal Line information
There are two Options available on this SLA page:
· View Transaction
· View Journal Entry
View Transaction’ will take us to the Sub ledger Transaction form. E.g for the current journal line, since the Source was Payable, it opens Invoice Workbench.
‘View Journal Entry’ will take to the Sub ledger 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 Sub ledger Transaction.
Some of the important fields in header part of the Sub ledger Transaction Journal are:
Some of the important fields in header part of the Sub ledger Transaction Journal are:
· Ledger Name
· Journal Entry Status
· Balance Type
· GL Date
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.
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
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 Sub ledger Journal Entry page.
The important details in this section are:
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 sub-ledgers side.
Thus the Drill down from General Ledger, takes us to the Sub ledger Journal Entry which shows the details of the Sub ledger journal. From here we can further drill down to the Sub ledger Transaction.
Profile Options related to Drill down:
Thus the Drill down from General Ledger, takes us to the Sub ledger Journal Entry which shows the details of the Sub ledger journal. From here we can further drill down to the Sub ledger Transaction.
Profile Options related to Drill down:
· SLA: Enable Sub ledger 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.
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.
Source: Support.oracle.doc.
