This week in our Support Services blog we would like to continue our discussion about the most common documents which are exchanged between Support Services and our valued eBridge customers.

Just to re-cap: we have in previous weeks looked at the ‘export only’ function which allows the user to extract the raw data used for the EDI document; and we have also outlined the steps required for retrieving a log report, which details the process the application runs to retrieve and send documents, and highlights any possible errors in the process.

Both sets of documentation are essential for troubleshooting issues you may have with your outbound and inbound profiles; but the most vital documentation required for troubleshooting are the maps!

In EDI, document maps determine what specific business data is to be transmitted between trading partners, and the mapping logic defines exactly how, and under what circumstances, that data should be used. Essentially, the maps provide logic and instruction to the translator based on the agreed-to system and business requirements of each trading partner.

Mapping issues can occur for a variety of reasons: Sometimes your trading partner’s system requirements change; other times the data has undergone some subtle change; and in some cases, accepted EDI protocols have changed. Finally, mapping issues may occur where a business scenario arises which is not covered by the current mapping logic.

Whatever the case has happens to be, if a document fails to process or is rejected by your trading partner, Support Services will almost always request a copy of your current document map, corresponding with the document type you are sending or receiving (orders, invoices, ASNs, etc.).

Retrieving the map is a fairly straightforward process:

The maps reside in the mapper folder. This is typically located at: C:\Program Files\eBridgesoft\eBridge200x\Mapper, for eBridge 2004 and 2006; and C:\Program Files\eBridgesoft\Mapper for eBridge 4.1.

For standard EDI, the map names are based on trading partner, document type, and eBridge application version.

For example: Target, 810 (invoice), Version 4010, would be: TAR81041.map

For ePortal users, the trading partner is most often not specified, as the same document map is used for each trading partner. In this instance, for example, an inbound order map would be labeled ‘850’ and the trading partner with which you are having the issue is inconsequential.

For webstore integration, map names vary and determining the correct map may require some dialogue with Support Services.

That is why we are always here to help!

If you have any issues, mapping or otherwise, please do not hesitate to give me a call at the Help Desk at 905-631-8057 or 1-800-755-6921 ext. 224

Have a great week and I will check in soon!

Paul Tittel

Help Desk Administrator

eBridge Support Services

EDI Tips and Tricks, Support