Search Results igi_gcc_gl_fa_inst_ops




Overview
Explore in AI Chat

Overview

The view APPS.IGI_GCC_GL_FA_INST_OPS is a reporting and inquiry object belonging to the Oracle E-Business Suite product IGI – Public Sector Financials International. Its documented purpose is to display status details of non Multi Org OPSFI (Office of Public Sector Financials International) requirements. In practice, the view exposes the installation and configuration state of the various OPSFI options that a deployment has registered, together with a human-readable description for each option.

Because the object is a view rather than a table, it carries no independent data of its own. Its role is to consolidate configuration/status rows held in the underlying options table and to join them to the descriptive lookup meanings stored in the Oracle EBS lookups infrastructure. This makes it well suited to reporting, diagnostics, and integration scenarios where an administrator or interface needs to confirm which OPSFI options are active, their version level, and their current status. The view is owned by the APPS schema and is documented as VALID in ETRM for the 12.2.2 release set (and is applicable to the 12.1.1/12.2.2 code lines).

The search term "option_name" maps directly to one of this view's exposed columns, reflecting that the object is commonly queried to enumerate OPSFI option names and their associated status metadata.

Underlying Base Objects

The view is defined over two documented referenced base objects:

These two sources are combined with an inner join. The join condition is LUP.LOOKUP_TYPE = 'GCC_DESCRIPTION' AND LUP.LOOKUP_CODE = OPTION_NAME. In other words, each row returned by IGI_GCC_GL_FA_INST_OPTIONS is matched to a lookup of type GCC_DESCRIPTION whose lookup code equals the option's OPTION_NAME. The lookup's MEANING column is projected into the view as DESCRIPTION. Consequently, the view returns only those options for which a matching GCC_DESCRIPTION lookup exists.

Key Columns

  • OPTION_ID — The surrogate identifier for the OPSFI option record from the base options table.
  • OPTION_NAME — The internal name/code of the option; also the value joined against the lookup code to derive the description and the column referenced by the "option_name" search.
  • STATUS_FLAG — The status indicator for the option, expressing whether the requirement is enabled, pending, or otherwise in a given state.
  • VERSION_NUMBER — The version level associated with the option, used to track which release or patch level the configuration reflects.
  • SWITCH_OPTION — The switch option value governing the option's toggling behavior.
  • DESCRIPTION — The derived, user-facing text sourced from IGI_LOOKUPS.MEANING where lookup type equals GCC_DESCRIPTION. This is the column that makes the view readable, since OPTION_NAME is an internal code.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard EBS row audit information inherited from the base options table.

Common Use Cases and Queries

The view is typically used to verify the state of OPSFI options during implementation, support triage, or upgrade validation. A representative query listing all options with readable descriptions is:

  • SELECT option_id, option_name, description, status_flag, version_number, switch_option FROM apps.igi_gcc_gl_fa_inst_ops;

To isolate options in a particular state, filter on the status flag:

  • SELECT option_name, description, status_flag FROM apps.igi_gcc_gl_fa_inst_ops WHERE status_flag = 'Y';

To resolve a single option by its internal name — the scenario most often associated with an "option_name" lookup — constrain the option name:

  • SELECT option_id, option_name, description, version_number FROM apps.igi_gcc_gl_fa_inst_ops WHERE option_name = :p_option_name;

For auditing, the standard audit columns can be selected to determine when configuration changed and by whom:

  • SELECT option_name, last_update_date, last_updated_by FROM apps.igi_gcc_gl_fa_inst_ops ORDER BY last_update_date DESC;

These queries are read-only against a view, so they incur no data modification risk and are safe for reporting, extraction, and integration use.