Results for “igs_ps_unt_dscp_hist_all”
27 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IGS_PS_UNT_DSCP_HIST_ALL is an Oracle EBS Student System (IGS) table that records the history of changes made to a unit version's unit discipline. In the Oracle E-Business Suite 12.1.1 and 12.2.2 data model, the Unit Version entity represents a specific offering of an academic unit (course) for a given version, and each unit version may be associated with one or more discipline groups. This history table preserves the temporal evolution of those discipline associations, capturing when a discipline group assignment became effective and when it was superseded. It therefore provides an auditable, date-effective record that supports academic reporting, accreditation analysis, and curriculum governance.
From a heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a link table — it resolves the relationship between unit version records and discipline group records while carrying descriptive temporal attributes. The table resides in the IGS schema and is documented as VALID in the ETRM repository, comprising 13 physical columns in the 12.1.1 schema.
Key Information Stored
The primary key is defined by the constraint IGS_PS_UNT_DSCP_HIST_PK, which spans four columns: UNIT_CD, VERSION_NUMBER, DISCIPLINE_GROUP_CD, and HIST_START_DT. These four columns together also form the unique index IGS_PS_UNT_DSCP_HIST_ALL_U1, making them the documented business-key candidates. The most significant columns are:
- UNIT_CD — the code identifying the academic unit; part of the primary key and a foreign key to IGS_PS_UNIT_VER_ALL.
- VERSION_NUMBER — the specific version of the unit; part of the primary key and, with UNIT_CD, a foreign key to the unit version entity.
- DISCIPLINE_GROUP_CD — the discipline group associated with the unit version; part of the primary key and a foreign key to IGS_PS_DSCP_ALL.
- HIST_START_DT — the effective start date of the historical record; part of the primary key.
- HIST_END_DT — the effective end date of the discipline assignment, delimiting the validity period.
- HIST_WHO — identifies the user or process that created the historical record.
- PERCENTAGE — the proportion of the unit attributed to the discipline group, where applicable.
- ORG_ID — the operating unit or organization identifier, supporting multi-org security.
- CREATED_BY, CREATION_DATE — standard audit columns recording row creation.
- LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording the most recent modification.
The surrogate primary key is the sequence-backed constraint IGS_PS_UNT_DSCP_HIST_PK itself; the business key is the natural combination UNIT_CD, VERSION_NUMBER, DISCIPLINE_GROUP_CD, and HIST_START_DT. Note that no separate numeric surrogate column is documented beyond the composite key.
Common Use Cases and Queries
Typical usage involves point-in-time and audit reporting. A common pattern retrieves the discipline groups active for a unit version on a given date:
- Filtering rows where HIST_START_DT <= :as_of_date and (HIST_END_DT is null or HIST_END_DT > :as_of_date) to reconstruct the effective discipline set.
- Joining to IGS_PS_UNIT_VER_ALL on UNIT_CD and VERSION_NUMBER to resolve unit titles and version details.
- Joining to IGS_PS_DSCP_ALL on DISCIPLINE_GROUP_CD to obtain discipline descriptions for curriculum and accreditation reports.
- Aggregating PERCENTAGE by discipline group to analyze disciplinary weighting across a program.
- Auditing changes by ordering on HIST_START_DT descending to view the most recent modifications per unit version.
Because the table is date-effective, reporting queries should always constrain by ORG_ID where multi-org access applies and by the history dates to avoid returning superseded rows.
Related Objects
The most significant related objects, based on the documented foreign key relationships, are:
- IGS_PS_UNIT_VER_ALL — the unit version entity; joined on UNIT_CD and VERSION_NUMBER.
- IGS_PS_DSCP_ALL — the discipline group entity; joined on DISCIPLINE_GROUP_CD.
- IGS_PS_UNT_DSCP_ALL — the current (non-historical) unit discipline association, serving as the operational counterpart to this history table.
- IGS_PS_UNIT_ALL — the parent unit entity referenced indirectly through unit versions.
- IGS_PS_DSCP_GRP_ALL — discipline group hierarchy definitions used in curriculum roll-ups.
- IGS_PS_UNT_DSCP_HIST_PK — the primary key constraint enforcing uniqueness across the four business-key columns.
These relationships make the table a critical link in the Student System curriculum model, enabling full historical traceability of disciplinary associations across unit versions.
-
This entity describes the history of changes to a unit version's unit discipline.
-
This entity describes the history of changes to a unit version's unit discipline.
Not implemented in this database·Explore IGS module →
-
View: IGS_PS_UNT_DSCP_HIST 12.1.1
APPS.IGS_PS_UNT_DSCP_HIST·↳ IGS_PS_UNT_DSCP_HIST_ALL·Explore IGS module →
-
Table: IGS_PS_DSCP_ALL 12.2.2
This entity describes the university set of discipline group codes. This is not limited to the DEET set and values, which are reported to DEET, will be mapped onto DEET equivalent values.
Not implemented in this database·Explore IGS module →
-
View: IGS_PS_UNT_DSCP_HIST 12.2.2
Not implemented in this database·Explore IGS module →
-
PACKAGE: APPS.IGS_AU_GEN_004 12.1.1
-
Table: IGS_PS_UNIT_VER_ALL 12.2.2
This entity describes a version of a unit, which is offered by the university.
Not implemented in this database·Explore IGS module →
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
eTRM - IGS Tables and Views 12.1.1
Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'.
-
eTRM - IGS Tables and Views 12.1.1
Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'.