How To Fix FEB_BSIMP095 - Source path &2 is currently being blocked by user &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FEB_BSIMP - Electronic Bank Statement Messages

• Message number: 095

• Message text: Source path &2 is currently being blocked by user &1

What causes this issue?

DEFINE &USER& = &V1&
INCLUDE MESSAGE_ENQUEUE_USER OBJECT DOKU ID TX

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?

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_BSIMP095 - Source path &2 is currently being blocked by user &1 ?

  The SAP error message FEB_BSIMP095 indicates that a source path is currently being blocked by a user. This typically occurs in the context of the SAP Financial Accounting (FI) module, particularly when dealing with bank statement processing or electronic bank statement imports.
  Cause:
  The error message is triggered when a user is trying to access or process a source path (such as a file or directory) that is already locked by another user. This locking mechanism is in place to prevent data inconsistencies and ensure that only one user can modify or process the data at a time.
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Identify the Blocking User: Check who is currently using the source path. This can often be done through transaction codes like SM12 (to view lock entries) or SM21 (to view system logs).
  
  
  Communicate with the User: If possible, contact the user who is blocking the source path and ask them to complete their task or release the lock.
  
  
  Wait for the Lock to be Released: If the blocking user is performing a long-running task, you may need to wait until they finish.
  
  
  Forcefully Release the Lock: If the blocking user is no longer active or you cannot reach them, you may need to forcefully release the lock. This can be done by a system administrator using transaction SM12. However, this should be done with caution, as it may lead to data inconsistencies.
  
  
  Check for Background Jobs: Sometimes, background jobs may also hold locks. Check transaction SM37 to see if there are any jobs running that might be causing the lock.
  
  
  Review Configuration: Ensure that the configuration for the bank statement processing is set up correctly and that there are no issues with the source path settings.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM12: To view and manage lock entries.
  SM21: To view system logs for any related issues.
  SM37: To check for background jobs that might be holding locks.
  
  
  
  Documentation: Refer to SAP Help documentation for more details on bank statement processing and handling locks.
  
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  
  
  By following these steps, you should be able to resolve the FEB_BSIMP095 error and continue with your bank statement processing tasks.