Note:
The only part to fix in 6.0 is the same that has been fixed in trunk: chaining locations should not create duplicate moves. The rest is ok. Currently in 6.0, if there is a chained location on the location where the products are received, you get duplicate lines when you process the incoming picking.
The production lot/batch number does not have to be copied to the chained moved, as OpenERP does not care about traceability of internal moves. If it is important to have it, the operator can manually input the number in the chained moved (even after the move has been processed, if needed)
Be careful when fixing this, as:
- it should behave properly when you do a partial receipt of the goods
- it should behave correctly if the chaining is automatic-no-step-added (i.e no chained moved at all; the original move is modified)
I haven't looked at which revision this was fixed in trunk, sorry.
Note:
The only part to fix in 6.0 is the same that has been fixed in trunk: chaining locations should not create duplicate moves. The rest is ok. Currently in 6.0, if there is a chained location on the location where the products are received, you get duplicate lines when you process the incoming picking.
The production lot/batch number does not have to be copied to the chained moved, as OpenERP does not care about traceability of internal moves. If it is important to have it, the operator can manually input the number in the chained moved (even after the move has been processed, if needed)
Be careful when fixing this, as: no-step- added (i.e no chained moved at all; the original move is modified)
- it should behave properly when you do a partial receipt of the goods
- it should behave correctly if the chaining is automatic-
I haven't looked at which revision this was fixed in trunk, sorry.