Results for “ahl_documents_vl”

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

Overview

APPS.AHL_DOCUMENTS_VL is a translatable (VL) view in the Oracle E-Business Suite AHL module, which supports Complex Maintenance Repair and Overhaul (CMRO). The view presents the language-dependent and language-independent attributes of maintenance documents in a single, denormalized result set, joining the base table AHL_DOCUMENTS_B to its translation table AHL_DOCUMENTS_TL. Because it is a VL ("view with language") object, it resolves the document title and description in the session's current language, identified through USERENV('LANG'). This makes it the standard access point for reports, concurrent programs, form LOVs, and integration interfaces that require document header information in the user's own locale rather than the base-language row.

In Oracle EBS 12.1.1 and 12.2.2, the view is owned by the APPS schema and is documented as VALID. It is widely used wherever AHL documents (for example, work orders, work requests, and maintenance task documents) must be surfaced alongside their translated titles.

Underlying Base Objects

The view is defined over two documented base objects, exposed in APPS as synonyms that resolve to the AHL schema tables:

• AHL_DOCUMENTS_B — the base ("_B") table holding language-independent document attributes such as document number, type, subtype, operator, product type, flags, and descriptive flexfield attributes.
• AHL_DOCUMENTS_TL — the translation ("_TL") table holding language-dependent text, principally DOCUMENT_TITLE.

The join is performed on DOCUMENT_ID (ADB.DOCUMENT_ID = ADT.DOCUMENT_ID), with the additional filter ADT.LANGUAGE = USERENV('LANG') so that exactly one translated row per document is returned for the current session language. The view also selects ADB.ROWID as ROW_ID, providing a row identifier consistent with Oracle Forms block definitions.

Key Columns

• ROW_ID — the rowid of the base table row, used by Forms and by updatable-view logic.
• DOCUMENT_ID — primary key linking document headers to their translations and to related AHL entities.
• DOCUMENT_NO — the user-visible document number.
• DOCUMENT_TITLE — the translated title sourced from AHL_DOCUMENTS_TL.
• SUBSCRIBE_AVAIL_FLAG — indicates whether subscription availability applies to the document.
• SUBSCRIBE_TO_FLAG — the subscription indicator; this is the column relevant to searches for "subscribe_to_flag" in the AHL document context.
• DOC_TYPE_CODE / DOC_SUB_TYPE_CODE — document type and subtype classification codes.
• OPERATOR_CODE / PRODUCT_TYPE_CODE — owning operator and product type associations.
• SOURCE_PARTY_ID — the party that originated the document.
• OBJECT_VERSION_NUMBER — optimistic locking version, together with the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).
• SECURITY_GROUP_ID — multi-organization security grouping.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns.

Common Use Cases and Queries

Typical scenarios include querying maintenance documents for a given operator or product type, checking subscription flags before publishing or distributing documents, and joining document headers to work order or task data. Because the view resolves titles in the session language, it is preferred over querying the base and translation tables separately.

• List all documents subscribing to a given scope: SELECT document_id, document_no, document_title FROM ahl_documents_vl WHERE subscribe_to_flag = 'Y';
• Filter by type and product type: SELECT document_no, document_title, doc_type_code FROM ahl_documents_vl WHERE doc_type_code = :p_type AND product_type_code = :p_product;
• Check subscription availability: SELECT document_no, subscribe_avail_flag, subscribe_to_flag FROM ahl_documents_vl WHERE subscribe_avail_flag = 'Y';
• Join to work orders using DOCUMENT_ID as the correlation key, always honoring the LANGUAGE filter implicitly supplied by USERENV('LANG').

Restrict queries to indexed columns such as DOCUMENT_ID, DOCUMENT_NO, and the flag columns to avoid full scans of the translation join.