Skip to Content

You are wondering about how to set up interfaces with the SAP Application Interface Framework? Or you want to know how you can make use of the new features of the SAP Application Interface Framework 2.0? Then you have found the right place to look for this kind of information.

In this space we will provide useful information for interface developers and everyone else who wants to facilitate implementing interfaces, monitoring and error handling with the SAP Application Interface Framework.

In case you are business user, don’t run away. You are also very welcome to have a look into this space. You will also find usefull hints here on how to do monitoring and error handling with the SAP Application Interface Framework.

First of all I’d like to give a short overview of what the SAP Application Interface Framework is:

The SAP Application Interface Framework is an add-on that provides you with a structured way to implement your interfaces. An interface consists of different interface building blocks, for example value mappings, actions and checks. The SAP Application Interface Framework does not only support you in implementing interfaces, you are also able to do monitoring and error handling. Actually, the monitoring and error handling of the SAP Application Interface Framework is targeted at business users. They usually know best how to solve functional errors that occurred during processing of a message. Since the SAP Application Interface Framework supports multiple interface technologies, monitoring and error handling can be done in the same transaction independent of the technology used for processing the message.

If you want to develop an interface with the SAP Application Interface Framework the best place to get information is the Cookbook. Within the cookbook all customizing activities are described, that are needed for defining an interface in the SAP Application Interface Framework.

The SAP Application Interface Framework 2.0 offers additional features, that are not described in the cookbook. For now I’d like to give you a short overview.  A description of how you can make use of those new features will be available soon in this topic space.

  • Monitoring and Error Handling for IDocs: For integrating your IDocs with the SAP Application Interface Framework four different scenarios exists:
    • Monitor existing IDocs
    • Process IDocs with SAP Application Interface Framework and call IDoc function in action
    • Process IDocs with SAP Application Interface Framework and call BAPI or any other function in action
    • Use the Enabler for IDocs to create index table entries and alerts
  • Persistence and Runtime of the SAP Application Interface Framework: With the SAP Application Interface Framework an own persistence and runtime is delivered that offers a fast and parallel message processing
  • Enabler: The Enabler allows you to monitor existing interfaces with the SAP Application Interface Framework without much effort. You can make use of functionalities like index tables, interface specific selection screens and alerting.
  • Integration of Error and Conflict Handler: The SAP Application Interface Framework offers you the possibility to monitor ECH interfaces (e.g. asynchronous SAP Enterprise Services). Vice versa it is also possible to monitor interfaces of the SAP Application Interface Framework in ECH (note: this is only possible if you have NetWeaver 7.31 and AIFX installed).
  • SIW template: A template for the Service Implementation Workbench is delivered that allows you to generate interfaces for the SAP Application Interface Framework (note: this is only possible if you have NetWeaver 7.31 and AIFX installed).
  • Web Application for Monitoring and Error Handling (note: to use the Web Application it is necessary that you use NetWeaver 7.31 and AIFX is installed)
  • Custom Specific Engines: In order to support different interface technologies different engines are delivered with the SAP Application Interface Framework. If the engines delivered do not fit your requirements it is also possible to create your own customer specific engines.
To report this post you need to login first.

10 Comments

You must be Logged on to comment or reply to a post.

  1. Michal Krawczyk

    Hi Verena,

    is there a way to do automated reprocessing in case of failed messages just like we have with IDOCs? (for example for locked transactions which will get unlocked within a few minutes and there is no need for business users to have a look at them in case of error as the reprocessing after a few minutes will solve the issue each time?)

    Thank you,

    Regards,

    Michal Krawczyk

    (0) 
    1. Verena Woerner Post author

      Hi Michal,

      no, AIF does not provide the possibility to do automatic reprocessing. But you can do a mass restart in the Message Summary. The Message Summary is an aggregated view of all log messages of the selected interface/namespace in the Interface Monitor. If you select a line and click Mass Restart, all data messages that contain the selected log messages will be restarted.

      Best regards,

      Verena

      (0) 
    2. Nicolas Busson

      Hi Michal,

      Funny enough I’ve just finished reading your sap press e-bites about AIF where you seem to have found a way to answer your own question, via serialization options… And it was a great read!

      Thanks for this very nice piece of work.

      Nick.

      (0) 
  2. vijay Kumar

    Hi Verena,

    AIF has a control on interface level authorization to business users. Can we restrict specific business users to re-process specific interfaces by correcting the data .

    Regards

    Vijay

    (0) 
  3. Shaun Jones

    Hi Verena,

    Just looking for a clarification if you don’t mind…  In the graphic in much of the AIF literature (and in associated text) we see that AIF supports the interface between the proxy and a) a standard function b) a customer function or c) a BAPI.  What seems to be missing is a OO method. I’m assuming OO methods are supported but was just looking for clarification in case there’s some restriction I may be not understanding.

    Thanks!

    Shaun

    (0) 
      1. Shaun Jones

        Hi Michal,

        Thanks for your response.  I should have been more clear.  In the cookbook and SAP’s AIF architecture overview it states:

        “Within and action, you can call an SAP standard function, your own customer-specific function, or a BAPI”

        My question was more towards that end.  The graphic and text in the cookbook make several mentions of business object methods (not OO methods), BAPI’s or function modules are allowed but it never explicitly states OO methods are allowed.  I don’t have access to AIF currently otherwise I’d just go in and play around and figure it out so was just hoping for a clarification on whether OO methods are allowed for the AIF actions.

        Thanks!

        Shaun Jones

        (0) 
        1. Verena Woerner Post author

          Hi Shaun,

          yes, you can also use OO methods in an AIF action.

          An AIF action consists of one or more action function modules. Within a function module you can also call an OO method.

          Best regards,

          Verena

          (0) 

Leave a Reply