Top 12 Common F110 Payment Run Errors and How to Solve in SAP

SAP Payment Proposal or Payment Run errors can be treated as an urgent concern especially if the transaction is in production. We are also considering that there is most likely a payment deadline that the client needs to meet.

In this tutorial, we will talk about the Top 12 common errors encountered during payment proposal or payment run (Transaction Code F110) in SAP. I will be including the actual error messages, their message class / message number log, and provide insight as to how to analyze or solve the error.

For those of you who are encountering this error in a non-production environment such as a test system or development system, you can still refer to the resolution below.

What is the TCode for Automatic Payment Run in SAP?

The transaction code for automatic payment run in SAP is F110. This will be the main transaction code for:

• Creating your payment run parameters,
• Executing the payment proposal,
• Executing the payment run,
• Triggering the payment medium output or Data Medium Exchange (DME), and
• Viewing the payment run error logs (if any)

Before executing or utilizing the automatic payment in SAP, it is necessary that the corresponding SAP configurations are already setup in the system.

Some example prerequisites would be the following:

• Transaction Code FBZP – Maintain Payment Program Configuration (this is the configuration where you can link payment methods to a specific payment medium format)
• Transaction Code OBPM1 – Creation of Payment Medium Formats
• Transaction Code DMEE – Data Medium Exchange Engine (for DME tree configuration)
• Transaction Code OBPM4 – Maintain Payment Medium Selection Variants / Assign Payment Medium Format to the concerned house banks

It is possible that some configurations may be left out or some settings have changed thus triggering errors, so it is always good to check on the configurations.

Why is the Payment Medium Important in SAP Automatic Payment Run?

You should also consider that the SAP payment run (F110) could be setup to output a payment medium output / file to a location in SAP or a shared folder.

Depending on how the system is setup, it is possible that these files will be provided to banks for their utilization. This is why the Payment Medium Format and DME configurations were mentioned as a pre-requisite.

Overview of SAP Payment Proposal Errors

1. Vendor & & is blocked, editing not possible
2. Customer & & is blocked, editing not possible
3. Item is blocked for payment
4. Vendor & &: No payment due to delete flag or posting block
5. Customer & &: No payment due to delete flag or posting block
6. Customer/vendor does not have suitable bank details for pmnt method &
7. Account & is contained in proposal & &; release not possible
8. Vendor & & is contained in proposal & &; no editing
9. Payment proposal & & has not yet been created
10. Payment method & is not defined in country &; correct
11. Payment method & is not defined in company code &; correct
12. File & could not be opened

Vendor & & is blocked, editing not possible

Message Class FZ Message Number 361

This error usually happens when another user is making changes or currently making a transaction to the same vendor. You can verify this by going to Transaction Code SM12 and entering the corresponding table (in this case it is LFB1 for vendor company code master data).

You should see a Lock Entry List below with details such as:

• User Name (highlighted in green)
• Date and Time details (highlighted in orange)
• Lock argument – this should contain the sap client, vendor number, vendor company code (highlighted in grey)
• Other attributes such as Transaction Code being used (under technical attributes)

In this example, we see that the other user is using transaction code FB05 to do a clearing transaction for the vendor. Thus, the error on vendor being blocked and the payment proposal or run cannot make edits.

To proceed with the payment proposal or run, the user (indicated in lock entry list) should close the window once done with the ongoing transaction.

Customer & & is blocked, editing not possible

Message Class FZ Message Number 360

This is the same approach to “Vendor & & is blocked, editing not possible” where you need to check on SM12 for the Lock Entry List.

This error usually happens when another user is making changes or currently making a transaction to the same customer. You can verify this by going to Transaction Code SM12 and entering the corresponding table (in this case it is KNB1 for customer company code master data).

To proceed with the payment proposal or run, the user (indicated in lock entry list) should close the window once done with the ongoing transaction.

Item is blocked for payment

Message Class FZ Message Number 503

The document/s indicated in the payment proposal or run has a payment block in its line item. Go to Transaction Code FB03 and view the corresponding document line item to see if there is a payment block indicated.

If this no longer needs to be blocked, the document should be updated such that payment block is removed.

Vendor & &: No payment due to delete flag or posting block

Message Class FZ Message Number 368

This happens when the concerned vendor has a posting block or deletion flag indicated. You can check on this through transaction codes XK05, XK06, FK05, and FK06. Transaction codes with “X” pertain to central edits while those with “F” correspond to company code level only.

You can also review the change logs by going to Environment > Account Changes, All Fields to see if any changes coincide with the date and time of the payment proposal run.

If the master data needs to be updated, the block or deletion flag needs to be removed. Here are some screenshots below.

As additional check, you can also go to FK03 or XK03 and view the Payment Transactions window to see if there is a payment block indicated on that level.

Customer & &: No payment due to delete flag or posting block

Message Class FZ Message Number 369

This is a similar case with error “Vendor & &: No payment due to delete flag or posting block” where the concerned customer has a posting block or deletion flag set.

You can check on this through transaction codes XD05, XD06, FD05, and FD06. Transaction codes with “X” pertain to central edits while those with “F” correspond to company code level only.

You can also review the change logs by going to Environment > Account Changes, All Fields to see if any changes coincide with the date and time of the payment proposal run.

If the master data needs to be updated, the block or deletion flag needs to be removed. Here are some screenshots below.

Customer/vendor does not have suitable bank details for pmnt method &

Message Class FZ Message Number 019

Review your customer or vendor master data (specifically in the payment transactions window) and update them as needed. You can do this through transaction codes XD03, FD03 for customer master data and XK03, FK03 for vendor master data.

Bank account and other bank details should be maintained accurately. These bank details should also be useable for the specific payment method.

As additional checking, you need to verify if the SWIFT / IBAN needs to be maintained in the master data.

Payment Transactions

Account & is contained in proposal & &; release not possible

Message Class FZ Message Number 032

The specified account is already contained in a different payment proposal run. In order to prevent double processing, SAP is letting you know that this parameter is already part of a different payment proposal run. As such, the payment proposal cannot be executed.

Analyze which payment run should contain the indicated account and remove the other instance from the other payment proposal (parameter). “contained in proposal & &” will let you know which payment run ID and run date is concerned. You can further analyze by entering these details and viewing the logs in transaction code F110.

Vendor & & is contained in proposal & &; no editing

Message Class FZ Message Number 349

The specified vendor and company code is already contained in a different payment proposal run. In order to prevent double processing, SAP is letting you know that this parameter is already part of a different payment proposal run. As such, the payment proposal cannot be executed.

Analyze which payment run should contain the indicated vendor and remove the other instance from the other payment proposal (parameter). “contained in proposal & &” will let you know which payment run ID and run date is concerned. You can further analyze by entering these details and viewing the logs in transaction code F110.

Payment proposal & & has not yet been created

Message Class FZ Message Number 001

You cannot do a payment run without executing your payment proposal first through transaction code F110. The order should always be the following:

1. Enter payment run parameters
2. Execute payment proposal run
3. Execute payment run

Payment method & is not defined in country &; correct

Message Class FZ Message Number 009

This is a missing configuration in FBZP. You need to maintain the payment method in the specified country. If the payment method or country is incorrect, update the payment parameters instead.

FBZP

Payment method & is not defined in company code &; correct

Message Class FZ Message Number 012

This is a missing configuration in FBZP. You need to maintain the payment method in the specified company code. If the payment method or company code is incorrect, update the payment parameters instead.

FBZP

File & could not be opened

Message Class FZ Message Number 231

Contact your BASIS team and/or concerned IT team to assist with the SAP file write permissions. There is a system account for SAP where the “write/read file” permissions are not allowed.

BASIS or the concerned IT team should update those permissions so SAP can read / write the payment medium output file in the designated shared folder or file path.

If the specified location in the error log is incorrect, please update the configuration for SAP to write the payment medium output file to the right location or file path.

I hope this helps. Good luck! 😊