Search Results positive_rule_ind




Overview
Explore in AI Chat

Overview

IGS_PR_RULE is a reporting and integration view that belongs to the IGS product family, formally identified as the Oracle Student System. In Oracle EBS 12.1.1 and 12.2.2 the IGS modules historically supported the Oracle Student System (OSS) footprint, and the ETRM metadata classifies this object as part of IGS – Student System (Obsolete). The view exposes progression rule definitions maintained in the Student System, joining the multi-organization rule table to a rule-category lookup table and applying an organization-security predicate based on the session's client information. Its principal role is to present a flattened, secured, denormalized projection of progression rules so that forms, concurrent programs, and downstream integrations can consume rule data without re-implementing the join logic or the organization filter.

Underlying Base Objects

The view text is defined over two base objects: IGS_PR_RULE_ALL (aliased TAB) and IGS_PR_RU_CAT (aliased PRC). IGS_PR_RULE_ALL stores the progression rule rows, including the rule category, rule code, description, sequence number, closed indicator, message, positive-rule flag source, standard WHO audit columns, and ORG_ID. IGS_PR_RU_CAT holds the rule-category attributes, including POSITIVE_RULE_IND, which indicates whether a category behaves as a positive or negative rule.

The join between the two tables is an equijoin on PROGRESSION_RULE_CAT. The organization predicate compares TAB.ORG_ID against the value derived from USERENV('CLIENT_INFO'), using a NVL/NVL wrapper that substitutes -99 when no organization context is available. Rows are therefore restricted to the organization currently set in the session, which is the conventional multi-org security pattern used by seeded IGS views. The ETRM entry records no referenced base objects and states that the view was not implemented in the documented database, meaning it exists in the shipped IGS schema but may be absent from a given environment.

Key Columns

  • ROW_ID – the ROWID of the underlying IGS_PR_RULE_ALL row, used for update and lock purposes.
  • PROGRESSION_RULE_CAT – the rule category, serving as the join key to IGS_PR_RU_CAT.
  • PROGRESSION_RULE_CD – the unique code identifying an individual progression rule.
  • DESCRIPTION – the descriptive text associated with the rule.
  • RUL_SEQUENCE_NUMBER – the ordering sequence applied when rules are evaluated within a category.
  • CLOSED_IND – indicates whether the rule is inactive or closed to further use.
  • MESSAGE – the message text presented when the rule is applied or violated.
  • POSITIVE_RULE_IND – sourced from IGS_PR_RU_CAT, distinguishing positive from negative rule behavior.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – the standard WHO audit columns.
  • ORG_ID – the organization owning the rule row, enforced through the client-info predicate.

Common Use Cases and Queries

The view is typically used to list active progression rules for the current organization, to report rules grouped by category, and to feed integration extracts. A typical listing query is:

SELECT PROGRESSION_RULE_CAT, PROGRESSION_RULE_CD, DESCRIPTION, RUL_SEQUENCE_NUMBER, POSITIVE_RULE_IND FROM IGS_PR_RULE WHERE CLOSED_IND = 'N' AND ORG_ID = :org_id ORDER BY PROGRESSION_RULE_CAT, RUL_SEQUENCE_NUMBER;

Because rows are already organization-filtered, an explicit ORG_ID predicate is optional; however, since ORG_ID is NULL for some seeded rows, the NVL to -99 means such rows surface only when no organization is set. Analysts should therefore test with and without an org context. A category summary query would be:

SELECT PROGRESSION_RULE_CAT, COUNT(*) FROM IGS_PR_RULE GROUP BY PROGRESSION_RULE_CAT;

Given the Obsolete classification in 12.1.1 and 12.2.2, any integration should verify object existence before deployment and treat the view as read-only reference data.