Results for “tracking_id”

50+ results




Overview
Explore in AI Chat

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

Overview

IGS_TR_STEP_GRP_LMT is a configuration table within the Oracle E-Business Suite IGS (Student System) product family. Its documented purpose is to store the Step Group Limit associated with the Step Group ID of Tracking Steps. In the ETRM 12.1.1 physical schema the table is owned by the IGS schema and contains eight columns. The object is flagged as obsolete in the supplied metadata, and the implementation note records that it is "Not implemented in this database," meaning it is documented for completeness but carries no active rows or runtime dependency in the referenced environment.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. In pure Data Vault terms this suggests the object behaves as neither a strong hub, link, nor satellite tied to surrounding referential structures; it holds its own attribute payload and is not modelled as a dependent child of a shared business key. Modelling guidance would therefore treat TRACKING_ID and STEP_GROUP_ID as a composite business key candidate (the unique index IGS_TR_STEP_GRP_LMT_U1), with STEP_GROUP_LIMIT and the standard audit columns forming the descriptive satellite attributes. Because the table is obsolete, this classification is a historical modelling suggestion rather than an active integration contract.

Key Information Stored

The most significant columns in the documented eight-column schema are:

  • TRACKING_ID — part of the composite primary key and unique index; identifies the tracking context for which the step group limit applies.
  • STEP_GROUP_ID — part of the composite primary key and unique index; identifies the step group within the tracking structure.
  • STEP_GROUP_LIMIT — the limit value held for the referenced tracking and step group combination; this is the principal business attribute of the table.
  • CREATED_BY, CREATION_DATE — standard EBS audit columns recording first insertion.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording last modification and the responsible session.

The surrogate primary key is IGS_TR_STEP_GRP_LMT_PK, defined over (TRACKING_ID, STEP_GROUP_ID). The business-key candidate is presented as the unique index IGS_TR_STEP_GRP_LMT_U1, also defined over (TRACKING_ID, STEP_GROUP_ID). The distinction is largely nominal here: the PK and the unique index share the same underlying columns, so no separate surrogate is documented beyond the composite itself. No foreign key columns beyond the two keyed identifiers are recorded in the supplied metadata.

Common Use Cases and Queries

Because the table is obsolete and unimplemented in the reference database, practical use cases are limited to historical research, migration analysis, and schema comparison across environments. A typical lookup verifies whether a limit is defined for a given tracking and step group pair:

  • Configuration review: select TRACKING_ID, STEP_GROUP_ID, STEP_GROUP_LIMIT from IGS_TR_STEP_GRP_LMT where TRACKING_ID = :p_tracking_id to confirm the limit applied to a step group.
  • Change auditing: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to trace who altered a limit and when, using the standard EBS audit columns.
  • Migration scoping: query the table to confirm whether legacy step group limits were carried forward before decommissioning IGS tracking objects.
  • Schema reconciliation: compare column presence and the PK/U1 index definitions between 12.1.1 and 12.2.2 environments where the object is documented.

Reporting should treat the table as historical reference data only, given the obsolete designation.

Related Objects

Given the standalone Data Vault classification and the absence of documented foreign keys, related objects are inferred from shared key columns and the IGS tracking schema. The most significant are the tracking-step parent tables keyed by TRACKING_ID and the step group definition tables keyed by STEP_GROUP_ID, joined on those columns. Additionally, the IGS Student System tracking APIs and concurrent programs that read or maintain step group configuration reference this table through the same composite key. Standard EBS audit views and the FND audit infrastructure apply to its audit columns.