What Is An EDI Mapping?
An EDI Mapping defines the translation of data structures from a proprietary file (in csv format, txt, SAP IDoc, ERP-specific etc.) to an EDI mapping standard format (EDIFACT, ANSI X12 etc.) and vice versa. On the one side the corporate ERP can integrate the data automatically and on the other side a standard based format can be sent to any trading partner which uses EDI and adheres the same EDI formats.
The EDI converter tool converts data (messages) from the ERP system into the established EDI mapping standard in place. For data to be exchanged electronically between EDI trading partners, both parties need to agree on an established EDI mapping standard which is defined by various organizations such as the UN, ANSI, VDA or DIN.
In addition to the global EDIFACT and the North American ANSI X12 standard, there are other regional or industry-specific EDI message standards.
From a pure syntax perspective, an EDI format strictly has to follow the established EDI mapping standard. With an EDI converter tool from SEEBURGER, a multitude of other data formats found on the market can be integrated.
Most retailers and automotive vendors are “EDI hubs” and publish their own EDI guidelines for their EDI communication and EDI data structures. In these guidelines, they explain which segments, elements and codes they use and which are mandatory or optional. This has the advantage of narrowing down the general EDIFACT andANSI X12 message structures. The disadvantage is that the EDI process becomes more complex when suppliers deal with many customers that use their own EDI guidelines for their own EDI mapping documents.
As a result, suppliers need a specific EDI mapping for each of their customers, and then they typically need a direct mapping for each of their EDI customers — and each mapping must be written, tested and maintained.
During conversion, the information from the source structure is transferred to the target structure using an individually-created mapping. This 1:1 translation is called "direct mapping" or 1:1 mapping, and it uniquely describes the data relation structure between both trading partners.
Canonical (Indirect) EDI mappings greatly simplify writing, change management and maintenance of mappings with message format definitions as with an EDI message. Canonical (Indirect) EDI mappings provide a partner mapping with standard format definitions that are unique for the respective trading partner and convert the EDI message into an abstraction layer format.
A company-specific mapping takes the data from the abstraction layer and converts it to the in-house format that the receiver’s ERP system can consume. This type of indirect EDI mapping approach makes the conversion of an EDI format (e.g. SAP IDoc conversion) easier because it scales better.
SEEBURGER uses SEEXML — a canonical format developed by SEEBURGER.
SEEXML Trading Partner mappings are available for more than 10,000 trading partner relations. For each ERP-system and business process, there is one unique process map. On the partner side, there is one ready-to-use partner map that is specific to a trading partner and comes from the SEEBURGER mapping repository.