Results for “s_relation_type”

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

Overview

The view APPS.IGS_PR_RU_CA_TYPE_V is a VALID database object owned by the APPS schema within the IGS – Student System product family of Oracle E-Business Suite (applicable to releases 12.1.1 and 12.2.2). It is a composite view defined over progression rule application and category-type tables and serves as a flattened access point for resolving which "category type" progression rules apply to a given progression-rule application record. Because the view merges multiple source tables through a UNION of three SELECT branches, it presents a normalized projection of progression rule categorisation that reporting, validation, and integration logic can consume without reproducing the join and set logic themselves. The view is typically used in student progression processing and related functional configurations where the relationship between progression rule applications (identified by PROGRESSION_RULE_CAT and SEQUENCE_NUMBER) and their associated calendar types and sequence ranges must be resolved.

Underlying Base Objects

The view text references two documented base tables:

• IGS_PR_RU_APPL — the progression rule application table, aliased as PRA in the first and second SELECT branches and as PRA1 in the second branch's self-join. This table supplies the rule category, sequence number, and the relationship type (S_RELATION_TYPE).
• IGS_PR_RU_CA_TYPE — the progression rule calendar-type/category table, aliased PRCT, which supplies calendar type (PRG_CAL_TYPE), start and end sequence numbers, effective period, and number of applications.

The ETRM metadata records none as explicitly documented referenced base objects, so the join relationships are inferred from the view SQL itself. The three UNION branches produce a consistent column list, with the second branch performing a self-join on IGS_PR_RU_APPL and an anti-join (NOT EXISTS) against IGS_PR_RU_CA_TYPE to include application rows whose relationship type falls into ('CRV','OU','CTY','SCA','PRO','SPO') and which lack a matching category-type parent.

Key Columns

• PROGRESSION_RULE_CAT — identifies the progression rule category; central to all three branches and both joins.
• PRA_SEQUENCE_NUMBER — sequence number of the progression rule application; in the third branch this is the original (category) sequence number from PRCT, aliased as ORIGINAL_PRA_SEQUENCE_NUMBER.
• PRG_CAL_TYPE — the calendar type associated with the progression rule category.
• START_SEQUENCE_NUMBER, END_SEQUENCE_NUMBER, START_EFFECTIVE_PERIOD — govern the effective range and application period of the rule.
• NUM_OF_APPLICATIONS — number of applications covered by the rule category.
• S_RELATION_TYPE — relationship type of the rule application (e.g., CRV, OU, CTY, SCA, PRO, SPO, PRR).
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include validating progression rule configuration, reconciling applications to category types, and feeding progression reports. A representative query:

• SELECT PROGRESSION_RULE_CAT, PRA_SEQUENCE_NUMBER, PRG_CAL_TYPE, S_RELATION_TYPE FROM APPS.IGS_PR_RU_CA_TYPE_V WHERE PROGRESSION_RULE_CAT = :p_cat;
• Filtering by relationship type, e.g. WHERE S_RELATION_TYPE IN ('CRV','PRR'), to isolate credit or prerequisite rules.
• Joining the view back to IGS_PR_RU_APPL on PROGRESSION_RULE_CAT and PRA_SEQUENCE_NUMBER to enrich application detail with calendar-type context for reporting.

Because the view applies a UNION with an anti-join, consumers should expect rows where no category-type match exists to be surfaced from the application side, making it suitable for completeness checks across progression rule applications.