Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2C050200D3C for ; Tue, 14 Nov 2017 11:02:19 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 2A4FD160BF4; Tue, 14 Nov 2017 10:02:19 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6EC9F1609EF for ; Tue, 14 Nov 2017 11:02:18 +0100 (CET) Received: (qmail 76413 invoked by uid 500); 14 Nov 2017 10:02:17 -0000 Mailing-List: contact user-help@ofbiz.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ofbiz.apache.org Delivered-To: mailing list user@ofbiz.apache.org Received: (qmail 76402 invoked by uid 99); 14 Nov 2017 10:02:16 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Nov 2017 10:02:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 2B9761807BC for ; Tue, 14 Nov 2017 10:02:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.59 X-Spam-Level: ** X-Spam-Status: No, score=2.59 tagged_above=-999 required=6.31 tests=[HTML_FONT_FACE_BAD=0.289, HTML_MESSAGE=2, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id kjXc7q5URkkl for ; Tue, 14 Nov 2017 10:02:14 +0000 (UTC) Received: from smtp26.services.sfr.fr (smtp26.services.sfr.fr [93.17.128.163]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id DE99061056 for ; Tue, 14 Nov 2017 10:02:13 +0000 (UTC) Received: from [192.168.1.2] (183.90.14.81.rev.sfr.net [81.14.90.183]) by msfrf2601.sfr.fr (SMTP Server) with ESMTP id 5D8541C001C40 for ; Tue, 14 Nov 2017 11:02:07 +0100 (CET) Received: from [192.168.1.2] (183.90.14.81.rev.sfr.net [81.14.90.183]) (Authenticated sender: jacques.leroux60@sfr.fr) by msfrf2601.sfr.fr (SMTP Server) with ESMTPA for ; Tue, 14 Nov 2017 11:02:06 +0100 (CET) Authentication-Results: sfr.fr; auth=pass (PLAIN) smtp.auth=jacques.leroux60@sfr.fr Subject: Re: RMA process To: user@ofbiz.apache.org References: From: Jacques Le Roux Organization: Les Arts Informatiques Message-ID: <54927d25-efcc-1319-b9a5-cd6a7c442af5@les7arts.com> Date: Tue, 14 Nov 2017 11:02:23 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: X-sfr-mailing: LEGIT Content-Type: multipart/alternative; boundary=------------6201EEB41E1862C02C88C54E Content-Language: en-GB archived-at: Tue, 14 Nov 2017 10:02:19 -0000 --------------6201EEB41E1862C02C88C54E Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit +1, makes sense, though for instance Amazon is creating invoice with 0 (zero) amount for such case. I was surprised by this, OFBiz can do better ;) I did not look into details, but *if the user has enough information about the replacement* I see no reasons to create a void invoice. So please check this condition. I guess Amazon uses a void invoice as a place holder, again not necessary, and IMO even confusing if you have links and info about the replacement Thanks Jacques Le 14/11/2017 à 10:49, Sanjay Yadav a écrit : > +1 to the solution proposed for the issue reported in case 2,  if replacement is done with the similar item and type is not serialized. > > Best Regards,* > * > * > * > *Sanjay Yadav* | Manager, Enterprise Quality Assurance > HotWax Commerce by**HotWax Systems > 80, Scheme No. 78, Part II, Indore, M.P. 452010, India > Mobile Phone: 787 918 8830 | Linkedin: Sanjay-Yadav > > HotWax Systems recently received 8 mentions in /*The Gartner Digital Commerce Vendor Guide, 2016 */by Gartner, Inc., the world's leading IT research > and advisory company.//Learn more about our researchhere . > Inline image 1 > > > > On Tue, Nov 14, 2017 at 2:32 PM, Amit Gadaley > wrote: > > Hello Everyone, > > In RMA process, there are two types of return items i.e. Refund and > Replacement. Actually, there are few more types but consider these two to > focus on the actual problem. > > CASE 1: Create return with return items of type 'Refund'. When return is > received, an invoice is created to refund to the customer. > *Issue: *No Issue > > CASE 2: Create return with return items of type 'Replacement'. When return > is received, a sales order with order total zero ($ 0) is created against > return. And, can be processed as usual. > *Issue: *An Invoice is created against the return. I think it should not be > created as an order is already created in replacement of received items. > > Please feel free to add your views and comments. > -- > Thanks and Regards, > *Amit Gadaley * | Senior Enterprise Software > Engineer > HotWax Commerce by HotWax Systems > > Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore, > M.P., India - 452010 > Cell phone: +91 958.459.3069 > > > > > --------------6201EEB41E1862C02C88C54E--