Do you have any question about this error?
Message type: E = Error
Message class: >2 -
Message number: 344
Message text: Account is currently being otherwise processed
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.
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.
>2344
- Account is currently being otherwise processed ?The SAP error message "2344 Account is currently being otherwise processed" typically occurs when a user attempts to post a transaction to an account that is currently locked or being processed by another transaction. This can happen in various scenarios, such as during month-end closing, when a financial document is being edited, or when a batch job is running that affects the account.
Causes:
- Concurrent Processing: Another user or process is currently accessing or modifying the account.
- Batch Jobs: A background job is running that locks the account for processing.
- Open Periods: The account may be locked due to open periods in financial accounting.
- Document Locking: A document related to the account is being edited or posted by another user.
Solutions:
- Wait and Retry: If the account is being processed by another user or job, wait for a few moments and then try posting again.
- Check for Locks: Use transaction codes like
SM12
(to check for locks) to see if there are any active locks on the account. If you find a lock that is no longer needed, you may need to contact the user who has the lock or your SAP administrator to release it.- Review Batch Jobs: Check if there are any batch jobs running that might be locking the account. You can use transaction
SM37
to monitor job statuses.- Consult with Team: If you are in a shared environment, communicate with your team to ensure that no one else is processing transactions on the same account.
- Check Configuration: Ensure that the account is not locked due to configuration settings in the financial module.
Related Information:
SM12
(to view and manage locks), SM37
(to monitor background jobs), and SE11
(to check table definitions).If the issue persists after trying the above solutions, it may be necessary to escalate the matter to your SAP support team or consult with an SAP expert for further investigation.
Get instant SAP help. Start your 7-day free trial now.
>2343
Ticket &1 is not (or no longer) valid
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
>2342
Not possible to distribute promised amount to open items
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
>2345
It was not possible to read open items
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
>2346
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...
Click on this link to search all SAP messages.