|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
Urgent GXS bisync unrecognized comm session failure issue
Just an FYI for those out there that are using Inovis TL EDI400 (maybe other
software affected too) with the new 866 phone # provided by GXS (formerly GEIS)
recently to continue bisync connections we have discovered a big problem.
Something has changed on the new # connecting to the network for failure
responses. Our Software is not recognizing the failure. There are 2 things
that we have witnessed 1 the session hangs for hours until visually recognized
and a hard cancel on the job is initiated by a user or 2 the comm session
completes normally but the edi docs were never sent to the VAN. The first one
is easy to respond to and recognize, but the second one is completely hidden to
us. In our software there is no recognized indication of failure. The comm
session has a completed normal status. The way I found it was a vendor
indicated a missing block of control #'s and I went out and pulled a billable
sender status report and sure enough the block of control #'s were missing. In
my software it all looked like it sent fine. So if you recently switched to the
new # that is supposed to be available for bisync till June I believe be aware
there are issues and you may want to require going back to your old phone #.
Check it out quick because the VAN only holds docs for 3 days including weekend
so we have already lost the tracking for Friday's business. We switched back on
2/21/03 so I have to come up with another way to identify the missing control
#'s from 2/21 to 2/28.
Good luck!
Dawn
Dawn Field
Sr. IT Developer
Medtronic Information Technology
|
|
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
