Transaction mapping and any-to-any mapping

In this chapter, transaction mapping and any-to-any mapping are discussed separately. First, transaction mapping is broken down into inbound transaction maps and outbound transaction maps. (There are slight differences between the mapping-related actions available in each and the way in which some actions are performed.) Within the two types of transaction map, there is a detailed explanation of actions related to EDI segments, actions related to EDI elements, actions related to the application data, mapping actions, and the “Find” function. After both types of transaction maps are discussed, any-to-any mapping is explained.

You can get to the transaction Mapping window or the Any-to-Any Map window from the main ECMap window either by selecting on the toolbar or on Work Space or by choosing Mapping from the Build menu. If the current map is a transaction map, the transaction Mapping window displays. If the current map is an any-to-any map, the Any-to-Any Map window displays. In addition, the Mapping window is automatically displayed after you create a transaction.

The Mapping window for transaction maps is divided into three sections – Source, Destination, and Mapping – with Source data on the left, Destination data on the right, and the Mapping section at the bottom.

For the Mapping section at the bottom of the window, a description for each column is listed below.

**Table 13-1: Mapping window description**
Column	Description
Level	Hierarchical number that is used in map flow
Segment	EDI Standards identifier for the segment
Element	The position of the element within the segment
Sub-Element	Position of the component within the element
Repeat No.	If an element can repeat, this number indicates which number is in the sequence of the repeating element
Record	The name of the record that contains the field that is mapped to the element
Field Name	Name of the field mapped to the element
Type	Data type of the element
Requirement	Specifies the status of the segment M – a mandatory segment must occur at this point in the transaction. O – an optional segment may occur at this point in the transaction. C – a conditional segment is required only if a specific condition exists. N – a segment is not used because the standards were created from an implementation guide R – a segment is required because the standards were created from an implementation guide S – a segment may occur if the standards were created from an implementation guide.
Minimum	Specifies the minimum length of the element as defined in the standard
Maximum	Specifies the maximum length of the element as defined in the standard
Number	Numeric identifier of the EDI element
Description	Name of the EDI element
Rule Type	The type of rule to be performed, for example Prior or Post
Rule	Number of the rule attached to an element
Table	Name of the cross-reference table associated with an element
Condition 1	When you set a condition for a segment in the Condition 1 field, the condition is shown in this field
Condition 2	When you set a condition for a segment in the Condition 2 field, the condition is shown in this field
TP Type	If a segment or element is linked to a specific trading partner, the “Trading Partner Type” (blank or NOT) is shown in this field
TP	If a segment or element is linked to a trading partner, the name of the trading partner is shown in this field
Notes	If you have entered informational notes about an element, they are shown in this field
Mandatory	Specifies whether the mapping is mandatory for the application field
Truncate	Specifies whether ECMap truncates data (without issuing a warning) when the field length to which data is mapped is shorter than the field length from which it is mapped. (This is a good choice if you know truncation will occur and do not want to see warnings in your log.)
Zero Fill	If you choose Zero Fill, ECMap adds leading zeroes to a field and output a zero if the application field is a numeric zero
Justification	For Justification, you can make one of three choices: Left Justification – indicates that data begins in the leftmost position of the record field. Left Justification without Trim – indicates that data begins without removing any leading spaces in the leftmost position of the record field. Right Justification – indicates that data ends in the rightmost position of the record field. If you choose None (the default justification), ECMap uses default justification for the record field. The default justification for alpha-numeric fields is left-justification, and the default justification for numeric fields is right-justification.

The Any-to-Any Map window is divided into four sections. There is a Source data section on the left, and a Destination data section on the right. Rather than extending all the way across the bottom of the window, the Mapping section is between the Source and Destination sections at the bottom. Above the Mapping section is a split window that allows you to view and perform intermediate mapping steps.