Process IDoc Using ALE, Write Index Tables with AIF Enabler

In this scenario, IDocs are processed using ALE runtime and index tables are written by the SAP Application Interface Framework enabler for IDocs.

Integration

You need to create an SAP Application Interface Framework interface and you have to maintain a raw and an SAP data structure. As the raw and an SAP data structure 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 , you must select the Move Corresponding checkbox to facilitate using transformation in the technical mode of Monitoring and Error Handling.

Some settings in Customizing for SAP Application Interface Framework, for example, for structure mappings or actions, are not relevant since the IDoc is not processed with the SAP Application Interface Framework runtime.

This graphic is explained in the accompanying text.

IDoc Processing Using ALE Runtime and Calling AIF Enabler

In the scenario for processing IDocs shown in the graphic above, the IDoc from the legacy system is processed by standard IDoc processing.

A new process function and messages type have to be created. The new process function calls the standard process function.

The SAP Application Interface Framework enabler for IDocs is then called to write SAP Application Interface Framework-specific table entries. The SAP Application Interface Framework enabler for IDocs is responsible for writing index tables and message statistics and for creating alerts.

It is also possible to write an SAP Application Interface Framework-specific application log. If a message is selected and an AIF application log is written, this application log is loaded into the application log view. If no AIF application log is written, the status records and application log the process function has written are loaded into the application log view in Monitoring and Error Handling. Whether an application log is written or the status records are used depends on the logging engine maintained in Customizing for SAP Application Interface Framework under Start of the navigation path Interface Development Next navigation step Additional Interface Properties Specify Interface Engines End of the navigation path .

Note Note

For performance reasons, writing an SAP Application Interface Framework-specific application log is optional and the SAP Application Interface Framework enabler for IDocs avoids transforming the complete IDoc data into the SAP structure.

End of the note.

Since the IDoc was not processed with the SAP Application Interface Framework runtime, there is no data link between the Log Messages view and the Data Content view.

Features

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

Defining recipients for alert management
Grouping messages by key fields in Data Messages view
Maintaining interface-specific selection index tables
Defining an interface-specific selection screen, which can be used to facilitate a selection of messages if customized

Activities

You have to assign engines to interfaces in Customizing for SAP Application Interface Framework under Start of the navigation path Interface Development Next navigation step Additional Interface Properties Specify Interface Engines End of the navigation path as follows:

Application engine for IDocs
Persistence engine for IDocs
Selection engine for index tables
Logging engine for IDoc status records