Do you have any question about this error?
Message type: E = Error
Message class: ESH_OM_OBJ_MODEL_RP2 - Object Model Repository (2)
Message number: 855
Message text: The scale is of dimension &3 (uom &2) but attribute &1 has no dimension
A ranking factor attribute can have a dimension and a scale can have a
unit of measure (uom) which itself has a dimension.
Here the attribute &v1& is assigned to the scale but the following
condition is not fulfilled:
As the scale has the unit of measure &v2& which is of dimension &v3& the
attribute must be of the same dimension &v3&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
ESH_OM_OBJ_MODEL_RP2855
- The scale is of dimension &3 (uom &2) but attribute &1 has no dimension ?The SAP error message ESH_OM_OBJ_MODEL_RP2855 indicates a problem related to the dimensionality of attributes in the context of an object model, particularly when dealing with scales and units of measure (UOM). Here’s a breakdown of the components of the error message and potential solutions:
Cause of the Error
- Dimension Mismatch: The error occurs when there is a mismatch between the dimensions of a scale and the attributes defined in the object model. Specifically, the scale has a defined dimension (e.g., length, weight) and a unit of measure (UOM), but the attribute in question does not have any dimension associated with it.
- Configuration Issues: This can happen due to incorrect configuration in the object model or when defining attributes in the SAP system. If an attribute is expected to have a dimension but is not configured properly, this error will be triggered.
- Data Integrity Issues: There may be issues with the data integrity where the expected attributes and their dimensions are not aligned with the defined scales.
Solution
- Check Attribute Configuration: Review the configuration of the attribute that is causing the error. Ensure that it is defined with the appropriate dimension. You may need to go into the relevant customizing settings in SAP and verify the attribute settings.
- Define Dimensions for Attributes: If the attribute is supposed to have a dimension, you need to define it accordingly. This can usually be done in the customizing settings where you manage object models and their attributes.
- Review Scale and UOM Settings: Ensure that the scale and unit of measure are correctly defined and that they correspond to the expected dimensions of the attributes. If necessary, adjust the scale or UOM settings to align with the attribute definitions.
- Data Validation: Perform data validation checks to ensure that all relevant attributes and scales are correctly populated and that there are no inconsistencies in the data.
- Consult Documentation: Refer to SAP documentation or help resources for specific guidance on configuring object models and attributes, as well as handling dimensionality issues.
Related Information
By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
ESH_OM_OBJ_MODEL_RP2854
The scale is of dimension &4 (uom &3) but attribute &1 is of dimension &2
What causes this issue? A ranking factor attribute can have a dimension and a scale can have a unit of measure (uom) which itself has a dimension. He...
ESH_OM_OBJ_MODEL_RP2853
Dimension key &1 of refrenced attribute &2 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_OM_OBJ_MODEL_RP2856
The scale has no uom but attribute &1 is of dimension &2 with si-unit &3
What causes this issue? A ranking factor attribute can have a dimension and a scale can have a unit of measure (uom) which itself has a dimension. Th...
ESH_OM_OBJ_MODEL_RP2857
Node &1 has no parent node - maybe relation report missing
What causes this issue? The node &v1& is no root node but no composition to its parent node exists.System Response The system issues an erro...
Click on this link to search all SAP messages.