How To Fix EK338 - Disconnection document not created as an item has already been cleared

SAP Error Message - Details

• Message type: E = Error

• Message class: EK - IS-U Accounts Receivable and Payable

• Message number: 338

• Message text: Disconnection document not created as an item has already been cleared

What causes this issue?

Business partner &V1& has reached a dunning level in which a disconnect
document is to be created, however, a dunned document has been paid
between the dunning proposal run and the dunning activity run. As a
result, no disconnect document is created.

System Response

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

How to fix this error?

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EK338 - Disconnection document not created as an item has already been cleared ?

  The SAP error message EK338, which states "Disconnection document not created as an item has already been cleared," typically occurs in the context of invoice verification or payment processing in SAP. This error indicates that the system is unable to create a disconnection document because the item in question has already been cleared or settled in a previous transaction.
  Cause:
  
  Cleared Item: The most common cause of this error is that the item you are trying to process has already been cleared in a prior transaction. This means that the financial transaction related to that item has been completed, and the system does not allow further processing on it.
  Incorrect Document Flow: There may be an issue with the document flow where the item was cleared in a way that the system does not recognize it as available for further processing.
  Data Integrity Issues: There could be inconsistencies in the data or configuration that prevent the system from recognizing the item as eligible for disconnection.
  
  Solution:
  
  Check Item Status: Verify the status of the item in question. You can do this by checking the relevant accounting documents or transaction history to confirm whether the item has indeed been cleared.
  Review Clearing Documents: Look for any clearing documents that may have been created for the item. If the item has been cleared, you may need to reverse the clearing if appropriate, depending on your business processes.
  Reprocess the Transaction: If the item was cleared in error, you may need to reverse the clearing and then attempt to create the disconnection document again.
  Consult with Finance Team: If you are unsure about the clearing status or how to proceed, consult with your finance or accounting team to ensure that you are following the correct procedures.
  Check Configuration: If this error occurs frequently, it may be worth reviewing the configuration settings in SAP related to invoice verification and clearing processes to ensure they are set up correctly.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like FB03 (Display Document), FBL1N (Vendor Line Item Display), or FBL3N (G/L Account Line Item Display) to investigate the status of the items.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common errors.
  Documentation: Review SAP documentation related to invoice verification and clearing processes for more detailed guidance on handling such errors.
  
  If the issue persists after following these steps, it may be necessary to involve your SAP support team or a consultant for further investigation.