Results for “file_extension”

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

Overview

JTF_FM_AMV_ATTACH_VL is an Oracle E-Business Suite view owned by the APPS schema within the JTF – CRM Foundation product. It is documented in the ETRM as a view referring to JTF_AMV_ATTACHMENTS_V, and its status is VALID. The "_VL" suffix conventionally denotes a "view link" style validation or read-only wrapper, and in this case the definition confirms that role: the view text is a straight projection over JTF_AMV_ATTACHMENTS_V, selecting the full column list and appending a literal NULL as the trailing column.

Functionally, the view exposes attachment metadata maintained by the CRM Foundation attachments framework. This includes file references, media/display attributes, ownership, language, and descriptive flexfield segments. Because it is a simple pass-through layer, it does not introduce additional filtering, joins, or security predicates of its own; any logic resides in the underlying JTF_AMV_ATTACHMENTS_V view and its own base tables. Reporting and integration consumers use it as a stable, named access point for attachment records rather than querying the underlying view directly.

Underlying Base Objects

The only documented referenced base object is JTF_AMV_ATTACHMENTS_V, itself a view. The relationship is a one-to-one column projection: every column in JTF_FM_AMV_ATTACH_VL is drawn from the same-named column in JTF_AMV_ATTACHMENTS_V, with the exception of the final column, which is emitted as a constant NULL. No filters, unions, or additional join conditions are documented in the view text.

This layering means the effective data set of JTF_FM_AMV_ATTACH_VL is identical to that of JTF_AMV_ATTACHMENTS_V. The dependency chain therefore runs from JTF_FM_AMV_ATTACH_VL to JTF_AMV_ATTACHMENTS_V, and from there to whatever base tables the parent view references. Because the definition carries no WHERE clause and no bind variables, the view cannot be relied upon to restrict data by application, user, or business unit on its own.

Key Columns

The view exposes a comprehensive set of attachment attributes. The columns most relevant to typical usage include:

• ATTACHMENT_ID and ROW_ID – Primary identifiers for an attachment record.
• FILE_ID, FILE_NAME, FILE_EXTENSION – The underlying file reference and its on-disk or LOB identifier.
• ATTACHMENT_TYPE, ATTACHMENT_USED_BY, ATTACHMENT_USED_BY_ID – Classify the attachment and identify the entity or context that consumes it.
• OWNER_USER_ID – The user who owns the attachment.
• DISPLAY_URL, DISPLAY_WIDTH, DISPLAY_HEIGHT, DISPLAY_LOCATION – Control how the attachment is rendered in CRM pages.
• DISPLAY_RULE_ID and DISPLAY_PROGRAM – Govern display logic and rule-based presentation. The DISPLAY_PROGRAM column is directly relevant to searches for that term.
• LINK_TO and LINK_URL – Target and address for link-type attachments.
• ENABLED_FLAG, CAN_FULFILL_ELECTRONIC_FLAG, SEND_FOR_PREVIEW_FLAG – Status and behavior indicators.
• LANGUAGE_CODE, APPLICATION_ID, DESCRIPTION, DEFAULT_STYLE_SHEET – Localization, ownership context, and styling.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 – Descriptive flexfield segments for extensible business attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER – Standard audit and optimistic locking columns.

The final column, F_DELETEDFLAG, is populated as a literal NULL and does not carry business meaning in this definition.

Common Use Cases and Queries

Because the view presents attachment data without embedded filters, it is commonly used in reporting extracts, integration staging, and troubleshooting of CRM attachment configuration. Typical scenarios include auditing which display programs or display rules are assigned to attachments, listing active attachments for a given owner, and extracting file metadata for migration.

Sample query retrieving all attachment records with display program assignments:

• SELECT attachment_id, file_name, attachment_type, display_url, display_rule_id, display_program
  FROM apps.jtf_fm_amv_attach_vl;

Sample query restricted to enabled attachments for a specific owner:

• SELECT attachment_id, file_name, attachment_used_by, attachment_used_by_id, display_location
  FROM apps.jtf_fm_amv_attach_vl
  WHERE enabled_flag = 'Y'
  AND owner_user_id = :owner_user_id;

Sample query locating records by display program or URL:

• SELECT attachment_id, file_name, display_program, display_url
  FROM apps.jtf_fm_amv_attach_vl
  WHERE display_program IS NOT NULL
  ORDER BY attachment_id;

In all cases, appropriate application or user context should be applied by the caller, since the view itself imposes no such restriction.