Search Results igs_ge_cfg_form




Overview
Explore in AI Chat

Overview

The IGS_GE_CFG_FORM table is a core configuration entity within the now-obsolete Oracle Student System (IGS) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It served as a master repository for storing form-level configuration detail records. Its primary role was to define and manage the specific forms that were accessible and configurable within a given application responsibility, acting as a central reference point for the user interface's navigational and structural setup. The table's design, using a composite primary key of RESPONSIBILITY_ID and FORM_CODE, enforces a model where form configurations are explicitly scoped to a particular responsibility, supporting multi-org and role-based access control within the student system.

Key Information Stored

The table's structure is defined by its primary key columns, which are the most critical for understanding its data model. The RESPONSIBILITY_ID column stores the unique identifier for an EBS application responsibility, effectively grouping forms by a user's functional role. The FORM_CODE column holds the identifier for a specific application form or page within the system. While the provided ETRM metadata does not list non-key columns, tables of this nature in EBS configuration schemas typically include descriptive fields (e.g., FORM_NAME), enabled flags, sequencing information, and creation/modification audit columns. The composite key ensures that a given form can have distinct configuration records under different responsibilities.

Common Use Cases and Queries

A primary use case for this table was administrative reporting and auditing of form-to-responsibility assignments within the Student System. System administrators could query it to verify which forms were configured for a specific role or to identify all responsibilities that had access to a particular form. Common SQL queries would involve joins with the FND_RESPONSIBILITY_VL view to get responsibility names. For instance, a query to list all forms configured for a responsibility named 'IGS Admissions User' would resemble:

SELECT f.form_code
FROM igs_ge_cfg_form f, fnd_responsibility_vl r
WHERE f.responsibility_id = r.responsibility_id
AND r.responsibility_name = 'IGS Admissions User';

Another critical use case was as a parent record in data integrity validation, ensuring that navigation and tab configuration records (in related tables) referenced valid form-responsibility pairs.

Related Objects

The IGS_GE_CFG_FORM table sits at the center of a configuration hierarchy, as evidenced by its documented foreign key relationships. Two key child tables reference it, inheriting its composite primary key to maintain referential integrity:

  • IGS_GE_CFG_NAV: References IGS_GE_CFG_FORM via the columns IGS_GE_CFG_NAV.RESPONSIBILITY_ID and IGS_GE_CFG_NAV.FORM_CODE. This table likely stored navigational paths or menu entries specific to a configured form.
  • IGS_GE_CFG_TAB: References IGS_GE_CFG_FORM via the columns IGS_GE_CFG_TAB.RESPONSIBILITY_ID and IGS_GE_CFG_TAB.FORM_CODE. This table was presumably used to configure the tabs or regions within a specific form for a given responsibility.

These relationships create a dependency chain: a record must exist in IGS_GE_CFG_FORM for a given responsibility and form before corresponding navigation or tab configuration details can be established in the related tables.