ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonard Lin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-7096) Inventory received are not getting reserved based on set Est. Delivery Date over Sales Order
Date Tue, 27 Dec 2016 07:31:58 GMT

    [ https://issues.apache.org/jira/browse/OFBIZ-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15779818#comment-15779818

Leonard Lin commented on OFBIZ-7096:

Wanted to add some use-cases comments.

I'm doing now my 2nd OFBiz implementation and in my first and 2nd implementation I had to
skip the built-in inventory reservation system because of this behaviour.
As the analysis above showed there is a hierarchy fields considered which orders get reservation
There is also the priority-field which should be able to influence reservation as well.
I spent a lot of time to get it working, but OFBiz OOTB seems to favor reservation priority
in "the order the sales-orders arrived".
even customizing "reserveProductInventory" wasn't enough to get it working reliably. 

For many cases a first-come, first-serve approach might be ok, but for more sophisticated
JIT platforms and everywhere you have purposefully a minimum amount of inventory at hand the
OOTB functionality does not work.

I think too, this is not a bug, but a feature.
Perhaps it can be a feature that inventory-reservation can be configurable.

> Inventory received are not getting reserved based on set Est. Delivery Date over Sales
> --------------------------------------------------------------------------------------------
>                 Key: OFBIZ-7096
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7096
>             Project: OFBiz
>          Issue Type: Bug
>            Reporter: Swapnil Shah
>            Assignee: Divesh Dutta
>            Priority: Critical
>         Attachments: SO1002.png, SO1003.png, SO1004.png
> Generally system would carry multiple sales order for a SKU with different Est.Delivery
Date(EDD) and inventory might not be available that time when orders were created/approved.
> Once we start receiving the inventory then reservations gets auto-triggered and allocated
based on created/approved date by overlooking the EDD altogether.
> A simple scenario could be that we have 3 different orders created in system at 3 different
time stamps as follows and all 3 are backordered:
> Order A>> Created on 05/21 10 AM >> EDD: 5/25
> Order B>> Created on 05/21 11 AM >> EDD: 5/27
> Order C>> Created on 05/21 12 AM >> EDD: 5/23
> As soon as inventory is received it first get allocated to Order A whereas Order C is
supposed to ship first even though it got approved later. 
> Expected Behavior: System should first honor the EDD and if its not set then use the
existing criteria of honoring Created/Approved time stamp for allocating the reservations
> Please refer to attached screenshots for reference

This message was sent by Atlassian JIRA

View raw message