How To Fix FEB_BSIMP332 - Import has been started

SAP Error Message - Details

• Message type: E = Error

• Message class: FEB_BSIMP - Electronic Bank Statement Messages

• Message number: 332

• Message text: Import has been started

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message FEB_BSIMP332 - Import has been started ?

  The SAP error message FEB_BSIMP332, which states "Import has been started," typically occurs in the context of the Financial Accounting (FI) module, particularly when dealing with the Bank Statement Import process. This error indicates that an import process for bank statements has already been initiated, and the system does not allow a new import to start until the current one is completed or canceled.
  Cause:
  
  Concurrent Import Process: The most common cause of this error is that a bank statement import process is already running. This could happen if a user or a background job has initiated the import, and the system is still processing it.
  Locking Mechanism: SAP uses a locking mechanism to prevent multiple imports from being processed simultaneously, which can lead to data inconsistencies.
  
  Solution:
  
  
  Check Running Processes: 
  
  Go to transaction code SM37 to check for any running jobs related to bank statement imports. Look for jobs that are currently in the "active" state.
  If you find a job that is stuck or taking too long, you may need to investigate further or terminate it if necessary.
  
  
  
  Wait for Completion: If you find that an import is currently in progress, the simplest solution is to wait for it to complete. Once the current import process finishes, you should be able to start a new import.
  
  
  Cancel the Import: If the import process is stuck and you need to cancel it:
  
  You can use transaction code SM37 to find the job and cancel it if you have the necessary authorizations.
  
  
  
  Check for Errors: If the import process fails or is taking too long, check the logs for any errors that might indicate why the process is not completing. You can do this in transaction SLG1 (Application Log) or by checking the job log in SM37.
  
  
  System Restart: In rare cases, if the system is not responding correctly, a restart of the application server may be required, but this should be done with caution and typically involves coordination with your Basis team.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SM37: Job Monitoring
  SLG1: Application Log
  FEBAN: Bank Statement Processing
  
  
  Documentation: Review SAP documentation or notes related to bank statement processing for any specific configurations or known issues.
  User Authorizations: Ensure that you have the necessary authorizations to view and manage background jobs and imports.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.