stock: when splitting incoming shipments, system allows to split lots in more than the total quantity, without warning

Bug #776245 reported by Lorenzo Battistini
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Status tracked in Trunk
6.0
Fix Released
Low
OpenERP Publisher's Warranty Team
Trunk
Fix Released
Low
OpenERP R&D Addons Team 2

Bug Description

openobject-addons/6.0 revno 4545

steps:

1- Create new incoming shipments
2- Add it a stock move with quantity '3'
3- Open the move and click on 'Split'
4- Add 4 lots
5- Click 'Ok'

System splits the move in 3 lots losing information about the fourth.
I would expect that, for instance, while clicking 'Ok', system warned me about having added too many lots

Tags: maintenance

Related branches

summary: - stock: when splitting incoming shipments, system allows to split in more
- lots than the total quantity
+ stock: when splitting incoming shipments, system allows to split lots in
+ more than the total quantity
Revision history for this message
Steffi Frank (Bremskerl, DE) (steffi-frank) wrote : [Bug 776245] [NEW] stock: when splitting incoming shipments,system allows to split lots in more than the total quantity

Lorenzo,

I think it really should be just a warning, not a prohibition. It happens quiet often a suppliers deliveres more than you ordered....

summary: stock: when splitting incoming shipments, system allows to split lots in
- more than the total quantity
+ more than the total quantity, without warning
Revision history for this message
Lorenzo Battistini (elbati) wrote :

Hello Steffi,

see this example:

Company bought 3 products and receives 6 products.
So, the warehouseman has in front of him 6 lots (6 serial numbers).
He opens the incoming shipment that has 1 stock.move with quantity '3'.
He splits the move in order to enter the serial numbers that he sees.
So, he enters 6 serial numbers.
He clicks 'Ok'.
The stock.move is split in 3 moves with the first 3 serial numbers, without warning the warehouseman

Amit Parik (amit-parik)
Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 2 (openerp-dev-addons2)
importance: Undecided → Low
status: New → Confirmed
Changed in openobject-addons:
status: Confirmed → In Progress
Revision history for this message
Rohan Nayani(Open ERP) (ron-tinyerp) wrote :

Hello,

Thanks for Reporting.
It has been fixed in lp:~openerp-dev/openobject-addons/trunk-bug-776245-ron
Revision ID: <email address hidden>
Revision num:4721.

It will be available in trunk soon.

Changed in openobject-addons:
status: In Progress → Fix Committed
tags: added: maintenance
Revision history for this message
Priyesh (OpenERP) (pso-openerp) wrote :

Hello Lorenzo,

It has been fixed in https://code.launchpad.net/~openerp-dev/openobject-addons/6.0-opw-10344-pso
Rev-id: <email address hidden>
Rev-no: 4680

It will be merged soon with Addons branch.

Thanks for reporting.

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hello Lorenzo,

Thanks for your participation here.

Talking more about your comment #2, I would like to share one opinion.

Company bought 3 products and receives 6 products.
In this case, we should add one extra move which adds 3 more quantities, and hence the reception of 6 qty can be justified.

As of now, the current 6.0.2 does not allow reception of more no. of qtys of products than the actual on move. A warning will be raised in such a case.

If I talk about your case, I agree its a scenario where we can get more than needed from suppliers. We can allow this in OpenERP, but imagine the vulnerability when user can enter 300 qty while only 5 qty were supposed to be entered.

Hence, we opted to restrict this by a warning message.

You can check latest 6.0 and work with this option as per #2.

Moreover, the issue reported here will be taken care of, by https://code.launchpad.net/~openerp-dev/openobject-addons/6.0-opw-10344-pso/+merge/66298.

We will be waiting for your inputs here and will proceed for the fix.

Thanks.

Revision history for this message
Lorenzo Battistini (elbati) wrote :

Hello Jay,

I approved that merge proposal as it fixes the problem for me.
It does precisely what I suggested.

Thanks

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Fix has been introduced over stable 6.0 by revision http://bazaar.launchpad.net/~openerp/openobject-addons/6.0/revision/4719.
Thanks.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.