Search Results p_oe_status

Overview

APPS.PO_POXRQOBO_XMLP_PKG is the packaged body that backs the Oracle EBS concurrent program and Oracle Reports executable associated with the POXRQOBO report — a Purchasing document that presents requisition and order information for XML/BI Publisher output. The package encapsulates report-level entry points, global initialization, and bind-variable computation for the Oracle Reports runtime. In Oracle EBS 12.1.1 and 12.2.2 it is deployed under the APPS schema and is classified as an OTHER API in ETRM, meaning it is not a public PL/SQL API intended for external callers but rather internal report infrastructure executed as part of the concurrent program lifecycle.

The specific search term p_oe_status refers to the report parameter that determines whether the Oracle Order Entry (OE) installation check succeeds before the report is allowed to run.

Key Procedures and Functions

The package body exposes eight documented program units. Their roles are as follows:

• BeforeReport — The Oracle Reports trigger fired before data retrieval. It resolves quantity precision via PO_COMMON_XMLP_PKG.get_precision, calls the structure number initialization, and performs the OE status validation for the p_oe_status parameter.
• AfterReport — The post-report trigger; in the shipped source it simply returns TRUE after the framework exit call.
• get_p_struct_num — Initializes the P_STRUCT_NUM global by selecting the structure id from mtl_default_sets_view where functional_area_id = 2.
• C_backorderedFormula — Column formula that conditionally returns a quantity expression (nvl(wdd.requested_quantity,0)) when p_oe_status = 'I'.
• C_whereFormula — Supplies the dynamic WHERE clause fragment used by the report query.
• C_fromFormula — Supplies the dynamic FROM clause fragment used by the report query.
• C_ship_quantityFormula — Column formula for the shipped/order quantity measure.
• G_requisitionGroupFilter — Group filter function governing requisition-level grouping/filtering in the report layout.

The p_oe_status logic is the central gate: fnd_installation.GET_APP_INFO is called for application 'PO' to populate P_OE_STATUS, and when the value is not 'I' the program returns FALSE and prevents execution with a message drawn from po_lookup_codes.

Tables Accessed

• MTL_DEFAULT_SETS_VIEW — Read to derive the item structure/functional area identifier used by the report.
• PO_LOOKUP_CODES — Read to retrieve descriptive messages (CANNOT RUN PROGRAM, FAILURE TO GET STATUS) for the SRW MESSAGE lookup type.
• PO_COMMON_XMLP_PKG — Referenced utility package for precision handling; not a table but a dependency.

The ETRM metadata lists no direct table references outside these, reflecting that most data access is delegated to the report SQL rather than PL/SQL.

Usage Notes

The package is invoked implicitly by the Oracle Reports runtime when the associated POXRQOBO concurrent program is submitted — never called directly by forms or custom code. The BeforeReport trigger fires when the report session opens, applies the p_oe_status installation check, and aborts the concurrent request if the OE application is not installed or if a failure occurs. The AfterReport trigger runs on session teardown.

Administrators encountering a request that fails at the p_oe_status check should verify ONT/OE installation registration in FND_INSTALLATION for the PO application, since the check is driven by fnd_installation.GET_APP_INFO. Because the package is marked OTHER and has no dependents, downstream customizations should not assume any supported API contract.