[6 stable][purchase_requisition] requisition workflow missing supplier feedback

[Raphaël Valyi - http://www.akretion.com]

Hello,

using stable 6:
I don't see how one can use the purchase requisition module:

create a new purchase requisition with some product, then create new quotations for it.

I supposed that at this step we send the request for quotation to each supplier, by mail or they even access it using our OpenERP.

In any case how am I supposed to keep track which are the quotations where we already got the price from the supplier and the others for which we don't have it yet?
Currently, there is only the "convert to purchase order" button available to change the status of a quotation. But that would validate the purchase order and even create an incoming shipment. This is really not what you want at this stage as you didn't even choose yet the supplier or which order lines go to which supplier.

Seems unusable as it is. Do I miss something? I remember that a few days/weeks ago, purchase orders had a 'confirmed by supplier' button/state that would have made the workflow much more appropriate here. Is that some kind of surprise regression? Is that some poison change introduced when creating the 'purchase_double_validation' module?

I'm about to make this module better, but at least it should be usable first.
Thanks

[Quentin THEURET @Amaris (qtheuret)]

Hello Raphael,

Indeed, it seems that it's a big issue.

The normal workflow should be : draft -> confirmed -> confirmed by
supplier -> done
or
with the purchase_double_validation : draft -> confirmed -> confirmed by
manager -> confirmed by supplier -> done

Do you agree with me ?

When the purchase_double_validation module is installed, if the total
amount of your order is not superior than the 'limit of amount', the
Request for Quotation is automatically confirmed by the supplier. If
it's superior, everything is ok.

Quentin

Le 20/01/2011 02:35, Raphaël Valyi - http://www.akretion.com a écrit :
> Public bug reported:
>
> Hello,
>
> using stable 6:
> I don't see how one can use the purchase requisition module:
>
> create a new purchase requisition with some product, then create new
> quotations for it.
>
> I supposed that at this step we send the request for quotation to each
> supplier, by mail or they even access it using our OpenERP.
>
> In any case how am I supposed to keep track which are the quotations where we already got the price from the supplier and the others for which we don't have it yet?
> Currently, there is only the "convert to purchase order" button available to change the status of a quotation. But that would validate the purchase order and even create an incoming shipment. This is really not what you want at this stage as you didn't even choose yet the supplier or which order lines go to which supplier.
>
> Seems unusable as it is. Do I miss something? I remember that a few
> days/weeks ago, purchase orders had a 'confirmed by supplier'
> button/state that would have made the workflow much more appropriate
> here. Is that some kind of surprise regression? Is that some poison
> change introduced when creating the 'purchase_double_validation' module?
>
> I'm about to make this module better, but at least it should be usable first.
> Thanks
>
> ** Affects: openobject-addons
> Importance: Undecided
> Status: New
>

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

Quentin, Vinay,

I hope you are not mistaken: for me purchase_requisition is unusable even
without the 'purchase_double_validation' installed as indeed I need the
workflow to be:
"draft -> confirmed -> confirmed by
supplier -> done"

Vinay, could could please justify why it's considered a "whishlist"?
I don't understand at all how you can use the module the way the workflow is
now, so why isn't that just considered some important bug? Could you please
comment?

On Thu, Jan 20, 2011 at 6:35 AM, Quentin THEURET <email address hidden>wrote:

> Hello Raphael,
>
> Indeed, it seems that it's a big issue.
>
> The normal workflow should be : draft -> confirmed -> confirmed by
> supplier -> done
> or
> with the purchase_double_validation : draft -> confirmed -> confirmed by
> manager -> confirmed by supplier -> done
>
> Do you agree with me ?
>
> When the purchase_double_validation module is installed, if the total
> amount of your order is not superior than the 'limit of amount', the
> Request for Quotation is automatically confirmed by the supplier. If
> it's superior, everything is ok.
>
> Quentin
>
>
> Le 20/01/2011 02:35, Raphaël Valyi - http://www.akretion.com a écrit :
> > Public bug reported:
> >
> > Hello,
> >
> > using stable 6:
> > I don't see how one can use the purchase requisition module:
> >
> > create a new purchase requisition with some product, then create new
> > quotations for it.
> >
> > I supposed that at this step we send the request for quotation to each
> > supplier, by mail or they even access it using our OpenERP.
> >
> > In any case how am I supposed to keep track which are the quotations
> where we already got the price from the supplier and the others for which we
> don't have it yet?
> > Currently, there is only the "convert to purchase order" button available
> to change the status of a quotation. But that would validate the purchase
> order and even create an incoming shipment. This is really not what you want
> at this stage as you didn't even choose yet the supplier or which order
> lines go to which supplier.
> >
> > Seems unusable as it is. Do I miss something? I remember that a few
> > days/weeks ago, purchase orders had a 'confirmed by supplier'
> > button/state that would have made the workflow much more appropriate
> > here. Is that some kind of surprise regression? Is that some poison
> > change introduced when creating the 'purchase_double_validation' module?
> >
> > I'm about to make this module better, but at least it should be usable
> first.
> > Thanks
> >
> > ** Affects: openobject-addons
> > Importance: Undecided
> > Status: New
> >
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/705218
>
> Title:
> [6 stable][purchase_requisition] requisition workflow missing supplier
> feedback
>
> Status in OpenERP Modules (addons):
> New
>
> Bug description:
> Hello,
>
> using stable 6:
> I don't see how one can use the purchase requisition module:
>
> create a new purchase requisition with some product, then create new
> quotations for it.
>
> I supposed that at this step we send the request for quotation to each
...

[Quentin THEURET @Amaris (qtheuret)]

Raphael,

I'm agree with you, but, for the moment, it's the
purchase_double_validation module which adds the state 'confirmed'.
If I understand you, the workflow without purchase_double_validation is
the following :
draft -> confirmed -> confirmed by supplier -> done

and, with the purchase_double_validation module :
draft -> confirmed -> confirmed by supplier -> done (if the amount is
less than the amount limit)
or
draft -> confirmed -> approbate by manager -> confirmed by supplier ->
done (if the amount is more than the amount limit).

Is it correct ?

Quentin

Le 20/01/2011 12:38, Raphaël Valyi - http://www.akretion.com a écrit :
> Quentin, Vinay,
>
> I hope you are not mistaken: for me purchase_requisition is unusable even
> without the 'purchase_double_validation' installed as indeed I need the
> workflow to be:
> "draft -> confirmed -> confirmed by
> supplier -> done"
>
> Vinay, could could please justify why it's considered a "whishlist"?
> I don't understand at all how you can use the module the way the workflow is
> now, so why isn't that just considered some important bug? Could you please
> comment?
>
>
> On Thu, Jan 20, 2011 at 6:35 AM, Quentin THEURET <email address hidden>wrote:
>
>> Hello Raphael,
>>
>> Indeed, it seems that it's a big issue.
>>
>> The normal workflow should be : draft -> confirmed -> confirmed by
>> supplier -> done
>> or
>> with the purchase_double_validation : draft -> confirmed -> confirmed by
>> manager -> confirmed by supplier -> done
>>
>> Do you agree with me ?
>>
>> When the purchase_double_validation module is installed, if the total
>> amount of your order is not superior than the 'limit of amount', the
>> Request for Quotation is automatically confirmed by the supplier. If
>> it's superior, everything is ok.
>>
>> Quentin
>>
>>
>> Le 20/01/2011 02:35, Raphaël Valyi - http://www.akretion.com a écrit :
>>> Public bug reported:
>>>
>>> Hello,
>>>
>>> using stable 6:
>>> I don't see how one can use the purchase requisition module:
>>>
>>> create a new purchase requisition with some product, then create new
>>> quotations for it.
>>>
>>> I supposed that at this step we send the request for quotation to each
>>> supplier, by mail or they even access it using our OpenERP.
>>>
>>> In any case how am I supposed to keep track which are the quotations
>> where we already got the price from the supplier and the others for which we
>> don't have it yet?
>>> Currently, there is only the "convert to purchase order" button available
>> to change the status of a quotation. But that would validate the purchase
>> order and even create an incoming shipment. This is really not what you want
>> at this stage as you didn't even choose yet the supplier or which order
>> lines go to which supplier.
>>> Seems unusable as it is. Do I miss something? I remember that a few
>>> days/weeks ago, purchase orders had a 'confirmed by supplier'
>>> button/state that would have made the workflow much more appropriate
>>> here. Is that some kind of surprise regression? Is that some poison
>>> change introduced when creating the 'purchase_double_validation' module?
>>>
>>> I'm about to make this module better, but at least it should be ...

[qdp (OpenERP) (qdp)]

Hi Quentin, Raphaël,

i've read through the discussion and indeed i have to confirm that the module purchase_double_validation is working exaclty as Quentin is explaining, except that the approbation state is not only dedicated for the manager but could also be usefull if you want an approval from your supplier (that's the reason the state is named "Approved" and not "Approved by Manager", or neither "Approved by Supplier").

So, Raphaël, in order to have the purchase_requisition module working eaxctly as you're expecting, you should install the purchase_double_validation module and set (with the configuration wizard) a limit amount = 0. It will add an validation step for each and every time.

The only remaining question is: should we set a dependancy between those 2 modules (in order to have purchase_double_validation automatically installed when installing purchase_requisition) ? i'm not sure... actually we though it was already usefull without as we could say that we encode the PO of the potential suppliers whennever we receive them, but we'll confirm only the one we choose for our purchase tender.

Thank you both for your contribution,
Quentin

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

Quentin,

thank you very much for those explanations.
1) I think that the dependency is required indeed, else I don't see anyway
to use the module
2) This might not be the general solution, but I can tell you that here in
the Sao Paulo 100 employees I just started implementing OpenERP 6 (don't
worry, we will have you yet an other maintenance contract), we need both a
validation step for purchase orders and also the purchase_requisition
module. So in that case, setting 0 as the validation amount would suck. I
guess we could of course program some extension, but ideally you could use
both the the validation feature and the supplier approval state required for
purchase requisitions.
Any patch that would make both usages compatible?

Thanks

On Thu, Jan 20, 2011 at 2:04 PM, qdp (OpenERP) <email address hidden>wrote:

> Hi Quentin, Raphaël,
>
> i've read through the discussion and indeed i have to confirm that the
> module purchase_double_validation is working exaclty as Quentin is
> explaining, except that the approbation state is not only dedicated for
> the manager but could also be usefull if you want an approval from your
> supplier (that's the reason the state is named "Approved" and not
> "Approved by Manager", or neither "Approved by Supplier").
>
> So, Raphaël, in order to have the purchase_requisition module working
> eaxctly as you're expecting, you should install the
> purchase_double_validation module and set (with the configuration
> wizard) a limit amount = 0. It will add an validation step for each and
> every time.
>
> The only remaining question is: should we set a dependancy between those
> 2 modules (in order to have purchase_double_validation automatically
> installed when installing purchase_requisition) ? i'm not sure...
> actually we though it was already usefull without as we could say that
> we encode the PO of the potential suppliers whennever we receive them,
> but we'll confirm only the one we choose for our purchase tender.
>
>
> Thank you both for your contribution,
> Quentin
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/705218
>
> Title:
> [6 stable][purchase_requisition] requisition workflow missing supplier
> feedback
>
> Status in OpenERP Modules (addons):
> Confirmed
>
> Bug description:
> Hello,
>
> using stable 6:
> I don't see how one can use the purchase requisition module:
>
> create a new purchase requisition with some product, then create new
> quotations for it.
>
> I supposed that at this step we send the request for quotation to each
> supplier, by mail or they even access it using our OpenERP.
>
> In any case how am I supposed to keep track which are the quotations where
> we already got the price from the supplier and the others for which we don't
> have it yet?
> Currently, there is only the "convert to purchase order" button available
> to change the status of a quotation. But that would validate the purchase
> order and even create an incoming shipment. This is really not what you want
> at this stage as you didn't even choose yet the supplier or which order
> lines go to which supplier.
>
> Seems ...