Skip to Content

Server proxy method name and interface operation name

Hi all,

I have successfully used inbound server proxies on several occasions. Each time, without thinking about it, I took the default option where the OPERATION name == the SERVICE INTERFACE name. When the proxy is generated, the ABAP method is the OPERATION name and everything works nicely.

This time however, I tried something different and built a service interface (PMNotification, as example) with the operation name 'Create', thinking that I could also have a second operation 'Update' (for example). The ABAP proxy method then becomes CREATE, but I then get 'NO IMPLEMENTING CLASS....' errors. If I change the operation name to match the interface name and regenerate, everything works again.

SO, my question is this : Is is true that the OPERATION name MUST equal the INTERFACE name for an inbound server proxy ??

If this is the case, then a (inbound) service interface can only have one operation; this doesn't seem right.

Looking forward to any insight.


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Jan 17, 2011 at 04:37 AM
    If this is the case, then a (inbound) service interface can only have one operation; this doesn't seem right.

    Open your service interface in ESR and press F7....if the proxy cannot be generated you would probably get an information on this....inbound SI can have multiple operations but then it seems to be a limitation in case of proxy.

    Also if your operations have different types of messages (combinations of message type and external definitions etc) then you face such limitations.

    Some reference from Michal's blog:

    Now the method that you need to call from to send an ABAP Proxy message has exactly the same name as a method 
    inside the Service Interface objects in Enterprise Service Repository (ESR is a successor of Integration Repository - IR) like 
    shown in the picture below:



    Edited by: abhishek salvi on Jan 17, 2011 10:08 AM

    Add a comment
    10|10000 characters needed characters exceeded

    • Thanks for that Abishek.

      Your response seems to confirm what I found - that there is a limitation for inbound proxies which forces the use of the same name for the service interface and the operation (and, by extension, that there can only be one operation for this type of proxy). This is not highlighted in the ESR when checking where no syntax problems are shown.

      I have been able to add a new operation to the same service interface - GetDetail for example - without a problem in the ESR. This is the behaviour I would expect. It should be (and is) possible to create an interface with one or more operations, each representing a corresponding method. In fact the proxy generates OK in ABAP with the new method GET_DETAIL. The problem arises only at run time when I get an interface registration error. This is alluded to in post multiple-operation-in-service-interface and one or two others.

      I guess this is an unfortunate 'feature' of ABAP server proxies.

      Thanks anyway,


  • Posted on Nov 24, 2011 at 02:40 AM

    See the replies. An unsatisfactory state of affairs !

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.