Time-Saving Tips for Testing Electronic Bank Statement in BAI2 Format
- by Seyed Omar Zeirideen, SAP Solution Architect
- January 16, 2014
Learn some tips on how to optimize the implementation and testing of the BA12 electronic bank statement file format for financial reporting.
After reading this article you’ll know how to:
- Test bank statement customization in a timely and effective manner.
- Generate test data for a BAI2 bank statement file format and open items.
- Reprocess the same test data by deleting the system buffer.
The BA12 electronic bank statement file format is used to transfer financial data to perform electronic cash management balance reporting. Balance reporting transmissions include data describing hundreds of different types of account activities.
Even the most experienced experts struggle when implementing the BAI2 electronic bank statement file format because creating a file from scratch or editing an existing file can be cumbersome and prone to errors. I describe some simple tools that make this process more effective and error free. This process is used in the SAP Banking (FI-BL) submodule in SAP ERP Financials. SAP offers two standard programs, both of which enable you to simulate the actual transmission process within an SAP system and validate the file format. These programs not only ensure that the testing is done correctly but also eliminate the risks of wasting time and money.
I explain how to create sample test files out of SAP transactional records using program RFEBKAT5 and how to save time by deleting the buffer with program RFEBKA96. Deleting the buffer allows you to bypass a system check and lets you reuse the test files.
Would you like to see this full item?