Results for “dom_documents_vl”

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

Overview

DOM_DOCUMENTS_VL is a translated (VL, "view language") view owned by the APPS schema within the DOM – Document Management and Collaboration product of Oracle E-Business Suite. It exposes the operational definition of a document as stored in the DOM schema, combining language-independent attributes held in the base table DOM_DOCUMENTS with the language-dependent descriptive attributes (name and description) held in DOM_DOCUMENTS_TL. Because the join is filtered on the session language, the view returns a single, current-language row per document for the calling user.

The view is a reporting and integration artifact rather than a transactional entity. Forms, concurrent programs, OAF pages, and third-party integrations that need a flattened, language-resolved read of document metadata query DOM_DOCUMENTS_VL instead of joining the base and translation tables manually. This is standard Oracle EBS multi-language design: the _VL view is the sanctioned read interface, and the underlying _B/_TL pair is the physical store.

Underlying Base Objects

The documented view text is:

SELECT B.DOCUMENT_ID, B.CATEGORY_ID, T.NAME, B.DOC_NUMBER, T.DESCRIPTION, B.DEF_REP_ID, B.DEF_FOLDER_ID, B.LOCK_STATUS, B.LOCKED_BY, B.LIFECYCLE_ID, B.CREATED_BY, B.CREATION_DATE, B.LAST_UPDATED_BY, B.LAST_UPDATE_DATE, B.LAST_UPDATE_LOGIN FROM DOM_DOCUMENTS B, DOM_DOCUMENTS_TL T WHERE B.DOCUMENT_ID = T.DOCUMENT_ID AND T.LANGUAGE = USERENV('LANG')

Two base objects are therefore referenced: DOM_DOCUMENTS (aliased B, the base table) and DOM_DOCUMENTS_TL (aliased T, the translation table). The join predicate is on DOCUMENT_ID, and the language filter uses USERENV('LANG'). This is an inner join, so a document lacking a translation row in the session language will not be returned. No further base objects are documented for the 12.2.2 metadata set.

Key Columns

• DOCUMENT_ID – Primary key of the document; the join key between the base and translation tables.
• CATEGORY_ID – Foreign key to the document category that classifies the document.
• NAME – Language-dependent document name, sourced from DOM_DOCUMENTS_TL.
• DESCRIPTION – Language-dependent description, also from DOM_DOCUMENTS_TL.
• DOC_NUMBER – User-visible document number.
• DEF_REP_ID – Default repository identifier associated with the document definition.
• DEF_FOLDER_ID – Default folder identifier within that repository.
• LOCK_STATUS / LOCKED_BY – Current lock state and the user holding the lock, supporting check-out/check-in concurrency.
• LIFECYCLE_ID – Identifier of the lifecycle assigned to the document; this is the column most often targeted by searches such as "lifecycle_id" because it drives routing, approval state, and status transitions for the document.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS WHO columns for auditing.

Common Use Cases and Queries

Typical uses include document inventory reports, lifecycle-based dashboards, lock monitoring, and integration extracts that must emit human-readable names in the user's language.

• List all documents and their lifecycles: SELECT document_id, doc_number, name, lifecycle_id FROM apps.dom_documents_vl ORDER BY doc_number;
• Filter by lifecycle: SELECT document_id, doc_number, name FROM apps.dom_documents_vl WHERE lifecycle_id = :p_lifecycle_id;
• Find documents currently locked: SELECT document_id, doc_number, locked_by FROM apps.dom_documents_vl WHERE lock_status = 'Y';
• Count documents per category: SELECT category_id, COUNT(*) FROM apps.dom_documents_vl GROUP BY category_id;

Because the view resolves language at runtime, reports run under different language sessions return different NAME and DESCRIPTION values for the same DOCUMENT_ID, while all other columns remain identical.