Do you have any question about this error?
Message type: E = Error
Message class: FEB_BSIMP - Electronic Bank Statement Messages
Message number: 071
Message text: Place holder
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.
FEB_BSIMP071
- Place holder The SAP error message FEB_BSIMP071 indicates that there is an issue with the usage of a placeholder in a financial document or transaction. Specifically, the message states that the placeholder
<COUNTER>
is only allowed with usage type 4. This typically relates to the configuration of financial documents in the SAP system, particularly in the context of the Financial Accounting (FI) module or the Bank Statement Processing (FEB) component.Cause:
- Incorrect Usage Type: The placeholder
<COUNTER>
is being used in a context where it is not permitted. This usually means that the placeholder is being used with a usage type other than 4, which is likely intended for a specific type of transaction or document.- Configuration Issues: There may be a misconfiguration in the bank statement processing settings or in the definition of the document types that are being processed.
- Data Entry Errors: There could be an error in the data entry or mapping of the bank statement that is causing the system to interpret the usage type incorrectly.
Solution:
- Check Usage Type: Review the configuration of the document types and ensure that the placeholder
<COUNTER>
is being used with the correct usage type (which should be 4). You may need to consult the documentation or configuration settings for the specific financial transaction you are working with.- Adjust Configuration: If the usage type is incorrect, you may need to adjust the configuration in the SAP system. This could involve changing the settings in the transaction codes related to bank statement processing (e.g., FEBAN, FEBP).
- Review Mapping: If you are importing bank statements, check the mapping of fields in the bank statement file to ensure that they align with the expected formats and placeholders in SAP.
- Consult Documentation: Refer to SAP documentation or help resources for more detailed information on the specific usage types and placeholders allowed in your version of SAP.
- Testing: After making changes, perform tests with sample data to ensure that the error does not recur and that the bank statement processing works as expected.
Related Information:
If the problem persists after following these steps, it may be beneficial to consult with an SAP expert or your organization's SAP support team for further assistance.
Get instant SAP help. Start your 7-day free trial now.
FEB_BSIMP070
Check failed. Costed: &1 &3. Delivered: &2 &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FEB_BSIMP069
Placeholder
What causes this issue? A usage other than <LS>Store Files (Append Counter to Existing File Names)</> is defined in Customizing.System Re...
FEB_BSIMP072
******
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FEB_BSIMP073
No persistence for bank statement &1 &2 &3
What causes this issue? The bank statement has not been downloaded to bank data storage nor stored in a transfer path.System Response The system iss...
Click on this link to search all SAP messages.