Settings for Special Code Pages 

In Unicode systems, you configure the conversion of text data for the RFC destinations on the tab page Special Options. Here, F1 help is available for you to get more information. You can configure the following:

Character Width in Target System

Here you specify whether the RFC destination is a Unicode system or a non-Unicode (MDMP) system. A pushbutton gets this information from the target system.

MDMP Setting for Non-Unicode Destinations

For non-Unicode destinations, the RFC either uses a preconfigured assignment of languages to code pages that is the same for all destinations, or an assignment which can be maintained for the destination; at the push of a button you can get the assignment list of the destination system by way of RFC.

Character Conversion

Here you define how conversion errors are handled:

·        The RFC terminates when conversion errors occur, or continues despite conversion errors, whereby non-convertible characters are replaced with replacement characters.

·        The RFC replaces non-convertible characters with the replacement character ‘#’.

·        The RFC replaces non-convertible characters with another character that you can choose.

 

Preconfigured Code Pages

The RFC uses a preconfigured assignment of text languages to code pages if:

·        The destination is set to non-Unicode and MDMP inactive.

·        A non-Unicode system calls a function in a Unicode system and does not make known its assignment list; this is true for systems with kernel older than Release 6.20, Patch level 375. More recent systems transmit their assignment list to the called Unicode system, meaning that the preconfiguration is not required.

 

The following table shows this assignment; the called system uses the transport code page specified by the caller, to determine whether the data involved is EBCDIC data or not.

 

Language (ISO, SAP ID):	Transport Code Page:
	Non EBCDIC	EBCDIC
West European languages	1100	0120
East European languages	1401	0410
Baltic languages	1900	0120
Japanese (JA, J)	8000
Chinese (ZH, 1)	8400
Korean (KO, 3)	8500
Arabic (AR, A)	8700
Taiwanese (ZF, M)	8300
Thai (TH, 2)	8600	0860
Ukrainian (UK, 8)	1500	0500
Hebrew (HE, B)	1800	0800
Greek (EL, G)	1700	0700
Russian (RU, R)	1500	0500
Turkish (TR, T)	1610	0610
Bulgarian (BG, W)	1500	0500

 

This table applies to standard transport code pages that are based on ISO standards (such as 1100, ISO8859-1) or country-specific standards (such as 8000, SJIS). If SAP’s own code pages are used as transport code pages, then the following assignment applies:

 

Transport Code Page:	Examples	Assigned Code Page:
SAP blended ambiguous	6100 SAP Unification 6200 Asian Unification 6500 Diocletian	Standard code page depending on text language. Data is therefore reinterpreted uniquely, language-dependently.
SAP blended  unambiguous	6300 Euro Japan	The same code page. Data is already coded uniquely.
Transliteration	1180	1180. Data is already coded uniquely.

 

 

Trusted System: Trust Relationships Between SAP Systems