Search Results p_group_name_t

Overview

IGI_IGISLSUA_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. It belongs to the Oracle iSetup/Digital Signature product family (IGI module) and follows the standard XML Publisher concurrent program package convention, where a package bearing the XMLP_PKG suffix acts as the server-side wrapper for a concurrent report. The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking user rather than the package owner. Its header carries the source control marker $Header: IGISLSUAS.pls 120.0.12010000.1 2008/07/29 08:59:52 appldev ship $, identifying the file as a shipped production script first delivered in the 12.0.0 code line and carried forward into 12.1.1 and 12.2.2.

The package provides the mandatory report lifecycle hooks and parameter retrieval logic required by Oracle Reports/XML Publisher concurrent processing. It is designed to expose a report's concurrent program parameters as package globals so that the report's data model and layout can reference them, and to supply before-report and after-report initialization and cleanup logic.

Key Procedures and Functions

• BEFOREREPORT — The standard pre-execution hook. Oracle Reports calls it once at the start of report execution, before the data model queries are processed. It is typically used to derive or default package-level parameters and to perform any setup work that must complete before data retrieval begins.
• AFTERREPORT — The standard post-execution hook, invoked after the report's data and layout phases complete. It returns control to the concurrent manager and is conventionally used to release resources or reset package state.
• CF_1FORMULA — A report-level formula function. It accepts a single IN parameter and returns a NUMBER, allowing the report layout to compute a derived numeric value from an incoming string value, such as a sort key or grouping sequence.
• CP_GROUP_P — A public function returning VARCHAR2, exposing the value of the CP_GROUP package variable to the report. This is the conventional accessor used by report queries and layout formulas to read the current group parameter.

The package also declares public globals, including P_CONC_REQUEST_ID, P_GROUP_NAME and its translated counterpart P_GROUP_NAME_T, P_USER_NAME and P_USER_NAME_T, and CP_GROUP. The presence of P_GROUP_NAME_T explains the user's search term: the "_T" variants hold the translated or displayed form of a group name parameter, while the untranslated variables hold the internal lookup value.

Tables Accessed

The documented metadata does not list any tables referenced through APPS synonyms. This is consistent with the standard XML Publisher wrapper pattern, in which the package itself performs little or no direct table access; the report's SQL queries, defined in the report data model, carry the actual table selections. Any lookup or validation associated with the group and user name parameters would be resolved inside those report queries rather than in the package body. The package makes no documented inserts, updates, or deletes and is therefore read-oriented with respect to database state.

Usage Notes

This package is invoked indirectly by the Oracle EBS concurrent manager when the associated iSetup report program is submitted. The concurrent manager passes the concurrent request identifier into P_CONC_REQUEST_ID, then calls BEFOREREPORT, executes the report, and calls AFTERREPORT. Users never call it directly; it is not referenced by any other documented package, confirming it sits at the top of its own call chain. Customizations should follow Oracle's supported practice of copying the package to a custom schema rather than modifying the shipped APPS version, since a patch or upgrade in 12.1.1 or 12.2.2 may overwrite the original source. Any extension of the parameter surface should preserve the existing public variable names, particularly P_GROUP_NAME and P_GROUP_NAME_T, to avoid breaking the report definition that binds to them.