[jira] [Commented] (OFBIZ-7096) Inventory received are not getting reserved based on set Est. Delivery Date over Sales Order

["Jagpreet Kaur (JIRA)" <ji...@apache.org>]

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

Jagpreet Kaur commented on OFBIZ-7096:
--------------------------------------

After reading the description and replicating the issue i researched around flow of inventory reservation and drawn some of the conclusions

1) When we create the order, reservation of inventory is done in 'reserveProductInventory' service where the entry in entity 'OrderItemShipGrpInvRes' is done, the promisedDatetime is set from 'ProductFacility' daysToShip record and if not found adding 30 days to orderDate.

2) But in my opinion the correct condition would be if we do entry in  'OrderItemShipGrpInvRes' entity promisedDatetime field as estimatedDeliveryDate
and if not present the above condition should be true, as the inventory reservation is done on the basis of promisedDatetime, priority, sequenceId.

> 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
(v6.3.4#6332)