How To Fix FDC_POSTING_001090 - Bank statement item already in process. Refresh list and try again.

SAP Error Message - Details

• Message type: E = Error

• Message class: FDC_POSTING_001 - FI Postings

• Message number: 090

• Message text: Bank statement item already in process. Refresh list and try again.

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_001090 - Bank statement item already in process. Refresh list and try again. ?

  The SAP error message FDC_POSTING_001090 indicates that a bank statement item is already being processed, which prevents further actions on that specific item. This typically occurs in the context of bank statement processing in SAP, particularly when using the Electronic Bank Statement (EBS) functionality.
  Cause:
  
  Concurrent Processing: The bank statement item is currently being processed by another user or session. This can happen if multiple users are trying to process the same bank statement simultaneously.
  System Lock: The item may be locked due to a previous transaction that has not yet been completed or has encountered an error.
  Background Jobs: If there are background jobs running that are processing bank statements, they may have locked the item for processing.
  
  Solution:
  
  Refresh the List: As suggested in the error message, refresh the list of bank statement items. This can sometimes resolve the issue if the item is no longer being processed.
  Check for Locks: Use transaction code SM12 to check for any locks on the bank statement items. If you find a lock that is no longer needed, you can release it (ensure you have the necessary authorizations to do so).
  Wait and Retry: If the item is being processed by another user or a background job, wait for the processing to complete and then try again.
  Check Background Jobs: Use transaction code SM37 to check if there are any background jobs that might be processing the bank statement. If you find any jobs that are stuck or taking too long, you may need to investigate further.
  Consult with Colleagues: If you are in a multi-user environment, check with your colleagues to see if anyone else is working on the same bank statement.
  System Logs: Review system logs for any additional error messages or warnings that might provide more context about the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  FEBA: Process Incoming Payments
  FF67: Manual Bank Statement
  SM12: Display and Delete Locks
  SM37: Job Monitoring
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to bank statement processing.
  User Authorizations: Ensure that you have the necessary authorizations to process bank statements and to release locks if needed.
  
  If the issue persists after trying the above solutions, it may be necessary to contact your SAP support team or consult with an SAP expert for further assistance.