Results for “region_cd”

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

Overview

IGS_OR_LOC_REGION is a table within the IGS (Student System) product schema of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. As documented in the ETRM metadata, the table "Stores the Region Information for a Location." It functions as an intersection entity that associates one or more geographic regions with a given location record, allowing a location to be qualified by the regions in which it operates or is situated. Within the IGS module this supports location-driven processing for academic and administrative functions that depend on regional classification.

The mined Data Vault classification places this object as satellite-leaning. In Data Vault modeling terms, this suggests the table behaves as a descriptive satellite that hangs off a parent hub or link (the location entity), carrying the qualifying region attribute rather than introducing a new independent business entity. Modelers should treat LOCATION_CD as the driving attribute and REGION_CD as the descriptive payload of the association.

Key Information Stored

The documented physical schema for 12.1.1 shows seven columns, with the primary key defined by the unique index IGS_OR_LOC_REGION_PK over the pair (LOCATION_CD, REGION_CD).

• LOCATION_CD — The location identifier. This is both a business-key component of the unique index and the foreign key column referencing IGS_AD_LOCATION_ALL.
• REGION_CD — The region identifier, forming the second business-key component of the unique index.
• CREATED_BY — Standard audit column recording the user who inserted the row.
• CREATION_DATE — Standard audit column recording the insertion timestamp.
• LAST_UPDATED_BY — Standard audit column recording the user who last modified the row.
• LAST_UPDATE_DATE — Standard audit column recording the modification timestamp.
• LAST_UPDATE_LOGIN — Standard audit column capturing the login/session that performed the update.

Because the primary key is a composite of two natural business attributes, the table carries no independent surrogate key column. The (LOCATION_CD, REGION_CD) combination itself is the business key and enforces uniqueness of each location-to-region pairing.

Common Use Cases and Queries

Typical reporting retrieves all regions associated with a location, or finds all locations belonging to a region. A common pattern joins this table to its parent location entity:

• List regions for a location: SELECT REGION_CD FROM IGS_OR_LOC_REGION WHERE LOCATION_CD = :p_location;
• List locations for a region: SELECT LOCATION_CD FROM IGS_OR_LOC_REGION WHERE REGION_CD = :p_region;
• Enrich a location report with region detail: join IGS_AD_LOCATION_ALL to IGS_OR_LOC_REGION on LOCATION_CD.
• Audit change tracking: query by LAST_UPDATE_DATE and LAST_UPDATED_BY to reconcile recent maintenance.

Because the table is narrow and purely associative, it is well suited to regional segmentation reports and validation of location-to-region coverage.

Related Objects

The documented foreign key relationship anchors this table to the location master:

• IGS_AD_LOCATION_ALL — Referenced by IGS_OR_LOC_REGION.LOCATION_CD; the parent location entity supplying descriptive location attributes.
• IGS_OR_LOC_REGION_PK — The unique index enforcing the composite business key on (LOCATION_CD, REGION_CD).

Downstream reporting layers and IGS location-region queries depend on this table, joining through LOCATION_CD and REGION_CD to the respective master data.