Mailing-List: contact dev-help@ofbiz.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ofbiz.apache.org
Message-ID: <22988981.1183465565556.JavaMail.jira@brutus>
Date: Tue, 3 Jul 2007 05:26:05 -0700 (PDT)
From: "Ray Barlow (JIRA)" <jira@apache.org>
To: dev@ofbiz.apache.org
Subject: [jira] Updated: (OFBIZ-830) Inventory balance for orders with
 picklists
In-Reply-To: <7576218.1174389992451.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/OFBIZ-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ray Barlow updated OFBIZ-830:
-----------------------------

    Priority: Minor  (was: Major)

Committed the patch rev: 552806

Will leave open as the second scenario still needs work.

> Inventory balance for orders with picklists
> -------------------------------------------
>
>                 Key: OFBIZ-830
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-830
>             Project: OFBiz
>          Issue Type: Bug
>          Components: product
>    Affects Versions: SVN trunk
>         Environment: N/A
>            Reporter: Ray Barlow
>            Priority: Minor
>         Attachments: balance_inventory.patch
>
>
> I'll break this in to two sections:
> 1) The balanceInventoryItems service checks to see if any pick lists are associated with the order id etc to exclude them from balancing to stop them appearing on duplicate pick list. The side effect of the current SQL condition is that part shipped orders don't get re-balanced as inventory changes happen.
> The scenario is an order for quantity 2 comes in you have 1 QOH so the order sets up 1 available and 1 on backorder. The customer is keen for the product so asks you to ship the first one which you do by splitting the shipment, creating a pick list, packing it and completing the pick list.
> You then receive more stock but the existing order will not clear the backorder flag because the SQL condition only checks for not-equals to PICKLIST_CANCELLED, there is a chance this will work IF the inventory reservation picks two different inventoryIds. The attached patch adds not-equals to PICKLIST_PICKED, as this is effectively a closed status for the pick list. I'll commit this if nobody has any objections.
> 2) The second scenario really relates to the same principle but occurs in a slightly different time line:
> You receive the order for a quantity of 2 and again only 1 QOH so the customer asks you to split ship. The order goes to picking and a pick list is generated and the picking packing process starts in the warehouse. But, if before it completes you receive additional stock either through expected goods receipting or even just adjustments after a shelf recount the second item will not come off backorder because their is an active pick list.
> The order item will remain on backorder now, even after the pick list is closed, until additional manual intervention occurs, such as using webtools to run the balance routine (not something you want average users doing!) or additional stock changes are made to trigger a balance.
> I don't have a solution for this scenario at the moment but wanted to suggest possibly triggering a balance event against orders when pick lists are canceled and also when they are completed in the case were the order is being part shipped. Or do we need to find an alternative way to stop pick lists allocating items that are on backorder?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.