Search Results p_to_sls_security_group

Overview

IGI_IGISLSCG_XMLP_PKG is an Oracle Applications (APPS) PL/SQL package that supports the IGISLSCG Oracle Reports XML Publisher (XMLP) concurrent program in Oracle E-Business Suite 12.1.1 and 12.2.2. The suffix "XMLP_PKG" identifies it as the standard generated package that Oracle Reports Builder creates when an RDF report is converted to the XML Publisher publishing model. Its principal role is to host the packaged variables and report-level trigger logic that the report uses to accept parameters, execute query-level calculations, and return values to the runtime engine.

The naming convention IGISLSCG indicates an IGI (Oracle Enterprise Asset Management / iAssets family) module object relating to a "Security Group" listing report. The package is therefore part of the security-group reporting feature that allows an EAM-enabled installation to enumerate and validate the security groups defined for the enterprise, and to constrain the report to a range of security groups. The RCS header comment (IGISLSCGS.pls, version 120.0.12010000.1, dated 2008) confirms the object has been part of the EBS code line since the 12.0 release and persists unchanged through 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes four documented program units, all declared without arguments in the specification except where a formal parameter is explicitly shown.

• BEFOREREPORT — the report-level Before Report trigger. It performs setup logic prior to the report query executing, typically initializing package variables, resolving the concurrent request context, and preparing the parameter values that the data model expects.
• AFTERREPORT — the report-level After Report trigger. It runs once the report has been generated and is used for post-processing, cleanup, and returning status to the concurrent manager.
• CF_1FORMULA — a formula column or formula trigger that accepts a TO_SLS_SECURITY_GROUP value and returns a NUMBER. It encapsulates a computed value derived from the security group parameter, most commonly a numeric flag or count used to control conditional formatting or grouping in the report output.
• CP_TO_SLS_SECURITY_GROUP_P — a getter function that returns the current value of the TO_SLS_SECURITY_GROUP parameter or its global variable. It provides report layout sections and other formula columns with a controlled read path to the parameter.

The specification also declares the public package variables P_TO_SLS_SECURITY_GROUP, P_TO_SLS_SECURITY_GROUP_T, P_FROM_SLS_SECURITY_GROUP, P_FROM_SLS_SECURITY_GROUP_T, and P_CONC_REQUEST_ID, together with the global CP_TO_SLS_SECURITY_GROUP. The "_T" variants hold the display (translated/description) form of the corresponding parameter, while the non-suffixed variables hold the stored value. P_CONC_REQUEST_ID carries the concurrent request identifier generated when the report is submitted.

Tables Accessed

No base tables are documented as directly referenced through APPS synonyms by this package. This is consistent with the XMLP_PKG pattern: the package itself contains report-trigger logic and parameter plumbing, while the report's data model query — not the PL/SQL package — performs the SELECTs against the underlying security-group views. Any table access in the IGISLSCG report is therefore executed by the query attached to the concurrent program rather than by the package body, and the package's variables simply supply bind values such as the from/to security group range and the concurrent request ID.

Usage Notes

IGI_IGISLSCG_XMLP_PKG is not intended to be called directly by application forms or custom code. It is invoked implicitly by the Oracle Reports runtime when the IGISLSCG concurrent program or its XML Publisher template is executed. The report engine fires BEFOREREPORT prior to query execution and AFTERREPORT after output is produced, while CF_1FORMULA and CP_TO_SLS_SECURITY_GROUP_P are called from the report layout and formula columns.

The metadata records zero referencing packages, confirming that the package is a leaf dependency used only by its own report definition. Because the search term p_from_sls_security_group_t corresponds to the public variable of the same name in the specification, users investigating this object are typically tracing how the From Security Group parameter is bound and displayed in the report. Customizations should avoid altering the package specification, since XML Publisher regenerates the specification and body whenever the underlying report is recompiled or upgraded, and any changes would be overwritten during patching. Where additional filtering or a modified security group range is required, the supported approach is to copy the concurrent program and its report definition rather than modify the seeded package.