Backordered items have line item status of cancelled

Bug #1270289 reported by Pamela Smith on 2014-01-17
This bug affects 9 people
Affects Status Importance Assigned to Milestone

Bug Description

In 2.5, when a line item is backordered (via EDI) the item status becomes cancelled. Can this be changed to reflect it's true status?
We would like backordered status so that it is clear that the item is still on order.

Kathy Lussier (klussier) wrote :

Hi Pam,

I was almost tempted to mark this one as a duplicate of, but, even though that fix offers a big improvement by displaying the cancel reason on the PO, we still have the issue that these lineitems are displaying as canceled. Our users find it confusing too.

We had an idea for one approach that you can see at If this were done, it would continue to use the canceled status for backordered lineitems, but it would display as backordered on the PO. Do you think this would be a reasonable approach?

One of my assumptions was that we would probably have to stick with the canceled status because it might be part of the EDI protocol. But I could probably be totally wrong on that point.

Changed in evergreen:
status: New → Confirmed
Bradley Bonner (bbonner) wrote :

I did a quick and dirty hack to the perl file to get around this temporarily. (version 2.4.5)

Normally, the EDI response read would interpret a 400 response as back-ordererd and assign a cancel reason(and cancel the line item and its copies). I just tried changing it to 401 instead, causing a 400 to be ignored.

If there IS a legitimate 401 returned, that might cause trouble! And, I don't have a way in the client to see back ordered items, although our staff has other ways to determine that from the vendors.

snippet changed (400 changed to 401):

if ($stat = $li_hash->{order_status}) {
                    $logger->info("EDI: lineitem has order status $stat");

                    if ($stat eq '200') {
                        $reason_id = 1007; # not accepted

                    } elsif ($stat eq '401') {
                        $reason_id = 1283; # back-order

Bradley Bonner

Bill Erickson (berick) wrote :

Lineitem order status "401" corresponds to "On order from our supplier". I don't know if it's used in the wild by suppliers.

To use this patch, I would recommend removing the elsif block for back-order entirely to avoid unintentional 401 events.

However, as Bradley says, this is quick and dirty. It causes the system to treat back-ordered items as regular on-order items. The staff cannot see in the UI that an item is on back-order nor can Evergreen tell that an item is on back-order. As such, I would not recommend using this unless you really don't care if an item is on back-order.

Pamela Smith (pamela-smith) wrote :

 For us Bradley's fix is preferrable. It really doesn't work for us to have backordered items cancelled and not be able to receive them until they are invoiced.

Kathy Lussier (klussier) wrote :

Hi Pamela,

I just wanted to note that work is being done to address the issue of not being able to receive a cancelled lineitem - I hope to test Bill's most recent branch very soon so that this bug fix can be included in Evergreen.

In our case, I think we do need to see that the lineitem is backordered in the interface. I'm hoping we can continue to work on this issue so that we can further distinguish the cancelled lineitems from those that are really just delayed. One approach we considered at MassLNC was

We're reviewing quotes for our development projects this week, and I should have more information next week as to whether we will be able to fund that project.


Bill Erickson (berick) wrote :

Here's a dev proposal for improving the display for delayed items. It's based on the MassLNC proposal, with some slight tweaks and I18N additions. Comments welcome.

Bill Erickson (berick) wrote :
tags: added: pullrequest
Changed in evergreen:
milestone: none →
Bill Erickson (berick) on 2014-07-31
Changed in evergreen:
milestone: → 2.7.0-beta1
Ben Shum (bshum) wrote :

Thanks for testing Kathy! Bill's code has been pushed to master for this new feature and slated for 2.7.0-beta1. Thanks Bill!

Changed in evergreen:
status: Confirmed → Fix Committed
importance: Undecided → Wishlist
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers