Search Results ordered_item_id_p




Overview

ONT_OEXOECCL_XMLP_PKG is a server-side PL/SQL package owned by the APPS schema that supports the Oracle Order Management customer item cross-reference report. The package name encodes its origin: OEXOECCL corresponds to the Order Management "Ordered Item / Customer Item Cross-Reference Listing" report, and the _XMLP_PKG suffix identifies it as the BI Publisher (XML Publisher) report logic package generated for the XML report template. It is declared AUTHID CURRENT_USER, so it executes with the privileges of the invoking user rather than as the package owner. Its responsibility is to collect report parameters, format display values, execute the underlying query logic against Order Management and inventory tables, and return a data-found flag so the report template can render either the detail output or a "no data found" message.

In Oracle EBS 12.1.1 and 12.2.2, this package is not part of the public application programming interface. It falls under the OTHER API classification and is intended strictly for internal consumption by the associated concurrent program and report definition. The header revision note indicates the package has been stable since at least Release 12.0, with the last recorded change in 2008.

Key Procedures and Functions

The package exposes twenty-two documented procedures and functions. Several fall into recognizable groupings:

  • BEFOREREPORT, AFTERREPORT, and AFTERPFORM are the standard XML Publisher report triggers. BEFOREREPORT establishes the report context before the query executes; AFTERPFORM fires after the parameter form is processed; AFTERREPORT performs cleanup and post-processing once the query completes.
  • C_DATA_NOT_FOUNDFORMULA evaluates whether the report returned any rows, returning a numeric indicator used by the template to suppress or display a "no records" message.
  • C_ADDRESSFORMULA concatenates address components (address line, city, state) into a single formatted mailing address string for the report layout.
  • P_ITEM_FLEX_CODEVALIDTRIGGER is the validation trigger for the P_ITEM_FLEX_CODE parameter, ensuring the user-entered item flexfield code is valid before the report runs.
  • INVENTORY_ITEM_ID_P, ORDERED_ITEM_P, and ORDERED_ITEM_ID_P are the accessor functions that return the internal inventory item identifier, the ordered item value, and the ordered item identifier respectively. The ORDERED_ITEM_ID_P function is the corresponding accessor for the ORDERED_ITEM_ID package variable, which is the object users locate when searching for "ordered_item_id_p." Accessors of this type exist because XML Publisher reports require public functions rather than direct variable references when binding values into the report template.
  • The remaining functions—RP_REPORT_NAME_P, RP_SUB_TITLE_P, RP_COMPANY_NAME_P, RP_FUNCTIONAL_CURRENCY_P, RP_DATA_FOUND_P, RP_DATE_HOLD_APPLIED_RANGE_P, RP_SHIP_P, RP_ORDER_P, RP_VAT_PROFILE_P, RP_PRINT_DESCRIPTION_P, and RP_ITEM_FLEX_ALL_SEG_P—are accessors for the report header and layout variables (the RP_ prefix denotes report parameters). They supply the report title, subtitle, company name, functional currency, hold-date range text, ship-to and order labels, VAT profile, print-description flag, and the item flexfield segment list.

Tables Accessed

The package queries seven tables through APPS synonyms, all read-only:

Usage Notes

This package is invoked exclusively by the Order Management customer item cross-reference concurrent program and its XML Publisher template. It is not called by Oracle Forms, nor is it referenced by any other documented package. The user search term "ordered_item_id_p" maps to the ORDERED_ITEM_ID_P accessor function, which is a report binding helper and not a callable business API. Because the package is classified as OTHER and carries the standard "noship" header marker, Oracle does not guarantee its interface across patches or upgrades. Customizations should not reference these functions directly; instead, customers requiring similar output should build their own concurrent program or use supported Order Management public APIs and views.