Generating a Proxy 

Use

ABAP proxy generation enables you to generate an ABAP proxy for an interface in the Enterprise Services Repository. This generates an ABAP Objects interface and an implementing ABAP Objects class (in the case of an inbound interface) or an ABAP Objects class (in the case of an outbound interface), and all the required data types. The ABAP proxies have the task of sending or receiving messages and converting internal data structures into XML (or the other way round).

In our example, a fully-implemented ABAP Objects class and all the required data types are generated for your outbound interface.

Perform the following steps in the client that represents your travel agency.

Procedure

...

       1.      Start the transaction ABAP Proxy Generation. To do this, choose Exchange Infrastructure → ABAP Proxy Generation (transaction SPROXY) in the user menu.

       2.      In the navigation tree, expand the software component version MyTutorial<Abbreviation>, 1 of <YourName>, followed by your namespace http://MyTutorial<Kürzel>.

       3.      Expand the subnode Service Interface (outbound).

       4.      Double-click the service interface BookingOrderCancelationRequest_Out. By doing this, you start proxy creation.

       5.      On the following screen, confirm by choosing Yes.

       6.      On the following screen, you must enter $TMP in the Package field and a prefix in the Prefix field. We recommend using a three-figure abbreviation and an underscore (for example, ZBC_). The prefix is represented below with <p>_

The prefix must begin with either Y or Z.

The prefix is required to avoid naming conflicts with other users of the demo example. You are free to choose any prefix, but it must be unique. For this reason, SAP recommends that you use <p>_, though <p> is the abbreviation of your namespace. If a prefix has already been assigned, naming conflicts may occur (see step 8). If a naming conflict occurs, choose another prefix.

       7.      On the following screen, choose Continue. The system determines which objects to generate.

       8.      In the display area of the ABAP proxy generationtransaction, select the Name Problems tab page.

First check which naming conflicts have occurred. We recommend the following if there is a naming conflict with the prefix:

- Terminate processing.

- Look at the prefixes that have been used to date. For example, in the Class Builder (SE24) you can search for classes CO*CANC* in package $TMP.

- Choose a prefix that has not already been used and restart the proxy generation.

       9.      The names for the structures that have been created by the system are displayed. The message type and data type were given the same name in the Enterprise Services Builder. However, in the Data Dictionary, you cannot create two different structures with the same name. Therefore, an appendix is added automatically.

To improve readability, we recommend changing the proposed names as follows:

○       Class name: CO_<p>_BOOKING_ORDER_CANCEL

○       Data type: <p>_BOOKING_ORDER_CANCEL

○       Lower-level data type: <p>_BOOKING_ID

○       Message type: <p>_BOOKING_ORDER_CANCEL_MT

To determine which names the system has given the message type, select the Structure tab page. This displays the assignment of names and structures.

   10.      Save the proxy as a local object (package $TMP).

   11.      Activate the proxy from the menu.

On the Generation tab page, you can display additional details for the generated objects.