07-21-04 12:51 PM
Beware,
The Base edi adapter is actually developed by covast for microsoft. And as
we did, you'll probably get stuck with the many limitations to the base edi
adapter. Then you'll have the option to buy covast Full adapter at an
outragous expense.
You'll have to do a very good/deep proof of concept for your needs,
You must not assume anything. You'll need technical proof of everything you
can imagine before going with the base adapter.
please note that I really think the covast adapter is great, but at 80 % of
your biztalk license.. you might consider building your own. And let me warn
you against the common sales talk for the biztalk edi adapter. Those
salesmen I have encountered have all said it could handle edi. That isn't
untrue it's is just extremely limited. Ie. supported edi envelopes are A and
B. that will constrain you to sending ascii characters only.
One would consider why only A and B was implemented ;-)
Best regards
Michael Høtoft
"Alex R." <Alex@nospam.com> wrote in message
news:uexBYhnbEHA.556@tk2msftngp13.phx.gbl...
> Hello,
>
> We are software development company trying to replace our current EDI
> engine with something that allow end user to make changes to the mappings
> and create their own.
>
> BizTalk - one of alternatives for this. Also - we are using MSSQL 2000
> as databse. Can somebody provide us opinions regarding:
> 1) Does BizTalk can handle EDI documents out of a box? We are looking
> primarily on Warehousing and Transportation transaction sets;
> 2) How hard for end user to manipulate mappings?
> 3) Anything alse we should know?
>
> Please use email: AlexR@**nospam**argosoftware.com (please remove test
with
> *).
>
> Thanks,
> Alex
>
>
[ Post a follow-up to this message ]
|