Search Results p_creation_date_to

Overview

PO_POXACTPO_XMLP_PKG is the generated PL/SQL package body that supports the Oracle Purchasing concurrent program "POXACTPO" — the Purchasing Activity Report. In Oracle EBS 12.1.1 and 12.2.2 this report provides buyers, purchasing managers, and financial analysts with a listing of purchase order activity across a specified date range, organized by creation date or buyer. The package body follows the standard Oracle Reports server-side PL/SQL architecture: Oracle Reports Builder generates a package specification and body containing user-named program units and formula columns, which are then compiled into the APPS schema and invoked at report runtime by the Reports Server.

The primary business purpose of the package is to normalize runtime parameters before the report query executes. Users enter values such as a creation date range in an Oracle Forms-based parameter window; the package converts those values into display-ready formats and resolves lookup codes into their user-facing descriptions so that the printed report header and layout show meaningful text rather than internal codes. The header comment marker ($Header: POXACTPOB.pls) confirms the package was last revised in 2008 and is shipped as a nonshipped ("noship") object, meaning it is generated rather than a maintained API.

Key Procedures and Functions

• BEFOREREPORT — The central initialization routine. It runs before the report's data model queries fire. It resolves the parameter P_TYPE against PO_LOOKUP_CODES for lookup type 'PO TYPE' and assigns the displayed description to P_type_displayed. It performs the same resolution for P_orderby against lookup type 'SRS ORDER BY', populating P_orderby_displayed. It then formats LP_CREATION_DATE_FROM and LP_CREATION_DATE_TO using a DD-MON-YY mask applied to the user-supplied P_CREATION_DATE_FROM and P_CREATION_DATE_TO parameters. This directly explains why the search term "p_creation_date_from" maps to this object: the parameter is the report's lower bound on PO creation date and is transformed here for display.
• AFTERREPORT — Runs after report completion. In this package it is effectively a stub, returning TRUE; the original SRW.USER_EXIT('FND SRWEXIT') cleanup call has been commented out, reflecting the migration away from SRW user exits toward the FND concurrent manager initialization model.
• ORDERBY_CLAUSEFORMULA — A formula column that translates the user's ORDERBY selection into the numeric column reference used by the report's GROUP BY / ORDER BY logic. A value of 'DATE' returns '1'; 'BUYER' returns '5'; all other values default to '1'.
• ROUND_AMOUNT — Accepts an amount and a currency precision and returns the amount rounded to that precision. Normally invoked in the report's data model to present PO line amounts consistent with the transaction currency's defined precision.
• BASE_AMOUNT_ROUND — Parallel rounding function for base (functional) currency amounts, taking the base amount and a precision argument. Ensures ledger-currency totals align with the ledger's rounding rules.
• AFTERPFORM — Executes after the parameter form is submitted. It is a placeholder in this package, with the historical SRW user-exit call commented out.

Tables Accessed

The documented table reference is FINANCIALS_SYSTEM_PARAMETERS, accessed via an APPS synonym. This is consistent with the report reading ledger and currency context — most importantly the functional currency and its precision — which the rounding functions rely on indirectly. In addition, the BEFOREREPORT logic queries PO_LOOKUP_CODES (Purchasing lookup codes) to resolve the PO TYPE and SRS ORDER BY values into displayed text. The main report data query, which retrieves the actual purchase order activity rows, is defined in the Oracle Reports XML/RDF file rather than in these package program units.

Usage Notes

The package is never called directly by end users or by custom PL/SQL. It is invoked implicitly by the Oracle Reports runtime when the POXACTPO concurrent program is submitted from the Purchasing responsibility (Reports > Run, or via the concurrent manager). The parameter P_CREATION_DATE_FROM — the term that led to this article — is one of the report's submission parameters, typically paired with P_CREATION_DATE_TO, and is passed directly into the package's BeforeReport logic for display formatting.

Because the package is generated and marked "noship," it must not be modified directly; any customization should be applied to a copy of the source .rdf/.pls file and recompiled, otherwise patches will overwrite the changes. The presence of only six documented program units and one table reference reflects the thin role of the package: it primarily mediates parameters and formatting while the bulk of data retrieval resides in the report definition itself. Environments upgrading between 12.1.1 and 12.2.2 should treat this package as stable, generated code with no public API surface.