Results for “edr_files_tl”

40 results




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

Overview

EDR_FILES_TL is the translation (language) table for the ERES File Upload System within the EDR – E-Records product module of Oracle E-Business Suite. It stores the language-dependent, descriptive attributes of files that have been uploaded through the ERES file upload framework, allowing a single uploaded file record to carry translated descriptive text across the languages enabled in the EBS instance. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the EDR schema and is reported as VALID in the data dictionary.

The object follows the standard EBS multilingual (_TL) design pattern: the base (non-translated) file definition is held in a companion base table, while EDR_FILES_TL holds one row per file per installed language. The documented primary key is EDR_FILES_TL_P, composed of FILE_ID and LANGUAGE, and this same index is the only documented unique, business-key candidate. Because the table contains no foreign keys to other tables in the mined relationship data, its heuristic Data Vault classification is standalone. In Data Vault modeling terms this is best treated as a descriptive satellite attached to the FILE_ID business key, rather than as a hub or a link.

Key Information Stored

The documented physical schema for 12.2.2 contains nine columns, combining the composite key, the translated descriptive attribute, and the standard EBS audit columns.

  • FILE_ID – Surrogate identifier of the uploaded file. Part of the EDR_FILES_TL_P primary key and the join column back to the base file record.
  • LANGUAGE – Installed language code for the translation row. The second component of the composite primary key.
  • SOURCE_LANG – The language from which the current row is derived; used by the translation framework to determine the source text for a given language.
  • DESCRIPTION – The translated descriptive text for the uploaded file; the principal language-dependent business attribute maintained in this table.
  • CREATED_BY, CREATION_DATE – Standard audit columns recording the user and timestamp of row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE – Standard audit columns recording the last modifying user, login session, and timestamp.

The surrogate key is FILE_ID plus LANGUAGE. There is no separate single-column surrogate; the ONLY documented unique index, EDR_FILES_TL_P (FILE_ID, LANGUAGE), serves simultaneously as primary key and business-key candidate, meaning the natural grain of the table is one translation row per file per language.

Common Use Cases and Queries

Typical uses center on retrieving the correct localized description of an uploaded ERES file for a given session language, on auditing translations, and on reporting file inventories by language. Because the table is language-keyed, queries should constrain LANGUAGE (or join to the base table, which typically filters on the current language) to avoid returning every translated row for the same FILE_ID.

  • Retrieve the description of a file in a specific language: SELECT FILE_ID, LANGUAGE, DESCRIPTION FROM EDR.EDR_FILES_TL WHERE FILE_ID = :file_id AND LANGUAGE = USERENV('LANG');
  • List all translations available for a file: SELECT LANGUAGE, SOURCE_LANG, DESCRIPTION, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM EDR.EDR_FILES_TL WHERE FILE_ID = :file_id ORDER BY LANGUAGE;
  • Audit recently changed translations: SELECT FILE_ID, LANGUAGE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM EDR.EDR_FILES_TL WHERE LAST_UPDATE_DATE > SYSDATE - 30;
  • Coverage reporting, identifying files that lack a translation for an enabled language, by comparing the distinct FILE_ID/LANGUAGE pairs in EDR_FILES_TL against the set of installed languages and the base file table.

When joining to the base table, restrict the join to the active language to preserve one-row-per-file reporting semantics; unrestricted joins will multiply rows by the number of installed languages.

Related Objects

The mined relationship data classifies EDR_FILES_TL as standalone, with no documented foreign keys. The most significant related objects are therefore the ERES file base table and the dependent reporting and lookup objects that operate on the FILE_ID key.

  • EDR_FILES (base table) – Stores the language-independent file record; joined to EDR_FILES_TL on FILE_ID.
  • EDR_FILES_TL_P – The composite unique index/primary key on (FILE_ID, LANGUAGE) that enforces translation uniqueness.
  • EDR_FILES_B / EDR_FILES_V – The base and possibly view layers exposing file data joined with translated DESCRIPTION.
  • ERES File Upload System interfaces and concurrent programs – Populate and maintain rows in the translation table when files are uploaded or descriptions edited.
  • FND_LANGUAGES – The language reference used to interpret the LANGUAGE and SOURCE_LANG columns.
  • FND_USER – Referenced indirectly through the CREATED_BY and LAST_UPDATED_BY audit columns for user attribution.

Because no FK constraints are documented, referential integrity to the base file table is maintained application-side rather than by the database, which is worth noting when building custom queries or extracts against these objects.