Search Results entry_region_id




Overview
Explore in AI Chat

Overview

IGS_AD_SS_REGN_ATTRS is an Oracle EBS table belonging to the IGS – Student System product family. According to the ETRM metadata, the table is explicitly flagged as obsolete and "not implemented in this database." Its documented purpose is to store entry region attributes corresponding to a region identifier. In the broader legacy Student System data model, entry regions defined how prospective students entered the system (for example, via a specific admissions channel, test score feed, or external interface), and this table captured the attribute-level configuration layered on top of each region. The obsolete designation indicates that the functionality it supported has been retired or migrated, so the object should be treated as a historical artifact rather than a supported integration point.

The metadata records the primary key as IGS_AD_SS_REGN_ATTRS_PK on ENTRY_REGION_ATTR_ID. Based on the heuristic Data Vault classification mined from the foreign key structure, the table is assessed as satellite-leaning. That is a modeling suggestion: the row identifies an attribute of a parent entry region through a surrogate key, with descriptive content attached to a hub-like entity (IGS_AD_SS_REGIONS), which is characteristic of a satellite construct.

Key Information Stored

  • ENTRY_REGION_ATTR_ID – The surrogate primary key (IGS_AD_SS_REGN_ATTRS_PK) uniquely identifying each attribute row.
  • ENTRY_REGION_ID – The foreign key linking back to IGS_AD_SS_REGIONS; this is the business identifier of the parent entry region. It participates in both unique indexes, confirming it is a business-key candidate.
  • ATTRIBUTE_CD – The code identifying which attribute is being configured for the region. It forms part of unique index IGS_AD_SS_REGN_ATTRS_UK1 together with ENTRY_REGION_ID.
  • DISPLAY_SEQ – The display sequence controlling the ordering in which the attribute appears for the region. It forms part of unique index IGS_AD_SS_REGN_ATTRS_UK2 together with ENTRY_REGION_ID.

The two unique indexes establish the true business keys: a region may have at most one row per attribute code (UK1) and at most one row per display sequence value (UK2). ENTRY_REGION_ATTR_ID is therefore the technical surrogate, while (ENTRY_REGION_ID, ATTRIBUTE_CD) and (ENTRY_REGION_ID, DISPLAY_SEQ) are the meaningful business-key candidates. No other columns appear in the documented metadata, which is consistent with the table's obsolete status.

Common Use Cases and Queries

Because the table is not implemented, no production query against it will return data in a standard EBS 12.1.1 or 12.2.2 instance. Its primary practical use is during historical data analysis, upgrade impact assessment, or when reconstructing the legacy Student System model. A typical pattern joins the attribute rows to their parent region:

  • Retrieve all attributes for a given entry region: SELECT attribute_cd, display_seq FROM igs_ad_ss_regn_attrs WHERE entry_region_id = :region_id ORDER BY display_seq;
  • Resolve the surrogate to its parent region: SELECT a.entry_region_attr_id, a.attribute_cd, r.entry_region_id FROM igs_ad_ss_regn_attrs a, igs_ad_ss_regions r WHERE a.entry_region_id = r.entry_region_id;
  • Detect duplicate attribute configuration using the unique key definitions as a validation template against archived extracts.
  • Locate rows without a valid parent region via an outer join from IGS_AD_SS_REGIONS to this table, useful when auditing orphaned historical data.

Reporting use cases are limited to data-migration audits, pre-upgrade fit-gap analysis, and documentation of deprecated entry-region configuration. No supported concurrent program, form, or API in 12.1.1/12.2.2 is documented as consuming this table.

Related Objects

  • IGS_AD_SS_REGIONS – The parent table; joined via IGS_AD_SS_REGN_ATTRS.ENTRY_REGION_ID → IGS_AD_SS_REGIONS.ENTRY_REGION_ID. This is the single documented foreign key relationship.
  • IGS_AD_SS_REGN_ATTRS_PK / _UK1 / _UK2 – The primary and unique key constraints that govern row identity and enforce region/attribute uniqueness.
  • IGS_AD_SS_* family tables – The surrounding entry-region configuration objects within the Student System model that share the ENTRY_REGION_ID convention and would have been referenced together in legacy logic.
  • Any obsolete Student System views or archived extracts that historically selected entry-region attributes; these should be validated against current releases before reuse.

Given the obsolete and unimplemented status, integrators should not build new dependencies on IGS_AD_SS_REGN_ATTRS and should instead consult the current Student System data model for the supported replacement structures.