Show TOC

Background documentationPreconfigured Code Pages Locate this document in the navigation structure

 

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 publish its assignment list. This is the case in systems with kernel older than Release 6.20, Patch level 375. More recent systems pass their assignment list to the called Unicode system, in which case the preconfigured setting is not required.

The table below shows this assignment. The called system uses the transport code page specified by the caller to determine whether the data is EBCDIC data.

Assignment of Text Languages to Code Pages

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 is valid for 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 code pages are used as transport code pages, the following assignment applies:

Assignment of SAP Code Pages

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.