Results for “form_code”

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

Overview

IGS_GE_CFG_NAV is a configuration table owned by the IGS (Student System) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the form navigation configurations that govern how Oracle Forms-based pages within the Student System are presented and sequenced for a given responsibility. Each row associates a responsibility with a form and a specific subform tab or block, allowing the application to control tab visibility, ordering, and button labeling without code changes.

The table participates in the broader IGS configuration framework, which lets institutions tailor the Student System user interface to institutional business processes. From a heuristic Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification, because the table carries descriptive, context-dependent attributes (such as sequence and label) that qualify a parent configuration entity rather than acting as an independent hub or a many-to-many link.

Key Information Stored

The table contains ten documented columns, of which the following are the most significant for interpretation and querying:

• RESPONSIBILITY_ID — Identifies the Oracle EBS responsibility for which the navigation configuration applies. This is the leading column of both unique indexes and the primary foreign key reference.
• FORM_CODE — The internal code of the target Oracle Forms module whose navigation is being configured.
• SUBFORM_CODE — Identifies the specific subform, tab, or block within the form. This is the column most commonly searched, since it pinpoints the exact UI element being configured.
• SEQ_NUMBER — Controls the display order of the subform within the form, enabling institutions to reorder tabs.
• BUT_LABEL — The button or tab label text displayed to the end user, supporting localization and terminology alignment.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created or last modified each configuration row and when.

The surrogate-style primary key is defined by IGS_GE_CFG_NAV_PK over (RESPONSIBILITY_ID, FORM_CODE, SUBFORM_CODE). A second unique index, IGS_GE_CFG_NAV_U1 over (RESPONSIBILITY_ID, FORM_CODE, SEQ_NUMBER), enforces that a given form cannot assign the same sequence number twice under one responsibility. Both indexes therefore serve as business-key candidates, guaranteeing uniqueness of the configuration set as well as of the ordering scheme.

Common Use Cases and Queries

Typical usage centers on auditing and troubleshooting navigation behavior. Administrators query this table to determine which tabs appear for a responsibility, in what order, and under what label. A common pattern retrieves the ordered navigation for one responsibility and form:

• SELECT subform_code, seq_number, but_label FROM igs.igs_ge_cfg_nav WHERE responsibility_id = :p_resp AND form_code = :p_form ORDER BY seq_number;
• Locating all responsibilities where a specific subform is enabled: SELECT responsibility_id, form_code, seq_number FROM igs.igs_ge_cfg_nav WHERE subform_code = :p_subform;
• Reporting gaps or duplicates in the configured sequence by grouping on responsibility_id and form_code and inspecting SEQ_NUMBER values.
• Comparing configuration across environments (for example, development versus production) by joining on the primary-key columns to detect drift in labels or ordering.

Because the table is configuration metadata rather than transactional data, reporting queries are typically low-volume and are frequently embedded in responsibility setup validation scripts or migration checks.

Related Objects

The documented foreign-key relationship links this table to the IGS_GE_CFG_FORM configuration table, joined on RESPONSIBILITY_ID and FORM_CODE. This parent table defines the forms available for navigation, while IGS_GE_CFG_NAV refines that definition at the subform level. Practitioners commonly query the two together to obtain a complete picture of form and tab configuration for a responsibility. Additional dependencies may exist through the IGS_GE_CFG_FORM hierarchy and standard EBS responsibility definitions (FND_RESPONSIBILITY), which provide the RESPONSIBILITY_ID values referenced here. No additional foreign keys are documented in the ETRM metadata, so the relationship set should be treated as bounded by the IGS_GE_CFG_FORM parent and the responsibility definition it depends upon.