Re: ERP Integration

[lbriggs@xxxxxxxxxxx]

We use Future Three EDI. . .as do many of the automotive suppliers.  Not sure
what your business is, but if you are an OEM supplier it may be worth looking at
.  A bit costly, but basically solid. There are already interfaces available
from F3 to JBA avaiable from both vendors.







Jim Sehi <jsehi@hach.com> on 04/05/2001 02:15:06 PM

Please respond to JBAUSERS-L@midrange.com
                                                                                
                                                                                
                                                                                


                                                              
                                                              
                                                              
 To:      "'JBAUSERS-L@midrange.com'"                         
          <JBAUSERS-L@midrange.com>                           
                                                              
 cc:      (bcc: Larry Briggs/UNIPRES)                         
                                                              
                                                              
                                                              
 Subject: ERP Integration                                     
                                                              








We are currently running JBA System/21 3.5.0, and are running into a wall
with some enterprise integration issues.  I would like to start a thread
discussing these issues, and what others have done to solve the problems
that seem to be inherent in the software.

The EDI module provided with 3.5.0 had limited functionality at best, and
has proven to be a bottleneck in our implementation.  The process is
completely batch driven, with no on line verification.  There also appear to
be issues with having multiple translation formats for the same transaction
(ie. an outbound 810, for example).

We have also built an integration with IBM's WebSphere Commerce Suite, based
on some preliminary API's that were provided by JBA.  These API's are now
part of a product called "eSupply".  From what I've experienced via the
webcast presented in March, eSupply doesn't really fit our needs either.

I'm assuming others have addressed similar issues.  What are some of the
types of things you have run into?  How did you fill the business need?
We've found a relatively poor supply of off-the-shelf application connectors
for JBA System/21, but I'm wondering if we are looking in the wrong places.

Thoughts anyone?

Jim Sehi

Title: ERP Integration

We are currently running JBA System/21 3.5.0, and are running into a wall with some enterprise integration issues.  I would like to start a thread discussing these issues, and what others have done to solve the problems that seem to be inherent in the software.

The EDI module provided with 3.5.0 had limited functionality at best, and has proven to be a bottleneck in our implementation.  The process is completely batch driven, with no on line verification.  There also appear to be issues with having multiple translation formats for the same transaction (ie. an outbound 810, for example).

We have also built an integration with IBM's WebSphere Commerce Suite, based on some preliminary API's that were provided by JBA.  These API's are now part of a product called "eSupply".  From what I've experienced via the webcast presented in March, eSupply doesn't really fit our needs either.

I'm assuming others have addressed similar issues.  What are some of the types of things you have run into?  How did you fill the business need?  We've found a relatively poor supply of off-the-shelf application connectors for JBA System/21, but I'm wondering if we are looking in the wrong places.

Thoughts anyone?

Jim Sehi