to backorder or not to backorder

[Patrick Amstutz]

Hey,

This bug is a logic issue.

1)

- Create a new sale order for 100 CPU1 from Stock with 40 CPU1 in stock.
- Confirm, go to Delivery order, change the quantity to 40 CPU1.
- Click check Availability, the first line is Assigned.
- Process. The first line is Done. Does not create any backorder.

vs.

- Create a new sale order for 100 CPU1 from Stock with 100 CPU1 in stock.
- Confirm, go to Delivery orde.
- Click check Availability, the line is Assigned.
- Process only 40 CPU1. A back order is created for the remaining 60 CPU1.

Please could you tell me what is the rationale of creating a Back order in one case and not in the other one? Why back order are only considered when the stock.move is assigned?

The consistency for this functionality should be improved.

Ubuntu 10.04, Openerp 6.0.2.

[Amit Parik (amit-parik)]

Hello Patrick,

I have checked your both issues But all are working fine.

And I have seen that the back order in both cases and both are working as a same way.

I have attached a video for your reference so would you please check it and notify us where you faced the problem.

Thanks and waiting for your reply!

[Launchpad Janitor (janitor)]

[Expired for OpenERP Addons because there has been no activity for 60 days.]

[Numérigraphe (numerigraphe)]

I'm hijacking this bug, because change the quantity directly in the stock move does lead to the problem that was described, and it's not all that logical for a usability point of view.
Lionel.