Search Results igs_or_org_inst_type_all




Overview

The IGS_OR_ORG_INST_TYPE_ALL table is a reference data entity within the now-obsolete Oracle Student System (IGS) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Its primary function is to serve as a master list or lookup for classifying educational institutions by type. It provides a standardized set of codes and descriptions, such as "University," "Community College," or "Technical Institute," which can be used to categorize and report on institutional data across the student lifecycle. As a foundational reference table, it ensures data consistency by centralizing these definitions. The metadata explicitly notes this table was "Not implemented in this database," indicating it may have been a planned data model component not deployed in standard installations, or its functionality was superseded by other tables in later releases of the IGS product.

Key Information Stored

Based on the provided entity description and key structure, the table's core purpose is to hold institution type codes and their corresponding descriptions. The primary data elements are the INSTITUTION_TYPE code, which serves as the unique identifier (Primary Key), and a descriptive field (implied by the entity description, though not explicitly named in the excerpt, such as DESCRIPTION). As a table with the "_ALL" suffix in EBS, it is architected to support multi-organization access control (MOAC), meaning it likely contains an ORG_ID column to partition data by operating unit. Its structure is designed for simple reference: a concise code linked to a clear, user-facing description.

Common Use Cases and Queries

The primary use case for this table is to validate and describe institution type codes used in transactional and statistical tables. In reporting scenarios, it is joined to fact tables to translate codes into meaningful descriptions for end-users. Common operational queries would involve listing all valid institution types or retrieving the description for a specific code. For example, a report on entry statistics might join to this table to group data by institution type description. A typical SQL pattern would be a simple lookup or a join to enrich data from related fact tables.

  • Lookup Query: SELECT institution_type, description FROM igs_or_org_inst_type_all WHERE org_id = :p_org_id ORDER BY description;
  • Reporting Join: SELECT stat.*, type.description FROM igs_ad_i_entry_stats stat, igs_or_org_inst_type_all type WHERE stat.institution_type = type.institution_type;

Related Objects

The documented foreign key relationships define this table's integration within the obsolete Student System data model. It is referenced as a parent lookup table by at least two other entities, both of which appear to store statistical data related to institutional entries. The specific relationships, as per the provided metadata, are:

  • IGS_AD_I_ENTRY_STATS: The INSTITUTION_TYPE column in this table references IGS_OR_ORG_INST_TYPE_ALL.INSTITUTION_TYPE. This links entry statistics to an institution type classification.
  • IGS_RC_I_ENT_STATS: The INSTITUTION_TYPE column in this table also references IGS_OR_ORG_INST_TYPE_ALL.INSTITUTION_TYPE, indicating a similar relationship for a different set of entry statistics.

These relationships enforce referential integrity, ensuring that the institution type codes recorded in the statistical tables are valid according to the master list. The primary key constraint IGS_OR_ORG_INST_TYPES_PK on the INSTITUTION_TYPE column enables these foreign key references.