How to Delete Wrongly Entered Bank Statements
- by Kees van Westerop, Senior SAP Consultant, Kwest Consulting
- February 15, 2004
SAP R/3 does not provide a standard transaction to delete bank statements from the Banks module in FI. This can lead to time-consuming problems when erroneous statements make their way into your system. While there is no transaction code, there is a report that allows you to delete bank statements. It has the added benefit of being able to work as timesaving testing tool that can be reused again and again. However, there is a risk when you use the report. If a user accidentally clicks the delete button without deselecting the found bank statements, the report deletes all bank statements for all company codes.
SAP R/3 does not provide a standard transaction to delete bank statements from the Banks module in FI. This can lead to time-consuming problems when erroneous statements make their way into your system. While it offers no transaction code, SAP provides a report that allows you to delete bank statements. It also has the added benefit of being able to work as a timesaving testing tool that can be reused again and again.
I learned about report RFEBKA96 from a colleague after implementing settings that allow bank statements to be entered manually in SAP. SAP R/3 can be configured to allow bank statements to be automatically entered into the system electronically or by manual entry. A user inadvertently entered a current date as a statement date and it was impossible to delete the bad statement. The problem became nearly critical because program FF67 limits the bank statements that can be entered into the system depending on its statement number and date.
In my crisis, the user was not allowed to enter a bank statement when the statement number was larger than a previously entered statement's number if it predated the lower numbered statement's date. None of the old bank statements with the correct date could be entered without the system generating an error indicating that the older bank statements already existed. The offending statement was several weeks old, so all bank statements with a statement date prior to the erroneous date had to be entered with bad statement dates as well.
Report RFEBKA96 provided a straightforward avenue to remove unwanted bank statements from the SAP system, and it allowed me to correct the above problem. Because all bank statements generate other financial documents in the system, I then went back and deleted the financial documents initiated by the bad bank statements to prevent double books when they were reprocessed with the correct date.
Report RFEBKA96 also provides a timesaving way to test that electronic bank statements are processed correctly. Typically, when testing an electronic bank statement, you upload an electronic file using transaction FF_5 into the SAP system. Without report RFBEKA96, you cannot reuse the same upload file twice to retest settings and you must adjust the opening balance, closing balance, and bank statement number after performing the test. By deleting the bank statement from the SAP system with this report, you don't have to make those changes and you can reuse the file as often as you wish.
Would you like to see this full item?