Search Results populate_history

Overview

The APPS.IGI_CIS2007_IGIPMTHP_PKG package body is part of the Oracle E-Business Suite UK Construction Industry Scheme (CIS) 2007 compliance module, delivered through the IGI (Public Sector / Government) product family. Its principal business purpose is to maintain the historical record of monthly CIS300 contractor returns and the detailed payment and vendor lines associated with those returns. In the CIS regime administered by HM Revenue & Customs, contractors are required to file monthly returns declaring payments made to subcontractors, together with the tax treatment applied to each payment. The package supports the archival and versioning of these submissions by writing snapshot rows into the history tables that mirror the live transaction tables.

Under Oracle EBS 12.1.1 and 12.2.2 the object resides in the APPS schema and is classified under ETRM as an OTHER API rather than a public interface. The body carries a header revision string dated 2007, consistent with the original CIS 2007 legislative rollout, and remains present unchanged through the 12.2.x code line.

Key Procedures and Functions

ETRM documents one named procedure for this package: PR_AUDIT_UPDATE. This routine is the audit-side entry point used to stamp or refresh audit information on the CIS monthly return records, ensuring that creation and update metadata remain consistent when a return is re-processed or archived.

The package source additionally declares populate_history, a private procedure that is the object of the search term "populate_history". Its purpose is to clone an existing monthly return header and its dependent detail rows into the history tables under a newly generated header identifier, while overriding the request status code supplied by the caller. This versioning mechanism preserves prior submission states so that duplicate, superseded, or previously transmitted returns can be retained for audit and reconciliation.

Tables Accessed

The package reads from and writes to the following documented objects via APPS synonyms:

• IGI_CIS_MTH_RET_HDR_T and IGI_CIS_MTH_RET_HDR_T_S — the live monthly return header table and its sequence, used to derive the new header identifier.
• IGI_CIS_MTH_RET_HDR_H — the header history table into which the cloned return header is inserted.
• IGI_CIS_MTH_RET_LINES_T and IGI_CIS_MTH_RET_LINES_H — the live and historical subcontractor payment line tables, supporting line-level archival.
• IGI_CIS_MTH_RET_PAY_T and IGI_CIS_MTH_RET_PAY_H — the live and historical payment allocation tables.
• DUAL — used to fetch the next sequence value.

The consistent _T (transaction) versus _H (history) naming pattern reflects the standard EBS audit-trail design: each history table is a structurally identical copy of its live counterpart, populated on demand rather than by database triggers.

Usage Notes

This package is not a public API and is not referenced by any other package in the ETRM inventory, so it is invoked internally by the CIS2007 processing logic — typically the monthly return generation and submission concurrent programs, or the associated OAF/Forms pages used to review and re-file returns. Because populate_history is declared in the package body only, it cannot be called directly from external code; it is reachable solely through the package's own procedures.

Customizations that require retention of superseded CIS300 submissions should treat the history tables as read-only reference data and avoid bypassing this package, since the sequence-derived header identifier and status-code override are essential to maintaining referential integrity between header, line, and payment history rows.