Results for “p_end_date”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMO_PURGE is a maintenance utility package that belongs to the Oracle E-Business Suite Process Manufacturing (GMO) module family, specifically the Oracle Enterprise Technical Reference Model (ETRM) component associated with shop-floor device and instruction management. Its documented purpose is to clean up temporary or transient data generated by the GMO device and instruction subsystems, removing obsolete rows from the underlying transactional tables so that the operational tables do not grow without bound and continue to perform efficiently.

The package header header comment in the source reads simply "Cleans the device temporary data" and "Cleans the instruction temporary data." Two administrative entry points exist: one that purges device-related temporary rows (PURGE_DEVICE_DATA), one that purges instruction-related temporary rows (PURGE_INSTRUCTION_DATA), and a third (PURGE_ALL) that combines both. The package is owned by APPS, is classified as OTHER in the ETRM catalog (i.e., not a public integration API), and is referenced by no other packages, indicating it is a standalone housekeeping program rather than a shared library.

Key Procedures and Functions

  • PURGE_DEVICE_DATA — Removes aging temporary data associated with the GMO device requests and responses tables. It accepts an end date parameter that bounds which records are eligible for removal, a truncate flag controlling whether the purge is performed by truncation rather than row-by-row deletion, and a commit flag. It is one of the 4 documented procedures/functions for the package.
  • PURGE_INSTRUCTION_DATA — Performs the equivalent cleanup for instruction temporary data, covering the instruction definition, instance, attribute, and task tables. Like the device variant, it takes an end date, a truncate option, and a commit option.
  • PURGE_ALL — The aggregate purge. It is exposed in two forms: a programmatic form that purges both the device and instruction modules together, and a concurrent-program form that is the standard way of running the routine from the EBS concurrent manager. The concurrent-manager form uses the conventional errbuf/retcode OUT parameters (return code 0 = success, 1 = warning, 2 = error), a module name parameter (default null means both DEVICE and INSTRUCTION), an age parameter giving the minimum age of data to purge, and a truncate-table flag. The truncate flag is defaulted through the GMO_CONSTANTS_GRP constant NO and ultimately draws its value from a profile or parameter supplied to the concurrent program.

Tables Accessed

The package acts on ten documented transactional tables, all referenced through APPS synonyms:

Because the package only cleans temporary data, its operations are DELETE or TRUNCATE on these tables. It is not a functional write path and does not modify configuration or master data.

Usage Notes

GMO_PURGE is designed to be scheduled and run by a system administrator, almost always through the Oracle EBS concurrent manager, so that housekeeping occurs without manual SQL. The concurrent-program wrapper for PURGE_ALL is the supported invocation path and accepts the module name, age, and truncate parameters; a DBMS_SCHEDULER or request-set schedule is normally installed to run it nightly or weekly. The lower-level PURGE_DEVICE_DATA and PURGE_INSTRUCTION_DATA entry points are available for targeted cleanup when only one module needs clearing or when a custom concurrent program must limit the scope.

Two operational cautions apply. First, the truncate option, when enabled, bypasses row-level deletes and resets the affected tables entirely; it should only be used when the user is certain that all rows in the selected tables are disposable, since truncated data cannot be rolled back. Second, the age parameter acts as a safety margin — data younger than the specified age is retained, preventing the purge from deleting records still needed by in-flight device or instruction processes. Because the package is classified OTHER and is referenced by no other package, it should not be called from within transactional code paths; it must remain an out-of-band administrative job.