openerp-community team mailing list archive

[Quentin THEURET <qt@xxxxxxxxxxxxxxxxxxx>]

Le jeu. 26 sept. 2013 17:05:37 CEST, Ray Carnes a écrit :
> What about reconfiguring the automatic move so that DO's need to be
> picked.
>
> Then DO's would just be 'ready to pick' instead of 'ready to deliver'
> and could be picked in any order, with the scheduler readjusting what
> is ready to pick after that when it is next run.
>
> (Haven't tested this, so I may be missing something).
>
> Ray.
>
>
> On Thu, Sep 26, 2013 at 6:02 AM, Alexandre Fayolle
> <alexandre.fayolle@xxxxxxxxxxxxxx
> <mailto:alexandre.fayolle@xxxxxxxxxxxxxx>> wrote:
>
>     On jeu. 26 sept. 2013 08:44:19 CEST, Alexandre Fayolle wrote:
>     > I agree.
>     >
>     > In the meantime I really need this feature for 7.0...
>     >
>     > Alexandre
>     >
>     > On jeu. 26 sept. 2013 08:41:46 CEST, Eric Caudal wrote:
>     >> It seems to me that should be part of the future WMS
>     implementation.
>     >> I am thinking of assignation sequence instead of only
>     assignation for
>     >> a SM. When proposing serving one product, SM would taken in
>     order of
>     >> assignation. Add to this a reorderable tree view and it could be a
>     >> nice and easy feature to use...
>     >>
>     >>
>     >> Eric CAUDAL
>     >> Eric Caudal
>     >> /CEO/
>     >> --
>     >> *Elico Corporation, Shanghai branch
>     >> /OpenERP Premium Certified Training Partner/ *
>     >> Cell: + 86 186 2136 1670
>     >> Office: + 86 21 6211 8017/27/37
>     >> Skype: elico.corp
>     >> eric.caudal@xxxxxxxxxxxxxx <mailto:eric.caudal@xxxxxxxxxxxxxx>
>     <mailto:eric.caudal@xxxxxxxxxxxxxx
>     <mailto:eric.caudal@xxxxxxxxxxxxxx>>
>     >> http://www.elico-corp.com
>     >>
>     >> Elico Corp
>     >> On 26/09/2013 14:34, Joël Grand-Guillaume wrote:
>     >>> I'm not aware of such a module in the community addons, but
>     the way
>     >>> you suggest to solve this seems good to me.
>     >>>
>     >>>
>     >>> On Wed, Sep 25, 2013 at 1:00 PM, Alexandre Fayolle
>     >>> <alexandre.fayolle@xxxxxxxxxxxxxx
>     <mailto:alexandre.fayolle@xxxxxxxxxxxxxx>
>     >>> <mailto:alexandre.fayolle@xxxxxxxxxxxxxx
>     <mailto:alexandre.fayolle@xxxxxxxxxxxxxx>>> wrote:
>     >>>
>     >>>     Hello,
>     >>>
>     >>>     I'm facing what seems to be a common need with sales
>     deliveries:
>     >>>
>     >>>     Given to sale orders SO001 and SO002, created and
>     validated in that
>     >>>     order, each with 5 units of product1, make to stock, with an
>     >>>     available
>     >>>     stock of 7 units, the picking for SO001 is ready to
>     deliver and
>     >>>     the one
>     >>>     for SO002 is not because there is not enough stock.
>     >>>
>     >>>     If for some reason, SO002 must be delivered first, there is no
>     >>>     clean way
>     >>>     of doing this with the standard OERP addons, AFAIK.
>     >>>
>     >>>     Is there a community addon solving this ?
>     >>>
>     >>>     A possible solution I've come up with involves the user
>     forcing
>     >>>     availability of the SO002 picking, with a customization
>     which would
>     >>>     recompute the availability of moves for the same
>     product(s) in the
>     >>>     affected stock.location after forcing the availability of the
>     >>>     moves. It
>     >>>     seems to me that this would integrate nicely with the rest
>     of the
>     >>>     sales
>     >>>     / logistic chain.
>     >>>
>     >>>     --
>     >>>     Alexandre Fayolle
>     >>>     Chef de Projet
>     >>>     Tel : + 33 (0)4 79 26 57 94
>     <tel:%2B%2033%20%280%294%2079%2026%2057%2094>
>     >>>     <tel:%2B%2033%20%280%294%2079%2026%2057%2094>
>     >>>
>     >>>     Camptocamp France SAS
>     >>>     Savoie Technolac, BP 352
>     >>>     73377 Le Bourget du Lac Cedex
>     >>>     http://www.camptocamp.com
>     >>>
>     >>>
>     >>>     _______________________________________________
>     >>>     Mailing list: https://launchpad.net/~openerp-community
>     >>>     <https://launchpad.net/%7Eopenerp-community>
>     >>>     Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>     <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
>     >>>     <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx
>     <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>>
>     >>>     Unsubscribe : https://launchpad.net/~openerp-community
>     >>>     <https://launchpad.net/%7Eopenerp-community>
>     >>>     More help   : https://help.launchpad.net/ListHelp
>     >>>
>     >>>
>     >>>
>     >>>
>     >>> --
>     >>>
>     >>>
>     >>> *camptocamp*
>     >>> INNOVATIVE SOLUTIONS
>     >>> BY OPEN SOURCE EXPERTS
>     >>>
>     >>> *Joël Grand-Guillaume*
>     >>> Division Manager
>     >>> Business Solutions
>     >>>
>     >>> +41 21 619 10 28 <tel:%2B41%2021%20619%2010%2028>
>     >>> www.camptocamp.com <http://www.camptocamp.com>
>     <http://www.camptocamp.com/>
>     >>>
>     >>>
>     >>>
>     >>> _______________________________________________
>     >>> Mailing list: https://launchpad.net/~openerp-community
>     >>> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>     <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
>     >>> Unsubscribe : https://launchpad.net/~openerp-community
>     >>> More help   : https://help.launchpad.net/ListHelp
>     >>
>     >>
>     >>
>     >> _______________________________________________
>     >> Mailing list: https://launchpad.net/~openerp-community
>     >> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>     <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
>     >> Unsubscribe : https://launchpad.net/~openerp-community
>     >> More help   : https://help.launchpad.net/ListHelp
>     >
>     >
>     >
>     > --
>     > Alexandre Fayolle
>     > Chef de Projet
>     > Tel : + 33 (0)4 79 26 57 94
>     <tel:%2B%2033%20%280%294%2079%2026%2057%2094>
>     >
>     > Camptocamp France SAS
>     > Savoie Technolac, BP 352
>     > 73377 Le Bourget du Lac Cedex
>     > http://www.camptocamp.com
>     >
>
>     Here is an implementation. Reviews are welcome.
>
>     https://code.launchpad.net/~camptocamp/stock-logistic-flows/7.0-add-stock_recompute_availability_on_force-afe/+merge/187768
>
>     --
>     Alexandre Fayolle
>     Chef de Projet
>     Tel : + 33 (0)4 79 26 57 94
>     <tel:%2B%2033%20%280%294%2079%2026%2057%2094>
>
>     Camptocamp France SAS
>     Savoie Technolac, BP 352
>     73377 Le Bourget du Lac Cedex
>     http://www.camptocamp.com
>
>
>     _______________________________________________
>     Mailing list: https://launchpad.net/~openerp-community
>     Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>     <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~openerp-community
>     More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp

Hello,

Why do that automatically ? Maybe just add a button to remove the 
availability on SM or SP to select which SM/SP you would set Not 
Available.

I fear that the automatic thing remove the availability of another 
SP/SM you would like send.

For example, if you have three SP, two available and one not available. 
You want to set availablee the not available one, you don't know which 
one of the two available SP will be changed. And if you need to force 
the availability for two of these SP, how to be sure that the good SPs 
become available ?

Your proposition about a priority on stock.picking object is IMHO a 
good solution and with a priority, the problem I raised above could be 
solved.


P.S. : On your MP, there are some conflicts that have to be resolved.

--
Quentin THEURET

TeMPO Consulting
9, rue du Parc
67205 Oberhausbergen
France

http://www.tempo-consulting.fr
Tel : +33 3 88 56 82 18
Fax : +33 3 88 56 46 64