Search Results dsp_preferred_name




Overview
Explore in AI Chat

Overview

IGS_TR_TYPE_STEP_V is a PL/SQL view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. It exposes the ordered steps that make up a tracking type — the configurable workflow of actions applied to a person, organization, or applicant record within Oracle Student System tracking functionality. Each row represents a single tracking type step, enriched with the preferred name and person number of the responsible recipient (the staff member or person assigned to perform the step) and with the decoded lookup meaning of the step type.

Because the view is a denormalized, ready-to-query projection rather than a base table, it is intended for reporting, OBIEE/BI Publisher extracts, and integration interfaces that need to surface tracking step definitions together with human-readable recipient and step-type descriptions. The column alias DSP_PREFERRED_NAME (mapped from PE.FULL_NAME) indicates that the view was designed to feed a display layer — commonly an Oracle Forms or OAF-based "Display" (DSP) block — where the preferred name of the assigned recipient must be presented alongside the step configuration.

Underlying Base Objects

The view text joins three documented sources:

All three joins are Oracle-style outer joins ((+)), confirming that the view is resilient to missing recipient or lookup reference data. The ROW_ID column is carried from TTS.ROWID, although in EBS 12.2.2 the ROWID may not be stable for tables in tablespaces with compression or for editioned objects; consumers relying on ROW_ID should validate against the actual base table.

Key Columns

  • ROW_ID — ROWID of the underlying IGS_TR_TYPE_STEP row; used by the display layer for direct row updates.
  • ORG_ID — operating unit / business unit identifier, supporting multi-org security.
  • TRACKING_TYPE and TRACKING_TYPE_STEP_ID — the tracking type and its child step identifier; the natural key of the row.
  • TRACKING_TYPE_STEP_NUMBER — the sequence in which the step executes within the tracking type.
  • DESCRIPTION — free-text description of the step.
  • S_TRACKING_STEP_TYPE and DESC_STEP_TYPE — the lookup code and its decoded meaning for the step category.
  • ACTION_DAYS — number of days allowed or expected for step completion, used for SLA/reminder logic.
  • RECIPIENT_ID and RECIPIENT_NUMBER — the person identifier and person number of the assigned recipient.
  • DSP_STAFF_MEMBER_IND — always NULL as defined in the view text; retained for interface compatibility.
  • DSP_PREFERRED_NAME — the recipient's full/preferred name, the column most often used in display and report layouts.
  • STEP_CATALOG_CD, STEP_GROUP_ID, PUBLISH_IND — catalog reference, grouping, and publication control for the step.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO audit columns.

Common Use Cases and Queries

The view is typically queried to list the steps of a tracking type with their recipient names, or to drive a display block/LOV that requires the preferred name of the assigned recipient.

List all steps for a tracking type, ordered by step number, showing the recipient's preferred name:

SELECT tracking_type_step_number,
       description,
       desc_step_type,
       action_days,
       recipient_number,
       dsp_preferred_name,
       publish_ind
FROM   apps.igs_tr_type_step_v
WHERE  tracking_type = :p_tracking_type
ORDER  BY tracking_type_step_number;

Find tracking steps assigned to a specific recipient, matching on the display column. Note that dsp_preferred_name is the person's full name, so it is best matched with an equality or LIKE filter, or joined back to the person base view for more precise identification:

SELECT tracking_type,
       tracking_type_step_number,
       description,
       dsp_preferred_name
FROM   apps.igs_tr_type_step_v
WHERE  recipient_id = :p_person_id
ORDER  BY tracking_type, tracking_type_step_number;

Report on unpublished steps or steps whose step type has not been decoded:

SELECT tracking_type,
       tracking_type_step_number,
       s_tracking_step_type,
       desc_step_type
FROM   apps.igs_tr_type_step_v
WHERE  publish_ind = 'N'
   OR  desc_step_type IS NULL;

Because IGS_TR_TYPE_STEP_V is a view and not a table, it carries no DML of its own; updates must be performed against IGS_TR_TYPE_STEP using ROW_ID or the primary key. Standard EBS multi-org and function security rules apply, and ORG_ID should be constrained where the tracking configuration is organization-specific. Reporting consumers should treat the view as read-only and be aware that DESC_STEP_TYPE, RECIPIENT_NUMBER, and DSP_PREFERRED_NAME may return NULL by design due to the outer joins.