openerp-expert-production team mailing list archive

[Ana Juaristi <ajuaristio@xxxxxxxxx>]

Only one little thing. When you make manual merge of orders origin of them
is mantained. This is extremely important to mantain documental
traceability. If it is made automatically, the process should take this in
mind. (my 2 cents)

If you use scheduler, the traceability is lost and this is correct since it
applies only to virtual stock of products and it doesn't mind what process
or needs created this "under" min stock rule virtual stock.

About mrp_jit... it has got a dependence with projects (at less in 5.0) so,
you can not have an implementation with projects installed without having
mrp_jit!!! This causes some problems on several implementation that work
with projects but buy against stock with min rules.

2011/4/10 Graeme Gellatly <gdgellatly@xxxxxxxxx>

> Sorry I just checked the code, while it is called as a consequence of
> action_ship_create the functionality is in make_po of procurement.
>
>
> On Sat, Apr 9, 2011 at 9:52 AM, Graeme Gellatly <gdgellatly@xxxxxxxxx>wrote:
>
>> Raphael,
>>
>> Regards your question, I have implemented this functionality already for a
>> client.  It was designed for MTO Purchase Orders, as with MTS orders like
>> yours, by simply not having JIT installed, you would already receive just
>> the one purchase order when the scheduler ran.  For me that is a better
>> solution than the one proposed.  It already does what you want without a new
>> module.
>>
>> Basically for your question I have implemented like this.
>>
>> When action_ship_create runs in a jit environment, and procurement orders
>> and draft po's are created, we run a check (_po_exists) which checks for an
>> open draft PO related to the same SO, for the same supplier, to the same
>> location etc etc.  If it finds one it adds the line to the order rather than
>> create a new order.  This is working really well in production.  In my
>> clients case they want just one PO for the supplier for each Sales Order as
>> all MTO products are custom made.  Unfortunately it is tied up in another
>> module which does quite a lot more but I can give code if you like.  By
>> simply removing the check for same SO it would merge all orders.
>>
>>
>> On Sat, Apr 9, 2011 at 6:08 AM, Jan Verlaan - Veritos <
>> jverlaan@xxxxxxxxxx> wrote:
>>
>>>  Hi Raphael,
>>>
>>> isn't the requested functionality not already available via the action
>>> button in purchase orders?
>>>  Merge Purchase orders Help
>>> <https://app.veritos.nl/view_diagram/process?res_model=purchase.order.group&res_id=False&title=Merge+Purchase+orders>
>>>       Are you sure you want to merge these orders ?
>>>    Please note that: Orders will only be merged if: * Purchase Orders
>>> are in draft * Purchase Orders belong to the same supplier * Purchase Orders
>>> are have same stock location, same pricelist Lines will only be merged if: *
>>> Order lines are exactly the same except for the product,quantity and unit
>>>      Ok, it isn't called automatically, but if you want to merge
>>> automatically perhaps this function could be called after MRP run instead of
>>> building a new one.
>>>  ------------------------------
>>> Met vriendelijke groet,
>>>
>>> *Veritos - Open Source Business Solutions
>>> Jan Verlaan CPIM*
>>>
>>> Op 08-04-11 19:07, Raphael Valyi schreef:
>>>
>>> Hello production experts,
>>>
>>>  with the current OpenERP procurement system: different sale order lines
>>> will have have their own move and their own procurement. It means that if
>>> you have 0 stock and you by 2 PC1 in one order and then 3 PC1 in an other
>>> order during the same day, you may have two draft purchase orders, even if
>>> the supplier is the same, generating manual merging work for the purchase
>>> manager.
>>> For our large ecommerce customers this is not usable.
>>> So we we made (Sebastien Beau) the "procurement_purchase_update" module
>>> https://code.launchpad.net/~akretion-team/+junk/procurement_purchase_update<https://code.launchpad.net/%7Eakretion-team/+junk/procurement_purchase_update>
>>> It at least, when it's the same product, it now adds up to the the same
>>> purchase order line when the purchase order is still in draft and if the MRP
>>> scheduler triggers new procurements.
>>>
>>>  Now, when the product is different, the procurement for the purchase
>>> moves need to be different. So currently it still generate different
>>> purchase orders even if the supplier is the same.
>>> I'm about to extend this module to offer an option to add to the same
>>> purchase order, even if purchase procurements are different.
>>>
>>>  So the question is:
>>> did somebody do something similar already? Where?
>>> Do you see any problem with this reasoning? Are you interested in that?
>>>
>>>
>>>  Thank you very much.
>>>
>>>
>>>  --
>>>  Raphaël Valyi
>>> Founder and consultant
>>> +55 21 3010 9965
>>> www.akretion.com
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openerp-expert-production
>>> Post to     : openerp-expert-production@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openerp-expert-production
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openerp-expert-production
>>> Post to     : openerp-expert-production@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openerp-expert-production
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-expert-production
> Post to     : openerp-expert-production@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-expert-production
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Ana Juaristi Olalde
Avanzosc, S.L.
Partner OpenERP
www.anajuaristi.com
www.openerpsite.com
www.avanzosc.com
Skype: avanzosc
677 93 42 59 - 943 02 69 02