Results for “fnd_documents”

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

Overview

FND_DOCUMENTS is the central repository table within the Oracle E-Business Suite Application Object Library (FND) that stores metadata and attributes for documents registered in the Attachments and Document Management framework. Owned by the APPLSYS schema, this table defines the identity, classification, storage characteristics, and security attributes of each attachment or document known to the EBS instance. It does not hold the binary content of files itself; rather, it acts as a catalog describing where and how each document is persisted (database column, file system, URL, or WebDAV/Content Management repository) and to which category, concurrent request, or concurrent program it pertains.

The table is present and VALID in both Oracle EBS 12.1.1 and 12.2.2, with 30 documented columns in the 12.2.2 ETRM physical schema. Based on the foreign key topology mined from the metadata, FND_DOCUMENTS exhibits a hub-leaning Data Vault classification. It is a natural modeling suggestion to treat DOCUMENT_ID as a business hub key, with numerous downstream link tables (for example FND_ATTACHED_DOCUMENTS, FND_DOCUMENTS_TL, JTF_AMV_ATTACHMENTS) acting as satellites or links that reference it. This reflects its role as the single point of identity for a document that other subsystems attach to and describe.

Key Information Stored

The surrogate primary key is DOCUMENT_ID, enforced by FND_DOCUMENTS_PK. A unique index, FND_DOCUMENTS_U1, also exists on DOCUMENT_ID, making it the primary business-key candidate for identifying a row. Other significant columns include:

• DATATYPE_ID – identifies the type of data the document represents (for example, short text, long text, or binary).
• CATEGORY_ID – foreign key to FND_DOCUMENT_CATEGORIES, classifying the document into a functional attachment category.
• SECURITY_TYPE and SECURITY_ID – define the security model applied to the document; SECURITY_ID references EDR_PSIG_SECURITY.
• PUBLISH_FLAG – indicates whether the document is published or private.
• IMAGE_TYPE, STORAGE_TYPE, USAGE_TYPE – describe the media type, the physical storage mechanism, and the intended use of the document.
• START_DATE_ACTIVE and END_DATE_ACTIVE – effective dating for the document registration.
• REQUEST_ID – foreign key to FND_CONCURRENT_REQUESTS, linking documents generated or captured by a concurrent request.
• PROGRAM_APPLICATION_ID and PROGRAM_ID – foreign keys to FND_CONCURRENT_PROGRAMS identifying the owning concurrent program.
• URL, FILE_NAME, MEDIA_ID – location and naming attributes for externally or file-stored documents.
• DM_NODE, DM_FOLDER_PATH, DM_TYPE, DM_DOCUMENT_ID, DM_VERSION_NUMBER – Content Management/WebDAV repository identifiers and versioning metadata.
• ORIG_DOC_ID – reference to the originating document, useful for version or copy lineage.
• Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

FND_DOCUMENTS is primarily queried to resolve attachment identifiers into their descriptive and storage attributes. A common reporting pattern joins it to FND_ATTACHED_DOCUMENTS to list the attachments associated with a specific business entity:

• Locating documents tied to a concurrent request: SELECT document_id, file_name, url FROM fnd_documents WHERE request_id = :request_id;
• Enumerating documents in a category: SELECT d.document_id, d.file_name FROM fnd_documents d WHERE d.category_id = :category_id;
• Identifying externally stored vs. database-stored documents via STORAGE_TYPE for capacity or migration planning.
• Auditing security configuration by joining SECURITY_ID to EDR_PSIG_SECURITY.
• Reviewing Content Management integration metadata (DM_NODE, DM_DOCUMENT_ID, DM_VERSION_NUMBER) when troubleshooting WebDAV attachments.
• Reconciling attachments created by concurrent programs using the REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID foreign keys.

Related Objects

The following objects are the most significant consumers of or references to FND_DOCUMENTS, based on the documented foreign key relationships:

• FND_ATTACHED_DOCUMENTS – links documents to application entities via DOCUMENT_ID; the principal attachment association table.
• FND_DOCUMENTS_TL – translation table holding language-specific document descriptions, joined on DOCUMENT_ID.
• JTF_AMV_ATTACHMENTS – references DOCUMENT_ID for attachment management in the JTF (CRM/TeleSales) schema.
• OE_ATTACHMENT_RULES – references DOCUMENT_ID to define attachment rules in Order Management.
• PON_ATTACHMENTS_INTERFACE – references DOCUMENT_ID for purchasing attachment interfaces.
• FND_DOCUMENT_CATEGORIES – parent lookup for CATEGORY_ID.
• FND_CONCURRENT_REQUESTS – referenced through REQUEST_ID.
• FND_CONCURRENT_PROGRAMS – referenced through PROGRAM_APPLICATION_ID and PROGRAM_ID.
• EDR_PSIG_SECURITY – referenced through SECURITY_ID for digital signature security.