How To Fix C2349 - Long text will be overwritten with standard text

SAP Error Message - Details

• Message type: E = Error

• Message class: C2 - Other messages production orders

• Message number: 349

• Message text: Long text will be overwritten with standard text

What causes this issue?

A standard text key is stored in the work center or in the resource.

System Response

The long text is overwritten with the text from the standard text key.

How to fix this error?

In dialog processing, the user can decide whether to replace the text
with the standard text (answer 'Yes'), whether to add the text to the
long text (answer 'No'), or whether the text should remain unchanged
(answer 'Cancel'). This option is not available in background processing
or batch input.
You can influence the system behavior by adjusting the message category
of the system message C2 349 using transaction OPJB. If there is no
entry there for the message C2 349, choose 'New Entries' and create the
following entry:
Version,,,,00000000
Application area,,,,C2
No.,,,,349
Message text,,(no entry)
Category,,,,,,(see below)
You can select from the following message categories:
Message category ' ' - No message or 'W' - Warning
The long text is overwritten with the text from the standard key. You
get the same result if you do not maintain any entry for message C2 349
in transaction OPJB.
Message category 'E' - Error message
The text from the standard text key is added to the long text. This
corresponds to the answer 'No' in the dialog.
Message category 'P' - Popup
The operation text remains unchanged. This corresponds to the answer
'Cancel' in the dialog.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message C2349 - Long text will be overwritten with standard text ?

  The SAP error message C2349, which states "Long text will be overwritten with standard text," typically occurs in the context of SAP when a long text (such as a description or notes) is being replaced by a standard text. This can happen in various modules, such as Sales and Distribution (SD), Materials Management (MM), or others where long texts are used.
  Cause:
  
  Text Type Configuration: The system is configured to use standard texts instead of custom long texts. This can happen if the text type is not set up correctly or if the standard text is prioritized over the long text.
  Text Length Limitations: The long text may exceed the allowed length or format, causing the system to revert to the standard text.
  Missing Text: If the long text is not maintained for a specific object (like a material or sales order), the system may default to the standard text.
  User Authorizations: The user may not have the necessary authorizations to maintain or view the long text, leading the system to use the standard text instead.
  
  Solution:
  
  Check Text Configuration: Review the configuration settings for text types in the relevant module. Ensure that the long text is properly defined and that the system is set to use it.
  Maintain Long Text: Ensure that the long text is maintained for the relevant object. You can do this by navigating to the appropriate transaction (e.g., MM01 for materials, VA01 for sales orders) and checking the long text section.
  Review Authorizations: Check if the user has the necessary authorizations to create or modify long texts. If not, work with your SAP security team to grant the required permissions.
  Adjust Text Length: If the long text exceeds the allowed length, consider shortening it or breaking it into multiple entries if applicable.
  Consult Documentation: Refer to SAP documentation or help files for specific guidance on handling long texts in the relevant module.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide specific fixes or workarounds.
  Transaction Codes: Familiarize yourself with relevant transaction codes for maintaining texts, such as SO10 (for standard texts) or the specific transaction for the module you are working in.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, providing insights or solutions from other users' experiences.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or a technical consultant for further investigation.