Do you have any question about this error?
Message type: E = Error
Message class: 31 - Message Processing: IDoc Service Master Record
Message number: 013
Message text: Short texts: language key & not in table T002
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.
31013
- Short texts: language key & not in table T002 ?The SAP error message 31013, which states "language key & not in table T002," typically occurs when the system is trying to access a language that is not defined in the T002 table. The T002 table in SAP contains the list of languages that are available for use in the system.
Cause:
- Missing Language Entry: The language key specified in the error message is not present in the T002 table. This could happen if the language was not installed or if there was an error during the installation process.
- Incorrect Language Key: The language key being referenced might be incorrect or misspelled.
- Configuration Issues: There may be configuration issues in the system that prevent the language from being recognized.
Solution:
Check T002 Table:
- Go to transaction code SE11 (Data Dictionary) and enter the table name T002.
- Check if the language key mentioned in the error message exists in the table. If it does not, you may need to add it or correct the configuration.
Add Language:
- If the language is missing, you can add it using transaction code SMLT (Language Transport). This allows you to install additional languages in your SAP system.
Verify Language Key:
- Ensure that the language key being used is correct. Common language keys include 'EN' for English, 'DE' for German, etc. If the key is incorrect, update it to the correct one.
Check User Settings:
- Sometimes, the issue may arise from user-specific settings. Check the user profile settings to ensure that the correct language is set.
Consult Documentation:
- Refer to SAP documentation or support notes for any specific instructions related to the language setup in your version of SAP.
Contact SAP Support:
- If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
Related Information:
By following these steps, you should be able to resolve the error message 31013 in SAP.
Get instant SAP help. Start your 7-day free trial now.
31012
Wage type: entry & for info category '3003' not in table TT512Z
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
31011
Master language: language key & not in table T002
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
31014
Unit of measurement &: conversion ISO to SAP not possible
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
31015
Function module called for wrong message category
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.