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



We still use one of those "expensive" translators... but we have thousands of documents/trading partners. Most are AS2.

I can't imagine trying to recreate the EDI data for each document.

How are you going to handle the EDI envelopes? Especially if you need to retransmit.

In any case, Mendelson has an open source AS2 solution. We use that when we can. It's a way better option that trying to use SFTP or something like that.

(soapbox warning)
Big retailers are trying to move away from EDI (driving me nuts)... first they outsourced their EDI, then fired their staff, and now the service companies are asking for more money. So they want to do APIs instead - which is great for them, because they dictate how each-and-every every document is structured. Meanwhile, as a manufacturer, we have to create a separate API interface for each-and-every retailer (approaching a thousand for us).

What a nightmare.

With the EDI translator, we can setup a new partner and all the documents in a few hours.

(off my soapbox)

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of K Crawford
Sent: Thursday, October 17, 2024 11:40 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: EDI 834 question

Thanks for the replies.
Art that 'line of code' is sort of what I was thinking. I will probably do that.
Charles, as for the communications I think we are okay. they said in one of the documents "Select your data transmission method: SFTP w/ PGP or HTTPS File Upload".
I think the biggest challenge is getting the correct data on the correct line, ISA vs INF vs REF etc.
I do have a contact that I will request the EDI document and a sample TXT.

On Thu, Oct 17, 2024 at 8:24 AM Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

Rolling your own translation for a single doc to a single vendor is
doable...

But make sure you understand how it's to be transmitted. Back when I
was doing EDI, we were sending via a Value Added Network (VAN);
originally dial-up and then via the Internet.

I know there's been a few new internet specific communication
protocols defined, such as AS2.
It's possible your vendor uses SFTP or HTTPS directly, but if they
want it via AS2 or via VAN. You might need tooling.

Lastly, when you start getting into multiple documents, with multiple
versions, to multiple partners. Tooling helps.

Charles

On Wed, Oct 16, 2024 at 2:19 PM K Crawford <kscx3ksc@xxxxxxxxx> wrote:

I have been asked to create an EDI 834 file. I just started my
research (google and vendor) and see that it could get complicated
if I let it. I am going to try not to let it get complicated. I do
recall many many
years
ago co-workers using some tools to create them. At my current job
we do not have any tools, I don't expect any $ to get any tools.

Any recommendations on free tools (I don't expect this) or good
documentation on how to?
TIA

--
Kerwin Crawford
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.



--
Kerwin Crawford
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Greg Wilburn
Director of IT
301.895.3792 ext. 1231

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.