Search Results fnd_attached_docs_form_vl




Overview
Explore in AI Chat

Overview

FND_ATTACHED_DOCS_FORM_VL is a read-only view owned by the APPS schema within the FND - Application Object Library product of Oracle E-Business Suite. It is a denormalized, forms-oriented presentation layer that joins attachment instance rows from FND_ATTACHED_DOCUMENTS with their corresponding document definitions, translated titles and descriptions, category information, and the attachment functions that govern where and how the attachment is permitted. The suffix "VL" follows Oracle naming conventions for a validated, language-aware view; it is intended primarily to serve the Oracle Forms-based Attachments block and related framework components, but it is fully queryable and is widely used for reporting and integration purposes.

Because the view resolves translated columns against the session language (USERENV('LANG')), any query returns document titles, descriptions, category user names, and entity prompts in the language of the connecting user's session. This makes it the natural source for reporting on attachments without re-implementing the language joins that the base tables require. The object is documented as VALID and is present in both Oracle EBS 12.1.1 and 12.2.2; the ETRM entry for 12.2.2 lists it under the APPS schema with a "Retrofitted" description, consistent with its role as a long-standing framework view.

Underlying Base Objects

The view is defined over eight base objects, exposed through public synonyms in the APPS schema:

  • FND_ATTACHED_DOCUMENTS (AD) — the central attachment instance table; each row links a specific entity record (identified by ENTITY_NAME and PK1_VALUE through PK5_VALUE) to a document.
  • FND_DOCUMENTS (D) — the document master, supplying storage type, file name, media, security and category attributes.
  • FND_DOCUMENTS_TL (DT) — translated document titles, descriptions, and descriptive flexfield columns.
  • FND_DOCUMENT_ENTITIES_TL (DET) — translated entity definitions, providing the user entity name and prompt.
  • FND_DOCUMENT_CATEGORIES_TL (DCT) — translated category user names.
  • FND_DOCUMENT_DATATYPES (DAT) — data type user names for the stored document.
  • FND_DOC_CATEGORY_USAGES (DCU) — the association between document categories and the attachment functions that may use them.
  • FND_ATTACHMENT_FUNCTIONS (AF) — the function definitions (name and type) that determine which form or entity can carry attachments.

Joins are driven from AD.DOCUMENT_ID to D and DT, from D.CATEGORY_ID to DCT and DCU, and from DCU.ATTACHMENT_FUNCTION_ID to AF, with DT.LANGUAGE and DCT.LANGUAGE restricted to the session language.

Key Columns

The view exposes the full column set of the attachment instance together with descriptive attributes. Principal columns include ATTACHED_DOCUMENT_ID (unique attachment instance identifier), DOCUMENT_ID and DATATYPE_ID, SEQ_NUM (ordering), ENTITY_NAME along with PK1_VALUE through PK5_VALUE (the owning application record), and COLUMN1. The AUTOMATICALLY_ADDED_FLAG, the column most frequently sought by users, indicates whether the attachment was inserted programmatically by the application rather than by a user action; it is essential when filtering reporting output to exclude system-generated attachments. Other notable columns are FILE_NAME, URL, MEDIA_ID, STORAGE_TYPE, IMAGE_TYPE, USAGE_TYPE, SECURITY_TYPE and SECURITY_ID, PUBLISH_FLAG, START_DATE_ACTIVE and END_DATE_ACTIVE, the translated TITLE, DESCRIPTION, and USER_NAME columns for document, entity, category, and datatype, plus FUNCTION_NAME and FUNCTION_TYPE, CATEGORY_ID, and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program context columns (PROGRAM_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE). ROWID of the base attachment row is also projected.

Common Use Cases and Queries

Typical uses include attachment auditing, migration or cleanup scripts, and custom inquiry pages that require translated titles and the entity prompt. The following query lists user-added attachments for a given entity and primary key:

  • SELECT attached_document_id, title, file_name, entity_name, pk1_value, automatically_added_flag FROM fnd_attached_docs_form_vl WHERE entity_name = :entity AND pk1_value = :pk1 AND automatically_added_flag = 'N' ORDER BY seq_num;
  • SELECT entity_name, COUNT(*) FROM fnd_attached_docs_form_vl WHERE automatically_added_flag = 'Y' GROUP BY entity_name; — identifies entities where the application is auto-attaching documents.
  • SELECT function_name, title, user_name FROM fnd_attached_docs_form_vl WHERE function_type = 'FORM'; — isolates form-based attachments.

Because the view performs the language joins internally, it should be preferred over hand-built queries against the base tables when translated content is required. When only raw attachment rows are needed for high-volume processing, querying FND_ATTACHED_DOCUMENTS directly may offer better performance.