How To Fix CNV_10500105 - Document splitting in new G/L is active, company code &1

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_10500 - Messages of Special Ledger Package

• Message number: 105

• Message text: Document splitting in new G/L is active, company code &1

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_10500105 - Document splitting in new G/L is active, company code &1 ?

  The SAP error message CNV_10500105 indicates that document splitting in the new General Ledger (G/L) is active for the specified company code. This error typically arises during data migration or when trying to post documents in a company code that has document splitting enabled, but the necessary configurations or data are not in place.
  Cause:
  
  Document Splitting Configuration: The company code has document splitting enabled, but the necessary settings for document splitting (like splitting characteristics, segment definitions, etc.) are not properly configured.
  Missing Segment Information: The document being posted does not contain the required segment information, which is necessary for document splitting.
  Incompatibility with Legacy Data: If you are migrating data from a legacy system, the data may not conform to the new G/L document splitting requirements.
  
  Solution:
  
  
  Check Document Splitting Configuration:
  
  Go to the configuration settings for document splitting in the new G/L. You can find this under SPRO > Financial Accounting > General Ledger > Document Splitting.
  Ensure that the splitting characteristics and segment definitions are correctly set up for the company code in question.
  
  
  
  Review Document Posting:
  
  When posting documents, ensure that all required fields for document splitting are filled out. This includes segment information if it is required by your configuration.
  
  
  
  Data Migration Adjustments:
  
  If you are migrating data, ensure that the legacy data is adjusted to meet the new G/L requirements. This may involve adding segment information or adjusting the data structure to align with the new G/L document splitting rules.
  
  
  
  Testing:
  
  After making the necessary adjustments, perform test postings to ensure that the error does not reoccur.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to document splitting and the new G/L for additional guidance and best practices.
  
  
  
  Related Information:
  
  Document Splitting: This is a feature in the new G/L that allows for more detailed financial reporting by splitting documents into different segments based on defined criteria.
  New G/L: The new General Ledger in SAP provides enhanced functionalities over the classic G/L, including document splitting, parallel accounting, and more flexible reporting options.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or provide patches related to document splitting and the new G/L.
  
  If the issue persists after following these steps, it may be beneficial to consult with an SAP expert or your technical support team for further assistance.