3
.. i18n: single: scheduler; lead time
7
single: scheduler; lead time
9
.. i18n: Calculation of lead times
10
.. i18n: =========================
13
Calculation of lead times
14
=========================
16
.. i18n: All procurement operations (that is, the requirement for both production orders and purchase orders)
17
.. i18n: are automatically calculated by the scheduler. But more than just
18
.. i18n: creating each order, OpenERP plans the timing of each step.
19
.. i18n: A planned date calculated by the system can be found on each order document.
22
All procurement operations (that is, the requirement for both production orders and purchase orders)
23
are automatically calculated by the scheduler. But more than just
24
creating each order, OpenERP plans the timing of each step.
25
A planned date calculated by the system can be found on each order document.
27
.. i18n: To organize the whole chain of manufacturing and procurement, OpenERP bases everything on the delivery
28
.. i18n: date promised to the customer. This is given by the date of the confirmation in the order and the
29
.. i18n: lead times shown in each product line of the order. This lead time is itself proposed automatically
30
.. i18n: in the field :guilabel:`Customer Lead Time` shown in the product form. This is the difference
31
.. i18n: between the time on an order and that of the delivery.
34
To organize the whole chain of manufacturing and procurement, OpenERP bases everything on the delivery
35
date promised to the customer. This is given by the date of the confirmation in the order and the
36
lead times shown in each product line of the order. This lead time is itself proposed automatically
37
in the field :guilabel:`Customer Lead Time` shown in the product form. This is the difference
38
between the time on an order and that of the delivery.
40
.. i18n: To see a calculation of the lead times, take the example of the cabinet above. Suppose that the
41
.. i18n: cabinet is assembled in two steps, using the two following bills of materials.
44
To see a calculation of the lead times, take the example of the cabinet above. Suppose that the
45
cabinet is assembled in two steps, using the two following bills of materials.
47
.. i18n: .. table:: Bill of Materials for 1 ARM100 Unit
49
.. i18n: ============ ======== ===============
50
.. i18n: Product Code Quantity Unit of Measure
51
.. i18n: ============ ======== ===============
52
.. i18n: PANLAT 2 Unit
53
.. i18n: BOIS002 0.25 m2
55
.. i18n: BOIS010 0.25 m2
56
.. i18n: TAQ000 12 Unit
57
.. i18n: ============ ======== ===============
60
.. table:: Bill of Materials for 1 ARM100 Unit
62
============ ======== ===============
63
Product Code Quantity Unit of Measure
64
============ ======== ===============
70
============ ======== ===============
72
.. i18n: .. table:: Bill of Materials for 2 PANLAT Units
74
.. i18n: ============ ======== ===============
75
.. i18n: Product Code Quantity Unit of Measure
76
.. i18n: ============ ======== ===============
77
.. i18n: BOIS002 0.17 m2
78
.. i18n: ============ ======== ===============
81
.. table:: Bill of Materials for 2 PANLAT Units
83
============ ======== ===============
84
Product Code Quantity Unit of Measure
85
============ ======== ===============
87
============ ======== ===============
89
.. i18n: The PANLAT is made from an order using the workflow shown. The BOIS02 is purchased on order and the
90
.. i18n: other products are all found in stock. An order for the product ARM100 will then generate two
91
.. i18n: production orders (ARM100 and PANLAT) then produce two purchase orders for the product BOIS02.
92
.. i18n: Product BOIS02 is used in the production of both ARM100 and PANLAT. Set the lead times on the
93
.. i18n: product forms to the following:
96
The PANLAT is made from an order using the workflow shown. The BOIS02 is purchased on order and the
97
other products are all found in stock. An order for the product ARM100 will then generate two
98
production orders (ARM100 and PANLAT) then produce two purchase orders for the product BOIS02.
99
Product BOIS02 is used in the production of both ARM100 and PANLAT. Set the lead times on the
100
product forms to the following:
102
.. i18n: .. table:: Lead Times
104
.. i18n: ============ ================== ==================== ==================
105
.. i18n: Product Code Customer Lead Time Production Lead Time Supplier Lead Time
106
.. i18n: ============ ================== ==================== ==================
107
.. i18n: ARM100 30 days 5 days
108
.. i18n: PANLAT 10 days
109
.. i18n: BOIS02 5 days
110
.. i18n: ============ ================== ==================== ==================
113
.. table:: Lead Times
115
============ ================== ==================== ==================
116
Product Code Customer Lead Time Production Lead Time Supplier Lead Time
117
============ ================== ==================== ==================
118
ARM100 30 days 5 days
121
============ ================== ==================== ==================
123
.. i18n: A customer order placed on the 1st January will set up the following operations and lead times:
126
A customer order placed on the 1st January will set up the following operations and lead times:
128
.. i18n: * Delivery ARM100: 31 January (=1st January + 30 days),
130
.. i18n: * Manufacture ARM100: 26 January (=31 January – 5 days),
132
.. i18n: * Manufacture PANLAT: 16 January (=26 January – 10 days),
134
.. i18n: * Purchase BOIS02 (for ARM100): 21 January (=26 January – 5 days),
136
.. i18n: * Purchase BOIS02 (for PANLAT): 11 January (=16 January – 5 days).
139
* Delivery ARM100: 31 January (=1st January + 30 days),
141
* Manufacture ARM100: 26 January (=31 January – 5 days),
143
* Manufacture PANLAT: 16 January (=26 January – 10 days),
145
* Purchase BOIS02 (for ARM100): 21 January (=26 January – 5 days),
147
* Purchase BOIS02 (for PANLAT): 11 January (=16 January – 5 days).
149
.. i18n: In this example, OpenERP will propose placing two orders with the supplier of product BOIS002. Each of
150
.. i18n: these orders can be for a different planned date. Before confirming these orders the
151
.. i18n: purchasing manager could group these orders into single order.
154
In this example, OpenERP will propose placing two orders with the supplier of product BOIS002. Each of
155
these orders can be for a different planned date. Before confirming these orders the
156
purchasing manager could group these orders into single order.
158
.. i18n: Security days
159
.. i18n: -------------
165
.. i18n: The scheduler will plan all operations as a function of the time configured on the products. But it
166
.. i18n: is also possible to configure these factors in the company. These factors are then global to the
167
.. i18n: company, whatever the product concerned. In the description of the company, on the
168
.. i18n: :guilabel:`Configuration` tab, you find the following parameters:
171
The scheduler will plan all operations as a function of the time configured on the products. But it
172
is also possible to configure these factors in the company. These factors are then global to the
173
company, whatever the product concerned. In the description of the company, on the
174
:guilabel:`Configuration` tab, you find the following parameters:
176
.. i18n: * Security days: number of days to deduct from a system order to cope with any problems of
177
.. i18n: procurement,
179
.. i18n: * Purchase lead time: additional days to include for all purchase orders with this supplier,
181
.. i18n: * Production lead time: number of additional days needed for manufacturing.
183
.. i18n: * Period for calculating requirements: all the requests which are for procuring for a later date to
184
.. i18n: the number of days which aren't calculated in the scheduler.
187
* Security days: number of days to deduct from a system order to cope with any problems of
190
* Purchase lead time: additional days to include for all purchase orders with this supplier,
192
* Production lead time: number of additional days needed for manufacturing.
194
* Period for calculating requirements: all the requests which are for procuring for a later date to
195
the number of days which aren't calculated in the scheduler.
197
.. i18n: .. note:: Purchasing lead time
199
.. i18n: The security delay for purchases is the average time between the order generated by OpenERP and
200
.. i18n: the real purchase time from the supplier by your purchasing department.
201
.. i18n: This delay takes account of the order process in your company, including order negotiation time.
204
.. note:: Purchasing lead time
206
The security delay for purchases is the average time between the order generated by OpenERP and
207
the real purchase time from the supplier by your purchasing department.
208
This delay takes account of the order process in your company, including order negotiation time.
210
.. i18n: Take for example the following configuration:
213
Take for example the following configuration:
215
.. i18n: * Security days: 2,
217
.. i18n: * Purchase Lead time: 3,
219
.. i18n: * Production Lead Time: 1.
224
* Purchase Lead time: 3,
226
* Production Lead Time: 1.
228
.. i18n: The example above will then be given the following lead times:
231
The example above will then be given the following lead times:
233
.. i18n: * Delivery ARM100: 29 January (=1st January + 30 days – 2 days),
235
.. i18n: * Manufacture ARM100: 23 January (=29 January – 5 days – 1 day),
237
.. i18n: * Manufacture PANLAT: 12 January (=26 January – 10 days – 1 day),
239
.. i18n: * Purchase BOIS02 (for ARM100): 15 January (=26 January – 5 days – 3 days),
241
.. i18n: * Purchase BOIS02 (for PANLAT): 4 January (=12 January – 5 days – 3 days).
244
* Delivery ARM100: 29 January (=1st January + 30 days – 2 days),
246
* Manufacture ARM100: 23 January (=29 January – 5 days – 1 day),
248
* Manufacture PANLAT: 12 January (=26 January – 10 days – 1 day),
250
* Purchase BOIS02 (for ARM100): 15 January (=26 January – 5 days – 3 days),
252
* Purchase BOIS02 (for PANLAT): 4 January (=12 January – 5 days – 3 days).
254
.. i18n: .. index:: work orders
257
.. index:: work orders
266
.. i18n: In the first part of this chapter, manufacturing management was handled in terms of products and
267
.. i18n: materials. This section focuses on manufacturing operations. To manufacture or assemble products, as
268
.. i18n: well as using raw materials and finished product you must also handle operations such as assembly,
269
.. i18n: drilling wood, and cutting timber.
272
In the first part of this chapter, manufacturing management was handled in terms of products and
273
materials. This section focuses on manufacturing operations. To manufacture or assemble products, as
274
well as using raw materials and finished product you must also handle operations such as assembly,
275
drilling wood, and cutting timber.
277
.. i18n: The different operations will have different impacts on the costs of manufacture and planning depending
278
.. i18n: on the available workload.
281
The different operations will have different impacts on the costs of manufacture and planning depending
282
on the available workload.
284
.. i18n: Definition of concepts
285
.. i18n: ----------------------
288
Definition of concepts
289
----------------------
291
.. i18n: To manage operations you should understand the following concepts
294
To manage operations you should understand the following concepts
296
.. i18n: * Workcenters,
300
.. i18n: * Operations.
310
.. i18n: single: workcenter
323
.. i18n: Workcenters represent units of product, capable of doing material transformation operations. You can
324
.. i18n: distinguish three types of workcenter: machines, tools and human resources.
327
Workcenters represent units of product, capable of doing material transformation operations. You can
328
distinguish three types of workcenter: machines, tools and human resources.
330
.. i18n: .. note:: Workcenter
332
.. i18n: Workcenters are units of manufacture consisting of one or several people and/or machines
333
.. i18n: that can be considered as a unit for the purposes of forecasting capacity and planning.
338
Workcenters are units of manufacture consisting of one or several people and/or machines
339
that can be considered as a unit for the purposes of forecasting capacity and planning.
341
.. i18n: Use the menu :menuselection:`Manufacturing --> Configuration --> Workcenters` to define a new
342
.. i18n: workcenter. You get a form as shown in the figure :ref:`fig-mrpwkc`.
345
Use the menu :menuselection:`Manufacturing --> Configuration --> Workcenters` to define a new
346
workcenter. You get a form as shown in the figure :ref:`fig-mrpwkc`.
348
.. i18n: .. _fig-mrpwkc:
350
.. i18n: .. figure:: images/mrp_workcenter.png
352
.. i18n: :align: center
354
.. i18n: *Definition of a workcenter*
359
.. figure:: images/mrp_workcenter.png
363
*Definition of a workcenter*
365
.. i18n: A workcenter must have a name and a code. You then assign a type: machine, human resource, tool, and
366
.. i18n: a description of operating hours or functionality. The figure :ref:`fig-mrpwkcwh` represents the hours from Monday
367
.. i18n: to Friday, from 09:00 to 17:00 with a break of an hour from 12:00.
370
A workcenter must have a name and a code. You then assign a type: machine, human resource, tool, and
371
a description of operating hours or functionality. The figure :ref:`fig-mrpwkcwh` represents the hours from Monday
372
to Friday, from 09:00 to 17:00 with a break of an hour from 12:00.
374
.. i18n: .. _fig-mrpwkcwh:
376
.. i18n: .. figure:: images/mrp_workcenter_working_hour.png
378
.. i18n: :align: center
380
.. i18n: *Working hours for a workcenter*
385
.. figure:: images/mrp_workcenter_working_hour.png
389
*Working hours for a workcenter*
391
.. i18n: You should show a description of the workcenter and its operations.
394
You should show a description of the workcenter and its operations.
396
.. i18n: Once the database is encoded you should enter data about the production capacity of the workcenter.
397
.. i18n: Depending on whether you have a machine or a person, a workcenter will be defined in cycles or
398
.. i18n: hours. If it represents a set of machines and people you can use both cycles and hours at the same
402
Once the database is encoded you should enter data about the production capacity of the workcenter.
403
Depending on whether you have a machine or a person, a workcenter will be defined in cycles or
404
hours. If it represents a set of machines and people you can use both cycles and hours at the same
408
.. i18n: single: workcenter, cycle
412
single: workcenter, cycle
414
.. i18n: .. note:: A Cycle
416
.. i18n: A cycle corresponds to the time required to carry out an assembly operation.
417
.. i18n: The user is free to determine which is the reference operation for a given workcenter.
418
.. i18n: It must be represented by the cost and elapsed time of manufacture.
420
.. i18n: For example, for a printing workcenter, a cycle will be the printing of 1 page or of 1000 pages
421
.. i18n: depending on the printer.
426
A cycle corresponds to the time required to carry out an assembly operation.
427
The user is free to determine which is the reference operation for a given workcenter.
428
It must be represented by the cost and elapsed time of manufacture.
430
For example, for a printing workcenter, a cycle will be the printing of 1 page or of 1000 pages
431
depending on the printer.
433
.. i18n: To define the capacity properly it is necessary know, for each workcenter, what will be the
434
.. i18n: reference operation which determines the cycle. You can then define the data relative
435
.. i18n: to the capacity.
438
To define the capacity properly it is necessary know, for each workcenter, what will be the
439
reference operation which determines the cycle. You can then define the data relative
442
.. i18n: Capacity per cycle (CA): determine the number of operations that can be done in parallel during a
443
.. i18n: cycle. Generally the number defines the number of identical machines or people defined by the
447
Capacity per cycle (CA): determine the number of operations that can be done in parallel during a
448
cycle. Generally the number defines the number of identical machines or people defined by the
451
.. i18n: Time for a cycle (TC): give the duration in hour for that or the operations defined by a cycle.
454
Time for a cycle (TC): give the duration in hour for that or the operations defined by a cycle.
456
.. i18n: Time before production (TS): give the wait in hours to initialise production operations. Generally
457
.. i18n: this represents the machine setup time.
460
Time before production (TS): give the wait in hours to initialise production operations. Generally
461
this represents the machine setup time.
463
.. i18n: Time after production (TN): give the delay in hours after the end of a production operation.
464
.. i18n: Generally this represents the cleaning time necessary after an operation.
467
Time after production (TN): give the delay in hours after the end of a production operation.
468
Generally this represents the cleaning time necessary after an operation.
470
.. i18n: Effective time (ET): is a factor that is applied to the three times above to determine the real
471
.. i18n: production time. This factor enables you to readjust the different times progressively and as a
472
.. i18n: measure of machine utilization. You can't readjust the other times because generally they're taken
473
.. i18n: from the machine's data sheet.
476
Effective time (ET): is a factor that is applied to the three times above to determine the real
477
production time. This factor enables you to readjust the different times progressively and as a
478
measure of machine utilization. You can't readjust the other times because generally they're taken
479
from the machine's data sheet.
481
.. i18n: The total time for carrying out X operations is then given by the following formula: ((C / CA) * TC
482
.. i18n: + TS + TN\_ * ET. In this formula the result of the division is rounded upwards. Then if the
483
.. i18n: capacity per cycle is 6 it takes 3 cycles to realize 15 operations.
486
The total time for carrying out X operations is then given by the following formula: ((C / CA) * TC
487
+ TS + TN\_ * ET. In this formula the result of the division is rounded upwards. Then if the
488
capacity per cycle is 6 it takes 3 cycles to realize 15 operations.
490
.. i18n: .. tip:: Multi-level routing
492
.. i18n: It is possible to define routing on several levels to support multi-level bills of materials.
493
.. i18n: You can select the routing on each level of a bill of materials.
494
.. i18n: The levels are then linked to hierarchies of bills of materials.
497
.. tip:: Multi-level routing
499
It is possible to define routing on several levels to support multi-level bills of materials.
500
You can select the routing on each level of a bill of materials.
501
The levels are then linked to hierarchies of bills of materials.
503
.. i18n: The second tab of the production order lets you define the links to analytical account to report the
504
.. i18n: costs of the workcenter operations. If you leave the different fields empty OpenERP won't have any
505
.. i18n: effect on the analytic accounts.
508
The second tab of the production order lets you define the links to analytical account to report the
509
costs of the workcenter operations. If you leave the different fields empty OpenERP won't have any
510
effect on the analytic accounts.
512
.. i18n: .. figure:: images/mrp_workcenter_tab.png
514
.. i18n: :align: center
516
.. i18n: *Data about analytic accounts for a workcenter*
519
.. figure:: images/mrp_workcenter_tab.png
523
*Data about analytic accounts for a workcenter*
526
.. i18n: pair: routing; manufacturing
530
pair: routing; manufacturing
533
.. i18n: single: routing
546
.. i18n: Routings define the assembly operations to be done in workcenters for manufacturing a certain
547
.. i18n: product. They are usually attached to bills of materials which will define the assembly of products
548
.. i18n: required for manufacture or for finished products.
551
Routings define the assembly operations to be done in workcenters for manufacturing a certain
552
product. They are usually attached to bills of materials which will define the assembly of products
553
required for manufacture or for finished products.
555
.. i18n: A routing can be defined directly in a bill of materials or through the menu
556
.. i18n: :menuselection:`Manufacturing --> Configuration --> Routings`. A routing has a name, a code and a
557
.. i18n: description. Later in this chapter you'll see that a routing can also be associated with a stock
558
.. i18n: location. That enable you to indicate where assembly takes place.
561
A routing can be defined directly in a bill of materials or through the menu
562
:menuselection:`Manufacturing --> Configuration --> Routings`. A routing has a name, a code and a
563
description. Later in this chapter you'll see that a routing can also be associated with a stock
564
location. That enable you to indicate where assembly takes place.
566
.. i18n: .. figure:: images/mrp_routing.png
568
.. i18n: :align: center
570
.. i18n: *Definition of a routing with three operations*
573
.. figure:: images/mrp_routing.png
577
*Definition of a routing with three operations*
579
.. i18n: .. note:: Subcontracting assembly
581
.. i18n: You'll see further on in this chapter that it is possible to link a routing and a stock location
582
.. i18n: for the customer or the supplier.
583
.. i18n: You do this after you've subcontracted the assembly of a product to a supplier, for example.
586
.. note:: Subcontracting assembly
588
You'll see further on in this chapter that it is possible to link a routing and a stock location
589
for the customer or the supplier.
590
You do this after you've subcontracted the assembly of a product to a supplier, for example.
592
.. i18n: In the routing you must show the list of operations that must be done. Each operation must be done
593
.. i18n: at a workcenter and possess a number of hours and/or cycles be done.
596
In the routing you must show the list of operations that must be done. Each operation must be done
597
at a workcenter and possess a number of hours and/or cycles be done.
599
.. i18n: Impact on the production order
600
.. i18n: ------------------------------
603
Impact on the production order
604
------------------------------
606
.. i18n: The routings are then attached to the bills of materials which are then also used to generate
607
.. i18n: product order. On a production order you'll find assembly operations for manufacture on the
608
.. i18n: :guilabel:`Operations` tab.
611
The routings are then attached to the bills of materials which are then also used to generate
612
product order. On a production order you'll find assembly operations for manufacture on the
613
:guilabel:`Operations` tab.
615
.. i18n: .. figure:: images/mrp_production_workorder.png
617
.. i18n: :align: center
619
.. i18n: *Operations on a production order*
622
.. figure:: images/mrp_production_workorder.png
626
*Operations on a production order*
628
.. i18n: The times and the cycles shown in the production order are, in the same way as the materials,
629
.. i18n: theoretical data. The user can change the values to reflect reality for manufacture.
632
The times and the cycles shown in the production order are, in the same way as the materials,
633
theoretical data. The user can change the values to reflect reality for manufacture.
635
.. i18n: So if you use routings, OpenERP automatically calculates the operations required for the production
636
.. i18n: order. If the workcenters are linked to analytic accounts, at the end of production, Open Erp will
637
.. i18n: generate the analytic accounts representing the costs of manufacture. This will allow you to work
638
.. i18n: out profitability per workcenter or manufacturing unit through analytic accounting.
641
So if you use routings, OpenERP automatically calculates the operations required for the production
642
order. If the workcenters are linked to analytic accounts, at the end of production, Open Erp will
643
generate the analytic accounts representing the costs of manufacture. This will allow you to work
644
out profitability per workcenter or manufacturing unit through analytic accounting.
646
.. i18n: But the routings also enable you to manage your production capacity. You will be able to leave the
647
.. i18n: demand charts for the days / weeks / months ahead to validate that you don't forecast more than you
648
.. i18n: are capable of producing.
651
But the routings also enable you to manage your production capacity. You will be able to leave the
652
demand charts for the days / weeks / months ahead to validate that you don't forecast more than you
653
are capable of producing.
655
.. i18n: To see a demand chart, list the workcenters using the menu :menuselection:`Manufacturing -->
656
.. i18n: Configuration --> Workcenters`. Then select one or several workcenters and click on the action
657
.. i18n: :guilabel:`Workcenter load`. OpenERP then asks you if you work in cycles or in hours and your
658
.. i18n: interval is calculated (by day, week or month).
661
To see a demand chart, list the workcenters using the menu :menuselection:`Manufacturing -->
662
Configuration --> Workcenters`. Then select one or several workcenters and click on the action
663
:guilabel:`Workcenter load`. OpenERP then asks you if you work in cycles or in hours and your
664
interval is calculated (by day, week or month).
666
.. i18n: .. figure:: images/mrp_workcenter_load.png
668
.. i18n: :align: center
670
.. i18n: *Charge by workcenter*
673
.. figure:: images/mrp_workcenter_load.png
677
*Charge by workcenter*
679
.. i18n: .. tip:: Theoretical times
681
.. i18n: Once the routings have been clearly defined, you determine the effective working time per
682
.. i18n: assembly worker.
683
.. i18n: This is the time actually taken by the assembly worker for each operation.
684
.. i18n: That enables you to compare the real working time in your company and work out the productivity
688
.. tip:: Theoretical times
690
Once the routings have been clearly defined, you determine the effective working time per
692
This is the time actually taken by the assembly worker for each operation.
693
That enables you to compare the real working time in your company and work out the productivity
697
.. i18n: single: work operations
701
single: work operations
703
.. i18n: Work operations
704
.. i18n: ---------------
710
.. i18n: A production order defines the use of the products defined in the Bills of Materials, and the
711
.. i18n: operations defined in the routing. You've seen how to handle manufacturing production as a top-level process,
712
.. i18n: but some companies prefer to have finer-grained control of operations where instead of
713
.. i18n: specifying just the production process itself, they enter data on each constituent production operation.
716
A production order defines the use of the products defined in the Bills of Materials, and the
717
operations defined in the routing. You've seen how to handle manufacturing production as a top-level process,
718
but some companies prefer to have finer-grained control of operations where instead of
719
specifying just the production process itself, they enter data on each constituent production operation.
721
.. i18n: Management of operations
722
.. i18n: ------------------------
725
Management of operations
726
------------------------
728
.. i18n: .. note:: Operations
730
.. i18n: Operations are often called work orders.
735
Operations are often called work orders.
738
.. i18n: single: module; mrp_operations
742
single: module; mrp_operations
744
.. i18n: To work using work orders you must install the optional module :mod:`mrp_operations`. Once the module
745
.. i18n: is installed you'll find a new menu called :menuselection:`Manufacturing --> Operations -->
746
.. i18n: Operations` to be carried out. The assembly workers must then encode each step operation by
747
.. i18n: operation and, for each step, the real working time for it.
750
To work using work orders you must install the optional module :mod:`mrp_operations`. Once the module
751
is installed you'll find a new menu called :menuselection:`Manufacturing --> Operations -->
752
Operations` to be carried out. The assembly workers must then encode each step operation by
753
operation and, for each step, the real working time for it.
755
.. i18n: .. figure:: images/mrp_operations_tree.png
757
.. i18n: :align: center
759
.. i18n: *List of operations to be carried out.*
762
.. figure:: images/mrp_operations_tree.png
766
*List of operations to be carried out.*
768
.. i18n: Operations must then be carried out one by one. On each operation the operator can click on
769
.. i18n: :guilabel:`Start operation` and then :guilabel:`Close Operation`. The time is then worked out
770
.. i18n: automatically on the operation between the two changes of status. The operator can also put the
771
.. i18n: operation on hold and start again later.
774
Operations must then be carried out one by one. On each operation the operator can click on
775
:guilabel:`Start operation` and then :guilabel:`Close Operation`. The time is then worked out
776
automatically on the operation between the two changes of status. The operator can also put the
777
operation on hold and start again later.
779
.. i18n: The following process is attached to each operation.
782
The following process is attached to each operation.
784
.. i18n: .. figure:: images/mrp_operations_workflow.png
786
.. i18n: :align: center
788
.. i18n: *Process for handling an operation*
791
.. figure:: images/mrp_operations_workflow.png
795
*Process for handling an operation*
797
.. i18n: Thanks to this use by operation, the real working time is recorded on the production order.
800
Thanks to this use by operation, the real working time is recorded on the production order.
802
.. i18n: The production order is automatically put into the state 'Running' once the first operation has been
803
.. i18n: started. That consumes some raw materials. Similarly the production order is closed automatically
804
.. i18n: once the last operation is completed. The finished products are then made.
807
The production order is automatically put into the state 'Running' once the first operation has been
808
started. That consumes some raw materials. Similarly the production order is closed automatically
809
once the last operation is completed. The finished products are then made.
811
.. i18n: .. index:: barcode
816
.. i18n: Events and barcodes
817
.. i18n: ===================
823
.. i18n: If the company wants to work with barcodes in manufacturing you can work on each operation using
824
.. i18n: events. Here are some examples of events for an operations:
827
If the company wants to work with barcodes in manufacturing you can work on each operation using
828
events. Here are some examples of events for an operations:
830
.. i18n: * Starting an operation,
832
.. i18n: * Pausing an operation,
834
.. i18n: * Restarting an operation,
836
.. i18n: * Closing an operation,
838
.. i18n: * Cancelling an operation.
841
* Starting an operation,
843
* Pausing an operation,
845
* Restarting an operation,
847
* Closing an operation,
849
* Cancelling an operation.
851
.. i18n: You place barcodes on the production orders on the machines or operators and a form of barcodes
852
.. i18n: representing the events. To print barcodes select the events using the menu
853
.. i18n: :menuselection:`Manufacturing --> Configuration --> Codes from start to finish`. Then click for
854
.. i18n: printing the barcodes for the selected events. You can do the same for printing barcodes for the
855
.. i18n: workcenters using the menu :menuselection:`Manufacturing --> Configuration --> Workcenters`.
858
You place barcodes on the production orders on the machines or operators and a form of barcodes
859
representing the events. To print barcodes select the events using the menu
860
:menuselection:`Manufacturing --> Configuration --> Codes from start to finish`. Then click for
861
printing the barcodes for the selected events. You can do the same for printing barcodes for the
862
workcenters using the menu :menuselection:`Manufacturing --> Configuration --> Workcenters`.
864
.. i18n: Using the system these operations don't need data to be entered on the keyboard. To use these
865
.. i18n: barcodes, open the menu :menuselection:`Manufacturing --> Barcode events`. You must then scan, in
869
Using the system these operations don't need data to be entered on the keyboard. To use these
870
barcodes, open the menu :menuselection:`Manufacturing --> Barcode events`. You must then scan, in
873
.. i18n: #. The barcode of the production order,
875
.. i18n: #. The workcenter used,
877
.. i18n: #. The event code.
880
#. The barcode of the production order,
882
#. The workcenter used,
886
.. i18n: .. figure:: images/mrp_operation.png
888
.. i18n: :align: center
890
.. i18n: *Capturing events for work orders*
893
.. figure:: images/mrp_operation.png
897
*Capturing events for work orders*
899
.. i18n: OpenERP then applies the events to the relevant operation.
902
OpenERP then applies the events to the relevant operation.
904
.. i18n: Subcontracting manufacture
905
.. i18n: --------------------------
908
Subcontracting manufacture
909
--------------------------
911
.. i18n: In OpenERP it is possible to subcontract production operations (for example painting and item
912
.. i18n: assembly) at a supplier's. To do this you must indicate on the relevant routing document a supplier
913
.. i18n: location for stock management.
916
In OpenERP it is possible to subcontract production operations (for example painting and item
917
assembly) at a supplier's. To do this you must indicate on the relevant routing document a supplier
918
location for stock management.
920
.. i18n: You must then configure a location dedicated to this supplier with the following data:
923
You must then configure a location dedicated to this supplier with the following data:
925
.. i18n: * :guilabel:`Type of location` : Supplier,
927
.. i18n: * :guilabel:`Address of Location` : Select an address of the subcontractor partner,
929
.. i18n: * :guilabel:`Type of linkage` : Fixed,
931
.. i18n: * :guilabel:`Location of linkage` : your Stock,
933
.. i18n: * :guilabel:`Lead time for linkage` : number of days before receipt of the finished product.
936
* :guilabel:`Type of location` : Supplier,
938
* :guilabel:`Address of Location` : Select an address of the subcontractor partner,
940
* :guilabel:`Type of linkage` : Fixed,
942
* :guilabel:`Location of linkage` : your Stock,
944
* :guilabel:`Lead time for linkage` : number of days before receipt of the finished product.
946
.. i18n: Then once the manufacture has been planned for the product in question, OpenERP will generate the
947
.. i18n: following steps:
950
Then once the manufacture has been planned for the product in question, OpenERP will generate the
953
.. i18n: Delivery of raw materials to the stores for the supplier,
956
Delivery of raw materials to the stores for the supplier,
958
.. i18n: Production order for the products at the suppliers and receipt of the finished products in the
962
Production order for the products at the suppliers and receipt of the finished products in the
965
.. i18n: Once the production order has been confirmed, OpenERP automatically generates a delivery order to
966
.. i18n: send to the raw materials supplier. The storesperson can access this delivery order using the menu
967
.. i18n: :menuselection:`Stock Management --> Incoming Products`. The raw materials will then be placed in
968
.. i18n: stock at the supplier's stores.
971
Once the production order has been confirmed, OpenERP automatically generates a delivery order to
972
send to the raw materials supplier. The storesperson can access this delivery order using the menu
973
:menuselection:`Stock Management --> Incoming Products`. The raw materials will then be placed in
974
stock at the supplier's stores.
976
.. i18n: Once the delivery of raw materials has been confirmed, OpenERP activates the production order. The
977
.. i18n: supplier uses the raw materials sent to produce the finished goods which will automatically be put
978
.. i18n: in your own stores. The confirmation of this manufacture is made when you receive the products from
979
.. i18n: your supplier. It's then that you indicate the quantities consumed by your supplier
982
Once the delivery of raw materials has been confirmed, OpenERP activates the production order. The
983
supplier uses the raw materials sent to produce the finished goods which will automatically be put
984
in your own stores. The confirmation of this manufacture is made when you receive the products from
985
your supplier. It's then that you indicate the quantities consumed by your supplier
987
.. i18n: .. tip:: Subcontract without routing
989
.. i18n: If you don't use routing you can always subcontract work orders by creating an empty routing in
990
.. i18n: the subcontract bill of materials.
993
.. tip:: Subcontract without routing
995
If you don't use routing you can always subcontract work orders by creating an empty routing in
996
the subcontract bill of materials.
998
.. i18n: Production orders are found in the menu :menuselection:`Manufacture --> Production Orders -->
999
.. i18n: Production Orders to start`. A production order is always carried out in two stages:
1002
Production orders are found in the menu :menuselection:`Manufacture --> Production Orders -->
1003
Production Orders to start`. A production order is always carried out in two stages:
1005
.. i18n: #. Consumption of raw materials.
1007
.. i18n: #. Production of finished products.
1010
#. Consumption of raw materials.
1012
#. Production of finished products.
1014
.. i18n: Depending on the company's needs, you can specify that the first step is confirmed at the
1015
.. i18n: acknowledgment of manufacturing supplier and the second at the receipt of finished goods in the
1019
Depending on the company's needs, you can specify that the first step is confirmed at the
1020
acknowledgment of manufacturing supplier and the second at the receipt of finished goods in the
1023
.. i18n: Treatment of exceptions
1024
.. i18n: =======================
1027
Treatment of exceptions
1028
=======================
1030
.. i18n: The set of stock requirements is generated by procurement orders. Then for each customer order line
1031
.. i18n: or raw materials in a manufacturing order, you will find a procurement form. To review all the
1032
.. i18n: procurement orders use the menu :menuselection:`Manufacturing --> Procurement orders`.
1035
The set of stock requirements is generated by procurement orders. Then for each customer order line
1036
or raw materials in a manufacturing order, you will find a procurement form. To review all the
1037
procurement orders use the menu :menuselection:`Manufacturing --> Procurement orders`.
1039
.. i18n: In normal system use, you don't need to worry about procurement orders because they're automatically
1040
.. i18n: generated by OpenERP and the user will usually work on the results of a procurement: a production
1041
.. i18n: order, a task or a supplier order.
1044
In normal system use, you don't need to worry about procurement orders because they're automatically
1045
generated by OpenERP and the user will usually work on the results of a procurement: a production
1046
order, a task or a supplier order.
1048
.. i18n: But if there are configuration problems, the system can remain blocked by a procurement without
1049
.. i18n: generating a corresponding document. For example, suppose that you configure a product :guilabel:`Procure Method`
1050
.. i18n: as ``Make to Order`` but you haven't defined the bill of materials. In that case procurement of the
1051
.. i18n: product will stay blocked in an exception state ``No Bill of Materials defined for this product``. You
1052
.. i18n: must then create a bill of materials to unblock the problem.
1055
But if there are configuration problems, the system can remain blocked by a procurement without
1056
generating a corresponding document. For example, suppose that you configure a product :guilabel:`Procure Method`
1057
as ``Make to Order`` but you haven't defined the bill of materials. In that case procurement of the
1058
product will stay blocked in an exception state ``No Bill of Materials defined for this product``. You
1059
must then create a bill of materials to unblock the problem.
1061
.. i18n: Possible problems include:
1064
Possible problems include:
1066
.. i18n: * No bill of materials defined for production: in this case you've got to create one or indicate
1067
.. i18n: that the product can be purchased instead.
1069
.. i18n: * No supplier available for a purchase: it's then necessary to define a supplier in the second tab
1070
.. i18n: of the product form.
1072
.. i18n: * No address defined on the supplier partner: you must complete an address for the supplier by
1073
.. i18n: default for the product in consideration.
1075
.. i18n: * No quantity available in stock: you must create a rule for automatically procuring (for example a
1076
.. i18n: minimum stock rule) and put it in the order, or manually procure it.
1079
* No bill of materials defined for production: in this case you've got to create one or indicate
1080
that the product can be purchased instead.
1082
* No supplier available for a purchase: it's then necessary to define a supplier in the second tab
1083
of the product form.
1085
* No address defined on the supplier partner: you must complete an address for the supplier by
1086
default for the product in consideration.
1088
* No quantity available in stock: you must create a rule for automatically procuring (for example a
1089
minimum stock rule) and put it in the order, or manually procure it.
1091
.. i18n: Some problems are just those of timing and can be automatically corrected by the system. That's why
1092
.. i18n: OpenERP has the two following menus:
1095
Some problems are just those of timing and can be automatically corrected by the system. That's why
1096
OpenERP has the two following menus:
1098
.. i18n: * :menuselection:`Manufacturing --> Automatic Procurement --> Procurement Exceptions --> Exceptions
1099
.. i18n: to correct`,
1101
.. i18n: * :menuselection:`Manufacturing --> Automatic Procurement --> Procurement Exceptions --> Temporary
1102
.. i18n: exceptions`.
1105
* :menuselection:`Manufacturing --> Automatic Procurement --> Procurement Exceptions --> Exceptions
1108
* :menuselection:`Manufacturing --> Automatic Procurement --> Procurement Exceptions --> Temporary
1111
.. i18n: If a product must be 'in stock' but is not available in your stores, OpenERP will make the
1112
.. i18n: exception in 'temporary' or 'to be corrected'. The exception is temporary if the system can procure
1113
.. i18n: it automatically, for example if a procurement rule is defined for minimum stock.
1116
If a product must be 'in stock' but is not available in your stores, OpenERP will make the
1117
exception in 'temporary' or 'to be corrected'. The exception is temporary if the system can procure
1118
it automatically, for example if a procurement rule is defined for minimum stock.
1120
.. i18n: .. figure:: images/mrp_exception.png
1122
.. i18n: :align: center
1124
.. i18n: *Example of a procurement in exception*
1127
.. figure:: images/mrp_exception.png
1131
*Example of a procurement in exception*
1133
.. i18n: If no procurement rule is defined the exception must be corrected manually by the user. Once the
1134
.. i18n: exception is corrected you can restart by clicking on :guilabel:`Retry`. If you don't do that then
1135
.. i18n: OpenERP will automatically recalculate on the next automated requirements calculation.
1138
If no procurement rule is defined the exception must be corrected manually by the user. Once the
1139
exception is corrected you can restart by clicking on :guilabel:`Retry`. If you don't do that then
1140
OpenERP will automatically recalculate on the next automated requirements calculation.
1142
.. i18n: Manual procurement
1143
.. i18n: ==================
1149
.. i18n: To procure internally, you can create a procurement order manually. Use the menu
1150
.. i18n: :menuselection:`Manufacturing --> Procurement Orders --> New Procurement` to do this.
1153
To procure internally, you can create a procurement order manually. Use the menu
1154
:menuselection:`Manufacturing --> Procurement Orders --> New Procurement` to do this.
1156
.. i18n: .. figure:: images/mrp_procurement.png
1158
.. i18n: :align: center
1160
.. i18n: *Encoding for a new procurement order*
1163
.. figure:: images/mrp_procurement.png
1167
*Encoding for a new procurement order*
1169
.. i18n: The procurement order will then be responsible for calculating a proposal for automatic procurement
1170
.. i18n: for the product concerned. This procurement wll start a task, a purchase order form the supplier or
1171
.. i18n: a production depending on the product configuration.
1174
The procurement order will then be responsible for calculating a proposal for automatic procurement
1175
for the product concerned. This procurement wll start a task, a purchase order form the supplier or
1176
a production depending on the product configuration.
1178
.. i18n: .. figure:: images/mrp_procurement_flow.png
1180
.. i18n: :align: center
1182
.. i18n: *Workflow for handling a procurement, a function of the product configuration*
1185
.. figure:: images/mrp_procurement_flow.png
1189
*Workflow for handling a procurement, a function of the product configuration*
1191
.. i18n: It is better to encode a procurement order rather than direct purchasing or production, That method
1192
.. i18n: has the following advantages:
1195
It is better to encode a procurement order rather than direct purchasing or production, That method
1196
has the following advantages:
1198
.. i18n: The form is simpler because OpenERP calculates the different values from other values and defined
1199
.. i18n: rules: purchase date calculated from order date, default supplier, raw materials needs, selection of
1200
.. i18n: the most suitable bill of materials, etc
1203
The form is simpler because OpenERP calculates the different values from other values and defined
1204
rules: purchase date calculated from order date, default supplier, raw materials needs, selection of
1205
the most suitable bill of materials, etc
1207
.. i18n: The calculation of requirements prioritises the procurements. If you encode a purchase directly you
1208
.. i18n: short-circuit the planning of different procurements.
1211
The calculation of requirements prioritises the procurements. If you encode a purchase directly you
1212
short-circuit the planning of different procurements.
1214
.. i18n: .. tip:: Shortcuts
1216
.. i18n: On the product form you have an :guilabel:`ACTIONS` shortcut button :guilabel:`Create Procurements`
1217
.. i18n: that lets you quickly create a new procurement order.
1222
On the product form you have an :guilabel:`ACTIONS` shortcut button :guilabel:`Create Procurements`
1223
that lets you quickly create a new procurement order.
1225
.. i18n: .. index:: waste products
1228
.. index:: waste products
1230
.. i18n: Management of waste products and secondary products
1231
.. i18n: ===================================================
1234
Management of waste products and secondary products
1235
===================================================
1238
.. i18n: single: module; mrp_subproduct
1242
single: module; mrp_subproduct
1244
.. i18n: For the management of waste you must install the module :mod:`mrp_subproduct`. The normal behaviour of
1245
.. i18n: manufacture in OpenERP enables you to manufacture several units of the same finished product from
1246
.. i18n: raw materials (A + B > C). With waste management, the result of a manufacture can be to have both
1247
.. i18n: finished products and secondary products (A + B > C + D).
1250
For the management of waste you must install the module :mod:`mrp_subproduct`. The normal behaviour of
1251
manufacture in OpenERP enables you to manufacture several units of the same finished product from
1252
raw materials (A + B > C). With waste management, the result of a manufacture can be to have both
1253
finished products and secondary products (A + B > C + D).
1255
.. i18n: .. note:: Waste material
1257
.. i18n: In OpenERP waste material corresponds to secondary products that are a by-product of the main
1258
.. i18n: manufacturing process.
1259
.. i18n: For example, cutting planks of timber will produce other planks but these bits of timber are too
1261
.. i18n: (or the offcuts may have value for the company if they can be used elsewhere).
1264
.. note:: Waste material
1266
In OpenERP waste material corresponds to secondary products that are a by-product of the main
1267
manufacturing process.
1268
For example, cutting planks of timber will produce other planks but these bits of timber are too
1270
(or the offcuts may have value for the company if they can be used elsewhere).
1272
.. i18n: If the module :mod:`mrp_subproduct` has been installed you get a new field in the Bill of Material that
1273
.. i18n: lets you set secondary products resulting from the manufacture of the finished product.
1276
If the module :mod:`mrp_subproduct` has been installed you get a new field in the Bill of Material that
1277
lets you set secondary products resulting from the manufacture of the finished product.
1279
.. i18n: .. figure:: images/mrp_bom_subproduct.png
1281
.. i18n: :align: center
1283
.. i18n: *Definition of waste products in a bill of materials*
1286
.. figure:: images/mrp_bom_subproduct.png
1290
*Definition of waste products in a bill of materials*
1292
.. i18n: When OpenERP generates a production order based on a bill of materials that uses secondary product
1293
.. i18n: you pick up the list of all products in the the third tab of the production order 'Finished
1297
When OpenERP generates a production order based on a bill of materials that uses secondary product
1298
you pick up the list of all products in the the third tab of the production order 'Finished
1301
.. i18n: .. figure:: images/mrp_production.png
1303
.. i18n: :align: center
1305
.. i18n: *A production order producing several finished products*
1308
.. figure:: images/mrp_production.png
1312
*A production order producing several finished products*
1314
.. i18n: Secondary products enable you to generate several types of products from the same raw materials and
1315
.. i18n: manufacturing methods – only these aren't used in the calculation of requirements. Then if you
1316
.. i18n: need the secondary products OpenERP won't ask you to manufacture another product to use the waste
1317
.. i18n: products and secondary products of this manufacture. In this case you should enter another
1318
.. i18n: production order for the secondary product.
1321
Secondary products enable you to generate several types of products from the same raw materials and
1322
manufacturing methods – only these aren't used in the calculation of requirements. Then if you
1323
need the secondary products OpenERP won't ask you to manufacture another product to use the waste
1324
products and secondary products of this manufacture. In this case you should enter another
1325
production order for the secondary product.
1327
.. i18n: .. note:: Services in Manufacturing
1329
.. i18n: Unlike most software for production management, OpenERP manages services as well as stockable
1331
.. i18n: So it's possible to put products of type :guilabel:`Service` in a bill of materials.
1332
.. i18n: These don't appear in the production order but their requirements will be taken into account.
1334
.. i18n: If they're defined as :guilabel:`Make to Order` OpenERP will generate a task for the manufacture or a
1335
.. i18n: subcontract order for the operations.
1336
.. i18n: The behaviour will depend on the supply method configured on the product form :guilabel:`Buy` or :guilabel:`Produce`.
1339
.. note:: Services in Manufacturing
1341
Unlike most software for production management, OpenERP manages services as well as stockable
1343
So it's possible to put products of type :guilabel:`Service` in a bill of materials.
1344
These don't appear in the production order but their requirements will be taken into account.
1346
If they're defined as :guilabel:`Make to Order` OpenERP will generate a task for the manufacture or a
1347
subcontract order for the operations.
1348
The behaviour will depend on the supply method configured on the product form :guilabel:`Buy` or :guilabel:`Produce`.
1350
.. i18n: .. index:: repairs
1355
.. i18n: Management of repairs
1356
.. i18n: =====================
1359
Management of repairs
1360
=====================
1363
.. i18n: single: module; mrp_repair
1367
single: module; mrp_repair
1369
.. i18n: The management of repairs is carried out using the module :mod:`mrp_repair`. Once it's installed this
1370
.. i18n: module adds new :menuselection:`Manufacturing --> Repairs` menus under the Manufacturing menu for
1371
.. i18n: creating repair jobs and reviewing repairs in progress.
1374
The management of repairs is carried out using the module :mod:`mrp_repair`. Once it's installed this
1375
module adds new :menuselection:`Manufacturing --> Repairs` menus under the Manufacturing menu for
1376
creating repair jobs and reviewing repairs in progress.
1378
.. i18n: In OpenERP a repair will have the following effects:
1381
In OpenERP a repair will have the following effects:
1383
.. i18n: * Use of materials: items for replacement,
1385
.. i18n: * Production of products: items replaced from reserved stock,
1387
.. i18n: * Quality control: tracking the reasons for repair,
1389
.. i18n: * Accounting entries: following stock moves,
1391
.. i18n: * Receipt and delivery of product from and to the end user,
1393
.. i18n: * Adding operations that can be seen in the product's traceability,
1395
.. i18n: * Invoicing items used and/or free for repairs.
1398
* Use of materials: items for replacement,
1400
* Production of products: items replaced from reserved stock,
1402
* Quality control: tracking the reasons for repair,
1404
* Accounting entries: following stock moves,
1406
* Receipt and delivery of product from and to the end user,
1408
* Adding operations that can be seen in the product's traceability,
1410
* Invoicing items used and/or free for repairs.
1412
.. i18n: Entering data for a new repair
1413
.. i18n: ------------------------------
1416
Entering data for a new repair
1417
------------------------------
1419
.. i18n: Use the menu :menuselection:`Manufacturing --> Repairs --> New Repair` to enter a new repair into
1420
.. i18n: the system. You'll see a blank form for the repair data, as shown in the figure :ref:`fig-mrprepnew` below.
1423
Use the menu :menuselection:`Manufacturing --> Repairs --> New Repair` to enter a new repair into
1424
the system. You'll see a blank form for the repair data, as shown in the figure :ref:`fig-mrprepnew` below.
1426
.. i18n: .. _fig-mrprepnew:
1428
.. i18n: .. figure:: images/mrp_repair_new.png
1430
.. i18n: :align: center
1432
.. i18n: *Entering data for a new repair*
1437
.. figure:: images/mrp_repair_new.png
1441
*Entering data for a new repair*
1443
.. i18n: Start by identifying the product that will be repaired using the product lot number. OpenERP then
1444
.. i18n: automatically completes fields from the selected lot – the partner fields, address, delivery
1445
.. i18n: location, and stock move.
1448
Start by identifying the product that will be repaired using the product lot number. OpenERP then
1449
automatically completes fields from the selected lot – the partner fields, address, delivery
1450
location, and stock move.
1452
.. i18n: If a warranty period has been defined in the product description, in months, OpenERP then completes
1453
.. i18n: the field :guilabel:`Warranty limit` with the correct warranty date.
1456
If a warranty period has been defined in the product description, in months, OpenERP then completes
1457
the field :guilabel:`Warranty limit` with the correct warranty date.
1459
.. i18n: You must then specify the components that you'll be adding, replacing or removing in the operations
1460
.. i18n: part. On each line you must specify the following:
1463
You must then specify the components that you'll be adding, replacing or removing in the operations
1464
part. On each line you must specify the following:
1466
.. i18n: Add or remove a component of the finished product:
1469
Add or remove a component of the finished product:
1471
.. i18n: * Product Component,
1473
.. i18n: * Quantity,
1475
.. i18n: * Unit of Measure
1477
.. i18n: * Price of Component,
1479
.. i18n: * Possible lot number,
1481
.. i18n: * Location where the component was found,
1483
.. i18n: * To invoice or not.
1486
* Product Component,
1492
* Price of Component,
1494
* Possible lot number,
1496
* Location where the component was found,
1498
* To invoice or not.
1500
.. i18n: Once the component has been selected, OpenERP automatically completes most of the fields:
1503
Once the component has been selected, OpenERP automatically completes most of the fields:
1505
.. i18n: * :guilabel:`Quantity` : 1,
1507
.. i18n: * :guilabel:`Unit of Measure` : unit for managing stock defined in the product form,
1509
.. i18n: * :guilabel:`Component Price` : calculated from the customer list price,
1511
.. i18n: * :guilabel:`Source location` : given by the stock management,
1513
.. i18n: * :guilabel:`To invoice or not` : depends on the actual date and the guarantee period.
1516
* :guilabel:`Quantity` : 1,
1518
* :guilabel:`Unit of Measure` : unit for managing stock defined in the product form,
1520
* :guilabel:`Component Price` : calculated from the customer list price,
1522
* :guilabel:`Source location` : given by the stock management,
1524
* :guilabel:`To invoice or not` : depends on the actual date and the guarantee period.
1526
.. i18n: This information is automatically proposed by the system but you can modify it all yourself.
1529
This information is automatically proposed by the system but you can modify it all yourself.
1531
.. i18n: You can also encode additional charges in the second tab of the repair - applicable list price,
1532
.. i18n: address and type of invoice, as well as additional line items that need to be added to the repair
1536
You can also encode additional charges in the second tab of the repair - applicable list price,
1537
address and type of invoice, as well as additional line items that need to be added to the repair
1540
.. i18n: .. figure:: images/mrp_repair_tab2.png
1542
.. i18n: :align: center
1544
.. i18n: *Repair form, second tab*
1547
.. figure:: images/mrp_repair_tab2.png
1551
*Repair form, second tab*
1553
.. i18n: The third tab, Quality, is for encoding information about the quality: internal notes, notes for the
1554
.. i18n: quotation, corrective actions and preventative actions for example.
1557
The third tab, Quality, is for encoding information about the quality: internal notes, notes for the
1558
quotation, corrective actions and preventative actions for example.
1560
.. i18n: Repair workflow
1561
.. i18n: ---------------
1567
.. i18n: A defined process handles a repair order – both the repair itself and invoicing the client. The
1568
.. i18n: figure :ref:`fig-mrprepflow` shows this repair process.
1571
A defined process handles a repair order – both the repair itself and invoicing the client. The
1572
figure :ref:`fig-mrprepflow` shows this repair process.
1574
.. i18n: .. _fig-mrprepflow:
1576
.. i18n: .. figure:: images/mrp_repair_workflow.png
1578
.. i18n: :align: center
1580
.. i18n: *Process for handling a repair*
1585
.. figure:: images/mrp_repair_workflow.png
1589
*Process for handling a repair*
1591
.. i18n: Once a repair has been entered onto the system, it is in the 'draft' state. In this state it has no
1592
.. i18n: impact on the rest of the system. You can print a quotation from it using the action 'Print
1593
.. i18n: Quotation'. The repair quotation can then be sent to the customer.
1596
Once a repair has been entered onto the system, it is in the 'draft' state. In this state it has no
1597
impact on the rest of the system. You can print a quotation from it using the action 'Print
1598
Quotation'. The repair quotation can then be sent to the customer.
1600
.. i18n: Once the customer approves the repair, use the menu :menuselection:`Manufacturing --> Repairs -->
1601
.. i18n: Repairs in quotation` to find the draft repair. Click to confirm the draft repair and put it into
1602
.. i18n: the running state. You can specify the invoicing mode in the second tab:
1605
Once the customer approves the repair, use the menu :menuselection:`Manufacturing --> Repairs -->
1606
Repairs in quotation` to find the draft repair. Click to confirm the draft repair and put it into
1607
the running state. You can specify the invoicing mode in the second tab:
1609
.. i18n: * no invoicing,
1611
.. i18n: * invoicing before repair,
1613
.. i18n: * invoicing after repair.
1618
* invoicing before repair,
1620
* invoicing after repair.
1622
.. i18n: You can confirm the repair operation or create an invoice for the customer depending on this state.
1625
You can confirm the repair operation or create an invoice for the customer depending on this state.
1628
.. i18n: pair: invoicing; repair
1632
pair: invoicing; repair
1634
.. i18n: Invoicing the repair
1635
.. i18n: --------------------
1638
Invoicing the repair
1639
--------------------
1641
.. i18n: When the repair is to be invoiced, an invoice is generated in the draft state by the system. This
1642
.. i18n: invoice contains the raw materials used (replaced components) and any other costs such as the time
1643
.. i18n: used for the repair. These other costs are entered on the second tab of the repair form.
1646
When the repair is to be invoiced, an invoice is generated in the draft state by the system. This
1647
invoice contains the raw materials used (replaced components) and any other costs such as the time
1648
used for the repair. These other costs are entered on the second tab of the repair form.
1650
.. i18n: If the product to be repaired is still under guarantee, OpenERP automatically suggests that the
1651
.. i18n: components themselves are not invoiced, but will still use any other defined costs. You can override
1652
.. i18n: any of these default values when you're entering the data.
1655
If the product to be repaired is still under guarantee, OpenERP automatically suggests that the
1656
components themselves are not invoiced, but will still use any other defined costs. You can override
1657
any of these default values when you're entering the data.
1659
.. i18n: The link to the generated invoice is shown on the second tab of the repair document.
1662
The link to the generated invoice is shown on the second tab of the repair document.
1664
.. i18n: Stock movements and repair
1665
.. i18n: --------------------------
1668
Stock movements and repair
1669
--------------------------
1671
.. i18n: When the repair has been carried out, OpenERP automatically carries out stock movements for
1672
.. i18n: components that have been removed, added or replaced on the finished product.
1675
When the repair has been carried out, OpenERP automatically carries out stock movements for
1676
components that have been removed, added or replaced on the finished product.
1678
.. i18n: The move operations are carried out using the locations shown on the first tab of the repair
1679
.. i18n: document. If a destination location has been specified, OpenERP automatically handles the final
1680
.. i18n: customer delivery order when the repair has been completed. This also lets you manage the delivery
1681
.. i18n: of the repaired products.
1684
The move operations are carried out using the locations shown on the first tab of the repair
1685
document. If a destination location has been specified, OpenERP automatically handles the final
1686
customer delivery order when the repair has been completed. This also lets you manage the delivery
1687
of the repaired products.
1689
.. i18n: For example, take the case of the cabinet that was produced at the start of this chapter. If you
1690
.. i18n: have to replace the shelf PANLAT, you must enter data for the repair as shown in figure :ref:`fig-mrpreppan`.
1693
For example, take the case of the cabinet that was produced at the start of this chapter. If you
1694
have to replace the shelf PANLAT, you must enter data for the repair as shown in figure :ref:`fig-mrpreppan`.
1696
.. i18n: .. _fig-mrpreppan:
1698
.. i18n: .. figure:: images/mrp_repair_panlat.png
1700
.. i18n: :align: center
1702
.. i18n: *Repair of a shelf in a cabinet*
1707
.. figure:: images/mrp_repair_panlat.png
1711
*Repair of a shelf in a cabinet*
1713
.. i18n: In this example, you'd carry out the following operations:
1716
In this example, you'd carry out the following operations:
1718
.. i18n: * Removal of a PANLAT shelf in the cabinet and put the faulty shelf in the location *Defective Products*,
1720
.. i18n: * Placement of a new PANLAT shelf that has been taken from stock.
1723
* Removal of a PANLAT shelf in the cabinet and put the faulty shelf in the location *Defective Products*,
1725
* Placement of a new PANLAT shelf that has been taken from stock.
1727
.. i18n: When the repair is ready to be confirmed, OpenERP will generate the following stock moves:
1730
When the repair is ready to be confirmed, OpenERP will generate the following stock moves:
1732
.. i18n: * Put faulty PANLAT into suitable stock location *Default Production > Defective Products*,
1734
.. i18n: * Consume PANLAT: *Stock > Default production*.
1737
* Put faulty PANLAT into suitable stock location *Default Production > Defective Products*,
1739
* Consume PANLAT: *Stock > Default production*.
1741
.. i18n: If you analyze the traceability of this lot number you'll see all the repair operations in the
1742
.. i18n: upstream and downstream traceability lists of the products concerned.
1745
If you analyze the traceability of this lot number you'll see all the repair operations in the
1746
upstream and downstream traceability lists of the products concerned.
1748
.. i18n: .. Copyright © Open Object Press. All rights reserved.
1751
.. Copyright © Open Object Press. All rights reserved.
1753
.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
1754
.. i18n: .. change the content. You can also print a copy to be read by yourself only.
1757
.. You may take electronic copy of this publication and distribute it if you don't
1758
.. change the content. You can also print a copy to be read by yourself only.
1760
.. i18n: .. We have contracts with different publishers in different countries to sell and
1761
.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
1762
.. i18n: .. in bookstores. This helps to distribute and promote the OpenERP product. It
1763
.. i18n: .. also helps us to create incentives to pay contributors and authors using author
1764
.. i18n: .. rights of these sales.
1767
.. We have contracts with different publishers in different countries to sell and
1768
.. distribute paper or electronic based versions of this book (translated or not)
1769
.. in bookstores. This helps to distribute and promote the OpenERP product. It
1770
.. also helps us to create incentives to pay contributors and authors using author
1771
.. rights of these sales.
1773
.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
1774
.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
1775
.. i18n: .. written authorisation for this.
1778
.. Due to this, grants to translate, modify or sell this book are strictly
1779
.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
1780
.. written authorisation for this.
1782
.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
1783
.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
1784
.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
1785
.. i18n: .. printed in initial capitals.
1788
.. Many of the designations used by manufacturers and suppliers to distinguish their
1789
.. products are claimed as trademarks. Where those designations appear in this book,
1790
.. and Open Object Press was aware of a trademark claim, the designations have been
1791
.. printed in initial capitals.
1793
.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
1794
.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
1795
.. i18n: .. resulting from the use of the information contained herein.
1798
.. While every precaution has been taken in the preparation of this book, the publisher
1799
.. and the authors assume no responsibility for errors or omissions, or for damages
1800
.. resulting from the use of the information contained herein.
1802
.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
1805
.. Published by Open Object Press, Grand Rosière, Belgium