Results for “fnd_document_entities”

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

Overview

FND_DOCUMENT_ENTITIES is a core metadata table in the Oracle E-Business Suite Application Object Library (FND) product, residing in the APPLSYS schema. It serves as the registry of document entities — the abstract definitions of business objects that can participate in the Oracle EBS attachment and document management framework. Each row describes a logical entity (for example, a purchase order, an invoice, or a supplier record) together with the physical or logical database table that implements it and the primary key columns required to uniquely identify a single instance of that entity.

Because the table defines how the attachment subsystem recognizes and locates business documents, it is consulted at runtime whenever a user attaches a file, URL, or text note to a record in the EBS Forms interface or through the public attachment APIs. The table acts as a bridge between user-facing attachments and the underlying transactional data model.

Under the heuristic Data Vault classification supplied in the metadata, this object is characterized as hub-leaning: the DOCUMENT_ENTITY_ID surrogate key functions as a stable hub identifier for each registered entity, while the business-key candidates are captured through the unique indexes described below. This classification is offered as a modeling suggestion rather than a documented Oracle design intent.

Key Information Stored

Of the sixteen documented columns, the most operationally significant are:

• DOCUMENT_ENTITY_ID — the system-generated surrogate primary key, enforced by FND_DOCUMENT_ENTITIES_PK. It uniquely identifies each registered document entity row.
• DATA_OBJECT_CODE — the developer-facing business key. This code is the value referenced by the attachment framework and by related extension tables to link an entity definition to actual attachment records.
• APPLICATION_ID — the owning FND_APPLICATION (product) to which the entity belongs, enabling product-scoped filtering.
• TABLE_NAME — the underlying database table that physically stores the entity instances.
• ENTITY_NAME — the EBS entity name used by the document management and Attachments APIs to resolve the object.
• PK1_COLUMN through PK5_COLUMN — up to five columns forming the concatenated primary key of the target entity. These drive the WHERE clause the attachment framework builds to locate a specific document instance.
• ZD_EDITION_NAME — the edition indicator supporting online patching and edition-based redefinition in EBS 12.2.2.

The unique indexes FND_DOCUMENT_ENTITIES_U1 (DOCUMENT_ENTITY_ID, ZD_EDITION_NAME) and FND_DOCUMENT_ENTITIES_U2 (DATA_OBJECT_CODE, ZD_EDITION_NAME) confirm that DATA_OBJECT_CODE is the effective business-key candidate alongside the surrogate key. Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) support change tracking. The table is largely static reference data: DBA data shows the shipped row population is small and changes infrequently.

Common Use Cases and Queries

The most frequent reporting need is identifying the physical table and key columns for a given attachment-enabled entity, so that customizations or extension reports can resolve attachment data:

SELECT data_object_code, entity_name, table_name,
       pk1_column, pk2_column, pk3_column
FROM   fnd_document_entities
WHERE  data_object_code = :p_code;

A second pattern lists all entities registered for a specific product:

SELECT fde.data_object_code, fde.entity_name, fa.application_short_name
FROM   fnd_document_entities  fde,
       fnd_application        fa
WHERE  fde.application_id = fa.application_id;

Integration scenarios commonly join FND_DOCUMENT_ENTITIES to FND_ATTACHMENT_BLK_ENTITIES to determine which block-level attachment definitions exist for an entity, and to OE_AK_OBJECTS_EXT when Order Management object metadata is required. Because the table controls the attachment API's key lookup, cache duration, and table resolution, DBAs should treat changes to this table with the same rigor as other FND configuration data; direct updates bypass supported diagnostic and setup flows.

Related Objects

• FND_APPLICATION — joined on FND_DOCUMENT_ENTITIES.APPLICATION_ID to identify the owning product.
• FND_DOCUMENT_ENTITIES_TL — the translated table, joined on DOCUMENT_ENTITY_ID, supplying user-facing entity descriptions in multiple languages.
• FND_ATTACHMENT_BLK_ENTITIES — references DATA_OBJECT_CODE, defining block-level attachment behavior for each entity.
• OE_AK_OBJECTS_EXT — references DATA_OBJECT_CODE, extending Order Management object definitions with EBS document entity metadata.
• FND_ATTACHMENTS and the related FND_ATTACHMENT_FUNCTIONS, FND_ATTACHED_DOCUMENTS — the runtime consumers that resolve an attachment to its owning entity using the definition stored here.
• FND_DOCUMENT_ENTITIES_PK / _U1 / _U2 — the primary and unique indexes that enforce entity and business-key uniqueness.