Do you have any question about this error?
Message type: E = Error
Message class: CNV_20200_CHECK - Messages for check functions (company code merge)
Message number: 112
Message text: Document splitting within new G/L not active for all participating CoCds
Document splitting within new G/L is not active for all involved company
codes.
Some participating company codes have document splitting active, whereas
other involved company codes have document splitting inactive.
Error
You cannot run the transformation solution for company code merge
because certain prerequisites have not been met. We recommend that you
contact SAP for support by creating a ticket using component CA-LT-CNV.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
CNV_20200_CHECK112
- Document splitting within new G/L not active for all participating CoCds ?The SAP error message CNV_20200_CHECK112 indicates that document splitting within the new General Ledger (G/L) is not activated for all participating company codes (CoCds) in a migration or conversion scenario. This error typically arises during the migration process when the system checks for the configuration of document splitting, which is essential for ensuring that financial documents are properly segmented and reported according to the requirements of the new G/L.
Cause:
- Document Splitting Not Activated: The primary cause of this error is that document splitting is not activated for one or more company codes involved in the migration.
- Inconsistent Configuration: There may be inconsistencies in the configuration of the new G/L settings across different company codes.
- Migration Settings: The migration settings may not have been properly configured to handle document splitting.
Solution:
To resolve this error, you need to ensure that document splitting is activated for all participating company codes. Here are the steps to do this:
Check Document Splitting Configuration:
- Go to the SAP Easy Access screen.
- Navigate to SPRO (SAP Project Reference Object) > Financial Accounting > General Ledger Accounting > Business Transactions > Document Splitting > Activate Document Splitting.
- Ensure that document splitting is activated for all relevant company codes.
Activate Document Splitting:
- If document splitting is not activated for a company code, you can activate it by selecting the company code and enabling the document splitting feature.
Review Configuration:
- Check the configuration settings for document splitting to ensure they are consistent across all company codes. This includes settings for splitting characteristics, document types, and other related parameters.
Test the Configuration:
- After making the necessary changes, perform a test to ensure that the document splitting works as expected and that the error does not reoccur.
Consult Documentation:
- Refer to SAP documentation or notes related to document splitting and the new G/L for any additional guidance or specific requirements.
Related Information:
By following these steps, you should be able to resolve the CNV_20200_CHECK112 error and ensure that document splitting is properly configured for all participating company codes in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
CNV_20200_CHECK111
Document splitting within new G/L inactive for all participating CoCodes
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CNV_20200_CHECK110
Document splitting within new G/L active for all particip. company codes
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CNV_20200_CHECK113
Company code &1, split_active = &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CNV_20200_CHECK114
Field &1-&2 is different (in &3 cases)
What causes this issue? The contents of field &V2& in table &V1& is different. Number of concerned G/L accounts / vendor accounts / c...
Click on this link to search all SAP messages.