Internal stock move stuck at waiting for another move

Bug #1250053 reported by Lara (Therp) on 2013-11-11
36
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Confirmed
Medium
OpenERP R&D Addons Team 2
OpenERP Community Backports (Addons)
Status tracked in 7.0
7.0
Undecided
Rafal Sobczynski

Bug Description

Hello,

I have some stock at my production location for production.
When creating a manufacturing order the following stock moves are created

Warehouse A/Stock -> Warehouse A/stock = A internal move

Warehouse A /Stock --> Virtual production

Virtual production --> Warehouse A/ Stock

At the first stock move (internal) OpenERP is waiting for a mutation, while there is enough stock at the location.
When I checking the internal move and check the availability OpenERP the following warning is shown (Not enough stock, unable to reserve the products.)

As I stated earlier there is enough stock at the location even if I put in a ridiculous amount of stock at the location.

So basically your manufacturing is stuck because of the waiting internal stock move.

Related branches

Amit Parik (amit-parik) wrote :

I seen two stock move after confirmation of the MO which is as below.

1) stock > stock (Waiting for another Move)
2) stock > production (Waiting for another Move)

it should be
1) stock > stock (available )
2) stock > production (Waiting for another Move).

Thanks for the reporting!

Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 2 (openerp-dev-addons2)
importance: Undecided → Medium
status: New → Confirmed
Yann Papouin (yann-papouin) wrote :

The internal stock.move is the one attached to the procurement.order, so when you say that the stock.move stays in 'waiting' state, what is the corresponding procurement.order state and message ?

the internal stock.move in my case is not a product I am buying, but one I am manufacturing. Raw material is bought and sent to an external Work Center for processing. after return, the MO is completed and produced the product required for the parent MO to start. but that parent MO can never be started as that internal move cannot be completed. I can assign the output of the inner MO correctly to the parent MO via the "Products to Consume" table, but there is that internal move which won't resolve.

Actually, just tried it again and it seems I can now continue the MO, if I "consume" the product in question both within the "Products to Consume" list AND in Extra Information > Picking List (see my word attachment for screenshots).

tags: added: maintenance
Patrick OShea (poshea) wrote :

This Fix :

if (move.state) == 'waiting':
    move.check_assign()

introduces a recursion error in some large Manufacturing Orders when confirming production.
I commented these lines and the recursion error is gone

I can confirm, this introduce recursion on MO's.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers