I am trying to understand when pack_operations_ids are used and when move_lines are used.
I do not understand what pack_operations_ids represents from a functional point of view.
The move_lines describes what should happen, and the pack_operation_ids describes how that happened.
If there is a PO requesting 5 units of X product.
this will generate a picking with stock move [not yet a pack_operation_ids created] with 5 units of the X product.
assume that we received just 3 units of it. After confirming the transfer. a line of pack_operation_ids will be created with the transferred qty '3' and the stock move will be updated from 5 to 3 and a new picking will be created with the remaining qty '2'.
For the new picking that with move with 2 qty. Assume we do a transfer with splitting 'we tracking by lot/serial for example'. So we split the 2 qty into to serials; so after confirmation the move will remain the same 'with 2 qty' and we have two lines of pack_operation_ids for our splitting.
Actually there is a link between the stock.moves and stock.pack.operations that implemented by the class stock_move_operation_link . So there may be several pack operations linked to one stock move. I think the stock operation used to enhance quantities computations. Also you can notice that in the picking printing the report will check if there is a pack_operation_ids if yes then it'll print them instead of move_lines ...
I know this may not be the perfect answer, and someone else can illustrate it with more information.
But I hope it can helps you to grasp a little bit .
Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!
About This Community
|Asked: 2/15/16, 5:24 PM|
|Seen: 316 times|
|Last updated: 2/16/16, 5:46 AM|