FI Bank Management

Prévia do material em texto

4/11/2024
1This is custom documentation. For more information, please visit the SAP Help Portal
Financial Accounting
Generated on: 2024-04-11 22:16:25 GMT+0000
Support Content | 1.0
PUBLIC
Original content: https://help.sap.com/docs/SUPPORT_CONTENT/�accounting?locale=en-
US&state=PRODUCTION&version=1.0
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re�ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the https://help.sap.com/docs/disclaimer.
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting?locale=en-US&state=PRODUCTION&version=1.0
https://help.sap.com/docs/disclaimer
4/11/2024
2This is custom documentation. For more information, please visit the SAP Help Portal
Banking Accounting
WELCOME TO THE BANKING ACCOUNTING EXPERT CONTENT PAGE
What is Banking Accounting?
This component is used to handle accounting transactions that you process with your bank.
It includes the management of bank master data, cash balance management (check and bill of exchange management), and the
creation and processing of incoming and outgoing payments. It is possible to freely de�ne all country-speci�c characteristics,
such as the speci�cations for manual and electronic payment procedures, payment forms, or data media.
Banking Accounting
General Documentation - Banking Accounting
Banking - Incomings (Bank Statement)
Banking - Master Records
FBCJ
Supportability Tools - Banking Accounting
Access SAP For Me Visit the SAP Community View Product Documentation
General Documentation - Banking Accounting
This section covers aspects of the Banking (BL) module, such as House Banks, Electronic Bank Statement (EBS), and Cash
Journal.
General Documentation - Banking Accounting
Banking - Incomings (Bank Statement)
Electronic Bank Statement
Interpretation Algorithm
How Interpretation Algorithms work
Search String
BELNR(XBLNR) number interval in program RFEBKA00
Deleting Electronic Bank Satement : RFEBKA96
Postprocessing transactions FEBA(N)/FEB_BSPROC
Error message F5 263
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881821.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878774.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878699.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3562425679.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880618.html
https://me.sap.com/
https://community.sap.com/
https://help.sap.com/docs/
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878774.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881808.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878693.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878775.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880535.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880368.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878760.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880461.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880560.html
4/11/2024
3This is custom documentation. For more information, please visit the SAP Help Portal
MT942 Upload - Error FV 151 ( Record 62F missing )
Automatic Clearing - deactivate
Posting on Account- deactivate
Manual Bank Statement
Banking - Master Records
Change Bank master data in FI02
House Banks
Con�guring House Bank Accounts for Payment transactions
How to maintain more than one language for the bank master data
Issue when adding new bank accounts in House Bank Determination
Bank chains
FBCJ
FBCJ - Printing customer receipt for REVENUE postings in cash journal.
Access SAP For Me Visit the SAP Community View Product Documentation
Banking - Incomings (Bank Statement)
This area contains information in relation to Banking Incoming processes.
Banking - Incomings (Bank Statement)
Electronic Bank Statement
Interpretation Algorithm
How Interpretation Algorithms work
Search String
BELNR(XBLNR) number interval in program RFEBKA00
Deleting Electronic Bank Satement : RFEBKA96
Postprocessing transactions FEBA(N)/FEB_BSPROC
Error message F5 263
MT942 Upload - Error FV 151 ( Record 62F missing )
Automatic Clearing - deactivate
Posting on Account- deactivate
Manual Bank Statement
Electronic Bank Statement
Electronic account statements are used to import bank statements.
The information in the account statement and customizing settings are used to generate the appropriate postings and the
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880570.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878559.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878703.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880180.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878699.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881934.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881185.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880809.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878505.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880708.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3564879506.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3562425679.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880891.html
https://me.sap.com/
https://community.sap.com/
https://help.sap.com/docs/
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881808.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878693.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878775.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880535.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880368.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878760.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880461.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880560.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880570.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878559.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878703.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880180.html
4/11/2024
4This is custom documentation. For more information, please visit the SAP Help Portal
program maps the actual bank transactions in the system.
Several bank statement formats SWIFT MT940, MultiCash, BAI, XML) are supported for this purpose.
Bank statements that could not be updated can be post-processed manually and posted (Transactions FEBA(N) or
FEB_BSPROC.
Electronic bank statement format
It is required to specify the format in which the bank statements are to be imported: M for MultiCash, S for SWIFT MT 940 or X
for XML.
 Standard XML formats are
camt052 Intraday MT942
camt053 End of Day MT940
camt054 Debit/Credit Noti�cation MT900/MT910
BOC Bank of China
In case of loading a bank statement in an XML format (for example, in the format camt053.001.02) or in a bank-speci�c format
into the SAP system, it would be necessary to de�ne XSL Transformation and BAdI implementation for each format in View
VFIEB_MAPP_XCTRL
Here is required to de�ne how a bank statement in XML format or in a bank-speci�c format is mapped to internal structures via
an XSL transformation or implementing method MAPP_BANK_STATEMENT of Business Add-In (BAdI) FIEB_MAPPING_X.
Uploading multiple�les 
In transaction FF.5 (program RFEBKA00), it is possible to upload only a single �le. 
In order to upload one or more �les from one or more directories on the customer’s �le system, transaction
FEB_FILE_HANDLING can be used. This transaction only supports uploads from application server.
Electronic Bank Reconciliation
The primary con�guration steps necessary to set up Electronic Bank Statements (EBS) Processing in SAP.
1. Create House Bank and Account ID (FI12)
2. Setup EDI Partner Pro�le for FINSTA Message Type (WE20)
3. Con�gure Global Settings for EBS (IMG) (or Use Transaction code OT83, to perform steps 4 - 10)
4. Create Account Symbols
5. Assign Accounts to Account Symbols
6. Create Keys for Posting Rules
7. De�ne Posting Rules
8. Create Transaction Types
9. Assign External Transaction Types to Posting Rules
10. Assign Bank Accounts to Transaction Types
Electronic Bank Statement
https://help.sap.com/docs/disclaimer
4/11/2024
5This is custom documentation. For more information, please visit the SAP Help Portal
Interpretation Algorithm
Search String
BELNR(XBLNR) number interval in program RFEBKA00
Deleting Electronic Bank Satement : RFEBKA96
Postprocessing transactions FEBA(N)/FEB_BSPROC
Error message F5 263
MT942 Upload - Error FV 151 ( Record 62F missing )
Automatic Clearing - deactivate
Posting on Account- deactivate
Related SAP Notes/KBAs: 
549277-FAQ: Electronic account statement 
124655 - Unsupported functions of the electronic bank statement
36833 - Multicash Format (auszug.txt and umsatz.txt)
2319064 - XSLT for camt052.001.02
1686264 - XML bank statement, for example, CAMT053.001.02
1729746 - XSLT for camt054.001.02
3152422 - CAMT054.001.008 transformation
2881354 - Transformation camt053.001.008
1769749 - New Bank Statement Import (FEB_FILE_HANDLING)
3271555 - Bank Statement Processing overview / how-to scenarios
Interpretation Algorithm
In Note to payee �elds there are contained several information of the electronic bank statement, relevant for clearing open
items.
As for instance, the Document number, Reference document number, Check number...
Via the interpretation algorithm it is possible to �nd payments in the bank statement, with the information in the note to payee
lines of the bank statement.
It is possible to �nd a complete list of interpretation algorithms available by SAP in Customizing of the Electronic Bank
Statement under Make Global Settings for Electronic Bank Statement and in SAP Note 114713.
For more information about each interpretation algorithm, check the SAP Help below:
http://help.sap.com/erp_fao_addon10/helpdata/en/4d/c5efb40c381c36e10000000a42189b/content.htm
If the standard algorithms provided by SAP do not meet your requirements, customer exits can be created using customer's
code however without any modi�cation of the standard system code.
How Interpretation Algorithms work
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878693.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880535.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880368.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878760.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880461.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880560.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880570.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878559.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878703.html
https://service.sap.com/sap/support/notes/549277
https://me.sap.com/notes/124655/E
https://service.sap.com/sap/support/notes/36833
https://service.sap.com/sap/support/notes/2319046
https://service.sap.com/sap/support/notes/1686264
https://service.sap.com/sap/support/notes/1729746
https://service.sap.com/sap/support/notes/3152422
https://service.sap.com/sap/support/notes/2881354
https://service.sap.com/sap/support/notes/1769749
https://launchpad.support.sap.com/#/notes/3271555
https://me.sap.com/notes/114713
http://help.sap.com/erp_fao_addon10/helpdata/en/4d/c5efb40c381c36e10000000a42189b/content.htm
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878775.html
4/11/2024
6This is custom documentation. For more information, please visit the SAP Help Portal
Related SAP Notes/KBAs:
114713 - New interpretation algorithms as of Rel. 3.0F
494777 - Customer enhancements in electronic bank statement
How Interpretation Algorithms work
General information
Lets take Algorithm 021, to check how algorithms work.
In this case it does works in the same way as algorithm 001, except that it interprets the contents of the note to payee �elds as
a reference document number only.
This means that the system should look for the document to be cleared according the the reference �eld or the document
number.
Please be in mind that this is necessary to select these ranges to make the interpretation algorithm working.
How does this algorithm work?
1.- It tries to �nd in the note to payee information, if there is any number in the document number range entered in the selection
screen.
2.- Once the system �nds all the possible Document Numbers, it tries to �nd the corresponding FI document by looking for it in
table BKPF. With this document number, it updates table FEBCL with the corresponding clearing information.
3.- If it is not possible to �nd such FI document number, then it updates the table FEBCL to clear the document by amount.
4.- Then the system tries to post the document using the clearing information from FEBCL (document number or amount,
depending on
 the above). Only in case, this posting fails, it posts the document on account. But �rst of all, it tries with the document number
or with the amount. 
 If desired, it is possible to change the customizing in order to change the behavior and not allow the system to post based on
the amount. In this case refer to the following link: 
 Automatic Clearing - deactivate
Also check the following points in order to �nd possible errors during the bank statement upload:
Range from[ ] to [ ] in BELNR/XBLNR and if the required document is included at it.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/114713
https://me.sap.com/notes/494777
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878559.html
4/11/2024
7This is custom documentation. For more information, please visit the SAP Help Portal
Review if there is user exits activated and check if the same is changing the interpretation.
Check what information was recorded at table FEBCL.
Search String
General information
You have created a search string. After uploading the bank statement �le, you notice that the target �eld (ex: posting
rule/interpretation algorithm) is not populated based on the search string created. 
Simulating the Search String
You can submit an existing bank statement to the string search in order to test the search (Transaction FEBSTS).
If the result is not in the simulation screen, then you should check table FEBRE via SE16. The search string uses the information
contained in FEBRE table, so it
will not work if the information to be located is not in the table.
If this is the case, please check if your bank is sending the note to payee in the correct �eld. 
Debugging the search string
In case the the info is in FEBRE table, then you should debug the search string process. Insert a breakpoing in the Function
Module BSPS_PATTERN_SEARCH.
Check the contents of HITS table in the following code:
https://help.sap.com/docs/disclaimer
4/11/2024
8This is custom documentation. For more information, please visit the SAP Help Portal
 
The system writes no value into the target �eld if there are several hits for a target �eld (exception: the note to payee target
�eld).
If this is the case, then you should review and correct the search string use in transaction OTPM.
Related SAP Notes/KBAs:
1901999- Delete leading zero by using Search String for Electronic Bank Statement
2741244 - Search string doesn't work after upgrade
494777 - Customer enhancements in electronic bank statement
 
BELNR(XBLNR) number interval in program RFEBKA00
Purpose:
Reason to �ll the parameters BELNR/XBLNR number interval (from and to) in the program RFEBKA00 (bank statement
upload)
 Overview:
When executing transaction FF_5 and select the program RFEBKA00 to upload the bank statement �le, there are 2 pairs of
parameter in the below part of the screen: 
 
Why it is necessary to �ll those parameters?
In order to parse the bank statement �le, one Interpretation algorithm must be assigned to each posting rule. For example,
“010 Standard algorithm ““020 Document number search” and “021 Reference document number search”. When uploading the
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/1901999
https://service.sap.com/sap/support/notes/2741244
https://service.sap.com/sap/support/notes/494777
4/11/2024
9This is custom documentation. For more information, please visit the SAP Help Portal
statement �le, system will search items base on the Interpretation algorithm for each posting area and do subsequent
operation. For example, clearing or reversal.
For example, if “020” is assigned, system will search Table BKPF base on �eld BKPF-BELNR and the entries which are found will
be inserted in to table FEBCL (interpretation). System will do subsequent operation for them after interpretation. During
interpretation following SQL statement will be executed:
Program RFEBBU10
……
 SELECT * FROM BKPF WHERE BUKRS = FEBKO-BUKRS
 AND BELNR = TREFFER-NUMMER.
How TREFFER-NUMMER is �lled?
1. System will parse all entries in note-to-payee information (table in FEBRE) and get internal table for all document
numbers
2. Then check if those numbers are in the range you �ll in parameter “BELNR number interval” (from and to), if not, this
number won’t be considered in the above SQL statement.
If �lling in parameters as below:
The entries in FEBRE are
1
1001
1002
20000
Then the last line item with value ʻ20000” won’t be considered and system won’t select BKPF base on it.
In addition, in order to improve the performance, we recommend to �ll the parameters with same length, for example, 1000 to
9999, 000001 to 999999
Related SAP Notes/KBAs:
3314910 - Bank statement import: No automatic clearing/difference too large for clearing (F5263)
2428443 - Electronic bank statement: Number range/interval in FF.5 / FF_5
Deleting Electronic Bank Satement : RFEBKA96
Functionality change: 
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/3314910
https://me.sap.com/notes/2428443/E
4/11/2024
10This is custom documentation. For more information, please visit the SAP Help Portal
As from SAP Note 3169942 on, in productive systems the deletion of bank statements via report RFEBKA96 is no longer
possible.
The note has been created based on legal requirements.
The program checks if something has been posted and only in this case the deletion is not allowed and error FV190 is issued 
Motivation: 
The intention is to decline bank statement deletion in production where postings have been executed, as in case of deletion of a
bank statement which has posted FI documents, there will have an inconsistency in customer's system.
The deletion of statements is possible for unprocessed bank statement items.
This means no FI documents and no updates in cash management.
The deletion is not allowed in the following case:
a) System role is ʻproduction’ and 
b) documents have already been posted or c) update in cash management has not been done.
The document posting check is done on FEBEP �elds:
BELNR
NBBLN
AK1BL 
AKBLN
B1DOC
B2DOC
Those �elds must be empty: BELNR and NBBLN can also have ʻ-ʻ instead of space.
Please check the mentioned FEBEP and FEBKO �elds. Use transaction SE16 and select the data with the short key(s).
If one of the mentioned �elds is �lled the deletion is not allowed and the program behavior is correct. This is a legal
requirement and it is not allowed to me to make the deletion possible.
Alternative to RFEBKA96: 
According to the advice from the Developers and SAP best practices, the recommendation is to archive statements instead of
deleting the same, to avoid inconsistencies in productive system.
Generally the archiving object FI_ELBANK should be used to remove bank statement data from the production system.
There is no other report,as per the standard, which substitutes RFEBKA96 to delete posted statements in production systems.
Postprocessing transactions FEBA(N)/FEB_BSPROC
Post processing of bank statements function is used to process bank statements that could not be posted by the system
automatically.
From SAP Enhancement Package 6 for SAP ERP 6.0 (EA-APPL 606), the business function FIN_BL_EB_1, Import and
Postprocessing of Electronic Bank Statement (New) can be activated via transaction SFW5. This provides the new functionality
in the FEBAN transaction also called FEB_BSPROC.
Once the BF is active the new postprocessing transaction will be called with transaction FEBA, FEBAN or FEB_BSPROC: All of
them will bring you to the "new" screen.
The single screen transaction for postprocessing bank statement items supports you with information and functions needed in
your day-to-day work to be able to post the open bank statement items in the system manually.
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/3169942
4/11/2024
11This is custom documentation. For more information, please visit the SAP Help Portal
The bene�ts of this transaction is the fast and efficient processing reducing manual steps and with a clearly arranged screen
with details on assigned amount, Note to Payee information, Clearing, Simulation and Posting views.
In case of requiring the control of transactions FEB_BSPROC, FEBAN or FEBA separately, to be able to check bank statement
from the different transactions and views, please check Knowledge Base Article (KBA) 1852491 explaining how to handle the
same.
As explained in the KBA, this can be controlled by the user parameter FIN_BSPROC_UI (System->User pro�le-> Own Data: TAB
'Parameters' with an entry 'Parameter ID') to set the default for post processing transaction per user. It is possible to use this
parameter with the values "FEB_BSPROC", "FEBAN" and "FEBA".
In case of setting this parameter with the value FEBAN, transaction FEBAN will be called with this transaction and in case new
postprocessing is required, it would be called via transaction FEB_BSPROC.
If this parameter is not maintained the new post processing will always be executed regardless of which transaction is used.
In the standard the parameter FIN_BSPROC_UI is not set.
Related SAP Notes/KBAs:
1852491 - Parameter FIN_BSPROC_UI
2378595 - FEB_BSPROC - �elds greyed out for input in Assignment tab
1866582 - FF67/FF68 document number updated with asterisk (*)
2003991 - FEB_BSPROC: Change the status of a posted statement
Error message F5 263
 
General Information
System tries to clear the invoices using the information which is stored in the bank statement �le (note to payee). If
the document cannot be located , you will get the error message F5263 in the posting log.
This error occurs as the bank statement programs (transactions FEBC, FF.5 and FF_5) call the transaction FB05 to perform the
clearing. Below the list of common issues that may cause this message error:
Document Search Range
Check whether the range for �eld BELNR was maintained. Check SAP KBA 1676001 for more details on how to maintain it.
Statement Date
 In case of check payment, the statement date must be earlier than the check date. You can see the statement date in the �rst
line of the statement �le.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/1852491
https://service.sap.com/sap/support/notes/1852491
https://launchpad.support.sap.com/#/notes/2378595https://launchpad.support.sap.com/#/notes/1866582
https://launchpad.support.sap.com/#/notes/2003991
https://service.sap.com/sap/support/notes/1676001
4/11/2024
12This is custom documentation. For more information, please visit the SAP Help Portal
Missing information in the note to Payee
Basically, when you import a bank statement �le, the system stores the information contained in the note to payee section
(position depends on the format) in
the table FEBRE. This information will be used by the interpreation algorithm in order to �nd the correct invoice. If not available
in FEBRE, the algorithm will
not work.
 
This can be checked by going to transaction SE16 and checking the contents of FEBRE table using the short key (KUKEY �eld).
The short key can be seen in the statement log or via table FEBKO, using statement Date and bank information.
Tolerances and Payment differences
Another workaround to avoid this error is post processing the statement in FEBA transaction in case of cash discount may
causing this, or de�ne permitted differences during the process.
 Go to post processing using FEBA transaction. Before selecting the SAVE button please choose "Speci�cations ->
Change method". Here you should select the option "A - Display all screens". On saving the document the system
will show you the screen with all the �elds available for changes. You can delete the cash discount amount and
continue the process of the statement.
De�ne a permitted payment difference. In transactions OBA3 and OBA4 you de�ne a tolerance group for
permitted payment difference and the G/L account to post this differences. De�ne an account for payment
difference in the following IMG path:
Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions ->
Outgoing Payments -> Outgoing Payments Global Settings -> De�ne Accounts for
Overpayments/Underpayments
Clearing Information
 You can check FEBCL in order to verify the clearing information. The �eld FEBCL-SELFD should contain the �eld name ('BELNR'
or 'XBLNR') in case it has been interpreted correctly. In addition, the �eld FEBCL-SELVON should contain the document number
or reference depending on the interpretation.
If no entries in the table FEBCL are available, no automatic clearing can take place. This means that the interpreation algorithm
was not able to �nd the correct
document.
https://help.sap.com/docs/disclaimer
4/11/2024
13This is custom documentation. For more information, please visit the SAP Help Portal
Interpretation Algorithm
In order to �nd out why the interpretation algorithm was not able to locate the open item , you should �rst identify whicht
algorithm you are using and how it works.
Algorithm used can be found via SE16 checking table FEBEP, �eld INTAG.
For more information about each interpretation algorithm, check the SAP Help below:
http://help.sap.com/erp_fao_addon10/helpdata/en/4d/c5efb40c381c36e10000000a42189b/content.htm
In case you need to debug the interpretation process in a TEST system, set a breakpoint in program RFEBBU10:
 
Program RFEBBU10 or include BBU10_F01
....
CASE FEBEP-INTAG. <<<<<<< Set breakpoint
 WHEN '000'.
* do nothing
 WHEN '001'.
* Standardalgo: Führt Suche nach BELNR bzw. XBLNR aus,
* wenn BELNR bzw. XBLNR Range nicht initial ist.
 IF NOT FILTER IS INITIAL.
 PERFORM ANALYSE_VERWENDUNGSZWECK USING 'BELNR'.
 ENDIF.
 IF NOT TFILTER IS INITIAL.
 PERFORM ANALYSE_VERWENDUNGSZWECK USING 'XBLNR'.
 ENDIF.
Related SAP Notes/KBAs:
3314910 - Bank statement import: No automatic clearing/difference too large for clearing (F5263)
https://help.sap.com/docs/disclaimer
http://help.sap.com/erp_fao_addon10/helpdata/en/4d/c5efb40c381c36e10000000a42189b/content.htm
https://me.sap.com/notes/3314910
4/11/2024
14This is custom documentation. For more information, please visit the SAP Help Portal
MT942 Upload - Error FV 151 ( Record 62F missing )
Purpose
The purpose of this content is to provide some guidance and possible system logic about error FV151.
Overview
As you know the reason for the error message lies in the �le. One completed MT942 bank statement or a completed end node
of a statement must end with a row with a hyphen "-".
When does the issue appear
Uploading bank statement �le '�le format MT942' in FF.5 ( Program RFEBKA00 ) you receive the following error
message: "Termination in statement no. xxxx of acct xxxxxxx; closing record 62F missing". ( FV 151 )
Solution:
Some banks don't deliver this hyphen, which is incorrect. You need to add the hyphen there, you can do it manually or via
enhancement. 
This is only an example of the �le ( MT942 can have another segments not mentioned in the image below ) :
P.S. Remember that for MT942 the format S and the �ag "Account Balance" must be selected. It's shown in the image below:
https://help.sap.com/docs/disclaimer
4/11/2024
15This is custom documentation. For more information, please visit the SAP Help Portal
Automatic Clearing - deactivate
General information
When the logic of the interpretation algorithm fails to �nd an open item, the system will try to �nd one based on the amount
(WRBTR). if the open item is found, the system will perform a posting based on the amount.
For some scenarios, this is undesirable and may lead to some issues.
How to deactivated the automatic clearing?
In order to deactivated the behavior call transaction OT83, choose 'Assign Bank Accounts to Transaction Types' and select �ag
"No Automatic Clearing".
F1 Help of the �eld states the following:
"No Automatic Clearing
If you select this �eld, when the amount is the only selection criteria for clearing an open item, no automatic clearing takes
place."
Related SAP Notes/KBAs:
2885488 - Clearing via amount does not work or returns surprising results
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/2885488
4/11/2024
16This is custom documentation. For more information, please visit the SAP Help Portal
Posting on Account- deactivate
General information
Business requires that posting on account does not occurs during the bank statement postings.
How to deactivate posting on account?
In order to deactivated the behavior please, refer to SAP notes 162568 and 452579.
According to note 162568, posting on account can only be suppressed if the payment advice note is removed from the posting.
Therefore, the solution for not posting in account is to remove payment advice creation via note 452579.
Related SAP Notes/KBAs:
162568 - Advice notes + subs. processing elect. bank statement
452579 - Suppressing generation of payment advice notes in bank statements
1910415 - Suppression of payment advices in the bank statement
Manual Bank Statement
Manual Bank Statement allows the user to manually enter bank account statements received.
This entry is usually a two-step process:
1) Enter the account line items in the system. 
2) Post the line items you have entered.
Entering bank statements manually allows to create up to two postings (Posting Areas) for each line item : Bank account
posting and subledger posting.
Customizing steps: 
Step 1 - De�ne Posting Keys and Posting Rules for Manual Bank Statement : de�ne all the posting rules required for bank
statement entry, including a key for each rule.
 The key determines the posting rules for general ledger and subledger accounting. 
Step 2 - Create and Assign Business Transactions (BT) : Enter an indicator for each business transaction and link a posting rule
to each business transaction. Several business transactions usually refer to the same posting rule.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/162568/E
https://me.sap.com/notes/452579/E
https://me.sap.com/notes/162568/E
https://me.sap.com/notes/452579/E
https://me.sap.com/notes/162568/E
https://me.sap.com/notes/452579/E
https://me.sap.com/notes/1910415/E4/11/2024
17This is custom documentation. For more information, please visit the SAP Help Portal
Step 3 - De�ne Variants for Manual Bank Statement : create separate account assignment variants for the manual bank
statement in order to adapt the selection of account assignment �elds to company-speci�c requirements.
Related SAP Notes/KBAs:
1866582 - FF67/FF68 document number updated with asterisk (*)
2937410 - FF67: Interpretation with KIDNO without warning FV094
3024469 - FF68/FF67 authorization check
3336916 - FF67: Sortierreihenfolge in der Übersicht 
Banking - Master Records
This area contains information related to Bank Master.
In ERP SAPGUI transactions FI01, FI02, FI03, FI06 (Create, change, display, set deletion �ag) are used to create a Bank key
manually.
In SAP S/4 Hana instead, Fiori app Manage Banks Basic is used for this purpose.
Additional information related this topic in : https://blogs.sap.com/2020/03/05/bank-account-management-in-sap-s-4hana/
Banking - Master Records
Change Bank master data in FI02
House Banks
Con�guring House Bank Accounts for Payment transactions
How to maintain more than one language for the bank master data
Issue when adding new bank accounts in House Bank Determination
Bank chains
Change Bank master data in FI02
Purpose
You use FI02 to change bank master data. You are unclear which �elds will have 'change history'. 
Overview
The change history can be found by clicking the button of "Change Documents" , or use program RFBKABL0 when you want to
see multiple banks change record in the same time.
The change history only displays the changes made to �elds of BNKA table. (the screen of 'Banks: Details')
If you go to further address screen by clicking 'Address F7' to make change, it will not be displayed in the change history.
Because this screen address is stored in BAS (Business Address Management, table ADRC and etc), but the change
history report doesn't read these tables.
Related SAP Notes/KBAs
SAP Note 1590785 Accessibility: change document for bank master data
House Banks
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/1866582
https://me.sap.com/notes/2937410/E
https://me.sap.com/notes/3024469/E
https://me.sap.com/notes/3336916/E
https://blogs.sap.com/2020/03/05/bank-account-management-in-sap-s-4hana/
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881934.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881185.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880809.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878505.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880708.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3564879506.html
https://launchpad.support.sap.com/#/notes/1590785
4/11/2024
18This is custom documentation. For more information, please visit the SAP Help Portal
In Bank Accounting we will have a House Bank. This House Bank is nothing but an identi�er that we have a transaction with that
particular Bank. And under this House Bank we have Bank Accounts/ Account ID's.
Each house bank of a company code is represented by a bank ID in the SAP system, every account at a house bank by an
account ID.
In the SAP system, you use the bank ID and the account ID to specify bank details. These speci�cations are used, for example,
for automatic payment transactions to determine the bank details for payment
These Account ID nothing but the couple of Bank Accounts we have with Bank for different uses like Current Account, Cheque
Deposit Account, Cheque Issue Account, etc.
Con�guring House Bank Accounts for Payment transactions
Purpose
Con�guration of the bank account for payment transactions.
Overview
Con�guration of bank accounts for payment transactions is an important step. This is to ensure that for each house bank and
payment method (and currency, if required), you specify which bank account is to be used for payments. Bank subaccounts are
used to post incoming and outgoing payments (accounts for outgoing checks, outgoing bank transfers, incoming checks, and
bank collection). 
Con�guration
https://help.sap.com/docs/disclaimer
4/11/2024
19This is custom documentation. For more information, please visit the SAP Help Portal
Step 1: In SPRO, you have to navigate as shown below 
 
Or you can use Transaction FBZP directly instead and select the option “Bank Determination”.
https://help.sap.com/docs/disclaimer
4/11/2024
20This is custom documentation. For more information, please visit the SAP Help Portal
 
Step 2:
1) Select the appropriate company code and then de�ne the ranking order for the same as shown below by selecting the
“ranking order” option on the left side (double click).
https://help.sap.com/docs/disclaimer
4/11/2024
21This is custom documentation. For more information, please visit the SAP Help Portal
2) De�ne Ranking order of the House Bank for the particular payment method as shown in example below 
The ranking order sequence number controls the order in which the payment program checks the house banks to determine
whether payment can be made from a particular bank.
Step 3:
Here in this step for each house bank and payment method (and currency, if required), you specify which bank account is to be
used for payments. 
https://help.sap.com/docs/disclaimer
4/11/2024
22This is custom documentation. For more information, please visit the SAP Help Portal
How to con�gure multiple accounts in the same House Bank for the speci�ed
Payment Method and Currency
When you try to con�gure multiple accounts in the same House Bank for the speci�ed Payment method & Currency, you get an
error mentioned below.
“An entry already exists with the same key - Message no. SV009”
Please see the example below: 
 
https://help.sap.com/docs/disclaimer
4/11/2024
23This is custom documentation. For more information, please visit the SAP Help Portal
This is the standard behaviour. For the same House Bank, payment method and currency you can only assign a unique Bank
Account. It is not possible to assign several bank accounts.
Bank account selection is based on the table T042I which has the following key �elds that “should be unique”:
ZBUKR - Paying company code
HBKID - Short key for a house bank
ZLSCH - Payment method
WAERS - Currency Key
The �eld 'Account ID' is not a key �eld since con�guration of F110 must be done for selection of payment methods. From sight of
SAP its makes no sense to de�ne more than one account for the same house bank and for the same payment method since, 
1. The payment program checks the payment methods in the order, given in parameters of transaction F110. 
2. The �rst house bank and its bank clearing account will be used, which is de�ned for the payment method and the currency,
and matches the further checks.
3. The ranking order is the sort order for this checking.
So, only one entry can be created which have these �elds with the same values. As �elds "Bank", "payment method" and
"currency", form a key all together. So in such cases please ensure the three criteria’s are different in order for you to create a
new one.
Also as an alternative you can de�ne the same house bank twice (with another identi�er) and use it like a separate house
bank. 
https://help.sap.com/docs/disclaimer
4/11/2024
24This is custom documentation. For more information, please visit the SAP Help Portal
New Functionality of Enhanced Bank Accounts: 
Please review the note "1640111 - F110: Selection of bank subaccount for RE items" where in new functionality is added. With this
note, you can assign several house bank accounts to a house bank for each payment method and currency. The selection of the
house bank account and, with it, the assigned bank subaccounts is made in each case for a combination of payment method and
currency in succession in the existing table of bank accounts and in the new table of the enhanced bank selection. In thisnew
table, a house bank account that may be speci�ed is also taken into account.
Payment program loops over the house banks (t042a) and is then looking up this in t042i or t042iy. The only difference to
t042iy is that you can de�ne multiple entries for one house bank by specifying different accounts (HKTID). The order in which
those entries are processed is de�ned only for the house banks (t042a). The order in t042iy is not relevant. So I think you need
to extend the house bank de�nition to do what you want (T042A). Finally the amounts are checked (t042d) and if an entry is
found this is checked. If no entry is found the whole process is done once again for the next house bank entry.
 
Related SAP Notes/KBAs
2004041 - F110: error FZ659
How to maintain more than one language for the bank master data
Overview
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/2004041/E
4/11/2024
25This is custom documentation. For more information, please visit the SAP Help Portal
You have maintained the bank master data in English, then you logon to the system in other language to check the bank master
data, English is displayed and you can not maintain other language
Reason
The bank master data are stored in table BNKA, in this table there is no there is no language �eld at all. Because of this fact, all
banks should be maintain in English only which is common practice worldwide for international bank transfers. 
Workaround
If you really need two languages, you can choose to maintain both languages in one �eld separated by e.g. '/'. This way the user
can see both texts regardless of logon language.
Issue when adding new bank accounts in House Bank Determination
Purpose
The purpose of this content is to provide some guidance and system logic about the error Message SV009 (An entry already
exists with the same key) in House Bank Determination for F110.
Overview
This error occurs when you are adding new bank accounts for the same house bank in the transaction FBZP ( customizing of the
payment program ).
Process
You can �nd the customizing through Transaction F110 -> Maintain con�g.
https://help.sap.com/docs/disclaimer
4/11/2024
26This is custom documentation. For more information, please visit the SAP Help Portal
Then you can see the FBZP transaction.
Alternatively, you can put FBZP on the command �eld and SAP will show you the following screen.
"Bank determination".
https://help.sap.com/docs/disclaimer
4/11/2024
27This is custom documentation. For more information, please visit the SAP Help Portal
 
Here you should select the "Paying company code" where you want to de�ne the new bank account.
 
Selecting "Bank Accounts" you'll receive this screen showing you the current accounts you have de�ned. Here you have to click
on "New Entries" to add a new account.
 Pay attention to the key �elds ( highlighted in red ).
https://help.sap.com/docs/disclaimer
4/11/2024
28This is custom documentation. For more information, please visit the SAP Help Portal
If you try to de�ne a new bank account using the same key �elds you'll see the error message SV009.
https://help.sap.com/docs/disclaimer
4/11/2024
29This is custom documentation. For more information, please visit the SAP Help Portal
Solution
The reason for message SV009, "An entry already exists with the same key", is that a key is formed by the combination of three
�elds:
"House Bank"
"Payment Method"
https://help.sap.com/docs/disclaimer
4/11/2024
30This is custom documentation. For more information, please visit the SAP Help Portal
"Currency".
See key �elds for the table T042I for F110 ( Screenshot below ).
 
For this reason, the SAP program is displaying message SV009. The system is, therefore, working correctly.
As a workaround for this issue, we'd recommend you to create adittional house banks or check with your local SAP consultant
about the possibility of using BTE 00001810 to achieveyour business requirements by changing the bank determination
standard logic.
OBS: F111 uses table T042Y. In this table the key entries include the Account ID. Here you can use the "House Bank", "Payment
Method" and "Currency" with differenct account Id's.
 
Bank chains
Bank chains are used to make payment via more than one bank, for example via the correspondence banks of the house bank,
the recipient bank or the intermediary banks. 
These are de�ned as intermediary banks and used for payment transfer in case that money does not required to be sent
directly from own house bank to payee’s bank (vendor bank details) and instead intermediary bank is required be used. The
motivation of this process is to reduce transfer costs.
https://help.sap.com/docs/disclaimer
4/11/2024
31This is custom documentation. For more information, please visit the SAP Help Portal
Usually only 1 intermediary bank is de�ned however there can de�ned up to three banks chains between the receiver bank (e.g.
vendor) and sending bank (e.g. house bank).
There are partner-speci�c bank chains and general bank chains. 
Partner speci�c bank chains belong to master data and transaction FIBPU is used for vendors and customers or
transaction BP. They have higher priority than general bank chains.
Database tables are TBCHAIN21 and TBCHAIN2.
General bank chains are customizing data and transaction FIBB is used for the maintenance.
Database tables are TBCHAIN0 and TBCHAIN1
Bank chains functionality is used only in case it is activated in transaction FIBD. 
Related SAP Notes/KBAs
2616557 Determination of bank chains 
2749570 RFZALI20 and bank chains 
2738698 Bank chains: determination of intermediary banks with unexpected results 
FBCJ
Financials cash Journal (transaction FBCJ) is a kind of subsidiary ledger or operational system for Financial Accounting, used for
managing liquid funds. We consider liquid funds to include the following: coins, bank notes and checks.
You can use cash journal independently of other posting transactions. Each cash journal is managed in one currency. In a two-
step procedure, entries (documents) are saved �rst in the cash journal before they are transferred to Financial Accounting.
After this transfer, the cash journal posting corresponds to the FI documents.
Customizing: 
Create G/L Account for Cash Journal
The G/L account to be used as Cash Journal account requires the following characteristics:
Zero balance account.
It is dedicated exclusively to the Cash Journal.
Do not set only balances in local currency" indicator (XSALH).
"Post automatically only" (XINTB) indicator: This prevents postings carried out manually in FI in order to avoid inconsistencies
between FI and Cash Journal.
Number range
Transaction: FBCJC1
Number range object: CAJO_DOC2
Enter a number range for each company code for document numbering in the Cash Journal. The only number range interval that
can be used is number 01.
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/2616557
https://launchpad.support.sap.com/#/notes/2749570
https://launchpad.support.sap.com/#/notes/2738698
4/11/2024
32This is custom documentation. For more information, please visit the SAP Help Portal
The de�nition of only one number range interval at the Company Code level enables all Cash Journals in the Company Code to
share this number range interval. As a result, it may appear that there are gaps in the numbering in a speci�c Cash Journal,
however the number are actually being used in another journal.
 
Example:
Cash journal 1: Document 1, Document 2, Document 4
Cash journal 2: Document3, Document 5, Document 6, Document 7,…
The �eld name of the �eld for the document numbers from the number range is POSTING_NUMBER (internal document
number) in the tables of Cash Journal documents. This �eld is always a key �eld .
For each Cash Journal there is also a consecutive numbering per journal. This number is stored in TCJ_DOCUMENTS-
D_POSTING_NUMB (document number).
If a numberrange with external number assignment is entered for a document type entered in transaction FBCJC0, then the
number of this number range interval has to be 01. Then the system assigns the Cash Journal document number
(POSTING_NUMBER) as an external number for the FI follow-on documents.
As of Release 600, SAP Note 1527787 provides the option to de�ne additional different number ranges for expenses, cash
receipts, and check receipts.
The existing �eld TCJ_DOCUMENTS-D_POSTING_NUMB is used for this numbering.
Error F5A244 Document save was unsuccessful; try again
This error is linked to the object number range, which it is not year dependant. It is to say, that with the new year the number
range will not be resetting, but the following document number will be used. Therefore, to �nd the last number, you just check in
table TCJ_DOCUMENTS the highest document number regardless the year.
 In the number range status the last number assigned + 1 should be updated, in the object range for Cash Journal CAJO_DOC2
using transaction SNRO.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/1527787/E
4/11/2024
33This is custom documentation. For more information, please visit the SAP Help Portal
Please, update your number range with the right current number and this error should not happen again.
As note 1326610 mentions, please check the settings in transactions FBCJC5 and FBCJC6:
"..
1. Required customizing
 o Create numbering groups for cash payment and cash receipt documents with transaction FBCJC5
 
o De�ne number ranges for numbering groups with transaction FBCJC6, you must use value 01 as the number range interval
for the number range objects
o De�ne numbering groups for cash payment and cash receipt documents with transaction FBCJC0
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/1326610/E
4/11/2024
34This is custom documentation. For more information, please visit the SAP Help Portal
Multiple users working in same Cash Journal:
Please be informed that it is not possible that more than one user at the same time working in change mode in the same cash
journal.
Since the implementation of note 506421 ( FBCJ: Display mode for FI cash journal -with block-) from release 4.6C on, it is
possible that an employee may be working at a cash desk and another employee needs to work in the same cash journal,
however just in display mode. 
In this situation, the system automatically gives read-only access to the second user: the same is locked for further changes and
the cash journal is accessible just in display mode. This ensures to avoid possible inconsistencies. 
Please, also refer to attached SAP note 532888 where it is mentioned the additional functions available in Cash Journal
transaction: 
 
"• Display mode
 On the one hand, an employee may be working at a cash desk and another employee wants to look at the sales. This is
now possible: In this situation, the system automatically gives read-only access to the second user.
On the other hand, a cash desk may be locked in Customizing (also a new function) but should still be accessible in read mode
(for example, for audit or reconciliation purposes)..."
Balance: 
Open and closing balance difference
Introduction
We should make a difference between the Cash journal balance (individual balance of each Cash Journal) and G/L account
balance ( in this case, balance of posted documents of all the cash journals in the same company code linked to the same G/L
account).
The system always displays the Cash Journal Balance that actually exists from both, Saved and Posted cash journal documents.
The reason is that when the cash journal document has been saved then it is a real document created in Cash journal. Therefore
in the same way, the document number in the cash journal has been created, the balance is updated accordingly in order not to
have inconsistent data.
When a document is saved, the actual document is generated and stored in the cash journal tables TCJ_DOCUMENTS and
TCJ_POSITIONS.
Then the BALANCE of the cash journal is updated in TCJ_BALANCE.
But just the balance of Cash journal is updated and not G/L balance in FI (transaction FS10N).
Therefore, although a saved document is a real document in cash journal, with an Internal document number
(POSTING_NUMBER), the same is not a real FI document, as it has not been posted yet.
Once the same is posted it could be displayed as a follow-on document in FI and balance will also be updated in pure FI.
Error in the balance table
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/506421/E
https://me.sap.com/notes/532888/E
4/11/2024
35This is custom documentation. For more information, please visit the SAP Help Portal
If the closing balance does not correspond with the opening balance of the display period that directly follows, then there is an
incorrect entry in the balance table.
As explained in SAP note 1309577 please, execute report RFCJ1 for the cash journal to remove this entry.
No source code corrections are required for the reset.
After successful execution of the program, the performance of the cash journal may deteriorate temporarily depending on how
many documents have
already been posted.
The program deletes the balance table, however, no information is lost.
Please read notes 377853 and 1883826 for further information.
FBCJ - Printing customer receipt for REVENUE postings in cash journal.
Related SAP Notes/ KBA
546365 - FAQ: Cash journal
532888 - FBCJ: Functions in cash journal
1479678 - FBCJ: Posting down payments 
616804 - FBCJ: BAPI for saving cash journal documents
1309577 - FBCJ: Incorrect balance in cash journal – report RFCJ1
377853 - FBCJ: Opening and closing balance
1883826 - FBCJ: Composite SAP Note for balance problems in cash journal
FBCJ - Printing customer receipt for REVENUE postings in cash journal.
Purpose
This content explains how to print cash receipts for REVENUE postings done via FBCJ.
Overview
In FBCJ transaction a customer receipt, of a regular invoice - transaction type D works �ne but if you post cash sales - revenue
transaction and one MUST print out receipt for the customer, this is not possible as customer �eld is not available for input. In
scenarios like a cash sale over counters as in case of hospitals which does not involve any receivables, users do not want to
carry customer postings instead want to do Revenue postings only which is relevant to this scenario.
FBCJ - Revenue Postings
Customer posts revenue postings - so the posting in FI is on a G/L account and is not an open item on customer account. If user
wants to enter some name so as to print receipt, then user should use the text �eld Recpt recipient - the name, entered here,
will be printed on the receipt. It is not possible to enter a customer account number in �eld Customer for a revenue posting.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/1309577/E
https://me.sap.com/notes/377853/E
https://me.sap.com/notes/1883826
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880891.html
https://me.sap.com/notes/546365/E
https://me.sap.com/notes/532888/E
https://me.sap.com/notes/1479678
https://me.sap.com/notes/616804/E
https://me.sap.com/notes/1309577/E
https://me.sap.com/notes/377853/E
https://me.sap.com/notes/1883826
4/11/2024
36This is custom documentation. For more information, please visit the SAP Help Portal
So you can enter the Customer name in Recpt Recipient �eld to ful�ll the above business requirement.
Then you can take a print as below
https://help.sap.com/docs/disclaimer
4/11/2024
37This is custom documentation. For more information, please visit the SAP Help Portal
Supportability Tools - Banking Accounting
Tool/App 
Name
Purpose/Bene�t/Objective Documentation Tool/App 
Location 
Category
FEBSTS Search String Simulation. Used to identify
the search string results for a posted bank
statement
Available In
 R/3
Simulation/Analysis
ANST
Automated
Note SearchTool
Replicate a transaction or program and get a
trace with all the ABAP objects
used/executed during the replication. Once
the trace is generated, you have the options
to:
1) Search for SAP Notes.
2) Problematic Custom Coding.
3) Missing Customizing Entries.
4) List of ABAP objects to start debugging.
Note 1818192. Available as of
release 740 SAP Basis Component
and included in Support Package in
releases 700, 701, 702, 731
PANKS A new button has been added to the
Performance Assistant in order to enable
context sensitive SAP Notes and KBAs
search.
Note 2096401. Released with note
2020356 and included in Support
Package in releases 700, 701, 702,
710, 711, 730, 731, 740 of SAP Basis
Component.
Debugging
with a
shortcut
Can´t enter /h at a pop up. 'Generate a
Short Cut' , (Type: 'System Command',
Command: '/h', Location 'Desktop'). Drag
and drop the icon from your desktop to the
pop up.
Available In R/3
RKSE16N_CD When entries in tables are changed using
SE16N, the system writes change
documents. Report RKSE16N_CD helps to
Available In R/3
https://help.sap.com/docs/disclaimer
4/11/2024
38This is custom documentation. For more information, please visit the SAP Help Portal
know if some entry was manually changed in
a table.
SE91 Where used list for a message number helps
to display the "suspicious" code to start 
root cause analysis when debugging isn´t
possible.
Available In R/3
[PAT03] This table contents the date when a system
was upgraded to some support package.
SE16, table PAT03, enter SAPKH* for �eld
'PATCH', execute, display �eld
'IMPLE_DATE'.
Available In R/3
How we
search
[VIDEO]
Best search strategy for notes and KBAs KBA 2172375
Access SAP For Me Visit the SAP Community View Product Documentation
https://help.sap.com/docs/disclaimer
https://me.sap.com/
https://community.sap.com/
https://help.sap.com/docs/