Results for “run_date”

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

Overview

The IGS_PR_COHORT_INST table resides in the IGS schema within the Oracle E-Business Suite Student System (IGS) product family. It stores Class Rank Cohort Instances, representing specific, calendar-anchored executions of a Class Rank Cohort definition. In the Oracle EBS 12.1.1 and 12.2.2 releases, this table serves as the transactional anchor that binds an abstract cohort definition to a concrete academic period in which ranking is performed. It forms part of the progression and ranking (PR) subsystem used by institutions to determine class standing, honors eligibility, and academic performance ordering among student groups.

From a dimensional modeling perspective, the foreign key structure suggests a satellite-leaning classification. The table does not behave as a pure hub, since it carries descriptive attributes such as status flags and run metadata; nor is it a pure link, though it bridges cohort definitions to calendar instances. Its role is most consistent with that of a satellite attached to the combination of a cohort hub (IGS_PR_COHORT) and a calendar instance dimension (IGS_CA_INST_ALL), capturing the state and processing outcome of each ranking run.

Key Information Stored

The primary key, IGS_PR_COHORT_INST_PK, is a composite key composed of COHORT_NAME, LOAD_CAL_TYPE, and LOAD_CI_SEQUENCE_NUMBER. These three columns also form the unique index IGS_PR_COHORT_INST_U1, making them the business-key candidates for the row. COHORT_NAME identifies the class rank cohort definition; LOAD_CAL_TYPE specifies the calendar type (for example, academic or load calendar); and LOAD_CI_SEQUENCE_NUMBER identifies the precise calendar instance sequence within that calendar type, effectively pinning the instance to a term or period.

Descriptive attributes capture processing state: COHORT_STATUS reflects the cohort instance’s lifecycle state, and RANK_STATUS records the status of the ranking computation for that instance. RUN_DATE holds the date the rank process was executed. The table also carries the standard Oracle EBS audit and concurrent-program columns, including CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. The audit and request columns allow administrators to trace which concurrent request and program produced or last modified the instance. The documented physical schema contains 15 columns in total.

Common Use Cases and Queries

Typical reporting scenarios include identifying cohorts with pending or failed ranking runs, auditing when a class rank was last calculated, and joining rank output to student records. A common pattern filters on processing state:

• SELECT COHORT_NAME, LOAD_CAL_TYPE, LOAD_CI_SEQUENCE_NUMBER, RANK_STATUS, RUN_DATE FROM IGS_PR_COHORT_INST WHERE RANK_STATUS = 'PENDING';
• Join to the rank detail table to produce class standing reports: SELECT i.COHORT_NAME, r.rank columns FROM IGS_PR_COHORT_INST i, IGS_PR_COHINST_RANK r WHERE i.COHORT_NAME = r.COHORT_NAME AND i.LOAD_CAL_TYPE = r.LOAD_CAL_TYPE AND i.LOAD_CI_SEQUENCE_NUMBER = r.LOAD_CI_SEQUENCE_NUMBER;
• Join to IGS_CA_INST_ALL to resolve human-readable term descriptions for a given LOAD_CAL_TYPE and LOAD_CI_SEQUENCE_NUMBER.
• Use REQUEST_ID and PROGRAM_ID to trace a ranking execution back to its concurrent program log for troubleshooting.

Related Objects

The most significant related objects are derived from the documented foreign key relationships and the dependent table that references this one:

• IGS_PR_COHORT — the parent cohort definition; joined on COHORT_NAME.
• IGS_CA_INST_ALL — the calendar instance dimension; joined on LOAD_CAL_TYPE and LOAD_CI_SEQUENCE_NUMBER.
• IGS_PR_COHINST_RANK — the child table holding per-student rank results; it references IGS_PR_COHORT_INST on COHORT_NAME, LOAD_CAL_TYPE, and LOAD_CI_SEQUENCE_NUMBER.
• IGS_PR_COHORT_INST_PK and IGS_PR_COHORT_INST_U1 — the primary key constraint and unique index enforcing row uniqueness.

Together these objects form the cohort ranking data model, with IGS_PR_COHORT_INST acting as the connecting instance record between cohort definitions, calendar periods, and computed rank outcomes.