Results for “igs_pr_ou_unit_set”

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

Overview

IGS_PR_OU_UNIT_SET is a reporting and inquiry view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. Its name reflects the functional area it serves: "PR" denotes progression rules, "OU" denotes operating unit, and "UNIT_SET" identifies the subject entity — the unit set definitions used within progression rule configuration. The view exposes a filtered, operating-unit-scoped projection of the underlying IGS_PR_OU_UNIT_SET_ALL table, which is the multi-organization (multi-org) base table storing unit set associations for progression rules per operating unit.

In EBS 12.1.1 and 12.2.2, views following the _ALL / _SET naming pattern are typically used by Oracle's Multi-Org architecture (also called Multiple Organizations or MOAC) to enforce operating unit security. The view applies a WHERE clause that restricts rows to the operating unit identified in the user's CLIENT_INFO session context. This makes it suitable for deployment in forms, concurrent programs, and reports that must respect the user's currently selected operating unit without requiring explicit ORG_ID predicates in the calling code.

From a reporting and integration perspective, the view is a read-only abstraction over the base table. It is commonly referenced in custom reports, OAF pages, and interface extracts that require access to progression rule to unit set relationships. Because it is a view, it carries no independent storage and inherits all DDL changes made to the base table.

Underlying Base Objects

The view is defined directly over the single base table IGS_PR_OU_UNIT_SET_ALL. No other documented base objects are referenced in the ETRM metadata. The view text is a straightforward column projection with a row-level security predicate on ORG_ID. The ROW_ID column is generated via TAB.ROWID, providing a stable physical row identifier for the underlying base table row.

The multi-org filtering predicate uses USERENV('CLIENT_INFO'), decoding the first ten characters of the session client context and comparing them to the row's ORG_ID. The NVL expressions default both sides to -99 when the client info is unavailable, which is the standard EBS convention for matching rows in a non-operating-unit context (such as a responsibility without an assigned org). This structure is characteristic of views generated by the Multi-Org initialization process and is functionally equivalent to a "secured" or "org-striped" view.

Key Columns

• ROW_ID — Physical ROWID of the base table row, exposed for locking and direct addressing.
• PROGRESSION_RULE_CAT — Progression rule category, the top-level discriminator grouping progression rules.
• PRA_SEQUENCE_NUMBER — Sequence number identifying a specific progression rule category entry (progression rule attribute sequence).
• PRO_SEQUENCE_NUMBER — Sequence number for the progression rule itself within the category.
• UNIT_SET_CD — Unit set code, the business key of the unit set being associated with the progression rule.
• US_VERSION_NUMBER — Version number of the unit set, allowing versioned references to unit set definitions.
• ORG_ID — Operating unit identifier used by the multi-org security predicate.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified the row, when, and from which login session.

Common Use Cases and Queries

Typical uses include validating progression rule to unit set assignments for a specific operating unit, extracting configuration data for migration between environments, and building custom reports that must honor MOAC security. A basic query listing all visible unit set associations for the current operating unit is:

SELECT unit_set_cd, us_version_number, progression_rule_cat,
pra_sequence_number, pro_sequence_number
FROM igs_pr_ou_unit_set
ORDER BY progression_rule_cat, pra_sequence_number;

To retrieve a specific unit set version:

SELECT *
FROM igs_pr_ou_unit_set
WHERE unit_set_cd = :unit_set_cd
AND us_version_number = :version;

For auditing recent changes:

SELECT unit_set_cd, last_updated_by, last_update_date
FROM igs_pr_ou_unit_set
WHERE last_update_date >= SYSDATE - 30;

Because the view enforces operating unit security, queries return rows only for the ORG_ID resolved from the session's client info. Callers operating in a non-MOAC context or from a background job without client info set should query IGS_PR_OU_UNIT_SET_ALL directly, or set the client info via FND_GLOBAL.APPS_INITIALIZE, to avoid unintended filtering.