× 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.



Hi Kathy ...

My company specializes in EDI integration with business systems. We have
been doing this work since 1986, and have served dozens of companies.

Here are a few of the guiding principles of our practice.

1) Most of the interface should be built in the space between the
translator and the ERP

2) Use interface facilities provided by the ERP, but try not to modify the
ERP code. Compensate for the shortcomings of the ERP interface facility
with processes located outside the ERP boundary.

3) Take the time to design an architecture ... Do not just start writing
code

4) Make little or no use of translator features for data conversion,
business logic and the like. Implementers often reason that internal
translator tables and scripts circumvent the need for programming, but use
of these features does in fact constitute programming, albeit using an
inferior tool.

5) The easy way to perform a given task is almost always the wrong way.
Taking shortcuts early in the development cycle can lead to layer upon
layer of poor choices.

Based on your message, I would say you are in a place where the next few
decisions you make will be critical to the long-term success of your
project.

Please let me know if we can help you.

Regards,


John G Dyer
Vice President
Information Management Consultants, Inc
http://www.imcedi.com
jdyer@xxxxxxxxxx
812.455.7372




-----Original Message-----
From: bpcs-l-bounces+davejfuller=btinternet.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+davejfuller=btinternet.com@xxxxxxxxxxxx] On Behalf
Of
Kathy Steigerwalt
Sent: 17 December 2009 03:29
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] BPCS EDI advice

Hi All!

I am looking for advice.

The shop has been using Trusted Link Enterprise EDI integration with
BPCS
(ECM module) for the outbound documents for years and it is stable.
They have also been receiving EDI transmissions from customers BUT
dumping the inbound EDI to paper for human re-keying.

My questions: Basically do we implement our own programming
integration
into BPCS **OR** upgrade Trusted Link?
**OR** continue with current TLE/ECM versions and automate the inbound
documents?

Regarding Trusted Link Enterprise and BPCS ECM see below versions, what
are the abilities or lack of abilities when it comes to inbound
integration? Pros and cons?
We are using TLE Version 3.2 Rel: 01
BPCS Version 6.0 Release
04

Thank you for all opinions.

Respectfully,
Kathy~
--





______________________________________________________________

Confidentiality Notice: This E-mail (including attachments) is confidential and the property
of Information Management Consultants, Inc. (IMC).

If you are not the intended recipient:
Reading, copying, disclosure or any action based on this message is prohibited. IMC retains
copyright and intellectual property rights and objects to misuse.

IF YOU HAVE RECEIVED THIS E-MAIL IN ERROR, PLEASE CONTACT THE SENDER
TO ADVISE OF THE ERROR AND PERMANENTLY DELETE THIS E-MAIL.

______________________________________________________________

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.