c2c-oerpscenario team mailing list archive

[Kevin McMenamin <877795@xxxxxxxxxxxxxxxxxx>]

Graeme

Understand what you are saying, but at the moment you can cancel a
picking then modify the SO and generate duplicate tasks/MO's which is
not desirable.

I think there should be a message that tells the user what downstream
records need to be cancelled before the SO can be modified. Would be
nice if that could be done at a line level, but at least the information
to allow the user to make an informed decision.

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

Title:
  Modifying a sales order

Status in OpenERP Addons (modules):
  Incomplete

Bug description:
  To modify a sales order requires the associated picking to be
  cancelled. But a sales order can also generate a PQ, MO or a task.
  There is no check on these and if the relevant line is deleted/amended
  from the SO the downstream document is not deleted/amended. Also, if
  the SO line is left, a new downstream document is created.

  A modification of a sales order should affect all downstream
  documents, and their state will determine if the SO can be modified
  (as it currently does for a picking list)

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