From 4e84e87b7f6de406b94e72580d0d31278cb717f3 Mon Sep 17 00:00:00 2001 From: Fabien Pinckaers Date: Tue, 12 Oct 2010 00:35:54 +0200 Subject: [PATCH] [IMP] improved meta data on __openerp__.py bzr revid: fp@tinyerp.com-20101011223554-ad0mvm8s45inhmg3 --- addons/stock_location/__openerp__.py | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/addons/stock_location/__openerp__.py b/addons/stock_location/__openerp__.py index 875b336..5c2ae8e 100644 --- a/addons/stock_location/__openerp__.py +++ b/addons/stock_location/__openerp__.py @@ -74,6 +74,15 @@ Technically, Pull flows allow to process procurement orders differently, not onl the product being considered, but also depending on which location holds the "need" for that product (i.e. the destination location of that procurement order). +Use-Case +-------- + +You can use the demo data as follow: + CPU1: Sell some CPU1 from Shop 1 and run the scheduler + - Warehouse: delivery order, Shop 1: reception + CPU3: + - When receiving the product, it goes to Quality Control location then stored to shelf 2. + - When delivering the customer: Pick List -> Packing -> Delivery Order from Gate A """, 'author': 'OpenERP SA', 'depends': ['procurement','stock','sale'], @@ -91,4 +100,3 @@ product (i.e. the destination location of that procurement order). 'active': False, 'certificate': '0046505115101', } -# vim:expandtab:smartindent:tabstop=4:softtabstop=4:shiftwidth=4: -- 1.7.10.4