Search Results xtr_xtrltigi_xmlp_pkg




Overview
Explore in AI Chat

Overview

The package APPS.XTR_XTRLTIGI_XMLP_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the XTR product family, which covers Treasury and Risk Management, and more specifically to the Treasury Management component in which letters of intent and related treasury instruments are processed. The "_XMLP_PKG" suffix, a naming convention widely used across the EBS application tier, identifies the package as the server-side companion to an Oracle XML Publisher (BI Publisher) report definition. In EBS releases 12.1.1 and 12.2.2 the package is reported with a status of VALID, confirming that it compiles cleanly against its dependencies.

The primary business function of the package is to bind a concurrent report to the XML Publisher engine. It provides the entry points that the Concurrent Manager and the XML Publisher runtime call while the associated treasury report is executed: one set of routines prepares the report request before the data model query runs, another set adjusts parameters during the parameter form lifecycle, and further routines handle post-processing and page-level formatting. Because the package contains only report-support logic, it does not itself implement a public business API; it is an internal implementation unit classified as OTHER in the documented metadata.

Key Procedures and Functions

The documented package exposes six procedures and functions, each named in accordance with the conventions that Oracle's report registration wizards generate for XML Publisher concurrent programs:

  • BEFOREREPORT — Executed before the report's main data model is processed. It is the standard hook for setting up session context, initialising package variables, and resolving any global values required by the report query.
  • BEFOREPFORM — Invoked before the report parameter form is displayed. It prepares or pre-populates the parameter page, for example by supplying default values or restricting what the user may enter.
  • AFTERPFORM — Invoked after the parameter form is submitted. It validates or transforms the user's parameter entries before the report is executed, and is the customary place for cross-parameter checks.
  • AFTERREPORT — Executed after report generation completes. It performs the corresponding teardown and cleanup, such as deleting temporary or global state created during execution.
  • BETWEENPAGE — Called between report pages to support formatting and pagination behaviour, allowing the report layout to reset or adjust page-level values as output is produced.
  • P_COMPANYVALIDTRIGGER — A validation routine associated with the company parameter. By naming convention it acts as the trigger logic that verifies the selected company against valid treasury organisation values before the report proceeds.

No parameter lists are published in the metadata, so each routine is described here only by its purpose and its position in the report execution lifecycle.

Tables Accessed

According to the documented metadata the package references two tables through APPS synonyms:

  • FND_CONCURRENT_REQUESTS — The core Oracle Application Object Library table that stores every concurrent request submitted in the instance, including the request ID, status, and completion information for the report. The package queries it to identify the currently executing request and its runtime context, which is a standard pattern for XML Publisher report packages.
  • FND_NEW_MESSAGES — A Foundation table used for message and notification handling. The package uses it to raise or retrieve application messages, most likely in support of validation performed by the parameter routines.

No other application tables are documented as referenced, indicating that the report data itself is retrieved by the XML Publisher data model rather than by this package.

Usage Notes

The package is invoked indirectly whenever the associated XML Publisher concurrent program is run. Oracle's report registration framework calls BEFOREREPORT, the parameter form routines, BETWEENPAGE, and AFTERREPORT at the appropriate points in the concurrent request lifecycle. Users generally do not call it directly from forms or custom code; instead, they submit the concurrent report and the Concurrent Manager invokes the packaged logic on their behalf. Because it is registered as a concurrent-program support package, it is not exposed as an open interface.

From a maintenance perspective, the object carries no dependents other than itself, and it references only SYS.STANDARD, FND_CONCURRENT_REQUESTS, and FND_NEW_MESSAGES. This narrow dependency footprint means the package is essentially self-contained, and customisations should target the underlying XML Publisher report definition and data template rather than the package body. In both 12.1.1 and 12.2.2 the object is expected to remain VALID, and recompilation after patching is normally handled by the standard AD utilities.