|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: translators

Mats,
I do agree, you are biased. I will stay vague, in order to protect the
foolish and innocent, but I have been involved in a very large SAP
integration project with Peregrine and it has been anything but smooth.
For example, there have been at least two rollbacks of two pieces of
this implementation (done by Peregrine staff as outsourced on Peregrine
machines, using Peregrine owned and managed systems) because "we didn't
think it would work that way".
I'm not saying everyone on this list hasn't been through this with every
project/software/system for many reasons, I'm just saying, don't spread
this BS, it just reflects poorly on you in a listserv of professionals
who've been there and done that.
Just my 2 cents.
Leah
-----Original Message-----
From: Mats Jansson [mailto:
Sent: Friday, October 19, 2001 5:06 PM
To: 'Pablo Escobar';
Subject: RE: [EDI-L] translators
Pablo:
Points well taken and I couldn't agree with you more that there is a lot
of
hype in the integration market - a couple of important things to look
for in
the "adapter" case, in order to separate the "hypsters" from the "real
thing" are:
1) Does the adapter use meta data (idoc, bapi, etc etc) from the actual
application installed, or does it have it's own default best guess as to
what the end system interface looks like, to be customized? Using
actual
installation meta data is obviously best, because then customizations
(which
is almost always the case) are automatically reflected and accounted for
in
the adapter implementation.
2) Was this a field developed adapter, or is it a real, robust,
productized,
QA'ed adapter? Field developed adapters are seldom extensible, or
intended
for broad use, and often do not support multiple versions of
end-systems,
etc.
3) How intuitive and easy-to-use are these adapters. Am I still writing
code? Scripting? ;or is there a Wizards-based graphical process that
walks
the user through the configuration of the adapter?
4) What type of organization stands behind the adapter? Is it a small
company, at risk of going out of business or get acquired; or is it a
well
recognized, global company with the ability to support adapters now and
in
the future.
I am obviously biased, but on further scrutiny, Peregrine's adapters
would
fair quite well in all these categories.
Mats Jansson
Sr. Technical Consultant - Business Development
Peregrine Systems ***frictionless business***
1 Davis Drive, Belmont, CA 94002
Voice: Int+1-650-486-4547
Fax: Int+1-520-832-5113
http://www.peregrine.com
-----Original Message-----
From: Pablo Escobar [mailto:
Sent: Friday, October 19, 2001 12:55 PM
To:
Subject: RE: [EDI-L] translators
I'd like to give Peregrine's product the benefit of
the doubt (haven't used it), but I've lost count on
the number of EDI products that have promised a no
customization, no programming solution to integrating
EDI with JDE, SAP, Oracle, Baan, etc.
None of them meet the marketing hype, because every
business handles their processes differently and has
to deal with the oddball partner relationships that
aways pop up. I've yet to meet an EDI plug-in,
adapter, connector, facillitator, or extension that I
didn't have to customeize for a client. If one of
these magic bullets truly existed most of us on this
list would be out of work.
-Peter
per the original question, I've used GentranNT on a
couple OneWorld EDI systems. Worked out fine...with
some custom mapping.
--- Mats Jansson < wrote:
> Drew:
>
> Later this quarter, Peregrine's Power.Enterprise
> (NT/Unix) translation
> product will allow direct plug-in of all the same
> adapters that power
> Peregrine's process oriented Alliance Manager
> (B2B/EAI) product suite. In
> the set of 25+ adapters is a JDE adapter. Think
> EDI-to-JDE without a single
> line of code to write! More info at:
>
> Power.Enterprise:
>
>
http://sdweb02.peregrine.com/prgn_corp_ap/Products/pstProductFullBodybp.
cfm?
>
objectID=65B9A8C7-7F83-11D4-9C160090277322BD&ProductFamilyid=D54F33CD-AA
B4-1
> 1D4-9C240090277322BD
>
> Application adapters:
>
>
http://sdweb02.peregrine.com/prgn_corp_ap/Products/pstProductApplication
Full
>
Body.cfm?appObjectid=8255559D-9650-11D5-967100508BD33BE3&objectID=825555
A9-9
>
650-11D5-967100508BD33BE3&Productname=AllianceManager&ProductFamilyid=D5
4F33
> CD-AAB4-11D4-9C240090277322BD
>
>
> Mats Jansson
> Sr. Technical Consultant - Business Development
> Peregrine Systems ***frictionless business***
> 1 Davis Drive, Belmont, CA 94002
> Voice: Int+1-650-486-4547
> Fax: Int+1-520-832-5113
> http://www.peregrine.com
>
>
> -----Original Message-----
> From: Drew [mailto:
> Sent: Wednesday, October 17, 2001 1:21 PM
> To:
> Subject: [EDI-L] translators
>
>
> Hi folks,
>
> I'm at the beginning of converting a legacy EDI over
> to a JDE/(insert
> NT package here).
>
> The 3 on NT I am considering:
>
> Gentran
> Peregrine
> Mercator
>
> I am looking for a perfect fit with Gentran in the
> lead. We do a lot
> of 811, 272, and proprietary documents. Gentran's
> ability to do
> application to application mapping would come in
> handy here.
>
> Anyone have any other ideas?
>
>
>
> To unsubscribe from this group, send an email to:
>
> Message Identifiers: <SALES>, <JOBS>, <LIST>,
> <TECH>, <MISC>, <EVENT>,
> <PRODUCT>
>
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
To unsubscribe from this group, send an email to:
Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
To unsubscribe from this group, send an email to:
Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|