How To Fix /PRA/ACCOUNTING398 - Journal Entry posting failed as new Accounting switch is active

SAP Error Message - Details

• Message type: E = Error

• Message class: /PRA/ACCOUNTING -

• Message number: 398

• Message text: Journal Entry posting failed as new Accounting switch is active

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 /PRA/ACCOUNTING398 - Journal Entry posting failed as new Accounting switch is active ?

  The SAP error message /PRA/ACCOUNTING398 Journal Entry posting failed as new Accounting switch is active typically indicates that there is an issue with the configuration of the new accounting framework in SAP, particularly when transitioning from the classic General Ledger (G/L) to the new G/L accounting.
  Cause:
  
  New Accounting Switch: The error suggests that the new accounting switch is active, which means that the system is expecting transactions to be processed in accordance with the new G/L accounting principles.
  Configuration Issues: There may be configuration settings that are not properly set up for the new G/L, such as missing account assignments, incorrect document types, or issues with the integration of sub-ledgers.
  Data Migration Issues: If data migration from the old G/L to the new G/L was not completed successfully, it could lead to inconsistencies that prevent journal entries from being posted.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to post in the new accounting environment.
  
  Solution:
  
  Check Configuration: Review the configuration settings for the new G/L accounting. Ensure that all necessary settings are correctly configured, including document types, account assignments, and integration with sub-ledgers.
  Review Migration Data: If you have recently migrated data, check for any inconsistencies or errors in the migration process. Ensure that all necessary data has been transferred correctly.
  Transaction Codes: Use transaction codes like OBY6 to check the settings for the new G/L and OBY1 for the company code settings.
  Authorization Check: Ensure that the user attempting to post the journal entry has the necessary authorizations to perform the action in the new accounting environment.
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error. SAP frequently releases updates and patches that may resolve known issues.
  Testing: If possible, test the posting in a development or quality assurance environment to identify any specific issues before attempting in the production environment.
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for guidance on configuring the new G/L accounting.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Support: If the issue persists, consider reaching out to SAP support for assistance, especially if it is impacting business operations.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.