Search Results p_where

Overview

INV_INVIRCXR_XMLP_PKG is the generated PL/SQL package body that supports the Oracle E-Business Suite XML Publisher (BI Publisher) concurrent program "Customer Item Cross Reference Report" (internal short name INVIRCXR), which is part of the Oracle Inventory (INV) module. The package implements the standard report-trigger interface used by Oracle Reports and XML Publisher report definitions: it initializes the concurrent request context, dynamically assembles a SQL WHERE clause from user-supplied report parameters, and performs cleanup at report completion. In EBS 12.1.1 and 12.2.2, packages of this naming convention (ending in _XMLP_PKG) are automatically generated when a report is converted to the XML Publisher engine, and they remain resident in the APPS schema so that the XML template and its associated data model or query can consume package-level variables such as P_WHERE.

Key Procedures and Functions

• BEFOREREPORT — The core logic of the package. It first captures the concurrent request identifier via FND_GLOBAL.CONC_REQUEST_ID, then conditionally concatenates filter predicates onto the package variable P_WHERE based on whether each user parameter is populated. The parameters covered include customer, customer address category, concatenated address, customer item number (from and to), item level, and a "list lowest rank" flag. When P_LIST_LOWEST_RANK is set to Yes or Y, the WHERE clause is extended with a correlated subquery against MTL_CUSTOMER_ITEM_XREFS_V that restricts results to the minimum rank per customer item and master organization. The function returns TRUE to allow the report to proceed.
• AFTERREPORT — The report teardown trigger. In the generated source, the legacy SRW.USER_EXIT('FND SRWEXIT') call has been commented out, leaving a NULL body that simply returns TRUE. It exists to satisfy the standard report trigger contract and to allow Oracle's report conversion tooling to hook post-processing logic if required.
• G_BODYGROUPFILTER — A boilerplate group filter function that unconditionally returns TRUE. It is generated automatically for XML Publisher report packages and serves as a placeholder hook; it applies no runtime filtering in this deployment.

Tables Accessed

The package metadata does not list any base tables read or written directly by PL/SQL statements. The only database object referenced within the source is the view MTL_CUSTOMER_ITEM_XREFS_V, which is queried inside the correlated subquery that enforces the "lowest rank" filter when P_LIST_LOWEST_RANK is enabled. All other filtering is expressed as text in the P_WHERE variable, which the report's underlying query consumes at runtime; those base tables (for example, customer and customer item cross-reference entities) are therefore accessed by the report SQL rather than by this package itself. No INSERT, UPDATE, or DELETE operations are performed.

Usage Notes

• The package is invoked automatically by the Oracle Reports/XML Publisher runtime whenever the INVIRCXR concurrent program is submitted; users do not call it directly.
• The p_where variable is the key integration point. All parameter-driven filtering is built here and later injected into the report data model, so changes to report parameters must be reflected in BEFOREREPORT.
• Parameter values are concatenated into the WHERE string with literal quoting, which is characteristic of these generated packages and is a known SQL injection consideration; parameter values should therefore be validated at the concurrent program definition level.
• ETRM metadata records three documented procedures, zero referencing packages, and APPS as the owner. The source header ($Header: INVIRCXRB.pls 120.1 ... noship) indicates the file is flagged noship and is maintained by Oracle development rather than intended for customer modification.
• Because the object resides in the APPS schema, any customization should be done through supported extension mechanisms rather than direct edits, which would be overwritten by patching.