Results for “jtf_amv_items_b”

50+ results




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

Overview

JTF_AMV_ITEMS_B is the base table of the Advanced Media Viewer (AMV) document repository within the JTF – CRM Foundation product family. It stores the definition of every document or content item managed by the AMV framework, including its classification, lifecycle status, access characteristics, and ownership. In Oracle EBS 12.1.1 and 12.2.2, this table underpins a wide range of content-delivery features, such as knowledge-base articles, CRM collateral, iStore merchandising content, and service contract process templates that reference AMV deliverables. The table is owned by the JTF schema and is marked VALID in the ETRM registry.

From a dimensional-modeling perspective, the foreign-key topology suggests a hub-leaning classification. JTF_AMV_ITEMS_B acts as a central entity whose ITEM_ID is referenced by numerous satellite-style and link-style tables across multiple product schemas (AMV, JTF, IBE, OKL). It is best treated as the anchor hub for document content, with attributes such as status, language, and security held directly on the hub row rather than in a separate satellite.

Key Information Stored

The primary key is the surrogate column ITEM_ID, enforced through the JTF_AMV_ITEMS_B_PK constraint. A unique index, AMVI_B_PK, additionally covers (ITEM_ID, ZD_EDITION_NAME), which is the documented business-key candidate and supports multi-edition content staging. The most significant descriptive columns are:

Common Use Cases and Queries

The table is queried to list active, published documents for a given application or security group, to drive AMV viewer pages, and to join to translated titles. A typical reporting query joins the translation table to return the display name alongside status and effective dates:

  • Filter published items: SELECT item_id, item_type, publication_date FROM jtf_amv_items_b WHERE status_code = 'PUBLISHED' AND SYSDATE BETWEEN effective_start_date AND NVL(expiration_date, SYSDATE);
  • Resolve titles: join JTF_AMV_ITEMS_TL t ON t.item_id = b.item_id AND t.language = :lang.
  • Audit approvals: join JTF_AMV_ITEM_AUTHORS and AMV_U_ACCESS to trace authorship and access grants.
  • iStore/IBE integration: join IBE_DSP_SECTIONS_B on DELIVERABLE_ID to enumerate merchandising deliverables.
  • Service contracts: join OKL_PROCESS_TMPLTS_ALL_B on JTF_AMV_ITEM_ID to find AMV-referenced process templates.

Related Objects

The following dependencies are the most significant for integration and impact analysis:

  • JTF_AMV_ITEMS_TL – translated item names and descriptions, joined on ITEM_ID.
  • JTF_AMV_ATTACHMENTS – attachments linked via ATTACHMENT_USED_BY_ID.
  • JTF_AMV_ITEM_AUTHORS and JTF_AMV_ITEM_KEYWORDS – authorship and keyword tagging on ITEM_ID.
  • AMV_U_ACCESS – access-control rows keyed by ACCESS_TO_TABLE_RECORD_ID.
  • IBE_DSP_SECTIONS_B – iStore deliverable sections referencing DELIVERABLE_ID.
  • OKL_PROCESS_TMPLTS_ALL_B – service contract templates referencing JTF_AMV_ITEM_ID.
  • FND_LANGUAGES, FND_APPLICATION, AMV_I_CONTENT_TYPES_B, FND_SECURITY_GROUPS – lookup parents for language, application, content type, and security group.