on 01-22-2010 7:53 AM
Dear Expert,
I am doing the File Content Conversion ...
Process in sender file adapter is working fine. However, when I check in the receiver folder, the XML file is incomplete after 4 records ...
The Flat File structure :
20100120;SAPQL0;0000000013380325
20100120;SAPQL0;0000000013380332
20100120;SAPQL0;0000000013380333
20100120;SAPQL0;0000000013380334
20100120;SAPQL0;0000000013380337
20100120;SAPQL0;0000000013380338
20100120;SAPQL0;0000000013380402
20100120;SAPQL0;0000000013391225
20100120;SAPQL0;0000000013394988
20100120;SAPQL0;0000000013416842
20100120;SAPQL0;0000000013420424
20100120;SAPQL0;0000000013420616
20100120;SAPQL0;0000000013420621
20100120;SAPQL0;0000000013420624
20100120;SAPQL0;0000000013420627
The XML result was truncated(incomplete) :
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_EDIFILE_LOG xmlns:ns0="http://zasp.edi.siemens.com/zedi/contentconversion">
<Record>
<EDIFILE>
<credate>20100120</credate>
<port>SAPQL0</port>
<idocnumber>0000000013380325</idocnumber>
</EDIFILE>
<EDIFILE>
<credate>20100120</credate>
<port>SAPQL0</port>
<idocnumber>0000000013380332</idocnumber>
</EDIFILE>
<EDIFILE>
<credate>20100120</credate>
<port>SAPQL0</port>
<idocnumber>0000000013380333</idocnumber>
</EDIFILE>
<EDIFILE>
<credate>20100120</credate>
<port>SAPQL0</port>
<idocnumber>0000000013380334</idocnumber>
</EDIFI
Please kindly suggest, which area should I check and correct...
Thank you very much expert.
Best Regards,
Y
By any chance, have you checked the "Number of records per message" indicator in the sender file adapter ? and set it to 4 records ? The XML output you show in your qn, is that from moni or from the actual file ?
Regards
Saravana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
can you please check the occurence it is "Unbounded"
Regards
Sateesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear All,
I believe that the file adapter has finished writing the file. Not sure, How to check whether the adapter is still working or not since from the SXMB_MONI, I see the mssage processing has been completed.
Further information
The data type structure :
1. DT_EDIFILE_LOG
1.1 Record --> occurence 1
1.1.1 EDIFILE --> occurence 1..unbounded
1.1.1.1 credate --> occurence 1
1.1.1.2 port --> occurence 1
1.1.1.3 idocnumber --> occurence 1
In content conversion parameters :
Recordset Name : Record
Recordset Structure : EDIFILE,*
Thank you very much for your suggestion.
Best Regards,
Y
Edited by: Yonisiwa on Jan 22, 2010 3:34 PM
Hi Yonisiwa,
Can you tell us the complete scenario?
What do you want your receiver file adapter to do?
Usually, we use content conversion at the receiver file adapter if you want to convert XML into text.
But, you say you are getting an incomplete XML file at the end.
If you want an xml file as the output, then you do NOT need to have content conversion in the receiver file adapter.
Regards,
Ravi Kanth Talagana
Hi,
If your requirement is to convert a flat file to xml, File content conversion should be done in sender adapter(to convert flat file to xml) and then execute the message mapping to get your required target xml in your target directory as mentioned in the receiver file adapter. No FCC is required in the receiver adapter.
Regards,
Swetha.
Hello Swetha,
Yes, the FCC is in sender adapter.
Hello Gouri,
the mapping process produced the correct result, no data was corrupted.
Hello Stefan,
thanks for your suggestion, I will check this with my system administrator, as I wrote a simple ABAP program to dump internal table contents to XML, and the result also corrupted, still not sure what happen with the file system.
Best Regards,
Y
Maybe the file adapter did not finish writing, when you opened the file?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.