Results for “igs_tr_step_ctlg_all_pk”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_TR_STEP_CTLG_ALL is a catalog table within the Oracle EBS IGS — Student System product family, historically shipped under the Oracle Student System (OSS) / iGSM academic module and now classified as obsolete in current ETRM documentation. The table serves as the repository for tracking steps — that is, it holds the master catalog of step definitions used to drive student-tracking workflows, transcripts, and administrative progression milestones. Each row represents one step catalog entry that other IGS transactional tables reference by code or identifier.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as hub-leaning. Its stable, non-volatile unique business key (STEP_CATALOG_CD) and multiple inbound references from dependent tables make it a natural candidate for a hub entity, with surrounding descriptive attributes possibly modeled as a satellite if historization were required. This is a heuristic suggestion rather than a documented EBS design intent.

Note the ETRM implementation flag: "Not implemented in this database." The table is documented for Oracle EBS 12.1.1 and 12.2.2 reference purposes, with 14 physical columns and owner IGS.

Key Information Stored

The table carries 14 documented columns. The most significant are:

• STEP_CATALOG_ID — surrogate primary key, enforced by IGS_TR_STEP_CTLG_ALL_PK and mirrored by unique index IGS_TR_STEP_CTLG_ALL_U1.
• STEP_CATALOG_CD — the business-key candidate, enforced by unique index IGS_TR_STEP_CTLG_ALL_UK (also listed as _U2). This is the primary target of the search term igs_tr_step_ctlg_all_uk.
• DESCRIPTION — human-readable name of the step catalog entry.
• ACTION_DAYS — the actionable duration or lead time associated with the step.
• S_TRACKING_STEP_TYPE — classification of the tracking step.
• S_TRACKING_USED_BY — indicates the consumer or context that utilizes the tracking step.
• PUBLISH_IND — publication flag controlling visibility.
• CLOSED_IND — indicates whether the catalog entry is closed/inactive.
• ORG_ID — multi-org operating unit discriminator.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage involves resolving a step catalog code to its surrogate ID, filtering by tracking type, or reporting active catalog entries per operating unit.

• Lookup a step catalog by business key: SELECT * FROM igs_tr_step_ctlg_all WHERE step_catalog_cd = :cd;
• List active, published steps for an operating unit: SELECT step_catalog_cd, description FROM igs_tr_step_ctlg_all WHERE org_id = :org AND publish_ind = 'Y' AND closed_ind = 'N';
• Join to dependent transaction steps to trace progression: SELECT t.* FROM igs_tr_step t JOIN igs_tr_step_ctlg_all c ON t.step_catalog_cd = c.step_catalog_cd;
• Reporting: catalog maintenance reports, step-type enumeration, and duration audits using ACTION_DAYS.

Because the table is marked obsolete and not implemented, validation queries should first confirm its existence via DBA_TABLES in a given environment.

Related Objects

The documented foreign keys and inbound references establish these significant dependencies:

• IGS_TR_STEP — joins on STEP_CATALOG_CD; holds the transactional step instances.
• IGS_TR_TYPE_STEP_ALL — joins on STEP_CATALOG_CD; associates catalog entries with step types.
• IGS_AD_PER_STM_TYP — references STEP_CATALOG_CD; relates admission/person statement types to steps.
• IGS_TR_STP_CTL_TYPE — references STEP_CATALOG_ID and is itself a foreign source for IGS_TR_STEP_CTLG_ALL; defines step control types.

These four tables represent the core referential neighborhood; broader usage should be validated against environment-specific IGS dictionaries.