This action might not be possible to undo. Are you sure you want to continue?
1] Modified 14-JUL-2010 Type TROUBLESHOOTING Status PUBLISHED
In this Document Purpose Last Review Date Instructions for the Reader Troubleshooting Details 1. UNDERSTANDING THE AP-SLA-GL RECONCILIATION 2. RECONCILING THE AMOUNTS AND UNDERSTANDING THE DATA FLOW BETWEEN SLA AND GL Key Tables and Columns used for Reconciliation 3. ESTABLISHING A BASELINE FOR ADDRESSING 11i UPGRADE ISSUES Scenario Technical perspective Common Reasons why Reconciliation issues are Encountered During the Upgrade Analyzing the Difference in the R12 Trial Balance How to Analyze the Data Even Further 4. RECONCILING R12 DATA AND ADDRESSING R12 TRIAL BALANCE-GL ISSUES 5. UNDERSTANDING HOW UNDO ACCOUNTING CAN IMPACT RECONCILIATION Scenario Original Event/Accounting How to find events/entities created by Undo Accounting 6. APPENDIX References
Applies to: Oracle Payables - Version: 12.0.0 to 12.0.5 - Release: 12.0 to 12.0 Information in this document applies to any platform. Purpose This document offers a technical perspective of the AP-GL Reconcialition. Its purpose is to assist the reader with reconciliation issues. In the simplest terms, AP-GL reconciliation means tallying the amounts in Accounts Payable (i.e., AP) for a CCID/Supplier and reconciling it to the figures in the General Ledger (GL). This document covers the following topics:
y y y y y y
Understanding the AP-SLA-GL reconciliation Reconciling the amounts and understanding the data flow between SLA and GL Establishing a baseline for addressing 11i upgrade data related issues. Reconciling R12 data and addressing R12 Trial Balance-GL issues Understanding how UNDO Accounting can impact Reconciliation Appendix
Last Review Date
We assume all batches are posted.December 4. We only reconcile data that has been transferred to GL. It is important to understand the information captured in XDL. It captures the invoice and payment amounts. UNDERSTANDING THE AP-SLA-GL RECONCILIATION In R12. 2. It is important to note the following: 1. XLA_AE_LINES (XAL) . The reconciliation process ensures that the following three areas are reconciled: o Amounts in the XLA_AE_LINES (XAL) table correspond to the XLA_TRIAL_BALANCES (XTB) table o Amounts in the XLA_AE_LINES (XAL) table correspond to the GL_JE_LINES (GJL) table.payment_history_id) SOURCE_DISTRIBUTION_TYPE APPLIED_TO_ENTITY_ID APPLIED_TO_SOURCE_ID_NUM_1 APPLIED_TO_DIST_ID_NUM_1 REF_AE_HEADER_ID REF_TEMP_LINE_NUM REF_EVENT_ID AP_PMT_DIST. y y y XLA_TRIAL_BALANCES (XTB) -This is the SLA Trial Balance table. XLA_DISTRIBUTION_LINKS (XDL) Table XDL table col Description Ref to AP table col DIST_ID of the current transaction (for invoice SOURCE_DISTRIBUTION_ID_NUM_1 ap_invoice_distributions_all. It captures the lowest level granularity of a transaction's accounting. RECONCILING THE AMOUNTS AND UNDERSTANDING THE DATA FLOW BETWEEN SLA AND GL In this section. 3. with respect to a supplier.ap_payment_hist_dists. we will discuss how to reconcile the amounts and show you how the data flows between SLA and specific GL tables and columns.This is the SLA Distributions table. AP does not store any accounting information. diagnostic tools are included in the document to assist in troubleshooting.invoice_distribution_id. for payment . such as a Prepayment. It is built using the data from the AP_LIABILITY_BALANCES in 11i and detailed information captured in XDL for R12 data. Troubleshooting Details 1. AP_PREPAY ENTITY_ID of the invoice/upstream transaction Invoice_id in case of LIABILITY line of the payment Invoice_distribution_id against which this payment_distribution_id is applied AE_HEADER_ID of the invoice/upstream transaction TEMP_LINE_NUM of the invoice/upstream transaction EVENT_ID of the invoice/upstream transaction AP_INVOICE_PAYMENTS_ALL & AP_PAYMENT_HIST_DIST 2. AP_INV_DIST. When possible. or it could also mean a transaction. Reconciliation of the posted transactions is done using data in the Subledger Accounting (SLA) tables. 2008 Instructions for the Reader A Troubleshooting Guide is provided to assist in debugging a specific issue. Applied Transaction means a transaction such as Payments.This is the SLA Detailed Lines table. which is applied to an Invoice. Only transactions transferred to GL are captured in this table. and o Amounts in the GL_JE_LINES (GJL) table correspond to GL_BALANCES table . XLA_DISTRIBUTION_LINKS (XDL) . This table stores the details at the distribution level for both source and applied transactions because AP utilizes the business flow feature of SLA.
Key Tables and Columns used for Reconciliation The following are the key tables and columns that are used for reconciliation purposes: XLA_AE_HEADERS (XAH) Table GL_TRANSFE ACCOUNTIN ACCOUNTIN R_ G_ G_ ENTITY_ID/AE_HEADER EVENT_TYPE_COD BALANCE_ UPG_BATCH_ GROUP_I STATUS_COD ENTRY_ DATE/ _ID/ E TYPE_CODE ID D E/ STATUS_ PERIOD_NA APPLICATION_ID DATE CODE ME INVOICE_VALIDATI ON E1/H1/200 (don't consider MANUAL ever) PAYMENT_CREATE D E2/H2/200 (don't consider MANUAL ever) XLA_AE_LINES (XAL) Table ENTITY_ID /AE_HEADER_ID/ AE_LINE_NUM/ APPLICATION_ID E1/H1/L1/200 E1/H1/L2/200 E1/H1/L3/200 E2/H2/L1/200 E2/H2/L2/200 E2/H2/L3/200 A-actual. as the CCID and Entity/Header are the same. E1-JAN5486 (not null encumbran G1 2000/JAN-00 for 11i) ce A-actual. GL_IMPORT_REFERENCES (GL_IMP_REF) Table If summary posting (most probably)! JE_HEADER_ID/JE_LINE_NUM GH1/GL1 JE_HEADER_ID/JE_LINE_NUM JE_BATCH_ID GH1/GL1 B1 GL_SL_LINK_ID/GL_SL_LINK_TABLE 123451/APECL . E1-JAN5486 (not null encumbran G2 2000/JAN-00 for 11i) ce Y/null F Y/null F ACCOUNTED_ ENTERED_ CR/DR CR/DR 500/0 500/0 500/0 0/250 0/250 0/250 500/0 500/0 500/0 0/250 0/250 0/250 CURRENCY_ CODE USD USD USD USD USD USD CODE_ COMBINATION_ ID 1000 1000 1500 1000 1000 1500 GL_SL_LINK_ID/ GL_SL_LINK_TABLE 123451/APECL 123452/APECL 123453/APECL 123454/APECL 123455/APECL 123456/APECL ACCOUNTING_ CLASS_ CODE LIABILITY LIABILITY LIABILITY LIABILITY LIABILITY LIABILITY XLA_TRIAL BALANCES (XTB) Table CODE_ COMBINATION_ ID 1000 1500 1000 1500 EVENT_ CLASS_ CODE AP_INVOICES AP_INVOICES AP_PAYMENTS AP_PAYMENTS SOURCE_ ENTITY_ID E1 E1 E2 E2 APPLIED_TO_ ENTITY_ID --E1 E1 ACCOUNTED_ CR/DR 1000/0 500/0 0/500 0/250 ENTERED_ CURRENCY_ CR/DR CODE 500/0 500/0 0/500 0/250 USD USD USD USD DEFINITION_ CODE AP_200_1 AP_200_1 AP_200_1 AP_200_1 * L1 and L2 are summed into TB.
then you are using Detailed Posting USD USD USD USD 1000 1500 1000 1500 y 3. GL_SL_LINK_TABLE is XLAJEL GL_JE_HEADERS (GJH) Table JE_HEADER_I JE_BATCH_I JE_FROM_SLA_FL ACTUA POSTED_DA REVERSED_JE_HEADER PERIO JE_SOURC JE_CATEGO D D AG L TE _ID D E RY GH1 GH2 B1 B2 U-upgrade for 11. JE_SOURCE=Cost Management .'WIP'.'MTL'.GH1/GL2 GH1/GL3 GH2/GL1 GH2/GL2 GH2/GL3 B1 B1 B2 B2 B2 123452/APECL 123453/APECL 123454/APECL 123455/APECL 123456/APECL GH1/GL1 GH1/GL2 GH2/GL1 GH2/GL1 GH2/GL2 * GIR and XAL are always one-one. ESTABLISHING A BASELINE FOR ADDRESSING 11i UPGRADE ISSUES . For R12.'Inventory') GL_JE_LINES (GJL) Table -. A/E Y for R12S ----JAN00 JAN00 Payables Payables Purchase Invoices Payments* y y y JE_SOURCE=Payables can have XLA 's MANUAL due to undo accounting.'Purchasing') and je_category in ('Receiving'. A/E Y for R12 U-upgrade for 11.IF Summary Posting in GL (most probably) JE_HEADER_ID/JE_LINE_NU GL_SL_LINK_ID/GL_SL_LINK_TABL ENTERED_CR/D CURRENCY_COD CODE_COMBINATION_I M E R E D GH1/GL1 GH1/GL2 GH2/GL1 GH2/GL2 1000/0 500/0 0/500 0/250 If GL_SL_LINK_ID is populated in GJL.has additional checks! -JE_source in ('Cost Management'.IF Detailed Posting in GL JE_HEADER_ID/JE_LINE_NU GL_SL_LINK_ID/GL_SL_LINK_TABL ENTERED_CR/D CURRENCY_COD CODE_COMBINATION_I M E R E D GH1/GL1 GH1/GL2 GH1/GL3 GH2/GL1 GH2/GL2 GH2/GL3 123451/APECL 123452/APECL 123453/APECL 123454/APECL 123455/APECL 123456/APECL 500/0 500/0 500/0 0/250 0/250 0/250 USD USD USD USD USD USD 1000 1000 1500 1000 1000 1500 y If GL_SL_LINK_ID is populated in GJL then it is Detailed Posting GL_JE_LINES (GJL) Table -.'Inventory'.
42 7174644.SLA+Man JE F=C-E+D Technical perspective AP does not upgrade all data in the XDL table.29 0. for upgraded data.completion_acct_seq_value AND 200 = xah.ae_line_id = xal.42 7174644.completion_acct_seq_value are values upgraded from AP to SLA.This implies that the XTB table cannot be constructed from the XAL and XDL tables.It is important to establish a baseline when the AP to GL Reconciliation was last completed (with or without known differences). Scenario Let us use the following as your Trial Balance.completion_acct_seq_version_id AND alb.21 0. then such data is not upgraded to the xla_trial_balances tables.00 0. then that data is NOT available in XTB If there is data corruption in the 11i AP_LIABILITY_BALANCE table . alb-ap_liability_balance ) xal. then those should be carried forward to the current reconciliation exercise.00 0. there is a mismatch between ap_ae_headers_all/ap_ae_lines_all & xla_trial_balances (on completion_acct_seq_value. In 11i.ae_header_id = xah.ae_line_num AND xah. Always reconcile the AP Trial Balance (APTB) with the GL account balances as of the upgrade period. per CCID. For upgraded data. Common Reasons why Reconciliation issues are Encountered During the Upgrade y y y y AP upgrade did not upgrade the accounting events correctly so the accounting events exist in AP and not in SLA. Get the Manual JEs YTD and adjust accordingly. as of the upgrade period Nov 2007 CCID A 15151 15071 15511 XXX YYY ZZZ GL Account B GL C 307778. ae_line_id) OR if during the upgrade. XTB is built from the AP_LIABILITY_BALANCE (APLB) table. APLB stores Payment details under the INVOICE_ID only. If there is a mismatch between ap_ae_headers_all/ap_ae_lines_all & ap_liability_balance (on ae_header_id.00 Manual JE D AP E 499899.upg_source_application_id = 200 ( xal-xla_ae_lines. Note: The data manager that is run later in the day will not be of any help. if there is a mismatch in the AE_LINE_ID col in AP_AE_LINES_ALL and AP_LIABILITY_BALANCE.ae_line_num & xah. The KEY joins from an upgrade perspective are AND alb. Run the APTB report in summary mode (option=group by Account Summary) for the upgrade period and identify the differences between the Remaining Amount and GL balances.29 -192121.00 Diff GL . There are ACCOUNTING_EVENT_IDs in AP that are not stamped back to invoice distributions so the invoice distributions were not upgraded to SLA.71 15067997. If there are differences that can be explained.92 15067997. ae_line_num).00 0. xah-xla_ae_headers.
nvl(tb. invoice_id.acctd_rounded_cr.xla_transaction_entities xte.code_combination_id IN (&Give_CCIDs_that_dont_tally) group by tb.acctd_rounded_cr.code_combination_id .acctd_rounded_dr..g.source_entity_id) entity_id.0)) <> sum(nvl(tb.0)))tb where tb. sum(nvl(accounted_cr.0)) diff from ap_liability_balance where set_of_books_id= &ledger_id and code_combination_id IN (&Give_CCIDs_that_dont_tally) and accounting_date <= to_Date('&upgrade_period_end_date') group by code_combination_id..applied_to_entity_id. QR2 .code_combination_id.0)) sum(nvl(accounted_dr.ledger_id=&ledger_id and tb.diff from xla. then do the following: ( See the example above for the CCID 15151 ) NOTE: When reporting the results of the SQL scripts in this document.0)) sum(nvl(tb.e.0)). tb.application_id=200 Run the following two SQL scripts to provide details about the transactions there are causing the differences.source_id_int_1. QR1 -.code_combination_id. sum(nvl(tb.0)) <> sum(nvl(accounted_dr. QR3 .0)) diff from xla_trial_balances tb where tb.applied_to_entity_id.entity_id=xte. tb.transaction_number.SQL Query Reference 1 Run this SQL script to show the data in the AP Liability table that should appear on the 11i Trial Balance create table ap_tb as select code_combination_id.ledger_id=&ledger_id and xte.definition_code= '&definition_code' and tb.xte.0)).gl_date <= to_date('&upgrade_period_end_date') and tb.1 and the SQL Reference-e. sum(nvl(accounted_dr..source_entity_id) having sum(nvl(tb.acctd_rounded_dr. the GL and SLA amounts are not the same) as of the upgrade period. include the Note number 605707. (select tb. QR1.Check for transactions in the SLA Trial Balance (SLA TB) table but not in the 11i APTB .acctd_rounded_dr. sum(nvl(tb. nvl(tb. QR3 etc.0)) cr.0)) dr.y If UNDO accounting is done on an 11i accounted event Analyzing the Difference in the R12 Trial Balance If you see differences in the R12 Trial Balance (i. invoice_id having sum(nvl(accounted_cr. QR2.sum(nvl(tb. tb.Run this SQL script to show the data in the SLA Trial Balance table that should show up in the Trial Balance as of the upgrade period create table xla_tb as select tb. xte.acctd_rounded_cr.entity_id and xte.0)).sum(nvl(accounted_cr.
invoice_id= xla.code_combination_id ) group by xla.code_combination_id.code_combination_id=ap. ap_ae_headers_all ah.Check for transactions in 11i APTB table but not in the SLA TB table select ap.ae_header_id.ae_header_id = al. ae_line_id/num).accounting_event_id = ah.xla_transaction_entities where ledger_id=1 and entity_code='AP_INVOICES' and nvl(source_id_int_1.code_combination_id QR4 .accounting_event_id from ap_accounting_events_all ae.source_id_int_1.code_combination_id How to Analyze the Data Even Further QR5 .Get the entity of any invoice select entity_id from xla. sum(ap.source_id_int_1 and xla.ae_header_id .select xla.Pick up any specific CCID select xla.invoice_id= xla.11i . ah.source_id_int_1 and xla.-99)=&INVOICE_ID and application_id=200 QR7 .invoice_id= xla. xla.code_combination_id=ap.diff from xla_tb xla where not exists (select 1 from ap_tb ap where ap. QR8 .ae_line_id. sum(xla.source_id_int_1 and xla.ae_line_number.Check whether the invoice is missing or payment is missing in the XTB table Select * from xla_trial_balances where definition_code=&DEF_CODE and nvl(applied_to_entity_id.accounting_event_id and ah. you can investigate the particular transaction by comparing the AP accounting data with the SLA accounting data (for ae_header_id.code_combination_id ) and code_combination_id=&CCID QR6 .diff) from xla_tb xla where not exists (select 1 from ap_tb ap where ap.diff) from ap_tb ap where not exists (select 1 from xla_tb xla where ap.code_combination_id ) group by ap. al. source_entity_id)=&ENTITY_ID and gl_date <= to_date('&upgrade_period_end_date') Using these SQL scripts.code_combination_id. al. xla.transaction_number. ap_ae_lines_all al where ae.code_combination_id=ap. The following five queries will help you determine if the AE_LINE_ID in AP is the same as that in the SLA tables.AP Invoice accounting select al.
ae_line_num.11i .completion_acct_seq_value FROM xla.-99) = &check_id and xte. ae_line_id from ap_liability_balance where invoice_id = &invoice_id and set_of_books_id = &ledger_id QR11 .accounting_event_id from ap_accounting_events_all ae.ENTITY_CODE = 'AP_PAYMENTS' AND XAL. xah. XLA_AE_LINES xal where xte.ledger_id = &ledger_id AND XTE.event_id .entity_id and xte.application_id and NVL(xte. XLA_AE_LINES xal where xte.ledger_id = &ledger_id AND XTE.ae_header_id = xal.and ae.completion_acct_seq_value FROM xla.source_id_int_1.xla_transaction_entities xte.ENTITY_CODE = 'AP_INVOICES' AND XAL.event_id .source_id_int_1. xal. XLA_AE_HEADERS xah.application_id and xah.R12 .SLA Invoice accounting SELECT xal.displayed_line_number. xal. xah.ACCOUNTING_CLASS_CODE = 'LIABILITY' QR12 .source_id = &invoice_id and ae. XLA_AE_HEADERS xah. ap_ae_lines_all al where ae.-99) = &invoice_id and xte.ae_header_id and xah.application_id and xah.entity_id = xah.AE_HEADER_ID.11i . xal.displayed_line_number.ae_line_num.entity_id and xte. xah.ae_header_id = xal.ae_header_id and xah.application_id = 200 and xte.ACCOUNTING_CLASS_CODE = 'LIABILITY' .application_id = xah.accounting_event_id = ah.source_table = 'AP_CHECKS' QR10 . ap_ae_headers_all ah.accounting_event_id and ah.application_id = xah.ae_line_id.ae_header_id and ae.application_id and NVL(xte.entity_id = xah.application_id = xal.source_id = &check_id and ae.AP Payment accounting select al.R12 .ae_header_id = al.source_table = 'AP_INVOICES' QR9 . xah.AE_HEADER_ID. al.SLA Payment accounting SELECT xal.ae_line_number. xal.application_id = 200 and xte.al.AP Liability balance (source for upgrade to R12 XLA TB table) select ae_header_id.application_id = xal.xla_transaction_entities xte.ae_header_id. ah.
code_combination_id ccid.71 0.64 8156. per CCID is the same as the data in GL_JE_LINES for the same CCID/source/month (and gl_je_headers.accounting_date between '01-MAR-2008' and '31-MAR-2008' <> group by currency_code R12. R12. 0)).application_id =xah.01 8156.17 12437132.upg_batch_id=-9999) -.code_combination_id =15151 <> and xal.concatenated_segments.Sum from the GL Tables select l.00 0.00 11842656.06 107676.00 Manual D AP E 380382.21 0. currency_code from gl.25 85439.70 Adjust the difference as of the Upgrade period.k.70 12630248.0)) diff.B) To get the sum from the GL tables QR14 .A) To get the sum from the SLA tables.Sum from the SLA Tables select /*+ parallel(xal) parallel(xah) leading(xah) */ sum(nvl(accounted_cr.gl_transfer_status_code = 'Y' and xah. Once you have reconciled the amounts in XLA_AE_LINES & GL_JE_LINES.64 11850812.ae_header_id and xal.0)) diff.accounted_cr.93 0.application_id = 200 and xal.00 639.ledger_id = 1 <> and xah. sum(nvl(l. Adjust the manual entries in GL accordingly.upg_batch_id is null or xah.accounting_entry_status_code='F' and xah. gl.gl_je_headers h .16 85439.ae_header_id = xah.je_from_sla_flag=Y). QR13 .balance_type_code='A' and (xah.4. in summary mode (option=group by Account Summary) XLA_AE_HEADERS (XAH) Table Trial Balance as of Jan 2008 CCID GL Account A 15151 XXX 15071 YYY 15511 ZZZ B GL C 188900.98 Diff GL . RECONCILING R12 DATA AND ADDRESSING R12 TRIAL BALANCE-GL ISSUES Run the report again for an R12 month.accounting_class_code = 'LIABILITY' and xal.application_id and xah.0)) -sum(nvl(accounted_dr. currency_code from xla_ae_lines xal.gl_je_lines l .SLA+Man JE Net Impact from Nov-07 Diff as of Jan-08 F=C-E-D -191482. xla_Ae_headers xah where xal.sum(nvl(l.accounted_dr. Then calculate the new Difference. If there is a difference then: y y First and foremost is to establish that the data in XLA_AE_LINES for application_id=200 per month. the next step is to verify the amounts in XLA_AE_LINES and XLA_TRIAL_BALANCES (for the CCID/entity_id) assuming that only LIABILITY accounts are defined in the TB definition.will help ignore upgraded data and xah.05 -192121.
currency_code. QR15 . currency within the period.application_id = 200 and xal.ae_header_id = xah.gl_code_combinations_kfv k where h.code_combination_id = 15151 <> and h. check per period. but will not match between XAL-to-XTB QR16 .ledger_id = 1 and xah.will help ingore upgraded data and l.je_header_id = l.accounting_date between '01-MAR-2008' and '31-MAR-2008' group by currency_code Note: In the following SQL query.0)) -sum(nvl(accounted_dr.0)) diff.code_combination_id =15011 -. Read the section. entity_id from xla_ae_lines xal.Get the XTB Difference select SUM(NVL(ACCTD_ROUNDED_CR. assuming all LIABILITY CCIDs are defined in the Trial Balance Definition.0)) diff.period_name in ('MAR-08') <> group by l. k. we have introduced another filter--event_class_code.je_header_id and h.je_from_sla_flag= 'Y' -. currency_code from xla_ae_lines xal.accounting_class_code = 'LIABILITY' and xah.je_source = 'Payables' and h.xal) leading(xah) */ sum(nvl(accounted_cr. QR17 . This is done in order to remove the UNDO ACCOUNTING datafix entries.currency_code = 'USD' and l. Such entries will match in SLA-to-GJL lines comparison.application_id and xah.0)) -sum(nvl(accounted_dr.accounting_class_code = 'LIABILITY' and xal.SUM(NVL(ACCTD_ROUNDED_DR.. xla_Ae_headers xah where xal. Understanding how UNDO Accounting can impact Reconciliation.xal) leading(xah) */ sum(nvl(accounted_cr.Get the difference from the SLA Lines table per CCID and currency select /*+ parallel (xah.gl_transfer_status_code = 'Y' and xah.concatenated_segments. xla_ae_headers xah where xal.event_type_code <> 'MANUAL' and xal. per CCID.0)) diff.accounting_entry_status_code='F' and xah.actual_flag = 'A' and h. currency_code R12.code_combination_id =15011 . trx_currency_code from xla_trial_balances xtb where definition_code = &definition_code and code_combination_id=15011 and gl_date between '01-MAR-2008' and '31-MAR-2008' group by trx_currency_code The Difference of the sum of Credit-Debit for the CCID/Currency combination in XAL (lines) should match the difference of the Sum Credit-Debit for the CCID/Transaction Currency in XTB.code_combination_id. for more details. per currency--This should be the difference between XAL and XTB. If it does.ledger_id = 1 <> and l.A and R12.code_combination_id = k.code_combination_id and h.i/p def code and xal.B should match per CCID.ae_header_id and xal.0)) .application_id =xah.To get the difference from SLA Lines table per CCID and currency select /*+ parallel (xah.
je_header_id=c. source_entity_id from xla_trial_balances xtb where definition_code = &definition_code and code_combination_id=15011 and gl_date between '01-MAR-2008' and '31-MAR-2008' group by trx_currency_code.ledger_id = 2 and xah.group_id QR20 .entity_id QR18 .entity_id source_entity_id.0)) diff_acc from apps.group_id.application_id = 200 and xal.application_id =xah.A and R12.application_id =xah. b. SUM(NVL(accounted_cr. apps.accounting_date between '01-MAR-2008' and '31-MAR-2008' group by entity_id.ae_header_id = xah.application_id = 200 and xal.group_id from xla_ae_lines xal.gl_je_lines c where a. trx_currency_code. then investigate the batches within that period from SLA and compare the amounts in SLA and GL using the group_id.posted_date is NOT NULL and a. sum(nvl(accounted_cr.je_header_id and a.je_batch_id and c.GL query for amounts per Group ID select 'GL' Module.i/p def code and xal. QR19 .ledger_id=2 and a.balance_type_code='A' group by xah.application_id and xah.accounting_class_code = 'LIABILITY' and xah.Get the difference from the XTB table select SUM(NVL(ACCTD_ROUNDED_CR.0)) diff.SLA query considering the SLA Manual entries select /*+ parallel(xal) parallel(xah) leading(xah) */ --xah.0)) -sum(nvl(accounted_dr.ae_header_id and xal.ae_header_id and xal.-.0)) diff .SUM(NVL(accounted_dr.code_combination_id =52261 and xal.SUM(NVL(ACCTD_ROUNDED_DR.je_source ='Payables' and a. This may not always work as the group_id sometimes gets deleted from GL.accounting_entry_status_code='F' and xah.ledger_id = 1 and xah.apps. xla_Ae_headers xah where xal.gl_je_headers a.code_combination_id=52261 group by b.event_type_code <> 'MANUAL' and xal.gl_transfer_status_code = 'Y' and xah.actual_flag='A' and c.gl_je_batches b.group_id.B do not match per CCID and currency within a period.0)) . xah.je_batch_id=b.accounting_entry_status_code='F' and xah. .ae_header_id = xah. source_entity_id If R12.gl_transfer_status_code = 'Y' and xah. currency_code.0)) .application_id and xah.
Subsequently.50 0. but in GL it is posted in one period. the invoice is still not displayed on the report.11 Null Group ID. as it is fully paid.72 28652.2588475.2588476 (reversal batch in GL) Null GROUP_ID in GL would generally mean it is a reversal batch in GL itself. If you submit the R12 Accounts Payable Trial Balance report as of 31-DEC-2000. 2588473.75 28652.2588472. if you submit the Accounts Payable Trial Balance report as of 31-JAN-2001. So in the above example.90 19409. UNDERSTANDING HOW UNDO ACCOUNTING CAN IMPACT RECONCILIATION Scenario The following is an example of how undo accounting works. you use the UNDO Accounting API to reverse the transaction as of 1-FEB-2001. Original Event/Accounting XLA_AE_HEADERS (XAH) Table EVENT_ID E1 EVENT_TYPE_CODE INVOICE_VALIDATE ACC_DATE 04-JAN-2001 H1 AE_HEADER_ID UPG_BATCH_ID ENTITY_ID XT1 XLA_AE_LINES (XAH) Table . Another possibility is: In GL 2069885 Apr 1027997 2069885 2069885 In SLA Apr Jan 999344.2582995.5 2069078 Dec -13387.75 Diff -28652.00 2069110 Dec 19409. but in GL it is posted in May. but it is posted to the GL.75 In SLA in Jan SLA Journal Posted in GL in Apr Comments A GROUP_ID in SLA has data of in two different periods. Someone may have edited the journal to change the period in GL.90 SLA Journal Posted in May in GL Dec 28919. You pay the full invoice and the payment date is 20-DEC-2000. y y y y y y y You enter an invoice with one distribution of $200. the invoice is NOT displayed on the report. 5. Similarly. There may be multiple batches that were reversed during the month. which uses a GL date of 04-JAN-2001. JE_BATCH_ID = -28919.2582994.11 2581709.In GL In SLA Diff Comments 2069078 Dec -13387. The other group_id=2069110 in SLA has a period-Dec. It is accounted incorrectly for a $205 LIABILITY. However. you see group_id=2067078 that has the same amounts in SLA and GL. the Posted Payment Register as of 31-DEC-2000 reports the Payment and the Posted Invoice Register as of 31-JAN-2001 reports the Invoice.
-99) =&invoice_id/check_id --this will be the MANUAL entity for the Original event.xla_transaction_entities where ledger_id=&ledger_id and entity_code='MANUAL' and application_id=200 and nvl(source_id_int_1. . after the UNDO accounting created the reversal entry in Feb 2001. How to find events/entities created by Undo Accounting Run the following SQL script to find the events and entities created by the UNDO Accounting: QR21 .Find the events and entries created by UNDO Accounting select entity_id XT3 from xla. the AP Trial Balance will not match the GL Balance.AE_HEADER_ID H1 H1 XLA_TRIAL_BALANCES (XTB) Table AE_HEADER_ID H1 After Undo: XLA_AE_HEADERS (XAH) Table EVENT_ID E1 E2 E3 EVENT_TYPE_CODE INVOICE_VALIDATE MANUAL MANUAL XT1 ITEM EXPENSE LIABILITY ACCOUNTING_CLASS_CODE C1 C2 CCID DR 220 CR 220 SOURCE_ENT_ID DEF_CODE AP_200_X X1 CCID DR CR 220 ACC_DATE 01-FEB-2001 04-JAN-2001 H2 H1 AE_HEADER_ID UPG_BATCH_ID -9999 -9999 ENTITY_ID XT1 XT2 XT3 XLA_AE_LINES (XAL) Table AE_HEADER_ID H1 H1 H2 H2 ACCOUNTING_CLASS_CODE ITEM EXPENSE LIABILITY ITEM EXPENSE LIABILITY C1 C2 C1 C2 220 CCID DR 220 CR DESC Datafix for Event: E1 220 Datafix for Event: E1 220 Datafix Reversal for Event: E2 Datafix Reversal for Event: E2 XLA_TRIAL_BALANCES (XTB) Table AE_HEADER_ID SOURCE_ENT_ID DEF_CODE CCID DR CR If you try to reconcile the AP Trial Balance (APTB) as of Jan 2001 with the GL Balance as of Jan 2001. If you look at the "After Undo" example. GL has the E1 event 's entry but APTB does not because it was converted to MANUAL.
balance_type_code='A' and h3.event_type_code='MANUAL' and h3.event_type_code='MANUAL' and h.ae_header_id = h.Determine if the UNDO Accounting correctly reversed all the amounts in a CCID select h. xla_ae_lines l where h.l.code_combination_id and h. QR23 .application_id = h.sum(nvl(accounted_dr.balance_type_code='A' AND h.application_id = 200 .Run this SQL script to list the Amounts in the SLA table for all Manual (YTD) transactions select /*+ parallel(l) parallel(h) parallel(gl) leading(h) */ gl.ledger_id=1 and h3.concatenated_segments.event_id) group by h.0)) <> 0 6. xla_ae_lines l.gl_transfer_status_code='Y' AND h.0)).event_id.0)).ledger_id = 1 and h.application_id=200 and h3. currency_code from xla_ae_headers h.0)).accounting_date between :p_period_start_date AND :p_period_end_date and h.application_id and l.accounting_entry_status_code='F' AND l.description='Data fix reversal entry: event_id of '||h.0))-sum(nvl(entered_dr.upg_batch_id=-9999 and h3.sum(nvl(entered_cr.0)) from xla_ae_headers h. APPENDIX The following are some useful queries that may help you to further analyze why you have a Reconciliation Issue.0)).application_id = 200 and l.sum(nvl(accounted_cr.sum(nvl(entered_cr.code_combination_id.event_id having sum(nvl(accounted_dr. So XT2=XT3-1 Use the following SQL script to determine if the UNDO Accounting correctly reversed all the amounts in a CCID: QR22 . gl_code_combinations_kfv gl where gl.description like 'Data fix entry: event_id of%' and not exists (select 1 from xla_ae_headers h3 where h3.code_combination_id=&CCID and h.upg_batch_id =-9999 and h.code_combination_id = l.Run this SQL script to determine the Segment from a CCID select concatenated_segments from gl_code_combinations_kfv where code_combination_id=52261 QR24 .Run this SQL script to determine the Batch ID for a Group select je_batch_id from gl_je_batches where group_id=2068553 QR25 .0)). sum(nvl(entered_dr. sum(nvl(entered_cr.sum(nvl(accounted_cr.ae_header_id --and h.The reversal manual entity would be 1 less than this entity. sum(nvl(entered_dr.0)).0)) .
gl_transfer_status_code='Y' AND h.gl_sl_link_id.gl_sl_link_table=l.application_id=:p_application_id AND h.and l.code_combination_id = 112771 <> and h.ae_header_id and xah.je_batch_id=gh.<> and h.Run this SQL script to list all transactions that are marked as transferred from SLA.je_batch_id and gh. QR27 .accrual_rev_je_header_id.application_id and xah.application_id = h. but is not present in the GL SELECT l.gl_sl_link_id AND ir.application_id AND l.ae_header_id = h.Run this SQL script periodically to check for multiple postings select distinct a.je_header_id and gh.ledger_id = 1 <> AND h.gl_sl_link_id=l.gl_sl_link_table) in (select distinct gl_sl_link_id.event_type_code='MANUAL' and h.gl_transfer_status_code='Y' AND h.accounting_entry_status_code='F' and xah.200 for AP.application_id=h.upg_batch_id IS NULL AND h.accounting_entry_status_code='F' AND l.application_id = xal.xla_ae_lines xal where xah.accounting_entry_status_code='F' AND h.gl_sl_link_id.je_batch_id = a.'DD-MON-YYYY') AND to_date('31-MAR-2008'.ae_header_id and h.'DD-MON-YYYY') -.code_combination_id.application_id and l.application_id=200 and h.accounting_date between :p_start and :p_end) and exists (select 1 from gl_je_headers gh where gh.ledger_id= :ledger_id and xah.application_id =:appl_id -. 222 for AR etc.ledger_id>0).je_batch_id AND gh.je_header_id=gh.a. gl. gl_je_headers gh WHERE ir.balance_type_code='A' group by l.ae_header_id AND h. l.event_type_code <> ' MANUAL' AND NOT EXISTS (SELECT 1 FROM gl_import_references ir .accounting_date BETWEEN :p_period_start_date AND :p_period_end_date AND h.je_header_id = a. l.gl_sl_link_id.concatenated_segments.je_header_id AND ir. currency_code QR26 . a. xla_ae_headers h WHERE l.ledger_id >0 and nvl(gh.ae_header_id=h. and xah.gl_sl_link_table FROM xla_ae_lines l.ledger_id= :p_ledger_id AND h. gl_sl_link_table from xla_ae_headers xah .0) =0 ) .gl_sl_link_table AND ir.accounting_date between to_date('01-JUL-2007'.ae_header_id.ae_header_id = xal.gl_sl_link_table from gl_import_references a where (a.
for a batch or period.gl_sl_link_table having count(*) > 1 QR28 .gl_sl_link_id. a.Run this SQL script to list all the Batches with Null Group IDs: select je_batch_id from gl_je_batches where group_id is null and je_batch_id in (select distinct je_batch_id from gl_je_headers where ledger_id=2 and je_source='Payables' and status='P' and period_name='Jan-08') .'Apr-08') ) and not exists (select 1 from xla_ae_lines where gl_sl_link_id=imp.je_header_id=imp.gl_sl_link_id and gl_sl_link_table='XLAJEL') and imp.'Feb-08'.'Mar-08'.je_line_num and code_combination_id=52261 and gl.group by a. select imp.Run this SQL script to identify where the GL_SL_LINK_ID is in GL but not in SLA.gl_sl_link_id is not null QR29 .je_line_num=imp.gl_sl_link_id from gl_import_references imp. gl_je_lines gl where gl.je_header_id in (select je_header_id from gl_je_headers where --je_batch_id=2586374 je_source='Payables' and ledger_id=2 and je_source ='Payables' and posted_date is NOT NULL and actual_flag='A' and period_name in ('Jan-08'.je_header_id and gl.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.