Unicode Errors - Interface with non-Unicode 3rd party system

[Former Member]

Does anyone have an experience working with an interface between a Unicode SAP system and a non-Unicode 3rd party system? Would appreciate your input on existing data declaration and logic (prior to SAP Unicode conversion), if changes need to be made to the character types and upload/download functions.

We are doing our testing in a newly converted Unicode system which has interface sending files through SAP Business Connector, and uses TDAccess/COMM-PRESS to encrypt the payment file.

We are getting an COMM-PRESS error that it's not able to get the private key

ERR=>RC=107#Error building signature segment (S1A/S2A) ERR=>#Error getting private key: #PUBLIC KEY FINGERPRINT = , rc = 524

The issue seems to be that the passphrase is not received correctly in COMM-PRESS (codepage 1100) from Unicode SAP (codepage 4102). The passphrase is uploaded from a text file (codepage 1100?) to T_PPLOC and then to W_PPLOC.

TYPES: BEGIN OF T_PPLOC,

FLINE(64) TYPE C,

END OF T_PPLOC.

DATA: W_PPLOC(64) TYPE C

CALL FUNCTION 'GUI_UPLOAD'

EXPORTING

FILENAME = W_FILENAME

FILETYPE = 'BIN'

TABLES

DATA_TAB = T_PPLOC

LOOP AT T_PPLOC.

IF W_PPLOC IS INITIAL.

MOVE T_PPLOC-FLINE TO W_PPLOC.

ELSE.

CONCATENATE W_PPLOC T_PPLOC-FLINE INTO W_PPLOC.

ENDIF.

ENDLOOP.

Comparing the results between a Unicode and non-Unicode system, the uploaded passphrase is different because of the codepage. But even if I convert the passphrase first from 1100 to 4102 codepage, it still fails.

[former_member194669]

Hi,

Try this by sending value to the CODEPAGE parameter of the function module GUI_UPLOAD.

aRs