Sub ledger Accounting Process:

When Transactions are created in Sub Ledger

1. Entity and Event Creation gets triggered in SLA.
2. Event will be created with Incomplete status.
3. Then move to unprocessed Status.
4. Now the user can account the Event.

Online Accounting/Create Accounting

1. User can accounting transaction either Online or throw running Create Accounting run
2. In R12 Receivables uses the Submit Accounting with internal calls Create Accounting
Program
3. Create Accounting Program Picks up all the events that needs to be accounted and Queue
them up for Processing
4. Then launches the Accounting program
5. Accounting Program in the main program that performs the required validations and
generates the lines in SLA and marks the lines with appropriate status( Accounted Or Error)

R12 Transfer to GL Process:

Accounting Program
(Transfer to GL=Y)

Transfer Journal Entries to GL

Concurrent Program

Online Accounting
with Final/ Post

GL_Interface Table

XLA_GLT_<Group_id>

Journal Import
Success

GL Header/Lines Created
GL Balances updated
SLA header(s) updated with Transferred Status

Error

SLA Headers are updated with Not

transferred Status

Accounting Flow in Receivables

1.
2.
3.
4.
5.
6.
7.
8.

Submit Accounting
Request Submission
Accounting Program Log file
Application Accounting Definition (AAD) Package
Create Accounting Out-put File
Journal Import out-put file
GL Summarization
Transfer Journal Entries to GL

Submit Accounting
Batch Accounting in Receivables is done via Submit Accounting Concurrent Program which might launce
Revenue Recognition or any other AR specific Program before spawning SLA owned create Accounting.

Request Submission

Accounting Program Log file

Accounting Application Definition (AAD) Package

This is the system generated package when user click on Validate button on AAD or when
Validate Accounting Definition Concurrent Program is run
Format of the package
o XLA_<5 Digit Application_id>_AAD_<owner>_<6DigitHashid>_PKG
o Ex: XLA_00222_AAD_S_000001_PKG
Owner: S for seeded and C for Custom
This PKG is used by Accounting Program to get the setup information to account transcation
and apply rules.
If any custom AAD is changed, the changes will be impacted accounting process only after AAD
is validated
Query to find AAD Package
select product_rule_code,compile_status_code,enabled_flag,product_rule_type_code,
product_rule_hash_id from xal_product_rules_fvl a where name like 'Receivable Default Accrual'
and amb_context_code='Default'

GL Summarization
GL Transfer can be done in Detailed Mode or Summary Mode.
If it is Detailed Mode the level of Detail in GL is same as level of detail in SLA. There will be one
to one mapping between xla_ae_lines and gl_je_lines tables
If it is Summarized mode Multiple journal are summarized into one journal entry per day or
per period based on summary criteria. In this case there will be many to one mapping between
xla_ae_lines and gl_je_lines tables
There are 2 setup options which controls journal summarization
i)
This is at Accounting Setup manager page under sub ledger accounting option
ii)
And again at Accounting Method Builder @ Journal Line Type(JLT)

Drilldown Process:
GL Drilldown Process is controlled by MO Profiles and SLA: Enable Subledger Transaction Security in
GL
GL Responsibility
Journal Entry Inquiry
Review Journal

GL Responsibility

Inquiry

Account Analysis Drill down

Line Drill Down

Subledger Accounting Data Flow:

1. Data is populated in xla_transaction_entities & xla_events when the transcation is created.

2. xla_transaction_entities drive table. We cannot see any data in this table unless we set org
context
3. we can use the synonym xla_transaction_entities_upg
4. source_id_int_1 in xla_transaction_entities links SLA with respective subledgers

5. customer_trx_id / cash_receipt_id will be mapped to source_id_int_1 in

xla_transaction_entities
6. When the transaction is created event is created in xla_events with event_status_code= I
and process_status_code=U when the transaction is completed event_status_code =U
and process_status_code=U

7. Draft Accounting:
o The event picks for accounting as long as event_status_code = U , irrespective of the
value in process_status_code.
o For time the data gets deleted and gets recreated. Hence ae_header_id keeps changing
for each create accounting run with Draft accounting.

8. Final Accounting

9. Transferred to General Ledger.

10. Drill Down

GL_JE_HEADERS.JE_FROM_FROM_SLA_FLAG controls the line drill down functionality.
Y = New R12 Data, Drilldown opens self-service page with SLA Data
U = upgraded data , Drilldown opens self-service page with SLA Data
Null = Not Upgraded, Drilldown opens Transactions workbench (like 11i)
N = Line drilldown button is disabled
View Journal entry fetches the data from SLA tables using the link between GL and SLA
View Transaction fetches the data from Receivables tables using the link between SLA and AR