Search Results xtr_xtrdisre_xmlp_pkg




Overview
Explore in AI Chat

Overview

XTR_XTRDISRE_XMLP_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM metadata as an OTHER API. Its name follows the standard Oracle XML Publisher (BI Publisher) concurrent program package convention: the "XMLP" infix indicates that the package drives a report defined against an XML Publisher data template, and the "XTR" prefix places it within the Treasury (XTR) product family. The "DISRE" component points to a disbursement-related report, most likely a disbursement register, reconciliation, or similar treasury cash disbursement report executed as a concurrent program.

In Oracle EBS 12.1.1 and 12.2.2, such packages are generated by Oracle's report registration utilities and are executed by the concurrent manager when the associated XML Publisher report is submitted. The package encapsulates the report's PL/SQL logic: it binds the concurrent request context, evaluates report parameters, executes the report query, and returns the resulting XML to the XML Publisher engine for formatting against an RTF or XSL-FO template. The ETRM record confirms the object is VALID and depends only on the SYS.STANDARD package, indicating the implementation relies on standard PL/SQL constructs rather than external APIs.

Key Procedures and Functions

The package exposes five documented program units. No parameter signatures are documented in the ETRM metadata, so only their conventional roles are described.

  • BEFOREREPORT — Standard XML Publisher report trigger executed before the report data query runs. It is used to initialize package state and prepare the concurrent request context for the report.
  • AFTERPFORM — Trigger fired after the report parameter form is processed. It is typically used to validate or capture parameter values submitted by the user for the treasury disbursement report.
  • AFTERREPORT — Post-processing trigger that runs after the report data set has been generated. It performs cleanup logic and any final context resets required by the XML Publisher engine.
  • CF_SET_PARAFORMULA — A formula-setting routine associated with the report's parameter form, used to derive or default parameter values dynamically at runtime.
  • CP_PARA_P — A concurrent program parameter helper, conventionally used to hold or resolve concurrent program parameter values passed at submission time.

Tables Accessed

ETRM documents three tables referenced through APPS synonyms:

  • FND_CONCURRENT_REQUESTS — Read to obtain the current concurrent request identifier and its execution context, which the report logic uses to key and log its output.
  • FND_NEW_MESSAGES — Accessed for message resolution, allowing the report to raise or display Oracle Applications-standard messages during execution.
  • DUAL — Used for singleton evaluations and initialization statements.

These framework tables indicate that the package itself is administrative in nature; the actual treasury disbursement data query is embedded in the report definition and executed through the XML Publisher data template rather than through explicit table references captured in the package dependency list.

Usage Notes

XTR_XTRDISRE_XMLP_PKG is not intended for direct invocation by custom code. It is invoked indirectly by the Oracle concurrent manager when the corresponding XML Publisher treasury report is submitted from the Submit Request window or from an Oracle Forms-based disbursement workflow. ETRM confirms the package is referenced by zero other packages, so it is a top-level entry point with no inbound PL/SQL dependencies, and it references no other APPS packages beyond the SYS.STANDARD built-in.

Because the package name follows Oracle's generated naming convention, it should be treated as an Oracle-owned artifact. Extensions or modifications should be limited to the underlying data template or, where supported, to personalization of the report's parameter form; editing the package body directly is unsupported and would be overwritten during patching. The package remains valid in both 12.1.1 and 12.2.2, where the XML Publisher runtime architecture is unchanged with respect to report package execution.