Results for “jtf_sources”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The JTF_SOURCES view is a CRM Foundation (JTF) dictionary object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents source-code reference data used throughout CRM applications, exposing lookup-driven values that identify the origin or channel of CRM entities. Per the ETRM documentation, the view is functionally identical to the JTF_SOURCES_ALL table, adding only the lookup descriptive attributes joined from FND_LOOKUPS. Because it is an APPS-owned view rather than a table, it provides a read-only, reporting-friendly projection of the base data without duplicating storage.

The view carries a multi-org awareness via the ORG_ID column projected from JTF_SOURCES_ALL, allowing CRM deployments to distinguish source definitions by operating unit. Its role in EBS reporting and integration is that of a denormalized access point: consumers obtain the numeric source identifier together with the human-readable lookup meaning, description, and effective dates in a single query.

Underlying Base Objects

The documented base objects referenced by the view definition are:

The join condition is an equality match on both LOOKUP_TYPE and LOOKUP_CODE between JTF_SOURCES_ALL and FND_LOOKUPS, so each source row is enriched with its corresponding lookup attributes. Rows in the base table that have no matching lookup entry are excluded by the inner join semantics.

Key Columns

The view exposes nineteen columns. The principal ones are summarized below.

  • SOURCE_ID — surrogate primary key identifying each source record; the primary reference value for foreign keys in dependent CRM tables.
  • LOOKUP_TYPE and LOOKUP_CODE — the lookup classification and code that qualify the source; both originate from the base table and are matched against FND_LOOKUPS.
  • MEANING — the translatable, user-facing name of the lookup value; the most commonly displayed attribute.
  • ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE — control whether the source is currently selectable and its effective window.
  • DESCRIPTION — longer descriptive text for the lookup code.
  • RELATED_ID1 through RELATED_ID5 — five generic foreign-key placeholders allowing the source to be associated with related CRM entities.
  • ORG_ID — operating unit identifier supporting multi-org security.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical usage includes decoding source identifiers in CRM reports, populating source LOVs, and confirming that a source is enabled before referencing it.

Listing all enabled sources:

SELECT source_id, lookup_code, meaning FROM jtf_sources WHERE enabled_flag = 'Y' ORDER BY meaning;

Restricting by operating unit:

SELECT source_id, meaning FROM jtf_sources WHERE org_id = :p_org_id;

Resolving a stored source ID to its descriptive meaning for a dependent entity:

SELECT meaning FROM jtf_sources WHERE source_id = :p_source_id;

Because the view applies an inner join to FND_LOOKUPS, only sources with valid lookup counterparts are returned; where orphaned source rows must be identified, query JTF_SOURCES_ALL directly.