credativ team mailing list archive

[Numérigraphe <796335@xxxxxxxxxxxxxxxxxx>]

** Tags added: backorder

** Changed in: openobject-addons
       Status: Expired => New

** Description changed:

  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.
+ - 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.

-- 
You received this bug notification because you are a member of OpenERP
Framework Experts, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/796335

Title:
  to backorder or not to backorder

Status in OpenERP Addons (modules):
  New

Bug 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, 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/796335/+subscriptions