Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Diagnostics SLA

Posted on September 18th, 2011 by Sanjit Anand ||Email This Post Email This Post

The SLA diagnostic framework provides features to review the journal entries created by the Subledger Accounting program. It provides the input data used for each transaction, such as the following:

  • Transaction objects
  • Ledger information
  • System sources
  • Source values

In order to do a SLA Diagonostic, you have to do these steps as pre-requsite;

  • enable profile option: SLA Enable Diagnostics to Yes
  • run Create Accounting program which then also populates the diagnostic tables.
  • run Transaction Objects Diagnostics to view the diagnostic report.

Diagnostics SLA1

SLA Enable Diagnostics

  • Reset profile option: SLA Enable Diagnostics to No

Diagnostics SLA

  • once done , run the System Administrator submits the Purge Transaction Objects Diagnostics concurrent request.

Hope this post helps in troubleshooting accounting error when you have deal with SLA.

Posted in Subledger Accounting | No Comments »

Supporting References In Release 12 SLA

Posted on September 11th, 2011 by Sanjit Anand ||Email This Post Email This Post

Supporting References enables users to enter additional information for the journal entry header and lines that can be used for analytical purposes. This functionality was earlier known as Analytical Criteria. This enhancement was released in R12.0.3.

Business Benifits of Supporting references may be used as follows:

  • To provide additional business information about a subledger journal entry at the header or line level
  • To establish a subledger balance for a particular source value or combination of source values for a particular account
  • To assist with reconciliation of account balances, and
  • For financial and managerial analysis

The use of supporting references is optional, consist of these steps in order to use.

  1. Define a Supporting Reference
  2. Attach the Supporting Reference to the Journal Line Type (JLT)
  3. Validate the Applications Accounting Definitions

In R11i, additional data was interfaced to GL on the journals using Descriptive Flexfields where as R12 With this, customers can create customized sources as Supporting References and pass values into those sources from Subledgers like AP/AR/PA etc. Supporting references (SR) are associated at the Event Class Level. These SRs are stored in XLA_AE_LINE_ACS and associated using ae_header_id/ae_line_num. This helps link back to XLA_AE_LINES records.

From XLA_AE_LINES, the link to GL is using GL_SL_LINK_ID and GL_SL_LINK_TABLE

For setup of Supporting References, there are 3 options

  • Always: Supporting Reference Balances are maintained always on a specific Code Combination and it keeps on accumulating once it is defined. At the end of a Financial Period, the balances are carried forward as the opening balances for the next financial period.
  • Based on Account: Supporting Reference Balances are maintained on a specific Code Combination & it gets accumulated till the end of a financial period. The closing balances of a Financial Period are not carried forward as the opening balances of the next financial period; rather the balance is rolled back to zero (0) at the beginning of the next financial period.
  • Never: Supporting Reference Balances are not maintained for that Supporting Reference, it is only used as an additional reference attribute.
    When the Create Accounting program is run in the “Final” mode for any subledger, it spawns the program “Update Subledger Balances” internally and the balances are updated in the XLA_AC_BALANCES table.

dgreybarrow Supporting References – What Tables for Analytical

Here are the list of table. If you have plan to do some custom reporting for Analytical for Opertional reporting you can understand the data model as per figure below.


SLA Supporting Ref


dgreybarrowSupporting Refrence for Manual created Refrence

In R12, supporting references were introduced and the UI enables a user to However, the current version of manual journal creation API has not been supported to capture. Check it out with latest version of the code.

Posted in Subledger Accounting | 2 Comments »

Manual Subledger Journal via XLA

Posted on August 8th, 2011 by Sanjit Anand ||Email This Post Email This Post

dgreybarrow Manual Subledger Journal

A manual subledger journal entry is not associated with a transaction or document of a subledger application. When users create a manual subledger journal entry, it is created with the event class and event type Manual that is seeded automatically when the subledger application is registered.

dgreybarrow Why Its Needed

Manual entries are typically adjustments in nature. If the adjustments are due to specific subledger activity such as Payables or AR or FA, then you may want to enter an SLA manual entry instead of a GL entry.

Such entries to recorded in SLA are tied the subledger source and therefore provided more accurate subledger accounting reporting.

You need to have account, debit, and credit amounts, and accounting class in Order to pass a manual entry. in case if you have to optionally enter third party information then description, and currency details for each line of the subledger journal entry is important.

Read the rest of this entry »

Posted in Subledger Accounting | 1 Comment »

API than can be used to load Journals into Subledger Accounting (SLA)

Posted on August 6th, 2011 by Sanjit Anand ||Email This Post Email This Post

Oracle provides the ability to enter manual sub-ledger journals via a button on the SLA Journal Inquiry pages.

A manual subledger journal entry is not associated with a transaction or document of a subledger application. If you are considering using the manual SLA journal feature to represent accounting in legacy systems, you can take the advantage of API which allows you to import such transactions into SLA rather than into the GL directly (via the GL interface).

You can use the API XLA_JOURNAL_ENTRIES_PUB_PKG and any of these functions:

  • Create_Journal_Entry_Header: This is used creates a new subledger journal entry header
  • Update_Journal_Entry_Header: This is used to modifies an existing manual subledger journal entry header, if journal entry is not Final and GL_DATE used must belong to a valid accounting period.
  • Delete_Journal_Entry:This deletes all information of a subledger journal entry including journal entry header and journal entry line
  • Create_Journal_Entry_Line:This is used to Create the JE line
  • Update_Journal_Entry_Line :This is used to Delete the JE line
  • Delete_Journal_Entry_Line :This is used to Delete the JE line
  • Complete_Journal_Entry: This is used to completes a subledger journal entry
  • Reverse_Journal_Entry : This is used to reverse the entry.

These API’s you can find more on Oracle Financial Services Accounting Hub Implementation Guide Release 12 Part No. B14420-01

You don’t need to have an FSAH License to be able to use those APIs.

Posted in R12, Subledger Accounting | 1 Comment »

SLA enhancements :R12.1.1, R12.1.2 & R12.1.3

Posted on July 16th, 2011 by Sanjit Anand ||Email This Post Email This Post

dgreybarrow R12.1.1 and R12.1.2 SLA enhancements

When you create new sub ledgers for reporting currencies, a new concurrent program SLA Secondary/ALC Ledger Historic Upgrade is provided to initialise the historical transactions for proper reconciliation.

This program retroactively posts historical accounting data from primarly ledgers to the newly created secondary or reporting currency ledgers.

Read the rest of this entry »

Posted in Subledger Accounting | No Comments »

Its all about GL Drilldown

Posted on May 27th, 2011 by Sanjit Anand ||Email This Post Email This Post

dgreybarrow What is GL Drilldown

GL Drilldown feature allows users to view sub ledger transaction information for the GL journal line created by importing information from the sub ledger products. Users are able to view sub ledger transaction information for different Products using the GL Drilldown feature by navigating to the Product UI that is the source of such transaction.

The Drill Down feature is invoked by Drill Down button on Journal Review screen. The Drill Down button opens XLA Drill Down UI. The UI shows product transaction and accounting information related to journal line.

This post is another extension of my previous post.

If you are starting Drilldown from General Ledger that will takes you SLA Journal details. Typically the flow is as:

  1. Drilldown is performed from Journal lines in General Ledger, that means data is stored in the table GL_JE_LINES. The link between SLA data and data in GL is through the table GL_IMPORT_REFERENCES.
  2. This data is populated in GL_IMPORT_REFERENCES only if “Import References”¨ option is selected in the Journal source definition.
  3. Once Populated, the data can be mapped from GL_JE_LINES to GL_IMPORT_REFERENCES table using the columns je_header_id and je_lines_num.
  4. From subledger side , SLA Journal line data is stored in the table XLA_AE_LINES, which is connected with its header which stored in XLA_AE_HEADERS.
  5. Then data in GL_IMPORT_REFERENCES can be mapped to XLA_AE_LINES using the columns gl_sl_link_id and gl_sl_link_table.
  6. When Transfer happen, typically it can be done either Summary or Detail mode, which typically configure when you define the Event Class, which is attached to the Journal Line Type.
    • Take a note, if the transfer is done in Summary mode, then the Reference columns will not be populated in any of these table GL_IMPORT_REFERENCES or GL_JE_LINES
  7. Then Journal Line Type is then attached to the Journal Line Definition, which internally hookup with Subledger Accounting Method.
  8. Data from SLA, which comes to GL_INTERFACE, can then be imported in either Summary or Detail Mode.
  9. The option for summary or details is configure in the Accounting Setup Manager
  10. If you are importing data in Summary mode, then the Reference columns are populated in GL_IMPORT_REFERENCES (provided data has come in Detail mode from SLA), while GL_JE_LINES will not have the Reference columns populated.
  11. On the other hand if data is imported in Detail mode, both GL_IMPORT_REFERENCES and GL_JE_LINES tables will have the Reference columns populated (again provided the data has come in Detail mode from SLA).
  12. Table XLA_AE_LINES Column gl_transfer_mode_code gives the information for the transfer mode from SLA to GL.
  13. For the Journal Import mode, the values for specific applications is stored in the table XLA_LEDGER_OPTIONS which stores the setup for various applications for the Ledgers defined. The column indicating the Journal Import mode is transfer_to_gl_mode_code, which have three values as P (Summarized by Period), A(Summarized by Accounting Date) or D(No Summarization i.e. Detail mode)
  14. The XLA_TRIAL_BALANCES table is populated after successful journal import.
  15. You can use the different SLA reports for pulling SLA data.
  16. Last but not the least, drilldown will work from GL to all the Subledgers that are using the SLA Engine

Posted in Oracle General Ledger, Subledger Accounting | No Comments »

R12 SLA : Profile Options related to SLA

Posted on May 27th, 2010 by Sanjit Anand ||Email This Post Email This Post

Some of the key Profile Options for SLA that you should aware of;

  • SLA: Accounting Methods Builder Context
  • SLA: Additional Data Access Set
  • SLA: Allow Reports Journal Source Override
  • SLA: Disable Journal Import
  • SLA: Display Timestamp on Trace
  • SLA: Enable Data Access Set Security in Subledger
  • SLA: Enable Diagnostics
  • SLA: Enable PL/SQL Profiler
  • SLA: Enable SQL Trace
  • SLA: Enable SRS Log/Output
  • SLA: Enable Subledger Transaction Security in GL
  • SLA: Enable Trace
  • SLA: Flush Trace File
  • SLA: Oracle Forms Trace Mode
  • SLA: SRS Trace Mode
  • SLA: Trace File Override Directory
  • SLA: Trace File Override Filename
  • SLA: Trace Level
  • SLA: Trace Timeout

dgreybarrow Similar Post

Posted in Subledger Accounting | No Comments »

Month End Close with Oracle R12

Posted on June 22nd, 2009 by Sanjit Anand ||Email This Post Email This Post

Fig 1 below outlines the period end dependency for Oracle Payables, Oracle Purchasing, Oracle Inventory, Oracle Receivables, Oracle Assets, Oracle Order Management, Oracle Projects and Oracle General Ledger (Release 12).
Period Closure

Fig 1: Period Close dependecy among the modules

If you are coming from 11i then you might see beacuse of SLA there would be additional steps you need to perform.Fig 2 will be a quick compare of steps between two versions.

Period Closure1

Fig 2: Process and flow changes between two versions

In almost all modules the period end process consist of 5-6 major activity as:

  1. Completing the Transactions
  2. Creating Accounting
  3. Followed by Reconcile Transactions
  4. Post to GL
  5. Reconcile Accounting
  6. Close Period

You can check some of closure process & checklist from previous post :


Posted in Oracle General Ledger, Oracle Payable, Oracle Purchasing, Oracle Receivable, R12, Subledger Accounting | No Comments »

R12 SLA :Reporting using SLA

Posted on December 11th, 2008 by Sanjit Anand ||Email This Post Email This Post

With SLA, all accounting reports normally use SLA data which store as the single repository to generate and output accounting related reports.

These are some of the reports which can be used for SLA reporting.

  • Account Analysis Report
  • Accounting Program
  • Complete Multiperiod Accounting
  • Create Accounting
  • Journal Entries Report
  • Open Account AP Balances Listing (Accounts Payable Trial Balance)
  • Subledger Accounting Balances Update
  • Subledger Multiperiod Accounting and Accrual Reversal Report
  • Third Party Balances Report
  • Trading Partner Summary Report
  • Transfer Journal Entries to GL
  • Validate Application Accounting Definitions

dgreybarrow Similar Post

Posted in Subledger Accounting | No Comments »

A note on sub ledger reconciliation reports during period closure

Posted on October 10th, 2008 by Sanjit Anand ||Email This Post Email This Post

This is short note for subledger reconciliation reports which helps during period end closure.

Reconciliations – Subledger Accounting on-line account reconciliation to streamline the reconciliation process.

  1. Subledger Journal Entry Report : This will display detailed Header & Line information for Subledger and General Ledger journal entries by Source & Category
  2. Subledger Account Analysis : This report can be used to display Transactions transferred to & posted to a GL account for a period or range of periods
  3. Payables Third Party Balances : If you are managing third party account, then you can see Balances for your Third Party Control accounts
  4. Open Items Listing :
    1. For this you need define this report by Segment or Accounting Flexfield.
    2. This report display Detail/Summary by Accounts/Third Party.
    3. This report output available in multiple output formats .
    4. This will shows only Open Transactions.
    5. This is very similar to SAP Open Item Report seeded report. User coming from SAP to Oracle Financial now find similar report with less information. Still SAP’s Compact Journal Report is missing from Oracle’s SLA.
  5. Subledger Period Close Exception Report :During the period end run the Subledger Period End Close Exception report, and you can find the data with these information.
    1. Incomplete: Not ready for accounting, Run Subledger’s validation programs!
    2. Unprocessed: Transactions exist but have as yet not been accounted
    3. This report help in resolving exceptions quickly so that exceptions are not left to slow down the period-end close

Posted in Subledger Accounting | 3 Comments »

« Previous Entries