How To Fix CM_SUB_INFOSYS036 - Contained indirectly also is only possible with dimension "relationshp"

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_SUB_INFOSYS - Substance information system

• Message number: 036

• Message text: Contained indirectly also is only possible with dimension "relationshp"

What causes this issue?

In the search <LS>Specification contains components</>, you can choose
<LS>Cont. indirectly also</> only if you have entered a relationship
(technically MPROPO, PROPOR, or VPROPO) as a unit of measurement
dimension in the <LS>Ref. quantity</> field.
A multilevel component relationship cannot be summarized as a
single-level relationship if it contains a dimension that cannot be
interpreted as a percentage (for example, weight specified in
kilograms).
Example:
A substance A contains a substance B that contains a substance C. These
two component relationships have the following weights specified:
Substance A
|
| 10 kg
|
Substance B
|
| 20 kg
|
Substance C
From the data model it is not possible to determine how many kilograms
of substance C are contained in substance A without additional
information.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CM_SUB_INFOSYS036 - Contained indirectly also is only possible with dimension "relationshp" ?

  The SAP error message CM_SUB_INFOSYS036 typically occurs in the context of SAP BW (Business Warehouse) or SAP HANA when dealing with data modeling, particularly when working with InfoObjects and their relationships. The error message indicates that a certain operation or configuration is not allowed because it involves dimensions that are not compatible with the specified relationship type.
  Cause:
  The error message "Contained indirectly also is only possible with dimension 'relationship'" suggests that you are trying to create or modify a data model or InfoProvider that involves dimensions that cannot be linked in the way you are attempting. Specifically, it indicates that the relationship you are trying to establish is not valid for the dimensions involved.
  Possible Causes:
  
  Incorrect Dimension Type: You may be trying to use a dimension that is not defined as a "relationship" dimension.
  Modeling Restrictions: There may be restrictions in the data model that prevent certain types of relationships from being established.
  Hierarchy Issues: If you are working with hierarchies, there may be issues with how they are defined or linked.
  Data Source Compatibility: The data source you are using may not support the type of relationship you are trying to create.
  
  Solution:
  To resolve this error, consider the following steps:
  
  
  Check Dimension Types: Ensure that the dimensions you are working with are correctly defined and that the relationships you are trying to establish are valid for those dimensions.
  
  
  Review Data Model: Go through the data model to ensure that all relationships are correctly defined and that there are no conflicts or unsupported configurations.
  
  
  Use Correct Relationship Type: If you are trying to create a relationship, make sure you are using the correct type of relationship (e.g., "relationship" dimension) as required by the system.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on how to define relationships between dimensions in your version of SAP BW or HANA.
  
  
  Test Changes: After making adjustments, test the changes in a development environment before applying them to production.
  
  
  Seek Support: If the issue persists, consider reaching out to SAP support or consulting with an SAP BW/HANA expert who can provide more tailored assistance based on your specific configuration and requirements.
  
  
  Related Information:
  
  SAP BW Documentation: Review the official SAP BW documentation for detailed information on data modeling and dimension relationships.
  SAP Community: Engage with the SAP Community forums where you can find discussions and solutions related to similar issues.
  Training Resources: Consider SAP training courses that cover data modeling and InfoProviders in SAP BW or HANA for a deeper understanding of the concepts involved.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.