Search Results fnd_attached_documents

The FND_ATTACHED_DOCUMENTS table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical repository for managing document attachments across various modules. It serves as a centralized storage mechanism for associating files, URLs, or text notes with transactional data, enabling seamless document integration within business processes. This table is part of Oracle's Document Management System (DMS) and is tightly integrated with the FND_DOCUMENTS and FND_LOBS tables to provide a comprehensive attachment framework.

Table Structure and Key Columns

The FND_ATTACHED_DOCUMENTS table contains metadata that links documents to application entities through a flexible key structure. Key columns include:

• ATTACHED_DOCUMENT_ID: Primary key identifier for the attachment record
• DOCUMENT_ID: Foreign key reference to FND_DOCUMENTS
• ENTITY_NAME: Application-specific entity name (e.g., 'AP_INVOICES')
• PK1_VALUE: First primary key value of the parent entity
• PK2_VALUE, PK3_VALUE, PK4_VALUE, PK5_VALUE: Additional key values for composite keys
• CREATION_DATE, CREATED_BY: Audit columns
• LAST_UPDATE_DATE, LAST_UPDATED_BY: Audit columns

Functional Architecture

The table operates within a three-tier architecture:

1. Attachment Definition: Metadata stored in FND_ATTACHED_DOCUMENTS
2. Document Metadata: Descriptive information in FND_DOCUMENTS
3. Content Storage: Actual content in FND_LOBS (for files) or as text/URL references

Integration Patterns

The attachment framework supports multiple integration methods:

• Form-based Attachments: Through standard Oracle Forms interface
• Web ADI: For bulk document uploads
• API-based: Using FND_ATTACHED_DOCUMENTS_PKG
• SOA Integration: For web service-based attachments

Technical Considerations

Key technical aspects include:

• Indexing Strategy: Composite indexes on (ENTITY_NAME, PK1_VALUE...) for performance
• Partitioning: Recommended for high-volume implementations
• Security Model: Inherits security from parent entities
• Storage Optimization: LOB storage parameters critical for performance

Common Use Cases

Typical implementations include:

• Invoice supporting documents in AP
• Contract attachments in Procurement
• Design documents in Engineering
• HR employee documents

Version-Specific Features

In EBS 12.2.2, enhancements include:

• Improved Web UI integration
• Enhanced REST API support
• Better content security features
• Integration with Oracle WebCenter Content

Best Practices

Implementation should consider:

• Regular purging of obsolete attachments
• Monitoring growth patterns
• Implementing retention policies
• Considering external content management for large files

The FND_ATTACHED_DOCUMENTS table remains a cornerstone of Oracle EBS document management, providing flexible, scalable attachment capabilities while maintaining tight integration with transactional data. Proper implementation ensures compliance, improves process efficiency, and enhances user productivity across the enterprise.