Application engine for IDocs

In order to display IDocs in the SAP Application Interface Framework, the application engine for IDocs is used. The application engine for IDocs enables the users to restart and cancel all IDocs displayed in Monitoring and Error Handling.

Persistence engine for IDocs

The persistence engine for IDocs retrieves an IDoc’s data records. Furthermore, the persistence engine locks and unlocks the IDoc. After an IDoc is edited, the persistence engine updates the IDoc’s data records.

Logging engine for IDoc status records

If the IDoc was not processed with the SAP Application Interface Framework, the status records written by the IDoc runtime have to be read from EDIDS. In order to display the status records in the Log Message view of Monitoring and Error Handling, the status records are added to a temporary application log. If a segment number and field name exists in the status record, it is possible to navigate from the Log Message view to the erroneous field in the Data Content view. If the IDoc has written its own application log, the log content is also displayed in the Log Message view.

Selection engine for IDoc control records

For IDocs processed without the SAP Application Interface Framework, no index table entries exist and the data has to be selected from the IDoc control records. In order to determine which IDoc belongs to which interface, you need to maintain the basic type and message type. Optionally, you can maintain a logical message variant and logical message function. You can maintain these in Customizing for SAP Application Interface Framework (transaction code /AIF/CUST) under  Interface Development Assign IDocs Types . In the Selection Screen of Monitoring and Error Handling, you can select by namespace, interface name, and version. You can also select by status, creation date, and IDoc number.