Introduction

A map is a set of instructions used to transform data from one format to another. ECMap can create:

Map direction

Transaction maps are said to be either:

An inbound map uses an EDI message to create application data. The EDI message is the input to the map, and it is being sent in to your company from your trading partner.

An outbound map uses application data to create an EDI message. The EDI message is the output of the map, and it is generally being sent from your company out to your trading partner.

ECMap also uses two specialized maps, compliance maps and print maps, which can also be said to have an inbound direction. They are also said to have direction. They are discussed in Chapter 25, “Working with Print Maps,” and Chapter 26, “Working with Compliance Maps.”

In ECMap, each transaction map is associated with a specific EDI standard—X12, EDIFACT, NCPDP, or HL7—and a specific transaction within that standard.

Where maps are stored

Maps are stored in projects. You must have a separate map for each business message that you exchange with a trading partner. For EDI transactions, this means one map per message type, application system, and map direction. The name given to a map often reflects the message type and the direction. For example, an X12 map that uses your company’s internal application data to produce an EDI invoice that is sent to a trading partner might be named 810OUT.

What you can do with maps using ECMap

In ECMap, you can add a new map, select a map, modify a map, delete a map, or copy a map. You can also generate all of the maps in one project, generate all of the maps in all of the projects, or view all of the maps in a project.

Starting point

You perform all map-related actions from the Map window.

StepsAccessing the Map window

  1. Select the Map icon on the main ECMap toolbar

    or

    Choose File>Map>Select from the main menu