Results for “jtf_fm_amv_items_vl”

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

Overview

JTF_FM_AMV_ITEMS_VL is a documented Oracle E-Business Suite view owned by the APPS schema and classified under the JTF (CRM Foundation) product family. It is valid in both EBS 12.1.1 and 12.2.2. Functionally, the view presents a restricted projection of the JTF_AMV_ITEMS_VL view, which is the foundational store for "AMV items" — the message, announcement, and article objects surfaced through the CRM Foundation Message/Announcement infrastructure. JTF_FM_AMV_ITEMS_VL exposes the item header columns together with the descriptive text attribute used by the publishing layer, and additionally appends a computed deletion indicator column (F_DELETEDFLAG) that is not present on the base view.

The "FM" prefix associates the view with the Oracle Field Service / CRM Foundation item framework, where AMV items are used to define structured content such as announcements, messages, and knowledge-style articles that can be published to users, destinations, and applications. Because it is a view rather than a table, it carries no independent storage; all reads are resolved against its single referenced base object at runtime.

Underlying Base Objects

Per the documented ETRM metadata for release 12.2.2, the view references a single base object:

• JTF_AMV_ITEMS_VL (VIEW) — the language-enabled item view that supplies the item header columns.

JTF_FM_AMV_ITEMS_VL is therefore a thin wrapper: the view text selects the identifier, audit, classification, publication, and descriptive columns from JTF_AMV_ITEMS_VL, and returns a literal NULL aliased as F_DELETEDFLAG as the final projected column. The deletion flag is derived at the wrapper level rather than being sourced from the base view, which means callers can rely on the column existing for uniform query construction even though the item records themselves are not physically flagged as deleted in this projection. The lack of any join or union in the view text confirms that filtering by language, status, or date range must be applied by the calling query, not by the view itself.

Key Columns

• ROW_ID — Row identifier used by the AMV framework for addressing a content row.
• ITEM_ID — Primary key of the AMV item; the principal join key to item-related child objects.
• OBJECT_VERSION_NUMBER — Optimistic locking column maintained by the CRM Foundation framework.
• ITEM_TYPE and CONTENT_TYPE_ID — Classify the item and the content type definition it adheres to.
• EFFECTIVE_START_DATE, EXPIRATION_DATE, PUBLICATION_DATE — Govern the validity and release window of the item.
• STATUS_CODE and PRIORITY — Support workflow-driven lifecycle and ordering logic.
• OWNER_ID, DEFAULT_APPROVER_ID — Identify the responsible party and the default approver in the publication flow.
• URL_STRING, ITEM_DESTINATION_TYPE — Define where and how the item is delivered.
• APPLICATION_ID, LANGUAGE_CODE — Scoping and translation attributes.
• ITEM_NAME, DESCRIPTION, TEXT_STRING — The display name, short description, and primary textual body of the item.
• F_DELETEDFLAG — A literal NULL placeholder returned by the view, intended to provide a uniform deletion-flag column for consumers.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 provide the standard DFF flexfield columns.

Common Use Cases and Queries

The view is typically used for reporting and integration over AMV item content — listing currently effective items, extracting textual content for downstream publishing, and joining item headers to destination or approval data. A representative query retrieves effective items with their descriptive text:

SELECT ITEM_ID, ITEM_NAME, TEXT_STRING, STATUS_CODE, PUBLICATION_DATE FROM APPS.JTF_FM_AMV_ITEMS_VL WHERE STATUS_CODE = 'PUBLISHED' AND SYSDATE BETWEEN EFFECTIVE_START_DATE AND EXPIRATION_DATE ORDER BY PUBLICATION_DATE DESC;

A second common pattern filters by application and language scope:

SELECT ITEM_ID, ITEM_TYPE, ITEM_NAME, URL_STRING FROM APPS.JTF_FM_AMV_ITEMS_VL WHERE APPLICATION_ID = 200 AND LANGUAGE_CODE = 'US' AND ITEM_DESTINATION_TYPE = 'URL';

Because the view applies no filtering of its own, all transactional predicates — status, date window, type, and language — must be supplied explicitly by the caller. The F_DELETEDFLAG column should be treated as informational only, since it is returned as NULL by design.