Search Results igi_igislssg_xmlp_pkg

Overview

IGI_IGISLSSG_XMLP_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM as an "OTHER" API type. The package name incorporates the XMLP_PKG suffix, a naming convention applied to the generated PL/SQL packages that back Oracle XML Publisher (XMLP/BIPublisher) report definitions. The embedded IGISLSSG token identifies the report this package supports, which falls within the IGI (Oracle Grants/Projects-related "IGI" public sector and international) application family. The package therefore exists to supply the server-side data logic — a before-report trigger, an after-report trigger, and formula or format-trigger callbacks — that the XML Publisher runtime invokes when the associated concurrent report executes. It is a report-support package rather than a general-purpose business API, and its public surface is dominated by the callback entry points that the BI Publisher engine expects. Its status is VALID, meaning it is compiled and present in the APPS schema. Dependency metadata records that it references SYS.STANDARD and is self-referenced through APPS.IGI_IGISLSSG_XMLP_PKG; no other packages were recorded as referencing it, consistent with its role as a leaf-level reporting package.

Key Procedures and Functions

The ETRM metadata documents eight procedures and functions. Their names map directly onto XML Publisher report lifecycle hooks and parameter-handling helpers:

• BEFOREREPORT — the before-report trigger. It is invoked by the XML Publisher runtime prior to data extraction, and is used to initialize session or reporting state, set up package-level variables, and perform any prerequisite logic required before the query executes.
• AFTERREPORT — the after-report trigger. It runs once report output has been generated, and is used for post-processing or cleanup of state established during the report cycle.
• CF_1FORMULA — a column formula callback. Functions of this naming pattern are referenced from report layout definitions to compute derived column values at run time.
• CF_2FORMULA — a second column formula callback, providing an additional derived-value computation used in the report output.
• CP_PRC_NAME_P — a parameter helper associated with the report's "process name" concurrent parameter, used to resolve or validate that parameter's value for use by the report query.
• CP_SEC_NAME_P — a companion parameter helper for a "section name" concurrent parameter, performing the equivalent resolution for that input.
• F_DATE_ENABLED1FORMATTRIGGER — a format trigger bound to a date-enabled field (index 1). It returns a Boolean controlling whether that report element is rendered or suppressed for a given row.
• F_PRC_DT_ENABLED_AU1FORMATTRIG — a format trigger for a process-date-related element, again controlling conditional display of that portion of the layout.

The CF_, CP_, and FORMATTRIGGER prefixes reflect the conventions Oracle uses when generating the PL/SQL stubs that accompany an XML Publisher data definition and template.

Tables Accessed

The supplied ETRM excerpt does not enumerate specific base tables for this package. Its documented dependencies are limited to SYS.STANDARD and to the package itself, which is typical of these generated XML Publisher support packages: the substantive SQL is usually embedded inside the report's data template rather than being exposed as a documented dependency table list. Where the package does touch data, any table references would be resolved through APPS synonyms at run time. Because no tables are documented, this package should not be treated as a source of record for table-level impact analysis; the underlying report data model — not the PL/SQL wrapper — should be consulted to determine which application tables are read.

Usage Notes

IGI_IGISLSSG_XMLP_PKG is not intended for direct invocation by application forms or custom code. It is called by the Oracle XML Publisher / BI Publisher runtime when the corresponding concurrent program report is submitted. The runtime invokes BEFOREREPORT before extraction, evaluates the CF_ formula and FORMATTRIGGER callbacks while rendering the layout, resolves the CP_ parameter helpers as the report parameters are bound, and finally invokes AFTERREPORT. Developers customizing the report may modify the package body to change before/after-report behavior or formula logic, but such changes should be made through the supported XML Publisher report definition workflow where possible, since regenerating the report can overwrite the generated package. Because no other packages reference it, changes have narrow blast radius, confined to this single report. The package is identical in behavior between EBS 12.1.1 and 12.2.2; the 12.2.2 ETRM listing records it as VALID with the same eight documented callables, and the online patching model in 12.2 does not alter how it is invoked at report run time.