Search Results completion_due_dt

Overview

APPS.IGS_TR_ITEM_V is a reporting and integration view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environment, belonging to the ETRM (Enterprise Tracking and Reporting Management) module. The view consolidates tracking item data from the IGS_TR_ITEM table with descriptive attributes drawn from the tracking type definition and personal details of the individuals associated with each item. Its principal role is to expose the core tracking record alongside several computed date and status columns — including the tracking completion date, the days-overdue measure, and the calculated date offset derived from the tracking start date, target days, and business-days indicator.

The view is significant because it surfaces the value returned by IGS_TR_GEN_001.trkp_clc_dt_offset, the function referenced in the user's search. Rather than requiring report authors to call this PL/SQL function directly, the view presents the offset calculation as a derived column, simplifying ad-hoc querying and downstream reporting.

Underlying Base Objects

The view definition is constructed over four documented referenced objects:

• IGS_TR_ITEM (aliased tri) — the primary base table holding the tracking item records.
• IGS_PE_PERSON_BASE_V (aliased pe1) — the source-person details, joined on tri.source_person_id = pe1.person_id (+).
• IGS_PE_PERSON_BASE_V (aliased pe2) — the originator-person details, joined on tri.originator_person_id = pe2.person_id (+).
• IGS_TR_TYPE (aliased trt) — the tracking type reference table, joined on trt.tracking_type = tri.tracking_type, supplying the description column.

Both person joins are outer joins (indicated by the (+) notation), confirming that tracking items may exist without an assigned source or originator person. The view also invokes several functions in the IGS_TR_GEN_001 package — trkp_clc_dt_offset, trkp_clc_tri_cmp_dt, and trkp_clc_days_ovrdue — which are not base tables but PL/SQL logic applied at query time.

Key Columns

• TRACKING_ID, TRACKING_STATUS, TRACKING_TYPE — identity and lifecycle attributes of the tracking item.
• DESCRIPTION — human-readable tracking type description from IGS_TR_TYPE.
• SOURCE_PERSON_ID / DSP_PREFERRED_NAME2, ORIGINATOR_PERSON_ID / DSP_PREFERRED_NAME — the person identifiers and their full names.
• START_DT, TARGET_DAYS, BUSINESS_DAYS_IND, OVERRIDE_OFFSET_CLC_IND — inputs consumed by trkp_clc_dt_offset to derive the computed offset date; the overriding indicator governs whether the standard offset computation is bypassed.
• trkp_clc_dt_offset(...) — the calculated offset date, the object of the user's search.
• trkp_clc_tri_cmp_dt(...) — the computed tracking completion date.
• trkp_clc_days_ovrdue(...) — the days-overdue value, which itself nests trkp_clc_dt_offset and trkp_clc_tri_cmp_dt.
• COMPLETION_DUE_DT, SEQUENCE_IND, S_CREATED_IND, PUBLISH_IND — due date, sequencing, creation-source, and publishing flags.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

The view is typically queried to report on open tracking items, their calculated due dates, and overdue status. A representative query lists active tracking items with their computed offsets:

• SELECT tracking_id, tracking_status, dsp_preferred_name, trkp_clc_dt_offset FROM apps.igs_tr_item_v WHERE tracking_status = 'OPEN';
• Filtering by days overdue to isolate items requiring escalation, using the derived days-overdue column.
• Joining the view to reporting layers to display the offset date alongside the completion due date for reconciliation.

Because the offset and overdue columns are computed through package functions, queries against this view may carry additional execution cost, and callers should restrict result sets with appropriate predicates.