File content conversion Testing

I would like to know method to test File Content Conversion to ensure it is read into the correct structure.
Thanks

You can do that by checking in the RWB->message monitoring, XI calling the file content conversion module.
If you have any doubts using the File Content Conversion, check
http://help.sap.com/saphelp_nw2004s/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm

Similar Messages

J2SE XML to Flat File Content Conversion

Hi
I've currently got a scenario which sends a flat file to the integration server, it gets mapped and sent to a receiver adapter on a deployed j2se engine.
I'm now trying to convert the xi-xml structured file to a flat file again on the j2se side (the same flat file format it originally had).
My original flat file looks like this -
477
477=AA1
My xml file looks like this -
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ResultMessage xmlns:ns0="urn:xxxx-com:a_test_j2se_filetofile">
<Item>
 <field1>477</field1>
</Item>
<Item>
 <field1>477</field1>
 <field2>AA1</field2>
</Item>
</ns0:ResultMessage>
I am using these content conversion parameters:
xml.addHeaderLine=0
xml.fieldSeparator==
xml.endSeparator='nl'
I get this error on the integration engine (sxmb_moni):
Error while sending by HTTP (error code: 500, error text: Internal Server Error:java.lang.NullPointerException) (See attachment HTMLError for details)
and the j2se adpater log says this:
17:16:32 (4120): Message "13b9d644-54c9-4ffb-0c40-db4c14458d77" of type "application/xml", kind "B" received
17:16:32 (4124): Parsing XML message
17:16:32 (4131): ERROR: Message processing failed with "java.lang.NullPointerException"
What am i missing?

So, now... I did a test configuration in XI and sent your test-payload...it worked.
The J2SE adapter configuration:
File adapter java class
classname=com.sap.aii.messaging.adapter.ModuleXMB2File
version=30
mode=XMB2FILEWITHCONVERSION
#Adress for XMB endpoint -
XI.httpPort=8111
XI.httpService=/file/receiver
#File Adapter specific parameters -
file.createDir=1
file.targetDir=c:/transfer/inbound
file.targetFilename=xmboutput.txt
#file.writeMode=append
#file.writeMode=overwrite
file.writeMode=addCounter
file.counterMode=immediately
#file.counterMode=afterFirst
file.counterSeparator=_
file.counterFormat=00000
file.counterStep=1
#File Content Conversion specific parameters -
xml.addHeaderLine=0
xml.fieldSeparator==
xml.endSeparator='nl'
And here the configuration of the receiver communication channel in the integration directory:
Adapter Type: XI
Receiver
Transport-Protocol: HTTP 1.0
Message-Protocol: XI 3.0
Adapter-Engine: Integration Server
Adressing-Type: URL Address
Target Host: <yourJ2SEip>
Service Number: 8111
Path Prefix:http://<yourJ2SEip>:8111/file/receiver
Authentication Data
Logon data for non-SAP systems
User
Password
That's it... sent your payload and got the wished result:
477
477=AA1
Regards,
Heinrich

File Content Conversion -All the input content was not shown in output file

Hi Experts,
In my scenario, I need to send data from .XML file to .txt file, using File Content Conversion at Receiver communication channel. This is File to File scenario.
This is my Input xml file.
<ns:FILEINPUT_MT xmlns:ns="http://File2FileTest">
<RECORD>
 <Row>
 <FirstName>Susie</FirstName>
 <LastName>Tony</LastName>
 <City>London</City>
 <Country>UK</Country>
 </Row>
</RECORD>
</ns:FILEINPUT_MT>
Processing Parameters
Target Directory = C:/Test
File Name Scheme = xi_output.txt
File Construction Mode = Add Time Stamp
File Type = Binary
Content Conversion Parameters
Recordset Structure : RECORD
RECORD.endSeparator = nl
RECORD.fieldSeparator = ;
After Activate and providing the input xml file, xi_output.txt file was generated. But the file content was shown only with Susie i.e. with First Name only. I need xi_output.txt file should have all the four fields (FirstName, LastName, City, Country)
Could some one help me to resolve the issue?
Thanks in advance
Sree

Check these blogs...Might help you.
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
/people/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
Link for SAP Help
http://help.sap.com/saphelp_nw2004s/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm

Issue w/ File content conversion (Receiver side)

Folks, there seems to be an issue with the conversion. I've read several of threads on this forum, but none helped! Although the file is generated with 8 bytes there seems to be nothing in the file.
However when 'File' message protocol is used, the xml file is generated correctly as expected. All my other settings are fine.
Here is the scenario:
1) created Message type -
MTX
..Material
..BaseUnit
..MatGrp
..Division
2) comm. channel created for -
Transport protocol: File (NFS)
Message protocol: File content conversion
Recordset Structure: MTX
parameters:
    MTX.fieldSeparator: ,
    MTX.endSeparator: 'nl'
Should recordset struc. and parameters have 'ns0' prefix, i.e.,
Recordset Structure: ns0:MTX
parameters:
    ns0:MTX.fieldSeparator: ,
    ns0:MTX.endSeparator: 'nl'
What esle is missing? any thoughts are welcome.
Thanks and appreciate your responses.

Hi ABAP JUNOON,
Could you please create another Test scenario and
try
MTI_XXX
     - DATA(0..unbounded)
         - fields?
i mean, without redundant RS(Record Structure).
and use
Transport protocol: File (NFS)
Message protocol: File content conversion
Recordset Structure: DATA.
it will written the complete output file.
some people create the Reciver data type for test scenario's as follows.
MTI_XXX
   -RS
     - DATA(0..unbounded)
         - fields?
i mean with redundant RS
in this case file is generated, but nothing will be appear.
so plz take care while creating the reciver data type with FCC.
and the following case also will work i.e
MTI_XXX
   -RS
     -Header(0,1)
         - fields?
     - DATA(0..unbounded)
           - fields?
     - Trailer(0,1)
         - fields?
Regards
Mahesh.

File Content Conversion Error

Hello,
I have Async. File receiver scenario in which the following is the XML message structure. This is received by the file adpater.
<ns1:MT_Info_File xmlns:ns1="urn:http://freemanco.com/xi/info_list">
 <TYPE>
 <FileItem>
 <FileName>DD11022007</FileName>
 </FileItem>
</TYPE>
<DATA>
 <LineItem> <LineEntry>234567891234567890123456789012345678901234567890</LineEntry>
 </LineItem>
 <LineItem>
<LineEntry>95473523647586969587265245437586979798376524253586</LineEntry>
 </LineItem>
<DATA>
<LineItem</ns1:MT_Info_File>
I want to write only folowiing DATA structure to file. I do not want to wite contents of TYPE structure
<DATA>
 <LineItem> <LineEntry>234567891234567890123456789012345678901234567890</LineEntry>
 </LineItem>
 <LineItem>
<LineEntry>95473523647586969587265245437586979798376524253586</LineEntry>
 </LineItem>
<DATA>
In the receiver file adpater I have follwoing File content conversion parameters.
RecordSetStructure: DATA,LineItem,*
*.addHeaderLine 0
*.fieldFixedLengths 301
*.fixedLengthTooShortHandling Error
*.endSeparator nl
LineItem.fieldSeparator nl
DATA.fieldSeparator nl
While testing I got following error. Looks like it is expecting some values for FileItem element in the XML.
Error Attempt to process file failed with java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)'
Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)'
Error Exception caught by adapter framework: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)'
Error Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)'.
How to resolve this issue? I appreciate your help.
Thank you,
Balaji

Balaji,
I would suggest to remove FileItem and LineItem in your receiver datatype. They are increasing the hierarchy of your content conversion. If you do that then you will have
<ns1:MT_Info_File xmlns:ns1="urn:http://freemanco.com/xi/info_list">
<TYPE>
<FileName>DD11022007</FileName>
</TYPE>
<DATA><LineEntry>234567891234567890123456789012345678901234567890</LineEntry>
<LineEntry>95473523647586969587265245437586979798376524253586</LineEntry>
<DATA>
</ns1:MT_Info_File>
Then in content converstion give this parameters:
Record structure : TYPE,FileName,DATA,LineEntry
TYPE.fieldfixedlengths : 0
FileName.fieldfixedlenghts:0
DATA.fieldfixedlenghts:0
LineEntry.fieldfixedlengths:301
LineEntry.endSeparator:'nl'
Then it should work. Also you can use FileName in your variable substituition. Also please see this weblog on how to use FileName in variable substitution:
/people/sravya.talanki2/blog/2005/08/11/solution-to-the-problem-encountered-using-variable-substitution-with-xi-sp12
If you dont want to remove FileItem and LineItem then add these also in your content conversion. Then the parameters would be:
Recordset: TYPE,FileItem,FileName,DATA,LineItem,LineEntry
TYPE.fieldfixedlengths : 0
FileItem.fieldfixedlengths:0
FileName.fieldfixedlenghts:0
DATA.fieldfixedlenghts:0
LineItem.fieldfixedlengths : 0
LineEntry.fieldfixedlengths:301
LineEntry.endSeparator:'nl'
Regards,
---Satish

File content conversion sender adapter

Hi Friends,
I am doing File to IDoc scenario.
I am using File Content Conversion for File Adapter.
My structure look like this
MT_File
HEADER1 1..1
--header1
-- header2
HEADER2 1..1
--header3
DETAILS 1..unbounded
--details1
--details2
--details3
TRAILER1 1..1
-- trailer1
TRAILER2 1..1
-- trailer2
----trailer3
In File Content conversion parameeters..
Document Name :MT_File
Document Namespace :urn:test:FileFcctoIdoc
RecordSet name :
RecordsetStructure :HEADER1,1,HEADER2,1,DETAILS,*,TRAILER1,1,TRAILER2,1
RecordSet Structure: Ascending
RecordSet Per message : *
Key Field Name :header1,header3,details1,trailer1,trailer3
ignoreRecordsetName     : true
HEADER1.fieldNames      :header1,header2
HEADER1.keyFieldValue      : H1
HEADER1.fieldFixedLengths :5,10
HEADER1.endSeparator   :'nl'
HEADER2.fieldNames             :header3
HEADER2.keyFieldValue         : *D
HEADER2.fieldFixedLengths     :5
HEADER2.endSeparator         :'nl'
DETAILS.fieldNames               :details1,details2,details3
DETAILS.keyFieldValue         : 3
DETAILS.fieldFixedLengths     :5,5,5
DETAILS.endSeparator         :'nl'
TRAILER1.fieldNames               :trailer1
TRAILER1.keyFieldValue         : *S
TRAILER1.fieldFixedLengths     :5
TRAILER1.endSeparator         :'nl'
TRAILER2.fieldNames               :trailer2,trailer3
TRAILER2.keyFieldValue         :SE    TRAILER2.fieldFixedLengths    :5,5
TRAILER2.endSeparator         :'nl'
File is :
H1hh1hhhhhhhhh2
*Ddd*
Xddd1dddd2dddd3
Xddd4dddd5dddd6
Xddd7dddd8dddd9
*Sss*
SEKss2
in RWB, Channel CC_FILE_Sender_FccDemo: Empty document found. Proceed without sending message
I think the problem is in FCC paramters..
Could please have a look and correct me
Regards
Ram

Ram,
The problem which i can see is your key field values in your test file. Remember you should have the key field value in each new line at the same place.
For example you have given your text file as shown below...
File Given By You is :
>H1hh1hhhhhhhhh2
>*Ddd *
>Xddd1dddd2dddd3
>Xddd4dddd5dddd6
>Xddd7dddd8dddd9
>*Sss *
>SEKss2
Compair the above file with the below one..
>H1hh1hhhhhhhhh2
>*Ddd *
>Xddd1dddd2dddd3
>Xddd4dddd5dddd3
>Xddd7dddd8dddd3
> *Sss *
>SEKss2
If you notice, for details I have given key field value 3 in each line & at same place.
One more thing just use the KeyFieldName only one ( just follow the same blog which I have given, to understand how to use the KeyFieldName )
e.g.
Document Name :MT_File
Document Namespace :urn:test:FileFcctoIdoc
RecordSet name :
RecordsetStructure :HEADER1,1,HEADER2,1,DETAILS,*,TRAILER1,1,TRAILER2,1
RecordSet Structure: Ascending
RecordSet Per message : *
Key Field Name : KF
Regards,
Sarvesh

File Content Conversion - Error in keyfield Value

Hello experts,
I am doing file content conversion for a file to file scenario. The input file is a csv file which is converted to xml using the file content conversion. The key field of input file is used for implementing conversion.
While testing the FCC, I noticed that if the keyfield value is wrong for a record in the file, the record is ignored altogether without throwing any errors or warnings. Is there any way to notify if any records have been ignored as a result of incorrect keyfield value??
Thanks in advance!
RR

There seems to be NO way to handle it in FCC.
File Content Conversion - Key Field Value
u can think of work arounds by handling it in mapping....
-santosh.

Need Help in Sender File Content Conversion

Hi All,
I request your expert advice on Sender File content Conversion. I need to process the below pasted file. I was able to achieve this by keeping a offset of 6 in Sender PI File Adapter (PI 7.1) to ignore first 6 lines and used a Unix script to remove last line"END OF REPORT".
Now my new requirement is I need to capture the date "DECEMBER 2009" from line 3. How can I do this. I have set offset as 6 so Adapter will start processing from line 7. If I don't set offset Interface fails. Please suggest. Thank you.
ABC LAB            XYZ LIMITED"
                   TRIAL BALANCE"
                   FOR THE PERIOD ENDED DECEMBER 2009"
"TEST Bank","101000",-1589365.58,0.00,738295.08,0.00
"TEST Bank Clearing A/c","101200",0.00,0.00,14848018.55,0.00
"TEST Bank Sweeps","101250",104315957.19,0.00,7571985482.08,0.00
"TEST Receipts","101260",0.00,0.00,19788596.15,0.00
"TEST Corporate Deposits","101270",-7776629.87,0.00,-135914980.50,0.00
"SHARES","00SH",0.00,0.00,-7869890086.22,0.00
"END OF REPORT"

Dear Phani,
Please go through the below blogs:
File content conversion sites
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Please see the below links for file content conversion..
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter - FCC
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter - FCC
File Content Conversion for Unequal Number of Columns
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns - FCC
Thanks,
Satya

Error whil doing File Content Conversion

Hi all,
I had configured a sender for File Content Conversion and I am getting the follwoing error.
Sender Adapter v1014 for Party '', Service 'bs_xml_sender':
Configured at 05:39:05 2007-04-27
Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Format error in 'xml.recordset' argument: incomplete structure (name,number) pair.
Any ideas why I am getting this error.

Here is the detailed error message.
"Messages:16:40:41 Start of test
- Cannot produce target element /ns:mt_receiver/PO_NUM. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
16:45:01 End of test
16:45:10 Start of test
- Creating Java mapping com/sap/xi/tf/_mm_Sender_Receiver_
- Loaded class com.sap.xi.tf._mm_Sender_Receiver_
- Call method execute of the application Java mapping com.sap.xi.tf._mm_Sender_Receiver_
- *** START APPLICATION TRACE ***
- Document start
- Start tag [ns:mt_receiver]
- Add raw attribute [ xmlns:ns="http://xml2xml"]
- Cannot produce target element /ns:mt_receiver/PO_NUM. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
16:45:12 End of test

File Content Conversion Removes Leading Blank/Space

I'm having a problem where file content conversion is trimming leading blanks/space/whitespace from fields when reading in the inbound file. I've seen where people have posted that you need to use fieldContentFormatting to prevent content conversion from stripping the leading/trailing whitespace. I added that parameter to my list (see below example) but it still appears to be trimming the leading whitespace. Look forward to hearing your thoughts. Here are the details:
I'm using fixed length file content conversion for Sender File Adapter (SP15). I have the following parameters set:
Document Name = MaterialData
Recordset name = item
Recordset Structure = MaterialLine, 1
I have:
MaterialLine.fieldNames = matno_external, mat_description
MaterialLine.fieldFixedLengths = 40, 40
MaterialLine.fieldContentFormatting = nothing, nothing
The following is the input file (notice spaces prior to second occurrence of material numbers)
ZED00000001 AIMS LIGHT A
ZED00000001 AIMS LIGHT B
ZED00000002 AIMS SWITCH A
ZED00000002 AIMS SWITCH B
ZED00000003 AIMS SEMICONDUCTOR A
ZED00000003 AIMS SEMICONDUCTOR B
The following is the source XML after file content conversion from SXMB_MONI (note spaces no longer exist in matno_external tag).
<?xml version="1.0" encoding="utf-8" ?>
- <ns:MaterialData xmlns:ns="http://xxxxxxx.com/yyy/test">
- <item>
- <MaterialLine>
<matno_external>ZED00000001</matno_external>
<mat_description>AIMS LIGHT A</mat_description>
</MaterialLine>
</item>
- <item>
- <MaterialLine>
<matno_external>ZED00000001</matno_external>
<create_date>10/09/06</create_date>
<mat_description>AIMS LIGHT B</mat_description>
</MaterialLine>
</item>
- <item>
- <MaterialLine>
<matno_external>ZED00000002</matno_external>
<mat_description>AIMS SWITCH A</mat_description>
</MaterialLine>
</item>
- <item>
- <MaterialLine>
<matno_external>ZED00000002</matno_external>
<mat_description>AIMS SWITCH B</mat_description>
</MaterialLine>
</item>
- <item>
- <MaterialLine>
<matno_external>ZED00000003</matno_external>
<mat_description>AIMS SEMICONDUCTOR A</mat_description>
</MaterialLine>
</item>
- <item>
- <MaterialLine>
<matno_external>ZED00000003</matno_external>
<mat_description>AIMS SEMICONDUCTOR B</mat_description>
</MaterialLine>
</item>
</ns:MaterialData>

Thanks all for your attempts but I figured it out and wasn't this the biggest case of irony.
Here I was trying to prevent leading spaces from being trimmed in the loading of my file and my problem was that when I typed:
MaterialLine.fieldContentFormatting
I actually left a "blank" at the end of the "g" in Formatting. Apparently XI didn't like that and neither gave me a runtime or compile error. Anyway I found this and though I'd share in case anyone else encounters it. I removed the blank and all is working now.

File content conversion scenario-empty file

Hi all,
I am doing file content conversion for my sender flat file. And I want to generate XML file in my receiver location.When I check with test tab in my message map in IR , no structure gets generated in RESULT.Overalls cenario is working fine and message is processed successfully but empty file is getting generated in target directory.When I check the payload in message content in RWB communication channel monitoring,it's picking data correctly from the file.I am not getting what might have gone wrong with my message mapping in IR. It's not showing any syntax error.Even it's not generating target message structure in Results window of test Messsage mapping.Could you suggest what mistake might be there in message mapping.

Hi all,
I am getting this message in message monitor(SXMB_MONI).
com.sap.aii.utilxi.misc.api.BaseRuntimeException
thrown during application mapping
com/sap/xi/tf/_MM_Flat_content_conv_:
RuntimeException in Message-Mapping transformatio~
I am able to see the output structure in test window of message mapping in IR and communication channel monitoring is also showing successful message.
fcc parameters used are:
Header.fieldNames KEY,EMPID,NAME,COMPANY,PHONE
Header.fieldFixedLengths 1,4,20,15,12
Header.processConfiguration FromConfiguratiion
Header.keyFieldValue H
Detail.fieldNames KEY,COMPANY,LOCATION
Detail.fieldFixedLengths 1,15,10
Detail.processConfiguration FromConfiguratiion
Detail.keyFieldValue D
Please suggest the mistake in mapping
Edited by: Jaya on Mar 3, 2010 12:45 PM
Edited by: Jaya on Mar 3, 2010 12:47 PM

Encoding problem after File Content Conversion

Hi SAP gurus!
we're about exporting debitor data via PI into CSV files. Therefore we use a mapping to an intermediate structure. In the receiver file adapter a file content conversion is done into the target CSV format.
We have a lot of data with eastern europe characters. Right after the mapping, everything is fine. All characters are processed correctly. After the file content conversion, the files written on the target system contain "?" instead of the special characters.
Does anybody have any hint to fix this problem? We already tried to change the "file.encoding" parameter, but hasn't helped.
Thanks in advance for your support!
Cheers,
Matthias

Hello Satish,
thanks for your reply.
First, I have to explain, that the sender side isn't done by file adapter but IDoc adapter. So I cannot change the encoding on sender side.
Both on IDoc and file side, the data is ok. Only when inserting the file content converion, the files become corrupted.
Without using the FCC, tjhe target files are stored as UTF-8. When using FCC the files are stored as ANSI. (I tested this by opening the files in notepad and performing "Save As")
Do you have further ideas?
Cheers,
Matthias

File Content Conversion with Multiple structures

Here is the scenario
Legacy to XI -> XI to R/3 (App Server)
txt file and fixed length.
Test file
100WELCOME 0430000960603201321
2000000000040008000803
Table2
RecordType
PriorityCode
Destination
BankOrginNo
CreationDate
CretionTime
Spaces
Table2
RecordType
Destination
BankOrginNo
ReferenceCode
ServiceCode
RecordLength
CharactersPerBlock
PartialCompression
CompressionSpaces
Content Conversion Parameters:
Document Name: Details
RecordsetName : recordset
Recordsetstructure : Table1,1,Table2,*
Recordsetsequence: Ascending
RecordsetperMessage: *
Keyfieldname : KF
Kefieldtype : String(Case-Sensitive)
Table1.keyFieldValue :'1'
Table1.fieldFixedLengths:1,2,10,10,6,4,47
Table1.fieldNames :RecordType,PriorityCode,Destination,BankOrginNo,CreationDate,CretionTime,Spaces
Table2.keyFieldValue :'2'
Table2.fieldFixedLengths: 1,10,10,10,3,3,4,1,38
Table2.fieldNames:RecordType,Destination,BankOrginNo,ReferenceCode,ServiceCode,RecordLength,CharactersPerBlock,PartialCompression,CompressionSpaces
ignoreRecordsetName :true
When I am trying with first structure it is working fine, where as 2 structures it is not.
in the adopter monitoring it show it pics the file from Legacy(file adopter display green), where as SXMB_MONI it is not showing any thing.
can any body help on this do I need to maintain any other parameters for file content conversion.
Thanks
M

HI,
I can see that.
The number of characters in the file for TABLE2 is lesser then the number of field size given.
for eg. if the table2 fixed field length sum is 20 ,your file contains only 10 characters. Please give complete data for table2
Test file
100WELCOME 0430000960603201321
2000000000040008000803
Table2.fieldFixedLengths: 1,10,10,10,3,3,4,1,38
Ragards
vijaya
Message was edited by: vijaya kumari

'nl' Not Working for fieldSeparator in File Content Conversion

I have a receiver communication channel where I want to create a file with each field being a new line. The xml (Message Protocol: File) output looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:complus_receiver_messageType xmlns:ns0="http://graybar.com/test/complus_rec
eiver"><cp><myrequest>AAFADFASFADFADSFDASFADFAAA</myrequest><myheader>DELADV</myheader></cp></ns0:complus_receiver_messageType>
When I turn on Message Protocol of File Content Conversion, and follow the SAP documentation on the parameters, the 'nl' is getting sent literally.
- I have Recordset Structure of: cp
- I have content conversion parameters of:
cp.fieldSeparator 'nl'
cp.fieldNames myrequest,myheader
cp.addHeaderLine 0
My file output looks like this:
AAFADFASFADFADSFDASFADFAAA'nl'DELADV0001
Note that the 'nl' is not processing as a new line. Ideas?

Hi,
Receiver FileContent conversion params dosen't have fieldNames
cp.fieldNames myrequest,myheader
so why don't u remove this and try once again...
Recordset Structure of: cp
cp.addHeaderLine 0
cp.fieldSeparator 'nl'
Hope this weblog helps you...
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
Cheers,
Siva Maranani.

File content conversion on Sender Side

Hi,
I am doing file content conversion on sender side.when i am executing the scenario,i am getting the following error in sxmb_moni:
Invalid at the top level of the document. Error processing resource 'file:///D:/Documents and Settings/...............
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> DOC_HEADER ...
when i right click on the pyaload and select view source
its displaying the whole flat file with the following line at the beginning:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
i have given all the parameters correctly....
in sxmb_moni.....the error category is Mapping and the error id id EXCEPTION_DURING_EXECUTE
Please help me with this error.
thanks n regards,
anuradha

Hi !!
The best way to debug would be to add TRACE statements in your mappigs. In both Graphical and java Mapping.
Trace out the entire output of java mapping and see if this is the input that the next mapping expects.
For trace , http://help.sap.com/saphelp_nw04/helpdata/en/c8/98e7d5c1620642973565ea3dd319d1/content.htm
refr this links also
Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Name expected
unsported character error in message mapping
Re: HTTP to RFC Mapping error:com.sap.aii.utilxi.misc.api.BaseRuntimeException:
Exception com.sap.aii.utilxi.misc.api.BaseRuntimeException
Re: Outbound error
Re: mapping error
error in file to file
have a look at this weblog on how to test your mapping
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
Thanks !!!

File content conversion Testing

Similar Messages

Maybe you are looking for