Results for “igs_ps_unitreqref_cd_u1”

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

Overview

IGS_PS_UNITREQREF_CD is a reference and configuration table within the Oracle EBS Student System (IGS) product family. It stores Unit Requirements Reference Codes, which associate a specific academic unit (identified by UNIT_CD and VERSION_NUMBER) with a categorised reference value maintained in the shared reference-code infrastructure. In functional terms, this table acts as a controlled vocabulary bridge: it allows an institution to attach one or more typed reference codes — for example, entry requirement categories, approval flags, or external classification labels — to a curriculum unit version without hard-coding those values into the unit definition itself.

From a data-modelling perspective, the heuristic Data Vault classification of this table is satellite-leaning. The presence of a surrogate primary key, descriptive attributes, and foreign-key links outward to the general reference-code table indicates that this object primarily holds descriptive context that hangs off a business key rather than acting as an independent hub or a pure many-to-many link. It is therefore best treated as a dependent satellite when reverse-engineering an integration or warehouse model.

Key Information Stored

• UNIT_REQ_REF_CD_ID — the system-generated surrogate primary key (IGS_PS_UNITREQREF_CD_PK) that uniquely identifies each row. It is also the basis of unique index IGS_PS_UNITREQREF_CD_U1.
• UNIT_CD — the academic unit code to which the reference code applies; part of the business-key candidate.
• VERSION_NUMBER — the version of the unit, enabling version-specific reference coding; part of the business key.
• REFERENCE_CD_TYPE — the type or category of the reference code. This column participates in the foreign key to IGS_GE_REF_CD and is part of the business key.
• REFERENCE_CODE — the actual reference value associated with the unit version; part of the business key and of the foreign-key relationship to IGS_GE_REF_CD.
• REFERENCE_CODE_ID — the identifier form of the reference value, also documented as referencing IGS_GE_REF_CD; provides an alternate key path to the reference-code definition.
• REFERENCE_CODE_DESC — a descriptive label for the reference code, supporting user-facing displays without a join.

The combination of UNIT_CD, VERSION_NUMBER, REFERENCE_CD_TYPE, and REFERENCE_CODE is enforced as a unique business key through index IGS_PS_UNITREQREF_CD_U2, guaranteeing that a unit version cannot carry a duplicate type/code pairing. The remaining audited columns record the standard who/when metadata (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), which supports audit reporting and incremental extraction.

Common Use Cases and Queries

Typical use cases include reporting all reference codes attached to a unit version, validating that codes conform to a permitted type, and extracting reference-code assignments for downstream curriculum or compliance reporting. A representative query joins to the general reference-code table to resolve descriptions:

• SELECT ur.UNIT_CD, ur.VERSION_NUMBER, ur.REFERENCE_CD_TYPE, ur.REFERENCE_CODE, ur.REFERENCE_CODE_DESC FROM IGS_PS_UNITREQREF_CD ur WHERE ur.UNIT_CD = :unit_code AND ur.VERSION_NUMBER = :version;
• SELECT ur.*, rc.DESCRIPTION FROM IGS_PS_UNITREQREF_CD ur JOIN IGS_GE_REF_CD rc ON rc.REFERENCE_CD_TYPE = ur.REFERENCE_CD_TYPE AND rc.REFERENCE_CODE = ur.REFERENCE_CODE WHERE ur.REFERENCE_CD_TYPE = :ref_type;
• Incremental extraction for a warehouse or integration layer can filter on LAST_UPDATE_DATE > :last_run_date.

Related Objects

• IGS_GE_REF_CD — the general reference-code table referenced twice from this object, via REFERENCE_CD_TYPE/REFERENCE_CODE and via REFERENCE_CODE_ID. This is the primary lookup dependency and the key join target.
• IGS_PS_UNIT and its version table — the unit definition objects that supply UNIT_CD and VERSION_NUMBER context.
• IGS_PS_UNITREQREF_CD_PK / _U1 / _U2 — the primary and unique indexes enforcing row identity and the business key.
• Student System unit-requirement enquiry forms and concurrent programs that read reference-code assignments for a unit version.
• Downstream curriculum, prospectus, and compliance reporting views built on top of the IGS unit and reference-code structures.