There might be inconsistencies between the Proxy Framework and the SAP Application Interface Framework. The Data Correction Report
(transaction code /AIF/CORRECTION_REPORT) checks for inconsistencies and corrects them. A test mode exists that allows you to check for inconsistencies but not to actually correct them. By default, the Testrun
checkbox is selected.
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 SAP NetWeaver PI message status. These inconsistencies occur if a message, which 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 an SAP NetWeaver PI message was deleted or archived, the corresponding application log written by the SAP Application Interface Framework must be deleted. Inconsistencies must be corrected.
When there are changes made in Customizing for alert recipients, the alert index table might not be updated correctly. Therefore, the table might contain inconsistent records when compared to current Customizing for alert recipients. You can regenerate the messages’ statistics to ensure that no inconsistencies exist and the messages’ statistics can be compressed.
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 are regarded as inconsistent and are 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 deletion or archiving jobs for the Proxy Framework with the following settings:
Namespace
, Interface Name
, and Interface Version
should be blank
Testrun
should not be selected
Check/Fix Deleted or Archived Messages
should be selected
Check/Fix Application Log
should be selected
Regenerate Statistics
should be selected
You can access the Data Correction Report
from the SAP Easy Access menu by choosing .
Recommendation
It is recommended that the Data Correction Report
is run regularly as a background job to ensure that no inconsistencies exist.
Recommendation
It is further recommended that you run the Data Correction Report
after your deletion or archiving job for messages in the Local Integration Engine was executed.