Results for “org_alternate_identifier”

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

Overview

IGSFV_ORG_ALTERNATE_IDS is a reporting view belonging to the Oracle IGS Student System product family. As documented in the ETRM metadata, the view is described as an entity that "contains alternate IDs for institutions or organizational unit." It exposes the registration of non-primary identifiers — such as accreditation numbers, government reporting codes, legacy system keys, and external agency identifiers — associated with institutional or organizational units defined within the Student System's organizational hierarchy.

The view is important because organizational structures in the Student System frequently require more than one identifier. While a single primary organization code drives internal referential integrity, downstream reporting and integration routines often must map those records to identifiers issued by external bodies. IGSFV_ORG_ALTERNATE_IDS presents that mapping together with descriptive metadata, effective dating, and preference indicators, in a denormalized and read-only format suitable for reporting.

The metadata notes that the object is part of IGS — Student System (Obsolete), and that it is "Not implemented in this database." For Oracle EBS 12.1.1 and 12.2.2 environments where IGS is not installed, the view will not exist. It is documented here for completeness of the ETRM catalog.

Underlying Base Objects

The view text documents four referenced base objects, joined in a single SELECT with a WITH READ ONLY clause:

• IGS_OR_ORG_ALT_IDS OAI — the primary transactional table of alternate identifiers, holding the structure identifier, alternate ID type, alternate ID value, and start/end dates.
• IGS_OR_ORG_ALT_IDTYP OAT — the alternate ID type definition table, supplying the type description and the institution-level and unit-level preference flags.
• IGS_PE_HZ_PARTIES IHP — the Student System bridge to the Trading Community Architecture party model, linking an organization structure code to a party record.
• HZ_PARTIES HP — the TCA party table, supplying the organization structure name.

Joins are established on ORG_ALTERNATE_ID_TYPE, ORG_STRUCTURE_ID to OSS_ORG_UNIT_CD, and PARTY_ID respectively. No additional base objects are documented in the ETRM metadata.

Key Columns

• ORG_STRUCTURE_IDENTIFIER — the unique key of the institution or organizational unit.
• ORG_ALTERNATE_ID_TYPE — the classification of the alternate identifier; this is the column most directly associated with the search term "org_alternate_id_type".
• ORG_ALTERNATE_IDENTIFIER — the actual alternate ID value assigned to the organization.
• PREF_INST_IND and PREF_UNIT_IND — indicate whether the alternate ID is the preferred identifier at the institution level or the unit level.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — the validity window of the alternate ID assignment.
• ORG_STRUCTURE_NAME — the organization name resolved from HZ_PARTIES.
• ORG_ALTERNATE_ID_TYPE_DESC — the human-readable description of the alternate ID type.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.

Two segments marked with "_LA:" prefixes are descriptive flexfield or lookup-value substitution placeholders resolved at runtime, returning lookup meanings for SYSTEM_ID_TYPE and ORG_STRUCTURE_TYPE.

Common Use Cases and Queries

Typical usage includes reconciling internal organization codes to external agency identifiers, reporting the preferred identifier for an institution, and validating effective dating on alternate ID assignments. A representative query follows:

SELECT ORG_STRUCTURE_IDENTIFIER, ORG_STRUCTURE_NAME, ORG_ALTERNATE_ID_TYPE, ORG_ALTERNATE_ID_TYPE_DESC, ORG_ALTERNATE_IDENTIFIER, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE FROM IGSFV_ORG_ALTERNATE_IDS WHERE ORG_ALTERNATE_ID_TYPE = :p_type AND SYSDATE BETWEEN EFFECTIVE_START_DATE AND NVL(EFFECTIVE_END_DATE, SYSDATE + 1);

Because the view is read-only, it is safe for integration extracts and BI datasets; all maintenance must be performed against the underlying tables.