Results for “data_column_name”
2 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
RHX_DP_DATA_LEVELS_V is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, delivered within the MRP — Master Scheduling/MRP product family. The view exposes the mapping between Demand Planner data elements and the hierarchical levels at which each data element is stored. In the ETRM metadata it is described as "Retrofitted," indicating that the object was reconstructed or re-registered as part of an upgrade or retrofit effort rather than delivered as a native standalone entity.
The view serves as an integration and reporting layer for Demand Planning configurations. It joins the data levels definition table (RHX_DP_DATA_LEVELS) to the data elements catalog (RHX_DP_DATA_ELEMENTS) and the levels hierarchy (RHX_DP_LEVELS), while decoding the dimension via FND_COMMON_LOOKUPS. Because the underlying structures carry the standard EBS WHO columns and concurrent program identifiers, the view is suitable for audit, diagnostics, and custom reporting on how Demand Planner dimensions, data elements, and levels are configured for a given demand plan.
Note that the documentation records "Not implemented in this database," meaning the view may be absent or disabled in certain instances. This is expected where the Demand Planning (RHX) schema is not licensed or installed.
Underlying Base Objects
The view is defined over four documented base objects:
- RHX_DP_DATA_LEVELS (RDL) — the driving table holding the data-level assignments, including DATA_LEVEL_ID, DATA_ELEMENT_ID, DIMENSION_CODE, LOWEST_LEVEL_ID, DATA_COLUMN_NAME, DATA_ID_COLUMN_NAME, seed flag, and audit columns.
- RHX_DP_DATA_ELEMENTS (RDE) — the data element catalog, providing DATA_ELEMENT_ID, DATA_ELEMENT_NAME, and DEMAND_PLAN_ID.
- RHX_DP_LEVELS (RL) — the level hierarchy, joined via an outer join (RL.LEVEL_ID (+) = RDL.LOWEST_LEVEL_ID) to supply LEVEL_NAME while tolerating rows with no matching level.
- FND_COMMON_LOOKUPS (FCU) — the standard lookup table, filtered on LOOKUP_TYPE = 'DEMAND_PLANNER_DIMENSIONS' and joined on LOOKUP_CODE = RDL.DIMENSION_CODE to resolve dimension descriptions.
The join conditions also enforce plan consistency through NVL(RL.DEMAND_PLAN_ID, RDE.DEMAND_PLAN_ID) = RDE.DEMAND_PLAN_ID, ensuring that level records belong to the same demand plan as their data element.
Key Columns
- DATA_LEVEL_ID — unique identifier for the data-level assignment.
- DATA_ELEMENT_ID / DATA_ELEMENT_NAME — the data element and its descriptive name from RHX_DP_DATA_ELEMENTS; the latter is central to searches on "data_element_name."
- DEMAND_PLAN_ID — identifies the demand plan owning the configuration.
- DIMENSION_CODE / DIMENSION_NAME — the dimension code and its lookup meaning, resolved from FND_COMMON_LOOKUPS.
- LOWEST_LEVEL_ID / LOWEST_LEVEL_NAME — the lowest hierarchy level at which the element is maintained.
- DATA_COLUMN_NAME / DATA_ID_COLUMN_NAME — physical column mappings used when the element is stored.
- SEED_FLAG — distinguishes Oracle-seeded rows from user-defined entries.
- Audit and WHO columns — LAST_UPDATE_DATE, CREATED_BY, and the concurrent request/program columns (REQUEST_ID, PROGRAM_ID) support traceability.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield storage for extensibility.
Common Use Cases and Queries
Typical uses include auditing which levels reference a given data element, validating dimension-to-element mappings, and generating configuration reports per demand plan.
SELECT DATA_ELEMENT_NAME,
DIMENSION_NAME,
LOWEST_LEVEL_NAME,
DEMAND_PLAN_ID,
SEED_FLAG
FROM RHX_DP_DATA_LEVELS_V
WHERE DATA_ELEMENT_NAME = :data_element_name;
SELECT DATA_ELEMENT_NAME, DIMENSION_CODE, DATA_COLUMN_NAME FROM RHX_DP_DATA_LEVELS_V WHERE DEMAND_PLAN_ID = :plan_id ORDER BY DATA_ELEMENT_NAME;
SELECT DATA_ELEMENT_NAME, LOWEST_LEVEL_NAME FROM RHX_DP_DATA_LEVELS_V WHERE LOWEST_LEVEL_ID IS NOT NULL AND SEED_FLAG = 'Y';
Because the view is documented as not implemented in every database, availability should be confirmed before use in custom reports or integrations.
-
View: RHX_DP_DATA_LEVELS_V 12.2.2
- Retrofitted
Not implemented in this database·Explore MRP module →
-
View: RHX_DP_DATA_LEVELS_V 12.1.1
- Retrofitted
Not implemented in this database·Explore MRP module →