Search Results igs_en_dl_offset_cons




Overview
Explore in AI Chat

Overview

The IGS.IGS_EN_DL_OFFSET_CONS table is a Student System (IGS) configuration table that defines the constraint rules governing enrollment deadline date offsets. In Oracle EBS 12.1.1 and 12.2.2, this table stores the metadata that determines how deadline offset calculations are constrained, resolved, and applied when the system derives enrollment deadlines for students. It sits at the core of the deadline-offset engine, providing the business logic that pairs a given offset constraint type with a non-standard use-case deadline setup and a specific deadline type.

The documented physical schema records 11 columns owned by the IGS schema, with the table marked VALID. Two unique indexes are defined: IGS_EN_DL_OFFSET_CONS_U1 and IGS_EN_DL_OFFSET_CONS_U2. The primary key constraint is IGS_EN_DL_OFFSET_CONS_PK on ENR_DL_OFFSET_CONS_ID. In Data Vault terms, the heuristic classification mined from the foreign-key structure is satellite-leaning. This suggests the table behaves primarily as a descriptive satellite attached to the non-standard use-case deadline step parent, rather than as a standalone hub or a pure link. Practitioners modelling this data for downstream analytics should therefore treat it as an attribute-bearing child keyed to its parent.

Key Information Stored

The most significant columns capture the constraint definition and its relationship to the enrollment deadline framework:

  • ENR_DL_OFFSET_CONS_ID — The surrogate primary key, uniquely identifying each offset constraint record. Enforced by IGS_EN_DL_OFFSET_CONS_PK and mirrored in unique index IGS_EN_DL_OFFSET_CONS_U1.
  • OFFSET_CONS_TYPE_CD — The offset constraint type code; a business-key candidate participating in unique index IGS_EN_DL_OFFSET_CONS_U2.
  • NON_STD_USEC_DLS_ID — Foreign key to IGS_EN_NSU_DLSTP_ALL, linking the constraint to a non-standard use-case deadline step. Also part of IGS_EN_DL_OFFSET_CONS_U2.
  • DEADLINE_TYPE — The deadline type to which the constraint applies; the third component of the business-key unique index IGS_EN_DL_OFFSET_CONS_U2.
  • CONSTRAINT_CONDITION — The condition expression or criteria that triggers the constraint.
  • CONSTRAINT_RESOLUTION — The resolution or action applied when the constraint condition is met.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns tracking record authorship and change history.

The composite unique index IGS_EN_DL_OFFSET_CONS_U2 (OFFSET_CONS_TYPE_CD, NON_STD_USEC_DLS_ID, DEADLINE_TYPE) is the strongest business-key candidate, guaranteeing that no duplicate constraint is defined for the same type, use-case deadline step, and deadline type combination.

Common Use Cases and Queries

Typical scenarios include validating deadline-offset configuration during implementation, troubleshooting unexpected deadline computations, and reporting on configured constraints for an institution. A representative query joining to the parent deadline-step table follows:

  • Retrieve all constraints for a given non-standard use-case deadline step: SELECT c.ENR_DL_OFFSET_CONS_ID, c.OFFSET_CONS_TYPE_CD, c.DEADLINE_TYPE, c.CONSTRAINT_CONDITION, c.CONSTRAINT_RESOLUTION FROM IGS.IGS_EN_DL_OFFSET_CONS c WHERE c.NON_STD_USEC_DLS_ID = :p_dls_id;
  • Join to the parent for descriptive context: SELECT c.*, p.* FROM IGS.IGS_EN_DL_OFFSET_CONS c, IGS.IGS_EN_NSU_DLSTP_ALL p WHERE c.NON_STD_USEC_DLS_ID = p.NON_STD_USEC_DLS_ID;
  • Audit recently modified constraints: SELECT * FROM IGS.IGS_EN_DL_OFFSET_CONS WHERE LAST_UPDATE_DATE > SYSDATE - 30 ORDER BY LAST_UPDATE_DATE DESC;

Related Objects

The most significant related object is the parent referenced by the documented foreign key:

  • IGS_EN_NSU_DLSTP_ALL — Referenced via IGS_EN_DL_OFFSET_CONS.NON_STD_USEC_DLS_ID; supplies the non-standard use-case deadline step context for each constraint.
  • Other IGS enrollment deadline tables, views, and the deadline-processing APIs that consume these constraint definitions, which resolve offset behaviour at runtime.

The FK relationship confirms that IGS_EN_DL_OFFSET_CONS functions as a dependent detail table, and it should always be queried with reference to its IGS_EN_NSU_DLSTP_ALL parent.