Results for “max_cp”

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

Overview

The IGS_PR_RU_APPL view is a reporting and integration object belonging to the IGS (Student System) product family within Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2, the IGS module is treated as an obsolete or legacy component; ETRM explicitly labels it "IGS - Student System (Obsolete)." The view exposes progression rule application data, specifically records that associate student progression rules with attendance types, course types, organizational units, and class standings. Its role is to present a denormalized, query-friendly projection of progression rule application information so that downstream reports, concurrent programs, and integrations can retrieve rule-to-student and rule-to-course relationships without joining the underlying tables directly.

The ETRM metadata notes that the object is "Not implemented in this database," meaning it is documented for reference but may not exist in every environment. Where present, it is a security-enabled (multi-org) view, as evidenced by the ORG_ID predicate applied through USERENV('CLIENT_INFO').

Underlying Base Objects

The view is defined over three documented base objects:

• IGS_PR_RU_APPL_ALL — the primary ALL table holding progression rule application rows across organizations. It supplies most columns, including the ROWID alias ROW_ID, progression rule attributes, attendance and course details, and audit columns.
• IGS_PR_RU_CAT — the progression rule category table, outer-joined to provide POSITIVE_RULE_IND via NVL(RC.POSITIVE_RULE_IND, 'N').
• IGS_PR_CLASS_STD — the class standing table, outer-joined on IGS_PR_CLASS_STD_ID to supply the CLASS_STANDING value.

The WHERE clause enforces the operating unit context by comparing the row's ORG_ID against the value decoded from the client information environment setting, defaulting to -99 when no context is set. The outer joins (+) ensure that rule application rows are returned even when category or class standing data is missing.

Key Columns

• ROW_ID — the ROWID of the underlying application row, useful for direct row access.
• PROGRESSION_RULE_CAT, PROGRESSION_RULE_CD, RUL_SEQUENCE_NUMBER, SEQUENCE_NUMBER — identify the progression rule category, code, and sequencing.
• S_RELATION_TYPE — indicates the relationship type governing the rule application.
• ATTENDANCE_TYPE, COURSE_TYPE, CRV_COURSE_CD, CRV_VERSION_NUMBER — course and attendance context for the rule.
• OU_ORG_UNIT_CD, OU_START_DT, ORG_ID — organizational unit and multi-org context.
• SCA_PERSON_ID, SCA_COURSE_CD, SPO_PERSON_ID, SPO_COURSE_CD, SPO_SEQUENCE_NUMBER — student/course associations referenced by the rule.
• MIN_CP, MAX_CP — minimum and maximum credit points applying to the rule.
• POSITIVE_RULE_IND, CLASS_STANDING, IGS_PR_CLASS_STD_ID — derived rule polarity and class standing details.
• LOGICAL_DELETE_DT, MESSAGE — soft-delete marker and diagnostic message.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include validating progression rule configurations, reporting rule application by operating unit, and feeding academic progress integrations. A simple query retrieves active rules for the current org context:

• SELECT PROGRESSION_RULE_CAT, PROGRESSION_RULE_CD, CRV_COURSE_CD, MIN_CP, MAX_CP, CLASS_STANDING FROM IGS_PR_RU_APPL WHERE LOGICAL_DELETE_DT IS NULL;
• SELECT SCA_PERSON_ID, COUNT(*) FROM IGS_PR_RU_APPL GROUP BY SCA_PERSON_ID;

Because the view is multi-org secured, direct queries return only rows matching the active operating unit context, which must be considered when troubleshooting missing data in EBS 12.1.1 and 12.2.2.