Results for “igs_en_unit_set_all”

50+ results




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

Overview

The IGS_EN_UNIT_SET_ALL table resides in the IGS schema and forms part of the Oracle E-Business Suite Student System (IGS) module. It stores the definition of a unit-set, which the ETRM documentation describes as "a logical sub-grouping of course," with representative examples being Major, Minor, Stream, and Strand. In institutional terms, a unit-set provides the academic container into which students are admitted, against which they accumulate units, and through which progression and award rules are evaluated. The documentation notes that a unit-set is "typically related to the rules which govern its completion via the Rules Sub-system," establishing this table as the anchor point between the curriculum definition layer and the rules engine.

The table supports record versioning. Its primary key is a composite of UNIT_SET_CD and VERSION_NUMBER (constraint IGS_EN_UNIT_SET_PK), and a unique index IGS_EN_UNIT_SET_ALL_U1 covers the same pair. This versioned design allows an existing unit-set to be re-released at a higher version without invalidating prior student records or historical rules. From a Data Vault modelling perspective, the heuristically mined FK structure classifies this object as hub-leaning: the combination of UNIT_SET_CD and VERSION_NUMBER behaves as a durable business key that a large family of dependent objects references, while the descriptive attributes (title, status, dates) are more satellite in character.

The table is validated and carries 42 documented columns in the 12.1.1 reference schema. It is a multi-org aware object, evidenced by the presence of ORG_ID, and is treated as an "ALL" table, indicating that it is exposed through the standard classification and security views of the Student System.

Key Information Stored

The most significant columns, drawn from the documented 42-column structure, are:

  • UNIT_SET_CD — the business identifier of the unit-set; first component of the primary key and of the unique index IGS_EN_UNIT_SET_ALL_U1.
  • VERSION_NUMBER — the version of that unit-set definition; second component of the primary key and unique index.
  • UNIT_SET_STATUS — lifecycle state of the definition (for example active, inactive, or under review), which governs whether the unit-set can be attached to new offers or application instances.
  • UNIT_SET_CAT — the category of unit-set, distinguishing concepts such as Major, Minor, Stream, or Strand.
  • TITLE, SHORT_TITLE, ABBREVIATION — the descriptive labels used in catalogues, offer letters, and student self-service.
  • START_DT, REVIEW_DT, EXPIRY_DT, END_DT — the validity window and administrative milestones for the version, used to determine which version is current on a given date.
  • RESPONSIBLE_ORG_UNIT_CD, ORG_ID, RESPONSIBLE_OU_START_DT — the owning organisational unit and operating unit context, supporting multi-org security and reporting.
  • ADMINISTRATIVE_IND — flags unit-sets maintained for administrative rather than academic purposes.
  • AUTHORISATION_RQRD_IND — indicates whether completion of the unit-set requires formal authorisation.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — the standard Oracle DFF (descriptive flexfield) block, used for institution-specific extensions.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns.

Unit-set completion itself is not stored here; it is governed by the Rules Sub-system and the associated rule table, while the mapping table IGS_EN_UNIT_SET_MAP relates stream unit-sets to their parent structures.

Common Use Cases and Queries

The most frequent access pattern is retrieval of the currently effective version of a unit-set for display or validation. Because multiple versions may share a UNIT_SET_CD, queries should filter on the date window or select the maximum version.

  • Current version lookup: SELECT unit_set_cd, version_number, title, unit_set_status FROM igs_en_unit_set_all WHERE unit_set_cd = :p_code AND SYSDATE BETWEEN start_dt AND NVL(end_dt, SYSDATE + 1);
  • Catalogue extract for reporting: join to IGS_PS_OFR_UNIT_SET to list unit-sets available against each program offering, using UNIT_SET_CD and VERSION_NUMBER as join keys.
  • Rules integration: join to IGS_EN_UNIT_SET_RULE on UNIT_SET_CD to inspect which completion rules apply to a given unit-set version.
  • Fee assessment impact: join to IGS_FI_FEE_AS_ITEMS or IGS_FI_FEE_AS_RATE on UNIT_SET_CD to determine which unit-sets drive fee calculations.
  • Organisational reporting: filter by RESPONSIBLE_ORG_UNIT_CD and ORG_ID to report unit-sets owned by a faculty or department.
  • Version history: SELECT unit_set_cd, version_number, unit_set_status, start_dt, end_dt FROM igs_en_unit_set_all WHERE unit_set_cd = :p_code ORDER BY version_number;

Because of the versioned key, any extract intended for downstream reconciliation should carry both UNIT_SET_CD and VERSION_NUMBER; omitting VERSION_NUMBER will produce duplicate rows.

Related Objects

The FK metadata shows IGS_EN_UNIT_SET_ALL as a heavily referenced parent. The most significant dependents include:

These relationships confirm that IGS_EN_UNIT_SET_ALL is a foundational hub in the IGS data model, connecting admissions, curriculum, fees, awards, and the rules engine through a single versioned business key.