Search Results delete_transaction_extension

Overview

ASO_PAYMENT_INT is an internal PL/SQL package body within the Oracle E-Business Suite Order-to-Cash (ASO) module, owned by the APPS schema. Its principal business function is to bridge Oracle Quoting payment information with the Oracle Payments (IBY) infrastructure. The package extracts payment term identifiers attached to quote headers and lines and orchestrates the creation, maintenance, and removal of payment records, including credit card instrument and payer context data, for downstream payment processing. The header comment in the source identifies the package simply as ASO_PAYMENT_INT and references the source file asoipayb.pls. Two package-level constants, G_APP_ID (697) and G_AUTH_ERROR (3), reflect the application identifier and an authorization error code used internally, consistent with the module's dependency on IBY funds capture APIs.

Key Procedures and Functions

The ETRM metadata documents six program units. No parameter lists are reproduced here; only documented purpose is described.

• GET_PAYMENT_TERM_ID — Returns a payment term identifier for a given quote context. Two cursors are declared: one querying ASO_PAYMENTS by quote line and quote header, and a second by quote header only. The function returns an existing, non-null payment term (excluding the FND_API.G_MISS_NUM sentinel) if found, otherwise falls back to the header-level value, providing graceful resolution where line-level payment terms have not been defined.
• CREATE_IBY_PAYMENT — Builds an Oracle Payments payer and credit card context. It accepts a payment record and an optional database payment record (defaulting to G_MISS_PAYMENT_REC) together with an IBY_FNDCPT_COMMON_PUB.PayerContext_rec_type, and returns an output payment record plus standard API return status, message count, and message data. Local variables include a payer context record and a credit card record, indicating credit card assignment processing.
• CREATE_PAYMENT_ROW — Inserts new payment rows into the ASO payment tables.
• UPDATE_PAYMENT_ROW — Modifies existing payment rows in place.
• DELETE_PAYMENT_ROW — Removes an individual payment row. In practice this operation is closely associated with the user search term delete_transaction_extension, which is not itself a documented unit of this package but is commonly encountered in custom extensions that precede or follow payment deletion.
• PURGE_ASO_PAYMENTS_DATA — Performs bulk removal of payment data, typically aligned with quote purge or housekeeping activity rather than single-record deletes.

Tables Accessed

The package operates against APPS synonyms for the following objects:

• ASO_PAYMENTS and ASO_PAYMENTS_S — Primary payment records and their shadow (audit) table, read by GET_PAYMENT_TERM_ID and maintained by the create, update, delete, and purge routines.
• HZ_PARTIES — Trading partner identity data used when establishing payer context.
• IBY_EXTERNAL_PAYERS_ALL and IBY_PMT_INSTR_USES_ALL — External payer and payment instrument usage records consumed during IBY payment creation.
• IBY_CREDITCARD — Credit card instrument data invoked by CREATE_IBY_PAYMENT.
• PLITBLM — The standard APPS PL/SQL table used for message-list handling and error propagation through the FND_API message stack.

Usage Notes

ASO_PAYMENT_INT is an internal implementation package rather than a public API surface. It is referenced directly by four other packages in the quoting and payments integration chain, which are the typical callers. Invocation occurs indirectly through the ASO Quote public APIs—notably aso_quote_pub, whose payment_rec_type structure appears in the CREATE_IBY_PAYMENT signature—when a user creates or modifies payment and credit card details on a quote in the Oracle Quoting interface. Deletion paths, such as DELETE_PAYMENT_ROW, may be reached from quote revision or cancellation logic, and PURGE_ASO_PAYMENTS_DATA supports data cleanup. Custom code requiring payment term resolution for a quote should prefer the supported public APIs and treat GET_PAYMENT_TERM_ID as reference logic, since direct calls bypass the standard validation and message-handling framework exposed by the FND_API return status parameters.