IDOC missing CRLF when send to middleware

[Former Member]

Hi,

Could someone help me here,

SAP is sending an IDOC via trfc port to BPM (Middleware). IDOC file received at BPM is having one continuous string of data as a single record (Having no CRLF delimiter).

We need IDOC to be sent with CRLF delimited when send from SAP, could you please suggest me what settings need to be changed from SAP side for this to happen.

(I am an EDI Consultant having the basic knowledge of SAP and its integration.... )

Thanks in advance for your answers!!!

Regards,V

[Former Member]

Hi,

Could someone help me here,

SAP is sending an IDOC via trfc port to BPM (Middleware). IDOC file received at BPM is having one continuous string of data as a single record (Having no CRLF delimiter).

We need IDOC to be sent with CRLF delimited when send from SAP, could you please suggest me what settings need to be changed from SAP side for this to happen.

(I am an EDI Consultant having the basic knowledge of SAP and its integration.... )

Thanks in advance for your answers!!!

Regards,V

[Jelena_Perfiljeva]

It doesn't seem to be an ABAP question. I can only suggest to ask the Basis administrator. There might be something in the RFC connection or gateway or something along those lines. Or maybe it's not even SAP but the recipient system's problem.

I've never heard of such issue and, as evidence suggests, in tRFC port lines do have CRLF.

[Former Member]

Thanks Jelena for your reply.. I have checked in SM59 for RFC settings and everything is fine , both SAP and BPM adapters are using Unicode type and Idoc SAP Type Release 4.x... When i tried to google it, something which needs to be done from SAP end while sending an IDOC ... Once IDOC is created , an ALE Functional Module is called to streamline the data and converts it to Binary while sending it via RFC... During that conversion, either the CRLF is stripped off or not being sent...

Please correct me if i am wrong anywhere...

[Jelena_Perfiljeva]

What kind of IDoc are we talking about exactly? In general, in case of the RFC port there is nothing special to be done by SAP customer other than configuring RFC connection. Naturally, there must be some ABAP program or function involved in sending the data, but this should not be the customer's concern.

If you believe there is an error in the standard SAP program then I'd suggest to open an incident with SAP.