How To Fix FEB_BSIMP073 - No persistence for bank statement &1 &2 &3

SAP Error Message - Details

• Message type: E = Error

• Message class: FEB_BSIMP - Electronic Bank Statement Messages

• Message number: 073

• Message text: 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 issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

If you want the bank statement to be downloaded to bank data storage and
processed further, you have to process Customizing activities
<DS:SIMG.SIMG_CFMENUORFBFI12>Define House Banks</> and
<DS:SIMG.FIBL_FEBVC_IMP_POST>Define Posting Parameters</>.
If you want the bank statement to be stored in a transfer path, you have
to carry out Customizing activity <DS:SIMG.FIBL_FEBVC_IMP_TRANSFER>
Define Transfer Information</>.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FEB_BSIMP073 - No persistence for bank statement &1 &2 &3 ?

  The SAP error message FEB_BSIMP073 indicates that there is no persistence for the bank statement in question. This typically occurs during the processing of bank statements in the Financial Accounting (FI) module, particularly when using the Bank Statement Interface (BSI) or Electronic Bank Statement (EBS) functionality.
  Cause:
  The error can be caused by several factors, including:
  
  Missing Configuration: The system may not be properly configured to handle the bank statement for the specified bank account or company code.
  Data Issues: The bank statement data may not be correctly formatted or may be missing required information.
  Technical Issues: There may be issues with the underlying database or application logic that prevent the persistence of the bank statement.
  Incorrect Bank Account: The bank account specified in the statement may not exist in the system or may not be set up correctly.
  Authorization Issues: The user may not have the necessary authorizations to process the bank statement.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Configuration:
  
  Ensure that the bank account is correctly configured in the system.
  Verify that the necessary settings for the Electronic Bank Statement are in place (e.g., transaction codes, formats, etc.).
  
  
  
  Validate Bank Statement Data:
  
  Review the bank statement file for any formatting issues or missing data.
  Ensure that the statement contains all required fields and that the data is valid.
  
  
  
  Review Logs and Messages:
  
  Check the application logs (transaction SLG1) for any additional error messages or warnings that may provide more context.
  Look for any related messages that could indicate what went wrong during the processing.
  
  
  
  Check User Authorizations:
  
  Ensure that the user processing the bank statement has the necessary authorizations to perform the action.
  
  
  
  Technical Support:
  
  If the issue persists, consider reaching out to your SAP Basis or technical support team to investigate any underlying technical issues with the database or application.
  
  
  
  Testing:
  
  If changes are made to the configuration or data, test the processing of the bank statement again to ensure that the issue is resolved.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FF67 (for manual bank statement processing) and FEBAN (for electronic bank statement processing).
  Documentation: Refer to SAP Help documentation for Electronic Bank Statement configuration and processing guidelines.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide patches related to this error message.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.