Search Results tracking_type_step_number

Overview

The IGS_TR_TYPE_STEP view is a reporting and integration object within the IGS – Student System product family in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It is owned by the APPS schema and holds a VALID status in the data dictionary. Functionally, the view exposes the ordered sequence of steps that make up a tracking type — the configurable workflow stages used by the Student System to monitor and progress activities such as admissions processing, applicant follow-up, and enrollment milestones.

Unlike a base table, IGS_TR_TYPE_STEP is a security- and organization-aware projection. It does not store data of its own; instead it presents a filtered, denormalized read of the underlying IGS_TR_TYPE_STEP_ALL table. Its principal role is to enforce multi-org (Operating Unit) access rules at query time, so that reports, concurrent programs, and integration extracts automatically return only the rows relevant to the caller's current organization context. This makes the view a preferred access point over the base table for read-only reporting.

Underlying Base Objects

The view text confirms that IGS_TR_TYPE_STEP selects from a single underlying object: IGS_TR_TYPE_STEP_ALL (referenced internally by the alias TAB). The _ALL suffix indicates that the base table stores rows across all operating units, each tagged with an ORG_ID. The view adds a WHERE clause that compares TAB.ORG_ID against the organization identifier derived from the session's client information.

Specifically, the predicate uses USERENV('CLIENT_INFO') to extract the current ORG_ID, and applies an NVL-based default of -99 when no client information is present. This is a classic Oracle EBS multi-org (MOAC) filter pattern. The effect is that a session operating under a given Operating Unit sees that unit's step definitions plus any rows with a null or sentinel ORG_ID (-99), which are treated as globally shared. No other base objects, synonyms, or joined tables are documented for this view.

Key Columns

• ROW_ID — The physical row identifier (ROWID) of the underlying table row.
• ORG_ID — The Operating Unit that owns the step definition; drives the multi-org filter.
• TRACKING_TYPE — The tracking type to which the step belongs.
• TRACKING_TYPE_STEP_ID — Primary key of the step record.
• TRACKING_TYPE_STEP_NUMBER — The ordinal position of the step within its tracking type sequence.
• DESCRIPTION — Textual label describing the step.
• S_TRACKING_STEP_TYPE — The step category/type indicator.
• ACTION_DAYS — Number of days associated with the step's action or due-date logic.
• RECIPIENT_ID — Identifier of the recipient associated with the step.
• STANDARD WHO COLUMNS — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN for audit tracking.
• STEP_CATALOG_CD and STEP_GROUP_ID — Catalog code and grouping reference for the step.
• PUBLISH_IND — Flag indicating whether the step is published/active.

Common Use Cases and Queries

Typical uses include building tracking-type configuration reports, validating step sequences, and extracting step metadata for integration or migration scripts. Queries should not filter ORG_ID manually, since the view already applies the MOAC predicate:

• List steps for a tracking type: SELECT TRACKING_TYPE_STEP_NUMBER, DESCRIPTION, ACTION_DAYS FROM IGS_TR_TYPE_STEP WHERE TRACKING_TYPE = :p_type ORDER BY TRACKING_TYPE_STEP_NUMBER;
• Retrieve published steps only: add WHERE PUBLISH_IND = 'Y'.
• Audit recently changed definitions: filter on LAST_UPDATE_DATE.

Because the view returns only the current Operating Unit's data, always run such queries from the correct organization context or from a MOAC-initialized session.