How To Fix CNV_MBT_SHELL063 - Table size data was not saved; saving is necessary to continue

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_MBT_SHELL - Shell Creation

• Message number: 063

• Message text: Table size data was not saved; saving is necessary to continue

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_MBT_SHELL063 - Table size data was not saved; saving is necessary to continue ?

  The SAP error message CNV_MBT_SHELL063 indicates that the table size data was not saved during a migration or conversion process, and saving this data is necessary to continue with the operation. This error typically occurs in the context of SAP's Migration and Conversion tools, particularly when using the SAP S/4HANA Migration Cockpit or similar tools.
  Cause:
  
  Incomplete Data Entry: The table size data may not have been entered or saved correctly in the migration cockpit.
  Technical Issues: There could be technical issues such as database connectivity problems, transaction timeouts, or system resource limitations.
  Authorization Issues: The user may not have the necessary authorizations to save the data.
  Configuration Issues: There may be configuration issues in the migration settings or parameters that prevent the saving of data.
  
  Solution:
  
  Check Data Entry: Ensure that all required fields for the table size data are filled out correctly. Go through the migration cockpit and verify that the data is complete.
  Save Data: Attempt to save the data again. Look for any prompts or buttons that allow you to save the current state.
  Review Logs: Check the application logs (transaction SLG1) for any additional error messages or warnings that could provide more context about the failure.
  Check Authorizations: Ensure that the user executing the migration has the necessary authorizations to perform the operation. You may need to consult with your SAP security team.
  System Resources: Verify that the system has sufficient resources (memory, CPU, etc.) to perform the operation. If necessary, consider increasing the resources or performing the operation during off-peak hours.
  Restart the Process: If the issue persists, try restarting the migration process from the beginning, ensuring that all steps are followed correctly.
  Consult Documentation: Refer to the official SAP documentation for the specific migration tool you are using, as it may provide additional troubleshooting steps or requirements.
  Contact SAP Support: If none of the above solutions work, consider reaching out to SAP Support for assistance, providing them with the error message and any relevant logs.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SLG1 for logs, SE80 for development objects, and SCC4 for client settings.
  Migration Cockpit: Understand the specific migration cockpit you are using, as different versions may have different requirements and functionalities.
  SAP Notes: Search for SAP Notes related to the error message or the migration tool you are using, as they may contain patches or updates that address known issues.
  
  By following these steps, you should be able to resolve the error and continue with your migration or conversion process.