Results for “rhx_dp_data_pub_v”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
RHX_DP_DATA_PUB_V is a public reporting view within the Oracle EBS Master Scheduling/MRP (MRP) product family. The RHX_ prefix and the "Retrofitted" designation indicate that this object belongs to the Oracle Advanced Planning / Demand Planning (DP) schema, which was retrofitted into the E-Business Suite data model. The view consolidates demand plan data records — the actual data values stored against demand plan data elements — together with their associated level hierarchies and demand plan names, producing a denormalized, query-friendly result set suitable for reporting and integration.
The view is documented in ETRM 12.2.2 with no owner recorded and no documented base objects, and the implementation note states "Not implemented in this database." This means the view exists in the delivered schema definitions but may not be present or populated in every environment. Because the view exposes the LEVEL_ID columns (implemented as LOWEST_LEVEL_ID_G, LOWEST_LEVEL_ID_P, and LOWEST_LEVEL_ID_T), it is directly relevant to users searching for "level_id" — it is one of the primary surfaces through which demand planning level identifiers are exposed to downstream queries.
Underlying Base Objects
The view is defined as a UNION ALL over the following tables:
- RHX_DP_DATA (DA) — the driving fact table holding data values, the demand plan reference, data element reference, and the three lowest-level identifiers and values.
- RHX_DP_DEMAND_PLANS (DP) — provides
DEMAND_PLAN_NAME, joined onDEMAND_PLAN_ID. - RHX_DP_DATA_ELEMENTS (DE) — provides
DATA_ELEMENT_NAMEand theDATA_ELEMENT_SOURCEfilter, joined onDATA_ELEMENT_ID. - RHX_DP_LEVELS (L1, L2, L3) — three aliased instances supplying
LEVEL_NAMEfor the G, P, and T level identifiers respectively. - ORG_ORGANIZATION_DEFINITIONS (OD) — used only in the second branch of the UNION ALL to append the organization code to the data element name.
The first branch excludes data elements whose source is FORECAST or FORECAST_SET. The second branch concatenates DATA_ELEMENT_NAME with a delimiter obtained from RHX_DP.GET_PARAMETER('RHX_DP_P_DELIMITER') and the organization code, effectively producing organization-qualified rows.
Key Columns
- DP_DATA_ID, LINE_ID — primary identifiers for the demand plan data record.
- DEMAND_PLAN_ID, DEMAND_PLAN_NAME — identifies the demand plan to which the record belongs.
- DATA_ELEMENT_ID, DATA_ELEMENT_NAME — identifies the measure or element being stored; the name may be organization-qualified in the UNION's second branch.
- DATA_VALUE — the actual stored value of the data element.
- LOWEST_LEVEL_ID_G, LOWEST_LEVEL_ID_P, LOWEST_LEVEL_ID_T — the lowest level identifiers for the three level dimensions (commonly Geographic, Product, and Time).
- L1.LEVEL_NAME, L2.LEVEL_NAME, L3.LEVEL_NAME — the descriptive names resolved from RHX_DP_LEVELS for each level identifier.
- LOWEST_LEVEL_VALUE_G/P/T — the lowest level values corresponding to each dimension.
- ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield columns.
Common Use Cases and Queries
Typical reporting scenarios include extracting demand plan data by level, resolving level identifiers to names, and joining plan data to organizational context.
- Retrieve data values for a demand plan along with resolved level names:
SELECT DEMAND_PLAN_NAME, DATA_ELEMENT_NAME, DATA_VALUE,
LOWEST_LEVEL_ID_G, LOWEST_LEVEL_ID_P, LOWEST_LEVEL_ID_T
FROM RHX_DP_DATA_PUB_V
WHERE DEMAND_PLAN_ID = :plan_id;
- Find records for a specific level identifier:
SELECT DP_DATA_ID, DATA_ELEMENT_NAME, DATA_VALUE FROM RHX_DP_DATA_PUB_V WHERE LOWEST_LEVEL_ID_G = :level_id OR LOWEST_LEVEL_ID_P = :level_id OR LOWEST_LEVEL_ID_T = :level_id;
- Aggregate a measure by level name:
SELECT L1.LEVEL_NAME, SUM(DATA_VALUE) FROM RHX_DP_DATA_PUB_V GROUP BY L1.LEVEL_NAME;
Because the view is documented as not implemented in every environment, verify its presence in ALL_VIEWS and confirm access privileges before relying on it in custom reports or integrations.
-
View: RHX_DP_DATA_PUB_V 12.1.1
- Retrofitted
Not implemented in this database·Explore MRP module →
-
View: RHX_DP_DATA_PUB_V 12.2.2
- Retrofitted
Not implemented in this database·Explore MRP module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2