EdisphereWhite PapersEDISPHERE – Mapping Simplified (Maps complex hierarchies)

EDISPHERE – Mapping Simplified (Maps complex hierarchies)

EDISPHERE is a comprehensive any-to-any mapping product, having a very intuitive user interface and semantic mapping features, which meets your complex mapping requirement in a simplified manner with very low mapping effort.

Executive Overview

Mapping is the most challenging part of your Electronic Data Interchange (EDI) implementation. The mapping capabilities and the ease of mapping in an EDI translator can exponentially increase your EDI implementation timeline from days to weeks or even months.

Traditionally, EDI refers to X12 and EDIFACT data interchange standards, which have been in existence for over three decades. Over period of years, EDI has assumed new meaning since different data interchange formats have been used for B2B. In this document, EDI is used to generically refer to different file formats used for B2B, including XML, proprietary file formats (fixed length, variable length, comma separated value – CSV), databases and is interchangeably used with B2B. Wherever a distinction is necessary, the same is explicitly mentioned unless it is obvious from the context.

Your business applications and EDI interfaces are developed with an eye toward keeping your long-term IT plans in mind. Similarly your EDI software should also adapt to your changing mapping requirements. EDISPHERE is designed to meet your long-term mapping objectives, such as:

1. Easy to create maps
EDISPHERE has a very intuitive and easy to learn user interface, where your maps can be created using “drag and drop”, “point and click” features. It is loaded with smart and innovative features, which greatly simplifies your complex mapping requirements while significantly reducing your mapping efforts.

2. Mapping messages having dissimilar file types (any to any mapping)
EDISPHERE maps messages from any one format to any other format. Your application-EDI interface may be XML, proprietary file format or database, whereas your partner-EDI interface may be X12, EDIFACT or XML.

3. Mapping messages having dissimilar hierarchies
The hierarchy of message in your application-EDI interface may be very different from that in your partner-EDI interface including cases where:
(a) One EDI interface has a master-detail segment hierarchy whereas the other interface has all masters segments first followed by detail segments.
(b) A segment in one EDI interface is required to be mapped to two or more segments in the other EDI interface.