Results for “igs_st_unt_load_appo”

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

Overview

The IGS_ST_UNT_LOAD_APPO table belongs to the IGS (Student System) product family within Oracle E-Business Suite, a module now classified as obsolete in both release 12.1.1 and 12.2.2. The table records the apportionment of teaching load for a specific unit within a teaching period. In practical terms, it captures how the total effort or weighting attached to a unit is divided across teaching calendar instances. The documented example — 75% in semester 1 only and 25% in semester 2 only — illustrates the intended semantics: a single unit offering is split into proportional components, each associated with a distinct teaching period.

The ETRM metadata notes that the object is not implemented in this database, meaning the table is documented as part of the historical data model but is absent from the delivered schema. It should therefore be treated as a legacy or reference artifact rather than a live transactional table.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is that of a link. This classification is a modeling suggestion: the table primarily resolves relationships between unit offerings, default load apportionment definitions, and teaching calendar instances, rather than acting as a standalone hub of business entities or a pure descriptive satellite.

Key Information Stored

The documented physical schema contains twelve columns. The most significant are those forming the primary key and the proportional weighting attributes:

• DLA_CAL_TYPE — the default load apportionment calendar type, linking to the IGS_ST_DFT_LOAD_APPO parent.
• CI_SEQUENCE_NUMBER — sequence identifier within the calendar instance context.
• UNIT_CD — the unit (subject/module) code being apportioned.
• VERSION_NUMBER — the version of the unit offering, enabling multiple effective versions.
• TEACH_CAL_TYPE — the teaching calendar type (e.g., semester) against which the portion is measured.
• PERCENTAGE — the primary proportion of load assigned to the teaching period.
• SECOND_PERCENTAGE — a secondary proportion, supporting the two-period split described in the documentation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified each row.

The surrogate primary key is IGS_ST_UNT_LOAD_APPO_PK, composed of DLA_CAL_TYPE, CI_SEQUENCE_NUMBER, UNIT_CD, VERSION_NUMBER, and TEACH_CAL_TYPE. A second documented key, ULA_PK, carries the same five columns. The unique index IGS_ST_UNT_LOAD_APPO_U1 mirrors this column set, making it the business-key candidate ensuring one apportionment row per unit, version, and teaching calendar combination.

Common Use Cases and Queries

Because the table is obsolete and not implemented, use cases are primarily historical, analytical, or migration-oriented. Typical scenarios include reconstructing teaching load distribution for legacy reporting, validating unit offering weights across semesters, and mapping old Student System data into replacement structures. A representative query pattern joins the apportionment rows to their unit offering and default load parent:

• Report the percentage split per unit and teaching period: SELECT UNIT_CD, VERSION_NUMBER, TEACH_CAL_TYPE, PERCENTAGE, SECOND_PERCENTAGE FROM IGS_ST_UNT_LOAD_APPO WHERE UNIT_CD = :unit_code;
• Validate that apportionments sum to 100% across teaching periods for a given unit version.
• Trace which default load apportionment definition governs a unit via DLA_CAL_TYPE and CI_SEQUENCE_NUMBER.

Related Objects

The foreign-key metadata identifies the principal related objects:

• IGS_ST_DFT_LOAD_APPO — parent definition of default load apportionment, joined on DLA_CAL_TYPE, CI_SEQUENCE_NUMBER, and TEACH_CAL_TYPE.
• IGS_PS_UNIT_OFR — the unit offering master, joined on UNIT_CD, VERSION_NUMBER, and TEACH_CAL_TYPE.

These two tables constitute the core referential context for IGS_ST_UNT_LOAD_APPO and are the most significant objects to consult when interpreting or migrating its data.