Search Results fnd_attachment_blocks_uk1

Overview

The FND_ATTACHMENT_BLOCKS table is a core repository table within the Oracle E-Business Suite Application Object Library (FND). It functions as a configuration registry that defines which specific UI blocks or forms are enabled to support the attachment of files, notes, or URLs. This table is fundamental to the EBS Attachment Manager framework, which provides a unified interface for associating documents with transactional data across the application. Its role is to establish the link between a high-level attachment function and the individual user interface components where attachments can be created and viewed. This configuration-driven approach allows for centralized control and consistent behavior of attachment features in both Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table stores metadata that maps attachment-enabled blocks to their parent attachment functions. The primary columns include ATTACHMENT_BLK_ID, which serves as the unique system-generated identifier (primary key). The ATTACHMENT_FUNCTION_ID is a foreign key that links the block to its parent function defined in the FND_ATTACHMENT_FUNCTIONS table. The BLOCK_NAME column holds the internal name of the specific form block or UI region that is configured for attachments. Together, the ATTACHMENT_FUNCTION_ID and BLOCK_NAME form a unique constraint (FND_ATTACHMENT_BLOCKS_UK1), ensuring a block is only registered once per function.

Common Use Cases and Queries

A primary use case is diagnosing attachment functionality issues or generating configuration reports. Developers and administrators query this table to verify if a specific block is correctly registered within the attachment framework. For instance, to list all blocks enabled for attachments under a specific function, one might execute: SELECT block_name FROM apps.fnd_attachment_blocks WHERE attachment_function_id = (SELECT attachment_function_id FROM apps.fnd_attachment_functions WHERE function_name = '<FUNCTION_NAME>');. Another common scenario involves joins to understand the full hierarchy, such as joining to FND_ATTACHMENT_FUNCTIONS to see all functions and their associated blocks, or to FND_ATTACHMENT_BLK_ENTITIES to see the specific entity columns within each block that are attachment-enabled.

Related Objects

The table sits at the center of a key relationship hierarchy in the attachment subsystem. It directly references the FND_ATTACHMENT_FUNCTIONS table via the foreign key on the ATTACHMENT_FUNCTION_ID column. This defines the parent function for the block. Conversely, the FND_ATTACHMENT_BLOCKS table is referenced as a parent by the FND_ATTACHMENT_BLK_ENTITIES table through the foreign key on ATTACHMENT_BLK_ID. This relationship allows for the further granular definition of specific columns or entities within a block that can store attachments. These documented foreign key relationships are critical for navigating the complete attachment configuration data model.