cancel
Showing results for 
Search instead for 
Did you mean: 

ABAP server proxy- parser-item missing error

Former Member
0 Kudos

Dear all,

I am working on File to proxy scenario (ABAP server proxy).

When I executing my scenario, I am getting following error at call adapter pipline step .

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

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

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

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

I checked my message payload after message mapping it containing the perfect SOAP Envelop.

What may be the reason for the error?

Regards,

navneet.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

hi,

the basis team helped to resolve the issue .

regards, navneet

former_member206760
Active Contributor
0 Kudos

Can you send your receiver communication channel paramters

Former Member
0 Kudos

Hi tarang,

here i configured receiver XI CC with the following parameter.

transport protocol:-http 1.0

message protocol:- XI 3.0

adapter engine :-IS

addressing type:-URL address.

target host:- host name for my target sap system.

service no:-8000

path:-sap/xi/engine?type=entry

Authentication type:-use logon data for sap system

user name:- *****

PWD:-******

language:-EN

client:- target R/3 client no.

i tyied with different User ID but i am getting same error.

regards, navneet

Former Member
0 Kudos

navneet

is your path determined ok.

  • /sap/xi/engine?type=entry

for SAP systems based on SAP BASIS 6.40 (XI 3.0 message protocol).

  • /sap/xi/engine?type=receiver

for SAP systems based on SAP BASIS 6.20 (XI 2.0 message protocol).

http://help.sap.com/saphelp_nw04/helpdata/EN/85/78af1bf407434796aaf8dbd6d4e7b7/frameset.htm

Sorry forget my message, this is not applicable for you

Greets

Edited by: Patrick Pot on Feb 25, 2009 10:42 AM

former_member206760
Active Contributor
0 Kudos

Is your system WAS 620 or WAS 640 based

Former Member
0 Kudos

Hi tarang,

i am using was640.

regards, navneet

former_member206760
Active Contributor
0 Kudos

Did u try

step 1 : create a type H RFC destination and then use in that RFC destination try both type = entry and type = receiver

Addr type : HTTP destination

Http dest : give ur http dest created in step 1

Former Member
0 Kudos

navneet,

Please take a look around in this forum there are more questions regarding this error.

Also it's wise to take a look at this blog

/people/padmankumar.sahoo/blog/2005/02/15/an-overview-of-soap

Here is descibed how SOAP calls work.

Greets

Former Member
0 Kudos

hi Patrick,

I already gone through the link u provided. And also searched for the problem ,but no where getting the exact reason.

In my system the client proxy is working fine.

regards, navneet

Former Member
0 Kudos

Navneet,

In SAP help there is a section which describes the configuration of the proxy.

http://help.sap.com/saphelp_nwpi71/helpdata/en/43/951aceb1146353e10000000a11466f/frameset.htm

I can also remember that this error message had something to do with "retrieve parameter from payload" or something like this in the adapter settings

Greets

Former Member
0 Kudos

Hi Patrick,

thanks for your reply. the link u sent is for SOAP adapter.

in my case the scenario is file to Server Proxy. so i am using Xi receiver adapter.I followed all the step described in below link.

http://help.sap.com/saphelp_nw70/helpdata/EN/f4/0a1640a991c742e10000000a1550b0/content.htm

I also did what said in this server proxy link.

https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1457. [original link is broken] [original link is broken] [original link is broken]

regards,

navneet

Former Member
0 Kudos

You are correct,

I pasted the incorrect link. The link below describes the ABAP proxy configuration

http://help.sap.com/saphelp_nwpi71/helpdata/en/5b/12b7e6a466456aa71ef852af033b34/frameset.htm

I have to say that there is no sufficient answer for your problem there as well.

In the link below the protocls are explained mmaybe this will get you in the correct line

http://help.sap.com/saphelp_nwpi71/helpdata/en/51/d5cd16235e4643ae8ec92395c4ad97/content.htm

greets