Improve SAP NetWeaver PI Value Mapping Performance in a High-Volume Situation

  • by Huaqiao Aaron Long, Support Consultant, Technology CoE NetWeaver Foundation XPI, SAP Active Global Support
  • September 12, 2011
Value mapping in SAP NetWeaver Process Integration can take up a lot of processing time and lead to poor performance. Learn how memory is consumed in high-volume scenarios with a large number of value mapping groups, which key factors affect performance, and what to do to achieve the best performance when using value mapping functionality.
Key Concept
An interface field can have different representations in the sender system and receiver system, depending on the context in which it is used. Value mapping is a standard SAP NetWeaver Process Integration function to map different representations of an interface field to each other. The mapping rules (including context, agency, and schema for source values and target values) are stored on table XI_RUNVALMAPGR. The value mapping table contents can be edited by manual input using the user interface of the Integration Directory or replication from external data sources using a specialist interface. During run time, the target value is retrieved according to the mapping rules by Java mapping or message mapping, which calls the standard value mapping function.

Frequent access to databases via SQL to retrieve data causes performance issues. A cache is introduced to transparently store data in memory so that future requests for that data can be served faster. The consumption of memory also creates system performance issues due to the high volume of processing it requires. You can use value mapping functionality in SAP NetWeaver Process Integration (SAP NetWeaver PI) to map some functions to others in an interface field to reduce the processing time by its internal cache mechanism.

In this article, I’ll use a simple business scenario to explain the value mapping rules. I’ll use a postal code and area description. Each postal code can be mapped to an area description in more detail. In this integration scenario, legacy system A is the sender and SAP ERP Central Component (SAP ECC) system B is the receiver. The data from sender system A uses the postal code. The data is sent to system B via SAP NetWeaver PI. Using value mapping, the system can look up and map the area description using information provided by the postal code from the sender XML payload. The SAP ECC receiver system receives the data with the area description instead of the postal code.

I’ll start by showing how to maintain the value mapping groups. I’ll show you examples to demonstrate how the volume of the value mapping groups affects memory consumption and how the key factors affect the performance. In the end, I’ll explain how to customize the value mapping function to allow you to cache only a small number of your critical value mapping groups. This article is intended for SAP NetWeaver PI consultants, developers, and administrators.

Huaqiao Aaron Long

Huaqiao (Aaron) Long is a senior SAP consultant specialist in SAP NetWeaver PI at SAP Active Global Support (SAP AGS). He is responsible for helping customers implement and operate their SAP solutions at their maximum potential and to manage their technical risks during solution implementation and operation. He has been with SAP AGS for seven years based at SAP China, with a three-year rotation working at SAP AG and one year working at SAP Americas.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.