The customer of our project uses such Vendors accounts that specified in payment orders of it’s different departments (geographically remote from each other). Such payment orders are generated in the Customer's organization by the hundreds every day. F110 settings in our project not presuppose the payment postings creating when create payment orders. The F110 functionality does not allow to create payment orders simultaneously by such Vendors accounts (in different departments). System blocks such Vendors accounts when users use them simultaneously in F110 (when such Vendors accounts are in different F110 proposals). We have the following errors in SAP (links to pictures. Also in attach):
1. https://yadi.sk/i/3YdRwTy0brTQU
2. https://yadi.sk/i/WNtB-Lw6brTWJ
Here is the official response of SAP Active Global Support on the issue. In General, SAP says that Vendors account level locking allows to avoid doubled payments. It is impossible to disable this lock by customizing.
Have you ever faced a similar problem? Do you have a solution of this problem?
SAP Active Global Support
Kindly note that blocking of vendor/customer accounts takes place at account level but not at document level.
The requested by you functionality of blocking based on involved documents rather than on business partners are not designed and is not planned to be realized by SAP Global Development Department in the standard.
The explanation of this system behavior is that when you schedule the proposal, it will never be allowed to launch another one at the same time because each proposal need to access the entire table (in order to avoid double payment). The system needs to access the whole table, and therefore, the vendor is blocked in the company code to avoid system inconsistencies. You block the vendor to be sure not to pay the same document/invoice twice. This will also happen if for example you create two documents and selects them in additional selections one at a time. The vendor will still be blocked. System will always check the Vendor number, regardless of the company code or the subdivision in order to assure that there is no duplication in payments.
This is the standard system design that is not planned to be altered. You should release the payment run or delete the proposal otherwise error FZ349 should arise.
SAP Standard System is designed in this way: when you run the F110 for a vendor/customer account, an entry in table REGUS is created to block the account.
Once this entry is create, there is no way to include this vendor in another payment proposal as you get the following error message. This is always done by the automatic payment program. The followings are some highlights with regards to system logic for the payment proposal block:
1. Payment proposal will be blocked by another vendor including the same vendor; but manual payment is blocked on item level, not on account level.
2. The block on item level is only relevant for manual clearing. A vendor that is in a payment proposal is blocked for all other payment proposals.
If no payment documents were generated, so you can delete the outputs via the menu option: 'Edit > Payments > Delete output'. Afterwards,
you can plan this payment run again or you can delete the proposal so that the vendor mentioned can be selected in another payment run (deleting the proposal seems to be your case). In order to solve the problem,please take the following steps: Transaction F110 -> Run date XX.XX.XX, identification YYYY -> Menu: Edit -> Payments -> Delete Output: This will delete all REGUH, REGUP and REGUS entries concerning this payment run.