Results for “ge_nav_subform”

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

Overview

APPS.IGS_GE_CFG_NAV_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as IGS.IGS_GE_CFG_NAV_V. It belongs to the Oracle Student System (formerly Oracle iLearning/Student Systems) configuration layer, specifically the geographical/enterprise configuration navigation component. The view presents navigation configuration records that drive the push-button navigation displayed on Oracle Forms-based self-service and administrative screens, including the label text that appears on each button. Its status is VALID in both 12.1.1 and 12.2.2.

The view is explicitly documented as a "supplementary view used to simplify forms coding." Oracle's own metadata carries a warning that querying or altering data through this view is not recommended, as its definition may change dramatically between minor or major releases. Consequently, it should be treated as an internal forms-support object rather than a stable integration interface, and any external reporting use should be weighed against that caveat.

Underlying Base Objects

The view is defined over the base table APPS.IGS_GE_CFG_NAV, which stores the navigation configuration rows (responsibility, form code, sequence, and subform routing). It also references APPS.IGS_LOOKUP_VALUES to resolve the subform meaning (SUBFORM_MEANING) from lookup codes, following the standard Oracle lookup pattern keyed on the subform code.

The view itself is not referenced by any other database object, confirming its position as a leaf-level forms convenience layer rather than a dependency for downstream PL/SQL or other views. Because the documentation lists IGS_GE_CFG_NAV and IGS_LOOKUP_VALUES as the referenced objects, the join effectively denormalises the navigation configuration with its descriptive lookup text, so that forms code can read both the routing information and the human-readable navigation label from a single source.

Key Columns

• ROW_ID (ROWID): Row identifier for the record being retrieved; useful for direct row addressing but not portable for joins across refreshes.
• RESPONSIBILITY_ID (NUMBER): The responsibility against which the navigation configuration applies, allowing different button layouts per responsibility.
• FORM_CODE (VARCHAR2, 30): The form to which the navigation configuration belongs.
• SEQ_NUMBER (NUMBER): The sequence number controlling the ordering of navigation entries.
• SUBFORM_CODE (VARCHAR2, 30): The subform code being navigated to.
• SUBFORM_MEANING (VARCHAR2, 80): The descriptive name of the subform, resolved via IGS_LOOKUP_VALUES.
• BUT_LABEL (VARCHAR2, 30): The navigation push-button label — the caption rendered on the button. This is the column of primary interest for label-related searches.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): Audit trail attributes populated by the standard Oracle EBS WHO columns.

Common Use Cases and Queries

The principal use case is auditing or troubleshooting button labels and navigation ordering on a form for a given responsibility. A typical query retrieves the label set for a responsibility and form, ordered by sequence:

• Retrieve all navigation labels for a responsibility: SELECT responsibility_id, form_code, seq_number, subform_code, subform_meaning, but_label FROM apps.igs_ge_cfg_nav_v WHERE responsibility_id = :p_resp_id ORDER BY seq_number;
• Locate entries by button label: SELECT form_code, subform_code, but_label FROM apps.igs_ge_cfg_nav_v WHERE but_label = :p_label;
• List navigation for a specific form: SELECT seq_number, subform_code, subform_meaning, but_label FROM apps.igs_ge_cfg_nav_v WHERE form_code = :p_form ORDER BY seq_number;
• Join to responsibility for context: SELECT r.responsibility_name, v.form_code, v.seq_number, v.but_label FROM apps.igs_ge_cfg_nav_v v, apps.fnd_responsibility_vl r WHERE v.responsibility_id = r.responsibility_id ORDER BY r.responsibility_name, v.seq_number;

Because the view is documented as forms-support only, Oracle recommends reading the underlying base table directly for any configuration-change or integration requirement, and treating but_label values as presentation metadata rather than business data.