How To Fix MQ543 - Dunning runs &1 / &2 have not been completed

SAP Error Message - Details

• Message type: E = Error

• Message class: MQ - Messages for Euro Changeover Package

• Message number: 543

• Message text: Dunning runs &1 / &2 have not been completed

What causes this issue?

All dunning runs must have been completed before the local currency
changeover. There are still dunning runs in the system for which
dunning notices have not yet been printed.

System Response

The program remains in the ERROR status.

How to fix this error?

Check these dunning runs as to whether these have to be completed
beforehand or whether they can be deleted. Carry out the corresponding
activities (printing the dunning notices or deleting the dunning run).

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MQ543 - Dunning runs &1 / &2 have not been completed ?

  The SAP error message MQ543 indicates that a dunning run has not been completed successfully. This error typically arises in the context of the dunning process, which is used to manage accounts receivable and remind customers of overdue payments.
  Cause:
  The error message MQ543 can be triggered by several factors, including:
  
  Incomplete Dunning Run: The dunning run may have been interrupted or not executed to completion due to system errors, user intervention, or other issues.
  Configuration Issues: There may be configuration problems in the dunning settings, such as incorrect parameters or missing data.
  Authorization Issues: The user executing the dunning run may not have the necessary authorizations to complete the process.
  Technical Errors: There could be underlying technical issues, such as database locks, system performance problems, or other system errors that prevent the dunning run from completing.
  
  Solution:
  To resolve the MQ543 error, you can follow these steps:
  
  
  Check Dunning Run Status: Go to the transaction code for dunning (usually F150) and check the status of the dunning run. Look for any logs or messages that indicate why the run was not completed.
  
  
  Review Configuration: Ensure that the dunning configuration is set up correctly. Check the dunning procedure, dunning levels, and any related settings in the configuration.
  
  
  Re-run the Dunning Process: If the dunning run was interrupted, you may need to re-run it. Make sure to select the correct parameters and ensure that all necessary data is available.
  
  
  Check Authorizations: Verify that the user executing the dunning run has the appropriate authorizations. If not, you may need to adjust user roles or permissions.
  
  
  Consult Logs: Check the system logs (transaction SM21) and application logs (transaction SLG1) for any error messages or warnings that could provide more context on the failure.
  
  
  Technical Support: If the issue persists, consider reaching out to your SAP Basis team or technical support for assistance. They can help diagnose any underlying technical issues.
  
  
  Related Information:
  
  Dunning Process: Understand the dunning process in SAP, including how to configure dunning procedures and levels.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F150 (Dunning) and FBL1N/FBL5N (Vendor/Customer Line Items) for checking account statuses.
  SAP Notes: Check SAP Notes for any known issues or patches related to the dunning process and the specific error message.
  
  By following these steps, you should be able to identify the cause of the MQ543 error and take appropriate action to resolve it.