[trunk/7.0] carrier information not propagated from sale order to pickings

Bug #1192115 reported by Alexandre Fayolle - camptocamp
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Committed
Low
OpenERP Publisher's Warranty Team
OpenERP Community Backports (Addons)
Status tracked in 7.0
7.0
Fix Released
Undecided
Unassigned

Bug Description

When I create a SO in v7 with, and I add the shipping fees using the "Add in Quote" button, the carrier_id is removed from the Sale Order.

As a result, the carrier information is not set on the pickings when the SO is confirmed, and this is not good because it prevents grouping the processing of pickings by carrier, which is very useful from a logistics point of view.

Fixing this requires care to avoid invoicing the shipping fees twice.

Tags: maintenance

Related branches

Revision history for this message
Amit Parik (amit-parik) wrote :

Hello,

You are using a delivery module for carrier . Carriers is one kind of services, that's why we have linked the service product with the delivery carriers. So whenever you add the delivery it will also add the delivery cost with service line product on sale order line.

As we know we can't deliver the service kind of product means when you have services on the sale order line it doesn't create the delivery order that's why we are not able to see that line on delivery order.

Please share your answer.

Thanks and waiting for your reply!

Changed in openobject-addons:
status: New → Incomplete
Revision history for this message
Guewen Baconnier @ Camptocamp (gbaconnier-c2c) wrote :

Hello Amit,

The problem is not that the service line is missing in the Delivery Order.

The problem is that the `carrier_id` is empty on the Delivery Order when you added shipping fees in a Sale Order.

Revision history for this message
Amit Parik (amit-parik) wrote :

Hello Camptocamp guys,

Sorry for misinterpretation.

I also want to share here something, When you add the delivery into quote then carrier_id will become blank on sale order. That's why you didn't see it on delivery order.

It has two scenario 1)Invoice on sale order 2) Invoice based on delivery Order.

So when we creates a invoice form the delivery order it will creates a problem.

Thank you!

Revision history for this message
Amit Parik (amit-parik) wrote :

I missed something ....Let me continue again...

We have put already a helps on "Add to quote" button such as "If you don't 'Add in Quote', the exact price will be computed when invoicing based on delivery order(s)"

So we have to perform the action like following way as per above two scenario.

1) Invoice on sale order. Create Sale order, add the delivery and use "add to quote" button. Here we have to add the cost on sale order because we have to create invoice form the order, So cost must be add on sale order.

2) Invoice based on Delivery Order: Create Sale order .... add delivery. Don't add delivery cost on sale order because our invoice will be based on delivery, So delivery cost don't need to add on sale order.

Hope I clear.

Thanks and please share your view!

Revision history for this message
Alexandre Fayolle - camptocamp (alexandre-fayolle-c2c) wrote :

Hello Amit, the problem is not in the invoicing part. I understand that part, thanks for the clear explanation. The problem is when handling the logistics.

Imagine an e-commerce company offering an expensive express shipping (using carrier UPS) and a low cost slow shipping (using carrier Chronopost). The Chronopost truck comes around once a week on wednesday to pick up the products, and the UPS truck comes once a day. The invoicing is made on sale order, and the orders are prepaid, so the customer says 'I choose the Chronopost delivery method' and gets invoiced for the amount related to this carrier. So we are using your scenario 1 (in comment #4).

Now, for the people working in the warehouse, things get complicated : they need to group the orders they prepare based on the delivery method (carrier_id), so that the process the UPS delivered sale orders in priority each day on the one hand, and make sure that all the orders shipped by Chronopost are ready on wednesday. However, since we are using "invoice on sale order" (which the logistics people don't care about), they don't have the information available on the stock.picking objects.

Is this explanation clearer?

Regards,

Alexandre

Revision history for this message
Amit Parik (amit-parik) wrote :

That's great..!!! Alexandre,

Thanks for providing a real use case. I also agreed with you that whenever we are using "invoice on sale order" (which the logistics people don't care about), they don't have the information available on the stock.picking objects.

So we have to pass the carrier_id on delivery order , let it be confirm it :)

Thank you!

summary: - [7.0] carrier information not propagated from sale order to pickings
+ [trunk/7.0] carrier information not propagated from sale order to
+ pickings
Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 3 (openerp-dev-addons3)
importance: Undecided → Low
status: Incomplete → Confirmed
tags: added: maintenance
Changed in openobject-addons:
status: Confirmed → In Progress
Revision history for this message
Somesh Khare (somesh.khare) wrote :

Hello Alexandre,

I have fixed this issue into lp:~openerp-dev/openobject-addons/7.0-595240-opw-skh branch with,

Revision ID: <email address hidden>
Revision Number: 9312

This branch is under the review of our experts and will be merge soon in the stable 7.0 addons, once approved.

Changed in openobject-addons:
assignee: OpenERP R&D Addons Team 3 (openerp-dev-addons3) → OpenERP Publisher's Warranty Team (openerp-opw)
status: In Progress → Fix Committed
Revision history for this message
Alexandre Fayolle - camptocamp (alexandre-fayolle-c2c) wrote : Re: [Bug 1192115] Re: [trunk/7.0] carrier information not propagated from sale order to pickings

On 14/03/2014 15:30, Frank Miao wrote:
> ** Branch unlinked: lp:~openerp-dev/openobject-addons/7.0-595240-opw-skh
>
Hello Frank.

Could you explain why you unlinked that branch from the bug report?

--
Alexandre Fayolle
Chef de Projet
Tel : + 33 (0)4 79 26 57 94

Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac Cedex
http://www.camptocamp.com

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.