Results for “hierarchy_level”

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

Overview

EDW_PO_VENDOR_HIERARCHIES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, catalogued under the Purchasing (PO) product family. It is a lightweight presentation layer defined over a single underlying object, EDW_PO_VENDOR_HIERARCHIES, and exposes a narrow, purpose-built projection of that source rather than the full column set.

The view is intended primarily for Enterprise Data Warehouse (EDW) extraction, supplier analytics, and integration workloads that must flatten or traverse the parent-child relationships between suppliers. Because it preserves vendor identifiers alongside their parent vendor identifiers and a hierarchy level indicator, it allows downstream consumers to reconstruct supplier organization trees without joining back to the master supplier tables. In the 12.1.1 and 12.2.2 release streams the object is documented as VALID, indicating that the editioning and dependency metadata are consistent and that the view is safe to reference in custom reporting objects such as materialized views, BI Publisher data models, and OBIEE repository mappings.

Underlying Base Objects

The documented view text is a straightforward projection:

SELECT "HIERARCHY_LEVEL",
       "LAST_UPDATE_DATE",
       "VENDOR_ID",
       "PARENT_VENDOR_ID"
FROM   EDW_PO_VENDOR_HIERARCHIES

The view is therefore defined exclusively over the EDW_PO_VENDOR_HIERARCHIES object. The ETRM metadata for this release records no additional referenced base objects, and the view text confirms there are no joins, unions, or function-based expressions. This is significant for two reasons. First, the view imposes no performance overhead beyond the base object's own access path, since no predicate transformation or aggregation occurs. Second, no denormalization is performed at this layer: the hierarchy is delivered as raw parent-child pairs plus a level marker, leaving recursive traversal logic to the consumer.

In practice the base EDW_PO_VENDOR_HIERARCHIES object derives its rows from the supplier tables in the PO and AP schemas, where supplier parent relationships are maintained through the supplier parent-child relationship model. The view deliberately omits the broad attribute set of the supplier master, retaining only the structural columns needed to describe the hierarchy.

Key Columns

• VENDOR_ID — The unique identifier of the supplier at the current node of the hierarchy. This is the primary join key back to supplier master data such as PO_VENDORS.
• PARENT_VENDOR_ID — The vendor identifier of the immediate parent supplier. A null or self-referencing value typically indicates a root node, depending on how the base object is populated.
• HIERARCHY_LEVEL — The depth of the node within the supplier hierarchy. Level 1 conventionally denotes the topmost parent, with successive integers identifying subordinate levels. This column removes the need to compute depth through recursive queries in most reporting scenarios.
• LAST_UPDATE_DATE — The timestamp of the most recent modification to the hierarchy row, supporting incremental and change-data-capture extraction patterns common in EDW loads.

Common Use Cases and Queries

Typical applications include supplier spend roll-up by parent company, global procurement reporting, and reconciliation of supplier hierarchies against master data extracts. The LAST_UPDATE_DATE column is frequently used to drive incremental extraction windows.

SELECT vendor_id,
       parent_vendor_id,
       hierarchy_level
FROM   apps.edw_po_vendor_hierarchies_v
WHERE  hierarchy_level = 1
ORDER  BY vendor_id;

To retrieve the direct children of a given supplier:

SELECT vendor_id,
       hierarchy_level
FROM   apps.edw_po_vendor_hierarchies_v
WHERE  parent_vendor_id = :p_vendor_id;

For incremental loads into a warehouse staging table:

SELECT vendor_id,
       parent_vendor_id,
       hierarchy_level,
       last_update_date
FROM   apps.edw_po_vendor_hierarchies_v
WHERE  last_update_date >= :p_last_run_date;

Because the view performs no filtering, callers should always restrict by hierarchy_level or last_update_date to avoid full scans of the base object.