topic Re: Split issue in Application Development and Automation Discussions

Split issue

AJeB — Tue, 08 Aug 2023 02:51:28 GMT

why the last character is missing after split ?

this is just a sample.

DATA(text) = 1234567890,abcde.

SPLIT text AT ',' INTO res1-num res2-letter.

The length of the res1-num is 10 but after split it only get the 123456789

output:
res1-num = 123456789 "0 or last number is missing after split"
res2-lettter = abcde "resutl is correct"
___________________________________________________________________________________________
Code from debug

Re: Split issue

xiswanto — Tue, 08 Aug 2023 03:20:21 GMT

this quick test I've done contradicted with your statement which the last character before split is missing, are you sure your receiving field is defined correctly?

DATA(z_a1) = '1234567890,abcde'.
SPLIT z_a1 AT ',' INTO DATA(z_a2) DATA(z_a3).

Re: Split issue

AJeB — Tue, 08 Aug 2023 03:30:04 GMT

yes it is defined correctly the length is correct, but I don't know why it is passing up to 9 characters only

the res1-num and res2-letter is from the structure, I checked the debug and the res1-num is receiving a wrong data

Re: Split issue

TarunTakshak6 — Tue, 08 Aug 2023 05:28:53 GMT

Hi bolivs22,

checked in debug getting exact output

DATA(text) = '1234567890,abcde'.
SPLIT text AT ',' INTO data(res1-num) data(res2-letter).
WRITE : res1-num,res2-letter.

Re: Split issue

AJeB — Tue, 08 Aug 2023 05:30:44 GMT

weird its not working on me

Re: Split issue

TarunTakshak6 — Tue, 08 Aug 2023 05:34:25 GMT

bolivs22 share screenshot of debugging screen

Re: Split issue

AJeB — Tue, 08 Aug 2023 05:39:15 GMT

Here the <fs_data> is P000177154 but after the split it only pass the P00017715
Note: value of <fs_data> is coming from application server

Re: Split issue

matt — Tue, 08 Aug 2023 07:20:10 GMT

bolivs22

What is the full hex for WA_POCNF-ODOO_PO? And the first 12 characters of <FS_DATA>?

Re: Split issue

AJeB — Tue, 08 Aug 2023 07:31:57 GMT

the full hex of wa_pocnf-odoo_po is FFFE500030003000300031003700370031003500

this is the hex of the first 12 characters of <fs_data> -> P000177154 = FFFE5000300030003000310037003700310035003400

Re: Split issue

gaddamarunkumar — Tue, 08 Aug 2023 07:40:58 GMT

Hi Aaron,

can I know the data declaration of the res1-num?

Re: Split issue

AJeB — Tue, 08 Aug 2023 07:43:30 GMT

Hi gaddamarunkumarreddy
Its just a sample please see the answer in the comment below

Re: Split issue

AJeB — Tue, 08 Aug 2023 07:45:53 GMT

its just a sample I can't give you a data declaration for that
please see the reply from taruntakshak, I have debug screen shot

Re: Split issue

Sandra_Rossi — Tue, 08 Aug 2023 08:06:11 GMT

especially because dot and comma look very similar in the forum, Please edit your question (Actions>Edit), select your code and press the button [CODE], which makes the code appear colored/indented, it'll be easier for people to look at it. Thanks!

, and .

versus

, and .

dot and comma look very different in the two situations.

Re: Split issue

Sandra_Rossi — Tue, 08 Aug 2023 08:09:36 GMT

bolivs22

FFFE is the invisible character for UTF-16LE (little endian) Unicode Byte Order Mark (BOM). You should not include it in your text variable. The exact solution depends on what you do to load the text. Or if you don't want to know how it works, just remove this first character.

That's the reason.

Re: Split issue

matt — Tue, 08 Aug 2023 08:15:40 GMT

Try this program:

REPORT.

DATA: BEGIN OF test,
        field1 TYPE char10,
        field2 TYPE char10,
      END OF test.

DATA(input) = 'P000177154,127007'.

SPLIT input AT ',' INTO test-field1 test-field2.

WRITE: test-field2, test-field2.

Do you get the same issue?

Re: Split issue

AJeB — Tue, 08 Aug 2023 08:52:17 GMT

reply from sandra.rossi

FFFE is the invisible character for UTF-16LE (little endian) Unicode Byte Order Mark (BOM). You should not include it in your text variable. The exact solution depends on what you do to load the text. Or if you don't want to know how it works, just remove this first character.

thanks for the idea
__________________________________________________________________________________________

already fix by changing the file

I changed the csv that I uploaded from the application server from CSV UTF8(Comma Delimited) to CSV (Comma Delimited) after that the HEX FFFE is not showing

Re: Split issue

matt — Tue, 08 Aug 2023 09:20:44 GMT

Darn, missed that!

Re: Split issue

Sandra_Rossi — Tue, 08 Aug 2023 10:12:27 GMT

Thx for feedback and the good solution.