Results for “access_name”

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

Overview

APPS.JTF_DSP_FEATURED_MEDIA_V is a database view owned by the APPS schema within the JTF – CRM Foundation product (CRM Foundation, formerly the Oracle CRM Technology Foundation). It exposes featured content and media associated with Oracle iStore and Oracle Marketing mini-sites, resolving the relationship between inventory items, categories, sections, and media context into a single consolidated result set. In Oracle EBS 12.1.1 and 12.2.2, the object carries a VALID status and is defined as a UNION ALL of three contributing queries, each distinguished by a literal type code: 'P' for product-level items, 'C' for category-level items, and 'S' for section-level entries.

The view is not a transactional table but a denormalized reporting and integration surface. It allows applications in the CRM Foundation stack—such as iStore storefront rendering, featured merchandising, and mini-site media assembly—to retrieve the featured media objects that should appear for a given mini-site without repeatedly joining the underlying DSP (Display) repository tables. Because it is defined on top of the business tables rather than storing data, it inherits the referential integrity and profile-driven behavior of those base objects.

Underlying Base Objects

The view is defined over the following documented base objects, all accessed through APPS-owned synonyms or views:

• JTF_DSP_SECTION_ITEMS (synonym) – maps inventory items to sections.
• JTF_DSP_SECTIONS_B (synonym) – header of each displayed section; filtered here by SECTION_TYPE_CODE = 'F' (featured).
• JTF_DSP_MSITE_SCT_ITEMS (synonym) – associates mini-sites with section items.
• JTF_DSP_OBJ_LGL_CTNT (synonym) – the object-to-legal-content linking table that drives object type discrimination ('I', 'C', 'S').
• JTF_DSP_CONTEXT_B (synonym) – business-side context definitions; filtered by CONTEXT_TYPE_CODE = 'MEDIA'.
• JTF_AMV_ITEMS_VL (view) – the media/content item view supplying the accessible name via ACCESS_NAME.
• MTL_ITEM_CATEGORIES (synonym) – joins inventory items to categories; restricted to the category set defined by the profile IBE_CATEGORY_SET.
• FND_PROFILE (package) – invoked as FND_PROFILE.VALUE('IBE_CATEGORY_SET') to resolve the active iStore category set at runtime.

Each of the three UNION ALL branches reuses this object set with different predicates on OBJECT_TYPE, ensuring all featured media records—whether tied to a product, a category, or a section—are returned with a uniform shape.

Key Columns

• OBJECT_ID – numeric identifier of the featured object (inventory item, category, or section, depending on the resolved type).
• CONTEXT_NAME – the access name of the media context, sourced from JTF_DSP_CONTEXT_B.ACCESS_NAME.
• ACCESS_NAME – the media item's access name, sourced from JTF_AMV_ITEMS_VL.ACCESS_NAME; this is the presentation-facing label/URL token.
• SITE_ID – the mini-site identifier (MINI_SITE_ID) to which the featured media belongs, enabling tenant or storefront isolation.

Common Use Cases and Queries

The view is typically queried to render featured media for a specific mini-site or to audit which items are configured as featured. A representative query retrieving all featured media for a site follows:

SELECT object_id, context_name, access_name, site_id
FROM   apps.jtf_dsp_featured_media_v
WHERE  site_id = :p_mini_site_id
ORDER BY context_name;

To isolate category-driven featured media, filter on the leading type discriminator by joining back to the branch logic, or simply constrain by object_id ranges against MTL_ITEM_CATEGORIES. Reporting queries frequently aggregate counts per mini-site, and integration routines consume the same view when publishing catalog content to external storefronts. Because the view depends on FND_PROFILE.VALUE('IBE_CATEGORY_SET'), results for category records vary with the session's iStore category-set profile setting, a behavior that must be considered when materializing or caching the output.