Search Results sy_purg_def_crit




Overview
Explore in AI Chat

Overview

The SY_PURG_DEF_CRIT table is a core data definition object within the Process Manufacturing Systems (GMA) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a repository for purge criteria tags, which are essential configuration elements for the system's data archival and purging processes. The table's primary role is to store the logical rules and conditions that determine which historical rows from application tables are eligible for archiving to a separate history table and subsequent removal (purging) from the operational table. This mechanism is critical for managing database growth and maintaining system performance in Process Manufacturing environments where transactional data volume can be substantial.

Key Information Stored

The table's structure is designed to link purge definitions with specific criteria. Based on the provided metadata, the primary key is a composite of two columns: PURGE_TYPE and CRIT_TAG. The PURGE_TYPE column associates the criteria with a specific purge definition stored in the related SY_PURG_DEF table. The CRIT_TAG column stores a unique identifier for the specific condition or rule. A significant column is TEXT_CODE, which serves as a foreign key to the SY_TEXT_HDR table. This relationship indicates that the detailed, potentially multi-language description or the actual SQL logic fragment for the criteria is stored in the generic text repository (SY_TEXT_HDR and SY_TEXT_DTL tables), a common pattern in Oracle EBS for managing translatable or lengthy text.

Common Use Cases and Queries

The primary use case involves administering and reviewing the configuration of data purge rules for Process Manufacturing entities. Database administrators and functional implementers query this table to understand what purge criteria are defined for a given purge process. A common query would join SY_PURG_DEF_CRIT to SY_PURG_DEF to list all criteria for a specific purge type, and further to SY_TEXT_HDR to retrieve the descriptive meaning of each CRIT_TAG. For example:

  • SELECT pdc.purge_type, pdc.crit_tag, sth.text
    FROM gma.sy_purg_def_crit pdc,
    gma.sy_purg_def pd,
    gma.sy_text_hdr sth
    WHERE pdc.purge_type = pd.purge_type
    AND pdc.text_code = sth.text_code
    AND pd.table_name = '<APPLICATION_TABLE_NAME>';

This table is typically accessed by the proprietary GMA purge engine during scheduled purge executions, not directly by end-users in daily operations.

Related Objects

SY_PURG_DEF_CRIT maintains documented foreign key relationships with two key tables in the GMA schema, forming the core of the purge definition framework.

  • SY_PURG_DEF: This is the parent definition table. The foreign key from SY_PURG_DEF_CRIT.PURGE_TYPE references SY_PURG_DEF.PURGE_TYPE. This relationship ties a specific criteria tag to its overarching purge process definition, which includes the target application table names.
  • SY_TEXT_HDR: This generic text repository stores the descriptive content. The foreign key from SY_PURG_DEF_CRIT.TEXT_CODE references SY_TEXT_HDR.TEXT_CODE. This design centralizes text management and supports multilingual descriptions for the purge criteria.