Search Results genp_del_log

Overview

Concurrent Program IGSGEJ01 is a system maintenance utility owned by the IGS — Student System product family within Oracle E-Business Suite. Its user-facing name is Delete System Log Entries, and its internal description mirrors that name. The program's purpose is to purge accumulated log records generated by the Student System's own logging mechanism, freeing space in the log table and keeping diagnostic data within manageable limits. In the ETRM 12.2.2 metadata the product is flagged as Obsolete, and the program carries an Enabled: Yes status, meaning it remains submittable in environments where the Student System schemas are still installed and the underlying package is present. The term the user searched for, genp_del_log, is in fact the execution file name for this program, i.e. the stored procedure entry point that the concurrent manager actually invokes.

Execution Details

The documented execution configuration is as follows:

• Execution Method: PL/SQL Stored Procedure
• Argument Method: Standard
• Executable: IGSGEJ01
• Execution Filename: IGS_GE_GEN_001.GENP_DEL_LOG
• Subroutine Name: (not documented)

Because the execution method is PL/SQL Stored Procedure, the concurrent manager calls the packaged procedure IGS_GE_GEN_001.GENP_DEL_LOG directly rather than launching a host script or report binary. The procedure package IGS_GE_GEN_001 resides in the Student System schema and encapsulates the DELETE logic against the log repository. The absence of a subroutine entry indicates the callable unit is the procedure at the package level, and no additional routine qualifier is appended at submission time.

How to Run

Users submit IGSGEJ01 through the standard Submit Requests (SRS) window, or programmatically via FND_REQUEST.SUBMIT_REQUEST using the executable short name IGSGEJ01. The program is registered with the Standard argument method, so parameters are presented in the standard SRS parameter block; the ETRM excerpt does not enumerate individual parameters, and the metadata provides no documented token list. In practice, purging utilities of this class generally accept a date or range criterion (for example, delete log rows older than a supplied date) so that operators can bound the volume of rows removed in a single run. When executing such a purge, the run should be scheduled during a low-activity period because the procedure performs direct deletes on the log table, and the output should be reviewed through the concurrent request log to confirm the number of rows processed. Oracle's recommended practice for this category of program is to verify space and rollback/undo capacity before a large purge and to retain recent log entries required for open service requests.

Related Objects

The program operates against the Student System logging tables maintained by the IGS_GE_GEN_001 package. Objects commonly associated with this maintenance activity include:

• The Student System log table(s) populated by the IGS logging routines, which supply the rows that GENP_DEL_LOG removes.
• Package IGS_GE_GEN_001, the executable's owning package and the location of the GENP_DEL_LOG procedure.
• The concurrent program definition and executable registration in the Application Object Library (FND_CONCURRENT_PROGRAMS / FND_EXECUTABLES), where IGSGEJ01 is defined with the PL/SQL Stored Procedure method.
• Standard concurrent manager and request-log reports used to monitor the purge and reconcile deleted volumes.

Because IGS is documented as Obsolete in 12.2.2, administrators should confirm whether custom or legacy code still depends on GENP_DEL_LOG before relying on this program for routine housekeeping, and should consider retiring it in favour of current logging maintenance utilities.