Search Results p_active_inactive

Overview

APPS.PO_POXSURUC_XMLP_PKG is the generated PL/SQL package body that supports an Oracle Reports executable (the "XMLP" / XML Publisher variant of a purchasing report). Its header identifies a source revision dated 2007/12/25 and confirms it is a report-side package rather than a public API. In the Oracle EBS 12.1.1 and 12.2.2 environments, packages of this naming pattern are created by Oracle Reports when a report is registered as a concurrent program against a PL/SQL or XML Publisher data model. The package serves as the container for the report trigger logic that Oracle Reports calls during execution: BeforeReport fires before the report layout is generated, and AfterReport fires once processing is complete.

The specific business purpose evidenced by the code is to translate a user-entered lookup value into its descriptive display text. The report accepts a parameter named P_active_inactive, resolves that value against the ACTIVE_INACTIVE lookup type, and exposes the resulting description through a report placeholder, P_active_inactive_disp, for use in the report output.

Key Procedures and Functions

• BeforeReport — The principal documented function and the only one containing meaningful logic. It executes the FND SRWINIT and FND SRWEXIT user exits have been commented out and replaced with null, an XML Publisher adaptation pattern. The function checks whether P_active_inactive is not null; if a value is present, it queries PO_LOOKUP_CODES for the matching displayed_field where the lookup code equals the parameter and the lookup type is ACTIVE_INACTIVE. The retrieved value is assigned to the report placeholder P_active_inactive_disp. If the parameter is null, the placeholder is set to an empty string. The function returns TRUE unconditionally, signalling Oracle Reports to proceed.
• AfterReport — A minimal cleanup function that also returns TRUE unconditionally. Its traditional role would be to invoke FND SRWEXIT, but that call is commented out in this XML Publisher variant, so no post-processing is performed.

Two report placeholder functions are also referenced in the source but are not enumerated among the documented procedures. As with BeforeReport and AfterReport, no parameter lists should be assumed beyond what the source header exposes.

Tables Accessed

The only table read by this package is PO_LOOKUP_CODES, accessed through its APPS synonym. The query is a single-row lookup on the ACTIVE_INACTIVE lookup type, retrieving the displayed_field column for the row whose lookup_code matches the incoming P_active_inactive parameter. This is a read-only operation; the package performs no inserts, updates, or deletes. The lookup type ACTIVE_INACTIVE supplies the standard Enabled/Disabled style values used throughout Oracle Purchasing, which explains why the report surfaces it as a user-selectable parameter.

Usage Notes

Because this is a report package, it is invoked implicitly by the Oracle Reports runtime when the associated concurrent program or report definition executes — not by application forms or by custom PL/SQL callers. The P_active_inactive parameter is defined on the report itself, and Oracle Reports passes it into BeforeReport at runtime. The placeholder P_active_inactive_disp is then available for display in the report layout.

Two practical points follow from the metadata. First, the query has no exception handler: if P_active_inactive contains a value that does not exist in PO_LOOKUP_CODES for type ACTIVE_INACTIVE, the SELECT INTO will raise NO_DATA_FOUND and abort report execution. Second, the disabled FND SRWINIT/FND SRWEXIT calls indicate the report has been repurposed for XML Publisher output, where the Applications initialisation user exits are unnecessary. Customisations to purchasing concurrent programs that rely on this package should avoid altering the package body directly, since regenerating the report can overwrite changes.