MovingMercedes-BenzInterfaceMonitoringtoSAPAIF

Interface monitoring is easier to run when it is part of the SAP standard rather than a separate product to maintain. At Mercedes-Benz, Codemine contributed technical consulting and AIF architecture to the integration team, supporting the move from a third-party monitoring tool to SAP Application Interface Framework (AIF).

Client

Mercedes-Benz

Industry

Automotive

Period

2021–2023

Codemine role

AIF architecture, technical consulting and ABAP leadership

Moving Mercedes-Benz Interface Monitoring to SAP AIF

Photo: Alexander Migl, CC BY-SA 4.0, via Wikimedia Commons

Interface monitoring moved from a separate third-party product into SAP’s own AIF, and the same work showed project teams what AIF could do for a new solution.

01

Context

Mercedes-Benz ran its interface monitoring on a third-party product, on an SAP ECC 6.0 landscape. SAP AIF, the standard solution for this task, is also part of the S/4HANA package.

Moving to AIF therefore meant replacing a separate tool with the SAP standard. The work took place in the integration team, together with an upgrade of AIF to a newer enhancement package.

02

The challenge

The integration landscape relied on a third-party product for interface monitoring. Moving this capability to SAP AIF meant migrating the existing monitoring setup while also upgrading AIF to a newer enhancement package level.

The migration had to cover demanding scenarios, including interfaces processing large files and SAP PI messages that needed to be processed in the correct order.

Interface monitoring moves from a third-party tool to SAP AIF, which then covers heavy file processing and PI message serialization. The same AIF know-how fed a proof of concept for press machines.
FIG. 1Interface monitoring moves from a third-party tool to SAP AIF, which then covers heavy file processing and PI message serialization. The same AIF know-how fed a proof of concept for press machines.

03

Our approach

  1. 01

    AIF upgrade

    AIF was upgraded to a newer enhancement package level, giving the migration a current foundation.

  2. 02

    Migration to AIF

    The interface monitoring set up in the third-party tool was moved to SAP AIF, including the AIF setup for the migrated interfaces.

  3. 03

    Heavy file interfaces

    Interfaces that process large files were set up in AIF, one of the demanding scenarios the migration had to cover.

  4. 04

    PI message serialization

    SAP PI messages that must be processed in a fixed order were serialized, so they arrive in SAP in the right sequence.

  5. 05

    A proof of concept for press machines

    In parallel, an ABAP/AIF proof of concept was built for a new greenfield solution for press machines, supported by AIF training and presentations for project teams.

04

Results

Interface monitoring moved to the SAP standard

The migration replaced the third-party monitoring tool with SAP AIF.

An upgraded AIF foundation

The AIF enhancement package upgrade was part of the integration scope.

Support for demanding interface scenarios

Work covered heavy file interfaces and PI message serialization.

A proof of concept for new solutions

AIF training, presentations and a PoC supported a greenfield solution for press machines.

05

Technologies

SAP AIF · SAP ECC 6.0 · SAP PI · ABAP · File interfaces · Message serialization · Interface monitoring

Replacing a third-party monitoring tool with SAP AIF?

Talk to Codemine about moving interface monitoring to the SAP standard, from AIF setup to complex file and message scenarios.

/MORE CASE STUDIES
All case studies →