Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: CNVA_20290_CHECK - Message class for company code merge preanalysis
Message number: 159
Message text: There are company codes in the system that are not yet set as productive
Error message extract from SAP system. Copyright SAP SE.
CNVA_20290_CHECK159
- There are company codes in the system that are not yet set as productive ?The SAP error message CNVA_20290_CHECK159 indicates that there are company codes in the system that have not been set to a productive status. This typically occurs during the migration or configuration process when certain company codes are still in a test or development phase and have not been activated for productive use.
Cause:
- Company Code Status: The company codes in question are likely still marked as "test" or "development" in the system, which means they cannot be used for productive transactions.
- Configuration Incomplete: The necessary configuration steps to set the company codes to productive status may not have been completed.
- Migration Process: If you are in the process of migrating data or settings, this error may arise if the migration checks for productive company codes.
Solution:
Check Company Code Status:
- Go to the transaction code OBY6 (or use the appropriate navigation path) to check the status of the company codes.
- Ensure that the company codes you intend to use are set to "productive."
Set Company Codes to Productive:
- If the company codes are not set to productive, you can change their status. In the configuration settings, look for the option to set the company code to productive.
- Make sure to follow the necessary steps to ensure that all required configurations are completed before setting the company code to productive.
Review Configuration:
- Ensure that all necessary configurations for the company codes are completed, including financial settings, fiscal year variants, and other relevant parameters.
Consult Documentation:
- Refer to SAP documentation or guides related to company code configuration and migration processes for detailed steps and best practices.
Testing:
- After making changes, conduct thorough testing to ensure that the company codes function correctly in a productive environment.
Related Information:
By following these steps, you should be able to resolve the CNVA_20290_CHECK159 error and ensure that your company codes are properly configured for productive use.
Get instant SAP help. Sign up for our Free Essentials Plan.
CNVA_20290_CHECK158
Purchase Account Processing is not active or inactive
Purchase Account Processing is not active or inactive for all the participating company codes. The activation (T001-XEINK) differs for the participa...
CNVA_20290_CHECK157
The participad company codes have different global company codes assigned
The participating company codes have different global company codes assigned (T001-BUKRS_GLOB). Note that the system uses the settings from the refer...
CNVA_20290_CHECK160
All selected company codes which contain data for the current FY
All selected company codes which contain data for the current and/or previous fiscal year are set as productive in the global parameters of the compa...
CNVA_20290_CHECK161
There are differences in the vendor master records for dunning
There are differences in the vendor master records for dunning at company code level. These differences could have impact on business processes, and ...
Click on this link to search all SAP messages.