Search Results p_salesrep_low




Overview

The APPS.ONT_OEXOEOSR_XMLP_PKG package body is the generated PL/SQL package that backs the Oracle Order Management seeded concurrent program report OEXOEOSR (Order Source / Salesrep Order Detail Report). Its source header (OEXOEOSRB.pls 120.1, 2007/12/25) confirms it is a report XML Publisher (BI Publisher) support package, originally created for Oracle Reports and later converted to the XMLP architecture. The package exists purely to service the runtime data model of that concurrent report: it initialises session context, resolves descriptive lookup values, defines the report's formula columns and group-level summary calculations, and supplies the substitution values consumed by the report layout template.

In Oracle EBS 12.1.1 and 12.2.2 this object resides in the APPS schema and is classified as OTHER; it is not a published business API. It is created by the Order Management patch/installation driver and is regenerated whenever the underlying report definition changes. As with all _XMLP_PKG packages, the naming convention ties it to the concurrent program short name, and each invocation is scoped to a single concurrent request.

Key Procedures and Functions

The package contains 38 documented program units. The most significant are:

Tables Accessed

The package reads the following APPS synonyms:

No INSERT, UPDATE, or DELETE operations are documented; the package is strictly read-only against the transactional and reference tables.

Usage Notes

The package is invoked exclusively by the Order Management concurrent program via the XML Publisher / Oracle Reports runtime, never directly from a form or custom code. The BEFOREREPORT trigger fires once per request before the query executes, while the formula functions are evaluated per row or per group during output generation. Because the package is regenerated by patching, customisations should be applied to a copied report definition rather than to this APPS-owned package body. Note that if P_SOB_ID or P_CONC_REQUEST_ID is not populated, the internal NO_DATA_FOUND handlers silently leave report-level variables null, which manifests as blank header fields on the output rather than as a hard error.