Results for “data_element_id”

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

Overview

The view RHX_DP_DATA_ELMNT_PUB_V belongs to the MRP (Master Scheduling/MRP) product family within Oracle E-Business Suite, specifically the Demand Planning (DP) subsystem that forms part of the Advanced Supply Chain Planning and Enterprise Resource Planning integration layer. Within ETRM documentation for releases 12.1.1 and 12.2.2, the object is labelled "Retrofitted," indicating that its definition has been carried forward or re-implemented to preserve compatibility with prior release functionality. The view exposes demand plan data elements together with their associated geographic (GEO) and product (PRD) dimension levels, presenting a denormalized, reporting-friendly projection of the underlying demand planning metadata.

Its purpose is to publish data element definitions to downstream consumers such as planners, integration programs, and custom reports that need to resolve a data element to its demand plan, level hierarchy, and source classification without navigating the full normalized schema. Notably, the ETRM record states that the object is "Not implemented in this database," meaning the view definition exists in the metadata repository but is not physically deployed in every environment.

Underlying Base Objects

The view is defined over five base tables in the RHX schema family:

• RHX_DP_DATA_ELEMENTS — the driving table, holding the core data element definitions.
• RHX_DP_DATA_LEVELS — joined twice (aliases DL1 and DL2) to resolve the data element's association with dimension levels.
• RHX_DP_LEVELS — joined twice (L1 and L2) to obtain the human-readable level names for the lowest level identifiers.
• RHX_DP_DEMAND_PLANS — provides the demand plan name for each element.

The join predicates restrict DL1.DIMENSION_CODE = 'GEO' and DL2.DIMENSION_CODE = 'PRD', so each row pairs a data element with one geographic level and one product level. The view is a UNION ALL of two branches: the first returns elements whose DATA_ELEMENT_SOURCE is not FORECAST or FORECAST_SET with the plain DATA_ELEMENT_NAME; the second concatenates the element name with an organization code using the delimiter supplied by RHX_DP.GET_PARAMETER('RHX_DP_P_DELIMITER'), joined to an organization source OD. Both branches filter on DATA_ELEMENT_TYPE_CODE = 1 and use SELECT DISTINCT to eliminate duplicates.

Key Columns

• DATA_ELEMENT_ID — primary identifier of the data element.
• DEMAND_PLAN_ID, DEMAND_PLAN_NAME — the demand plan to which the element belongs.
• DATA_ELEMENT_SOURCE, DATA_ELEMENT_NAME, DATA_ELEMENT_GROUP, DATA_ELEMENT_TYPE_CODE — classification and naming attributes.
• DATA_LEVEL_ID, LOWEST_LEVEL_ID, LEVEL_NAME (twice) — the geographic and product dimension levels.
• MODIFY_RELATIVE_TO, MODIFY_START — relative modification window for planning.
• START_DATE, END_DATE, LOAD_FLAG, LOCK_FLAG — lifecycle and state control.
• DATA_TYPE, DISPLAY_FORMAT, HISTORICAL_SUBS_FLAG, ROW_TYPE — presentation and substitution behaviour.
• ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield segment columns.

Common Use Cases and Queries

Typical uses include validating demand plan setup, driving custom planning extracts, and populating reporting tables. A representative query:

• SELECT DEMAND_PLAN_NAME, DATA_ELEMENT_NAME, LEVEL_NAME, DATA_ELEMENT_SOURCE FROM RHX_DP_DATA_ELMNT_PUB_V WHERE DEMAND_PLAN_ID = :p_plan_id;
• Filter by source: ... WHERE DATA_ELEMENT_SOURCE NOT IN ('FORECAST','FORECAST_SET');
• Join to organization masters via the organization-code-suffixed name branch for site-level reporting.

Because the view is documented as not implemented in some databases, deployments should verify its existence before referencing it in concurrent programs or BI Publisher data templates.