Results for “igs_tr_type”

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

Overview

The IGS_TR_TYPE view is a secured, organization-aware reporting object within the Oracle E-Business Suite Student System (IGS) product family. It exposes configuration data for tracking types — the categories used by institutions to monitor and sequence student-related activities such as admissions follow-up, document collection, enrollment checkpoints, and communication milestones. Each tracking type defines a target completion window (expressed in days), whether that window counts business or calendar days, and whether the type is open or closed for use.

Because it is a view rather than a base table, IGS_TR_TYPE does not store data itself; it presents a filtered, column-aliased projection of an underlying _ALL table and applies an operating-unit (ORG_ID) security predicate. This makes it the preferred object for forms, concurrent programs, and ad hoc SQL that must respect multi-org access rules without re-implementing them. In Oracle EBS 12.1.1 and 12.2.2, the view is owned by the APPS schema and registered as VALID, meaning it compiles cleanly against its base object and is safe to reference in reporting and integration logic.

Underlying Base Objects

The ETRM documentation for this object records the view text as selecting from IGS_TR_TYPE_ALL TAB. The _ALL suffix is the standard Oracle EBS multi-org convention: the base table holds rows for every operating unit, while the view narrows the result set to the operating unit of the current session. The relationship is therefore strictly one-to-one on a row basis — every row visible through IGS_TR_TYPE corresponds to exactly one row in IGS_TR_TYPE_ALL, with the same column values but renamed and reordered for reporting convenience.

The documented metadata lists no additional referenced base objects. In practice, IGS_TR_TYPE_ALL is itself the transactional master for tracking type definitions, and no join to a separate description or lookup table appears in the documented view text. The ROWID of the underlying _ALL row is passed through as ROW_ID, which allows the view to be used in certain update-capable contexts and to support row identification in exported data sets.

Key Columns

• ROW_ID — the ROWID of the base row in IGS_TR_TYPE_ALL; useful as a unique row identifier in extracts.
• ORG_ID — the operating unit that owns the tracking type. This column drives the security filter in the view's WHERE clause.
• TRACKING_TYPE — the primary business key, the code identifying the tracking type.
• DESCRIPTION — the user-facing name or explanatory text for the tracking type.
• S_TRACKING_TYPE — the short or secondary representation of the tracking type, typically used in constrained display contexts.
• TARGET_DAYS — the number of days allowed to complete the tracked activity. This is the column most directly associated with the search term "target_days" and is the core planning value used to compute due dates.
• BUSINESS_DAYS_IND — an indicator determining whether TARGET_DAYS is counted in business days (excluding weekends and holidays) or in calendar days.
• SEQUENCE_IND — indicates whether the tracking type participates in a defined sequence of tracking steps.
• CLOSED_IND — flags whether the tracking type is retired or otherwise unavailable for new use.
• PUBLISH_IND — controls whether the tracking type is published or exposed to downstream consumers such as self-service pages or integration interfaces.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns describing who created and last modified the row and when.

Common Use Cases and Queries

The view is typically queried to list the tracking types available to the current operating unit and to retrieve their target windows. A representative query is:

• SELECT tracking_type, description, target_days, business_days_ind FROM igs_tr_type WHERE closed_ind = 'N' ORDER BY tracking_type; — returns active tracking types with their target windows for the session's operating unit.
• SELECT tracking_type, target_days FROM igs_tr_type WHERE target_days IS NOT NULL AND business_days_ind = 'Y'; — isolates business-day-based tracking types for due-date calculations.
• SELECT org_id, COUNT(*) FROM igs_tr_type GROUP BY org_id; — confirms which operating units have tracking type data defined, useful during multi-org validation.
• SELECT tracking_type, target_days, closed_ind, publish_ind FROM igs_tr_type WHERE publish_ind = 'Y'; — identifies tracking types eligible for publication to self-service or integration endpoints.

Because the ORG_ID predicate is embedded in the view definition, callers do not add their own operating-unit filter; doing so is redundant and, if wrong, will simply return no rows. For cross-operating-unit reporting, consumers must query IGS_TR_TYPE_ALL directly or run under a session whose client information is set appropriately. Practically, IGS_TR_TYPE functions as the canonical, security-compliant source for tracking type configuration and the TARGET_DAYS value used throughout student tracking workflows.