Start of Content Area

Background documentation Standard Functions  Locate the document in its SAP Library structure


Values of elements or attributes of the XML message (the payload ) are technically speaking a string. Therefore, all standard functions that operate on field values expect string arguments and return a string value. Nevertheless, the transferred value can of course have a different semantic data type, namely, the one that you specified when you defined the schema for the payload for the field. Standard functions exhibit the following standard behavior:

      Depending on the standard function, data type conversions are used to ensure that the values are transferred in a format suitable for the function (using a cast). If the value cannot be interpreted, the mapping runtime triggers a Java exception.

      If-clauses evaluate conditions that return Boolean values. Standard functions that return Boolean values return the string true or false. Standard functions that expect Boolean values interpret the values “1” and “true” (not case-sensitive) as true and all other values as false.


See also: Runtime Behavior

Overview of Functions

Data-flow objects for standard functions are structured as follows:

      Most data-flow objects have two or three inbound channels on the left-hand side, and one outbound channel on the right-hand side.

      If-functions are shaped as rhombuses or triangles.

      There are also conversion functions with one inbound and outbound channel and functions that return a value without any input.

      Standard functions that require additional specifications are indicated with a star (This graphic is explained in the accompanying text). To call the dialog for Function Parameters, double-click the data-flow object.

The following figure provides an overview of all the different forms of data-flow objects:

This graphic is explained in the accompanying text

To illustrate how the individual functions are used, the input boxes in the figure above have the variables X, Y, Z or I, and the result variable is either R or O. All standard functions in the tables below are described using these input and output variables. In the data-flow editor, other data-flow objects that are connected to the functions using the connecting boxes either return the input values or receive the result of the operation. You can combine the functions in any way you require (provided that the values transferred to a function can be interpreted).

Function Category: Arithmetic

You can only enter numerical values for this category (this includes values with digits after the decimal point). If the value cannot be interpreted as a digit, then the system triggers a Java exception. Otherwise, all calculations are executed with the precision of the Java data type float. The format of the result value depends on the result:

      If the result is a value with digits after the decimal point, these remain unchanged.

      Exception: If a zero follows the decimal point, then this is cut off. This means that the result of the calculation 4.2 0.2 is 4 and not 4.0.

Also note that Java values of type float are converted to the second system before the calculation. The result is calculated there and then this result is converted back to decimal format. The conversion may result in decimal places in the dyadic format that are periodically repeated and then automatically cut off. In the decimal system, this can result in inaccurate results (example: 2.11 + 22.11 = 24.220001). If the number of positions after the decimal point is to be restricted to two, for example, in the case of values for a currency, you can format the values after the calculation by using the standard function FormatNum.


If the particular usage case requires more detailed results, you can also select the decimal system as the basis for the calculations. The Java class BigDecimal is used for internal purposes. For more details see SAP Note 958486.

Function Name



R = X + Y


R = X - Y


R = true, if value X equals value Y, otherwise R = false. The values are interpreted numerically, therefore the value 1.5 is the same as 1.50.


O = Absolute value of I


R is the square root of X


R is the square of X


R = 1, when X is a positive number

R = 0, when X equals 0

R = 1, when X is a negative number


R = -X


R is the reciprocal of X


R = XY


true, when X < Y, otherwise false


true, when X > Y, otherwise false


R = X * Y


R = X / Y


R = Maximum of values X and Y


R = Minimum of values X and Y


O = The smallest possible integer value (up to minus 'infinite’) that is not smaller than the argument I. Corresponds to the Java function java.lang.Math.ceil().


O = The largest possible integer value that is not larger than the argument I. Corresponds to the Java function java.lang.Math.floor().


O = Integer value that is closest to the value of argument I. Corresponds to the Java function java.lang.Math.round().


O = Number of calls for this target-field mapping where you specify the initial value and the increment of the counter in the function parameters.


Converts I according to a pattern that you define using the function parameters. The possible patterns are the same as in the Java class java.text.DecimalFormat.

Function Category: Boolean

All functions in this category expect Boolean input values (see above).

Function Name



R is true if X and Y have the value true. Otherwise, R is false.


R is true if X or Y have the value true. Otherwise, R is false.


      O is false if I has the value true

      O is true if I has the value false


Compares both Boolean values X and Y and returns true if both are equal, otherwise false. Non-Boolean values are interpreted as false (see above).

Use the functions equalsS or compare from the Text category to compare strings.


R = Not(Equals(X,Y))


      If condition X is fulfilled (returns true): R = Y

      If condition X is not fulfilled (returns false): R = Z


If condition X is satisfied (returns true): R = Y. Which Else value the function should return depends on various different factors (see detailed documentation).

Function Category: Constants

Since these functions do not have any input values, they are generating functions.




O gets any string constant that you can enter in the dialog for the function parameters.


For a frequently occurring element, copies the value at a defined position in the source structure to the assigned target field.


O gets the name of the sender business system. Test_Sender_System is output when you test the message mapping in the Integration Builder.


O returns the name of the receiver business system. Test_Receiver_System is output when you test the message mapping in the Integration Builder.

Function Category: Conversions




Executes a value mapping using a fixed value table that you complete using the function parameters. The table is saved together with the most current message mapping and can only be used once.

Value mapping

Executes a value mapping for the value I entered. In the function parameters, assign the both input value I and source value O to a representation in the value-mapping table. In this way, you can assign source and target structure fields to a representation. You complete the value-mapping table on the configuration maintenance screen in the Integration Builder. Since these entries are not available at design time, the mapping result is just an estimate when you test the message mapping. See also Value Mapping


The runtime interface for value mappings has changed for XI 3.0. However, XI 2.0 message mappings that call the Value Mapping function still function using the old runtime interface. To use the function parameters in the new runtime interface, choose XI 3.0 Interface.

In the function properties for the standard function Value mapping, in the fields Agency and Schema, enter the key for the source or target value. These values can have any values. However, you can also refer to the fields SenderParty, SenderService, ReceiverParty or ReceiverService. The mapping runtime replaces these values at runtime with the values from the corresponding fields in the message header of the message for which a value mapping is being executed.


In the field Agency you can also enter the name of a business system. When transporting value mappings from one Integration Directory to another, the Integration Builder sees if you have entered a business system as the agency and converts it during the transport (see also: Configuring Groups and Transport Targets).

Function Category: Date

The following functions enable you to define the date format for the source or target format using the dialog for the function parameters.


The format adheres to the convention as defined in the standard Java class java.util.SimpleDateFormat. The function parameters dialog provides you with a wizard that you can use to enter the most frequently used date formats.




Returns the current date using O. This function is a generating function.


Converts date format I to another date format O.


R = true, when date X comes before date Y, otherwise false


R = true, when date X comes after date Y, otherwise false


R = 1, when date X is after date Y
R = 0, when date X is the same as date Y
R = -1, when date X is before date Y

Extended Settings

It is not only date formats that are country-specific; the count for weekdays and calendar weeks is also country-specific. You can specify the relevant conventions for these in the function parameters:

      First Weekday
Specifies which day of the week is recorded as the first weekday. In the United States, for example, the first weekday is Sunday, while in France, it is Monday. The count begins at 1. The mapping runtime sets this attribute using the Java method
setFirstDayOfWeek(). For more information, see the Java documentation under

      Minimum Number of Days Required in First Week
Specifies how many days the first week of the year must have for it to be considered the first calendar week. The mapping runtime sets this attribute using the Java method
setMinimalDaysInFirstWeek(). For more information, see the Java documentation under

Using the checkbox Calendar Is Lenient, you can control whether invalid dates trigger exceptions or not. If the checkbox is checked, the mapping runtime permits a date such as February 942, 1996, which is then interpreted as the 941st day after February 1, 1996. An exception is not triggered. The mapping runtime sets this attribute using the Java method setLenient(). For more information, see the Java documentation under

Function Category: Node Functions




If there are structuring elements in your target structure that do not exist in the source structure, insert them using this function. Using condition I you can control whether the element is inserted or not. You connect the element in the target structure using O.


Removes all higher-level contexts of a source field. In this way, you can delete all hierarchy levels and generate a list.


Replaces the value I with a value that you can define in the dialog for the function parameters.


O = true, if the source field assigned to inbound channel I exists in the XML instance. Otherwise, false.


Inserts a context change for an element.


Deletes all values from all contexts from the inbound queue except for the first value. Empty contexts (= ResultList.SUPPRESS) are replaced by empty strings. Only one queue remains, which consists of contexts that contain just one value each. Finally, all internal context changes are deleted, so that all values belong to one and the same context.


Replicates a value of a field occurring once to pair it as a record with the values of a field occurring more than once.


Sorts all values of the multiply-occurring inbound field I within the existing or set context. The sorting process is stable (the order of elements that are the same is not switched) and it sorts the values in O(n*log(n)) steps. Using the function parameters, you can specify whether values are to be sorted numerically or lexicographically (case-sensitive or non case-sensitive) and in ascending or descending order.


Like sort, but with two inbound parameters to sort (key/value) pairs. The sort process can be compared to that of a table with two columns.

      Using the first parameter, you pass key values from the first column, which are used to sort the table. If you have classified the key values as numeric in the function parameters, they must not be equal to the constant ResultList.SUPPRESS. See also: The ResultList Object

      Using the second parameter, you pass the values from the second column of the table.

If there is a discrepancy between the number of keys and values, the mapping runtime triggers an exception. The function returns a queue with the values sorted according to the keys.


Replaces empty contexts in the inbound queue with a default value, which you specify in the function parameters.

If “Default” is the default value and
A|B1,B2| |C| |D
is the inbound queue,
mapWithDefault returns the following outbound queue:
A | B1,B2 | Default | C | Default |D.

The function corresponds to the following combination of standard functions:



This function has two inbound queues, which must both have the same number of values. To generate the result queue, the function takes the values from the first queue and combines them with the context changes from the second queue.

Function Category: Statistics

The functions of this function category are designed for source fields that occur more than once in the source structure (maxOccurs = i > 1).




R = Sum of values X1 to Xi of a context.


R = Average of values X1 to Xi of a context


R = Number of fields in a context (i)


R = Index i of Xi. In the function parameters, you specify the following: the initial value of i, the increment, and whether the index value is to be reinitialized at the beginning of every new context, or whether it is to have the same value for the entire source structure.

Function Category: Text


In position specifications, the 0 position corresponds to the first character in the string.




Returns a substring O for a string I. Use the dialog for the function properties to specify the position of the substring. Example: substring(“Hello”, 0,1) = “H”, means that the substring from Startindex 0 to Endindex 1 (not including position 1) is shown.


R = Linking of strings X and Y (without blanks).

Example: X = „Mrs.“; Y = „Miller“; R = „Mrs.Miller“. Use the dialog for the function properties to insert a separator in the string.


R = true, if string X equals string Y, otherwise R = false.

(2 input parameters)

R = first position at which string Y is found in X and –1 if Y does not occur at all.

(3 input parameters)

R = first position from position Z at which string Y is found in X and –1 if Y does not occur at all.

(2 input parameters)

R = last position at which string Y is found in X and –1 if Y does not occur at all.

(3 input parameters)

R = last position from position z at which string Y is found in X and –1 if Y does not occur at all.


Compares string X with string Y:

R = 0, when the strings are equal
R = positive number i, when X is lexicographically larger than Y
R = negative number i, when X is lexicographically smaller than Y

i specifies the difference between the two strings lexicographically.

The function acts in the same way as the compareTo() method of the JDK class java.lang.String.


X: String in which something is to be replaced

Y: String to be replaced in X

Z: String to replace Y

R = String in which each occurrence of Y in X is replaced by Z.


X = "sparring with a purple porpoise"

Y = “p”

Z = “t”

R = "starring with a turtle tortoise"



O = Length of string


R = true when Y is the last string in X; otherwise false.

(2 input parameters)

R = true when Y is the first string in X; otherwise false.

(3 input parameters)

R = true when Y matches X from position Z; otherwise false.


Converts all lower case letters in I to upper case letters.


Removes all white space characters (spaces, tabs, returns) at the start and end of a string. Acts the same as the trim() method of the JDK class java.lang.String.


Converts all upper case letters in I to lower case letters.






End of Content Area