Data Transformation Engine Type Designer Reference Guide

Chapter 9 - Partitioning Introduction to Partitioning
Determining When to Partition
There are some cases in which you will need to partition your data and others in
which you will want to partition your data. You are required to partition for
unordered data when a data object at a certain place in the data stream can be
any number of types and each type has different definitions. Choose to partition
for convenience, either to simplify mapping rules or to put additional logic into
your data’s definition.
Required Partitioning
Partitioning is required when components are randomly or partially ordered. The
following example represents unordered data:
BGI – 13100,REM,931104,19970424…
AXR – 10930,INV,003X114,19970422…
PVY – 19496,ORD,PO-104-1499,19970425…
BGI – 13100,ORD,PO-182-2587,19970425…
AXR – 10930,INV,003X-114,19970422…
PVY – 19496,REM,931104,19970424…
The file shown contains three different types of transactions: Invoice, Order, and
Remittance. Each transaction has a different definition based on the type of
information it represents.
Partitioning for Convenience
You may decide to use partitioning in your type tree to build additional logic into
the definition of your data. You may also use partitioning to simplify the rules
needed in your map.