How To Fix /STMC/CR_MSG895 - Error while merging &1&2 for CM-Object &3: base document not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /STMC/CR_MSG -

• Message number: 895

• Message text: Error while merging &1&2 for CM-Object &3: base document not found

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 /STMC/CR_MSG895 - Error while merging &1&2 for CM-Object &3: base document not found ?

  The SAP error message /STMC/CR_MSG895 indicates that there is an issue while merging two components (or objects) in the Change Management (CM) context. The specific message states that the base document for the merge operation could not be found. This typically occurs in scenarios involving change requests, transport requests, or document management within SAP.
  Cause:
  
  Missing Base Document: The most common cause of this error is that the base document (the original document that is being merged) is missing or has been deleted from the system.
  Incorrect Object References: The references to the objects being merged may be incorrect, leading to the system being unable to locate the base document.
  Transport Issues: If the objects are part of a transport request, there may be issues with the transport itself, such as it not being released or imported correctly.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the base document.
  
  Solution:
  
  Check Document Existence: Verify that the base document exists in the system. You can do this by searching for the document using its identifier or key.
  Review Object References: Ensure that the references to the objects being merged are correct. Check if the identifiers used in the merge operation are valid and correspond to existing documents.
  Transport Request Verification: If the objects are part of a transport request, check the status of the transport. Ensure that it has been released and imported correctly into the target system.
  Authorization Check: Ensure that the user performing the merge operation has the necessary authorizations to access the base document and perform the merge.
  Consult Logs: Check the system logs for any additional error messages or warnings that may provide more context about the issue.
  SAP Notes: Look for relevant SAP Notes or documentation that may address this specific error. SAP frequently updates its knowledge base with solutions for known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE09 (Transport Organizer), SE10 (Transport Organizer for Workbench Requests), and SE38 (ABAP Editor) for debugging purposes.
  SAP Support: If the issue persists, consider reaching out to SAP Support for assistance. Provide them with the error message details and any relevant logs or screenshots.
  Documentation: Review SAP documentation related to Change Management and document merging for best practices and troubleshooting steps.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.