Response message from Salesforce

[Former Member]

Hi Experts,

I am sending a getServerTimestamp request message from SAP PI to Salesforce. The request message going out of PI is as given below:

<?xml version="1.0" encoding="UTF-8" ?>
- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:enterprise.soap.sforce.com">
- <soapenv:Header>
- <urn:SessionHeader>
  <urn:sessionId>00DE0000000aCQ2!ARoAQGB0CzSWCFEII4p7qOXeyXm9L1rrXuzOFibiyFDmugcIVpiLJlIAViTNtpfJlEL6RhloFZT8L7GYexme_3T.uj3kNbnu</urn:sessionId>
  </urn:SessionHeader>
  </soapenv:Header>
- <soapenv:Body>
  <ns0:getServerTimestamp xmlns:ns0="urn:enterprise.soap.sforce.com" />
  </soapenv:Body>
  </soapenv:Envelope>

A response message does come back into PI successfully from Salesforce, but I am unable to see the payload of the response message. The actual timestamp from Salesforce is not visible anywhere. The payload node does not appear at all in any of the pipeline steps of the response message in SXMB_MONI, and is also not visible in Message Monitoring in RWB.

Also, when I test the WSDL from SOAP UI with the above request message, The response with the timestamp, is fetched correctly from the WSDL.

Is there any particular way in which I can debug this to check what message exactly is coming back from Salesforce? Does Salesforce send the response in any particular format like an attachment or something similar to that?

Kindly help.

Thanks,

Namrata.

[former_member234039]

HI,

Were you able to solve this?

I am working with create method from SF WSDL and records are getting created. i can even see the response message in inbound message payload but it does not get mapped.

Looks like the PI expects the return message tags to have namespace 'ns0'.

Any Clues?

Thanks

[Former Member]

HI, i'm having the same issue right now.  Seems like the soap response is different with the WSDL message.  Would appreciate any immediate reply. Thanks

[rcsegovia]

Please have a look to: http://scn.sap.com/message/13845955

cheers,

Roberto 

[Former Member]

Hi Roberto, just to clearly state my issue.  I can see the below payload in MONI.

But this seems not equivalent to the WSDL message below.  How can I correct this?

[former_member184720]

in the soap adapter select the check box "Do not use SOAP envelope" and try..

[rcsegovia]

Try also removing 'soap envelope'

http://scn.sap.com/thread/3176435 I hope it help you.

[Former Member]

The "Do not use SOAP envelope" is needed since i'm building the soap header request for the session ID using java mapping....

[Former Member]

I've tried using java mapping as well in removing the soap header of response but it seems that the java mapping is not removing it.  Note that I have included the java mapping as part of the Operations Mapping before the graphical mapping.

Any other inputs? Or maybe someone can show me a java mapping code? I'm not sure if what I have created is correct...

[former_member184720]

you can find it here.. http://scn.sap.com/message/10475327

[rcsegovia]

Please have a look into that link, I think  answer from Iñaki can help you too, a XSLT mapping to remove all soap tags:

http://scn.sap.com/message/14376039

XSLT doc: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/000ee4d0-be91-2d10-8aaf-ff8045bdd...

cheers,

Roberto.

[former_member208934]

Hi,

2 ways you can resolve this issue.

1.Java /XSLT Mapping - using this you can remove/add the Envelop structure

2. Using ccBPM also you can resolve this

Thanks,

Naga.

[Former Member]

Hi Hareesh, It worked! Thank you for the link.

[nageshwar_reddy]

Do you see payload for any other synchronous messages? Can you check if logging for synchronous messages is enabled using SXMB_ADM?

This should help you to see the payload through different versions...

[Former Member]

Hi Nageshwar,

This parameter is already maintained in SXMB_ADM, and the response payload is visible for other synchronous messages.

Thanks,

Namrata.

[nageshwar_reddy]

You can try using the xpi_inspector to see what response you are getting. More details on xpi_inspector are available at and .