stock outgoing deliveries - must check for sign of quantity
Bug #588197 reported by
Ferdinand
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Addons (MOVED TO GITHUB) |
Won't Fix
|
Undecided
|
Unassigned | ||
Odoo Server (MOVED TO GITHUB) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
currently it is possible (and IMHO good) to be able to include returning goods (like pallets) in outgoing deliveries.
the reports apparently assume all goods are outgoing and do not print quantity with negative sign.
Changed in openobject-addons: | |
status: | New → Invalid |
status: | Invalid → New |
Changed in openobject-server: | |
status: | New → Invalid |
Changed in openobject-addons: | |
status: | New → Triaged |
To post a comment you must log in.
Small remark: I voted for your blueprint: /blueprints. launchpad. net/openobject- addons/ +spec/packing- sequence
https:/
(different type of pick lists should have different sequences). And I think we should go that way further: All pick lists should be coherent and all pick lists should have visible source location and destination location (stock_picking object even has hidden fields for that). This way pick lists could be much better identified and filtered in functionality. I will have to do it in PL localization anyway because of convention used here.
So I think it is better expect that pick list are more consistent than expect reports analyse stock moves inside pick lists if they are different than pick type. Return palette should be in separate pick list of type "in" in my opinion.
But it is true that SO works bad now: If you have product and palette, You made shipment of both, then you made return shipment of palette (in separate pick list of type "in") and you invoice just product (not palette because it was returned) You get in SO status (progress bar) that you still didn't invoiced palette.
I think palette management will need separate module because it is more complex. For separate discussion.