Search Results abas_global_attribute1




Overview
Explore in AI Chat

Overview

The ECE_AP_CHECKS_INTERFACE table, owned by the EC (e-Commerce Gateway) schema, is a transactional interface table within Oracle E-Business Suite that stores outbound payment and remittance data. Specifically, it holds the payment records required to generate the outbound Payment/Remittance Advice transaction set (EDI 820, PAYORD, or REMADV). During an outbound payment run, Oracle Payables populates this interface table with check and electronic payment details, which the e-Commerce Gateway then reads, translates into the appropriate EDI or flat-file format, and transmits to a trading partner or financial institution.

The table is present and valid in both release 12.1.1 and 12.2.2, and the documented physical schema in 12.2.2 spans 222 columns. This large column count reflects the wide variety of optional data segments that a payment remittance document can carry, including bank, supplier, address, and descriptive flexfield attributes. With respect to the heuristic Data Vault classification mined from its foreign key structure, this table is a standalone object, meaning it does not naturally decompose into a hub, link, or satellite pattern. A modeling suggestion would be to treat it as a transient staging or interface entity rather than a durable modeled warehouse object, since its contents are batch-oriented and periodically purged or reprocessed.

Key Information Stored

The table's primary key is the ECE_AP_CHECKS_INTERFACE_PK constraint, defined on the CHECKRUN_NAME column. This surrogate-style, run-scoped key groups all payment records created by a single payment batch, and it acts as the primary access path for the e-Commerce Gateway's extraction process.

Business-key candidates and significant descriptive columns include:

Numerous ADA/global flexfield columns (ABA_GLOBAL_ATTRIBUTE1–20, ABAS_GLOBAL_ATTRIBUTE1–20, PVS_GLOBAL_ATTRIBUTE1–20) and TPH/TPD attribute columns provide extensibility for trading-partner-specific data.

Common Use Cases and Queries

Typical uses include auditing outbound payment transmissions, reconciling Gateway output to Payables payments, and troubleshooting failed remittance advice generation. A representative query retrieves all payment records for a payment run:

  • SELECT checkrun_name, check_number, check_amount, currency_code, vendor_name, payment_date FROM ece_ap_checks_interface WHERE checkrun_name = :p_run;
  • Void analysis: SELECT check_number, void_flag, void_date FROM ece_ap_checks_interface WHERE void_flag = 'Y' AND checkrun_name = :p_run;
  • Joining back to Payables: ... FROM ece_ap_checks_interface c, ap_selected_invoice_checks_all a WHERE c.selected_check_id = a.check_id;

Reporting commonly aggregates payment amounts by currency or supplier, and integration teams inspect EDI_PAYMENT_METHOD and COMMUNICATION_METHOD to confirm the correct transmission channel was selected.

Related Objects

  • AP_SELECTED_INVOICE_CHECKS_ALL — referenced by SELECTED_CHECK_ID; the upstream Payables source of selected checks.
  • AP_CHECKS_ALL — the Payables check header table from which payment data is derived.
  • ECE_AP_INVOICES_INTERFACE — companion interface table carrying remittance invoice detail for the 820 transaction.
  • ECE_TP_HEADERS / ECE_TP_TRANSLATORS — trading partner and translator configuration used by the Gateway extraction.
  • IBY_PAYMENTS / IBY_PAYMENT_METHODS — Payments module records underpinning electronic payment methods.
  • e-Commerce Gateway outbound concurrent programs and the ECE_OUTBOUND_* API family, which read this table to produce the final EDI output.