Do you have any question about this error?
Message type: E = Error
Message class: 1P - BCA: Payment Transactions
Message number: 855
Message text: Entry for &1 &2 is missing in table BNKA
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
1P855
- Entry for &1 &2 is missing in table BNKA ?The SAP error message 1P855 indicates that there is a missing entry in the table BNKA for a specific bank account. This error typically occurs when the system is trying to access bank details that are not present in the database.
Cause:
The error can be caused by several factors, including:
- Missing Bank Master Data: The bank account you are trying to use has not been created in the system.
- Incorrect Bank Key or Account Number: The bank key or account number provided in the transaction does not match any entry in the BNKA table.
- Data Deletion: The bank account data may have been deleted or not properly maintained.
- Configuration Issues: There may be issues with the configuration of the bank master data in the system.
Solution:
To resolve the error, you can take the following steps:
Check Bank Master Data:
- Go to transaction code FI01 (Create Bank) or FI02 (Change Bank) to check if the bank account exists in the system.
- Ensure that the bank key and account number are correctly entered.
Create Missing Entry:
- If the bank account does not exist, create a new entry using transaction code FI01.
- Fill in all required fields, including the bank key, account number, and other relevant details.
Verify Data:
- Ensure that the bank key and account number you are using in your transaction match the entries in the BNKA table.
- You can check the BNKA table directly using transaction code SE16N or SE11.
Check for Deletions:
- If the bank account was recently deleted, you may need to recreate it or restore it if possible.
Consult Configuration:
- If you suspect configuration issues, consult with your SAP Basis or FI consultant to ensure that the bank master data configuration is correct.
Testing:
- After making the necessary changes, test the transaction again to see if the error persists.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP documentation for further troubleshooting.
Get instant SAP help. Start your 7-day free trial now.
1P853
Work Day Rule: input '&' not valid
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
1P852
Standing order &3 in bank area &1 for account &2 already deleted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
1P856
Bank &1 &2 in Table BNKA has a deletion flag
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
1P860
Transaction type &1 not used for Online Standing Orders
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.