Search Results id_type_description

Overview

APPS.IGS_OR_ORG_ALT_IDTYP_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under the FND Design Data reference IGS.IGS_OR_ORG_ALT_IDTYP_V. It belongs to the Student Systems / institutional registry (IGS) product family and exposes the set of alternate identification types that can be assigned to organizations and organization units, together with their descriptive text, flags and audit columns. Its principal purpose, as stated in the ETRM documentation, is to simplify forms coding; Oracle explicitly warns that the view should not be used to query or alter data directly because its definition may change dramatically in subsequent minor or major releases.

In practice the view is an internal implementation object rather than a supported public interface. The object is listed as VALID in both Oracle EBS 12.1.1 and 12.2.2, and its design metadata is identical across those releases, indicating a stable structure throughout the 12.x lifecycle. Users searching for the term "id_type_description" will most often require the ID_TYPE_DESCRIPTION column, which returns the translatable name of each alternate identification type — for example a value used to label an organization alias such as a tax registration number, a statutory body code or an internal reference identifier.

Underlying Base Objects

The ETRM dependency section documents that APPS.IGS_OR_ORG_ALT_IDTYP_V references two base objects within the APPS schema: IGS_OR_ORG_ALT_IDTYP and IGS_LOOKUP_VALUES. The former is the transactional/setup table that stores the enabled alternate ID types for organizations, while the latter is the standard Oracle lookup view used to resolve the descriptive text and meaning associated with lookup-coded values. The view therefore joins the persistent organization alternate ID type records against the lookup definitions that supply the human-readable descriptions exposed as ID_TYPE_DESCRIPTION and SYSTEM_ID_TYPE_DESC.

The view is itself referenced by other APPS objects, notably IGF_SL_UPLOAD_XML and IGS_HE_IMPORT_DATA. This means the view participates in XML upload processing for student loans (IGF) and in higher-education data import routines, so changes to the view can propagate into those dependent code units. Any modification to the underlying lookup values or to IGS_OR_ORG_ALT_IDTYP will be reflected immediately through the view.

Key Columns

• ROW_ID — ROWID pseudocolumn identifying the underlying row, useful for uniqueness but not stable across reorganization.
• ORG_ALTERNATE_ID_TYPE — the code of the alternate identification type assigned to the organization.
• ID_TYPE_DESCRIPTION — the descriptive name of the alternate ID type; this is the column most commonly sought when users search for "id_type_description".
• INST_FLAG / UNIT_FLAG — indicate whether the ID type may be used for institutions and/or organization units respectively.
• CLOSE_IND — closure indicator showing whether the ID type has been retired from use.
• SYSTEM_ID_TYPE / SYSTEM_ID_TYPE_DESC — the mapped system-level identification type and its description, linking institutional definitions to system-wide codes.
• PREF_INST_IND / PREF_UNIT_IND — flags indicating whether the ID type is the preferred alternate ID type for an institution or for an organization unit.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical reporting requirements involve resolving the description of an alternate ID type held against an organization, or listing all active ID types available for institutions. The simplest query is:

SELECT ORG_ALTERNATE_ID_TYPE, ID_TYPE_DESCRIPTION, INST_FLAG, UNIT_FLAG, PREF_INST_IND, PREF_UNIT_IND, CLOSE_IND FROM APPS.IGS_OR_ORG_ALT_IDTYP_V WHERE CLOSE_IND = 'N' ORDER BY ID_TYPE_DESCRIPTION;

For integration work, developers frequently join the view to organization tables on ORG_ALTERNATE_ID_TYPE to translate stored codes into descriptions, or filter on SYSTEM_ID_TYPE when reconciling institutional setup against system-level definitions. Because Oracle does not support querying this view directly, such usage should be treated as read-only and, where external integration is required, replaced by a query against the underlying tables IGS_OR_ORG_ALT_IDTYP and IGS_LOOKUP_VALUES so that the dependency is explicit and insulated from view definition changes in future releases.