Search Results request_config_id

Overview

The table IGS_DA_CNFG_REQ_TYP is a core configuration entity within the Oracle E-Business Suite Student System (IGS), specifically for the Degree Audit module in releases 12.1.1 and 12.2.2. As indicated by its description, it stores Degree Audit configurations that define which Run Types are permissible for selection on the student request screen. This table acts as a control point, linking a specific degree audit configuration to the types of audit requests (e.g., "What-If" scenarios, official evaluations) that can be initiated for a student. It is important to note the metadata explicitly labels the IGS product as "Obsolete," indicating this table is part of a legacy codebase that may be superseded in later application versions or cloud offerings.

Key Information Stored

The table's structure centers on linking a configuration to a request type and, for certain types, associated academic program details. The primary identifier is REQUEST_TYPE_ID. The key columns, derived from the primary and unique key definitions and foreign key relationships, are REQUEST_CONFIG_ID, which links to the main configuration header (IGS_DA_CNFG), and REQUEST_TYPE, which classifies the audit. For "What-If" (WIF) scenario configurations, the table references specific academic program and catalog data through the columns WIF_PROGRAM_CODE, WIF_CATALOG_CAL_TYPE, and WIF_CATALOG_CI_SEQ_NUM, which are foreign keys to the IGS_PS_COURSE and IGS_CA_INST_ALL tables, respectively.

Common Use Cases and Queries

The primary use case is administrative setup and validation. A system administrator would use this table to configure which degree audit run types are available for a given audit setup. Common reporting or validation queries would involve joining to related configuration tables to ensure consistency. For example, to list all configured request types for a specific degree audit configuration, a query would join IGS_DA_CNFG_REQ_TYP to IGS_DA_CNFG. To audit "What-If" scenario setups, a query would join to the course and calendar tables via the WIF_ prefixed columns. A typical SQL pattern would be:

• SELECT cfg.CONFIGURATION_NAME, req_typ.REQUEST_TYPE, req_typ.WIF_PROGRAM_CODE FROM IGS_DA_CNFG cfg, IGS_DA_CNFG_REQ_TYP req_typ WHERE cfg.REQUEST_CONFIG_ID = req_typ.REQUEST_CONFIG_ID;

This table is also critical for the application logic that populates the list of available run types when a user initiates a new degree audit request.

Related Objects

IGS_DA_CNFG_REQ_TYP sits at the center of a network of Degree Audit configuration and transaction tables, as evidenced by its foreign key relationships. The documented relationships are as follows:

• Parent Tables:
  • IGS_DA_CNFG (via REQUEST_CONFIG_ID)
  • IGS_CA_INST_ALL (via WIF_CATALOG_CAL_TYPE, WIF_CATALOG_CI_SEQ_NUM)
  • IGS_PS_COURSE (via WIF_PROGRAM_CODE)
• Child Tables (referencing IGS_DA_CNFG_REQ_TYP.REQUEST_TYPE_ID):
  • IGS_DA_CNFG_FTR - Likely stores additional features or rules for the request type.
  • IGS_DA_CNFG_STAT - Likely stores status transitions or rules applicable to the request type.
  • IGS_DA_RQST - The main transactional table for audit requests, linking each request to its configured type.

The metadata also notes a recursive relationship where IGS_DA_CNFG references this table, and a potential duplicate reference from IGS_DA_CNFG_FTR, which should be verified against a specific installation's data model.