How To Fix /SCWM/EEC_CHECK035 - Remote ERP release for business system &1 is not known

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/EEC_CHECK -

• Message number: 035

• Message text: Remote ERP release for business system &1 is not known

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 /SCWM/EEC_CHECK035 - Remote ERP release for business system &1 is not known ?

  The SAP error message /SCWM/EEC_CHECK035 indicates that the system is unable to find a valid remote ERP release for the specified business system. This typically occurs in the context of Extended Warehouse Management (EWM) when there is a configuration issue related to the integration between EWM and the ERP system.
  Cause:
  
  Missing Configuration: The business system (e.g., an ERP system) may not be properly configured in the EWM system.
  Incorrect Release Information: The release information for the business system may not be correctly defined or may be missing.
  System Landscape Issues: There may be issues with the system landscape configuration, such as incorrect RFC destinations or missing logical systems.
  Transport Issues: If the configuration was recently transported from another system, it may not have been set up correctly.
  
  Solution:
  
  
  Check Business System Configuration:
  
  Go to the transaction code SPRO and navigate to the EWM settings.
  Ensure that the business system is correctly defined and that the relevant ERP release is specified.
  
  
  
  Verify Logical System:
  
  Check the logical system configuration in transaction SCC4 to ensure that the logical system for the ERP is correctly set up.
  Ensure that the logical system is assigned to the correct client.
  
  
  
  Check RFC Connections:
  
  Use transaction SM59 to verify that the RFC connection to the ERP system is correctly configured and operational.
  Test the connection to ensure that it is working as expected.
  
  
  
  Review Release Information:
  
  Ensure that the release information for the business system is correctly maintained in the EWM configuration.
  You may need to check the relevant customizing settings in the EWM system.
  
  
  
  Transport Requests:
  
  If the configuration was recently transported, check the transport logs for any errors or issues.
  Ensure that all necessary objects were included in the transport request.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to EWM and integration with ERP for any specific requirements or known issues.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  EWM Documentation: Review the official SAP EWM documentation for best practices on system integration and configuration.
  
  By following these steps, you should be able to identify and resolve the issue causing the /SCWM/EEC_CHECK035 error message.