Search Results fnd_documents




The FND_DOCUMENTS table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 serves as a central repository for document metadata, facilitating document management across various modules. This table is part of the Oracle Application Object Library (FND) and stores essential attributes of documents, such as document IDs, titles, descriptions, and associated application details, while the actual document content is typically stored in the FND_LOBS table as BLOB (Binary Large Object) data. ### **Key Columns in FND_DOCUMENTS** The table includes critical columns that define document properties and relationships: - DOCUMENT_ID: A unique identifier for each document, often referenced in other modules. - APPLICATION_ID: Associates the document with a specific Oracle EBS application (e.g., AP, AR, GL). - TITLE and DESCRIPTION: Human-readable metadata for document identification. - CATEGORY_ID: Classifies documents into predefined categories (linked to FND_DOCUMENT_CATEGORIES). - SECURITY_TYPE and SECURITY_ID: Control access permissions, often tied to responsibilities or user roles. - PUBLISH_FLAG: Indicates whether the document is publicly accessible. - USAGE_TYPE: Defines the document's purpose (e.g., "ATTACHMENT", "TEMPLATE"). ### **Integration with Oracle EBS Modules** The FND_DOCUMENTS table supports document attachments in modules like: - **Payables (AP)**: Invoice attachments. - **Receivables (AR)**: Customer correspondence. - **General Ledger (GL)**: Journal entry supporting documents. - **Projects (PA)**: Project deliverables or contracts. Documents are typically uploaded via Oracle Forms or the WebADI interface, with metadata written to FND_DOCUMENTS and content stored in FND_LOBS. The FND_ATTACHED_DOCUMENTS table links documents to transactional entities (e.g., invoice IDs, journal IDs) using ENTITY_NAME and PK1_VALUE columns. ### **Technical Workflow** 1. **Document Upload**: A user attaches a file via an EBS form, triggering an API (e.g., fnd_webattch.add_attachment). 2. **Metadata Storage**: The system inserts a record into FND_DOCUMENTS with a generated DOCUMENT_ID. 3. **Content Storage**: The BLOB data is written to FND_LOBS, linked via DOCUMENT_ID. 4. **Entity Association**: A cross-reference entry is created in FND_ATTACHED_DOCUMENTS to tie the document to a transaction. ### **Security and Performance Considerations** - **Access Control**: Documents inherit security from the linked entity or use SECURITY_TYPE for role-based restrictions. - **Indexing**: DOCUMENT_ID and APPLICATION_ID are indexed for efficient querying. - **Purging**: Obsolete documents should be archived using FND_DOCUMENTS_PKG APIs to prevent table bloating. ### **Customization and Extensions** Developers can extend functionality by: - Creating custom document categories via FND_DOCUMENT_CATEGORIES. - Leveraging Oracle Workflow for document approval processes. - Using BI Publisher to generate reports on document metadata. In summary, FND_DOCUMENTS is a foundational component of Oracle EBS document management, enabling secure, modular, and auditable document storage. Proper utilization of its metadata structure ensures seamless integration with transactional workflows while maintaining compliance and performance.