Search Results xtr_xtrliexp_xmlp_pkg




Overview
Explore in AI Chat

Overview

The APPS.XTR_XTRLIEXP_XMLP_PKG package is a generated PL/SQL package in Oracle E-Business Suite that accompanies the Oracle XML Publisher (BI Publisher) report definition associated with the ETRM (External Tax and Regulatory Management) module. In EBS, every XML Publisher concurrent program that uses a data definition based on a PL/SQL package produces a dedicated package of the form <report_name>_XMLP_PKG. This package serves as the runtime engine for the report's data model: it defines the bind parameters, resolves format triggers and value sets used by the report's parameter form, and executes the SQL query that populates the XML data feed consumed by the report template.

The name indicates an XTR (E-Business Tax / regulatory reporting) subsidiary ledger or line-item export report. The package owns the standard lifecycle hooks expected of an XML Publisher data source, and its status is VALID, confirming it is compiled and deployed in the target instance.

Key Procedures and Functions

The ETRM documentation records eight procedures and functions classified under API classification OTHER, reflecting their internal, report-supporting role rather than a public integration interface:

  • CF_SET_PARAFORMULA — a column/formula function that supplies the parameter list values (names, data types, and defaults) used to build the report's parameter form.
  • CF_DESCRIPTIONFORMULA — returns the descriptive text for a report parameter, providing the label shown to the user.
  • COMPANY_CODEVALIDTRIGGER — a validation trigger executed when the company/legal entity parameter is entered, enforcing that a valid organization or company code is selected before the report runs.
  • LIMIT_CODEVALIDTRIGGER — a validation trigger for the limit code parameter, restricting selection to configured tax or regulatory limit codes.
  • BEFOREREPORT — the standard XML Publisher hook that runs before the data query is executed; it initializes session context, resolves lexical parameters, and prepares the query environment.
  • AFTERREPORT — the complementary hook executed after the data set is fetched, used for cleanup and post-processing.
  • AFTERPFORM — invoked after the parameter form is submitted to finalize parameter processing before data retrieval.
  • CP_PARA_P — the concurrent program parameter retrieval procedure that exposes the report parameters to the concurrent manager.

Tables Accessed

The package references three objects through the APPS schema:

  • FND_CONCURRENT_REQUESTS — read to obtain the concurrent request identifier and runtime context for the current submission, allowing the report to log and retrieve request-specific information.
  • FND_NEW_MESSAGES — the EBS messages repository, used to resolve translatable message text for prompts, validation messages, and report labels.
  • DUAL — the standard single-row utility table, used for simple value evaluations and trigger logic.

Notably, the package does not directly reference the XTR transaction tables in the documented metadata; the reporting query for the extract is embedded in the XML Publisher data definition rather than in this package body.

Usage Notes

This package is not intended for direct invocation by developers or by other application code — the metadata confirms it is referenced by zero other packages. It is executed implicitly by the Oracle XML Publisher concurrent program infrastructure whenever the associated XTR_ XTRLIEXP report is submitted from the Submit Request form, an EBS menu function, or an OAM/OCM request set. The BEFOREREPORT, AFTERREPORT, and AFTERPFORM entry points are called automatically by the XML Publisher engine, while the validation triggers are fired interactively as the user completes the parameter form. Oracle recommends treating this as a generated, report-owned object: customizations should be applied through the XML Publisher data definition or the report template rather than by editing the package directly, since the object is regenerated on patch application and is classified as internal API. Behavior is consistent across EBS 12.1.1 and 12.2.2, with the 12.2.2 edition documented here.