Search Results related_id5




Overview

The APPS.JTF_QUAL_TYPE_DENORM_V view is a denormalization view defined in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases. It belongs to the Oracle CRM Foundation / Trading Community Architecture (TCA) qualification schema and is used to present qualification type relationships in a flattened, row-based form. The base table JTF_QUAL_TYPES_ALL stores up to five distinct related entity references per qualification type row (RELATED_ID1 through RELATED_ID5). Rather than requiring consumers to interrogate five separate columns, this view collapses those columns into a single RELATED_ID column, producing one row per populated relationship. This makes it convenient for reporting, integration, and lookup logic where a qualification type can be linked to any of several associated records.

Underlying Base Objects

The view is defined over a single documented base object, the synonym APPS.JTF_QUAL_TYPES_ALL, which is the underlying qualification types table. The view definition is a UNION of five SELECT statements, each projecting QUAL_TYPE_ID together with one of the related identifier columns:

  • SELECT qual_type_id, related_id1 FROM jtf_qual_types_all WHERE related_id1 IS NOT NULL
  • SELECT qual_type_id, related_id2 FROM jtf_qual_types_all WHERE related_id2 IS NOT NULL
  • SELECT qual_type_id, related_id3 FROM jtf_qual_types_all WHERE related_id3 IS NOT NULL
  • SELECT qual_type_id, related_id4 FROM jtf_qual_types_all WHERE related_id4 IS NOT NULL
  • SELECT qual_type_id, related_id5 FROM jtf_qual_types_all WHERE related_id5 IS NOT NULL

The view does not join to any additional table; it is a pure row-expansion transformation of the base table. Because it uses UNION (not UNION ALL), duplicate (QUAL_TYPE_ID, RELATED_ID) pairs are eliminated, and only non-null relationships are surfaced.

Key Columns

  • QUAL_TYPE_ID — The primary identifier of the qualification type record in JTF_QUAL_TYPES_ALL. It links the view back to the parent qualification type definition.
  • RELATED_ID — The logical output column that carries the value of whichever RELATED_IDn column was non-null for that base row. It represents the associated entity reference (for example, a related qualification, interest, or dependent object) associated with the qualification type.

Note that the view output column name is RELATED_ID; the individual source columns RELATED_ID1 through RELATED_ID5 from the base table are not exposed as separate columns. Because no source-column tag is preserved, the original position (1–5) of a given relationship cannot be determined directly from this view.

Common Use Cases and Queries

This view is typically used when the caller wants to enumerate every relationship defined for a qualification type without hard-coding which of the five slots is populated. A search for "related_id5" indicates the user is likely investigating how the fifth related identifier is represented; via this view, RELATED_ID5 values appear simply as RELATED_ID rows.

Sample query retrieving all related identifiers for a specific qualification type:

  • SELECT qual_type_id, related_id FROM apps.jtf_qual_type_denorm_v WHERE qual_type_id = :p_qual_type_id;

Sample query to list all populated relationships:

  • SELECT qual_type_id, related_id FROM apps.jtf_qual_type_denorm_v ORDER BY qual_type_id;

Because UNION is used, the view may incur extra sorting/distinct processing on large data sets; in performance-sensitive paths, querying JTF_QUAL_TYPES_ALL directly and filtering the appropriate RELATED_IDn column is preferable. The view remains the most portable way to retrieve relationships without knowledge of the underlying slot layout.