Show TOC

Procedure documentationDetect and Correct Inconsistencies Locate this document in the navigation structure

Procedure

There might be inconsistencies between the Proxy Framework and the SAP Application Interface Framework. The Data Correction Report checks for inconsistencies and corrects them. The report is executed using the Corrections transaction (/AIF/CORRECTIONS).

A test mode exists that allows the user to check for inconsistencies but not to actually correct them. By default, the test mode is activated. For further information on the available selections, please refer to the corresponding field help in the system.

The following inconsistencies can be fixed:

  • There might be inconsistencies between the message status in the Proxy Framework and the single index tables in the SAP Application Interface Framework. These inconsistencies can occur if a message was canceled, deleted or archived in the Proxy Framework, but the status was not updated in the single index tables of the SAP Application Interface Framework.

  • There might be inconsistencies between the message index table and the PI message status. These inconsistencies occur, if a message ended with errors in the SAP Application Interface Framework is restarted with the Proxy Framework and processed successfully. In this case, the status in the SAP Application Interface Framework might not be updated.

  • If a PI message was deleted or archived, the corresponding application log written by the SAP Application Interface Framework must be deleted. Inconsistencies must be corrected.

  • Where there are changes in the Customizing of the alert recipients, the alert index table might not be updated correctly. Therefore, the table might contain inconsistent records when compared to current recipient customizing.

  • Additionally, the user can regenerate the messages’ statistics to ensure that no inconsistencies exist and the messages’ statistics can be compressed.

It is recommended that the Data Correction Report is run regularly as a background job to ensure that no inconsistencies exist.

It is further recommended to run the transaction after your deletion or archiving job for messages in the Local Integration Engine was executed. When running the Data Correction Report, the system checks for messages that exist in the message index tables of the SAP Application Interface Framework, but not in the Proxy Framework. These will be regarded as inconsistent and deleted from the message index tables of the SAP Application Interface Framework. It is recommended to also delete the corresponding application log messages. Hence, the Data Correction Report should be planned as a background job after execution of the archive / delete jobs for the Proxy Framework with the following settings:

  • Namespace, Interface Name, and Interface Version should be blank

  • Testrun must be unchecked

  • Check/Fix Deleted or Archived Messages must be checked

  • Check/Fix Application Log must be checked

  • Regenerate Statistics must be checked