SRM-PI-ECC Integration issue

[Former Member]

Hey All

There is some issue coming in Central Contact management scenario.

SRM 7.0

ECC 6.0 EHP 4

PI

*below is the error details we get in SXMB_MONI of SRM Sytem* <REMOVED BY MODERATOR>

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

- <!-- Call Integration Server

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

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

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

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

<SAP:P2><Fault></SAP:P2>

<SAP:P3 />

<SAP:P4>ST: ST_XMS_MSGHDR30_SOAP_FAULT</SAP:P4>

<SAP:AdditionalText>System expected the element 'Fault'</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Unexpected XML element <>; <Fault> was expected System expected the element 'Fault'</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Thanks

Narender

Edited by: Prateek Raj Srivastava on Mar 5, 2011 4:49 PM

[Former Member]

Hi ,

At what level interface failed in MONI(check pipe line steps),i think SRP data not matiching with your structure what you have defined.might be XSD wrong.

Regards,

Raj

[Former Member]

Hey Raja

It is pre-configured scenario..every thing is standard including Function Module also ...

Problem is whe we check the SXMB_mONI message ststus ..the below mention message we are getting...

sender Adapter is XI Adapter (Proxy). Message are Getting failed in SRM Box only .....

Thanks

Abhishek Agrahari

[Former Member]

hi,

you're probably missing the fault message type in your service interface definition. go to the esr to the SI definition and add a fault message and try again

[baskar_gopalakrishnan2]

>> sender Adapter is XI Adapter (Proxy). Message are Getting failed in SRM Box only .....

Hope below steps might help...

a) Sender side proxy then you dont need cllient proxy adapter.

b) Check proxy configuration between SRM and PI. (if messges are getting failed in SRM Box only...)

c) Also make sure ID objects are properly configured with sender business system (ABAP type) in Receiver determination, Interface determination, Receiver agreement etc

d) in your case you dont need sender comm channel and sender agreement.

e) Check proxy structure on the client side matches with PI source data structure. If there is mismatch , regenerate outbound proxy side in SRM and do the coding...