Results for “get_doc_ext_agg”

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

Overview

The APPS.IBY_FD_EXTRACT_EXT_PUB package body is a public PL/SQL API within the Oracle Payments (IBY) module of Oracle E-Business Suite. It supports the Funds Disbursement (FD) Extract process by providing extensibility hooks that allow customer-specific and Oracle-supplied aggregation logic to be applied to payment instruction data before extraction and formatting. In release 12.1.1 and 12.2.2, the package is registered as a PUB-classified API in the ETRM repository with a status of VALID, confirming that it compiles cleanly and its dependencies resolve within the APPS schema.

Its principal role is to aggregate extension-level attributes associated with payment instructions, payments, documents, document lines, and payment process requests (PPRs). These aggregations are consumed by the payment extract and formatting engines so that extended data is presented consistently across the various output formats supported by Oracle Payments. The package forms part of the integration surface delivered to customers extending Oracle Payments functionality.

Key Procedures and Functions

The ETRM documentation identifies six documented procedures or functions within this public package. The principal aggregator entry points are:

• GET_INS_EXT_AGG — Aggregates extension attribute values at the payment instruction level, consolidating data associated with a given instruction for downstream extract processing.
• GET_PMT_EXT_AGG — Aggregates extension attributes at the individual payment level, ensuring payment-specific extension data is available during formatting.
• GET_DOC_EXT_AGG — Returns aggregated extension data for a document associated with a payment.
• GET_DOCLINE_EXT_AGG — Returns aggregated extension data for document lines, supporting line-level extension visibility in the extract output.
• GET_PPR_EXT_AGG — Aggregates extension attributes at the Payment Process Request level, providing a summary view across the PPR.

A sixth documented procedure or function exists but is not enumerated in the metadata provided; it should be verified through the package specification in the target environment. Parameter lists are not documented here and should not be assumed — the signatures must be sourced directly from the APPS.IBY_FD_EXTRACT_EXT_PUB specification in the database.

Tables Accessed

The dependency report shows that the package body references XMLTYPE (a SYS-owned type exposed through APPS synonyms) and the STANDARD package. XMLTYPE usage indicates that extension data is constructed, parsed, or returned as XML fragments, consistent with Oracle Payments' XML-driven extract and formatting architecture. No application data tables are listed among the documented dependencies, and the package is reported as not referenced by any database object, meaning it is invoked through application-level code rather than through static PL/SQL dependency chains.

Usage Notes

This public API is typically invoked by the Oracle Payments extract and formatting framework during funds disbursement processing, and it may be called from the Payments dashboard, payment instruction creation flows, or custom extensions that require aggregated extension attributes. Two other packages are documented as referencing this API, confirming its role as a shared utility. Because the package body relies on XMLTYPE and reports no base-table dependencies, extensions should treat it as an aggregation façade over the Payments data model rather than a direct table interface. Custom code invoking these procedures must rely on the specification for exact signatures and should expect XML-formatted results suitable for extract templates and payment formats.