ABAP PROXY ERROR

[AntonioSanz]

Hi all,

i`m working with a ABAP PROXY to WEBSERVICE scenario. I have created a the proxy in abap but when i test the proxy I get the next error:

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

- <!-- Call Adapter

-->

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

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=DBECLNT100;TS=FINHOTEL_DES;AN=MI_TC001_IN;ANS=http://beefficient/tc/tc.001;</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

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

</SAP:Error>

I have revised my integration scenario and the it have the receiver agreement properly configured. I have also checked my connection with sld (througth sldcheck) and it works fine.

Any idea?

Thanks

[Former Member · Accepted solution]

Hi Antonio !

Try to refresh the cache, and also you can make any dummy changes in the receiver agreement and activate it again.

Please keep me posted.

Regards,

Matias.

[AntonioSanz · Accepted solution]

Thanks Matias.

I have done what you said and i get the same error.

Any other suggestion?

[justin_santhanam · Accepted solution]

Anto,

Can u do more thing. Go to Integration Directory make a change to all the objects and reactivate again.

If it doesn't works - try the cache resresh using URL.

Best regards,

raj.

[Former Member · Accepted solution]

In addition to what Raj said, you can also try to regenerate Proxy and activate it..

[AntonioSanz]

I finally discovered where the error was.

I had done a change on the data type which used the by interface over which I generate my proxy abap class.

But my system when I do the regenerate proxy option doesn´t work. So I had to delete my proxy abap and all the data which was generated, and do It again.

So with the right "version" of the proxy abap class all works fine.

The message test throws by SAP XI in this case was not very usefull for me.

Thanks to all for your interest in my problem.

[Former Member]

Hi Antonio !

Just for the record...which data type were you using that caused the problem? any standard data type?

Thanks,

Matias.

[AntonioSanz]

In fact the change was on the name of the data type. I have created a new data type (all atrributes and elements are Strings) and I have used it in message type replacing the old one.

Thanks for your interest.

Antonio

[AntonioSanz]

Thanks Matias. I have done that and i get the same error.

In my systems are:

SAP R/3 DEV

SAP XI DEV

and SAP XI PROD where SLD is active.

So SAP R/3 and SAP XI DEV are configured to point SLD in SAP XI PROD. (sxmb_adm, sldapicust and rfc destination points to SAP XI PROD).

[Former Member]

Have you done what Raj and I said... If error comes can you post the error

[AntonioSanz]

I have done that and get the same error:

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

- <!-- Call Adapter

-->

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

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=DBECLNT100;TS=FINHOTEL_DES;AN=MI_TC001_IN;ANS=http://beefficient/tc/tc.001;</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

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

</SAP:Error>

Message was edited by:

Antonio Sanz

The interface works fine in ABAP PROXY --> WEB SERVICE REQUEST

The error comes in WEB SERVICE Response --> ABAP PROXY

[Former Member]

Just checking....Did you create the inbound proxy for that.... and the corresponding communication channel (if any).... Hope you are not trying to use the same out bound proxy ( ABAP PROXY --> WEB SERVICE REQUEST)...

[AntonioSanz]

My scenario is an online scenario. and I think that is not necessary. My interface has a Input and an output message. The abap proxy has Output data and input data.

Thanks

[Former Member]

Hi Antonio !!

I could suggest this things:

- check in sxi_cache if the receiver agreement exists, you can also use the menu in this transaction "Goto" | "Adapter Engine Cache" and delete the rows that appear on table to force AF cache refresh

- to detect if the problem is on the webservice or abap proxy side, you could make another

synch abap proxy based on the webservice message interface to simulate the webservice and check that communication between both abap services goes without problems.

- you can test the returning message path using the test tool in configuration integration

- you can check if the call method of the abap proxy to start the communication has the proper parameters.

Regards,

Matias.