Results for “igs_pr_ru_ca_type”

25 results




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

Overview

IGS_PR_RU_CA_TYPE is a reporting and integration view belonging to the IGS — Student System product family, a module now classified as obsolete within Oracle E-Business Suite. The view exposes configuration data for progression rule categories that are associated with a specific program calendar type, allowing progression rules to be segmented into categories and ordered by sequence. In EBS 12.1.1 and 12.2.2 the object is documented but not implemented in the database, meaning the underlying _ALL table and the view itself are absent from standard installations. Its principal role is to present a secured, organization-filtered projection of progression rule category data for downstream reporting, concurrent programs, or integration interfaces within the student system.

Underlying Base Objects

The view is defined over a single base table, IGS_PR_RU_CA_TYPE_ALL, which stores progression rule category definitions together with their calendar-type context and sequence boundaries. It is an _ALL style object, indicating that rows are partitioned by operating unit through the ORG_ID column. The view applies a multi-org security predicate that reads USERENV('CLIENT_INFO'), extracting the operating unit identifier from the client information string and comparing it against the row's ORG_ID. Where no operating unit is resolved, the expression defaults to -99, which effectively excludes unrestricted rows. Although ETRM lists no additional referenced base objects, the view's row identity is supplied by TAB.ROWID, aliased as ROW_ID, rather than by a named primary key column.

Key Columns

  • ROW_ID — the physical row identifier from the base table, useful for row-level addressing and updates.
  • PROGRESSION_RULE_CAT — the progression rule category, the primary business descriptor for the record.
  • PRA_SEQUENCE_NUMBER — sequence numbering applied to the progression rule category.
  • PRG_CAL_TYPE — the program calendar type to which the category applies, linking configuration to a delivery calendar.
  • START_SEQUENCE_NUMBER and END_SEQUENCE_NUMBER — the lower and upper bounds of the sequence range covered by the category. The END_SEQUENCE_NUMBER column is the term most frequently queried, as it defines the inclusive upper limit of the progression rule category's coverage.
  • START_EFFECTIVE_PERIOD — the effective period from which the category configuration applies.
  • NUM_OF_APPLICATIONS — the number of applications permitted or expected for the category.
  • Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — standard EBS who-column auditing.
  • ORG_ID — the operating unit that owns the row and drives the view's multi-org security filter.

Common Use Cases and Queries

Because the view enforces operating unit security automatically, it is the preferred access path for any query that must respect multi-org isolation. A typical retrieval lists all categories for a program calendar type in sequence order, including the end sequence boundary:

  • SELECT progression_rule_cat, prg_cal_type, start_sequence_number, end_sequence_number FROM igs_pr_ru_ca_type WHERE prg_cal_type = :calendar_type ORDER BY start_sequence_number;
  • SELECT progression_rule_cat, end_sequence_number, num_of_applications FROM igs_pr_ru_ca_type WHERE end_sequence_number >= :sequence AND org_id = :org_id;
  • SELECT COUNT(*) FROM igs_pr_ru_ca_type WHERE start_effective_period BETWEEN :from_period AND :to_period;

The END_SEQUENCE_NUMBER predicate is the most common filter, used to determine which progression rule category governs a given sequence position. Analysts should note the object's obsolete status: it should not be relied upon in new development, and any legacy query referencing it requires verification that the IGS Student System components are actually installed in the target environment.