How To Fix /STMC/CR_MSG897 - Error while merging &1&2 in layer &3: base document not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /STMC/CR_MSG -

• Message number: 897

• Message text: Error while merging &1&2 in layer &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_MSG897 - Error while merging &1&2 in layer &3: base document not found ?

  The SAP error message /STMC/CR_MSG897 indicates that there is an issue while merging documents in a specific layer, where the base document cannot be found. This error typically occurs in the context of SAP's Document Management System (DMS) or when dealing with change requests in the SAP Change Request Management (ChaRM) module.
  Cause:
  
  Missing Base Document: The primary cause of this error is that the system cannot locate the base document that is required for the merge operation. This could happen if the document was deleted, moved, or if there is a mismatch in the document identifiers.
  Incorrect Layer Configuration: The layer specified in the error message may not be correctly configured or may not contain the expected documents.
  Authorization Issues: There may be authorization issues preventing access to the base document.
  Data Consistency Issues: There could be inconsistencies in the database or in the document management system that prevent the system from finding the base document.
  
  Solution:
  
  Verify Document Existence: Check if the base document exists in the specified layer. You can do this by navigating to the document management area and searching for the document using its identifier.
  Check Layer Configuration: Ensure that the layer configuration is correct and that it includes the necessary documents for the merge operation.
  Review Authorizations: Make sure that the user performing the merge operation has the necessary authorizations to access the base document.
  Database Consistency Check: Run consistency checks on the database to identify and resolve any inconsistencies that may be causing the issue.
  Recreate the Base Document: If the base document is missing and cannot be recovered, you may need to recreate it or restore it from a backup if available.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes or patches that may address this specific error.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CV01N (Create Document), CV02N (Change Document), and CV03N (Display Document) for managing documents in SAP DMS.
  Change Request Management: If this error occurs in the context of ChaRM, ensure that the change request is properly configured and that all related documents are correctly linked.
  SAP Community and Forums: Consider searching or posting in SAP community forums for additional insights or similar experiences from other users.
  
  If the issue persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.