Results for “csi_csicprep_xmlp_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CSI_CSICPREP_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under ETRM as API classification OTHER. It supports the concurrent program report "Customer Products - Summary" (internally identified through the RP_REPORT_NAME variable, which carries the literal value "Customer Products - Summary"). The package is generated in the Oracle Reports XML Publisher (XMLP) integration style: the _XMLP_PKG suffix and the presence of BEFOREREPORT, AFTERREPORT, AFTERPFORM, and _P return functions are characteristic of the PL/SQL library that Oracle Reports attaches to a report definition when XML Publisher output is used.

The package declares the bind and lexical parameters that the report accepts at runtime, including P_SOB_ID (the Set of Books identifier), P_ITEM_STRUCT_NUM, P_FLEX_ITEM_CODE, P_ORGANIZATION_ID, P_INSTALL_LOCATION, P_CP_STATUS, and the customer number low/high range. Lexical parameters such as LP_CUSTOMER_RANGE, LP_ITEM_RANGE, LP_INSTALL_LOCATION, LP_CP_STATUS, and P_ITEM_WHERE are initialized to the neutral predicate "and 1=1", which the report dynamically replaces with the user's filter selections to build the query WHERE clause.

Key Procedures and Functions

• BEFOREREPORT — Standard Oracle Reports XMLP package hook executed before the report's data model is processed, used to initialize package state and report parameters.
• AFTERREPORT — Standard post-report hook executed after report execution completes, used for cleanup or final report-level processing.
• P_SOB_IDVALIDTRIGGER — Validation trigger function for the P_SOB_ID parameter. It corresponds to the user's search term p_sob_idvalidtrigger. This is the Reports validation trigger fired when the Set of Books parameter is entered, permitting the report to confirm that a valid Set of Books identifier has been supplied before the query executes.
• AFTERPFORM — After-parameter-form hook, invoked once the report parameter form is completed, commonly used to derive dependent parameters or populate lexical values before the main query runs.
• RP_REPORT_NAME_P — Returns the report name (RP_REPORT_NAME), defaulted to "Customer Products - Summary".
• RP_COMPANY_NAME_P — Returns the company name (RP_COMPANY_NAME), used to print the organization's legal name in the report header.

Tables Accessed

The ETRM metadata for this package documents no tables referenced through APPS synonyms. This is expected for the XMLP PL/SQL package portion of a report: the package is largely a parameter and hook container, while the actual data retrieval for the Customer Products - Summary report is performed by the Oracle Reports query and the underlying CSI (Customer Support Intelligence / installed base) views and tables, not by static SQL embedded in this package. Any table access occurs through the report's query definition rather than through the package body.

Usage Notes

This package is not intended to be invoked directly by custom code. It is generated and maintained automatically when the underlying Oracle Reports definition is compiled or migrated, and it is called by the Reports runtime whenever the Customer Products - Summary concurrent program is run from the Concurrent Programs or the relevant application responsibility. The validation trigger P_SOB_IDVALIDTRIGGER fires as part of the report parameter form processing in Oracle Reports; if a value fails validation, the user is prompted to correct the Set of Books selection before the report proceeds. Because the package is AUTHID CURRENT_USER and resides in APPS, any customizations should be applied to the report definition rather than to the package itself. Direct references from other packages are not documented (0 referencing objects), confirming its role as a leaf-level, report-dedicated module.