Skip to end of metadata
Go to start of metadata

This Wiki page primarily tries to explain performance issues that occur during Data Correction, for example deadlocks, long runtime, problems during interface processing, etc. For further information about the Correction please visit SAP Help Portal

AIF Correction Report checks inconsistencies in message status between /AIF/IFMON Interface Monitor and /AIF/ERR Error Handling, or standard persistency tables. To reach this function use transaction AIF/CORRECTONS. On the appearing screen there is possible to customize the Correction Report.

Important information

  • Most of the issues stem from not using the correct selection parameters for the report. For this reason, it is important to select only those checkboxes that are really needed. 
  • Report should be executed in background mode, and scheduled to a timeframe when there is little chance of processing on an interface, ideally at weekends, or at night. The frequency should be based on observed inconsistencies in message statistics, status, or application logs.
  • Depending on the use case, archiving prior to using correction report is suggested for legacy data in the system, reducing the number of messages to be corrected by the report.
Below is a description to help you navigate through the settings.


This page is part of:

AIF Wiki

Tiny link (useful for e-mail):

https://wiki.scn.sap.com/wiki/x/RY2KIQ

Generic Selection

In this section, the user can specify the appropriate namespace and interface.

Always execute the report on exact Namespace / Interface / Interface Version combination, where the error occurs!

Otherwise the Correction Report will run on all interfaces, which can cause long runtime and dumps. The same problem arises if they are left blank. 

Always execute the Data Correction Report in Test mode first and use checkbox "Output Execution Details", to have a general knowledge about what will be fixed by the report. Once the report parameters have been set, you can turn off the test mode.

Package Size for SELECT and DELETE: Default values are recommended to be kept.

  • In case of slowness (long runtime of background job): performance issue the package size can be increased by an additional 20%, when correcting interfaces with large volume of data
  • In case of memory overflow issue: (dump: SYSTEM_NO_ROLL or TSV_TNEW_PAGE_ALLOC_FAILED ) the package size can be reduced by 20% 

Field

Description

Output Execution Details

Indicates whether or not the details of the executed report are displayed on the screen.

Test Run

Indicates whether the fixings should be saved to the database or if the report should only be executed in test mode.

Correction with Date Range

Restrict the time and date for a specific range where data should be corrected. Without this selection, the report will consider all the available data for an interface with the parameters selected below. Depending on interface activity this could mean millions of messages, thus increasing the runtime of the report, and can cause further performance degradation. The single index table of the interface is the main point of selection for the correction report. 

You can look up the number of messages in the interface index table in SE16 transaction. Perform a selection for the same Creation Date.

The interface index table can be found in AIF Customizing IMG ( Transaction /AIF/CUST ) Error Handling → Define Namespace-Specific Features → Input the selected 'Namespace' and Continue  Find the single index table name under the column Message Index Table Name.

If this is left alone, AIF uses the standard interface index table for this interface: /AIF/STD_IDX_TBL

If a fix is performed or not, depends on the Test Run checkbox. If the 'Test Run' checkbox is selected, no changes will be made to the corresponding database tables.

Field

Description

Dependencies

Performance Impact

Further Info

Check/Fix Messages with Cancelled status

Indicates whether or not checking and fixing should be executed for SAP Netweaver PI messages with the status Cancelled.

There might be inconsistencies between the message status in the Proxy Framework and the status in the single index tables in the SAP Application Interface Framework. A message is inconsistent if the status of a message in the Proxy Framework is Canceled but the status in the single index table was not updated. This inconsistency will be corrected.

Medium

Apply this fix when messages in Integration engine (SXMB_MONI) are shown in status canceled. The corresponding message in AIF is still in the earlier processing status.

Check/Fix Messages with Successful status

Indicates whether or not checking and fixing should be executed for SAP Netweaver PI messages with the status Successful.

There might be inconsistencies between the message status in the Proxy Framework and the status in the single index tables in the SAP Application Interface Framework. A message is inconsistent if the status of a message in the Proxy Framework is Successful but the status in the single index table was not updated. This inconsistency will be corrected.

Medium

Message got processed in Integration engine monitor, but status was not updated to AIF. This is a possible case when reprocessing happened from Integration engine monitor (SXMB_MONI), and not directly from AIF (/AIF/ERR). Use in conjunction with 'Check/Fix Message Index Table' checkbox

Check/Fix Deleted or Archived Messages

Indicates whether or not the report will check and fix SAP Netweaver PI messages which were already deleted or archived.

There might be inconsistencies between the message status in the Proxy Framework and the status in the single index tables in the SAP Application Interface Framework. A message is inconsistent if it was already deleted or achieved in the Proxy Framework but has a different status/still exists in the single index tables. Furthermore, a message is inconsistent if data in the application log still exists for the message. This inconsistency must be corrected.

Medium

PI housekeeping processes change the status of the messages in the ABAP backend, causing inconsistency in AIF status.

PI Archiving Conceptual Overview

Check/Fix Message Index Table

Indicates whether or not the message index tables should be checked and fixed.

There might be inconsistencies between the single index table and the SAP NetWeaver PI message status. A message is processed in the SAP Application Interface Framework and errors are recorded. If this message will be reprocessed successfully by the Proxy Framework and not with the SAP Application Interface Framework, the message status can be inconsistent. This inconsistency must be corrected.

Medium

Use together with 'Check/Fix Messages with Successful status' checkbox

Check/Fix Application Log

Indicates if the application log should be checked for consistency. Inconsistencies will be fixed.

If an SAP NetWeaver PI message was deleted or achieved, the corresponding application log written by the SAP Application Interface Framework should be deleted. Inconsistencies must be corrected.

Medium

This check does not apply in case AIF Application log is used as a Logging engine. If other logging engines are used,

Check/Fix Alert Index Table

Indicates whether or not the alert index tables will be checked for inconsistencies and whether or not those inconsistencies will be fixed.

In case of any changes in the Customizing of the alert recipients, the alert index table might not be updated correctly. Therefore, the table might contain inconsistent records compared to current recipient Customizing.

This inconsistency must be corrected.

High

During a message processing based on the logs of a message recipients are determined. In case the recipient customizing has been changed, use this option to redetermine the recipients


 Correction of Message Statistics

Selecting these checkboxes blocks message processing on the selected interface. Use this setting carefully!

Regenerate and Compress Statistics options are independent of date restriction, and meant for rearranging message statistics in tables /AIF/MSG_STATALL and /AIF/MSG_STAT, affecting message statistics in Interface Monitor according to currently assigned recipients. This exclusive lock on tables causes performance issues and is the most time consuming. This option is best to be chosen once archiving, and data deletion has been already executed.

The checkbox for HANA DB systems are not required to use.

Field

Description

Dependencies

Performance Impact

Further Info

Regenerate Statistics

Indicates whether or not message statistics should be regenerated for the selected interfaces.

The regeneration of the messages statistics will only be triggered if run in Save mode.


If you observe any erroneous statistics, ask your administrator for regeneration.

High


Compress Statistics

Indicates whether or not message statistics should be compressed.

If the Test Run checkbox is not selected, the message statistics will be compressed.

For technical reasons, every system process involved in message processing writes its own entries in the statistics tables. These entries can be aggregated to reduce the size of the statistics tables and increase performance of the SAP Application Interface Framework.

High


Correction of XML Persistence Table

❗Use these settings only if requested by SAP Support. Otherwise, leave the checkboxes blank❗

Field

Description

Dependencies

Performance Impact

Further Info

Delete Inconsistent Messages

Indicates whether or not the report will delete XML persistency messages with interface keys that are not in the single index table.

There might be inconsistencies between the entries in the XML persistency table and the single index tables in the SAP Application Interface Framework.

For example, a message with a certain key has been deleted from a single index table but there is still a message with the same key in the XML persistency table. This entry will be deleted.

Medium


Delete w/o IF Key

Indicates whether or not the report will delete XML persistency messages which do not have interface keys.

There might be messages stored in the XML persistency table that do not have interface keys (namespace, name, version).

These entries cannot be deleted in conventional ways, for example, during an archiving run. These entries will be deleted.

Medium


Correction of Message Variables Table

These tables are for advanced message processing in /AIF/IFMON, when message becomes obsolete, the message variable table should also be updated.

Field

Description

Dependencies

Performance Impact

Further Info

Delete Inconsistent Messages

Indicates whether or not the report will delete inconsistent messages in the message variables table /AIF/MMSG_VARS with message keys that are not in the index table.

There might be inconsistencies between the /AIF/MMSG_VARS table and the index tables in the SAP Application Interface Framework.

For example, a message with a certain key has been deleted from an index table but there is still a message with the same key in the /AIF/MMSG_VARS table. This entry will be deleted.

Low



Check note 2724401 for job /AIF/SAP_AIF_CORRECTION for older release for example S4CORE 101

  • No labels