Search Results p_item_lo

Overview

The APPS.CSI_CSICPREP_XMLP_PKG package body is the server-side PL/SQL library associated with the Oracle EBS concurrent report Customer Products Summary Report. The package follows the standard Oracle Reports XML Publisher (XMLP) integration pattern, in which a report definition is bound to a generated PL/SQL package that owns the report's user parameters and provides the procedural hooks executed at defined points in the report lifecycle. In this case, the report draws on Oracle Inventory item and item-category data and is executed from the Discrete/Process Manufacturing or Order Management reporting menus.

The package's primary role is to make the report's user parameters available to the SQL query defined in the report data model, and to supply the values of the report's session context (organisation, request identifier, company name, report title). The header comment ($Header: CSICPREPB.pls 120.1 … noship $) indicates the file is owned by the CSI (Customer Support/Service) product family and has not been shipped to customers as a standalone script, but exists in the APPS schema as the compiled executable for the XMLP report definition.

Key Procedures and Functions

• BEFOREREPORT — the mandatory Before Report trigger function. It initialises the runtime environment, populates the report's session parameters (organisation identifier from the SO_ORGANIZATION_ID profile option, concurrent request identifier from FND_GLOBAL.CONC_REQUEST_ID), and resolves the company name and report title by calling the shared reporting utilities CS_REPORTS_PACKAGE.CS_GET_COMPANY_NAME and CS_REPORTS_PACKAGE.CS_GET_REPORT_NAME. It also builds the dynamic P_ITEM_WHERE fragment used to constrain the report query according to the item selection parameters.
• AFTERREPORT — the After Report trigger function, which performs post-report housekeeping, typically releasing the report resources acquired during initialisation.
• AFTERPFORM — the After Parameter Form trigger, executed once the user has submitted the parameter form and before the report query runs. It is used to validate and prepare derived parameter values.
• P_SOB_IDVALIDTRIGGER — the validation trigger for the P_SOB_ID (Set of Books) report parameter, ensuring the user-supplied ledger identifier is valid before the report executes.
• RP_REPORT_NAME_P — a function returning the formatted report name used on the printed output, populated by CS_GET_REPORT_NAME in BEFOREREPORT.
• RP_COMPANY_NAME_P — a function returning the formatted company/legal entity name displayed in the report header, populated by CS_GET_COMPANY_NAME in BEFOREREPORT.

Tables Accessed

The ETRM metadata records no direct table references through APPS synonyms; all database access for the Customer Products Summary Report is performed by the report's own SQL query, not by the package. The package itself only invokes supporting APIs — principally the shared CS_REPORTS_PACKAGE routines that resolve company and report titles — and reads profile option and concurrent request context values via FND_PROFILE and FND_GLOBAL. The report query itself operates against Oracle Inventory item and category views.

Usage Notes

The package is invoked indirectly: it is executed by the XML Publisher/Reports runtime whenever the Customer Products Summary Report concurrent program is submitted. It is not designed to be called directly from custom code, and no other PL/SQL package in the APPS schema references it (recorded as "Referenced by 0 other packages"). The package is present in both 12.1.1 and 12.2.2 environments; the 12.2.2 metadata confirms the same six documented entry points. The parameter p_item_lo, which appears in the searched source context, is a report parameter representing the low bound of the item range; together with p_item_high and p_item_struct_num it controls the dynamic WHERE clause assembled in BEFOREREPORT.