Results for “run_date”

2 results




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

Overview

IC_PURG_PRM is a GMI (Process Manufacturing Inventory) table that stores inventory purge parameters in Oracle E-Business Suite 12.1.1 and 12.2.2. The table holds the selection criteria used by the inventory purge process to determine which inventory transaction and document records qualify for archival or deletion. Because the purge process is destructive and irreversible, IC_PURG_PRM serves as the governing control record: each row defines a named, versioned set of criteria that administrators define, review, and execute against the transactional inventory tables.

The object resides in the GMI schema (owner GMI) and is documented as VALID in ETRM. Its primary key, IC_PURG_PRM_PK, is a composite of CRITERIA_NO and VERSION_NO, which allows a single purge criteria definition to be maintained across multiple versions without losing prior definitions. Under the heuristic Data Vault classification mined from the foreign key structure, IC_PURG_PRM is satellite-leaning. This suggests that the table is best modeled as a descriptive satellite attached to the inventory class business key, with IC_INVN_CLS acting as the referenced hub or parent. The VERSION_NO column reinforces this pattern by providing change-over-time semantics for each criteria definition.

Key Information Stored

The table contains 44 documented columns. The most significant are the following:

The surrogate primary key is the composite (CRITERIA_NO, VERSION_NO) exposed through IC_PURG_PRM_PK. No separate business-key unique index beyond this PK is documented, so CRITERIA_ID functions as a descriptive business identifier rather than a uniquely enforced key.

Common Use Cases and Queries

Typical scenarios include auditing what purge criteria are defined before executing a purge, reporting purge activity volumes, and investigating whether a specific inventory class or item range has an active criteria set. A common pattern joins the criteria row to its inventory class and inspects the range and delta columns:

  • List all active criteria: SELECT criteria_no, version_no, criteria_id, table_name, in_use FROM ic_purg_prm WHERE NVL(delete_mark,0) = 0;
  • Join to inventory class: SELECT p.criteria_no, p.inv_class, c.* FROM ic_purg_prm p, ic_invn_cls c WHERE p.inv_class = c.inv_class;
  • Review purge results: SELECT criteria_no, version_no, run_date, moved_rowcount, deleted_rowcount, zero_rowcount, negbal_rowcount FROM ic_purg_prm ORDER BY run_date DESC;
  • Find criteria scoped to a date window: SELECT * FROM ic_purg_prm WHERE docdelta_today IS NOT NULL OR transdelta_today IS NOT NULL;

Because the table is single-purpose configuration data, reporting is typically narrow: administrators extract criteria definitions, and DBAs reconcile historical purge statistics across versions.

Related Objects

The documented foreign key relationship is the anchor for related objects:

  • IC_INVN_CLS — referenced through IC_PURG_PRM.INV_CLASS; provides the inventory class definition for each criteria set.
  • IC_PURG_PRM_PK — the composite unique index on (CRITERIA_NO, VERSION_NO) enforcing row uniqueness.
  • Transactional inventory tables targeted by TABLE_NAME and OBJECT_CODE, which are selected for purge based on the criteria stored here.
  • Audit and concurrency columns interact with standard EBS user and login tables via CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN references.
  • GMI process manufacturing inventory transaction tables that consume PURGE_PRECISION, BACKUP_TYPE, and PROCESS_IND settings during execution.

Together these relationships position IC_PURG_PRM as a satellite configuration object in the GMI inventory domain, with IC_INVN_CLS as its principal parent.