Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-I18 (Application Component) Internationalization (I18N)⤷
SCP (Package) SAP Code Pages
Basic Data
| Data Element | SM59MDMPSWITCH |
| Short Description | RFC Non-Unicode Destination: MDMP Mode On/Off |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | MDMP Mode |
| Medium | 18 | MDMP Mode On/Off |
| Long | 37 | Non-Unicode Destination: MDMP On/Off |
| Heading | 41 | RFC Non-Unicode Destination: MDMP On/Off |
Documentation
Definition
MDMP settings
Use
In MDMP systems, text data exists in different languages, which are all differently coded (for example, Japanese data in SJIS, Polish data in ISO 8859-2).
If the type of the text data contains a language key, the RFC converts the text fields between Unicode and the codepage that the MDMP system uses for this language.
If the data contains no language key, the RFC converts between Unicode and the transport codepage specified for this RFC connection, which depends on the logon language of the calling system.
Inactive:
When text data is converted between Unicode and a non-Unicode codepage in the target system, a predefined codepage is used, which depends on the language key of the data.
Note 547444 describes this default setting, which is the same for all destinations.
This is the default.
Active:
Here, you assign the codepage used in the target system to the languages yourself.
Choose the "Detail" button to branch to the maintenance tool for this assignment. Here you can read a description of the tool and adopt, edit, or extend the assignment provided by the destination.
CAUTION: Pressing this button triggers an RFC to the destination. To avoid any RFC errors, you must first ensure that the connection for an RFC is correctly set up.
Dependencies
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 630 |
