Losing 0x0D in Content Conversion of a file receiver communication channel

[Former Member]

Hi everyone, I have a file to file scenario in which I receive an XML like this:

<MT_IDOCS>

<IDOCS>

<IDOC>E2EDK14 10000000000000000010000020000010200600

E2EDK14 10000000000000000010000030000010200712

</IDOC>

</IDOCS>

<MT_IDOCS>

Actually this is just to give you an idea, but inside the IDOC tag I have a whole IDoc with the flat file structure that is going to be processed by with program RSEINB00. The incoming file has characters 0x0D and 0x0A between both lines, which is correct and is the desired format for program RSEINB00.

But when I download this XML using content conversion, the resulting file has lost the 0x0D character, it still has the 0x0A, but all 0x0D are gone.

The content conversion is set like this

Recordset structure IDOCS

IDOCS.fieldSeparator $$$$$$

IDOCS.endSeparator '0'

(I don't know exactly why they did it that one...anyway only 1 IDOCS tag is expected). The I have to extract the exact bytes from inside the IDOC tag and download them to a file. Is it possible to handle it from the content conversion? Thanks!

[kenny_scott · Accepted solution]

Hi Pablo,

maybe the problem relates to the file encoding you have specified in the Communication Channels. Maybe the file is being picked up from a Windows system which uses Carriage Return (CR) in conjunction with the line feed character ( LF) to indicate

the end of an ASCII text file. The hex code 0D0A. Whereas the receiver system maybe a Unix systems which uses only LF (0A).

-

---

The module

ConvertCRLFfromToLF

using parameter value

LFtoCRLF

may resolve this

e.g.,

see the 'Example' SAP online help -

[Adapter Framework Module Interfaces|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/32/43d84072378031e10000000a1550b0/content.htm]

[Former Member]

Hi! I solved the problem with a work around. I guess the suggested module would probably help, but the main problem was that the file was passing through many mappings, so I removed some of them and now there's only one Java Mapping that does everything.