What are the tables involved in the Transfer to GL and GL posting?

Subledger Tables
XLA_AE_HEADERS
XLA_AE_LINES
XLA_DISTRIBUTION_LINKS
Transfer Journal Entries to GL (XLAGLTRN) process takes the subledger journals and inserts
records into the Interface Tables
Interface Tables
GL_INTERFACE / XLA_GLT_<groupid>
Journal Import (GLLEZL) then reads from the interface table and creates records in the GL Tables
GL Tables
GL_JE_BATCHES
GL_JE_HEADERS
GL_JE_LINES
GL_IMPORT_REFERENCES
GL Posting process then posts to the GL_BALANCES table.
What are the different methods to transfer Subledger journals to GL?
a) ONLINE MODE
GL Transfer can be spawned during Online Accounting using the Final Post option for a specific
document (Example: AP Invoice and AR Transaction).
Example: Navigation in Payables: Invoices/Entry/Invoices: Action: Create Accounting/Final Post.
This spawns the GL Transfer, the Journal Import, Data Manager and the GL Posting processes. This
request transfers ALL the final accounted data for that document. This method of transfer uses the
interface table GL_INTERFACE to move the journals to the general ledger.
b) BATCH MODE
GL Transfer can also be spawned by the Create Accounting concurrent request when submitted with
the Transfer to GL parameter set to Y.
Example: Navigation in Payables: Other/Request/Run: Create Accounting
This spawns the journal import and the data manager processes. The GL Posting process is spawned
if the Post to GL parameter is set to Yes when submitting the Create Accounting. This request
transfers all the final accounting created by the Create Accounting request that spawned it. This
method uses the interface table XLA_GLT_<groupid>.

c) CONCURRENT REQUEST
GL Transfer can be submitted in standalone mode using the concurrent request Transfer Journal
Entries to GL.
Example: Navigation in Payables: Other/Request/Run: Transfer Journal Entries to GL
This spawns the Journal Import and the Data Manager programs. This request transfers all the final
accounting that exists for the given ledger and end date. This method uses the interface table
XLA_GLT_<groupid>.
What is the setup option that determines the level of detail in the accounting
lines created for a specific transaction in XLA_AE_LINES?
Each Journal Line Type (JLT) can be setup as required to result in either detailed or merged lines in
XLA_AE_LINES.
Navigation: Accounting Setups : Subledger Accounting Setup : Accounting Methods Builder :
Journal Entry Setups
Form :Define Journal Line Types
Field : Merge Matching Lines
The different options are as follows:
1) ALL The matching lines in XLA_DISTRIBUTION_LINKS for the specific accounting header and
specific journal line type (example: LIABILITY) are merged to create records in XLA_AE_LINES.
2) DR/CR The matching lines in XLA_DISTRIBUTION_LINKS, for the specific accounting header
and specific journal line type (example: LIABILITY) with debit side entries, are merged to create one
debit entry in XLA_AE_LINES. The matching lines with credit side entries are merged to create one
credit side entry in XLA_AE_LINES.
3) NO Lines in XLA_DISTRIBUTION_LINKS for the specific accounting header and specific
journal
line type (example: LIABILITY) are not merged and copied into XLA_AE_LINES.
NOTE: This setup applies to merging lines within a specific transaction.
What is the setup option that determines if transfer to GL is in detail or
summarised mode?
There are two variables that determine how the data is transferred to GL from the subledger tables
XLA_AE_HEADERS and XLA_AE_LINES. These setups determine whether accounting data from
across multiple transactions in the subledger will be merged or not merged while inserting into rows
in the GL_JE_HEADERS and GL_JE_LINES tables.
a) Subledger Accounting Options

Navigation: Accounting Setups : Ledger Setup : Define : Accounting Setups

Choose the ledger
Click on Update Accounting Options
Scroll to Subledger Accounting Options in the Primary Ledger section
Click on Update Icon
Click on Update Icon against the Application to be setup(Example: Payables)
Field: General Ledger Journal Entry Summarization
This can be set to ONE of the following:

Summarize by GL Period

Summarize by GL Date

No Summarization

This setup determines if the accounting header is summarized or not.

b) Journal Line Types
Navigation: Accounting Setups : Subledger Accounting Setup : Accounting Methods Builder :
Journal
Entry Setups
Form :Define Journal Line Types
Field: Transfer to GL
This can be set to Summary or Detail
This setup determines if the accounting lines in XLA_AE_LINES are summarized during transfer to
GL.
Note 1: Lines cannot be summarised if the headers are not summarised.
If General Ledger Journal Entry Summarization is set to No Summarization, the Transfer to GL
setup in the Journal Line Types are irrelevant. The lines and headers are not summarized in this
scenario.
Note 2: Irrespective of transfer in Detail or Summary, there is always a one-to-one correspondence
between the XLA_AE_LINES and GL_IMPORT_REFERENCES tables.
What are the different combinations of the two setup options that determine
if transfer to GL is in summary or detail and the corresponding outcome?
JLT
-Transf
GL Journal Entry

er to

Summarization

GL

Expected behavior

Summarized at both
Summarize(By GL

Summar

GL_JE_HEADERS and

Date or Period)

GL_JE_LINES
Summarized at

Summarize(By GL
Date or Period)

GL_JE_HEADERS, detail
Detail

GL_JE_LINES
Detailed at
GL_JE_HEADERS and

No Summarization

Detail

GL_JE_LINES
Detailed at

No Summarization

Summar

GL_JE_HEADERS and

GL_JE_LINES

Note: The last two options cause the level of detail in the GL to be the same as in the Subledger.

WHAT COLUMNS ASSOCIATE GL DATA BACK TO THE SLA DATA?

Since there is always a one-to-one correspondence between XLA_AE_LINES and
GL_IMPORT_REFERENCES, they are used to link GL and the subledgers.
GL_IMPORT_REFERENCES.gl_sl_link_id => XLA_AE_LINES.gl_sl_link_id
GL_JE_BATCHES.group_id => XLA_AE_HEADERS.group_id

What columns indicate the Transfer Status of accounting data in subledger?

The XLA_AE_HEADERS table shows the transfer status of the accounting data, after successful
transfer to the GL and Journal Import:
XLA_AE_HEADERS.gl_transfer_status_code = Y
XLA_AE_HEADERS.gl_transfer_date is not null
XLA_AE_HEADERS.group_id is not nullFor 11i data upgraded to R12, the transfer status
can be determined using the followingXLA_AE_HEADERS.gl_transfer_status_code = Y
XLA_AE_HEADERS.gl_transfer_date is null
XLA_AE_HEADERS.group_id is null
XLA_AE_HEADERS.upg_batch_id is not null > indicates 11i data
What is Subledger Accounting?
#Subledger Accounting is a Service, not an Application.
#There are no SLA responsibilities and there is no direct
login to SLA.
#SLA forms and programs are embedded within

standard Oracle Application responsibilities(e.g.

Payables Manager).
o Simply, It is a rule-based accounting engine, toolset &
repository supporting Oracle E-Business Suite modules.
o Allows multiple accounting representations for a single
business event, resolving conflicts between corporate
and local fiscal accounting requirements.
o Retains the most granular level of detail in the
subledger accounting model, with different
summarization options in the General Ledger, allowing
full auditability and reconciliation.
o Introduces a common data model and UI across
subledgers, replaces various disparate 11i setups, providing single source of
truth for financial and management
analysis.

Screen shots of sample Invoice Distribution and It's Accounting

Journal Entries

Simple Illustration on Journal Line Creation in SLA

Please go thorough the AMB components explained below to understand more about this
picture.

What is Accounting Methods Builder(AMB) in SLA?

A set of screens which provides flexibility to create your own subledger accounting set up or

use seeded subledger accounting setup.

You can use the AMB to define the way in which subledger transactions are accounted. This
enables you to create and modify subledger journal line setups and application accounting
definitions. These definitions define the journal entries that enable an organization to meet
specific fiscal, regulatory, and analytical requirements. These definitions are grouped into
subledger accounting methods and assigned collectively to the ledger.
Following picture shows hierarchy of the components in the AMB.

o Each ledger is assigned with SLAM.

o Subledger accounting method(SLAM) which tells what type of accounting method you are
using(Ex: Cash or Accrual) in your ledger.
o Under SLAM, you will find set of Application Accounting Definitions(AAD) for different
subledgers(Ex: Payables, Receivables)
o Under AAD, you will find set of journal line definitions(JLD) for each Event Class(Ex:
Invoices, Prepayments, Payments) and Event Type(Ex: Invoice Validated, Prepay Application,
Payment Created) combination.
o Each journal line definitions(JLD) holds group of JLT's(Ex: Name it Liability, Item Expense,
Gain, Loss, etc), ADR(rules), JED(description) for each Event Class and Event Type
combination.

o Journal Line Types(JLT) contains..

1.
Accounting Attributes(Ex: Accounting Date, Entered Amount,
Accounted Amount, Party Id, etc )
2.
Basic Info which determines journal line properties( Ex: Side(Cr or Dr),
Balance Type(Actual or Encum), TransferToGL(Summary or Detail), etc)
3.
Conditions(This condition need to be satisfied to use this JLT)
o Account Derivation Rules(ADR) (Ex: Accounting segment values. It is
nothing but GL account)
o Journal Entry Descriptions(JED): Which give more information about
transaction (Ex: Invoice/Check details)

Navigation Paths to SLA Forms

Explain AMB Components?

Event Model(Definition of the subledger transaction types and lifecycle)
Event Entities
Group event classes into technical transaction models called event entities.
For example, group the event classes Invoices and Prepayments into the
event entity Invoices because both classes of transaction are stored in the
Payables invoice transaction table (AP_INVOICES_ALL). Event entities enable

you to treat events for a single transaction model in the same way. The event
entity often logically corresponds to a single document used as a basis for
several related transactions.

Event Class
Group accounting event types into user-orientated transaction categories
called event classes. For example, group the event types Invoice Approved,
Invoice Adjusted, and Invoice Canceled into the event class Invoices. Then
assign AMB components, such as journal line types, by event class within the
application accounting definition. This assignment simplifies setup when the
accounting requirements for all event types in a class are the same. Also,
sources assigned to an event class are available for the accounting of all
event types in that event class.
Example
Payables: Invoice, Debit Memo, Prepayment, Payments, Refunds
Receivables: Invoice, Deposit, Receipt, Bill Receivable
Event Type
Each accounting event should be represented by an accounting event type.
These types are registered in the AMB. When subledger journal entries need
to be created, the event type determines which application accounting
definitions should be used to process the accounting event. Application
accounting definitions created in the AMB determine the lines, descriptions,
accounts, and other elements of subledger journal entries.

Example
AP Invoice Events: Validated, Adjusted, Cancelled
AR Receipt Events: Created, Applied, Unapplied, Updated, Reversed

Subledger Accounting Method(SLAM)

The subledger accounting method(SLAM) is a collection of accounting definitions for all the
applications that you will be generating accounting for. Each primary and subledger level or
adjustment secondary ledger is associated with a SLAM, which determines the accounting
rules and standards that will be applied when generating entries for that ledger.
Example:
Standard Accrual, Standard Cash, etc

Application Accounting Definition(AAD)

Use Application Accounting Definitions(AADs) to assign journal line
definitions and header descriptions to event classes and event types. AADs
must be included in a subledger accounting method and assigned to a
ledger. You can group accounting definitions from multiple products, such as
Oracle Payables, receivables Assets into a single accounting method.

Journal Line Definition(JLD)

Journal line type, description, account derivations rules grouped together as
a journal line definition to create the rule for particular event type.

Journal Line Type(JLT)

-Identify the natural side: Debit, Credit, Gain/Loss
-Determine the accounting class
-Set under which conditions the rule will create a line
-Define the values needed for entry line generation, such as amount,
currency, conversion rate information
-Control behavior for certain features i.e. multi period accounting, business
flows, line merging and summarization

Account Derivation Rules(ADR)

Account derivation rules are used to determine the account combinations for
subledger journal entries. You can define various rules in te AMB to
determine how a journal entry account is derived. You can derive accounts
segment by segment or as a complete account combination. This picture
shows an Account Derivation Rule with conditional logic. If the condition
holds for priority 1, then this source (Invoice Liability Account) is used. If not,
SLA uses the source for priority 2(If it is available).

Journal Entry Description

This is useful in finding the actual transaction object details(Ex:
Invoice/Payment details from journal line)
Transaction Object
Example for transaction objects:
ap_invoice_extract_details_v.xdf
ap_invoice_extract_header_v.xdf
ap_payment_extract_details_v.xdf
ap_payment_extract_header_v.xdf
ap_prepayapp_extract_details_v.xdf
ap_system_parameters_extract_v.xdf
Transaction Object is nothing but a view which fetches all transaction
information required to create journal line for particular event class.
AP_INVOICE_EXTRACT_HEADER_V, AP_INVOICE_EXTRACT_DETAILS_V are
transaction objects for event class Invoices. So, accounting for all invoice
type events get transaction information from these transaction objects.

Sources
Each column in the transaction object is defined as Source in the AMB. AMB
uses these sources to get transaction information from Transaction Objects.

Accounting Attributes
Sources are mapped with Accounting Attributes. Accounting Attributes are
bridge between JLT and Sources.

Example
GL Date, Entered Currency Code, Entered Amount, Accounted Amount,
Conversion Rate Date, Conversion Rate Type, Conversion Rate, Distribution
Type, Party Type, Party Identifier, Party Site Identifier

What are the important tables in SLA Accounting?

The XLA_EVENTS table stores records for accounting events generated by subledger
applications. Each product team populates this table by calling Subledger Accounting API and
the respective product team will decide when this table is to be populated during the transaction
life cycle.

The XLA_AE_HEADERS table stores subledger journal entries. There is a one-to-many

relationship between accounting events and journal entry headers.
The XLA_DISTRIBUTION_LINKS table stores detailed distributions for journal entries. This
table stores the data at most granular level and represents data contained in respective
subledger products distribution tables. The detailed distributions stored in this table are merged
into accounting lines and stored in XLA_AE_LINES table. Subledger Accounting uses this table
for processing reversals and business flows.
The XLA_AE_LINES table stores the subledger journal entry lines. There is a one-to-many
relationship between subledger journal entry headers and subledger journal entry lines. This
table will store at least one row for debit and one row for credit for
each accounting entry created. If multiple debit or credit journal entry lines exists for any specific
event type and if the journal line type allows merge matching lines then these lines will be
merged into single line. The unmerged granular level of detail for each accounting line will be
available in XLA_DISTRIBUTION_LINKS table.

What are the Accounting Methods seeded in SLA?

Standard Accrual
Standard Cash
Encumbrance Accrual and Encumbrance Cash
United States Federal
China Standard Accrual
What are the reports available in SLA?
Journal Entries Report
Account Analysis Report
Third Party Balances Report
Period Close Exceptions Report
Open Account Balances Listing