# SOME DESCRIPTIVE TITLE. # Copyright (C) 2015-TODAY, Odoo S.A. # This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # # Translators: # Morten Schou , 2020 # Martin Trigaux, 2021 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2021-02-11 09:05+0100\n" "PO-Revision-Date: 2020-09-22 14:41+0000\n" "Last-Translator: Martin Trigaux, 2021\n" "Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: da\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #: ../../purchase.rst:5 msgid "Purchase" msgstr "Indkøb" #: ../../purchase/advanced.rst:3 msgid "Advanced" msgstr "Avanceret" #: ../../purchase/advanced/analyze.rst:3 msgid "Analyze the performance of your purchases" msgstr "" #: ../../purchase/advanced/analyze.rst:5 msgid "" "If your company regularly purchases products, you have several reasons to " "track and analyze your performance. The insights gathered can help you to " "better forecast and plan your future orders. For example, you can assess if " "your business is dependent on particular vendors, and the data can help you " "negotiate discounts on prices." msgstr "" #: ../../purchase/advanced/analyze.rst:11 msgid "Generate customized reports" msgstr "" #: ../../purchase/advanced/analyze.rst:13 msgid "" "Go to *Reporting* to access the purchase analysis. Simply by accessing the " "reporting dashboard, you can get a quick overview of your actual " "performance. By default, the reporting dashboard displays a line chart " "presenting the untaxed amount of your purchase orders per day, and below it," " key metrics and a pivot table." msgstr "" #: ../../purchase/advanced/analyze.rst:22 msgid "" "While the data initially presented is useful, there are several tools and " "features you can use to get even more insights on your purchases." msgstr "" #: ../../purchase/advanced/analyze.rst:26 msgid "Use filters to select the data you need" msgstr "" #: ../../purchase/advanced/analyze.rst:28 msgid "" "Odoo offers several default filters you can use and combine by clicking on " "*Filters*. When you select one or several filters, Odoo looks for all the " "orders that match at least one of the filters you have chosen and populates " "the chart, key metrics, and pivot table with the data. The pre-configured " "filters are:" msgstr "" #: ../../purchase/advanced/analyze.rst:33 msgid "All *Requests for Quotation*" msgstr "" #: ../../purchase/advanced/analyze.rst:35 msgid "All *Purchase Orders*, except canceled ones" msgstr "" #: ../../purchase/advanced/analyze.rst:37 msgid "" "*Confirmation Date Last Year* includes all orders that were confirmed the " "previous year, canceled purchase orders included" msgstr "" #: ../../purchase/advanced/analyze.rst:40 msgid "" "*Order Date* includes all orders - request for quotations and purchases " "orders (canceled ones included) - depending on their date of creation" msgstr "" #: ../../purchase/advanced/analyze.rst:43 msgid "" "*Confirmation Date* includes all confirmed orders, canceled ones included, " "depending on their date of confirmation" msgstr "" #: ../../purchase/advanced/analyze.rst:47 msgid "" "When you have to select a period, you can use multiple years, and, with at " "least one year selected, multiple quarters and the three most recent months." msgstr "" #: ../../purchase/advanced/analyze.rst:51 msgid "" "If you use the *Order Date* or *Confirmation Date* filters, the *Comparison*" " feature appears next to *Filters*. It enables you to compare the period you" " filtered with the previous one." msgstr "" #: ../../purchase/advanced/analyze.rst:59 msgid "Add custom filters" msgstr "" #: ../../purchase/advanced/analyze.rst:61 msgid "" "Thanks to the 31 filtering options to choose from, the possibilities of your" " customizing your dataset are almost limitless. Go to " ":menuselection:`Filters --> Add Custom Filter`, specify the condition the " "filtering option should meet (e.g. *is equal to*, *contains*, etc.), and " "click on *Apply*. If you want to select orders matching several conditions " "simultaneously (*and* operator), repeat the process to add another custom " "filter. If you want to use the *or* operator, don't click on *Apply*, and " "click on *Add a condition* instead. Once you have added all the desired " "filtering options, click on *Apply*." msgstr "" #: ../../purchase/advanced/analyze.rst:74 msgid "" "To avoid having to recreate custom filters every time, save them by clicking" " on :menuselection:`Favorites --> Save current search --> Save`. The " "customized search filter can then be accessed by clicking on *Favorites* or " "can even be set as the default filter when you open the reporting dashboard." msgstr "" #: ../../purchase/advanced/analyze.rst:80 msgid "Measure exactly what you need" msgstr "" #: ../../purchase/advanced/analyze.rst:82 msgid "" "Before selecting what you want to measure, you need to decide whether you " "prefer using the graph view or the pivot view. By default, the dashboard " "presents both views. However, the measures you select won't be applied to " "both views. You can access each view separately by clicking on the icons at " "the top right of the dashboard." msgstr "" #: ../../purchase/advanced/analyze.rst:92 msgid "Visualize your data" msgstr "" #: ../../purchase/advanced/analyze.rst:94 msgid "" "You can transform the main graph in just a click by selecting one of the " "three charts: bar, line or pie. Fourteen different measures are available, " "but you can only use one at a time. However, you can group the measure using" " one or several of the 19 *Groups*." msgstr "" #: ../../purchase/advanced/analyze.rst:102 msgid "" "For bar and line charts, the selected measure is your y-axis, and the first " "group you select is used to create the x-axis. Adding more group adds " "additional lines (line chart) or transforms your bar chart into a stacked " "bar chart. For pie charts, the more groups you select, the more slices are " "displayed." msgstr "" #: ../../purchase/advanced/analyze.rst:108 msgid "Explore your data" msgstr "" #: ../../purchase/advanced/analyze.rst:110 msgid "" "The pivot table view enables you to explore your data in great detail. " "Unlike the graph view, the pivot table enables you to add several measures " "at the same time. By clicking on *Measures* or on the **+** sign in the " "*Total* column, you can add as many as you want, each assigned to a new " "column. By clicking on the **+** sign in the *Total* row, you can add " "*Groups*. If you click on a group's **+** sign, you can add a sub-group, and" " so on." msgstr "" #: ../../purchase/advanced/analyze.rst:121 msgid "" "You can insert your pivot table's data directly in the Spreadsheet app or " "export it as an Excel file." msgstr "" #: ../../purchase/manage_deals.rst:3 msgid "Manage deals" msgstr "" #: ../../purchase/manage_deals/agreements.rst:3 msgid "Purchase agreements: blanket orders and calls for tenders" msgstr "" #: ../../purchase/manage_deals/agreements.rst:5 msgid "" "There are two main types of purchase agreements preconfigured in Odoo: " "blanket orders and call for tenders." msgstr "" #: ../../purchase/manage_deals/agreements.rst:8 msgid "" "Blanket orders are long-term agreements between a company and a vendor to " "deliver products on a recurring basis with predetermined pricing. Your " "company should consider using them when you frequently purchase the same " "products from the same vendor in varying quantities and/or at different " "times. Among their many benefits, you can save time as the ordering process " "is simplified, and money thanks to more advantageous bulk pricing." msgstr "" #: ../../purchase/manage_deals/agreements.rst:14 msgid "" "Calls for tenders use a special procedure to request offers from multiple " "vendors at the same time. While public sector organizations are often " "legally bound to release calls for tenders when they want to purchase goods " "or services, private organizations can also use them to get the best deal " "among several vendors." msgstr "" #: ../../purchase/manage_deals/agreements.rst:20 msgid "Enable purchase agreements" msgstr "" #: ../../purchase/manage_deals/agreements.rst:22 msgid "" "From the Purchase app, go to :menuselection:`Configuration --> Settings` and" " activate *Purchase Agreements*." msgstr "" #: ../../purchase/manage_deals/agreements.rst:30 msgid "Configure or create new types of purchase agreements" msgstr "" #: ../../purchase/manage_deals/agreements.rst:32 msgid "" "Before you start using purchase agreements, make sure they are configured " "the way you want by going to :menuselection:`Configuration --> Purchase " "Agreement Types`. From there, you can edit the way blanket orders and calls " "for tenders or *Create* a new type of purchase agreement. You can configure " "the:" msgstr "" #: ../../purchase/manage_deals/agreements.rst:37 msgid "Agreement Type: the name you want to give to the agreement." msgstr "" #: ../../purchase/manage_deals/agreements.rst:39 msgid "" "Agreement Selection Type: you can either select multiple offers using " "*Select multiple RFQ (non-exclusive)*, which is the default setting for both" " blanket orders and calls for tenders, or a single offer using *Select only " "one RFQ (exclusive)*, which is sometimes needed for calls for tenders where " "you only want to select a single vendor." msgstr "" #: ../../purchase/manage_deals/agreements.rst:44 msgid "" "Lines: generally, you would always want to select *Use lines of agreement*, " "which are the different product lines you can configure when you set up your" " purchase agreement. However, you can select *Do not create RfQ lines " "automatically* if you don't want your requests for quotations to be pre-" "filled in with that information." msgstr "" #: ../../purchase/manage_deals/agreements.rst:49 msgid "" "Quantities: if you use lines of agreements, you can also specify " "independently if the products' quantities should be used to pre-fill new " "requests for quotations. The default option for blanket orders is *Set " "quantities manually*, while for calls for tenders are set to *Use quantities" " of agreement*." msgstr "" #: ../../purchase/manage_deals/agreements.rst:59 msgid "Set up a blanket order" msgstr "" #: ../../purchase/manage_deals/agreements.rst:61 msgid "" "Go to :menuselection:`Orders --> Purchase Agreements` and click on *Create*." " Select *Blanket Order* as your *Agreement Type*. Next, select the vendor. " "The other fields aren't mandatory, but you usually want to define an " "*Agreement Deadline* after which the blanket order won't be valid anymore." msgstr "" #: ../../purchase/manage_deals/agreements.rst:65 msgid "" "Next, add the products you want to order and their price. Note that you can " "also add a *Quantity* for each product, for example, if you have agreed with" " your vendor to order a specific minimum quantity each time or in total. If " "you have configured your blanked order to *Set quantities manually*, this is" " only used for informational purposes." msgstr "" #: ../../purchase/manage_deals/agreements.rst:74 msgid "" "You can also write any *Terms and Conditions* at the bottom of the " "agreement. Once you are satisfied with your blanket order, click on " "*Confirm*. Its status then changes from *Draft* to *Ongoing* and it's ready " "to be used." msgstr "" #: ../../purchase/manage_deals/agreements.rst:79 msgid "Create requests for quotation from the blanket order" msgstr "" #: ../../purchase/manage_deals/agreements.rst:81 msgid "" "You can now create new quotations from the blanket order whenever you need " "it by clicking on *New Quotation*. Odoo automatically fills in requests for " "quotation with the information initially defined when you set up the blanket" " order. Depending on the way you configured the *Purchase Agreement Type*, " "product lines can also be pre-filled." msgstr "" #: ../../purchase/manage_deals/agreements.rst:86 msgid "" "From here, you can quickly view all the requests for quotations made under " "that blanket order by clicking on *RFQs/Orders*." msgstr "" #: ../../purchase/manage_deals/agreements.rst:94 msgid "" "You can also create a *Request for Quotation* the usual way and then link it" " to an existing *Blanket Order*." msgstr "" #: ../../purchase/manage_deals/agreements.rst:98 msgid "Blanket orders and replenishment" msgstr "" #: ../../purchase/manage_deals/agreements.rst:100 msgid "" "Blanket orders can be used for :doc:`automated replenishment " "<../../purchase/products/reordering>`, as once a blanket order is confirmed," " a new vendor line is added to your product. Make sure the related vendor is" " in the first position if you have several vendors linked to your product." msgstr "" #: ../../purchase/manage_deals/agreements.rst:109 msgid "Set up a call for tenders" msgstr "" #: ../../purchase/manage_deals/agreements.rst:111 msgid "" "Go to :menuselection:`Orders --> Purchase Agreements` and click on *Create*." " Select *Call for Tenders* as your *Agreement Type*. The other fields aren't" " mandatory, but you can add the date you want to be delivered and set an " "agreement deadline. You usually don't want to select a vendor for calls for " "tenders as you are looking to get quotations from multiple vendors." msgstr "" #: ../../purchase/manage_deals/agreements.rst:116 msgid "" "Next, add the products you want to order and in what quantity. For calls for" " tenders, you typically don't add a price, as the vendors should give you " "their best quote." msgstr "" #: ../../purchase/manage_deals/agreements.rst:119 msgid "" "You can also write any *Terms and Conditions* at the bottom of the " "agreement. Once you are ready, click on *Confirm*." msgstr "" #: ../../purchase/manage_deals/agreements.rst:127 msgid "Requests quotations from the call for tenders" msgstr "" #: ../../purchase/manage_deals/agreements.rst:129 msgid "" "You can now request new quotations from the call for tenders. Click on *New " "Quotation* and select one of your vendors you want to invite to the call for" " tenders. Product lines should also be pre-filled in, depending on how you " "configured the *Purchase Agreement Type*. Click on *Send by email* to send " "it to the vendor. Go back to the call for tenders and repeat this process " "for each vendor." msgstr "" #: ../../purchase/manage_deals/agreements.rst:139 msgid "" "Once you have sent a request for quotation to every vendor and receiving " "their quotes, click on *Validate* to proceed to the bid selection. Next, " "click on the RFQs/Orders smart button to view all your vendors' quotations." msgstr "" #: ../../purchase/manage_deals/agreements.rst:147 msgid "" "Click on each request for quotation to add the price communicated by your " "vendors manually. When that's done, select the most advantageous offer and " "click on *Confirm Order*. This automatically closes the call for tenders. " "You can now proceed with the purchase order as you would for a regular one." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:3 msgid "Control and know when vendor bills should be paid" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:5 msgid "" "With Odoo, you can define how your vendor bills are controlled. For each " "purchase order, you can decide when the related vendor bill should be paid: " "either before or after you have received your products. You can also check " "at a glance what is the billing status of each purchase order." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:9 msgid "" "With the 3-way matching feature, Odoo compares the information appearing on " "the *Purchase Order*, the *Vendor Bill* and the *Receipt*, and lets you know" " if you should pay the bill. This way you can avoid paying incorrect or " "fraudulent vendor bills." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:14 msgid "Vendor bills default control policy" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:16 msgid "" "As a first step, open your Purchase app and go to " ":menuselection:`Configuration --> Settings` to set the default bill control " "policy for all the products created onwards." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:23 msgid "" "By selecting *On ordered quantities*, you can create a vendor bill as soon " "as you confirm an order. The quantities mentioned in the purchase order are " "used to generate the draft bill." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:26 msgid "" "If you choose *On received quantities* instead, you can only create one once" " you have at least received some of the products you have ordered. The " "quantities you have received are used to generate the draft bill. If you try" " to create one without having received any product, you get an error " "message." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:36 msgid "Change a specific product's control policy" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:38 msgid "" "If you want to modify a specific product's control policy, go to " ":menuselection:`Products --> Products`, open it, click on *Edit* and go to " "the *Purchase tab*. There you can change a product's default bill control " "policy." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:47 msgid "View a purchase order's billing status" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:49 msgid "" "Once you confirm an order, you can view its *Billing Status* by going to the" " *Other Information* tab." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:56 msgid "" "Below you can find a list of the different *Billing Status*, and when they " "are displayed, depending on the products' bill control policy." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:60 msgid "**Billing status**" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:60 msgid "**Conditions**" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:62 msgid "*On received quantities*" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:62 msgid "*On ordered quantities*" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:64 msgid "*Nothing to Bill*" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:64 msgid "PO confirmed; no products received" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:64 msgid "*(Not applicable)*" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:66 msgid "*Waiting Bills*" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:66 msgid "All/some products received; bill not created" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:66 msgid "PO confirmed" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:68 msgid "*Fully Billed*" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:68 msgid "All/some products received; draft bill created" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:68 msgid "Draft bill created" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:72 msgid "Determine when to pay with 3-way matching" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:74 msgid "" "First, go to :menuselection:`Configuration --> Settings` and activate *3-way" " matching*." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:81 msgid "" "3-way matching is intended to work with the bill control policy set to *On " "received quantities*." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:84 msgid "Should I pay the vendor bill?" msgstr "" #: ../../purchase/manage_deals/control_bills.rst:86 msgid "" "With the feature activated, your vendor bills now display the *Should Be " "Paid* field under the *Other info* tab." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:93 msgid "" "As you can't create a bill until you have received your products - and if " "you haven't received all of them, Odoo only includes the products you have " "received in the draft bill - the *Should Be Paid* status is set to *Yes* " "when you create one." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:97 msgid "" "If you edit a draft bill to increase the billed quantity, change the price, " "or add other products, the *Should Be Paid* status is set to *Exception*. It" " means Odoo notices the discrepancy, but that you might have a valid reason " "to have done so." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:101 msgid "" "Once the payment has been registered and mentions *Paid*, the *Should Be " "Paid* status is set to *No*." msgstr "" #: ../../purchase/manage_deals/control_bills.rst:109 msgid "" "The *Should Be Paid* status is set automatically by Odoo. However, you can " "change the status manually when you are viewing a bill in edit mode." msgstr "" #: ../../purchase/products.rst:3 msgid "Products" msgstr "Varer" #: ../../purchase/products/reordering.rst:3 msgid "Don’t run out of stock with reordering rules" msgstr "" #: ../../purchase/products/reordering.rst:5 msgid "" "To make sure you never run out of stock, you can define *Reordering Rules* " "on products. Thanks to them, Odoo can help you replenish your stock " "automatically when it reaches set quantities or whenever a sales order is " "created." msgstr "" #: ../../purchase/products/reordering.rst:9 msgid "You need to install the *Inventory app* to use reordering rules." msgstr "" #: ../../purchase/products/reordering.rst:12 msgid "Configure your storable product" msgstr "" #: ../../purchase/products/reordering.rst:14 msgid "" "Open or create a product with its *Product Type* set to *Storable Product*." msgstr "" #: ../../purchase/products/reordering.rst:20 msgid "" "As you are purchasing this product from a vendor, go to the product's " "*Purchase tab* and add a vendor by clicking on *Add a line*. You can add " "multiple vendors, but make sure to order them correctly, since reordering " "rules always use the first vendor in a list. You can add a price, but it " "isn't necessary for the reordering rule to work. In addition, you can add a " "minimum quantity you must order to benefit from that price." msgstr "" #: ../../purchase/products/reordering.rst:27 msgid "" "If the quantity Odoo has to reorder doesn't match the minimum quantity " "specified, Odoo selects the next vendor on your list. If you don't have " "another vendor on your list, the reordering rule won't work. For that " "purpose, you can add the same vendor multiple times with different prices " "for different quantities." msgstr "" #: ../../purchase/products/reordering.rst:37 msgid "" "By default, a draft purchase order is created. However, if you have enabled " "*Purchase Agreements*, you can *Propose a call for tenders* instead as shown" " in the image above. For more information, see " ":doc:`../manage_deals/agreements`" msgstr "" #: ../../purchase/products/reordering.rst:41 msgid "" "Next, make sure the correct route is selected under the Inventory tab of " "your product. If you created your product within the Purchase app, the *Buy*" " route is selected by default. If you are looking to dropship your product, " "select *Dropship*." msgstr "" #: ../../purchase/products/reordering.rst:50 msgid "Set up your reordering rule" msgstr "" #: ../../purchase/products/reordering.rst:52 msgid "Open your product and click on the *Reordering Rules* button." msgstr "" #: ../../purchase/products/reordering.rst:58 msgid "" "Once you are on the product's reordering rules page, click on *Create*." msgstr "" #: ../../purchase/products/reordering.rst:61 msgid "" "You can access and create reordering rules from :menuselection:`Inventory " "--> Configuration --> Reordering Rules` and from :menuselection:`Inventory " "--> Operations --> Replenishment`. By default, the replenishment view " "presents a summary of all the products that you might need to purchase to " "fulfill your sales orders. From there, you can ask Odoo with a single click " "to order a product once or automate all orders for that product, future " "orders included." msgstr "" #: ../../purchase/products/reordering.rst:68 msgid "Define quantities" msgstr "" #: ../../purchase/products/reordering.rst:70 msgid "" "You can set a **minimum quantity** your stock should always have. Once set, " "if your stock goes below the minimum quantity, and if you selected the Buy " "route, a request for quotation is automatically generated to reach that " "minimum quantity, plus any additional quantity needed to fill in a sales " "order for example." msgstr "" #: ../../purchase/products/reordering.rst:75 msgid "" "If you set a **maximum quantity**, every time the product has to be " "replenished, enough products are reordered to reach the maximum quantity." msgstr "" #: ../../purchase/products/reordering.rst:78 msgid "" "If you want to order only the exact quantity needed to fill in a sales order" " for example, set both both the minimum and maximum quantity to **zero**. " "The quantity mentioned in the sales order is then used by the reordering " "rule." msgstr "" #: ../../purchase/products/reordering.rst:82 msgid "" "You can also add a **quantity multiple** to only order products in batches " "of a certain quantity. Click on the optional columns drop-down menu, and " "select *Multiple Quantity* to show the column. Bear in mind that you might " "go over the maximum quantity you set if your rule includes a quantity " "multiple, as Odoo orders enough products to reach the maximum quantity and " "respect the set quantity multiple." msgstr "" #: ../../purchase/products/reordering.rst:92 msgid "" "If you selected multiple routes for the same product under its Inventory " "tab, make sure to select your *Preferred Route* on your reordering rule by " "clicking on the optional columns drop-down menu, adding the *Preferred " "Route* column, and selecting the right route." msgstr "" #: ../../purchase/products/uom.rst:3 msgid "Purchase in different units of measure than sales" msgstr "" #: ../../purchase/products/uom.rst:5 msgid "" "When you purchase a product, it may happen that your vendor uses a different" " unit of measure than you do when you sell it. This can cause confusion " "between sales and purchase representatives. It is also time-consuming to " "convert measures manually every time. With Odoo, you can configure your " "product once and let Odoo handle the conversion." msgstr "" #: ../../purchase/products/uom.rst:10 msgid "Consider the following examples:" msgstr "" #: ../../purchase/products/uom.rst:12 msgid "" "You purchase orange juice from an American vendor, and they use **gallons**." " However, your customers are European and use **liters**." msgstr "" #: ../../purchase/products/uom.rst:15 msgid "" "You buy curtains from a vendor in the form of **rolls** and you sell pieces " "of the rolls to your customers using **square meters**." msgstr "" #: ../../purchase/products/uom.rst:19 msgid "Enable units of measure" msgstr "" #: ../../purchase/products/uom.rst:21 msgid "" "Open your Sales app and go to :menuselection:`Configuration --> Settings`. " "Under Product Catalog, enable *Units of Measure*." msgstr "" #: ../../purchase/products/uom.rst:29 msgid "Specify sales and purchase units of measure" msgstr "" #: ../../purchase/products/uom.rst:32 msgid "Standard units of measure" msgstr "" #: ../../purchase/products/uom.rst:34 msgid "" "A variety of units of measure are available by default in your database. " "Each belongs to one of the five pre-configured units of measure categories: " "*Length / Distance*, *Unit*, *Volume*, *Weight* and *Working Time*." msgstr "" #: ../../purchase/products/uom.rst:39 msgid "" "You can create your new units of measure and units of measure categories " "(see next section)." msgstr "" #: ../../purchase/products/uom.rst:41 msgid "" "To specify different units of measures for sales and purchases, open the " "Purchase app and go to :menuselection:`Products --> Products`. Create a " "product or select an existing one. Under the product's *General Information*" " tab, first select the *Unit of Measure* to be used for sales (as well as " "for other apps such as inventory). Then, select the *Purchase Unit of " "Measure* to be used for purchases." msgstr "" #: ../../purchase/products/uom.rst:47 msgid "" "Back to the first example, if you purchase orange juice from your vendor in " "**gallons** and sell it to your customers in **liters**, first select *L* " "(liters) as the *Unit of Measure*, and *gal (US)* (gallons) as the *Purchase" " Unit of Measure*, then click on *Save*." msgstr "" #: ../../purchase/products/uom.rst:56 msgid "Create new units of measure and units of measure categories" msgstr "" #: ../../purchase/products/uom.rst:58 msgid "" "Sometimes you need to create your own units and categories, either because " "the measure is not pre-configured in Odoo or because the units do not relate" " with each other (e.g. kilos and centimeters)." msgstr "" #: ../../purchase/products/uom.rst:62 msgid "" "If you take the second example where you buy curtains from a vendor in the " "form of **rolls** and you sell pieces of the rolls using **square meters**, " "you need to create a new *Units of Measure Category* in order to relate both" " units of measure." msgstr "" #: ../../purchase/products/uom.rst:66 msgid "" "To do so, go to :menuselection:`Configuration --> Units of Measure " "Categories`. Click on *Create* and name the category." msgstr "" #: ../../purchase/products/uom.rst:73 msgid "" "The next step is to create the two units of measures. To do so, go to " ":menuselection:`Configuration --> Units of Measure`." msgstr "" #: ../../purchase/products/uom.rst:76 msgid "" "First, create the unit of measure used as the reference point for converting" " to other units of measure inside the category by clicking on *Create*. Name" " the unit and select the units of measure category you just created. For the" " *Type*, select *Reference Unit of Measure for this category type*. Enter " "the *Rounding Precision* you would like to use. The quantity computed by " "Odoo is always a multiple of this value." msgstr "" #: ../../purchase/products/uom.rst:82 msgid "" "In the example, as you cannot purchase less than 1 roll and won't use " "fractions of a roll as a unit of measure, you can enter 1." msgstr "" #: ../../purchase/products/uom.rst:89 msgid "" "If you use a *Rounding Precision* inferior to 0.01, a warning message might " "appear stating that it is higher than the *Decimal Accuracy* and that it " "might cause inconsistencies. If you wish to use a *Rounding Precision* lower" " than 0.01, first :doc:`activate the Developer Mode " "<../../general/developer_mode/activate>`, then go to " ":menuselection:`Settings --> Technical --> Database Structure --> Decimal " "Accuracy`, select *Product Unit of Measure* and edit *Digits* accordingly. " "For example, if you want to use a rounding precision of 0.00001, set " "*Digits* to 5." msgstr "" #: ../../purchase/products/uom.rst:96 msgid "" "Next, create a second unit of measure, name it, and select the same units of" " measure category as your reference unit. As *Type*, select *Smaller* or " "*Bigger than the reference Unit of Measure*, depending on your situation." msgstr "" #: ../../purchase/products/uom.rst:100 msgid "" "As the curtain roll equals to 100 square meters, you should select " "*Smaller*." msgstr "" #: ../../purchase/products/uom.rst:102 msgid "" "Next, you need to enter the *Ratio* between your reference unit and the " "second one. If the second unit is smaller, the *Ratio* should be greater " "than 1. If the second unit is larger, the ratio should be smaller than 1." msgstr "" #: ../../purchase/products/uom.rst:106 msgid "For your curtain roll, the ratio should be set to 100." msgstr "" #: ../../purchase/products/uom.rst:112 msgid "" "You can now configure your product just as you would using Odoo's standard " "units of measure." msgstr ""