Search Results step_catalog_id




Overview
Explore in AI Chat

Overview

The IGS_TR_STEP_CTLG_ALL table is a core repository within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the IGS (Oracle's Student Management) product family. It functions as a master catalog or definition table for tracking steps. These steps represent discrete actions, milestones, or stages within a larger tracking process, such as a student application, enrollment, or administrative workflow. The table's primary role is to store the reusable metadata that defines each possible step, including its code, description, type, and timing parameters. The presence of the ORG_ID column indicates it is a multi-organization access control (MOAC) enabled table, allowing step definitions to be partitioned by operating unit.

Key Information Stored

The table's structure is designed to define the characteristics of a tracking step. The most critical columns include the unique identifiers STEP_CATALOG_ID (primary key) and STEP_CATALOG_CD (unique business code). The DESCRIPTION provides a human-readable name, while ACTION_DAYS stores the total number of days allocated for the step's completion. The S_TRACKING_STEP_TYPE classifies the step, and the PUBLISH_IND and CLOSED_IND columns control the step's visibility and active status within the application. Notably, the S_TRACKING_USED_BY column is documented as obsolete. Standard WHO columns (CREATED_BY, CREATION_DATE, etc.) and the ORG_ID for MOAC compliance complete the table's definition.

Common Use Cases and Queries

This table is central to configuring and reporting on process tracking. Common use cases include setting up new workflow steps, modifying timelines by adjusting ACTION_DAYS, or deactivating obsolete steps via the CLOSED_IND. For reporting, it is frequently joined to transactional tables to provide descriptive context for step instances. A fundamental query to retrieve all active, published step definitions for a specific operating unit would be:

  • SELECT STEP_CATALOG_CD, DESCRIPTION, ACTION_DAYS, S_TRACKING_STEP_TYPE FROM IGS_TR_STEP_CTLG_ALL WHERE NVL(CLOSED_IND, 'N') = 'N' AND NVL(PUBLISH_IND, 'N') = 'Y' AND ORG_ID = :org_id ORDER BY STEP_CATALOG_CD;

Another common pattern is to look up the internal ID for a known step code, which is essential for programmatic references or detailed joins: SELECT STEP_CATALOG_ID FROM IGS_TR_STEP_CTLG_ALL WHERE STEP_CATALOG_CD = '<code>';

Related Objects

Based on the provided dependency information, the IGS_TR_STEP_CTLG_ALL table is referenced by objects within the APPS schema. While specific foreign key relationships are not detailed in the excerpt, the table's design implies it is a parent table. The unique indexes on STEP_CATALOG_ID and STEP_CATALOG_CD suggest these columns are likely referenced as foreign keys in child transactional tables that record instances of these defined steps (e.g., tables storing tracking history for specific students or cases). These child tables would use STEP_CATALOG_ID to maintain referential integrity to the master definition catalog.