Search Results desc_used_by




Overview
Explore in AI Chat

Overview

IGS_TR_TYPE_V is a seeded Oracle E-Business Suite view owned by the APPS schema and defined over the IGS (Intellectual Property/Sponsored Projects) product family. It exposes the definition of tracking types — configurable categories used to group and monitor tracked items such as deliverables, milestones, or research obligations — and enriches each row with the descriptive meaning of its seeded tracking type code. The view is a reporting and integration layer rather than a transactional store; it presents a clean, already-joined projection of the base tracking type table so that developers, reports, and interfaces do not need to reproduce the lookup join themselves.

Because the view carries ORG_ID, it is multi-org aware and is intended to be queried in the context of the operating unit through which the tracking type was defined. This makes it suitable for both Oracle Reports/BI Publisher datasets and for inbound or outbound integration programs that need to resolve a tracking type code into a human-readable description.

Underlying Base Objects

The view is defined by joining two base objects: IGS_TR_TYPE (aliased TT), the table holding the tracking type definitions, and IGS_LOOKUP_VALUES (aliased LKUP), the standard lookup table. The join condition is:

The view also projects TT.ROWID as ROW_ID, which permits row-based navigation and supports tools that rely on ROWID for updatable or identifiable result sets. All other columns are drawn directly from IGS_TR_TYPE, with the addition of LKUP.MEANING surfaced as S_TRACKING_TYPE_DESC. Two unnamed NULL placeholders are included in the select list, which is common in seeded views retained for backward compatibility with prior column orderings. No additional documented base objects appear in the ETRM metadata; the view is limited to the two tables above.

Key Columns

  • ROW_ID — the ROWID of the underlying IGS_TR_TYPE row.
  • ORG_ID — operating unit identifier; drives multi-org filtering.
  • TRACKING_TYPE — the tracking type value itself (the business key).
  • DESCRIPTION — user-facing description of the tracking type.
  • S_TRACKING_TYPE — the seeded system tracking type code; joined to the lookup.
  • S_TRACKING_TYPE_DESC — the lookup MEANING for the seeded code, providing the translated/displayable name.
  • TARGET_DAYS — number of days targeted for the tracking type (e.g., expected response or completion window).
  • SEQUENCE_IND — indicates whether sequential processing or ordering applies.
  • BUSINESS_DAYS_IND — indicates whether TARGET_DAYS is counted in business days rather than calendar days.
  • CLOSED_IND — whether the tracking type is closed/inactive.
  • PUBLISH_IND — whether the tracking type is published/available for use.
  • Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include validating that a tracking type exists before assigning it, populating a value set or LOV, and producing configuration listings per operating unit.

List active tracking types for an operating unit:

  • SELECT tracking_type, description, s_tracking_type_desc, target_days, business_days_ind FROM igs_tr_type_v WHERE org_id = :p_org_id AND NVL(closed_ind,'N') = 'N' ORDER BY tracking_type;

Resolve a seeded code to its display meaning:

  • SELECT tracking_type, s_tracking_type_desc FROM igs_tr_type_v WHERE s_tracking_type = :p_code;

Because the view already performs the lookup join, it should be preferred over ad-hoc joins to IGS_LOOKUP_VALUES for reporting consistency, and any multi-org query must constrain ORG_ID appropriately.