How To Fix F5A173 - Document cannot be deleted since follow-on document already exists

F5A173 - Overview

• Message type: E = Error

• Message class: F5A - Document Editing

• Message number: 173

• Message text: Document cannot be deleted since follow-on document already exists

What causes this issue?

You have tried to delete a cash journal document. This document is a
check that has been transferred from the cash account.

System Response

The system does not delete the document, since the transfer of the
check has already generated one or more follow-on documents and
deletion of the document would lead to inconsistencies.

How to fix this error?

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

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message F5A173 - Document cannot be deleted since follow-on document already exists ?

  
  Cause:
  The SAP error message F5A173 occurs when you try to delete a document in SAP that has a follow-on document already created. This error message is a preventive measure to ensure data integrity and consistency within the system.
  
  Solution:
  To resolve this error, you need to first delete the follow-on document before attempting to delete the original document. Follow these steps:
  
  
  Identify the follow-on document: Check the document number or reference number mentioned in the error message. This will help you identify the document that needs to be deleted first.
  
  
  Delete the follow-on document: Use the appropriate transaction code or navigation path to access the follow-on document. Once you have located the document, delete it using the relevant delete function or transaction.
  
  
  Delete the original document: After successfully deleting the follow-on document, go back to the original document and attempt to delete it again. This time, the deletion should be successful without the F5A173 error.
  
  
  Related