Skip to Content

MDMP - Multiple Display/Multiple Processing

History

The MDMP solution has been introduced with R/3 3.1I after the SAP Blended Code Pages solution turned out to be no longer sufficient, because the size of a code page limits the number and the combination of languages that can be supported in a single code page system. MDMP was considered to be a temporary solution for R/3 systems with the restrictions mentioned in the SAP Notes 747036, 745030 and 73606. CRM, SCM, BI and other non-R/3 components never supported MDMP.

Since Web AS 6.20, the standard code page technology for SAP systems is Overview of Unicode.  

Support

Existing MDMP installations are supported up to SAPNetWeaver 2004 (ERP 2004). With SAP NetWeaver 7.0 (ERP 6.0) and all higher releases including all enhancement packages, MDMP is out of support: SAP Note 79991 provides the current status of MDMP support. SAP systems with more than one system code page must be converted to Unicode before or during the upgrade to SAP NetWeaver 7.0 (ERP 6.0). See SAP Notes 838402 and 928729, and Statement for customers (SMP login required) for details.

Technical Information

In an MDMP system, more than one code page can be used on the application server, in order to allow languages to be used together in one system, although the characters used by those languages are not in the same code page. The code page used on the application server is selected dynamically, according to the user's logon language. Whenever a table contains a language field, the character data is always processed with the language in the language field. Language fields therefore guarantee that texts will be processed with the correct language; without a language field, the application server always uses the code page of the logon language. To sum up, only the characters that are in the active code page can be displayed properly, but on the database they are correct.

End of Support

Support has been discontinued because MDMP installations have a number of restrictions:

  • Users can only use the characters of their logon language or 7-bit ASCII. 
  • Incorrect or faulty locales can lead to data corruption. 
  • English texts are "fixed" in one code page and therefore must be repeatedly translated. 
  • Handling errors are likely: e.g. users must log on with the correct language, Batch processes must be assigned with the correct user ID and language, the correct device type must be used. 
  • Global data (from tables without language flag) must contain only 7-bit ASCII characters, which are in all code pages, otherwise data corruption can occur. 
  • As MDMP is an SAP proprietary solution, mixed MDMP data can not be interpreted by most third party products. Only RFC and BAPI communication is possible. 
  • Java integration of MDMP systems is problematic. Java is always based on Unicode. SAP cannot guarantee that Java texts containing Unicode data are properly interpreted by MDMP systems. 
  • Integration of WebDynpro and MDMP systems is problematic. SAP cannot guarantee that data coming from the internet containing Unicode data are properly interpreted by MDMP systems. 
  • The relationships between the language keys and code pages in MDMP systems are only well-defined with SAP systems.

Back to SAP Code Page Solutions Before Unicode

Tags:
Former Member

No comments