cancel
Showing results for 
Search instead for 
Did you mean: 

error in sender system

Former Member
0 Kudos

Hi we have a scenerio where we have used Integration Server communication.WS adaper is used on sender side when triggering the data from sender system

i am getting the falloing error in Sender system(Bank analyzer)

SAP:Category>XIServer</SAP:Category> 

<SAP:Code area="INTERNAL">IN_BIND_WRONG_ADPT</SAP:Code>

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

<SAP:P2>XI</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>Sender agreement found belongs to adapter WS, however the current adapter is XI</SAP:Stack>

Accepted Solutions (0)

Answers (2)

Answers (2)

aashish_sinha
Active Contributor
0 Kudos

Hi,

It looks like you are using incorrect communication channel in sender agreement. Can you please check and change it to WS?

Regards

Aashish Sinha

Former Member
0 Kudos

Thanks for the reply ,

our scenerio is we are replicating data from banking service to bank analyzer.

And we are using proxies on both sides and also  WS adapter on both sides in one of our test systems and is working fine there.as we want to develop the same interface in another test system we are  getting this error

regards

sivaramaraju

aashish_sinha
Active Contributor
0 Kudos

Hi,

If you are generating Client proxy from sender side, then you are not supposed to create sender agreement. If I understood you clearly, for receiver side, you already have one standard enterprise service to post incoming message to bank analyzer. If this is the case, create one XI receiver Adapter. In the mapping side create one Source data and map that source data type to your enterprise service, and create all OM,SI, MT and DT and configure it.

Regards

Aashish Sinha

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

>>>SAP:Stack>Sender agreement found belongs to adapter WS, however the current adapter is XI</SAP:Stack>


as epr this error check the sender agreement - as you've probably used a wrong adapter

XI instead of WS...

XI adapter can handle SOAP calls (WS) using the SOAP protocol of this adapter

but this is not the SAP WS adapter. In most cases like for ABAP proxies, normal soap (WS) calls you always use XI-SOAP adapter however.

Regards,

Michal Krawczyk

Former Member
0 Kudos

Thanks for the reply micheal,

our scenerio is we are replicating data from banking service to bank analyzer.

And we are using proxies on both sides but they have used WS adapter on both sides in one system and is working fine there.as we want to develop the same here getting this error

regards

sivaramaraju