Results for “jtf_amv_attachments_v”

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

Overview

JTF_AMV_ATTACHMENTS_V is a reporting and integration view owned by the APPS schema within the JTF – CRM Foundation product module of Oracle E-Business Suite. It exposes the attachment details managed by the CRM Foundation attachment infrastructure, which underpins the Attachments and Notes functionality used throughout Oracle EBS applications such as CRM, Order Management, Service, and the eBusiness Suite general attach framework. In the ETRM configuration for 12.1.1 and 12.2.2 the object carries a status of VALID, and its documented description is simply that it is "a view on the attachment details."

Because JTF_AMV_ATTACHMENTS_V is a thin, pass-through view rather than a denormalized or filtered construct, its principal role is to provide a stable, versioned read interface over the underlying attachment entity. This allows forms, OA Framework pages, concurrent programs, and custom integration extracts to reference attachment metadata without binding directly to the base table. In multi-org aware 12.2.2 environments it remains part of the standard JTF object set supplied by the CRM Foundation product installation.

Underlying Base Objects

The documented view text defines a single-source SELECT over JTF_AMV_ATTACHMENTS:

• Every column in the view is selected directly from the base table using the alias B, with the base table named as JTF_AMV_ATTACHMENTS.
• ETRM metadata for 12.2.2 records the referenced base object as JTF_AMV_ATTACHMENTS, exposed to the APPS schema through a SYNONYM.
• No joins, unions, DISTINCT clauses, or WHERE predicates are present, so the row cardinality and identity of the view match the base table exactly.
• The view is created under the APPS schema in combination with the standard JTF foundation grants, making it callable from any EBS session that holds the corresponding APPS synonym privileges.

Key Columns

The view projects the full documented column list of the base attachment entity. The most functionally significant columns fall into several groups:

• Identity and concurrency: ROW_ID, ATTACHMENT_ID, OBJECT_VERSION_NUMBER, VERSION.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• Ownership and association: OWNER_USER_ID, ATTACHMENT_USED_BY_ID, ATTACHMENT_USED_BY, ENABLED_FLAG.
• File attributes: FILE_ID, FILE_NAME, FILE_EXTENSION, KEYWORDS, LANGUAGE_CODE.
• Presentation and rendering: DISPLAY_WIDTH, DISPLAY_HEIGHT, DISPLAY_LOCATION, DISPLAY_URL, DISPLAY_TEXT, ALTERNATE_TEXT, DEFAULT_STYLE_SHEET, DISPLAY_RULE_ID, DISPLAY_PROGRAM.
• Link and preview control: LINK_TO, LINK_URL, SEND_FOR_PREVIEW_FLAG, CAN_FULFILL_ELECTRONIC_FLAG.
• Classification: ATTACHMENT_TYPE, ATTACHMENT_SUB_TYPE, APPLICATION_ID, DESCRIPTION.
• Flexfield support: ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical usages include reporting on attachment inventory, locating orphaned or disabled attachments, and extracting attachment metadata during data conversion. The following examples reflect the standard JTF attachment model.

• List active attachments for a specific owning user:

SELECT attachment_id, file_name, attachment_type, creation_date
FROM jtf_amv_attachments_v
WHERE owner_user_id = :p_user_id
  AND enabled_flag = 'Y';

• Identify attachments tied to a particular used-by entity:

SELECT attachment_id, attachment_used_by, attachment_used_by_id, link_to
FROM jtf_amv_attachments_v
WHERE attachment_used_by = 'ORDER'
  AND attachment_used_by_id = :p_order_id;

• Locate attachments created within a period for audit and purge programs:

SELECT attachment_id, file_name, created_by, creation_date
FROM jtf_amv_attachments_v
WHERE creation_date BETWEEN :p_start_date AND :p_end_date
ORDER BY creation_date;

Because the view adds no filtering or transformation logic, queries against it behave identically to equivalent queries against JTF_AMV_ATTACHMENTS, and it can be used safely in both online and batch integration paths within 12.1.1 and 12.2.2.