Hi all,
I'm taking this opportunity to be loud on a couple of acquisitions
problems we've encountered.
We have two consortia that are going live on Evergreen in less than a
month. This morning, I sat down with the acq people at one consortium to
identify the issues that will be most problematic for them when they go
live. I'm hoping we can work to get these issues resolved so that the
transition to acquisitions in Evergreen can go as smoothly as possible.
* https://bugs.launchpad.net/evergreen/+bug/969494 describes a problem
where using the "Add to Purchase Order" option from the View/Place
Orders interface does not carry over the PO's provider to that lineitem.
Consequently, the PO cannot be activated. We have several libraries who
do not plan to use selection lists, and fixing this problem will make a
big difference in their workflow.
* I also added a new bug today for problems we encountered when trying
to activate a PO as part of the order record upload process.
https://bugs.launchpad.net/evergreen/+bug/992108. Since the workaround
for this isn't too onerous (uploading directly to the PO and then
activating), it probably isn't as high of a priority as my first item,
but it is still fairly important.
* We also are having ongoing problems with EDI order responses. From the
acquisitions discussion Saturday morning, it sounds like nobody is
working with order responses. We are committed to putting in some of the
legwork to try to figure out what the problems are and to get order
responses working properly so that acquisitions can become a more
attractive option for other Evergreen users.
However, we have encountered some problems that I suspect might not be
bugs, but may be related to configuration issues, and we just need to
know where to start looking to resolve these problems. I sent something
to the list regarding this issue earlier this month,
http://markmail.org/message/gjn4eiadi7s55jdt, but I'll try to provide
more detail below.
We have been working with a vendor that has been posting test order
responses. We have been able to successfully translate these order
responses two times, and both times occurred on the day after we
performed an Evergreen update on our test system.
Afterwards, we get an error in our EDI messages every day. It seems as
if the system keeps trying to translate that same message that had
already been successfully translated after our Evergreen update.
The status of these messages is trans_error.
The error message is:
EDI Translator edi2json failed, Error 2: Uncaught exception Input/output
error in method edi2json
The EDI Message Body is:
UNB+UNOA:3+1697978:31B+3075052:31B+120328:1751+00000000000011++EANCOM'UNG+ORDRSP+1697978:31B+3075052:31B+120328:1751+00000000000007+UN+D:96A'UNH+00000000000007+ORDRSP:D:96A:UN:EAN008'BGM+231+148+29'DTM+137:20120313:102'RFF+ON:148'NAD+BY+20N6885::91'NAD+SU+1697978::31B'LIN+166+5+9780060186944:EN'PIA+5+0060186941:IB'QTY+21:1'PRI+AAF:22:CA:SRP'RFF+LI:148/166'LIN+167+5+9780142437261:EN'PIA+5+0142437263:IB'QTY+21:1'PRI+AAF:7:CA:SRP'RFF+LI:148/167'LIN+168+5+9780152052201:EN'PIA+5+0152052208:IB'QTY+21:3'PRI+AAF:6.95:CA:SRP'RFF+LI:148/168'LIN+169+2+:EN'PIA+5+:IB'QTY+21:1'QTY+12:0'FTX+LIN++200:1B:28'PRI+AAF:5:CA:SRP'RFF+LI:148/169'LIN+170+5+9780345475800:EN'PIA+5+0345475801:IB'QTY+21:1'PRI+AAF:14.95:CA:SRP'RFF+LI:148/170'UNS+S'CNT+2:5'UNT+36+00000000000007'UNE+1+00000000000007'UNZ+1+00000000000011'
Any thoughts on where we can start troubleshooting this?
Thanks!
Kathy
--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 756-0172
(508) 755-3721 (fax)
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier
