Search Results fnd_attached_documents




Overview
Explore in AI Chat

Overview

The FND_ATTACHED_DOCUMENTS table is a core repository within the Oracle E-Business Suite (EBS) Application Object Library (FND). It serves as the central relational mapping table that links documents, managed by the Oracle EBS document attachment entity model, to other entities across the application. Its primary role is to establish and maintain the relationships between a document's metadata (stored in FND_DOCUMENTS) and the specific application data rows to which the document is attached. This enables the generic attachment functionality that allows users to link files, text, or URLs to virtually any transaction, master data record, or concurrent request within the system, providing a unified document management layer.

Key Information Stored

The table's structure is designed to support flexible, entity-based attachments. The most critical columns include the surrogate primary key, ATTACHED_DOCUMENT_ID, and the foreign key, DOCUMENT_ID, which links to the FND_DOCUMENTS table where the document's title, category, and security attributes are stored. The entity-linking mechanism is facilitated by the ENTITY_NAME and PK* columns (PK1_VALUE, PK2_VALUE, PK3_VALUE, PK4_VALUE, PK5_VALUE), which store the application table name and the composite key values of the specific record the document is attached to. Additional columns like SEQ_NUM order multiple attachments, and ATTRIBUTE_CATEGORY/DATE provide descriptive flexfield support. The table also includes PROGRAM_ID, PROGRAM_APPLICATION_ID, and REQUEST_ID columns to manage attachments associated with concurrent programs and their execution requests.

Common Use Cases and Queries

A primary use case is generating reports of all documents attached to a specific entity, such as all files linked to a particular purchase order. Administrators may also query the table to audit attachment usage or clean up orphaned records. Common SQL patterns involve joining to FND_DOCUMENTS and the target application table. For example, to find documents attached to a specific concurrent request:

  • SELECT fad.seq_num, fd.title, fd.file_name FROM apps.fnd_attached_documents fad, apps.fnd_documents fd WHERE fad.document_id = fd.document_id AND fad.entity_name = 'FND_CONCURRENT_REQUESTS' AND fad.pk1_value = :request_id;

Another frequent pattern is retrieving attachments for a transactional entity, such as a journal entry in General Ledger (GL_JE_HEADERS), by using the appropriate ENTITY_NAME and primary key values stored in the PK* columns.

Related Objects

FND_ATTACHED_DOCUMENTS is a central hub with documented foreign key relationships to several key FND tables, as per the provided metadata:

  • FND_DOCUMENTS: The fundamental link via FND_ATTACHED_DOCUMENTS.DOCUMENT_ID. This join retrieves the core document metadata (title, file name, media type).
  • FND_CONCURRENT_REQUESTS: Linked via FND_ATTACHED_DOCUMENTS.REQUEST_ID. This relationship manages output files or supporting documents attached to a specific concurrent request instance.
  • FND_CONCURRENT_PROGRAMS: Linked via the composite key of FND_ATTACHED_DOCUMENTS.PROGRAM_APPLICATION_ID and FND_ATTACHED_DOCUMENTS.PROGRAM_ID. This supports attachments at the concurrent program definition level.

Furthermore, the table is referenced by the public Document Entity Application Programming Interface (DEAPI), specifically by packages like FND_DOCUMENTS_PKG and FND_ATTACHED_DOCUMENTS_PKG, which provide the standard procedures for attaching, querying, and deleting documents.