Results for “dom_document_catalogs_vl”

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

Overview

DOM_DOCUMENT_CATALOGS_VL is a translation-enabled (VL, or "view language") database view within the Oracle EBS Document Management and Collaboration (DOM) module. Its role is to present document catalog definitions in the language of the active user session, providing a single, convenient source for catalog identification, naming, and descriptive metadata without requiring the caller to manually join the base entity and its translation table. Document catalogs group and classify documents managed within DOM, so this view serves as a foundational data source for reports, lookups, and integration extracts that must display catalog names in a locale-appropriate manner.

Because it is a VL view, it draws localized text columns from a translation table while pulling non-translated administrative attributes from the base (non-translated) table. This design follows Oracle's standard multi-language support (MLS) pattern used throughout EBS 12.1.1 and 12.2.2, ensuring that report outputs and API calls return values appropriate to the user's language setting.

Underlying Base Objects

The view is defined over two documented base objects: DOM_DOCUMENT_CATALOGS (aliased B) and DOM_DOCUMENT_CATALOGS_TL (aliased T). The two are joined on CATALOG_ID. The translation table supplies the locale-dependent columns (NAME, DESCRIPTION, and INTERNAL_NAME as exposed in the view text), while the base table supplies the transactional/administrative columns such as CATALOG_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

The critical filter is the language predicate: T.LANGUAGE = USERENV('LANG'). This restricts the result set to the single row whose language matches the current session's language identifier, guaranteeing that each catalog is returned once, in the user's own language. The ETRM metadata notes that the view is "not implemented in this database," meaning it may not exist in every environment or may be delivered only where the DOM module is fully installed. Documented owner and referenced base object metadata are limited, so the join structure above should be treated as the authoritative definition where the view exists.

Key Columns

• CATALOG_ID — Surrogate primary key of the document catalog; the join column between base and translation tables and the identifier used in foreign-key relationships.
• INTERNAL_NAME — Internal, system-facing name of the catalog, typically used for programmatic reference and stable identification across languages.
• NAME — Display (translated) name of the catalog shown to end users in the session language.
• DESCRIPTION — Translated descriptive text explaining the catalog's purpose.
• CREATED_BY / CREATION_DATE — Audit columns capturing the creating user and timestamp.
• LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — Audit columns capturing the last modifying user, timestamp, and login context.

Common Use Cases and Queries

Typical uses include populating catalog list-of-values, feeding document classification reports, and supporting integration extracts that require localized catalog labels. A basic query returning active catalogs follows:

SELECT catalog_id, internal_name, name, description
FROM   dom_document_catalogs_vl
ORDER  BY name;

To retrieve a single catalog by its internal identifier:

SELECT catalog_id, name, description
FROM   dom_document_catalogs_vl
WHERE  internal_name = :p_internal_name;

For audit-oriented reporting on recent catalog maintenance:

SELECT name, last_updated_by, last_update_date
FROM   dom_document_catalogs_vl
WHERE  last_update_date >= :p_from_date
ORDER  BY last_update_date DESC;

Because results are automatically filtered to USERENV('LANG'), no explicit language predicate is required in consumer queries. Note that the search prompt referencing "how to redeem Visio Standard 2024" is unrelated to this DOM database object; it reflects an external product-licensing query and has no bearing on the view or its usage within Oracle EBS.