Solution : https://service.sap.com/sap/support/notes/871945 (SAP Service marketplace login required)
Summary :
In SAP Unicode systems, specific issues arise with RFC connections involving Z languages, which lack built-in default code pages. This discrepancy leads to runtime errors and other complications when these languages, not usually expected in language configurations, appear in RFC parameters or tables. For error resolution, updating to recommended kernel patches and implementing explicit Z language configurations are prescribed. Activation of correct Z languages and assigning non-Unicode code pages, as referenced by error messages, is crucial for maintaining system interoperability and preventing data handling anomalies.
Key words :
=`/'2fxz6 cp=1100 miss zn lang, '2cxz4 cp=1100 hit zn lang, '3bxz8 cp=1100 miss zn lang, list=a1401t$8000f$1100d$$ lang=`/', required language/ code page association, 9xy error => rfc ======> rscplangcplistgetcp failed, explicit language/code page vector, =`$'24xnn cp=nnnn skip, short dump rfc_conversion_table indicating, final zn fallback fails
Related Notes :
| 1375438 | Globalization Collection Note |
| 1319517 | Unicode Collection Note |
| 920831 | RFC with inactive text language |
| 881781 | Unicode/non-Unicode RFC language and code page assignment |
| 814707 | Troubleshooting for RFC connections Unicode/non-Unicode |
| 809279 | RFC non-Unicode to Unicode with unknown text language |
| 647495 | RFC for Unicode ./. non-Unicode Connections |
| 302063 | Correspondence Language |
| 112065 | Using customer language 'Z1' |
| 19466 | Downloading SAP kernel patches |