Skip to Content
Technical Articles
Author's profile photo Robert Quindt

Value Mapping usage in XSLT Mappings with CPI


I recently got asked by a collegue how to add information to an xslt mapping from a value mapping in SAP Integration Suite/ Cloud Integration for a migration project from SAP PI/PO to SAP Integration Suite. In the specific case he needed a solution to change the IDOC EDI_DC40 field RCVPRN based on the SNDPRN/RCVPRN provided in the input ducument for several sender/ receiver systems and different IDOC Basic types.

I created a xslt mapping to edit the required target field and to add the information dynamicly based on extracted values from the input xml through a value mapping call.

This solution can be reused for all requirements there a xslt mapping is used and information from a value mapping needs to be included in the transformation.

To use this solution you should have basic value mapping, basic groovy script / java and basic xslt knowledge.



Solution overview:

Use the adapter of your choise to send input data to your IFlow. For this blog post I use the HTTPS adapter to post a sample xml via postman to the SAP Integration Suite.



Content Modifier:

I use a content modifier to read the input information from the input xml as xpath parameters. This can also be achieved directly in the Groovy script by analysing the input xml. For simplicity and if you are not so experienced in Java/ Groovy I recomend the usage of the Content Modifier.

Content Modifier


Groovy Script:

In the Groovy script I define variables to hold the information from the Content Modifier.

The variables are then used to call the ValueMapping API for mapping an input value to an output value. This mapped value is then stored as an exchange parameter that can be acces in the xslt mapping afterwards.

import java.util.HashMap;

def Message processData(Message message) {
    def map = message.getProperties();
    sAgency = map.get("inputSAgency");
    sIdentifier = map.get("inputSIdentifier");
    inputValue = map.get("inputValue");
    rAgency = map.get("inputRAgency");
    rIdentifier = map.get("inputRIdentifier");
    def VMservice = ITApiFactory.getService(ValueMappingApi.class, null);
    if( VMservice != null)
        def mappedValue = VMservice.getMappedValue(sAgency, sIdentifier, inputValue, rAgency, rIdentifier)
        message.setProperty("outputValue", mappedValue);
    return message;


XSLT Mapping:

In the XSLT Mapping I access the exchange parameters via a xslt param, which are automaticly linked to the corresponding exchange parameters or header of the IFlow. I use the mapped outputValue in the mapping. If no value mapping is found and the value is null or empty, I copy the input value as a fallback.

<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet xmlns:xsl="" version="3.0" xmlns:xs="" exclude-result-prefixes="#all">
	<xsl:output method="xml" indent="yes" encoding="UTF-8"/>
	<xsl:mode on-no-match="shallow-copy"/>
	<xsl:param name="outputValue"/>
	<xsl:template match="/" name="xsl:initial-template">
	<xsl:template match="//IDOC/EDI_DC40/RCVPRN">
		<xsl:element name="RCVPRN">
				<xsl:when test="string-length($outputValue)>0">
					<xsl:value-of select="$outputValue"/>
					<xsl:value-of select="."/>


Value Mapping:

In the Value Mapping I added a value map for a Source agency “SAgency”, Source identifier “SIdentifier”, Target agency “RAgency”, Target identifier “RIdentifier”. I added a value mapping for a source value “SValue” to a target value “RValue”.

For your purpose you can modifie the corresponding values.




Test the solution:

For testing this solution I use postman. You can use a tool of your choise to the send data to the SAP Integration Suite.

I send a part of an IDOC xml via postman with the SNDPRN as “SAgency” and the RCVRPN as “SValue”. This fields are then extracted in the Content Modifier. The Groovy Script that uses the information for the Value Mapping and in the XSLT Mapping I map the mapped Value “RValue” to the RCVPRN field. In the picture below you can see the input xml and the output xml with the mapped value in the RCVPRN fiel.





Conclusion and further Enhancements:

In this blog post I wanted to show you the usage of a XSLT mapping with a Value Mapping.

Further enhancements to this solutions could be the use of XSLT to access the Value Mapping API directly from the script without the need of a Content Modifier or a Groovy script. For such an aproch you would need to create a seperate Java Class to provide a methode that do the work describet in the Groovy script or to find out, how theĀ  ITApiFactory class can be used in XSLT to get the VMService and exceute the getMappendValue function.

Another useful scenario would be to use this aproach with the combination of an XSLT Mapping created in the Integration Advisor and access the mapped value as a global parameter.

I hope this post is helpful to you and thank you for reading this blog post. Please feel free to share your feedback or thoughts in the comments section.


Best regards

Robert Quindt

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Vijay Konam
      Vijay Konam

      I like the approach. However, wouldn't a graphical mapping addition simplify the solution? It can access Valuemapping as well out of the box. More visual, easily maintainable?

      Author's profile photo Robert Quindt
      Robert Quindt
      Blog Post Author

      Hi Vijay,

      Since we needed to map the RCVPRN in multiple IDOC basic types in my case (ORDERS02, ORDERS05, DESADV, MATMAS) a graphical mapping would mean having multiple graphical mappings, one for each basic type. With a xslt mapping we only needed one because EDI_DC40 is the same in all base types and the xslt mapping simply copies every other node in the xml. This solution is also useful when using the Integration Advisor, as SAP generates a XSLT mapping.

      But the groovy script and graphical mapping approach is also useful if you need to dynamically decide which value mapping to use, as Sriprasad shows in Dynamic Value Mapping in SAP CPI.

      If there is only one basic type, simple mapping, and the value mapping is also static, then an approach with the built-in functionality in the graphical mapping would also be my preferred choice.

      Kind regards