diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst index 040d13216..ea377a974 100644 --- a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst +++ b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst @@ -1,262 +1,347 @@ -=========================================== -How is the Scheduled Delivery Date Computed -=========================================== +======================== +Scheduled delivery dates +======================== -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. +Accurately forecasting delivery dates is vital for fulfilling customer expectations. In Odoo, the +*Inventory* app allows for comprehensive lead time configuration, allowing coordination and planning +of manufacturing orders, deliveries, and receptions. -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. +Lead time types +=============== -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. +Different lead times for different operations can impact various stages of the order fulfillment +process. Here's a summary of the types of lead times in Odoo: -How are Lead Times Calculated? -============================== +.. image:: scheduled_dates/all-lead-times.png + :align: center + :alt: Show graphic of all lead times working together. -.. raw:: html +- :ref:`Customer lead time `: The default time frame for + fulfilling customer orders. The customer lead time is the number of days from the date the sales + order (SO) is confirmed to the date the products are shipped from the warehouse. This is also + known as *delivery lead time*. - +- :ref:`Sales security lead time `: moves the *scheduled + delivery date* forward by a specified number of days. This serves as a buffer to allow the team + ample time to prepare the outgoing shipment earlier, considering the possibility of delays in the + fulfillment process. -.. link to the Google Slides: https://docs.google.com/presentation/d/1nVM5PyD5OYM4jB13HqHpmBHn40NSDqbLEUUMxivsJeo +- :ref:`Purchase lead time `: the number of days from the + confirmation of a purchase order (PO) to the receipt of products. It provides insight on the time + it takes for products to arrive at the warehouse, facilitating effective scheduling and planning + of supplier deliveries. -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: +- :ref:`Purchase security lead time `: advances the order + deadline on a :abbr:`PO (Purchase Order)` by a specified number of days. This proactive approach + of placing orders earlier mitigates the risk of vendor or shipping delays. Thus, for products that + are set to replenish to order, the need appears on the *Replenishment report* earlier, according + to the specified number of days. -- **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. +- :ref:`Manufacturing lead time `: the number of days needed to + complete a manufacturing order (MO) from the date of confirmation. This lead time includes + weekends (non-working hours in Odoo), and is used to forecast an approximate production date for a + finished good. -- **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**. +- :ref:`Manufacturing security lead time `: moves the + scheduled date of the :abbr:`MO (Manufacturing Order)` forward by a specified number of days. When + used in conjunction with :ref:`replenish to order `, the + security lead time makes the need appear earlier on the replenishment report. -- **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. +.. _inventory/management/customer-lt: -- **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. +Sales lead times +================ -- **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. +Customer lead times and sales security lead times can be configured to automatically compute an +*expected delivery date* on a :abbr:`SO (Sales Order)`. The expected delivery date ensures a +realistic *delivery dates* setting for shipments from the warehouse. -- **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. +Odoo issues a warning message if the set delivery date is earlier than the expected date, as it may +not be feasible to fulfill the order by that time, which would impact other warehouse operations. -- **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. +.. example:: + A :abbr:`SO (Sales Order)` containing a `Coconut-scented candle` is confirmed on July 11th. The + product has a customer lead time of 14 days, and the business uses a sales security lead time of + 1 day. Based on the lead time inputs, Odoo suggests a delivery date in 15 days, on July 26th. -Sales - Lead Times -================== + .. image:: scheduled_dates/scheduled-date.png + :align: center + :alt: Set *Delivery Date* in a sales order. Enables delivery lead times feature. -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. +The following sections demonstrate how to automatically compute expected delivery dates. -.. image:: scheduled_dates/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:: scheduled_dates/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 +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*. +Set the customer lead time on each product form, by navigating to the products page. To do so, go to +:menuselection:`Sales app --> Products --> Products`. From there, select the desired product, and +switch to the :guilabel:`Inventory` tab. Then, under the :guilabel:`Customer Lead Time` field, fill +in the number of calendar days required to fulfill the delivery order from start to finish. -.. image:: scheduled_dates/scheduled_dates_04.png - :align: center - :alt: View of the customer lead time configuration from the product form +.. example:: + Set a 14-day customer lead time for the `Coconut-scented candle` by navigating to its product + form. Then, in the :guilabel:`Inventory` tab, type `14.00` days into the :guilabel:`Customer Lead + Time` field. -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. + .. image:: scheduled_dates/customer.png + :align: center + :alt: Set *Customer Lead Time* on the product form. -Security Lead Time ------------------- +.. _inventory/management/sales-security-lt: -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. +Sales security lead time +------------------------ -The number of security days is subtracted from the calculation to -compute a scheduled date earlier than the one promised to the customer. +*Sales security lead time* is set globally for the business in :menuselection:`Inventory app --> +Configuration --> Settings`. -To set this up, go to :menuselection:`Inventory --> Configuration --> -Settings` and enable the feature *Security Lead Time for Sales*. +On the configuration page, under the :guilabel:`Advanced Scheduling` heading, locate the box for +:guilabel:`Security Lead Time for Sales`, and click the checkbox to enable the feature. -.. image:: scheduled_dates/scheduled_dates_05.png - :align: center - :alt: View of the security lead time for sales configuration from the sales settings +Next, enter the desired number of calendar days. This security lead time is a buffer notifying the +team to prepare for outgoing shipments earlier than the scheduled date. -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. +.. example:: + Setting the :guilabel:`Security Lead Time for Sales` to `1.00` day, pushes the + :guilabel:`Scheduled Date` of a delivery order (DO) forward by one day. In that case, if a + product is initially scheduled for delivery on April 6th, but with a one-day security lead time, + the new scheduled date for the delivery order would be April 5th. + + .. image:: scheduled_dates/sales-security.png + :align: center + :alt: View of the security lead time for sales configuration from the sales settings. 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. +For orders that include multiple products with different lead times, the lead times can be +configured directly from the quotation itself. On a quotation, click the :guilabel:`Other Info` tab, +and set the :guilabel:`Shipping Policy` to: -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. +#. :guilabel:`As soon as possible` to deliver products as soon as they are ready. The + :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is determined by adding today's + date to the shortest lead time among the products in the order. -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. +#. :guilabel:`When all products are ready` to wait to fulfill the entire order at once. The + :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is determined by adding today's + date to the longest lead time among the products in the order. -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. +.. image:: scheduled_dates/shipping-policy.png + :align: center + :alt: Show *Shipping Policy* field in the *Other Info* tab of a quotation. -Purchase - Lead Times -===================== +.. example:: + In a quotation containing 2 products, `Yoga mat` and `Resistance band,` the products have a lead + time of 8 days and 5 days, respectively. Today's date is April 2nd. -Supplier Lead Time ------------------- + When the :guilabel:`Shipping Policy` is set to :guilabel:`As soon as possible`, the scheduled + delivery date is 5 days from today: April 7th. On the other hand, selecting :guilabel:`When all + products are ready` configures the scheduled date to be 8 days from today: April 10th. -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. +.. _inventory/management/purchase-lt: -.. image:: scheduled_dates/scheduled_dates_06.png - :align: center - :alt: View of the way to add vendors to products +Purchase lead times +=================== -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*. +Automatically determining the dates on which to place orders from suppliers can help simplify the +procurement process. -.. image:: scheduled_dates/scheduled_dates_07.png - :align: center - :alt: View of the delivery lead time configuration from a vendor form +Odoo calculates the supplier shipment *receipt date*, and :abbr:`PO (Purchase Order)` deadline, +based on the required date the product is needed in the warehouse. By working backwards from the +receipt date, vendor lead times and purchase security lead times are taken into account, in order to +determine the :abbr:`PO (Purchase Order)` deadline. + +This deadline is the date by which the order should be confirmed, in order to ensure timely arrival +by the expected receipt date. + +.. image:: scheduled_dates/vendor-lead-times.png + :align: center + :alt: Visualization of PO deadline and receipt date used with vendor lead times. + +.. seealso:: + :ref:`PO scheduling with reordering rules ` + +Vendor lead time +---------------- + +To set a vendor lead time for orders arriving in the warehouse from a vendor location, begin by +navigating to a product form through :menuselection:`Purchase app --> Products --> Products`. + +Next, select the desired product, and switch to the :guilabel:`Purchase` tab. In the editable vendor +pricelist, click the :guilabel:`Add a line` button to add vendor details, such as the +:guilabel:`Vendor` name, :guilabel:`Price` offered for the product, and lastly, the +:guilabel:`Delivery Lead Time`. .. note:: - It is possible to add different vendors and, thus, different lead times - depending on the vendor. + Multiple vendors and lead times can be added to the vendor pricelist. The default vendor and lead + time selected will be the entry at the top of the list. -Security Lead Time ------------------- +.. example:: + On the vendor pricelist of the product form, the :guilabel:`Delivery Lead Time` for the selected + vendor is set to `10 days.` -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. + .. image:: scheduled_dates/set-vendor.png + :align: center + :alt: Add delivery lead times to vendor pricelist on a product. -To set up *Security Lead Time* for purchase, go to -:menuselection:`Inventory --> Configuration --> Settings` and enable -the feature. +By setting the vendor lead time, the expected arrival date of the item is automatically determined +as the date of the :abbr:`PO (Purchase Order)` confirmation, plus the vendor lead time. This ensures +that warehouse employees are notified, if the products do **not** arrive within the expected +timeframe. -.. image:: scheduled_dates/scheduled_dates_08.png - :align: center - :alt: View of the security lead time for purchase from the inventory settings +.. example:: + On a :abbr:`PO (Purchase Order)` confirmed on July 11th, for a product configured with a 10-day + vendor lead time, Odoo automatically sets the :guilabel:`Receipt Date` to July 21st. The receipt + date also appears as the :guilabel:`Scheduled Date` on the warehouse receipt form, accessible + from the :guilabel:`Receipt` smart button, located on the :guilabel:`PO (Purchase Order)`. -Doing so, every time the system generates purchase orders, those are -scheduled that many days earlier to cope with unexpected vendor delays. + .. image:: scheduled_dates/receipt-date.png + :align: center + :alt: Show expected *Receipt Date* of the product from the vendor. -Manufacturing - Lead Times -========================== + .. image:: scheduled_dates/scheduled-date-receipt.png + :align: center + :alt: Show expected *Scheduled Date* of arrival of the product from the vendor. -Manufacturing Lead Time +.. _inventory/management/purchase-security-lt: + +Purchase security lead time +--------------------------- + +*Purchase security lead time* is set globally for the business in :menuselection:`Inventory app --> +Configuration --> Settings`. + +On the configuration page, under the :guilabel:`Advanced Scheduling` heading, locate the box for +:guilabel:`Security Lead Time for Purchase`, and click the checkbox to enable the feature. + +Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is +set to account for potential delays in supplier deliveries. + +.. example:: + Setting the :guilabel:`Security Lead Time for Purchase` to `2.00` days, pushes the + :guilabel:`Scheduled Date` of receipt back by one day. In that case, if a product is initially + scheduled to arrive on April 6th, with a two-day security lead time, the new scheduled date for + the receipt would be April 8th. + + .. image:: scheduled_dates/vendor-security.png + :align: center + :alt: Set security lead time for purchase from the Inventory > Configuration > Settings. + +.. _inventory/management/manuf-lt: + +Manufacturing lead times +======================== + +Lead times can help simplify the procurement process for consumable materials and components used in +manufactured products with bills of materials. + +The :abbr:`MO (Manufacturing Order)` deadline, which is the deadline to begin the manufacturing +process to complete the product by the scheduled delivery date, can be determined by configuring the +manufacturing lead times and manufacturing security lead times. + +.. image:: scheduled_dates/manuf-lead-times.png + :align: center + :alt: Visualization of the determination of planned MO date 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. +Configure the manufacturing lead time directly on the product form, by navigating to +:menuselection:`Manufacturing app --> Products --> Products`, and select the desired product. -.. image:: scheduled_dates/scheduled_dates_09.png - :align: center - :alt: View of the manufacturing lead time configuration from the product form +In the :guilabel:`Inventory` tab of the product, specify the calendar days needed to the manufacture +the product in the :guilabel:`Manufacturing Lead Time` field. -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. +.. example:: + Specify a 14-day :guilabel:`Manufacturing Lead Time` for a product directly in the + :guilabel:`Inventory` tab of the product. -Security Lead Time ------------------- + .. image:: scheduled_dates/set-manufacturing.png + :align: center + :alt: View of the manufacturing lead time configuration from the product form. -The *Security Lead Time* for manufacturing allows generating -manufacturing orders earlier to cope with the risk of manufacturing -delays. +Establish a :abbr:`MO (Manufacturing Order)` deadline, based on the *expected delivery date*, +indicated in the :guilabel:`Scheduled Date` field of the :abbr:`DO (Delivery Order)`. -To enable it, go to :menuselection:`Manufacturing --> Configuration --> -Settings` and tick *Security Lead Time*. +The :abbr:`MO (Manufacturing Order)` deadline, which is the :guilabel:`Scheduled Date` field on the +:abbr:`MO (Manufacturing Order)`, is calculated as the *expected delivery date* subtracted by the +manufacturing lead time. -.. image:: scheduled_dates/scheduled_dates_10.png - :align: center - :alt: View of the security lead time for manufacturing from the manufacturing app settings +This ensures the manufacturing process begins on time, in order to meet the delivery date. -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. +However, it's important to note that lead times are based on calendar days. Lead times do **not** +consider weekends, holidays, or *work center capacity* (:dfn:`the number of operations that can be +performed at the work center simultaneously`). -Global Example +.. seealso:: + - :ref:`Manufacturing planning ` + - :ref:`Configure automatic MO scheduling with reordering rules + ` + +.. example:: + A product's scheduled shipment date on the :abbr:`DO (Delivery Order)` is August 15th. The + product requires 14 days to manufacture. So, the latest date to start the :abbr:`MO + (Manufacturing Order)` to meet the commitment date is August 1st. + +.. _inventory/management/manuf-security-lt: + +Manufacturing security lead time +-------------------------------- + +*Manufacturing security lead time* is set globally for the business in :menuselection:`Manufacturing +app --> Configuration --> Settings`. Under the :guilabel:`Planning` heading, locate the box for +:guilabel:`Security Lead Time`, and click the checkbox to enable the feature. + +Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is +set to account for potential delays in the manufacturing process. + +.. image:: scheduled_dates/manuf-security.png + :align: center + :alt: View of the security lead time for manufacturing from the manufacturing app settings. + +.. example:: + A product has a scheduled shipment date on the :abbr:`DO (Delivery Order)` set for August 15th. + The manufacturing lead time is 7 days, and manufacturing security lead time is 3 days. So, the + :guilabel:`Scheduled Date` on the :abbr:`MO (Manufacturing Order)` reflects the latest date to + begin the manufacturing order. In this example, the planned date on the :abbr:`MO (Manufacturing + Order)` is August 5th. + +Global example ============== -Here is a configuration: +See the following example to understand how all the lead times work together to ensure timely order +fulfillment: -- 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 +- **Sales security lead time**: 1 day +- **Manufacturing security lead time**: 2 days +- **Manufacturing lead time**: 3 days +- **Purchase security lead time**: 1 day +- **Vendor lead time**: 4 days -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. +The customer places an order for a manufactured product on September 1st, and the scheduled delivery +date from the warehouse is on September 20th. Odoo uses lead times and automated reordering rules to +schedule the necessary operations, based on the outgoing shipment delivery date, September 20th: -- **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) +.. image:: scheduled_dates/global-example.png + :align: center + :alt: Show timeline of how lead times work together to schedule warehouse operations. + +- **September 1st**: Sales order created, confirmed by salesperson. + +- **September 9th**: Deadline to order components to ensure they arrive in time when manufacturing + begins (4-day supplier lead time). + +- **September 13th**: Scheduled date of receipt for components. Initially, it was set to 9/14, but + the 1-day purchase security lead time pushed the date earlier by 1 day. + +- **September 14th**: Deadline to begin manufacturing. Calculated by subtracting the manufacturing + lead time of 3 days, and the manufacturing security lead time of 2 days, from the expected + delivery date of September 19th. + +- **September 19th**: :guilabel:`Scheduled Date` on the delivery order form indicates the updated + expected delivery date, which was originally set as September 20th. But the sales security lead + time pushed the date forward by a day. + +Odoo's replenishment planning maps a business' order fulfillment process, setting pre-determined +deadlines and raw material order dates, including buffer days for potential delays. This ensures +products are delivered on time. diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/all-lead-times.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/all-lead-times.png new file mode 100644 index 000000000..b190d8b2a Binary files /dev/null and b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/all-lead-times.png differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/customer.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/customer.png new file mode 100644 index 000000000..559569acb Binary files /dev/null and b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/customer.png differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/global-example.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/global-example.png new file mode 100644 index 000000000..51d000e7b Binary files /dev/null and b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/global-example.png differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/manuf-lead-times.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/manuf-lead-times.png new file mode 100644 index 000000000..173a1bd61 Binary files /dev/null and b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/manuf-lead-times.png differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/manuf-security.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/manuf-security.png new file mode 100644 index 000000000..d5840616c Binary files /dev/null and b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/manuf-security.png differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/receipt-date.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/receipt-date.png new file mode 100644 index 000000000..60b738b42 Binary files /dev/null and b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/receipt-date.png differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_05.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/sales-security.png similarity index 100% rename from content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_05.png rename to content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/sales-security.png diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled-date-receipt.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled-date-receipt.png new file mode 100644 index 000000000..74a377f24 Binary files /dev/null and b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled-date-receipt.png differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled-date.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled-date.png new file mode 100644 index 000000000..770c1adad Binary files /dev/null and b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled-date.png differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_02.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_02.png deleted file mode 100644 index 29976c8b5..000000000 Binary files a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_02.png and /dev/null differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_03.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_03.png deleted file mode 100644 index 3ee2885b5..000000000 Binary files a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_03.png and /dev/null differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_04.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_04.png deleted file mode 100644 index c13ddc003..000000000 Binary files a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_04.png and /dev/null differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_06.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_06.png deleted file mode 100644 index 2456d64d1..000000000 Binary files a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_06.png and /dev/null differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_07.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_07.png deleted file mode 100644 index 78c880081..000000000 Binary files a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_07.png and /dev/null differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_08.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_08.png deleted file mode 100644 index 18cb90170..000000000 Binary files a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_08.png and /dev/null differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_10.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_10.png deleted file mode 100644 index bb70626ab..000000000 Binary files a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_10.png and /dev/null differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_09.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/set-manufacturing.png similarity index 100% rename from content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/scheduled_dates_09.png rename to content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/set-manufacturing.png diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/set-vendor.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/set-vendor.png new file mode 100644 index 000000000..d9d331bf5 Binary files /dev/null and b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/set-vendor.png differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/shipping-policy.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/shipping-policy.png new file mode 100644 index 000000000..f617ba25f Binary files /dev/null and b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/shipping-policy.png differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/vendor-lead-times.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/vendor-lead-times.png new file mode 100644 index 000000000..853f45127 Binary files /dev/null and b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/vendor-lead-times.png differ diff --git a/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/vendor-security.png b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/vendor-security.png new file mode 100644 index 000000000..723ba11ab Binary files /dev/null and b/content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates/vendor-security.png differ diff --git a/content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst b/content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst index b50c63b8f..4e1b68d81 100644 --- a/content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst +++ b/content/applications/inventory_and_mrp/inventory/management/products/reordering_rules.rst @@ -2,6 +2,8 @@ Reordering rules ================ +.. _inventory/management/reordering_rules: + Reordering rules are used to keep forecasted stock levels above a certain threshold without exceeding a specified upper limit. This is accomplished by specifying a minimum quantity that stock should not fall below and a maximum quantity that stock should not exceed. diff --git a/content/applications/inventory_and_mrp/inventory/management/products/strategies.rst b/content/applications/inventory_and_mrp/inventory/management/products/strategies.rst index b5d2edc3d..61a46c4b2 100644 --- a/content/applications/inventory_and_mrp/inventory/management/products/strategies.rst +++ b/content/applications/inventory_and_mrp/inventory/management/products/strategies.rst @@ -27,6 +27,8 @@ maximum stock level. Reordering rules can be created and managed in the replenishment report, or from the product form. +.. _inventory/management/products/strategies: + Make to order ------------- diff --git a/content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst b/content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst index 4f839a66f..1e9cc577c 100644 --- a/content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst +++ b/content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst @@ -2,6 +2,8 @@ Use the Master Production Schedule ================================== +.. _manufacturing/management/use_mps: + The Master Production Schedule (MPS) is a valuable tool to plan your production based on your demand forecast. diff --git a/content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst b/content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst index fb8d41ce2..9a2f4e2da 100644 --- a/content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst +++ b/content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst @@ -31,6 +31,8 @@ Within the :guilabel:`Manufacturing` module, select :menuselection:`Configuratio :align: center :alt: An example of a fully configured work center form. +.. _manufacturing/management/using_work_centers/wc-setup: + Set standards for work center productivity ------------------------------------------