diff --git a/inventory/management/delivery.rst b/inventory/management/delivery.rst index 63129bdea..d05923eec 100644 --- a/inventory/management/delivery.rst +++ b/inventory/management/delivery.rst @@ -10,7 +10,6 @@ Delivery Orders delivery/one_step delivery/two_steps delivery/three_steps - delivery/scheduled_dates delivery/dropshipping delivery/label_type delivery/packaging_type diff --git a/inventory/management/delivery/media/scheduled_dates01.png b/inventory/management/delivery/media/scheduled_dates01.png deleted file mode 100644 index f1d974d15..000000000 Binary files a/inventory/management/delivery/media/scheduled_dates01.png and /dev/null differ diff --git a/inventory/management/delivery/media/scheduled_dates02.png b/inventory/management/delivery/media/scheduled_dates02.png deleted file mode 100644 index 7943db835..000000000 Binary files a/inventory/management/delivery/media/scheduled_dates02.png and /dev/null differ diff --git a/inventory/management/delivery/media/scheduled_dates03.png b/inventory/management/delivery/media/scheduled_dates03.png deleted file mode 100644 index 8fb289364..000000000 Binary files a/inventory/management/delivery/media/scheduled_dates03.png and /dev/null differ diff --git a/inventory/management/delivery/media/scheduled_dates04.png b/inventory/management/delivery/media/scheduled_dates04.png deleted file mode 100644 index 0d4c0fcba..000000000 Binary files a/inventory/management/delivery/media/scheduled_dates04.png and /dev/null differ diff --git a/inventory/management/delivery/media/scheduled_dates05.png b/inventory/management/delivery/media/scheduled_dates05.png deleted file mode 100644 index 8858a8edc..000000000 Binary files a/inventory/management/delivery/media/scheduled_dates05.png and /dev/null differ diff --git a/inventory/management/delivery/media/scheduled_dates06.png b/inventory/management/delivery/media/scheduled_dates06.png deleted file mode 100644 index 520a7d87a..000000000 Binary files a/inventory/management/delivery/media/scheduled_dates06.png and /dev/null differ diff --git a/inventory/management/delivery/media/scheduled_dates07.png b/inventory/management/delivery/media/scheduled_dates07.png deleted file mode 100644 index e0cc8cda6..000000000 Binary files a/inventory/management/delivery/media/scheduled_dates07.png and /dev/null differ diff --git a/inventory/management/delivery/scheduled_dates.rst b/inventory/management/delivery/scheduled_dates.rst deleted file mode 100644 index 438a98114..000000000 --- a/inventory/management/delivery/scheduled_dates.rst +++ /dev/null @@ -1,154 +0,0 @@ -============================================ -How is the scheduled delivery date computed? -============================================ - -Scheduled dates are computed in order to be able to plan deliveries, -receptions and so on. Depending on the habits of your company Odoo -automatically generates scheduled dates via the scheduler. The Odoo -scheduler computes everything per line, whether it's a manufacturing -order, a delivery order, a sale order, etc. The dates that are computed -are dependent on the different leads times configured in Odoo. - -Configuring lead times -====================== - -Configuring **lead times** is a first essential move in order to compute -scheduled dates. Lead times are the delays (in term of delivery, -manufacturing, ...) promised to your different partners and/or clients. - -Configuration of the different lead times are made as follows: - -At a product level ------------------- - -- **Supplier lead time**: - -Is the time needed for the supplier to deliver your purchased product. -To configure the supplier lead time select a product, and go in the -**Inventory** tab. You will have to add a vendor to your product in order -to select a supplier lead time. - -.. image:: media/scheduled_dates05.png - :align: center - -.. tip:: - Do not forget that it is possible to add different vendors and thus - different delivery lead times depending on the vendor. - -Once a vendor is selected, just open its form and fill its **Delivery lead -time**. In this case security days have no influence, the scheduled -delivery days will be equal to: **Date** of the purchase order + **Delivery -Lead Time**. - -.. image:: media/scheduled_dates02.png - :align: center - -- **Customer lead time**: - -Customer lead time is the time needed to get your product from your -store / warehouse to your customer. It can be configured for any -product. Simply select a product, go into the sales tab and indicate -your **Customer lead time**. - -.. image:: media/scheduled_dates01.png - :align: center - -- **Manufacturing lead time**: - -At the same page it is possible to configure the **Manufacturing Lead -Time** as well. Manufacturing lead time is the time needed to -manufacture the product. - -.. tip:: - Don't forget to tick the manufacturing box in inventory if you - want to create manufacturing routes. - -At the company level --------------------- - -At company level, it is possible to configure **security days** in order -to cope with eventual delays and to be sure to meet your engagements. -The idea is to subtract **backup** days from the **computed scheduled date** -in case of delays. - -- **Sales Safety days**: - -Sales safety days are **back-up** days to ensure you will be able to -deliver your clients engagements in times. They are margins of errors -for delivery lead times. Security days are the same logic as the early -wristwatch, in order to arrive on time. The idea is to subtract the -numbers of security days from the calculation and thus to compute a -scheduled date earlier than the one you promised to your client. In that -way you are sure to be able to keep your commitment. - -To set up your security dates, go to :menuselection:`Settings --> General settings` and -click on **Configure your company data**. - -.. image:: media/scheduled_dates04.png - :align: center - -Once the menu is open, go in the configuration tab and indicate the -number of safety days. - -- **Purchase Safety days**: - -Purchase days follow to the same logic than sales security days. - -They are margins of error for vendor lead times. When the system -generates purchase orders for procuring products, they will be scheduled -that many days earlier to cope with unexpected vendor delays. Purchase -lead time can be found in the same menu as the sales safety days - -.. image:: media/scheduled_dates03.png - :align: center - -.. tip:: - Note that you can also configure a default - Manufacturing lead time from here. - -At route level --------------- - -The internal transfers that a product might do due to the movement of -stocks can also influence the computed date. - -The delays due to internal transfers can be specified in the **inventory** -app when creating a new push rule in a route. - -Go to the push rules section on a route form to set a delay. - -.. image:: media/scheduled_dates06.png - :align: center - -At sale order level: --------------------- - -- **Requested date**: - -Odoo offers the possibility to select a requested date by the client by -indicating the date in the other information tab of the sales order. -If this date is earlier than the theoreticaly computed date odoo will -automatically display a warning. - -.. image:: media/scheduled_dates07.png - :align: center - -Example -======= - -As an example, you may sell a car today (January 1st), that is purchased -on order, and you promise to deliver your customer within 20 days -(January 20). In such a scenario, the scheduler may trigger the -following events, based on your configuration: - -- January 19: actual scheduled delivery (1 day of Sales Safety days) - -- January 18: receive the product from your supplier (1 day of Purchase - days) - -- January 10: deadline to order at your supplier (9 days of supplier - delivery lead time) - -- January 8: trigger a purchase request to your purchase team, since - the team need on average 2 days to find the right supplier and - order. diff --git a/inventory/management/planning.rst b/inventory/management/planning.rst index 43fbfab62..d480d85d5 100644 --- a/inventory/management/planning.rst +++ b/inventory/management/planning.rst @@ -6,5 +6,5 @@ Planning :titlesonly: :glob: - planning/scheduled_date + planning/scheduled_dates planning/schedulers diff --git a/inventory/management/planning/media/scheduled_date_01.png b/inventory/management/planning/media/scheduled_date_01.png deleted file mode 100644 index 31f719922..000000000 Binary files a/inventory/management/planning/media/scheduled_date_01.png and /dev/null differ diff --git a/inventory/management/planning/media/scheduled_date_02.png b/inventory/management/planning/media/scheduled_date_02.png deleted file mode 100644 index 83ab9e25f..000000000 Binary files a/inventory/management/planning/media/scheduled_date_02.png and /dev/null differ diff --git a/inventory/management/planning/media/scheduled_date_03.png b/inventory/management/planning/media/scheduled_date_03.png deleted file mode 100644 index de47d2b92..000000000 Binary files a/inventory/management/planning/media/scheduled_date_03.png and /dev/null differ diff --git a/inventory/management/planning/media/scheduled_date_04.png b/inventory/management/planning/media/scheduled_date_04.png deleted file mode 100644 index bed24bdcf..000000000 Binary files a/inventory/management/planning/media/scheduled_date_04.png and /dev/null differ diff --git a/inventory/management/planning/media/scheduled_date_05.png b/inventory/management/planning/media/scheduled_date_05.png deleted file mode 100644 index 5664f7716..000000000 Binary files a/inventory/management/planning/media/scheduled_date_05.png and /dev/null differ diff --git a/inventory/management/planning/media/scheduled_date_06.png b/inventory/management/planning/media/scheduled_date_06.png deleted file mode 100644 index 4780d3d59..000000000 Binary files a/inventory/management/planning/media/scheduled_date_06.png and /dev/null differ diff --git a/inventory/management/planning/media/scheduled_date_07.png b/inventory/management/planning/media/scheduled_date_07.png deleted file mode 100644 index 98330e83f..000000000 Binary files a/inventory/management/planning/media/scheduled_date_07.png and /dev/null differ diff --git a/inventory/management/planning/media/scheduled_date_08.png b/inventory/management/planning/media/scheduled_date_08.png deleted file mode 100644 index f87031388..000000000 Binary files a/inventory/management/planning/media/scheduled_date_08.png and /dev/null differ diff --git a/inventory/management/planning/media/scheduled_date_09.png b/inventory/management/planning/media/scheduled_date_09.png deleted file mode 100644 index 4b2cb6217..000000000 Binary files a/inventory/management/planning/media/scheduled_date_09.png and /dev/null differ diff --git a/inventory/management/planning/media/scheduled_dates_01.png b/inventory/management/planning/media/scheduled_dates_01.png new file mode 100644 index 000000000..34a90f515 Binary files /dev/null and b/inventory/management/planning/media/scheduled_dates_01.png differ diff --git a/inventory/management/planning/media/scheduled_dates_02.png b/inventory/management/planning/media/scheduled_dates_02.png new file mode 100644 index 000000000..29976c8b5 Binary files /dev/null and b/inventory/management/planning/media/scheduled_dates_02.png differ diff --git a/inventory/management/planning/media/scheduled_dates_03.png b/inventory/management/planning/media/scheduled_dates_03.png new file mode 100644 index 000000000..3ee2885b5 Binary files /dev/null and b/inventory/management/planning/media/scheduled_dates_03.png differ diff --git a/inventory/management/planning/media/scheduled_dates_04.png b/inventory/management/planning/media/scheduled_dates_04.png new file mode 100644 index 000000000..c13ddc003 Binary files /dev/null and b/inventory/management/planning/media/scheduled_dates_04.png differ diff --git a/inventory/management/planning/media/scheduled_dates_05.png b/inventory/management/planning/media/scheduled_dates_05.png new file mode 100644 index 000000000..188fe036c Binary files /dev/null and b/inventory/management/planning/media/scheduled_dates_05.png differ diff --git a/inventory/management/planning/media/scheduled_dates_06.png b/inventory/management/planning/media/scheduled_dates_06.png new file mode 100644 index 000000000..2456d64d1 Binary files /dev/null and b/inventory/management/planning/media/scheduled_dates_06.png differ diff --git a/inventory/management/planning/media/scheduled_dates_07.png b/inventory/management/planning/media/scheduled_dates_07.png new file mode 100644 index 000000000..78c880081 Binary files /dev/null and b/inventory/management/planning/media/scheduled_dates_07.png differ diff --git a/inventory/management/planning/media/scheduled_dates_08.png b/inventory/management/planning/media/scheduled_dates_08.png new file mode 100644 index 000000000..18cb90170 Binary files /dev/null and b/inventory/management/planning/media/scheduled_dates_08.png differ diff --git a/inventory/management/planning/media/scheduled_dates_09.png b/inventory/management/planning/media/scheduled_dates_09.png new file mode 100644 index 000000000..02663ac38 Binary files /dev/null and b/inventory/management/planning/media/scheduled_dates_09.png differ diff --git a/inventory/management/planning/media/scheduled_dates_10.png b/inventory/management/planning/media/scheduled_dates_10.png new file mode 100644 index 000000000..bb70626ab Binary files /dev/null and b/inventory/management/planning/media/scheduled_dates_10.png differ diff --git a/inventory/management/planning/scheduled_date.rst b/inventory/management/planning/scheduled_date.rst deleted file mode 100644 index 3d6618c06..000000000 --- a/inventory/management/planning/scheduled_date.rst +++ /dev/null @@ -1,187 +0,0 @@ -============================================ -How is the Scheduled Delivery Date Computed? -============================================ - -In most cases, scheduled dates are computed to be able to plan -deliveries, receptions, and so on. Depending on your company’s habits, -Odoo generates scheduled dates via the scheduler. - -To make your life easier, the Odoo scheduler computes everything per -line, whether it’s a manufacturing order, a delivery order, a sale -order, etc. - -.. note:: - The computed dates are dependent on the different lead times configured - in Odoo. - -Configuring lead times -====================== - -Configuring lead times is the first move if you want to compute -scheduled dates. Those are the delays promised (in terms of delivery, -manufacturing, etc.) to your partners and/or clients. - -.. note:: - In Odoo, you can configure different lead times. - -At a product level ------------------- - -When configuring lead times at the product level, you have three -different types to take into account: supplier lead time, customer lead -time, and manufacturing lead time. - -Supplier lead time -~~~~~~~~~~~~~~~~~~ - -The supplier lead time is the time needed for the supplier to deliver -your purchased products. To configure it, select a product and click on -the inventory tab. There, you will have to add a vendor to your product. - -.. image:: media/scheduled_date_01.png - :align: center - -Now, just open the vendor form and fill its *Delivery lead time*. In -this case, the delivery day will be equal to *Date of the Purchase -Order + Delivery Lead Time*. - -.. image:: media/scheduled_date_02.png - :align: center - -.. tip:: - Do not forget that it is possible to add different vendor pricelists - and, thus, different delivery lead times, depending on the vendor. - -Customer Lead Time -~~~~~~~~~~~~~~~~~~ - -It is the time needed to get your product from your store/warehouse to -your customer. It can be configured for any product. To add it, select a -product and go to the inventory tab. There, simply indicate your -*customer lead time*. - -.. image:: media/scheduled_date_03.png - :align: center - -Manufacturing lead time -~~~~~~~~~~~~~~~~~~~~~~~ - -On the same page, it is possible to configure what’s called the -*Manufacturing Lead Time*. It is the time needed to manufacture the -product. - -At the company level --------------------- - -At the company level, you can configure security days. Those are useful -to cope with eventual dalys and to be sure to meet your engagements. The -idea is to subtract backup days from the computed scheduled date in case -of delays. - -Once again, there are three different types of security lead times: for -sales, for purchases, and for manufacturing. - -Security lead time for sales -~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -In sales, security lead time corresponds to backup days to ensure you -will be able to deliver your clients in times. They are margins of -errors for delivery lead times. Security days are the same logic as the -early wristwatch, in order to arrive on time. - -The idea is to subtract the numbers of security days from the -calculation and, thus, to compute a scheduled date earlier than the one -you promised to your client. In that way, you are sure to be able to -keep your commitment. - -To set up your security dates, go to :menuselection:`Inventory --> Configuration --> -Settings` and enable the feature. - -.. image:: media/scheduled_date_04.png - :align: center - -Security lead time for purchase -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -It follows the same logic as security lead time for sales except that -security lead time for purchase is the margin of error for vendor lead -times, not for sales. - -When the system generates purchase orders for procuring products, they -will be scheduled that many days earlier to cope with unexpected vendor -delays. - -To find purchase lead time, go to :menuselection:`Inventory --> Configuration --> -Settings` and enable the feature. - -.. image:: media/scheduled_date_05.png - :align: center - -Security lead time for manufacturing -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -The security lead time for manufacturing allows generating manufacturing -orders which are scheduled that many days earlier to cope with -unexpected manufacturing days. - -To configure it, go to :menuselection:`Manufacturing --> Configuration --> Settings` and -enable the *Security Lead Time* option. Then, hit save. - -.. image:: media/scheduled_date_06.png - :align: center - -At route level --------------- - -Sometimes, the internal transfers that a product might do may also -influence the computed date. The delays due to internal transfers can be -specified in the *Inventory* app when you create a new rule in a -route. - -To specify them, go to :menuselection:`Inventory --> Configuration --> Routes` and add a -push rule to set a delay. Of course, you need to activate *Multi-step -Routes* to use this feature. - -.. image:: media/scheduled_date_07.png - :align: center - -At the sale order level ------------------------ - -Expected date -~~~~~~~~~~~~~ - -In the *Sales* application, you have the possibility to activate the -option *Delivery Date*. It will allow you to see additional fields on -the sale order. - -By enabling this option, Odoo will indicate the *Expected Date* in the -*Other Info* tab of the sales order. This one is automatically -computed based on the different lead times. - -.. image:: media/scheduled_date_08.png - :align: center - -If you set a *Commitment Date* to deliver your customer that is -earlier than the *Expected Date*, a warning message will appear on the -screen. - -.. image:: media/scheduled_date_09.png - :align: center - -Example -~~~~~~~ - -To better understand all the above info, here is an example. You may -sell a car today (January 1st), that is purchased on order, and you -promise to deliver your customer within 20 days (January 20th). In such -a scenario, the scheduler will trigger the following events, based on -your configuration: - -- January 19: this is the actual scheduled delivery (1 day of Sales Safety Days); - -- January 18: you receive the product from your supplier (1 day of Purchase days); - -- January 10: this is the deadline to order at your supplier (9 days of Supplier Delivery Lead Time); - -- January 8: trigger a purchase request to your purchase team, since they need, on average, 2 days to find the right supplier and order. \ No newline at end of file diff --git a/inventory/management/planning/scheduled_dates.rst b/inventory/management/planning/scheduled_dates.rst new file mode 100644 index 000000000..7f9489396 --- /dev/null +++ b/inventory/management/planning/scheduled_dates.rst @@ -0,0 +1,260 @@ +=========================================== +How is the Scheduled Delivery Date Computed +=========================================== + +Providing the best possible service to customers is vital for business. It implies planning +every move: manufacturing orders, deliveries, receptions, and so on. To do so, you need to +configure lead time properly and coordinate scheduled dates. + +By using lead times, Odoo provides end dates, the **Commitment +Date**, for each process. On a sales order, for example, this is the +date your customer will get the products he ordered. + +From the customers’ side, the commitment date is important because it +gives them an estimation of when they will receive their products. The +dates take all other lead times, such as manufacturing, delivery, or +suppliers, into account. + +How are Lead Times Calculated? +============================== + +.. image:: media/scheduled_dates_01.png + :align: center + :alt: Visual representation of various lead times such as customer lead time or delivery LT + +As said above, there are several types of lead times. Each is calculated +based on various indicators. Before going through the configuration, +here is a brief summary of how lead times are calculated and what they +are: + +- **Customer Lead Time**: the customer lead time is the default + duration you set. Therefore, the expected date on the sales + orders is today + customer lead time. + +- **Sales Security Lead Time**: the purpose is to be ready shipping + that many days before the actual commitment taken with the + customer. Then, the default scheduled date on the delivery order + is **SO delivery date - Security Lead Time**. + +- **Purchase Security Lead Time**: additional time to mitigate the risk + of a vendor delay. The receipt will be scheduled that many days + earlier to cope with unexpected vendor delays. In case of a + *Replenish to Order*, the **Delivery order scheduled date - + Security lead time** for purchase will be the default + *Receipt* scheduled date. + +- **Purchase Delivery Lead Time**: this is the expected time between a + PO being confirmed and the receipt of the ordered products. The + **Receipt scheduled date - Vendor delivery date** is the + default *PO Order By* date. + +- **Days to Purchase**: number of days the purchasing department takes + to validate a PO. If another RFQ to the same vendor is already + opened, Odoo adds the line to the RFQ instead of creating a new + one. Then, the specific date is set on the line. + +- **Manufacturing Lead Time**: this is the expected time it takes to + manufacture a product. This lead time is independent of the + quantity to produce and does not take the routing time into + account. + +- **Manufacturing Security Lead Time**: additional time to mitigate the + risk of a manufacturing delay. In case of a *Replenish to + Order*, the **Delivery Order scheduled date - Manufacturing + Lead Time - Manufacturing Security Lead Time** is the default + *Manufacturing Order* planned date. + +Sales - Lead Times +================== + +In the *Sales* app, there is an option called *Delivery Date*. It +allows seeing an additional field on the sales orders, *Expected +Date*. This one is automatically computed based on the different lead +times previously configured. + +.. image:: media/scheduled_dates_02.png + :align: center + :alt: View of the delivery settings to have the delivery lead time taken into account + +If the set up *Delivery Date* is earlier than the the *Expected +Date*, a warning message is displayed. + +.. image:: media/scheduled_dates_03.png + :align: center + :alt: View of the error that occurs when trying to choose an earlier date than what calculated + by Odoo + +But, for all of this properly working, it is still necessary to +configure all the lead times that could occur. + +Customer Lead Time +------------------ + +The *Customer Lead Time* is the time needed for your product to go +from your warehouse to the customer place. It can be configured on any +product by going to :menuselection:`Sales --> Products --> Products`. +There, open your product form, go in the inventory tab, and add your +*Customer Lead Time*. + +.. image:: media/scheduled_dates_04.png + :align: center + :alt: View of the customer lead time configuration from the product form + +For example, product B is ordered on the 2nd of April but the *Customer +Lead Time* is two days. In that case, the expected delivery date is the +4th of April. + +Security Lead Time +------------------ + +In sales, *Security Lead Time* corresponds to backup days to ensure +you are able to deliver the products in time. The purpose is to be ready +shipping earlier in order to arrive on time. + +The number of security days is subtracted from the calculation to +compute a scheduled date earlier than the one promised to the customer. + +To set this up, go to :menuselection:`Inventory --> Configuration --> +Settings` and enable the feature *Security Lead Time for Sales*. + +.. image:: media/scheduled_dates_05.png + :align: center + :alt: View of the security lead time for sales configuration from the sales settings + +For example, product B is scheduled to be delivered on the 6th of April +but the *Security Lead Time* is one day. In that case, the scheduled +date for the delivery order is the 5th of April. + +Deliver several products +------------------------ + +In many cases, customers order several products at the same time. Those +can have different lead times but still need to be delivered, at once or +separately. Fortunately, Odoo can help you handle these cases easily. + +From the *Other Info* tab of your *Sale Order*, you can choose +between *When all products are ready* and *As soon as possible*. The +first one is to deliver products at once, while the second is to deliver +them separately. + +For example, products A and B are ordered at the same time. A has 8 lead +days and B has 5. With the first option, the *Expected Date* is +calculated based on the product with the most lead days, here A. If the +order is confirmed on the 2nd of April, then the *Expected Date* is on +the 10th of April. + +With the second option, the *Expected Date* is calculated based on the +product with the least customer lead days. In this example, B is the +product with the least lead days. So, the *Expected Date* is on the +7th of April. + +Purchase - Lead Times +===================== + +Supplier Lead Time +------------------ + +The *Supplier Lead Time* is the time needed for a product you +purchased to be delivered. To configure it, open a product from +:menuselection:`Purchase --> Products --> Products` and add a vendor +under the *Purchase* tab. + +.. image:: media/scheduled_dates_06.png + :align: center + :alt: View of the way to add vendors to products + +By clicking on *Add a line*, a new window is displayed. You can +specify the *Delivery Lead Time* there. If done so, the delivery day +for every purchase of that product is now equal to *Date of the +Purchase Order + Delivery Lead Time*. + +.. image:: media/scheduled_dates_07.png + :align: center + :alt: View of the delivery lead time configuration from a vendor form + +.. note:: + It is possible to add different vendors and, thus, different lead times + depending on the vendor. + +Security Lead Time +------------------ + +The *Security Lead Time* for purchase follows the same logic as the +one for *Sales*, except that you are the customer. Then, it is the +margin of error for your supplier to deliver your order. + +To set up *Security Lead Time* for purchase, go to +:menuselection:`Inventory --> Configuration --> Settings` and enable +the feature. + +.. image:: media/scheduled_dates_08.png + :align: center + :alt: View of the security lead time for purchase from the inventory settings + +Doing so, every time the system generates purchase orders, those are +scheduled that many days earlier to cope with unexpected vendor delays. + +Manufacturing - Lead Times +========================== + +Manufacturing Lead Time +----------------------- + +The *Manufacturing Lead Time* is the time needed to manufacture the +product. To specify it, open the *Inventory* tab of your product form +and add the number of days the manufacturing takes. + +.. image:: media/scheduled_dates_09.png + :align: center + :alt: View of the manufacturing lead time configuration from the product form + +When working with *Manufacturing Lead Times*, the *Deadline Start* +of the *MO* is **Commitment Date - Manufacturing Lead Time**. For +example, the MO’s deadline start date for an order having a commitment +date on the 10th of July is June 27th. + +Security Lead Time +------------------ + +The *Security Lead Time* for manufacturing allows generating +manufacturing orders earlier to cope with the risk of manufacturing +delays. + +To enable it, go to :menuselection:`Manufacturing --> Configuration --> +Settings` and tick *Security Lead Time*. + +.. image:: media/scheduled_dates_10.png + :align: center + :alt: View of the security lead time for manufacturing from the manufacturing app settings + +For example, a customer orders B with a delivery date scheduled on the +20th of June. The *Manufacturing Lead Time* is 14 days and the +*Security Lead Time* is 3 days, so the manufacturing of B needs to +start at the latest on the 3rd of June, which is the MO’s planned date. + +Global Example +============== + +Here is a configuration: + +- 1 day of security lead time for Sales +- 2 days of security lead time for Manufacturing +- 3 days of manufacturing lead time +- 1 day of security lead time for Purchase +- 4 days of supplier lead time + +Let’s say that a customer orders B on the 1st of September and the +delivery date is planned to be within 20 days (September 20th). In such +a scenario, here is when all the various steps are triggered. + +- **September 1st**: the sales order is created +- **September 10th**: the deadline to order components from the supplier + because of the manufacturing process (4 days of supplier lead + time) +- **September 13th**: the reception of the product from the supplier (1 day + of security lead time for Purchase) +- **September 14th**: the deadline start date for the manufacturing (19th - + 3 days of manufacturing lead time - 2 days of security lead time + for Manufacturing) +- **September 19th**: the expected date on the delivery order form (1 day + of security lead time for sales) \ No newline at end of file diff --git a/redirects.txt b/redirects.txt index cc089b50d..8c8ab0359 100644 --- a/redirects.txt +++ b/redirects.txt @@ -130,6 +130,7 @@ inventory/management/adjustment/virtual_warehouses.rst inventory/management/repl inventory/settings/warehouses.rst inventory/management/warehouses.rst # settings/* --> management/* (#424) inventory/settings/warehouses/difference_warehouse_location.rst inventory/management/warehouses/difference_warehouse_location.rst # settings/* --> management/* (#424) inventory/settings/warehouses/location_creation.rst inventory/management/warehouses/location_creation.rst # settings/* --> management/* (#424) +inventory/management/delivery/schedule_date.rst inventory/management/planning/scheduled_dates.rst # delivery/schedule_date --> planning/scheduled_dates (#660) helpdesk/getting_started.rst helpdesk/overview/getting_started.rst # (#565) helpdesk/after_sales.rst helpdesk/advanced/after_sales.rst # (#565)