| 2012-01-20 14:44:37 |
Numérigraphe |
description |
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, put in a new pack leaving 40 CPU1 in the first one.
- 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. |
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. |
|
