How To Fix CNV_PE145 - Totals table belongs to NewGL, however ClassicGL is active

CNV_PE145 - Overview

• Message type: E = Error

• Message class: CNV_PE - General messages for posting engine

• Message number: 145

• Message text: Totals table belongs to NewGL, however ClassicGL 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.

CNV_PE145 - Details

• The SAP error message CNV_PE145 indicates a conflict between the New General Ledger (NewGL) and Classic General Ledger (ClassicGL) configurations in your SAP system. Specifically, it suggests that the totals table you are trying to access or manipulate is associated with the NewGL, but the ClassicGL is still active in your system. This situation can arise during data migration or when trying to execute certain transactions that require a specific configuration.
  
  Cause:
  
  Mixed Configuration: The system is configured to use both NewGL and ClassicGL, which can lead to inconsistencies, especially if the totals tables are being accessed or modified.
  Migration Issues: If you are in the process of migrating from ClassicGL to NewGL, this error may occur if the migration is not fully completed or if there are still dependencies on ClassicGL.
  Transaction Settings: Certain transactions or reports may be set to use ClassicGL, while the underlying data is in NewGL format.
  
  
  Solution:
  
  
  Check Configuration:
  
  Verify the