Search Results put_endtag

Overview

FUN_XML_REPORT_PKG is a server-side PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. Its principal business function is the construction and emission of XML-formatted report output from within the Oracle EBS file and messaging infrastructure. The package provides a controlled mechanism for streaming XML markup to the concurrent manager output file, allowing report programs to assemble well-formed XML documents without managing low-level file handles directly. This is particularly relevant to the Funds Netting and settlement reporting domain, where structured output is consumed by downstream processors, reconciliation tools, or external systems.

The package is a thin but purposeful wrapper around FND_FILE and FND_LOG utilities. It handles large XML payloads represented as CLOB data types, and it emits tag markup incrementally so that report output is produced in manageable chunks rather than held entirely in memory.

Key Procedures and Functions

The ETRM metadata documents two procedures at the package interface: PROPOSED_NETTING_REPORT and FINAL_NETTING_REPORT. These represent the two operational reporting modes supported by the package.

• PROPOSED_NETTING_REPORT — Generates the report output for proposed netting activity. This mode presents netting positions that have been calculated but not yet finalized, supporting review and approval workflows prior to settlement.
• FINAL_NETTING_REPORT — Generates report output for finalized netting activity. This mode is invoked after netting has been committed, producing the authoritative record of settled positions.

Internally, the package body also exposes helper routines that the search term "put_endtag" alludes to. The documented source excerpt shows procedures including clob_to_file and put_starttag, with the natural counterpart being a put_endtag routine. These helpers emit opening and closing XML elements respectively. The clob_to_file routine reads a CLOB in 3000-character chunks and writes each chunk to FND_FILE.OUTPUT, looping until the entire LOB length has been consumed, then appends a newline. Parameter lists should not be assumed beyond those shown in the source header.

Tables Accessed

The package draws on a broad set of application tables, reflecting the cross-module nature of netting and settlement reporting. Payables data is sourced from AP_INVOICES_ALL and FUN_NET_AP_INVS_ALL; receivables data from AR_CASH_RECEIPTS_ALL, RA_CUSTOMER_TRX_ALL, and RA_CUSTOMER_TRX_LINES_ALL; and netting transaction detail from FUN_NET_AR_TXNS_ALL, FUN_NET_AGREEMENTS_ALL, and FUN_NET_BATCHES_ALL. Party, account, site, and location attributes are resolved through HZ_PARTIES, HZ_PARTY_SITES, HZ_CUST_ACCOUNTS_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, and HZ_LOCATIONS. FND_LOOKUP_VALUES supplies reference code translations used to render descriptive labels in the report output. All tables are referenced through APPS synonyms.

Usage Notes

FUN_XML_REPORT_PKG is not referenced by any other package, indicating it is an entry-point object rather than a shared utility library. It is typical to invoke such a package from a concurrent program registered in Oracle EBS, where the concurrent manager supplies the FND_FILE.OUTPUT destination. The package may also be called from custom code that requires XML output within an EBS session context. Because the package relies on FND_FILE and FND_LOG, it must execute within a valid EBS runtime environment. Developers extending XML report output should use the start-tag, content, and end-tag helper pattern demonstrated by the package body rather than writing raw file I/O.