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: UMG - Message Class for the Unicode Migration Tool.
Message number: 350
Message text: The table name is too long (number of characters >26)
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.
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.
UMG350
- The table name is too long (number of characters >26) ?The SAP error message UMG350 indicates that a table name exceeds the maximum allowed length of 26 characters. In SAP, the naming conventions for database objects, including tables, are strict, and this limitation is in place to ensure compatibility and maintainability within the system.
Cause:
The error occurs when you attempt to create or reference a table with a name that is longer than the allowed limit of 26 characters. This can happen during various operations, such as:
To resolve this error, you need to ensure that the table name adheres to the 26-character limit. Here are some steps you can take:
Rename the Table: If you are creating a new table, choose a shorter name that is descriptive but within the character limit. You can use abbreviations or acronyms to shorten the name.
Modify Existing References: If the error arises from an existing table, check any references to that table in your code or configuration. Ensure that you are not inadvertently using a longer name.
Check Transport Requests: If the error occurs during a transport, verify that the objects being transported do not include any tables with names exceeding the limit.
Review Naming Conventions: Establish and follow a naming convention for your database objects that keeps names concise and within the character limit.
Consult Documentation: Refer to SAP documentation or guidelines for naming conventions to ensure compliance with best practices.
By following these steps, you should be able to resolve the UMG350 error and ensure that your table names comply with SAP's requirements.
Get instant SAP help. Sign up for our Free Essentials Plan.
UMG349
The table has been inserted into the exception list.
What causes this issue? The table has been inserted into the SPUMG Exception List already. The table is not scanned (flag "Skip Scan") or i...
UMG348
The table has already been inserted.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
UMG351
Table &1 is currently processed. It will not be reset.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
UMG352
Please mark a table in the tree.
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.