Data Transformation Engine Map Designer Reference Guide

Chapter 8 - Functional Map Basics Output Card Type of a Functional Map
Map Designer Reference Guide
148
Functional maps do not require InputData and OutputData settings.
Note If InputData and OutputData settings exist in input and output cards in a
functional map, they are ignored when the executable map is compiled.
Output Card Type of a Functional Map
The type of the output card in a functional map is the type whose map rule
includes the functional map name. For example, if the functional map name is
entered in the rule cell for CarRecord(s), the output of that functional map must
be CarRecord.
The output of a functional map must match the output data object (where the
map rule that calls the functional map is), therefore a functional map has only one
output card.
Note A functional map may have only one output card.
Entering Map Rules
Map rules of a functional map are entered to generate to the desired output of the
functional map. Similar to an executable map, output data is generated in the
specified format. This specified format is determined by the type properties of the
type on the output card.
Essentially, a function maps a single data object for every data object received
from the input.
Using Multiple Inputs in a Functional Map
A functional map may require more than one input. For example, you are mapping
an input purchase order to an output purchase order. The input PO consists of a
header and multiple details. The output PO is composed of a series of item
records. Each ItemRecord contains the PO# and the company name, which must
be mapped from the Header of the input PO. Each ItemRecord also contains
item, quantity and price information, which is mapped from a Detail in the input.
You need a functional map to generate an ItemRecord. The inputs of the
functional map would be everything that is necessary to generate one
ItemRecord: both the Detail and Header from the input. A suitable name for
the functional map may be MakeItemRecord.