Results for “data_element_type_code”

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

Overview

RHX_DP_DATA_ELEMENTS_V is a reporting and integration view within the Oracle E-Business Suite Master Scheduling/MRP (MRP) product family. It exposes the configuration metadata that defines the individual data elements belonging to demand plans stored in the RHX_DP_DEMAND_PLANS and RHX_DP_DATA_ELEMENTS base tables. In the ETRM documentation the object is annotated as "Retrofitted" and marked "Not implemented in this database," meaning the view definition is shipped as part of the historical Rapid Planning / demand planning schema but is not deployed in every environment. The view is essentially a denormalized read layer: it joins the demand plan header, the data element definition, the organization master, and the RHX_DP_DATA_ELEMENT_TYPE lookup so that consumers can resolve human-readable meanings rather than raw coded values.

Underlying Base Objects

The view is defined over four documented base objects:

• RHX_DP_DATA_ELEMENTS RDE — the primary driver table holding each data element definition, including its type, group, view mapping, and substitution behavior.
• RHX_DP_DEMAND_PLANS RDP — the demand plan header, joined on DEMAND_PLAN_ID to supply the plan name.
• MFG_LOOKUPS MLU — the lookup table, filtered to LOOKUP_TYPE = 'RHX_DP_DATA_ELEMENT_TYPE', to translate DATA_ELEMENT_TYPE_CODE into a meaning.
• MTL_PARAMETERS MP — the organization definition, used to resolve ORGANIZATION_CODE.

The join to MTL_PARAMETERS is an outer join (MP.ORGANIZATION_ID (+) = NVL(RDE.ORGANIZATION_ID, -999)), which allows data elements that are not tied to a specific organization to remain visible with a null organization code. The plan-to-element and lookup joins are inner joins, so any data element without a valid plan or lookup code will be excluded from the result set.

Key Columns

• DEMAND_PLAN_ID / DEMAND_PLAN_NAME — identifies the demand plan to which the data element belongs.
• DATA_ELEMENT_ID / DATA_ELEMENT_NAME / DATA_ELEMENT_NAME2 — the unique identifier and display names of the element.
• DATA_ELEMENT_SOURCE, DATA_ELEMENT_GROUP, DATA_ELEMENT_TYPE_CODE, DATA_ELEMENT_TYPE — classification fields, with DATA_ELEMENT_TYPE providing the decoded lookup meaning.
• DATA_VIEW_NAME, DATA_VALUE_COLUMN, WHERE_CLAUSE — the view, column, and filter that supply the element's underlying data.
• MODIFY_RELATIVE_TO, MODIFY_START — control how the element is positioned relative to the plan calendar.
• HISTORICAL_SUBS_FLAG — indicates whether historical substitution applies to the element; this is the column most frequently targeted by searches for "historical_subs_flag" and drives whether historical data is substituted during plan processing.
• DP_DB_FILENAME, DP_DB_FILENAME_FLAG, DATA_TYPE, DISPLAY_FORMAT — storage and presentation attributes.
• LOCK_FLAG, SEED_FLAG, ROW_TYPE — governance fields distinguishing seeded versus user-defined elements and their editability.
• PLAN_OPTIONAL_PARAMS, LOAD_OPTIONAL_PARAMS — parameter payloads used when the element is loaded or planned.

Common Use Cases and Queries

The view is commonly used to audit data element definitions, to report which elements participate in historical substitution, and to drive integrations that copy element definitions between environments. A typical query listing elements and their historical substitution behavior is:

• SELECT DEMAND_PLAN_NAME, DATA_ELEMENT_NAME, DATA_ELEMENT_TYPE, HISTORICAL_SUBS_FLAG FROM RHX_DP_DATA_ELEMENTS_V WHERE HISTORICAL_SUBS_FLAG = 'Y';
• SELECT DEMAND_PLAN_NAME, DATA_ELEMENT_NAME, ORGANIZATION_CODE, SEED_FLAG FROM RHX_DP_DATA_ELEMENTS_V ORDER BY DEMAND_PLAN_NAME, DATA_ELEMENT_NAME;
• SELECT DATA_ELEMENT_TYPE, COUNT(*) FROM RHX_DP_DATA_ELEMENTS_V GROUP BY DATA_ELEMENT_TYPE;

Because the object is documented as not implemented in all databases, availability should be verified against the target instance before use in a production report or interface.