Results for “igs_pr_sca_prg_rule_appl_v”

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

Overview

The view IGS_PR_SCA_PRG_RULE_APPL_V belongs to the IGS — Student System product family within Oracle E-Business Suite (documented here in the context of EBS 12.1.1 and 12.2.2). Its name decomposes into the functional elements it joins: IGS (the Student System schema prefix), PR (Progression Rules), SCA (Student Course Attempt), and PRG_RULE_APPL (progression rule application). The view therefore presents the combined result of progression rules applied against a student's course attempt records, resolved through the programme calendar type and calendar instance.

In the ETRM reference, the object is flagged as belonging to a module marked Obsolete, and the Implementation/DBA Data section records it as "Not implemented in this database." This indicates the view is a legacy or compatibility object that may not exist in every installation. Where present, it serves as a reporting and integration surface, allowing progression-rule outcomes to be queried in a denormalised, human-readable form without requiring callers to reconstruct the underlying rule logic.

Underlying Base Objects

ETRM lists no separately documented referenced base objects for this view. The view text, however, exposes an explicit FROM clause joining the following physical objects:

• IGS_CA_STAT (aliased CS) — calendar status.
• IGS_PR_PRG_RU_CA_TYPE_CI_V (aliased PRCTCV) — the programme calendar type / calendar-instance view, the source of PRG_CAL_TYPE and PRG_CI_SEQUENCE_NUMBER.
• IGS_CA_INST (aliased CI) — calendar instances.
• IGS_PR_RU_APPL (aliased PRA) — the progression rule application records.
• IGS_PS_VER (aliased CRV) — programme version / course version.
• IGS_EN_STDNT_PS_ATT (aliased SCA) — student programme attempt records.

Rule evaluation is delegated to two packaged functions: IGS_PR_GEN_005.IGS_PR_GET_SCA_APPL, which returns 'Y' or 'N' to indicate whether a rule applies to a given student course attempt, and IGS_EN_GEN_014.ENRS_GET_ACAD_ALT_CD, which resolves the academic alternate code. A NOT EXISTS subquery over IGS_PR_RU_APPL and IGS_PR_PRG_RU_CA_TYPE_CI_V filters out lower-priority or superseded rule applications, so the view returns only the effective application per context.

Key Columns

The projection exposes both identity and descriptive columns. Notable ones include:

• PERSON_ID, COURSE_CD — the student and course attempt being evaluated.
• PRG_CAL_TYPE, PRG_CI_SEQUENCE_NUMBER — the programme calendar type and calendar-instance sequence, the core context for rule applicability and the term the user searched for.
• PROGRESSION_RULE_CAT, SEQUENCE_NUMBER, RUL_SEQUENCE_NUMBER — rule categorisation and ordering.
• S_RELATION_TYPE and its decoded form — a DECODE maps 'OU' to "ORG UNIT", 'CTY' to "CRS TYPE", 'CRV' to "COURSE", and 'SCA' to "STUDENT", giving the rule's target scope. The view text restricts the primary query to S_RELATION_TYPE = 'CTY'.
• PROGRESSION_RULE_CD, REFERENCE_CD — the rule identity.
• ATTENDANCE_TYPE, START_EFFECTIVE_PERIOD, NUM_OF_APPLICATIONS — rule application parameters.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include auditing which progression rules apply to a cohort, reconciling term-based rule application against PRG_CAL_TYPE, and feeding downstream reporting on student progression. A representative query selecting by calendar type is:

SELECT PERSON_ID, COURSE_CD, PRG_CAL_TYPE, PRG_CI_SEQUENCE_NUMBER,
PROGRESSION_RULE_CD, S_RELATION_TYPE, ATTENDANCE_TYPE
FROM IGS_PR_SCA_PRG_RULE_APPL_V
WHERE PRG_CAL_TYPE = :p_cal_type
AND PERSON_ID = :p_person_id;

Because the object is flagged obsolete and may be unimplemented, callers should verify its existence in ALL_VIEWS before relying on it, and prefer supported progression-rule APIs where available.