NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[IMP] *: export translations

Browse Source 
closes odoo/documentation#6215

Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
This commit is contained in:
Martin Trigaux 2023-10-26 07:27:32 +02:00
parent 82055c1f15
commit 1dedb18c09
4 changed files with 290 additions and 215 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
locale/sources/administration.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-10-09 07:26+0000\n"
"POT-Creation-Date: 2023-10-26 05:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1396,11 +1396,11 @@ msgid "Create a new application"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:24
msgid "To get started, go to `Microsoft's Azure Portal <https://portal.azure.com/>`_. Log in with the :guilabel:`Microsoft Outlook Office 365` account if there is one, otherwise log in with the personal :guilabel:`Microsoft account`. A user with administrative access to the Azure Settings will need to connect and perform the following configuration. Next, navigate to the section labeled :guilabel:`Manage Azure Active Directory`."
msgid "To get started, go to `Microsoft's Azure Portal <https://portal.azure.com/>`_. Log in with the :guilabel:`Microsoft Outlook Office 365` account if there is one, otherwise log in with the personal :guilabel:`Microsoft account`. A user with administrative access to the Azure Settings will need to connect and perform the following configuration. Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID` (formally *Azure Active Directory*)."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:30
msgid "Now, click on :guilabel:`Add (+)`, located in the top menu, and then select :guilabel:`App registration`. On the :guilabel:`Register an application` screen, rename the :guilabel:`Name` to `Odoo` or something recognizable. Under the :guilabel:`Supported account types` section select :guilabel:`Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)`."
msgid "Now, click on :guilabel:`Add (+)`, located in the top menu, and then select :guilabel:`App registration`. On the :guilabel:`Register an application` screen, rename the :guilabel:`Name` to `Odoo` or something recognizable. Under the :guilabel:`Supported account types` section select :guilabel:`Accounts in any organizational directory (Any Microsoft Entra ID directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)`."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:36

28
locale/sources/general.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-11 14:17+0000\n"
"POT-Creation-Date: 2023-10-26 05:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -281,7 +281,7 @@ msgid "A user with administrative access to the *Azure Settings* must connect an
msgstr ""
#: ../../content/applications/general/auth/azure.rst:53
msgid "Next, navigate to the section labeled :guilabel:`Manage Azure Active Directory`. The location of this link is usually in the center of the page."
msgid "Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID` (formally *Azure Active Directory*). The location of this link is usually in the center of the page."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:56
@ -2243,46 +2243,50 @@ msgid "IAP accounts"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:25
msgid "Credits to use IAP services are stored on IAP accounts, which are specific to each service and database. By default, IAP accounts are common to all companies, but can be restricted to specific ones. Activate the :ref:`developer mode <developer-mode>`, then go to :menuselection:`Technical Settings --> IAP Account`."
msgid "Credits to use IAP services are stored on IAP accounts, which are specific to each service. By default, IAP accounts are common to all companies, but can be restricted to specific ones. Activate the :ref:`developer mode <developer-mode>`, then go to :menuselection:`Technical Settings --> IAP Account`."
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:34
msgid "An IAP account can be disabled by appending `+disabled` to its token. Reverting this change will re-enable the account."
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:38
msgid "IAP Portal"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:36
#: ../../content/applications/general/in_app_purchase.rst:40
msgid "The IAP Portal is a platform regrouping my IAP Services. It is accessible from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, I can view my current balance, recharge my credits, review my consumption and set a reminder to when credits are low."
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:44
#: ../../content/applications/general/in_app_purchase.rst:48
msgid "Get notified when credits are low"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:46
#: ../../content/applications/general/in_app_purchase.rst:50
msgid "To be notified when it’s time to recharge my credits, I’ll go to my IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and mark the Receive threshold warning option. Then, I’ll provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent to by email!"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:56
#: ../../content/applications/general/in_app_purchase.rst:60
msgid "IAP services available"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:58
#: ../../content/applications/general/in_app_purchase.rst:62
msgid "Different services are available depending on the hosting type of your Database:"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:60
#: ../../content/applications/general/in_app_purchase.rst:64
msgid "*Odoo Online*: only the IAP services provided by Odoo can be used (i.e. the SMS, Snailmail, Reveal and Partner Autocomplete features);"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:62
#: ../../content/applications/general/in_app_purchase.rst:66
msgid "*Odoo.sh and Odoo Enterprise (on-premise)*: both the services provided by Odoo and by third-party apps can be used."
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:66
#: ../../content/applications/general/in_app_purchase.rst:70
msgid "Offering my own services"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:68
#: ../../content/applications/general/in_app_purchase.rst:72
msgid "I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity to get recurring revenue for an ongoing service use rather than — and possibly instead of — a sole initial purchase. Please, find more information at: :doc:`/developer/howtos/provide_iap_services`."
msgstr ""

395
locale/sources/inventory_and_mrp.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-10-09 07:26+0000\n"
"POT-Creation-Date: 2023-10-26 05:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -4549,7 +4549,6 @@ msgid "view of a generic pull from rule when preparing deliveries"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:50
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:45
msgid "How does it work?"
msgstr ""
@ -5108,269 +5107,341 @@ msgid "Use the star button under the search bar to save current search as a favo
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:3
msgid "What is a Removal Strategy (FIFO, LIFO, and FEFO)?"
msgid "Removal strategies (FIFO, LIFO, FEFO)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:5
msgid "Usually, *Removal Strategies* are defined in picking operations to select the best products to optimize the distance for the worker, for quality control purposes, or to first move the products with the closest expiration date."
msgid "For companies with warehouses, **removal strategies** determine which products are taken from the warehouse, and when. Removal strategies are typically defined for specific picking operations. This helps companies to select the best products, optimize the distance workers need to travel when picking items for orders, and account for quality control, such as moving products with expiration dates."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:9
msgid "When a product movement needs to be done, Odoo finds available products that can be assigned to the transfer. The way Odoo assigns these products depends on the *Removal Strategy* defined in the *Product Category* or on the *Location*."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:11
msgid "When a product needs to be moved, Odoo finds available products that can be assigned to the transfer. The way Odoo assigns these products depends on the :guilabel:`Removal Strategy` defined in either the :guilabel:`Product Category` or the :guilabel:`Location` dashboards."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:14
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:15
msgid "To change the :guilabel:`Removal Strategy`, go to :menuselection:`Inventory app --> Configuration --> Locations` or :menuselection:`Product Categories`. Click on a :guilabel:`Location` or :guilabel:`Product Category`, and then click :guilabel:`Edit`. Change the product category :guilabel:`Force Removal Strategy` or the location :guilabel:`Removal Strategy` by clicking on the drop-down menu and selecting the desired removal strategy. After selecting the new removal strategy, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "Change the Force Removal Strategy for either the Product Categories or Locations."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:27
msgid "What happens inside the warehouse?"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:16
msgid "Imagine a generic warehouse plan, with receiving docks and area, storage locations, picking and packing areas, and shipping docks. All products go through all these locations, but some rules, such as removal strategies, can have an effect on which products are taken for the pickings."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:29
msgid "Most warehouses share the same important areas: receiving docks and sorting areas, storage locations, picking and packing areas, and shipping/loading docks. While all products entering or leaving the warehouse might go through each of these locations at some point, removal strategies can have an effect on which products are taken, from where, and when."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:34
msgid "In this example below, vendor trucks unload pallets of goods at the receiving docks. Then, operators scan the products in the receiving area, with the reception date and expiration date. After that, products are stored in their respective storage locations."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:39
msgid "Not all products have expiration dates, but in this example, expiration dates apply."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "empty stock waiting for deliveries at the docks."
msgid "Products entering stock via the receiving area."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:24
msgid "Here, vendor trucks unload pallets of goods at the docks. Then, operators scan the products in the receiving area, with the receiving date and, if the product has an expiration date, the expiration date. After that, products are stored in their respective locations."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "products entering stock via the receiving area."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:32
msgid "Next, several orders for the same product are made, but you didn’t receive the goods the same day and they don’t have the same expiration date. In that situation, you logically prefer sending those with the closest date first. Depending on the removal strategy you chose, Odoo generates a transfer with the products fitting your settings the best."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "products being packed at packing area for delivery, taking expiration dates into account."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:42
msgid "On the transfer form, you can find the product’s lot/serial number to pick for delivery."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:48
msgid "First In, First Out (FIFO)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:50
msgid "When using a **First In, First Out** strategy, a demand for some products triggers a removal rule which requests a transfer for the lot/serial number that has entered your stock the first."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:45
msgid "In Odoo, receive products by navigating to the :menuselection:`Inventory` application, and in the kanban view, click on either the :guilabel:`Receipts` heading or :guilabel:`# TO PROCESS` button. On the :guilabel:`Receipts` dashboard, find and click on the individual receipt which will open the warehouse intake form. Click :guilabel:`Edit`, and then enter the received quantity in the :guilabel:`Done` column. To finish, :guilabel:`Validate` to receive the products and register them in the Odoo database."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:53
msgid "To be clearer, let’s imagine that you have three lots of nails in your warehouse. Those three have the following lot numbers: 00001, 00002, 00003, each with 5 nails boxes in it. 00001 entered the stock on the 23rd of May, 00002 on the 25th of May, and 00003 on the 1st of June. A customer orders you 6 boxes on the 11th of June. With the *FIFO* strategy selected, a transfer is requested for the five boxes of 00001 and one of the boxes in 00002 because 00001 has entered your stock before the others. The box from 00002 is taken because it has the oldest enter date after 00001."
msgid "Receiving products can also be done within the Odoo *Barcode* application. If using the *Barcode* app, scan the product(s), update the quantity, and finally, click :guilabel:`Validate`. After products are received in Odoo, the products can then be moved to their respective storage locations."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:60
msgid "So, for every order of a product with the *FIFO* strategy selected, Odoo requests a transfer for the good that has been in your stock for the longest period."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:58
msgid "Continuing with the same example, below, imagine several sales orders are made for the products received earlier, that use expiration dates. In this example, the products weren't received on the same day, and they don't have the same expiration date. In this situation, logically, sending products with the closest expiration date is preferred, instead of products received first or last. Using the chosen removal strategy configured for those products (in this example, :ref:`FEFO <routes/FEFO>`), Odoo generates a transfer for the products with the soonest expiration date to the picking area, then the packing area, and finally, to the shipping docks for delivery to the customer."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:64
msgid "Last In, First Out (LIFO)"
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "Products being packed at the packing area for delivery, taking the expiration dates into\n"
"account."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:66
msgid "The same way as for FIFO, the **Last In, First Out** strategy is based on moving products based on the date they entered the stock. Here, a demand for some products triggers a removal rule that requests a transfer for the lot/serial number that has entered your stock the last."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:73
msgid "To pick for delivery, the product's lot/serial number can be found on the transfer form. To learn more about picking and shipping, refer to either :doc:`../../management/shipments_deliveries/receipts_delivery_two_steps` or :doc:`../../management/shipments_deliveries/delivery_three_steps`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:70
msgid "To better understand, let’s imagine three lots of screws in your warehouse. Those three have the following numbers: 10001, 10002, 10003, each with 10 screw boxes in it. 10001 has entered the stock on the 1st of June, 10002 on the 3rd of June, and 10003 on the 6th of June. A customer orders 7 boxes on the 8th of June. With the *LIFO* strategy selected, a transfer is requested for seven boxes of 10003 because that lot is the last one to have entered the stock."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:79
msgid "How each removal strategy works"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:76
msgid "So, basically, for every order of a product with the *LIFO* strategy used, a transfer for the last one to have entered the stock is requested."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:80
msgid "This strategy is banned in many countries and can lead to only have old or obsolete products in your stock."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:81
msgid "Removal strategies determine which products are taken from the warehouse when orders are confirmed."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:84
msgid "First Expire, First Out (FEFO)"
msgid "First In, First Out (FIFO)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:86
msgid "The **First Expire, First Out** strategy is a bit different from the two others. Here, it is the expiration date that is important and not the date the product entered the stock."
msgid "When using a :guilabel:`First In, First Out (FIFO)` strategy, demand for a product triggers a removal rule, which requests a transfer for the lot/serial number that entered the stock first (and therefore, has been in stock for the longest time)."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:89
msgid "Let’s imagine three lots of 6-eggs boxes (in this specific case, don’t forget to use :doc:`units of measure <../../management/products/uom>`). Those three have the following numbers: 20001, 20002, and 20003, each with 5 boxes in it. 20001 has entered the stock on the 1st of July and expires on the 15th of July, 20002 on the 2nd and expires on the 14th of July, and 20003 on the 4th and expires on the 21st of July. A customer orders 6 boxes on the 5th of July. With the *FEFO* strategy selected, a transfer is requested for the five boxes of 20002 and one from 20001. The transfer for all the boxes of the lot 20002 is because they have the closest expiration date. The transfer also requests one box from 20001 because it’s the lot that expires the sooner after 20002."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:90
msgid "For example, imagine there are three lots of nails in the warehouse, and have the corresponding lot numbers: `00001`, `00002`, `00003`. Each lot has five boxes of nails in it."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:98
msgid "Then, you can remember that for every order of a product with the *FEFO* strategy, a transfer is requested for the product that has the nearest expiration date from the order date."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:93
msgid "Lot `00001` entered the stock on May 23, lot `00002` on May 25, and lot `00003` on June 1. A customer orders six boxes on June 11."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:102
msgid "Use Removal Strategies"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:104
msgid "To identify some units from other ones, you need to track them, either by *lot* or by *serial number*. To do so, go to :menuselection:`Configuration --> Settings`. Then, activate *Storage Location*, *Multi-Steps Routes*, and *Lots & Serial Numbers*."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:96
msgid "Using the :abbr:`FIFO (First In, First Out)` removal strategy, a transfer request will pick the five boxes from lot `00001` first, and then from the boxes in lot `00002`, since lot `00001` entered the stock first. The box from lot `00002` is taken next because it has the oldest receipt date after lot `00001`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "features to enable in order to properly use removal strategies."
msgid "The detailed operations for the transfer shows the nail lots to be removed."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:113
msgid "To work with the *FEFO* strategy, activate the *Expiration Dates* feature."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:106
msgid "Last In, First Out (LIFO)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:115
msgid "Next, you need to define your removal strategy, on *Product Categories* via :menuselection:`Inventory --> Configuration --> Product Categories`."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:108
msgid "Similar to the :abbr:`FIFO (First In, First Out)` method, the :guilabel:`Last In, First Out (LIFO)` removal strategy moves products based on the date they entered a warehouse's stock. Instead of removing the oldest stock on-hand, however, it targets the **newest** stock on-hand for removal."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "force removal strategy set up as first in first out."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:112
msgid "Every time an order for products with the :abbr:`LIFO (Last In, First Out)` method is placed, a transfer is created for the lot/serial number that has most recently entered the stock (the **last** lot/serial number that entered the warehouse's inventory)."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:117
msgid "In many countries, the :abbr:`LIFO (Last In, First Out)` removal strategy in banned, since it can potentially result in old, expired, or obsolete products being delivered to customers."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:120
msgid "For example, imagine there are three lots of boxes of screws in the warehouse, and have the corresponding lot numbers: `10001`, `10002`, and `10003`, each with 10 boxes of screws per lot."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:123
msgid "FIFO (First In, First Out)"
msgid "Lot `10001` entered the stock on June 1, lot `10002` on June 3, and lot `10003` on June 6. A customer orders seven boxes on June 8."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:125
msgid "As said, a *FIFO* strategy implies that products stocked first move out first. Companies should use that method if they are selling products with short demand cycles, such as clothes, and to ensure they are not stuck with outdated styles in stock."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:129
msgid "For this example, we created three lots of white shirts. Those are from the All/Clothes category, where we put *FIFO* as the removal strategy. In our stock location (WH/Stock), we now find the three lots available."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:126
msgid "Using the :abbr:`LIFO (Last In, First Out)` removal strategy, a transfer is requested for seven boxes of screws from lot `10003` because that lot is the last one to have entered the stock."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "view of the white shirt lots inventory valuation."
msgid "The detailed operations shows which lots are being selected for the picking."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:137
msgid "The lot 000001 contains 5 shirts, 000002 contains 3 shirts, and 000003 contains 2. As it can be seen above, 000001 has entered the stock first. Let’s create a sale order of six white shirts to check that products from that lot are the first ones to move out."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:134
msgid "First Expired, First Out (FEFO)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:141
msgid "On the delivery order linked to the picking, you can see that the oldest lot numbers have been reserved thanks to the *FIFO* strategy."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:136
msgid "While the :abbr:`FIFO (First In, First Out)` and :abbr:`LIFO (Last In, First Out)` methods target products for removal based on date of entry into the warehouse, the :guilabel:`First Expired, First Out (FEFO)` method targets products for removal based on their assigned expiration dates."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "two lots being reserved for sell with the FIFO strategy."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:140
msgid "Using the :abbr:`FEFO (First Expired, First Out)` removal strategy, every sales order that includes products with this removal strategy assigned ensures that transfers are requested for products with the expiration date soonest to the order date."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:149
msgid "LIFO (Last In, First Out)"
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:144
msgid "As an example, imagine there are three lots of six-egg boxes. Those three lots have the following lot numbers: `20001`, `20002`, and `20003`, each with five boxes in it."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:147
msgid "Lot `20001` entered the stock on July 1 and expires on July 15, lot `20002` entered on July 2 and expires on July 14, and lot `20003` entered on July 3 and expires on July 21. A customer orders six boxes on July 5."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:151
msgid "With a *LIFO* strategy, that’s quite the opposite. In fact, the products that are brought the last move out the first. It is mostly used in case of products without a shelf life."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:154
msgid "Even if our white shirts are clothes, we can say that they are timeless. So, let’s use them to test our *LIFO* strategy. Once again, open the product category via :menuselection:`Inventory --> Configuration --> Product Categories` and change the removal strategy to *LIFO*."
msgid "Using the :abbr:`FEFO (First Expired, First Out)` method, a transfer is requested for the five boxes from lot `20002` and one from lot `20001`. All the boxes in lot `20002` are transferred because they have the earliest expiration date. The transfer also requests one box from lot `20001` because it has the next closest expiration date after lot `20002`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "last in first out strategy set up as forced removal strategy."
msgid "The detailed operations for the transfer shows the lots to be removed."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:162
msgid "Now, create a sale order for 4 white shirts and check that the reserved products are from lots 000003 and 000002."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:161
msgid "Using removal strategies"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:163
msgid "To differentiate some units of products from others, the units need to be tracked, either by :guilabel:`Lot` or by :guilabel:`Serial Number`. To do so, go to :menuselection:`Inventory --> Configuration --> Settings`. Then, activate the :guilabel:`Storage Locations`, :guilabel:`Multi-Step Routes`, and :guilabel:`Lots & Serial Numbers` settings. Click :guilabel:`Save` to save changes."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "two lots being reserved for sell with the LIFO strategy."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:170
msgid "Don’t forget that the *LIFO* strategy is banned in many countries!"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:173
msgid "FEFO (First Expiry, First Out)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:175
msgid "With the *FEFO* strategy, the way products are picked is not based on the reception date. In this particular case, they are dispatched according to their expiration date."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:179
msgid "To have more information about Expiration date, please have a look at :doc:`the related doc <../../management/lots_serial_numbers/expiration_dates>`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:182
msgid "By activating *Expiration Dates*, it becomes possible to define different dates on the serial/lot numbers to be used in *FEFO*. These dates can be set by going to :menuselection:`Inventory --> Master Data --> Lots/Serial Numbers`."
msgid ":alt: Traceability settings."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "view of the removal date for 0000001."
msgid ":alt: Warehouse settings."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:190
msgid "Lots are picked based on their removal date, from earliest to latest. Lots without a removal date defined are picked after lots with removal dates."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:177
msgid "To use the :abbr:`FEFO (First Expired, First Out)` removal strategy, the :guilabel:`Expiration Dates` setting needs to be activated as well. To enable this, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the checkbox next to :guilabel:`Expiration Dates`. Remember to click :guilabel:`Save` to save all changes."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:194
msgid "Other dates are for informational and reporting purposes only. If not removed from the stock, lots that are past the expiration dates may still be picked for delivery orders!"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:197
msgid "To use the *FEFO* strategy, once again go to :menuselection:`Inventory --> Configuration --> Product Categories` and choose *FEFO* as the *Force Removal Strategy*."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:183
msgid "Now, specific removal strategies can be defined on product categories. To do this, go to :menuselection:`Inventory app --> Configuration --> Product Categories`, and choose a product category to define the removal strategy on. In the :guilabel:`Force Removal Strategy` field, choose a removal strategy."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "view of the FEFO strategy being set up as forced removal strategy."
msgid ":alt: Removal strategy on a product category."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:204
msgid "For this particular case, let’s use hand cream. As usual, we have three lots of them."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:192
msgid "To view all products with lots/serial numbers assigned to them, navigate to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. This reveals a page with drop-down menus of all products assigned lots or serial numbers, filtered by *product* by default. To change the category these products are filtered by, click :guilabel:`Product` (in the search bar, in the top right of the page) to remove the default filter, and select a new filter if desired."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:207
msgid "**Lot / Serial No**"
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "Click on Products, then Lots/Serial Numbers to display all the products with lots or serial\n"
"numbers."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:207
msgid "**Product**"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:207
msgid "**Expiration Date**"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:209
msgid "0000001"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:209
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:211
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:213
msgid "Hand Cream"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:209
msgid "09/30/2019"
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:203
msgid "To view the serial numbers being selected for a sales order, go to the :guilabel:`Sales app` and select the sales order in question. In the sales order, click the :guilabel:`Delivery` smart button in the top right. In the :guilabel:`Operations` tab, click the :guilabel:`⦙≣ (Detailed Operations)` icon in the far right for the product in question. The :guilabel:`Detailed Operations` window appears, and displays the lot or serial numbers selected for that specific product for the delivery order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:211
msgid "0000002"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:211
msgid "11/30/2019"
msgid "FIFO (First In, First Out)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:213
msgid "0000003"
msgid "The :abbr:`FIFO (First In, First Out)` removal strategy implies that products which enter a warehouse's stock first are removed first. Companies should use this method if they are selling products with short demand cycles, such as clothes, to ensure they are not stuck with outdated styles in stock."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:213
msgid "10/31/2019"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:216
msgid "When we realize a sale for 25 units of Hand Cream, we can see that the lot numbers which have been automatically reserved by Odoo are the ones with the closest expiration date, meaning 0000001 and 0000003."
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:218
msgid "In this example, there are three lots of white shirts. The shirts are from the *All/Clothes* category, where *FIFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "two hand cream lots reserved for sell with the FEFO strategy."
msgid "View of the lots of white shirts in the inventory valuation report."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:226
msgid "Lot `000001` contains five shirts, lot `000002` contains three shirts, and lot `000003` contains two shirts."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:229
msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`White Shirt`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (for this example, `6.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:236
msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the oldest lot numbers will be reserved thanks to the :abbr:`FIFO (First In, First Out)` strategy. All five shirts from lot `000001` and one shirt from lot `000002` will be selected to be sent to the customer."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "Two lots being reserved for a sales order with the FIFO strategy."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:246
msgid "LIFO (Last In, First Out)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:248
msgid "The :abbr:`LIFO (Last In, First Out)` removal strategy works in the **opposite** manner from the :abbr:`FIFO (First In, First Out)` strategy. With this method, the products that are received **last** are moved out first. This method is mostly used for products without a shelf life, and no time-sensitive factors, such as expiration dates."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:253
msgid "In this example, there are three lots of cinder blocks. The blocks are from the *All/Building Materials* category, where *FIFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "View of the lots of cinder blocks in the inventory valuation report."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:261
msgid "Lot `000020` contains three cinder blocks, lot `000030` contains five cinder blocks, and lot `0000400` contains four cinder blocks."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:264
msgid "To see how the :abbr:`LIFO (Last In, First Out)` strategy works, first navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`, and select a product category (for this example, the :guilabel:`All/Building Materials` category) to edit. This reveals a product category form."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:269
msgid "Once on the product category form, under the :guilabel:`Logistics` section, change the :guilabel:`Force Removal Strategy` to :guilabel:`Last In First Out (LIFO)`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "Last in first out (LIFO) strategy set up as forced removal strategy."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:276
msgid "To see the removal strategy in action, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`Cinder Block`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (for this example, `5.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:283
msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the newest lot numbers will be reserved thanks to the :abbr:`LIFO (Last In, First Out)` strategy. All four cinder blocks from lot `0000400` and one cinder block from lot `000030` will be selected to be sent to the customer."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "Two lots being reserved for sale with the LIFO strategy."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:295
msgid "FEFO (First Expired, First Out)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:297
msgid "The :abbr:`FEFO (First Expired, First Out)` removal strategy differs from the :abbr:`FIFO (First In, First Out)` and :abbr:`LIFO (Last In, First Out)` strategies, because it targets products for removal based on **expiration dates** instead of their warehouse receipt dates. With this method, the products that are going to expire first are moved out first. This method is used for perishable products, such as medicine, food, and beauty products."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:303
msgid "Lots are picked based on their **removal date** from earliest to latest. Removal dates indicate how many days *before* the expiration date the product needs to be removed from stock. The removal date is set on the product form. Lots without a removal date defined are picked after lots with removal dates."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:309
msgid "If products are not removed from stock when they should be, lots that are past the expiration date may still be picked for delivery orders!"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:313
msgid "For more information about expiration dates, reference the :doc:`Expiration dates </applications/inventory_and_mrp/inventory/management/lots_serial_numbers/expiration_dates>` document."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:317
msgid "First, go to :menuselection:`Inventory app --> Configuration --> Settings` and ensure :guilabel:`Expiration Dates` is enabled. Once the :guilabel:`Expiration Dates` setting is enabled, it's possible to define different expiration dates for individual serialized products, as well as for lot numbers containing many products."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:322
msgid "In this example, there are three lots of hand cream. The creams are from the *All/Health & Beauty* category, where *FEFO* is set as the removal strategy. In the :guilabel:`Inventory Valuation Report`, the three different receipts are listed with the amounts."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:326
msgid "Lot `0000001` contains twenty tubes of hand cream, expiring on Sept 30, lot `0000002` contains ten tubes of hand cream, expiring on November 30, and lot `0000003` contains ten tubes of hand cream, expiring on October 31."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "View the hand cream lot numbers and expiration dates in the inventory report."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:334
msgid "Expiration dates can be entered when validating the received products, or set on products by going to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Click :guilabel:`Create`, enter the serial number, and select the product from the drop-down menu. Next, select the expiration date in the :guilabel:`Dates` tab. Finally, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "View of the removal date for 0000001."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:343
msgid "To see how the :abbr:`FEFO (First Expired, First Out)` strategy works, first navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`, and select a product category (in this example, the :guilabel:`All/Health & Beauty` category) to edit. This reveals a product category form."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:348
msgid "Once on the product category form, under the :guilabel:`Logistics` section, change the :guilabel:`Force Removal Strategy` to :abbr:`FEFO (First Expired, First Out)`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "FEFO forced removal strategy set on the product category."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:355
msgid "Next, go to the :menuselection:`Sales app` and click :guilabel:`Create` to create a sales order. Next, select a :guilabel:`Customer` from the drop-down menu. Then click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Select a product (for this example, the :guilabel:`Hand Cream`) from the drop-down menu, or type in the name of the product in the field. Enter a quantity (in this example, `25.00`) in the :guilabel:`Quantity` field, then click :guilabel:`Save`, then click :guilabel:`Confirm`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:362
msgid "Once the sales order is confirmed, the delivery order will be created and linked to the picking, and the lot numbers expiring first will be reserved thanks to the :abbr:`FEFO (First Expired, First Out)` strategy. All twenty tubes of hand cream from lot `0000001` and five from lot `0000003` will be selected to be sent to the customer, detailed in the :guilabel:`Detailed Operations` tab in the :guilabel:`Sales Order`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:-1
msgid "Hand cream lot numbers selected for the sales order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping.rst:5

76
locale/sources/productivity.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-11 14:17+0000\n"
"POT-Creation-Date: 2023-10-26 05:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -245,46 +245,46 @@ msgid "To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure acco
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:19
msgid "Refer to `Microsoft's documentation <https://docs.microsoft.com/en-us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ on how to set up an Azure AD Tenant (also called an *environment*), which is a representation of an organization to manage and register apps."
msgid "Refer to `Microsoft's documentation <https://docs.microsoft.com/en-us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ on how to set up an Microsoft Entra ID (formally called *Microsoft Azure Active Directory (Azure AD)*), which is a representation of an organization to manage and register apps."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:23
msgid "Then, `Register an Application <https://docs.microsoft.com/en-us/azure/active-directory/develop/ quickstart-register-app>`_, choosing the appropriate :guilabel:`Supported account type`. Users who wish to connect their Outlook calendar to Odoo should select the :guilabel:`Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported account types`."
#: ../../content/applications/productivity/calendar/outlook.rst:24
msgid "Then, `Register an Application <https://docs.microsoft.com/en-us/azure/active-directory/develop/ quickstart-register-app>`_, choosing the appropriate :guilabel:`Supported account type`. Users who wish to connect their Outlook calendar to Odoo should select the :guilabel:`Accounts in any organizational directory (Any Microsoft Entra ID directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported account types`."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:29
#: ../../content/applications/productivity/calendar/outlook.rst:30
msgid "When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and copy the Odoo database URI (URL) followed by `/microsoft_account/authentication`."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:33
#: ../../content/applications/productivity/calendar/outlook.rst:34
msgid "Enter `https://www.companyname.odoo.com/microsoft_account/authentication` for the :guilabel:`Redirect URI`."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:-1
msgid "The \"Supported account type\" and \"Redirect URI\" settings in the Microsoft Azure AD portal."
msgid "The \"Supported account type\" and \"Redirect URI\" settings in the Microsoft Entra ID portal."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:40
#: ../../content/applications/productivity/calendar/outlook.rst:41
msgid "For more information on the restrictions and limitations of URIs, `check this page <https://docs. microsoft.com/en-us/azure/active-directory/develop/reply-url>`_."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:43
#: ../../content/applications/productivity/calendar/outlook.rst:44
msgid "Regarding the application credentials, the user *must* add a client secret, which allows Odoo to authenticate itself, requiring no interaction from the user's side. :guilabel:`Certificates` are optional."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:47
#: ../../content/applications/productivity/calendar/outlook.rst:48
msgid "To do add a client secret, click :guilabel:`Add a certificate or secret` and then click :guilabel:`New client secret`. Next, type a :guilabel:`Description` and select when the client secret :guilabel:`Expires`."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:51
#: ../../content/applications/productivity/calendar/outlook.rst:52
msgid "Since resetting the synchronization can be tricky, Odoo recommends setting the maximum allowed expiration date for the client secret (24 months), so there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to generate the client secret (:guilabel:`Secret ID`)."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:56
#: ../../content/applications/productivity/calendar/outlook.rst:57
msgid "Configuration in Odoo"
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:58
#: ../../content/applications/productivity/calendar/outlook.rst:59
msgid "In the Odoo database, go to :menuselection:`Settings --> General Settings --> Integrations` and activate the :guilabel:`Outlook Calendar` setting."
msgstr ""
@ -292,7 +292,7 @@ msgstr ""
msgid "The \"Outlook Calendar\" setting activated in Odoo."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:65
#: ../../content/applications/productivity/calendar/outlook.rst:66
msgid "From the Microsoft Azure portal, under the :guilabel:`Overview` section of the application, copy the :guilabel:`Application (Client) ID`, and paste it into the :guilabel:`Client ID` field in Odoo."
msgstr ""
@ -300,7 +300,7 @@ msgstr ""
msgid "The \"Client ID\" in the Microsoft Azure portal."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:72
#: ../../content/applications/productivity/calendar/outlook.rst:73
msgid "In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` section, copy the :guilabel:`Client Secret Value` and paste it into the :guilabel:`Client Secret` field in Odoo."
msgstr ""
@ -308,67 +308,67 @@ msgstr ""
msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:79
#: ../../content/applications/productivity/calendar/outlook.rst:80
msgid "Finally, on the Odoo :menuselection:`Settings --> General Settings` page, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:84
#: ../../content/applications/productivity/calendar/outlook.rst:85
msgid "Sync with Outlook"
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:88
#: ../../content/applications/productivity/calendar/outlook.rst:89
msgid "Odoo highly recommends testing the Outlook calendar synchronization on a test database and a test email address (that is not used for any other purpose) before attempting to sync the desired Outlook Calendar with the user's production database."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:92
#: ../../content/applications/productivity/calendar/outlook.rst:93
msgid "If the user has any past, present, or future events on their Odoo calendar before syncing their Outlook calendar, Outlook will treat the events pulled from Odoo's calendar during the sync as new events, causing an email notification to be sent from Outlook to all the event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:96
#: ../../content/applications/productivity/calendar/outlook.rst:97
msgid "To avoid unwanted emails being sent to all past, present, and future event attendees, the user must add the events from the Odoo calendar to the Outlook calendar before the first ever sync, delete the events from Odoo, and then start the sync."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:100
#: ../../content/applications/productivity/calendar/outlook.rst:101
msgid "Even after synchronizing the Odoo Calendar with the Outlook calendar, Outlook will still send a notification to all event participants every time an event is edited (created, deleted, unarchived, or event date/time changed), with no exceptions. This is a limitation that cannot be fixed from Odoo's side."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:105
#: ../../content/applications/productivity/calendar/outlook.rst:106
msgid "After one user syncs their Outlook calendar to the Odoo database, unwanted email notifications are unavoidable because the first synchronized user's events will be in the Odoo Calendar. If the Odoo database is shared amongst multiple users, and another user wants to sync their Outlook calendar with Odoo Calendar, Outlook will again pull the existing Odoo Calendar events during the sync and treat them as new events, causing Outlook to send email invitations to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:112
#: ../../content/applications/productivity/calendar/outlook.rst:113
msgid "In summary, once a user synchronizes their Outlook calendar with the Odoo calendar:"
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:114
#: ../../content/applications/productivity/calendar/outlook.rst:115
msgid "Creating an event in Odoo causes Outlook to send an invitation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:115
#: ../../content/applications/productivity/calendar/outlook.rst:116
msgid "Deleting an event in Odoo causes Outlook to send a cancellation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:116
#: ../../content/applications/productivity/calendar/outlook.rst:117
msgid "Unarchiving an event in Odoo causes Outlook to send an invitation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:117
#: ../../content/applications/productivity/calendar/outlook.rst:118
msgid "Archiving an event in Odoo causes Outlook to send a cancellation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:118
#: ../../content/applications/productivity/calendar/outlook.rst:119
msgid "Adding a contact to an event causes Outlook to send an invitation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:119
#: ../../content/applications/productivity/calendar/outlook.rst:120
msgid "Removing a contact from an event causes Outlook to send a cancellation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:122
#: ../../content/applications/productivity/calendar/outlook.rst:123
msgid "Sync Odoo Calendar and Outlook"
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:124
#: ../../content/applications/productivity/calendar/outlook.rst:125
msgid "In the Odoo database, go to the :guilabel:`Calendar` module and click the :guilabel:`Outlook` sync button. The page will redirect to a Microsoft login page, and the user is asked to log in to their account, if they are not already, and grant the required permissions."
msgstr ""
@ -376,19 +376,19 @@ msgstr ""
msgid "The \"Outlook\" sync button in Odoo Calendar."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:132
#: ../../content/applications/productivity/calendar/outlook.rst:133
msgid "The synchronization is a two-way process, meaning that events are reconciled in both accounts (Outlook and Odoo)."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:136
msgid "All users that want to use the synchronization simply need to :ref:`sync their calendar with Outlook <outlook/sync>`. The configuration of Microsoft's Azure account is only done once, as Azure AD tenants' Client IDs and Client Secrets are unique, and represent an organization that helps the user to manage a specific instance of Microsoft cloud services for their internal and external users."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:143
msgid ":doc:`../../sales/crm/optimize/outlook_extension`"
#: ../../content/applications/productivity/calendar/outlook.rst:137
msgid "All users that want to use the synchronization simply need to :ref:`sync their calendar with Outlook <outlook/sync>`. The configuration of Microsoft's Azure account is only done once, as Microsoft Entra ID tenants' Client IDs and Client Secrets are unique, and represent an organization that helps the user to manage a specific instance of Microsoft cloud services for their internal and external users."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:144
msgid ":doc:`../../sales/crm/optimize/outlook_extension`"
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:145
msgid ":doc:`google`"
msgstr ""