A map is a set of instructions used to transform data from one format to another. ECMap can create the following maps:
Transaction maps use EDI standards data in the mapping process, either as input or output.
Any-to-any maps use application data as both the input and the output. An any-to-any map can use EDI data, but it treats the EDI data as application data, rather than standards data.
You can add, select, modify, copy, or delete maps. You can also generate all maps in one project, generate all maps in all projects, or view all maps in a project.
Transaction maps are said to be either inbound or outbound.
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.
ECMap also uses two specialized inbound maps, compliance maps and print maps. See the ECMap User’s Guide for more information on these two maps.
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.
In ECMap, each transaction map is associated with a specific EDI standard—X12, EDIFACT, NCPDP, or HL7—and a specific transaction within that standard.You assign a map type when you create a new map.
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.
Accessing the Map window
You perform all map-related actions from the Map window.
Click the Map icon on the main ECMap toolbar or Choose File > Map > Select from the main menu.
