Interface mix up

[Former Member]

Hi,

The scenario is designed and configured correctly. But the Receiver interface is comming up in Sender and vice versa.

The following log will make the problem more clear:

<SAP:Sender>

<SAP:Service>MaterialRFC_Receiver_bs</SAP:Service>

<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">BAPI_MATERIAL_GETLIST</SAP:Interface>

</SAP:Sender>

- <SAP:Receiver>

<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" />

<SAP:Service>material_SOAP_Sender_bs</SAP:Service>

<SAP:Interface namespace="http://materialList">material_mi</SAP:Interface>

</SAP:Receiver>

Can any body through light this interfaces are appearing in wrong side please.

Regards

Venkat

[Former Member]

Hi,

Cross check your communication channels, if the adapters are configured correctly (both sender and receiver).

cheers,

Deepak

[Former Member]

HI,

Message interface is Inbound, Sync with Request_MT as input message and Response as output message.

Inteface mapping Request is from Request_MT to BAPI

Response is from BAPI.response to Response_MT

SOAP Sender communicational

RFC request Communicational

No noticiable mistake is there.

Still the mixup is happening.

Regards,

Venkat

[Former Member]

Any clue please

Venkat

[prateek]

In the SOAP sender channel, check the Interface name and namespace again. Perorm a full CPACache refresh then.

Regards,

Prateek

[Former Member]

Hi,

Full cache refresh and restarting of the server also done . No difference. Receiver service is still appearing in sender service when viewed through SXMB_moni.

Entire scenario carried out afresh under different newname space in same software component even then error exactly same.

Any body faced such problem earlier? Is it possible for any body to simulate such an error?

Experts may kindly come to my rescue

Regards,

Venkat

[Former Member]

Hi all,

The problem is only with the message mapping. As the field names are same for different nodes, mapping has been done to same fields of wrong node. On changing the mapping the problem has been rectified.

HI SAP Folks,

Please comment on the following and indicate weather they are bugs ? If they are like that to take care of different functionality. Also request make the the following foolproof.

1) Message mapping has following freedom causing confusion to PI folks:

A sunchronous massage mapping works either as inbound or outbound if the input and the output message types are given suitably.

It shall be fixed as inbound or outbound for a given scenario for easy planning.

2) When message mapping is wrong why should receiver service appear in sender and sender service in receiver in SXMB_MONI.

I beleave this is a bug and adding lot of confution and diverting the attention to wrong area.

Please attend to this scerious bug please.

I hope this information from my problem may help others.

Thanks & Regards,

Venkat

[Former Member]

Hi,

Maybe you named them wrong

The only thing comming to mind now is that you maybe have something wrong the the MI or IM. Or you really should check the naming