Results for “stat_type_cd”

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

Overview

IGS_OR_INST_STATS is a table in the IGS (Student System) product of Oracle E-Business Suite, documented in ETRM for releases 12.1.1 and 12.2.2. Its description, "Describes Institution Statistic Details," identifies it as the storage point for institution-level statistical attributes associated with a party, typically an institution or organization unit tracked within the Student System. In the Oracle EBS data model, the table functions as an association between a party record and a statistical classification, allowing the institution's profile to be annotated with one or more statistics that downstream admissions, recruitment, and reporting processes can consume.

The heuristic Data Vault classification mined from the foreign key structure is satellite-leaning. Under this modeling suggestion, IGS_OR_INST_STATS would be treated as a satellite attached to the IGS_OR_INST_STATS parent keyed by INST_STAT_ID, carrying descriptive attributes whose changes are tracked over time. The two inbound foreign key references to IGS_AD_CODE_CLASSES and HZ_PARTIES position the table as a dependent descriptive structure rather than an independent hub.

Key Information Stored

The table contains 13 documented columns. The most significant are the following:

• INST_STAT_ID — the surrogate primary key defined by IGS_OR_INST_STATS_PK and reinforced by the unique index IGS_OR_INST_STATS_U1. This is the system-generated identifier for each institution statistic record.
• STAT_TYPE_ID — a foreign key to IGS_AD_CODE_CLASSES that specifies the statistical classification being recorded.
• STAT_TYPE_CD — the coded value of the statistic type, the second component of the unique index IGS_OR_INST_STATS_U2 and the primary key IGS_OR_INST_STATS_UK alongside PARTY_ID. This is a business-key candidate.
• PARTY_ID — a foreign key to HZ_PARTIES identifying the institution or party to which the statistic applies; it is the other business-key candidate in IGS_OR_INST_STATS_U2.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns capturing who created or last modified the record and when.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — the standard concurrent program context columns recording which concurrent request and program last touched the row.

The distinction matters: INST_STAT_ID is the technical primary key used for joins, while the PARTY_ID plus STAT_TYPE_CD combination (and separately STAT_TYPE_CD within the unique-key definition) forms the business-key candidate that enforces one statistic type per party.

Common Use Cases and Queries

Typical reporting scenarios retrieve the statistics attached to a given institution for admissions or recruitment analysis. A common pattern joins the table to HZ_PARTIES to resolve the institution name and to IGS_AD_CODE_CLASSES to resolve the statistic description:

• Listing all statistics for a party: SELECT stat_type_cd, stat_type_id FROM igs.igs_or_inst_stats WHERE party_id = :p_party_id;
• Resolving descriptive detail via the child table: SELECT h.* FROM igs.igs_or_inst_stats h, igs.igs_or_inst_stat_dtl d WHERE h.inst_stat_id = d.inst_stat_id AND h.party_id = :p_party_id;
• Driving lookups by statistic code: SELECT party_id FROM igs.igs_or_inst_stats WHERE stat_type_cd = :p_stat_code;
• Audit and concurrency reporting using LAST_UPDATE_DATE, REQUEST_ID, and PROGRAM_ID.

Because the detail child table carries the granular statistic values, most reporting queries join parent to child rather than reading the parent alone.

Related Objects

• HZ_PARTIES — referenced through IGS_OR_INST_STATS.PARTY_ID; supplies the institution identity.
• IGS_AD_CODE_CLASSES — referenced through IGS_OR_INST_STATS.STAT_TYPE_ID; supplies the statistical code classification.
• IGS_OR_INST_STAT_DTL — the detail child table joined by INST_STAT_ID; it holds the granular statistic data that complements this header record.

These three relationships define the table's role: a party-linked, code-classified header supported by a detail table, and best modeled as a satellite around its parent key.