Search Results ap_check_formats




Overview
Explore in AI Chat

Overview

The AP_CHECK_FORMATS table is a core data object within the Oracle E-Business Suite Payables (AP) module, historically used to define the configuration templates for check payments. Its primary role was to serve as a master repository for check format definitions, linking specific layout and printing parameters to payment methods and currencies. This table was essential for the automated generation and formatting of checks, including the integration of concurrent programs for payment building, formatting, and remittance advice generation. As indicated by the official ETRM documentation, this table is marked as "No Longer Used" in releases 12.1.1 and 12.2.2, signifying its functional logic has been superseded or migrated, though the table structure remains in the database for reference and potential data integrity with historical transactions.

Key Information Stored

While the full column list is not detailed in the provided excerpt, the primary and foreign key relationships reveal the critical data elements. The table's structure centers on a unique check format definition. The primary identifier is CHECK_FORMAT_ID. The table enforced a unique constraint (AP_CHECK_FORMATS_UK1) on the combination of NAME and PAYMENT_METHOD_LOOKUP_CODE, indicating that format names were unique within a given payment method (e.g., CHECK, WIRE). Crucially, it stored foreign keys to three separate programs in the AP_PAYMENT_PROGRAMS table: BUILD_PAYMENTS_PROGRAM_ID, FORMAT_PAYMENTS_PROGRAM_ID, and REMITTANCE_ADVICE_PROGRAM_ID, which defined the concurrent programs executed for payment processing. The CURRENCY_CODE column linked to FND_CURRENCIES, allowing for currency-specific format rules.

Common Use Cases and Queries

Given its deprecated status, direct operational use in 12.1.1/12.2.2 is minimal. However, it may be referenced in historical data analysis or during upgrade validations. Common queries would involve joining to related transactional tables to audit legacy payment setups. A sample diagnostic query to list historical format definitions and their associated programs might be:

  • SELECT cf.name, cf.payment_method_lookup_code, cf.currency_code, pp_build.program_name AS build_program, pp_format.program_name AS format_program FROM ap_check_formats cf, ap_payment_programs pp_build, ap_payment_programs pp_format WHERE cf.build_payments_program_id = pp_build.program_id(+) AND cf.format_payments_program_id = pp_format.program_id(+);

Reporting use cases are now largely retrospective, such as tracing the configuration used for checks printed in closed accounting periods.

Related Objects

As documented by the foreign key relationships, AP_CHECK_FORMATS is integrally connected to several key Payables tables:

  • AP_PAYMENT_PROGRAMS: Linked via three columns (BUILD_PAYMENTS_PROGRAM_ID, FORMAT_PAYMENTS_PROGRAM_ID, REMITTANCE_ADVICE_PROGRAM_ID). This defined the executable programs for the payment lifecycle.
  • FND_CURRENCIES: Linked via CURRENCY_CODE to restrict the format to a valid currency.
  • AP_CHECKS_ALL: A foreign key from AP_CHECKS_ALL.CHECK_FORMAT_ID references this table. This relationship ties issued checks to the format definition used at the time of payment.
  • AP_CHECK_STOCKS_ALL: A foreign key from AP_CHECK_STOCKS_ALL.CHECK_FORMAT_ID references this table, linking physical check stock to a specific format template.