Results for “igs_ge_cfg_form”

30 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_GE_CFG_FORM is a configuration table in the IGS (Student System) product schema of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. The table stores form-level configuration detail records that govern how Oracle Forms-based pages behave when launched within the context of a specific Oracle EBS responsibility. Each row associates a responsibility with a form and captures presentation or runtime attributes — most notably whether the form is rendered in query-only mode. Because IGS_GE_CFG_FORM acts as the parent of both navigation-level and tab-level configuration tables, it defines the top of a small three-level hierarchy used by the Student System to customize the user interface delivered to different administrative user communities.

The table is owned by the IGS schema and is documented as VALID in ETRM. A heuristic Data Vault classification derived from the foreign-key topology treats this object as hub-leaning: it holds the unique business key of the configuration hierarchy and is referenced by downstream satellite-style tables. This classification is offered as a modeling suggestion rather than a physical design statement; in the delivered EBS schema, IGS_GE_CFG_FORM is a conventional relational table with a composite primary key and standard WHO audit columns.

Key Information Stored

The table has eight documented columns. The most significant are:

  • RESPONSIBILITY_ID — Identifies the Oracle EBS responsibility for which the form configuration applies. Together with FORM_CODE it forms the composite unique business key.
  • FORM_CODE — The identifier of the Oracle Forms module (form) whose configuration is being defined. This is the second component of the composite key.
  • QUERY_ONLY_IND — A flag indicating whether the form is presented in query-only mode, restricting the user from inserting, updating, or deleting records through that responsibility.
  • CREATED_BY, CREATION_DATE — Standard WHO audit columns recording the user and timestamp of row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing the most recent modification, the responsible user, and the login session context.

The primary key, IGS_GE_CFG_FORM_PK, is a composite key over (RESPONSIBILITY_ID, FORM_CODE). Because that same unique index supplies the business identity of the row, there is no separate surrogate key column; the composite PK serves simultaneously as the business-key candidate. No additional unique indexes are documented for this table.

Common Use Cases and Queries

Configuration administrators and support analysts query this table to determine how a given responsibility behaves when a Student System form is opened. Typical scenarios include diagnosing why a user cannot enter data on a form, auditing which responsibilities permit only query access, and comparing configuration differences between responsibilities after a clone or upgrade.

SELECT responsibility_id,
       form_code,
       query_only_ind
  FROM igs.igs_ge_cfg_form
 WHERE responsibility_id = :p_resp_id;

A related pattern lists the full configuration footprint of a responsibility by joining downward to the navigation and tab configuration tables:

SELECT f.form_code,
       f.query_only_ind,
       n.navigation_code,
       t.tab_code
  FROM igs.igs_ge_cfg_form f,
       igs.igs_ge_cfg_nav  n,
       igs.igs_ge_cfg_tab  t
 WHERE f.responsibility_id = :p_resp_id
   AND n.responsibility_id = f.responsibility_id
   AND n.form_code         = f.form_code
   AND t.responsibility_id = f.responsibility_id
   AND t.form_code         = f.form_code;

Reporting uses include generating a matrix of responsibilities versus query-only forms for access reviews, and reconciling configuration rows after a responsibility is copied between environments. Because the table is small and keyed on responsibility plus form, such queries are inexpensive and can be run directly against the production schema.

Related Objects

IGS_GE_CFG_FORM is referenced by two dependent configuration tables through their composite foreign keys, both of which carry the (RESPONSIBILITY_ID, FORM_CODE) pair:

  • IGS_GE_CFG_NAV — Stores navigation-level configuration for the same responsibility and form combination.
  • IGS_GE_CFG_TAB — Stores tab-level configuration entries that further refine how the form is presented.

Together these three tables form the delivered hierarchy: a form is configured for a responsibility, and that configuration is qualified by navigation and tab settings. Oracle Forms-based functionality in the Student System reads this hierarchy at runtime, so any change to IGS_GE_CFG_FORM or its children should be validated through the corresponding IGS responsibility before being promoted to other instances.