Results for “fnd_document_entities_tl”

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

Overview

FND_DOCUMENT_ENTITIES_TL is the translation table for FND_DOCUMENT_ENTITIES in the Oracle E-Business Suite Application Object Library (FND) schema. It resides in the APPLSYS schema and stores language-specific, translated attributes for each document entity row defined in the base table. Document entities represent the catalog of business documents that Oracle EBS knows how to attach, categorize, or otherwise process — for example, purchase orders, invoices, or journal entries. Because Oracle EBS is deployed in multilingual environments, any user-facing text associated with these entities (such as the prompt or display name shown to end users) is stored separately per language in this table, following the standard "_TL" translation-table pattern used throughout the EBS data model.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as satellite-leaning. This is a heuristic derived from its foreign-key structure: the table is dependent on FND_DOCUMENT_ENTITIES via a foreign key and carries descriptive, language-scoped attributes rather than serving as a hub or link. It should be treated as a descriptive satellite keyed by entity identity plus language.

Key Information Stored

The table is keyed primarily by DOCUMENT_ENTITY_ID together with LANGUAGE, forming the FND_DOCUMENT_ENTITIES_TL_PK primary key. The most significant columns are:

• DOCUMENT_ENTITY_ID — surrogate identifier for the underlying document entity; foreign key to FND_DOCUMENT_ENTITIES, and part of the composite primary key.
• LANGUAGE — the language code for which the translated values apply; the second component of the primary key.
• DATA_OBJECT_CODE — the internal code that identifies the data object associated with the entity; a business-key candidate (index FND_DOCUMENT_ENTITIES_TL_U1 alongside LANGUAGE and ZD_EDITION_NAME).
• USER_ENTITY_NAME — the user-facing name of the entity in the given language; a business-key candidate (index FND_DOCUMENT_ENTITIES_TL_U2 alongside LANGUAGE and ZD_EDITION_NAME).
• USER_ENTITY_PROMPT — the prompt or label displayed to users for the entity in that language.
• SOURCE_LANG — the source language from which the translation derives, used for translation tracking.
• ZD_EDITION_NAME — editioning column supporting Online Patching (adoption in 12.2.x multi-tenant/editioned environments).

Standard audit columns are also present: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The distinction between the surrogate key (DOCUMENT_ENTITY_ID, LANGUAGE) and the business-key candidates (DATA_OBJECT_CODE and USER_ENTITY_NAME) is important when designing joins or deduplication logic.

Common Use Cases and Queries

Typical scenarios involve retrieving the translated display name and prompt for document entities in a specific language, or joining this table to the base entity table to report on entity metadata across languages. A common pattern is to filter by LANGUAGE to resolve the correct translation for the current session.

• Resolve prompts for attachments or document categorization in reports:

SELECT de.DOCUMENT_ENTITY_ID, t.USER_ENTITY_NAME, t.USER_ENTITY_PROMPT
FROM   FND_DOCUMENT_ENTITIES de,
       FND_DOCUMENT_ENTITIES_TL t
WHERE  de.DOCUMENT_ENTITY_ID = t.DOCUMENT_ENTITY_ID
AND    t.LANGUAGE = USERENV('LANG');

• Reporting on language coverage: group translations by DATA_OBJECT_CODE to identify entities missing a given language variant.
• Integration and data-migration work: verify business-key uniqueness against the U1 and U2 unique indexes before inserting or updating translation rows.

Related Objects

The primary related objects are the base entity table and its dependent structures:

• FND_DOCUMENT_ENTITIES — the base (non-translated) table joined via DOCUMENT_ENTITY_ID; this is the parent referenced by the documented foreign key.
• FND_DOCUMENT_ENTITIES_TL_PK / _U1 / _U2 — the primary and unique indexes that enforce entity-language uniqueness and business-key candidates.
• FND_DOCUMENTS_TL and FND_DOCUMENTS — related document-catalog translation and base tables typically referenced alongside entity definitions.
• FND_ATTACHED_DOCUMENTS — attaches actual documents and frequently resolves entity prompts via this translation table.
• FND_DOCUMENT_CATEGORIES_TL / FND_DOCUMENT_CATEGORIES — related categorization translation objects in the same FND family.

Because the table participates in the FND document framework, joins almost always originate from the base entity table and fan out into this translation table filtered by LANGUAGE.