Search Results igs_tr_tstp_grp_lmt

Overview

IGS_TR_TSTP_GRP_LMT is a transactional configuration table in the Oracle EBS IGS — Student System product (also marketed as Oracle Student System / Oracle Higher Education). It stores the Step Group Limit associated with a Step Group ID for Tracking Step Types. In practical terms, the table enforces or records cap values applied to groups of tracking steps within the student tracking framework, where tracking types drive progress-tracking workflows such as admissions checklists, enrollment milestones, or academic requirement fulfillment.

The object resides in the IGS schema, holds status VALID, and is documented in ETRM for both 12.1.1 and 12.2.2. Its documented physical schema comprises eight columns and one primary key, IGS_TR_TSTP_GRP_LMT_PK, defined over (TRACKING_TYPE, STEP_GROUP_ID). A unique index, IGS_TR_TSTP_GRP_LMT_U1, exists over the same column pair, which effectively makes the composite a business-key candidate. Under the heuristic Data Vault classification mined from the FK structure, the table is characterized as standalone. As a modeling suggestion, it can be treated as a small reference or satellite-style entity keyed by its composite business key, since no dependent children were documented.

Key Information Stored

The documented column set is compact. The most significant columns are:

• TRACKING_TYPE — Identifies the tracking type to which the step group limit applies. Part of the composite primary key (IGS_TR_TSTP_GRP_LMT_PK) and of the unique index IGS_TR_TSTP_GRP_LMT_U1.
• STEP_GROUP_ID — Identifies the specific step group whose limit is being recorded. The second component of both the primary key and the unique index, and the column most frequently used in joins to the step-group definition.
• STEP_GROUP_LIMIT — The numeric limit value defined for the step group, i.e., the effective cap stored for the (TRACKING_TYPE, STEP_GROUP_ID) combination. This is the principal payload column of the table.
• CREATED_BY — Standard EBS WHO column recording the user who inserted the row.
• CREATION_DATE — Standard WHO column recording insertion timestamp.
• LAST_UPDATED_BY — Standard WHO column recording the last user to modify the row.
• LAST_UPDATE_DATE — Standard WHO column recording the last modification timestamp; commonly used for incremental extracts and audit reporting.
• LAST_UPDATE_LOGIN — Standard WHO column capturing the login session associated with the last update.

There is no separate single-column surrogate key: the primary key is composite and coincides with the unique business key. Consequently, TRACKING_TYPE and STEP_GROUP_ID together uniquely determine a row, and STEP_GROUP_LIMIT plus the five WHO audit columns complete the documented structure.

Common Use Cases and Queries

Typical usage centers on retrieving the configured limit for a tracking type and step group, validating that limits exist for all active groups, and auditing configuration changes.

• Point lookup of a limit: SELECT step_group_limit FROM igs.igs_tr_tstp_grp_lmt WHERE tracking_type = :p_tracking_type AND step_group_id = :p_step_group_id;
• Listing all limits for a tracking type: SELECT step_group_id, step_group_limit FROM igs.igs_tr_tstp_grp_lmt WHERE tracking_type = :p_tracking_type ORDER BY step_group_id;
• Audit/incremental extract: SELECT * FROM igs.igs_tr_tstp_grp_lmt WHERE last_update_date >= :p_since;
• Finding who changed limits: join the WHO columns to FND_USER on LAST_UPDATED_BY to attribute configuration changes.
• Reporting: compare configured limits against actual step-group usage to identify groups approaching or exceeding their cap.

Because the table has no documented FK children, queries tend to be lookups driven by TRACKING_TYPE, filtered or joined further by STEP_GROUP_ID. In migration or upgrade testing between 12.1.1 and 12.2.2, row-count and limit-value reconciliation on this table is a straightforward validation step.

Related Objects

The documented relationship data classifies this object as standalone, so no enforced FK parents or children were mined. The most significant related objects are therefore those joined through the composite business key or the WHO audit columns:

• IGS_TR_TSTP_GRP_LMT_PK / IGS_TR_TSTP_GRP_LMT_U1 — the primary key constraint and unique index over (TRACKING_TYPE, STEP_GROUP_ID).
• Step group definition tables in the IGS tracking-step family — joined on STEP_GROUP_ID to resolve group names and attributes.
• Tracking type definition tables in IGS — joined on TRACKING_TYPE to resolve the tracking type description.
• IGS_TR_STEP / IGS_TR_TSTP family tables — the tracking step and tracking step type entities that provide context for the groups being limited.
• FND_USER — joined on CREATED_BY or LAST_UPDATED_BY for audit reporting.
• FND_APPLICATION / FND_PRODUCT_INSTALLATIONS — used to confirm the IGS product and schema registration.

Given the limited documented relationship data, joins should be confirmed against the actual 12.1.1 or 12.2.2 instance metadata before being relied upon in production reporting.