cancel
Showing results for 
Search instead for 
Did you mean: 

Files from EBCDIC environment gets a hash sign as EoL in SAP ECC6.0

Former Member
0 Kudos

Hi,

We are having an external warehouse system and a home made "integrator" running in a EBCDIC partition on a AS/400. The "integrator" put files on the file system, as a shared file area, of the SAP ECC6.0 system which is running in an ASCII environment.

When looking at the file "on the AS/400" the end of all lines in the files looks fine. When looking at the HEX notation of the file all lines end with 0D25 (is EBCDIC for CR/LF).

When looking at the file in AL11 all lines end with a #.

We also have a temporary system that is just on ASCII but not upgraded, ie still on 46C. There the end of the lines looks fine in AL11. We have even copied a file from the ECC6.0 environment to the 46C environment to be sure we have the exact same file.

As ECC6.0 don't play well with EBCDIC my thought is that this is the reason that we get the #-signs as EoL. Could that be true? If so, what can we do to fix it, besides change the codepage on the "integrator"-environment.

best regards,

Glenn Karlsson

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi Glenn,

This is kind of known and should be repaired in higher releases. A potential solution might be the program attached to note 788907 - Lines end with '#' in a file created in Windows, although your file was not created in windows.

Watch out, though: The program currently attached only handles ASCII files. We are working on a new version that is also capable of EBCDIC files like in your environment and will tell you in this thread as soon as it is available.

HTH,

Thomas

Edited by: Thomas Obermeier on Mar 9, 2009 11:03 AM

0 Kudos

Hi,

Note 788907 was updated. Preferably you change your integrator to open files with mode "crln=no".

Best regards,

Thomas

Answers (0)