How many times the question “How to cancel payment run F110?” (reverse F110, mass change F110, you name it) has been raised here on SCN?
The answer has always been: do it manually by FBRA + F.80. Manual. Painful. Long. Frustrating.
Well it was till now. Because believe it or not, SAP has actually improved F110 :smile: .
Source: http://www.sapimprovementfinder.com/public/note?n=0002127698
Improvement request
The department can reverse the payment documents of a payment run (F110) only individually using transactions FBRA and FB08. In case of error, it should be possible to reverse all payment documents of a payment run.
Reason
If an error occurs (for example, caused by incorrect Customizing settings or incorrect parameter entries), the reversal of all payment documents of a payment run is time-critical because late payments may have negative financial effects. Currently, reversals must be made individually by a user or with the help of a customer program or a consulting program. In the standard SAP system, there is no solution for this exceptional situation.
Improvement
With the new program RFF110S_REVERSE, the department can reverse all payment documents of a payment run (F110) if there are incorrect clearing postings in the payment run due to an error. Application examples:
- There is an incorrect grouping of cleared items due to incorrect Customizing settings.
- There is an incorrect posting date or value date due to incorrect parameter entries.
Subsequently, the payment run can be repeated under a new identification after the correction of the Customizing or the parameters.
Benefit
With the new program RFF110S_REVERSE, the department can reset and repeat the payment run timely and without support from IT, the support department, or consulting. As a result, the risk of financial damage caused by late payments due to user errors is reduced.
Delivery
The improvement is delivered as of SAP ERP 6.0 via a correction, and it is also delivered in a Support Package as of SAP ERP 6.0 Enhancement Package 7. For additional information, see SAP Note 2125220.
