Results for “display_program”

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

Overview

JTF_AMV_ATTACHMENTS is a CRM Foundation (JTF) table that stores the document attachments associated with published content items held in JTF_AMV_ITEMS_B. In Oracle EBS 12.1.1 and 12.2.2, it functions as the central attachment registry for the Advanced Media Viewer (AMV) framework, which drives rich media and documentation presentation across CRM and iStore-facing modules. The table holds both the descriptive attributes of each attachment (file name, type, display geometry, link behavior) and the pointer to the physical binary payload, which is retained separately in FND_LOBS through the FILE_ID column.

From a dimensional modeling perspective, the mined foreign-key structure classifies this object as satellite-leaning. This is a heuristic suggestion: the table carries descriptive, version-aware attributes that hang off a parent entity (JTF_AMV_ITEMS_B) rather than acting as a pure transactional hub or an associative link. The presence of the ZD_EDITION_NAME column and its inclusion in the unique index confirms that the object participates in editioning, and the OBJECT_VERSION_NUMBER column supports optimistic locking on concurrent updates.

Key Information Stored

The documented physical schema contains 54 columns. The most operationally significant are:

• ATTACHMENT_ID — Surrogate primary key, enforced by JTF_AMV_ATTACHMENTS_PK. Also the leading column of the unique index JTF_AMV_ATTACHMENTS_U1 (ATTACHMENT_ID, ZD_EDITION_NAME), which is the closest documented business-key candidate.
• ATTACHMENT_USED_BY_ID — Foreign key to JTF_AMV_ITEMS_B, tying the attachment to its parent AMV content item.
• ATTACHMENT_USED_BY — Discriminator describing the entity type that consumes the attachment.
• FILE_ID — Foreign key to FND_LOBS; retrieves the actual binary content of the attached file.
• FILE_NAME and FILE_EXTENSION — The stored file name and its extension, used for display and type resolution.
• ATTACHMENT_TYPE and ATTACHMENT_SUB_TYPE — Classification of the attachment (for example, image, document, link).
• DOCUMENT_ID — Foreign key to FND_DOCUMENTS, linking the attachment to the shared document repository.
• OWNER_USER_ID — Foreign key to FND_USER identifying the attachment owner.
• LANGUAGE_CODE — Foreign key to FND_LANGUAGES for multilingual presentation.
• APPLICATION_ID — Foreign key to FND_APPLICATION, scoping the attachment to its owning application.
• DISPLAY_WIDTH, DISPLAY_HEIGHT, DISPLAY_LOCATION, DISPLAY_URL — Rendering attributes controlling how the media appears.
• LINK_TO and LINK_URL — Navigation target when the attachment is clicked.
• ENABLED_FLAG, SECURED_FLAG, SECURITY_GROUP_ID, DISPLAY_RULE_ID — Activation, access control, and conditional display configuration.
• ZD_EDITION_NAME — Edition identifier supporting the editioning model.

Common Use Cases and Queries

Typical usage centers on retrieving attachments for a content item, resolving the underlying file, and joining to the consuming entities that reference attachments as logos or mapped resources. A representative pattern retrieves all enabled attachments for a parent item along with their file metadata:

• SELECT a.attachment_id, a.file_name, a.file_extension, a.attachment_type FROM jtf.jtf_amv_attachments a WHERE a.attachment_used_by_id = :item_id AND a.enabled_flag = 'Y';
• Join to FND_LOBS on a.file_id = l.file_id to obtain the stored binary document.
• Join to JTF_AMV_ITEMS_B on a.attachment_used_by_id = i.item_id to report attachments grouped by published item.
• Filter by security_group_id in multi-org or secured configurations to honor data access boundaries.
• Resolve theme logos by joining IBE_EOS_THEMES_B on logo_attachment_id = attachment_id, a query relevant to the identifier the user searched for.

Reporting scenarios include attachment inventory by application, orphan detection where FILE_ID does not resolve to FND_LOBS, and edition-aware extracts filtered on ZD_EDITION_NAME for 12.2.2 environments.

Related Objects

• JTF_AMV_ITEMS_B — Parent content item; joined via attachment_used_by_id.
• FND_LOBS — Physical file storage; joined via file_id.
• FND_DOCUMENTS — Shared document registry; joined via document_id.
• FND_USER — Attachment owner; joined via owner_user_id.
• FND_LANGUAGES and FND_APPLICATION — Language and application lookups; joined via language_code and application_id.
• AMS_IBA_DISPLAY_RULES — Display rule configuration; joined via display_rule_id.
• IBE_EOS_THEMES_B — iStore theme definitions referencing logos through logo_attachment_id.
• IBE_DSP_LGL_PHYS_MAP and JTF_DSP_LGL_PHYS_MAP — Physical-to-logical mapping tables referencing attachment_id.
• AMS_DELIVERABLES_ALL_B — Marketing deliverables referencing jtf_amv_item_id.
• FND_SECURITY_GROUPS — Security grouping referenced through security_group_id.