6 years ago I’ve published two posts on use of search string for bank statement in SAP (you can find them following these links: part 1, part 2). These posts became quite popular, reaching over 65 thousand views in total. So I’ve decided to write another post describing the option of this functionality, which is probably the least used in community. What’s worse, I could not find any proper documentation describing at least the basic scenario for this option.
You can find another post of mine, where I describe the business scenario behind handling of bank charges. This post will explore how search string can be used to determine the amount of bank fees and update this information for a line of bank statement into field FEBEP-SPESK. Once the amount of bank charges will be updated in this field, SAP will be able to post bank charges as a separate line item in accounting document in subledger posting area.
Let’s assume that bank statement MT940 line item looks as follows:
The purpose of the search string would be to find the amount of 10.00 and save it as fees amount.
Go to transaction code OTPM and define search string as follows – CHARGES #+.##. This entry means that SAP will look for any number that is proceed by fixed word “charges” and has two decimals.
Define search string use by assigning it to an appropriate combination of company code, house bank and account ID. Make sure to indicate correct external transaction code and the same interpretation mechanism that is used in mapping of external business transaction code to posting rule (i.e. in OT83, under “Assign External Transaction Types to Posting Rules”). Use target field “EBSPESK – Fees in account currency” – this is an update mechanism that will trigger saving of fees amount into FEBEP-SPESK.
Load bank statement and check the result in FEBAN to make sure that bank fee amount is not empty:
Check appropriate value in FEBEP :
Well… that’s basically it – easy and elegant way to extract bank charges information for a bank statement line item. What’s more important it doesn’t require any complicated development efforts. However, end result depends on the quality of bank statement information. If information is presented in a consistent manner, the chances are that this solution will work very well.
Your suggestions and comments are welcome!