odoo
/
odoo
2
0
Fork 0
Code Pull Requests Releases Activity

[IMP] Chpt4 

bzr revid: jco@openerp.com-20140325172644-3u4us23o6szzuwoh
This commit is contained in:
Josse Colpaert 2014-03-25 18:26:44 +01:00
parent a2e061accf
commit 452f3299e7
1 changed files with 21 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
addons/stock/doc/stock.rst
View File

@ -170,6 +170,8 @@ It is however possible that the procurement goes into Exception when no procurem
By default, the JIT scheduler is installed and the system will try to check the procurement immediately when it is confirmed. If this would give performance issues, it is possible to uninstall this and then it will only run the procurements immediately generated by the sales order. This will result in a delivery order, but the procurements generated by the delivery orders, will not be run. This will however be done by the Scheduler.
A push rule can not be applied anymore when the rule was created from a pull rule, so pull rules kind of have priority over the push rules.
=======================================================
Procurement method of stock moves and procurement rules
@ -361,10 +363,12 @@ A Route is a collection of procurement rules and push rules. Routes can be appl
* Warehouse
* Sale Order Line (activated through setting Settings > Configuration > Sales > Choose MTO, Dropship, ... on sale order lines)
If they can be applied on these models can be specified on the route itself. For example, you could create a route 'purchase' with the purchase procurement rule from stock in it allowed to be selected on Product Category. Then you could go to the product category e.g. Purchased Goods and add it there. When a procurement is made in stock for the products in this category, the system will try to create purchase orders for it.
If they can be applied on these models can be specified on the route itself. For example, you could create a route 'buy' with the purchase procurement rule from stock in it allowed to be selected on Product Category. Then you could go to the product category e.g. Purchased Goods and add it there. When a procurement is made in stock for the products in this category, the system will try to create purchase orders for it.
===============================================================================
How does the system choose the correct procurement/push rule for a procurement?
How does the system choose the correct procurement rule
===============================================================================
When a sales order creates a procurement it passes some useful information to it. First, a sales order has a warehouse where the goods need to be picked up. This warehouse will be copied on the procurement. For example, when you have a procurement in Customers, but you know it has to be delivered from Warehouse WH, it can add a route with a procurement rule from WH/Stock to Customers and it will not apply a procurement rule from WH2/Stock to Customers. Second, it is possible to supply an extra route on the sale order line itself. This can come in handy when you decide on the sale order what route to follow e.g. if you sometimes decide to do dropshipping, you could enter it there. These routes are copied on the procurement related to the sale order line.
@ -379,16 +383,25 @@ When OpenERP needs to find a procurement/push rule, it will check the routes tha
If in any of these cases, multiple rules are found, it will select the rule with the highest sequence. This sequence can be changed in Warehouse > Routes (drag/drop the lines). Normally, this will play almost no role.
Actually, when you select MTO on a product, this is a route that is chosen. As in the basic configuration, it is defined on the product. (it is shown in the product form in a special widget that shows all the possible elements it could have in the one2many and you can select them) As suchn this route will be chosen over the standard route and will have a rule that puts procure method "Create Procurement on Source" to stock. In the route MTO all such rules for all warehouses will be put in the standard configuration.
Actually, when you select MTO on a product, this is a route that is chosen. As in the basic configuration, it is defined on the product. (it is shown in the product form in a special widget that shows all the possible elements it could have in the one2many and you can select them) As such, this route will be chosen over the standard route and will have a rule that puts procure method "Create Procurement on Source" to stock. In the route MTO all such rules for all warehouses will be put in the standard configuration.
The reason behind such a configuration is that in most situations, the routes followed through the warehouse are the same for almost all products. The exceptions on it can be defined for certain product categories or products. Some things like MTO or buy/manufacture might be better to put on product level. And then it is still possible that you change your mind on the sales order line.
================================================
How does the system choose the correct push rule
================================================
Searching for a push rule is quite similar as for the pull rule. It will however just search for all the rules in the routes of product and product categories and take the rule with the highest sequence. (???)
========================
Simple Warehouse config
=======================
When you activate setting << >> and go to Warehouse > Warehouse and select a Warehouse (or create a new), you will have a simplified way to configure these routes without worrying about its complexity.
When you activate setting <<Activate push/pull rules >> and go to Warehouse > Warehouse and select a Warehouse (or create a new), you will have a simplified way to configure these routes without worrying about its complexity.
For the incoming and outgoing shipments you can supply how many steps are needed to receive or ship goods. This allows you e.g. to receive at the docks, and move the goods later on into a precise location in your racks. It can also be interesting to do some quality control. For shipping, you can also put your products at the gates first, but you might also want to package them at a separate location before bringing them at the gates. These routes will be directly related to the warehouse.
For the incoming and outgoing shipments, you can supply how many steps are needed to receive or ship goods. This allows you e.g. to receive at the docks, and move the goods later on into a precise location in your racks. It can also be interesting to do some quality control. For shipping, you can also put your products at the gates first, but you might also want to package them at a separate location before bringing them at the gates. These routes will be directly related to the warehouse.
If you check Purchase or Manufacture to resupply this warehouse, if a product is manufacture/buy, it will also be able to buy/manufacture from/in this warehouse.
@ -403,11 +416,11 @@ What happens behind simple warehouse config
The wizard will create all the necessary locations and picking types to support the selected settings.
The Incoming shipments and Outgoing shipments are bundled into routes that are on the warehouse. So, if you choose that warehouse, it will choose the route by default.
The purchase to resupply is a procurement rule added to the buy route, which will also buy to this warehouse.
The Incoming shipments and Outgoing shipments routes are bundled into routes that are on the warehouse. So, if you choose that warehouse, it will choose the route by default. The incoming routes will also have the push rules associated with them.
The purchase to resupply is a procurement rule added to the buy route, which will also buy to this warehouse.
Also crossdock is added as a route to the warehouse. This can be added on specific products and product categories that upon arrival are almost immediately transferred to the customer. (might be mostly the case with mto products)