Data Transformation Engine Map Designer Reference Guide

Chapter 8 - Functional Map Basics Using Multiple Inputs in a Functional Map
Map Designer Reference Guide
150
♦ The input arguments must match the input card types, in the same order.
♦ The order of the arguments does not affect the number of times a rule is
evaluated. However, it may affect the order in which the output objects appear
and the performance at run-time. For more information on how rules are
evaluated, see the Functions and Expressions Reference Guide.
In MakeItemRecord, map the PO# and Company from the Header into the
components of ItemRecord. Map the Item, Qty, and Price from the Detail. As
shown in the following figure, some outputs are mapped from Detail, and some
from Header.
Input Objects are Triggers
A functional map is triggered by the presence of the input objects that are
specified as the arguments of the functional map. Each time a new combination of
input objects is evaluated, the functional map is executed.
The functional map MakeItemRecord has two inputs: Detail and Header. One
output ItemRecord is produced for each combination of Detail and Header in
the input. In this example, there is one Header for many Details. The same
Header object is sent to the functional map again and again with each new
Detail.
For a complete explanation of how map rules are evaluated, see the Functions and
Expressions Reference Guide.