on 2011 Mar 02 10:07 PM
We recentently implemented the Enterprise Services Repository and I am in the process of ramping up my knowledge on the use of this tool. I've been doing a lot of reading, trial and error to get my head wrapped around the concept.
Incidently we are running ECC 6.0 and Composition Environment 7.1.
But I have a question that I have been unable to find an answer to...
1. It is my understanding I can develop multiple operations per service interface which will then be translated to class methods when I generate the proxy in the ABAP environment. However, I am currently my first operations is being renamed EXECUTE_SYNCRHONOUS, and the remainder named as I had created them. From my reading I understand that this was correct for a previous versions of ES. Is there EP or a note that needs to be applied to our system to correct this behavior or is how it is supposed to be?
Thank you in advance.
Hi,
On ECC side if you apply SAP_BASIS SP14 then EXECUTE_SYNCRHONOUS and EXECUTE_ASYNCRHONOUS methods will disappear once you create proxy (existing proxies won't change).
Read this blog from Michal: /people/michal.krawczyk2/blog/2009/06/20/pixi-abap-proxies-say-goodbye-to-executeasynchronous-method
Regards,
Gourav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
70 | |
10 | |
10 | |
7 | |
6 | |
6 | |
6 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.