Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Active Contributor
0 Kudos

As of October 2014 the new version of AIF (3.0) is available and with the new version lots of new functionalities are available. One of them is the preprocessing function. This new functionality can be used in two cases:

- in case you'd like to use an SAP standard Enterprise Service but before it's execution you'd like to change some of the fields - perform a mapping (master data lookup for example)

- in case you have a custom Enteprise Service or a simple custom proxy message and you'd like to implement a mapping without changing the existing code

In both cases it would be possible to implement the mapping in the code of the Enterprise Service/proxy either in the BADI/enhancement spot or in the custom proxy's code but why it is better to use the AIF for doing the premapping:

- you don't need to modify the standard object - how can a standard Enterprise Service be still standard if you change it heavily in the BADI/enhancement ? With AIF you can still call the original Enterprise Service in a second interface without using the new mapping

- BADIs/Enhancements are very often implemented in multiple places of the Enterprise Services or custom proxies and if we want to be able to govern the interfaces easily we should put all mappings in the same place (AIF structure mapping step)

What are the required steps to use the new functionality:

Step 1

Select the preprecessing checkbox in the interface definition of your AIF interface: SPRO - Interface Development - Define Interfaces

Step 2

Next you need to create a mapping: SPRO - Interface Development - Define Structure Mappings.

Select the source and destination structures of your Enterprise Service - in this case it's going to be the same structure. As a next step you can implement a field mapping where you can use the AIF value mapping table to change the values of the fields from your interface.

Only those two steps are required to implement the new functionality, now when you send the new message with the use of this interface the mapping step will be performed as a first step before the standard Enterprise Service gets called.

In the next blogs I will try to show some more new functions of the AIF 3.0.

Labels in this area