How To Fix MQ541 - Payment runs &1 / &2 not completed

SAP Error Message - Details

• Message type: E = Error

• Message class: MQ - Messages for Euro Changeover Package

• Message number: 541

• Message text: Payment runs &1 / &2 not completed

What causes this issue?

All payment runs must have been completed before the local currency
changeover. There are still payment proposals in the system without an
update run or scheduled and not yet complete payment runs.

System Response

The program remains in the ERROR status.

How to fix this error?

Delete any existing payment proposals. Scheduled and not yet complete
payment runs must have been completed.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MQ541 - Payment runs &1 / &2 not completed ?

  The SAP error message MQ541 indicates that a payment run has not been completed successfully. This message typically arises in the context of the payment program in SAP, which is used to process outgoing payments to vendors or customers.
  Cause:
  The error message MQ541 can be triggered by several factors, including:
  
  
  Technical Issues: There may be technical problems such as system errors, database issues, or connectivity problems that prevent the payment run from completing.
  
  
  Configuration Issues: Incorrect configuration settings in the payment program or related modules (like FI-AP for accounts payable) can lead to incomplete payment runs.
  
  
  Missing Data: Required data for the payment run may be missing or incorrect, such as vendor master data, payment terms, or bank details.
  
  
  Locking Issues: If another user or process is currently accessing the same data or if there are locks on the payment documents, it can prevent the payment run from completing.
  
  
  Insufficient Authorization: The user executing the payment run may not have the necessary authorizations to complete the process.
  
  
  Payment Medium Issues: Problems with the payment medium format or settings can also cause the payment run to fail.
  
  
  Solution:
  To resolve the MQ541 error, you can take the following steps:
  
  
  Check Logs: Review the payment run logs for detailed error messages or warnings that can provide insights into why the payment run failed.
  
  
  Verify Configuration: Ensure that the payment program is correctly configured. Check settings in transaction codes like OBPM1 (Payment Methods in Country) and FBZP (Payment Program Configuration).
  
  
  Data Validation: Validate that all necessary data is complete and correct. Check vendor master records, payment terms, and bank details.
  
  
  Check for Locks: Use transaction code SM12 to check for any locks on the payment documents. If locks are found, you may need to wait for the other process to complete or contact the user holding the lock.
  
  
  Authorization Check: Ensure that the user executing the payment run has the necessary authorizations. You can check this in transaction SU53 or by consulting with your security team.
  
  
  Test Payment Medium: If applicable, test the payment medium format to ensure it is set up correctly. You can do this in transaction OBPM2 (Payment Medium Workbench).
  
  
  Retry the Payment Run: After addressing the issues, retry the payment run. Make sure to monitor the process closely for any further errors.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F110 (Automatic Payment Transactions), FBZP (Payment Program Configuration), and SM37 (Job Monitoring) to troubleshoot and manage payment runs.
  SAP Notes: Check SAP Notes for any known issues or patches related to the MQ541 error. You can search for relevant notes in the SAP Support Portal.
  Documentation: Review SAP documentation on the payment program for best practices and troubleshooting tips.
  
  If the issue persists after following these steps, it may be necessary to involve your SAP Basis or technical support team for further investigation.