Search Results cf_hold_valueformula




Overview

ONT_OEXOEWFR_XMLP_PKG is an Oracle Application Object Library generated PL/SQL package that backs the Oracle Order Management XML Publisher (BI Publisher) concurrent report OEXOEWFR, commonly known as the Order Workflow Status Report or a related order exception/aging report. In Oracle EBS 12.1.1 and 12.2.2, concurrent programs registered against XML Publisher data templates and report definitions produce a supporting package that encapsulates the report's lexical parameters, its before/after triggers, and its user-defined summary and formula columns. This package is owned by APPS and is classified as OTHER; it exposes an API surface consisting of public package globals and 27 procedures and functions. It performs no business transactions of its own and is not referenced by any other package, which confirms that it is an implementation artifact of a single concurrent program rather than a shared library.

Key Procedures and Functions

Tables Accessed

  • OE_ORDER_HOLDS_ALL — read to resolve hold names, hold release information, and hold status for the order or line being reported, supporting CF_HOLD_VALUEFORMULA.
  • WF_ITEM_ACTIVITY_STATUSES and WF_PROCESS_ACTIVITIES — read through the Workflow views to determine the current activity and process state of each order header flow, which drives the report's workflow status columns.
  • DUAL — used by the formula functions for scalar lookups and constant resolution.

Usage Notes

The package is invoked only by its associated XML Publisher concurrent program; developers do not call it directly. Substitution parameters such as P_ACTIONS, P_OVERDUE_DAYS, P_ORDER_TYPE, P_ORDER_NO_LOW, P_ORDER_NO_HIGH, P_LINE_CATEGORY, P_ITEM, and P_NO_DATA are passed at submission time and are available as package globals throughout report execution. The P_NO_DATAVALIDTRIGGER function that the user searched for is the validation trigger for P_NO_DATA; when customizing or debugging the report, extensions should be implemented in the corresponding XML data template or PL/SQL after-processor rather than by modifying ONT_OEXOEWFR_XMLP_PKG, because the package is regenerated whenever the report definition is recompiled and any direct edits are lost. Organizations that require enhanced validation of the P_NO_DATA parameter should instead restrict the parameter's list of values in the concurrent program definition or wrap the report invocation with a custom concurrent program.