Results for “original_file_name”

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

Overview

EDR_FILES_LATEST_VERSION_V is a reporting view owned by the APPS schema within the EDR (E-Records) product family of Oracle E-Business Suite. As its name implies, the view is designed to surface the latest version of each file stored in the File Upload System. Rather than presenting every historical revision of a document, this view aggregates the EDR file repository so that only the most recent version per file identity is exposed, which is essential for downstream reporting, integration, and user-facing dashboards that must always reflect current content.

Because the view is owned by APPS and marked VALID in the ETRM 12.2.2 metadata, it is a supported, queryable object available to any session with the appropriate grants. Its structure is intentionally lightweight, returning only four logical columns, which makes it well suited for joining against other EBS views and tables without incurring unnecessary performance overhead.

Underlying Base Objects

The view is defined over a single documented base object: EDR_FILES_VL, itself a view in the APPS schema. EDR_FILES_VL is the multi-language (VL) view that presents translatable and non-translatable attributes of the EDR file records. The view text shows that EDR_FILES_LATEST_VERSION_V applies an aggregation against this base object:

• The file name is normalized with UPPER(ORIGINAL_FILE_NAME) so that case variations do not produce duplicate identities.
• Rows are grouped by the uppercased file name together with ATTRIBUTE_CATEGORY.
• The aggregation returns MAX(VERSION_NUMBER) to identify the latest revision, and COUNT(FILE_ID) to indicate how many file records exist within each group.

Because the definition groups by file name and attribute category, the "latest version" is scoped to that combination rather than to an absolute global maximum across the entire repository.

Key Columns

The view exposes the following columns, each derived directly from the aggregation over EDR_FILES_VL:

• ORIGINAL_FILE_NAME — the uppercased name of the uploaded file, used as the primary grouping key. Normalization ensures that files differing only by letter case are collapsed into a single logical entity.
• ATTRIBUTE_CATEGORY — the descriptive flexfield category associated with the EDR record, providing an additional classification dimension for the group.
• VERSION_NUMBER — the maximum version number within the group, representing the latest revision of the file.
• COUNT — the number of file records (by FILE_ID) contributing to each group, useful as an indicator of revision history volume.

Common Use Cases and Queries

Typical scenarios include auditing the current state of the File Upload System, validating that expected documents are present and at the expected revision, and feeding lightweight extracts into external reporting tools. A basic query lists all latest versions:

• SELECT original_file_name, attribute_category, version_number, COUNT FROM apps.edr_files_latest_version_v ORDER BY original_file_name;
• To find a specific document: SELECT * FROM apps.edr_files_latest_version_v WHERE original_file_name = UPPER('&file_name');
• To identify heavily revised files: SELECT original_file_name, COUNT FROM apps.edr_files_latest_version_v WHERE COUNT > 5 ORDER BY COUNT DESC;
• To join against file detail for additional attributes, join back to EDR_FILES_VL on the uppercased file name and attribute category, matching VERSION_NUMBER to the aggregated maximum.

All queries should reference the view through the APPS schema or a synonym, consistent with standard EBS access conventions.