Search Results p_owner_t

Overview

IGI_IGISLSOS_XMLP_PKG is an Oracle Applications (APPS) PL/SQL package that supports the Oracle E-Business Suite XML Publisher (BI Publisher) concurrent program associated with the IGI product line (the former "IGI" application module, historically linked to Oracle Financials for the public sector and grants-related reporting). Packages in the IGISLSOS family follow the standard Oracle Reports-to-XML Publisher conversion naming convention, where the "_XMLP_PKG" suffix denotes a package automatically generated to underpin an XML Publisher report definition. The "IGISLSOS" report identifier indicates a specific seeded report within the IGI module, and this package serves as its data-model entry point.

The package defines global (session-level) package variables and a small set of functions that are invoked by the XML Publisher report engine at runtime. Its primary purpose is to expose concurrent program parameters — notably the table name and owner parameters referenced in the user's search — to the report's data template, and to provide the before/after report life-cycle hooks that Oracle generates for every XML Publisher report wrapper.

Key Procedures and Functions

The ETRM metadata documents four procedures/functions, all with PUBLIC scope and no reserved argument lists reported beyond those shown for the one formula function:

• BEFOREREPORT — The standard "before report" trigger function. It executes once at the start of report processing, prior to fetching data, and is where Oracle-generated code typically initializes package globals, resolves the concurrent request ID, and validates the incoming parameters.
• AFTERREPORT — The standard "after report" trigger function. It executes once after all data has been retrieved and formatted. Oracle-generated implementations usually perform cleanup or final status handling here.
• CF_1FORMULA — A "column formula" (CF) function. Oracle names these CF_<n>FORMULA and they compute derived column values in the report query output. This one accepts a table name argument, indicating the formula is applied per-row against the supplied table name.
• CP_TABLE_NAME_P — A parameter accessor function that returns the VARCHAR2 value of the CP_TABLE_NAME package variable, exposing the concurrent program's table name parameter to the XML Publisher data template.

Tables Accessed

The documented ETRM metadata for this package does not list any tables referenced via APPS synonyms. This is consistent with the package's role as a thin parameter and life-cycle wrapper: the actual query logic for the IGISLSOS report is defined in the XML Publisher data template (an associated .xml/.rtf definition) or in a separate report query, not in PL/SQL embedded in this package. Where table access does occur, it is driven dynamically by the P_TABLE_NAME and P_OWNER parameters, which is why the package stores them as VARCHAR2 globals rather than hard-coding object references.

Usage Notes

This package is not intended for direct invocation by developers or custom code. It is invoked exclusively by the Oracle XML Publisher concurrent program engine when the associated IGISLSOS report is submitted from the Concurrent Programs form or from the XML Publisher Administrator responsibility. The package is listed as being referenced by zero other packages, confirming that it sits at the top of its own call stack with no dependencies from other PL/SQL units.

The parameters P_OWNER and P_TABLE_NAME (and their _T "text" counterparts) correspond directly to the concurrent program's input parameters. The user's search term "p_owner_t" refers to the character (text) form of the owner parameter — used by the report engine to pass the schema/owner name as a displayable string, distinguishing it from the non-suffixed variable that may hold a resolved or typed value. Both P_TABLE_NAME/P_TABLE_NAME_T and P_OWNER/P_OWNER_T follow this dual-variable convention. Because these are package-level globals set by BEFOREREPORT, customizations should avoid modifying this seeded package directly; parameter-driven behavior should instead be adjusted through the concurrent program definition or the XML Publisher template.