Do you have any question about this error?
Message type: E = Error
Message class: CNV_PE_CHECK - Check Framework messages for posting engine
Message number: 035
Message text: Status with ID &1 missing
Every status bundle ID must contain certain status values, as they are
hardcoded within the application.
The program found that status &V1& does <ZH>not </>exist
Error
Contact SAP for support.
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_PE_CHECK035
- Status with ID &1 missing ?The SAP error message CNV_PE_CHECK035 with the description "Status with ID &1 missing" typically occurs in the context of data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or other data migration tools. This error indicates that a specific status ID that is expected in the system is not found, which can halt the migration process.
Cause:
- Missing Status ID: The error is primarily caused by a missing status ID in the relevant tables or configuration settings. This could happen if the status was not created or was deleted inadvertently.
- Configuration Issues: There may be issues with the configuration of the migration project or the source system, leading to discrepancies in expected data.
- Data Inconsistencies: If the data being migrated has inconsistencies or does not meet the required criteria, it can lead to this error.
- Version Compatibility: Sometimes, the error can arise due to compatibility issues between different versions of SAP systems or migration tools.
Solution:
- Check Status Configuration: Verify that the status ID mentioned in the error message exists in the relevant configuration tables. You can do this by checking the customizing settings in the SAP system.
- Create Missing Status: If the status ID is indeed missing, you may need to create it manually in the system. This can usually be done through the relevant transaction codes or customizing paths.
- Review Migration Settings: Ensure that the migration settings and parameters are correctly configured. Check if the source and target systems are aligned in terms of data structure and requirements.
- Data Validation: Validate the data being migrated to ensure that it meets all necessary criteria and does not contain any inconsistencies.
- Consult Documentation: Refer to the SAP documentation or notes related to the specific migration tool you are using for any additional troubleshooting steps or known issues.
- SAP Support: If the issue persists, consider reaching out to SAP Support for assistance. They can provide insights based on the specific context of your migration project.
Related Information:
By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.
Get instant SAP help. Start your 7-day free trial now.
CNV_PE_CHECK034
Usage type differs, see long text
What causes this issue? The program found that the currently checked object has usage type &V1&, while object ID &V2& (&V3&) ...
CNV_PE_CHECK033
Severity differs within severity level &1
What causes this issue? Within the same severity level all status severities must be the same. This rule of thumb is violated within severity level &...
CNV_PE_CHECK036
Area status without corresponding worklist item status
What causes this issue? On area level the status &V1& with the characteristics <ZK>Severity level/Severity/Status type</>: &V...
CNV_PE_CHECK037
Execution rule &1 is not assigned to area &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.