Results for “ecapp_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IBY_PAY_INVOICEPMTS is a Payments (IBY) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM documentation, its purpose is to "store a reference to the invoice in the calling payable programs." It therefore acts as a transactional bridge between the payment transaction records held in IBY_PAY_PAYMENTS_ALL and the source invoices processed by the Payables payment programs, capturing the invoice-level detail associated with each payment transaction.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is satellite-leaning. This suggests the table is best modeled as a satellite attached to the IBY_PAY_PAYMENTS_ALL hub, carrying descriptive invoice context rather than acting as an independent hub or link. The table is owned by the IBY schema and is documented as VALID in the ETRM repository, with 17 physical columns in the 12.2.2 schema.

Key Information Stored

The primary key of the table, and the principal identifier, is IBY_PAY_INVOICEPMTS_PK, a composite key over PMT_TRXN_ID and INVOICE_NUMBER. The PMT_TRXN_ID column is also a foreign key to IBY_PAY_PAYMENTS_ALL, tying each invoice-payment row to its parent payment transaction. The most significant columns include:

• PMT_TRXN_ID — surrogate transaction identifier linking to the payment record.
• INVOICE_NUMBER — the invoice key referenced by the calling payable program.
• PMT_BATCH_REQUEST_ID and BATCH_ID — batching context for the payment run.
• INVOICE_DATE, INVOICE_AMOUNT, PAYMENT_AMOUNT — invoice and paid amounts.
• ERROR_LOCATION, BEP_CODE, BEP_MESSAGE — error/diagnostic fields used by the payment batch process.
• ECAPP_ID — application context identifier.
• OBJECT_VERSION_NUMBER plus the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).

Beyond the primary key, a second unique index, IBY_PAY_IP_PK_U1, spans PMT_BATCH_REQUEST_ID, BATCH_ID, PMT_TRXN_ID, and INVOICE_NUMBER, representing an alternate business-key candidate. The WHO columns are not enumerated individually here but follow standard EBS audit conventions.

Common Use Cases and Queries

Typical usage includes reconciliation of paid invoices to payment transactions, batch-level audit reporting, and diagnostics of payment program errors. A common query joins this table to IBY_PAY_PAYMENTS_ALL on PMT_TRXN_ID to retrieve invoice-level detail for a payment:

SELECT p.PMT_TRXN_ID, i.INVOICE_NUMBER, i.INVOICE_AMOUNT, i.PAYMENT_AMOUNT
FROM IBY_PAY_PAYMENTS_ALL p, IBY_PAY_INVOICEPMTS i
WHERE p.PMT_TRXN_ID = i.PMT_TRXN_ID;

Reporting use cases include summarising payment amounts by batch (grouping on PMT_BATCH_REQUEST_ID and BATCH_ID), listing invoices with payment errors (filtering on BEP_CODE or ERROR_LOCATION), and totals of INVOICE_AMOUNT versus PAYMENT_AMOUNT to identify partial payments. Because INVOICE_NUMBER is part of the primary key, joining to AP invoice tables on that column supports Payables-to-Payments reconciliation.

Related Objects

The most significant related object is IBY_PAY_PAYMENTS_ALL, the parent table joined through PMT_TRXN_ID (IBY_PAY_INVOICEPMTS.PMT_TRXN_ID → IBY_PAY_PAYMENTS_ALL). Downstream, AP invoice tables are commonly joined on INVOICE_NUMBER for reconciliation. Payment batch and instruction tables in the IBY module share the PMT_BATCH_REQUEST_ID and BATCH_ID context, and the standard EBS WHO/audit columns link to FND_USER and related security objects. The table is populated by the calling Payables payment programs, so the Payables Payment workbench and payment process request logic are the principal functional dependencies.