Skip to Content
0

FCC Receiver side error in fixed length file-IDoc to file scenario

Aug 08 at 03:30 PM

87

avatar image

I have an IDoc to File scenario.FCC required at receiver end.The structure is as follows:

Header

Item

Details

Trailer

Where Details is the subnode of Item.Header,Item and Trailer are at same level.

Recordset defined as Header,Item,Details,Trailer.

I have defined fixedfieldLengths,fieldnames,endseparator at receiver FCC for each node.

Im getting XML parse error.Content too long error.Is there something im missing.I have searched but didnt get exact answer.Can someone please help.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Manoj K Aug 08 at 03:52 PM
1

Hi Steffy,

You say Details is sub node of Item . So this can't be handled in FCC you need to bring it in the same level as item you can use nodedeception as explained here

Can you please share your FCC screenshot ?

Br,

Manoj

Show 13 Share
10 |10000 characters needed characters left characters exceeded

Hi,

Thanks for your response.I checked the blog.Somewhat relevant.In my case the Item node repeats and it may contain 0-n Details.
One level nesting is not possible using FCC?

0

Hi,

Nope the standard modules or FCC provided by SAP is not capable of handling nested Structure.

Br,

Manoj

0

Thanks for you reply.I got it into a flat struture by using xslt mapping.But im facing issue with FCC.The Item node which contains the Details node Keep repeating.Its not fixed.This is fixed length Scenario.

Can you please guide me how to tackle this?

0

Can you please share the xml after mapping and also attach the screenshot of your FCC ?

0

<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Struct xmlns:ns0="http://www.xyz.com/Data">
<Data>
<BURKS>1230</BURKS>
</Data>
<Item>
<RECORD_TYPE>P01</RECORD_TYPE>
<TIME>092723</TIME>
<JUL_DATE>2017215</JUL_DATE>
<VERSION_NUM>001</VERSION_NUM>
<SEQ_NUM>01234</SEQ_NUM>
<LegacySYSID>01101</LegacySYSID>
<RATING_NAME>PPM</RATING_NAME>
<REC_COUNT>123456</REC_COUNT>
<Filler>59</Filler>
<FACILITY>37009</FACILITY>
<Filler2>16</Filler2>
</Item>
<Details>
<REC_TYPE>P02</REC_TYPE>
<TIME>123456</TIME>
<JULIANDATE>2017215</JULIANDATE>
<VERSIONNUM>001</VERSIONNUM>
<SEQUENCENUM>01234</SEQUENCENUM>
<LEGSYSID>01101</LEGSYSID>
<RATINGNAME>PPM</RATINGNAME>
<DUNS>175631233</DUNS>
<LOCALSUPCODE/>
<DISCREPPARTS>0000000000</DISCREPPARTS>
<RECEIVEDPARTS>0000000200</RECEIVEDPARTS>
<RATEYRMN/>
<ORGANDIV>0000021</ORGANDIV>
<SuperSrcSysID/>
<Filler/>
<FacilityRecLoc>37009</FacilityRecLoc>
<PART>16486744</PART>
<MailBoxLoc/>
<Filler2>PC</Filler2>
<STDATE>20160701</STDATE>
<ENDATE>20170731</ENDATE>
<SAP_PLANT>J701</SAP_PLANT>
<DUNS_CA>036661353</DUNS_CA>
<MATNR_DESC>PIPE-ASM & CAP - ASM</MATNR_DESC>
<MATNR_GRP>01</MATNR_GRP>
<MATNR_GRP_DESC>Material group 1</MATNR_GRP_DESC>
<PRDHA>TAUSPTPRT</PRDHA>
<PRDHA_DESC>PTC Part</PRDHA_DESC>
<DISPO>PRN</DISPO>
<DSNAM>PTC-RAW-N/AMERICA</DSNAM>
</Details>
<Item>
<RECORD_TYPE>P01</RECORD_TYPE>
<TIME>092723</TIME>
<JUL_DATE>2017215</JUL_DATE>
<VERSION_NUM>001</VERSION_NUM>
<SEQ_NUM>01234</SEQ_NUM>
<LegacySYSID>01101</LegacySYSID>
<RATING_NAME>PPM</RATING_NAME>
<REC_COUNT>123456</REC_COUNT>
<Filler>59</Filler>
<FACILITY>37682</FACILITY>
<Filler2>16</Filler2>
</Item>
<Details>
<REC_TYPE>P02</REC_TYPE>
<TIME>123456</TIME>
<JULIANDATE>2017215</JULIANDATE>
<LEGSYSID>01101</LEGSYSID>
<RATINGNAME>PPM</RATINGNAME>
<DUNS>175631233</DUNS>
<LOCALSUPCODE/>
<DISCREPPARTS>0000000000</DISCREPPARTS>
<RECEIVEDPARTS>0000000499</RECEIVEDPARTS>
<RATEYRMN/>
<ORGANDIV>0000021</ORGANDIV>
<SuperSrcSysID/>
<Filler/>
<FacilityRecLoc>37682</FacilityRecLoc>
<PART>52497555</PART>
<MailBoxLoc/>
<Filler2>PC</Filler2>
<STDATE>20160701</STDATE>
<ENDATE>20170731</ENDATE>
<SAP_PLANT>J801</SAP_PLANT>
<DUNS_CA/>
<MATNR_DESC>Fan</MATNR_DESC>
<MATNR_GRP>01</MATNR_GRP>
<MATNR_GRP_DESC>Material group 1</MATNR_GRP_DESC>
<PRDHA>TAUSPTPRT</PRDHA>
<PRDHA_DESC>PTC Part</PRDHA_DESC>
<DISPO>TSC</DISPO>
<DSNAM>FG GMT800 DUCTS</DSNAM>
</Details>
<Trailer>
<Constant>SAP9PPM PPM N</Constant>
<BatchId>00001234</BatchId>
<TotalRecords>0000</TotalRecords>
<RcvdParts>000000000000000101</RcvdParts>
</Trailer>
</ns0:MT_Struct>

FCC

Recordset Structure:

Data,Item,Details,Trailer

Data,PPM_DATA_P01,PPM_DATA_P02,Trailer
Data.fieldFixedLengths 4
Data.endSeparator 'nl'
Details.fieldFixedLengths 3,6,7,3,5,5,4,11,15,10,10,6,7,5,1,5,18,6,3,8,8,4,11,40,9,20,18,40,3,18
Item.fieldNames RECORD_TYPE,TIME,JUL_DATE,VERSION_NUM,SEQ_NUM,LegacySYSID,RATING_NAME,REC_COUNT,Filler,FACILITY,Filler2
Item.fieldFixedLengths 3,6,7,3,5,5,4,6,59,5,16
Details.fieldNames REC_TYPE,TIME,JULIANDATE,VERSIONNUM,SEQUENCENUM,LEGSYSID,RATINGNAME,DUNS,LOCALSUPCODE,DISCREPPARTS,RECEIVEDPARTS,RATEYRMN,ORGANDIV,SuperSrcSysID,Filler,FacilityRecLoc,PART,MailBoxLoc,Filler2,STDATE,ENDATE,SAP_PLANT,DUNS_CA,MATNR_DESC,MATNR_GRP,MATNR_GRP_DESC,PRDHA,PRDHA_DESC,DISPO,DSNAM
Item.endSeparator 'nl'
Details.endSeparator 'nl'
Trailer.fieldNames Constant,BatchId,TotatRecords,RcvdParts
Trailer.endSeparator 'nl'
Trailer.fieldFixedLengths 30,8,8,18

0

Here you go..

fcc1.png (11.5 kB)
fcc2.png (11.0 kB)
txt.png (21.3 kB)
1

Hi,

Thank you so much for you answer.But im still getting error.

3 for 3. column) - must stop, probably configuration error in file adapter (XML parser error)" id="CEPJICNK.MsgDetailedView.TextKey_editor.19" style="white-space: normal;" ti="0" ct="TV" lsdata="{0:'MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: Exception in XML Parser (format problem?):java.lang.Exception: Message processing failed in XML parser: java.lang.Exception: Column value 01101 too long (>3 for 3. column) - must stop, probably configuration error in file adapter (XML parser error)',9:true}" bresettabindex="true">MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: Exception in XML Parser (format problem?):java.lang.Exception: Message processing failed in XML parser: java.lang.Exception: Column value 01101 too long (>3 for 3. column) - must stop, probably configuration error in file adapter (XML parser error)

Im using NFS.What am I missing here?

Really appreciate your help!

0

Hi Steffy,

Make sure you have these parameters :

Data.fixedLengthTooShortHandling = Cut
Item.fixedLengthTooShortHandling = Cut
Details.fixedLengthTooShortHandling = Cut
Trailer.fixedLengthTooShortHandling = Cut

Make sure you don't have any space while copy pasting these parameters in your FCC

Br,

Manoj

0

Hi..Its working for Data,Item,Details,Tiem,Details,Trailer.
When I'm checking for

Data,Item,Details,Details,Item,Details,ItemDetails,Details,Details,Trailer i giving the error I mentioned.

Th ecase where there are multiple Details under Item.

0

Ideally it should work for any case , instead of FCC you can try by MessageTransformBean too.

You can attach the xml which is giving error i can try out that in my system. and also the error screenshot too.

0

I had tried message transform bean which gave same result. for xml just copy and paste the details node once again under details..

Error is xml parser error. If you try it on your system it would be great help..

0

Works for me Perfectly . Please check the screenshot which i have mentioned above and make sure you have all those parameters and without space.

If you still face the error please share the xml , FCC and the error screenshot.

Br,

Manoj

inp.png (17.8 kB)
out.png (35.6 kB)
1

Hi Manoj,

It worked finally!

In Parameters there was mistake.Thanks a ton for your help!

0