Results for “enrollment_function”

3 results




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

Overview

The view IGS_EN_NSU_DLSTP belongs to the IGS — Student System product family in Oracle E-Business Suite. The IGS module provided the foundation for the Oracle Student System (OSS) functionality, and this view is documented as obsolete in both EBS 12.1.1 and 12.2.2. It exposes the configuration data that governs non-standard unit section enrollment deadline setup — that is, the rules that determine when a deadline is calculated for enrollment into a section whose unit value deviates from the standard institutional definition.

Functionally, this view is a reporting and integration layer rather than a transactional object. Its purpose is to present the raw numeric and coded values stored in the underlying deadline-setup table alongside their human-readable meanings, so that reports, concurrent programs, or interface extracts can present deadline configuration without performing their own multi-table decoding.

Underlying Base Objects

The view is defined over the following objects (as reflected in the ETRM view text and documented metadata):

  • IGS_EN_NSU_DLSTP_ALL — the primary base table holding the deadline-setup rows for non-standard unit section enrollment.
  • IGS_LOOKUPS_VIEW — referenced three times (aliases LKV1, LKV2, LKV3) to translate coded columns into meanings.
  • IGS_OR_UNIT — joined with an outer join ((+)) on ORG_UNIT_CODE = OU.ORG_UNIT_CD to supply the organization description.

The joins to the lookup view are keyed by LOOKUP_TYPE values of ENROLLMENT_FUNCTION, DEFINITION_LEVEL, and OFFSET_DATE respectively. The view also applies a Multi-Org security predicate against ORG_ID, using USERENV('CLIENT_INFO') with a sentinel of -99 when no organization is set. The ETRM record notes the view is not implemented in this database and that no base objects are formally documented, which is consistent with its obsolete status.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing deadline configuration, validating lookup integrity, and driving enrollment or billing extracts. Because the view resolves code meanings, it is well suited to ad-hoc reporting and reference-data reconciliation.

Example — list active deadline setups with their decoded meanings for a specific organization unit:

  • SELECT function_name, function_name_meaning, definition_code_meaning, org_unit_code, org_description, offset_dt_code_meaning, offset_duration, incl_wkend_duration_flag
  • FROM igs_en_nsu_dlstp
  • WHERE org_unit_code = :p_org_unit_code
  • ORDER BY function_name, definition_code;

Example — identify records whose lookup values may no longer resolve:

  • SELECT non_std_usec_dls_id, function_name, definition_code, offset_dt_code
  • FROM igs_en_nsu_dlstp
  • WHERE function_name_meaning IS NULL OR definition_code_meaning IS NULL OR offset_dt_code_meaning IS NULL;

Given the obsolete designation, deployments on 12.1.1 or 12.2.2 should treat this view as read-only reference metadata and confirm existence via ALL_VIEWS before relying on it in custom code.