Update integrating_landed_costs.rst

landed costs now possible for any costing method

content/applications/inventory_and_mrp/inventory/management.rst

@@ -10,10 +10,10 @@ Warehouse Management
 
    management/products
    management/warehouses
-   management/inventory_adjustments
+   management/replenishment_strategies
    management/delivery
    management/incoming
    management/misc
    management/planning
    management/lots_serial_numbers
-   management/reporting
+   management/reporting

content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/count_products.rst

@@ -1,96 +0,0 @@
-=====================
-Inventory Adjustments
-=====================
-
-Inventory adjustments can be accessed through :menuselection:`Inventory --> Operations -->
-Inventory Adjustments`.
-The report has all products currently in the stock. Each line is a unique combination of
-- Location
-- Product
-- Lot/Serial
-- Package
-- Owner
-
-
-Add new product in your stock
-=============================
-
-To add a line, just hit *Create* and fill in product and counted quantity fields then press 
-`tab` or click *Save*
-
-.. image:: count_products/create-line.png
-   :align: center
-   :alt: apply all wizzard allows to change reason and accounting date
-
-At this stage, the count is recorded but not yet *applied*. Meaning the quantity on hand is 
-not yet updated. 
-
-Just press *Apply* on the line or button *Apply All* button on the top of the screen.
-
-*Apply All* allows to edit the reason to use for the adjustments applied
-
-
-.. image:: count_products/apply-all.png
-   :align: center
-   :alt: apply all wizzard allows to change reason 
-
-Count products
-==============
-
-Counting products is a recurring activity in a warehouse. It often happens that theoric 
-stock levels are not correct and must be amended. 
-
-If a count is correct, press on *set*, it will copy the on hand quantity in the counted
-quantity. Applying such line will record a move in the history with a 0 quantity.
-
-If the count is different, record it in the counted quanditity field. Applying such line
-will record a move with the difference in tin the history.
-
-.. image:: count_products/history.png
-   :align: center
-   :alt: history of moves
-   
-.. note::
-    It happens that users count but apply only later. In the meantime, transfers of 
-    a counted product can occur. In such case quanities counted and on hand are not
-    consistant with the difference. When applying such line, Odoo will ask if you
-    want to keep the difference and the count.
-   
-Plan counts
-===========
-
-On each line there is:
-- *Scheduled Date*: it's the date at which a count should be made.
-- *User*: it's the person in charge of the count.
-- *Accounting Date*: this is the date at which the adjustments will be accounted. The
-  column is hidden by default.
-
-.. image:: count_products/plan.png
-   :align: center
-   :alt: history of moves
-   
-.. important::
-    In the barcode app, you will only see counts to make assigned to you, scheduled
-    for today or earlier.
-
-If you want to plan big counts, the easiest way is to select some lines, then hit 
-**Request A Count***. There you can select who will count and when. You can also 
-prefill the quantity with the on hand quantity.
-
-.. image:: count_products/request-count.png
-   :align: center
-   :alt: history of moves
-     
-.. tip::
-    The report offers a lot of filters that you can use to make your selection
-    
-By default, after an adjustment is applied, the scheduled date for the next 
-count is the 31st of december of the current year. This is a setting that can
-be modified in :menuselection:`Inventory --> Configuration --> Settings`.
-under the setting **Annual Inventory Day and Month**
-
-.. image:: count_products/annual-inventory.png
-   :align: center
-   :alt: history of moves
-
-

content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts.rst

@@ -1,38 +0,0 @@
-============
-Cycle Counts
-============
-
-In most companies, the stock is only counted once a year. 
-That's why by default, after making an inventory adjustment, the 
-scheduled date for the next count is set on the 31th of decemeber.
-But for some businesses it's crucial to have an accurate
-inventory count. 
-
-The goal of cycle counts is to count more often at key locations
-to keep your critical stock levels accurate.
-
-Configuration
-=============
-
-In Odoo, cycle counts are location-based. That means that the 
-frequency of the counts is defined on the storage location. That
-also means that to use cycle counts you need to activate the setting
-**Storage Locations**. 
-
-.. image:: cycle_counts/locations-settings.png
-   :align: center
-   :alt: Enable locations in an Odoo database's settings
-   
-Then, go to the locations via :menuselection:`Inventory --> Configuration -->
-Locations`.
-
-Open a location and change the Inventory Frequency. In this example we want to 
-count items in this loctation every 30 days. That means that once an adjustment 
-is applied on this location, the next scheduled date for this line will be 30 days
-after.
-
-.. image:: cycle_counts/inventory-frequency.png
-   :align: center
-   :alt: edit a location to change the inventory frequency
-
-

content/applications/inventory_and_mrp/inventory/management/inventory_adjustments/cycle_counts/test

@@ -1 +0,0 @@
-

content/applications/inventory_and_mrp/inventory/management/replenishment_strategies.rst

@@ -8,5 +8,4 @@ Inventory Adjustment
    :titlesonly:
    :glob:
 
-   inventory_adjustments/count_products
-   inventory_adjustments/cycle_counts
+   replenishment_strategies/virtual_warehouses

content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst

@@ -6,10 +6,6 @@ The landed cost feature in Odoo allows to include additional costs
 (shipment, insurance, customs duties, etc.) into the cost of the
 product.
 
-.. note::
-         Landed costs can only be applied to products with a FIFO or AVCO costing
-         method and an automated inventory valuation (which requires the
-         accounting application to be installed).
 
 Configuration
 =============
@@ -61,4 +57,4 @@ by clicking on the journal entry.
 
 .. note::
    You are not forced to start from the vendor bill, you can also go in :menuselection:`Inventory
-   --> Operations --> Landed Costs` and directly create the landed cost from there.
+   --> Operations --> Landed Costs` and directly create the landed cost from there.

content/applications/inventory_and_mrp/inventory/management/warehouses.rst

@@ -8,5 +8,4 @@ Warehouses
    :titlesonly:
    :glob:
 
-   warehouses/warehouses_locations
-   warehouses/resupply_warehouses
+   warehouses/difference_warehouse_location

content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst

@@ -0,0 +1,34 @@
+========================================================
+What is the difference between warehouses and locations?
+========================================================
+
+In Odoo, a **Warehouse** is the actual building/place in which your items
+are stocked. You can setup multiple warehouses and create moves between
+warehouses.
+
+A **Location**, is a specific space within your warehouse. It can be
+considered as a sublocation of your warehouse, as a shelf, a floor, an
+aisle, etc. Therefore, a location is part of one warehouse only and it
+is not possible to link one location to multiple warehouses. You can
+configure as many locations as you need under one warehouse.
+
+There are 3 types of locations:
+
+-   The **Physical Locations** are internal locations that are part of the
+    warehouses for which you are the owner. They can be the loading and
+    unloading area of your warehouse, a shelf or a department, etc.
+
+-   The **Partner Locations** are spaces within a customer and/or vendor's
+    warehouse. They work the same way as Physical Locations with the only
+    difference being that you are not the owner of the warehouse.
+
+-   The **Virtual Locations** are places that do not exist, but in which
+    products can be placed when they are not physically in an inventory yet
+    (or anymore). They come in handy when you want to place lost products
+    out of your stock (in the **Inventory loss**), or when you want to take into
+    account products that are on their way to your warehouse (**Procurements**).
+
+In Odoo, locations are structured hierarchically. You can structure your
+locations as a tree, dependent on a parent-child relationship. This
+gives you more detailed levels of analysis of your stock operations and
+the organization of your warehouses.

content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst

@@ -1,55 +0,0 @@
-===============================
-Resupply from another Warehouse
-===============================
-
-A common use case for multiple warehouses is to have one central warehouse that
-resupplies shops, each shop is considered as a local warehouse. When a shop want 
-to replenish a product, this product is ordered to the central stock.
-Odoo allows you to set easily which warehouse(s) can resupply a warehouse.
-
-Configuration
-=============
-
-In order to be able to resupply from another warehouse, you need to
-activate *multi-step routes*.
-
-.. image:: resupply_warehouses/virtual-warehouses-settings.png
-   :align: center
-   :alt: Enable Multi-Step Routes in an Odoo database's settings
-
-You can then access your warehouses via :menuselection:`Inventory --> Configuration -->
-Warehouses`.
-Open the warehouse which should be resupplied by the another one. You will
-have the possibility to directly indicate through which warehouse(s) it
-can be resupplied.
-
-.. image:: resupply_warehouses/virtual_warehouses_02.png
-   :align: center
-
-By activating this option, a new route will now be available on your
-products *Supply Product from Second warehouse*. It can now be
-selected, along with either a *reordering rule* or a *make to
-order*.
-
-.. image:: resupply_warehouses/virtual_warehouses_03.png
-   :align: center
-
-In this example, a reordering rule is set with a minimum of 5 units
-in stock and a maximum of 10 units in stock, having currently 0 units on
-hand.
-
-The system automatically creates two pickings, one *delivery order*
-from my Second Warehouse which contains the necessary products, and a
-receipt in my main warehouse WH/Stock for the same products. The source
-document is the *reordering rule* which triggered the route *Supply
-Product from Second warehouse*. 
-The location between the delivery and the receipt is a transit location.
-
-.. image:: resupply_warehouses/virtual_warehouses_05.png
-   :align: center
-
-.. image:: resupply_warehouses/virtual_warehouses_06.png
-   :align: center
-
-.. image:: resupply_warehouses/virtual_warehouses_07.png
-   :align: center

content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst

@@ -1,96 +0,0 @@
-===============================
-Manage Warehouses and Locations
-===============================
-
-Terminology
-===========
-
-Warehouse
----------
-
-In Odoo, a **Warehouse** is the actual building/place in which your items
-are stocked. You can setup multiple warehouses and create moves between
-warehouses.
-
-Location
---------
-
-A **Location**, is a specific space within your warehouse. It can be
-considered as a sublocation of your warehouse, as a shelf, a floor, an
-aisle, etc. Therefore, a location is part of one warehouse only and it
-is not possible to link one location to multiple warehouses. You can
-configure as many locations as you need under one warehouse.
-
-There are 3 types of locations:
-
--   The **Physical Locations** are internal locations that are part of the
-    warehouses for which you are the owner. They can be the loading and
-    unloading area of your warehouse, a shelf or a department, etc.
-
--   The **Partner Locations** are spaces within a customer and/or vendor's
-    warehouse. They work the same way as Physical Locations with the only
-    difference being that you are not the owner of the warehouse.
-
--   The **Virtual Locations** are places that do not exist, but in which
-    products can be placed when they are not physically in an inventory yet
-    (or anymore). They come in handy when you want to place lost products
-    out of your stock (in the **Inventory loss**), or when you want to take into
-    account products that are on their way to your warehouse (**Procurements**).
-
-In Odoo, locations are structured hierarchically. You can structure your
-locations as a tree, dependent on a parent-child relationship. This
-gives you more detailed levels of analysis of your stock operations and
-the organization of your warehouses.
-
-Configuration
-=============
-
-To activate the locations, go to :menuselection:`Configuration --> Settings` and enable 
-**Storage Locations**. Then, hit *Save*.
-
-.. image:: warehouses_locations/feature-storage-location.png
-   :align: center
-   :alt: Enabling the storage location feature in Odoo Inventory.
-
-.. important::
-   If you want to manage several routes within your warehouses, then enable **Multi-Step Routes**
-   and check :doc:`use-routes`.
-
-Creating a new warehouse
-========================
-
-To create a warehouse, go to :menuselection:`Configuration -->
-Warehouse Management --> Warehouses` and click on **Create**.
-
-Fill out a **Warehouse Name** and a **Short Name**. The short name is five characters maximum.
-
-.. image:: warehouses_locations/create-new-warehouse.png
-   :align: center
-   :alt: Short name field of a warehouse on Odoo Inventory.
-
-.. important::
-   The **Short Name** appears on your transfer orders and other warehouse documents. We recommend
-   using an understandable one (e.g.: WH/[first letters of location]).
-
-Now, go back to your dashboard. There, new operations related to your warehouse have been
-automatically generated.
-
-.. image:: warehouses_locations/new-transfer-types.png
-   :align: center
-   :alt: Inventory app dashboard displaying new transfer type for the recently created warehouse.
-
-.. note::
-   Adding a second warehouse will automatically activate the **Locations** setting.
-   
-Creating a new location
-=======================
-
-To create a location, go to :menuselection:`Configuration -->
-Warehouse Management --> Locations` and click on **Create**.
-
-Fill out a **Location Name** and a **Parent Location** and hit *Save*.
-
-.. image:: warehouses_locations/create-new-location.png
-   :align: center
-   :alt: Short name field of a warehouse on Odoo Inventory.
-

content/applications/inventory_and_mrp/inventory/routes/concepts/inter_warehouse.rst

@@ -7,10 +7,73 @@ Proceeding to such behavior is called *inter-warehouse transfers*. If this actio
 easy to perform, the administrative part can be arduous. Fortunately, Odoo comes with an intuitive
 flow that helps save time when registering those transfers.
 
+Configuration
+=============
+
+First of all, go to :menuselection:`Configuration --> Settings` and enable **Storage Locations**.
+Then, hit save.
+
+.. image:: inter_warehouse/feature-storage-location.png
+   :align: center
+   :alt: Enabling the storage location feature in Odoo Inventory.
+
+.. important::
+   If you want to manage several routes within your warehouses, then enable **Multi-Step Routes**
+   and check :doc:`use-routes`.
+
+Creating a new warehouse
+========================
+
+The next step is to create your new warehouse. To do so, go to :menuselection:`Configuration -->
+Warehouse Management --> Warehouses` and click on **Create**.
+
+Fill out a **Warehouse Name** and a **Short Name**. The short name is five characters maximum.
+
+.. image:: inter_warehouse/create-new-warehouse.png
+   :align: center
+   :alt: Short name field of a warehouse on Odoo Inventory.
+
+.. important::
+   The **Short Name** appears on your transfer orders and other warehouse documents. We recommend
+   using an understandable one (e.g.: WH/[first letters of location]).
+
+Now, go back to your dashboard. There, new operations related to your warehouse have been
+automatically generated.
+
+.. image:: inter_warehouse/new-transfer-types.png
+   :align: center
+   :alt: Inventory app dashboard displaying new transfer type for the recently created warehouse.
+
+Creating a new inventory
+========================
+
+If you create a new warehouse, you might already have an existing inventory in it. In that case, you
+should create an inventory in Odoo. If this is not the case, you can skip this step.
+
+Into the inventory application, select :menuselection:`Operations --> Inventory Adjustment`.
+Then, create a new inventory by clicking on **Create**. Fill in the **Inventory Reference**,
+**Date** and make sure to select the right warehouse and location.
+
+.. image:: inter_warehouse/annual-inventory.png
+   :align: center
+   :alt: View of the inventory adjustment form before hitting the start button.
+
+Next, click on **Start Inventory**. You will be able to input your existing products in the new
+window. Select add an item and indicate the **Real Quantity** available in the warehouse.
+The theoretical quantity can not be changed as it represents a computed one from purchase and sales
+orders.
+
+.. image:: inter_warehouse/in-progress-annual-inventory.png
+   :align: center
+   :alt: View of the actual physical inventory of the new warehouse.
+
+.. tip::
+   Don't forget to validate your inventory once you have recorded the state of all your products.
 
 Create an internal transfer
 ===========================
-If you want to transfer eight units of a product
+
+The final step is to create your internal transfer. If you want to transfer eight units of a product
 from your first warehouse to another one, proceed as follows:
 
 From your dashboard, select an internal movement of one of the two warehouses. To do so, click on
@@ -63,4 +126,4 @@ It is also possible to manually transfer each product:
    **backorder**.
 
    - Create a backorder if you expect to process the remaining products later.
-   - Do not create a backorder if you will not supply/receive the remaining products.
+   - Do not create a backorder if you will not supply/receive the remaining products.

content/applications/sales/crm/acquire_leads/lead_mining.rst

@@ -31,7 +31,7 @@ From there, click on the **Generate Leads** button, a window where you will be a
    :align: center
 
 
-When choosing to target Companies and their contacts you can choose the contacts you are getting based on Role or Seniority. 
+When choosing to target Companied and their contacts you can choose the contacts you are getting based on Role or Seniority. 
 When getting contact information make sure to be aware of the latest EU regulation, get more information about General Data Protection Regulation on
 `Odoo GDPR <http://odoo.com/gdpr>`__, 
 
@@ -49,10 +49,10 @@ You can also add tags to track your generated leads.
 Pricing
 ==================
 This is an In-App Purchase feature, each generated lead will cost you one credit.
-If you choose to get contact information each contact will also cost you one additional credit.
+If you choose to get contact information each contact will also cost us one additional credit.
 Here is the pricing for this `feature <https://iap.odoo.com/iap/in-app-services/167?>`__, 
 To buy credits you can either go to :menuselection:`CRM --> Configuration --> Settings --> Buy
-Credits`; or go to :menuselection:`Settings --> Contacts --> Odoo IAP --> View my Services`.
+Credits`; or go to :menuselection:`Settings --> In-App Purchases --> View my Services`.
 
 .. image:: media/LM6.png
    :align: center

content/developer/howtos/rdtraining/02_setup.rst

@@ -148,10 +148,10 @@ Here are some useful git commands for your day-to-day work.
   .. code-block:: console
 
     $ cd $HOME/src/odoo
-    $ git checkout 15.0
+    $ git checkout 14.0
 
     $ cd $HOME/src/enterprise
-    $ git checkout 15.0
+    $ git checkout 14.0
 
 * Fetch and rebase:
 
@@ -159,11 +159,11 @@ Here are some useful git commands for your day-to-day work.
 
     $ cd $HOME/src/odoo
     $ git fetch --all --prune
-    $ git rebase --autostash odoo/15.0
+    $ git rebase --autostash odoo/14.0
 
     $ cd $HOME/src/enterprise
     $ git fetch --all --prune
-    $ git rebase --autostash enterprise/15.0
+    $ git rebase --autostash enterprise/14.0
 
 
 Install the dependencies

content/developer/howtos/rdtraining/B_acl_irrules.rst

@@ -169,7 +169,7 @@ C                     X
 ====== ====== ==== ====== ======
 
 A user with the groups A and C will be able to do anything but delete the object
-while one with B and C will be able to read and update it, but not create or delete it.
+while one with B and C will be able to read or update, but not search or read.
 
 .. note::
 

content/developer/reference/backend/views.rst

@@ -92,7 +92,7 @@ an impact on all view types.
 
   Disable/enable record deletion on the view through the **Action** dropdown.
 
-* ``duplicate`` (``form``)
+* ``duplicate`` (``form`` & ``list``)
 
   Disable/enable record duplication on the view through the **Action** dropdown.
 
@@ -1693,7 +1693,7 @@ root can have the following attributes:
     ``{$name}`` can be ``bf`` (``font-weight: bold``), ``it``
     (``font-style: italic``), or any `bootstrap contextual color`_ (``danger``,
     ``info``, ``muted``, ``primary``, ``success`` or ``warning``).
-``create``, ``edit``, ``delete``, ``import``, ``export_xlsx``
+``create``, ``edit``, ``delete``, ``duplicate``, ``import``, ``export_xlsx``
     allows *dis*\ abling the corresponding action in the view by setting the
     corresponding attribute to ``false``
 ``limit``

locale/de/LC_MESSAGES/inventory_and_mrp.po

@@ -2241,9 +2241,11 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:41
 msgid ""
-"**Purchase Security Lead Time**: Margin 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 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."
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:48

locale/es/LC_MESSAGES/general.po

@@ -28,7 +28,6 @@
 # Braulio D. López Vázquez <bdl@odoo.com>, 2022
 # Borja García Rouco <bgrouco@gmail.com>, 2022
 # Martin Trigaux, 2022
-# marcescu, 2022
 # 
 #, fuzzy
 msgid ""
@@ -37,7 +36,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-04-08 13:26+0000\n"
 "PO-Revision-Date: 2021-11-02 08:47+0000\n"
-"Last-Translator: marcescu, 2022\n"
+"Last-Translator: Martin Trigaux, 2022\n"
 "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -1108,8 +1107,6 @@ msgid ""
 "In the URL, add ``?debug=1`` or ``?debug=true`` after *web*. To deactivate "
 "the debug mode, add `?debug=0` instead."
 msgstr ""
-"En la URL, añade ``?debug=1`` o ``?debug=true`` después de *web*. Para "
-"desactivar el modo de depuración, añada ``debug=0`` en su lugar."
 
 #: ../../content/applications/general/developer_mode.rst:58
 msgid ""
@@ -1133,23 +1130,23 @@ msgstr ""
 
 #: ../../content/applications/general/developer_mode.rst:70
 msgid "edit action"
-msgstr "Editar acción"
+msgstr ""
 
 #: ../../content/applications/general/developer_mode.rst:71
 msgid "manage filters"
-msgstr "Gestionar Filtros"
+msgstr ""
 
 #: ../../content/applications/general/developer_mode.rst:72
 msgid "edit the current view"
-msgstr "editar la vista actual"
+msgstr ""
 
 #: ../../content/applications/general/developer_mode.rst:73
 msgid "see the `fields view get`"
-msgstr "ver la `vista de campos obtener`"
+msgstr ""
 
 #: ../../content/applications/general/developer_mode.rst:74
 msgid "and much more."
-msgstr "y mucho más."
+msgstr ""
 
 #: ../../content/applications/general/digest_emails.rst:3
 msgid "Digest Emails"
@@ -1171,29 +1168,26 @@ msgstr ""
 #: ../../content/applications/general/digest_emails.rst:15
 msgid "You can control a variety of settings for your Digest Emails, such as:"
 msgstr ""
-"Puede controlar una variedad de configuraciones para sus correos "
-"electrónicos de resumen, tales como:"
 
 #: ../../content/applications/general/digest_emails.rst:17
 msgid "which KPIs are shared in the Digest"
-msgstr "qué KPIs se comparten en el Digest"
+msgstr ""
 
 #: ../../content/applications/general/digest_emails.rst:18
 msgid "how often Digest Emails are sent"
 msgstr ""
-"la frecuencia con la que se envían los correos electrónicos de resumen"
 
 #: ../../content/applications/general/digest_emails.rst:19
 msgid "who in your organization receives Digest Emails"
-msgstr "quién en su organización recibe los correos electrónicos del Digest"
+msgstr ""
 
 #: ../../content/applications/general/digest_emails.rst:20
 msgid "creating custom Digest Email templates"
-msgstr "creación de plantillas de correo electrónico personalizadas de Digest"
+msgstr ""
 
 #: ../../content/applications/general/digest_emails.rst:21
 msgid "adding additional KPIs (Studio required)"
-msgstr "añadir KPIs adicionales (Estudio requerido)"
+msgstr ""
 
 #: ../../content/applications/general/digest_emails.rst:24
 msgid ""
@@ -1201,14 +1195,10 @@ msgid ""
 "serves as the primary template, which includes all KPI measurements across "
 "your Odoo database and is sent daily to administrators."
 msgstr ""
-"Por defecto, el correo electrónico de compendio está *habilitado*, y *Su "
-"compendio periódico de Odoo* sirve como plantilla principal, que incluye "
-"todas las mediciones de KPI a través de su base de datos de Odoo y se envía "
-"diariamente a los administradores."
 
 #: ../../content/applications/general/digest_emails.rst:31
 msgid "Customize *Your Odoo Periodic Digest*"
-msgstr "Personaliza *Tu resumen periódico de Odoo*"
+msgstr ""
 
 #: ../../content/applications/general/digest_emails.rst:33
 msgid ""
@@ -1223,36 +1213,28 @@ msgid ""
 "A popup window appears and presents a variety of editable settings, which "
 "include:"
 msgstr ""
-"Aparece una ventana emergente que presenta una variedad de ajustes "
-"editables, que incluyen:"
 
 #: ../../content/applications/general/digest_emails.rst:39
 msgid "**Digest Title** - what you want your Digest Email to be called"
-msgstr "**Título del Digest** - cómo quiere que se llame su Digest Email"
+msgstr ""
 
 #: ../../content/applications/general/digest_emails.rst:40
 msgid ""
 "**Periodicity** - control the regimen in how often Digest Emails are sent"
 msgstr ""
-"**Periodicidad** - controla el régimen en la frecuencia de envío de los "
-"correos electrónicos de resumen"
 
 #: ../../content/applications/general/digest_emails.rst:41
 msgid ""
 "**KPIs** - check/uncheck each calculated KPI that appears in Digest Emails"
 msgstr ""
-"**KPIs** - marque/desmarque cada KPI calculado que aparece en los correos "
-"electrónicos de resumen"
 
 #: ../../content/applications/general/digest_emails.rst:42
 msgid "**Recipients** - add/remove users who receive your Digest Emails"
 msgstr ""
-"**Recipientes** - añada/elimine los usuarios que reciben sus correos "
-"electrónicos de resumen"
 
 #: ../../content/applications/general/digest_emails.rst:43
 msgid "**Custom** - add your own KPIs (Studio required)"
-msgstr "**Personalizado** - añada sus propios KPIs (se requiere un estudio)"
+msgstr ""
 
 #: ../../content/applications/general/digest_emails.rst:52
 msgid "Custom digest emails"

locale/es/LC_MESSAGES/inventory_and_mrp.po

@@ -23,7 +23,6 @@
 # Martin Trigaux, 2022
 # Lucia Pacheco <lpo@odoo.com>, 2022
 # Braulio D. López Vázquez <bdl@odoo.com>, 2022
-# marcescu, 2022
 # 
 #, fuzzy
 msgid ""
@@ -32,7 +31,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-04-08 13:26+0000\n"
 "PO-Revision-Date: 2021-11-02 08:48+0000\n"
-"Last-Translator: marcescu, 2022\n"
+"Last-Translator: Braulio D. López Vázquez <bdl@odoo.com>, 2022\n"
 "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -3055,10 +3054,18 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:41
 msgid ""
-"**Purchase Security Lead Time**: Margin 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 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."
 msgstr ""
+"**Plazo de seguridad para compras**: este es el tiempo adicional para "
+"mitigar el riesgo de retrasos por el proveedor. Se programará el recibo ese "
+"número de días previos para prevenir retrasos inesperados del proveedor. En "
+"caso de una *orden de reabastecimiento*, la **fecha programada de entrega - "
+"plazo de seguridad** para la compra será la fecha de *recepción* programada "
+"predeterminada."
 
 #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:48
 msgid ""
@@ -7767,7 +7774,7 @@ msgstr "Gestión de la fabricación"
 
 #: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:3
 msgid "Alternative Work Centers"
-msgstr "Centros de trabajo alternativos"
+msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:5
 msgid ""

locale/es/LC_MESSAGES/services.po

@@ -12,7 +12,6 @@
 # Jesse Garza <jga@odoo.com>, 2021
 # Braulio D. López Vázquez <bdl@odoo.com>, 2022
 # Patricia Gutiérrez Capetillo <pagc@odoo.com>, 2022
-# marcescu, 2022
 # 
 #, fuzzy
 msgid ""
@@ -21,7 +20,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-03-18 14:56+0000\n"
 "PO-Revision-Date: 2021-11-02 08:49+0000\n"
-"Last-Translator: marcescu, 2022\n"
+"Last-Translator: Patricia Gutiérrez Capetillo <pagc@odoo.com>, 2022\n"
 "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -1094,7 +1093,7 @@ msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:28
 msgid "Step 2: Set up a service"
-msgstr "Paso 2: Configurar un servicio"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:31
 msgid ""
@@ -1114,8 +1113,6 @@ msgid ""
 "Now, select the invoicing management you would like to have under the "
 "*Sales* tab. We recommend the following configuration:"
 msgstr ""
-"Ahora, seleccione la gestión de facturación que desea tener en la pestaña "
-"*Ventas*. Recomendamos la siguiente configuración:"
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:47
 msgid ""
@@ -1136,11 +1133,11 @@ msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:58
 msgid "Prevision an invoice and record time"
-msgstr "Previsión de una factura y registro del tiempo"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:61
 msgid "Step 1: Place an order"
-msgstr "Paso 1: Hacer un pedido"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:63
 msgid ""
@@ -1152,17 +1149,15 @@ msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:72
 msgid "Step 2: Invoice the customer"
-msgstr "Paso 2: Facturar al cliente"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:74
 msgid "In *Sales*, select the respective sales order to *Create Invoice*."
 msgstr ""
-"En *Ventas*, seleccione el pedido de venta correspondiente para *Crear "
-"factura*."
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:82
 msgid "Step 3: Link the task to the ticket"
-msgstr "Paso 3: Vincular la tarea al ticket"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:84
 msgid ""
@@ -1172,47 +1167,38 @@ msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:92
 msgid "Step 4: Record the time spent"
-msgstr "Paso 4: Registrar el tiempo empleado"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:94
 msgid ""
 "Still on the respective helpdesk ticket, record the hours performed under "
 "the *Timesheets* tab."
 msgstr ""
-"Siempre en el ticket de asistencia correspondiente, registre las horas "
-"realizadas en la pestaña *Hojas de tiempo*."
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:100
 msgid ""
 "Note that the hours recorded on the ticket form are shown on the *Delivered*"
 " column in the sales order."
 msgstr ""
-"Tenga en cuenta que las horas registradas en el formulario del ticket se "
-"muestran en la columna *Entregado* del pedido de venta."
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:108
 msgid ""
 "Hours recorded on the ticket are automatically shown in *Timesheets* and on "
 "the dedicated task."
 msgstr ""
-"Las horas registradas en el ticket se muestran automáticamente en *Hojas de "
-"tiempo* y en la tarea dedicada."
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:111
 msgid ":doc:`reinvoice_from_project`"
-msgstr ":doc:`reinvoice_from_project`"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:112
 msgid ""
 ":doc:`/applications/inventory_and_mrp/inventory/management/products/uom`"
 msgstr ""
-":doc:`/applications/inventory_and_mrp/inventory/management/products/uom`"
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:3
 msgid "Invoice Time Spent on Tickets (Postpaid Support Services)"
 msgstr ""
-"Facturación del tiempo dedicado a los tickets (servicios de asistencia de "
-"pospago)"
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:5
 msgid ""
@@ -1220,10 +1206,6 @@ msgid ""
 "into sales orders and invoices through a project task. It gives you more "
 "control over what you charge your client, and it is more efficient."
 msgstr ""
-"Extraiga directamente el tiempo facturable que ha rastreado en sus tickets "
-"del servicio de asistencia en los pedidos de venta y las facturas a través "
-"de una tarea del proyecto. De este modo, tendrá más control sobre lo que "
-"cobra a su cliente y será más eficiente."
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:10
 msgid "Configuration"
@@ -1234,9 +1216,6 @@ msgid ""
 "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk team --> Edit`"
 " and enable the options *Timesheet on Ticket* and *Time Reinvoicing*."
 msgstr ""
-"Vaya a :menuselection:`Helpdesk --> Configuración --> Equipo de Helpdesk -->"
-" Editar` y active las opciones *Hoja de tiempo en el ticket* y "
-"*Refacturación de tiempo*."
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:15
 msgid ""
@@ -1244,13 +1223,10 @@ msgid ""
 "timesheets) will be linked by default. Open its *External link* to enable "
 "the feature *Bill from tasks*."
 msgstr ""
-"En *Hoja de tiempo en el ticket*, elija el *Proyecto* al que se vincularán "
-"por defecto los tickets (y las hojas de tiempo). Abra su *Enlace externo* "
-"para habilitar la función *Factura desde las tareas*."
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:22
 msgid "Create a sales order and an invoice"
-msgstr "Crear un pedido de venta y una factura"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:24
 msgid ""
@@ -1260,7 +1236,7 @@ msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:31
 msgid "*Create Sales Order* and proceed to create the invoice."
-msgstr "*Crear Pedido de Venta* y proceder a crear la factura."
+msgstr ""
 
 #: ../../content/applications/services/project.rst:8
 msgid "Project"
@@ -1272,8 +1248,6 @@ msgid ""
 "`Odoo Tutorials: Project and Timesheets "
 "<https://www.odoo.com/slides/project-and-timesheets-21>`_"
 msgstr ""
-"`Tutoriales de Odoo: Proyectos y hojas de tiempo "
-"<https://www.odoo.com/slides/project-and-timesheets-21>`_"
 
 #: ../../content/applications/services/project/tasks.rst:5
 msgid "Tasks"
@@ -1281,7 +1255,7 @@ msgstr "Tareas"
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:3
 msgid "Create Project's Tasks from an Email Alias"
-msgstr "Crear tareas del proyecto a partir de un alias de correo electrónico"
+msgstr ""
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:5
 msgid ""
@@ -1294,28 +1268,23 @@ msgstr ""
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:11
 msgid "Set up an incoming email server"
-msgstr "Configurar un servidor de correo electrónico entrante"
+msgstr ""
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:14
 msgid ""
 "On the *Settings* application, enable *External Email Servers* and define "
 "the incoming email alias you would like to use."
 msgstr ""
-"En la aplicación *Configuración*, active *Servidores de correo electrónico "
-"externos* y defina el alias de correo electrónico entrante que desea "
-"utilizar."
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:15
 msgid ""
 "**For more information**: "
 ":doc:`/applications/general/email_communication/email_servers`"
 msgstr ""
-"**Para más información**: "
-":doc:`/applications/general/email_communication/email_servers"
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:18
 msgid "Configure the email alias in your project"
-msgstr "Configure el alias de correo electrónico en su proyecto"
+msgstr ""
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:22
 msgid ""
@@ -1328,21 +1297,16 @@ msgstr ""
 #: ../../content/applications/services/project/tasks/email_alias.rst:23
 msgid "In addition, you can now directly set it when creating a new project."
 msgstr ""
-"Además, ahora se puede establecer directamente al crear un nuevo proyecto."
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:30
 msgid ""
 "All the recipients of the email (To/Cc/Bcc) are automatically added as "
 "followers of the task."
 msgstr ""
-"Todos los destinatarios del correo electrónico (To/Cc/Bcc) se añaden "
-"automáticamente como seguidores de la tarea."
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:32
 msgid "The email can be seen under the name of your project on the dashboard."
 msgstr ""
-"El correo electrónico puede verse bajo el nombre de su proyecto en el "
-"tablero."
 
 #: ../../content/applications/services/timesheets.rst:8
 msgid "Timesheets"
@@ -1369,8 +1333,6 @@ msgid ""
 "Activate the :ref:`developer mode <developer-mode>`, go to *Timesheets*, and"
 " change the *Project* and *Task* set by default, if you like."
 msgstr ""
-"Activar el modo :ref:`developer <developer-mode>`, vaya a *Hojas de tiempo*,"
-" y cambie el *Proyecto* y la *Tarea* establecidos por defecto, si lo desea."
 
 #: ../../content/applications/services/timesheets/overview/time_off.rst:16
 msgid ""

locale/es/LC_MESSAGES/sphinx.po

@@ -9,7 +9,6 @@
 # Braulio D. López Vázquez <bdl@odoo.com>, 2022
 # Martin Trigaux, 2022
 # Patricia Gutiérrez Capetillo <pagc@odoo.com>, 2022
-# marcescu, 2022
 # 
 #, fuzzy
 msgid ""
@@ -18,7 +17,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2022-04-08 13:26+0000\n"
 "PO-Revision-Date: 2022-03-18 15:03+0000\n"
-"Last-Translator: marcescu, 2022\n"
+"Last-Translator: Patricia Gutiérrez Capetillo <pagc@odoo.com>, 2022\n"
 "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -103,7 +102,7 @@ msgstr "Actualizaciones de solución de bugs"
 
 #: ../../extensions/odoo_theme/layout_templates/homepage.html:51
 msgid "Upgrading Odoo"
-msgstr "Actualizando Odoo"
+msgstr ""
 
 #: ../../extensions/odoo_theme/layout_templates/homepage.html:56
 msgid "Odoo.sh: The Odoo Cloud Platform"

locale/th/LC_MESSAGES/inventory_and_mrp.po

@@ -2241,9 +2241,11 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:41
 msgid ""
-"**Purchase Security Lead Time**: Margin 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 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."
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:48

locale/zh_CN/LC_MESSAGES/inventory_and_mrp.po

@@ -22,7 +22,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 15.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-04-08 13:26+0000\n"
+"POT-Creation-Date: 2022-03-18 14:56+0000\n"
 "PO-Revision-Date: 2021-11-02 08:48+0000\n"
 "Last-Translator: Martin Trigaux, 2022\n"
 "Language-Team: Chinese (China) (https://www.transifex.com/odoo/teams/41243/zh_CN/)\n"
@@ -1369,14 +1369,7 @@ msgid ""
 "suppliers are considered as being always available."
 msgstr "现在，输入你想要处理的拣货。你可点击*确认*，直接完成这步操作，因为供应商发货的产品总是被视为库存充足。"
 
-#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:49
-msgid ""
-"If you have :guilabel:`Storage Locations` activated, you can click the "
-"hamburger menu next to the :guilabel:`Done quantity` to specify the "
-"location(s) where you are storing the received product(s)."
-msgstr ""
-
-#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:56
+#: ../../content/applications/inventory_and_mrp/inventory/management/incoming/one_step.rst:51
 msgid ""
 "Once you *Validate* the receipt, the products leave the *Supplier Location* "
 "to enter your *WH/Stock Location*. You can easily see that the receipt took "
@@ -2352,10 +2345,14 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:41
 msgid ""
-"**Purchase Security Lead Time**: Margin 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 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."
 msgstr ""
+"**采购安全提前期** ：减少供应商延误风险的额外时间。 收据将安排在许多天前，以应对意外的供应商延误。 如果是 *补货到订单* ，则采购的 "
+"**交货订单预定日期-安全提前期** 将是默认的 *收货* 预定日期。"
 
 #: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:48
 msgid ""
@@ -6204,16 +6201,10 @@ msgid ""
 msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:37
-msgid ""
-"The destination location should **not** be a scrap location. A scrap "
-"location is where you put products that you don't need."
-msgstr ""
-
-#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:41
 msgid "Using the same BoM to describe Variants"
 msgstr "使用同一个物料清单描述产品变体"
 
-#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:43
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:39
 msgid ""
 "As suggested above, you can use *BOMs* for specific *Product Variants*. Once"
 " the various attributes have been configured on the product form, there are "
@@ -6221,7 +6212,7 @@ msgid ""
 "combination."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:47
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:43
 msgid ""
 "Either create one BoM per variant, by specifying the Product Variant in the "
 "dedicated field below the product name. Or use one BOM, that contains all of"
@@ -6229,48 +6220,48 @@ msgid ""
 "to, using the *Apply on Variants* column, as shown below."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:57
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:53
 msgid "Adding Operations"
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:59
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:55
 msgid ""
 "You can also add operations to your *BoM*, if you want workers to follow "
 "instructions or register time spent. To use this feature, enable the *Work "
 "Orders* feature in the *Manufacturing* app settings, as shown below."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:67
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:63
 msgid ""
 "Each operation is unique as it is always linked to only one BOM. This being "
 "said, Operations Operations can be re-used when configuring a new BOM, with "
 "the *Copy Existing Operations* feature."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:74
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:70
 msgid ""
 "Finally, just like for components, operations can also be variant specific "
 "only, as shown below."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:82
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:78
 msgid "Adding By-Products"
 msgstr "添加副产品"
 
-#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:84
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:80
 msgid ""
 "A *by-product* is a product that is produced on top of the main product of a"
 " *BoM*. As opposed to the primary product, there can be more than one on a "
 "BOM."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:87
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:83
 msgid ""
 "To add *by-products* to a *BoM*, you will first need to enable the by-"
 "product feature from the *Manufacturing* app settings."
 msgstr ""
 
-#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:93
+#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:89
 msgid ""
 "Once the feature is enabled, you can add *by-products* to your *BoMs*. Note "
 "that if you have Operations, you'll need to specify in which operation the "