Results for “igs_pr_ru_ou_v”

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

Overview

IGS_PR_RU_OU_V is a database view belonging to the IGS (Student System) product family in Oracle E-Business Suite. In the ETRM metadata for release 12.2.2 the object is flagged as part of an obsolete module, and the Implementation/DBA section explicitly records that it is "Not implemented in this database." This indicates the view is a legacy dictionary object that survives from earlier Oracle Student System releases and is not deployed in a standard current EBS installation. Where it does exist, it presents progression-rule configuration data used by the academic progression and enrolment engine.

The view joins progression outcome rules to their outcome type definitions, exposing a flat, report-friendly row per rule/outcome combination. It is intended for reporting and integration rather than for transactional maintenance, and consumers should treat all rows as read-only projections of the underlying rule tables.

Underlying Base Objects

The documented view text defines IGS_PR_RU_OU_V over two base tables:

• IGS_PR_RU_OU (aliased RUO) — the primary progression rule outcome table, supplying the rule category, sequence numbers, failure thresholds, duration attributes, restricted enrolment and restricted attendance attributes, audit columns, and the logical delete date.
• IGS_PR_OU_TYPE (aliased ROT) — the progression outcome type table, contributing the POSITIVE_OUTCOME_IND flag.

The two objects are equijoined on PROGRESSION_OUTCOME_TYPE. The metadata records no other documented base objects, so the view is effectively a two-table projection with a single inner join. Because the join is an inner join, any rule row whose outcome type has no matching definition in IGS_PR_OU_TYPE will not appear in the view. Row identity is supplied through RUO.ROWID, aliased as ROW_ID, which allows downstream processes to address the underlying rule row directly.

Key Columns

Key columns exposed by the view include:

• ROW_ID — the ROWID of the base progression rule row, used for identity and update targeting.
• PROGRESSION_RULE_CAT, PRA_SEQUENCE_NUMBER, SEQUENCE_NUMBER — identify the rule category and the ordering of individual rule lines.
• NUMBER_OF_FAILURES — the failure count threshold that triggers the outcome.
• PROGRESSION_OUTCOME_TYPE and POSITIVE_OUTCOME_IND — the outcome applied and whether that outcome is classified as positive.
• APPLY_AUTOMATICALLY_IND, PRG_RULE_REPEAT_FAIL_TYPE — control automatic application and repeat-failure handling.
• OVERRIDE_SHOW_CAUSE_IND, OVERRIDE_APPEAL_IND — govern whether cause and appeal overrides are permitted.
• DURATION, DURATION_TYPE, RANK — define validity period and precedence when multiple rules compete.
• RESTRICTED_ATTENDANCE_TYPE and RESTRICTED_ENROLMENT_CP — capture restricted attendance and restricted enrolment checkpoint settings. These columns are the ones most frequently referenced by searches for RESTRICTED_ATTENDANCE_TYPE.
• Audit and lifecycle columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and LOGICAL_DELETE_DT, the last of which supports soft deletion.

Common Use Cases and Queries

Typical uses are diagnosing why a student progressed or was refused progression, auditing restricted attendance configuration, and feeding progression data into extracts. Reports normally filter out soft-deleted rows and restrict results to the relevant outcome types.

Sample query listing rules with restricted attendance settings:

SELECT ROW_ID, PROGRESSION_RULE_CAT, SEQUENCE_NUMBER, PROGRESSION_OUTCOME_TYPE, RESTRICTED_ATTENDANCE_TYPE, RESTRICTED_ENROLMENT_CP FROM IGS_PR_RU_OU_V WHERE RESTRICTED_ATTENDANCE_TYPE IS NOT NULL AND LOGICAL_DELETE_DT IS NULL ORDER BY PROGRESSION_RULE_CAT, SEQUENCE_NUMBER;

Sample query identifying automatically applied negative outcomes:

SELECT PROGRESSION_OUTCOME_TYPE, COUNT(*) FROM IGS_PR_RU_OU_V WHERE APPLY_AUTOMATICALLY_IND = 'Y' AND POSITIVE_OUTCOME_IND = 'N' AND LOGICAL_DELETE_DT IS NULL GROUP BY PROGRESSION_OUTCOME_TYPE;

Because the object is obsolete and undocumented in modern installations, any query referencing IGS_PR_RU_OU_V should first confirm existence through ALL_VIEWS or the EBS data dictionary; a failure is expected on environments where the Student System is absent.