Search Results fnd_document_entities_tl




Overview
Explore in AI Chat

Overview

The FND_DOCUMENT_ENTITIES_TL table is a core translation table within the Application Object Library (FND) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. Residing in the APPLSYS schema, its primary role is to store translated, language-specific versions of the descriptive data for document entities. A document entity is a logical representation of a business document, such as a purchase order or invoice, within the EBS document management architecture. This table enables the system to present entity names and descriptions in a user's preferred language, supporting the multilingual capabilities essential for global deployments. It functions as a child table to the base table FND_DOCUMENT_ENTITIES, which holds the language-independent entity definitions.

Key Information Stored

The table's structure is designed to manage multilingual data through a combination of a key identifier, a language code, and the translated text. The critical columns, as indicated by the primary and unique keys, include DOCUMENT_ENTITY_ID, which links each translation row to its corresponding master record in FND_DOCUMENT_ENTITIES. The LANGUAGE column stores the language code (e.g., 'US' for American English). The USER_ENTITY_NAME column holds the translated name of the document entity as presented to end-users. Another significant column is DATA_OBJECT_CODE, which, along with LANGUAGE, forms a unique key, suggesting it is a stable identifier for the entity used within the translation context. The table also typically contains standard translation table columns such as SOURCE_LANG, CREATION_DATE, and LAST_UPDATE_DATE.

Common Use Cases and Queries

This table is primarily accessed for generating user interfaces and reports in the correct language or for administrative data audits. A common operational query retrieves the translated name for a specific entity in a session's current language. For example, to find all translations for a known DATA_OBJECT_CODE, one might use: SELECT language, user_entity_name FROM apps.fnd_document_entities_tl WHERE data_object_code = 'PO_HEADERS';. For reporting or troubleshooting, administrators often join this table with its base table to see all available translations: SELECT b.data_object_code, t.language, t.user_entity_name FROM apps.fnd_document_entities b, apps.fnd_document_entities_tl t WHERE b.document_entity_id = t.document_entity_id ORDER BY 1, 2;. This is essential for verifying translation completeness during implementation or upgrade projects.

Related Objects

The FND_DOCUMENT_ENTITIES_TL table has a direct and singular foreign key relationship with its base table, as documented in the provided metadata.

  • Foreign Key to FND_DOCUMENT_ENTITIES: The column FND_DOCUMENT_ENTITIES_TL.DOCUMENT_ENTITY_ID references FND_DOCUMENT_ENTITIES. This relationship enforces referential integrity, ensuring every translation record is associated with a valid master document entity definition. The standard join condition is fnd_document_entities_tl.document_entity_id = fnd_document_entities.document_entity_id.

While not listed in the brief metadata, this translation table is also conceptually related to the FND_LANGUAGES table, which defines the valid LANGUAGE values available within the EBS instance.