[IMP] Inventory: New screenshots for reception in 3-steps (#634)
Before Width: | Height: | Size: 18 KiB After Width: | Height: | Size: 25 KiB |
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 19 KiB |
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 9.4 KiB |
Before Width: | Height: | Size: 9.7 KiB After Width: | Height: | Size: 19 KiB |
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 9.4 KiB |
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 23 KiB |
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 9.1 KiB |
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 23 KiB |
@ -2,113 +2,108 @@
|
||||
Process a Receipt in three steps (Input + Quality + Stock)
|
||||
==========================================================
|
||||
|
||||
In many companies, it is necessary to assess the received good. The goal
|
||||
is to check that the products correspond to the quality requirements
|
||||
agreed with the suppliers. Therefore, adding a *quality control step*
|
||||
in the goods receipt process can become essential.
|
||||
Quality is essential for most companies. To make sure we maintain quality throughout the supply
|
||||
chain, it only makes sense that we assess the quality of the products received from suppliers.
|
||||
To do so, we will add a quality control step.
|
||||
|
||||
Odoo uses routes to define exactly how you will handle the different
|
||||
receipt steps. The configuration is done at the level of the warehouse.
|
||||
By default, the reception is a one-step process, but changing the
|
||||
configuration can allow having 3 steps.
|
||||
Odoo uses routes to define how to handle the different receipt steps.
|
||||
Configuration of those routes is done at the warehouse level. By default, the reception is a
|
||||
one-step process, but it can also be configured to have two-steps or three-steps processes.
|
||||
|
||||
The 3-steps flow is as follows: You receive the goods in an input area,
|
||||
then transfer them into a quality area for *quality control*. When the
|
||||
quality check has been processed, you can move the goods from QC to
|
||||
stock. Of course, you may change the quantity and only transfer to stock
|
||||
the quantity that is valid and decide that you will return the quantity
|
||||
that is not good.
|
||||
The three-steps flow works as follows: you receive the goods in your receiving area, then transfer
|
||||
them into a quality area for quality control (QC). When the quality check is completed, the goods
|
||||
that match the QC requirements are moved to stock
|
||||
|
||||
Multi-Step Routes
|
||||
=================
|
||||
Activate Multi-Step Routes
|
||||
==========================
|
||||
|
||||
First, you will need to activate the *multi-step routes* option.
|
||||
Indeed, routes provide a mechanism to chain different actions together.
|
||||
Here, we will chain the picking to the shipping.
|
||||
The first step is to allow the use of *Multi-Step Routes*. Routes provide a mechanism to chain different
|
||||
actions together. In this case, we will chain the picking step to the shipping step.
|
||||
|
||||
To activate *multi-step routes*, open the *inventory app*, and go to
|
||||
:menuselection:`Configuration --> Settings` and activate the option. By default,
|
||||
activating *multi-step routes* will also activate *Storage
|
||||
Locations*.
|
||||
To enable *Multi-Step Routes*, go to :menuselection:`Inventory --> Configuration --> Settings` and
|
||||
activate the option.
|
||||
|
||||
.. image:: media/three_steps_01.png
|
||||
:align: center
|
||||
:alt: View of the features to enable in order to use multi-step routes for goods reception
|
||||
|
||||
Warehouse configuration
|
||||
=======================
|
||||
.. note::
|
||||
By default, activating *Multi-Step Routes* also activates *Storage
|
||||
Locations*.
|
||||
|
||||
Now that *Multi-Step Routes* is activated, go to :menuselection:`Configuration -->
|
||||
Warehouse` and open the one you will use to deliver in 3 steps. Then,
|
||||
you can select the option *Pack good, send goods in output and then
|
||||
deliver (3 steps)* as *Outgoing Shipments*.
|
||||
Configure warehouse for receipt in 3-steps
|
||||
==========================================
|
||||
|
||||
Once *Multi-Step Routes* has been activated, go to :menuselection:`Inventory --> Configuration -->
|
||||
Warehouse` and enter the warehouse which should work with the 3-steps reception. Then, select
|
||||
*Receive goods in input, then quality and then stock (3 steps)* for *Incoming Shipments*.
|
||||
|
||||
.. image:: media/three_steps_02.png
|
||||
:align: center
|
||||
:alt: View of the incoming shipment strategy to choose to receive goods in three steps
|
||||
|
||||
Activating this option will lead to the creation of two new locations,
|
||||
*Output* and *Packing Zone*.
|
||||
Activating this option leads to the creation of two new locations: *Input* and *Quality Control*.
|
||||
To rename them, go to :menuselection:`Inventory --> Configuration --> Locations` and select
|
||||
the one you want to rename.
|
||||
|
||||
Of course, you can rename them if you want. To do so, go to
|
||||
:menuselection:`Configuration --> Locations` and select the one you want to rename.
|
||||
Change its name and hit save.
|
||||
Create a Purchase Order
|
||||
=======================
|
||||
|
||||
Create a Sales Order
|
||||
====================
|
||||
To start the 3-steps reception process, create a *Request for Quotation* from the *Purchase* app,
|
||||
add some storable products to it and confirm. Then, three pickings are created with your *Purchase
|
||||
Order* as the source document:
|
||||
|
||||
In the *Sales* app, create a quotation with storable products to
|
||||
deliver. Then, confirm it and three pickings will be created and linked
|
||||
to your sale order.
|
||||
1. The first one with a reference *IN* to designate the receipt
|
||||
process;
|
||||
|
||||
2. The second one with a reference *INT*, which is the move to the
|
||||
quality control zone;
|
||||
|
||||
3. The last one with a reference *INT* to designate the move to stock.
|
||||
|
||||
.. image:: media/three_steps_03.png
|
||||
:align: center
|
||||
:alt: View of the three moves created by the purchase of products in three steps strategy
|
||||
|
||||
Now, click on the button. You should see three different pickings:
|
||||
Process the receipt, quality control and entry in stock
|
||||
=======================================================
|
||||
|
||||
- The first one, with a reference PICK, designates the picking process;
|
||||
As the receipt operation is the first one to be processed, it has a *Ready* status while the others
|
||||
are *Waiting Another Operation*.
|
||||
|
||||
- The second one, with a reference PACK, is for the packing process;
|
||||
|
||||
- The third one, with a reference OUT, designates the shipping process.
|
||||
To access the receipt operation, click on the button from the *Purchase Order* or go back to the
|
||||
*Inventory* app dashboard and click on *Receipts*.
|
||||
|
||||
.. image:: media/three_steps_04.png
|
||||
:align: center
|
||||
:alt: View of the button to click to see the receipts that need to be processed
|
||||
|
||||
Process the picking, packing, and delivery
|
||||
==========================================
|
||||
|
||||
The first operation to be processed is the picking and has a *Ready*
|
||||
status, while the others are *Waiting Another Operation*. The packing
|
||||
will become *Ready* as soon as the picking is marked as *Done*.
|
||||
|
||||
You can enter the picking operation from here, or access it through the
|
||||
inventory app.
|
||||
In the receipt order, products are always considered available because they come from the supplier.
|
||||
Then, the receipt can be validated.
|
||||
|
||||
.. image:: media/three_steps_05.png
|
||||
:align: center
|
||||
:alt: View of the move (internal transfer) from the reception area to the warehouse input area
|
||||
|
||||
Note that, if you have the product in stock, it will be automatically
|
||||
reserved and you can validate the picking document.
|
||||
Once the receipt has been validated, the transfer to quality becomes *Ready*. And, because the documents
|
||||
are chained to each other, products previously received are automatically reserved on the
|
||||
transfer. Then, the transfer can be directly validated.
|
||||
|
||||
.. image:: media/three_steps_06.png
|
||||
:align: center
|
||||
|
||||
Now that the picking has been validated, the packing order is ready to
|
||||
be processed. Since the documents are chained, the products that have
|
||||
been picked are automatically reserved on the packing order so you can
|
||||
directly validate it.
|
||||
:alt: View of the button to click to see the internal transfers that need to be processed
|
||||
|
||||
.. image:: media/three_steps_07.png
|
||||
:align: center
|
||||
:alt: View of the move (internal transfer) from the input area to the quality control area
|
||||
|
||||
Now, the transfer that enters the products to stock is *Ready*. Here, it is again ready to be
|
||||
validated in order to transfer the products to your stock location.
|
||||
|
||||
.. image:: media/three_steps_08.png
|
||||
:align: center
|
||||
|
||||
Then, you can validate your packing. In doing so, the delivery order can
|
||||
be processed. Once again, it will be ready to be validated so you can
|
||||
transfer the products to the customer location.
|
||||
:alt: View of the button to click to see the internal transfers that need to be processed
|
||||
|
||||
.. image:: media/three_steps_09.png
|
||||
:align: center
|
||||
|
||||
.. image:: media/three_steps_10.png
|
||||
:align: center
|
||||
:alt: View of the move (internal transfer) from the quality control area to the stock
|
@ -2,149 +2,206 @@
|
||||
Define Quality Control Points
|
||||
=============================
|
||||
|
||||
Quality is an important factor when it comes to products or services.
|
||||
Nowadays, quality has become the differentiating factor for all goods
|
||||
and services. It is vital for businesses to deliver products that meet
|
||||
or exceed expectations. It also helps minimize waste.
|
||||
|
||||
That is why most manufacturers would not think of eliminating the
|
||||
quality control from their manufacturing process. After all, removing
|
||||
quality controls would dramatically increase the number of defective
|
||||
products that the company then has to rework or scrap.
|
||||
|
||||
Then, using business applications to ensure data quality is important.
|
||||
With Odoo insuring the rear, any major problem can be avoided before
|
||||
occurring!
|
||||
|
||||
Quality Control Points
|
||||
======================
|
||||
|
||||
If it is the first *Quality Control Point* that you create, know that
|
||||
you need to open the *Quality* app. Then, go to :menuselection:`Quality Control -->
|
||||
Control Points`. Once there, you have to define the product on which
|
||||
the quality control will take place, as well as the operation at which
|
||||
it should take place.
|
||||
To create a *Quality Control Point*, go to :menuselection:`Quality
|
||||
--> Quality Control --> Control Points`. Once there, define the product
|
||||
on which the quality control point should take place. The operation at
|
||||
which it takes place also is to be defined here.
|
||||
|
||||
The *Quality Control Points* can take place during transfers or during
|
||||
the manufacturing process of the products. If you work with routings on
|
||||
your *Bill of Materials*, you have to precise at which step of the
|
||||
manufacturing process the quality control point should be applied.
|
||||
The *Quality Control Points* take place during transfers or during the
|
||||
manufacturing process of the products. If working with routings on
|
||||
*Bill of Materials*, you have to precise at which step of the
|
||||
manufacturing process the quality control point needs to be applied.
|
||||
|
||||
The control type defines at which frequency the quality checks should
|
||||
take place:
|
||||
The *Control Type* defines at which frequency the quality checks
|
||||
should take place:
|
||||
|
||||
- All Operations: all the operations will generate quality checks to perform;
|
||||
- **All operations**: all the operations automatically generate quality
|
||||
checks to perform;
|
||||
|
||||
- Randomly: the quality checks will only be performed on x% of the operation. You must define the percentage yourself, on the control point;
|
||||
- **Randomly**: the quality checks only perform on x% of the operation. The
|
||||
percentage needs to be defined on the control point;
|
||||
|
||||
- Periodically: the quality checks will be performed periodically. The periodicity is based on the period you define (once a day, once a week).
|
||||
- **Periodically**: the quality checks are performed periodically. The
|
||||
periodicity is based on the defined period (once a day, once a
|
||||
week).
|
||||
|
||||
.. image:: media/control_points_01.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
Quality Control Point Types
|
||||
===========================
|
||||
|
||||
Now that the rest is configured, you need to define the type of quality
|
||||
check.
|
||||
Now, one thing remains to be configured: the type of quality check.
|
||||
There are several types that can be used: text, take a picture,
|
||||
pass-fail, take a measure, register consumed material, register
|
||||
by-product, and print label.
|
||||
|
||||
.. note::
|
||||
Some of the types are only available with the manufacturing application.
|
||||
Some types are available only with the manufacturing application
|
||||
installed.
|
||||
|
||||
Text
|
||||
----
|
||||
|
||||
This control point type allows you to give instructions to your workers
|
||||
during the transfer, or the manufacturing process.
|
||||
This control point type allows giving instructions to workers during the
|
||||
transfer or during the manufacturing process.
|
||||
|
||||
.. image:: media/control_points_01.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
.. image:: media/control_points_02.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
.. image:: media/control_points_03.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
Take a Picture
|
||||
--------------
|
||||
|
||||
This control point type asks you to take a picture of the product in a
|
||||
transfer, or when manufacturing it.
|
||||
This control point type asks to take a picture of the product applied in
|
||||
a transfer or when manufacturing it.
|
||||
|
||||
.. image:: media/control_points_04.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
.. image:: media/control_points_05.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
.. image:: media/control_points_06.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
.. tip::
|
||||
This process can be simplified by using a connected :doc:`camera
|
||||
<../../iot/devices/measurement_tool>`.
|
||||
|
||||
Pass-Fail
|
||||
---------
|
||||
|
||||
This type of control point requires that you specify if the products
|
||||
pass or fail a specific text. It can be applied for both transfers or
|
||||
manufacturing orders.
|
||||
*Pass-Fail* requires to specify if the products pass or fail specific
|
||||
criteria. It can be applied for both transfers or manufacturing orders.
|
||||
|
||||
.. image:: media/control_points_07.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
For this kind of control point type, you have the possibility to define
|
||||
a failure message that will give instructions to follow in case of
|
||||
quality check failure.
|
||||
For this kind of type, there is the possibility to define a failure
|
||||
message giving instructions to follow in case of failure.
|
||||
|
||||
.. image:: media/control_points_08.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
.. image:: media/control_points_09.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
.. image:: media/control_points_10.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
Take a Measure
|
||||
--------------
|
||||
|
||||
This control point type requires you to enter the product’s measurements
|
||||
during a transfer, or during the manufacturing process.
|
||||
Taking measures requires to enter the product’s measurements during a
|
||||
transfer or during the manufacturing process.
|
||||
|
||||
To use it, it necessary to specify the norm for your product’s
|
||||
measurements, but also a tolerance threshold. Doing so, all the products
|
||||
with good measures can are automatically accepted.
|
||||
|
||||
.. image:: media/control_points_11.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
For this kind of control point type, you also have the possibility to
|
||||
define a failure message that will give instructions to the worker.
|
||||
As for *Pass-Fail*, this type allows defining a failure message that
|
||||
gives instructions to the worker.
|
||||
|
||||
.. image:: media/control_points_12.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
.. image:: media/control_points_13.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
.. image:: media/control_points_14.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
.. tip::
|
||||
This process can be simplified by using connected :doc:`measurement tools <../../iot/devices/camera>`.
|
||||
|
||||
Register Consumed Materials
|
||||
---------------------------
|
||||
|
||||
This control point type requires you register the component serial/lot
|
||||
numbers during the manufacturing process. It is only available if you
|
||||
work with routings.
|
||||
When using *Register Consumed Materials*, it is required to register
|
||||
the component’s serial/lot numbers during the manufacturing process.
|
||||
|
||||
.. note::
|
||||
This type is only available when working with routings.
|
||||
|
||||
.. image:: media/control_points_15.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
.. image:: media/control_points_16.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
Register By-Products
|
||||
--------------------
|
||||
|
||||
With this control point type, you must register the serial/lot number of
|
||||
the by-products that are manufactured. It is also only available with
|
||||
routings.
|
||||
With *Register By-Products*, it is required to register the serial/lot
|
||||
number of the by-products that are manufactured.
|
||||
|
||||
.. note::
|
||||
This type is only available when working with routings.
|
||||
|
||||
.. image:: media/control_points_17.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
.. image:: media/control_points_18.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
Print Label
|
||||
-----------
|
||||
|
||||
This control point type allows you to print labels to add to the product
|
||||
during the manufacturing process.
|
||||
*Print Label*, as its name points out, allows printing labels to add
|
||||
to the product during the manufacturing process.
|
||||
|
||||
.. image:: media/control_points_19.png
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
.. image:: media/control_points_20.png
|
||||
:align: center
|
||||
:align: center
|
||||
:alt:
|
||||
|
||||
.. tip::
|
||||
This process can be simplified by using a connected :doc:`printer <../../iot/devices/printer>`.
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 26 KiB |
Before Width: | Height: | Size: 17 KiB After Width: | Height: | Size: 19 KiB |
Before Width: | Height: | Size: 5.2 KiB After Width: | Height: | Size: 15 KiB |
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 36 KiB |
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 21 KiB |
Before Width: | Height: | Size: 6.7 KiB After Width: | Height: | Size: 19 KiB |
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 40 KiB |
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 29 KiB |
Before Width: | Height: | Size: 6.0 KiB After Width: | Height: | Size: 17 KiB |
Before Width: | Height: | Size: 4.4 KiB After Width: | Height: | Size: 11 KiB |
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 40 KiB |
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 29 KiB |
Before Width: | Height: | Size: 5.7 KiB After Width: | Height: | Size: 16 KiB |
Before Width: | Height: | Size: 7.4 KiB After Width: | Height: | Size: 21 KiB |
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 50 KiB |
Before Width: | Height: | Size: 67 KiB After Width: | Height: | Size: 90 KiB |
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 48 KiB |
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 41 KiB |