× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: ERP Integration
  • From: Jim Sehi <jsehi@xxxxxxxx>
  • Date: Fri, 6 Apr 2001 15:31:42 -0600

Title: ERP Integration
We are trying to use multiple EDI translation formats for the same transaction... different trading partners... due to different standards levels.
 
It sounds like your implementation doesn't have that requirement.
-----Original Message-----
From: CHI LEUNG [mailto:CLEUNG@CELSINC.COM]
Sent: Friday, April 06, 2001 11:07 AM
To: JBAUSERS-L@midrange.com
Subject: RE: ERP Integration

I do not experience the problem with multiple translation formats for the same transaction.  Our shop has one format for every function. (810, 850, 856).  Take 810 for example.  Batch Menu OE3445 (14/STOEB) will do a print from sales Order.  AI080CLP (1/STAIS) will send invoice to AI080PT.  File in Harbinger (we are using) such as AIP** will get updated. Yes, these are all Batch driven. But this layout does not call for different translation format for the same function, and there is no need for that as far as my shortsight can see.
 
Good Luck.
 
CL 
-----Original Message-----
From: owner-jbausers-l@midrange.com [mailto:owner-jbausers-l@midrange.com]On Behalf Of Jim Sehi
Sent: Thursday, April 05, 2001 12:15 PM
To: 'JBAUSERS-L@midrange.com'
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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.