[7.0] Urgent please - wrong name get on partner to invoice

Bug #1112507 reported by Frederic Clementi - Camptocamp
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
New
Undecided
OpenERP Publisher's Warranty Team

Bug Description

Hello,

test done on : http://trunk-2760.runbot.openerp.com/

I created a partner named 'Axelor'
I created a contact 'Mr foo' which belong to Axelor

I invoice Mr foo.

I invoice Axelor later

On my customer invoice list view, if I do a group by partner, then Mr foo (Axelor) is considered a different partner of Axelor (see my printscreen).

I should see only Axelor in both case and the contact name should be the first line of the address.

This problem has impact in many places, it is not simple a group by issue but it is a convenient example for this bug report...

Same issue on orders obviously...

partner on accounting entries are correct (we already identify and fix the problem with qdp in december)

Many thanks

Frederic
Camptocamp

Tags: maintenance
Revision history for this message
Frederic Clementi - Camptocamp (frederic-clementi) wrote :
Revision history for this message
Nicolas JEUDY (njeudy) wrote :

I began to change this with :

- Contact of partner inherit of account (property_account_recievable and property_account_payable)
- The group by partner should do group by partner_id or parent_id if exist

You have same problem in task and issue ...

Revision history for this message
Frederic Clementi - Camptocamp (frederic-clementi) wrote :

Don't you think that we should never show the partner like Mr foo (Axelor) but Axelor instead (what ever the contact name) and keep the contact name as 1st line of the address ?

Revision history for this message
Nicolas JEUDY (njeudy) wrote : Re: [Bug 1112507] Re: [7.0] Urgent please - wrong name get on partner to invoice

I think a good way could be:

- keep partner_id for customer (AXELOR)
- Add contact_id that pointed on contact Mr foo (AXELOR)

Then report can use both for document generation.

Think it's a bad id to use first line adresse as contact because it is not
is principal use. First line is the first line of address :)

Nicolas JEUDY

Expert Technique et Fonctionnel Système d'Information
TUXSERVICES

22 rue du seminaire - 25170 Pelousey
e-mail : <email address hidden>
mob. : +33 (0)6 28 95 36 64
http://www.tuxservices.com

2013/2/4 Frederic Clementi - Camptocamp.com <
<email address hidden>>

> Don't you think that we should never show the partner like Mr foo
> (Axelor) but Axelor instead (what ever the contact name) and keep the
> contact name as 1st line of the address ?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1112507
>
> Title:
> [7.0] Urgent please - wrong name get on partner to invoice
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-addons/+bug/1112507/+subscriptions
>

Changed in openobject-addons:
assignee: nobody → OpenERP Publisher's Warranty Team (openerp-opw)
tags: added: maintenance
Revision history for this message
Nicolas JEUDY (njeudy) wrote :

@Naresh: Could you please write what will be done for this bug ? I think
there are differents possibilities to have functional way to deals with
partner and contact (maybe 2 fields) or use parent_id link for the partner
in case of res.partner.type = contact...

Nicolas JEUDY

Expert Technique et Fonctionnel Système d'Information
TUXSERVICES

22 rue du seminaire - 25170 Pelousey
e-mail : <email address hidden>
mob. : +33 (0)6 28 95 36 64
http://www.tuxservices.com

2013/2/5 Naresh(OpenERP) <email address hidden>

> ** Changed in: openobject-addons
> Assignee: (unassigned) => OpenERP Publisher's Warranty Team
> (openerp-opw)
>
> ** Tags added: maintenance
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1112507
>
> Title:
> [7.0] Urgent please - wrong name get on partner to invoice
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-addons/+bug/1112507/+subscriptions
>

Revision history for this message
Frederic Clementi - Camptocamp (frederic-clementi) wrote :

@ nicolas...

here is (unfortunately) the final decision that I have received today :

Hello,
the current behavior of group by is the expected and normal one, a contact is a customer and some companies may invoice to contact and want to see this contact in the result of group by. So this change won't be done. However, we will make that the search on partner field will list parents and children. Search on Axelor in invoice will show Axelor and also his contact 's invoices.
Thanks
Aline Preillon

Revision history for this message
Raphaël Valyi - http://www.akretion.com (rvalyi) wrote :

Hello Frederic and Nicolas,

I totally agree with Nicolas,
double read the party pattern http://www.tdan.com/view-articles/5014/
let's say now our party thing is the res.partner table/object.

It's not because companies, their contact and final customers now live in the same table that they should be always inter-changeable. They are not!!
Accouting, financial and fiscal data will be all wrong if you start invoicing contact Mr Foo.

Instead I suggest we put a domain on invoice partner_id field to forbid selecting a company contact. And as Nicolas suggest, we add a new contact_id field to carry the invoice contact.

Regards.

Revision history for this message
Ana Juaristi Olalde (ajuaristio) wrote :

+1 Frederic, Nicolas and Raphaël.
Invoicing to a contact or taking a company contact as an entity with fiscal atributions is a big mistake and even ilegal in several countries including spain.

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

Duplicates of this bug

Other bug subscribers