Search Results igs_pr_ou_unit




Overview
Explore in AI Chat

Overview

IGS_PR_OU_UNIT is a secure (organization‑unit‑filtered) view owned by the APPS schema in the Oracle E‑Business Suite Student System (product code IGS). It exists in Oracle EBS release 12.1.1 and 12.2.2 and is registered as a VALID database object. The view exposes progression‑rule configuration data that governs how student progression is evaluated against individual academic units (courses) within the institution.

The view functions as the multi‑tenant, business‑unit‑aware presentation layer over the underlying IGS_PR_OU_UNIT_ALL table. Rather than exposing all rows across every organization unit, IGS_PR_OU_UNIT restricts the visible record set using the standard EBS MOAC (Multi‑Org Access Control) pattern. It reads the current operating unit identifier from the session‑level CLIENT_INFO value via USERENV('CLIENT_INFO') and returns only those rows whose ORG_ID matches the caller's active organization context. This makes it the appropriate access point for inquiry screens, concurrent programs, and reporting that must be scoped to a single operating unit.

Because it is a view rather than a table, it holds no data of its own; it is a reporting and integration artifact, and forms, APIs, and extraction routines rely on it to provide org‑secured reads of progression‑rule‑to‑unit associations.

Underlying Base Objects

The view is defined over a single documented base object: IGS_PR_OU_UNIT_ALL, which is the _ALL (non‑org‑filtered) table storing the full cross‑organization data set. The view text explicitly selects the row identifier and the relevant business columns from this table and applies the organization predicate in the WHERE clause:

  • The predicate compares TAB.ORG_ID with a value derived from USERENV('CLIENT_INFO').
  • Where CLIENT_INFO is null or blank, both sides resolve to the sentinel value -99, preserving the standard EBS convention for non‑org‑secured access.
  • The ROW_ID column is populated from ROWID of the base table, giving each row a unique physical address usable for locking or direct updates.

No other referenced base objects are documented in the ETRM metadata. This one‑table definition means the view inherits the storage, indexing, and constraint behavior of IGS_PR_OU_UNIT_ALL; its cost is therefore the cost of scanning or indexing that underlying table plus the predicate evaluation.

Key Columns

  • ROW_ID — The base‑table ROWID, uniquely identifying each physical row.
  • PROGRESSION_RULE_CAT — The progression rule category, identifying the classification of the progression rule being configured.
  • PRA_SEQUENCE_NUMBER — Sequence number associated with the progression rule category (PRA), used for ordering and unique identification of the rule entry.
  • PRO_SEQUENCE_NUMBER — Sequence number for the progression object, further qualifying the specific rule element.
  • UNIT_CD — The academic unit (course/subject) code to which the progression rule applies.
  • S_UNIT_TYPE — The student unit type indicator, distinguishing how the unit is treated for progression purposes.
  • CREATED_BY / CREATION_DATE — Standard audit columns recording who created the row and when.
  • LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification and the login of the updating user.
  • ORG_ID — The operating unit identifier that drives the MOAC filter; a value of -99 represents the non‑org‑specific context.

Together, the progression category, sequence numbers, unit code, and unit type form the functional key describing which units participate in a given progression rule configuration.

Common Use Cases and Queries

Typical scenarios include auditing progression‑rule configuration for a department, exporting unit‑to‑rule mappings into reporting extracts, and validating that all units for a program are correctly associated. Because the view auto‑filters by operating unit, queries run in a MOAC‑initialized session (for example, via the Multi‑Org preferences in Forms or an FND_GLOBAL.APPS_INITIALIZE call) automatically return only the relevant rows.

List all progression‑rule unit mappings visible to the current operating unit:

  • SELECT progression_rule_cat, pra_sequence_number, pro_sequence_number, unit_cd, s_unit_type, org_id FROM apps.igs_pr_ou_unit;

Retrieve all rows for a specific unit code regardless of the active org context, using the base table directly:

  • SELECT * FROM apps.igs_pr_ou_unit_all WHERE unit_cd = :p_unit_cd ORDER BY pra_sequence_number, pro_sequence_number;

Report recently modified configuration, leveraging the audit columns:

  • SELECT unit_cd, progression_rule_cat, last_updated_by, last_update_date FROM apps.igs_pr_ou_unit WHERE last_update_date >= TRUNC(SYSDATE) - 30 ORDER BY last_update_date DESC;

For any extract intended to span multiple operating units, the _ALL table should be queried; the view is reserved for org‑secured, single‑unit access and should not be used where cross‑unit visibility is required.