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

Jacopo Cappellato commented on OFBIZ-7096:
------------------------------------------

I think this ticket/proposal and all the follow up comments are valuable and so 
I am trying to summarize an actionable plan for the resolution of this ticket:
 # change the type and priority of the ticket from Bug/Critical to 
Improvement/Minor (based on the 4th of July by Divesh Dutta and comments by 
Taher and Jacques); I will take care of this now
 # enhance the reservation algorithm to "honor Desired Delivery Date in case 
Ship After Date is found missing or not set by user" (quoting the proposal at 
the end of Swapnil Shah); this should provide enough flexibility to manage use 
cases like the ones mentioned by Leonard Lin)

 

> Inventory received are not getting reserved based on set Est. Delivery Date 
> over Sales Order
> --------------------------------------------------------------------------------------------
>
>                 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
(v7.6.3#76005)

Reply via email to