Search Results p_print_description

Overview

The package body APPS.ONT_OEXIODIS_XMLP_PKG implements the server-side PL/SQL logic that supports the Oracle Order Management "Open Orders and Item Details" XML Publisher (BI Publisher) report, historically known as the Order Information Detail (OEXIODIS) concurrent program. It is a report-support package generated in the standard XML Publisher report package pattern, in which a combination of package-level variables, a before-report function, an after-form trigger function, and multiple value-returning "R_" and "CF_" formula functions are consumed by the report template to render parameter labels, column captions, and conditional SQL fragments. The package is owned by APPS and is classified as API classification OTHER, meaning it is not intended for external calling as a public API; it is an internal report companion object.

The package was last shipped with a header revision dated 2008/05/05 and remains present in EBS 12.1.1 and 12.2.2, largely unchanged, because it drives a long-standing order-line detail reporting requirement rather than a core transactional API.

Key Procedures and Functions

The documented package exposes 24 procedures and functions. The principal groups are:

• AFTERPFORM — the after-parameter-form trigger. It evaluates the user's runtime parameter selections (order number low/high, order date low/high, order type low/high, open-order-only flag, item ranges, and so on) and builds the lexical LP_* global variables that carry dynamically assembled WHERE-clause fragments and concatenated bind conditions. It also resolves transaction type names from OE_TRANSACTION_TYPES_TL using USERENV('LANG'), with each block wrapped in a nested WHEN OTHERS THEN NULL handler.
• BEFOREREPORT and AFTERREPORT — report lifecycle hooks that initialize session state before the query executes and perform any cleanup afterwards.
• CF_* formula functions — CF_SO_HOLDFORMULA, CF_PO_ITEM_DISPLAYFORMULA, and CF_ORDER_BYFORMULA are conditional formula functions that return the display option selected for the sales-order hold, purchase-order item display method, and report ordering, respectively.
• C_BUILD_LBLFORMULA — assembles label/heading text used by the report layout.
• RP_* report parameter functions — RP_REPORT_NAME_P, RP_COMPANY_NAME_P, RP_SUB_TITLE_P, RP_ORDER_RANGE_P, RP_REQUISITION_RANGE_P, RP_ORDER_DATE_RANGE_P, RP_ITEM_DISPLAY_METHOD_P, RP_OPEN_ORDER_ONLY_P, RP_ORDER_BY_P, RP_ITEM_FLEX2_P, RP_ITEM_FLEX_ALL_SEG_P, and RP_ITEM_RANGE_P — return formatted parameter display strings for the report header. These are the functions a user inspects when searching on p_print_description, since the print/display description text is ultimately produced through this parameter-formatting family.
• P_CUSTOMER_NUMBER_LOWVALIDTRIG — a validation trigger function associated with the customer number low parameter.

No parameter lists are documented in the metadata; purposes are inferred from function naming and the OEXIODIS report context.

Tables Accessed

The package references the following tables through APPS synonyms:

• FND_CONCURRENT_REQUESTS — provides concurrent request context, typically for report identification, request ID, and parameter logging.
• OE_TRANSACTION_TYPES_TL — supplies translated order transaction type names for the order type low/high parameters, restricted to the session language.
• OE_ORDER_HOLDS_ALL — supports the sales order hold display logic.
• MTL_CUSTOMER_ITEMS, MTL_CUSTOMER_ITEM_XREFS — supply customer item number and cross-reference data for the item detail output.
• MTL_CROSS_REFERENCES, MTL_CROSS_REFERENCE_TYPES — provide cross-reference type descriptions used in item cross-reference display.

Usage Notes

This package is invoked only by the XML Publisher engine when the OEXIODIS report is submitted as a concurrent program. It is not referenced by any other package (referenced-by count of 0), so it should be treated as a private report implementation object. It is not a supported extension point. Customizations should be limited to copying and cloning the report definition rather than modifying the shipped package. Because it executes under the APPS schema and constructs SQL fragments from user-entered parameters, runtime errors in parameter text are absorbed by local WHEN OTHERS THEN NULL handlers, which can silently suppress messages; this behavior is consistent with legacy XML Publisher report packages and is a consideration when debugging unexpected report output.