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

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_PE - General messages for posting engine

• Message number: 146

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

  The SAP error message CNV_PE146 indicates that there is a conflict between the Classic General Ledger (Classic GL) and the New General Ledger (New GL) in your SAP system. Specifically, this error occurs when a totals table that is expected to be part of the Classic GL is being referenced while the New GL is active.
  Cause:
  
  Mixed Configuration: The system is configured to use New GL, but there are still references or data in the Classic GL totals tables.
  Data Migration Issues: During a migration process from Classic GL to New GL, some data or configurations may not have been properly updated or converted.
  Inconsistent Settings: The settings in the Financial Accounting (FI) module may not be consistent, leading to references to Classic GL tables while New GL is active.
  
  Solution:
  
  
  Check Configuration: Ensure that the New GL is properly configured and that all necessary settings have been made to fully transition from Classic GL to New GL.
  
  Go to transaction code OBY6 to check the settings for the New GL.
  
  
  
  Data Migration: If you are in the process of migrating from Classic GL to New GL, ensure that all necessary migration steps have been completed. This may involve running specific migration programs or tools provided by SAP.
  
  Use transaction SCPR20 to check for any migration issues.
  
  
  
  Review Totals Tables: Investigate the totals tables (e.g., BSIK, BSAK) to see if there are any entries that should have been migrated or cleared.
  
  You may need to run reports or programs to clean up or migrate data from Classic GL totals tables.
  
  
  
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
  
  Use transaction SNOTE to search for notes related to this error.
  
  
  
  System Consistency Check: Perform a consistency check on your financial data to ensure that there are no discrepancies between the Classic GL and New GL.
  
  Use transaction FAGLB03 to review the general ledger balances.
  
  
  
  Contact SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance. They can provide more specific guidance based on your system configuration and version.
  
  
  Related Information:
  
  New GL vs. Classic GL: Understanding the differences between Classic GL and New GL is crucial. New GL offers enhanced functionalities such as parallel accounting, segment reporting, and improved data structures.
  Migration Tools: Familiarize yourself with SAP's migration tools and methodologies for transitioning from Classic GL to New GL, as these can help streamline the process and avoid errors.
  Documentation: Review SAP documentation and guides related to New GL implementation and migration for best practices and troubleshooting tips.
  
  By following these steps, you should be able to resolve the CNV_PE146 error and ensure that your SAP system is correctly configured to use the New GL.