Search Results priority_order




Overview
Explore in AI Chat

Overview

APPS.IGS_EN_TIMESLOT_PRTY_V is a reporting view in the Oracle E-Business Suite Student System (formerly Oracle Student System / OSS) enrollment module, exposed under the APPS schema. It presents timeslot priority assignments, joining each priority record to its decoded lookup meaning so that consumers see a human-readable priority label rather than a raw lookup code. The view is a denormalized, read-oriented projection of the transactional table IGS_EN_TIMESLOT_PRTY, enriched with a description column sourced from the lookups view. The igs_en_timeslot_stup_id column referenced by the user's search is the foreign key that links a priority row to the timeslot setup (student unit attempt / timeslot setup) it qualifies, making the view the natural entry point when resolving which priority values apply to a given timeslot configuration.

Because the object is a view rather than a table, it carries no independent storage, no constraints, and no DML of its own. It exists to support inquiry screens, concurrent reports, and integration extracts that require the priority meaning alongside the coded value. It behaves identically in 12.1.1 and 12.2.2; the view definition is unchanged across those releases, and both the column list and the underlying join logic as documented in ETRM apply to either version.

Underlying Base Objects

The documented view text defines the projection over exactly two sources:

  • IGS_EN_TIMESLOT_PRTY ETP — the driving table holding one row per timeslot priority assignment, including the primary key igs_en_timeslot_prty_id, the linking key igs_en_timeslot_stup_id, ordering and value columns, and the standard WHO audit columns.
  • IGS_LOOKUPS_VIEW LKUP — a lookup view filtered in the WHERE clause to LOOKUP_TYPE = 'TIMESLOT_PRIORITY'. The join predicate is LKUP.LOOKUP_CODE = ETP.PRIORITY_VALUE, which restricts output to priority rows whose value resolves to an active lookup entry of that type.

Note the inner-join semantics: any priority row whose priority_value does not match a lookup code in the TIMESLOT_PRIORITY lookup type will be silently excluded from the result set. This is a significant behavioural detail for reconciliation and for diagnosing "missing" priority rows. The ETRM metadata records no additional referenced base objects beyond these two, so no other dependency should be assumed.

Key Columns

  • ROW_ID — the ROWID of the underlying IGS_EN_TIMESLOT_PRTY row; useful for direct row identification in update utilities.
  • IGS_EN_TIMESLOT_PRTY_ID — primary key of the priority assignment record.
  • IGS_EN_TIMESLOT_STUP_ID — the timeslot setup identifier that the priority belongs to; the principal filter column in most queries against this view.
  • PRIORITY_ORDER — sequencing value establishing the ranking of priorities for the timeslot.
  • PRIORITY_VALUE — the stored lookup code representing the priority.
  • DSP_PRIORITY_MEANING — the decoded lookup meaning for the priority code, the primary reason for using the view instead of the base table.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO audit columns passed through unchanged from the base table.

Common Use Cases and Queries

The view is typically queried to display or extract the priority configuration for a timeslot setup, or to validate that all stored priority values resolve to valid lookup codes.

Retrieve all priorities for a given timeslot setup, in order:

  • SELECT igs_en_timeslot_stup_id, priority_order, priority_value, dsp_priority_meaning FROM apps.igs_en_timeslot_prty_v WHERE igs_en_timeslot_stup_id = :p_stup_id ORDER BY priority_order;

Audit recent changes for integration tracking:

  • SELECT igs_en_timeslot_prty_id, igs_en_timeslot_stup_id, priority_value, dsp_priority_meaning, last_updated_by, last_update_date FROM apps.igs_en_timeslot_prty_v WHERE last_update_date >= :p_since ORDER BY last_update_date;

Detect orphaned priority rows (values present in the base table but absent from the lookup), which the inner join hides:

  • SELECT etp.igs_en_timeslot_prty_id, etp.priority_value FROM apps.igs_en_timeslot_prty etp WHERE NOT EXISTS (SELECT 1 FROM apps.igs_lookups_view lkup WHERE lkup.lookup_type = 'TIMESLOT_PRIORITY' AND lkup.lookup_code = etp.priority_value);

Because the view contains no complex aggregation or function calls on the driving table, it performs efficiently when igs_en_timeslot_stup_id is supplied as a predicate, provided the supporting index on the base table is present.