cancel
Showing results for 
Search instead for 
Did you mean: 

Sender SOAP Stripping my xml namespace definition

Former Member
0 Kudos

Hi All,

I am on SAP PI 7.31 Release 5. I see an unusual behavior in Sender SOAP Adapter. I tried to create the scenario both as on ICO and a normal configuration and I see the sender soap adapter removing the xml namespace.

The Sender SOAP adapter is removing the xml namespace from my xml payload which is resulting in mapping error in SAP PI.

I tried the same scenario in PI 7.1 EHP 1 and it behaves differently and there I am able to see the xml namespace.

Is that a bug in the SOAP adapter or I need to use XML Anomalyzer in the Sender SOAP Adapter.

In PI 7.3 we have CallSapAdapter in Module and in 7.1 we have XISOAPAdapterBean, so does that Module act differently ?

SAP PI 7.31 Release 5

<notifications xmlns='http://soap.sforce.com/2005/09/outbound'>

<Notification>  

<Id>5555566666</Id> 

<sObject xmlns:sf='urn:sobject.enterprise.soap.sforce.com' xsi:type='sf:Account'>  

<sf:Id>4444455555</sf:Id>  

<sf:Account__c>9876</sf:Account__c>  

<sf:Name>Order Header Unit Test</sf:Name> 

<sf:SAP_Action__c>M</sf:SAP_Action__c>  

<sf:Text__c>Test 2</sf:Text__c>

</sObject>  

</Notification> 

</notifications>


SAP PI 7.1 EHP 1

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

<!--  Inbound Message

-->

-<notifications xmlns="http://soap.sforce.com/2005/09/outbound" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<Notification>

<Id>5555566666</Id>

<sObject xmlns:sf="urn:sobject.enterprise.soap.sforce.com" xsi:type="sf:Account">

<sf:Id>4444455555</sf:Id>

<sf:Account__c>9876</sf:Account__c>

<sf:Name>Order Header Unit Test</sf:Name>

<sf:SAP_Action__c>M</sf:SAP_Action__c>

<sf:Text__c>Test 2</sf:Text__c>

</sObject>

</Notification>

</notifications>

Any suggestions for me ?

Thx in advance

Ravijeet



Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi All,

Issue resolved.

Note 1786611 - Namespace definitions missing in payload.

Adios

RJ

Answers (0)