Search Results by_pass_ind

Overview

IGS_TR_STEP_V is an APPS-owned supplementary view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 schemas, defined under the FND Design Data object IGS.IGS_TR_STEP_V and registered as VALID. It presents a denormalized, forms-oriented projection of the academic tracking step data used by the Student Systems / Student Records (IGS) family of products, which supports admissions, progression, and related administrative processes. Because it is a supplementary view created expressly to simplify Oracle Forms coding, Oracle explicitly warns that it should not be queried or altered for transactional purposes, and its structure may change dramatically in subsequent minor or major releases.

Practically, the view joins the core tracking step table to lookup, person, and item data so that a single row describes a tracking step together with the recipient details and the human-readable system step type. The presence of the DESC_STEP_TYPE column explains the common search term "desc_step_type": report and form developers look for the descriptive label of S_TRACKING_STEP_TYPE, which is the system tracking step type code. This makes the view attractive for read-only reporting on tracking progress, deadlines, and overdue actions.

Underlying Base Objects

The documented dependency list shows that IGS_TR_STEP_V is built on the following objects:

• APPS.IGS_TR_STEP — the primary tracking step table, supplying step identifiers, numbering, description, dates, completion and bypass indicators, and the S_TRACKING_STEP_TYPE code.
• APPS.IGS_TR_ITEM — the tracking item table, providing the tracking context (TRACKING_ID) and related attributes.
• APPS.IGS_PE_PERSON_BASE_V — the person base view, used to resolve recipient identity, including DSP_PREFERRED_NAME (the recipient's full name).
• APPS.IGS_LOOKUPS_VIEW — the lookup view, used to derive DESC_STEP_TYPE, the description of the system step type.
• APPS.IGS_TR_GEN_001 — a generated database object referenced with dependent code, typically a packaged procedure or function supporting the view's logic.

The documented metadata lists no explicitly documented base tables beyond those references, but the column comments confirm that DESCRIPTION and S_TRACKING_STEP_TYPE originate from TRACKING_STEP, and that DESC_STEP_TYPE is the description of the system step type.

Key Columns

• TRACKING_ID / TRACKING_STEP_ID / TRACKING_STEP_NUMBER — identify the tracking record and the ordinal step within it.
• DESCRIPTION — the step description from TRACKING_STEP.
• S_TRACKING_STEP_TYPE / DESC_STEP_TYPE — the system step type code and its decoded description, the latter being the column most often sought when searching "desc_step_type".
• COMPLETION_DT, ACTION_DT, ACTION_DAYS, OVERDUE_DAYS — date and elapsed-time measurements supporting deadline and follow-up reporting.
• STEP_COMPLETION_IND, BY_PASS_IND — flags indicating whether a step was completed or bypassed.
• RECIPIENT_ID, RECIPIENT_NUMBER, DSP_PREFERRED_NAME — recipient identity, resolved through IGS_PE_PERSON_BASE_V.
• STEP_CATALOG_CD, STEP_GROUP_ID, PUBLISH_IND — catalog grouping and publication attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical uses include tracking-step status reports, overdue-step aging, recipient notification extractsto feeder views such as IGS_AD_MISSING_ITEMS_LETTER_V and IGS_AD_POSTADM_MISS_ITM_LTR_V, and ad hoc operational queries. A representative query grouping by system step type is:

SELECT s_tracking_step_type,
       desc_step_type,
       COUNT(*) AS step_count
FROM   apps.igs_tr_step_v
GROUP  BY s_tracking_step_type, desc_step_type
ORDER  BY s_tracking_step_type;

For overdue actions by recipient, the DSP_PREFERRED_NAME and OVERDUE_DAYS columns are combined:

SELECT tracking_id,
       tracking_step_number,
       description,
       desc_step_type,
       dsp_preferred_name,
       overdue_days
FROM   apps.igs_tr_step_v
WHERE  overdue_days > 0
AND    step_completion_ind = 'N'
ORDER  BY overdue_days DESC;

Because this is a supplementary view with no documented base tables in certain ETRM releases and explicit Oracle cautions against production querying, organizations should treat it as a development aid rather than a stable integration interface, validating behavior against the base objects (IGS_TR_STEP, IGS_TR_ITEM, and their lookups) before relying on it in critical reports.