Search Results igs_en_atd_mode




Overview
Explore in AI Chat

Overview

IGS_EN_ATD_MODE is an Oracle E-Business Suite view owned by the APPS schema and reported as VALID under the IGS (Student System) product family. Its documented purpose is to expose university-defined attendance modes — such as Internal, External and Multimodal — that drive the enrolment process within the Student System. In practice it is a reporting and integration-friendly projection over the underlying attendance mode data, presenting a single row per attendance mode together with the descriptive and administrative attributes that a student records implementation requires.

Most technical references to this object appear in reporting contexts such as Oracle Reports, BI Publisher, Discoverer and downstream extracts where attendance mode codes must be resolved to descriptions. This is corroborated by the fact that the view follows the standard EBS "reporting view over an _ALL table" pattern: the column list mirrors the base table exactly, with ROW_ID added as a ROWID alias, and the only behavioural change is the enforcement of organization-level (multi-org) security via the ORG_ID predicate. Because the caller never sees rows outside its own operating unit context, the view is a natural choice for data extracts and interfaces that must respect EBS multi-org isolation.

Underlying Base Objects

The view text defines IGS_EN_ATD_MODE as a single-table view over IGS_EN_ATD_MODE_ALL. No other base objects are documented in the ETRM metadata, and the view text confirms there are no joins, unions or aggregations — all columns are selected directly from the base table, with only ROW_ID derived from the physical ROWID of IGS_EN_ATD_MODE_ALL.

  • Base table: IGS_EN_ATD_MODE_ALL (the "all organizations" repository of attendance modes).
  • Filter: NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTRB(USERENV('CLIENT_INFO'), 1, 10))), -99)) = the same expression — the classic multi-org _ALL predicate pattern used throughout EBS 11i, 12.1.1 and 12.2.2.
  • Multi-org mechanism: the predicate extracts the operating unit identifier from the CLIENT_INFO session context (set by FND_CLIENT_INFO), so the view returns seeded/global rows (where ORG_ID is null, normalized to -99) as well as rows belonging to the caller's operating unit.

Because the view is defined over an _ALL table, no base object other than IGS_EN_ATD_MODE_ALL is exposed or required.

Key Columns

  • ROW_ID — the database ROWID of the underlying row in IGS_EN_ATD_MODE_ALL; useful for uniquely identifying or subsequently updating a row.
  • ATTENDANCE_MODE — the coded identifier of the attendance mode (for example Internal, External or Multimodal); the primary business key used in enrolment logic.
  • DESCRIPTION — the university-defined display text for the attendance mode.
  • GOVT_ATTENDANCE_MODE — the statutory or government reporting attendance mode classification, where the institution maps its own modes to an external reporting code.
  • CLOSED_IND — indicates whether the attendance mode has been closed and is therefore unavailable for new enrolment.
  • ORG_ID — the operating unit that owns the record; NULL denotes a global/seeded row visible to all operating units.
  • Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS "who did what, when" set for traceability.

Common Use Cases and Queries

Typical consumers are enrolment reports and validation routines that need the set of active attendance modes available to a student's operating unit, plus extracts that must publish the government-facing classification.

  • Populating an LOV or validation list with open attendance modes.
  • Extracting a code-to-description lookup for enrolment or student record extracts.
  • Joining attendance mode data to enrolment records for statistical or statutory reporting.

Example — all active attendance modes for the current operating unit context:

  • SELECT attendance_mode, description, govt_attendance_mode FROM igs_en_atd_mode WHERE NVL(closed_ind, 'N') = 'N' ORDER BY attendance_mode;

Example — resolving a description from a stored mode code within an extract join:

  • SELECT e.person_id, e.attendance_mode, a.description FROM igs_en_enrolments e, igs_en_atd_mode a WHERE e.attendance_mode = a.attendance_mode;

Because multi-org filtering is already applied inside the view, application code need not add an ORG_ID predicate; doing so explicitly is redundant but harmless provided the value matches the caller's operating unit.