Search Results igs_en_nstd_usec_dl_uk1

Overview

IGS_EN_NSTD_USEC_DL is a transactional table within the IGS (Student System) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It belongs to the IGS schema and stores the enrollment deadline rules that apply to non-standard unit section enrollments. In the Oracle Student System model, standard sections follow institution-wide enrollment calendar rules; non-standard sections — those that do not conform to the normal term or session pattern — require their own deadline logic. This table holds that logic, capturing how an enrollment deadline date is derived for a specific combination of a non-standard enrollment deadline setup and a unit offering option.

From a Data Vault modeling perspective, the mined foreign-key structure suggests classifying this object as a link. The table sits between two parent entities — the non-standard unit section deadline setup (IGS_EN_NSU_DLSTP_ALL) and the unit offering option (IGS_PS_UNIT_OFR_OPT_ALL) — and its business-key uniqueness constraint is defined over the pairing of FUNCTION_NAME and UOO_ID, which is consistent with a relationship or association construct.

Key Information Stored

The table contains eighteen documented columns. The surrogate primary key is NSTD_USEC_DL_ID, enforced through IGS_EN_NSTD_USEC_DL_PK and repeated in unique index U1. Two business-key candidates are documented: U1 on NSTD_USEC_DL_ID and U2 on the composite of FUNCTION_NAME and UOO_ID.

• NSTD_USEC_DL_ID — surrogate primary key identifying each deadline rule row.
• NON_STD_USEC_DLS_ID — foreign key to IGS_EN_NSU_DLSTP_ALL, linking the row to its parent non-standard deadline setup.
• UOO_ID — foreign key to IGS_PS_UNIT_OFR_OPT_ALL, identifying the unit offering option to which the deadline rule applies.
• FUNCTION_NAME — the functional identifier used with UOO_ID to form the second unique key; it distinguishes rule variants attached to the same offering option.
• DEFINITION_CODE and ORG_UNIT_CODE — the definition and organizational unit context governing the rule.
• FORMULA_METHOD and ROUND_METHOD — control how the deadline is calculated and how any resulting fractional days are rounded.
• OFFSET_DT_CODE, OFFSET_DURATION, and ENR_DL_OFFSET_DAYS — define the offset basis and the number of days by which the deadline shifts relative to that basis.
• ENR_DL_DATE and ENR_DL_TOTAL_DAYS — the resolved enrollment deadline date and the total day count within the allowed window.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns.

Common Use Cases and Queries

Typical usage centers on determining the enrollment deadline for a non-standard section, either for display in self-service enrollment or for batch eligibility checks. A common reporting pattern joins this table to its parents to resolve descriptive context:

• Retrieve all deadline rules for a given unit offering option: SELECT nstd_usec_dl_id, function_name, enr_dl_date, enr_dl_total_days FROM igs_en_nstd_usec_dl WHERE uoo_id = :uoo_id;
• Resolve the deadline setup context: SELECT d.* FROM igs_en_nstd_usec_dl d, igs_en_nsu_dlstp_all s WHERE d.non_std_usec_dls_id = s.non_std_usec_dls_id AND d.uoo_id = :uoo_id;
• Audit recently changed rules using last_update_date and last_updated_by.
• Validation extracts confirming that every row satisfies the U2 uniqueness constraint on FUNCTION_NAME and UOO_ID.

Related Objects

The table participates in two documented foreign-key relationships, and its primary key is typically referenced indirectly through the deadline setup hierarchy.

• IGS_EN_NSU_DLSTP_ALL — parent setup table joined on NON_STD_USEC_DLS_ID.
• IGS_PS_UNIT_OFR_OPT_ALL — unit offering option table joined on UOO_ID.
• IGS_EN_NSTD_USEC_DL_PK, IGS_EN_NSTD_USEC_DL_U1, and IGS_EN_NSTD_USEC_DL_U2 — the supporting primary and unique index objects.
• IGS_EN_NSTD_USEC_DL_UK1 — the alternate unique constraint over FUNCTION_NAME and UOO_ID.

Because the IGS Student System processes enrollment deadlines through concurrent programs and self-service APIs, any extraction or integration reading this table should preserve the FUNCTION_NAME and UOO_ID pairing to avoid ambiguity across rule variants.