cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with content conversion in File Receiver Adapter

0 Kudos

Hello, everybody.

I have a RFC-to-File scenario with file content conversion. Everything is working well except that my file is generated with 2 blank lines at the top of it.

The function module has 3 importing parameters (1 optional) and the file content comes from an internal table.

Is it caused by the function module parameters? If yes, how can I avoid this, once I really need them? If not, does anyone have any idea?

Thanks a lot,

Marcos.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi

In file content conversion parameters make sure that to write <Record>.Headerline = 0.

Regards,

srinivas.

Answers (2)

Answers (2)

VijayKonam
Active Contributor
0 Kudos

Open the generated file in any hexadecimal file opner or in a note pad check if this are blank lines or carriage return characters. It could be the data in the RFC table, which has got some carriage returns (enter keys) in tha data.

If you could let us know the destimation structure, some one would be able to hekp you.

VJ

justin_santhanam
Active Contributor
0 Kudos

Marcos,

Can u give us the target structure, it will be easy for us to suggest.

Best regards,

raj.

0 Kudos

Hi, Raj.

Here they are the function module parameters:

  • Importing parameters:

ICARRIER TYPE CHAR1

FPATH TYPE IPATH

IFILE LIKE VBAK-BNAME

  • Tables

IYLASDS_RECPT LIKE YLASDS_RECPT

The structure YLASDS_RECPT has only one field with a single line of the file. I am using this field as the <i>Recordset Name</i> inside file adpater parameters.

There is no mapping between RFC and FTP messages.

Thanks a lot,

Marcos.