Acq: We need to fully implement EDI availability codes
Bug #1627373 reported by
Chris Sharp
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Evergreen's acq implementation reads and stores lineitem availability codes from EDI order response (ORDRSP) messages, but doesn't really do anything with them. Since at least one vendor that PINES libraries order from uses these codes to automatically cancel or otherwise indicate a delay (such as a backorder), we should use them to do so. They are documented in EDItEUR's EDI documentation for the ORDSRP message:
http://
Changed in evergreen: | |
importance: | Undecided → Wishlist |
tags: | added: acq edi |
tags: | added: needsdiscussion |
Changed in evergreen: | |
status: | New → Confirmed |
tags: |
added: acq-edi removed: edi |
To post a comment you must log in.
Untested working branch available here: http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ csharp/ lp1627373_ edi_availabilit y_codes
I decided to limit this to codes that we need for libraries that use Brodart, who provided me a list of codes and how they treat them on their end. My implementation does not add any cancel_reasons, but uses either "Delayed: Backordered" or "Canceled: By Vendor", depending on how Brodart handles them. I'm very interested in further use cases for this, but since this is the first bug report I've seen on this issue, I'm guessing we're the first to run into the problem.