Search Results igs_ps_purge_del_record




Overview
Explore in AI Chat

Overview

IGS_PS_PURGE_DEL_RECORD is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as an "OTHER" API within the ETRM repository. Its stated purpose, as recorded in the package header comments, is to purge logically deleted records from tables that employ the logical delete pattern — that is, rows flagged as deleted rather than physically removed from the underlying table. The package is scoped specifically to the Program Structure and Planning (PSP) module of Oracle Student Systems / Oracle Higher Education, processing only those tables that belong to that module.

The package was created by user "shtatiko" on 19-FEB-2003, and its source header ($Header: IGSPS88S.pls 120.1 2005/10/04) indicates a maintenance revision during the 11i development cycle. The package remains present and documented in ETRM for both EBS 12.1.1 and 12.2.2, meaning that although its code lineage predates Release 12, it is still catalogued as a valid database object in later application releases.

Key Procedures and Functions

The ETRM metadata documents a single callable program unit within this package:

  • PURGE_PS_RECORDS — The sole documented procedure. It performs the physical removal of records that have been marked as logically deleted within the Program Structure and Planning tables. By centralizing this cleanup in one procedure, the PSP module provides a controlled mechanism for reclaiming storage and removing obsolete data without requiring each functional area to implement its own delete logic. No parameter list is documented in the ETRM metadata; the procedure is referenced as a standalone invocation that operates over the PSP table set defined by the package body.

The package specification contains no other public procedures or functions, and the change history block in the header lists no subsequent modifications beyond the original creation and the shipped revision noted in the header string.

Tables Accessed

ETRM documents the following tables as being referenced by the package through APPS synonyms, all belonging to the Program Structure and Planning data model:

  • IGS_CA_INST_ALL — The calendar instance table, holding dated instances derived from calendar definitions used in program and unit scheduling.
  • IGS_PS_OFR_OPT_ALL — The program offering option table, which stores option-level detail for program offerings.
  • IGS_PS_UNIT_OFR_PAT_ALL — The unit offering pattern table, which defines attendance patterns associated with unit offerings.

These tables are the purge targets: rows in each that carry a logical-delete indicator are candidates for physical deletion when PURGE_PS_RECORDS is executed. Because all three are "_ALL" tables, they are multi-organization enabled, and the purge operates within the appropriate operating unit context. The package is also documented as being referenced by one other package, indicating it participates in a broader PSP housekeeping chain rather than functioning in isolation.

Usage Notes

Packages of this type are normally invoked from a concurrent program, a menu-driven form, or scheduled database job rather than being called interactively by end users. In a typical deployment the concurrent manager submits a purge request that calls IGS_PS_PURGE_DEL_RECORD.PURGE_PS_RECORDS, allowing the purge to run in batch against the PSP tables during a maintenance window. Because the procedure physically deletes rows, it should be run only after logical deletion has been completed and verified, and after confirming that no dependent data or audit requirements prevent permanent removal. Custom code should call the packaged procedure rather than issuing direct DELETE statements against the three referenced tables, so that any internal validation or ordering logic in the package body is preserved. Testing in a non-production environment is advisable before scheduling the purge in production, particularly on Release 12.2.2 where the online patching editioning model affects how long-running batch jobs interact with the database.