Results for “operator_name”

50+ results




Overview
Explore in AI Chat

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

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, APPS.AHL_DOCUMENTS_V is a reporting and integration view owned by the APPS schema and delivered as part of the AHL — Complex Maintenance Repair and Overhaul product family. It exposes the header-level attributes of documents maintained in AHL, resolving the internal code values stored on the base tables into their user-facing descriptions. The view is designated VALID and is typically consumed by OAF-based AHL document pages, concurrent programs, and inbound/outbound interfaces that require a denormalized, human-readable projection of document records without joining the underlying transactional, translated, and lookup tables individually.

Because AHL documents represent contractual and operational artifacts (such as service agreements, warranties, and subscription documents exchanged between parties), the view is the natural source when reporting must show both the stored code and its descriptive meaning — for example, returning PRODUCT_TYPE_CODE alongside the derived PRODUCT_TYPE_DESC, which is precisely the attribute a search on "product_type_desc" targets.

Underlying Base Objects

The documented definition of AHL_DOCUMENTS_V is built from a small set of base and reference objects:

The ETRM metadata lists referenced objects only at the top level, so AHL_DOCUMENTS_B, AHL_DOCUMENTS_TL, and FND_LOOKUP_VALUES are reached transitively through their respective _VL views. Join predicates combine these sources, with outer joins (+) applied to the sub-type, product-type, and operator lookups so that documents lacking those attributes are still returned.

Key Columns

Common Use Cases and Queries

A representative query retrieving the product-type description alongside other resolved attributes is:

SELECT d.document_no,
       d.document_title,
       d.doc_type_desc,
       d.doc_sub_type_desc,
       d.product_type_code,
       d.product_type_desc,
       d.operator_name,
       d.source_party_number
FROM   apps.ahl_documents_v d
WHERE  d.product_type_desc IS NOT NULL
ORDER  BY d.document_no;

Typical scenarios include: reporting on documents by product type for MRO planning; integration extracts feeding external maintenance systems; and filtered lookups returning only documents whose product-type description matches a target value. Because the lookup columns are outer-joined, filters on PRODUCT_TYPE_DESC implicitly exclude documents with no product type, so WHERE clauses should be written accordingly.