Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

open dataset coversion problem and no entry found in database even if existing

Former Member
0 Likes
1,204

Tried with encoding UTF-8, same problem

c_split TYPE c VALUE cl_abap_char_utilities=>horizontal_tab.

Bukrs is missing a 0.

My other problem is that the data is existing in the custom table but unable to retrieve it.

Data type is character 10. no conversion exits.

Data class         APPL0

Size category      4

But when * is added as a suffix, it works. CA*

Thanks,

Conrad

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,167

solved

used

in TEXT MODE ENCODINg utf-8 for INPUT SKIPPING BYTE-ORDER mark.

forthe 2nd problem i just used select like for the spaces. though the data should be re uploaded to fix the spaces

5 REPLIES 5
Read only

Former Member
0 Likes
1,167

1st problem, when using non unicode, data is 2000#568615#717918#08162013#06172013#CA#3750#Php#BF1-0000000000000107#

2nd problem looks like the data was uploaded with spaces at the end.

Read only

FredericGirod
Active Contributor
0 Likes
1,167

Hi,

does your field GT_FILEDATA-BUKRS is CHAR 3 or CHAR 4 ??

regards

Fred

Read only

Former Member
0 Likes
1,167

From the first screen shot, it looks like your are reading a delimited file but not breaking the read string on the delimiter..  That will trash out your data...

Neal

Read only

mayur_priyan
Active Participant
0 Likes
1,167

Hi,

First check the length of BUKRS in the structure GT_FIELDDATA whether it is 3 or 4.

Else just use c_split TYPE c VALUE '#' , which is direct.

Second try select the value which you are searching through F4 help.

Read only

Former Member
0 Likes
1,168

solved

used

in TEXT MODE ENCODINg utf-8 for INPUT SKIPPING BYTE-ORDER mark.

forthe 2nd problem i just used select like for the spaces. though the data should be re uploaded to fix the spaces