How To Fix FDC_POSTING_001055 - Bank statement item & locked by &

SAP Error Message - Details

• Message type: E = Error

• Message class: FDC_POSTING_001 - FI Postings

• Message number: 055

• Message text: Bank statement item & locked by &

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 FDC_POSTING_001055 - Bank statement item & locked by & ?

  The SAP error message FDC_POSTING_001055 indicates that a bank statement item is locked by another user or process, preventing the current user from processing or posting the bank statement item. This can occur in various scenarios, such as during bank reconciliation or when trying to post transactions related to bank statements.
  Cause:
  
  Concurrent Access: Another user is currently processing the same bank statement item.
  Incomplete Processing: A previous transaction involving the bank statement item was not completed, leaving it in a locked state.
  System Lock: The system may have a temporary lock due to a background job or a transaction that is still running.
  
  Solution:
  
  
  Check for Locks: 
  
  Use transaction code SM12 to check for locks on the bank statement item. You can filter by the user or the object type to identify who is holding the lock.
  If you find a lock that is no longer needed, you can delete it (if you have the necessary authorizations).
  
  
  
  Wait and Retry: If another user is processing the item, you may need to wait until they complete their transaction and then try again.
  
  
  Review Background Jobs: Check if there are any background jobs that might be processing the bank statement. You can use transaction code SM37 to monitor background jobs.
  
  
  Consult with Colleagues: If you are in a multi-user environment, communicate with your colleagues to see if someone else is working on the same bank statement.
  
  
  System Administrator: If the issue persists and you cannot identify the cause, contact your SAP system administrator for assistance. They may need to investigate further or release locks that are no longer valid.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM12: To view and manage locks.
  SM37: To monitor background jobs.
  FEBA: To process bank statements.
  
  
  
  Documentation: Refer to SAP Help documentation for more details on bank statement processing and handling locks.
  
  
  User Authorizations: Ensure that you have the necessary authorizations to view and manage locks in the system.
  
  
  By following these steps, you should be able to resolve the error and continue with your bank statement processing.