How To Fix UIU_TEXT021 - &1, &2: You have switched between SAPscript and HTML-based texts

SAP Error Message - Details

• Message type: E = Error

• Message class: UIU_TEXT - generic text service

• Message number: 021

• Message text: &1, &2: You have switched between SAPscript and HTML-based texts

What causes this issue?

If you switch between SAPscript and HTML-based texts, you will change
from which persistency texts are read and written. It is not possible to
read and write texts from a particular text object and ID from both
SAPscript and HTML-based texts. You can only use either SAPscript or
HTML-based texts for a single text object and ID combination.
When swtiching between SAPscript and HTML-based texts, any existing
texts for this text object and ID combination will remain in the
corresponding database tables. Therfore, these texts will not be
included in UI any longer.
Recommendation: It is recommended that you do not switch a text object
and ID combination between SAPscript and HTML-based texts. Use different
text objects and ID combinations.
For more information about text formatting options and persistency, see
<DS:SIMG.CRM_TEXT_FORMAT>Define Text Format</>.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Configure different or create new text object and ID combinations to
keep SAPscript and HTML-based texts separate.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message UIU_TEXT021 - &1, &2: You have switched between SAPscript and HTML-based texts ?

  The SAP error message UIU_TEXT021 indicates that there is a conflict between SAPscript and HTML-based texts in your SAP system. This typically occurs when a user attempts to switch between these two types of text formats in a context where only one format is expected.
  Cause:
  
  
  Text Format Conflict: The error arises when the system detects that a user is trying to use both SAPscript and HTML-based text formats in a single transaction or context. This can happen if:
  
  The user has previously created or edited a text in one format and is now trying to switch to the other format.
  The configuration or settings for the text type are not consistent.
  
  
  
  Inconsistent Settings: The settings for the text type in the relevant application may not be properly configured to handle both formats, leading to this error when a switch is attempted.
  
  
  Solution:
  
  
  Consistent Text Format: Ensure that you are using a consistent text format throughout your transaction. If you start with SAPscript, continue using SAPscript, and similarly for HTML-based texts.
  
  
  Check Text Type Settings: Review the configuration settings for the text types in the relevant application. Make sure that the text type is set to either SAPscript or HTML, depending on your requirements.
  
  
  Clear Text Fields: If you need to switch formats, clear any existing text in the text fields before switching to the other format. This can help avoid conflicts.
  
  
  Use the Correct Transaction: Make sure you are using the correct transaction or function module that supports the text format you intend to use.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on handling text formats in your particular application area.
  
  
  Related Information:
  
  SAPscript: A traditional SAP text processing tool used for creating and formatting texts in SAP applications.
  HTML-based Texts: A newer format that allows for more flexible and visually appealing text presentations, often used in web-based applications.
  Transaction Codes: Familiarize yourself with relevant transaction codes that deal with text management, such as SO10 (for standard texts) or other specific transactions related to your application.
  
  If the issue persists after trying the above solutions, consider reaching out to your SAP support team or consulting SAP Notes for any known issues or patches related to this error message.