How To Fix M8662 - Document & deleted and saved as parked under & ( & & )

SAP Error Message - Details

• Message type: E = Error

• Message class: M8 - Invoice Verification/Valuation

• Message number: 662

• Message text: Document & deleted and saved as parked under & ( & & )

What causes this issue?

The 'parked as complete' invoice document &V1& has been deleted and
recreated with the status 'parked' under the invoice document number
&V2&.

System Response

When the fiscal year of a parked-as-complete invoice document invoice
document is changed, the system deletes the original document and
creates a document with the same data in the new fiscal year. When the
FI document type is changed by the assignment of a different number
range interval, the system proceeds analogically.
In this case, the system was only able to generate the new document in
the status 'parked' even though the original document had the status
'parked as complete'. Errors occurred preventing the automatic creation
of the invoice document in the original status 'parked as complete'.

How to fix this error?

Remaintain invoice document &V2& manually with the transaction 'Change
Invoice Document' (transaction code MIR4) by saving the invoice document
as 'parked as complete'.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message M8662 - Document & deleted and saved as parked under & ( & & ) ?

  The SAP error message M8662 indicates that a document has been deleted and subsequently saved as a parked document. This typically occurs in the context of material management or financial transactions within SAP. Here’s a breakdown of the cause, potential solutions, and related information:
  
  Cause:
  
  Document Deletion: The original document (such as a material document or accounting document) was deleted in the system.
  Parking Process: After deletion, the system may have automatically parked the document, which means it is saved in a temporary state and not yet posted to the ledger.
  User Actions: This can happen due to user actions, such as trying to reverse a document or during a posting process where the document is not in a valid state.
  
  
  Solution:
  
  Check Document Status: Verify the status of the document in question. You can do this by using transaction codes like MB03 (for material documents) or FB03 (for financial documents) to see if the document