Search Results fnd_attachment_functions




Overview
Explore in AI Chat

Overview

The FND_ATTACHMENT_FUNCTIONS table is a core repository within the Oracle E-Business Suite Application Object Library (FND). It serves as the master registry that defines which forms, form functions, and concurrent programs are enabled to support the Attachment Framework. This framework allows users to attach documents, files, or notes directly to specific business objects and transactions. The table's primary role is to establish a link between a navigable application entity (like a form) and the underlying attachment functionality, thereby controlling where attachments can be created and viewed within the application's user interface. It is a critical component for enabling and managing document-centric processes across both Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure centers on identifying the application entity and its type. The primary key, ATTACHMENT_FUNCTION_ID, is a unique system-generated identifier. The most significant columns for functional configuration are APPLICATION_ID, FUNCTION_ID, and FUNCTION_TYPE. The APPLICATION_ID and FUNCTION_ID together identify the specific program or form, while the FUNCTION_TYPE column distinguishes whether the referenced entity is a 'FORM', 'FUNCTION', or 'CONCURRENT PROGRAM'. This triplet of columns is protected by a unique key constraint (FND_ATTACHMENT_FUNCTIONS_UK1), ensuring that a given entity is registered only once for attachment purposes. The table does not store the attachments themselves but acts as a pointer to entities that can have attachments.

Common Use Cases and Queries

A primary use case is auditing or reporting on which application functions are attachment-enabled. System administrators may run queries to verify setup or troubleshoot missing attachment features. A common pattern is to join with FND_FORM_FUNCTIONS or FND_CONCURRENT_PROGRAMS to get the executable name. For example, to list all registered concurrent programs:

Another critical scenario involves data migration or patching, where scripts may need to insert or update records in this table to enable attachments for custom-developed forms or programs, ensuring they adhere to the same integration standards as seeded Oracle functionality.

Related Objects

FND_ATTACHMENT_FUNCTIONS sits at the center of a key data model. It has foreign key relationships to several foundational tables: FND_FORM_FUNCTIONS, FND_FORM, and FND_CONCURRENT_PROGRAMS, which supply the entity details. More importantly, it is referenced as a parent table by objects that manage the attachment details. The FND_ATTACHMENT_BLOCKS table defines specific UI blocks within a form that can host attachments, linking back via ATTACHMENT_FUNCTION_ID. Similarly, FND_DOC_CATEGORY_USAGES, which controls the document categories available for a given function, also references this table. These relationships illustrate how this table is the gateway that connects an application's navigational structure to its document attachment capabilities.