Search Results rp_print_description_p

Overview

ONT_OEXOEUBK_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. It is a report-support package generated for the Oracle Order Management "Open Orders" style concurrent program, whose XML Publisher (BI Publisher) template is driven by the concurrent request parameters declared in this specification. The package name follows the standard Oracle Reports-to-XML Publisher conversion convention (the _XMLP_PKG suffix), and the "$Header" comment (OEXOEUBKS.pls, version 120.2, dated 2008/05/05) confirms it originated as the server-side library for the OEXOEUBK report.

The package declares the report parameter block (P_CONC_REQUEST_ID, P_SOB_ID, P_ORDER_BY, P_CREATED_BY_LOW/HIGH, P_ITEM_FLEX_CODE, P_ORGANIZATION_ID/ID1, P_ORDER_DATE_LOW/HIGH, P_ITEM_STRUCTURE_NUM, P_PRINT_DESCRIPTION, P_ORDER_CATEGORY, P_LINE_CATEGORY, P_ONE_TIME, C_PERIODICITY_DSP_FLAG, and the LP_ display variables), together with the BEFORE/AFTER report and form triggers and the group of "P" getter functions used by the XML Publisher data template. Its business purpose is to gather open order and item information for printing, applying the item flexfield structure, currency, category, and date-range filters selected at run time.

Key Procedures and Functions

• BEFOREREPORT — Initialisation logic executed once before the report query runs; populates report context values such as functional currency and company name.
• AFTERREPORT — Post-processing/cleanup routine invoked after the report completes.
• P_ITEM_FLEX_CODEVALIDTRIGGER — Validation trigger for the P_ITEM_FLEX_CODE parameter; validates the entered item flexfield key flexfield combination and derives RP_ITEM_FLEX_ALL_SEG (defaulting to 'MSI.SEGMENT1') for use by the report query. This is the object referenced by the search term "p_item_flex_codevalidtrigger".
• AFTERPFORM — Fires after the parameter form is populated, typically to default or conditionally enable dependent parameters (for example organisation-dependent values).
• RP_ORDER_CATEGORYFORMULA / RP_LINE_CATEGORYFORMULA — Return formatted display text for the order and line category parameters.
• C_MASTER_ORGFORMULA — Returns the master organisation context used to resolve value sets such as inventory organisations.
• C_PERIODICITY_DSPFORMULA — Converts a charge periodicity code into its display value.
• RP_REPORT_NAME_P, RP_SUB_TITLE_P, RP_COMPANY_NAME_P, RP_FUNCTIONAL_CURRENCY_P, RP_DATA_FOUND_P, RP_ITEM_FLEX_ALL_SEG_P, RP_PRINT_DESCRIPTION_P, RP_DUMMY_ITEM_P — Getter functions that expose report attributes to the XML Publisher template.
• ITEM_DSPFORMULA — Returns the formatted item display value (flexfield concatenation or description) for each report row.

Tables Accessed

• FND_CONCURRENT_REQUESTS — Reads the concurrent request record using P_CONC_REQUEST_ID to resolve submission context.
• FND_CURRENCIES — Resolves functional currency name/description for RP_FUNCTIONAL_CURRENCY.
• MTL_CUSTOMER_ITEMS / MTL_CUSTOMER_ITEM_XREFS — Customer item definitions and customer-to-internal item cross-references included in the output.
• MTL_CROSS_REFERENCES / MTL_CROSS_REFERENCE_TYPES — Cross-reference values and their type definitions, used to print item cross-reference information.
• DUAL — Used in scalar computation expressions.

Usage Notes

The package is invoked indirectly: the concurrent program tied to the OEXOEUBK report calls these routines at run time, the parameter form triggers P_ITEM_FLEX_CODEVALIDTRIGGER and AFTERPFORM during parameter entry, and the XML Publisher data template calls the RP_* getter functions to obtain header and row attributes. It is not referenced by any other documented package (referenced-by count is zero), so custom code should not depend on it. Because it is AUTHID CURRENT_USER, execute privileges and any direct SQL issued inside it resolve against the calling schema rather than APPS. The declared parameter variables are also read/overwritten by the report engine at run time, so they should not be treated as an API entry point.