Search Results override_offset_clc_ind

Overview

IGS_TR_ITEM is a multi-organization secured view owned by the APPS schema within the IGS (Student System) product family of Oracle E-Business Suite. It is the runtime-facing projection of the IGS_TR_ITEM_ALL base table and exposes child tracking item records used by the Oracle iRecruitment and Student System tracking framework. Tracking items represent individual units of work assigned to a person, with attributes governing due dates, sequencing, and publication of the tracking record.

The view is defined with a Row Level Security predicate that restricts rows to the operating unit identified by the session. Specifically, the WHERE clause compares NVL(TAB.ORG_ID, ...) against the value decoded from USERENV('CLIENT_INFO'), substituting -99 when no context is set. This makes IGS_TR_ITEM the standard access path for forms, concurrent programs, and reports that must respect multi-org isolation. Because the view performs only column projection and the ORG_ID filter, it imposes no join overhead and behaves almost identically to the base table.

Underlying Base Objects

The single referenced object is IGS_TR_ITEM_ALL, the multi-organization base table that stores every tracking item regardless of operating unit. The view selects each column explicitly, plus the pseudo-column ROWID aliased as ROW_ID, which allows consumers to identify the physical row for updates or for constructing foreign-key style references without exposing ROWID directly.

The view adds no aggregation, no outer joins, and no decode logic on the business columns, so all attributes are inherited unchanged from the base table. Any DML against the base table is immediately visible through the view; conversely, the view is not updatable for ORG_ID manipulation and should be treated as read-only for reporting purposes. The documented metadata lists no additional referenced objects, confirming the view sits directly on a single base table.

Key Columns

• ROW_ID — ROWID of the underlying IGS_TR_ITEM_ALL row; useful as a unique row locator.
• ORG_ID — Operating unit identifier; drives the view's multi-org security predicate.
• TRACKING_ID — Foreign key linking the item to its parent tracking record in IGS_TR_TRACKING.
• TRACKING_STATUS — Current lifecycle state of the item.
• TRACKING_TYPE — Classifies the item, for example by activity or workflow type.
• SOURCE_PERSON_ID / ORIGINATOR_PERSON_ID — The person associated with the item and the person who raised it.
• START_DT, TARGET_DAYS, COMPLETION_DUE_DT — Scheduling attributes used to compute the due date.
• SEQUENCE_IND, BUSINESS_DAYS_IND — Control indicators for ordering and for counting calendar versus business days.
• S_CREATED_IND — Flag denoting system-created items.
• OVERRIDE_OFFSET_CLC_IND — The column associated with the user's search term. It signals whether the standard offset calculation for the due date may be overridden for this tracking item, allowing an explicitly supplied COMPLETION_DUE_DT to supersede the TARGET_DAYS-based calculation.
• PUBLISH_IND — Determines whether the item is exposed to the tracking UI.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Standard who-columns and concurrent program audit columns.

Common Use Cases and Queries

The view is typically queried to report outstanding tracking items, to drive workflow reminders, or to inspect due-date computation. The following examples illustrate typical access patterns.

List active items for the current operating unit:

• SELECT tracking_id, tracking_status, tracking_type, completion_due_dt FROM igs_tr_item WHERE publish_ind = 'Y';

Identify items whose due date has been manually overridden rather than calculated from TARGET_DAYS:

• SELECT tracking_id, target_days, completion_due_dt, override_offset_clc_ind FROM igs_tr_item WHERE override_offset_clc_ind = 'Y';

Items past their completion due date:

• SELECT tracking_id, source_person_id, completion_due_dt FROM igs_tr_item WHERE completion_due_dt < SYSDATE AND tracking_status NOT IN ('COMPLETE','CANCELLED');

Because ORG_ID filtering is enforced internally, queries against the view automatically return only rows for the session's operating unit; reports that span organizations must be executed with the appropriate multi-org context set or must target IGS_TR_ITEM_ALL directly where cross-org visibility is permitted.