How To Fix /RPM/ITEM347 - No custom long texts are available in source language

SAP Error Message - Details

• Message type: E = Error

• Message class: /RPM/ITEM -

• Message number: 347

• Message text: No custom long texts are available in source language

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 /RPM/ITEM347 - No custom long texts are available in source language ?

  The SAP error message /RPM/ITEM347 No custom long texts are available in source language typically occurs in the context of SAP's Resource and Portfolio Management (RPM) module. This error indicates that the system is unable to find any custom long texts for a specific item in the source language that is being used.
  Cause:
  
  Missing Long Texts: The primary cause of this error is that there are no long texts defined for the item in the specified source language. Long texts are often used to provide additional information about an item, and if they are not maintained, this error can occur.
  Language Settings: The language settings in the user profile or the system configuration may not match the language in which the long texts are expected.
  Data Migration Issues: If data has been migrated from another system, long texts may not have been transferred correctly.
  Custom Development: If there are custom developments or enhancements in the system, they may not be handling long texts properly.
  
  Solution:
  
  
  Maintain Long Texts: 
  
  Navigate to the relevant transaction or area in SAP where you can maintain long texts for the item in question.
  Ensure that long texts are created and saved for the item in the source language.
  
  
  
  Check Language Settings:
  
  Verify the language settings in your user profile. You can do this by going to the user settings and ensuring that the correct language is set.
  Check the system settings to ensure that the source language is correctly configured.
  
  
  
  Review Data Migration:
  
  If this issue arose after a data migration, review the migration process to ensure that long texts were included and correctly mapped.
  
  
  
  Custom Development Review:
  
  If there are custom developments, review the code to ensure that it correctly handles long texts. You may need to involve a developer to troubleshoot this.
  
  
  
  SAP Notes and Support:
  
  Check for any relevant SAP Notes that may address this issue. Sometimes, SAP releases notes that provide fixes or workarounds for specific error messages.
  If the problem persists, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may need to use transaction codes like SE11 (Data Dictionary), SE78 (SAP ArchiveLink), or others to maintain or check long texts.
  Documentation: Refer to SAP documentation for the RPM module to understand how long texts are used and maintained.
  User Forums: Consider checking SAP community forums or other user groups for similar issues and solutions shared by other users.
  
  By following these steps, you should be able to resolve the error message and ensure that long texts are available for the items in question.