Community mailing list archives

community@mail.odoo.com

Re: Cancel done delivery order

by
Akretion, Raphael Valyi
- 03/25/2015 06:35:01
Perfect Joël,

On my side, I'll also rush to get sale_order_revision and purchase_order_revision in OCA v8 for next week. I also apologize for my very low personal activity around the OCA over the last 4 months as I had a hard personal situation to face. Luckily Akretion OCA activity has only been increasing meanwhile and I'm also slowly coming back to a normal activity and OCA will be able to count on my participation again. Thanks again to all the people involved in the project.

Regards.

On Wed, Mar 25, 2015 at 4:53 AM, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
Dear Raphaël,


This is the roadmap, I investigate all modules before writting the specs, and for version "3.0" of our sale and purchase amendment modules you can read here :https://github.com/gurneyalex/sale-workflow/blob/8.0-sale_amendment/sale_amendment/README.rst

That it is already plan :)

Regards,

Joël


On Tue, Mar 24, 2015 at 5:22 PM, Raphaël Valyi <rvalyi@akretion.com> wrote:
Hello,

I also take the opportunity to point to 2 related modules that makes it possible to archive several revisions of sale or purchase orders and have them properly linked together:
https://github.com/OCA/purchase-workflow/tree/7.0/purchase_order_revision
and the same for sale orders which is not yet merged int the OCA:
https://github.com/OCA/sale-workflow/compare/7.0...akretion:70-add-sale_order_revision


Now dealing with a related picking is out of the scope of these modules which only deal with when happen before confirmation. But may be it's a good basis to extend further as they are quite clean.

@Joël, may you should extend them in your modules, what do you think?

Regards and thank you for bringing this important topic on the table again.

On Tue, Mar 24, 2015 at 1:08 PM, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:
Dear community,


Here is the final decision taken on Camptocamp side about those amendment process:

https://github.com/gurneyalex/sale-workflow/blob/8.0-sale_amendment/sale_amendment/README.rst

We start the devs now and it'll of course be publish under the OCA umbrella. It'll be composed by sale_amendment and purchase_amendment modules.

Hope you'll enjoy it !

Regards,

Joël


 

On Fri, Mar 20, 2015 at 11:35 AM, Nuria Arranz Velazquez <nuria@opusvl.com> wrote:
Eloquently put, +1

On 19/03/15 16:27, Joël Grand-Guillaume wrote:
<blockquote cite="mid:CACk3wOLkZHteo=7ASrcCGjd4Tmg5Mf+kuMrei+J0aOs2OpUjMQ@mail.gmail.com" type="cite">
Hi,


What a debate :) My opinion here is:

 * We need to educate our users properly
 * We need to set proper business process around to ensure those use cases below do not happen, at least not too much
 * We need to solve (without headache) the situation in the ERP in some cases where it make sense

I try to make an approach of what are the use cases where you need such a feature (and those use cases have to be resolved for : MTO, Drop ship and MTS). My below cases are based on drop shipping because it is the "worst" as you need a strong agreement from supplier (but the same happen with MTO). I take the assumption you agree to be nice with your customer.

1) Customer want to decrease the quantity to be shipped of an ordered product
=> We have remaining quantity to be shipped and the customer want less product, but still want some (so you can't cancel).
 - Ask supplier if ok, he says yes !

=> You're stuck with the system and can't do something. Only way out: cancel the remaining deliveries, SO goes in exception, say "manually corrected", do the same for PO, make a new SO and PO. That's not really good but it works.

2) Customer want to increase the quantity to be shipped of an ordered product
=> We have remaining quantity to be shipped and the customer want more of the product.
 - Ask supplier if ok, he says yes !

=> You're stuck with the system and can't do something. Only way out: make a new SO and PO. That's not really good but it works.

3) Customer want to cancel the remaining quantity to be shipped of a product

=> We have remaining quantity to be shipped and the customer want to cancel it. Here, it can work the following way only is you cancel all remaining, because if you have other line to be shipped, we have the same trouble than in 4)

 - Ask supplier if ok, he says yes !
 - Cancel the remaining picking
 - SO goes in exception, say "manually corrected"
 - Same for PO

Trouble => You don't have the historical value somewhere. You may log a note in the chatter, but well, this is not really clean as your SO contain the ordered quantity only.

4) Customer want to cancel a whole line of a product not yet shipped
=> Imagine you already ship some line, but still 2 lines to be shipped.

 - Ask supplier if ok, he says yes !

=> You're stuck with the system and can't do something. You cannot split a delivery so you can cancel the proper line. Only work around: make note in the chatter. Once you will have the only remaining line in a delivery, you'll be able to cancel it like 3)

5) Customer want to cancel a SO no yet shipped
 - Check with supplier it is OK
 - Cancel the pickings of the SO
 - Cancel the PO
 - Cancel the SO

6) Customer want to add a new product in existing confirm SO
Create a new SO :)


Conclusion

 * 5) and 6) are ok
 * 1) and 2)) are ok, but really boring task
 * 3) is boring if no other product, but if other product are here, it's like 4)...
 * 4) is may work, but is really the worst...

My solution would be not to bypass any of the system process, but provide automation so the task is not taking too much time, but overall it'll avoid to make mistake !

Solution 1:

- Create a wizard for SO, a wizard for PO that help the user to make those operations in a semi-automatic way (e.g. for 1) it will automatically cancel the remaining and create a new so with the wanted value).

- The wizard will always keep a link between canceled or done document and the new created one for audit purpose (like backorder in pickings)

- The document will always store the ordered quantity AND the new agreed one, with a log of what has been done. The user will have to provide a reason for his changes and it'll be logged

Solution 2:

- Create a wizard for SO, a wizard for PO that help the user to make those operations in a semi-automatic way

- The wizard will work at line level and "play" with the status of the line
    e.g. I have a confirmed SO line with ordered qty = 1000 ; I already ship 200 ; The user only wants 300 of the remaining 800
           => the wizard will:
                - Keep the original line and change quantity for 200, mark it as shipped
                - Add a new line with quantity 300, confirm it and generate the delivery
                - Add a new line with quantity 500, set state to cancel

- The user will have to provide a reason for his changes and it'll be logged

=> Regarding the accounting flow, for both solution, the wizard will try to cancel the invoice if any. If it cannot (e.g. already paid), it'll generated a full refund and set the proper line to "to be invoice" (will here to take care of the invoicing policy of the document).


Any preferred solution, comment or idea for me :) ?


Regards,

Joël


On Thu, Mar 19, 2015 at 3:02 PM, Lionel Sausin <ls@numerigraphe.com> wrote:
Le 19/03/2015 12:47, Eva Pinter a écrit :
> The problem we have to solve there is that the confirmation does 
> creates immediately delivery order on confirmation. This is causing so 
> much trouble because it then requires cancellation of delivery and 
> order, in case the customer changes his mind.
Unless I misunderstand your comment, as I wrote this problem was solved 
sooner this week in v8.
Now conform order => creates delivery
Cancel order => cancels delivery.
I juste tried on runbot, it works.
Just be careful if you make to order, you don't want to make the same 
things twice. But again, MTO doesn't lend itself to changing orders anyway.

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe




--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager
Business Solutions

+41 21 619 10 28

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe



-- 
N. Arranz-Velazquez
OpusVL Odoo Specialist Team (OOST)

OpusVL
Drury House
Drury Lane
Rugby
CV21 3DE

T: 01788 298 450
W: www.opusvl.com

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe




--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager
Business Solutions

+41 21 619 10 28


_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe




--

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe




--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager
Business Solutions

+41 21 619 10 28


_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe




--
Raphaël Valyi
Founder and consultant
+55 21 3942-2434