Académique Documents
Professionnel Documents
Culture Documents
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
Summarize by GL Period
Summarize by GL Date
No Summarization
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.
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
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