Search Results igs_or_org_alt_ids_v




Overview
Explore in AI Chat

Overview

The view APPS.IGS_OR_ORG_ALT_IDS_V is a reporting and inquiry object within the Oracle E-Business Suite Student System (IGS) product family. It presents alternate identification data assigned to organizations and organizational structures, joining each identifier to its controlling identifier type so that a human-readable description is returned alongside the stored code. Organizations in the Student System frequently require multiple concurrent identifiers — statutory registration numbers, external agency codes, legacy migration keys, accreditation references, and similar values — and this view provides a single denormalized access point for that information without requiring the caller to resolve the type lookup explicitly.

The object is owned by the APPS schema and carries a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, it stores no data of its own; it is a read-only projection intended for queries, reports, and integration extracts. The legal notice accompanying the definition confirms that the underlying structures are Oracle proprietary and confidential.

Underlying Base Objects

The view is defined over two IGS base tables:

  • IGS_OR_ORG_ALT_IDS (aliased OLI) — the transaction table holding the actual alternate identifier values for each organizational structure record, including validity dates and standard WHO audit columns.
  • IGS_OR_ORG_ALT_IDTYP (aliased OLT) — the identifier type reference table, supplying the descriptive text for each alternate ID type.

The two tables are equijoined on ORG_ALTERNATE_ID_TYPE. This is an inner join, so an alternate ID row is returned only when a matching identifier type exists in the reference table. The view selects OLI.ROWID as ROW_ID, which preserves a row-level handle to the underlying IGS_OR_ORG_ALT_IDS record — useful where a tool or concurrent program requires an addressable row reference. Because the ETRM metadata documents no separate base objects beyond these two tables, the view is a straightforward two-table join with no aggregation or derived logic.

Key Columns

Common Use Cases and Queries

Typical uses include institutional reporting on external registration identifiers, data migration reconciliation, and integration extracts that must publish alternate organization codes with their descriptive type labels. Effective-dating filters using START_DATE and END_DATE allow point-in-time reporting.

Retrieve all alternate IDs for a given organization:

SELECT org_structure_id, org_alternate_id_type, id_type_description,
       org_alternate_id, start_date, end_date
FROM   apps.igs_or_org_alt_ids_v
WHERE  org_structure_id = :p_org_structure_id
ORDER BY org_alternate_id_type;

Identify currently active identifiers only:

SELECT org_structure_id, id_type_description, org_alternate_id
FROM   apps.igs_or_org_alt_ids_v
WHERE  TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));

Audit recently modified records:

SELECT org_structure_id, org_alternate_id, last_update_date, last_updated_by
FROM   apps.igs_or_org_alt_ids_v
WHERE  last_update_date >= TRUNC(SYSDATE) - 30;