How To Fix >2346 - Account was intermittently being otherwise processed

SAP Error Message - Details

• Message type: E = Error

• Message class: >2 -

• Message number: 346

• Message text: Account was intermittently being otherwise processed

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 >2346 - Account was intermittently being otherwise processed ?

  The SAP error message "2346 Account was intermittently being otherwise processed" typically indicates that there is a conflict or issue with the processing of a specific account in the system. This error can occur in various scenarios, such as during posting transactions, running reports, or executing batch jobs.
  Causes:
  
  Concurrent Processing: The account may be locked or in use by another user or process, leading to intermittent access issues.
  Batch Jobs: If there are batch jobs running that are processing the same account, it can lead to conflicts.
  Data Consistency Issues: There may be inconsistencies in the data related to the account, such as incomplete postings or errors in previous transactions.
  System Performance: High system load or performance issues can cause delays in processing, leading to this error.
  
  Solutions:
  
  Check for Locks: Use transaction codes like SM12 to check for any locks on the account. If another user or process is holding a lock, you may need to wait or coordinate with them.
  Review Batch Jobs: Check if there are any batch jobs running that might be processing the same account. You can use transaction SM37 to monitor and manage batch jobs.
  Data Consistency Check: Run consistency checks on the account data. You can use transaction FB03 to review the account and ensure that all postings are complete and correct.
  Retry the Transaction: Sometimes, simply retrying the transaction after a short period can resolve the issue if it was caused by temporary locks or system load.
  System Performance Monitoring: Monitor system performance and resource usage. If the system is under heavy load, consider scheduling intensive processes during off-peak hours.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (Lock Entries), SM37 (Job Monitoring), and FB03 (Display Document).
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  User Coordination: If multiple users are working with the same account, ensure proper communication to avoid conflicts.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.