Data Transformation Engine Map Designer Reference Guide

Chapter 6 - Map Rules A Map Rule is an Expression
Map Designer Reference Guide
106
An expression can be complex and have simpler expressions nested within it.
Examples of more complex expressions using nested expressions are shown
below:
IF (Qualifier = “ST”, Address, NONE)
LOOKUP (ProductCode:LookupList, ItemCode:Data =
ItemCode:LookupList)
EXTRACT (Record:Input, Company Field:Record:Input = “My
Company”)
COUNT (EXTRACT (Row:Input, Company Column:Row:Input = “My
Company”))
These examples use the functions IF, LOOKUP, COUNT, and EXTRACT. These
functions are specific to the Integration Broker suite of products. Functions have
their own syntax. For more information on functions, see the Functions and
Expressions Reference Guide.
Map Rules Define How to Generate Data Objects
The object of an output card may be composed of components and partitions.
Each object on the output card has a corresponding rule cell, where map rules that
transform that data are entered.
A map rule evaluates to a particular data object. The data object is either a group
type or an item type. The following rule evaluates to the data object Record,
which is a group:
= LOOKUP (Record:Input, Company:Record:Input = “ABC
Printing”)
A map rule for a data object must evaluate to a data object with the same
subclass. Objects with an Item Subclass of Date & Time must evaluate to an
object with an Item Subclass of Date & Time.
For example, the output item ShipDate has the Item Subclass of Date & Time.
The following map rule:
ShipDate = ShipToDate:PO:Input
is valid when the data object ShipToDate also has an Item Subclass of Date &
Time.