How To Fix M8660 - Document & was deleted and regenerated under & ( & & )

SAP Error Message - Details

• Message type: E = Error

• Message class: M8 - Invoice Verification/Valuation

• Message number: 660

• Message text: Document & was deleted and regenerated under & ( & & )

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 M8660 - Document & was deleted and regenerated under & ( & & ) ?

  The SAP error message M8660 indicates that a document has been deleted and subsequently regenerated. This typically occurs in the context of inventory management or material document processing. Here’s a breakdown of the cause, potential solutions, and related information:
  
  Cause:
  
  Document Deletion: The original document (e.g., a material document related to goods movement) was deleted. This could happen due to various reasons, such as manual deletion by a user, a system error, or a data correction process.
  Regeneration: After deletion, the system automatically regenerates the document, which can lead to inconsistencies or conflicts if the original document is still referenced in other processes or transactions.
  
  
  Solution:
  
  Check Document Status: Verify the status of the document in question. You can use transaction codes like MB03 (Display Material Document) to check if the document exists and its current status.
  Review Change Logs: Use transaction code SCU3 to review change logs for the material document to understand why it