cancel
Showing results for 
Search instead for 
Did you mean: 

PARSER Error with "ITEM_MISSING"

Former Member
0 Kudos
95

Hi,

I have a file to file interface that is failing with the below error when my file size is more than 20 MB. Has any faced simillar problem. How to resolve this. Is it XI limitation or some parameter is set that is defining the size. Any help on this highly appreciated.

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>XIProtocol</SAP:Category>

<SAP:Code area="PARSER">ITEM_MISSING</SAP:Code>

<SAP:P1>Envelope</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Thanks

Sri

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

hi,

I am getting simillar error on one of our systems all of a sudden. This had been working fine earlier. Scenario is File->XI->File

Any input highly appreciated.

cheers,

sachin

Former Member
0 Kudos

Hey

can you please test you scenario with a smaller file,like 1-2 MB,also make sure that the sender and receiver File adapter have been configured properly,usually you should not find this error in File to File scenario,there is something wrong with the communication channel configuration

Thanx

Ahmad

Former Member
0 Kudos

Hi Ahmad,

The scenario works if I use a file that is less than 20 MB. I have tested this with 19 MB file and it has worked. Anything over 20 MB it is failing.

Thanks

Sudheer

Former Member
0 Kudos

Hey

you can split the file by either writing a shell script to split the files into smaller chunks or you may use BPM.

considering the BPM performance issues i would prefer writing a script and executing it on the receiver side system

Thanx

Ahmad