Search Results default_msite




Overview
Explore in AI Chat

Overview

APPS.JTF_DSP_ATTACHMENTS_V is an Oracle E-Business Suite internal database view owned by the APPS schema. It is classified under FND Design Data as JTF.JTF_DSP_ATTACHMENTS_V and holds a VALID status in both 12.1.1 and 12.2.2 environments. The view presents attachment metadata for the Oracle Applications Media/Attachments infrastructure, exposing file names, descriptive text, language attributes, logical identifiers, and the underlying FND_LOBS file reference. Its primary role is to surface attachment records associated with items managed through the JTF_AMV (Application Media Viewer) tables and the "DSP" (Display) logical-to-physical mapping layer used by Oracle's content and media display framework.

Oracle issues an explicit warning that this view is for Oracle Internal Use Only and that access to Oracle applications data through this object is unsupported except from standard Oracle Applications programs. Consequently, the view functions primarily as a supporting construct for Oracle-delivered UI components, such as the Attachments region within Self-Service and Forms-based displays, rather than as a documented, customer-facing integration interface.

Underlying Base Objects

The documented dependency list identifies three referenced objects:

  • APPS.JTF_AMV_ATTACHMENTS (SYNONYM) — the core attachments table in the JTF_AMV schema, holding the association between media/attachment records and their parent items, along with access control and site scoping attributes.
  • APPS.JTF_AMV_ITEMS_VL (VIEW) — the translated (VL) view over JTF_AMV_ITEMS, supplying the item-level description and language columns that surface in the attachment view.
  • APPS.JTF_DSP_LGL_PHYS_MAP (SYNONYM) — the logical-to-physical mapping synonym used by the DSP content resolution framework to translate logical identifiers into physical storage references.

The view is defined as an internal, non-updatable view type. It does not reference FND_LOBS directly; instead, FILE_ID carries the identifier into FND_LOBS for the actual binary content. Critically, the metadata records that APPS.JTF_DSP_ATTACHMENTS_V is not referenced by any database object, confirming its role as a terminal presentation layer rather than an intermediate dependency.

Key Columns

  • FILE_NAME (VARCHAR2, 240) — the displayed name of the attached file.
  • DESCRIPTION (VARCHAR2, 2000) — descriptive text for the attachment.
  • LANGUAGE_CODE (VARCHAR2) — the language of the attachment record.
  • LOGICAL_ID (NUMBER) — the logical identifier resolved against the logical/physical mapping used by the DSP framework.
  • ACCESS_NAME (VARCHAR2, 40) — the access control name governing visibility of the attachment.
  • SITE_ID (NUMBER) — the site/organization scoping identifier.
  • DEFAULT_MSITE (VARCHAR2) — flags the default multi-site (MSITE) designation for the attachment. This is the column most directly associated with the search term "default_msite." It allows Oracle's media display logic to determine whether a given attachment should be treated as the default rendering across multiple sites.
  • DEFAULT_LANGUAGE (VARCHAR2) — indicates whether the attachment serves as the default language rendition.
  • FILE_ID (NUMBER) — the identifier of the attached file in FND_LOBS, providing the link to the stored binary content.

Common Use Cases and Queries

Because the view is unsupported for direct customer access, use cases center on diagnostics, data validation, and read-only reference rather than integration. Typical scenarios include verifying which attachment is flagged as the default multi-site rendition, auditing descriptions and access names for a given logical content object, and tracing a presented attachment back to its FND_LOBS file.

A straightforward inspection query is:

SELECT FILE_NAME, DESCRIPTION, ACCESS_NAME, SITE_ID, DEFAULT_MSITE, DEFAULT_LANGUAGE, FILE_ID FROM APPS.JTF_DSP_ATTACHMENTS_V;

To isolate default multi-site attachments for a particular site:

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

To resolve the stored binary for a specific attachment:

SELECT a.FILE_NAME, l.FILE_CONTENT FROM APPS.JTF_DSP_ATTACHMENTS_V a, FND_LOBS l WHERE a.FILE_ID = l.FILE_ID AND a.LOGICAL_ID = :p_logical_id;

These queries are appropriate for read-only investigation only; any functional dependency on Oracle Internal Use Only objects should be avoided in supported customizations.