Results for “fnd_attachment_blocks”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_ATTACHMENT_BLOCKS is a core configuration table in the Oracle E-Business Suite FND (Application Object Library) schema, owned by APPLSYS. It records the individual form blocks within an Oracle Forms-based application function for which the Attachments feature has been enabled. In effect, this table defines the granular attachment "hooks" that the EBS Attachments framework recognizes at runtime — each row maps a named block to a parent attachment function, allowing the system to determine which DFF-style attachments entity is exposed on a given form and block combination.

From a Data Vault modeling perspective, the mined FK structure (a single reference to FND_ATTACHMENT_FUNCTIONS plus downstream references from FND_ATTACHMENT_BLK_ENTITIES) suggests a satellite-leaning classification. FND_ATTACHMENT_BLOCKS behaves as a descriptive child that captures the attributes and configuration context of an attachment function, rather than serving as the central hub of the attachment model. This is a heuristic suggestion only; the table is documented as a standard 12.2.2 VALID object with 17 columns.

Key Information Stored

The table's surrogate primary key is ATTACHMENT_BLK_ID (enforced by FND_ATTACHMENT_BLOCKS_PK). Two unique business-key candidates are documented:

• FND_ATTACHMENT_BLOCKS_U1 — (ATTACHMENT_BLK_ID, ZD_EDITION_NAME), the edition-aware form of the primary key.
• FND_ATTACHMENT_BLOCKS_U2 — (ATTACHMENT_FUNCTION_ID, BLOCK_NAME, ZD_EDITION_NAME), the true business key ensuring a block name is unique within its parent function.

The most significant columns include:

• ATTACHMENT_BLK_ID — surrogate primary key identifying the block row.
• ATTACHMENT_FUNCTION_ID — foreign key to FND_ATTACHMENT_FUNCTIONS; identifies the owning attachment function.
• BLOCK_NAME — the Oracle Forms block name on which attachments are enabled.
• QUERY_FLAG — controls whether the block supports attachments querying.
• SECURITY_TYPE — determines the security model applied to attachments on this block.
• ORG_CONTEXT_FIELD, SET_OF_BOOKS_CONTEXT_FIELD, BUSINESS_UNIT_CONTEXT_FIELD — context fields used to scope attachments by operating unit, set of books, or business unit.
• CONTEXT1_FIELD, CONTEXT2_FIELD, CONTEXT3_FIELD — generic context DFF fields for additional specialization.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ZD_EDITION_NAME — editioning marker used by the Online Patching (adop) architecture in 12.2.

Common Use Cases and Queries

Administrators and developers query this table to diagnose why the paperclip attachment icon does not appear on a form, to confirm which blocks have attachments configured for a given function, and to audit security and context setup. A representative query joins the block to its parent function:

• SELECT b.ATTACHMENT_BLK_ID, b.BLOCK_NAME, b.QUERY_FLAG, b.SECURITY_TYPE, f.ATTACHMENT_FUNCTION_NAME FROM FND_ATTACHMENT_BLOCKS b, FND_ATTACHMENT_FUNCTIONS f WHERE b.ATTACHMENT_FUNCTION_ID = f.ATTACHMENT_FUNCTION_ID AND b.BLOCK_NAME = :block_name;

Reporting use cases include inventorying enabled attachment blocks per application, verifying that ORG_CONTEXT_FIELD / BUSINESS_UNIT_CONTEXT_FIELD are populated where multi-org security is required, and reconciling the block registry against runtime entity registrations in FND_ATTACHMENT_BLK_ENTITIES.

Related Objects

• FND_ATTACHMENT_FUNCTIONS — referenced via FND_ATTACHMENT_BLOCKS.ATTACHMENT_FUNCTION_ID; the parent that defines the attachment function.
• FND_ATTACHMENT_BLK_ENTITIES — references this table via ATTACHMENT_BLK_ID; stores the entity-level attachment registrations tied to each block.
• FND_ATTACHMENT_BLOCKS_PK / _U1 / _U2 — primary and unique indexes enforcing identity and the business key.
• Related attachment framework objects such as FND_ATTACHMENTS, FND_ATTACHMENT_LINKS, and FND_DOCUMENTS operate downstream of the block/function configuration and are commonly joined for end-to-end troubleshooting.