Search Results igr_i_info_types_v




Overview
Explore in AI Chat

Overview

IGR_I_INFO_TYPES_V is a VALID database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the IGS (Student System) product family and is designed to expose the subset of deliverable attributes that OSS (Oracle Student System) requires for the definition and management of information types. In functional terms, an "information type" in IGS corresponds to a deliverable that is packaged as a kit — that is, a logical container of related content presented to a user. The view therefore serves as a purpose-built presentation layer that shields consumers from the full complexity of the underlying deliverable model while enforcing the business rule that only kit-flagged deliverables qualify as information types. It is typically consumed by reporting queries, integration extracts, and OSS-facing APIs that need a stable, denormalized shape for information type metadata rather than the raw transactional tables.

Underlying Base Objects

Per the documented metadata, the view is defined over two sources:

  • IGR_I_PKG_ITEM (aliased INFOTYPE) — The IGS Information Package Item junction table. This table supplies the PACKAGE_ITEM_ID, which the view publishes as INFO_TYPE_ID, and the ROWID, published as ROW_ID.
  • AMS_P_DELIVERABLES_V (aliased DELIV) — An OMO (Oracle Marketing/Advanced Marketing) public view over deliverables. This is the attribute source for names, descriptions, availability dates, flags, and audit columns.

The two sources are joined by the predicate INFOTYPE.PACKAGE_ITEM_ID = DELIV.DELIVERABLE_ID, with an additional filter requiring DELIV.KIT_FLAG = 'Y'. The KIT_FLAG restriction is the defining characteristic of the view: it ensures that only kit-style deliverables are surfaced, thereby mapping the general deliverable concept onto the IGS-specific notion of an information type. Because the second source is itself a view, the effective lineage extends one level deeper into the OMO deliverables base tables, though no additional base objects are documented in the ETRM metadata.

Key Columns

The view exposes eighteen columns, organized into identity, descriptive, availability, and audit groups:

Common Use Cases and Queries

The view is commonly queried during information type setup validation, OSS content publishing extracts, and reporting on available learning or informational deliverables. A basic listing of active information types filtered by availability date is straightforward:

  • SELECT info_type_id, information_type, description, actual_avail_from_date, actual_avail_to_date FROM igr_i_info_types_v WHERE active_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(actual_avail_from_date, SYSDATE) AND NVL(actual_avail_to_date, SYSDATE);
  • SELECT info_type_id, information_type FROM igr_i_info_types_v WHERE private_flag = 'N' ORDER BY information_type;
  • SELECT info_type_id, information_type, language_code, owner_user_id FROM igr_i_info_types_v WHERE last_update_date >= :p_since;

Because KIT_FLAG is constrained to 'Y' within the view definition, consumers can rely on every returned row representing a kit deliverable, simplifying downstream logic in OSS integrations and Information Type lookups.