Search Results pmtdtls_tbl_type

Overview

APPS.IEX_PAYMENTS_PUB is a public PL/SQL package belonging to the Oracle E-Business Suite Collections (Advanced Collections / IEX) module. Its primary purpose is to expose a supported, callable interface for creating payment records against a payer and for retrieving payer information from the underlying Oracle Receivables and Trading Community Architecture (TCA) data model. The package encapsulates the business logic required to register a payment intent — including the payment target (accounts, invoices, consolidated items, or contracts), the amount and currency, exchange rate details, the payee and payer party identifiers, and optional payment instrument details such as credit card or bank account information.

The package defines several public record types that are used as the parameter interface for its procedures: ATTRIBUTE_REC_TYPE (a standard 15-column DFF attribute structure plus attribute category), BANKACCTINSTR_REC_TYPE, CREDITCARDINSTR_REC_TYPE, PMTINSTR_REC_TYPE, and PMT_REC_TYPE. PMT_REC_TYPE is the composite structure that carries the payment-level data and nests the instrument and attribute records. This design allows callers to pass a single strongly-typed record rather than a long positional parameter list.

Key Procedures and Functions

• CREATE_PAYMENT — The principal API entry point. It accepts payment data (referenced through the PMT_REC_TYPE structure) and creates the payment record in the Advanced Collections schema. It validates and persists the payer/payee relationship, payment target, amount, currency, and instrument details, and it writes the associated cross-reference and receipt-number records required to tie the payment to its source transaction and to generate a receipt number.
• GET_PAYER_INFO — A query API that returns payer information for a given payer context. It is used by callers that need to resolve payer party, account, or site-use details before invoking CREATE_PAYMENT or before displaying payer data in a Collections user interface.

The package additionally exposes the record type definitions listed above, which are part of its public contract and are referenced by dependent packages.

Tables Accessed

• IEX_PAYMENTS_S — The base sequence/table for payment records; the primary target of CREATE_PAYMENT inserts.
• IEX_PAY_RECEIPT_XREF_S — Cross-reference linking a payment to its generated receipt number.
• IEX_RECEIPT_NUMBER_S — Source of unique receipt numbers assigned to new payments.
• IEX_DEL_PAY_XREF_S — Cross-reference between delinquency records and payments.
• IEX_DELINQUENCIES — Delinquency records associated with the payer; read during payment processing.
• HZ_PARTIES — TCA party master; queried by GET_PAYER_INFO to resolve payer party details.
• DUAL and PLITBLM — Used for scalar evaluations and for PL/SQL table (index-by table) handling within the package.

Usage Notes

IEX_PAYMENTS_PUB is classified as a public (PUB) API, meaning it is supported for customer and partner extension in both Oracle EBS 12.1.1 and 12.2.2. It is typically invoked from Advanced Collections forms, from Collections concurrent programs, and from custom PL/SQL that must create or query payments programmatically. Because the procedure signatures rely on the published record types, callers must declare variables of PMT_REC_TYPE (and its nested components) and populate the relevant fields before calling CREATE_PAYMENT.

The user search term pmtdtls_tbl_type does not appear in the documented public interface of this package; the documented collection type is PMT_REC_TYPE. The similarity suggests the search may relate to a related internal or dependent object rather than to IEX_PAYMENTS_PUB itself. When implementing customizations, developers should call only the documented public procedures and should not depend on internal package bodies, as the header indicates this package has been patched across the 12.1.x release stream and internal implementation details may change between patch levels.