When you specify multiple partitions in a target load order group that uses mapping variables, the Integration Service evaluates the value of a mapping variable in each partition separately. The Integration Service uses the following process to evaluate variable values:
It updates the current value of the variable separately in each partition according to the variable function used in the mapping.
After loading all the targets in a target load order group, the Integration Service combines the current values from each partition into a single final value based on the aggregation type of the variable.
If there is more than one target load order group in the session, the final current value of a mapping variable in a target load order group becomes the current value in the next target load order group.
When the Integration Service finishes loading the last target load order group, the final current value of the variable is saved into the repository.
Use one of the following variable functions in the mapping to set the variable value:
The following table describes how the Integration Service calculates variable values across partitions:
Variable Value Calculation Across Partitions
Integration Service calculates the final count values from all partitions.
Integration Service compares the final variable value for each partition and saves the highest value.
Integration Service compares the final variable value for each partition and saves the lowest value.
Use variable functions only once for each mapping variable in a pipeline. The Integration Service processes variable functions as it encounters them in the mapping. The order in which the Integration Service encounters variable functions in the mapping may not be the same for every session run. This may cause inconsistent results when you use the same variable function multiple times in a mapping.