Search Results igs_ad_ss_regions

Overview

IGS_AD_SS_REGIONS is a table within the Oracle E-Business Suite Student System (IGS) product family, which supports admissions, recruitment, and applicant tracking functions in higher-education implementations. The ETRM metadata explicitly classifies this object as an obsolete table, and it is documented as "Not implemented in this database." Its stated purpose is to store entry regions corresponding to an entry status identifier — in other words, it associated a region code with a particular entry status value used during the admissions or applicant-entry process.

Because the table is obsolete, it does not represent a currently functional data object in EBS 12.1.1 or 12.2.2. The presence of a primary key, a unique key, and foreign key relationships in the metadata indicates that at some point the object was part of a normalized admissions model, but it has since been superseded by alternative structures. From a heuristic Data Vault modeling perspective, the relationship data classifies this object as satellite-leaning. That classification is a modeling suggestion: the table appears to record descriptive attributes (region codes) tied to a parent entry-status entity, making it a candidate satellite rather than a hub or link. Any integrator or reporting author encountering this object should treat it as a legacy artifact rather than an active data source.

Key Information Stored

The documented metadata identifies a small set of significant columns. Rather than a full column inventory, the following are the most important for understanding and, if necessary, migrating or reconciling this object:

• ENTRY_REGION_ID — the surrogate primary key defined by the IGS_AD_SS_REGIONS_PK constraint. This is a system-generated identifier with no business meaning.
• INQ_ENTRY_STAT_ID — a foreign key column referencing IGS_AD_I_ENTRY_STATS. This links a region to an inquiry or entry status, forming the core business relationship of the table.
• REGION_CD — the region code value; together with INQ_ENTRY_STAT_ID it forms the unique key IGS_AD_SS_REGIONS_UK, indicating that a given entry status may have at most one row per region code. This is the principal business-key candidate.

The distinction between the surrogate key (ENTRY_REGION_ID) and the business-key candidate (INQ_ENTRY_STAT_ID plus REGION_CD) is important. The unique index reflects the natural uniqueness rule, while the primary key provides the physical row identifier used by dependent foreign keys. No additional descriptive attribute columns are documented in the available metadata.

Common Use Cases and Queries

Because the table is obsolete and not implemented, direct querying is rarely productive in a live 12.1.1 or 12.2.2 environment. The realistic use cases fall into three categories: validating whether the object exists in a given instance, historical data migration from older releases, and impact analysis for customizations that may still reference it.

A typical existence check queries the data dictionary rather than the table itself:

• SELECT table_name, status FROM dba_tables WHERE table_name = 'IGS_AD_SS_REGIONS'; — confirms whether the object is present and valid.
• SELECT constraint_name, constraint_type, column_name FROM dba_cons_columns WHERE table_name = 'IGS_AD_SS_REGIONS'; — validates the PK, UK, and FK definitions documented above.
• A join pattern against the parent status table would take the form SELECT r.entry_region_id, r.region_cd, s.* FROM igs_ad_ss_regions r, igs_ad_i_entry_stats s WHERE r.inq_entry_stat_id = s.inq_entry_stat_id; — useful only if the obsolete object still holds legacy rows in a pre-upgrade copy.

Reporting on current admissions entry-status configuration should target the replacement structures delivered by the IGS product team rather than this table.

Related Objects

The following objects are the most significant relationships documented in the metadata:

• IGS_AD_I_ENTRY_STATS — referenced by the foreign key IGS_AD_SS_REGIONS.INQ_ENTRY_STAT_ID. This parent table holds the entry-status definition that each region row qualifies.
• IGS_AD_SS_REGN_ATTRS — references IGS_AD_SS_REGIONS via ENTRY_REGION_ID, making it a child detail table holding region attributes. This confirms the satellite-leaning classification, as child attributes hang off the region entity.
• IGS_AD_SS_REGIONS_PK and IGS_AD_SS_REGIONS_UK — the primary and unique constraints that enforce row identity and the INQ_ENTRY_STAT_ID/REGION_CD uniqueness rule.

Collectively, these relationships show a parent-child hierarchy rooted in entry-status configuration. Since the object is documented as obsolete and not implemented, integrators should verify current replacements within the IGS Admissions module before designing any dependency on this structure.