Results for “form_code”

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

Overview

IGS_GE_CFG_NAV_V is a configuration view belonging to the IGS (Student System) product family. Its documented purpose is to expose form navigation configuration data — the metadata that governs how forms are sequenced and presented within navigable form flows in the legacy Oracle Student System. The view joins the navigation configuration table IGS_GE_CFG_NAV to the lookup values view IGS_LOOKUP_VALUES so that the stored subform code is returned alongside its human-readable meaning. In Oracle EBS 12.1.1 and 12.2.2, this view is classified as obsolete; the ETRM metadata records it as "Not implemented in this database," meaning the object may not exist in a given instance even though its definition remains documented.

Because navigation configuration is reference data rather than transactional data, the view's role is limited to administration, diagnostics, and reporting on how application forms were wired together. It carries no direct reporting or integration responsibility in a supported EBS implementation, but it retains value for audit and migration exercises where legacy IGS configuration must be understood or mapped.

Underlying Base Objects

The documented base object is the table IGS_GE_CFG_NAV, aliased T in the view text. Two columns are sourced from a second object, IGS_LOOKUP_VALUES (aliased L1): the join resolves T.SUBFORM_CODE against L1.LOOKUP_CODE where L1.LOOKUP_TYPE = 'GE_NAV_SUBFORM'. This lookup constrainment ensures that only subform codes registered under the GE_NAV_SUBFORM lookup type are decorated with a meaning. The join is written in legacy Oracle outer-join syntax rather than ANSI LEFT JOIN, consistent with the code base of the era. Because the view selects T.ROWID as ROW_ID, the driving table is row-addressable; however, the presence of a join means the view is not inherently updatable without an INSTEAD OF trigger. No other base objects are documented.

Key Columns

• ROW_ID — the ROWID of the underlying IGS_GE_CFG_NAV row, useful for direct row identification and troubleshooting.
• RESPONSIBILITY_ID — identifies the EBS responsibility to which the navigation configuration applies, scoping each configuration set to a user security context.
• FORM_CODE — the form identifier, expressed as the EBS form_code (the FND_FORM.FORM_NAME style key) that the navigation entry targets. This is the column most frequently used to filter the view.
• SEQ_NUMBER — the ordering position of the entry within the navigation sequence.
• SUBFORM_CODE — the subform identifier used for nested navigation; resolved to its lookup meaning via the join.
• SUBFORM_MEANING — the descriptive meaning of SUBFORM_CODE from IGS_LOOKUP_VALUES; null when no matching lookup value exists.
• BUT_LABEL — the label displayed on the navigation button or control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns for audit tracking.

Common Use Cases and Queries

Typical usage centers on auditing or documenting navigation configuration, particularly when locating which responsibilities reference a given form. A representative query filtering by form code follows:

• SELECT form_code, responsibility_id, seq_number, subform_meaning, but_label FROM igs_ge_cfg_nav_v WHERE form_code = :form_code ORDER BY responsibility_id, seq_number;
• SELECT responsibility_id, form_code, but_label FROM igs_ge_cfg_nav_v ORDER BY responsibility_id, form_code, seq_number;
• SELECT form_code, COUNT(*) FROM igs_ge_cfg_nav_v GROUP BY form_code HAVING COUNT(*) > 1;

Where the object is not implemented, these queries raise ORA-00942: table or view does not exist. In such instances the same columns can be retrieved directly from IGS_GE_CFG_NAV where that table is present, replicating the lookup join manually against FND_LOOKUP_VALUES or IGS_LOOKUP_VALUES.