Proxy error : INTERFACE_REGISTRATION_ERROR

[Former Member]

We have two proxy - proxy scenarios between SUS and SRM

1) PO creation in SRM

2) PO Cancel in SRM

PO creation is working good, but in PO cancelation ...Proxy is thorwing an error in SRM (target ABAP system)

Proxy error : INTERFACE_REGISTRATION_ERROR

No implementing class registered for the interface (ABAP interface, request message

I did search the forums, we have correct role of business system in SXMB_ADM in target system which is Application Sytem

PO cancellation proxy is active.

Both proxies PO creation and PO cancelation are using same RFC destination, since PO creation is succesfully executed, I am expecting there is no issue with RFC destination.

Please share your thoughts..

[Former Member]

Hi

go to SPROXY transaction in ABAP system and check for the service Interface and see if you can see an active proxy available for that service interface....if not then you have to activate the service as per the SRM documentation.

thanks...

Karna

[Former Member]

Hi, I came across this error once a partner sent a message without payload (0 bytes). Check also the following:

Does the incoming message have a payload?

If yes, is the message type of the payload correct, meaning does the message type of the payload corresponds with the one defined in inbound service interface?

Regards, Martin

[baskar_gopalakrishnan2]

Proxy error : INTERFACE_REGISTRATION_ERROR

No implementing class registered for the interface (ABAP interface, request message

The above error shows abap proxy classes are not implemented. THat means either abap proxies are not generated in sap system or after generating proxy objects they are not implemented using application logic. This is a known issue.

[Former Member]

Thank You for the response.

But proxies are already implemented by SAP as this is a delivered interface

FYi..We have imported the standard content of SRM into ESR. I have created a configuration scenario with all required.

Interface determination looks like this

Sender

Communication Component: BXX_100

Interface : PurchaseOrderCancellationRequest_Out

Namespace : http://sap.com/xi/SRM/Procurement/Global

Receiver

Communication Component: BXX_200

Receiver Interfaces

Operation mapping - blank nothing is given

Receiver Interface-PurchaseOrderCancellationRequest_In

Namespace - http://sap.com/xi/SRM/SupplierEnablement/Global

Here is the ERROR

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

<SAP:Category>XIProxy</SAP:Category>

<SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>

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

<SAP:P2>PurchaseOrderCancellationRequest_in</SAP:P2>

<SAP:P3>http://sap.com/xi/SRM/SupplierEnablement/Global</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message PurchaseOrderCancellationRequest_in, request message, namespace http://sap.com/xi/SRM/SupplierEnablement/Global)</SAP:Stack>;

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

</SAP:Error>

[Former Member]

Vamsi,

May be it is with the Business system setup, but it shoud fail the other message also anyhow please check this...

Go to SXMB_ADM in PI and check the Business system role as below...if it is Application server then you should change it to IS

--Got to SXMB_ADM.

--Execute Integration Engine

--EDIT-> Change Global configuration data

--Select the Role of Business System as Integration Server.

thanks...

Karna....

[Former Member]

I have checked the payload it looks good.

Checked SXMB_ADM in PI, Role of Business System is Integration Server

Proxies are active in target system.

De registered XBQ* ques and re - registered again.

Also checked if XIAPPLUSER (which proxy carries) has permissions to do cancellation.

Security is telling it got all the required roles.

Unfortunately issue still remains... for PO Cancelation, where PO Create is working good as mentioned earlier.

[Former Member]

Vamsi,

Here is one more thing, if this is a sync call and if you are using report to invoke the Proxy call then you should be implementing execute.syncronous method for inbound interface so that you will receive the reply back...

Thanks....

Karna....