Results for “fnd_attached_documents”

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

Overview

FND_ATTACHED_DOCUMENTS is a core Applications Object Library (FND) table in Oracle E-Business Suite, owned by the APPLSYS schema and validated in releases 12.1.1 and 12.2.2. It implements the attachment framework that binds a physical or logical document record to a specific business entity within the E-Business Suite. Each row represents one attachment instance: it links a row in FND_DOCUMENTS (the document itself, including file content or URL) to an owning entity identified by ENTITY_NAME plus the generic PK1_VALUE through PK5_VALUE columns. Because the same document can be attached to multiple entities and the same entity can carry multiple attachments, the table functions as an intersection or association structure.

The ETRM metadata carries a heuristic Data Vault classification of link. As a modeling suggestion, FND_ATTACHED_DOCUMENTS behaves as a classic link table: it resolves many-to-many relationships between FND_DOCUMENTS and the various business entities (or concurrent requests) that consume them, while also carrying descriptive and audit attributes. This classification should be treated as a starting heuristic rather than a canonical warehouse design.

Key Information Stored

The table contains 40 documented columns. The most significant are:

• ATTACHED_DOCUMENT_ID — surrogate primary key, enforced by FND_ATTACHED_DOCUMENTS_PK and also covered by unique index FND_ATTACHED_DOCUMENTS_U1. This is the business-key candidate and the value referenced by downstream tables.
• DOCUMENT_ID — foreign key to FND_DOCUMENTS, identifying the stored document (file, URL, or text) that is attached.
• ENTITY_NAME — the name of the owning entity to which the document is attached (for example, an application entity or concurrent program context).
• PK1_VALUE, PK2_VALUE, PK3_VALUE, PK4_VALUE, PK5_VALUE — the composite key values of the owning entity instance, providing a generic pointer that supports attachment to virtually any business object.
• SEQ_NUM — ordering sequence for attachments sharing the same entity.
• REQUEST_ID — foreign key to FND_CONCURRENT_REQUESTS, supporting attachments tied to concurrent request output.
• PROGRAM_APPLICATION_ID and PROGRAM_ID — foreign key components to FND_CONCURRENT_PROGRAMS, identifying the concurrent program associated with the attachment.
• AUTOMATICALLY_ADDED_FLAG — indicates whether the attachment was created automatically by the system versus manually by a user.
• CATEGORY_ID — categorizes the attachment for retrieval and display purposes.
• STATUS — lifecycle or state indicator of the attachment record.
• ORIG_ATTACH_DOC_ID — reference to the originating attached document, useful for copies or propagated attachments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns present on most FND tables.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle Flexfield descriptive attribute set for extensibility.

Common Use Cases and Queries

The table is queried whenever attachment information must be reported, migrated, or audited. Typical patterns include retrieving all attachments for a given entity, joining to FND_DOCUMENTS to obtain the actual file name or URL, and reporting attachments associated with concurrent requests.

• List attachments by entity: SELECT a.attached_document_id, a.document_id, d.file_name FROM fnd_attached_documents a, fnd_documents d WHERE a.document_id = d.document_id AND a.entity_name = :entity AND a.pk1_value = :pk1;
• Attachments for a concurrent request: join REQUEST_ID to FND_CONCURRENT_REQUESTS and PROGRAM_APPLICATION_ID/PROGRAM_ID to FND_CONCURRENT_PROGRAMS.
• Audit of automatic attachments: filter on AUTOMATICALLY_ADDED_FLAG and CREATED_BY/CREATION_DATE to trace system-generated links.
• Downstream reporting: examine ECE_ATTACHMENT_HEADERS, ECE_ATTACHMENT_DETAILS, and SO_NOTE_REFERENCES, all of which key back through ATTACHED_DOCUMENT_ID.

Related Objects

• FND_DOCUMENTS — joined via DOCUMENT_ID; supplies the document content and metadata.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID; links attachments to concurrent request output.
• FND_CONCURRENT_PROGRAMS — joined via PROGRAM_APPLICATION_ID and PROGRAM_ID; identifies the generating program.
• ECE_ATTACHMENT_HEADERS — references FND_ATTACHED_DOCUMENTS.ATTACHED_DOCUMENT_ID.
• ECE_ATTACHMENT_DETAILS — references FND_ATTACHED_DOCUMENTS.ATTACHED_DOCUMENT_ID.
• SO_NOTE_REFERENCES — references FND_ATTACHED_DOCUMENTS.ATTACHED_DOCUMENT_ID.