topic Re: Unicode issue: in Application Development and Automation Discussions

Unicode issue:

Former Member — Mon, 30 Jun 2008 13:02:01 GMT

Hello friends,

I am getting unicode non- convertiable error, actually I have an internal table of char and to this internal table I need to assign a structure which contains all fields as char except one field which is dec...

how I can fix this issue ?

regards,

I guess field-symbols could solve my problem but not so much sure ...

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 13:04:47 GMT

FIELD-SYMBOLS: <fs_wa> TYPE ANY.

LOOP AT itab INTO wa.
  ASSIGN wa TO <fs_wa> CASTING TYPE c.
ENDLOOP.

Regards

Kannaiah

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 13:07:26 GMT

go to se 38

select radio button Attributes

click OK

then disable the unicode check active

I think this ll work

Thanks & Regards

vinsee

Re: Unicode issue:

naveen_inuganti2 — Mon, 30 Jun 2008 13:09:05 GMT

Hi......

convert decimal to char and proceed

Thanks.

Naveen.I

Edited by: Naveen Inuganti on Jun 30, 2008 6:39 PM

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 13:15:56 GMT

Hi,

Check this link:

http://help.sap.com/saphelp_nw04/helpdata/en/79/c5545bb3dc11d5993800508b6b8b11/content.htm

https://help.sap.com/saphelp_nw04/helpdata/en/79/c55488b3dc11d5993800508b6b8b11/content.htm

Regards

Adil

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 13:21:52 GMT

I did the following and now getting short dump:

FIELD-SYMBOLS: <fs_wa> TYPE ANY.

LOOP AT zidoc_post.

CLEAR: lt_raw_data.

ASSIGN zidoc_post TO <fs_wa> CASTING TYPE c.

lt_raw_data-line = <fs_wa>.

"lt_raw_data-line = zidoc_post.

APPEND lt_raw_data.

Runtime Error SYNTAX_ERROR is the shot dump:

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 13:24:22 GMT

hello Abdul, the links you have provided are not working ??

Re: Unicode issue:

former_member194669 — Mon, 30 Jun 2008 13:35:10 GMT

You need to use class cl_abap_container_utilities for this "type casting" will not work in unicode


LOOP AT zidoc_post.

CLEAR: lt_raw_data.

class cl_abap_container_utilities definition load.
call method cl_abap_container_utilities=>fill_container_c
     exporting
       im_value               = zidoc_post
     importing
       ex_container           = lt_raw_data-line
     exceptions
       illegal_parameter_type = 1
       others                 = 2.

APPEND lt_raw_data.

a®

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 13:41:47 GMT

Hello,

I have tried the class utilities way, and again got the same shot dump.

Error analysis

The following syntax error was found in the program /XYZ :

""LT_ZIDOC_POST" and "PT_RAW_DATA-LINE" are not mutually convertible in"

Regards,

Re: Unicode issue:

former_member194669 — Mon, 30 Jun 2008 13:48:18 GMT

Whether your PT_RAW_DATA-LINE is a character type variable.

if not declare a character variable

data : VLINE(1000) TYPE C.and use in place of PT_RAW_DATA-LINE

a®

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 13:54:11 GMT

Line is type LCHR .....

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 14:14:49 GMT

Hi,

since unicode there is no solution for this (for good reasons - aligment would be a real problem for most code pages).

Required procedure:

1) define a structure containing character fields only

2) Move your IDOC data to this structure

3) Call a mapping routine moving each component of the new structure to the final target structure (doing all neccessary conversions).

New structure and target structure may have the same component names - this makes dynamic programming a bit easier....

Kind regards,

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 14:42:25 GMT

I am trying something like this: but still did not work as expected:

data : VLINE(5000) TYPE C.

LOOP AT zidoc_post.

CLEAR: lt_raw_data.

ASSIGN zidoc_post TO <fs_wa> CASTING TYPE c.
lt_raw_data-line = <fs_wa>.
"lt_raw_data-line = zidoc_post.

CALL METHOD cl_abap_container_utilities=>fill_container_c

EXPORTING

im_value = zidoc_post

IMPORTING

ex_container = VLINE

EXCEPTIONS

illegal_parameter_type = 1

OTHERS = 2.

move VLINE to lt_raw_data-line.

APPEND lt_raw_data.

ENDLOOP.

Please note in zidc_post there is only one field which id dec, remaing all fields are tpye c.

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 14:44:25 GMT

fields in both tables shud hav same data type.plz check.

The internal table you are using shud hav the same order of fields as it is in data base. The internal table cant hav less no of fields from data base..

Check all this. ur problem will be solved.

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 14:56:20 GMT

As I said, I am haing one table which has all char field apart of one field which is dec...now I need to assign this table as following:

lt_raw_data-line = zidoc_post.

So Zidoc_post is the table I am getting need to assign to lt_raw_data-line . where as line is the field of type Lchar 5000 .

when I make all fields in zidoc_post char things work fine, but there one field is now price which is DEC....

So thats why I am getting unicode non-convertaible issue...

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 15:41:23 GMT

Hi,

as I posted above - you have to move that component by component. One single move for the whole structure is strictly forbidden even if only one field is numerical.

kind regards,

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 15:48:12 GMT

Hi holger,

I did not understand what do you mean by component to component, I have only having 1 field in the target str.

Regards,

Re: Unicode issue:

former_member194669 — Mon, 30 Jun 2008 15:57:13 GMT

Try to be simple.

Create another workarea (type) as same as zidoc_post and make it all fields are character.


LOOP AT zidoc_post.
  move fields by field to type (ie new type (work area)
  and only for DEC field
  write  zidoc_post-<decimal field> to type-character field of decimal
  move type-< new structure> to lt_raw_data.
  APPEND lt_raw_data.

a®

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 16:06:57 GMT

Hi, your suggstin could work: but then I need to change both str, if I extend the one, anyway i will give it a try, if it temp. solve me issue..... but I was more looking for Uni-code solution.... might be a keyword or they way you provided / suggest with class ??

I will be back after tring you suggestion anyway

Re: Unicode issue:

Former Member — Mon, 30 Jun 2008 16:43:43 GMT

Hi,

a®s got the point. Unfortunately there is no shortcut. Only field symbols may help a bit (ASSIGN COMPONENT OF STRUCTURE).

kind regards,