How To Fix RD035 - DataSource &1 cannot be displayed in combined profitability analysis.

SAP Error Message - Details

• Message type: E = Error

• Message class: RD - CO-PA Connection to SAP BW

• Message number: 035

• Message text: DataSource &1 cannot be displayed in combined profitability analysis.

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message RD035 - DataSource &1 cannot be displayed in combined profitability analysis. ?

  The SAP error message RD035 indicates that a specific DataSource cannot be displayed in combined profitability analysis (COPA). This error typically arises when there are issues related to the configuration or the data source itself. Here’s a breakdown of the potential causes, solutions, and related information:
  Causes:
  
  DataSource Configuration: The DataSource may not be properly configured for use in COPA. This could include missing settings or incorrect mappings.
  DataSource Activation: The DataSource might not be activated in the system, which is necessary for it to be used in reporting.
  Authorization Issues: The user may not have the necessary authorizations to access the DataSource or the related profitability analysis data.
  Data Source Compatibility: The DataSource may not be compatible with the version of SAP or the specific COPA setup being used.
  Technical Issues: There could be underlying technical issues, such as problems with the data extraction process or data inconsistencies.
  
  Solutions:
  
  
  Check DataSource Configuration:
  
  Go to the DataSource configuration in the SAP system (transaction code RSA1).
  Ensure that the DataSource is correctly set up for COPA and that all necessary fields are mapped correctly.
  
  
  
  Activate the DataSource:
  
  If the DataSource is not activated, activate it in the Data Warehousing Workbench (transaction code RSA1).
  After activation, check if the error persists.
  
  
  
  Review Authorizations:
  
  Ensure that the user has the necessary authorizations to access the DataSource and the COPA reports.
  Check the roles and profiles assigned to the user.
  
  
  
  Check Compatibility:
  
  Verify that the DataSource is compatible with the version of SAP you are using.
  Consult SAP notes or documentation for any known issues or updates related to the DataSource.
  
  
  
  Technical Troubleshooting:
  
  Check for any errors in the data extraction process. You can use transaction codes like SLG1 to view application logs for any related errors.
  If there are inconsistencies in the data, consider running data consistency checks or reloading the data.
  
  
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to the DataSource or COPA.
  Documentation: Review the official SAP documentation for COPA and DataSources to ensure that you are following best practices.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or technical team for further investigation or to reach out to SAP support for assistance.