c2c-oerpscenario team mailing list archive

["Amit Parik \(OpenERP\)" <amp@xxxxxxxxxxx>]

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!

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/796335

Title:
  to backorder or not to backorder

Status in OpenERP Modules (addons):
  Incomplete

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

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