Re: [tryton-contrib] How to handle goods temporarily absent from the warehouse
2015-03-14 15:20 GMT+01:00 Mathias Behrle : > Hi all, > > it would be nice to find a generic approach for the following operations in > the > scope of many companies: > > - Handing out samples for inspection to the customer for evaluation and evtl. > later purchase. You can add a new location (even one per customer) and make an internal move for that. If you eventually sell them, you should pick up that location (well, warehouse) in the sale. > - Lending goods to the customer. > - Leasing goods to the customer. > > All operations have in common, that the goods still are property of the > warehouse, but physically are at the customers place. > > The challenge: since those goods are just temporarily unavailable and are > expected to come back to the storage zone, they shouldn't trigger any > provisioning mechanisms like internal or purchase requests. So for all kind of > requests the goods should behave as being in a location of type storage, but > without being available for sales. > > I have setup the following scenario: > > The stock part: > > - Defined a location of type storage as a child of the primary storage zone, > which shall contain the goods temporarily not available. > - This should allow for correct processing of requests, since e.g. > generate_internal_shipment is called with_child=True. > Note: it currently doesn't behave correctly (3.4), the child locations don't > seem to be propagated to the parent location. > - The display of the available quantity should then be the storage zone > with_childs=False. > Note: the display is currently that way, but could also be part of the > bug mentioned above. > > The model part: > > May be > - there could be a model similar to sale, that will generate moves targeting > the temporary locations depicted above instead or additional to the customer > location Why not using an internal shipment? > - or some asset type like it is done in Nan-tics module pool. > > Does this sound reasonable? Other ideas? > > > -- > > Mathias Behrle > MBSolutions > Gilgenmatten 10 A > D-79114 Freiburg > > Tel: +49(761)471023 > Fax: +49(761)4770816 > http://www.m9s.biz > UStIdNr: DE 142009020 > PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6 -- Albert Cervera i Areny Tel. 93 553 18 03 @albertnan www.NaN-tic.com
Re: [tryton-contrib] How to handle goods temporarily absent from the warehouse
On 14 Mar 15:20, Mathias Behrle wrote: > Hi all, > > it would be nice to find a generic approach for the following operations in > the > scope of many companies: > > - Handing out samples for inspection to the customer for evaluation and evtl. > later purchase. I guess it could be free product sample. > - Lending goods to the customer. > - Leasing goods to the customer. You don't do that with goods but with assets. > All operations have in common, that the goods still are property of the > warehouse, but physically are at the customers place. Not for assets (except rarely when you sale it but it is already managed). > The challenge: since those goods are just temporarily unavailable and are > expected to come back to the storage zone, they shouldn't trigger any > provisioning mechanisms like internal or purchase requests. So for all kind of > requests the goods should behave as being in a location of type storage, but > without being available for sales. Already with assets. -- Cédric Krier - B2CK SPRL Email/Jabber: cedric.kr...@b2ck.com Tel: +32 472 54 46 59 Website: http://www.b2ck.com/ pgpoH6_YYPeAz.pgp Description: PGP signature
[tryton-contrib] How to handle goods temporarily absent from the warehouse
Hi all, it would be nice to find a generic approach for the following operations in the scope of many companies: - Handing out samples for inspection to the customer for evaluation and evtl. later purchase. - Lending goods to the customer. - Leasing goods to the customer. All operations have in common, that the goods still are property of the warehouse, but physically are at the customers place. The challenge: since those goods are just temporarily unavailable and are expected to come back to the storage zone, they shouldn't trigger any provisioning mechanisms like internal or purchase requests. So for all kind of requests the goods should behave as being in a location of type storage, but without being available for sales. I have setup the following scenario: The stock part: - Defined a location of type storage as a child of the primary storage zone, which shall contain the goods temporarily not available. - This should allow for correct processing of requests, since e.g. generate_internal_shipment is called with_child=True. Note: it currently doesn't behave correctly (3.4), the child locations don't seem to be propagated to the parent location. - The display of the available quantity should then be the storage zone with_childs=False. Note: the display is currently that way, but could also be part of the bug mentioned above. The model part: May be - there could be a model similar to sale, that will generate moves targeting the temporary locations depicted above instead or additional to the customer location - or some asset type like it is done in Nan-tics module pool. Does this sound reasonable? Other ideas? -- Mathias Behrle MBSolutions Gilgenmatten 10 A D-79114 Freiburg Tel: +49(761)471023 Fax: +49(761)4770816 http://www.m9s.biz UStIdNr: DE 142009020 PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6 pgpbf41Cr5gpo.pgp Description: Digitale Signatur von OpenPGP
