<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap__Mastering_IDocs__Proxy_Interfaces_File_Ad_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2025-01-16T09:44:29.000Z

Building and Monitoring Inbound Interfaces

<div id="content"><p tabindex="0">SAP Application Interface Framework enables you to implement and monitor inbound and outbound ABAP proxy interfaces.</p><p tabindex="0">Review the following steps and diagram for an asynchronous inbound interface:</p><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Asynchronous Inbound Steps as outlined in the steps below." alt="Asynchronous Inbound Steps as outlined in the steps below." src="/service/media/BIT751_04_en-US_media/BIT751_04_en-US_images/Unit2_Asyn_Inbound_Steps.png" tabindex="0"><div class="imageCaption"></div><ol><li tabindex="0">Generate an ABAP proxy from a service interface.<ul style="list-style-type:disc"><li tabindex="0">As a prerequisite to creating an SAP Application Interface Framework interface for an inbound proxy, you need a service interface. The service interface is created in the ESR or MDR and is not the task of the SAP Application Interface Framework interface developer.</li><li tabindex="0">For this service interface, an inbound proxy class has to be generated in the back end system.</li></ul></li><li tabindex="0">Implement the proxy method by simply calling SAP Application Interface Framework and passing the input data and exception name to /AIF/CL_ENABLER_PROXY=&gt;PROCESS_MESSAGE( ): You must pass the proxy method’s input structure and the exception class’ name.</li><li tabindex="0">Create the destination structure: Another prerequisite is the destination structure. You have to create this structure. What the structure should look like depends on the BAPIs, function modules, and so on, that should be called in the SAP Application Interface Framework action.</li><li tabindex="0">Create an SAP Application Interface Framework interface, and maintain the proxy class and destination structure.<ul style="list-style-type:disc"><li tabindex="0">An SAP Application Interface Framework interface has to be created. You have to specify the name of your inbound proxy class; the raw structure and the record type should then be inserted automatically.</li><li tabindex="0">Furthermore, you have to specify the SAP structure (destination structure). The engines used for inbound proxy messages are the default ones, therefore, you do not have to change anything here.</li></ul></li><li tabindex="0">Create a structure mapping, value mappings, actions, and so on, for the interface.</li></ol></div>

Asynchronous Inbound Interface

<div id="content"><div class="section"><p tabindex="0">With the SAP Application Interface Framework, you can monitor and implement your own customer-specific proxy interfaces. Without SAP Application Interface Framework, you would usually implement the proxy’s method with some custom-specific code to execute your business logic. With Application Interface Framework, you simply call Application Interface Framework and pass the data received by the proxy to SAP Application Interface Framework. The logic, for example, mapping and checks, is moved to SAP Application Interface Framework.</p><div class="kalturaVideoLessonWrapper"><div aria-label="" class="kalturaVideoLessonContainer" data-testid="video" id="1_6o57id07"></div></div><div class="kalturaVideoLessonWrapper"><div aria-label="" class="kalturaVideoLessonContainer" data-testid="video" id="1_q7qkklgg"></div></div><div class="kalturaVideoLessonWrapper"><div aria-label="" class="kalturaVideoLessonContainer" data-testid="video" id="1_pnzsfry5"></div></div></div></div>

How to Use a Customer-Specific Inbound Proxy Interface

Managing SAP Application Interface Framework

Task 48_Create a Proxy to Send Data to AIF.mp4

In this demonstration, you will learn more about how to create a proxy to send data to AIF. Let's create a service interface. Enter SE80 in the transaction field. Select the required object. Select Create and then Enterprise Service. Then the service provider. And continue. The backend has already been selected. Now select Continue. Fill the name field. and the namespace field and then continue. The package has already been entered. Fill the request or task field. Then the prefix field. Select Continue. And complete. We can now see the service provider details. Let's add operations to the service interface. Select Internal View. Right-click the value shown. Select Add Operation. fill the name field and continue right click the value shown now select set request and then select existing message type fill the type field the name field and the namespace field select continue and copy right click the value shown then select add fault and then select existing fault message type fill the name field and the namespace field select continue then copy next save and activate and activate let's create a proxy class implementation select properties then select the value shown select the value shown we can now see the display mode select the display mode select the icon to switch to the change mode You can add the coding is shown. Now select pattern. The ABAP objects patterns has already been selected. Select Continue. Fill the class or interface field. Then the method field. And, okay, you can pass the input from the proxy method to IS input and the name of the exception class to parameter IV exception class name of method process message. The method implementation appears as in the code shown. Now select Save, and activate. We can now see a dialog showing all items that the system is set to activate. Now select Continue. We have successfully created a proxy to send data to AIF.

Task 49_Create and Map an Inbound Proxy Interface.mp4

In this demonstration, we will learn how to create and map an inbound proxy interface. First, let's define an interface. Enter /N/AIF/CUST in the transaction field. Go to interface development and then select define interfaces. Fill in the namespace. Select Apply. And then new entries. Fill in the interface name and interface version. And interface version. Use the existing structure as the destination structure. When creating an inbound interface, the SAP data structure is the destination structure. Fill in the description. SAP data structure. And then, proxy class inbound. We can now see that the raw data structure and record type in raw structure are filled automatically. When an inbound interface is created, the raw data structure is created, the raw structure is Raw data structure is the source structure. If the fields are not filled automatically, check if the proxy class is active. Open the Interface Direction List. Select the desired option, and then save. Select Continue and exit. Next, let's check if the correct engines are set for the proxy interface in AIF. Select additional interface properties and then, specify interface engines select apply and then the required interface interface. Open the application engine list and select the Required Engine List and select the Required Application Engine List and select the Required Persistence Engine List. The persisted data is selected from the Proxy Framework by AIF. The message also restarts here. Select Proxy for Application Engine and Persistence Engine if it is NetWeaver 7.31 or PI is used as middleware. By default, selection engine and logging engine are selected. Select Save. Continue. And then, back. Let's see how to map the source structure containing the booking data to the corresponding destination structure. Select interface development and then define structure mappings. Fill in the interface name and interface version. Select Apply and then new entries. Open the input help to search for the source structure. Select booking data. Then OK. And save. And then continue. Select the required source structure. And then assign destination structure. Select new entries. Fill in the number of structure mapping. Open the input help to search for the destination structure. Select booking data. Then OK. Select Save. And continue. Now, let's see how to add a data element for a conversion or a conversion routine. Select Define Field Mappings. and then new entries. Fill in the destination structure. And field name one. Select Next Entry. Now, create three more entries using the data. For this demo, the data has been entered for you. Select Next Entry. Open the input help to search for the field in destination structure. Select Flight Date. and then OK. Open the input help to search for the field name one. Select the required field name and then OK. Now, let's add a data element for conversion. Fill in the data element for conversion. Open the direction of conversion exit list. And select the desired option. Select Save. And then, Then back. Let's add value mappings for fields that cannot be directly mapped. Select new entries. Fill in the field in the field in destination structure. Now, add value mappings for other fields of Airline ID destination structure. For this demo, these steps have been performed for you. Select next entry. Fill in the destination structure. Now, add value mappings for other. fields of connect ID destination structure. For this demo, these steps have been performed for you. Select Save, then back. We can now see that the value mappings have been added for the fields. We have now seen how to create and map an inbound proxy interface.

Task 50_Use Actions in an Inbound Proxy.mp4

In this demonstration, we will learn how to use actions in an inbound proxy. Now, let's assign an action. Enter /n/aif/cust in the transaction field. Go to interface development and then select define structure mappings. For this demo, the data is already entered. Select apply, then assign actions. And new entries. Fill the action number, namespace, and action, select enter, then yes, select continue, then save, and continue. Now select the action. Check the main component type, which is the interface's SAP data structure type. Select exit, and save. The record type in Assign Actions remains empty. Select Exit. Now let's test the interface. Enter SE80 in the Transaction field. The package and package number are already filled. Select Enterprise Services and then Service Providers. Now select the desired service provider. Then Test. And Execute. An XML file can be seen with some data. Select XML Editor. For this demo, the data is already entered. Select Save. Fill the description. Select Continue. And Execute. Select Extras. Trigger Commit Work. And then exit. Now let's check the message. Enter /N/AIF/ERR in the transaction field. Fill in the namespace. Interface name. And interface version. Select select all. Then execute. Expand the items pane. Select the message. Then booking data. In test environment, content will not be persisted. Creators created in S-proxy do not persist. We have now seen how to use the actions in an inbound proxy.