Search Results ont_oexordtp_xmlp_pkg




Overview
Explore in AI Chat

Overview

ONT_OEXORDTP_XMLP_PKG is an Oracle Application Object Library package body owned by APPS in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is the backing PL/SQL package generated for the Oracle Order Management seeded concurrent program that produces the Order Transaction Types report, identified in the source header as OEXORDTPB.pls. The package provides the report-level server-side logic that the Oracle Reports XML publisher executable invokes at defined trigger points in the report life cycle. It is classified under the ETRM API classification OTHER, indicating that it is not a public, supported integration API but rather an internal report-support package.

Its principal responsibilities are to initialize report-level variables, to build the dynamic WHERE clause fragments that drive the transaction type query used by the report, and to expose the resulting values to the report layout through packaged functions. The report enumerates transaction type definitions that control order entry behavior, and the package therefore plays a supporting role in order-management configuration reporting rather than in transactional processing.

Key Procedures and Functions

  • BEFOREREPORT — Executed before the report query fires. It derives and assigns the organization (set of books) name by querying GL_SETS_OF_BOOKS using the P_SOB_ID parameter, and resolves the concurrent program name from FND_CONCURRENT_PROGRAMS_VL and FND_CONCURRENT_REQUESTS using P_CONC_REQUEST_ID. When no matching program row is found, it falls back to the literal report title. It returns TRUE on completion.
  • AFTERPFORM — Executed after the report parameter form is processed. It constructs LP_WHERE_CLAUSE, the dynamic predicate applied to the transaction type view, based on the high and low transaction type name parameters. When both range values are supplied it builds a BETWEEN-style clause; when only one bound is supplied it builds an equality predicate; when neither is supplied it proceeds to evaluate the transaction type code and order category parameters. This is the procedure directly relevant to the search term p_order_category, which participates in the alternate branch of the WHERE clause construction.
  • AFTERREPORT — Executed after the report completes, used for end-of-report processing such as cleanup or final state handling.
  • RP_REPORT_NAME_P — Packaged function exposing the resolved report name (RP_Report_Name) to the report layout.
  • RP_ORG_NAME_P — Packaged function exposing the resolved organization or set of books name (rp_org_name) to the report layout.
  • RP_DATA_FOUND_P — Packaged function returning a flag that indicates whether report data was retrieved.

Tables Accessed

The ETRM metadata documents FND_CONCURRENT_REQUESTS as a referenced table, accessed through APPS synonyms to correlate the current request with its concurrent program definition and thereby resolve the report title displayed in the output. In addition, the package body source references GL_SETS_OF_BOOKS for organization name resolution and FND_CONCURRENT_PROGRAMS_VL for the concurrent program display name. All access is read-only; the package performs no DML.

Usage Notes

This package is not intended for direct invocation by custom code. It is invoked implicitly by the Oracle Reports runtime when the Order Transaction Types concurrent program is submitted, with BEFOREREPORT firing before the query, AFTERPFORM after the parameter form, and AFTERREPORT at completion. The RP_* functions are called from within the report layout to render derived values. Because the package is classified as OTHER and is referenced by no other documented packages, it should be treated as an internal implementation artifact. Customizations should be confined to the concurrent program parameters — including the order category and transaction type parameters surfaced through the WHERE clause logic — rather than to the package itself, since the body is subject to replacement during patching.