Results for “fnd_attachment_blk_entities”

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

Overview

FND_ATTACHMENT_BLK_ENTITIES is a configuration table in the Oracle E-Business Suite Application Object Library (FND) schema, APPLSYS. It defines the individual data entities that participate within a defined attachment block, effectively binding an attachment block to the specific document or data object it is permitted to serve. In Oracle EBS 12.1.1 and 12.2.2, this table underpins the attachment framework used throughout the applications, where users attach files, URLs, or text notes to business records such as invoices, purchase orders, or journal entries. Each row describes how an entity is presented and secured inside its parent block, including display behavior, query and DML permissions, and optional filter conditions.

From a heuristic Data Vault modeling perspective, this object classifies as a link. It resolves the relationship between two hubs-like references — the attachment block (FND_ATTACHMENT_BLOCKS) and the document entity (FND_DOCUMENT_ENTITIES) — and carries descriptive attributes that would then be modeled as a satellite.

Key Information Stored

The table holds 26 documented columns in 12.2.2. The most operationally significant are:

• ATTACHMENT_BLK_ENTITY_ID — surrogate primary key, uniquely identifying each block-entity association (FND_ATTACHMENT_BLK_ENTITIES_PK).
• ATTACHMENT_BLK_ID — foreign key to FND_ATTACHMENT_BLOCKS, identifying the parent attachment block.
• DATA_OBJECT_CODE — foreign key to FND_DOCUMENT_ENTITIES, identifying the target document entity.
• DISPLAY_METHOD — controls how the attachment entity is rendered in the UI.
• INCLUDE_IN_INDICATOR_FLAG and INDICATOR_IN_VIEW_FLAG — determine whether descriptive indicators appear for this entity.
• QUERY_PERMISSION_TYPE, INSERT_PERMISSION_TYPE, UPDATE_PERMISSION_TYPE, DELETE_PERMISSION_TYPE — define CRUD security for the entity.
• PK1_FIELD through PK5_FIELD — additional key columns mapping the entity's primary key.
• SQL_STATEMENT — optional query driving entity population.
• CONDITION_FIELD, CONDITION_OPERATOR, CONDITION_VALUE1, CONDITION_VALUE2 — define filtering conditions.
• ZD_EDITION_NAME — editioning support column enabling Online Patching in 12.2.x.

The business-key candidates are captured by unique indexes FND_ATTACHMENT_BLK_ENTITIES_U1 (ATTACHMENT_BLK_ENTITY_ID, ZD_EDITION_NAME) and FND_ATTACHMENT_BLK_ENTITIES_U2 (ATTACHMENT_BLK_ID, DATA_OBJECT_CODE, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include tracing which document entities belong to a given attachment block, and auditing permission behavior. A representative join returns block-to-entity mappings:

• Listing entities per block: SELECT e.ATTACHMENT_BLK_ENTITY_ID, e.DATA_OBJECT_CODE, e.DISPLAY_METHOD FROM FND_ATTACHMENT_BLK_ENTITIES e WHERE e.ATTACHMENT_BLK_ID = :blk_id;
• Joining to FND_ATTACHMENT_BLOCKS on ATTACHMENT_BLK_ID to resolve block names and owning application.
• Joining to FND_DOCUMENT_ENTITIES on DATA_OBJECT_CODE to obtain entity descriptions.
• Reviewing CRUD permission columns to troubleshoot why users cannot insert or delete attachments against a record.

Related Objects

• FND_ATTACHMENT_BLOCKS — parent block definition, joined on ATTACHMENT_BLK_ID.
• FND_DOCUMENT_ENTITIES — document entity definitions, joined on DATA_OBJECT_CODE.
• FND_ATTACHMENT_FUNCTIONS — functions associated with attachment blocks.
• FND_ATTACHMENTS — actual attachment instances governed by block-entity configuration.
• FND_ATTACHED_DOCUMENTS — links attachments to entity records.
• FND_DOCUMENTS — underlying document definitions referenced by attachments.