Search Results edr_files_vl




Overview
Explore in AI Chat

Overview

EDR_FILES_VL is a multi-language (MLS) view owned by the APPS schema in Oracle E-Business Suite, defined within the EDR – E-Records product. Its documented purpose is to expose the files uploaded and managed through the ERES (E-Records and E-Signatures) File Upload System. As a "_VL" view, it collapses the standard "_B" (base) and "_TL" (translation) table pair into a single logical row per file, returning the current session-language description alongside the base-language-independent attributes. In practice, EDR_FILES_VL is the primary read interface through which forms, reports, and integration routines retrieve file metadata — file name, version information, category, status, and content type — without joining the underlying tables manually. The view is documented as VALID in ETRM 12.2.2 and applies equally to 12.1.1, since the EDR schema and its MLS view naming conventions are consistent across both releases.

Underlying Base Objects

The view is defined over two documented base synonyms: EDR_FILES_B and EDR_FILES_TL. The metadata records the defining SQL as a join between EDR_FILES_TL (aliased T) and EDR_FILES_B (aliased B) on FILE_ID, filtered by the session language:

  • EDR_FILES_B — the base table that stores language-independent file attributes such as FILE_ID, FILE_NAME, CONTENT_TYPE, FILE_FORMAT, STATUS, VERSION_NUMBER, and the fifteen descriptive flexfield attributes.
  • EDR_FILES_TL — the translation table that stores the language-specific DESCRIPTION and is keyed by FILE_ID plus LANGUAGE.
  • Join condition — WHERE B.FILE_ID = T.FILE_ID AND T.LANGUAGE = USERENV('LANG'), which restricts output to the language of the current session and prevents duplicate rows across installed languages.

Because the view exposes B.ROWID as ROW_ID, it remains key-preserving and can be used in certain DML contexts where the underlying base table would otherwise be required.

Key Columns

  • ROW_ID — the row identifier derived from EDR_FILES_B.ROWID.
  • FILE_ID — the primary identifier linking base and translation records.
  • FILE_NAME / ORIGINAL_FILE_NAME — the stored file name and the name as originally uploaded.
  • VERSION_LABEL / VERSION_NUMBER — versioning metadata for the uploaded file.
  • CATEGORY_ID — the file category classification within the upload system.
  • CONTENT_TYPE / FILE_FORMAT — MIME content type and internal format indicator.
  • STATUS — lifecycle status of the file record.
  • FND_DOCUMENT_ID — the reference into the FND Documents repository, linking the E-Records file to the standard Oracle attachments framework.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the descriptive flexfield columns, available for customer-specific extensions.
  • DESCRIPTION — the translated description from EDR_FILES_TL, returned in the session language.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include reporting on uploaded ERES files, validating attachment linkage to FND Documents, and building integrations that reconcile file metadata. A representative query listing files matching a name pattern is:

SELECT file_id, file_name, version_label, status, description,
       creation_date, created_by
FROM   apps.edr_files_vl
WHERE  UPPER(file_name) LIKE '%SPEC%'
ORDER  BY creation_date DESC;

To review versioning history for a specific document, query by FILE_ID:

SELECT file_id, version_number, version_label, content_type,
       fnd_document_id
FROM   apps.edr_files_vl
WHERE  file_id = :p_file_id;

Reporting queries should account for the language filter built into the view: only descriptions in the session language are returned, so cross-language reporting must either set the session language or query EDR_FILES_TL directly. Because the view is key-preserving, it may also be referenced in update statements targeting file status where permitted by the EDR application's business rules.