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
