Search Results ap_checks_all

The AP_CHECKS_ALL table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a fundamental repository for storing check payment information within the Accounts Payable (AP) module. As a core transactional table, it captures comprehensive details about issued checks, including payment attributes, vendor data, bank information, and accounting entries. This table supports multi-organization access through the ORG_ID column, enabling shared service implementations while maintaining data segregation.

Table Structure and Key Columns

The AP_CHECKS_ALL table contains over 100 columns, with these critical fields:

• CHECK_ID: Primary key identifier for each check record
• CHECK_NUMBER: Human-readable check number assigned during payment processing
• CHECK_DATE: Date when the check was issued
• VENDOR_ID: Foreign key to PO_VENDORS identifying the payee
• BANK_ACCOUNT_ID: Links to CE_BANK_ACCOUNTS for payment source details
• AMOUNT: Total payment value in functional currency
• CURRENCY_CODE: Payment currency (links to FND_CURRENCIES)
• STATUS_LOOKUP_CODE: Tracks payment lifecycle (NEGOTIABLE, VOIDED, RECONCILED)
• PAYMENT_METHOD_CODE: Identifies payment instrument type (CHECK, EFT, WIRE)
• ORG_ID: Multi-org identifier for partitioning data

Functional Integration Points

The table integrates with multiple EBS modules:

1. Cash Management (CE): Check records reconcile with bank statements through CE_ STATEMENT_LINES
2. General Ledger (GL): Accounting entries post to GL_JE_LINES via the ACCTS_PAY_CODE_COMBINATION_ID
3. Payables (AP): Links to invoices through AP_INVOICE_PAYMENTS_ALL junction table
4. Purchasing (PO): Vendor details reference PO_VENDORS and PO_VENDOR_SITES_ALL

Technical Considerations

Key technical attributes of AP_CHECKS_ALL include:

• Indexing: Oracle creates indexes on CHECK_ID, CHECK_NUMBER, and BANK_ACCOUNT_ID for performance
• Partitioning: Commonly partitioned by CHECK_DATE in large implementations
• Audit Columns: Includes standard CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY
• Concurrent Processing: Check printing and payment programs update this table through Payables Open Interface

Business Process Context

The table supports these payment workflows:

1. Check Creation: Populated during Payment Batch processing (APXPAWKB.rdf)
2. Check Printing: Updated with print status and MICR details
3. Payment Reconciliation: Status changes when clearing through Cash Management
4. Escheatment Processing: Tracks stale-dated checks via STATUS_LOOKUP_CODE
5. 1099 Reporting: Provides payment data for year-end tax reporting

Customization Considerations

Common extension patterns include:

• Adding descriptive flexfields for industry-specific payment attributes
• Creating database triggers for custom validation rules
• Developing custom reports leveraging the AP_CHECKS_ALL and related tables
• Implementing VPD policies for enhanced data security

The table's design reflects Oracle's payment processing architecture, where AP_CHECKS_ALL serves as the system of record for all check-based disbursements, with related tables storing supporting details. Proper maintenance through standard Payables programs ensures referential integrity with dependent modules.