Search Results c_cost_variance_p

Overview

PO_POXRQSDD_XMLP_PKG is the PL/SQL package that backs the Oracle Purchasing seeded XML Publisher report POXRQSDD (Requisition and Order Shipment/Receipt Detail). The package was last modified under header revision 120.2 (2007/12/25) and is declared AUTHID CURRENT_USER, so it executes with the privileges of the invoking APPS session. Its role is to hold report-level global variables, format masks, and the PL/SQL functions invoked from the report's data model and formula columns, and to compute shipped quantity, quantity variance, and cost variance for requisition and purchase order lines.

The public globals include report parameters such as P_CONC_REQUEST_ID, P_REQ_NUMBER_FROM, P_REQ_NUMBER_TO, P_CREATION_DATE_FROM, P_CREATION_DATE_TO, P_REQUESTOR, P_QTY_PRECISION, P_ORDERBY, P_OE_STATUS, P_SINGLE_PO_PRINT, and P_WHERE_QUERY. Numeric accumulators C_quantity_shipped, C_Quantity_Variance, and C_Cost_variance hold running report totals, exposed through the C_QUANTITY_SHIPPED_P, C_QUANTITY_VARIANCE_P, and C_COST_VARIANCE_P accessor functions used by the report layout. The user search term "get_shipped_quantity" corresponds to the function declared at line 31 of the package.

Key Procedures and Functions

• GET_SHIPPED_QUANTITY — the function matching the user's search. It accepts an original line number, an original header number, and an order source identifier, and returns the shipped quantity for the referenced order line. It is the primary entry point used by the report to derive shipped quantity from the originating order rather than from requisition data alone.
• C_GET_SHIPPED_QUANTITY — a companion computation that takes quantity delivered, unit price, line, requisition number, and order source ID, and returns a shipped quantity value. It supports the report's formula columns where line-level context is required.
• BEFOREREPORT — initialization logic that runs before the report query is executed, typically resolving the precision and format mask values.
• AFTERPFORM — post-parameter-form processing used to validate or transform user-entered parameters before report execution.
• AFTERREPORT — cleanup and any final report-level processing.
• GET_PRECISION — populates the quantity precision and format mask globals (QTY_PRECISION and FORMAT_MASK) so quantities are displayed consistently.
• ORDERBY_CLAUSEFORMULA — returns the dynamically built ORDER BY clause used by the report query based on the user's P_ORDERBY selection; P_ORDERBY_DISPLAYED holds the user-facing value.
• C_SHIPPED_QTYFORMULA, C_SELLING_PRICEFORMULA — formula columns that compute the shipped quantity and selling price displayed on the report.
• C_FROMFORMULA, C_WHEREFORMULA — formula columns that return the FROM and WHERE fragments for the report's dynamic SQL, driven by P_WHERE_QUERY and related parameters.
• C_QUANTITY_SHIPPED_P, C_QUANTITY_VARIANCE_P, C_COST_VARIANCE_P — accessor functions returning the current values of the corresponding package globals for use in report totals and summaries.

Tables Accessed

• OE_ORDER_HEADERS_ALL — the Order Management order header table, read to identify the originating sales order for lines whose order source indicates OE order flow.
• OE_ORDER_LINES_ALL — the Order Management order line table, read to obtain line-level shipment and pricing attributes used in the shipped quantity and variance calculations.
• PO_SYSTEM_PARAMETERS — the Purchasing system parameters table, read by the precision and format mask routines to resolve quantity display precision and other report defaults.

Usage Notes

PO_POXRQSDD_XMLP_PKG is invoked indirectly through the POXRQSDD XML Publisher report definition, not as a standalone API. Oracle E-Business Suite 12.1.1 and 12.2.2 users run the report from the Purchasing responsibility or submit it as a concurrent program; the report framework calls BEFOREREPORT, then the formula columns, then AFTERPFORM and AFTERREPORT as part of the standard XML Publisher execution sequence.

Because the package is AUTHID CURRENT_USER and owned by APPS, all executions occur in the APPS schema context. The package is referenced by no other documented PL/SQL packages, confirming it is a report-specific private package rather than a shared utility. Customization should be limited to copying the package under a site-specific name and repointing the report definition, since direct modification of the APPS-owned package violates Oracle's support guidelines and may be overwritten by patching.