Solution : https://service.sap.com/sap/support/notes/784381 (SAP Service marketplace login required)
Summary :
SAP Note addresses issues with IDoc status "02" due to undetermined code pages in scenarios where Unicode SAP systems interface with non-Unicode systems via tRFC. The issue arises because the receiver system’s code page cannot be dynamically determined, resulting in IDocs defaulting to status "02" and error message E0266. To resolve, it's advised to ensure correct settings in SM59 and potentially use report RBDAGAIN. Additionally, implementing a custom table ZEDIPOACODPAG for capturing the last used code page and adjusting permissions for function module NPL_GET_LANGU_CP_TAB are recommended. Updates in SAP's Release 6.40 require extra authorizations for RFC users.
Key words :
field data element short description mandt mandt client portname edi_pvrcvp port logdes edi_logdes rfc destination langu rfclang explicit language codpag edi_codpag character set, cpi-c-port, idoc inbound processing procedure, field rfc_name = scp5, destination, field actvt = 16, find code page, terms code page, function module nls_get_langu_cp_tab, role sap_bc_usr_cua_client - note 492589
Related Notes :
| 1338638 | Lock problem during update in table EDIPOACODPAG |
| 1062576 | SCP_LANGUAGES_IN_INSTANCE returns nothing |
| 816556 | NLS_GET_LANGU_CP_TAB: wrong code page |
| 613389 | ALE SAP system group with Unicode systems |
| 492589 |