On 10 Feb 17:58, Àngel Àlvarez Serra wrote:
> 2015-02-10 17:30 GMT+01:00 Cédric Krier <[email protected]>:
> > On 10 Feb 16:40, Àngel Àlvarez Serra wrote:
> >> 2015-02-10 16:11 GMT+01:00 Cédric Krier <[email protected]>:
> >> >> I add this two fields:
> >> >> cost: Float()
> >> >> causer: Many2One to party.party.
> >> >
> >> > What are that?
> >>
> >> Cost: cost to manage complaint.
>
> To quantify cost.
> Not important could be added in custom module.
>
> >
> > Sorry, I don't see the usage.
> >
> >> Causer: (maybe we can find other name). Who introduce this complaint,
> >> culprit for example Company, Supplier, Manufacturer, Employee...
> >
> > But it is the customer who introduces a customer complaint.
>
> Used to dectect if we need to purchase to another supplier for example,
> because
> you have to many complaints that you determine that the culprit is the
> provider, or employee.
There are 2 cases:
- you have only one supplier for a product, so you don't need to
know encode the supplier
- you have many supplier for a product and so you don't know which
supplier supplied this one (or you know because you have a lot and
so this information is enough to find the supplier).
> >> >> document: reference to any object of ERP, configurable (like sale,
> >> >> purchase or invoice).
> >> >
> >> > It is better to set an origin on the generated record.
> >>
> >> >
> >> >> It easy and simplier and you can manage any complaint manaually,
> >> >
> >> > It is already the case with the proposal.
> >> >
> >> >> whith
> >> >> this designs you can manage refund, or give a present and let for
> >> >> other modules to make automation.
> >> >
> >> > Idem with current proposal.
> >>
> >> But, I try to manage any type of complaint not only sale to make
> >> extensible.
> >
> > I don't understand which other complaint you try to manage.
> > I already stated that supplier complaint will have a different workflow
> > (just like purchase has a different workflow from sale).
> >
>
> I will try to explain despite my English.
>
> I don't think that purchase, shipment or invoce complaint have
> different workflow
> if you remove sales. specific funcionality and fields
I only say for purchase it is different because you don't have to take
action, you have to complain to the supplier so the communication
channel is in the opposite way.
For shipment and invoice, it depends if it is a incoming or outgoing
shipment and if it is a customer or supplier invoice.
So the case of outgoing shipment and customer invoice are supported in
the current design. The other will be on a future supplier_complaint.
> >> > So you just want to have no action per default an having an other module
> >> > for each major modules like sale, account_invoice etc.
> >> > I don't think it diserve that as for me, customer complaint needs a
> >> > customer and such parties are in a large cases created by the sale
> >> > module.
> >>
> >> Yes, but you can receive a complaint for a delivery, invoice.
> >
> > Yes it is supported by the current design.
>
> yes, but actions it's only related sales refund and credit notes.
And what do you want to do more?
--
Cédric Krier - B2CK SPRL
Email/Jabber: [email protected]
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/
