Search Results l_order_type_high_disp

Overview

ONT_OEXWFASG_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the generic API classification of OTHER. The package name follows the standard Oracle Reports XML Publisher naming convention, where the _XMLP_PKG suffix denotes a report-level package generated or maintained alongside a concurrent program definition. The embedded header comment, $Header: OEXWFASGS.pls 120.0 2007/12/31, ties the object to the Order Management (ONT) module and specifically to the Order Import / Workflow Assignment family of reports, reflected in the "OEXWFASG" fragment of the report short name.

The package serves as the supporting PL/SQL layer for an XML Publisher (BI Publisher) report that drives Oracle Order Management transaction type assignment data. It encapsulates global parameter values, display variables, and report lifecycle hooks used by the report's data model to build the runtime query and to render header information such as the report name and company name. The presence of variables such as L_ORDER_TYPE_LOW_DISP and L_ORDER_TYPE_HIGH_DISP confirms that the report presents low and high order type ranges to the user, and that the package maintains both the raw concatenated value and the display-formatted value for each bound.

Key Procedures and Functions

• BEFOREREPORT — Standard Oracle Reports trigger function executed before the report's data model is processed. It initializes package-level parameters, prepares the LP_WHERE_CLAUSE dynamic filter used by the report query, and populates display variables derived from the order type range inputs.
• AFTERPFORM — Executed after the parameter form is submitted. This function drives post-parameter-form logic, resolving the user-entered P_ORDER_TYPE_HI and P_ORDER_TYPE_LO values into the internal L_ORDER_TYPE_HIGH, L_ORDER_TYPE_HIGH_DISP, L_ORDER_TYPE_LOW and L_ORDER_TYPE_LOW_DISP variables and setting the set-of-books identifier P_SOB_ID.
• AFTERREPORT — Executed when report processing completes. It performs end-of-report cleanup and releases any package state retained during execution.
• RP_REPORT_NAME_P — Returns the value of the RP_REPORT_NAME variable, exposing the report name to the report template for header display.
• RP_COMPANY_NAME_P — Returns the value of the RP_COMPANY_NAME variable, exposing the organization or company name to the report template for header display.

Tables Accessed

• FND_CONCURRENT_REQUESTS — Read to retrieve the concurrent request identifier and related runtime attributes used to bind the report execution context, seeded through the P_CONC_REQUEST_ID global.
• OE_TRANSACTION_TYPES_TL — The translated Order Management transaction type table. It supplies the order type names and descriptions that populate the low and high order type values and their display equivalents.

Both tables are accessed through APPS synonyms, which is typical for report-support packages in the ONT schema territory. The package neither writes to nor is referenced by other PL/SQL packages; the metadata records zero inbound package references, indicating it is a terminal consumer invoked only by its associated report.

Usage Notes

This package is invoked exclusively by its accompanying Oracle Reports / XML Publisher concurrent program; it is not an API intended for direct invocation from forms, workflows, or custom code. Administrators configure it by assigning the concurrent program to a request group and submitting it from the Order Management responsibility. The parameter values P_ORDER_TYPE_HI and P_ORDER_TYPE_LO are supplied by the user on the report parameter form. Because the object is documented as APPS-owned with a NOSHIP header tag, it should be treated as an Oracle-managed internal object; customizations should be limited to the underlying report definition rather than the package itself.