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



Thanks Bob and John

Working with our trading partner is where I'm at, and you have identified the "missing link" in our current data flow
which provides Y/N for 997 acknowledgement, but no information for any possible 824.

997 Date and Time acknowledged has been promised, but has yet to arrive, and is currently available only as a text
file attachment to an e-mail.

In our case, we use a shared resource that provides EDI translation and other services for companies such as ours,
so I typically have little EDI knowledge other than the business data and requirements to interface with our core
systems and the shared resource, so it took some time for me to understand the "gap" between knowing we
"successfully transmitted" ASN data x hours before delivery time, and then hearing that afternoon that x number
of drivers had to down-stack each pallet because the "store did not get the ASN".

To close the "gap" I requested, some months past, that we receive 997 data as a data file with 997 date and time
acknowledged and any corresponding 824 data that may be available as of some agreed cut-off time.

My goal is to provide ASN document receipt detail to our driver at departure from our warehouse, but my data request
does not have much priority with our "shared resource" (understandable due to another VERY BIG project) so, for our
driver, store delivery is kind of like Mr. Gump's box of chocolates . . .

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John King
Sent: Monday, June 15, 2015 9:00 AM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: RE: EDI 856 ASN Confirmation

Hello Gary,

Since X12 lacks a dedicated 'ASN acknowledgement' document you'll have to work with your trading partner to develop a customized response. You might think about the 824 document - it contains the basic elements to identify the original ASN and has TED segments which could identify the specific lines that were accepted or rejected.

JK

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob Cagle
Sent: Friday, June 12, 2015 12:45 PM
To: Midrange Systems Technical Discussion
Subject: RE: EDI 856 ASN Confirmation

The 997 is just an acknowledgement that the trading partner received a document successfully, not that it was free from errors. Most trading partners will have a validation process outside of 'standard EDI'. How they process that and notify you of any errors depends on the partner, unfortunately.

Thanks

Bob Cagle
IT Manager
Lynk, Inc.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Wednesday, June 10, 2015 1:31 PM
To: Midrange Systems Technical Discussion
Subject: RE: EDI 856 ASN Confirmation

Thanks Steve!
We have a 1996 copy of X12 standards which shows: "997 Functional Acknowledgement - Draft Standard for Trial Use"
Also, our particularly large partner's documentation specifically mentions they send "transaction set 997 . . . within 24 hours"
( 24 hours ?!? )
I'll get with my contact at the National Facility and see what they have to say.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve Richter
Sent: Wednesday, June 10, 2015 11:58 AM
To: Midrange Systems Technical Discussion
Subject: Re: EDI 856 ASN Confirmation

the other side sends a 997 to acknowledge what you sent them. When you send an 856 you will get a 997 back with the AK1 segment containing an "SH"


On Wed, Jun 10, 2015 at 1:48 PM, Gary Thompson <gthompson@xxxxxxxxxxx>
wrote:

I'm working on an EDI Advance Shipment Notice that has been in place
for a few years.

I can barely spell EDI and we don't do EDI translation locally; all
EDI translation is handled by a national facility so that we send and
receive "transaction flat files" containing the data required for our
EDI Orders, Invoices, Ship Notices, etc.

One gap we have is getting a definitive "acknowledgement" that an ASN
document has been received and successfully translated by our trading
parter.

The trading partner we are more concerned with is a particularly large
one, and the best we currently have is an acknowledgement they
"received" an ASN document for a particular store for a particular
delivery date.

There are a couple of known "error conditions" which may be returned
to us, but no confirmation of the ASN being successfully translated,
never mind any indication when and if the document was available to
the store.

My question:
Is there a way, in the "EDI Standard" to get "positive confirmation"
of an EDI 856 ASN ?


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


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.