Search Results l_order_type_low_disp

Overview

ONT_OEXWFASG_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that serves as the report logic container for the Order Management workflow assignment diagnostic report. The "XMLP" suffix in the package name identifies it as a BI Publisher (XML Publisher) report package, generated to support the OEXWFASG concurrent report program. The package is declared with AUTHID CURRENT_USER, meaning its unqualified database object references resolve against the privileges of the invoking user rather than the package owner, and its header carries the source control signature "$Header: OEXWFASGS.pls 120.0 2007/12/31 12:37:17 dwkrishn noship $". This signature confirms the package has been part of the Order Management code line since at least the 11i/R12 transition and remains present, unchanged, in 12.1.1 and 12.2.2. Its functional purpose is to gather and format the data used by the workflow assignment report, which displays the assignment of order types and order lines to Oracle Workflow processes and activities. The package exposes a small, focused public surface consisting entirely of report lifecycle hooks and report attribute accessors, with the substantive report extraction logic implemented in the accompanying report query and the underlying OE_ tables. The package is classified as API classification OTHER, indicating it is an internal report-support object and is not a published, supported public API for customer extension.

Key Procedures and Functions

The package documents five procedures and functions.

• BEFOREREPORT — The standard BI Publisher/Reports "before report" trigger function, returning BOOLEAN. It performs initialization work prior to report execution, such as setting up the WHERE clause and derived values used by the report query.
• AFTERREPORT — The standard "after report" trigger, returning BOOLEAN. It executes cleanup and finalization once the report body has been produced.
• AFTERPFORM — The "after parameter form" trigger, returning BOOLEAN. It runs after the concurrent program's parameter form has been submitted, and is the typical location for deriving the flexible L_* and LP_* variables from the user-entered parameters.
• RP_REPORT_NAME_P — A report attribute accessor function returning VARCHAR2, exposing the RP_REPORT_NAME package variable, which carries the report's display name property.
• RP_COMPANY_NAME_P — A report attribute accessor function returning VARCHAR2, exposing the RP_COMPANY_NAME package variable, which carries the company name property printed in the report header or footer.

Parameter lists are not documented and should not be assumed. The public package specification additionally declares the typed package variables P_CONC_REQUEST_ID, P_ORDER_TYPE_HI, P_ORDER_TYPE_LO, P_SOB_ID, LP_WHERE_CLAUSE, L_ORDER_TYPE_LOW, L_ORDER_TYPE_LOW_DISP, L_ORDER_TYPE_HIGH, L_ORDER_TYPE_HIGH_DISP, RP_REPORT_NAME, and RP_COMPANY_NAME, which give the report its parameter and derived-value context (concurrent request ID, order type range, and set of books ID).

Tables Accessed

Two APPS-synonym tables are documented as referenced by the package.

• FND_CONCURRENT_REQUESTS — The Oracle Application Object Library concurrent request table. The package reads it, keyed by P_CONC_REQUEST_ID, to obtain request-level context such as the submitting user and request attributes used to drive report formatting and security.
• OE_TRANSACTION_TYPES_TL — The Order Management order/transaction type translation table. The package reads it to translate the order type identifiers and range parameters into translated, user-facing descriptions, populating L_ORDER_TYPE_LOW_DISP and L_ORDER_TYPE_HIGH_DISP for the report output.

The documented metadata lists no write operations, and no other packages are shown to reference this package.

Usage Notes

This package is not intended for direct invocation. It is called by the Oracle Reports/BI Publisher runtime when the OEXWFASG concurrent program is executed from the Order Management responsibility (typically under the workflow assignment or order type setup diagnostics menu). The runtime calls AFTERPFORM after parameter entry, BEFOREREPORT before the query, and AFTERREPORT after output generation; the RP_*_P accessors are invoked by the report layout to retrieve package-level display values. Because the package is classified as OTHER and does not appear in the published API taxonomy, customizations should not call its procedures directly. Integrity concerns in this report are more commonly caused by missing OE_TRANSACTION_TYPES_TL translations for the requested order type range or by invalid concurrent request context than by defects in the package itself.