c2c-oerpscenario team mailing list archive

[Valdemar Cantu <760836@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In OpenERP V6, Windows 7.

I have a default database with chained locations Output->Customers

I created a Sales Order with 2 detail lines. Line 1 has quantity 6, line
2 has quantity 4. Both lines are set to be sourced from the available
stock.

When I confirm the Sales Order I have to make a two step delivery in the warehouse management:
a) In Menu Warehouse ->Warehouse Management->Delivery Orders, I have to review and process an INTERNAL MOVE from location STOCK to location OUTPUT.
b) In Menu Warehouse ->Warehouse Management->Delivery Orders, I have to review and process an  OUTGOING MOVE from location OUTPUT to location CUSTOMERS.

My issue comes like this:
In Menu Warehouse ->Warehouse Management->Delivery Orders, I review and process an INTERNAL MOVE from location STOCK to location OUTPUT. For some reason this process creates 3 OUTGOING MOVES/DOCUMENTS (from location OUTPUT to location CUSTOMERS) instead of just 1.

In Menu Warehouse ->Warehouse Management->Delivery Orders, When I review after the previous step I have:
One OUTGOING MOVE from location OUTPUT to location CUSTOMERS. With the same contents as the original INTERNAL MOVE (two lines) and the lines inside this move are in status READY to process. This one is OK.

One OUTGOING MOVE from location OUTPUT to location CUSTOMERS. With only
one of the detail lines in the original INTERNAL MOVE and the lines
inside this move are in status waiting (even though, there is stock).
Why is this? This MOVE should not be created.

One OUTGOING MOVE from location OUTPUT to location CUSTOMERS. With the
same contents as the original INTERNAL MOVE and the lines inside this
move are in status READY to process. Why is this? This MOVE should not
be created.

Please let me know if you need more info.

Best Regards
V

** Affects: openobject-addons
     Importance: Undecided
         Status: New

-- 
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/760836

Title:
  Additional Delivery orders created incorrectly

Status in OpenERP Modules (addons):
  New

Bug description:
  In OpenERP V6, Windows 7.

  I have a default database with chained locations Output->Customers

  I created a Sales Order with 2 detail lines. Line 1 has quantity 6,
  line 2 has quantity 4. Both lines are set to be sourced from the
  available stock.

  When I confirm the Sales Order I have to make a two step delivery in the warehouse management:
  a) In Menu Warehouse ->Warehouse Management->Delivery Orders, I have to review and process an INTERNAL MOVE from location STOCK to location OUTPUT.
  b) In Menu Warehouse ->Warehouse Management->Delivery Orders, I have to review and process an  OUTGOING MOVE from location OUTPUT to location CUSTOMERS.

  My issue comes like this:
  In Menu Warehouse ->Warehouse Management->Delivery Orders, I review and process an INTERNAL MOVE from location STOCK to location OUTPUT. For some reason this process creates 3 OUTGOING MOVES/DOCUMENTS (from location OUTPUT to location CUSTOMERS) instead of just 1.

  In Menu Warehouse ->Warehouse Management->Delivery Orders, When I review after the previous step I have:
  One OUTGOING MOVE from location OUTPUT to location CUSTOMERS. With the same contents as the original INTERNAL MOVE (two lines) and the lines inside this move are in status READY to process. This one is OK.

  One OUTGOING MOVE from location OUTPUT to location CUSTOMERS. With
  only one of the detail lines in the original INTERNAL MOVE and the
  lines inside this move are in status waiting (even though, there is
  stock). Why is this? This MOVE should not be created.

  One OUTGOING MOVE from location OUTPUT to location CUSTOMERS. With the
  same contents as the original INTERNAL MOVE and the lines inside this
  move are in status READY to process. Why is this? This MOVE should not
  be created.

  Please let me know if you need more info.

  Best Regards
  V