Adaptor for EDI

[Former Member]

Hi,

I have a scenario to send an invoice from R3 to a third party system using EDI.

Do I have to use the SEABURGER adaptor for EDI or is there another way to do it?

Thanks,

M

[MichalKrawczyk]

Hi Mushon,

>>>o I have to use the SEABURGER adaptor for EDI or is there another way to do it?

no

you have to find out in which format you have to send this EDI message

for example in my country you can send EDI messages

through a web service to the EDI provider

so we can use SOAP or http adapters to do that

Regards,

michal

[Former Member]

Thanks michal!

So please explain me in which case do I need to use EDI Adaptor (Seaburger)? and pay extra money for the adaptor if i can use standard adaptors such as SOAP , HTTP ?!

Thanks,

M

[MichalKrawczyk]

hi,

you have to use seeburger if:

1. you don't know how to develope your onw adapter

2. your "EDI provider" telles you to use EDI standard that the EDI adapter supports

but as I've told you:

find out if your EDI provider can use SOAP messages

then you won't have to use any non standard adapter

Regards,

michal

[Former Member]

How can i do an EDI scenario in my enviroment to test it?

[Former Member]

How can i do an EDI scenario in my enviroment to test it?

[MichalKrawczyk]

hi,

this is a standard interface

you just have to know inobund message, outbound message

and the adapter that's all

Regards,

michal

[Former Member]

> but as I've told you:

> find out if your EDI provider can use SOAP messages

> then you won't have to use any non standard adapter

>

>

> Regards,

> michal

I don't totally agree with this statement, let me tell you why.

When you buy an industry specific adapter from Seeburger, you get more than support for EDI protocols.

Seeburger provides you with industry specific business content, i.e. ready to use integration scenarios. These business scenario's contains standard mappings (including all repository objects you need in XI to build your interface) from IDOC to EDI documents and vice versa. Some of the adapters also contain communication adapters for EDI Specific networks like VAN networks etc.. So in other words, if you have the time, money and want to take the risks of implementing your EDI interface from scratch then go ahead with the earlier suggested custom solution.

As far as I know EDI is a very old protocol (in comparisson with SOAP) and it does not support SOAP for B2B communication. If you really want to use SOAP for B2B communication then you better take a look of ebXML.

Cheers,

Rob