Search Results tracking_step_type




Overview
Explore in AI Chat

Overview

IGS_TR_TYPE_STEP_V is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema and primarily associated with the Oracle Student System (formerly Oracle iLearning / Oracle Higher Education, product family "IGS"). The view exposes the configuration of tracking type steps — the discrete stages that make up a tracking type used to monitor the progress of a person or entity through a defined workflow. The user search term "tracking_step_type" maps directly to the view's central column S_TRACKING_STEP_TYPE and to the lookup type TRACKING_STEP_TYPE referenced in the WHERE clause.

The view's purpose is to present tracking-type steps in a denormalized, display-ready form. It resolves the internal tracking step type code to its user-facing lookup meaning, resolves the recipient identifier to a person's number and formatted full name, and supplies a placeholder column for a DSP staff member indicator. This makes the view suitable for concurrent programs, XML Publisher (BI Publisher) reports, Oracle Forms LOVs, and inbound/outbound interfaces that need step definitions without joining multiple base tables directly.

Underlying Base Objects

Although the documented metadata lists no referenced base objects, the view text is definitive. It is defined over three sources joined in a single SELECT:

Both the person and lookup joins are outer joins (indicated by the (+) operator), so steps with no recipient or no matching lookup code remain visible. TTS.ROWID is surfaced as ROW_ID to support row-level identification in Forms or update-aware integrations.

Key Columns

Common Use Cases and Queries

Typical uses include listing all steps for a tracking type, identifying steps assigned to a specific recipient, and validating that every step type code maps to an active lookup meaning. A representative query follows:

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

To find steps with unresolved lookup or recipient data:

SELECT tracking_type_step_id, tracking_type, s_tracking_step_type, recipient_id FROM apps.igs_tr_type_step_v WHERE meaning IS NULL OR recipient_number IS NULL;

Because the view applies outer joins and does not filter by org, callers must apply ORG_ID predicates explicitly to respect operating unit security. Since only SELECT privileges are exposed via APPS, the view is safe for read-only reporting and integration use.