on 11-16-2007 10:05 AM
Hi, i have done this before but now i am stuck. I have following target structure for flat file:
<?xml version="1.0" encoding="UTF-8"?>
<MT_PRVO>
<PRVORecordSet>
<PRVODetStruct>
<PVNR/>
<PVADAT/>
<PVSTELL/>
<PVNAME/>
<PVUPM/>
<PVNH/>
<PVKW/>
<PVLEER/>
<PVDIN/>
<TYPE/>
<PRVO_TXT/>
</PRVODetStruct>
</PRVORecordSet>
</MT_PRVO>
My FCC parameters are:
RecordsetStructure: PRVORecordSet,PRVODetStruct,PRVO_TXT
PRVORecordSet.fieldFixedLengths: 04,10,03,15,06,04,04,04,05,08,1400,1400,1400,1400
PRVODetStruct.fieldSeparator: ;
PRVODetStruct.endSeparator:'nl'
PRVO_TXT.fieldFixedLengths: 1400,1400,1400,1400
PRVO_TXT.fieldSeparator: 'nl'
My test-output after Mapping in SXMB_Moni is like this:
<?xml version="1.0" encoding="UTF-8" ?>
- <MT_PRVO>
- <PRVORecordSet>
- <PRVODetStruct>
<PVNR>78</PVNR>
<PVADAT />
<PVSTELL />
<PVNAME />
<PVUPM />
<PVNH />
<PVKW />
<PVLEER />
<PVDIN />
<TYPE />
- <PRVO_TXT>
<PVTXTD>D1 HIER D2 D5 D6 D9</PVTXTD>
</PRVO_TXT>
- <PRVO_TXT>
<PVTXTF>F1 F2 F3 F4 F7</PVTXTF>
</PRVO_TXT>
- <PRVO_TXT>
<PVTXTE>E1 E2 E3 E4</PVTXTE>
</PRVO_TXT>
- <PRVO_TXT>
<PVTXTS>S1 S2 S3 S4 S8 S10</PVTXTS>
</PRVO_TXT>
</PRVODetStruct>
</PRVORecordSet>
</MT_PRVO>
Problem is that i am getting this error in adapter Moni:
java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value 'D1 HIER D2 D5 D6 D9 ')', probably configuration error in file adapter (XML parser error)'
What have i done wrong? I am really stuck because in other scenarios everything works like this.
br
hi Carsten,
did u checked <b>TEST in message mapping</b>, if it is giving successful test, so copy your source structure and put it into your source file.
hope it will help.
regards
HONEY
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, well of course!
The recordset-structure i changed nothing, in parameters the following:
I added following values to the parameters:
PRVORecordSet.fieldFixedLengths: 04,10,03,15,06,04,04,04,05,08,<b>1400</b>
PRVORecordSet.endSeparator: ;
PRVODetStruct.fieldSeparator:;
PRVODetStruct.endSeparator: 'nl'
PRVO_TXT.fieldSeparator: '0'
please compare to the posted parameters before.
br
Hi,
Check out the number of fields you mapped and the fields you provided in XML structure.. This is because of mismatch.
regards
Aashish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, i know. But because of my given Recordset-structure it all should be fine:
PRVORecordSet,PRVODetStruct,PRVO_TXT
Just PRVO_TXT is causing the problem because this substructure occurs more than one time and in MessageMapping the occurrence is 0...99.
Do i have to give the inner elements of PRVO_TXT also?! i think i don't have to...
br
Hi
Check if you provided
-exact number of fields in the the content conversion parameter fieldFixedLengths(fields must be with full lengths and exact spaces).
-to set this fixedLengthTooShortHandling = Cut
- XML Output is not having all fields
- Check out the payload in SXMB_MONI related to all fields there
regards
Aashish Sinha
PS : reward points if helpful
Hi,
Check out these blogs they may help you.
/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/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns - FCC
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file - FCC
/people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario - FCC /people/shabarish.vijayakumar/blog/2006/04/03/xi-in-the-role-of-a-ftp - FCC
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - FCC
/people/mickael.huchet/blog/2006/09/18/xipi-how-to-exclude-files-in-a-sender-file-adapter - EOIO
regards
Aashish Sinha
User | Count |
---|---|
96 | |
11 | |
11 | |
10 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.