Evergreen only recognizes a few EDI order statuses

Bug #1770202 reported by Jane Sandberg
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
New
Undecided
Unassigned

Bug Description

From my understanding of the EDI code, the only codes that are accepted by Evergreen are 200 (order not accepted) and 400 (backordered - awaiting supply). However, our vendor (Proquest Coutts) is sending a much wider variety of codes to us. A quick look at our recent ORDRSP messages shows the following:
* 221 (Outstanding order line cancelled: past order expiry date)
* 222 (Outstanding order line cancelled by customer request)
* 401 (On order from our supplier)

And none of those statuses are updating line items in Evergreen.

Note that the 401 status was previously discussed in this bug (in which the fact that the 401 status doesn't do anything was actually considered a feature to some extent): https://bugs.launchpad.net/evergreen/+bug/1270289

Tags: acq acq-edi
Revision history for this message
Tiffany Little (tslittle) wrote :

Adding a link to a related/potential dupe bug that includes helpful info:

https://bugs.launchpad.net/evergreen/+bug/1627373

I'm also in agreement that it would be useful/desirable to fully map these to cancel reasons.

Revision history for this message
Jane Sandberg (sandbergja) wrote :

For reference, these status codes show up in the 12B segment.

Revision history for this message
Jane Sandberg (sandbergja) wrote :

We just got our first 407 status (Our supplier sent damaged item(s), re-ordered), which Evergreen also had no idea what to do with.

Revision history for this message
Tiffany Little (tslittle) wrote :

It *looks* like mapping the EDI codes to cancel reasons is done in EDI.pm around line 782. That was the first place I looked, so it may be somewhere else too/instead.

My first thought was just to add in more codes to that portion of the Perl module, then realized that could easily get out of control. So I'm inclined to lean toward Chris's suggestion in comment #3 of bug #1627373 of storing the EDI availability codes in DB tables. I'd also say they should go ahead and be mapped to the cancel reasons in those tables as well. Then EDI.pm can just talk to that table.

And looking at the stock cancel reasons, in conjunction with this, we should probably expand the available stock cancel reasons. We have some in PINES that I thought were stock but appears they aren't, like Canceled: EBL which would map nicely to the 221 availability code.

Revision history for this message
Jane Sandberg (sandbergja) wrote :

+1 to Tiffany's suggestion and Chris' work adding all those codes to a branch. Also, +1 to expanding the default cancel reasons.

tags: added: edi
Revision history for this message
Jane Sandberg (sandbergja) wrote :

Just ran across our first order status 412 - Order line held awaiting customer instruction.

Evergreen did not do anything with this information.

tags: added: acq-edi
removed: edi
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.