Search Results ont_oexoepcl_xmlp_pkg




Overview
Explore in AI Chat

Overview

ONT_OEXOEPCL_XMLP_PKG is an Oracle Applications (APPS) package body belonging to the Oracle Order Management (ONT) module. The "_XMLP_PKG" naming suffix indicates it is an Oracle XML Publisher (BI Publisher) concurrent program support package generated for the Order Management "Pricing" or "Price List" report family, specifically the program identified by the short name OEXOEPCL (Order Management Pricing report). The package body encapsulates the PL/SQL logic that executes during runtime of the associated XML Publisher concurrent program. It is responsible for initializing report parameters and formatting values—such as company name, report title, sub-title, and functional currency—that are consumed by the report template to render output. Because it resides in the APPS schema and references standard FND and OE views, it operates as a standard, concurrent-manager-driven reporting utility rather than an integration or business transaction API.

Key Procedures and Functions

The package exposes eight documented procedures and functions, characteristic of an XML Publisher report support package generated by the Oracle report publishing framework:

  • BEFOREREPORT — Executes at the start of report execution to perform initialization tasks before data retrieval begins.
  • AFTERREPORT — Executes at the end of report processing, typically to release resources or finalize output.
  • AFTERPFORM — Invoked after the report parameter form has been processed, used to derive or validate values based on user-entered parameters.
  • C_APPL_TOFORMULA — A function that supplies the "Application" value to the report formula/parameter set, identifying the application context.
  • RP_REPORT_NAME_P — Supplies the report name parameter used for the report header and template resolution.
  • RP_SUB_TITLE_P — Supplies the sub-title text displayed on the report output.
  • RP_COMPANY_NAME_P — Supplies the legal entity or company name for the report header, typically derived from GL sets of books.
  • RP_FUNCTIONAL_CURRENCY_P — Supplies the functional currency code for the operating unit or set of books, sourced from FND_CURRENCIES.

Tables Accessed

The package references its data primarily through APPS synonyms. The documented tables include FND_CONCURRENT_REQUESTS and FND_CURRENCIES. FND_CONCURRENT_REQUESTS is read to identify the current concurrent request and its associated parameters, allowing the report to resolve context at runtime. FND_CURRENCIES provides currency information used to populate the functional currency value returned by RP_FUNCTIONAL_CURRENCY_P. Broader dependency information shows the package also draws on FND_CONCURRENT_PROGRAMS_VL (concurrent program definition), FND_GLOBAL (session context such as user, responsibility, and org), FND_LOOKUPS and OE_LOOKUPS (lookup code meanings), and GL_SETS_OF_BOOKS (company and functional currency derivation). Several OE_PC_* views (OE_PC_ATTRIBUTES_V, OE_PC_ENTITIES_V, OE_PC_RESPS_V, OE_PC_RSETS_VL, OE_PC_VENTITIES_V, OE_PC_VTMPLTS_VL) are referenced, indicating the report surfaces pricing or price-list configuration entities such as price list attributes, entities, responsibility assignments, and templates.

Usage Notes

ONT_OEXOEPCL_XMLP_PKG is invoked automatically by the concurrent manager as the PL/SQL component of the associated XML Publisher concurrent program; it is not intended to be called directly from Oracle Forms or custom PL/SQL. The FND_CONCURRENT_REQUESTS reference confirms the package executes within the standard concurrent processing framework, using FND_GLOBAL to establish session context for the responsible application, responsibility, and organization. Per the ETRM metadata, the package is referenced by zero other database objects, meaning it is a terminal reporting package with no downstream dependents. Customizations should be applied cautiously: because XML Publisher report packages are regenerated by the publisher, direct modifications may be overwritten. Organizations requiring changes typically copy the definition or apply template-level customization instead. The package is marked VALID in both Oracle EBS 12.1.1 and 12.2.2, and its dependencies on standard FND and OE objects remain consistent across both releases.