issue in content conversion

[#1]

Hi,

Am trying to convert Big-Endian content format (file to file scenario with content conversion in both adapters) with sender file adapter to utf-8 format file which is going to upload into SAP.

but am getting an issue while converting Big-Endian content...if you see input file...its converting in wrong format as the content is generating with blanks and so...fixedfiledlengths are showing wrong data.

anybody please help me what is going wrong...

-Kishore

[zameerf]

Hi,

>>file to file scenario with content conversion in both adapters

is there any mapping or other run time requirements for this interface?

if not, just go for only ID objects and do a pass through file transfer.

Regards,

Zameer

[Former Member]

Zameer,

there is no mapping involved...i can even pass through with file protocol but while placing in SAP, file content is again showing junk characters and hence am trying through content conversion...

[zameerf]

Hi,

once you place the file in target directory, how is the file processed by SAP? where you able to see the same file as in source once you place in target directory? or you see junk characters there?

[Former Member]

Zameer, once i place file in SAP, am not able to process the file and i see junk characters...but if i exctract the same file through filezilla to my local directory, i can see the data...not sure how can handle this...

[zameerf]

normally in pass through scenario, the file content will not be altered.

can you share a sample output file which has the junk chars?

[Former Member]

[Former Member]

can anybody help me on this...

[zameerf]

Do you see this junk char only in al11 transaction?

when you open the file directly from file system how is the content?

[Former Member]

I see this junk char in al11 tcode...if i download the same from system...file is OK and no issues...

[zameerf]

in receiver file adapter, do you have file type as Binary in processing parameters?

can you try changing this to Text?

may be you can try setting the encoding as UTF-8 as well and see if that helps

this looks like unicode issue

[Former Member]

Thats right...this is unicode issue...

I have tried to change setting to UTF-8 but then am getting parser issue during conversion in receiver adapter level...

please suggest...

[zameerf]

did you try with only file type as text? without any encoding..

also please confirm if your are using any FCC here, i assume you are using pass through scenario?

[Former Member]

here 2 things...i can simply pass through file but since am getting encoding issue am trying to sort out through FCC in which also am getting similar error.

let me try only file type as text without encoding...will update you. thanks...

[Former Member]

Hi,

I am not sure but can you please try with encoding as UTF-16BE in sender File adapter?

http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm

■       UTF-16BE

16-bit Unicode character format, big-endian byte order

Thanks,

Beena

[Former Member]

I have tried this...but am getting error as "Transform: failed to execute the transformation: com.sap.aii.af.sdk.xi.adapter.trans.TransformException: Error converting Message: java.lang.Exception: Exception in XML Parser (format problem?):org.xml.sax.SAXParseException: Content is not allowed in prolog.'; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):org.xml.sax.SAXParseException: Content is not allowed in prolog"

[Former Member]

This message was moderated.

[Ryan-Crosby]

Hi Kishore,

Have you tried setting the sender encoding as text and using the TextCodepageConversionBean to convert to utf-8 without the use of FCC parameters?

Regards,

Ryan Crosby

[Former Member]

Hello Ryan,

I have not tried that but in sender adapter, i have changed the file format to UTF-8 in sender adapter configuration parameters. let me try the way you have suggested and also please confirm if any change required in receiver file adapter properties...

Thanks

Kishore

[Ryan-Crosby]

Hi Kishore,

I have never had this requirement so I cannot be sure but I believe you only need to set your encoding as type text with 'UTF-16BE' as your codepage and then add the adapter module to specify that you want to convert it to utf-8.  Then remove all of your FCC parameters and have it drop the file where you wish for the receiver.

Regards,

Ryan Crosby