Modeling Web Service Objects in the Back-End

You can either model Web service objects (data types, message types, fault message types, inbound service interfaces, outbound service interfaces, event providers, or data type enhancements) in Enterprise Services Repository (ESR) or directly in the ABAP back-end. This procedure outlines the general principles of modeling Web service objects using the proxy editor. The proxy editor and Enterprise Services Wizard are easy-to-use when following these principles.

Prerequisites

For more information on modeling services in Enterprise Services Repository, see the documentation in the function-oriented view of the application help for SAP NetWeaver on the SAP Help Portal at http://help.sap.com.
You have assigned your namespace to the ABAP back-end as the generating application in transaction SPXNGENAPPL. For more information, see the chapter entitled Proxy Identification in the system documentation. To find this documentation, choose the [Tips & Tricks] icon in transaction SPROXY.

Procedure

Start the proxy editor, for example by double-clicking a Web service object in Enterprise Service Browser.
On the Internal View tab, the proxy editor is divided in two parts. On the left hand side, the object is displayed in a tree. Here, you can use the context menu to add objects or you can drag and drop objects from Enterprise Service Browser or Enterprise Service Repository Browser. Also, you always have a powerful field help at your disposal that only offers objects that are allowed at this particular place.
In case of problems, the proxy editor displays warnings on the bottom of the window that often have long texts. Read through these long texts for helpful hints and solutions to these problems.