topic Re: # problem in AL11 in Application Development and Automation Discussions

# problem in AL11

Former Member — Fri, 04 Dec 2009 12:39:09 GMT

Hi,

May I know what is the cause that each character is split with hash # which saved in AL11?

What should I do so that not saved with # in AL11.

This happen when I do read data step in LSMW. However, display read data step not showing #. With this error, convert data step cannot perform.

The same lsmw object during 4.6c was ok but when in ecc6, this # problem come out.

###R#L#S#M#W#Z#F#I#_#Y#Y#C#U#S#T# # # # # #A#L#L#_#C#C#_#L#D# # # # # # #F#D#0#2#_#F#A#X#E#M#

Need advice from expert.

Thanks

Rgds

Re: # problem in AL11

Former Member — Fri, 04 Dec 2009 12:43:02 GMT

FAQ. The # could refer to the horizontal space tab. Please search you will find many threads as to how to replace it

Re: # problem in AL11

Former Member — Fri, 04 Dec 2009 12:49:23 GMT

Hi,

As per what i have noticed till date # in AL11 is equalant to a tab.

Regards,

surinder

Re: # problem in AL11

Former Member — Fri, 04 Dec 2009 12:52:50 GMT

If those aren't tabs, could it be a unicode issue?

Re: # problem in AL11

Clemenss — Fri, 04 Dec 2009 12:54:03 GMT

Hi,

after nearly 1000 posts and more than two years of participation in SDN it is really hard to believe that you never stumbled about the # hash character. ABAP alwas uses it to let the user know that there is a character that simply can not be displayed.

In debug mode, you may switch to HEX display to see what control character is really behind, e.g. horizontal or vertical tab, carriage return, linefeed, formfeed, bell or what know I.

Regards,

Clemens

Re: # problem in AL11

SuhaSaha — Fri, 04 Dec 2009 13:12:25 GMT

Hello,

What is the source of the file?

I know that in ABAP if you write a file in app. server IN BINARY MODE, the data are separated by '#' as mentioned by you.

I donot think that in this case the # is because of line feed, tabs etc. May be i am wrong though.

BR,

Suhas

Re: # problem in AL11

Former Member — Fri, 04 Dec 2009 13:21:36 GMT

Hi All,

As I explained, this is done in LSMW and in 4.6c the same LSMW object no such problem but in ecc6, hash problem.

If it is due to unicode, what I can get rid of this hash problem?

Again, the same object no such problem in 4.6c but now in ecc6, hash problem.

Thanks

Rgds

Re: # problem in AL11

Former Member — Fri, 04 Dec 2009 13:55:34 GMT

Hello,

It is related unicode in the newer ECC 6 version. You will have to use CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB to replace the # after the getting the data into internal table from READ DATASET .

Vikranth

Re: # problem in AL11

SuhaSaha — Fri, 04 Dec 2009 14:16:40 GMT

Hello Guys,

I think these are not tabs. Try writing a file to app. server in BINARY mode you will get the letters separated by #.(Atleast i get the files that way in my app server)

If you remove the # this is what the filecontents looks like:

RLSMWZFI_YYCUST	ALL_CC_LD	FD02_FAXEM

BR,

Suhas