Data Transformation Engine Map Designer Reference Guide

Chapter 8 - Functional Map Basics Input Card Types of a Functional Map
Map Designer Reference Guide
147
Input Card Types of a Functional Map
The input and output cards in a functional map must be in the same order as the
data objects are specified in the map rule argument.
The input card type(s) in a functional map must be coordinated with the input
argument(s).
For example, if the input arguments evaluate to Record, Claim, and LookupFile,
in that order, then the input card types in the functional map must be Record,
Claim, and LookupFile, in the same order.
Input Arguments May Evaluate to Data Objects
Input arguments of a functional map may evaluate to Item or Group type data
objects.
Item Types
When an input argument of a functional map evaluates to an item type, the type
of the corresponding input card must be an item type with the same Item
Subclass (Number, Text, Date & Time, or Syntax).
An input argument might evaluate to a number. If the input argument:
INDEX (Record:File)
evaluates to a number, the corresponding input card type must be an item with an
Item Subclass of Number.
If the input argument is a text literal (for example,
“Mercator”), the input card
type that corresponds to this argument must be an item with an Item Subclass
of Text.
Group Types
When an input argument of a functional map evaluates to a group type, the type
of the corresponding input card must be the exact same group. For example, if the
second input argument evaluates to InvoiceSet, the TypeName of input card #2
must be InvoiceSet.
If there is one argument of the functional map, there will be one input card. The
TypeName on the input card must correspond to the data object specified in the
argument for the functional map.