Show TOC

Procedure documentationMeasure Interface Performance Locate this document in the navigation structure

Procedure

The performance of the SAP Application Interface Framework can be measured using the Performance Tracking transaction (/AIF/PERFORMANCE_TRACKING). Using this performance analysis tool, you are able to detect time-consuming routines and processes within the SAP Application Interface Framework.

Using tracking variants available in this transaction, you can track the performance of specific objects within the SAP Application Interface Framework. These objects include particular interfaces, users and time ranges.

Goals

The goals of the performance optimization process and the Performance Tracking transaction include:

  • Measuring interface performance in back-end systems

  • Determining the area for performance improvements (for example, interface-specific logic, interface framework and so on.)

  • Defining measures for bottlenecks with most saving potential

  • Implementing performance improvement measures

  • Confirming the positive impact of performance improvement measures

Scope

The scope of the Interface Performance Measuring is defined for all interfaces via SAP Process Integration and the SAP Application Interface Framework.

The following are measured:

  • ABAP Proxy

  • SAP Application Interface Framework

  • Interface specific logic (for example, value mappings, validations and so on)

  • Posting logic (for example BAPI and so on)

The following are not measured:

  • Legacy extractors

  • Transmission of data (for example, file transfer, MQSeries and so on)

  • SAP Process Integration

Set Up Tracking

In order to track performance, a variant needs to be set up. You can either select a variant that already exists or create a new variant. If you select an existing variant, the corresponding data for the variant is loaded into the fields on the screen.

If a variant has not been created, the default values are shown in the selection screen of the transaction and the variant is marked as unsaved. While creating a variant in the selection screen, you can specify a message ID, namespace, interface name, interface version and the name of the user starting the message. You can also insert the minimum duration and the time range.

You can start tracking by selecting the Start Tracking button. You can stop tracking by selecting the Stop Tracking button.

Analyze Results

Performance issues are expected in the areas of:

  • Interface-specific logic

  • SAP Application Interface Framework

  • Posting logic (for example, SAP BAPIs)

Examples of performance issues in those areas are:

  • Frequent selection of identical data (for example, function modules that are customized on an item level in the SAP Application Interface Framework)

    ->Possible solution: buffering in hashed internal table

  • Slow Select-Statements (for example, database index not used)

    -> Possible solution: usage of database index if available; creation of database index, if feasible; database access via alternative table

  • Long read access to internal tables

    -> Possible solution: usage of sorted or hashed tables; usage of field-symbols

  • Long runtime of SAP BAPIs

    ->Possible solution: check for user exits with poor performance; redesign of interface if BAPI supports “multi-post”