on 08-20-2013 2:40 PM
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
Hi Kishore,
Have you checked the below blog and the reply of Deepak:
http://scn.sap.com/thread/1644363
In your sender file channel Specify the File Type Text.
Once you have selected Text, specify a code page under File Encoding. The default setting is to use the system code page that is specific to the configuration of the installed operating system. The file content is converted to the UTF-8 code page before it is sent.
Following are the values you can use. I think in ur case use UTF-16.
○ US-ASCII
Seven-bit ASCII, also known as ISO646-US, or Basic Latin block of the Unicode character set
○ ISO-8859-1
ISO character set for Western European languages (Latin Alphabet No. 1), also known as ISO-LATIN-1
○ UTF-8
UTF-8 (BC-ABA)
○ UTF-16BE
16-bit Unicode character format, big-endian byte order
○ UTF-16LE
16-bit Unicode character format, little-endian byte order
○ UTF-16
UTF-16 (BC-ABA), byte order
Regards,
Nabendu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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"
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
Hi,
are you converting csv to xml?
from the xml it looks like it is converting the header?
that is why no values are not coming in the xml.
check this
http://scn.sap.com/thread/1946048
Regards,
Muniyappan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I got you what you mean to say...but somehow am not able to see the values are in proper format due to content issue...for ex: first field am having lengh of 10 chars but if you see it is stopping with 4 if you see in XML file but when you see the source...blanks are coming in between and so it is taking only 4 chars...how to handle this...
Hi,
here i dont see any issue in FCC...if you see my first screenshot where "date" is the only char coming in for 10 chars and if you see the source file there are blanks which are occupying that length...which means file reading content is problem...i know source file update is useful but for the time being i could not update the same due to network issues...
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.