No Receiver in SOAP header in sxmb_moni

Hi all
My scenario is using the HTTP sender channel.the url is like this:
http://xiserver:8000/sap/xi/adapter_plain?namespace=http%3A//my&interface=MI_Leo_HTTP_Sou_OB&service=ZBS_Leo_Http&party=&agency=&scheme=&QOS=EO&sap-user=*****&sap-password=****&sap-client=001&sap-language=EN
after i trigger the scenario, i got the message'status scheduled
and the info of SOAP Header in sxmb_moni as followed:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>7603ACFE-A4DB-5F48-8F6A-A9DFC3CB97CB</SAP:MessageId>
<SAP:TimeSent>2007-11-01T03:34:43Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>ZBS_Leo_Http</SAP:Service>
<SAP:Interface namespace="http://my">MI_Leo_HTTP_Sou_OB</SAP:Interface>
</SAP:Sender>
 <SAP:Interface namespace="http://my">MI_Leo_HTTP_Sou_OB</SAP:Interface>
</SAP:Main>
i think it's really wired, in the info, i couldn't find the receiver info, while my receiver determination is really ok.
the bold highlighted aboved should be like this:
<SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>*******</SAP:Service>
<SAP:Interface namespace="****">*****</SAP:Interface>
<SAP:Mapping notRequired="X" />
</SAP:Receiver>
but it's wrong.how should solve this????
and i restarted the message, it became manual restart status, it didn't work
Please help me.
Thank you in advance.

it works now

Similar Messages

SOAP Header XSLT mapping

Hi,
I am working on Proxy to SOAP synchronous scenario. How to create SOAP header message in XSLT mapping...I am trying but no sauces becz receiver side SOAP header and Body in different message types please see below.
Header part is message type 1
<CredentialsHeader xmlns="http://reuters.com/datascopeselect/ExtractionService/v1/">
 <Username>string</Username>
 <Password>string</Password>
 <AuthenticationToken>string</AuthenticationToken>
 </CredentialsHeader>
Body part is
message type 2
<soap:Body>
 <Extract xmlns="http://reuters.com/datascopeselect/ExtractionService/v1/">
 <request>
 <OutputFields>
 <string>string</string>
 <string>string</string>
 </OutputFields>
 </request>
 </Extract>
</soap:Body>
</soap:Envelope>
But source is single.. I try ed multi mapping but synchronous scenario it will not working.
I am trying to generate both message types as single message type in XSLT mapping target side and will give service interface as dummy in ESR.
Please guide how to generate 2 message types as single message type in XSLT mapping...
Thanks,
Venkat

Hi Venkat,
I suggest to produce a complete SOAP message in message mapping. Import the SOAP XSD from [http://schemas.xmlsoap.org/soap/envelope/] as external definition and use it as target message in message mapping. You need at 2 mapping programs in order to produce the message. The first mapping creates header and body. In the second mapping use "Return as XML" to map the header and body nodes to the SOAP envelope.
In the SOAP receiver communication channel, you need to activate the parameter "Do Not Use SOAP Envelope", see [Configuring the Receiver SOAP Adapter|http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm].
Regards, Martin

In Receiver Mail Adapter ,how to ignore SOAP Header attachment

HI Folks,
Am using Receiver Mail Adapter and am getting 2 attachments.
1. one is Soap header which contains Control records
2. payload
I want only Payload as attachment and need to ignore SOAP Header(AT00001.xml).
The configuration is as below:-Trasport protocol : SMTP
                                            Message Protocol: XIALL
Please provide Inputs.
Thanks & Regards
Ashok Reddy

Hi Gagandeep,
Scenario: File------>mail( Bypass scenario)
i had posted file in FTP and am getting attachment properly but aditionally am getting ATT00001.xml as SoapHeader.this i need to ignore.
PFB Module Parametrs i used:
localejbs/AF_Modules/MessageTransformBean   LocalEnterpriseBean    transform
Modulekey                      Parameterattribute                        value
transform                      Transform.ContentDisposition            attachment;filename=”Pocr_860.txt”
transform                     Tansform.ContentType                       text/plain
Regards
Ashok

SOAP Receiver Adapter - Read Header data on Synchronous Response

I have a scenario - flat file to SOAP. The web service provider sends a response that contains data in the Header that I need to access. I have tried to use the "Do Not Use SOAP envelope" option on my receiver SOAP adapter, and I have configured my request message type to include the soap envelope elements. However I'm getting the following error from the web service
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Cannot process the message because the content type 'application/xml' was not the expected type 'text/xml; charset=utf-8'.
I've read some inputs on this error that say to use the Transform bean to adjust the content to text/xml. However I'm not sure how to do that. If that is the correct resolution to my problem, can someone provide detailed steps on how to add the Transform bean to the adapter module. I have no experience with adding items to the module tab.
If there are other ways to tackle this scenario to get access to the SOAP Header from the SOAP receiver adapter, please share those as well.
Thanks in advance.
Chris

Resolved with the following blog
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi

SOAP Header in SOAP Receiver adapter

Hi All,
I am doing a Proxy to Webservice scenario where webservice requires the SOAP request as below.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP-ENV:Header>
 <mh:CustomHeader xmlns:mh="http://schemas.test.com/customHeader">
 <mh:MessageData>
 <mh:MessageId>12345</mh:MessageId>
 <mh:Timestamp>2004-06-09T14:41:44Z</mh:Timestamp>
 </mh:MessageData>
 </mh:CustomHeader>
 <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/04/secext">
 <wsse:UsernameToken>
 <wsse:Username>test</wsse:Username>
 <wsse:Password>test123</wsse:Password>
 </wsse:UsernameToken>
 </wsse:Security>
 </SOAP-ENV:Header>
 <SOAP-ENV:Body>
 </SOAP-ENV:Body>
Need your help to understand how can we achieve this using Standard SOAP adapter to customize the Header part as it requires to include "<mh:CustomHeader " & "UsernameToken".
Or Do i need to go for adapter module development to create this SOAP request.
Please provide your suggestion to achieve this scenario.
Thanks & regards
Ashwin
Edited by: ashwin dhakne on May 17, 2010 5:32 PM

Hi all,
Created a below target payload in a message mapping with SOAP Header & Body part as per the requirement.
In SOAP receiver communication channel, checked the option " Do Not Use SOAP Envelope".
But while executing an sceanrio, i am facing an error in SOAP receiver channel as Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
And if i don't check the option " Do Not Use SOAP Envelope" it gives an error as
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Unable to obtain service binding,error=Payload Envelope is not a known message for TestWebserviceService.
Please provide your suggestions to handle this issue.
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:Envelope xmlns:ns1="http://schemas.test.com/CustomrHeader">
<ns1:Header>
<ns1:CustomrHeader>
<ns1:MessageData>
<ns1:MessageId>Constant</ns1:MessageId>
<ns1:Timestamp>Constant</ns1:Timestamp>
</ns1:MessageData>
<ns1:Security>
<ns1:UsernameToken>
<ns1:Username>Constant</ns1:Username>
<ns1:Password>Constant</ns1:Password>
</ns1:UsernameToken>
</ns1:Security>
</ns1:CustomrHeader>
</ns1:Header>
<ns1:Body>
<ns1:Details>
<ns1:Information>
<ns1:Title>Test</ns1:JobTitle>
</ns1:Information>
<ns1:Contacts>
<ns1:Street>Test Drive</ns1:Street />
</ns1:Contacts>
</ns1:Details>
</ns1:Body>
</ns1:Envelope>
Thanks
Ashwin
Edited by: ashwin dhakne on May 18, 2010 5:47 PM
Edited by: ashwin dhakne on May 18, 2010 5:48 PM
Edited by: ashwin dhakne on May 18, 2010 5:48 PM

Error in SXMB_MONI in SOAP Header -- Call Adapter

Hi ALL,
Got a problem with monitoring activity.
In SXMB_MONI, iam getting errors with Call Adapter section in SOAP HEADER section of the message.
The Error part shows the following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Problem inserting 4657f861-f853-60e8-e100-00000a80314d(INBOUND) into the database: java.sql.SQLException: ORA-25153: Temporary Tablespace is Empty</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anybody give me a clear picture of the exact error and what could be the diagnosis for this particular problem.
cheers,
Santosh

Hi Santhosh
1.Check your authorization settings in XI and R/3. Whether the user has sufficient rights to execute the Function Module etc. This is the most common reason for this error.
2.If the XI system was brought online even before the R/3 system then re-activate the communication channels from the Integration directory.
Cheers..
Vasu
** Reward Points if found useful **

Query reg adding custom tags in SOAP Header - AXIS Receiver Adapter

Hi All,
I need to send custom tags as mentioned below to my traget webservice application. I think I can do this with Receiver AXIS adapter but not sure how it can be done. Can any of you suggest?
 <WSContext>
 <FromAppId>ABC</FromAppId>
 <ToAppId>XYZ</ToAppId>
 </WSContext>
Thanks,

If you want to add custom tags in the soap header, one possible solution is use XSLT mapping or Java mapping to create header first then do message mapping for mapping the payload structure between your source and target as usual.
So in operation mapping you sequence mapping like this... first XSLT mapping for custom tags for the SOAP Header followed by payload mapping.
Hope that helps.
Search SDN for XSLT Mapping for soap header. Already we have handled these issues.

Header autentication Receiver HTTP (soap-axis)

hi,
I need to place the authentication in the header to the SOAP receiver channel is for soap-http axis.
Place the authentication module, but the monitor shows pi invalid username and password.
Was entered in the module, but does not work
ParameterName Module Key Parameter Value
wssec UsernameToken action
wssec Handler.Type java: com.sap.aii.adapter.axis.ra.handlers.security.WSDoAllSender
wssec passwordType PasswordText
wssec pwd.password <enter password> = <enter password>
wssec user <enter username>
How rare header from soapUI putting in username and password works, but since IP does not work, it no longer occurs to me that may be happening.
We spent a WSDL with soap12, you can from an XSL add the user and password or may be going ?.
Greetings.

Hi Diego
Check this links
SOAP Header Authentication
https://websmp230.sap-ag.de/sap/support/notes/1039369
Regards
Osman

Dynamic Receiver Determination using Soap header

Hi ,
I am trying to use a field in SOAP Header to determine the receivers dynamically.
1, Using XPATH gives me only values in the Payload and not the SOAP header. Is it possible to pull the value from the SOAP header to the payload and then do dynamic receiver determination.
2. Using Context Object is it possible to transfer the value of the field in SOAP header to variable header Xheadername1 and then use it to determine the receiver. I am having problems in passing the value of the field in soap header to XHeadername1.
Any help is appreciated and points will be awarded.
Joe Vellaiparambil

Hi Joe,
This is a good blog by William, hope this is helpful.
/people/william.li/blog/2009/07/30/how-to-read-soap-header-information
Let us know if you need more information.
Regards,
Neetesh

Handling SOAP HEADER using SOAP Receiver Adapter

Hi Experts,
I need to implement SOAP Receiver Scenario and passing ( Header fields User, Password and token) I have seen a lot of scenario using a XSLT Mapping, to handling the SOAP Header. So need to help to understand some details:
Suppose I need to implement the SOAP Header below? In this case I need add only the fields u201CUsername, Password and AuthenticationTokenu201D. I created the XSLT Transform, the source XML? Where I put it? Or can create it into Message Interface?
Is it possible to do this in Java Mapping?
Thanks!
Best Regards
Fábio Ferri
<soap:Header>
 <v1:ExecutionHintHeader>
 <v1:Name></v1:Name>
 <!Optional:>
 <v1:Arguments>
 <!1 or more repetitions:>
 <v1:Argument Name="?" Value="?"/>
 </v1:Arguments>
 </v1:ExecutionHintHeader>
 <v1:CredentialsHeader>
 <!Optional:>
 <v1:Username>pi</v1:Username>
 <!Optional:>
 <v1:Password>jhjhjjhjhjius</v1:Password>
 <!Optional:>
 <v1:AuthenticationToken></v1:AuthenticationToken>
 </v1:CredentialsHeader>
 </soap:Header>

You need to put XSLT mapping in 2° step mapping in request.
SourceMessageRequest -> Message Mapping -> XSLT Mapping -> DestinationMessageRequest
If you test mapping program, this should be working fine.
In adapter module, put localejbs/AF_Modules/MessageTransformBean with parameter value text/xml; charset=utf-8 and correctly set Conversion Parameter "Do not use Soap Envelop"
XSLT Request Mapping
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Header>
<ServiceAuthHeader xmlns="http://WIND.WEBSERVICES.DMS/">
<Username>USER</Username>
<Password>PASSWORD</Password>
</ServiceAuthHeader>
</soap:Header>
<soap:Body>
<xsl:copy-of select="*"/>
</soap:Body></soap:Envelope>
</xsl:template>
</xsl:stylesheet>

Overriding Soap Header using Axis(SOAP) Receiver

Hi Experts,
I am having a problem in including the SOAP Header in the XML using the SOAP Axis Receiver Adapter. Well I am not sure on how to place this structure in the header:
<SoapHeader>
 <Header1>
 <child1>
 <child2>
 </Header1>
 <Header2>
 <child1>
 <child2>
 </Header2>
</SoapHeader
I have already tried overriding the SOAP Header via Java Mapping but it is not working when I send it to the third-party. I believe this header should be directly encoded using the axis module, but I can only find examples for simple headers and not nested ones...
Please help.
Edited by: Mark Dihiansan on Sep 7, 2010 5:15 PM

Hi,
you simply place your header template in the handler configuration. If you need to set some values of the header dynamically, you can pass each value in the dynamic configuration header. The axis handler will fill the header with the supplied values.
The Axis Note 1039369 describes a few header insertion examples that you should look at.
regards, yza

SOAP RECEIVER: Possible to change the soap header request

Hi
Is it possible to change what is included in the soap header like namespaces (.. xmlns:ns="http://what.com"
Specifically I need to have the "http://Strange.org/thisis.xsd" (see below) included in the header and the <ns:pi-create> included in SOAP-ENV
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns="http://Strange.org/thisis.xsd">
<SOAP-ENV:Body>
<ns:pi-create>
<request>
<request-data>...
</request-data>
</request>
</ns:pi-create>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Hope somebody can help
Cheers

Hi Bowie,
1.You can change the Namespace. condition is no obj's under the namesapce then only it's possible otherwise u can't.
2.create a new namesapce what ever u want and copy all the obj's under that namesapce.finally delete the previous one.
XMLAnonymizerBean
Use
You use this module to anonymize XML elements and attributes by removing namespaces or namespace prefixes from the XML document of the main payload.
You can define a particular namespace prefix for each namespace. You can also change the encoding attribute of the XML declaration.
Integration
You can use the module in adapters that can be extended in the module processor.
Activities
Entries in the Processing Sequence
● Insert the module before the adapter module.
If the adapter comprises multiple modules, for information about the position of the module, see: Extending the Module Chain in the Module Processor
● Enter the module name AF_Modules/XMLAnonymizerBean.
● Select the Module Type Local Enterprise Bean.
● The system proposes a module key.
Entries in the Module Configuration
● anonymizer.acceptNamespaces
Enter a list of namespaces and their prefixes that are to be kept in the XML document as follows: namespace1 n1 namespace2 n2 u2026
To enter a namespace without a prefix, enter '' (two single quotation marks).
Any namespaces you do not specify are removed from the XML document.
● anonymizer.quote
Specify the character to be used to enclose the attribute values.
The default value is '. The parameter is optional.
● anonymizer.encoding
To use a code page other than UTF-8, enter it. The parameter is optional.
For example, enter ISO-8859-1.
Example
The anonymizer.acceptNamespaces parameter has the following value:
urn:sap-com:document:sap:rfc:functions rfc urn:sap-com:document:sap:soap:functions:mc-style rfc
● Payload before using the XMLAnonymizerBean:
<Z_PAYMITEM_GET_LIST
xmlns="urn:sap-com:document:sap:rfc:functions"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<I_ACCOUNTIDENT xmlns="">
 <ACCOUNT_NUMBER>0080000094</ACCOUNT_NUMBER>
 <BANK_COUNTRY>DE</BANK_COUNTRY>
 <BANK_COUNTRY_ISO>DE</BANK_COUNTRY_ISO>
</I_ACCOUNTIDENT>
</Z_PAYMITEM_GET_LIST>
● Payload after using the XMLAnonymizerBean:
<?xml version='1.0' encoding='utf-8'?>
<rfc:Z_PAYMITEM_GET_LIST
xmlns:rfc='urn:sap-com:document:sap:rfc:functions'>
<I_ACCOUNTIDENT>
 <ACCOUNT_NUMBER>0080000094</ACCOUNT_NUMBER>
 <BANK_COUNTRY>DE</BANK_COUNTRY>
 <BANK_COUNTRY_ISO>DE</BANK_COUNTRY_ISO>
</I_ACCOUNTIDENT>
</rfc:Z_PAYMITEM_GET_LIST>
with rgds,
MFH

Reading custom SOAP header with XHeaderName1

Hello Experts,
I have a SOAP to File scenario and I am trying to do dynamic receiver determination by looking at the SOAP request header info. I am adding a custom field (System_ID) that I want rules to run against in Receiver Determination..
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:*******************">
<soapenv:Header>
<System_ID>100</System_ID>
</soapenv:Header>
<soapenv:Body>
</soapenv:Body>
</soapenv:Envelope>
In the Receiver Determination I have multiple rules using SOAP context object to XHeaderName1 = the System_ID (100) to pass the message to the right system at runtime according to the System_ID.
In the SOAP sender channel I have Set Adapter-Specific Message Attributes and Variable Transport Binding checked. I also have the variable name System_ID in the first Variable Header (XHeaderName1).
In the SOAP sender Conversion Parameters I have Do Not Use SOAP Envelope and Keep Headers checked, as well as nosoap=true in the SOAP request URL.
I'm getting the System ID to show in XI in sxmb_moni in the Header but no where do I see it being used with XHeaderName1.
Am I using XHeaderName1 right? If not could you advise as to how XHeaderName1 should be used?
My requirement is to read system ID from Header, not payload.
Thank you!
Tim

I was able to find a solution to my problem.
I created a basic senario below to test:
1.A basic Asynchronous scenario is created using a SOAP sender adapter to 2 possible flat file receivers.
2.The SOAP sender channel will have the option u201CDo Not Use SOAP envelopeu201D checked and SOAPUI URL will have u201C&nosoap=trueu201D added to the end.
3.The receiver system name will be stored in the WS-Addressing u201CActionu201D field sent from SOAPUI.
4.Two ABAP mappings are created. One mapping will extract the system number from the WS-Addressing u201CActionu201D field. The other mapping will extract just the body of the SOAP message to send along. Using regex and string manipulation in the ABAP mappings we can reuse the mappings for any SOAP message.
5.Enhanced (Extended) Receiver Determination is selected and interface mapping using system/XI ReceiverDetermination service interface is used to capture the receiver system.
While this is a solution is not the best, it is a solution. Upon research I found a recent SAP Note 1385579 talking about implementing a SAP delivered generic SOAP Sender AXIS handler com.sap.aii.axis.soap.HeaderExtractionHandler to extract SOAP Header elements and place in message attributes. I will be trying this out.

How to view SOAP Header

Hi Gurus,
i have a simple questions to you (hopefully).
At the moment i am working with SOAP AXIS Receiver Adapter because i need to add <wsse> Tags to my SOAP Header. (according to blog: /people/pravesh.puria/blog/2009/08/26/adding-usernametoken-timestamp-in-soap-adapter-using-axis-framework)
I get no error for this configuration but i am wondering where i can have a look at the SOAP Header that will be transfered to the target url.
when i go to CommChan-Monitoring and have a look into Message-Details-->Message-Content i only can view "SOAP Document" this looks to me like the internal SOAP Envelope, but this is not going out the target url right? And i also can have a look on the payload, but there is no SOAP Header at all.
thank you for your help
Best Regards
Udo

No, this XML is the whole XI message and it is not sent by the SOAP (axis) adapter. If you want to see exactly what is sent, try checking it with the TCPGateway tool as advised on the SOAP FAQ note
[Note 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=856597]
Under question "Q: How can I trace the whole message?". Otherwise, on SXMB_MONI, try selecting the PAYLOAD item on the left menu and, on the payload on the right, right-click and select "VIEW SOURCE".

XI to XI Communication : SOAP Header behavior

Hi Techeis,
I have a scenario XI(A) to XI(B) communication..
I use Receiver XI adapter using HTTP Destination to transfer the payload from IE of A to IE of B. However i see strange behaviour as mentioned below;
in A --> in the SOAP header o/b message interface is A_OUT & i/b message interface is A_IN
when the paylaod reaches XI(B)
in B --> in the SOAP header o/b message interface is A_IN & i/b message interface is A_IN
i.e. in the target XI server, in the SOAP header o/b message interface is always same as the i/b message interface in source XI server !!
why is that behavior , does anybody have idea on this?

Hi Stefan,
Thanks for your inputs. If that is the case then please help me get answerd for the following queries:
1) Why we need to make the o/b MI in B same as i/b MI in A while creating Receiver Determination again in B ?
2) why it loses the information of another MI ? why does it not carry the information of both MI to the B-XI system?
3) Does that mean, in SXMB_MONI, the SOAP header that we see is only for the display purpose and does not reflect the actually nformation carried ?
Thanks in advance!

No Receiver in SOAP header in sxmb_moni

Similar Messages

Maybe you are looking for