Search Results pon_attachments_interface

Overview

The FND_DOCUMENTS table is a core repository within the Application Object Library (FND) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the central master table for storing metadata and references to documents managed by the EBS document attachment system. This system enables the association of files and descriptive text with virtually any entity across the application, such as purchase orders, invoices, or customers. The table, owned by the APPLSYS schema, provides the foundational structure for the document lifecycle, linking document definitions to their categories, associated programs, and the actual physical or logical content stored elsewhere.

Key Information Stored

The table's primary key is DOCUMENT_ID, which uniquely identifies each document record. Key columns include CATEGORY_ID, which links to FND_DOCUMENT_CATEGORIES to classify the document type (e.g., 'Purchase Order', 'Specification'). The REQUEST_ID column associates the document with a specific concurrent request run, linking to FND_CONCURRENT_REQUESTS. For programmatically generated documents, PROGRAM_APPLICATION_ID and PROGRAM_ID link to FND_CONCURRENT_PROGRAMS. Other critical columns typically include DATATYPE_ID (defining the media type), TITLE, DESCRIPTION, and various audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY). The table stores document metadata and references, while the actual file data is typically housed in related structures like FND_LOBS.

Common Use Cases and Queries

A primary use case is querying documents attached to a specific business entity, which often involves joining FND_DOCUMENTS with FND_ATTACHED_DOCUMENTS. For example, to find all documents linked to a particular purchase order header (entity_name='PO_HEADERS'), one would use a query joining these tables on DOCUMENT_ID. Another common scenario is generating a report of all documents created within a date range or by a specific category. Administrators may also query the table to audit document usage or clean up orphaned records. A basic pattern to retrieve document metadata is:

• SELECT d.document_id, d.title, d.description, c.name category_name FROM apps.fnd_documents d, apps.fnd_document_categories_tl c WHERE d.category_id = c.category_id AND c.language = USERENV('LANG');

Related Objects

FND_DOCUMENTS is a central hub with several key dependencies. The FND_ATTACHED_DOCUMENTS table provides the crucial linkage between a DOCUMENT_ID and application entities. Descriptive translations are stored in the FND_DOCUMENTS_TL table. Document categories are defined in FND_DOCUMENT_CATEGORIES. As per the provided metadata, it is also referenced by objects in other modules, including JTF_AMV_ATTACHMENTS (Marketing), OE_ATTACHMENT_RULES (Order Management), and PON_ATTACHMENTS_INTERFACE (Purchasing), demonstrating its cross-functional role. The foreign keys to FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS integrate document generation with the concurrent processing framework.