Cost Mangement Subledger Accounting (SLA) Data Flow Chart

Important columns affected:

After a transaction is performed in forms:
mtl_material_transactions.costed_flag = 'N'

After the Cost Manager Picks up the data and processes it:
mtl_material_transactions.costed_flag is Null
xla_events.event_status_code = 'U'
xla_events.process_status_code = 'U'

After the Create Accounting - Cost Management is run:
xla_events.event_status_code = 'P'
xla_events.process_status_code = 'P'
xla_ae_headers.gl_transfer_status_code = 'N'
xla_ae_headers.gl_transfer_date is Null

After the Transfer To GL is run:
xla_ae_headers.gl_transfer_status_code = 'Y'
xla_ae_headers.gl_transfer_date is Not Null


Queries involved:

select * from mtl_material_transactions where transaction_id = '&transaction_id'

select * from mtl_transaction_accounts where transaction_id = '&transaction_id'

select * from XLA_TRANSACTION_ENTITIES_upg where source_id_int_1 = '&transaction_id'

select * from xla_events where entity_id in (select entity_id from XLA_TRANSACTION_ENTITIES_upg where source_id_int_1 = '&transaction_id')

select * from xla_distribution_links where source_distribution_type = 'MTL_TRANSACTION_ACCOUNTS' and source_distribution_id_num_1 in (select inv_sub_ledger_id from mtl_transaction_accounts where transaction_id = '&txnid')

select * from xla_ae_headers where ae_header_id in (select ae_header_id from xla_distribution_links where source_distribution_type = 'MTL_TRANSACTION_ACCOUNTS' and source_distribution_id_num_1 in (select inv_sub_ledger_id from mtl_transaction_accounts where transaction_id = '&txnid'))

select * from xla_ae_lines where ae_header_id in (select ae_header_id from xla_distribution_links where source_distribution_type = 'MTL_TRANSACTION_ACCOUNTS' and source_distribution_id_num_1 in (select inv_sub_ledger_id from mtl_transaction_accounts where transaction_id = '&txnid'))

select * from gl_import_references where gl_sl_link_table = 'XLAJEL' and gl_sl_link_id in (<give the gl_sl_link_id from result of query 7>)

select * from gl_je_lines where je_header_id in (<give the je_header_id from result of query 8>) and je_line_num in ('<result from query 8>')

select * from xla_accounting_errors where event_id in (select event_id from xla_events where entity_id in (select entity_id from XLA_TRANSACTION_ENTITIES_upg where source_id_int_1 = '&transaction_id'))

GL - XLA - AR Functionality

There is no one-to-one mapping between AR, XLA and GL.

The data that actually posts to the GL comes from the XLA tables and not AR. Depending on the Application Accounting Definition (AAD) rules you have defined, one row that appears in AR could become 10 rows in XLA_DISTRIBUTION_LINKS, but when the data is posted into the GL, the accounts of the same type and ccid are merged to a single entry.

For example, a transaction could have 34 gl_dist rows, but 201 rows in ar_distribution_links, but when it actually posts, consolidates to 9 rows in gl_import_references.

The main link to bind information together is the GL_SL_LINK_ID. This field exists in GL_JE_LINES, GL_IMPORT_REFERENCES and XLA_AE_LINES tables.

Also, the XLA_DISTRIBUTION_LINKS table contains the application_id, event_id, ae_header_id, ae_line_num from the XLA Tables and source_distribution_id_num_1 will be the cust_trx_line_gl_dist_id in the case of a transaction.

ACTION: COMPLETE TRANSACTION:

RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID = RA_CUST_TRX_LINE_GL_DIST_ALL.CUSTOMER_TRX_ID
RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID = XLA_TRANSACTION_ENTITIES.SOURCE_ID_INT_1
XLA_TRANSACTION_ENTITIES.ENTITY_ID = XLA_EVENTS.ENTITY_ID

ACTION: RUN CREATE ACCOUNTING: 

RA_CUST_TRX_LINE_GL_DIST_ALL.CUST_TRX_LINE_GL_DIST_ID = XLA_DISTRIBUTION_LINKS.SOURCE_DISTRIBUTION_ID_NUM_1
XLA_AE_LINES.AE_HEADER_ID = XLA_DISTRIBUTION_LINKS.AE_HEADER_ID
XLA_AE_HEADERS.AE_HEADER_ID = XLA_DISTRIBUTION_LINKS.AE_HEADER_ID

ACTION: RUN TRANSFER TO GL: 

XLA_AE_LINES.GL_SL_LINK_ID = GL_JE_LINES.GL_SL_LINK_ID
XLA_AE_LINES.GL_SL_LINK_ID = GL_IMPORT_REFERENCES.GL_SL_LINK_ID
GL_IMPORT_REFERENCES.JE_HEADER_ID = GL_JE_LINES.JE_HEADER_ID
GL_IMPORT_REFERENCES.JE_HEADER_ID = GL_JE_HEADERS.JE_HEADER_ID

Subledger Account Analysis Report using parameter 'Journal Entry Source' in Release 12

1. Parameter 'Journal Entry Source' (parameter code p_application_id) in Subledger
Account Analysis Report by default is display disabled.
2. Enable the display of this parameter from System Administrator Responsibility and submit the
report from a Subledger or General Ledger responsibility.
3. If no source is provided or the parameter is not enabled the report by default would run for
all sources for the given account range as per the standard behavior of Account Analysis Report.

If the parameter is not available:
1.Download and review the readme and pre-requisites for Patch.9668652:R12.XLA.B
2.Ensure that you have taken a backup of your system before applying the recommended patch.
3.Apply the patch in a test environment.
4.Confirm the following file versions:
xlapatch/115/import/USxla120cp.ldt120.131.12010000.40
xlapatch/115/publisher/defsXLAAARPT.xml120.29.12010000.13
xlapatch/115/publisher/templates/USXLAAAR01.rtf120.12.12010000.10
xlapatch/115/sqlxlarpaan.pkb120.25.12010000.10
xlapatch/115/sqlxlarpaan.pkh120.12.12010000.6
You can use the commands like the following: strings -a $XX_TOP/filename |grep '$Header'
5.Retest the issue.
6.Migrate the solution as appropriate to other environment

How To Transfer Reconciliation References From FA Subledger To GL

Navigation: Setup > Financials > Subledger Accounting > Accounting Methods Builder > Journal Entry Setups > Journal Line Types

1. Query a seeded Journal Line Type and copy it by clicking on the Copy button at the bottom left of the form

2. Give your Journal Line Type code, name, and description a meaningful name.

3. Click on the Accounting Attribute Assignments button at the bottom right of the form

4. Pick a source for the Reconciliation Reference

5. Save.

Navigation: Setup > Financials > Subledger Accounting > Accounting Methods Builder > Methods and Definitions > Journal Line Definitions

6. Link the Journal Line Type just created to the Journal Line Definition. Copy a seeded one and create your own if needed.

7. Assuming that the JLD is already linked to the Application Accounting Definition, validate the Application Accounting Definition either in the form or via the concurrent program 'Validate Application Accounting Definitions'.
Assuming also that the Application Accounting Definition is already linked to the Subledger Accounting Method which in turn is already linked with the ledger, Create Accounting can now be run.

8. Once Create Accounting, Journal Import and the Post program in GL have completed, one can reconcile either manually or run Automatic reconciliation in GL.

Setup Steps to Enable GL Reconciliation from Subledgers in Oracle R12

1] Customize the complete Subledger Accounting (SLA), reconciliation reference is enabled as a part of Journal Line Type.

2] For the Custom SLA ensure that the Journal Line Type for the corresponding line for the corresponding subledger is set to 'Detail'. Navigation: Setup : Accounting Setups : Subledger Accounting Setup : Accounting Methods Builder : Journal Entry Setups

3] Enable 'Reconciliation Reference' for this particular line by selecting something in the 'Source' field LOV, click on 'Accounting Attribute Assignments' in the Journal Line Type form. Note that such changes can not be made in Standard (Seeded) SLA setups, hence a completely customized SLA is required to enable reconciliation references

4] Ensure that the customized SLA is attached to the concerned Ledger as well. this can be done using Accounting Setup Manager (ASM). Navigation: Setup : Financials : Accounting Setup Manager

5] Ensure that reconciliation is enabled for the ledger as well, this can be done using Accounting Setup Manager (ASM). Navigation: Setup : Financials : Accounting Setup Manager

6] Ensure that the code combination which is used in Subledger and transferred to General Ledger as a part of Create Accounting process is enabled for Reconciliation. This can be done at Setup > Accounts > Combinations form, there is a new field in this form in R12 called as 'Reconcile'. This should be enabled for the required code combination. If this is enabled then only journal import imports the reconciliation references.

To to automatically propagate the Reconciliation Flag of a segment value to all account code combinations which contain that segment value Program - Inherit Segment Value Attributes needs to be run.