Results for “effective_start_dt”

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

Overview

IGS_PS_ANL_LOAD is a table within the Oracle E-Business Suite Student System (IGS) product family, documented in the ETRM reference for releases 12.1.1 and 12.2.2. The entity describes the annual load for each year of a program, with units subsequently linked to that load to define the standard load used in Equivalent Full-Time Student Unit (EFTSU) calculations. In institutional terms, the table provides the year-by-year workload baseline against which individual program units are measured for funding, progression, and load normalization purposes.

The ETRM metadata records this object as obsolete, and the implementation note states that it is not implemented in the documented database. Its principal value today is therefore historical and structural: it explains how legacy IGS program-version data modeled annual load values before replacement by the successor Student System schema. Applying the mined Data Vault classification heuristic, the table leans toward a satellite classification, since it carries descriptive load measures (ANNUAL_LOAD_VAL) keyed by a composite business key plus effective dating, hanging off a parent program-version construct.

Key Information Stored

The table comprises 11 documented columns in the 12.1.1 physical schema, owned by the IGS schema. The most significant columns are:

• COURSE_CD – the program (course) identifier to which the annual load applies, forming the leading component of the primary key.
• VERSION_NUMBER – the version of the program record, allowing multiple versions of the same program to carry distinct load definitions.
• YR_NUM – the year number within the program, identifying the specific year of study for which load is defined.
• EFFECTIVE_START_DT and EFFECTIVE_END_DT – date-effective boundaries that establish the validity window of the load record.
• ANNUAL_LOAD_VAL – the actual annual load value used as the standard load for EFTSU calculation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – the standard Oracle EBS auditing columns, in this case populating the remainder of the 11 documented columns.

The primary key is defined by the constraint IGS_PS_ANL_LOAD_PK, spanning COURSE_CD, VERSION_NUMBER, YR_NUM, and EFFECTIVE_START_DT. No separate surrogate key is documented; the unique index IGS_PS_ANL_LOAD_U1 carries the identical column set, so the business-key candidate and the primary key coincide, with date-effectivity embedded in that key rather than expressed as a surrogate identifier.

Common Use Cases and Queries

In a historical reporting context, the most frequent requirement is reconstructing the standard annual load for a program year so that EFTSU figures for linked units can be validated. A representative query pattern joins the load table to the assessment load table and filters on date-effectivity:

• Retrieve the current annual load for a program version and year: SELECT annual_load_val FROM igs_ps_anl_load WHERE course_cd = :course AND version_number = :version AND yr_num = :yr AND TRUNC(SYSDATE) BETWEEN effective_start_dt AND NVL(effective_end_dt, TRUNC(SYSDATE));
• Compare load definitions across program versions to detect changes introduced by version rollover.
• Feed EFTSU calculations by joining annual load values to the unit-level load mapping table on COURSE_CD, VERSION_NUMBER, YR_NUM, and EFFECTIVE_START_DT.
• Audit historical load records using CREATED_BY, CREATION_DATE, and LAST_UPDATE_DATE to establish when a load value was introduced or amended.
• Produce year-by-year load profiles for a program to support curriculum and funding analysis.

Because the object is obsolete and not implemented in the documented database, such queries are relevant chiefly when migrating or reconciling legacy IGS data rather than for current production reporting.

Related Objects

Relationship data identifies a small dependency footprint, centered on the parent program-version record and the downstream unit-load mapping:

• IGS_PS_VER_ALL – the parent program version table, joined to IGS_PS_ANL_LOAD on COURSE_CD and VERSION_NUMBER. This is the foreign key target recorded for IGS_PS_ANL_LOAD.
• IGS_PS_ANL_LOAD_U_LN – the unit-to-load mapping table that references IGS_PS_ANL_LOAD on COURSE_CD, CRV_VERSION_NUMBER, YR_NUM, and EFFECTIVE_START_DT, linking individual units to the annual load for EFTSU purposes.

These two relationships define the practical join path: program version to annual load, then annual load to unit load. No views or public APIs specific to this table are recorded in the supplied ETRM excerpt.