cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP Sender Channel: Receiving corrupted Payload in SAP PI.

Former Member
0 Kudos

Hi All,

Our PI system is 7.31 SP15. We are facing a strange issue in our system for SOAP Sender Adapter with HTTP protocol.

The payload is getting corrupted while entering our PI system. Most often its the ending tag which gets corrupted. Due to this the Mapping step fails in PI. The source system is also PI system and the payload in the Source PI system is well formed. This does not happen to all messages and the behavior is not predictable. The issue cannot be replicated.

Payload in Our PI System: Additional characters after the end tag.

Payload in the source PI system: The ending tag is as expected.

We had a similar issue for another interface. It was again SOAP sender adapter and the message was coming from SAP system. Since the message flow in this case was very less we used the XML validation feature to reject the messages in PI and make it fail in the source system itself. When these failed messages were reprocessed from source system they were successfully processed in our PI system.

We are avoiding XML validation for the above interface since the message flow is very high.

Please provide your suggestions how to resolve this issue.

Regards,

Mohit Hosmani

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Aby,

No RFC used and no character conversion being done.

Any other views?

Regards,

Mohit Hosmani

aby_jose
Explorer
0 Kudos

Hi Mohit,

Few thoughts

Are you using a mapping; if yes, could you monitor the payload before and after the mapping  (just to ensure that, no special characters gets added due to the mapping).

Did you apply the XML validation for adapter engine (sender adapter)?

Can you explain a little more about your sender system. Is there any difference in encoding between sender system and PI system?

Since the sender adapter is soap, could you execute the scenario few times from 'wsnavigator' and check whether the issue still exists?

Also kindly check the failed messages and see if you can find out a common pattern (just need to know is the issue is due to a specific payload type)

Best Regards,

Aby

aby_jose
Explorer
0 Kudos

Hi Mohit,

Are you doing a character conversion somewhere?.

Are you using RFC connection for the communication anywhere? If yes, kindly check the Unicode conversion (Unicode should be checked for Unicode system etc..)

Thanks,

Aby

Former Member
0 Kudos

Hi Raghu,

That is the issue here. Some junk values get appended to the payload. In this example it is "<uni" in other cases it could just be a single character like "a" getting added at the end or the payload  ends with "<ns0:StandardBusi" which is incomplete ending tag. We are unable to trace this behavior.

Regards,

Mohit Hosmani

former_member186851
Active Contributor
0 Kudos

Hello Mohit,

Check using XPI inspector, its a tracing tool.

And did you import any WSDL in the second PI box?

Former Member
0 Kudos

Hi Raghu,

Since the issue is cannot be replicated, we were not able to make use of the XPI Inspector.

Regarding the WSDL i need to contact the other PI Support team for this info. What possible issues could it be related to WSDL?

former_member186851
Active Contributor
0 Kudos

Hello Mohit,

Just thought something got corrected in WSDL.

And one more thing, instead of sending from PI ,check once using SOAP UI.I mean to second PI box

Then we can get an idea from where exactly junks are getting added

former_member186851
Active Contributor
0 Kudos


Hello Mohit,

what is this </uni Tag.its added randomly?