From notifications-return-25564-archive-asf-public=cust-asf.ponee.io@ofbiz.apache.org Sat Apr 27 12:51:02 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id D6ACA180630 for ; Sat, 27 Apr 2019 14:51:01 +0200 (CEST) Received: (qmail 77931 invoked by uid 500); 27 Apr 2019 12:51:01 -0000 Mailing-List: contact notifications-help@ofbiz.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ofbiz.apache.org Delivered-To: mailing list notifications@ofbiz.apache.org Received: (qmail 77913 invoked by uid 99); 27 Apr 2019 12:51:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Apr 2019 12:51:01 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5FDC4E0371 for ; Sat, 27 Apr 2019 12:51:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1227825810 for ; Sat, 27 Apr 2019 12:51:00 +0000 (UTC) Date: Sat, 27 Apr 2019 12:51:00 +0000 (UTC) From: "Deepak Nigam (JIRA)" To: notifications@ofbiz.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OFBIZ-10518?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D168= 27589#comment-16827589 ]=20 Deepak Nigam commented on OFBIZ-10518: -------------------------------------- For enabling this feature productStore.allocateInventory should be equal to= Y. > Inventory (Supply) Allocation Planning > -------------------------------------- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product > Reporter: Deepak Nigam > Assignee: Suraj Khurana > Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, CreateAllocationPlan= -Step2.png, CreateAllocationPlanEditMode-Step2.png, EditAllocationPlan.png,= FindAllocationPlan.png, OFBiz-10518-UI.patch, OFBiz-10518-data.patch, OFBi= z-10518-entity-model.patch, OFBiz-10518-secas.patch, OFBiz-10518-services.p= atch, OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, OF= Biz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, V= iewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory ge= ts reserved for the order=C2=A0based on the reservation algorithm (FIFO, LI= FO etc). Many times,=C2=A0the fulfilment cycle of the order is too long or = due to some unexpected circumstances,=C2=A0the order holds the inventory fo= r a long time. In such scenarios, inventory availability becomes one of the= major bottlenecks in fulfilling the other sales order and businesses often= remains short supplied against the demand. > =C2=A0 > We can provide a feature (Create, Find and Edit supply allocation screen= ) to allocate the available and any future supply judiciously amongst exist= ing customers orders by considering different factors like estimated delive= ry dates, order priority, customer preference etc. > =C2=A0 > Following are the details design notes for the same: > =C2=A0 > An order in the approved status will be considered as =E2=80=98Eligible f= or Allocation=E2=80=99. The proposed supply allocation planning will have t= he following set of features: > =C2=A0 > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the d= esired product.=20 > =C2=A0 > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligibl= e for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sal= e Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given = order in the priority ranking. Higher is the order in display result list, = higher will be the priority it would get during reservations. > 4) The user can set the =E2=80=98Allocated Quantity=E2=80=99 against orde= red quantity at order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign th= e priority and set the allocated quantity for each of the submitted orders = to be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation = plan during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock s= hould be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan= , then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revisio= n unless the Shipment Plan is created against them. > =C2=A0 > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan = Id, Order Id, Product Id, Plan Method, Status etc. > =C2=A0 > =C2=A0 > =C2=A0 > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)