[ADD]: Images of stock_location module.
bzr revid: rch@tinyerp.com-20110314052522-mc7uaf8g2207wclw
This commit is contained in:
parent
cb168e18b6
commit
e6332012c2
|
@ -36,7 +36,7 @@
|
|||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'images' : ['purchase_order.jpeg', 'purchase_analysis.jpeg', 'request_for_quotation.jpeg'],
|
||||
'images' : ['images/purchase_order.jpeg', 'images/purchase_analysis.jpeg', 'images/request_for_quotation.jpeg'],
|
||||
'depends': ['base', 'account', 'stock', 'process', 'procurement'],
|
||||
'data': [
|
||||
'security/purchase_security.xml',
|
||||
|
|
|
@ -29,7 +29,7 @@
|
|||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'images' : ['purchase_analytic_distribution.jpeg'],
|
||||
'images' : ['images/purchase_analytic_distribution.jpeg'],
|
||||
'depends': ['purchase', 'account_analytic_plans'],
|
||||
'init_xml': [],
|
||||
'update_xml': ['purchase_analytic_plans_view.xml'],
|
||||
|
|
|
@ -22,7 +22,7 @@
|
|||
"version" : "0.1",
|
||||
"author" : "OpenERP SA",
|
||||
"category" : "Generic Modules/Sales & Purchases",
|
||||
"images" : ['purchase_requisitions.jpeg'],
|
||||
"images" : ['images/purchase_requisitions.jpeg'],
|
||||
"website" : "http://www.openerp.com",
|
||||
"description": """
|
||||
This module allows you to manage your Purchase Requisition.
|
||||
|
|
|
@ -43,7 +43,7 @@ Thanks to the double entry management, the inventory controlling is powerful and
|
|||
* Graph : Products to send in delay (date < = today)
|
||||
""",
|
||||
"website" : "http://www.openerp.com",
|
||||
"images" : ["delivery_orders.jpeg", "inventory_analysis.jpeg","location.jpeg","moves_analysis.jpeg","physical_inventories.jpeg","warehouse_dashboard.jpeg"],
|
||||
"images" : ["images/delivery_orders.jpeg", "images/inventory_analysis.jpeg","images/location.jpeg","images/moves_analysis.jpeg","images/physical_inventories.jpeg","images/warehouse_dashboard.jpeg"],
|
||||
"depends" : ["product", "account"],
|
||||
"category" : "Generic Modules/Inventory Control",
|
||||
"init_xml" : [],
|
||||
|
|
|
@ -25,9 +25,8 @@
|
|||
'version': '1.0',
|
||||
'category': 'Generic Modules/Inventory Control',
|
||||
'description': """
|
||||
This module supplements the Warehouse application by adding support for per-product
|
||||
location paths, effectively implementing Push and Pull inventory flows.
|
||||
|
||||
This module supplements the Warehouse application by adding support for per-product location paths, effectively implementing Push and Pull inventory flows.
|
||||
-----------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
Typically this could be used to:
|
||||
* Manage product manufacturing chains
|
||||
* Manage default locations per product
|
||||
|
@ -55,19 +54,19 @@ processed, or require a manual confirmation, depending on the parameters.
|
|||
|
||||
Pull flows
|
||||
----------
|
||||
Pull flows are a bit different from Pull flows, in the sense that they are not related to
|
||||
Pull flows are a bit different from Push flows, in the sense that they are not related to
|
||||
the processing of product moves, but rather to the processing of procurement orders.
|
||||
What is being pulled is a need, not directly products.
|
||||
A classical example of Push flow is when you have an Outlet company, with a parent Company
|
||||
A classical example of Pull flow is when you have an Outlet company, with a parent Company
|
||||
that is responsible for the supplies of the Outlet.
|
||||
|
||||
[ Customer ] <- A - [ Outlet ] <- B - [ Holding ] <~ C ~ [ Supplier ]
|
||||
|
||||
When a new procurement order (A, coming from the confirmation of a Sale Order for example) arrives
|
||||
in the Outlet, it is converted into another procurement (B, via a Push flow of type 'move')
|
||||
in the Outlet, it is converted into another procurement (B, via a Pull flow of type 'move')
|
||||
requested from the Holding. When procurement order B is processed by the Holding company, and
|
||||
if the product is out of stock, it can be converted into a Purchase Order (C) from the Supplier
|
||||
(Push flow of type Purchase). The result is that the procurement order, the need, is pushed
|
||||
(Pull flow of type Purchase). The result is that the procurement order, the need, is pushed
|
||||
all the way between the Customer and Supplier.
|
||||
|
||||
Technically, Pull flows allow to process procurement orders differently, not only depending on
|
||||
|
@ -85,6 +84,7 @@ You can use the demo data as follow:
|
|||
- When delivering the customer: Pick List -> Packing -> Delivery Order from Gate A
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'images': ['images/pulled_flow.jpeg','images/pushed_flow.jpeg'],
|
||||
'depends': ['procurement','stock','sale'],
|
||||
'init_xml': [],
|
||||
'update_xml': ['stock_location_view.xml', 'security/ir.model.access.csv', 'procurement_pull_workflow.xml'],
|
||||
|
|
Loading…
Reference in New Issue