topic STRING_SIZE_TOO_LARGE in Application Development and Automation Discussions

STRING_SIZE_TOO_LARGE

former_member333481 — Sat, 13 Mar 2021 15:04:35 GMT

I am converting xstring to string value by using standard FM ECATT_CONV_XSTRING_TO_STRING. Since my file is large in size more than 2 GB hence the FM is producing short dump as the string size exceeds the maximum length.

Please suggest if there is any other way to convert large xtring value to string. We are getting the xtring from Middleware after decrypting the file.

Re: STRING_SIZE_TOO_LARGE

Sandra_Rossi — Sat, 13 Mar 2021 17:44:53 GMT

I guess you are decoding text encoded in UTF-8 (?)

Try to process it by chunks of 100000 bytes for instance. CL_ABAP_CONV_OBJ used to work well for that, with constructor parameter broken = 'R' to handle "broken characters" at end of chunks. Parameter INUSED of method CONVERT says exactly how many bytes were decoded (for instance 99997 to 100000) so that to start at the right offset for the next chunk.

I don't know if there's a successor of old CL_ABAP_CONV_OBJ.

See in the forum if there are examples for CL_ABAP_CONV_OBJ with parameter broken = 'R'.

Re: STRING_SIZE_TOO_LARGE

former_member333481 — Sat, 13 Mar 2021 17:49:57 GMT

Hello Sandra,

Thanks for the suggestion. Would you mind to send me the full code which need to be implemneted to handle this

Re: STRING_SIZE_TOO_LARGE

Sandra_Rossi — Sat, 13 Mar 2021 18:35:57 GMT

Please use the COMMENT button for comments, questions, adding details, replying to people, etc., ANSWER is only to propose a solution, dixit SAP text at the right of the answer area.

Re: STRING_SIZE_TOO_LARGE

Sandra_Rossi — Sat, 13 Mar 2021 18:38:33 GMT

See here .

Re: STRING_SIZE_TOO_LARGE

Sandra_Rossi — Sat, 13 Mar 2021 18:39:57 GMT

It was not difficult to find it by searching this:

"CL_ABAP_CONV_OBJ" "BROKEN = 'R'" site:sap.com