cancel
Showing results for 
Search instead for 
Did you mean: 

XML element {http://schemas.xmlsoap.org/soap/envelope/}Envelope missing in

Former Member
0 Kudos

Hi,

Here I am using PROXY-TO-FILE Interface and I am sending 90+ MB message.

In that case, I am getting below Error in SXI_MONITOR.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <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>

whenever I will send small amount of data, its processing successfully.

Here, I am sending large amount of data. Any parameters is there for processing large amount of data.

Please help out regarding this.

Regards,

Nageswari

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Eswari,

Refer this..

/people/sravya.talanki2/blog/2005/11/29/night-mare-processing-huge-files-in-sap-xi

Hope it helps..

Kumar.S

Former Member
0 Kudos

Hi Nageswari !

You could try to split your outbound data in smaller chunks an use EOIO, and use "append" mode in file adapter to rebuild the file.

Check this link for EOIO in ABAP Proxy:

/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies

Regards,

Matias.

Former Member
0 Kudos

Hi Matias,

In the below BLOG, they hardcoded Purchase Order Number.

Check this link for EOIO in ABAP Proxy:

/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies

But in our case, We are extracting the data from R3 and We are creating the file in FTP Server. Please advice me, how to proceed.

Regards,

Nageswari

Former Member
0 Kudos

Hi Nageswari !

The blog hardcoded the PO number, but of course you can make it dynamic. We used this solution for a scenario like yours. We create the queue id dynamically on runtime each time, on each execution (for each PO number). Just assign the name you need to the queue Id and it will automatically create the queue. Just use a common prefix for the queue name. I'm not sure right now, but the queues have a maximun name length of about 16 chars.

Regards,

Matias.