Show TOC

Function documentationMonitoring of Existing IDocs in Monitoring and Error Handling

 

In this scenario, existing IDocs are monitored in Monitoring and Error Handling in the SAP Application Interface Framework. IDocs are processed in the ALE runtime.

You should use this scenario if you have an existing IDoc, for which you do not want to change the configuration but which you want to monitor with the SAP Application Interface Framework.

Integration

In order to display an existing IDoc in Monitoring and Error Handling, you have to create a raw and an SAP data structure for an IDoc’s basic type and you need to define an SAP Application Interface Framework interface. To do this, use the Generate IDoc Structure and Interface Definition report (transaction code /AIF/IDOC_GEN, see IDoc Structure Generation and Interface Definition).

The raw and SAP data structures are the same. In Customizing for SAP Application Interface Framework (transaction code /AIF/CUST) under Start of the navigation path Interface Development Next navigation step Define Interfaces End of the navigation path, the Move Corresponding checkbox is automatically selected by the system to facilitate using transformation in the technical mode of Monitoring and Error Handling.

In the scenario for processing IDocs shown in the graphic above, the SAP Application Interface Framework is not involved in processing the IDoc and the IDoc from the legacy system is, as always, processed with ALE runtime.

The standard process function, process code, and message type is used. During processing, the data is written to the standard IDoc tables, for example, EDIDC. In the SAP Application Interface Framework, there is no data written to the AIF tables and data is selected from the IDoc tables in order to display the IDocs in Monitoring and Error Handling.

The raw data structure containing the data from the IDoc tables is displayed in the Data Structure view of Monitoring and Error Handling.

The status records written during IDoc processing are displayed in the Log Messages view. If an application log for an IDoc was written, the application log containing the data from the IDoc tables is displayed in the Log Messages view too.

An index table can be maintained. This index table is needed to display IDoc messages in the tree of the Data Message view. If no index table is maintained, the standard single index table is used.

Features

In this scenario, the following are not possible in the SAP Application Interface Framework:

  • Displaying messages in the Interface Monitor

    There are no entries in the AIF index and statistic tables as the IDoc is not processed by SAP Application Interface Framework

  • Creating alerts using and sending e-mail notifications

  • Defining an interface-specific selection screen

  • Using a key fields based search in Monitoring and Error Handling

    There are no index table entries

Activities

In order to display an existing IDoc in Monitoring and Error Handling, engines have to be assigned to interfaces in Customizing for SAP Application Interface Framework under Start of the navigation path Interface Development Next navigation step Additional Interface Properties Next navigation step Specify Interface Engines End of the navigation path as follows:

  • Application engine for IDocs

  • Persistence engine for IDocs

  • Selection engine for IDoc control records

  • Logging engine for IDoc status records