Search Results frm_documents_vl




Overview
Explore in AI Chat

Overview

FRM_DOCUMENTS_VL is a standard Oracle E-Business Suite translation (VL) view owned by the APPS schema and defined within the FRM — Report Manager product module. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. As a translation view, it presents a language-specific, joined projection of the underlying document base and translation entities, resolving the user-facing descriptive attribute (USER_NAME) according to the session language while exposing the operational columns required for reporting and integration. In the Report Manager architecture, a "document" represents an entry within a report directory, and this view is the canonical read interface for querying those entries in a multi-language environment. The view does not store data itself; it derives its results dynamically from its base objects at query time.

Underlying Base Objects

The documented definition of FRM_DOCUMENTS_VL joins two synonyms: FRM_DOCUMENTS_B, the base (language-independent) table, and FRM_DOCUMENTS_TL, the translation table. The join condition is B.DOCUMENT_ID = T.DOCUMENT_ID, constrained by T.LANGUAGE = USERENV('LANG'), the standard mechanism by which Oracle translation views return rows only for the language of the current session. The row identifier ROW_ID is sourced from the B (base) table's ROWID. The view joins the two objects on the DOCUMENT_ID key, which uniquely identifies each document and links its functional attributes to its language-specific name.

Key Columns

  • ROW_ID — The base table ROWID, exposed for row-level addressing.
  • DOCUMENT_ID — Primary identifier of the document; the join key between base and translation tables.
  • DIRECTORY_ID — Reference to the report directory to which the document belongs.
  • SEQUENCE_NUMBER — Ordering position of the document within its directory.
  • EXPANDED_FLAG — Indicates whether the document node is displayed in expanded state in the Report Manager hierarchy.
  • DS_APP_SHORT_NAME — Application short name of the data source associated with the document.
  • DATA_SOURCE_CODE — Code identifying the underlying data source definition.
  • OBJECT_VERSION_NUMBER — Optimistic locking/versioning column used by the framework for concurrency control.
  • USER_NAME — The user-facing (translated) document name, sourced from FRM_DOCUMENTS_TL.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns describing record creation and last modification.
  • END_DATE — End-dating attribute used for effective-dated lifecycle management of the document.
  • ARCHIVED_FLAG — Indicates whether the document has been archived.

Common Use Cases and Queries

Typical uses include extracting the list of documents (with translated names) under a given directory, reporting on archived versus active entries, and integrating Report Manager metadata into external reporting tools. Because the view enforces the session-language predicate, no explicit language filter is required; results are automatically localized.

Listing all documents in a directory:

  • SELECT document_id, directory_id, sequence_number, user_name, archived_flag FROM apps.frm_documents_vl WHERE directory_id = :p_directory_id ORDER BY sequence_number;

Identifying active, non-archived documents:

  • SELECT document_id, user_name, data_source_code, ds_app_short_name FROM apps.frm_documents_vl WHERE NVL(archived_flag,'N') = 'N';

Auditing recent changes to document definitions:

  • SELECT document_id, user_name, last_updated_by, last_update_date FROM apps.frm_documents_vl WHERE last_update_date >= :p_since_date ORDER BY last_update_date DESC;

Because FRM_DOCUMENTS_VL is a view over translation-enabled entities, callers should reference it rather than the TL table directly whenever user-facing names are required, ensuring correct language resolution and consistent join semantics.