Results for “location_cd”

50+ results




Overview
Explore in AI Chat

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

Overview

IGS_OR_UNIT_LOC is a table in the IGS (Student System) product schema of Oracle E-Business Suite, present and valid in releases 12.1.1 and 12.2.2. The entity describes the intersection between an organizational unit and a location, effectively modeling the assignment or association of a physical or logical location to an organizational unit within the institution. In the Oracle Student System data model, organizational units represent academic or administrative structures, while locations represent campuses, buildings, or other physical sites. This table therefore acts as the associative bridge that records which locations are valid or active for a given organizational unit and from which point in time that association applies.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is satellite-leaning. This suggests that the table behaves primarily as a descriptive association that carries contextual attributes and validity dates around a business relationship, rather than as a pure hub of business keys or a standalone link. The inclusion of a start date in the primary key reinforces this temporal, effectivity-oriented character.

Key Information Stored

The documented physical schema for IGS_OR_UNIT_LOC contains eight columns. The most significant are the three that constitute the composite primary key, IGS_OR_UNIT_LOC_PK, which also corresponds to the unique index IGS_OR_UNIT_LOC_U1 (ORG_UNIT_CD, START_DT, LOCATION_CD):

  • ORG_UNIT_CD — the organization unit code identifying the academic or administrative unit in the association.
  • START_DT — the effective start date of the association, providing the temporal dimension of the relationship.
  • LOCATION_CD — the location code identifying the associated location; this column also carries a foreign key to IGS_AD_LOCATION_ALL.

Together these three columns form the business-key candidate, meaning no two records may exist for the same organizational unit, start date, and location combination. The remaining documented columns are standard Oracle EBS audit/WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — which capture row-level change tracking and user accountability. No separate surrogate key column is documented; the composite business key itself serves as the primary key.

Common Use Cases and Queries

The principal use case is reporting and validation of organizational unit to location assignments. Typical scenarios include identifying all locations associated with a given organizational unit, determining which organizational unit owns a location as of a specific date, and driving location-based access or scheduling logic.

A representative query retrieves current associations for an organization unit:

  • SELECT org_unit_cd, location_cd, start_dt FROM igs_or_unit_loc WHERE org_unit_cd = :p_org_unit_cd ORDER BY start_dt DESC;
  • SELECT u.org_unit_cd, u.location_cd, l.description FROM igs_or_unit_loc u, igs_ad_location_all l WHERE u.location_cd = l.location_cd AND u.start_dt = (SELECT MAX(start_dt) FROM igs_or_unit_loc WHERE org_unit_cd = u.org_unit_cd AND location_cd = u.location_cd);

Because START_DT participates in the primary key, historical and future-dated associations can coexist, supporting point-in-time reporting and effectivity analysis.

Related Objects

The most significant related object is IGS_AD_LOCATION_ALL, referenced by the LOCATION_CD foreign key, which supplies the descriptive detail (name, address, status) for each location. Beyond this documented relationship, other objects in the Student System that reference organizational units and locations — such as organizational unit definition tables and scheduling or enrollment entities that consume unit-location context — depend indirectly on this intersection. The composite primary key and unique index IGS_OR_UNIT_LOC_U1 enforce integrity across the ORG_UNIT_CD, START_DT, and LOCATION_CD combination, ensuring consistent associations throughout the IGS data model.