Search Results purge_records

Overview

The APPS.IGS_GE_PURGE_DEL_RECORD package body is a component of the Oracle E-Business Suite Student System (IGS) general (GE) subsystem. Its business function is to physically remove records that have previously been logically deleted (soft-deleted) from the base application tables, reclaiming storage and maintaining data integrity across the product's logical-delete framework. The header comment identifies the author as "Shtatiko" and the creation date as 19-FEB-2003, with the stated purpose being "to purge logically deleted records from the tables, where logical delete functionality is being used." The package operates as a top-level orchestrator: rather than performing deletions directly, it invokes module-specific sub-processes that each handle the purging logic pertinent to their own functional area. In the current documented revision (120.1, dated 09-JAN-2006), the only activated sub-process is the PS module call, although the design anticipates additional module processors. The change history records that Bug# 4869737 introduced a call to igs_ge_gen_003.set_org_id, which is directly relevant to the search term "set_org_id".

Key Procedures and Functions

The package body exposes a single documented procedure:

• PURGE_RECORDS — The entry point and sole procedure of the package. It accepts the standard concurrent-program parameter signature used across Oracle EBS: errbuf OUT NOCOPY VARCHAR2 and retcode OUT NOCOPY NUMBER. These parameters are characteristic of a concurrent program's PL/SQL executable, allowing the program to return an error message and a completion status code to the concurrent manager. Within its executable section, PURGE_RECORDS first establishes the runtime operating-unit context through igs_ge_gen_003.set_org_id(NULL), then delegates the actual purge work to the PS module sub-process igs_ps_purge_del_record.purge_ps_records. An EXCEPTION WHEN OTHERS handler sets retcode := 2, loads the message IGS_GE_UNHANDLED_EXP via FND_MESSAGE (with the token NAME set to "purge_records"), concatenates that message with SQLERRM into errbuf, and finally calls IGS_GE_MSG_STACK.CONC_EXCEPTION_HNDL to register the failure on the message stack.

Tables Accessed

The ETRM metadata does not enumerate any base tables referenced directly through APPS synonyms by this package. The absence of a direct table list is consistent with the package's design as an orchestrator: it owns no DML of its own and instead relies on the called sub-processes (notably igs_ps_purge_del_record.purge_ps_records) to read and delete records from the underlying module tables. The set_org_id call to igs_ge_gen_003 implies that the sub-processes depend on an initialized operating unit (ORG_ID) context, typically maintained in FND session state rather than in a domain table accessed by this package itself.

Usage Notes

PURGE_RECORDS is designed to be run as a concurrent program under the Oracle EBS concurrent manager. This is evidenced by its errbuf/retcode signature and its use of FND_MESSAGE and the IGS message stack for error reporting. Administrators invoke it when logically deleted records require physical removal — for example, during scheduled housekeeping of the Student System or when database growth from soft-deleted rows must be controlled. Because the package relies on set_org_id to set the operating-unit context, it should be submitted with an appropriate responsibility/operating unit so that the downstream PS purge logic processes the correct data set. The catastrophic exception handler ensures that any unhandled error is returned to the concurrent manager with a status of 2 and an informative message rather than failing silently. No other packages are documented as referencing this package, and it exposes no public API beyond the concurrent-program entry point.