Search Results jtf_dsp_attachments_v




Overview
Explore in AI Chat

Overview

JTF_DSP_ATTACHMENTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the JTF product family, commonly labeled CRM Foundation (also referred to as Oracle CRM Technology Foundation or OJTF). The view exposes attachment metadata that has been linked to display or logical-to-physical mapping records through JTF_DSP_LGL_PHYS_MAP, coupling attachment file details with item-level descriptive text.

The object carries a VALID status in the ETRM repository, meaning the compiled definition resolves successfully against the underlying base objects at the documented release level. Its role is to provide a denormalized projection that joins three sources into a single, queryable result set, thereby simplifying PL/SQL, concurrent program, and integration-layer access to attachments within the JTF Application Module for Media (AMV) framework. Because the view is restricted internally to APPLICATION_ID 671, results are scoped to the JTF application context only.

Underlying Base Objects

The ETRM 12.2.2 metadata documents three referenced base objects: JTF_AMV_ATTACHMENTS (SYNONYM), JTF_AMV_ITEMS_VL (VIEW), and JTF_DSP_LGL_PHYS_MAP (SYNONYM). The view definition joins them as follows:

  • JTF_AMV_ATTACHMENTS (aliased V1) — supplies FILE_NAME, FILE_ID, ATTACHMENT_ID, and APPLICATION_ID. It is the physical attachment registry.
  • JTF_AMV_ITEMS_VL (aliased V2) — supplies DESCRIPTION, ITEM_ID, ACCESS_NAME, and APPLICATION_ID. This is the translated (VL) items view holding attachment-to-item associations.
  • JTF_DSP_LGL_PHYS_MAP (aliased A) — supplies LANGUAGE_CODE, MSITE_ID, DEFAULT_SITE, DEFAULT_LANGUAGE, and ATTACHMENT_ID. It maps logical entities to physical sites.

The join predicates are A.ATTACHMENT_ID = V1.ATTACHMENT_ID, A.ITEM_ID = V2.ITEM_ID, and the constant filter V1.APPLICATION_ID = 671 AND V2.APPLICATION_ID = 671.

Key Columns

  • FILE_NAME / FILE_ID — Name and primary key of the stored attachment file from JTF_AMV_ATTACHMENTS.
  • DESCRIPTION / ACCESS_NAME — User-facing item text and the access control name from JTF_AMV_ITEMS_VL.
  • LANGUAGE_CODE — Language context for the item as mapped in the display layer.
  • SITE_ID (documented as MSITE_ID) — The physical site identifier from the logical-to-physical map.
  • DEFAULT_MSITE — The site flag matching the user's search term; the view text defines it as DEFAULT_SITE, exposing which mapped site is the default physical site.
  • DEFAULT_LANGUAGE — Default language attribute for the mapped record.
  • ITEM_ID — Foreign key linking the attachment to the underlying item.

Common Use Cases and Queries

Typical scenarios include listing all files attached to a CRM item for a given site and language, or identifying the default physical site for each attachment during display resolution. Because the view embeds the APPLICATION_ID = 671 filter, callers do not need to re-filter by application.

SELECT FILE_NAME, DESCRIPTION, ITEM_ID, SITE_ID,
       DEFAULT_MSITE, DEFAULT_LANGUAGE, FILE_ID
FROM   APPS.JTF_DSP_ATTACHMENTS_V
WHERE  ITEM_ID = :p_item_id
AND    DEFAULT_MSITE = 'Y';

To enumerate attachments for a language:

SELECT FILE_ID, FILE_NAME, LANGUAGE_CODE
FROM   APPS.JTF_DSP_ATTACHMENTS_V
WHERE  LANGUAGE_CODE = :p_lang;

Queries should account for the outer join behavior implied by the mapping table, as items without a matching physical map entry will not appear.