Search Results igi_cis2007_igippadr_pkg




Overview
Explore in AI Chat

Overview

IGI_CIS2007_IGIPPADR_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its naming convention, combining the IGI (Oracle Financials for the United Kingdom / international localizations) prefix with the CIS2007 and IGIPPADR tokens, identifies it as a reporting component associated with the Construction Industry Scheme (CIS) legislation that took effect in the United Kingdom in 2007. The "IGIPPADR" segment relates to the Contractor Payment and Deduction Statement (commonly rendered as a "payment and deduction statement" — PPADR), a statutory document that contractors must issue to subcontractors summarizing gross payments, materials, and tax deducted under the CIS regime.

The package is classified as OTHER in the ETRM metadata, meaning it is not a formal public API. It functions as a report-support package: its procedures supply derived values, print controls, and descriptive attributes to an Oracle Reports or BI Publisher layout at runtime, rather than exposing transaction-entry business logic. In the EBS 12.1.1 and 12.2.2 file systems, it resides in the $IGI_TOP area and is compiled into the APPS schema alongside other CIS localization objects.

Key Procedures and Functions

The documented interface consists of four procedures and functions, each supporting report generation rather than transactional processing:

  • BEFOREREPORT — A standard Oracle Reports before-report trigger program unit. It performs initialization tasks such as setting global variables, establishing session context, and preparing the data environment before the main query is executed for the CIS payment and deduction statement.
  • GET_PRINT_TYPE — Returns the print format or output type to be applied to the statement, allowing the report to distinguish between print modes (for example, whether a duplicate or specific stationery variant is required).
  • GET_ORG_NAME — Retrieves the organization name of the reporting entity (the contractor) so that the statutory statement is correctly headed with the legal name of the issuing organization.
  • GET_PERIOD_END_DATE — Derives the period end date associated with the CIS return period, which is used to label the statement and to bound the payment and deduction figures presented on it.

The metadata does not document parameter lists for these units, so callers must reference the form or report definition to confirm invocation arguments.

Tables Accessed

The package references AP_OTHER_PERIODS, an Oracle Payables table that stores the definitions of accounting and reporting periods outside the standard Payables period calendar. This dependency is consistent with GET_PERIOD_END_DATE: the procedure reads the relevant non-standard period row to obtain the end date that governs the CIS reporting window. The table is accessed through an APPS synonym rather than a direct schema-qualified reference, which is standard practice in EBS localization code and preserves the APPS-only grant model.

No other application tables are documented as dependencies, indicating that the package is deliberately narrow in scope and relies on its caller (usually the report or concurrent program) to supply the bulk of the transactional data.

Usage Notes

IGI_CIS2007_IGIPPADR_PKG is invoked at runtime by the CIS2007 payment and deduction statement report, primarily through the report's BeforeReport trigger via BEFOREREPORT. The remaining functions are called as formula columns or format triggers within the report layout to populate the organization name, period end date, and print attributes.

The package is not referenced by any other PL/SQL package in the documented dependency set, confirming that it is an end-point component rather than a shared library. Customizations should therefore avoid modifying it directly; instead, extensions should be implemented in custom report definitions that call the standard package. Because it is a localization object, it is only active where the corresponding IGI UK legislative patches have been applied, and it should be validated after any upgrade between 12.1.1 and 12.2.2 to confirm both the package body and dependent report definitions remain in a VALID state.