Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata


The purpose of this page is to provide information around Blended code pages. Although they are no longer supported, it is good to know the background as to why they were created by SAP and why they are no longer in use today.


In the past, some customers using a Single code page system found they had a requirement to use languages which were not part of the active code page. They needed more than what a Single code page could offer. SAP therefore invested time in creating SAP Blended code pages. These are in effect Single code page systems, but with characters included from more than one code page. This resulted in the possibility of using more languages, however, only those specified as part of the Blended code page could be used. One drawback was that some of the lesser used "special" characters in the languages were omitted


Support for Blended code pages on new installations has stopped since >= SAP_BASIS 6.xx Release. Support for existing installations is deprecated since >= SAP Netweaver 7.xx Release.

Types of Blended code pages

There are two different types of Blended code page: Unambiguous and Ambiguous.

  • Unambiguous Blended code page
    With an Unambiguous Blended code page only one character is assigned to each byte sequence, therefore there is no ambiguity when it comes to the character. Because of this, it is far easier to convert this type of Blended code page system to Unicode than a system configured with an Ambiguous code page. The conversion is similar to that of a Single code page system.


  • Ambiguous Blended code page
    An Ambiguous Blended code page is designed so that more than one character can be allocated to the same byte sequence. The character to display on screen is determined by the logon language. A conversion to Unicode is more difficult from the conversion for an Unambiguous Blended code page; it is similar to an MDMP conversion. Usually the Vocabulary is large when carrying out this type of conversion.


Converting to Unicode 

If your system is still using a Blended code page, SAP highly recommends that you consider converting the system to Unicode. As mentioned above, a conversion to Unicode is much easier if the system is configured with an Unambiguous Blended code page, however, both types have been converted in the past without issue. SAP have created guidelines and conversion documentation to assist you with your conversion, regardless of system type. For more information, please review SAP Note 818374  Unicode Conversion of a Blended Code Page System


When Blended code pages were developed they provided customers with the ability to expand the number of languages they could use, particularly when there was a need to use and support European and Asian languages on the one system. In reality, they were a "stop-gap" until MDMP was introduced. In the last few years, with the introduction of Unicode, usage and support for both of these configurations has decreased and stopped. Unicode is now the recommended solution for multiple language support. 

Related Content

Related Documents

Related Notes

SAP Note 818374 Unicode Conversion of a Blended Code Page System

  • No labels