How To Fix CM_EHFND_REQ_EXT_IMP035 - Cannot update or add new revision with different &2 of req. with ID "&1"

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_EHFND_REQ_EXT_IMP - Message Class For External Content Providers Import

• Message number: 035

• Message text: Cannot update or add new revision with different &2 of req. with ID "&1"

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 CM_EHFND_REQ_EXT_IMP035 - Cannot update or add new revision with different &2 of req. with ID "&1" ?

  The SAP error message CM_EHFND_REQ_EXT_IMP035 indicates that there is an issue with updating or adding a new revision of a request due to a mismatch in the specified field (denoted by &2) for the request with the ID &1. This typically occurs in the context of managing change requests or transport requests in SAP, particularly when dealing with external import processes.
  Cause:
  The error is usually caused by one of the following reasons:
  
  Field Mismatch: The field specified (e.g., a version number, status, or other key attribute) does not match the existing record in the database. This could happen if the request is being modified in a way that is not allowed due to business rules or system constraints.
  Data Integrity Issues: There may be data integrity issues where the system expects certain values to remain consistent across revisions, and the new revision is attempting to change a critical field.
  Authorization Issues: The user may not have the necessary permissions to make changes to the specified request or field.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  Check the Request ID: Verify that the request ID (&1) is correct and that you are attempting to update the correct request.
  Review Field Values: Look at the field specified by &2 and ensure that the value you are trying to set is consistent with the existing data. If you are trying to change a field that should not be changed, consider whether you need to create a new request instead.
  Consult Documentation: Review the relevant SAP documentation or configuration settings to understand the rules governing the field in question.
  User Authorizations: Ensure that you have the necessary authorizations to perform the update. If not, contact your SAP administrator to obtain the required permissions.
  Check for Locks: Ensure that the request is not locked by another user or process, which could prevent updates.
  System Logs: Check the system logs for any additional error messages or warnings that might provide more context about the issue.
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that might address this specific error message or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with transaction codes related to change requests and transport management, such as SE09 (Transport Organizer) and SE10 (Transport Organizer for Workbench Requests).
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the issue persists after following these steps, it may be necessary to involve your SAP Basis team or technical support for further investigation.