Search Results sy_purg_mst_crit




Overview
Explore in AI Chat

Overview

The SY_PURG_MST_CRIT table is a core data object within the Oracle Process Manufacturing (OPM) module of Oracle E-Business Suite (EBS), specifically under the GMA (Process Manufacturing Systems) product schema. Its primary role is to support the Purge and Archive functionality, a critical process for managing data lifecycle and optimizing database performance in manufacturing environments. The table acts as a detailed criteria repository, storing the specific parameters and conditions defined by users when setting up a purge or archive run. Each record is logically tied to a master purge definition via a PURGE_ID, enabling the system to execute complex data retention and cleanup operations based on configurable business rules.

Key Information Stored

The table's structure is designed to capture the granular details of purge criteria. The primary key is a composite of PURGE_ID and CRIT_TAG, ensuring unique criteria definitions per purge master. The PURGE_ID column is a foreign key that links the criteria to its parent purge master record in the SY_PURG_MST table. The CRIT_TAG column likely serves as a unique identifier or sequence for multiple criteria lines associated with a single purge ID. A significant column is TEXT_CODE, which is a foreign key to the SY_TEXT_HDR table. This relationship suggests that the actual, potentially lengthy, criteria text or descriptive information is stored in a separate flexible text repository, a common design pattern in EBS for handling large or variable-length descriptive fields. This design separates transactional data from descriptive content.

Common Use Cases and Queries

This table is central to administrative and operational reporting for data management. A common use case involves auditing historical purge criteria to understand what data was removed and under what conditions. Database administrators may query this table to analyze purge configurations before execution. A typical analytical query would join SY_PURG_MST_CRIT to SY_PURG_MST to retrieve the criteria alongside the master purge setup details (like purge name, status, and date). Another frequent pattern involves joining to SY_TEXT_HDR to fetch the full textual description of the criteria. For example: SELECT m.purge_name, c.crit_tag, t.text FROM gma.sy_purg_mst_crit c JOIN gma.sy_purg_mst m ON c.purge_id = m.purge_id LEFT JOIN gma.sy_text_hdr t ON c.text_code = t.text_code WHERE m.purge_status = 'COMPLETED';. This helps in compliance reporting and validating data retention policies.

Related Objects

The SY_PURG_MST_CRIT table exists within a well-defined relationship hierarchy, primarily as a child table. Its documented foreign key relationships are as follows:

  • SY_PURG_MST: This is the parent master table. The relationship is defined by SY_PURG_MST_CRIT.PURGE_ID = SY_PURG_MST.PURGE_ID. Every criteria record must correspond to a valid master purge definition.
  • SY_TEXT_HDR: This table stores the descriptive text for the criteria. The relationship is defined by SY_PURG_MST_CRIT.TEXT_CODE = SY_TEXT_HDR.TEXT_CODE. This link is essential for retrieving the human-readable criteria details.
The table itself is referenced by its primary key constraint, SY_PURG_MST_CRIT_PK, which enforces data integrity on the combination of PURGE_ID and CRIT_TAG.