Results for “doc_sub_type_desc”

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:

• AHL_DOCUMENTS_VL (VIEW) — the translated, multi-language superview of AHL_DOCUMENTS_B and AHL_DOCUMENTS_TL, supplying the base document columns and translated title. The view aliases this as ADB.
• FND_LOOKUP_VALUES_VL (VIEW) — referenced three times, aliased as FND_DOC_TYPE (lookup type AHL_DOC_TYPE), FND_DOC_SUB_TYPE (lookup type AHL_DOC_SUB_TYPE), and FND_PRODUCT_TYPE (lookup type ITEM_TYPE), providing lookup meanings for the corresponding code columns.
• HZ_PARTIES (SYNONYM) — referenced twice, aliased as HZ_OPERATOR and HZ_SOURCE, resolving party IDs to party number and party name.

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

• ROW_ID / DOCUMENT_ID — the row identifier from the base record and the primary document identifier.
• DOCUMENT_NO — the business-facing document number.
• SOURCE_PARTY_ID / SOURCE_PARTY_NUMBER — the issuing party; the number is resolved from HZ_PARTIES.
• DOC_TYPE_CODE / DOC_TYPE_DESC — document type code and its AHL_DOC_TYPE lookup meaning.
• DOC_SUB_TYPE_CODE / DOC_SUB_TYPE_DESC — optional sub-type code and its AHL_DOC_SUB_TYPE meaning.
• PRODUCT_TYPE_CODE / PRODUCT_TYPE_DESC — the product-type code and the ITEM_TYPE lookup meaning, the resolved descriptive column the user asked about.
• OPERATOR_CODE / OPERATOR_NAME — the operator party ID and resolved party name.
• SUBSCRIBE_AVAIL_FLAG / SUBSCRIBE_TO_FLAG — subscription availability indicators.
• DOCUMENT_TITLE — the (translated) document title.
• ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 — extensible descriptive flexfield columns.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, SECURITY_GROUP_ID.

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.