This is the "classic" AIF scenario. Interfaces are built - mainly based on Customizing - with the SAP Application Interface Framework. Monitoring of the interfaces is done in AIF. Due to the very high integration and synergy between interface development and ongoing monitoring inside one single tool, this scenario provides excellent benefits.

 

This scenario can be used based on top of multiple interface technologies (for example, web service, IDOC, qRFC, bgRFC, and customer-specific technologies).

 

Scenario 2 - Monitoring

In scenario 2, AIF is only used for monitoring. This scenario provides very quick wins and benefits for customers who want to have a very efficient and business-centric monitoring tool but who have existing interfaces or who have specific reasons to use another interface technology instead of AIF. This scenario can be used to monitor existing interfaces and requires very few changes or adaptions.

 

To monitor existing interfaces, a surrounding AIF interface is required to tell the framework what to monitor.

 

Scenario 3 - Runtime

This scenario can be used in cases where functions from AIF runtime should be re-used, (for example checks, mappings, and actions), without the need for monitoring, (for example, synchronous call where error handling is done in the calling application).

 

This enables you to call logic from the framework for multiple use cases while having an excellent governance through a structured and central view and handling of interface logic instead of doing it locally in multiple different tools and technologies.

 

Underlying Basis Technologies

 

The SAP Application Interface Framework allows you to implement and monitor interfaces of different interface technologies. The support of several technologies is delivered with AIF:

• Proxy XI Runtime
• AIF Runtime XML
• Files
• ALE / IDoc
• Web Service
• Enterprise Service, and

 

Furthermore, the monitoring and error handling of AIF can be extended to also support other technologies. This can be done with custom code without having to modify the monitoring and error handling. In this way, it is possible to support, for example:

• CIF
• qRFC
• bgRFC
• MWB
• or any other customer-specific technology.

The Interface Monitor provides an overview of the different interfaces a user is responsible for. It is available with a SAP GUI and a web-based user interface.

 

The Interface Monitor consists of two main parts:

• Message Overview:
  Provides a personalized overview of the interfaces the user is responsible for. Displays the overall status (Okay, Caution, Errors, and Undefined) of an interface. Also, the number of messages for each status (Warnings, Application Errors, Successfully Processed, Technical Error, and In Process) is displayed. As well as the number of messages for each status, the sum of all messages is displayed. If the interface uses key fields for recipient determination, the key fields are also displayed.

   

• Calendar:
  With the calendar, you can restrict the data range for the information shown in the message overview. This can be done by selecting dates in the calendar control. Days where messages are found in the system are highlighted as follows depending on the highest error status:

   

  • Red: There are error message for this day (successful, canceled and warning messages may also have occurred).
  • Yellow: There are warning messages (successful or canceled messages may also have occurred; there are no error messages).
  • Green: There are only successful or canceled messages.

   

  If the calendar is not displayed, press the Without Date Restriction button .

   

  Possible Activities in the Calendar:

  • • 1
    • 2
    • 3
    • 4