How To Fix FZ120 - Payment medium run was reset

SAP Error Message - Details

• Message type: E = Error

• Message class: FZ - Payment Transactions

• Message number: 120

• Message text: Payment medium run was reset

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FZ120 - Payment medium run was reset ?

  The SAP error message FZ120, which states "Payment medium run was reset," typically occurs during the execution of a payment medium run in the SAP system. This error indicates that the payment medium run was interrupted or canceled, preventing the successful generation of payment files.
  Causes:
  
  User Intervention: The payment medium run may have been manually canceled by a user.
  System Errors: There could be underlying system issues, such as database locks or connectivity problems, that caused the run to fail.
  Configuration Issues: Incorrect configuration settings in the payment medium format or payment method can lead to this error.
  Missing Data: Required data for the payment run may be missing or incomplete, causing the process to be reset.
  Authorization Issues: The user executing the payment run may not have the necessary authorizations to complete the process.
  
  Solutions:
  
  Check Logs: Review the application logs (transaction SLG1) for any detailed error messages or warnings that can provide more context about why the run was reset.
  Re-run the Payment Medium: If the issue was a temporary glitch, you can try to re-run the payment medium process.
  Verify Configuration: Ensure that the payment medium format and payment method configurations are correct. Check transaction OBPM1 for payment medium formats and transaction FBZP for payment methods.
  Data Validation: Ensure that all necessary data for the payment run is complete and accurate. Check for missing vendor or customer information.
  User Authorizations: Verify that the user has the appropriate authorizations to execute the payment medium run.
  System Health Check: If the issue persists, perform a system health check to identify any underlying issues that may be affecting the payment run.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  FBZP: Payment methods in country
  OBPM1: Payment medium formats
  SLG1: Application log
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the payment medium run.
  Documentation: Review SAP documentation for payment processing and payment medium generation for best practices and troubleshooting steps.
  
  If the problem continues after trying the above solutions, it may be necessary to consult with your SAP Basis team or SAP support for further assistance.