Search Results sequence_ind




Overview

The IGS_TR_TYPE view is a critical data object within the Oracle E-Business Suite (EBS) Student System (IGS) module, versions 12.1.1 and 12.2.2. It provides a filtered, multi-organization (Multi-Org) aware perspective on the underlying base table, IGS_TR_TYPE_ALL. The view's primary function is to expose master data for different tracking types used to monitor and manage various student-related processes or items, such as applications, inquiries, or service requests. The view's WHERE clause logic ensures data security by restricting rows based on the ORG_ID (Operating Unit identifier) derived from the user's session context (USERENV('CLIENT_INFO')), thereby enforcing a fundamental EBS security model. This allows different business units within an institution to maintain and view only their own tracking type definitions.

Key Information Stored

The view presents a comprehensive set of columns that define the characteristics and behavior of a tracking type. Key columns include:

  • TRACKING_TYPE & DESCRIPTION: The unique code and descriptive name for the tracking type.
  • S_TRACKING_TYPE: A system-defined classification for the tracking type, likely driving specific application behavior.
  • TARGET_DAYS: The expected number of days for completion of items under this tracking type.
  • SEQUENCE_IND, BUSINESS_DAYS_IND, CLOSED_IND, PUBLISH_IND: Important flags controlling functionality. These indicate if sequence numbering is used, if target days are calculated using business days only, if the type is closed for new assignments, and if the type is published for general use, respectively.
  • ORG_ID: The Operating Unit identifier, central to the view's row-level security.
  • Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are also included.

Common Use Cases and Queries

This view is primarily used for setup validation, operational reporting, and as a source for List of Values (LOV) in application forms. Common scenarios include generating a list of all active tracking types for a given operating unit to configure workflow steps, or reporting on target service levels. A typical query would filter on key indicators and the session's ORG_ID.

Sample Query: To retrieve all published, open tracking types that use business-day calculations for the current operating unit:
SELECT tracking_type, description, target_days
FROM apps.igs_tr_type
WHERE publish_ind = 'Y'
AND closed_ind = 'N'
AND business_days_ind = 'Y'
ORDER BY description;

This view is also central in joins for transactional reporting, linking tracking type metadata to actual tracked items (e.g., in IGS_TR_ITEM or related tables) to analyze performance against targets.

Related Objects

The IGS_TR_TYPE view is intrinsically linked to several other EBS objects within the Student System module. Its direct base table is IGS_TR_TYPE_ALL, which stores the physical data for all operating units. This view is a likely source for foreign key references in transactional tables that assign a tracking type to a specific item or case, such as IGS_TR_ITEM or similar. It may also be referenced by other setup views or public APIs (e.g., IGS_TRACKING_PUB) that provide programmatic access to tracking functionality. The presence of the S_TRACKING_TYPE column suggests a relationship with a lookup table defining valid system types, such as IGS_LOOKUPS_VIEW for the relevant lookup type.