loss of traceability on a chainded location

[Joannes Landy]

for example, i have add a input location to the warehouse.
This input location is chaining with a automatic move to the stock location.

when i validate a purchase order with some products:
 * there is a incoming shipment by partner location to input location
 * there is a internal move from the input location to stock location

I assign 2 production lots to my product on the incoming shipment.
So my original stock move is splitting into 2 lines with their own production lot.
When i validate the incoming shipment, the chained stock move from input location to stock location is automatically validated.

It's ok, but the chained stock move don't copy the informations about the production lot. So the stock move loss the traceability information.
I can't see where is the production lot on my warehouse.

The same problem appears when we used the pack number.
The same problem appears if we use a manual chained but we can correct it before validation.
This bug is on version 6.0 and 6.1

[Quentin THEURET @Amaris (qtheuret)]

Le 02/02/2012 14:34, Joannes Landy a écrit :
> Public bug reported:
>
> for example, i have add a input location to the warehouse.
> This input location is chaining with a automatic move to the stock location.
>
> when i validate a purchase order with some products:
> * there is a incoming shipment by partner location to input location
> * there is a internal move from the input location to stock location
>
> I assign 2 production lots to my product on the incoming shipment.
> So my original stock move is splitting into 2 lines with their own production lot.
> When i validate the incoming shipment, the chained stock move from input location to stock location is automatically validated.
>
> It's ok, but the chained stock move don't copy the informations about the production lot. So the stock move loss the traceability information.
> I can't see where is the production lot on my warehouse.
>
> The same problem appears when we used the pack number.
> The same problem appears if we use a manual chained but we can correct it before validation.
> This bug is on version 6.0 and 6.1
>
> ** Affects: openobject-addons
> Importance: Undecided
> Status: New
>
Hello Joannes,

I'm agree with you on this point. The issue is due to time of the
creation of the destination move : at the first move creation, the
system watches if the the destination location has a chaining type and
if it's the case, it creates the second move.
So, when you change production lot or other information in the first
move, the destination move is already created and information are not
propagated in the destination move.

In the other side, if you can change the production lot in the
destination move, there is integrity control of the data with the
original move !!

There are big issues on the chaining moves !

--
Quentin THEURET
<email address hidden>

[Joannes Landy (j-landy)]

Hi Quentin,

i have asked to the support of OpenERP to correct this bug with our maintenance contract.

Regards,

[Numérigraphe (numerigraphe)]

Dear Joannes Landy,
Please direct them to Bug #692948 instead, because this is a duplicate and work already seems to have been made on the original bug.
Lionel.