Results for “hz_source”

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

Overview

APPS.AHL_DOCUMENTS_V is a reporting and integration view in the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 environments that exposes document records maintained by the Oracle Product Information Management (PIM) / Product Hub module — specifically the AHL (Advanced Product Catalog) schema. The view presents a denormalized, human-readable projection of the AHL_DOCUMENTS_VL entity, joining the base document rows to Oracle FND lookup values and Oracle Trading Community Architecture (HZ) party records. Rather than requiring consumers to resolve coded values independently, the view supplies translated description columns alongside the raw codes. It is read-only in practice and is intended for inquiries, reports, and downstream integrations that need document metadata enriched with lookup meanings and party names.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is owned by APPS and is defined over the following referenced base objects:

• AHL_DOCUMENTS_VL (VIEW) — the primary source of document rows, supplying the document identifiers, descriptive attributes, descriptive flexfield (DFF) columns, and code columns.
• FND_LOOKUP_VALUES_VL (VIEW) — referenced three times through inline aliases (FND_DOC_TYPE, FND_DOC_SUB_TYPE, FND_PRODUCT_TYPE) to translate document type, document sub-type, and product type codes into their display meanings.
• HZ_PARTIES (SYNONYM) — referenced twice (HZ_OPERATOR, HZ_SOURCE) to resolve operator and source party identifiers into party names and party numbers.

All lookup joins on the code columns are outer joins (indicated by the (+) operator), so a document row is retained even when no matching lookup value exists. The join to the source party (HZ_SOURCE) is an inner join, which means the source party must resolve for the row to be returned.

Key Columns

The view exposes the following principal columns:

• ROW_ID, DOCUMENT_ID, OBJECT_VERSION_NUMBER — row identity, primary document key, and optimistic locking version.
• DOCUMENT_NO, DOCUMENT_TITLE — the human-readable document number and title.
• DOC_TYPE_CODE / DOC_TYPE_DESC — the raw AHL_DOC_TYPE code and its translated meaning.
• DOC_SUB_TYPE_CODE / DOC_SUB_TYPE_DESC — the code and meaning derived from the AHL_DOC_SUB_TYPE lookup type, the specific columns relevant to the user's search term ahl_doc_sub_type.
• PRODUCT_TYPE_CODE / PRODUCT_TYPE_DESC — product classification code and its ITEM_TYPE lookup meaning.
• SOURCE_PARTY_ID, SOURCE_PARTY_NUMBER, OPERATOR_CODE, OPERATOR_NAME — source and operator party identifiers and descriptions.
• SUBSCRIBE_AVAIL_FLAG, SUBSCRIBE_TO_FLAG — subscription availability and subscription target indicators.
• SECURITY_GROUP_ID — the Multi-Org / security group discriminator.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield context and segment values.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically queried to produce document registers and to validate that sub-type codes carry the expected lookup meaning. A representative query filtering on the sub-type is:

• SELECT document_no, document_title, doc_type_desc, doc_sub_type_desc, operator_name FROM apps.ahl_documents_v WHERE doc_sub_type_code = 'SOME_SUBTYPE';
• Joining back to AHL_DOCUMENTS_VL or AHL_DOCUMENTS_B when the caller needs the base primary key or additional unexposed attributes.
• Reporting inventory of documents by operator, source party, or product type using OPERATOR_NAME, SOURCE_PARTY_NUMBER, and PRODUCT_TYPE_DESC.

Because the view performs multiple outer joins against FND_LOOKUP_VALUES_VL and inner joins against HZ_PARTIES, queries returning large document sets should filter aggressively on DOCUMENT_NO, DOC_TYPE_CODE, or DOC_SUB_TYPE_CODE to avoid full scans of the underlying lookup and party tables.