How To Fix RSPLS_CR003 - Source characteristic value '&1' is not included in hierarchy '&2'

RSPLS_CR003 - Overview

• Message type: E = Error

• Message class: RSPLS_CR - Messages on Characteristic Relationships/Data Slices

• Message number: 003

• Message text: Source characteristic value '&1' is not included in hierarchy '&2'

What causes this issue?

You are using a hierarchy with technical name '&V2&' in the
characteristic relationships for InfoCube '&V4&'. You want to perform
a derivation for characteristic '&V3&' with characteristic value '&V1&'.
However, the characteristic value is not included in the hierarchy.

System Response

The system cannot perform derivation.

How to fix this error?

If necessary, extend the hierarchy to include this value.

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSPLS_CR003 - Source characteristic value '&1' is not included in hierarchy '&2' ?

  The SAP error message RSPLS_CR003 indicates that a source characteristic value (represented as &1) is not included in the specified hierarchy (represented as &2). This error typically occurs in the context of SAP BW (Business Warehouse) when working with hierarchies in queries or data models.
  
  Cause:
  
  Missing Hierarchy Entry: The specific characteristic value you are trying to use is not part of the defined hierarchy. This can happen if the data has been updated or if the hierarchy has been modified without including the new values.
  Incorrect Hierarchy Assignment: The characteristic value may belong to a different hierarchy or may not be assigned to any hierarchy at all.
  Data Load Issues: If the data load process did not include the characteristic value in the hierarchy, it will lead to this error.
  Hierarchy Activation: The hierarchy might not be activated or might be in a state that does not allow it to be used in queries.
  
  
  Solution:
  
  Check