Search Results supplier bank account assign




The AP_RECON_CHECK_RESULTS table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical repository for storing reconciliation check results between Payables and General Ledger modules. This table plays a pivotal role in ensuring financial data integrity by capturing discrepancies identified during the reconciliation process. Below is a detailed analysis of its structure, purpose, and operational context.

1. Purpose and Functional Context

The AP_RECON_CHECK_RESULTS table is primarily used by the "Payables to General Ledger Reconciliation Report" (APXGLR.rdf). This report validates whether Payables accounting entries match corresponding General Ledger postings, ensuring accurate financial reporting. The table stores reconciliation exceptions when variances occur between AP and GL data, such as:
  • Mismatched posted amounts between Payables and GL
  • Missing accounting entries in either subsystem
  • Discrepancies in accounting period close statuses

2. Key Table Columns

The table contains these critical columns:
Column NameData TypeDescription
RECON_IDNUMBERPrimary key identifier
CHECK_IDNUMBERForeign key to AP_RECON_CHECKS
RESULT_TYPEVARCHAR2(30)Type of discrepancy (AMOUNT/PERIOD/ENTRY)
RESULT_CODEVARCHAR2(30)Specific error code
RESULT_MESSAGEVARCHAR2(2000)Detailed error description
GL_BALANCENUMBERAmount from GL perspective
AP_BALANCENUMBERAmount from Payables perspective
PERIOD_NAMEVARCHAR2(15)Accounting period in conflict
CREATION_DATEDATETimestamp when discrepancy was logged

3. Integration Points

The table interacts with several key EBS components:
  • AP_RECON_CHECKS: Contains reconciliation check definitions
  • GL_JE_BATCHES: References GL batches that failed reconciliation
  • AP_ACCOUNTING_EVENTS: Links to source Payables transactions
  • AP_INVOICES: Connects to original invoice documents

4. Technical Implementation

Data flows into this table through:
  1. The standard reconciliation concurrent program (APXRECON)
  2. Custom extensions via AP_RECON_PKG procedures
  3. Direct SQL inserts for manual reconciliation entries

5. Maintenance Considerations

For optimal performance:
  • Purge old records using AP_RECONCILIATION_PURGE_PKG
  • Create indexes on frequently queried columns (RECON_ID, CHECK_ID)
  • Monitor table growth during period-end close cycles

6. Troubleshooting Common Issues

Frequent reconciliation errors include:
  • GL_POSTED_FLAG='N': GL batches not posted
  • PERIOD_STATUS='Closed': Attempts to post to closed periods
  • AMOUNT_DIFFERENCES: Caused by manual GL adjustments

7. Customization Potential

The table supports extensions through:
  • Custom result types via FND_LOOKUPS
  • User-defined reconciliation checks
  • Additional descriptive columns (max 2000 chars)
This table serves as the system of record for financial controls between Payables and General Ledger, with strict retention policies recommended for audit compliance.