Results for “dp_data_id”

4 results




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

Overview

RHX_DP_DATA_V is a reporting view in the Oracle EBS Master Scheduling/MRP (MRP) product family, associated with the Demand Planning data model. It is documented in ETRM with the descriptor "Retrofitted," indicating that the object was carried forward from an earlier release lineage into the 12.1.1 / 12.2.2 code streams rather than being introduced as a new design. The view exposes the contents of the Demand Planning data table (RHX_DP_DATA) joined to demand plan definitions, data element definitions, and the three planning level dimensions (geography, product/item, and time), presenting denormalized, human-readable names alongside the numeric level and element identifiers.

The object is central to any report or interface that needs to read demand plan values without independently resolving the geography, item, and time level identifiers. Its grain is one row per demand planning data entry, uniquely identified by DP_DATA_ID and associated to a plan through DEMAND_PLAN_ID. Because the view is documented as not implemented in the reference database, it should be treated as a distributed object that exists only in environments where the Demand Planning schema has been installed and populated.

Underlying Base Objects

The view text is defined over the following tables:

All joins are inner equijoins on the respective identifiers: DATA.DEMAND_PLAN_ID = DEMAND_PLANS.DEMAND_PLAN_ID, DATA.DATA_ELEMENT_ID = DATA_ELEMENTS.DATA_ELEMENT_ID, DATA.LOWEST_LEVEL_ID_G = GEOGRAPHY.LEVEL_ID, DATA.LOWEST_LEVEL_ID_P = ITEM.LEVEL_ID, and DATA.LOWEST_LEVEL_ID_T = TIME.LEVEL_ID. Consequently, rows whose level or element identifiers lack a corresponding definition row are excluded from the result set.

Key Columns

  • DP_DATA_ID — primary identifier of the demand planning data row; the column most often used in point lookups.
  • LINE_ID — line-level identifier associated with the data entry.
  • DEMAND_PLAN_ID / DEMAND_PLAN_NAME — the owning demand plan and its descriptive name.
  • DATA_ELEMENT_ID / DATA_ELEMENT_NAME — the measure or element being stored (for example, a demand quantity or forecast figure).
  • DATA_VALUE — the numeric or character value recorded for the element at the specified level intersection.
  • LOWEST_LEVEL_ID_G / LEVEL_NAME / LOWEST_LEVEL_VALUE_G — geography level identifier, level name, and level value; the corresponding P (product/item) and T (time) triples follow the same pattern.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield segment columns.

Common Use Cases and Queries

Typical usage includes demand plan extracts for downstream analytics, verification of level assignments, and reconciliation between plan definitions and stored values. To retrieve all data for a single plan:

  • SELECT dp_data_id, line_id, data_element_name, data_value, level_name_g, level_value_g, level_name_p, level_value_p, level_name_t, level_value_t FROM rhx_dp_data_v WHERE demand_plan_id = :p_plan_id ORDER BY dp_data_id;

To resolve a specific data row by its documented primary identifier:

  • SELECT * FROM rhx_dp_data_v WHERE dp_data_id = :p_dp_data_id;

To aggregate values by element and time level value for trend reporting:

  • SELECT data_element_name, level_value_t, SUM(data_value) FROM rhx_dp_data_v WHERE demand_plan_id = :p_plan_id GROUP BY data_element_name, level_value_t ORDER BY level_value_t;

Because the view performs five inner joins, queries filtering on DEMAND_PLAN_ID or DATA_ELEMENT_ID benefit from indexes on the underlying base tables. The "Retrofitted" designation and the note that the object is not implemented in the reference database warrant confirming availability and column semantics against the specific 12.1.1 or 12.2.2 environment before relying on the view in production reporting.