Search Results applicable_to_code

Overview

The JTF_DSP_AMV_ITEMS_V view is a read-only database object owned by the APPS schema within the JTF (CRM Foundation) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is part of the Oracle Marketing / Advanced Marketing Views (AMV) infrastructure that manages reusable content items, deliverables, and their attachments. The "DSP" in the name refers to the display layer used by CRM self-service and marketing content presentation pages, while "AMV" reflects the underlying AMV item repository. The view is marked VALID in the ETRM data dictionary.

The view consolidates item metadata, keyword associations, and physical attachment file information into a single flattened result set, making it convenient for reporting, concurrent programs, and integration extracts that need to resolve an item's deliverable type, language, site, and associated file together. Because the view text is declared WITH READ ONLY, it is intended purely for query access and cannot be used for DML operations.

Underlying Base Objects

The view is defined over four documented base objects joined with outer-join semantics to preserve item rows even when dependent data is absent:

• JTF_AMV_ITEMS_VL (VIEW) — the primary driving object, providing item-level attributes such as item name, access name, application, and description. It supplies the item base record.
• JTF_AMV_ITEM_KEYWORDS_V (VIEW) — supplies keyword associations, outer-joined on ITEM_ID.
• JTF_DSP_LGL_PHYS_MAP (SYNONYM) — the logical-to-physical mapping that resolves the default site and default language for an item. Only rows where DEFAULT_SITE = 'Y' and DEFAULT_LANGUAGE = 'Y' are retained.
• JTF_AMV_ATTACHMENTS (SYNONYM) — the attachment repository, joined on ATTACHMENT_ID to yield FILE_NAME and FILE_ID.

The outer-join syntax (+) preserves the item even when no keyword, attachment, or physical mapping exists, which is essential for content inventory reporting.

Key Columns

The view exposes twelve columns. Principal among them, in the context of the searched term deliverable_type_code, is DELIVERABLE_TYPE_CODE, which classifies the item by the type of deliverable it represents (for example document, URL, or file-based content). Other significant columns include:

• ITEM_ID — primary identifier linking to the AMV item.
• ACCESS_NAME and ITEM_NAME — user-facing identifiers and titles for the content item.
• APPLICATION_ID — the owning application, enabling product-scoped filtering.
• APPLICABLE_TO_CODE — indicates the applicability scope of the item.
• DESCRIPTION — free-text item description.
• KEYWORD — associated search keywords from the keyword view.
• FILE_NAME and FILE_ID — attachment file reference details.
• OBJECT_VERSION_NUMBER — optimistic locking version for the underlying row.

Common Use Cases and Queries

Typical scenarios include content inventory reporting, deliverable-type analysis, and attachment auditing. A representative query is:

• SELECT ITEM_ID, ITEM_NAME, DELIVERABLE_TYPE_CODE, FILE_NAME FROM APPS.JTF_DSP_AMV_ITEMS_V WHERE DELIVERABLE_TYPE_CODE = :p_type; — filters items by deliverable type.
• SELECT APPLICATION_ID, COUNT(*) FROM APPS.JTF_DSP_AMV_ITEMS_V GROUP BY APPLICATION_ID; — content volume per application.
• SELECT ITEM_ID, KEYWORD FROM APPS.JTF_DSP_AMV_ITEMS_V WHERE KEYWORD IS NOT NULL; — keyword-driven search and indexing.

Because the view resolves the default site and default language mapping, it is the preferred source for presentation-layer queries that require the canonical attachment for a given item.