topic Re: JSON encoding in Application Development and Automation Discussions

JSON encoding

former_member570046 — Tue, 23 Aug 2016 05:46:58 GMT

Hello all

I need to send JSON data to a customer, for example :

[{"PERNR":"00000001","NACHN":"Smith","VORNA":"Jürgen"}]

This data will be sent and received via flat files, and also via OData in SEGW (SAP Gateway Builder). So I assume the name "Jürgen" for example would need to be encoded ..

Questions:

1) Do I need to encode this to UTF-8 ?

2) If so, how do I do this in ABAP ?

(If seen cl_abap_conv_out_ce=>create( encoding = '4110' ) - but this results in an XSTRING ? )

Thanks in advance !

Jan

Re: JSON encoding

larshp — Tue, 23 Aug 2016 06:00:21 GMT

see

Re: JSON encoding

Sandra_Rossi — Tue, 23 Aug 2016 06:01:12 GMT

Of course it's XSTRING, how could it be stored another way? If you're in a Unicode system, characters in String or C are always stored in UTF-16, cannot be anything else (more exactly UCS-2).

Re: JSON encoding

retired_member — Tue, 23 Aug 2016 06:10:39 GMT


 cl_abap_conv_out_ce=>create( encoding = '4110' )

A more convenient class is CL_ABAP_CODEPAGE, e.g.:

DATA: str TYPE string,

xstr TYPE xstring.

xstr = cl_abap_codepage=>convert_to(

source = str

codepage = `UTF-8` ).

You get a codepage representation of a character string in an xstring. Method convert_from does it vice versa.

If you transform ABAP data with call transformation you can decide whether the result is a string or an xstring, where xstring is the recommended type.

As Sandra said, ABAP characters are stored internally in UCS-2. But the standard transfer format for XML and JSON is UTF-8. Therfore, it makes sense to convert the internal ABAP representation into UTF-8 in an xstring.

Horst

Re: JSON encoding

former_member570046 — Tue, 23 Aug 2016 06:20:12 GMT

Thanks Sandra, I understand that the result is XSTRING but my challenge is to now represent this as JSON data in an OData response - which I thought could only be of type STRING - therefore ü would be "&#252" or something similar ?

Re: JSON encoding

retired_member — Tue, 23 Aug 2016 06:41:44 GMT

which I thought could only be of type STRING

What makes you think so?

OData is itself based on XML and/or JSON. You create the files as strings on your platform, but you send them around as UTF-8.

In fact I don't think you have to care at all. "Jürgen" should be translated to the appropriate UTF-8 representation by the OData framework, your'e using.

Horst

Re: JSON encoding

former_member570046 — Tue, 23 Aug 2016 06:51:09 GMT

Excellent, thanks for the confirmation - much appreciated !

Re: JSON encoding

retired_member — Tue, 23 Aug 2016 06:55:49 GMT

Of course, you have to test it