Search Results igs_tr_step_grp_lmt_u1

Overview

IGS.IGS_TR_STEP_GRP_LMT is a transactional table in the Oracle E-Business Suite 12.1.1 / 12.2.2 IGS (Intelligent Grants / Tracking) schema. It stores the Step Group Limit defined for the Step Group ID associated with Tracking Steps. In practice, the table serves as a configuration and control store that caps or bounds the behavior of a logical grouping of tracking steps belonging to a given tracking item.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, reflecting its role as a transactional data object rather than a reference or setup table. It is documented in the ETRM as VALID and is exposed to the APPS schema through the synonym IGS_TR_STEP_GRP_LMT, which allows custom reporting and data extraction from PL/SQL, concurrent programs, and BI Publisher reports.

From a Data Vault modeling perspective, the metadata classifies this object as standalone. A reasonable modeling suggestion is to treat it as a satellite-like detail table anchored on the combination of TRACKING_ID and STEP_GROUP_ID, since it holds descriptive and controlling attributes (notably STEP_GROUP_LIMIT) that describe a relationship between a tracking item and a step group rather than acting as a pure hub or link.

Key Information Stored

The table contains eight documented columns. The most significant are:

• TRACKING_ID — NUMBER. Identifies the Tracking Item to which the step group limit applies. Part of the composite primary key and the unique index.
• STEP_GROUP_ID — NUMBER(10). Identifies the Step Group for the tracking steps. This is the exact column the user searched for. It is the second component of the composite primary key.
• STEP_GROUP_LIMIT — NUMBER(10). The substantive business payload: the limit value enforced for the step group. This is the attribute most frequently queried and reported on.
• CREATED_BY — NUMBER(15). Standard WHO column capturing the user who created the row.
• CREATION_DATE — DATE. Standard WHO column recording row creation timestamp.
• LAST_UPDATED_BY — NUMBER(15). Standard WHO column capturing the last user to modify the row.
• LAST_UPDATE_DATE — DATE. Standard WHO column recording the last modification timestamp.
• LAST_UPDATE_LOGIN — NUMBER(15). Standard WHO column recording the login context of the last update.

The primary key IGS_TR_STEP_GRP_LMT_PK is defined on (TRACKING_ID, STEP_GROUP_ID). A unique index, IGS_TR_STEP_GRP_LMT_U1, is defined on the same two columns in the APPS_TS_TX_IDX tablespace, confirming that the combination of TRACKING_ID and STEP_GROUP_ID is the business key. Because the primary key is composite and built entirely from business identifiers, there is no separate surrogate key column; STEP_GROUP_LIMIT is the sole non-key descriptive attribute.

Common Use Cases and Queries

Typical uses include validating that a step group has not exceeded its configured limit, reporting on limits by tracking item, and auditing changes to limits over time using WHO columns.

Retrieve the limit for a specific tracking item and step group:

• SELECT tracking_id, step_group_id, step_group_limit FROM igs.igs_tr_step_grp_lmt WHERE tracking_id = :tracking_id AND step_group_id = :step_group_id;

List all step group limits for a tracking item, ordered by step group:

• SELECT step_group_id, step_group_limit FROM igs.igs_tr_step_grp_lmt WHERE tracking_id = :tracking_id ORDER BY step_group_id;

Audit recent changes to limits:

• SELECT tracking_id, step_group_id, step_group_limit, last_updated_by, last_update_date FROM igs.igs_tr_step_grp_lmt WHERE last_update_date >= :from_date;

Because STEP_GROUP_LIMIT is the only meaningful payload column, reporting joins typically focus on enriching this value with tracking item and step group descriptive data from related IGS tables.

Related Objects

Per the ETRM documentation, IGS.IGS_TR_STEP_GRP_LMT does not reference any other database object via declared foreign keys. It is referenced by the APPS synonym IGS_TR_STEP_GRP_LMT, which is the normal entry point for custom code and reports. Because the relationship metadata identifies the object as standalone, join relationships to parent tracking and step group definitions are implicit rather than enforced by constraints. The most significant related objects are therefore:

• APPS.IGS_TR_STEP_GRP_LMT — the APPS-schema synonym used by all application and custom SQL, defined over the IGS owner table.
• IGS_TR_STEP_GRP_LMT_PK — the composite primary key index on (TRACKING_ID, STEP_GROUP_ID).
• IGS_TR_STEP_GRP_LMT_U1 — the unique index on (TRACKING_ID, STEP_GROUP_ID) in APPS_TS_TX_IDX, representing the business key.
• Parent tracking item and step group definition tables in the IGS schema, joined on TRACKING_ID and STEP_GROUP_ID respectively, which provide the descriptive context for the limit values stored here.

Custom reporting should always query through the APPS synonym to remain consistent with standard EBS schema access conventions.