Results for “igs_pr_stdnt_pr_ou_all”

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

Overview

IGS_PR_STDNT_PR_OU_ALL is a transactional table within the Oracle E-Business Suite IGS — Student System product family, a module now classified as obsolete in the EBS 12.1.1 / 12.2.2 release stream. The table records a progression outcome applied to an individual student. Each row captures the result of a progression decision — generated either by the system after a student fails a progression rule, or entered manually by an administrative user — together with the approval, waiving, show-cause, and appeal lifecycle that governs whether the outcome is ultimately applied to the student's record. It therefore sits at the intersection of academic rule evaluation, student standing, and institutional review workflow.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is hub-leaning. This is a modeling suggestion only: the primary key of person, course, and sequence behaves as a durable business key identifying a progression-outcome event, while most surrounding attributes (decision status, appeal dates, comments, audit columns) are descriptive payload that would typically be split into satellite structures in a Data Vault implementation.

Note the ETRM implementation line stating "Not implemented in this database." In many reference instances the object exists in the 12.1.1 documented schema (owner IGS, 39 columns) but is not physically created in the target database, so DBAs must confirm physical presence before writing dependent SQL.

Key Information Stored

The documented schema defines 39 columns. The most significant are the following.

• Primary key (surrogate/business key): IGS_PR_STDNT_PR_OU_PK is composed of PERSON_ID, COURSE_CD, and SEQUENCE_NUMBER. The unique index IGS_PR_STDNT_PR_OU_ALL_U1 covers the same three columns, confirming this tuple as the business-key candidate that uniquely identifies a progression outcome per student per course.
• Progression context: PRG_CAL_TYPE, PRG_CI_SEQUENCE_NUMBER, and RULE_CHECK_DT identify the progression calendar, calendar instance, and the date the progression rule was evaluated.
• Rule linkage: PROGRESSION_RULE_CAT, PRA_SEQUENCE_NUMBER, PRO_SEQUENCE_NUMBER, and PRO_PRA_SEQUENCE_NUMBER tie the outcome back to the specific progression rule and its outcome definition that produced it.
• Outcome definition: PROGRESSION_OUTCOME_TYPE references the outcome type; DURATION and DURATION_TYPE express the length and unit of any outcome-imposed period.
• Decision workflow: DECISION_STATUS, DECISION_DT, DECISION_ORG_UNIT_CD, and DECISION_OU_START_DT capture who approved the outcome, when, and under which organizational unit.
• Show-cause and appeal lifecycle: SHOW_CAUSE_DT, SHOW_CAUSE_EXPIRY_DT, SHOW_CAUSE_OUTCOME_DT, SHOW_CAUSE_OUTCOME_TYPE, APPEAL_DT, APPEAL_EXPIRY_DT, APPEAL_OUTCOME_DT, and APPEAL_OUTCOME_TYPE model the student's right of response and its resolution.
• Restrictions: ENCMB_COURSE_GROUP_CD, RESTRICTED_ENROLMENT_CP, and RESTRICTED_ATTENDANCE_TYPE express encumbrance and restricted attendance or enrolment consequences.
• Narrative and audit: COMMENTS, SHOW_CAUSE_COMMENTS, and APPEAL_COMMENTS hold free text; CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, ORG_ID, EXPIRY_DT, and APPLIED_DT provide multi-org and audit context.

Common Use Cases and Queries

Typical uses include tracking the state of progression outcomes awaiting decision, reporting appeal and show-cause volumes, and feeding student-history and encumbrance processes.

• Outcomes pending decision: filter on DECISION_STATUS and DECISION_DT IS NULL to list outcomes not yet approved.
• Show-cause / appeal dashboards: select rows where SHOW_CAUSE_DT or APPEAL_DT falls within a term date range, grouping by PROGRESSION_OUTCOME_TYPE.
• Current standing for a student:

  SELECT person_id, course_cd, sequence_number,
         progression_outcome_type, decision_status, applied_dt
  FROM   igs_pr_stdnt_pr_ou_all
  WHERE  person_id = :p_person_id
  AND    course_cd = :p_course_cd
  ORDER BY sequence_number DESC;

• Rule performance analysis: join to IGS_PR_RU_OU_ALL on PROGRESSION_RULE_CAT, PRA_SEQUENCE_NUMBER, and PRO_SEQUENCE_NUMBER to correlate outcomes with rule definitions.
• Encumbrance extraction: report RESTRICTED_ENROLMENT_CP and RESTRICTED_ATTENDANCE_TYPE for downstream registration blocking.

Related Objects

Foreign-key relationships reveal the principal dependencies and dependents of this table.

• IGS_EN_STDNT_PS_ATT_ALL — referenced via PERSON_ID and COURSE_CD; supplies the underlying student program-attempt record.
• IGS_PR_SDT_PR_RU_CK_ALL — referenced via PERSON_ID, COURSE_CD, PRG_CAL_TYPE, PRG_CI_SEQUENCE_NUMBER, PROGRESSION_RULE_CAT, PRA_SEQUENCE_NUMBER, and RULE_CHECK_DT; the rule-check instance that generated the outcome.
• IGS_PR_RU_OU_ALL — referenced via PROGRESSION_RULE_CAT, PRO_PRA_SEQUENCE_NUMBER, and PRO_SEQUENCE_NUMBER; defines the rule and outcome.
• IGS_PR_OU_TYPE_ALL — referenced via PROGRESSION_OUTCOME_TYPE; the outcome-type lookup.
• IGS_EN_ATD_TYPE_ALL and IGS_PS_GRP_ALL — referenced via RESTRICTED_ATTENDANCE_TYPE and ENCMB_COURSE_GROUP_CD respectively.
• IGS_PR_STDNT_PR_FND and IGS_PE_PERS_ENCUMB — dependent tables referencing PERSON_ID, COURSE_CD, and SEQUENCE_NUMBER, carrying findings and person encumbrances.
• IGS_PR_RU_APPL_ALL, IGS_PR_STU_OU_HIST_ALL, IGS_PR_STDNT_PR_PS, IGS_PR_STDNT_PR_AWD, IGS_PR_SDT_PR_UNT_ST, and IGS_PR_STDNT_PR_UNIT — downstream tables that consume the progression outcome for applications, history, awards, and unit decisions.