Community mailing list archives
Re: RMA 8.0by
Camptocamp SA, Yannick Vaucher - Camptocamp
crm_claim_rma module is now there on Github: https://github.com/oca/rmaIt hasn't been ported yet. And as I see can see in forks graph someone started to work on it:
No idea what is the current status you might ask Vauxoo
Business Solutions Software Developer
PSE A, CH-1015 Lausanne
Phone: +41 21 619 10 30
Office: +41 21 619 10 10
On Wed, Dec 10, 2014 at 5:32 PM, OpenERP Master <email@example.com> wrote:
Hi,Has anyone looked at porting the crm_claim_rma module to v8? Is this mailing list the best place to discuss? Since everything moved to github i'm a little lost on the best place to discuss such things.Reviewing the changes in v8, it seems like a lot of work to port this module. From a high level review, it actually is quite complex, (rma in general). It's basically a glorified sales order, meaning you can create delivery order and invoice, return/exchange/refund, etc.I was thinking about starting over for my client, although I know a lot of people don't like duplicate work. I'm trying to find the easiest plan. My customer doesn't need anything like warranty, and the module seems tailored to such concept.
Additionally, I have trouble with the design. IMO an RMA should be managed from a sales order in the context of an Ecommerce order. CS agents using the feature, will manage almost all detail from a sales order level. I was thinking of doing a one2many from a sales order, then only call built in functionality for things like returns and refunds. Such things like return and refund are already built in functionality.Exchanging is a different story and may have to come up with something special here. I want to reduce the complexity of the module.