Results for “us_version_number”

50+ results




Overview
Explore in AI Chat

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

Overview

The view IGS_PR_OU_UNIT_SET_V belongs to the Oracle E-Business Suite product family IGS — Student System, a module that Oracle has classified as obsolete. It is a thin, read-only projection view that exposes the column set of the underlying IGS_PR_OU_UNIT_SET table alongside a surrogate ROW_ID derived from the table's physical ROWID. In the taxonomy of EBS dictionary objects, this is a simple wrapper view — it does not perform joins, aggregation, decoding, or translation of any kind. Its purpose is to present progression-rule organizational unit set data to forms, concurrent programs, and external integrations in a stable, named interface without exposing the full base table.

The ETRM metadata for release 12.2.2 explicitly records the object as "Not implemented in this database," meaning the view definition exists in the E-Business Suite data model but is not instantiated in the shipping installation. This is consistent with the obsolete status of the IGS product line: objects are retained for dictionary compatibility and historical reference rather than for active operational use.

Underlying Base Objects

The view is defined over exactly one base object, IGS_PR_OU_UNIT_SET, as confirmed by the ETRM view text. No referenced base objects are documented beyond this single table, and no joins, unions, or inline subqueries appear in the definition. The relationship is therefore one-to-one: every row returned by the view corresponds to a single row of IGS_PR_OU_UNIT_SET, and no filtering or predicate is applied.

The ROW_ID column is produced by selecting the physical ROWID of the base table row and aliasing it. Because ROWID is not a stable logical key and can change after table reorganization, exports, or imports, it should never be persisted as a foreign key reference. Downstream consumers should rely on the natural composite key formed by the progression rule category, the two sequence numbers, the unit set code, and the unit set version number.

Key Columns

  • ROW_ID — The base table's physical ROWID, useful only for intra-session row identification.
  • PROGRESSION_RULE_CAT — Progression rule category, the high-level classification that groups related progression rule definitions.
  • PRA_SEQUENCE_NUMBER — Sequence number that orders or identifies entries within the progression rule category.
  • PRO_SEQUENCE_NUMBER — Additional sequence used to qualify the progression rule record.
  • UNIT_SET_CD — The unit set code identifying the set of academic units (modules, subjects, or course units) associated with the rule.
  • US_VERSION_NUMBER — Version number of the unit set, supporting effective-dated or versioned curriculum definitions.
  • CREATED_BY, CREATION_DATE — Standard EBS audit columns recording the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording the most recent modification user, timestamp, and login.

Common Use Cases and Queries

Because the view adds no logic, its practical value is limited to convenience and naming consistency. Typical scenarios include reporting on progression-rule-to-unit-set mappings, validating curriculum version data, and building integrations that must reference the public view rather than the base table. A standard query retrieving all mapped unit sets is:

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

A version-history query for a single unit set applies an equality filter:

SELECT us_version_number, pra_sequence_number, last_update_date FROM igs_pr_ou_unit_set_v WHERE unit_set_cd = :p_unit_set_cd ORDER BY us_version_number DESC;

An integration extract relying on the surrogate identifier takes the form:

SELECT row_id, unit_set_cd, us_version_number FROM igs_pr_ou_unit_set_v WHERE last_update_date >= :p_since;

Given the obsolete status of the IGS product and the "not implemented" designation, any query against this view should first verify that the object exists in the target database and that the base table contains data. Where the object is absent, the equivalent selection can be performed directly against IGS_PR_OU_UNIT_SET, adding ROWID AS ROW_ID to reproduce the view's output exactly.