c2c-oerpscenario team mailing list archive

["Jacques-Etienne Baudoux \(OpenERP\)" <763426@xxxxxxxxxxxxxxxxxx>]

Hi Steffi,

The pushed flows should not be split automatically. However I agree that
there are issues when you split manually the pushed flows.

Here are the issues to solve:
* When you copy/split a move in waiting state, the new moves should be in state confirmed
* When you make a partial reception, do not break the dest_id when splitting the move
* When you mark a move as done, check all moves with same dest_id are also done before advancing state of chained move from waiting to available (assigned)
* If received qty is more than expected qty, raise an error message (wizard/stock_move.py)


** Changed in: openobject-addons
       Status: Triaged => Confirmed

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

Title:
  Chained location and partial delivery (reception)

Status in OpenERP Modules (addons):
  Confirmed

Bug description:
  I defined my warehouse like this

  'Stock' with chained location 'Quality Control'
  'Quality Control' with chained location 'Stock free'
   
  Create a new RFQ with 10 pce and convert it to PO, system generates 3 stock moves:
  1. 'Supplier' --> 'Stock' 10 pce (available)
  2. 'Stock' --> 'Quality Control' 10 pce (waiting)
  3. 'Quality Control' --> 'Stock free' 10 pce (waiting)
   
  Open 'Receptions' enter a new production lot 0000175 and process partial (4 pce)

  I've got 4 stock moves now:
  1. 'Supplier' --> 'Stock' 4 pce (done)
  1.1 'Supplier' --> 'Stock' 6 pce (available)
  2. 'Stock' --> 'Quality Control' 10 pce (waiting)
  3. 'Quality Control' --> 'Stock free' 10 pce (waiting)

  In 'Internal Moves' I open stock move no 2 ('Stock'--> 'Quality Control')
  I Change qty from 10 to 4 and select the production lot 0000175
  State does not change: even if I try to 'Check Availability' a warning occurs "Not enough stock to reserve the products". The state for 4 pce is still 'Waiting'

  The only chance to process this move is to set 'Force Availability'
   
  Hence: the system splits move 1 when partial reception gets processed. IMHO chained moves 2 and 3 (created through 'chained location') should get splited as well: one move with qty received in state available and a second move with qty not received in state waiting.