Search Results prg_type

Overview

The IGS_CA_DA_OVD_RULES table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Institutional Global Systems (IGS) module. It functions as a control table that defines rules for overriding system date validations. Its primary role is to manage the conditions under which date-related validations can be bypassed for specific organizational elements, such as academic programs or organizational units. This enables flexible administration of academic calendars and date-sensitive processes. The provided ETRM metadata explicitly notes it is a supplementary view used to simplify forms coding, with a strong warning that direct querying or data alteration is not recommended by Oracle, as its structure may change in future releases.

Key Information Stored

The table's columns store the parameters that define an override rule. The SYS_DATE_TYPE column is a mandatory field identifying the specific seeded system date type (e.g., a key academic calendar date) to which the rule applies. The ELEMENT_CODE column holds the code for the organizational entity (like an Org Unit, Program Type, or Program Version) that is allowed the override, linked to a lookup. The SQL_VAL column contains an optional SQL validation string (up to 2000 characters) to further restrict the override to specific data subsets. The SQL_VAL_OVRD_FLAG and CLOSED_IND columns act as control flags to indicate if the SQL validation should be ignored and if the rule is inactive, respectively. Standard WHO columns (CREATED_BY, CREATION_DATE, etc.) track audit information. A unique primary key index, IGS_CA_DA_OVD_RULE_PK, is defined on the combination of SYS_DATE_TYPE and ELEMENT_CODE.

Common Use Cases and Queries

This table is central to configuring exceptions in academic date enforcement. A common use case is permitting a specific department (ORG) or graduate program (PRG_TYPE) to operate on a different schedule for add/drop deadlines (SYS_DATE_TYPE) than the standard university calendar. Administrators would use forms-based interfaces, which leverage this underlying table, to create and maintain these rules. For diagnostic or reporting purposes, a technical consultant might execute a query to audit all active override rules. A sample query, based on the ETRM-provided text, to list rules for a specific date type would be:

• SELECT sys_date_type, element_code, sql_val, closed_ind FROM apps.igs_ca_da_ovd_rules WHERE sys_date_type = '&DATE_TYPE' AND NVL(closed_ind, 'N') = 'N';

It is critical to query the synonym (APPS.IGS_CA_DA_OVD_RULES) rather than the base IGS schema object. Any direct data manipulation (INSERT, UPDATE, DELETE) should be performed only through official application interfaces to maintain data integrity.

Related Objects

As per the dependency information, the IGS_CA_DA_OVD_RULES table does not reference other objects but is itself referenced. The primary reference is the public synonym APPS.IGS_CA_DA_OVD_RULES, which is the correct access point for all application code and privileged queries. This setup is standard in EBS to provide a layer of abstraction from the underlying schema. The table's data is consumed by forms and likely by PL/SQL logic within the IGS module that evaluates date validations and determines if an override rule is applicable for a given transaction, based on the context of the SYS_DATE_TYPE and the current ELEMENT_CODE.