Search Results get_pmt_ext_agg

Overview

IBY_EXT_WRAP_PUB is a public PL/SQL package body owned by APPS within the Oracle Payments (IBY) module of Oracle E-Business Suite. Its central purpose is to act as an extension wrapper: it delegates calls to the corresponding extension API procedures and functions in IBY_FD_EXTRACT_EXT_PUB, returning the resulting data to the calling process. This design separates Oracle's seeded extraction logic from customer-specific extension code, allowing implementations to customize payment instruction, payment, document, document line, and payment process request extraction without modifying delivered objects.

The package is instrumented with the FND_LOG diagnostic framework. Standard logging constants are declared, including G_LEVEL_UNEXPECTED, G_LEVEL_ERROR, G_LEVEL_EXCEPTION, G_LEVEL_EVENT, G_LEVEL_PROCEDURE, and G_LEVEL_STATEMENT, each bound to its FND_LOG counterpart. A private helper, print_debuginfo, writes messages to the concurrent request log when the runtime level permits, using FND_LOG.STRING for logged-in sessions and FND_FILE.PUT_LINE for concurrent programs. This explains why the search term g_level_unexpected surfaces in this source: the constant is referenced when exceptions are trapped, ensuring that unexpected errors encountered while invoking custom extraction code are recorded at the appropriate severity.

Key Procedures and Functions

The package exposes five documented functions that mirror the extension capability of IBY_FD_EXTRACT_EXT_PUB:

• GET_INS_EXT_AGG — Retrieves the extension aggregate (XML) associated with a given payment instruction, allowing custom extracted attributes to be merged with seeded payment instruction data.
• GET_PMT_EXT_AGG — Returns the extension aggregate for a payment, supporting custom attributes defined at the payment level.
• GET_DOC_EXT_AGG — Supplies the extension aggregate for a payment document, enabling customization of document-level extracted data.
• GET_DOCLINE_EXT_AGG — Provides the extension aggregate for a payment document line, addressing line-level custom extraction needs.
• GET_PPR_EXT_AGG — Delivers the extension aggregate for a payment process request, covering custom attributes at the PPR level.

Each function returns an XMLTYPE payload. The visible implementation of GET_INS_EXT_AGG demonstrates the pattern used throughout: the wrapper invokes IBY_FD_EXTRACT_EXT_PUB, checks for a NULL result, logs a diagnostic message if none is returned, and propagates any exception through the WHEN OTHERS handler, where messages are logged using the G_LEVEL_UNEXPECTED severity. No parameter lists are documented beyond the payment instruction identifier shown for the sample function.

Tables Accessed

The documented metadata lists XMLTYPE as the referenced object. Because these are aggregate-returning APIs, the underlying extraction routines assemble their results as XML documents rather than performing direct DML against base tables within this wrapper. The package itself therefore does not insert, update, or delete rows; it transforms and returns data produced by the extension extraction layer.

Usage Notes

IBY_EXT_WRAP_PUB is classified as a PUB API and is referenced by four other packages, indicating it is called from within the Payments extraction and formatting flow rather than directly from a form. Typical invocation occurs during payment instruction, payment, document, document line, and payment process request extraction, particularly when custom extension attributes have been configured. Because logging depends on FND_LOG runtime levels and the concurrent request identifier, administrators diagnosing extraction problems commonly raise the FND logging level and inspect the concurrent program log for the debug messages emitted by print_debuginfo. Custom code should follow the wrapper pattern shown, including exception handling that logs at G_LEVEL_UNEXPECTED, to preserve supportability of the Payments extraction process.