Results for “ams_act_attachments_v”

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

Overview

AMS_ACT_ATTACHMENTS_V is an APPS-owned database view in the Oracle E-Business Suite Marketing (AMS) module. It exposes attachment records associated with marketing activities, presenting a denormalized, query-friendly projection of underlying attachment data together with the owning user name and a decoded attachment type meaning. Because it is a view rather than a base table, it carries no storage of its own and is intended strictly for read access in reporting, integration, and extension scenarios.

The view is listed as VALID against both Oracle EBS 12.1.1 and 12.2.2, and the documented metadata is identical across these releases. Its principal value lies in abstracting the join logic among the JTF attachment framework, the FND user directory, and the AMS attachment-type lookup, so that consumers need not re-implement those joins. The status column DEFAULT_STYLE_SHEET is surfaced directly from the JTF attachment layer and is relevant where attachment rendering or formatting metadata must be inspected.

Underlying Base Objects

Per the documented view text, AMS_ACT_ATTACHMENTS_V is defined over the following referenced objects:

• JTF_AMV_ATTACHMENTS_V (VIEW) — the primary source, aliased as A. All attachment attribute columns, including ROW_ID, ATTACHMENT_ID, FILE_* columns, DISPLAY_* columns, DEFAULT_STYLE_SHEET, and the fifteen descriptive flexfield attributes, originate here.
• FND_USER (SYNONYM) — aliased as U, joined on A.OWNER_USER_ID = U.USER_ID, supplying USER_NAME.
• AMS_LOOKUPS (VIEW) — aliased as K, joined on LOOKUP_TYPE = 'AMS_ATTACHMENT_TYPE' and A.ATTACHMENT_TYPE = K.LOOKUP_CODE, supplying the MEANING column.

Oracle documents the base table as APPS.AMS_ACT_ATTACHMENTS_V, with the inner joins restricted as shown. The file format column is populated with a literal space rather than derived from a file-format lookup.

Key Columns

• ROW_ID — primary surrogate identifier inherited from the attachment framework; useful as a unique key in reporting queries.
• ATTACHMENT_ID — the attachment identifier used by the JTF attachment APIs and file repository.
• OWNER_USER_ID / USER_NAME — the owning user identifier and resolved login name.
• ATTACHMENT_USED_BY_ID / ATTACHMENT_USED_BY — identify the entity an attachment is linked to, typically the activity.
• FILE_ID, FILE_NAME, FILE_EXTENSION, FILE_FORMAT — file repository identification and metadata.
• DISPLAY_WIDTH, DISPLAY_HEIGHT, DISPLAY_LOCATION, DISPLAY_URL, DISPLAY_RULE_ID, DISPLAY_PROGRAM — control how the attachment renders in the UI.
• LINK_TO, LINK_URL — destination information for URL-type attachments.
• ATTACHMENT_TYPE / MEANING — the lookup code and its translated meaning from AMS_LOOKUPS.
• DEFAULT_STYLE_SHEET — the style sheet associated with the attachment record, relevant where template or formatting behavior is evaluated.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — descriptive flexfield segment values.

Common Use Cases and Queries

Typical consumers of this view include custom reports, concurrent programs, and integration extracts that need attachment details for marketing activities without joining the JTF, FND, and lookup layers independently.

Listing attachments for a given owning user:

SELECT attachment_id, file_name, attachment_type, meaning,
       default_style_sheet, display_url, creation_date
FROM   apps.ams_act_attachments_v
WHERE  owner_user_id = :p_user_id
AND    enabled_flag  = 'Y'
ORDER BY creation_date DESC;

Resolving attachment types to their meanings for reporting:

SELECT attachment_id, attachment_used_by_id, attachment_type,
       meaning, link_url, default_style_sheet
FROM   apps.ams_act_attachments_v
WHERE  attachment_used_by_id = :p_activity_id
AND    enabled_flag = 'Y';

Filtering file-based attachments and exposing their display configuration:

SELECT file_name, file_extension, display_width,
       display_height, display_location, default_style_sheet
FROM   apps.ams_act_attachments_v
WHERE  file_id IS NOT NULL;

Because the view joins FND_USER and AMS_LOOKUPS internally, all such queries implicitly require an enabled, resolvable user and a valid AMS_ATTACHMENT_TYPE lookup code; rows without a matching lookup or user will not be returned.