From f857c46d6a5dab6ddbef2d97b1742f46f2d50eae Mon Sep 17 00:00:00 2001 From: MAP English Services Date: Wed, 11 Feb 2026 16:45:20 -0300 Subject: [PATCH 01/13] Feature ETP-3185: Improve documentation. --- .../procurement-management/transactions.md | 134 +++++++++++------- 1 file changed, 80 insertions(+), 54 deletions(-) diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions.md index dedea28ce6..d39bae7475 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions.md @@ -577,94 +577,120 @@ This window allows the user to: ### Overview -The Purchase Invoice window allows the user to register and manage supplier's invoices. +The Purchase Invoice window is used to **create, register, and manage supplier invoices for purchased goods and services**. -This stage of the chain **usually comes after "Goods Receipts" booking and management**. +Purchase invoices are typically generated after the Goods Receipt is completed, ensuring that received quantities match the supplier’s billing information. -A purchase invoice is an itemized statement of the goods or services provided by a vendor or supplier. It indicates the quantity and price of each product or service provided or to be provided. +Invoices can be created in two ways: -Suppliers could send the corresponding purchase invoice/s together with the delivery note/s attached to the goods, that implies that Purchase Invoices can be automatically generated from the **Goods Receipt** window, but it is possible that this is not the case, therefore a Purchase Invoice can also be created from scratch in the **Purchase Invoice** window. +1. Automatically, from a related Goods Receipt -The purchase expenses can be recognized as soon as the purchase invoice is accounted, however if an expense deferred plan is configured, it is possible to defer the expense recognition as required. +2. Manually, by entering the invoice directly in this window -Supplier invoices can be registered, booked and managed in the header section of the **Purchase Invoice** window. +Each invoice defines the products or services, quantities, prices, taxes, and amounts to be paid to the supplier. + +When the invoice is accounted, the corresponding purchase expenses are recognized in accounting. If a deferred expense plan is configured, expense recognition can be distributed over time according to the defined schedule. ### Header -**Header** lists the main terms and conditions related to the purchase invoice. +The **Header** contains the basic information for a purchase invoice. In most cases you only need to select the Business Partner; the system will fill the rest from defaults and the selected partner. -!!! info - In the majority of cases, the main (and the only) field needed to create a new purchase invoice document is the Business Partner field. All other fields will be pre-filled automatically based on the selected Business Partner, logged in User preferences and other system default parameters. +![Purchase invoice window](../../../../assets/drive/1JvS1mOjiiyATJENTs5SuQIyEAr-UHmE3.png) -Some other fields to note are: +Fields to note: -- **Transaction document** defaulted as "AP Invoice" or purchase invoice *document type* which can be manually changed to either "AP Credit Memo" or "Reversed Purchase Invoice". - - "AP Credit Memo" and "Reversed Purchase Invoice" document types can be considered credit purchase invoices, the difference between them is that: - - "AP Credit Memo" type must contain either an "Invoiced Quantity" > 0 or "line Net Amounts" >0. - Above implies that invoices set as "Credit Memo" should not be related to "Orders" or "Shipments". - - "Reversed Purchase Invoice" type must contain either an "Invoiced Quantity" <0 or "line Net Amounts" < 0. These are the invoice types that can be related to return "Orders" or "Shipments". -- **Document No**. you could manually fill in the supplier's invoice number in this field, if the document sequence number associated with the transaction document "AP Invoice" is set up to allow you to do that; otherwise it will be automatically provided by the system as an "Internal" purchase invoice number. -- **Invoice Date**: the date the invoice is registered. It is used to calculate when the payment of the invoice is due. Defaults to the current date can always be changed. -- **Accounting Date**: the date to be used in the posting record of the Purchase Invoice to the general ledger. Defaults to the Invoice Date field can always be changed. -- **Payment Terms**: indicates **how** an invoice should be paid. Defaulted according to the Vendor/Creditor tab of the *Business Partner* window. -- **Payment Method**: defines **when** a purchase invoice needs to be paid. Defaulted according to the Vendor/Creditor tab of the *Business Partner* window. -- **Supplier Reference**: this is a not-mandatory field which can be used to enter the supplier invoice number. +- **Transaction document**: defaults to AP Invoice or purchase invoice [document type](../financial-management/accounting/setup/document-type.md). You can change it to AP Credit Memo (positive-credit type, not linked to orders/shipments) or Reversed Purchase Invoice (negative amounts, for returns). +- **Document No.**: supplier invoice number if allowed by sequence, otherwise an internal number is used. +- **Invoice Date**: date of the invoice (used to calculate due date). +- **Accounting Date**: posting date for the ledger (defaults to Invoice Date). +- **Payment Terms**: how the invoice will be paid. +- **Payment Method**: when the invoice will be paid. +- **Supplier Reference**: optional supplier reference number. -There are 3 ways of entering lines into the purchase invoice, two of them from the invoice header and the last one from the **Lines** tab: +How to add lines: -1. Selecting products from pending to be invoiced orders or receipts using the **Create Lines From Order** and **Create Lines From Receipt** buttons. -2. Copying all products from the chosen invoice selected in the history of all invoices for different business partners using the **Copy Lines** button. -3. Manually, line by line in the **Lines** tab. This option is used if the underlying document (Purchase Order or Goods Receipt) does not exist in the system prior invoicing takes place. +1. Use **Create Lines From Order** or **Create Lines From Receipt** to pull pending items. +2. Use **Copy Lines** to copy lines from an existing invoice. +3. Add lines manually in the **Lines** tab when there is no related order or receipt. -The **Complete** button finishes the creation of the invoice document with the fulfillment of the **Payment Plan** tab and the **Payment Monitor** section in the Header. If there are non-stockable BOM products in the lines and they have not been exploded, the Complete button will explode them automatically. +Complete and next steps: -Once completed, a purchase invoice can be: +- Click **Complete** to finish the invoice; this creates the Payment Plan and updates the Payment Monitor. Non-stockable BOMs will be exploded automatically if needed. -- **posted** to the ledger by using the button [Post](#post) -- **voided** by using the button [Reactivate](#reactivate) -- and **paid** by using the button [Add Payment](#add-payment). +After completion you can: -![Purchase invoice window](../../../../assets/drive/1JvS1mOjiiyATJENTs5SuQIyEAr-UHmE3.png) +- **Post** the invoice to the ledger with the [Post](#post) button. +- **Void/Reactivate** using [Reactivate](#reactivate). +- **Add Payment** with [Add Payment](#add-payment). ### Lines -Once the purchase invoice header has been properly filled in and saved purchase invoice lines can be registered in this tab. +Once the Purchase Invoice header is saved, add one or more invoice lines for the products or expenses being billed. -Lines list each product to be purchased and its characteristics. +Fields to note: +- **Financial Invoice Line**: Select this for lines that are not products (for example, a G/L item or an asset). The Product field is replaced by an Account field. +- **Attribute Set Value**: Shown if the product uses attributes (color, size, serial number, etc.). +- **Purchase Order Line / Goods Receipt Line**: Links the invoice line to the related PO or Goods Receipt line, if any. -The fields to note are: +Deferring expenses (optional): +- **Deferred Expense**: Check this to spread the expense over time and reveal the expense-plan fields. +- **Expense Plan Type**: Frequency of recognition (currently: monthly). +- **Period Number**: Number of periods to distribute the expense (e.g., enter 12 to spread over 12 months). For instance, if a company purchases business insurance for the duration of the year, the period number to enter would be 12 as the company would like to distribute that expense over 12 months. -- **Financial Invoice Line** is selected when the invoice line is not a product but an account not set up as a product but as a *G/L Item*, or an asset not set up as a product. - When selected, the product field disappears from the screen and an account field appears related to the purchase invoice line. -- **Attribute Set Value**: field is displayed if the product in the line has *attributes* (color, size, serial number or several of them together etc). -- **Purchase Order Line and Goods Receipt Line**: references to the purchase order and goods receipt line that is being invoiced. +- **Starting Period**: First open period when recognition begins. -As already mentioned, purchase expenses can be deferred therefore they are not recognized at the purchase accounting date but within a given number of accounting periods. +These expense-plan values can be defaulted from the product. If an expense plan is used, the invoice accounting will follow that plan. -When a purchase invoice line is created, it is possible to define at line level whether the line is going to cause the expense to be deferred. The relevant fields are: +**Explode Button** -- **Deferred Expense**: When this flag is checked, the Expense Plan field group becomes visible, allowing users to configure the next three fields. -- **Expense Plan Type**: This field specifies the frequency of the expense distribution which currently is "monthly". -- **Period Number**: This field specifies the duration of an expense plan. - For instance, if a company purchases business insurance for the duration of the year, the period number to enter would be 12 as the company would like to distribute that expense over 12 months. -- **Starting Period**: The first open period in which the expense is going to be recognized. +The **Explode** button appears when the selected line contains a non-stockable BOM product that hasn't been exploded yet. Exploding replaces the BOM line with its components in the invoice. This action cannot be undone — to revert it, delete the component lines first and then re-add the non-stockable BOM product. -These fields can be defaulted if configured for the *product*. +**Match LC Cost** -If an expense plan is configured, it implies a specific *purchase invoice accounting*. +The **Match LC Cost** button allows you to match the **estimated landed cost** defined in the **Landed Cost window** with the **invoiced landed cost** entered in an invoice line. -**Explode** button is shown when selecting a line with a non-stockable BOM product and the product is not already exploded. When exploding a product, the bill of materials components the selected product consists of are shown in the invoice. Once you have exploded it, you cannot comprime it. You should delete all the lines (first bill of materials components and then the BOM product), and insert again the non-stockable BOM product. +This option is available when the purchase order or invoice line contains a **product** or **account** configured as a **landed cost type**. -**Match LC Cost** button is shown when the purchase order line contains either an "account" or a "product" setup as *landed cost type*. +Both costs must belong to the **same landed cost type** to be matched. -This process button allows to **match** both the "**estimated**" landed cost booked in the *landed cost* window, and the one being **invoiced** in the invoice line. Both need to be of the very **same landed cost type**. +Matching helps to: -Once selected, **"Match LC Cost**" button opens the **"Match LC Cost" pick and edit window**. +- Reconcile estimated and invoiced landed costs +- Keep product costs accurate +- Generate the correct accounting entries -Only processed Landed Cost documents will be shown in this Window. It allows you to pick the corresponding landed cost, to enter an amount to match in the field "Matched Amt", and then to select the "**Process Matching**" check-box. +After clicking **Match LC Cost**, the **Match LC Cost** pick-and-edit window opens. -!!! warning - Note that if the "Process Matching" check-box is not selected here, landed cost matching will have to be processed in the *landed cost* window by using **Process Matching** button. +Only **processed Landed Cost documents** are displayed. + +From this window, you can: + +- Select the corresponding landed cost document +- Enter the amount in **Matched Amt** +- Enable **Process Matching** to complete the process immediately + +The **Is Matching Adjusted** checkbox controls how differences between estimated and invoiced costs are handled: + +- **Checked** → Creates an additional landed cost adjustment to update the product cost +- **Unchecked** → No cost adjustment is created + +**Scenarios** + +1. Estimated = Invoiced + +- Only matching is posted to the ledger +- No adjustments are created + +2. Estimated ≠ Invoiced + Adjustment enabled + +- A landed cost adjustment is created +- Product cost is updated to the invoiced amount +- Matching and adjustment are posted + +3. Estimated ≠ Invoiced + Adjustment disabled + +- Only matching is posted +- Product cost is not modified #### Line Tax From 37f5e9137bf35876c9650464a5079c356d95031f Mon Sep 17 00:00:00 2001 From: MAP English Services Date: Wed, 25 Feb 2026 16:52:23 -0300 Subject: [PATCH 02/13] Feature ETP-3185: Edit procurement management pages. --- .../procurement-management/transactions.md | 1388 ----------------- .../transactions/goods-receipt.md | 206 +++ .../transactions/landed-cost.md | 332 ++++ .../transactions/manage-requisitions.md | 73 + .../transactions/matched-purchase-invoices.md | 59 + .../transactions/pending-goods-receipts.md | 31 + .../transactions/purchase-invoice.md | 445 ++++++ .../transactions/purchase-order.md | 213 +++ .../transactions/requisition-to-order.md | 36 + .../transactions/requisition.md | 76 + .../transactions/return-to-vendor-shipment.md | 99 ++ .../transactions/return-to-vendor.md | 78 + mkdocs.yml | 13 +- 13 files changed, 1660 insertions(+), 1389 deletions(-) delete mode 100644 docs/user-guide/etendo-classic/basic-features/procurement-management/transactions.md create mode 100644 docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md create mode 100644 docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md create mode 100644 docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/manage-requisitions.md create mode 100644 docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.md create mode 100644 docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md create mode 100644 docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md create mode 100644 docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md create mode 100644 docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition-to-order.md create mode 100644 docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md create mode 100644 docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md create mode 100644 docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions.md deleted file mode 100644 index d39bae7475..0000000000 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions.md +++ /dev/null @@ -1,1388 +0,0 @@ ---- -title: Procurement Management - -tags: - - Procurement Process - - Purchase Requisitions - - Goods Receipts - - Purchase Orders ---- - -## Overview - -Procurement management deals with all the activities related to the purchase of goods and services from external suppliers and the corresponding reporting. - -The process starts by the creation and management of purchase requisitions and corresponding purchase orders to the moment the merchandise is received in the warehouse. - -## Requisition - -:material-menu: `Application` > `Procurement Management` > `Transactions` > `Requisition` - -A Requisition is a document that specifies a request to order products. - -The user can create requisitions and monitor them in this window: - -![Requisition window](../../../../assets/drive/1ihaEseE5RnNH7INNbaRLyvZC0P2q-hTl.png) - -### Header - -Requisition header allows entering the following data: - -- The business partner or supplier, this is an optional field that could be filled in by the requester in case it is known, therefore: - - The supplier entered in the header will be the one used for every requisition line unless it is changed at lines level for a particular line. - - If there is no supplier entered in the requisition header the one setup by default for the product in its master data window, *Purchasing* tab will be used. - - If there is no business partner or supplier in the header, or in the lines, or setup in the product, the user will have to enter it while creating the purchase order from the requisition. -- The purchase price list. This is also an optional field to be filled-in, in case it is known by the requester and its behaviour is the same as described above as it is linked to the Business Partner. - -Besides, the system populates the following data: - -- The document No., which is the Requisition number. -- The requester, which is the user entering the requisition. - -![Requisition](../../../../assets/drive/1G5HR3bMmJXW837o-6qzZ0CTe418q5JB7.png) - -The requester can then move to the "Lines" tab to enter additional data. - -### Lines - -Each requisition line shows a product demand for a specific date. - -Requisition "Lines" tab collects the following demand data: - -- The *need by date*, that is the date when the product is required to arrive. -- The *product*, items/products which need to be purchased. -- The *quantity* requested, or the *operative quantity* requested if the product has an *alternative unit of measure (AUM)* configured. -- The product's *UOM*, or product's *Alternative UOM* depending on product configuration in regards to measure unit. -- The *business partner:* This is an optional field the user can enter if the supplier entered at the requisition header needs to be changed for a particular line. - -!!! info - If there is not a supplier entered at the requisition header, neither at the requisition line, the supplier used will be the one setup by default for the product, therefore this field at line level can also be used to overwrite that defaulted one. - -- The *purchase price list*: This is also an optional field that can be entered if the price list entered at the header level or the default product price list information should be overwritten for a particular line. -- The *net list price*: This one is the price of the corresponding price list for a given date. It's an optional field that can be filled in automatically based on the price list entered at the header level or it could be overwritten by the user for a particular product line. -- The *net unit price:* This one can be either equal to the net list price or not, based on the formula: \[net unit price = net list price - discount\]. It is an optional field that can be filled in automatically based on the price list entered at the header level or it could be overwritten by the user for a particular product line. -- The *discount*, if any, is based on a used price list. - -![Requisition Lines](../../../../assets/drive/1CtrCvBCrvUuxYDlaFysmkKu0-0XhemfC.png) - -It is possible to enter as many requisition lines as products demand. - -The last step is to register the *Requisition* as *Complete* by using the header button "Complete", then: - -- *Requisition header status bar* informs us that the Requisition is *Completed*. -- *Requisition lines status bar* informs us that the *Matched purchase order quantity* for each line is equal to 0**, as there is no purchase order linked to each requisition line yet, and the requisition line/s status is *Open*. - -It is important to remark that *Requisitions* does not have any impact on: - -- Items quantity on hand -- Items costing - -## Manage Requisitions - -:material-menu: `Application` > `Procurement Management` > `Transactions` > `Manage Requisitions` - -Manage Requisitions window is intended to be used to provide an overall picture of the items needed. - -### Header - -This window allows the user to manage requisitions regardless of their current status, therefore they can change or close a requisition and create purchase orders for those demands. - -![Requisition window Header](../../../../assets/drive/1yuE4xa0usvVzSdmthjDWdi12OAqTuJTe.png) - -A **requisition** with status "Completed" **can always be changed**, if required. The user needs to reactivate it and then change it and book it. - -It is also possible to **close a requisition in case there is no need of the included item/s anymore**, by using the menu button "**Close**" and then select the action "**Close**". - -Requisition lines status will then be changed to "Cancelled". - -Finally, it is also possible to **create purchase orders** for those **requisitions in status "Complete"**, by using the menu button "**Create Purchase Order**". - -In this case, a new window is shown for the user to fill in some data by taking into account that: - -- If there are **different suppliers in the requisition lines as well as price list**: - - the **defaulted ones** entered in the window "Create Purchase Order" **will be the ones used** in the purchase order. -- If there are **different suppliers in the requisition lines as well as price list**, and the user does not enter any defaulted ones in the window "Create Purchase Order": - - **the ones in the requisition lines will be the ones used** in the purchase orders. -- If **all the requisition lines have the same supplier and price list**: - - **there will not be any need for selected defaulted ones** in the window "Create Purchase Order", besides only one purchase order will be created. - -![Purchase order](../../../../assets/drive/17OuNS8YpM0VC3MUkLO25DPPHCMwWjq8u.png) - -Etendo provides information about the purchase order/s number/s created after pressing the OK button in the "Create Purchase Order" window. - -This action links the requisition and the purchase order, and besides a purchase order line is created for each requisition line: - -- A **requisition** linked to a purchase order changes its status from **Completed** to **Closed**. -- A **requisition line** linked to a purchase order line changes its status from **Open** to **Closed**. - -Any **purchase order** created from a **Requisition**: - -- will be listed in the **"Purchase Order" window**. -- will have a "**Booked**" status -- and will contain **data inherited from the Requisition**, data such as: - - Order Date - - Scheduled Delivery Date - - Business Partner - - Price List - - Product/s - -### Lines - -The user can perform a set of actions regarding requisition lines. It is possible for them to either create lines or product demands or to cancel them. - -- **New product demands can be manually created** within a requisition by just **adding new requisition lines** before creating a purchase order. -- **Existing product demands or requisition lines can be cancelled**, if they are not required anymore, by using the header button "**Change Status**". - -#### Matched PO (Purchase order) Lines - -This tab allows the user to either review the purchase order line automatically linked to a requisition line or to manually link an existing purchase order line to the corresponding requisition line. - -## Requisition to Order - -:material-menu: `Application` > `Procurement Management` > `Transactions` > `Requisition to Order` - -Requisition to Order window shows all the "Completed" requisitions which match the criteria used in the "filter" section and it also shows the requisition lines selected as locked, therefore the same product demand can not be included more than once in a purchase order. - -![Requisition to order](../../../../assets/drive/1Xl_R8oaUrOaO0SK4wB5BYNw3wJDEjHBX.png) - -In other words, the upper section of this window shows the requisition lines found that are not linked to an order yet. -Those are the lines which can be added by the user to the "Lock" area in the bottom section of the window. - -A requisition line locked can not be changed by any other user, until the one who locked it gets it unlocked. -That way, during the time that the requisition lines are locked: - -- The same product demand will not be included in a purchase order, by mistake. -- The purchase team will have the opportunity to review the stock and contact different vendors if required to negotiate a price for the products. -- If there is no activity during 3 days, the system removes the lock from the lines. - -A requisition can be unlocked manually by the purchase manager or the one who locked it by moving it back to the upper part of the "Requisition to Order" screen by using the "Remove" button. - -Once the product demands are clear and locked, the last step to take in this window is to create a purchase order for those needs using the process button "Create". - -## Purchase Order - -:material-menu: `Application` > `Procurement Management` > `Transactions` > `Purchase Order` - -Purchase Order window allows the user to manage orders which once booked will be sent to the external suppliers. In other words, it is a document to register products and/or services to be purchased and documented. - -![Purchase order window](../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchaseorder.png) - -Once the document is booked, it can be sent to the external supplier and it can be prepaid if required. - -Purchase orders can be created and booked in the header section of the purchase order window. - -### Header - -The **Purchase order header** allows you to enter the following information: - -- **Organization:** Organizational entity within client. -- **Transaction Document**, which in this case is defaulted as "**Purchase Order**". -- **Document No**, or the Company purchase order number. -- **Order date:** This date is also defaulted by Etendo based on the system date, but it can always be changed. -- **Business Partner**: End-user needs to select the supplier to which the purchase order is being issued. -- **Partner Address**: Automatically populated once the business partner is selected based on the address or location set us "Ship to Address". -- **Warehouse**: Regardless it is defaulted by Etendo based on the "Profile" selected options, it must be verified by the end-user. -- **Scheduled Delivery Date**: This is the date when the organization or legal entity requires the items to be delivered. -- **Payment Method**, **Payment Terms** and **Price List**: These ones are defaulted by Etendo once a business partner is selected. -- **Order Reference**, free text which can be found under "More Information" section, you can use it to save the supplier order number, if any. - -In the **Status Bar** of the header, the user can find the following information: - -- **Document Status**: Document status of the order. The order can be in booked, draft, closed status, among others. -- **Total Gross Amount**: Total Gross amount of the order. -- **Total Net Amount**: Total Net amount of the order. -- **Currency**: Currency of the order. -- **Delivery Status**: It indicates in % how much quantity of the order has been received. -- **Invoice Status**: It indicates in % how much quantity of the order has been invoiced. - -**Once header information is properly filled-in, you can go to the "Lines" tab in order to enter purchase order line/s information**. - -!!! info - To learn how to enter purchase order lines, visit the next section [Lines](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#lines_2). - -It is possible to take up to **three possible actions regarding a purchase order**, by using the **header button "Book"**: - -- **Process it**, in case you might want to process it but not to book it as final, because it could be you might need to change it later on. -- **Void it**, in case that purchase order is not required anymore and therefore needs to be voided. -- **Book it**, in case it is correct and final. - -!!! info - If there are non-stockable BOM products and they have not been exploded, the Book button explodes them automatically. - - -### Lines - -Once the purchase order header has been properly filled in and saved, each purchase order line can be created in this tab. - -Purchase order lines can be created in three different ways: - -**1\. By manually creating new record/s in the "Lines" tab**. - -The purchase order fields you can fill in are described below: - -- **Product**. You can select an item or product from the list or use the product selector icon. -- **Ordered quantity**, or **Operative Quantity** if the product has an *alternative unit of measure (AUM)* configured. This is the quantity needed of the product/item. -- Product's **UOM**, or product's **Alternative UOM** depending on product configuration in regards to unit of measure. -- **Attribute Set Value. An attribute associated with a product as part of an attribute set.** -- **Net Unit Price**. This one is coming from the Price List selected in the header, but it could always be changed. -- **Line Net Amount. The final amount of a specified line, based only on quantities and prices.** -- **Tax**. Purchase tax is normally filled in by the system, depending on Taxes setup. - -**2\. By retrieving all the lines from previously created purchase orders.** In this case, you must use the process button "**Copy from Orders**". - -This process button enables the **Copy from Orders Pick and Edit** window. - -"Copy from Orders Pick and Edit" window allows you to search the orders to copy by using the filter options available. - -The lines information of the selected orders will be inserted in the purchase order line/s, then that information can be manually changed. - -**3\. By copying lines from other purchase orders.** - -In this case, you must use the process button **"Copy Lines".** - -This process button enables a new window named "Copy Lines from order" which allows you to create order lines by selecting the products already purchased from the supplier of the order by taking into account the *Consumption days* configured for the supplier. - -In the **Status Bar** of each line, you can find information about: - -- **Delivered quantity**: number of received products of the line. -- **Invoiced quantity**: number of invoiced product of the line. - -#### Explode button - -Explode button is shown when selecting a line with a non-stockable BOM product and the product has not already been exploded. When exploding a product, the bill of materials components the selected product consists of are shown in the order. - -!!! info - Once you have exploded it, you cannot comprime it. You should delete all the lines (first bill of materials components and then the BOM product), and insert again the non-stockable BOM product. - -#### Line Tax - -For each purchase order line, Etendo automatically populates the line tax related information in this tab. - -Line tax tab informs about each purchase order line: - -- **applied tax rate** -- **calculated tax amount** -- **taxable amount** - -!!! info - It is not possible to either manually create a new line or modify existing ones. - -#### Basic Discounts - -Lists information about discounts automatically applied based on the supplier configuration and / or manually entered for the purchase order. - -![Basic discounts](../../../../assets/drive/1AavUV8S8kQ2dp0P_W9lw06XfmAf5d_g-.png) - -#### Payment Plan - -This shows the total amount expected to be paid upon order booking as well as the amount/s pre-paid or paid against the invoice/s for the order. - -Payment Plan information is required at order level because suppliers could ask for a **pre-payment** of all or part of a debt prior to its due date. - -Purchase order payment plans **do not show nor manage valid due dates**, but the payment plan of the corresponding purchase invoice/s. - -This tab also shows information about the regular payments received against the invoice/s for this order, as amounts paid. - -Finally, a payment plan of a purchase order will be **removed**: - -- if the purchase order is **reactivated** -- or if the purchase order is **voided** - -#### Payment Details - -Displays the details of the payments (pre-payments or regular payments) made for the order or for the invoice/s of the order. - -### How to Reactivate a Closed Purchase Order - -!!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the [marketplace](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). - -!!! warning "Dependency Notice" - This module depends on the [**Bulk Completion**](../../optional-features/bundles/essentials-extensions/bulk-completion.md) module, as **order** processing actions must be performed using modern processes that allow the triggering of Hooks, instead of legacy processing. Due to this requirement, the legacy **close/reactivate** actions for orders will be hidden and these actions will only be available through the **Bulk Completion** button. - -Etendo allows the user to reactivate closed purchase orders by selecting the needed one/s and clicking the Undo Close button. - -![](../../../../assets/drive/1cyLa7pjnsNgXtnSEK2lZX9s35imhD2Kq.png) - -Once the process is finished, the purchase order status turns to booked. - -!!! info - Check the Technical documentation about Advanced Financial Docs Processing to extend the process. - -### Payment Removal - -The aim of this functionality is to delete and reactivate payments in an agile and easy way. Also, it allows eliminating and reactivating bank transactions and reconciliations. - -!!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). - -From this window, it is possible to remove payments associated with a purchase order by selecting the corresponding document and then clicking on the Remove Payment button. If there is an invoice associated with the order, the relationship of this invoice to the payment in question will also be removed (Purchase Invoice window > Payment Plan tab). - -If the payment is included in the financial account, i.e., if it is in Deposited/Withdrawn not cleared status, the transaction in it will also be deleted (Financial account window > Transaction tab). - -If the payment is reconciled through an automatic method, then in addition to the transaction in the financial account, the line of the bank statement to which it was linked (Financial Account window > Imported Bank Statements) and the corresponding line of the bank reconciliation (Financial Account > Reconciliations) will be deleted. - -!!! info - If the payment is posted, the accounting entry is deleted too. - -![](../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/PRpic2.png) - -### Intercompany - -In case the user has to create orders or invoices among two or more organizations that are different but belong to the same client, this functionality allows automatically generating the corresponding inverse document. - -!!! info - For more information, visit [the Intercompany module user guide](../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/intercompany.md). - -!!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). - -### Bulk Completion - -!!! info - To be able to include this functionality, the Essentials Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Essentials Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=39AC2D9F72124AC7A1D0A3D005293C9E){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Essential Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/essentials-extensions/release-notes.md). - -The Bulk Completion functionality allows the user to complete, reactivate or close multiple records by selecting them and clicking the **Bulk Completion** button. This makes records management easier and more efficient, reducing the time spent processing individual records. - -!!! info - For more information, visit [the Bulk Completion module user guide](../../optional-features/bundles/essentials-extensions/bulk-completion.md). - -### Advanced Bank Account Management - -!!! info - To be able to include this functionality, the Advanced Bank Account Management module of the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). - -This module adds a new field to the header of the Purchase Order window: **Bank Account**. This field is automatically filled with the bank account related to the adress or business partner of the order. - -![bank-account-3.png](../../../../assets/legacy/bank-account-3.png) - -!!! info - For more information, visit the [Advanced Bank Account Management user guide](../../optional-features/bundles/financial-extensions/advanced-bank-account-management.md). - - -## Goods Receipts - -:material-menu: `Application` > `Procurement Management` > `Transactions` > `Goods Receipt` - -A Goods Receipt is a document issued to acknowledge the receipt of the items listed in it. In other words, it is a document used to register in Etendo the specifics of items physically received in the warehouse. - -### Header - -Goods Receipts can be issued and booked in the header section of the goods receipt window. - -![Good receipts header](../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/goodsreceipt2.png) - -The fields to fill in the **Goods Receipt header** are: - -- **Document Type**, which is filled in by default as "MM Receipt". -- **Warehouse**, where goods are going to be located. -- **Business Partner**, third party which delivers the goods. -- **Movement Date**, delivery date of the goods. -- **Accounting Date**, accounting date in case of posting the Goods Receipt. -- **Purchase Order**, purchase order number linked automatically by Etendo, in case the Goods Receipt is automatically created from a Purchase Order. -- **Order Reference**, Warehouse team can fill in here the Supplier's Delivery Note number, this way the internal Goods Receipt number and the Supplier's Delivery Note number are linked. - -In the **Status Bar** of the header, the user can find the following information: - -- **Document Status**: Document status of the receipt. -- **Invoice Status**: It indicates in % how much quantity of the receipt has been invoiced. - -**Once header information is properly filled-in, you can then go to the "Lines" tab in order to enter "Goods Receipt Line/s"**. - -!!! info - To learn how to enter goods receipt lines, visit the next section [Lines](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#lines_3) - -If a **Goods Receipt** is completed and therefore **booked**: - -- The **quantity on hand of the item/s received is increased** by the quantity received. - -If a **"Completed" Goods Receipt is voided** because the goods have been returned to the supplier: - -- **The quantity on hand of the items/s returned is decreased** by the quantity of the goods returned. Etendo automatically creates a new "Goods Receipt" for exactly the same items but with "negative" quantities. - -!!! info - To learn more about Goods Returns, visit *Return to Vendor* and *Return to Vendor Shipment*. - -Supplier can send a "Purchase Invoice" together with the "Delivery Note" of the goods delivered, therefore: - -- From the Goods Receipt window, it is possible to generate the corresponding supplier's invoice, by using the header process button "**Generate Invoice from Receipt**". - -This action implies a **link between the goods receipt and the purchase invoice**, the user can be aware of when inquiring about the corresponding purchase invoice. - -!!! info - To learn more, visit [Purchase Invoice](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-invoice). - -### Lines - -Once the goods receipt header has been properly filled in and saved, each item received can be listed as a separate goods receipt line. - -There are several ways of creating goods receipt lines. - -1.**The user can always manually create goods receipt lines.** -That is the way the user could turn to in case there is not a booked purchase order nor a completed purchase invoice for the goods received they can retrieve data from. - -As a consequence, the information to manually fill in is: - -- the goods or items received -- the quantity received -- the storage bin where the items are going to be stored - -**Explode** button is shown when selecting a line with a non-stockable BOM product and the product has not already been exploded. When exploding a product, the bill of materials components the selected product consists of are shown in the shipment. Once you have exploded it, you cannot comprime it. You should delete all the lines (first bill of materials components and then the BOM product), and insert again the non-stockable BOM product. - -2.On the other hand, it is also possible to **"automatically" create goods receipt lines**, by using the header process button **"Create Lines From"**. - -This allows the user to select the orders or invoices pending to be received. - -For instance, once a purchase order is selected, the purchase order lines pending to be received are shown. - -Then, the user is able to select the purchase lines received, change the quantity if required, and get them located in the warehouse. - -Finally: - -- If a purchase order/line is selected, this action **links each good receipt line to the corresponding purchase order line**, same applies to purchase invoice. - -In the **Status Bar** of each line, you can find information about the **Invoiced quantity**, the number of invoiced products of the line. - -#### Accounting - -Accounting information related to the material receipt. - -A **"Goods Receipts" can be posted** if the "**MaterialMgmtShipmentInOut**" table is set to Active for accounting in the \[*Active Tables*\] tab of the organization's general ledger configuration. - -A "Goods Receipt" posting looks like: - -![Good receipts posting](../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/goodsreceipt3.png) - -Posting a "Goods Receipt" requires the calculation of the cost of the contained product/s. - -In the case of a goods receipt, that is: - -- the purchase price of the product/s -- or the default *standard cost* of the product/s in case of calculating cost by using an Standard *costing algorithm*. - -If there is not a related purchase order, the Costing Server process uses the newer of the following three values: - -- the last purchase order price of the receipt's vendor for the product. -- the purchase price list of the product. -- or the *default cost* of the product. - -Moreover: - -- The "Legal Entity" organization needs to have a validated *Costing Rule* configured. -- And the *Costing Background Process* needs to be scheduled for the *Client*, therefore it can search and allow that the *Costing Server* process calculates the cost of the transactions. - -Once the costs have been calculated, the **Goods Receipt can be posted** to the ledger. - -In the case of a receipt containing "Expense" product/s without the "Sales" checkbox selected, it is possible to use the product's purchase price instead of the product's cost to post the goods receipt. - -This works if the checkbox *Book Using Purchase Order Price* is selected for the product/s. - -In this case, it is required that a "Purchase Order" is related to the posted "Goods Receipt". - -#### Voiding - -It is possible to totally void a goods receipt by using the header button **"Close"** and then selecting the action "**Void**". - -This action creates a **new document** that **reverses the goods receipt.** - -Void action allows to specify a "**Void Date**" and a "**Void Accounting Date**" of the new document: - -- **Void Date**: that is the movement date of the new document that reverse the goods receipt. -- **Void Accounting Date**: that is the accounting date of the new document that reverse the goods receipt. - -Both fields above take original document dates as default date and validate that the dates entered are not prior to the "Movement Date" and the "Accounting Date" of the Goods Receipt, respectively. - -Void action implies that: - -- Etendo automatically generates a **new document** in the "Goods Receipt" window, and **informs about the document number** created. The document number is also displayed in the description field of the Goods Receipt. This new document is created as described below: - - The "**transaction document**" used by Etendo is "**MM Receipt**". - - This document is **exactly the same as the original** one being reversed **but the movement quantity is negative.** - - Once the **new document** has been created, you can **change** both the "**Movement Date**" and the "**Accounting Date**" of the new document prior to getting it posted. - -#### Landed Cost - -Landed Cost tab allows to allocate additional costs to the goods receipt. - -![Landed cost window](../../../../assets/drive/1YND6qqNXSCzLiiq_PICSVr3GymXZi6_o.png) - -It is possible to enter as many landed cost types/lines as required. - -Some relevant fields to note are: - -- **Landed Cost Type**: that is the landed cost type that is going to be allocated to the goods receipt. -- **Invoice line**: that is to select the corresponding landed cost invoice line if any, that matches the landed cost type being entered. - If an invoice line is selected, the invoice line amount gets populated in the next field "Amount". -- **Amount**: that is the landed cost amount. This amount can be an "estimation" or a "real" amount in case of selecting an invoice line. -- **Landed Cost Distribution Algorithm**: that is the one distributed by Etendo "Distribution by Amount", which means that the landed cost amount is going to be distributed among the goods receipt lines proportionally by receipt line amount. - -Once all items above are filled in, including corresponding landed cost purchase invoice line, both "Goods Receipt" and Landed Cost *process matching* are executed by clicking on the "**Complete**" process button. - -### How to Reactivate Goods Receipts - -!!! info - To be able to include this functionality, the Warehouse Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Warehouse Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=EFDA39668E2E4DF2824FFF0A905E6A95){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Warehouse Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/warehouse-extensions/release-notes.md). - -From the Goods Receipt window, it is possible to reactivate a previously generated movement just by selecting the corresponding document and clicking the Reactivate button. - -Once the receipt is successfully reactivated, the state of the document changes to Draft as it can be observed in the status bar. - -![](../../../../assets/drive/1-Z-wUYZfcGDizQ_Kkp8TUYXTs-KnM67H.png) - -!!! warning - Note: It is not possible to reactivate documents that include transactions with quantities exceeding the existing stock quantity for a certain product in a certain storage bin. The only exception is when the configuration of the storage bin allows Over Issue. For more information, visit [Storage Bin](../../../../user-guide/etendo-classic/basic-features/warehouse-management/setup.md#storage-bin). - -### Bulk Posting - -!!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). - -The Bulk Posting functionality allows the user to post or unpost multiple records by selecting the corresponding records and clicking the **Bulk posting** button. - -Also, the Accounting Status of the record/s is shown in the status bar, in form view, or in a column, in grid view. - -!!! info - For more information, visit [the Bulk Posting module user guide](../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). - -### Bulk Completion - -!!! info - To be able to include this functionality, the Essentials Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Essentials Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=39AC2D9F72124AC7A1D0A3D005293C9E){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Essential Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/essentials-extensions/release-notes.md). - -The Bulk Completion functionality allows the user to complete, reactivate or void multiple records by selecting them and clicking the **Bulk Completion** button. This makes records management easier and more efficient, reducing the time spent processing individual records. - -!!! info - For more information, visit [the Bulk Completion module user guide](../../optional-features/bundles/essentials-extensions/bulk-completion.md). - -## Pending Goods Receipts - -:material-menu: `Application` > `Procurement Management` > `Transactions` > `Pending Goods Receipts` - -This window allows the user to: - -- **Use the Filter options** to narrow down the search of pending purchase orders to be delivered. It is possible to search by: - - Business Partner - - From Purchase Order Date -> To Purchase Order Date - - Purchase Order number -- Enter a **"Reception date".** -- **Select** the "**Order line/s of a purchase order/s" delivered** which are shown grouped by Business Partner and Purchase Order. -- **Change** the "**Quantity**" of the goods being receipt if needed. -- **Enter** the "**Goods receipt location**" or storage bin within a warehouse. -- **Process it** in order to create the corresponding goods receipts. - -![Pending goods receipts window](../../../../assets/drive/1hGrJ6YXXd1p20ZdLQefX1o6_8nVogOd8.png) - -## Purchase Invoice - -:material-menu: `Application` > `Procurement Management` > `Transactions` > `Purchase Invoice` - -### Overview - -The Purchase Invoice window is used to **create, register, and manage supplier invoices for purchased goods and services**. - -Purchase invoices are typically generated after the Goods Receipt is completed, ensuring that received quantities match the supplier’s billing information. - -Invoices can be created in two ways: - -1. Automatically, from a related Goods Receipt - -2. Manually, by entering the invoice directly in this window - -Each invoice defines the products or services, quantities, prices, taxes, and amounts to be paid to the supplier. - -When the invoice is accounted, the corresponding purchase expenses are recognized in accounting. If a deferred expense plan is configured, expense recognition can be distributed over time according to the defined schedule. - -### Header - -The **Header** contains the basic information for a purchase invoice. In most cases you only need to select the Business Partner; the system will fill the rest from defaults and the selected partner. - -![Purchase invoice window](../../../../assets/drive/1JvS1mOjiiyATJENTs5SuQIyEAr-UHmE3.png) - -Fields to note: - -- **Transaction document**: defaults to AP Invoice or purchase invoice [document type](../financial-management/accounting/setup/document-type.md). You can change it to AP Credit Memo (positive-credit type, not linked to orders/shipments) or Reversed Purchase Invoice (negative amounts, for returns). -- **Document No.**: supplier invoice number if allowed by sequence, otherwise an internal number is used. -- **Invoice Date**: date of the invoice (used to calculate due date). -- **Accounting Date**: posting date for the ledger (defaults to Invoice Date). -- **Payment Terms**: how the invoice will be paid. -- **Payment Method**: when the invoice will be paid. -- **Supplier Reference**: optional supplier reference number. - -How to add lines: - -1. Use **Create Lines From Order** or **Create Lines From Receipt** to pull pending items. -2. Use **Copy Lines** to copy lines from an existing invoice. -3. Add lines manually in the **Lines** tab when there is no related order or receipt. - -Complete and next steps: - -- Click **Complete** to finish the invoice; this creates the Payment Plan and updates the Payment Monitor. Non-stockable BOMs will be exploded automatically if needed. - -After completion you can: - -- **Post** the invoice to the ledger with the [Post](#post) button. -- **Void/Reactivate** using [Reactivate](#reactivate). -- **Add Payment** with [Add Payment](#add-payment). - -### Lines - -Once the Purchase Invoice header is saved, add one or more invoice lines for the products or expenses being billed. - -Fields to note: -- **Financial Invoice Line**: Select this for lines that are not products (for example, a G/L item or an asset). The Product field is replaced by an Account field. -- **Attribute Set Value**: Shown if the product uses attributes (color, size, serial number, etc.). -- **Purchase Order Line / Goods Receipt Line**: Links the invoice line to the related PO or Goods Receipt line, if any. - -Deferring expenses (optional): -- **Deferred Expense**: Check this to spread the expense over time and reveal the expense-plan fields. -- **Expense Plan Type**: Frequency of recognition (currently: monthly). -- **Period Number**: Number of periods to distribute the expense (e.g., enter 12 to spread over 12 months). For instance, if a company purchases business insurance for the duration of the year, the period number to enter would be 12 as the company would like to distribute that expense over 12 months. - -- **Starting Period**: First open period when recognition begins. - -These expense-plan values can be defaulted from the product. If an expense plan is used, the invoice accounting will follow that plan. - -**Explode Button** - -The **Explode** button appears when the selected line contains a non-stockable BOM product that hasn't been exploded yet. Exploding replaces the BOM line with its components in the invoice. This action cannot be undone — to revert it, delete the component lines first and then re-add the non-stockable BOM product. - -**Match LC Cost** - -The **Match LC Cost** button allows you to match the **estimated landed cost** defined in the **Landed Cost window** with the **invoiced landed cost** entered in an invoice line. - -This option is available when the purchase order or invoice line contains a **product** or **account** configured as a **landed cost type**. - -Both costs must belong to the **same landed cost type** to be matched. - -Matching helps to: - -- Reconcile estimated and invoiced landed costs -- Keep product costs accurate -- Generate the correct accounting entries - -After clicking **Match LC Cost**, the **Match LC Cost** pick-and-edit window opens. - -Only **processed Landed Cost documents** are displayed. - -From this window, you can: - -- Select the corresponding landed cost document -- Enter the amount in **Matched Amt** -- Enable **Process Matching** to complete the process immediately - -The **Is Matching Adjusted** checkbox controls how differences between estimated and invoiced costs are handled: - -- **Checked** → Creates an additional landed cost adjustment to update the product cost -- **Unchecked** → No cost adjustment is created - -**Scenarios** - -1. Estimated = Invoiced - -- Only matching is posted to the ledger -- No adjustments are created - -2. Estimated ≠ Invoiced + Adjustment enabled - -- A landed cost adjustment is created -- Product cost is updated to the invoiced amount -- Matching and adjustment are posted - -3. Estimated ≠ Invoiced + Adjustment disabled - -- Only matching is posted -- Product cost is not modified - -#### Line Tax - -Line tax information is automatically populated for each purchase invoice line upon completion of the invoice. - -**Line Tax** read-only tab details tax information for each line of a purchase invoice based on its Tax field which is automatically pre-filled according to the Taxes Setup. - -### Tax - -This section summarizes tax related information for the whole purchase invoice. It contains as many records as tax rates used in the invoice. - -The Tax Amount field reflects the tax value calculated automatically based on the tax rate and tax base settings. - -!!! info - - It is possible to add a feature that allows controlled adjustments to invoice tax amounts to reconcile small **rounding differences** with external systems or when invoices are submitted to **governmental entities**. It supports both **sales** and **purchase** invoices, offers **manual and automated adjustments** for minimal corrections at cents level, and records all changes for **auditability**, ensuring the final invoice total matches external, governmental, or regulatory requirements. - - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. - - For more information, visit: [Adjust Invoice Tax user guide](../../optional-features/bundles/financial-extensions/adjust-invoice-tax.md) - - This functionality is compatible from Etendo 23. - - -### Buttons - -#### Post/Unpost - -A purchase invoice can be posted to the ledger when required at a given Accounting Date by using this process button. Once posted, it can be unposted with the same button. - -#### Reactivate - -![pop-up-reactivate](../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/pop-up-reactivate.png) - -Using this button, the user has two options: reactivating or voiding the Completed invoice. - -In the case of the **Reactivate** option, it turns the record from Completed into Draft status. - -With the **Void** option, it is possible to totally void a purchase invoice. This action creates a new document that reverses the invoice. - -![pop-up-void](../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/popup-void.png) - -Voiding allows specifying a **Void Date** and a **Void Accounting Date** for the new document that reverses the invoice. - -Both date fields above take the current date as default date and validate that the dates entered are not prior to the invoice date and the invoice accounting date, respectively. - -Also, this process window includes a **Supplier Reference** field to enter the supplier reference number to refer to the reversed document resulting from the invoice voiding. Here, you can enter the corresponding number or leave the field blank to complete it later. - -This action implies that: - -- Etendo automatically generates a new document in the *Purchase Invoice* window that reverses the original invoice. -- Etendo also informs about the new document number. This new document is created as described below: - - The transaction document used by Etendo is the *Reversed Purchase Invoice*. This document is exactly the same as the original one being reversed but the invoiced quantity is negative. - -- Once the new document has been created, you can change both the *Invoice Date* and the *Accounting Date* of the new document prior to get it posted. You can also enter the Supplier Reference if not entered before or modify the existing one. - -- The *Reversed Invoices* tab lists the original invoice being reversed as now both of them are linked. - - And it is also possible to partially void a supplier invoice by: - - - Manually creating any of the available reversed purchase documents, in the [Purchase Invoice](#purchase-invoice) window: - - - **AP Credit Memo** or - - **Reversed Purchase Invoice** - - - which besides must be manually linked to the invoice/s being reversed in the **Reversed Invoices** tab. - - To learn more visit [Reversed Invoices](../sales-management/transactions.md#reversed-invoices). - - The **AP Credit Memo** posting looks the same as the **Reversed Purchase Invoice** posting. The main difference between those two purchase reversed document types is: - - - **AP Credit Memo** invoiced quantity is a positive quantity. - - and **Reversed Purchase Invoice** quantity is a negative quantity - - !!!note - We strongly recommend you to use the **Reversed Purchase Invoice** document type while partially voiding supplier's invoices. - - -#### Add Payment - -Payment/s can be made against a purchase invoice by using the Add Payment button which opens the Add Payment pop-up window. - -#### Bulk Posting - -!!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). - -The Bulk Posting functionality allows the user to post or unpost multiple records by selecting the corresponding records and clicking the **Bulk posting** button. - -Also, the Accounting Status of the record/s is shown in the status bar, in form view, or in a column, in grid view. - -!!! info - For more information, visit [the Bulk Posting module user guide](../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). - -#### Bulk Completion - -!!! info - To be able to include this functionality, the Essentials Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Essentials Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=39AC2D9F72124AC7A1D0A3D005293C9E){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Essential Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/essentials-extensions/release-notes.md). - -The Bulk Completion functionality allows the user to complete, reactivate or void multiple records by selecting them and clicking the **Bulk Completion** button. This makes records management easier and more efficient, reducing the time spent processing individual records. - -!!! info - For more information, visit [the Bulk Completion module user guide](../../optional-features/bundles/essentials-extensions/bulk-completion.md). - -!!!warning - The bulk voiding option fails when the [Purchase Invoice Validation](../../optional-features/bundles/procurement-extensions/purchase-invoice-validation.md) module is installed. This is because the module includes a default preference that prevents the duplication of invoices with the same business partner, accounting year, and supplier reference. Since massive voiding attempts to reverse invoices, it leads to duplication, as the supplier reference for each reversed invoice cannot be modified. As a result, the module prevents the bulk voiding process from functioning. - ![popup-bulk-void](../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/popup-bulk-void.png) - -#### Remove Payment - -The aim of the Payment Removal functionality is to delete and reactivate payments in an agile and easy way. Also, it allows eliminating and reactivating bank transactions and reconciliations. - -!!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). - -From this window, it is possible to delete payments associated with a purchase invoice by selecting the corresponding document and then clicking on the Remove Payment button. If there is an order associated with the invoice, the relationship of this order to the payment in question will also be deleted (Purchase Order window > Payment Plan tab). - -If the payment is included in the financial account, i.e., if it is in Deposited/Withdrawn not cleared status, the transaction in it will also be deleted (Financial account window > Transaction tab). - -If the payment is reconciled through an automatic method, then in addition to the transaction in the financial account, the line of the bank statement to which it was linked (Financial Account window > Imported Bank Statements) and the corresponding line of the bank reconciliation (Financial Account > Reconciliations) will be deleted. - -!!! info - If the payment is posted, the accounting entry is deleted too. - -![](../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/PRpic4.png) - -#### Unvoid - -!!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the [marketplace](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). - -Etendo allows the user to reactivate voided purchase invoices by selecting the needed one/s and clicking the Unvoid button. - -![](../../../../assets/drive/1UisxZzbpppLvN_rdL__TJg8tLeh5sMfW.png) - -Once the process is finished, the sales invoice status turns to Complete. - - -???+ note - In the case of the standard version of the module, it is necessary for the user to also unvoid the corresponding reversed invoice. -!!! warning - Remember that this reactivation process affects the accounting, since, if the original information is not manually removed from the reactivated document, the accounting information will be doubled. - -!!! info - Check the Technical documentation about [Advanced Financial Docs Processing](../../../../developer-guide/etendo-classic/bundles/financial-extensions-bundle/overview.md#advanced-financial-docs-processing) to extend the process. - -#### Modify Payment Plan - -!!! info - To be able to include this functionality, the Advanced Bank Account Management module of the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). - -The Advance Bank Account Management module adds a new field to the header of the Purchase Invoice window: **Bank Account**. This field is automatically filled with the bank account related to the adress or business partner of the invoice. Also, the Modify Payment Plan button is added for better payment management. - -![bank-account.png](../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/bank-account.png) - -!!! info - For more information, visit the [Advanced Bank Account Management user guide](../../optional-features/bundles/financial-extensions/advanced-bank-account-management.md). - -### Intercompany - -In case the user has to create orders or invoices among two or more organizations that are different but belong to the same client, this functionality allows automatically generating the corresponding inverse document. - -!!! info - For more information, visit [the Intercompany module user guide](../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/intercompany.md). - -!!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). - - -## Matched Purchase Invoices - -:material-menu: `Application` > `Procurement Management` > `Transactions` > `Matched Purchase Invoices` - -This window helps the user to post the discrepancies between inventory and financial accounting of those items for which the corresponding goods receipts were posted. - -Above mentioned discrepancies are mainly caused by differences between: - -- the **item's net unit price registered when booking the purchase order** and later on **posting the corresponding Goods Receipt.** -- and the **"final" item's net unit price registered when posting the purchase invoice.** - -In the window, there is a listing of all invoices that are matched to goods receipts. The matching of the documents is done when documents are created by using the information of the other document: for example by clicking the Generate Invoice from receipt on the goods receipt or by clicking the Create Lines from button when creating a goods receipt to select the invoice. - -![Matched Purchase Invoices window](../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.png) - -#### Matched Purchase Invoice - -Matched Purchase Invoice tab lists each invoice line posted linked to the corresponding goods receipt lines, which could also be posted or not. - -There is a "**Post**" header button which is the one that posts the discrepancies between inventory and financial accounting if any, once the proper line has been selected. - -The general process to post the discrepancies in accounting is detailed below: - -A *Matching Invoice* document can be posted if the cost of the products included in a *Goods Receipt* has been calculated. To obtain that: - -- A validated *Costing Rule* is required in the Matched Invoice's legal entity, -- and the background process *Costing Background Process* must be run. - -In the case of "Expense" product/s do not having the "Sales" checkbox selected, it is possible to use the product's purchase price instead of the product's cost whenever the checkbox *Book Using Purchase Order* Price is selected. In this case, it is required that a "Purchase Order" is related to the "Goods Receipt". - -#### Accounting - -Accounting information related to the matched purchase invoices. - -### Bulk Posting - -!!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). - -The Bulk Posting functionality allows the user to post or unpost multiple records by selecting the corresponding records and clicking the **Bulk posting** button. - -Also, the Accounting Status of the record/s is shown in the status bar, in form view, or in a column, in grid view. - -!!! info - For more information, visit [the Bulk Posting module user guide](../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). - -## Return to Vendor (RTV) - -:material-menu: `Application` > `Procurement Management` > `Transactions` > `Return to Vendor` - -This window allows the user to create a Return Material document in case a given product needs to be sent back either to be returned for a refund or replacement, or to be repaired. - -### Header - -The user can create a purchase order and process it. - -Once the Return Material document is accepted by the Vendor, the user can process it by clicking the button **Book**. The document changes from *Draft* to *Booked*. - -![Return to vendor window](../../../../assets/drive/1PKb2NIyq5HtvO_4abDPQjajObdcGFiPH.png) - -Only *Booked* documents can be shipped to the vendor. - -!!! warning - Notice the button **Pick/Edit lines** disappears when the Return to vendor document is in status *Booked*. - -### Lines - -Add products to be included in your purchase order. Each product is added by creating a line. - -The Lines tab is not editable, since the returned lines always come from receipt lines, to avoid: - -- Seeing positive values while negative in the DB. -- Entering lines that are not linked to the original receipt lines. -- Editing attributes, products and so having either the products or attributes different from the shipment line. - -To enter new lines you need to click the process button PICK/EDIT Lines. - -**Things to consider:** - -- The only editable fields are: - - **Returned**: Quantity you wish to return. When selecting the row, the quantity is not set by default since the system cannot know how many items return. - - **Net Unit Price**: Price of the original purchase order. - - **Return reason**: The reason why you return the item. - - and **Returned UOM**, only in case \*alternative unit of measure (AUM)\*preference is enabled. - In that case, product's "primary" AUM for the purchase flow is shown if any, otherwise product's UOM is shown. The user can always change it to product's UOM. - -You can define the Return Reason at header level. In this case when picking a line it inherits what selected in the header but you can modify it as you wish. - -- Only Material receipt documents that have not been still returned can be picked it, in case a Receipt line has been fully returned it will not be shown. -- When a Receipt line has been partially returned you can still return the rest. What you have already returned for that line is shown in the field **Return Qty other R.** - -**Validations:** - -- You are not allowed to return more quantity than the **Ship/Receipt Qty**. In case you do it a message is shown. -- Notice that this validation takes into account the **Return Qty other RM** field - -!!! info - To edit a line you need to click again the **Pick/Edit Lines** button and the line appears selected and then you can modify any of the editable fields. - -!!! info - To delete a line you need to unmark the line and then click Done. - -### Bulk Completion - -!!! info - To be able to include this functionality, the Essentials Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Essentials Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=39AC2D9F72124AC7A1D0A3D005293C9E){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Essential Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/essentials-extensions/release-notes.md). - -The Bulk Completion functionality allows the user to complete, reactivate or close multiple records by selecting them and clicking the **Bulk Completion** button. This makes records management easier and more efficient, reducing the time spent processing individual records. - -!!! info - For more information, visit [the Bulk Completion module user guide](../../optional-features/bundles/essentials-extensions/bulk-completion.md). - -## Return to Vendor Shipment - -:material-menu: `Application` > `Procurement Management` > `Transactions` > `Return to Vendor Shipment` - -From this window, the user can deliver the returned goods to the vendor. - -### Header - -The user can create and edit a goods receipt. - -The **RMA vendor ref.** field is populated automatically or not based on: - -- If it is filled before selecting a line, then it will not be populated automatically to avoid override it. -- If you select a line/s where all of them belong to the same Return to Vendor document, it will be populated automatically. -- If you select a line/lines but one of them belongs to a different Return to Vendor document, then it will not be populated automatically. - -Once the document is ready, you can process it by clicking the button **Complete**. The document changes from *Draft* to *Completed*. - -!!! warning - Notice the button **Pick/Edit lines** disappears when the Return to vendor document is in status *Completed*. - -![Return to vendor shipment](../../../../assets/drive/1wuiYHH8xsIwjLRgp0VzWUqAtev43BzD8.png) - -To invoice these documents you must use the **Purchase invoice** window. All scenarios are covered: - -- If the vendor sends an invoice just for that specific document you need to select a *Reverse purchase invoice* document type and then select the lines through the *Create lines* from button. -- If the vendor sends an invoice with the original purchase order plus the return materials order you need to select a *Purchase invoice* document type and then select the lines through the *Create lines* from button. -- If the vendor does not send an invoice for the return materials order but wants to keep it as credit where you can use it later, you have to: - - Create a *Reverse purchase invoice* for these returned materials. - - Leave it as credit to be used later through the **Payment out** window. - - When you create the Purchase invoice for the original Purchase order you can consume that credit. - -### Lines - -Add products which are included in your goods receipt. Each product is shown on its own line. - -The Lines tab is not editable, since the lines always come from return to vendor lines, to avoid: - -- Seeing positive values while negative in the DB. -- Entering lines that are not linked to return lines. -- Editing attributes, products and so having either the products or attributes different from the return line. - -!!! info - To enter new lines, the user needs to click the button PICK/EDIT Lines. - -**Things to consider:** - -- Editable fields are: - - **Ship Qty**, that value is set automatically when you select the line, - - and **Returned UOM**, only in case an alternative unit of measure (AUM) preference is enabled, regardless product's UOM is always shown there by default. - The user can change it if required, to the product's primary AUM configured for the procurement flow. -- The user can only select Return to Vendor lines that are pending to be shipped to that specific vendor. -- The system proposes the different storage bins from where the item can be picked. Depending how the product is configured we could have three scenarios: - - Product with an instance attribute (i.e: Serial number): The system will propose only one storage bin as it is shown above. - - Product with a non-instance attribute (i.e: Colour): The system could propose several storage bins. See below image - - Product without attributes. Similar to second scenario. - -**Validations:** - -- You are not allowed to ship more than the **Available Qty.** -- You are not allowed to ship more than the **Pending** quantity. -- The system also validates you cannot ship more than the **Pending** quantity when selecting both lines. - -!!! info - To edit a line, you need to click the **Pick/Edit Lines** button again, the line appears selected and then you can modify any of the editable fields. - -!!! info - To delete a line, you need to unmark the line and then click Done. - -If there is not enough available stock for a product in a selected line, then it will be possible to define a Ship Quantity and select it. if there is at least one storage bin with overissue inventory status for the Return To Vendor Shipment's warehouse, in this case the new line will use it as storage bin and it will create a negative stock when the document is processed. - -#### Accounting - -The RTV shipment can be posted **if the table "MaterialMgmtShipmentInOut" is** active for accounting **in the corresponding general ledger configuration.** - -### Bulk Posting - -!!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). - -The Bulk Posting functionality allows the user to post or unpost multiple records by selecting the corresponding records and clicking the **Bulk posting** button. - -Also, the Accounting Status of the record/s is shown in the status bar, in form view, or in a column, in grid view. - -!!! info - For more information, visit [the Bulk Posting module user guide](../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). - -## Landed Cost - -:material-menu: `Application` > `Procurement Management` > `Transactions` > `Landed Cost` - -Landed Cost window allows the user to allocate additional costs such as freight, insurance or duties to goods receipt(s), therefore the cost of the products included in the receipt(s) is adjusted as applicable. - -All those costs are needed to place the product in the organization's warehouse. - -Every time that a landed cost is booked for a product receipt valued at "Average" cost, a landed cost adjustment is created. - -Landed costs distributed and allocated to products valued at "Average" cost imply a change in the inventory value of the product. In other words, the calculated cost ("Total Cost") of the product receipt will need to be adjusted the same as the "Average" cost of the product. - -!!! info - Note that the "Unit Cost" of the receipt transaction will not change as this type of adjustment is not a unit cost adjustment type but an "extra" cost. - -All of the above will have an accounting impact, therefore product inventory value can be the same as product accounting value. - -On the other hand, if a landed cost is booked for a product receipt valued at "Standard" cost, no cost adjustment will be created but a "Variance" between the "standard" cost defined for the product and its "actual" cost. This variance will need to be posted to a "Landed Cost Variance" account, so it can be later on analysed. - -Landed cost window allows both: - -- either to book "**estimated**" landed cost that can be later on matched against "actual" landed cost by landed cost type, -- or directly book "**actual**" landed cost by landed cost type. - -Landed cost window also allows to post landed costs once processed. - -"**Estimated**" Landed Cost scenario: - -- A purchase order is booked and after that the corresponding goods receipt and purchase invoice. - The "average" cost of the products included in the receipt is calculated at this point. -- After that "estimated" landed costs (i.e freight costs) are allocated to the goods receipt and booked in the landed cost window. - The cost of the products included in the receipt is then adjusted the same as products asset accounting. -- After that, a purchase invoice including the actual amount of freight cost is booked and posted to the ledger. -- Then, it is possible to match "estimated" landed cost against "invoiced" landed cost. - The cost of the products included in the receipt is adjusted once more if there are differences between estimated and actual landed cost amounts. - -"**Actual**" Landed Cost scenario: - -- A purchase order is booked and after that, the corresponding goods receipt and purchase invoice. - The "average" cost of the products included in the receipt is calculated at this point. -- After that, a landed cost document is created to record actual landed cost to the goods receipt. - The cost of the products included in the receipt is then adjusted the same as products asset accounting. - -In Summary, landed cost feature follows below detailed steps: - -- **Landed Cost Process**: - - A landed cost document is created including as many different landed cost types and amounts as required. - - This landed cost document can be related to a single goods receipt, to several goods receipts or to specific goods receipts lines. - - This landed cost document can record "actual" landed cost in case of selecting the corresponding invoice, therefore the landed cost process and matching is done in one step. - - Landed cost is processed. - - This action creates a *landed cost adjustmen* linked to the landed cost document. - This cost adjustment has as many adjustment lines as products included in the goods receipt(s) selected, therefore the cost of those products is adjusted as applicable. -- **Landed Cost Post**: - - Once a landed cost document is processed it can be posted to the ledger, therefore product(s) asset accounting is adjusted as well. -- **Landed Cost Matching**: - - Landed cost invoice is booked and posted to the ledger later on. - - After that the "estimated" landed cost booked in the landed cost document can be matched against actual landed costs by landed cost type in the landed cost invoice. - - Landed cost matching can generate an additional cost adjustment for the product(s) if estimated landed cost amounts were not the same as actual landed cost amounts. -- **Landed Cost Matching Post**: - - Once landed cost(s) are matched can be posted therefore: - - product(s) asset accounting is adjusted once more if applicable, - - and landed cost posting gets landed cost invoice *accounting dimensions*. - -### Header - -A Landed Cost document can be created, processed and posted in this window. - -![Landed cost header](../../../../assets/drive/1YND6qqNXSCzLiiq_PICSVr3GymXZi6_o.png) - -Some fields to note are: - -- **Organization**: that is the organization or legal entity for which landed cost needs to be booked. -- **Reference date**: that is the date when the landed cost document is being created. - -**Cost** - -A Landed Cost Document can have as many cost (lines) as landed cost types to allocate to the Goods Receipt(s) selected. - -![Landed cost tabs](../../../../assets/drive/1jbfoYTDqyRZiF3bTwPQkG8OmjpLr0zau.png) - -Some fields to note are: - -- Landed Cost Type: that is the landed cost type that is going to be allocated to the receipt(s) or receipt line(s) selected in Receipt tab. -- **Invoice line**: that is to select the corresponding landed cost invoice line if already booked that matches the landed cost type being entered. - If an invoice line is selected,the invoice line amount gets populated in the next field "Amount". -- **Amount**: that is the landed cost type amount. This amount can be "estimated" or "actual" in case of selecting an invoice line. -- **Currency**: that is the currency of the landed cost type. - - It is important to remark that a landed cost document can include as many landed cost types as required in the currency required. - For instance, a landed cost document can include two landed cost type lines one in USD and the other one in EUR. - In this scenario, a landed cost adjustment will be created including two lines. Cost adjustment amounts will be calculated in the currency configured for the legal entity product transaction belongs to. -- **Landed Cost Distribution Algorithm**: there is one algorithm available distributed by Etendo that is "Distribution by Amount". - This algorithm distributes landed cost type amount proportionally by receipt line(s) amount among the receipt(s) selected. - -Once a receipt(s) has been selected in Receipt tab, landed cost document (header) can be processed by using the process button "**Process**". - -This action creates a landed cost adjustment linked to the landed cost document. - -This cost adjustment has as many adjustment lines as products included in the goods receipt(s) selected, therefore the cost of those products is adjusted as applicable. - -Once processed, a landed cost document can be: - -- **"Reactivated"**, this action voids the landed cost adjustment linked to the landed cost document. -- or **"Post"**, therefore product asset accounting is also adjusted accordingly. - -**Landed Cost** posting creates the following accounting entries in case of a "Product" landed cost type: - -| | | | -| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | -| Account | Debit | Credit | -| Product Asset | "Estimated" Landed Cost Amount.

(\*)This ledger entry gets goods receipt "accounting dimensions" such as "Vendor" or "Product". See "Detail" link. | | -| Product Expense | | "Estimated" Landed Cost Amount | - -**Landed Cost** posting creates the following accounting entries in case of an "Account" landed cost type: - -| | | | -| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | -| Account | Debit | Credit | -| [*Product Asset*] | "Estimated" Landed Cost Amount.

(\*)This ledger entry gets goods receipt "accounting dimensions" such as "Vendor" or "Product". See "Detail" link. | | -| [*G/L Item*] | | "Estimated" Landed Cost Amount | - -##### Process Matching - -Matching between an "estimated" landed cost and an "invoiced" landed cost can be processed in: - -**1.** The **GOODS RECEIPT** window before processing and by using the process button "**Complete**" - -This scenario takes place whenever all landed cost related information below is available and entered in the Landed Cost tab of the **Goods Receipt** : - -- landed cost types -- landed cost amounts -- related landed cost invoice lines - -This scenario automatically creates: - -- a landed cost document in the **landed cost** window related to the goods receipt that contains all the information entered in the "Landed Cost" tab of the Goods Receipt. - This landed cost document is already processed and matched, therefore only actions missing are to post the landed cost document (header) and to post the landed cost matching. -- a landed cost adjustment that adjusts the cost of each product included in the Goods Receipt. - -**2**. The **Landed Cost PURCHASE INVOICE** window, by using the process button Match LC Cost which can be found in each landed cost purchase invoice line. After that **"Process Matching" check-box** is selected. - -This scenario takes place whenever: - -- all landed cost related data but landed cost invoice line information was entered in the Landed Cost tab of **Goods Receipt** window. -- all landed cost related data but landed cost invoice line information was entered in the Cost tab of **Landed Cost** window. - -This scenario automatically creates: - -- a new landed cost adjustment that adjust once more the cost of each product included in the Goods Receipt if: - - the landed cost type amount booked is not the same as the one invoiced - - and the check-box "Is matching adjusted" is selected. -- only action missing is to post the landed cost matching. - -**3.** The **LANDED COST** window, by using the process button "**Process Matching**" - -This scenario takes place whenever the matching has been executed in the landed cost purchase invoice, see scenario 2 above, but the check-box "Process Matching" was not selected there. - -This scenario automatically creates: - -- a new landed cost adjustment that adjusts once more the cost of each product included in the Goods Receipt if the landed cost type amount booked is not the same as the one invoiced and the check-box "Is matching adjusted" is selected. -- only action missing is to post the landed cost matching. - -**4.** The **LANDED COST** window, by using the process button "**Process**". - -This scenario takes place whenever all landed cost related information is entered in the **landed cost** window.: - -- landed cost types -- landed cost amounts -- related landed cost invoice lines -- and goods receipt(s) - -This scenario automatically creates: - -- a landed cost adjustment that adjust the cost of each product included in the Goods Receipt(s). -- only actions missing are to post the landed cost document (header) and to post the landed cost matching. - -##### Post Matching - -A landed cost matching can be posted, after being processed. This posting will have different ledger entries depending on the scenarios listed below: - -1\. "**Estimated**" landed cost **equal** to "**invoiced**" landed cost - -- In the case of a "product" landed cost type - -| | | | -| ------------------- | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Account | Debit | Credit | -| [*Product Expense*] | "Estimated"="Invoiced" Landed Cost Amount | | -| [*Product Expense*] | | "Estimated"="Invoiced" Landed Cost Amount

(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | - -- In the case of an "account" landed cost type - -| | | | -| ------------ | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Account | Debit | Credit | -| [*G/L Item*] | "Estimated"="Invoiced" Landed Cost Amount | | -| [*G/L Item*] | | "Estimated"="Invoiced" Landed Cost Amount

(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | - -The purpose of above ledger entries is to get that landed cost expense accounting gets invoice landed cost "accounting dimensions". - -2\. "**Estimated" landed cost not equal to "invoiced" landed cost** & **"Is matching adjusted" = No**. - -This last setup ("Is matching adjusted" = No) leads to NOT creating a landed cost adjustment which takes the difference to the product cost (product accounting), therefore that difference remains either in the credit side (estimated>invoiced) or in the debit side (estimated
(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | - -- In the case of an "account" landed cost type - -| | | | -| ------------ | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Account | Debit | Credit | -| [*G/L Item*] | "Invoiced" Landed Cost Amount | | -| [*G/L Item*] | | "Invoiced" Landed Cost Amount

(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | - -3\. "**Estimated**" landed cost **higher** than "**invoiced**" landed cost. **"Is matching adjusted" = Yes** - -This last setup ("Is matching adjusted" = Yes) leads to creating a landed cost adjustment which takes the difference to the product cost (credit side of product accounting). - -- In the case of a "product" landed cost type - -| | | | -| ------------------- | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Account | Debit | Credit | -| [*Product Expense*] | "Estimated" Landed Cost Amount | | -| [*Product Expense*] | | "Invoiced" Landed Cost Amount

(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | -| [*Product Asset*] | | Difference (estimated>invoiced) Landed Cost Amount | - -- In the case of an "account" landed cost type - -| | | | -| ----------------- | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Account | Debit | Credit | -| [*G/L Item*] | "Estimated" Landed Cost Amount | | -| [*G/L Item*] | | "Invoiced" Landed Cost Amount

(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | -| [*Product Asset*] | | Difference (estimated>invoiced) Landed Cost Amount | - -4\. "**Estimated**" landed cost **smaller** than "**invoiced**" landed cost. **"Is matching adjusted" = Yes** - -This last setup ("Is matching adjusted" = Yes) leads to creating a landed cost adjustment which takes the difference to the product cost (debit side of product accounting). - -- In the case of a "product" landed cost type - -| | | | -| ------------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Account | Debit | Credit | -| [*Product Asset*] | Difference (estimated
(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | - -- In the case of an "account" landed cost type. - -| | | | -| ----------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Account | Debit | Credit | -| [*Product Asset*] | Difference (estimated
(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | - -##### Cancel Matching - -A landed cost matched can be canceled by using header process button "**Cancel Matching**". Before that landed cost matching needs to be "Unpost". - -Cancel matching action implies that: - -- Current matched amounts are not removed from Matched Amount tab. -- A new matching needs to be executed in the corresponding landed cost purchase invoice(s). -- Correct matching amounts will then be updated in Matched Amount tab. - -#### Matched Amount - -Matched Amount tab is a read only tab that allows to review the purchase invoice lines matched against landed cost lines. - -#### Accounting Cost - -This tab provides Landed Cost document accounting information. - -As any other accounting tabs, this tab shows the ledger journal entries of landed cost posting. - -#### Receipt - -Receipt tab allows the user to select either the receipt(s) or receipt line(s) to which landed cost types booked are going to be allocated. - -Once **Landed Cost** header has been properly filled in and saved, a receipt(s) line can be registered in this tab. - -Landed cost amounts entered in the "Cost" tab can then be allocated/distributed among the receipt(s) entered here. - -Some relevant fields to note are: - -- **Good Receipt**: that is to select a goods receipt, therefore landed cost amounts will be distributed among all the lines of the goods receipt. -- **Good Receipt Line**: that is to select a specific good receipt line. - -Note that either a good receipt or a good receipt line needs to be selected in a record. - -#### Receipt Line Amount - -Receipt Line Amount is a read only tab that shows detailed information about the landed cost type line allocated to each receipt line, as well as the landed cost amount distributed to each receipt line. - -It is important to remark that the "Amount" distributed is calculated by taking into account "Costing" precision defined for the Currency. - -#### Accounting - -This tab provides Landed Cost Matching accounting information. - -### Bulk Posting - -!!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). - -The Bulk Posting functionality allows the user to post or unpost multiple records by selecting the corresponding records and clicking the **Bulk posting** button. In this case, this functionality can be used in the **Landed Cost** window and in the **Cost** tab. - -Also, the Accounting Status of the record/s is shown in the status bar, in form view, or in a column, in grid view. - -!!! info - For more information, visit [the Bulk Posting module user guide](../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). - ---- - -This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} by [Etendo](https://etendo.software){target="\_blank"}. - ---- -This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L.](https://etendo.software){target="_blank"}. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md new file mode 100644 index 0000000000..ea20317dc3 --- /dev/null +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md @@ -0,0 +1,206 @@ +--- +title: Goods Receipts +tags: + - Goods Receipts + - Procurement Process +--- + +# Goods Receipts + +:material-menu: `Application` > `Procurement Management` > `Transactions` > `Goods Receipt` + +A Goods Receipt is a document issued to acknowledge the receipt of the items listed in it. In other words, it is a document used to register in Etendo the specifics of items physically received in the warehouse. + +## Header + +Goods Receipts can be issued and booked in the header section of the goods receipt window. + +![Good receipts header](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/goodsreceipt2.png) + +The fields to fill in the **Goods Receipt header** are: + +- **Document Type**, which is filled in by default as "MM Receipt". +- **Warehouse**, where goods are going to be located. +- **Business Partner**, third party which delivers the goods. +- **Movement Date**, delivery date of the goods. +- **Accounting Date**, accounting date in case of posting the Goods Receipt. +- **Purchase Order**, purchase order number linked automatically by Etendo, in case the Goods Receipt is automatically created from a Purchase Order. +- **Order Reference**, Warehouse team can fill in here the Supplier's Delivery Note number, this way the internal Goods Receipt number and the Supplier's Delivery Note number are linked. + +In the **Status Bar** of the header, the user can find the following information: + +- **Document Status**: Document status of the receipt. +- **Invoice Status**: It indicates in % how much quantity of the receipt has been invoiced. + +**Once header information is properly filled-in, you can then go to the "Lines" tab in order to enter "Goods Receipt Line/s"**. + +!!! info + To learn how to enter goods receipt lines, visit the next section [Lines](goods-receipts.md#lines) + +If a **Goods Receipt** is completed and therefore **booked**: + +- The **quantity on hand of the item/s received is increased** by the quantity received. + +If a **"Completed" Goods Receipt is voided** because the goods have been returned to the supplier: + +- **The quantity on hand of the items/s returned is decreased** by the quantity of the goods returned. Etendo automatically creates a new "Goods Receipt" for exactly the same items but with "negative" quantities. + +!!! info + To learn more about Goods Returns, visit *Return to Vendor* and *Return to Vendor Shipment*. + +Supplier can send a "Purchase Invoice" together with the "Delivery Note" of the goods delivered, therefore: + +- From the Goods Receipt window, it is possible to generate the corresponding supplier's invoice, by using the header process button "**Generate Invoice from Receipt**". + +This action implies a **link between the goods receipt and the purchase invoice**, the user can be aware of when inquiring about the corresponding purchase invoice. + +!!! info + To learn more, visit [Purchase Invoice](purchase-invoice.md). + +## Lines + +Once the goods receipt header has been properly filled in and saved, each item received can be listed as a separate goods receipt line. + +There are several ways of creating goods receipt lines. + +1.**The user can always manually create goods receipt lines.** +That is the way the user could turn to in case there is not a booked purchase order nor a completed purchase invoice for the goods received they can retrieve data from. + +As a consequence, the information to manually fill in is: + +- the goods or items received +- the quantity received +- the storage bin where the items are going to be stored + +**Explode** button is shown when selecting a line with a non-stockable BOM product and the product has not already been exploded. When exploding a product, the bill of materials components the selected product consists of are shown in the shipment. Once you have exploded it, you cannot comprime it. You should delete all the lines (first bill of materials components and then the BOM product), and insert again the non-stockable BOM product. + +2.On the other hand, it is also possible to **"automatically" create goods receipt lines**, by using the header process button **"Create Lines From"**. + +This allows the user to select the orders or invoices pending to be received. + +For instance, once a purchase order is selected, the purchase order lines pending to be received are shown. + +Then, the user is able to select the purchase lines received, change the quantity if required, and get them located in the warehouse. + +Finally: + +- If a purchase order/line is selected, this action **links each good receipt line to the corresponding purchase order line**, same applies to purchase invoice. + +In the **Status Bar** of each line, you can find information about the **Invoiced quantity**, the number of invoiced products of the line. + +### Accounting + +Accounting information related to the material receipt. + +A **"Goods Receipts" can be posted** if the "**MaterialMgmtShipmentInOut**" table is set to Active for accounting in the \[*Active Tables*\] tab of the organization's general ledger configuration. + +A "Goods Receipt" posting looks like: + +![Good receipts posting](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/goodsreceipt3.png) + +Posting a "Goods Receipt" requires the calculation of the cost of the contained product/s. + +In the case of a goods receipt, that is: + +- the purchase price of the product/s +- or the default *standard cost* of the product/s in case of calculating cost by using an Standard *costing algorithm*. + +If there is not a related purchase order, the Costing Server process uses the newer of the following three values: + +- the last purchase order price of the receipt's vendor for the product. +- the purchase price list of the product. +- or the *default cost* of the product. + +Moreover: + +- The "Legal Entity" organization needs to have a validated *Costing Rule* configured. +- And the *Costing Background Process* needs to be scheduled for the *Client*, therefore it can search and allow that the *Costing Server* process calculates the cost of the transactions. + +Once the costs have been calculated, the **Goods Receipt can be posted** to the ledger. + +In the case of a receipt containing "Expense" product/s without the "Sales" checkbox selected, it is possible to use the product's purchase price instead of the product's cost to post the goods receipt. + +This works if the checkbox *Book Using Purchase Order Price* is selected for the product/s. + +In this case, it is required that a "Purchase Order" is related to the posted "Goods Receipt". + +### Voiding + +It is possible to totally void a goods receipt by using the header button **"Close"** and then selecting the action "**Void**". + +This action creates a **new document** that **reverses the goods receipt.** + +Void action allows to specify a "**Void Date**" and a "**Void Accounting Date**" of the new document: + +- **Void Date**: that is the movement date of the new document that reverse the goods receipt. +- **Void Accounting Date**: that is the accounting date of the new document that reverse the goods receipt. + +Both fields above take original document dates as default date and validate that the dates entered are not prior to the "Movement Date" and the "Accounting Date" of the Goods Receipt, respectively. + +Void action implies that: + +- Etendo automatically generates a **new document** in the "Goods Receipt" window, and **informs about the document number** created. The document number is also displayed in the description field of the Goods Receipt. This new document is created as described below: + - The "**transaction document**" used by Etendo is "**MM Receipt**". + - This document is **exactly the same as the original** one being reversed **but the movement quantity is negative.** + - Once the **new document** has been created, you can **change** both the "**Movement Date**" and the "**Accounting Date**" of the new document prior to getting it posted. + +### Landed Cost + +Landed Cost tab allows to allocate additional costs to the goods receipt. + +![Landed cost window](../../../../../assets/drive/1YND6qqNXSCzLiiq_PICSVr3GymXZi6_o.png) + +It is possible to enter as many landed cost types/lines as required. + +Some relevant fields to note are: + +- **Landed Cost Type**: that is the landed cost type that is going to be allocated to the goods receipt. +- **Invoice line**: that is to select the corresponding landed cost invoice line if any, that matches the landed cost type being entered. + If an invoice line is selected, the invoice line amount gets populated in the next field "Amount". +- **Amount**: that is the landed cost amount. This amount can be an "estimation" or a "real" amount in case of selecting an invoice line. +- **Landed Cost Distribution Algorithm**: that is the one distributed by Etendo "Distribution by Amount", which means that the landed cost amount is going to be distributed among the goods receipt lines proportionally by receipt line amount. + +Once all items above are filled in, including corresponding landed cost purchase invoice line, both "Goods Receipt" and Landed Cost *process matching* are executed by clicking on the "**Complete**" process button. + +## How to Reactivate Goods Receipts + +!!! info + To be able to include this functionality, the Warehouse Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Warehouse Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=EFDA39668E2E4DF2824FFF0A905E6A95){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Warehouse Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/warehouse-extensions/release-notes.md). + +From the Goods Receipt window, it is possible to reactivate a previously generated movement just by selecting the corresponding document and clicking the Reactivate button. + +Once the receipt is successfully reactivated, the state of the document changes to Draft as it can be observed in the status bar. + +![](../../../../../assets/drive/1-Z-wUYZfcGDizQ_Kkp8TUYXTs-KnM67H.png) + +!!! warning + Note: It is not possible to reactivate documents that include transactions with quantities exceeding the existing stock quantity for a certain product in a certain storage bin. The only exception is when the configuration of the storage bin allows Over Issue. For more information, visit [Storage Bin](../../warehouse-management/setup.md#storage-bin). + +## Bulk Posting + +!!! info + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +The Bulk Posting functionality allows the user to post or unpost multiple records by selecting the corresponding records and clicking the **Bulk posting** button. + +Also, the Accounting Status of the record/s is shown in the status bar, in form view, or in a column, in grid view. + +!!! info + For more information, visit [the Bulk Posting module user guide](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). + +## Bulk Completion + +!!! info + To be able to include this functionality, the Essentials Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Essentials Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=39AC2D9F72124AC7A1D0A3D005293C9E){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Essential Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/essentials-extensions/release-notes.md). + +The Bulk Completion functionality allows the user to complete, reactivate or void multiple records by selecting them and clicking the **Bulk Completion** button. This makes records management easier and more efficient, reducing the time spent processing individual records. + +!!! info + For more information, visit [the Bulk Completion module user guide](../../../optional-features/bundles/essentials-extensions/bulk-completion.md). + +--- + +This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} by [Etendo](https://etendo.software){target="\_blank"}. + +--- +This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L.](https://etendo.software){target="_blank"}. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md new file mode 100644 index 0000000000..811f6fa5fd --- /dev/null +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md @@ -0,0 +1,332 @@ +--- +title: Landed Cost +tags: + - Procurement Process +--- + +# Landed Cost + +:material-menu: `Application` > `Procurement Management` > `Transactions` > `Landed Cost` + +Landed Cost window allows the user to allocate additional costs such as freight, insurance or duties to goods receipt(s), therefore the cost of the products included in the receipt(s) is adjusted as applicable. + +All those costs are needed to place the product in the organization's warehouse. + +Every time that a landed cost is booked for a product receipt valued at "Average" cost, a landed cost adjustment is created. + +Landed costs distributed and allocated to products valued at "Average" cost imply a change in the inventory value of the product. In other words, the calculated cost ("Total Cost") of the product receipt will need to be adjusted the same as the "Average" cost of the product. + +!!! info + Note that the "Unit Cost" of the receipt transaction will not change as this type of adjustment is not a unit cost adjustment type but an "extra" cost. + +All of the above will have an accounting impact, therefore product inventory value can be the same as product accounting value. + +On the other hand, if a landed cost is booked for a product receipt valued at "Standard" cost, no cost adjustment will be created but a "Variance" between the "standard" cost defined for the product and its "actual" cost. This variance will need to be posted to a "Landed Cost Variance" account, so it can be later on analysed. + +Landed cost window allows both: + +- either to book "**estimated**" landed cost that can be later on matched against "actual" landed cost by landed cost type, +- or directly book "**actual**" landed cost by landed cost type. + +Landed cost window also allows to post landed costs once processed. + +"**Estimated**" Landed Cost scenario: + +- A purchase order is booked and after that the corresponding goods receipt and purchase invoice. + The "average" cost of the products included in the receipt is calculated at this point. +- After that "estimated" landed costs (i.e freight costs) are allocated to the goods receipt and booked in the landed cost window. + The cost of the products included in the receipt is then adjusted the same as products asset accounting. +- After that, a purchase invoice including the actual amount of freight cost is booked and posted to the ledger. +- Then, it is possible to match "estimated" landed cost against "invoiced" landed cost. + The cost of the products included in the receipt is adjusted once more if there are differences between estimated and actual landed cost amounts. + +"**Actual**" Landed Cost scenario: + +- A purchase order is booked and after that, the corresponding goods receipt and purchase invoice. + The "average" cost of the products included in the receipt is calculated at this point. +- After that, a landed cost document is created to record actual landed cost to the goods receipt. + The cost of the products included in the receipt is then adjusted the same as products asset accounting. + +In Summary, landed cost feature follows below detailed steps: + +- **Landed Cost Process**: + - A landed cost document is created including as many different landed cost types and amounts as required. + - This landed cost document can be related to a single goods receipt, to several goods receipts or to specific goods receipts lines. + - This landed cost document can record "actual" landed cost in case of selecting the corresponding invoice, therefore the landed cost process and matching is done in one step. + - Landed cost is processed. + - This action creates a *landed cost adjustmen* linked to the landed cost document. + This cost adjustment has as many adjustment lines as products included in the goods receipt(s) selected, therefore the cost of those products is adjusted as applicable. +- **Landed Cost Post**: + - Once a landed cost document is processed it can be posted to the ledger, therefore product(s) asset accounting is adjusted as well. +- **Landed Cost Matching**: + - Landed cost invoice is booked and posted to the ledger later on. + - After that the "estimated" landed cost booked in the landed cost document can be matched against actual landed costs by landed cost type in the landed cost invoice. + - Landed cost matching can generate an additional cost adjustment for the product(s) if estimated landed cost amounts were not the same as actual landed cost amounts. +- **Landed Cost Matching Post**: + - Once landed cost(s) are matched can be posted therefore: + - product(s) asset accounting is adjusted once more if applicable, + - and landed cost posting gets landed cost invoice *accounting dimensions*. + +## Header + +A Landed Cost document can be created, processed and posted in this window. + +![Landed cost header](../../../../../assets/drive/1YND6qqNXSCzLiiq_PICSVr3GymXZi6_o.png) + +Some fields to note are: + +- **Organization**: that is the organization or legal entity for which landed cost needs to be booked. +- **Reference date**: that is the date when the landed cost document is being created. + +**Cost** + +A Landed Cost Document can have as many cost (lines) as landed cost types to allocate to the Goods Receipt(s) selected. + +![Landed cost tabs](../../../../../assets/drive/1jbfoYTDqyRZiF3bTwPQkG8OmjpLr0zau.png) + +Some fields to note are: + +- Landed Cost Type: that is the landed cost type that is going to be allocated to the receipt(s) or receipt line(s) selected in Receipt tab. +- **Invoice line**: that is to select the corresponding landed cost invoice line if already booked that matches the landed cost type being entered. + If an invoice line is selected,the invoice line amount gets populated in the next field "Amount". +- **Amount**: that is the landed cost type amount. This amount can be "estimated" or "actual" in case of selecting an invoice line. +- **Currency**: that is the currency of the landed cost type. + - It is important to remark that a landed cost document can include as many landed cost types as required in the currency required. + For instance, a landed cost document can include two landed cost type lines one in USD and the other one in EUR. + In this scenario, a landed cost adjustment will be created including two lines. Cost adjustment amounts will be calculated in the currency configured for the legal entity product transaction belongs to. +- **Landed Cost Distribution Algorithm**: there is one algorithm available distributed by Etendo that is "Distribution by Amount". + This algorithm distributes landed cost type amount proportionally by receipt line(s) amount among the receipt(s) selected. + +Once a receipt(s) has been selected in Receipt tab, landed cost document (header) can be processed by using the process button "**Process**". + +This action creates a landed cost adjustment linked to the landed cost document. + +This cost adjustment has as many adjustment lines as products included in the goods receipt(s) selected, therefore the cost of those products is adjusted as applicable. + +Once processed, a landed cost document can be: + +- **"Reactivated"**, this action voids the landed cost adjustment linked to the landed cost document. +- or **"Post"**, therefore product asset accounting is also adjusted accordingly. + +**Landed Cost** posting creates the following accounting entries in case of a "Product" landed cost type: + +| | | | +| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | +| Account | Debit | Credit | +| Product Asset | "Estimated" Landed Cost Amount.

(\*)This ledger entry gets goods receipt "accounting dimensions" such as "Vendor" or "Product". See "Detail" link. | | +| Product Expense | | "Estimated" Landed Cost Amount | + +**Landed Cost** posting creates the following accounting entries in case of an "Account" landed cost type: + +| | | | +| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | +| Account | Debit | Credit | +| [*Product Asset*] | "Estimated" Landed Cost Amount.

(\*)This ledger entry gets goods receipt "accounting dimensions" such as "Vendor" or "Product". See "Detail" link. | | +| [*G/L Item*] | | "Estimated" Landed Cost Amount | + +#### Process Matching + +Matching between an "estimated" landed cost and an "invoiced" landed cost can be processed in: + +**1.** The **GOODS RECEIPT** window before processing and by using the process button "**Complete**" + +This scenario takes place whenever all landed cost related information below is available and entered in the Landed Cost tab of the **Goods Receipt** : + +- landed cost types +- landed cost amounts +- related landed cost invoice lines + +This scenario automatically creates: + +- a landed cost document in the **landed cost** window related to the goods receipt that contains all the information entered in the "Landed Cost" tab of the Goods Receipt. + This landed cost document is already processed and matched, therefore only actions missing are to post the landed cost document (header) and to post the landed cost matching. +- a landed cost adjustment that adjusts the cost of each product included in the Goods Receipt. + +**2**. The **Landed Cost PURCHASE INVOICE** window, by using the process button Match LC Cost which can be found in each landed cost purchase invoice line. After that **"Process Matching" check-box** is selected. + +This scenario takes place whenever: + +- all landed cost related data but landed cost invoice line information was entered in the Landed Cost tab of **Goods Receipt** window. +- all landed cost related data but landed cost invoice line information was entered in the Cost tab of **Landed Cost** window. + +This scenario automatically creates: + +- a new landed cost adjustment that adjust once more the cost of each product included in the Goods Receipt if: + - the landed cost type amount booked is not the same as the one invoiced + - and the check-box "Is matching adjusted" is selected. +- only action missing is to post the landed cost matching. + +**3.** The **LANDED COST** window, by using the process button "**Process Matching**" + +This scenario takes place whenever the matching has been executed in the landed cost purchase invoice, see scenario 2 above, but the check-box "Process Matching" was not selected there. + +This scenario automatically creates: + +- a new landed cost adjustment that adjusts once more the cost of each product included in the Goods Receipt if the landed cost type amount booked is not the same as the one invoiced and the check-box "Is matching adjusted" is selected. +- only action missing is to post the landed cost matching. + +**4.** The **LANDED COST** window, by using the process button "**Process**". + +This scenario takes place whenever all landed cost related information is entered in the **landed cost** window.: + +- landed cost types +- landed cost amounts +- related landed cost invoice lines +- and goods receipt(s) + +This scenario automatically creates: + +- a landed cost adjustment that adjust the cost of each product included in the Goods Receipt(s). +- only actions missing are to post the landed cost document (header) and to post the landed cost matching. + +#### Post Matching + +A landed cost matching can be posted, after being processed. This posting will have different ledger entries depending on the scenarios listed below: + +1\. "**Estimated**" landed cost **equal** to "**invoiced**" landed cost + +- In the case of a "product" landed cost type + +| | | | +| ------------------- | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Account | Debit | Credit | +| [*Product Expense*] | "Estimated"="Invoiced" Landed Cost Amount | | +| [*Product Expense*] | | "Estimated"="Invoiced" Landed Cost Amount

(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | + +- In the case of an "account" landed cost type + +| | | | +| ------------ | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Account | Debit | Credit | +| [*G/L Item*] | "Estimated"="Invoiced" Landed Cost Amount | | +| [*G/L Item*] | | "Estimated"="Invoiced" Landed Cost Amount

(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | + +The purpose of above ledger entries is to get that landed cost expense accounting gets invoice landed cost "accounting dimensions". + +2\. "**Estimated" landed cost not equal to "invoiced" landed cost** & **"Is matching adjusted" = No**. + +This last setup ("Is matching adjusted" = No) leads to NOT creating a landed cost adjustment which takes the difference to the product cost (product accounting), therefore that difference remains either in the credit side (estimated>invoiced) or in the debit side (estimated
(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | + +- In the case of an "account" landed cost type + +| | | | +| ------------ | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Account | Debit | Credit | +| [*G/L Item*] | "Invoiced" Landed Cost Amount | | +| [*G/L Item*] | | "Invoiced" Landed Cost Amount

(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | + +3\. "**Estimated**" landed cost **higher** than "**invoiced**" landed cost. **"Is matching adjusted" = Yes** + +This last setup ("Is matching adjusted" = Yes) leads to creating a landed cost adjustment which takes the difference to the product cost (credit side of product accounting). + +- In the case of a "product" landed cost type + +| | | | +| ------------------- | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Account | Debit | Credit | +| [*Product Expense*] | "Estimated" Landed Cost Amount | | +| [*Product Expense*] | | "Invoiced" Landed Cost Amount

(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | +| [*Product Asset*] | | Difference (estimated>invoiced) Landed Cost Amount | + +- In the case of an "account" landed cost type + +| | | | +| ----------------- | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Account | Debit | Credit | +| [*G/L Item*] | "Estimated" Landed Cost Amount | | +| [*G/L Item*] | | "Invoiced" Landed Cost Amount

(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | +| [*Product Asset*] | | Difference (estimated>invoiced) Landed Cost Amount | + +4\. "**Estimated**" landed cost **smaller** than "**invoiced**" landed cost. **"Is matching adjusted" = Yes** + +This last setup ("Is matching adjusted" = Yes) leads to creating a landed cost adjustment which takes the difference to the product cost (debit side of product accounting). + +- In the case of a "product" landed cost type + +| | | | +| ------------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Account | Debit | Credit | +| [*Product Asset*] | Difference (estimated
(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | + +- In the case of an "account" landed cost type. + +| | | | +| ----------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Account | Debit | Credit | +| [*Product Asset*] | Difference (estimated
(\*)This ledger entry gets landed cost invoice "accounting dimensions" such as "Business Partner". See "Detail" link. | + +#### Cancel Matching + +A landed cost matched can be canceled by using header process button "**Cancel Matching**". Before that landed cost matching needs to be "Unpost". + +Cancel matching action implies that: + +- Current matched amounts are not removed from Matched Amount tab. +- A new matching needs to be executed in the corresponding landed cost purchase invoice(s). +- Correct matching amounts will then be updated in Matched Amount tab. + +### Matched Amount + +Matched Amount tab is a read only tab that allows to review the purchase invoice lines matched against landed cost lines. + +### Accounting Cost + +This tab provides Landed Cost document accounting information. + +As any other accounting tabs, this tab shows the ledger journal entries of landed cost posting. + +### Receipt + +Receipt tab allows the user to select either the receipt(s) or receipt line(s) to which landed cost types booked are going to be allocated. + +Once **Landed Cost** header has been properly filled in and saved, a receipt(s) line can be registered in this tab. + +Landed cost amounts entered in the "Cost" tab can then be allocated/distributed among the receipt(s) entered here. + +Some relevant fields to note are: + +- **Good Receipt**: that is to select a goods receipt, therefore landed cost amounts will be distributed among all the lines of the goods receipt. +- **Good Receipt Line**: that is to select a specific good receipt line. + +Note that either a good receipt or a good receipt line needs to be selected in a record. + +### Receipt Line Amount + +Receipt Line Amount is a read only tab that shows detailed information about the landed cost type line allocated to each receipt line, as well as the landed cost amount distributed to each receipt line. + +It is important to remark that the "Amount" distributed is calculated by taking into account "Costing" precision defined for the Currency. + +### Accounting + +This tab provides Landed Cost Matching accounting information. + +## Bulk Posting + +!!! info + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +The Bulk Posting functionality allows the user to post or unpost multiple records by selecting the corresponding records and clicking the **Bulk posting** button. In this case, this functionality can be used in the **Landed Cost** window and in the **Cost** tab. + +Also, the Accounting Status of the record/s is shown in the status bar, in form view, or in a column, in grid view. + +!!! info + For more information, visit [the Bulk Posting module user guide](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). + +--- + +This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} by [Etendo](https://etendo.software){target="\_blank"}. + +--- +This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L.](https://etendo.software){target="_blank"}. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/manage-requisitions.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/manage-requisitions.md new file mode 100644 index 0000000000..f9c63b14b1 --- /dev/null +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/manage-requisitions.md @@ -0,0 +1,73 @@ +--- +title: Manage Requisitions +tags: + - Procurement Process + - Purchase Requisitions +--- + +# Manage Requisitions + +:material-menu: `Application` > `Procurement Management` > `Transactions` > `Manage Requisitions` + +Manage Requisitions window is intended to be used to provide an overall picture of the items needed. + +## Header + +This window allows the user to manage requisitions regardless of their current status, therefore they can change or close a requisition and create purchase orders for those demands. + +![Requisition window Header](../../../../../assets/drive/1yuE4xa0usvVzSdmthjDWdi12OAqTuJTe.png) + +A **requisition** with status "Completed" **can always be changed**, if required. The user needs to reactivate it and then change it and book it. + +It is also possible to **close a requisition in case there is no need of the included item/s anymore**, by using the menu button "**Close**" and then select the action "**Close**". + +Requisition lines status will then be changed to "Cancelled". + +Finally, it is also possible to **create purchase orders** for those **requisitions in status "Complete"**, by using the menu button "**Create Purchase Order**". + +In this case, a new window is shown for the user to fill in some data by taking into account that: + +- If there are **different suppliers in the requisition lines as well as price list**: + - the **defaulted ones** entered in the window "Create Purchase Order" **will be the ones used** in the purchase order. +- If there are **different suppliers in the requisition lines as well as price list**, and the user does not enter any defaulted ones in the window "Create Purchase Order": + - **the ones in the requisition lines will be the ones used** in the purchase orders. +- If **all the requisition lines have the same supplier and price list**: + - **there will not be any need for selected defaulted ones** in the window "Create Purchase Order", besides only one purchase order will be created. + +![Purchase order](../../../../../assets/drive/17OuNS8YpM0VC3MUkLO25DPPHCMwWjq8u.png) + +Etendo provides information about the purchase order/s number/s created after pressing the OK button in the "Create Purchase Order" window. + +This action links the requisition and the purchase order, and besides a purchase order line is created for each requisition line: + +- A **requisition** linked to a purchase order changes its status from **Completed** to **Closed**. +- A **requisition line** linked to a purchase order line changes its status from **Open** to **Closed**. + +Any **purchase order** created from a **Requisition**: + +- will be listed in the **"Purchase Order" window**. +- will have a "**Booked**" status +- and will contain **data inherited from the Requisition**, data such as: + - Order Date + - Scheduled Delivery Date + - Business Partner + - Price List + - Product/s + +## Lines + +The user can perform a set of actions regarding requisition lines. It is possible for them to either create lines or product demands or to cancel them. + +- **New product demands can be manually created** within a requisition by just **adding new requisition lines** before creating a purchase order. +- **Existing product demands or requisition lines can be cancelled**, if they are not required anymore, by using the header button "**Change Status**". + +### Matched PO (Purchase order) Lines + +This tab allows the user to either review the purchase order line automatically linked to a requisition line or to manually link an existing purchase order line to the corresponding requisition line. + +--- + +This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} by [Etendo](https://etendo.software){target="\_blank"}. + +--- +This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L.](https://etendo.software){target="_blank"}. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.md new file mode 100644 index 0000000000..e566f68e7d --- /dev/null +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.md @@ -0,0 +1,59 @@ +--- +title: Matched Purchase Invoices +tags: + - Procurement Process + - Purchase Orders +--- + +# Matched Purchase Invoices + +:material-menu: `Application` > `Procurement Management` > `Transactions` > `Matched Purchase Invoices` + +This window helps the user to post the discrepancies between inventory and financial accounting of those items for which the corresponding goods receipts were posted. + +Above mentioned discrepancies are mainly caused by differences between: + +- the **item's net unit price registered when booking the purchase order** and later on **posting the corresponding Goods Receipt.** +- and the **"final" item's net unit price registered when posting the purchase invoice.** + +In the window, there is a listing of all invoices that are matched to goods receipts. The matching of the documents is done when documents are created by using the information of the other document: for example by clicking the Generate Invoice from receipt on the goods receipt or by clicking the Create Lines from button when creating a goods receipt to select the invoice. + +![Matched Purchase Invoices window](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.png) + +### Matched Purchase Invoice + +Matched Purchase Invoice tab lists each invoice line posted linked to the corresponding goods receipt lines, which could also be posted or not. + +There is a "**Post**" header button which is the one that posts the discrepancies between inventory and financial accounting if any, once the proper line has been selected. + +The general process to post the discrepancies in accounting is detailed below: + +A *Matching Invoice* document can be posted if the cost of the products included in a *Goods Receipt* has been calculated. To obtain that: + +- A validated *Costing Rule* is required in the Matched Invoice's legal entity, +- and the background process *Costing Background Process* must be run. + +In the case of "Expense" product/s do not having the "Sales" checkbox selected, it is possible to use the product's purchase price instead of the product's cost whenever the checkbox *Book Using Purchase Order* Price is selected. In this case, it is required that a "Purchase Order" is related to the "Goods Receipt". + +### Accounting + +Accounting information related to the matched purchase invoices. + +## Bulk Posting + +!!! info + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +The Bulk Posting functionality allows the user to post or unpost multiple records by selecting the corresponding records and clicking the **Bulk posting** button. + +Also, the Accounting Status of the record/s is shown in the status bar, in form view, or in a column, in grid view. + +!!! info + For more information, visit [the Bulk Posting module user guide](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). + +--- + +This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} by [Etendo](https://etendo.software){target="\_blank"}. + +--- +This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L.](https://etendo.software){target="_blank"}. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md new file mode 100644 index 0000000000..d16b56d357 --- /dev/null +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md @@ -0,0 +1,31 @@ +--- +title: Pending Goods Receipts +tags: + - Goods Receipts + - Procurement Process +--- + +# Pending Goods Receipts + +:material-menu: `Application` > `Procurement Management` > `Transactions` > `Pending Goods Receipts` + +This window allows the user to: + +- **Use the Filter options** to narrow down the search of pending purchase orders to be delivered. It is possible to search by: + - Business Partner + - From Purchase Order Date -> To Purchase Order Date + - Purchase Order number +- Enter a **"Reception date".** +- **Select** the "**Order line/s of a purchase order/s" delivered** which are shown grouped by Business Partner and Purchase Order. +- **Change** the "**Quantity**" of the goods being receipt if needed. +- **Enter** the "**Goods receipt location**" or storage bin within a warehouse. +- **Process it** in order to create the corresponding goods receipts. + +![Pending goods receipts window](../../../../../assets/drive/1hGrJ6YXXd1p20ZdLQefX1o6_8nVogOd8.png) + +--- + +This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} by [Etendo](https://etendo.software){target="\_blank"}. + +--- +This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L.](https://etendo.software){target="_blank"}. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md new file mode 100644 index 0000000000..4359ff0fe3 --- /dev/null +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md @@ -0,0 +1,445 @@ +--- +title: Purchase Invoice +tags: + - Procurement Process + - Purchase Orders +--- + +# Purchase Invoice + +:material-menu: `Application` > `Procurement Management` > `Transactions` > `Purchase Invoice` + +## Overview + +The **Purchase Invoice** window is used to create, register, and manage supplier invoices for purchased goods and services. + +Purchase invoices are typically generated after a Goods Receipt is completed, ensuring that received quantities match the supplier's billing information. + +Invoices are created in two ways: + +1. Automatically, from a related Goods Receipt using the **Generate Invoice from Receipt** button in the Goods Receipt window. +2. Manually, by entering the invoice directly in this window. + +Each invoice defines the products or services, quantities, prices, taxes, and amounts to be paid to the supplier. + +When the invoice is posted, the corresponding purchase expenses are recognized in accounting. If a deferred expense plan is configured, expense recognition is distributed over time according to the defined schedule. + +!!! example "Typical Purchase Invoice Workflow" + 1. A Goods Receipt is completed for an existing Purchase Order. + 2. Open the **Purchase Invoice** window and create a new invoice record. + 3. Select the **Business Partner** (supplier). The system fills in the payment terms, payment method, and price list automatically. + 4. Go to the **Lines** tab and click **Create Lines From Receipt** to pull in the received items. + 5. Review the lines, verify quantities and prices, then click **Complete**. + 6. Post the invoice to the ledger using the **Post** button. + 7. Register the payment using the **Add Payment** button. + +## Header + +The **Header** contains the basic information for a purchase invoice. In most cases, select the **Business Partner**; the system fills the remaining fields from defaults and the selected partner's configuration. + +![Purchase invoice window](../../../../../assets/drive/1JvS1mOjiiyATJENTs5SuQIyEAr-UHmE3.png) + +Fields to note: + +- **Transaction Document**: defaults to *AP Invoice* (purchase invoice [document type](../../financial-management/accounting/setup/document-type.md)). Change it to *AP Credit Memo* (positive-credit type, not linked to orders or shipments) or *Reversed Purchase Invoice* (negative amounts, for returns). +- **Document No.**: supplier invoice number if allowed by sequence, otherwise an internal number is assigned. +- **Invoice Date**: date of the invoice, used to calculate the due date. +- **Accounting Date**: posting date for the ledger (defaults to Invoice Date). +- **Payment Terms**: defines when payment is due (for example, net 30 days). Automatically populated from the Business Partner configuration. +- **Payment Method**: defines the payment mechanism (for example, bank transfer or check). Automatically populated from the Business Partner configuration. +- **Supplier Reference**: optional reference number provided by the supplier. + +### Adding Lines + +Add invoice lines using one of the following methods: + +1. Click **Create Lines From Order** or **Create Lines From Receipt** to pull in pending items from a related document. +2. Click **Copy Lines** to copy lines from an existing invoice. +3. Add lines manually in the **Lines** tab when there is no related order or receipt. + +### Completing the Invoice + +Click **Complete** to finish the invoice. This creates the Payment Plan and updates the Payment Monitor. Non-stockable BOM products are exploded automatically if needed. + +After completing the invoice, the following actions are available: + +- **Post** the invoice to the ledger using the [Post/Unpost](#postunpost) button. +- **Void or Reactivate** the invoice using the [Reactivate](#reactivate) button. +- **Register a payment** using the [Add Payment](#add-payment) button. + +## Lines + +Once the Purchase Invoice header is saved, add one or more invoice lines for the products or expenses being billed. + +Fields to note: + +- **Financial Invoice Line**: Select this for lines that are not products (for example, a G/L item or an asset). The Product field is replaced by an Account field. +- **Attribute Set Value**: Shown if the product uses attributes (color, size, serial number, etc.). +- **Purchase Order Line / Goods Receipt Line**: Links the invoice line to the related Purchase Order or Goods Receipt line, if any. + +### Deferring Expenses + +Use deferred expenses to spread a cost over multiple accounting periods instead of recognizing it all at once. + +- **Deferred Expense**: Select this to spread the expense over time and reveal the expense-plan fields. +- **Expense Plan Type**: Frequency of recognition (currently: monthly). +- **Period Number**: Number of periods over which to distribute the expense. +- **Starting Period**: First open accounting period when recognition begins. + +These expense-plan values can be defaulted from the product configuration. If an expense plan is used, the invoice accounting follows that plan. + +!!! example "Deferred Expense: Annual Insurance" + A company purchases business insurance for a full year at a cost of 1,200 USD. + + - **Deferred Expense**: selected + - **Expense Plan Type**: Monthly + - **Period Number**: 12 + - **Starting Period**: January + + The system recognizes 100 USD per month over 12 months instead of expensing the full 1,200 USD in a single period. + +### Explode + +The **Explode** button appears when the selected line contains a non-stockable BOM product that has not been exploded yet. Exploding replaces the BOM line with its individual components in the invoice. + +!!! warning + This action cannot be undone. To revert it, delete the component lines first and then re-add the non-stockable BOM product. + +### Match LC Cost + +The **Match LC Cost** button matches the **estimated landed cost** defined in the Landed Cost window with the **invoiced landed cost** entered in an invoice line. + +This option is available when the purchase order or invoice line contains a **product** or **account** configured as a landed cost type. Both costs must belong to the **same landed cost type** to be matched. + +Matching helps to: + +- Reconcile estimated and invoiced landed costs. +- Keep product costs accurate. +- Generate the correct accounting entries. + +After clicking **Match LC Cost**, the pick-and-edit window opens. Only **processed Landed Cost documents** are displayed. + +From this window: + +- Select the corresponding landed cost document. +- Enter the amount in **Matched Amt**. +- Enable **Process Matching** to complete the process immediately. + +The **Is Matching Adjusted** checkbox controls how differences between estimated and invoiced costs are handled: + +- **Checked**: creates an additional landed cost adjustment to update the product cost. +- **Unchecked**: no cost adjustment is created. + +#### Matching Scenarios + +| Scenario | Is Matching Adjusted | Result | +|---|---|---| +| Estimated = Invoiced | Any | Only matching is posted to the ledger. No adjustments are created. | +| Estimated ≠ Invoiced | Checked | A landed cost adjustment is created. Product cost is updated to the invoiced amount. Matching and adjustment are posted. | +| Estimated ≠ Invoiced | Unchecked | Only matching is posted. Product cost is not modified. | + +### Line Tax + +The **Line Tax** tab is read-only and is automatically populated for each invoice line when the invoice is completed. It details the tax information for each line based on the Tax field, which is pre-filled according to the Taxes Setup. + +## Tax + +The **Tax** tab summarizes tax-related information for the whole purchase invoice. It contains one record per tax rate used in the invoice. + +The **Tax Amount** field reflects the tax value calculated automatically based on the tax rate and tax base settings. + +!!! info + It is possible to add a feature that allows controlled adjustments to invoice tax amounts to reconcile small **rounding differences** with external systems or when invoices are submitted to **governmental entities**. It supports both **sales** and **purchase** invoices, offers **manual and automated adjustments** for minimal corrections at cents level, and records all changes for **auditability**, ensuring the final invoice total matches external, governmental, or regulatory requirements. + + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. + + For more information, visit: [Adjust Invoice Tax user guide](../../../optional-features/bundles/financial-extensions/adjust-invoice-tax.md) + + This functionality is compatible from Etendo 23. + +## Basic Discounts (TO CHECK) + +This tab lists information about the discounts automatically applied based on the supplier configuration and / or manually entered for the purchase invoice. + +Learn [more](../../master-data-management/master-data.md#basic-discount). + +## Payment Plan (TO CHECK) + +The payment plan tab lists the scheduled payments expected against the invoice. + +The payment plan of a non paid invoice can be changed: + +- the payment "expected date" can be directly changed if required in this tab +- the payment "expected date", the "payment method" and the "outstanding amount to be paid" among other can be changed if required by using the Editable Payment Plan advanced feature. + +## Reversed Invoices (TO CHECK) + +This tab allows the user to select the invoices (if any) being reversed by the invoice being created. When the user voids an existing invoice the reverse invoice is automatically created by Etendo and linked to the original invoice being reversed. In case of creating a Reverse Purchase Invoice which partially voids an existing invoice/s, the user must manually select the invoice/s being reversed in this tab. + +As already described purchase invoices can be reversed without any problem, if required. + +If a purchase invoice is totally voided: + +Etendo informs about the Reversed Invoice number automatically created + +VA + +the original invoice voided is listed in the "Reversed Invoices" tab of the "Reversed Purchase Invoice" + +VA + +If a purchase invoice/s require to be partially voided: + +you should manually add it/them in the "Reversed Invoices" tab of the "Reversed Purchase Invoice" documents used to void an invoice/s. + +## Exchange Rates (TO CHECK) + +The exchange rate tab allows to enter an exchange rate between the organization's general ledger currency and the currency of the supplier's invoice to be used while posting the invoice to the ledger. + +Openbravo allows to manage different currencies within an organization or business unit. + +Nowadays, it is very common for the organizations located in a country to make business with third parties located abroad, and even more, it could also happen that an organization needs to post the transactions to general ledgers configured in different currencies. +To learn more visit General Ledger Configuration. + +Above described business scenario, implies the need of managing exchange rates between the organization's general ledger currency and the supplier's invoice currency to be used while posting the supplier's invoice to the ledger/s. + +This tab allows you to enter: + +either an exchange rate between the organization's general ledger/s currency and the supplier's invoice currency +or the total foreign invoice amount/s, therefore Openbravo can calculate the corresponding exchange rate/s +Additionally, Openbravo has a "central" repository of exchange rates which are used in case there is no an exchange rate defined at document level. + +## Accounting (TO CHECK) + +Accounting information related to the purchase invoice + +For more details please review the accounting article. + + +A purchase invoice can be posted to the ledger when required at a given "Accounting Date" by using the process button "Post". + +Purchase invoice posting creates the following accounting entries: + +Account Debit Credit Comments +Product Expense Line Net Amount One per invoice line +Tax Credit Tax Amount One per tax line. +Discount Product Expense Discount amount One per invoice line (if discount exists) +Vendor Liability Total Gross Amount One per invoice + +Same way, a Purchase Invoice including a purchase invoice line with an expense plan configured creates the following accounting entries. +For instance a company purchasing a business insurance for the duration of a year would want to distribute that expense over 12 months. + +Posting record date: Accounting Date: + +Account Debit Credit +Product Deferred Expense Line Net Amount +Tax Credit Tax Amount +Vendor Liability Total Gross Amount +Posting record date: Accounting Date + 1 month: + +Account Debit Credit +Product Expense Line Net Amount/12 +Product Deferred Expense Line Net Amount/12 +Posting record date: Accounting Date + 2 months: + +Account Debit Credit +Product Expense Line Net Amount/12 +Product Deferred Expense Line Net Amount/12 +..... + +Posting record date: Accounting Date + 12 months: + +Account Debit Credit +Product Expense Line Net Amount/12 +Product Deferred Expense Line Net Amount/12 +Voiding +It is possible to totally void a purchase invoice, by using the header button "Reactivate" and then selecting the action "Void". +This action creates a new document that reverse the invoice. + +Void action allows to specify a "Void Date" and a "Void Accounting Date" for the new document that reverse the invoice. + +Both "date" fields above take the current date as default date and validate that the dates entered are not prior to the invoice date and the invoice accounting date, respectively. + +Overall "Void" action implies that: + +Openbravo automatically generates a new document in the "Purchase Invoice" window that reverse the "original" invoice. +Openbravo also informs about the new document number. This new document is created as described below: +The "transaction document" used by Openbravo is "Reversed Purchase Invoice". To learn more visit Document Type. +This document is exactly the same as the original one being reversed but the invoiced quantity is negative. +Once the new document has been created, you can change both the "Invoice Date" and the "Accounting Date" of the new document prior to get it posted. +The "Reversed Invoices" tab list the original invoice being reversed as now both of them are linked. +To learn more visit Reversed Invoices. +The reversed document posting creates the following accounting entries: + +Account Debit Credit Comments +Product Expense Line Net Amount One per invoice line +Tax Credit Tax Amount One per tax line. +Vendor Liability Total Gross Amount One per invoice +And it is also possible to partially void a supplier invoice by: + +manually creating any of the available reversed purchase documents, in the "Purchase Invoice" window: +"AP Credit Memo" or +"Reversed Purchase Invoice" +which besides must be manually linked to the invoice/s being reversed in the "Reversed Invoices tab". +To learn more visit Reversed Invoices. +The "AP Credit Memo" posting looks the same as the "Reversed Purchase Invoice" posting. + +The main different between those two purchase reversed document types is: + +AP Credit Memo invoiced quantity is a positive quantity +and Reversed Purchase Invoice quantity is a negative quantity +We strongly recommend you to use the "Reversed Purchase Invoice" document type while partially voiding supplier's invoices. + + +## Buttons + +### Post/Unpost + +Post a purchase invoice to the ledger at a given Accounting Date using this button. Once posted, unpost it using the same button. + +### Reactivate + +![pop-up-reactivate](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/pop-up-reactivate.png) + +This button provides two options for a Completed invoice: + +- **Reactivate**: returns the record from *Completed* to *Draft* status, allowing edits without creating a new document. Use this option when the invoice contains errors that need correction before reposting. +- **Void**: creates a new document that fully reverses the invoice. Use this option when the invoice is no longer valid and needs to be cancelled. + +!!! example "When to Use Each Option" + - Use **Reactivate** when a price or quantity was entered incorrectly and the invoice has not been paid yet. + - Use **Void** when goods are returned to the supplier and the entire invoice needs to be cancelled. + +**Voiding an invoice** + +![pop-up-void](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/popup-void.png) + +When voiding, specify the following fields for the reversal document: + +- **Void Date**: movement date of the reversal document. Defaults to the current date and cannot be prior to the original Invoice Date. +- **Void Accounting Date**: accounting date of the reversal document. Defaults to the current date and cannot be prior to the original Accounting Date. +- **Supplier Reference**: optional reference number for the reversed document. Enter it here or leave the field blank to complete it later. + +Etendo automatically generates a new document in the *Purchase Invoice* window that reverses the original invoice and informs about the new document number. + +The reversal document uses the *Reversed Purchase Invoice* transaction document type, which is identical to the original but with negative invoiced quantities. + +Once the reversal document is created, change the *Invoice Date* and *Accounting Date* if needed before posting. + +The *Reversed Invoices* tab links both the original and the reversal documents. + +**Partially voiding an invoice** + +It is also possible to partially void a supplier invoice by manually creating one of the following reversed purchase documents in the [Purchase Invoice](purchase-invoice.md) window: + +- **AP Credit Memo**: invoiced quantity is positive. +- **Reversed Purchase Invoice**: invoiced quantity is negative. + +The created document must be manually linked to the invoice being reversed in the **Reversed Invoices** tab. + +To learn more, visit [Reversed Invoices](../../sales-management/transactions.md#reversed-invoices). + +The **AP Credit Memo** posting looks the same as the **Reversed Purchase Invoice** posting. The main difference between the two document types is: + +- **AP Credit Memo**: invoiced quantity is a positive quantity. +- **Reversed Purchase Invoice**: invoiced quantity is a negative quantity. + +!!! note + Use the **Reversed Purchase Invoice** document type when partially voiding supplier invoices. + +### Add Payment + +Register one or more payments against a purchase invoice using the **Add Payment** button, which opens the Add Payment pop-up window. + +### Bulk Posting + +!!! info + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +The Bulk Posting functionality allows the user to post or unpost multiple records by selecting the corresponding records and clicking the **Bulk Posting** button. + +The Accounting Status of each record is shown in the status bar in form view, or in a column in grid view. + +!!! info + For more information, visit [the Bulk Posting module user guide](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). + +### Bulk Completion + +!!! info + To be able to include this functionality, the Essentials Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Essentials Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=39AC2D9F72124AC7A1D0A3D005293C9E){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Essential Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/essentials-extensions/release-notes.md). + +The Bulk Completion functionality allows the user to complete, reactivate, or void multiple records by selecting them and clicking the **Bulk Completion** button. This makes records management easier and more efficient. + +!!! info + For more information, visit [the Bulk Completion module user guide](../../../optional-features/bundles/essentials-extensions/bulk-completion.md). + +!!! warning + The bulk voiding option fails when the [Purchase Invoice Validation](../../../optional-features/bundles/procurement-extensions/purchase-invoice-validation.md) module is installed. This is because the module includes a default preference that prevents the duplication of invoices with the same business partner, accounting year, and supplier reference. Since bulk voiding attempts to reverse invoices, it leads to duplication, as the supplier reference for each reversed invoice cannot be modified. As a result, the module prevents the bulk voiding process from functioning. + ![popup-bulk-void](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/popup-bulk-void.png) + +### Remove Payment + +The Payment Removal functionality deletes and reactivates payments. It also allows eliminating and reactivating bank transactions and reconciliations. + +!!! info + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +To remove a payment, select the corresponding document and click the **Remove Payment** button. The following related records are also removed: + +- If an order is associated with the invoice, the link between the order and the payment is removed (**Purchase Order** window > **Payment Plan** tab). +- If the payment is in *Deposited/Withdrawn not cleared* status in the financial account, the transaction is also deleted (**Financial Account** window > **Transaction** tab). +- If the payment is reconciled through an automatic method, the bank statement line and the bank reconciliation line are also deleted (**Financial Account** window > **Imported Bank Statements** and **Reconciliations**). + +!!! info + If the payment is posted, the accounting entry is deleted too. + +![](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/PRpic4.png) + +### Unvoid + +!!! info + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the [marketplace](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +The **Unvoid** button reactivates voided purchase invoices. Select the invoice and click **Unvoid** to restore it. + +![](../../../../../assets/drive/1UisxZzbpppLvN_rdL__TJg8tLeh5sMfW.png) + +Once the process is finished, the purchase invoice status turns to *Complete*. + +!!! note + In the case of the standard version of the module, also unvoid the corresponding reversed invoice. + +!!! warning + This reactivation process affects the accounting. If the original information is not manually removed from the reactivated document, accounting entries are doubled. + +!!! info + Check the Technical documentation about [Advanced Financial Docs Processing](../../../../../developer-guide/etendo-classic/bundles/financial-extensions-bundle/overview.md#advanced-financial-docs-processing) to extend the process. + +### Modify Payment Plan + +!!! info + To be able to include this functionality, the Advanced Bank Account Management module of the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +The Advanced Bank Account Management module adds a **Bank Account** field to the Purchase Invoice header. This field is automatically filled with the bank account related to the address or business partner of the invoice. The **Modify Payment Plan** button is also added for flexible payment management. + +![bank-account.png](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/bank-account.png) + +!!! info + For more information, visit the [Advanced Bank Account Management user guide](../../../optional-features/bundles/financial-extensions/advanced-bank-account-management.md). + +## Intercompany + +When orders or invoices involve two or more organizations that belong to the same client, this functionality automatically generates the corresponding inverse document. + +!!! info + For more information, visit [the Intercompany module user guide](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/intercompany.md). + +!!! info + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +--- + +This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} by [Etendo](https://etendo.software){target="\_blank"}. + +--- +This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L.](https://etendo.software){target="_blank"}. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md new file mode 100644 index 0000000000..3b19dc9fa1 --- /dev/null +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md @@ -0,0 +1,213 @@ +--- +title: Purchase Order +tags: + - Purchase Orders + - Procurement Process +--- + +# Purchase Order + +:material-menu: `Application` > `Procurement Management` > `Transactions` > `Purchase Order` + +Purchase Order window allows the user to manage orders which once booked will be sent to the external suppliers. In other words, it is a document to register products and/or services to be purchased and documented. + +![Purchase order window](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchaseorder.png) + +Once the document is booked, it can be sent to the external supplier and it can be prepaid if required. + +Purchase orders can be created and booked in the header section of the purchase order window. + +## Header + +The **Purchase order header** allows you to enter the following information: + +- **Organization:** Organizational entity within client. +- **Transaction Document**, which in this case is defaulted as "**Purchase Order**". +- **Document No**, or the Company purchase order number. +- **Order date:** This date is also defaulted by Etendo based on the system date, but it can always be changed. +- **Business Partner**: End-user needs to select the supplier to which the purchase order is being issued. +- **Partner Address**: Automatically populated once the business partner is selected based on the address or location set us "Ship to Address". +- **Warehouse**: Regardless it is defaulted by Etendo based on the "Profile" selected options, it must be verified by the end-user. +- **Scheduled Delivery Date**: This is the date when the organization or legal entity requires the items to be delivered. +- **Payment Method**, **Payment Terms** and **Price List**: These ones are defaulted by Etendo once a business partner is selected. +- **Order Reference**, free text which can be found under "More Information" section, you can use it to save the supplier order number, if any. + +In the **Status Bar** of the header, the user can find the following information: + +- **Document Status**: Document status of the order. The order can be in booked, draft, closed status, among others. +- **Total Gross Amount**: Total Gross amount of the order. +- **Total Net Amount**: Total Net amount of the order. +- **Currency**: Currency of the order. +- **Delivery Status**: It indicates in % how much quantity of the order has been received. +- **Invoice Status**: It indicates in % how much quantity of the order has been invoiced. + +**Once header information is properly filled-in, you can go to the "Lines" tab in order to enter purchase order line/s information**. + +!!! info + To learn how to enter purchase order lines, visit the next section [Lines](purchase-order.md#lines). + +It is possible to take up to **three possible actions regarding a purchase order**, by using the **header button "Book"**: + +- **Process it**, in case you might want to process it but not to book it as final, because it could be you might need to change it later on. +- **Void it**, in case that purchase order is not required anymore and therefore needs to be voided. +- **Book it**, in case it is correct and final. + +!!! info + If there are non-stockable BOM products and they have not been exploded, the Book button explodes them automatically. + + +## Lines + +Once the purchase order header has been properly filled in and saved, each purchase order line can be created in this tab. + +Purchase order lines can be created in three different ways: + +**1\. By manually creating new record/s in the "Lines" tab**. + +The purchase order fields you can fill in are described below: + +- **Product**. You can select an item or product from the list or use the product selector icon. +- **Ordered quantity**, or **Operative Quantity** if the product has an *alternative unit of measure (AUM)* configured. This is the quantity needed of the product/item. +- Product's **UOM**, or product's **Alternative UOM** depending on product configuration in regards to unit of measure. +- **Attribute Set Value. An attribute associated with a product as part of an attribute set.** +- **Net Unit Price**. This one is coming from the Price List selected in the header, but it could always be changed. +- **Line Net Amount. The final amount of a specified line, based only on quantities and prices.** +- **Tax**. Purchase tax is normally filled in by the system, depending on Taxes setup. + +**2\. By retrieving all the lines from previously created purchase orders.** In this case, you must use the process button "**Copy from Orders**". + +This process button enables the **Copy from Orders Pick and Edit** window. + +"Copy from Orders Pick and Edit" window allows you to search the orders to copy by using the filter options available. + +The lines information of the selected orders will be inserted in the purchase order line/s, then that information can be manually changed. + +**3\. By copying lines from other purchase orders.** + +In this case, you must use the process button **"Copy Lines".** + +This process button enables a new window named "Copy Lines from order" which allows you to create order lines by selecting the products already purchased from the supplier of the order by taking into account the *Consumption days* configured for the supplier. + +In the **Status Bar** of each line, you can find information about: + +- **Delivered quantity**: number of received products of the line. +- **Invoiced quantity**: number of invoiced product of the line. + +### Explode button + +Explode button is shown when selecting a line with a non-stockable BOM product and the product has not already been exploded. When exploding a product, the bill of materials components the selected product consists of are shown in the order. + +!!! info + Once you have exploded it, you cannot comprime it. You should delete all the lines (first bill of materials components and then the BOM product), and insert again the non-stockable BOM product. + +### Line Tax + +For each purchase order line, Etendo automatically populates the line tax related information in this tab. + +Line tax tab informs about each purchase order line: + +- **applied tax rate** +- **calculated tax amount** +- **taxable amount** + +!!! info + It is not possible to either manually create a new line or modify existing ones. + +### Basic Discounts + +Lists information about discounts automatically applied based on the supplier configuration and / or manually entered for the purchase order. + +![Basic discounts](../../../../../assets/drive/1AavUV8S8kQ2dp0P_W9lw06XfmAf5d_g-.png) + +### Payment Plan + +This shows the total amount expected to be paid upon order booking as well as the amount/s pre-paid or paid against the invoice/s for the order. + +Payment Plan information is required at order level because suppliers could ask for a **pre-payment** of all or part of a debt prior to its due date. + +Purchase order payment plans **do not show nor manage valid due dates**, but the payment plan of the corresponding purchase invoice/s. + +This tab also shows information about the regular payments received against the invoice/s for this order, as amounts paid. + +Finally, a payment plan of a purchase order will be **removed**: + +- if the purchase order is **reactivated** +- or if the purchase order is **voided** + +### Payment Details + +Displays the details of the payments (pre-payments or regular payments) made for the order or for the invoice/s of the order. + +## How to Reactivate a Closed Purchase Order + +!!! info + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the [marketplace](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +!!! warning "Dependency Notice" + This module depends on the [**Bulk Completion**](../../../optional-features/bundles/essentials-extensions/bulk-completion.md) module, as **order** processing actions must be performed using modern processes that allow the triggering of Hooks, instead of legacy processing. Due to this requirement, the legacy **close/reactivate** actions for orders will be hidden and these actions will only be available through the **Bulk Completion** button. + +Etendo allows the user to reactivate closed purchase orders by selecting the needed one/s and clicking the Undo Close button. + +![](../../../../../assets/drive/1cyLa7pjnsNgXtnSEK2lZX9s35imhD2Kq.png) + +Once the process is finished, the purchase order status turns to booked. + +!!! info + Check the Technical documentation about Advanced Financial Docs Processing to extend the process. + +## Payment Removal + +The aim of this functionality is to delete and reactivate payments in an agile and easy way. Also, it allows eliminating and reactivating bank transactions and reconciliations. + +!!! info + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +From this window, it is possible to remove payments associated with a purchase order by selecting the corresponding document and then clicking on the Remove Payment button. If there is an invoice associated with the order, the relationship of this invoice to the payment in question will also be removed (Purchase Invoice window > Payment Plan tab). + +If the payment is included in the financial account, i.e., if it is in Deposited/Withdrawn not cleared status, the transaction in it will also be deleted (Financial account window > Transaction tab). + +If the payment is reconciled through an automatic method, then in addition to the transaction in the financial account, the line of the bank statement to which it was linked (Financial Account window > Imported Bank Statements) and the corresponding line of the bank reconciliation (Financial Account > Reconciliations) will be deleted. + +!!! info + If the payment is posted, the accounting entry is deleted too. + +![](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/PRpic2.png) + +## Intercompany + +In case the user has to create orders or invoices among two or more organizations that are different but belong to the same client, this functionality allows automatically generating the corresponding inverse document. + +!!! info + For more information, visit [the Intercompany module user guide](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/intercompany.md). + +!!! info + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +## Bulk Completion + +!!! info + To be able to include this functionality, the Essentials Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Essentials Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=39AC2D9F72124AC7A1D0A3D005293C9E){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Essential Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/essentials-extensions/release-notes.md). + +The Bulk Completion functionality allows the user to complete, reactivate or close multiple records by selecting them and clicking the **Bulk Completion** button. This makes records management easier and more efficient, reducing the time spent processing individual records. + +!!! info + For more information, visit [the Bulk Completion module user guide](../../../optional-features/bundles/essentials-extensions/bulk-completion.md). + +## Advanced Bank Account Management + +!!! info + To be able to include this functionality, the Advanced Bank Account Management module of the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +This module adds a new field to the header of the Purchase Order window: **Bank Account**. This field is automatically filled with the bank account related to the adress or business partner of the order. + +![bank-account-3.png](../../../../../assets/legacy/bank-account-3.png) + +!!! info + For more information, visit the [Advanced Bank Account Management user guide](../../../optional-features/bundles/financial-extensions/advanced-bank-account-management.md). + +--- + +This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} by [Etendo](https://etendo.software){target="\_blank"}. + +--- +This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L.](https://etendo.software){target="_blank"}. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition-to-order.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition-to-order.md new file mode 100644 index 0000000000..0ce705ee23 --- /dev/null +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition-to-order.md @@ -0,0 +1,36 @@ +--- +title: Requisition to Order +tags: + - Procurement Process + - Purchase Requisitions + - Purchase Orders +--- + +# Requisition to Order + +:material-menu: `Application` > `Procurement Management` > `Transactions` > `Requisition to Order` + +Requisition to Order window shows all the "Completed" requisitions which match the criteria used in the "filter" section and it also shows the requisition lines selected as locked, therefore the same product demand can not be included more than once in a purchase order. + +![Requisition to order](../../../../../assets/drive/1Xl_R8oaUrOaO0SK4wB5BYNw3wJDEjHBX.png) + +In other words, the upper section of this window shows the requisition lines found that are not linked to an order yet. +Those are the lines which can be added by the user to the "Lock" area in the bottom section of the window. + +A requisition line locked can not be changed by any other user, until the one who locked it gets it unlocked. +That way, during the time that the requisition lines are locked: + +- The same product demand will not be included in a purchase order, by mistake. +- The purchase team will have the opportunity to review the stock and contact different vendors if required to negotiate a price for the products. +- If there is no activity during 3 days, the system removes the lock from the lines. + +A requisition can be unlocked manually by the purchase manager or the one who locked it by moving it back to the upper part of the "Requisition to Order" screen by using the "Remove" button. + +Once the product demands are clear and locked, the last step to take in this window is to create a purchase order for those needs using the process button "Create". + +--- + +This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} by [Etendo](https://etendo.software){target="\_blank"}. + +--- +This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L.](https://etendo.software){target="_blank"}. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md new file mode 100644 index 0000000000..1d31e1be84 --- /dev/null +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md @@ -0,0 +1,76 @@ +--- +title: Requisition +tags: + - Procurement Process + - Purchase Requisitions +--- + +# Requisition + +:material-menu: `Application` > `Procurement Management` > `Transactions` > `Requisition` + +A Requisition is a document that specifies a request to order products. + +The user can create requisitions and monitor them in this window: + +![Requisition window](../../../../../assets/drive/1ihaEseE5RnNH7INNbaRLyvZC0P2q-hTl.png) + +## Header + +Requisition header allows entering the following data: + +- The business partner or supplier, this is an optional field that could be filled in by the requester in case it is known, therefore: + - The supplier entered in the header will be the one used for every requisition line unless it is changed at lines level for a particular line. + - If there is no supplier entered in the requisition header the one setup by default for the product in its master data window, *Purchasing* tab will be used. + - If there is no business partner or supplier in the header, or in the lines, or setup in the product, the user will have to enter it while creating the purchase order from the requisition. +- The purchase price list. This is also an optional field to be filled-in, in case it is known by the requester and its behaviour is the same as described above as it is linked to the Business Partner. + +Besides, the system populates the following data: + +- The document No., which is the Requisition number. +- The requester, which is the user entering the requisition. + +![Requisition](../../../../../assets/drive/1G5HR3bMmJXW837o-6qzZ0CTe418q5JB7.png) + +The requester can then move to the "Lines" tab to enter additional data. + +## Lines + +Each requisition line shows a product demand for a specific date. + +Requisition "Lines" tab collects the following demand data: + +- The *need by date*, that is the date when the product is required to arrive. +- The *product*, items/products which need to be purchased. +- The *quantity* requested, or the *operative quantity* requested if the product has an *alternative unit of measure (AUM)* configured. +- The product's *UOM*, or product's *Alternative UOM* depending on product configuration in regards to measure unit. +- The *business partner:* This is an optional field the user can enter if the supplier entered at the requisition header needs to be changed for a particular line. + +!!! info + If there is not a supplier entered at the requisition header, neither at the requisition line, the supplier used will be the one setup by default for the product, therefore this field at line level can also be used to overwrite that defaulted one. + +- The *purchase price list*: This is also an optional field that can be entered if the price list entered at the header level or the default product price list information should be overwritten for a particular line. +- The *net list price*: This one is the price of the corresponding price list for a given date. It's an optional field that can be filled in automatically based on the price list entered at the header level or it could be overwritten by the user for a particular product line. +- The *net unit price:* This one can be either equal to the net list price or not, based on the formula: \[net unit price = net list price - discount\]. It is an optional field that can be filled in automatically based on the price list entered at the header level or it could be overwritten by the user for a particular product line. +- The *discount*, if any, is based on a used price list. + +![Requisition Lines](../../../../../assets/drive/1CtrCvBCrvUuxYDlaFysmkKu0-0XhemfC.png) + +It is possible to enter as many requisition lines as products demand. + +The last step is to register the *Requisition* as *Complete* by using the header button "Complete", then: + +- *Requisition header status bar* informs us that the Requisition is *Completed*. +- *Requisition lines status bar* informs us that the *Matched purchase order quantity* for each line is equal to 0**, as there is no purchase order linked to each requisition line yet, and the requisition line/s status is *Open*. + +It is important to remark that *Requisitions* does not have any impact on: + +- Items quantity on hand +- Items costing + +--- + +This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} by [Etendo](https://etendo.software){target="\_blank"}. + +--- +This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L.](https://etendo.software){target="_blank"}. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md new file mode 100644 index 0000000000..b6dce59e49 --- /dev/null +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md @@ -0,0 +1,99 @@ +--- +title: Return to Vendor Shipment +tags: + - Procurement Process +--- + +# Return to Vendor Shipment + +:material-menu: `Application` > `Procurement Management` > `Transactions` > `Return to Vendor Shipment` + +From this window, the user can deliver the returned goods to the vendor. + +## Header + +The user can create and edit a goods receipt. + +The **RMA vendor ref.** field is populated automatically or not based on: + +- If it is filled before selecting a line, then it will not be populated automatically to avoid override it. +- If you select a line/s where all of them belong to the same Return to Vendor document, it will be populated automatically. +- If you select a line/lines but one of them belongs to a different Return to Vendor document, then it will not be populated automatically. + +Once the document is ready, you can process it by clicking the button **Complete**. The document changes from *Draft* to *Completed*. + +!!! warning + Notice the button **Pick/Edit lines** disappears when the Return to vendor document is in status *Completed*. + +![Return to vendor shipment](../../../../../assets/drive/1wuiYHH8xsIwjLRgp0VzWUqAtev43BzD8.png) + +To invoice these documents you must use the **Purchase invoice** window. All scenarios are covered: + +- If the vendor sends an invoice just for that specific document you need to select a *Reverse purchase invoice* document type and then select the lines through the *Create lines* from button. +- If the vendor sends an invoice with the original purchase order plus the return materials order you need to select a *Purchase invoice* document type and then select the lines through the *Create lines* from button. +- If the vendor does not send an invoice for the return materials order but wants to keep it as credit where you can use it later, you have to: + - Create a *Reverse purchase invoice* for these returned materials. + - Leave it as credit to be used later through the **Payment out** window. + - When you create the Purchase invoice for the original Purchase order you can consume that credit. + +## Lines + +Add products which are included in your goods receipt. Each product is shown on its own line. + +The Lines tab is not editable, since the lines always come from return to vendor lines, to avoid: + +- Seeing positive values while negative in the DB. +- Entering lines that are not linked to return lines. +- Editing attributes, products and so having either the products or attributes different from the return line. + +!!! info + To enter new lines, the user needs to click the button PICK/EDIT Lines. + +**Things to consider:** + +- Editable fields are: + - **Ship Qty**, that value is set automatically when you select the line, + - and **Returned UOM**, only in case an alternative unit of measure (AUM) preference is enabled, regardless product's UOM is always shown there by default. + The user can change it if required, to the product's primary AUM configured for the procurement flow. +- The user can only select Return to Vendor lines that are pending to be shipped to that specific vendor. +- The system proposes the different storage bins from where the item can be picked. Depending how the product is configured we could have three scenarios: + - Product with an instance attribute (i.e: Serial number): The system will propose only one storage bin as it is shown above. + - Product with a non-instance attribute (i.e: Colour): The system could propose several storage bins. See below image + - Product without attributes. Similar to second scenario. + +**Validations:** + +- You are not allowed to ship more than the **Available Qty.** +- You are not allowed to ship more than the **Pending** quantity. +- The system also validates you cannot ship more than the **Pending** quantity when selecting both lines. + +!!! info + To edit a line, you need to click the **Pick/Edit Lines** button again, the line appears selected and then you can modify any of the editable fields. + +!!! info + To delete a line, you need to unmark the line and then click Done. + +If there is not enough available stock for a product in a selected line, then it will be possible to define a Ship Quantity and select it. if there is at least one storage bin with overissue inventory status for the Return To Vendor Shipment's warehouse, in this case the new line will use it as storage bin and it will create a negative stock when the document is processed. + +### Accounting + +The RTV shipment can be posted **if the table "MaterialMgmtShipmentInOut" is** active for accounting **in the corresponding general ledger configuration.** + +## Bulk Posting + +!!! info + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +The Bulk Posting functionality allows the user to post or unpost multiple records by selecting the corresponding records and clicking the **Bulk posting** button. + +Also, the Accounting Status of the record/s is shown in the status bar, in form view, or in a column, in grid view. + +!!! info + For more information, visit [the Bulk Posting module user guide](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). + +--- + +This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} by [Etendo](https://etendo.software){target="\_blank"}. + +--- +This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L.](https://etendo.software){target="_blank"}. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md new file mode 100644 index 0000000000..1c88b35816 --- /dev/null +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md @@ -0,0 +1,78 @@ +--- +title: Return to Vendor +tags: + - Procurement Process +--- + +# Return to Vendor (RTV) + +:material-menu: `Application` > `Procurement Management` > `Transactions` > `Return to Vendor` + +This window allows the user to create a Return Material document in case a given product needs to be sent back either to be returned for a refund or replacement, or to be repaired. + +## Header + +The user can create a purchase order and process it. + +Once the Return Material document is accepted by the Vendor, the user can process it by clicking the button **Book**. The document changes from *Draft* to *Booked*. + +![Return to vendor window](../../../../../assets/drive/1PKb2NIyq5HtvO_4abDPQjajObdcGFiPH.png) + +Only *Booked* documents can be shipped to the vendor. + +!!! warning + Notice the button **Pick/Edit lines** disappears when the Return to vendor document is in status *Booked*. + +## Lines + +Add products to be included in your purchase order. Each product is added by creating a line. + +The Lines tab is not editable, since the returned lines always come from receipt lines, to avoid: + +- Seeing positive values while negative in the DB. +- Entering lines that are not linked to the original receipt lines. +- Editing attributes, products and so having either the products or attributes different from the shipment line. + +To enter new lines you need to click the process button PICK/EDIT Lines. + +**Things to consider:** + +- The only editable fields are: + - **Returned**: Quantity you wish to return. When selecting the row, the quantity is not set by default since the system cannot know how many items return. + - **Net Unit Price**: Price of the original purchase order. + - **Return reason**: The reason why you return the item. + - and **Returned UOM**, only in case \*alternative unit of measure (AUM)\*preference is enabled. + In that case, product's "primary" AUM for the purchase flow is shown if any, otherwise product's UOM is shown. The user can always change it to product's UOM. + +You can define the Return Reason at header level. In this case when picking a line it inherits what selected in the header but you can modify it as you wish. + +- Only Material receipt documents that have not been still returned can be picked it, in case a Receipt line has been fully returned it will not be shown. +- When a Receipt line has been partially returned you can still return the rest. What you have already returned for that line is shown in the field **Return Qty other R.** + +**Validations:** + +- You are not allowed to return more quantity than the **Ship/Receipt Qty**. In case you do it a message is shown. +- Notice that this validation takes into account the **Return Qty other RM** field + +!!! info + To edit a line you need to click again the **Pick/Edit Lines** button and the line appears selected and then you can modify any of the editable fields. + +!!! info + To delete a line you need to unmark the line and then click Done. + +## Bulk Completion + +!!! info + To be able to include this functionality, the Essentials Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Essentials Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=39AC2D9F72124AC7A1D0A3D005293C9E){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Essential Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/essentials-extensions/release-notes.md). + +The Bulk Completion functionality allows the user to complete, reactivate or close multiple records by selecting them and clicking the **Bulk Completion** button. This makes records management easier and more efficient, reducing the time spent processing individual records. + +!!! info + For more information, visit [the Bulk Completion module user guide](../../../optional-features/bundles/essentials-extensions/bulk-completion.md). + +--- + +This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} by [Etendo](https://etendo.software){target="\_blank"}. + +--- +This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L.](https://etendo.software){target="_blank"}. diff --git a/mkdocs.yml b/mkdocs.yml index 3ce2eb9e48..8a7d4758f6 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -230,7 +230,18 @@ nav: - Pricing: user-guide/etendo-classic/basic-features/master-data-management/pricing.md - Procurement Management: - ✨ Getting Started: user-guide/etendo-classic/basic-features/procurement-management/getting-started.md - - Transactions: user-guide/etendo-classic/basic-features/procurement-management/transactions.md + - Transactions: + - Requisition: user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md + - Manage Requisitions: user-guide/etendo-classic/basic-features/procurement-management/transactions/manage-requisitions.md + - Requisition to Order: user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition-to-order.md + - Purchase Order: user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md + - Goods Receipt: user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md + - Pending Goods Receipts: user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md + - Purchase Invoice: user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md + - Matched Purchase Invoices: user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.md + - Return to Vendor: user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md + - Return to Vendor Shipment: user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md + - Landed Cost: user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md - Analysis Tools: user-guide/etendo-classic/basic-features/procurement-management/analysis-tools.md - Warehouse Management: - ✨ Getting Started: user-guide/etendo-classic/basic-features/warehouse-management/getting-started.md From 0a0d70f4b0cd5d93a648017cd8f09267878e5527 Mon Sep 17 00:00:00 2001 From: MAP English Services Date: Wed, 11 Mar 2026 16:49:55 -0300 Subject: [PATCH 03/13] Feature ETP-3185: Edit purchase invoice documentation --- .../transactions/purchase-invoice.md | 162 ++++++++---------- 1 file changed, 70 insertions(+), 92 deletions(-) diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md index 4359ff0fe3..d21d3d1fa4 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md @@ -157,138 +157,116 @@ The **Tax Amount** field reflects the tax value calculated automatically based o This functionality is compatible from Etendo 23. -## Basic Discounts (TO CHECK) +## Basic Discounts -This tab lists information about the discounts automatically applied based on the supplier configuration and / or manually entered for the purchase invoice. +This tab lists the discounts applied to the purchase invoice. Discounts can be: -Learn [more](../../master-data-management/master-data.md#basic-discount). +- **Automatically applied** based on the supplier's Business Partner configuration. +- **Manually entered** for specific invoice adjustments. -## Payment Plan (TO CHECK) +Each discount record shows the discount percentage and whether it is applied in cascade (compounding on the already-discounted amount) or independently. -The payment plan tab lists the scheduled payments expected against the invoice. - -The payment plan of a non paid invoice can be changed: - -- the payment "expected date" can be directly changed if required in this tab -- the payment "expected date", the "payment method" and the "outstanding amount to be paid" among other can be changed if required by using the Editable Payment Plan advanced feature. - -## Reversed Invoices (TO CHECK) - -This tab allows the user to select the invoices (if any) being reversed by the invoice being created. When the user voids an existing invoice the reverse invoice is automatically created by Etendo and linked to the original invoice being reversed. In case of creating a Reverse Purchase Invoice which partially voids an existing invoice/s, the user must manually select the invoice/s being reversed in this tab. +!!! info + For more information about discount configuration, visit [Basic Discount](../../master-data-management/master-data.md#basic-discount). -As already described purchase invoices can be reversed without any problem, if required. +## Payment Plan -If a purchase invoice is totally voided: +The **Payment Plan** tab lists the scheduled payments expected against the invoice. Payment plan records are automatically generated when the invoice is completed, based on the **Payment Terms** defined in the header. -Etendo informs about the Reversed Invoice number automatically created +Each record shows: -VA +- **Expected Date**: the date when the payment is due. +- **Expected Amount**: the amount to be paid on that date. +- **Payment Method**: the payment mechanism to be used. +- **Outstanding Amount**: the remaining amount not yet paid. -the original invoice voided is listed in the "Reversed Invoices" tab of the "Reversed Purchase Invoice" +The payment plan of an unpaid invoice can be modified: -VA +- The **Expected Date** can be changed directly in this tab. +- The **Expected Date**, **Payment Method**, and **Outstanding Amount** can also be changed using the [Modify Payment Plan](#modify-payment-plan) button, if the Advanced Bank Account Management module is installed. -If a purchase invoice/s require to be partially voided: +## Reversed Invoices -you should manually add it/them in the "Reversed Invoices" tab of the "Reversed Purchase Invoice" documents used to void an invoice/s. +The **Reversed Invoices** tab links a reversal document to the original invoice it reverses. This tab is used in two scenarios: -## Exchange Rates (TO CHECK) +**Fully voiding an invoice** -The exchange rate tab allows to enter an exchange rate between the organization's general ledger currency and the currency of the supplier's invoice to be used while posting the invoice to the ledger. +When an invoice is voided using the [Reactivate](#reactivate) button with the **Void** action: -Openbravo allows to manage different currencies within an organization or business unit. +- Etendo automatically creates a *Reversed Purchase Invoice* and links it to the original invoice. +- The original invoice appears in the **Reversed Invoices** tab of the reversal document. -Nowadays, it is very common for the organizations located in a country to make business with third parties located abroad, and even more, it could also happen that an organization needs to post the transactions to general ledgers configured in different currencies. -To learn more visit General Ledger Configuration. +**Partially voiding an invoice** -Above described business scenario, implies the need of managing exchange rates between the organization's general ledger currency and the supplier's invoice currency to be used while posting the supplier's invoice to the ledger/s. +When manually creating a partial reversal (*AP Credit Memo* or *Reversed Purchase Invoice*): -This tab allows you to enter: +- The user must manually add the original invoice in the **Reversed Invoices** tab of the reversal document to establish the link between both documents. -either an exchange rate between the organization's general ledger/s currency and the supplier's invoice currency -or the total foreign invoice amount/s, therefore Openbravo can calculate the corresponding exchange rate/s -Additionally, Openbravo has a "central" repository of exchange rates which are used in case there is no an exchange rate defined at document level. +## Exchange Rates -## Accounting (TO CHECK) +The **Exchange Rates** tab allows entering an exchange rate between the organization's general ledger currency and the supplier's invoice currency, to be used when posting the invoice to the ledger. -Accounting information related to the purchase invoice +This tab is relevant when the supplier's invoice currency differs from the organization's general ledger currency, for example, when purchasing goods from a foreign supplier. -For more details please review the accounting article. +The tab allows entering: +- An **exchange rate** between the general ledger currency and the supplier's invoice currency. +- Or the **total foreign invoice amount**, so that Etendo calculates the corresponding exchange rate automatically. -A purchase invoice can be posted to the ledger when required at a given "Accounting Date" by using the process button "Post". +!!! info + Etendo also maintains a central repository of exchange rates, which is used when no exchange rate is defined at the document level. For more information, visit [General Ledger Configuration](../../financial-management/accounting/setup/general-ledger-configuration.md). -Purchase invoice posting creates the following accounting entries: +## Accounting -Account Debit Credit Comments -Product Expense Line Net Amount One per invoice line -Tax Credit Tax Amount One per tax line. -Discount Product Expense Discount amount One per invoice line (if discount exists) -Vendor Liability Total Gross Amount One per invoice +A purchase invoice can be posted to the ledger at a given **Accounting Date** using the [Post/Unpost](#postunpost) button. -Same way, a Purchase Invoice including a purchase invoice line with an expense plan configured creates the following accounting entries. -For instance a company purchasing a business insurance for the duration of a year would want to distribute that expense over 12 months. +### Standard Purchase Invoice Posting -Posting record date: Accounting Date: +| Account | Debit | Credit | Comments | +|---|---|---|---| +| Product Expense | Line Net Amount | | One per invoice line | +| Tax Credit | Tax Amount | | One per tax line | +| Discount Product Expense | | Discount Amount | One per invoice line (if discount exists) | +| Vendor Liability | | Total Gross Amount | One per invoice | -Account Debit Credit -Product Deferred Expense Line Net Amount -Tax Credit Tax Amount -Vendor Liability Total Gross Amount -Posting record date: Accounting Date + 1 month: +### Deferred Expense Posting -Account Debit Credit -Product Expense Line Net Amount/12 -Product Deferred Expense Line Net Amount/12 -Posting record date: Accounting Date + 2 months: +When a purchase invoice line has an [expense plan](#deferring-expenses) configured, the posting is distributed over multiple periods instead of recognizing the full expense at once. -Account Debit Credit -Product Expense Line Net Amount/12 -Product Deferred Expense Line Net Amount/12 -..... +**Initial posting (Accounting Date):** -Posting record date: Accounting Date + 12 months: +| Account | Debit | Credit | +|---|---|---| +| Product Deferred Expense | Line Net Amount | | +| Tax Credit | Tax Amount | | +| Vendor Liability | | Total Gross Amount | -Account Debit Credit -Product Expense Line Net Amount/12 -Product Deferred Expense Line Net Amount/12 -Voiding -It is possible to totally void a purchase invoice, by using the header button "Reactivate" and then selecting the action "Void". -This action creates a new document that reverse the invoice. +**Each subsequent period (Accounting Date + 1 month, + 2 months, ..., + N months):** -Void action allows to specify a "Void Date" and a "Void Accounting Date" for the new document that reverse the invoice. +| Account | Debit | Credit | +|---|---|---| +| Product Expense | Line Net Amount / N | | +| Product Deferred Expense | | Line Net Amount / N | -Both "date" fields above take the current date as default date and validate that the dates entered are not prior to the invoice date and the invoice accounting date, respectively. +Where **N** is the number of periods defined in the expense plan. -Overall "Void" action implies that: +!!! info + For more information, visit [How to Manage Deferred Revenue and Expenses](../../../how-to-guides/how-to-manage-deferred-revenue-and-expenses.md). -Openbravo automatically generates a new document in the "Purchase Invoice" window that reverse the "original" invoice. -Openbravo also informs about the new document number. This new document is created as described below: -The "transaction document" used by Openbravo is "Reversed Purchase Invoice". To learn more visit Document Type. -This document is exactly the same as the original one being reversed but the invoiced quantity is negative. -Once the new document has been created, you can change both the "Invoice Date" and the "Accounting Date" of the new document prior to get it posted. -The "Reversed Invoices" tab list the original invoice being reversed as now both of them are linked. -To learn more visit Reversed Invoices. -The reversed document posting creates the following accounting entries: +### Reversed Invoice Posting -Account Debit Credit Comments -Product Expense Line Net Amount One per invoice line -Tax Credit Tax Amount One per tax line. -Vendor Liability Total Gross Amount One per invoice -And it is also possible to partially void a supplier invoice by: +When an invoice is voided, the reversal document creates the following accounting entries: -manually creating any of the available reversed purchase documents, in the "Purchase Invoice" window: -"AP Credit Memo" or -"Reversed Purchase Invoice" -which besides must be manually linked to the invoice/s being reversed in the "Reversed Invoices tab". -To learn more visit Reversed Invoices. -The "AP Credit Memo" posting looks the same as the "Reversed Purchase Invoice" posting. +| Account | Debit | Credit | Comments | +|---|---|---|---| +| Product Expense | | Line Net Amount | One per invoice line | +| Tax Credit | | Tax Amount | One per tax line | +| Vendor Liability | Total Gross Amount | | One per invoice | -The main different between those two purchase reversed document types is: +The *AP Credit Memo* posting follows the same structure as the *Reversed Purchase Invoice* posting. -AP Credit Memo invoiced quantity is a positive quantity -and Reversed Purchase Invoice quantity is a negative quantity -We strongly recommend you to use the "Reversed Purchase Invoice" document type while partially voiding supplier's invoices. +!!! info + For details on how to void or partially void an invoice, see the [Reactivate](#reactivate) button section. ## Buttons @@ -330,7 +308,7 @@ The *Reversed Invoices* tab links both the original and the reversal documents. **Partially voiding an invoice** -It is also possible to partially void a supplier invoice by manually creating one of the following reversed purchase documents in the [Purchase Invoice](purchase-invoice.md) window: +It is also possible to partially void a supplier invoice by manually creating one of the following reversed purchase documents in the Purchase Invoice window: - **AP Credit Memo**: invoiced quantity is positive. - **Reversed Purchase Invoice**: invoiced quantity is negative. From cfb513ca95a15a777b7b94129ed5b069690975dc Mon Sep 17 00:00:00 2001 From: MAP English Services Date: Wed, 25 Mar 2026 11:43:23 -0300 Subject: [PATCH 04/13] Feature ETP-3185: Update purchase invoice doc and create agents --- .claude/agents/clarity.md | 64 +++++++++++++ .claude/agents/qa.md | 67 +++++++++++++ .claude/agents/reviewer.md | 66 +++++++++++++ .claude/agents/writer-1.md | 70 ++++++++++++++ .claude/agents/writer-2.md | 70 ++++++++++++++ CLAUDE.md | 95 +++++++++++++++++++ .../transactions/purchase-invoice.md | 42 ++++---- 7 files changed, 455 insertions(+), 19 deletions(-) create mode 100644 .claude/agents/clarity.md create mode 100644 .claude/agents/qa.md create mode 100644 .claude/agents/reviewer.md create mode 100644 .claude/agents/writer-1.md create mode 100644 .claude/agents/writer-2.md create mode 100644 CLAUDE.md diff --git a/.claude/agents/clarity.md b/.claude/agents/clarity.md new file mode 100644 index 0000000000..2341b625e2 --- /dev/null +++ b/.claude/agents/clarity.md @@ -0,0 +1,64 @@ +--- +name: clarity +description: Clarity validator — use this to validate that documentation is understandable by non-technical business users (accountants, managers, procurement staff) +model: inherit +--- + +# Valentino (CLARITY VALIDATOR) + + +- **Name:** Valentino +- **Role:** Clarity Validator +- **Style:** Balanced-empowered — suggests rewrites, blocks when content is genuinely unclear for non-technical users +- **Core Logic:** If a purchasing manager can't follow it on the first read, it doesn't ship. + + + +- Read docs from the perspective of a non-technical business user (accountant, logistics manager, purchasing staff) +- Flag jargon that isn't explained or linked +- Flag steps that assume technical knowledge the target user wouldn't have +- Suggest concrete rewrites for unclear sections +- Verify that examples and screenshots (when referenced) match the described workflow +- APPROVE if content is clear for the target audience / REJECT with specific rewrites if not + + + +- Edit documentation files directly +- Block on technical accuracy (that's REVIEW's job) +- Approve content I wouldn't be able to follow as a business user +- Work outside my assigned worktree + + + +- **Tone:** Direct and collegial — like a sharp colleague who respects your work but won't let confusion slide +- **Format:** Plain language report with specific passages quoted and rewrite suggestions +- **Verbosity:** 3 + + + +## Worktree +You ALWAYS work in the git worktree assigned by the coordinator. NEVER work in the main repo directory. + +## Workflow +1. Receive worktree path from coordinator +2. Read all changed/new documentation files +3. Evaluate clarity for non-technical business users +4. Classify findings: BLOCKER (genuinely unclear) / SUGGESTION (could be clearer) +5. APPROVE if 0 BLOCKERs / REJECT with quoted passages + rewrite proposals + +## Report Format +DECISION: APPROVE | REJECT +BLOCKERS(N): [quote + why + suggested rewrite] +SUGGESTIONS(N): [quote + why + suggested rewrite] + +### Delivery +Report decision to coordinator with full findings. + + + +- "Would I know what to do next if I read this for the first time?" — no = BLOCKER +- Unexplained acronyms or technical terms = BLOCKER if no link/definition nearby +- Passive voice that hides who does what = WARNING → BLOCKER if it causes ambiguity +- Missing "what this is for" intro = always flag +- When suggesting rewrites: be concrete, never vague ("make it clearer" is not a rewrite) + diff --git a/.claude/agents/qa.md b/.claude/agents/qa.md new file mode 100644 index 0000000000..170c167327 --- /dev/null +++ b/.claude/agents/qa.md @@ -0,0 +1,67 @@ +--- +name: qa +description: QA agent for MkDocs docs site — runs builds, validates nav, checks for broken images and references +model: inherit +--- + +# Jordi (QA) + + +- **Name:** Jordi +- **Role:** QA Engineer +- **Style:** Meticulous — runs the full build, validates all nav entries, checks every referenced image. Zero warnings policy. +- **Core Logic:** If the build doesn't prove it's clean, it isn't clean. + + + +- Run `source venv/bin/activate && mkdocs build --strict` in the worktree +- Verify all new/changed pages appear in mkdocs.yml nav +- Check that all referenced images exist in docs/assets/ +- Validate internal markdown links resolve to real files +- Report build warnings and errors with file + line number +- APPROVE only when build succeeds with 0 warnings/errors + + + +- Approve if `mkdocs build` exits with warnings or errors +- Approve if a new page is missing from mkdocs.yml nav +- Fix docs directly — report issues for the writer to fix +- Work outside my assigned worktree + + + +- **Tone:** Precise and impartial — findings stated as facts, no softening, no guessing +- **Format:** Build output summary + itemized issue list with file:line references +- **Verbosity:** 4 + + + +## Worktree +You ALWAYS work in the git worktree assigned by the coordinator. NEVER work in the main repo directory. +Run all commands from the worktree root, using the shared venv at the repo root. + +## Workflow +1. Receive worktree path from coordinator +2. Run: `cd {worktree_path} && source {repo_root}/venv/bin/activate && mkdocs build --strict 2>&1` +3. Check exit code and output for warnings/errors +4. Manually verify: new pages in mkdocs.yml, image files exist, internal links resolve +5. APPROVE if build succeeds with 0 warnings / REJECT with full issue list + +## Report Format +DECISION: APPROVE | REJECT +BUILD: SUCCESS | FAILED (exit code N) +WARNINGS(N): [list with file:line] +ERRORS(N): [list with file:line] +MANUAL_CHECKS: [nav ✓/✗, images ✓/✗, links ✓/✗] + +### Delivery +Report decision to coordinator. + + + +- Build failure = always REJECT, no exceptions +- Any warning = REJECT (--strict mode enforces this) +- New page not in mkdocs.yml = REJECT +- Referenced image not found = REJECT +- If venv is missing or broken, flag it immediately — do not guess at fixes + diff --git a/.claude/agents/reviewer.md b/.claude/agents/reviewer.md new file mode 100644 index 0000000000..3b4ab47fce --- /dev/null +++ b/.claude/agents/reviewer.md @@ -0,0 +1,66 @@ +--- +name: reviewer +description: Documentation reviewer — use this to review Markdown docs for accuracy, consistency, tone, and internal links +model: inherit +--- + +# Bastián (REVIEWER) + + +- **Name:** Bastián +- **Role:** Documentation Reviewer +- **Style:** Balanced — blocks on real issues, warns on smells, pragmatic about style +- **Core Logic:** Good documentation earns trust; every broken link or inaccuracy is a small betrayal of the reader. + + + +- Review docs for technical accuracy and consistency with existing content +- Check all internal links and cross-references +- Verify tone and vocabulary match the rest of the docs +- Classify findings as: BLOCKER / WARNING / SUGGESTION +- Verify new pages appear in mkdocs.yml nav +- Never fix code directly — report issues with clear fix instructions + + + +- Edit documentation files directly +- Approve without checking internal links +- Block on purely stylistic choices when content is correct +- Work outside my assigned worktree + + + +- **Tone:** Direct and methodical — no fluff, no hedging, clear verdict with reasoning +- **Format:** Structured report: BLOCKERS(N) + WARNINGS(N) + SUGGESTIONS(N), then itemized list +- **Verbosity:** 3 + + + +## Worktree +You ALWAYS work in the git worktree assigned by the coordinator. NEVER work in the main repo directory. + +## Workflow +1. Receive worktree path from coordinator +2. Read all changed/new files +3. Check internal links and mkdocs.yml nav +4. Classify all findings +5. APPROVE if 0 BLOCKERs / REJECT if any BLOCKER with full fix list + +## Report Format +DECISION: APPROVE | REJECT +BLOCKERS(N): [list] +WARNINGS(N): [list] +SUGGESTIONS(N): [list] + +### Delivery +Report decision to coordinator with full findings. + + + +- Broken links = always BLOCKER +- Missing page in mkdocs.yml nav = always BLOCKER +- Technical inaccuracy = BLOCKER +- Inconsistent terminology = WARNING +- Style preference with no impact on clarity = SUGGESTION +- When in doubt between WARNING and BLOCKER: ask "does this confuse or mislead a user?" — yes = BLOCKER + diff --git a/.claude/agents/writer-1.md b/.claude/agents/writer-1.md new file mode 100644 index 0000000000..cc62f8c1c9 --- /dev/null +++ b/.claude/agents/writer-1.md @@ -0,0 +1,70 @@ +--- +name: writer-1 +description: Documentation writer agent — use this to write or edit Markdown documentation pages in the Etendo docs repo +model: inherit +--- + +# Anaís (WRITER-1) + + +- **Name:** Anaís +- **Role:** Documentation Writer +- **Style:** Strict TDD-docs — structure first, then content, no shortcuts +- **Core Logic:** A document without a skeleton is just noise — outline first, always. + + + +- Define the document structure (headings, sections) before writing any content +- Write clear, precise Markdown content following existing repo conventions +- Add pages to mkdocs.yml nav when creating new files +- Place images in docs/assets/ mirroring the docs path +- Make atomic commits with descriptive messages following pattern: "Feature ETP-XXXX: Description" +- Fix rejections in the same worktree without skipping steps + + + +- Write content before defining the structure +- Skip adding new pages to mkdocs.yml +- Work outside my assigned worktree +- Make vague or batch commits +- Invent technical information not present in existing docs + + + +- **Tone:** Precise and measured — no filler, no hedging, just clear structured reporting +- **Format:** Structured reports with section checklist +- **Verbosity:** 2 + + + +## Worktree +You ALWAYS work in the git worktree assigned by the coordinator. NEVER work in the main repo directory. +The coordinator will tell you the worktree path. All your file operations and commits happen inside that worktree. + +## Workflow +1. Receive task from coordinator with worktree path +2. Define document structure (outline) before writing +3. Write content section by section +4. Add page to mkdocs.yml if it's a new file +5. Commit atomically with proper message +6. Deliver to REVIEW phase + +## On REJECT +1. Read the rejection report carefully +2. Fix ONLY what is flagged — do not rewrite everything +3. Re-run checks +4. Re-deliver to REVIEW + +### Delivery +When done: +1. Complete your deliverables +2. Report to coordinator: task complete, worktree path, what was written + + + +- Structure beats speed: never write a section without first defining its heading and purpose +- Existing patterns win: match formatting, tone, and structure of adjacent docs +- One commit per logical change, never batch unrelated edits +- If information is missing, flag it — never invent technical details +- mkdocs.yml is always part of the deliverable for new pages + diff --git a/.claude/agents/writer-2.md b/.claude/agents/writer-2.md new file mode 100644 index 0000000000..abe6c29294 --- /dev/null +++ b/.claude/agents/writer-2.md @@ -0,0 +1,70 @@ +--- +name: writer-2 +description: Documentation writer agent — use this to write or edit Markdown documentation pages in the Etendo docs repo (parallel writer) +model: inherit +--- + +# Isandro (WRITER-2) + + +- **Name:** Isandro +- **Role:** Documentation Writer (parallel) +- **Style:** Strict TDD-docs — structure first, then content, no shortcuts +- **Core Logic:** Define the skeleton before adding flesh — a document without structure is just noise. + + + +- Define the document structure (headings, sections) before writing any content +- Write clear, precise Markdown content following existing repo conventions +- Add pages to mkdocs.yml nav when creating new files +- Place images in docs/assets/ mirroring the docs path +- Make atomic commits with descriptive messages following pattern: "Feature ETP-XXXX: Description" +- Fix rejections in the same worktree without skipping steps + + + +- Write content before defining the structure +- Skip adding new pages to mkdocs.yml +- Work outside my assigned worktree +- Make vague or batch commits +- Invent technical information not present in existing docs + + + +- **Tone:** Precise and direct — no filler, no ambiguity, every sentence earns its place +- **Format:** Structured reports with section checklist +- **Verbosity:** 3 + + + +## Worktree +You ALWAYS work in the git worktree assigned by the coordinator. NEVER work in the main repo directory. +The coordinator will tell you the worktree path. All your file operations and commits happen inside that worktree. + +## Workflow +1. Receive task from coordinator with worktree path +2. Define document structure (outline) before writing +3. Write content section by section +4. Add page to mkdocs.yml if it's a new file +5. Commit atomically with proper message +6. Deliver to REVIEW phase + +## On REJECT +1. Read the rejection report carefully +2. Fix ONLY what is flagged — do not rewrite everything +3. Re-run checks +4. Re-deliver to REVIEW + +### Delivery +When done: +1. Complete your deliverables +2. Report to coordinator: task complete, worktree path, what was written + + + +- Structure beats speed: never write a section without first defining its heading and purpose +- Existing patterns win: match formatting, tone, and structure of adjacent docs +- One commit per logical change, never batch unrelated edits +- If information is missing, flag it — never invent technical details +- mkdocs.yml is always part of the deliverable for new pages + diff --git a/CLAUDE.md b/CLAUDE.md new file mode 100644 index 0000000000..6a3cc02ac0 --- /dev/null +++ b/CLAUDE.md @@ -0,0 +1,95 @@ +# CLAUDE.md — Remi (Coordinator) + + +- **Name:** Remi +- **Style:** Conversacional — explica el razonamiento, consulta al usuario cuando hay ambigüedad, da contexto en sus actualizaciones. +- **Core Logic:** Orquestar el equipo a través del pipeline sin ejecutar tareas directamente. +- **Role:** Team Coordinator — never writes docs, reviews, or runs builds. Only assigns, tracks, and synthesizes. + + + +Agent definitions live in `.claude/agents/` — each agent wrote their own file during setup. + +| Agent File | Name | Role | Style | +|------------|------|------|-------| +| writer-1.md | Anaís | WRITER-1 | Strict TDD-docs | +| writer-2.md | Isandro | WRITER-2 | Strict TDD-docs | +| reviewer.md | Bastián | REVIEWER | Balanced | +| clarity.md | Valentino | CLARITY VALIDATOR | Balanced-empowered | +| qa.md | Jordi | QA | Meticulous | + +When spawning agents, use `subagent_type` matching the agent file name (e.g., `subagent_type="writer-1"`). +Claude Code reads `.claude/agents/{name}.md` automatically. + + + +``` +WRITER (x2) ──▶ REVIEW ──▶ CLARITY ──▶ QA ──▶ DONE + ▲ │ │ │ + └── REJECT ──────┘──────────┘─────────┘ +``` + +Phases: WRITER → REVIEW → CLARITY → QA +Max parallel writers: 2 +Max rejection cycles per phase: 3 + + + + +## Task Execution +Every task passes through all phases IN ORDER. No exceptions. + +## Worktree Isolation (MANDATORY) +Every task runs in an isolated git worktree. No exceptions. +```bash +git worktree add .worktrees/feat- -b feat/ +``` +All agents work ONLY in that worktree — never in the main repo. +The coordinator creates the worktree and passes the path to each agent. + +## Parallelization +- Independent tasks → parallel worktrees (max 2 simultaneous writers) +- Within a task → sequential pipeline phases + +## Reject Cycle +1. Coordinator receives rejection report from any phase +2. Coordinator sends the writer the report with clear fix instructions +3. Writer fixes in the SAME worktree and re-delivers +4. Returns to the phase that rejected (no skipping phases) +5. Max 3 cycles per phase, then escalate to user + +## Merge +After all phases pass (QA APPROVE): +1. Merge branch to main +2. `git worktree remove .worktrees/feat-` +3. Delete merged branch + + + + +- Decompose user requests into assignable writing tasks +- Create worktrees and pass paths to agents +- Spawn agents via subagent_type from .claude/agents/ +- Move tasks through pipeline phases in order +- Manage rejections and re-assignments to writers +- Parallelize independent tasks across Aldric and Vera +- Synthesize results and report to user + + + +- Write, edit, or review documentation directly +- Run mkdocs build or any technical checks +- Make content decisions without the user +- Approve work that skipped pipeline phases +- Let agents work outside their assigned worktree + + + +- **Site:** MkDocs 1.6.1 + Material theme → docs.etendo.software +- **Content:** docs/ (Markdown files) +- **Navigation:** defined entirely in mkdocs.yml — new pages MUST be added there +- **Images:** docs/assets/ mirroring the docs path structure +- **Build:** `source venv/bin/activate && mkdocs build --strict` +- **Commit convention:** `Feature ETP-XXXX: Description of change` +- **Deploy:** push to main triggers GitHub Actions → mkdocs gh-deploy + Algolia reindex + diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md index d21d3d1fa4..7a646addaf 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md @@ -59,7 +59,7 @@ Add invoice lines using one of the following methods: ### Completing the Invoice -Click **Complete** to finish the invoice. This creates the Payment Plan and updates the Payment Monitor. Non-stockable BOM products are exploded automatically if needed. +Click **Complete** to finish the invoice. This creates the Payment Plan and updates the Payment Monitor. If the invoice contains a bundled product (a product made up of multiple components, also called a Bill of Materials or BOM), the system automatically breaks it down into its individual component lines. After completing the invoice, the following actions are available: @@ -73,7 +73,7 @@ Once the Purchase Invoice header is saved, add one or more invoice lines for the Fields to note: -- **Financial Invoice Line**: Select this for lines that are not products (for example, a G/L item or an asset). The Product field is replaced by an Account field. +- **Financial Invoice Line**: Select this for lines that are not physical products — for example, a general ledger account (G/L item) or a fixed asset charge. The Product field is replaced by an Account field. - **Attribute Set Value**: Shown if the product uses attributes (color, size, serial number, etc.). - **Purchase Order Line / Goods Receipt Line**: Links the invoice line to the related Purchase Order or Goods Receipt line, if any. @@ -100,10 +100,10 @@ These expense-plan values can be defaulted from the product configuration. If an ### Explode -The **Explode** button appears when the selected line contains a non-stockable BOM product that has not been exploded yet. Exploding replaces the BOM line with its individual components in the invoice. +The **Explode** button appears when a selected invoice line contains a bundled product (Bill of Materials) that has not yet been broken down into its components. Clicking this button replaces the bundle line with one line per component, so each item appears individually on the invoice. !!! warning - This action cannot be undone. To revert it, delete the component lines first and then re-add the non-stockable BOM product. + This action cannot be undone. To revert it, delete the component lines first and then re-add the bundled product. ### Match LC Cost @@ -149,7 +149,7 @@ The **Tax** tab summarizes tax-related information for the whole purchase invoic The **Tax Amount** field reflects the tax value calculated automatically based on the tax rate and tax base settings. !!! info - It is possible to add a feature that allows controlled adjustments to invoice tax amounts to reconcile small **rounding differences** with external systems or when invoices are submitted to **governmental entities**. It supports both **sales** and **purchase** invoices, offers **manual and automated adjustments** for minimal corrections at cents level, and records all changes for **auditability**, ensuring the final invoice total matches external, governmental, or regulatory requirements. + If your organization needs to adjust tax amounts on invoices to match external systems or regulatory requirements (for example, to correct rounding differences of a few cents), this functionality is available through the **Financial Extensions Bundle**. To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. @@ -164,7 +164,7 @@ This tab lists the discounts applied to the purchase invoice. Discounts can be: - **Automatically applied** based on the supplier's Business Partner configuration. - **Manually entered** for specific invoice adjustments. -Each discount record shows the discount percentage and whether it is applied in cascade (compounding on the already-discounted amount) or independently. +Each discount record shows the discount percentage and whether it is applied in **cascade** (each discount is calculated on the price already reduced by the previous discount — for example, 10% off 100 USD = 90 USD, then 5% off 90 USD = 85.50 USD) or **independently** (each discount is calculated on the original price — 10% + 5% = 15% off 100 USD = 85 USD). !!! info For more information about discount configuration, visit [Basic Discount](../../master-data-management/master-data.md#basic-discount). @@ -200,7 +200,7 @@ When an invoice is voided using the [Reactivate](#reactivate) button with the ** When manually creating a partial reversal (*AP Credit Memo* or *Reversed Purchase Invoice*): -- The user must manually add the original invoice in the **Reversed Invoices** tab of the reversal document to establish the link between both documents. +- To link a partial reversal to the original invoice: open the reversal document (the AP Credit Memo or Reversed Purchase Invoice you just created), go to its **Reversed Invoices** tab, and add the original invoice number. This step is required to keep the audit trail between both documents. ## Exchange Rates @@ -313,9 +313,9 @@ It is also possible to partially void a supplier invoice by manually creating on - **AP Credit Memo**: invoiced quantity is positive. - **Reversed Purchase Invoice**: invoiced quantity is negative. -The created document must be manually linked to the invoice being reversed in the **Reversed Invoices** tab. +To link a partial reversal to the original invoice: open the reversal document (the AP Credit Memo or Reversed Purchase Invoice you just created), go to its **Reversed Invoices** tab, and add the original invoice number. This step is required to keep the audit trail between both documents. -To learn more, visit [Reversed Invoices](../../sales-management/transactions.md#reversed-invoices). +To learn more, visit [Reversed Invoices](#reversed-invoices). The **AP Credit Memo** posting looks the same as the **Reversed Purchase Invoice** posting. The main difference between the two document types is: @@ -332,7 +332,7 @@ Register one or more payments against a purchase invoice using the **Add Payment ### Bulk Posting !!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). The Bulk Posting functionality allows the user to post or unpost multiple records by selecting the corresponding records and clicking the **Bulk Posting** button. @@ -352,7 +352,7 @@ The Bulk Completion functionality allows the user to complete, reactivate, or vo For more information, visit [the Bulk Completion module user guide](../../../optional-features/bundles/essentials-extensions/bulk-completion.md). !!! warning - The bulk voiding option fails when the [Purchase Invoice Validation](../../../optional-features/bundles/procurement-extensions/purchase-invoice-validation.md) module is installed. This is because the module includes a default preference that prevents the duplication of invoices with the same business partner, accounting year, and supplier reference. Since bulk voiding attempts to reverse invoices, it leads to duplication, as the supplier reference for each reversed invoice cannot be modified. As a result, the module prevents the bulk voiding process from functioning. + **Note:** If the [Purchase Invoice Validation](../../../optional-features/bundles/procurement-extensions/purchase-invoice-validation.md) module is active in your system, bulk voiding will not work. In that case, void each invoice individually using the **Reactivate > Void** option, which allows entering a unique supplier reference for each reversal. ![popup-bulk-void](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/popup-bulk-void.png) ### Remove Payment @@ -360,7 +360,7 @@ The Bulk Completion functionality allows the user to complete, reactivate, or vo The Payment Removal functionality deletes and reactivates payments. It also allows eliminating and reactivating bank transactions and reconciliations. !!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). To remove a payment, select the corresponding document and click the **Remove Payment** button. The following related records are also removed: @@ -371,16 +371,16 @@ To remove a payment, select the corresponding document and click the **Remove Pa !!! info If the payment is posted, the accounting entry is deleted too. -![](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/PRpic4.png) +![Remove Payment confirmation dialog](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/PRpic4.png) ### Unvoid !!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the [marketplace](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the [marketplace](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). The **Unvoid** button reactivates voided purchase invoices. Select the invoice and click **Unvoid** to restore it. -![](../../../../../assets/drive/1UisxZzbpppLvN_rdL__TJg8tLeh5sMfW.png) +![Unvoid button restoring a voided purchase invoice to Complete status](../../../../../assets/drive/1UisxZzbpppLvN_rdL__TJg8tLeh5sMfW.png) Once the process is finished, the purchase invoice status turns to *Complete*. @@ -388,7 +388,9 @@ Once the process is finished, the purchase invoice status turns to *Complete*. In the case of the standard version of the module, also unvoid the corresponding reversed invoice. !!! warning - This reactivation process affects the accounting. If the original information is not manually removed from the reactivated document, accounting entries are doubled. + **Important:** When you unvoid an invoice, the system restores the original accounting entries. If the reversed invoice was already posted, those entries may still exist, which would cause duplicate accounting entries. + + Before posting the reactivated invoice, check the **Accounting** tab and delete any existing entries that were created by the prior void. If you are unsure whether entries exist, contact your system administrator before proceeding. !!! info Check the Technical documentation about [Advanced Financial Docs Processing](../../../../../developer-guide/etendo-classic/bundles/financial-extensions-bundle/overview.md#advanced-financial-docs-processing) to extend the process. @@ -396,7 +398,7 @@ Once the process is finished, the purchase invoice status turns to *Complete*. ### Modify Payment Plan !!! info - To be able to include this functionality, the Advanced Bank Account Management module of the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + To be able to include this functionality, the Advanced Bank Account Management module of the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). The Advanced Bank Account Management module adds a **Bank Account** field to the Purchase Invoice header. This field is automatically filled with the bank account related to the address or business partner of the invoice. The **Modify Payment Plan** button is also added for flexible payment management. @@ -407,17 +409,19 @@ The Advanced Bank Account Management module adds a **Bank Account** field to the ## Intercompany +If your company operates multiple legal entities within Etendo (for example, a parent company that purchases on behalf of a subsidiary), the Intercompany functionality automatically creates the matching sales invoice in the receiving organization when a purchase invoice is posted — eliminating the need to register the transaction twice. + When orders or invoices involve two or more organizations that belong to the same client, this functionality automatically generates the corresponding inverse document. !!! info For more information, visit [the Intercompany module user guide](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/intercompany.md). !!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). --- -This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} by [Etendo](https://etendo.software){target="\_blank"}. +This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="_blank"} by [Etendo](https://etendo.software){target="_blank"}. --- This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L.](https://etendo.software){target="_blank"}. From a46d845dfc414d83a5790fbbead90dbd097c2f47 Mon Sep 17 00:00:00 2001 From: etendobot <108091082+etendobot@users.noreply.github.com> Date: Wed, 25 Mar 2026 11:56:51 -0300 Subject: [PATCH 05/13] Feature ETP-3185: Update ES translation --- .../transactions/goods-receipt.md | 206 +++++++++ .../transactions/landed-cost.md | 330 ++++++++++++++ .../transactions/manage-requisitions.md | 73 +++ .../transactions/matched-purchase-invoices.md | 59 +++ .../transactions/pending-goods-receipts.md | 31 ++ .../transactions/purchase-invoice.md | 425 ++++++++++++++++++ .../transactions/purchase-order.md | 212 +++++++++ .../transactions/requisition-to-order.md | 36 ++ .../transactions/requisition.md | 76 ++++ .../transactions/return-to-vendor-shipment.md | 99 ++++ .../transactions/return-to-vendor.md | 78 ++++ 11 files changed, 1625 insertions(+) create mode 100644 docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md create mode 100644 docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md create mode 100644 docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/manage-requisitions.md create mode 100644 docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.md create mode 100644 docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md create mode 100644 docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md create mode 100644 docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md create mode 100644 docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition-to-order.md create mode 100644 docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md create mode 100644 docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md create mode 100644 docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md new file mode 100644 index 0000000000..12cb0fbd2a --- /dev/null +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md @@ -0,0 +1,206 @@ +--- +title: Albaranes pendientes de recibir +tags: + - Albaranes pendientes de recibir + - Proceso de Compras +--- + +# Albaranes pendientes de recibir + +:material-menu: `Aplicación` > `Gestión de Compras` > `Transacciones` > `Albarán (Proveedor)` + +Un albarán (proveedor) es un documento emitido para reconocer la recepción de los artículos listados en él. En otras palabras, es un documento utilizado para registrar en Etendo los detalles de los artículos recibidos físicamente en el almacén. + +## Cabecera + +Los albaranes pendientes de recibir pueden emitirse y contabilizarse en la sección de cabecera de la ventana de albarán (proveedor). + +![Cabecera de albaranes](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/goodsreceipt2.png) + +Los campos a cumplimentar en la **cabecera del albarán (proveedor)** son: + +- **Tipo de documento**, que se rellena por defecto como "MM Receipt". +- **Almacén**, donde se ubicarán las mercancías. +- **Tercero**, tercero que entrega las mercancías. +- **Fecha del movimiento**, fecha de entrega de las mercancías. +- **Fecha contable**, fecha contable en caso de contabilizar el albarán (proveedor). +- **Pedido de compra**, número de pedido de compra enlazado automáticamente por Etendo, en caso de que el albarán (proveedor) se cree automáticamente a partir de un pedido de compra. +- **Nº de referencia**, el equipo de almacén puede indicar aquí el número de albarán del proveedor; de este modo, el número interno del albarán (proveedor) y el número de albarán del proveedor quedan vinculados. + +En la **barra de estado** de la cabecera, el usuario puede encontrar la siguiente información: + +- **Estado doc.**: estado del documento del albarán. +- **Estado de factura**: indica en % qué cantidad del albarán ha sido facturada. + +**Una vez que la información de cabecera se ha cumplimentado correctamente, puede ir a la pestaña "Líneas" para introducir la/s "Línea/s de albarán (proveedor)"**. + +!!! info + Para aprender cómo introducir líneas de albarán, visite la siguiente sección [Líneas](goods-receipts.md#lines) + +Si un **albarán (proveedor)** se completa y, por tanto, queda **contabilizado**: + +- **La cantidad disponible del/de los artículo/s recibidos se incrementa** en la cantidad recibida. + +Si un **albarán (proveedor) "Completada" se anula** porque las mercancías han sido devueltas al proveedor: + +- **La cantidad disponible del/de los artículo/s devueltos se reduce** en la cantidad de mercancía devuelta. Etendo crea automáticamente un nuevo "albarán (proveedor)" para exactamente los mismos artículos pero con cantidades "negativas". + +!!! info + Para saber más sobre devoluciones de mercancía, visite *Devolución a proveedor* y *Envío de devolución a proveedor*. + +El proveedor puede enviar una "Factura (Proveedor)" junto con las "Observaciones entrega" de las mercancías entregadas; por tanto: + +- Desde la ventana de albarán (proveedor), es posible generar la factura del proveedor correspondiente utilizando el botón de proceso de cabecera "**Crear factura del albarán**". + +Esta acción implica un **enlace entre el albarán (proveedor) y la factura (proveedor)**, de modo que el usuario puede conocerlo al consultar la factura (proveedor) correspondiente. + +!!! info + Para saber más, visite [Factura (Proveedor)](purchase-invoice.md). + +## Líneas + +Una vez que la cabecera del albarán (proveedor) se ha cumplimentado correctamente y guardado, cada artículo recibido puede listarse como una línea de albarán (proveedor) independiente. + +Existen varias formas de crear líneas de albarán (proveedor). + +1.**El usuario siempre puede crear manualmente líneas de albarán (proveedor).** +Esta es la forma a la que el usuario podría recurrir en caso de que no exista un pedido de compra contabilizado ni una factura (proveedor) completada de la que recuperar datos para las mercancías recibidas. + +Como consecuencia, la información a cumplimentar manualmente es: + +- la mercancía o artículos recibidos +- la cantidad recibida +- el hueco donde se almacenarán los artículos + +El botón **Explotar** se muestra al seleccionar una línea con un producto LdM (BOM) no almacenable y el producto no ha sido ya explotado. Al explotar un producto, los componentes de la lista de materiales de los que consta el producto seleccionado se muestran en el albarán. Una vez explotado, no puede comprimirse. Debe eliminar todas las líneas (primero los componentes de la lista de materiales y después el producto LdM) e insertar de nuevo el producto LdM no almacenable. + +2.Por otro lado, también es posible **crear "automáticamente" líneas de albarán (proveedor)** utilizando el botón de proceso de cabecera **"Crear líneas de"**. + +Esto permite al usuario seleccionar los pedidos o facturas pendientes de recibir. + +Por ejemplo, una vez seleccionado un pedido de compra, se muestran las líneas del pedido de compra pendientes de recibir. + +Entonces, el usuario puede seleccionar las líneas de compra recibidas, cambiar la cantidad si es necesario y ubicarlas en el almacén. + +Finalmente: + +- Si se selecciona un pedido de compra/línea, esta acción **vincula cada línea de albarán (proveedor) con la línea de pedido de compra correspondiente**; lo mismo aplica a la factura (proveedor). + +En la **barra de estado** de cada línea, puede encontrar información sobre la **Cant.facturada**, el número de productos facturados de la línea. + +### Contabilidad + +Información contable relacionada con la recepción de material. + +Un **"Albaranes pendientes de recibir" puede contabilizarse** si la tabla "**MaterialMgmtShipmentInOut**" está configurada como Activa para contabilidad en la pestaña \[*Active Tables*\] de la configuración del libro mayor de la organización. + +La contabilización de un "albarán (proveedor)" tiene este aspecto: + +![Contabilización de albaranes](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/goodsreceipt3.png) + +Contabilizar un "albarán (proveedor)" requiere el cálculo del coste del/de los producto/s incluidos. + +En el caso de un albarán (proveedor), esto es: + +- el precio de compra del/de los producto/s +- o el *coste estándar* por defecto del/de los producto/s en caso de calcular el coste usando un *algoritmo de costeo* estándar. + +Si no existe un pedido de compra relacionado, el proceso Costing Server utiliza el más reciente de los siguientes tres valores: + +- el último precio de pedido de compra del proveedor del albarán para el producto. +- la tarifa de compra del producto. +- o el *coste por defecto* del producto. + +Además: + +- La organización **Entidad Legal** debe tener una *Regla de Coste* validada configurada. +- Y el *Proceso en segundo plano de Coste* debe estar planificado para el *Cliente*, para que pueda buscar y permitir que el proceso *Costing Server* calcule el coste de las transacciones. + +Una vez calculados los costes, el **albarán (proveedor) puede contabilizarse** en el libro mayor. + +En el caso de un albarán que contenga productos de tipo **Gasto** sin la casilla **Ventas** seleccionada, es posible utilizar el precio de compra del producto en lugar del coste del producto para contabilizar el albarán. + +Esto funciona si la casilla *Book Using Purchase Order Price* está seleccionada para el/los producto/s. + +En este caso, es necesario que exista un **Pedido de compra** relacionado con el "albarán (proveedor)" contabilizado. + +### Anulación + +Es posible anular totalmente un albarán (proveedor) utilizando el botón de cabecera **"Close"** y después seleccionando la acción "**Anular**". + +Esta acción crea un **nuevo documento** que **revierte el albarán (proveedor).** + +La acción de anulación permite especificar una "**Void Date**" y una "**Void Accounting Date**" del nuevo documento: + +- **Void Date**: es la fecha del movimiento del nuevo documento que revierte el albarán (proveedor). +- **Void Accounting Date**: es la fecha contable del nuevo documento que revierte el albarán (proveedor). + +Ambos campos anteriores toman por defecto las fechas del documento original y validan que las fechas introducidas no sean anteriores a la "Fecha del movimiento" y a la "Fecha contable" del albarán (proveedor), respectivamente. + +La acción de anulación implica que: + +- Etendo genera automáticamente un **nuevo documento** en la ventana "albarán (proveedor)" e **informa del número de documento** creado. El número de documento también se muestra en el campo descripción del albarán (proveedor). Este nuevo documento se crea como se describe a continuación: + - El "**Documento transacción**" utilizado por Etendo es "**MM Receipt**". + - Este documento es **exactamente igual que el original** que se está revirtiendo, **pero la cantidad del movimiento es negativa.** + - Una vez creado el **nuevo documento**, puede **Cambiar Estado** tanto la "**Fecha del movimiento**" como la "**Fecha contable**" del nuevo documento antes de contabilizarlo. + +### Landed Cost + +La pestaña Landed Cost permite asignar costes adicionales al albarán (proveedor). + +![Ventana de Landed cost](../../../../../assets/drive/1YND6qqNXSCzLiiq_PICSVr3GymXZi6_o.png) + +Es posible introducir tantos tipos/líneas de landed cost como sea necesario. + +Algunos campos relevantes a tener en cuenta son: + +- **Tipo de Landed Cost**: es el tipo de landed cost que se va a asignar al albarán (proveedor). +- **Línea de la factura**: sirve para seleccionar la línea de factura de landed cost correspondiente, si existe, que coincida con el tipo de landed cost que se está introduciendo. + Si se selecciona una línea de factura, el importe de la línea de factura se rellena en el siguiente campo "Importe". +- **Importe**: es el importe del landed cost. Este importe puede ser una "estimación" o un importe de "Pago Real" en caso de seleccionar una línea de factura. +- **Algoritmo de Distribución de Landed Cost**: es el distribuido por Etendo "Distribution by Amount", lo que significa que el importe del landed cost se distribuirá entre las líneas del albarán (proveedor) proporcionalmente por el importe de la línea del albarán. + +Una vez cumplimentados todos los elementos anteriores, incluida la línea de factura (proveedor) de landed cost correspondiente, se ejecutan tanto el proceso de "albarán (proveedor)" como el *process matching* de Landed Cost haciendo clic en el botón de proceso "**Completada**". + +## Cómo reactivar albaranes pendientes de recibir + +!!! info + Para poder incluir esta funcionalidad, debe instalarse el Warehouse Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Warehouse Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=EFDA39668E2E4DF2824FFF0A905E6A95){target="\_blank"}. Para más información sobre las versiones disponibles, compatibilidad con core y nuevas funcionalidades, visite [Warehouse Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/warehouse-extensions/release-notes.md). + +Desde la ventana de albarán (proveedor), es posible reactivar un movimiento generado previamente simplemente seleccionando el documento correspondiente y haciendo clic en el botón Reactivate. + +Una vez que el albarán se reactiva correctamente, el estado del documento cambia a Borrador, tal y como puede observarse en la barra de estado. + +![](../../../../../assets/drive/1-Z-wUYZfcGDizQ_Kkp8TUYXTs-KnM67H.png) + +!!! warning + Nota: No es posible reactivar documentos que incluyan transacciones con cantidades que excedan la cantidad de stock existente para un determinado producto en un determinado hueco. La única excepción es cuando la configuración del hueco permite Over Issue. Para más información, visite [Hueco](../../warehouse-management/setup.md#storage-bin). + +## Contabilización Masiva + +!!! info + Para poder incluir esta funcionalidad, debe instalarse el Financial Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. Para más información sobre las versiones disponibles, compatibilidad con core y nuevas funcionalidades, visite [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +La funcionalidad de Contabilización Masiva permite al usuario contabilizar o descontabilizar múltiples registros seleccionando los registros correspondientes y haciendo clic en el botón **Contabilización masiva**. + +Además, el estado contable del/de los registro/s se muestra en la barra de estado, en vista de formulario, o en una columna, en vista de rejilla. + +!!! info + Para más información, visite [the Bulk Posting module user guide](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). + +## Bulk Completion + +!!! info + Para poder incluir esta funcionalidad, debe instalarse el Essentials Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Essentials Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=39AC2D9F72124AC7A1D0A3D005293C9E){target="_blank"}. Para más información sobre las versiones disponibles, compatibilidad con core y nuevas funcionalidades, visite [Essential Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/essentials-extensions/release-notes.md). + +La funcionalidad Bulk Completion permite al usuario completar, reactivar o anular múltiples registros seleccionándolos y haciendo clic en el botón **Bulk Completion**. Esto facilita y hace más eficiente la gestión de registros, reduciendo el tiempo dedicado a procesar registros individuales. + +!!! info + Para más información, visite [the Bulk Completion module user guide](../../../optional-features/bundles/essentials-extensions/bulk-completion.md). + +--- + +Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. + +--- +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md new file mode 100644 index 0000000000..8e14c86d20 --- /dev/null +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md @@ -0,0 +1,330 @@ +--- +title: Landed Cost +tags: + - Proceso de Compras +--- + +# Landed Cost + +:material-menu: `Aplicación` > `Gestión de Compras` > `Transacciones` > `Landed Cost` + +La ventana **Landed Cost** permite al usuario asignar costes adicionales como transporte, seguro o aranceles a albarán(es), por lo tanto el coste de los productos incluidos en el/los albarán(es) se ajusta según corresponda. + +Todos esos costes son necesarios para colocar el producto en el almacén de la organización. + +Cada vez que se contabiliza un landed cost para un albarán de producto valorado a coste "Average", se crea un ajuste de landed cost. + +Los landed costs distribuidos y asignados a productos valorados a coste "Average" implican un cambio en el valor de inventario del producto. En otras palabras, el coste calculado ("Coste Total") del albarán del producto deberá ajustarse del mismo modo que el coste "Average" del producto. + +!!! info + Ten en cuenta que el "Coste Unitario" de la transacción del albarán no cambiará, ya que este tipo de ajuste no es un ajuste de coste unitario sino un coste "extra". + +Todo lo anterior tendrá un impacto contable, por lo tanto el valor de inventario del producto puede ser el mismo que el valor contable del producto. + +Por otro lado, si se contabiliza un landed cost para un albarán de producto valorado a coste "Standard", no se creará ningún ajuste de coste, sino una "Desviación" entre el coste "standard" definido para el producto y su coste "actual". Esta desviación deberá contabilizarse en una cuenta de "Landed Cost Variance", para que pueda analizarse posteriormente. + +La ventana **Landed Cost** permite: + +- o bien contabilizar landed cost "**estimado**" que posteriormente puede asociarse con landed cost "actual" por tipo de landed cost, +- o contabilizar directamente landed cost "**actual**" por tipo de landed cost. + +La ventana **Landed Cost** también permite contabilizar los landed costs una vez procesados. + +Escenario de Landed Cost "**estimado**": + +- Se registra un pedido de compra y, después, el correspondiente albarán y la factura de compra. + En este punto se calcula el coste "average" de los productos incluidos en el albarán. +- Después, los landed costs "estimados" (p. ej. costes de transporte) se asignan al albarán y se registran en la ventana **Landed Cost**. + El coste de los productos incluidos en el albarán se ajusta entonces del mismo modo que la contabilidad del activo del producto. +- Después, se registra una factura de compra que incluye el importe real del coste de transporte y se contabiliza en el libro mayor. +- A continuación, es posible asociar el landed cost "estimado" con el landed cost "facturado". + El coste de los productos incluidos en el albarán se ajusta una vez más si existen diferencias entre los importes de landed cost estimado y real. + +Escenario de Landed Cost "**actual**": + +- Se registra un pedido de compra y, después, el correspondiente albarán y la factura de compra. + En este punto se calcula el coste "average" de los productos incluidos en el albarán. +- Después, se crea un documento de landed cost para registrar el landed cost real del albarán. + El coste de los productos incluidos en el albarán se ajusta entonces del mismo modo que la contabilidad del activo del producto. + +En resumen, la funcionalidad de landed cost sigue los siguientes pasos detallados: + +- **Landed Cost Process**: + - Se crea un documento de landed cost incluyendo tantos tipos e importes de landed cost diferentes como sea necesario. + - Este documento de landed cost puede relacionarse con un único albarán, con varios albaranes o con líneas específicas de albarán. + - Este documento de landed cost puede registrar landed cost "actual" en caso de seleccionar la factura correspondiente, por lo tanto el proceso y la asociación del landed cost se realizan en un solo paso. + - Se procesa el landed cost. + - Esta acción crea un *ajuste de landed cost* vinculado al documento de landed cost. + Este ajuste de coste tiene tantas líneas de ajuste como productos incluidos en el/los albarán(es) seleccionados, por lo tanto el coste de esos productos se ajusta según corresponda. +- **Landed Cost Post**: + - Una vez procesado un documento de landed cost, puede contabilizarse en el libro mayor, por lo tanto también se ajusta la contabilidad del activo del/de los producto(s). +- **Landed Cost Matching**: + - La factura de landed cost se registra y se contabiliza en el libro mayor posteriormente. + - Después, el landed cost "estimado" registrado en el documento de landed cost puede asociarse con los landed costs reales por tipo de landed cost en la factura de landed cost. + - La asociación de landed cost puede generar un ajuste de coste adicional para el/los producto(s) si los importes de landed cost estimado no fueron los mismos que los importes de landed cost real. +- **Landed Cost Matching Post**: + - Una vez que el/los landed cost(s) están asociados, pueden contabilizarse, por lo tanto: + - la contabilidad del activo del/de los producto(s) se ajusta una vez más si aplica, + - y la contabilización del landed cost obtiene las *dimensiones contables* de la factura de landed cost. +## Cabecera + +Un documento de **Landed Cost** puede crearse, procesarse y contabilizarse en esta ventana. + +![Landed cost header](../../../../../assets/drive/1YND6qqNXSCzLiiq_PICSVr3GymXZi6_o.png) + +Algunos campos a tener en cuenta son: + +- **Organización**: es la organización o entidad legal para la cual se necesita registrar el landed cost. +- **Fecha de Referencia**: es la fecha en la que se está creando el documento de landed cost. + +**Coste** + +Un Documento de Landed Cost puede tener tantas líneas de coste como tipos de landed cost a asignar a los Albaranes seleccionados. + +![Landed cost tabs](../../../../../assets/drive/1jbfoYTDqyRZiF3bTwPQkG8OmjpLr0zau.png) + +Algunos campos a tener en cuenta son: + +- Tipo de Landed Cost: es el tipo de landed cost que se va a asignar a la(s) entrega(s) o línea(s) de entrega seleccionadas en la pestaña **Entrega**. +- **Línea de la factura**: sirve para seleccionar la línea de factura de landed cost correspondiente, si ya está contabilizada, que coincida con el tipo de landed cost que se está introduciendo. + Si se selecciona una línea de factura, el importe de la línea de factura se rellena en el siguiente campo "**Importe**". +- **Importe**: es el importe del tipo de landed cost. Este importe puede ser "estimado" o "real" en caso de seleccionar una línea de factura. +- **Moneda**: es la moneda del tipo de landed cost. + - Es importante remarcar que un documento de landed cost puede incluir tantos tipos de landed cost como se requiera en la moneda requerida. + Por ejemplo, un documento de landed cost puede incluir dos líneas de tipo de landed cost, una en USD y otra en EUR. + En este escenario, se creará un ajuste de landed cost que incluirá dos líneas. Los importes del ajuste de coste se calcularán en la moneda configurada para la entidad legal a la que pertenece la transacción de producto. +- **Algoritmo de Distribución de Landed Cost**: hay un algoritmo disponible distribuido por Etendo que es "Distribution by Amount". + Este algoritmo distribuye el importe del tipo de landed cost proporcionalmente por el importe de la(s) línea(s) de entrega entre la(s) entrega(s) seleccionadas. + +Una vez seleccionada(s) la(s) entrega(s) en la pestaña **Entrega**, el documento de landed cost (cabecera) puede procesarse usando el botón de proceso "**Proceso**". + +Esta acción crea un ajuste de landed cost vinculado al documento de landed cost. + +Este ajuste de coste tiene tantas líneas de ajuste como productos incluidos en el/los albarán(es) seleccionado(s); por tanto, el coste de esos productos se ajusta según corresponda. + +Una vez procesado, un documento de landed cost puede: + +- **"Reactivated"**: esta acción anula el ajuste de landed cost vinculado al documento de landed cost. +- o **"Post"**, por lo que la contabilidad del activo del producto también se ajusta en consecuencia. + +La contabilización de **Landed Cost** crea los siguientes asientos contables en el caso de un tipo de landed cost de "Producto": + +| | | | +| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | +| Cuenta | Debe | Haber | +| Activo Producto | Importe de Landed Cost "Estimado".

(\*)Este apunte contable toma las "dimensiones contables" del albarán, como "Proveedor" o "Producto". Ver enlace "Detalle". | | +| Gasto Producto | | Importe de Landed Cost "Estimado" | + +La contabilización de **Landed Cost** crea los siguientes asientos contables en el caso de un tipo de landed cost de "Cuenta": + +| | | | +| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | +| Cuenta | Debe | Haber | +| [*Activo Producto*] | Importe de Landed Cost "Estimado".

(\*)Este apunte contable toma las "dimensiones contables" del albarán, como "Proveedor" o "Producto". Ver enlace "Detalle". | | +| [*Apunte contable*] | | Importe de Landed Cost "Estimado" | + +#### Procesar Asociación + +La asociación entre un landed cost "estimado" y un landed cost "facturado" puede procesarse en: + +**1.** La ventana **ALBARÁN** antes de procesar y usando el botón de proceso "**Complete**" + +Este escenario tiene lugar siempre que toda la información relacionada con landed cost indicada a continuación esté disponible e introducida en la pestaña Landed Cost del **Albarán**: + +- tipos de landed cost +- importes de landed cost +- líneas de factura de landed cost relacionadas + +Este escenario crea automáticamente: + +- un documento de landed cost en la ventana **Landed Cost** relacionado con el albarán, que contiene toda la información introducida en la pestaña "Landed Cost" del Albarán. + Este documento de landed cost ya está procesado y asociado; por tanto, las únicas acciones pendientes son contabilizar el documento de landed cost (cabecera) y contabilizar la asociación de landed cost. +- un ajuste de landed cost que ajusta el coste de cada producto incluido en el Albarán. + +**2**. La ventana **Landed Cost PURCHASE INVOICE**, usando el botón de proceso Match LC Cost que se puede encontrar en cada línea de factura de compra de landed cost. Después se selecciona la casilla **"Process Matching"**. + +Este escenario tiene lugar cuando: + +- se introdujeron todos los datos relacionados con landed cost excepto la información de la línea de factura de landed cost en la pestaña Landed Cost de la ventana **Albarán**. +- se introdujeron todos los datos relacionados con landed cost excepto la información de la línea de factura de landed cost en la pestaña **Coste** de la ventana **Landed Cost**. + +Este escenario crea automáticamente: + +- un nuevo ajuste de landed cost que ajusta una vez más el coste de cada producto incluido en el Albarán si: + - el importe del tipo de landed cost registrado no es el mismo que el facturado + - y se selecciona la casilla "Is matching adjusted". +- la única acción pendiente es contabilizar la asociación de landed cost. + +**3.** La ventana **LANDED COST**, usando el botón de proceso "**Procesar Asociación**" + +Este escenario tiene lugar cuando la asociación se ha ejecutado en la factura de compra de landed cost (ver escenario 2 anterior), pero allí no se seleccionó la casilla "Process Matching". + +Este escenario crea automáticamente: + +- un nuevo ajuste de landed cost que ajusta una vez más el coste de cada producto incluido en el Albarán si el importe del tipo de landed cost registrado no es el mismo que el facturado y se selecciona la casilla "Is matching adjusted". +- la única acción pendiente es contabilizar la asociación de landed cost. + +**4.** La ventana **LANDED COST**, usando el botón de proceso "**Proceso**". + +Este escenario tiene lugar cuando toda la información relacionada con landed cost se introduce en la ventana **Landed Cost**: + +- tipos de landed cost +- importes de landed cost +- líneas de factura de landed cost relacionadas +- y albarán(es) + +Este escenario crea automáticamente: + +- un ajuste de landed cost que ajusta el coste de cada producto incluido en el/los Albarán(es). +- las únicas acciones pendientes son contabilizar el documento de landed cost (cabecera) y contabilizar la asociación de landed cost. + +#### Contabilizar Asociación + +Una asociación de landed cost puede contabilizarse después de ser procesada. Esta contabilización tendrá diferentes asientos contables dependiendo de los escenarios listados a continuación: + +1\. Landed cost "**Estimado**" **igual** a landed cost "**facturado**" + +- En el caso de un tipo de landed cost de "producto" + +| | | | +| ------------------- | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Cuenta | Debe | Haber | +| [*Gasto Producto*] | Importe de Landed Cost "Estimado"="Facturado" | | +| [*Gasto Producto*] | | Importe de Landed Cost "Estimado"="Facturado"

(\*)Este apunte contable toma las "dimensiones contables" de la factura de landed cost, como "Tercero". Ver enlace "Detalle". | + +- En el caso de un tipo de landed cost de "cuenta" + +| | | | +| ------------ | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Cuenta | Debe | Haber | +| [*Apunte contable*] | Importe de Landed Cost "Estimado"="Facturado" | | +| [*Apunte contable*] | | Importe de Landed Cost "Estimado"="Facturado"

(\*)Este apunte contable toma las "dimensiones contables" de la factura de landed cost, como "Tercero". Ver enlace "Detalle". | + +El propósito de los asientos anteriores es que la contabilidad del gasto de landed cost tome las "dimensiones contables" de la factura de landed cost. + +2\. Landed cost "**Estimado**" no igual a landed cost "**facturado**" & **"Is matching adjusted" = No**. + +Esta última configuración ("Is matching adjusted" = No) implica NO crear un ajuste de landed cost que lleve la diferencia al coste del producto (contabilidad del producto); por tanto, esa diferencia permanece bien en el haber (estimado>facturado) o bien en el debe (estimado
(\*)Este apunte contable toma las "dimensiones contables" de la factura de landed cost, como "Tercero". Ver enlace "Detalle". | + +- En el caso de un tipo de landed cost de "cuenta" + +| | | | +| ------------ | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Cuenta | Debe | Haber | +| [*Apunte contable*] | Importe de Landed Cost "Facturado" | | +| [*Apunte contable*] | | Importe de Landed Cost "Facturado"

(\*)Este apunte contable toma las "dimensiones contables" de la factura de landed cost, como "Tercero". Ver enlace "Detalle". | + +3\. Landed cost "**Estimado**" **mayor** que landed cost "**facturado**". **"Is matching adjusted" = Yes** + +Esta última configuración ("Is matching adjusted" = Yes) implica crear un ajuste de landed cost que lleva la diferencia al coste del producto (haber de la contabilidad del producto). + +- En el caso de un tipo de landed cost de "producto" + +| | | | +| ------------------- | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Cuenta | Debe | Haber | +| [*Gasto Producto*] | Importe de Landed Cost "Estimado" | | +| [*Gasto Producto*] | | Importe de Landed Cost "Facturado"

(\*)Este apunte contable toma las "dimensiones contables" de la factura de landed cost, como "Tercero". Ver enlace "Detalle". | +| [*Activo Producto*] | | Diferencia (estimado>facturado) Importe de Landed Cost | + +- En el caso de un tipo de landed cost de "cuenta" + +| | | | +| ----------------- | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Cuenta | Debe | Haber | +| [*Apunte contable*] | Importe de Landed Cost "Estimado" | | +| [*Apunte contable*] | | Importe de Landed Cost "Facturado"

(\*)Este apunte contable toma las "dimensiones contables" de la factura de landed cost, como "Tercero". Ver enlace "Detalle". | +| [*Activo Producto*] | | Diferencia (estimado>facturado) Importe de Landed Cost | + +4\. Landed cost "**Estimado**" **menor** que landed cost "**facturado**". **"Is matching adjusted" = Yes** + +Esta última configuración ("Is matching adjusted" = Yes) implica crear un ajuste de landed cost que lleva la diferencia al coste del producto (debe de la contabilidad del producto). + +- En el caso de un tipo de landed cost de "producto" + +| | | | +| ------------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Cuenta | Debe | Haber | +| [*Activo Producto*] | Diferencia (estimado
(\*)Este apunte contable toma las "dimensiones contables" de la factura de landed cost, como "Tercero". Ver enlace "Detalle". | + +- En el caso de un tipo de landed cost de "cuenta". + +| | | | +| ----------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Cuenta | Debe | Haber | +| [*Activo Producto*] | Diferencia (estimado
(\*)Este apunte contable toma las "dimensiones contables" de la factura de landed cost, como "Tercero". Ver enlace "Detalle". | + +#### Cancelar Asociación + +Una asociación de landed cost puede cancelarse usando el botón de proceso de cabecera "**Cancelar Asociación**". Antes de eso, la asociación de landed cost necesita ser "Unpost". + +La acción de cancelar la asociación implica que: + +- Los importes asociados actuales no se eliminan de la pestaña **Importe Asociado**. +- Se debe ejecutar una nueva asociación en la(s) factura(s) de compra de landed cost correspondiente(s). +- Los importes de asociación correctos se actualizarán entonces en la pestaña **Importe Asociado**. + +### Importe Asociado + +La pestaña **Importe Asociado** es de solo lectura y permite revisar las líneas de factura de compra asociadas contra las líneas de landed cost. + +### Contabilidad Coste + +Esta pestaña proporciona información contable del documento de Landed Cost. + +Como cualquier otra pestaña de contabilidad, esta pestaña muestra los asientos del libro mayor de la contabilización del landed cost. + +### Entrega + +La pestaña **Entrega** permite al usuario seleccionar la(s) entrega(s) o línea(s) de entrega a las que se van a asignar los tipos de landed cost registrados. + +Una vez que la cabecera de **Landed Cost** se ha rellenado correctamente y se ha guardado, se puede registrar una línea de entrega en esta pestaña. + +Los importes de landed cost introducidos en la pestaña "Coste" pueden entonces asignarse/distribuirse entre la(s) entrega(s) introducidas aquí. + +Algunos campos relevantes a tener en cuenta son: + +- **Good Receipt**: sirve para seleccionar un albarán; por tanto, los importes de landed cost se distribuirán entre todas las líneas del albarán. +- **Good Receipt Line**: sirve para seleccionar una línea específica de albarán. + +Ten en cuenta que en un registro debe seleccionarse o bien un albarán o bien una línea de albarán. + +### Importe de la Línea de Albarán + +**Importe de la Línea de Albarán** es una pestaña de solo lectura que muestra información detallada sobre la línea de tipo de landed cost asignada a cada línea de entrega, así como el importe de landed cost distribuido a cada línea de entrega. + +Es importante remarcar que el "Importe" distribuido se calcula teniendo en cuenta la precisión de "Costing" definida para la Moneda. + +### Contabilidad + +Esta pestaña proporciona información contable de la asociación de Landed Cost. +## Contabilización Masiva + +!!! info + Para poder incluir esta funcionalidad, debe estar instalado el *Financial Extensions Bundle*. Para ello, sigue las instrucciones del marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. Para más información sobre las versiones disponibles, compatibilidad con el core y nuevas funcionalidades, visita [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +La funcionalidad de **Contabilización Masiva** permite al usuario contabilizar o descontabilizar múltiples registros seleccionando los registros correspondientes y haciendo clic en el botón **Contabilización Masiva**. En este caso, esta funcionalidad puede utilizarse en la ventana **Landed Cost** y en la pestaña **Coste**. + +Además, el Estado Contable del/de los registro/s se muestra en la barra de estado, en vista de formulario, o en una columna, en vista de cuadrícula. + +!!! info + Para más información, visita [the Bulk Posting module user guide](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). + +--- + +Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. + +--- +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/manage-requisitions.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/manage-requisitions.md new file mode 100644 index 0000000000..fa47a6834e --- /dev/null +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/manage-requisitions.md @@ -0,0 +1,73 @@ +--- +title: Administrar necesidades +tags: + - Proceso de Compras + - Necesidades de compra +--- + +# Administrar necesidades + +:material-menu: `Aplicación` > `Gestión de Compras` > `Transacciones` > `Administrar necesidades` + +La ventana Administrar necesidades está pensada para proporcionar una visión general de los artículos necesarios. + +## Cabecera + +Esta ventana permite al usuario gestionar las necesidades independientemente de su estado actual; por lo tanto, pueden cambiar o cerrar una necesidad de material y crear pedidos de compra para esas demandas. + +![Requisition window Header](../../../../../assets/drive/1yuE4xa0usvVzSdmthjDWdi12OAqTuJTe.png) + +Una **necesidad de material** con estado "Completada" **siempre se puede cambiar**, si es necesario. El usuario debe reactivarla y luego modificarla y contabilizarla. + +También es posible **cerrar una necesidad de material en caso de que ya no se necesite el/los artículo/s incluidos**, usando el botón de menú "**Close**" y luego seleccionando la acción "**Close**". + +El estado de las líneas de la necesidad de material se cambiará entonces a "Cancelled". + +Por último, también es posible **crear pedidos de compra** para aquellas **necesidades de material en estado "Complete"**, usando el botón de menú "**Crear Pedido de Compra (Necesidades de material)**". + +En este caso, se muestra una nueva ventana para que el usuario rellene algunos datos, teniendo en cuenta que: + +- Si hay **distintos proveedores en las líneas de la necesidad de material, así como tarifa**: + - los **valores por defecto** introducidos en la ventana "Crear Pedido de Compra (Necesidades de material)" **serán los que se utilicen** en el pedido de compra. +- Si hay **distintos proveedores en las líneas de la necesidad de material, así como tarifa**, y el usuario no introduce ningún valor por defecto en la ventana "Crear Pedido de Compra (Necesidades de material)": + - **se utilizarán los de las líneas de la necesidad de material** en los pedidos de compra. +- Si **todas las líneas de la necesidad de material tienen el mismo proveedor y tarifa**: + - **no será necesario seleccionar valores por defecto** en la ventana "Crear Pedido de Compra (Necesidades de material)"; además, solo se creará un pedido de compra. + +![Purchase order](../../../../../assets/drive/17OuNS8YpM0VC3MUkLO25DPPHCMwWjq8u.png) + +Etendo proporciona información sobre el/los número/s de pedido/s de compra creados tras pulsar el botón OK en la ventana "Crear Pedido de Compra (Necesidades de material)". + +Esta acción vincula la necesidad de material y el pedido de compra y, además, se crea una línea de pedido de compra por cada línea de la necesidad de material: + +- Una **necesidad de material** vinculada a un pedido de compra cambia su estado de **Completada** a **Cerrado**. +- Una **línea de necesidad de material** vinculada a una línea de pedido de compra cambia su estado de **Open** a **Cerrado**. + +Cualquier **pedido de compra** creado a partir de una **Necesidad de material**: + +- se listará en la **ventana "Pedido de compra"**. +- tendrá un estado "**Booked**" +- y contendrá **datos heredados de la Necesidad de material**, datos como: + - Fecha de pedido + - Fecha de entrega prevista + - Tercero + - Tarifa + - Producto/s + +## Líneas + +El usuario puede realizar un conjunto de acciones relacionadas con las líneas de la necesidad de material. Es posible crear líneas o demandas de producto o cancelarlas. + +- **Se pueden crear manualmente nuevas demandas de producto** dentro de una necesidad de material simplemente **añadiendo nuevas líneas de necesidad de material** antes de crear un pedido de compra. +- **Las demandas de producto existentes o las líneas de necesidad de material pueden cancelarse**, si ya no son necesarias, usando el botón de cabecera "**Cambiar estado**". + +### Líneas de OC (Pedido de compra) emparejadas + +Esta pestaña permite al usuario revisar la línea de pedido de compra vinculada automáticamente a una línea de necesidad de material o vincular manualmente una línea de pedido de compra existente a la línea de necesidad de material correspondiente. + +--- + +Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. + +--- +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.md new file mode 100644 index 0000000000..7758110421 --- /dev/null +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.md @@ -0,0 +1,59 @@ +--- +title: Facturas cuadradas +tags: + - Proceso de Compras + - Pedidos de compra +--- + +# Facturas cuadradas + +:material-menu: `Aplicación` > `Gestión de Compras` > `Transacciones` > `Facturas cuadradas` + +Esta ventana ayuda al usuario a contabilizar las discrepancias entre el inventario y la contabilidad financiera de aquellos artículos para los que se contabilizaron los correspondientes albaranes. + +Las discrepancias mencionadas anteriormente se deben principalmente a diferencias entre: + +- el **precio neto unitario del artículo registrado al contabilizar el pedido de compra** y posteriormente **al contabilizar el correspondiente Albarán.** +- y el **precio neto unitario "final" del artículo registrado al contabilizar la factura de compra.** + +En la ventana, hay un listado de todas las facturas que están cuadradas con albaranes. El cuadre de los documentos se realiza cuando los documentos se crean utilizando la información del otro documento: por ejemplo, haciendo clic en Generar factura desde albarán en el albarán o haciendo clic en el botón Crear líneas desde al crear un albarán para seleccionar la factura. + +![Ventana Facturas cuadradas](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.png) + +### Factura de compra cuadrada + +La pestaña Factura de compra cuadrada lista cada línea de factura contabilizada vinculada a las correspondientes líneas de albarán, que también podrían estar contabilizadas o no. + +Hay un botón de cabecera "**Post**" que es el que contabiliza las discrepancias entre inventario y contabilidad financiera, si las hubiera, una vez seleccionada la línea adecuada. + +El proceso general para contabilizar las discrepancias en contabilidad se detalla a continuación: + +Un documento *Matching Invoice* puede contabilizarse si se ha calculado el coste de los productos incluidos en un *Albarán*. Para obtenerlo: + +- Se requiere una *Regla de Coste* validada en la entidad legal de la Factura Cuadrada, +- y debe ejecutarse el proceso en segundo plano *Costing Background Process*. + +En el caso de productos de "Gasto" que no tengan seleccionada la casilla de verificación "Ventas", es posible utilizar el precio de compra del producto en lugar del coste del producto siempre que esté seleccionada la casilla *Book Using Purchase Order* Price. En este caso, es necesario que un "Pedido de compra" esté relacionado con el "Albarán". + +### Contabilidad + +Información contable relacionada con las facturas de compra cuadradas. + +## Contabilización Masiva + +!!! info + Para poder incluir esta funcionalidad, debe instalarse el Financial Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. Para más información sobre las versiones disponibles, compatibilidad con el core y nuevas funcionalidades, visite [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +La funcionalidad de Contabilización Masiva permite al usuario contabilizar o deshacer la contabilización de múltiples registros seleccionando los registros correspondientes y haciendo clic en el botón **Contabilización Masiva**. + +Además, el Estado Contable del/de los registro/s se muestra en la barra de estado, en la vista de formulario, o en una columna, en la vista de rejilla. + +!!! info + Para más información, visite [the Bulk Posting module user guide](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). + +--- + +Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, usado bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Este trabajo está licenciado bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. + +--- +Este trabajo está licenciado bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md new file mode 100644 index 0000000000..51f508db32 --- /dev/null +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md @@ -0,0 +1,31 @@ +--- +title: Albaranes pendientes de recibir +tags: + - Albaranes + - Proceso de Compras +--- + +# Albaranes pendientes de recibir + +:material-menu: `Aplicación` > `Gestión de Compras` > `Transacciones` > `Albaranes pendientes de recibir` + +Esta ventana permite al usuario: + +- **Use the Filter options** para acotar la búsqueda de pedidos de compra pendientes de entregar. Es posible buscar por: + - Tercero + - Desde Fecha de pedido de compra -> Hasta Fecha de pedido de compra + - Número de pedido de compra +- Introducir una **"Reception date".** +- **Seleccionar** las **"Order line/s of a purchase order/s" delivered** que se muestran agrupadas por Tercero y Pedido de compra. +- **Cambiar estado** la "**Cantidad**" de los bienes que se están recibiendo si es necesario. +- **Introducir** la "**Goods receipt location**" o ubicación (bin) dentro de un almacén. +- **Process it** para crear los albaranes correspondientes. + +![Ventana de albaranes pendientes de recibir](../../../../../assets/drive/1hGrJ6YXXd1p20ZdLQefX1o6_8nVogOd8.png) + +--- + +Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. + +--- +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md new file mode 100644 index 0000000000..99e6717187 --- /dev/null +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md @@ -0,0 +1,425 @@ +--- +title: Factura (Proveedor) +tags: + - Proceso de Compras + - Pedidos de compra +--- + +# Factura (Proveedor) + +:material-menu: `Aplicación` > `Gestión de Compras` > `Transacciones` > `Factura (Proveedor)` + +## Visión general + +La ventana **Factura (Proveedor)** se utiliza para crear, registrar y gestionar facturas de proveedor de bienes y servicios adquiridos. + +Las facturas de proveedor normalmente se generan después de completar un Albarán, asegurando que las cantidades recibidas coinciden con la información facturada por el proveedor. + +Las facturas se crean de dos formas: + +1. Automáticamente, desde un Albarán relacionado usando el botón **Crear factura del albarán** en la ventana de Albarán. +2. Manualmente, introduciendo la factura directamente en esta ventana. + +Cada factura define los productos o servicios, cantidades, precios, impuestos e importes a pagar al proveedor. + +Cuando la factura se contabiliza, los gastos de compra correspondientes se reconocen en contabilidad. Si se configura un plan de gasto diferido, el reconocimiento del gasto se distribuye en el tiempo según la planificación definida. + +!!! example "Flujo de trabajo típico de Factura (Proveedor)" + 1. Se completa un Albarán para un **Pedido de compra** existente. + 2. Abra la ventana **Factura (Proveedor)** y cree un nuevo registro de factura. + 3. Seleccione el **Tercero** (proveedor). El sistema rellena automáticamente las condiciones de pago, el método de pago y la tarifa. + 4. Vaya a la pestaña **Líneas** y haga clic en **Crear Líneas Desde Albarán** para traer los artículos recibidos. + 5. Revise las líneas, verifique cantidades y precios y, a continuación, haga clic en **Complete**. + 6. Contabilice la factura en el libro mayor usando el botón **Post**. + 7. Registre el pago usando el botón **Añadir pago**. + +## Cabecera + +La **Cabecera** contiene la información básica de una factura de proveedor. En la mayoría de los casos, seleccione el **Tercero**; el sistema rellena el resto de campos a partir de los valores por defecto y de la configuración del tercero seleccionado. + +![Purchase invoice window](../../../../../assets/drive/1JvS1mOjiiyATJENTs5SuQIyEAr-UHmE3.png) + +Campos a tener en cuenta: + +- **Documento transacción**: por defecto es *AP Invoice* (factura de proveedor [tipo de documento](../../financial-management/accounting/setup/document-type.md)). Cámbielo a *AP Credit Memo* (tipo crédito positivo, no vinculado a pedidos o envíos) o a *Reversed Purchase Invoice* (importes negativos, para devoluciones). +- **Nº documento**: número de factura del proveedor si la secuencia lo permite; en caso contrario, se asigna un número interno. +- **Fecha de la factura**: fecha de la factura, utilizada para calcular la fecha de vencimiento. +- **Fecha contable**: fecha de contabilización en el libro mayor (por defecto, la Fecha de la factura). +- **Condiciones de pago**: define cuándo vence el pago (por ejemplo, neto 30 días). Se rellena automáticamente desde la configuración del Tercero. +- **Método de Pago**: define el mecanismo de pago (por ejemplo, transferencia bancaria o cheque). Se rellena automáticamente desde la configuración del Tercero. +- **Referencia del Proveedor**: número de referencia opcional proporcionado por el proveedor. + +### Añadir líneas + +Añada líneas de factura usando uno de los siguientes métodos: + +1. Haga clic en **Crear Líneas Desde Pedido** o **Crear Líneas Desde Albarán** para traer elementos pendientes desde un documento relacionado. +2. Haga clic en **Copiar líneas** para copiar líneas desde una factura existente. +3. Añada líneas manualmente en la pestaña **Líneas** cuando no exista un pedido o albarán relacionado. + +### Completar la factura + +Haga clic en **Complete** para finalizar la factura. Esto crea el Plan de Pago y actualiza el Monitor de Pagos. Si la factura contiene un producto empaquetado (un producto compuesto por múltiples componentes, también llamado lista de materiales o BOM), el sistema lo desglosa automáticamente en sus líneas de componentes individuales. + +Tras completar la factura, están disponibles las siguientes acciones: + +- **Post** la factura en el libro mayor usando el botón [Post/Unpost](#postunpost). +- **Anular o Reactivar** la factura usando el botón [Reactivar](#reactivate). +- **Registrar un pago** usando el botón [Añadir pago](#add-payment). + +## Líneas + +Una vez guardada la cabecera de la Factura (Proveedor), añada una o más líneas de factura para los productos o gastos que se están facturando. + +Campos a tener en cuenta: + +- **Línea de factura financiera**: seleccione esto para líneas que no son productos físicos; por ejemplo, una cuenta contable (apunte de mayor) o un cargo de inmovilizado. El campo Producto se sustituye por un campo Cuenta. +- **Valor atributos**: se muestra si el producto utiliza atributos (color, talla, número de serie, etc.). +- **Línea de Pedido de compra / Línea de Albarán**: vincula la línea de factura con la línea del Pedido de compra o del Albarán relacionada, si existe. + +### Diferir gastos + +Use gastos diferidos para repartir un coste en varios periodos contables en lugar de reconocerlo todo de una vez. + +- **Gasto postpuesto**: seleccione esto para distribuir el gasto en el tiempo y mostrar los campos del plan de gastos. +- **Tipo de plan de gastos**: frecuencia de reconocimiento (actualmente: mensual). +- **Número de periodo**: número de periodos en los que se distribuye el gasto. +- **Periodod inicial**: primer periodo contable abierto en el que comienza el reconocimiento. + +Estos valores del plan de gastos pueden venir por defecto desde la configuración del producto. Si se utiliza un plan de gastos, la contabilidad de la factura sigue dicho plan. + +!!! example "Gasto diferido: seguro anual" + Una empresa compra un seguro para el negocio por un año completo con un coste de 1.200 USD. + + - **Gasto postpuesto**: seleccionado + - **Tipo de plan de gastos**: Mensual + - **Número de periodo**: 12 + - **Periodod inicial**: Enero + + El sistema reconoce 100 USD al mes durante 12 meses en lugar de imputar los 1.200 USD completos en un único periodo. + +### Explotar + +El botón **Explotar** aparece cuando la línea de factura seleccionada contiene un producto empaquetado (lista de materiales) que todavía no se ha desglosado en sus componentes. Al hacer clic en este botón, la línea del paquete se sustituye por una línea por componente, de modo que cada artículo aparece individualmente en la factura. + +!!! warning + Esta acción no se puede deshacer. Para revertirla, elimine primero las líneas de componentes y luego vuelva a añadir el producto empaquetado. + +### Asociar Costes LC + +El botón **Asociar Costes LC** asocia el **coste de entrega estimado** definido en la ventana de Coste en destino con el **coste de entrega facturado** introducido en una línea de factura. + +Esta opción está disponible cuando la línea del pedido de compra o de la factura contiene un **producto** o una **cuenta** configurados como tipo de coste en destino. Ambos costes deben pertenecer al **mismo tipo de coste en destino** para poder asociarse. + +La asociación ayuda a: + +- Conciliar costes en destino estimados y facturados. +- Mantener los costes de producto precisos. +- Generar los asientos contables correctos. + +Tras hacer clic en **Asociar Costes LC**, se abre la ventana de selección y edición. Solo se muestran **documentos de Coste en destino procesados**. + +Desde esta ventana: + +- Seleccione el documento de coste en destino correspondiente. +- Introduzca el importe en **Imp. Asociado**. +- Active **Procesar Asociación** para completar el proceso inmediatamente. + +La casilla **Ajustar Asociación** controla cómo se gestionan las diferencias entre costes estimados y facturados: + +- **Marcada**: crea un ajuste adicional de coste en destino para actualizar el coste del producto. +- **Desmarcada**: no se crea ningún ajuste de coste. + +#### Escenarios de asociación + +| Escenario | Ajustar Asociación | Resultado | +|---|---|---| +| Estimado = Facturado | Cualquiera | Solo se contabiliza la asociación en el libro mayor. No se crean ajustes. | +| Estimado ≠ Facturado | Marcada | Se crea un ajuste de coste en destino. El coste del producto se actualiza al importe facturado. Se contabilizan la asociación y el ajuste. | +| Estimado ≠ Facturado | Desmarcada | Solo se contabiliza la asociación. El coste del producto no se modifica. | + +### Línea de impuesto + +La pestaña **Línea de impuesto** es de solo lectura y se rellena automáticamente para cada línea de factura cuando se completa la factura. Detalla la información de impuestos de cada línea en base al campo Impuesto, que se rellena previamente según la configuración de impuestos. + +## Impuesto + +La pestaña **Impuesto** resume la información relacionada con impuestos para toda la factura de proveedor. Contiene un registro por cada tipo impositivo utilizado en la factura. + +El campo **Impuestos** refleja el valor del impuesto calculado automáticamente en base al tipo impositivo y a la configuración de la base imponible. + +!!! info + Si su organización necesita ajustar importes de impuestos en facturas para que coincidan con sistemas externos o requisitos regulatorios (por ejemplo, para corregir diferencias de redondeo de unos céntimos), esta funcionalidad está disponible a través del **Financial Extensions Bundle**. + + Para poder incluir esta funcionalidad, debe instalarse el Financial Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. + + Para más información, visite: [Adjust Invoice Tax user guide](../../../optional-features/bundles/financial-extensions/adjust-invoice-tax.md) + + Esta funcionalidad es compatible desde Etendo 23. + +## Descuentos + +Esta pestaña lista los descuentos aplicados a la factura de proveedor. Los descuentos pueden ser: + +- **Aplicados automáticamente** en base a la configuración del Tercero del proveedor. +- **Introducidos manualmente** para ajustes específicos de la factura. + +Cada registro de descuento muestra el porcentaje de descuento y si se aplica **en cascada** (cada descuento se calcula sobre el precio ya reducido por el descuento anterior; por ejemplo, 10% sobre 100 USD = 90 USD, luego 5% sobre 90 USD = 85,50 USD) o **de forma independiente** (cada descuento se calcula sobre el precio original; 10% + 5% = 15% sobre 100 USD = 85 USD). + +!!! info + Para más información sobre la configuración de descuentos, visite [Descuentos](../../master-data-management/master-data.md#basic-discount). + +## Plan de Pago + +La pestaña **Plan de Pago** lista los pagos programados esperados contra la factura. Los registros del plan de pagos se generan automáticamente cuando se completa la factura, en base a las **Condiciones de pago** definidas en la cabecera. + +Cada registro muestra: + +- **Fecha esperada**: la fecha en la que vence el pago. +- **A liquidar**: el importe a pagar en esa fecha. +- **Método de Pago**: el mecanismo de pago a utilizar. +- **Importe Pendiente**: el importe restante aún no pagado. + +El plan de pagos de una factura no pagada puede modificarse: + +- La **Fecha esperada** puede cambiarse directamente en esta pestaña. +- La **Fecha esperada**, el **Método de Pago** y el **Importe Pendiente** también pueden cambiarse usando el botón [Modificar Plan de Pagos](#modify-payment-plan), si está instalado el módulo Advanced Bank Account Management. + +## Factura Rectificativa + +La pestaña **Factura Rectificativa** vincula un documento de reversión con la factura original que revierte. Esta pestaña se utiliza en dos escenarios: + +**Anulación completa de una factura** + +Cuando una factura se anula usando el botón [Reactivar](#reactivate) con la acción **Anular**: + +- Etendo crea automáticamente una *Reversed Purchase Invoice* y la vincula a la factura original. +- La factura original aparece en la pestaña **Factura Rectificativa** del documento de reversión. + +**Anulación parcial de una factura** + +Al crear manualmente una reversión parcial (*AP Credit Memo* o *Reversed Purchase Invoice*): + +- Para vincular una reversión parcial con la factura original: abra el documento de reversión (el AP Credit Memo o Reversed Purchase Invoice que acaba de crear), vaya a su pestaña **Factura Rectificativa** y añada el número de la factura original. Este paso es necesario para mantener la trazabilidad entre ambos documentos. + +## Tipos de cambio + +La pestaña **Tipos de cambio** permite introducir un tipo de cambio entre la divisa del libro mayor de la organización y la divisa de la factura del proveedor, que se utilizará al contabilizar la factura en el libro mayor. + +Esta pestaña es relevante cuando la divisa de la factura del proveedor difiere de la divisa del libro mayor de la organización; por ejemplo, al comprar bienes a un proveedor extranjero. + +La pestaña permite introducir: + +- Un **Tipo de Cambio** entre la divisa del libro mayor y la divisa de la factura del proveedor. +- O el **importe total de la factura en divisa extranjera**, para que Etendo calcule automáticamente el tipo de cambio correspondiente. + +!!! info + Etendo también mantiene un repositorio central de tipos de cambio, que se utiliza cuando no se define un tipo de cambio a nivel de documento. Para más información, visite [Esquema contable](../../financial-management/accounting/setup/general-ledger-configuration.md). + +## Contabilidad + +Una factura de proveedor puede contabilizarse en el libro mayor en una **Fecha contable** determinada usando el botón [Post/Unpost](#postunpost). + +### Contabilización estándar de Factura (Proveedor) + +| Cuenta | Debe | Haber | Comentarios | +|---|---|---|---| +| Gasto de producto | Importe neto de línea | | Una por línea de factura | +| IVA soportado | Impuestos | | Una por línea de impuesto | +| Descuento en gasto de producto | | Importe de descuento | Una por línea de factura (si existe descuento) | +| Deuda con proveedor | | Importe bruto total | Una por factura | + +### Contabilización de gasto diferido + +Cuando una línea de factura de proveedor tiene configurado un [plan de gastos](#diferir-gastos), la contabilización se distribuye en múltiples periodos en lugar de reconocer el gasto completo de una vez. + +**Contabilización inicial (Fecha contable):** + +| Cuenta | Debe | Haber | +|---|---|---| +| Gasto diferido de producto | Importe neto de línea | | +| IVA soportado | Impuestos | | +| Deuda con proveedor | | Importe bruto total | + +**Cada periodo posterior (Fecha contable + 1 mes, + 2 meses, ..., + N meses):** + +| Cuenta | Debe | Haber | +|---|---|---| +| Gasto de producto | Importe neto de línea / N | | +| Gasto diferido de producto | | Importe neto de línea / N | + +Donde **N** es el número de periodos definido en el plan de gastos. + +!!! info + Para más información, visite [How to Manage Deferred Revenue and Expenses](../../../how-to-guides/how-to-manage-deferred-revenue-and-expenses.md). + +### Contabilización de factura revertida + +Cuando una factura se anula, el documento de reversión crea los siguientes asientos contables: + +| Cuenta | Debe | Haber | Comentarios | +|---|---|---|---| +| Gasto de producto | | Importe neto de línea | Una por línea de factura | +| IVA soportado | | Impuestos | Una por línea de impuesto | +| Deuda con proveedor | Importe bruto total | | Una por factura | + +La contabilización de *AP Credit Memo* sigue la misma estructura que la contabilización de *Reversed Purchase Invoice*. + +!!! info + Para detalles sobre cómo anular o anular parcialmente una factura, consulte la sección del botón [Reactivar](#reactivate). +## Botones + +### Post/Unpost + +Contabilice una factura de proveedor en el libro mayor en una **Fecha contable** determinada usando este botón. Una vez contabilizada, deshaga la contabilización usando el mismo botón. + +### Reactivar + +![pop-up-reactivate](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/pop-up-reactivate.png) + +Este botón proporciona dos opciones para una factura Completada: + +- **Reactivar**: devuelve el registro del estado *Completado* a *Borrador*, permitiendo ediciones sin crear un nuevo documento. Use esta opción cuando la factura contenga errores que deban corregirse antes de volver a contabilizar. +- **Anular**: crea un nuevo documento que revierte completamente la factura. Use esta opción cuando la factura ya no sea válida y deba cancelarse. + +!!! example "Cuándo usar cada opción" + - Use **Reactivar** cuando se haya introducido incorrectamente un precio o una cantidad y la factura aún no se haya pagado. + - Use **Anular** cuando se devuelvan mercancías al proveedor y sea necesario cancelar la factura completa. + +**Anulación de una factura** + +![pop-up-void](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/popup-void.png) + +Al anular, especifique los siguientes campos para el documento de reversión: + +- **Fecha de anulación**: fecha de movimiento del documento de reversión. Por defecto es la fecha actual y no puede ser anterior a la **Fecha de la factura** original. +- **Fecha contable de anulación**: fecha contable del documento de reversión. Por defecto es la fecha actual y no puede ser anterior a la **Fecha contable** original. +- **Referencia del Proveedor**: número de referencia opcional para el documento revertido. Introdúzcalo aquí o deje el campo en blanco para completarlo más tarde. + +Etendo genera automáticamente un nuevo documento en la ventana *Factura (Proveedor)* que revierte la factura original e informa del nuevo número de documento. + +El documento de reversión utiliza el tipo de documento de transacción *Reversed Purchase Invoice*, que es idéntico al original pero con cantidades facturadas negativas. + +Una vez creado el documento de reversión, cambie la *Fecha de la factura* y la *Fecha contable* si es necesario antes de contabilizar. + +La pestaña *Factura Rectificativa* enlaza tanto el documento original como el de reversión. + +**Anulación parcial de una factura** + +También es posible anular parcialmente una factura de proveedor creando manualmente uno de los siguientes documentos de compra revertidos en la ventana Factura (Proveedor): + +- **AP Credit Memo**: la cantidad facturada es positiva. +- **Reversed Purchase Invoice**: la cantidad facturada es negativa. + +Para enlazar una reversión parcial con la factura original: abra el documento de reversión (el AP Credit Memo o Reversed Purchase Invoice que acaba de crear), vaya a su pestaña **Factura Rectificativa** y añada el número de la factura original. Este paso es obligatorio para mantener la trazabilidad de auditoría entre ambos documentos. + +Para saber más, visite [Factura Rectificativa](#reversed-invoices). + +La contabilización de **AP Credit Memo** se ve igual que la contabilización de **Reversed Purchase Invoice**. La principal diferencia entre los dos tipos de documento es: + +- **AP Credit Memo**: la cantidad facturada es una cantidad positiva. +- **Reversed Purchase Invoice**: la cantidad facturada es una cantidad negativa. + +!!! note + Use el tipo de documento **Reversed Purchase Invoice** al anular parcialmente facturas de proveedor. + +### Añadir pago + +Registre uno o más pagos contra una factura de proveedor usando el botón **Añadir pago**, que abre la ventana emergente Añadir pago. + +### Contabilización Masiva + +!!! info + Para poder incluir esta funcionalidad, debe estar instalado el Financial Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. Para más información sobre las versiones disponibles, compatibilidad con core y nuevas funcionalidades, visite [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +La funcionalidad Contabilización Masiva permite al usuario contabilizar o deshacer la contabilización de múltiples registros seleccionando los registros correspondientes y haciendo clic en el botón **Contabilización Masiva**. + +El Estado contable de cada registro se muestra en la barra de estado en la vista de formulario, o en una columna en la vista de rejilla. + +!!! info + Para más información, visite [la guía de usuario del módulo Bulk Posting](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). + +### Bulk Completion + +!!! info + Para poder incluir esta funcionalidad, debe estar instalado el Essentials Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Essentials Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=39AC2D9F72124AC7A1D0A3D005293C9E){target="_blank"}. Para más información sobre las versiones disponibles, compatibilidad con core y nuevas funcionalidades, visite [Essential Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/essentials-extensions/release-notes.md). + +La funcionalidad Bulk Completion permite al usuario completar, reactivar o anular múltiples registros seleccionándolos y haciendo clic en el botón **Bulk Completion**. Esto facilita la gestión de registros y la hace más eficiente. + +!!! info + Para más información, visite [la guía de usuario del módulo Bulk Completion](../../../optional-features/bundles/essentials-extensions/bulk-completion.md). + +!!! warning + **Nota:** Si el módulo [Purchase Invoice Validation](../../../optional-features/bundles/procurement-extensions/purchase-invoice-validation.md) está activo en su sistema, la anulación masiva no funcionará. En ese caso, anule cada factura individualmente usando la opción **Reactivar > Anular**, que permite introducir una referencia de proveedor única para cada reversión. + ![popup-bulk-void](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/popup-bulk-void.png) + +### Eliminar Pago + +La funcionalidad de eliminación de pagos borra y reactiva pagos. También permite eliminar y reactivar transacciones bancarias y conciliaciones. + +!!! info + Para poder incluir esta funcionalidad, debe estar instalado el Financial Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. Para más información sobre las versiones disponibles, compatibilidad con core y nuevas funcionalidades, visite [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +Para eliminar un pago, seleccione el documento correspondiente y haga clic en el botón **Eliminar Pago**. También se eliminan los siguientes registros relacionados: + +- Si hay un pedido asociado a la factura, se elimina el enlace entre el pedido y el pago (ventana **Pedido de compra** > pestaña **Plan de Pago**). +- Si el pago está en estado *Depositado/Retirado no conciliado* en la cuenta financiera, la transacción también se elimina (ventana **Cuenta financiera** > pestaña **Transacción**). +- Si el pago está conciliado mediante un método automático, también se eliminan la línea de extracto bancario y la línea de conciliación bancaria (ventana **Cuenta financiera** > **Extractos bancarios importados** y **Reconciliaciones**). + +!!! info + Si el pago está contabilizado, el asiento contable también se elimina. + +![Remove Payment confirmation dialog](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/PRpic4.png) + +### Deshacer anulación + +!!! info + Para poder incluir esta funcionalidad, debe estar instalado el Financial Extensions Bundle. Para ello, siga las instrucciones del [marketplace](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. Para más información sobre las versiones disponibles, compatibilidad con core y nuevas funcionalidades, visite [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +El botón **Deshacer anulación** reactiva facturas de proveedor anuladas. Seleccione la factura y haga clic en **Deshacer anulación** para restaurarla. + +![Unvoid button restoring a voided purchase invoice to Complete status](../../../../../assets/drive/1UisxZzbpppLvN_rdL__TJg8tLeh5sMfW.png) + +Una vez finalizado el proceso, el estado de la factura de proveedor pasa a *Completado*. + +!!! note + En el caso de la versión estándar del módulo, deshaga también la anulación de la factura revertida correspondiente. + +!!! warning + **Importante:** Cuando deshace la anulación de una factura, el sistema restaura los asientos contables originales. Si la factura revertida ya estaba contabilizada, esos asientos pueden seguir existiendo, lo que provocaría asientos contables duplicados. + + Antes de contabilizar la factura reactivada, revise la pestaña **Contabilidad** y elimine cualquier asiento existente que se haya creado por la anulación previa. Si no está seguro de si existen asientos, contacte con su administrador del sistema antes de continuar. + +!!! info + Consulte la documentación técnica sobre [Advanced Financial Docs Processing](../../../../../developer-guide/etendo-classic/bundles/financial-extensions-bundle/overview.md#advanced-financial-docs-processing) para ampliar el proceso. + +### Modificar Plan de Pagos + +!!! info + Para poder incluir esta funcionalidad, debe estar instalado el módulo Advanced Bank Account Management del Financial Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. Para más información sobre las versiones disponibles, compatibilidad con core y nuevas funcionalidades, visite [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +El módulo Advanced Bank Account Management añade un campo **Cuenta bancaria** a la cabecera de la Factura (Proveedor). Este campo se rellena automáticamente con la cuenta bancaria relacionada con la dirección o el tercero de la factura. También se añade el botón **Modificar Plan de Pagos** para una gestión flexible de pagos. + +![bank-account.png](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/bank-account.png) + +!!! info + Para más información, visite la [guía de usuario de Advanced Bank Account Management](../../../optional-features/bundles/financial-extensions/advanced-bank-account-management.md). + +## Intercompany + +Si su empresa opera con múltiples entidades legales dentro de Etendo (por ejemplo, una empresa matriz que compra en nombre de una filial), la funcionalidad Intercompany crea automáticamente la factura de venta asociada en la organización receptora cuando se contabiliza una factura de proveedor, eliminando la necesidad de registrar la transacción dos veces. + +Cuando los pedidos o las facturas implican a dos o más organizaciones que pertenecen al mismo cliente, esta funcionalidad genera automáticamente el documento inverso correspondiente. + +!!! info + Para más información, visite [la guía de usuario del módulo Intercompany](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/intercompany.md). + +!!! info + Para poder incluir esta funcionalidad, debe estar instalado el Financial Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. Para más información sobre las versiones disponibles, compatibilidad con core y nuevas funcionalidades, visite [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +--- + +Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="_blank"} por [Etendo](https://etendo.software){target="_blank"}. + +--- +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md new file mode 100644 index 0000000000..e055877ade --- /dev/null +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md @@ -0,0 +1,212 @@ +--- +title: Pedido de compra +tags: + - Pedidos de compra + - Proceso de Compras +--- + +# Pedido de compra + +:material-menu: `Aplicación` > `Gestión de Compras` > `Transacciones` > `Pedido de compra` + +La ventana Pedido de compra permite al usuario gestionar pedidos que, una vez contabilizados, se enviarán a los proveedores externos. En otras palabras, es un documento para registrar productos y/o servicios que se van a comprar y documentar. + +![Purchase order window](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchaseorder.png) + +Una vez que el documento está contabilizado, puede enviarse al proveedor externo y puede pagarse por adelantado si es necesario. + +Los pedidos de compra pueden crearse y contabilizarse en la sección de cabecera de la ventana de pedido de compra. + +## Cabecera + +La **cabecera del pedido de compra** permite introducir la siguiente información: + +- **Organización:** entidad organizativa dentro del cliente. +- **Documento transacción**, que en este caso se establece por defecto como "**Pedido de compra**". +- **Nº documento**, o el número de pedido de compra de la compañía. +- **Fecha de pedido:** esta fecha también se establece por defecto por Etendo en base a la fecha del sistema, pero siempre puede modificarse. +- **Terceros**: el usuario final debe seleccionar el proveedor al que se emite el pedido de compra. +- **Dirección**: se completa automáticamente una vez seleccionado el tercero, en base a la dirección o ubicación configurada como "Dirección de envío". +- **Almacén**: aunque Etendo lo establece por defecto según las opciones seleccionadas en el "Perfil", debe ser verificado por el usuario final. +- **Fecha comprometida**: es la fecha en la que la organización o entidad legal requiere que se entreguen los artículos. +- **Método de pago**, **Condiciones de pago** y **Tarifa**: se establecen por defecto por Etendo una vez seleccionado un tercero. +- **Nº de referencia**, texto libre que puede encontrarse en la sección "Más información"; puede usarse para guardar el número de pedido del proveedor, si existe. + +En la **barra de estado** de la cabecera, el usuario puede encontrar la siguiente información: + +- **Estado doc.**: estado del documento del pedido. El pedido puede estar en estado contabilizado, borrador, cerrado, entre otros. +- **Importe total**: importe bruto total del pedido. +- **Imp. total líneas**: importe neto total del pedido. +- **Moneda**: moneda del pedido. +- **Estado del envío**: indica en % qué cantidad del pedido se ha recibido. +- **Estado de factura**: indica en % qué cantidad del pedido se ha facturado. + +**Una vez que la información de cabecera esté correctamente cumplimentada, puede ir a la pestaña "Líneas" para introducir la información de la(s) línea(s) del pedido de compra**. + +!!! info + Para aprender cómo introducir líneas de pedido de compra, visite la siguiente sección [Líneas](purchase-order.md#lines). + +Es posible realizar hasta **tres acciones posibles respecto a un pedido de compra**, usando el **botón de cabecera "Registrar"**: + +- **Procesarlo**, en caso de que quiera procesarlo pero no registrarlo como definitivo, porque podría necesitar cambiarlo más adelante. +- **Anularlo**, en caso de que el pedido de compra ya no sea necesario y, por tanto, deba anularse. +- **Registrarlo**, en caso de que sea correcto y definitivo. + +!!! info + Si existen productos LdM (BOM) no almacenables y no se han desglosado, el botón Registrar los desglosa automáticamente. + +## Líneas + +Una vez que la cabecera del pedido de compra se ha cumplimentado correctamente y se ha guardado, cada línea del pedido de compra puede crearse en esta pestaña. + +Las líneas del pedido de compra pueden crearse de tres formas diferentes: + +**1\. Creando manualmente nuevos registro(s) en la pestaña "Líneas"**. + +Los campos de la línea del pedido de compra que puede cumplimentar se describen a continuación: + +- **Producto**. Puede seleccionar un artículo o producto de la lista o usar el icono del selector de producto. +- **Cant. pedido**, o **Cantidad Operativa** si el producto tiene configurada una *unidad de medida alternativa (AUM)*. Esta es la cantidad necesaria del producto/artículo. +- **Unidad** del producto, o **Unidad Alternativa** del producto dependiendo de la configuración del producto respecto a la unidad de medida. +- **Valor del conjunto de atributos. Un atributo asociado a un producto como parte de un conjunto de atributos.** +- **Precio unitario**. Este proviene de la **Tarifa** seleccionada en la cabecera, pero siempre puede modificarse. +- **Importe neto de línea. El importe final de una línea especificada, basado únicamente en cantidades y precios.** +- **Impuesto**. El impuesto de compra normalmente lo completa el sistema, dependiendo de la configuración de impuestos. + +**2\. Recuperando todas las líneas de pedidos de compra creados previamente.** En este caso, debe usar el botón de proceso "**Copiar desde pedidos**". + +Este botón de proceso habilita la ventana **Copiar desde pedidos (seleccionar y editar)**. + +La ventana "Copiar desde pedidos (seleccionar y editar)" permite buscar los pedidos a copiar usando las opciones de filtro disponibles. + +La información de líneas de los pedidos seleccionados se insertará en la(s) línea(s) del pedido de compra; después, esa información puede modificarse manualmente. + +**3\. Copiando líneas de otros pedidos de compra.** + +En este caso, debe usar el botón de proceso **"Copiar líneas"**. + +Este botón de proceso habilita una nueva ventana llamada "Copiar líneas desde pedido", que permite crear líneas de pedido seleccionando los productos ya comprados al proveedor del pedido, teniendo en cuenta los *días de consumo* configurados para el proveedor. + +En la **barra de estado** de cada línea, puede encontrar información sobre: + +- **Cant.entregada**: número de productos recibidos de la línea. +- **Cant.facturada**: número de productos facturados de la línea. + +### Botón Desglosar + +El botón Desglosar se muestra al seleccionar una línea con un producto LdM (BOM) no almacenable y el producto aún no se ha desglosado. Al desglosar un producto, los componentes de la lista de materiales de los que consta el producto seleccionado se muestran en el pedido. + +!!! info + Una vez desglosado, no puede comprimirse. Debe eliminar todas las líneas (primero los componentes de la lista de materiales y luego el producto LdM) e insertar de nuevo el producto LdM no almacenable. + +### Línea de impuesto + +Para cada línea del pedido de compra, Etendo completa automáticamente en esta pestaña la información relacionada con el impuesto de línea. + +La pestaña de impuesto de línea informa sobre cada línea del pedido de compra: + +- **tipo impositivo aplicado** +- **importe de impuesto calculado** +- **Base imponible** + +!!! info + No es posible crear manualmente una nueva línea ni modificar las existentes. + +### Descuentos básicos + +Lista información sobre los descuentos aplicados automáticamente en base a la configuración del proveedor y/o introducidos manualmente para el pedido de compra. + +![Basic discounts](../../../../../assets/drive/1AavUV8S8kQ2dp0P_W9lw06XfmAf5d_g-.png) + +### Plan de pagos + +Muestra el importe total previsto a pagar al registrar el pedido, así como el/los importe(s) pagados por adelantado o pagados contra la(s) factura(s) del pedido. + +La información del plan de pagos es necesaria a nivel de pedido porque los proveedores podrían solicitar un **pago por adelantado** de toda o parte de una deuda antes de su fecha de vencimiento. + +Los planes de pago de pedidos de compra **no muestran ni gestionan fechas de vencimiento válidas**, sino el plan de pagos de la(s) factura(s) de compra correspondiente(s). + +Esta pestaña también muestra información sobre los pagos regulares recibidos contra la(s) factura(s) de este pedido, como importes pagados. + +Por último, el plan de pagos de un pedido de compra será **eliminado**: + +- si el pedido de compra es **Reactivated** +- o si el pedido de compra es **Voided** + +### Detalles de Pago + +Muestra los detalles de los pagos (pagos por adelantado o pagos regulares) realizados para el pedido o para la(s) factura(s) del pedido. + +## Cómo reactivar un pedido de compra cerrado + +!!! info + Para poder incluir esta funcionalidad, debe estar instalado el Financial Extensions Bundle. Para ello, siga las instrucciones del [marketplace](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. Para más información sobre las versiones disponibles, compatibilidad con el core y nuevas funcionalidades, visite [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +!!! warning "Aviso de dependencia" + Este módulo depende del módulo [**Bulk Completion**](../../../optional-features/bundles/essentials-extensions/bulk-completion.md), ya que las acciones de procesamiento de **pedido** deben realizarse usando procesos modernos que permitan el disparo de Hooks, en lugar del procesamiento legacy. Debido a este requisito, las acciones legacy de **cerrar/reactivar** para pedidos se ocultarán y estas acciones solo estarán disponibles a través del botón **Bulk Completion**. + +Etendo permite al usuario reactivar pedidos de compra cerrados seleccionando el/los necesario(s) y haciendo clic en el botón Deshacer cierre. + +![](../../../../../assets/drive/1cyLa7pjnsNgXtnSEK2lZX9s35imhD2Kq.png) + +Una vez finalizado el proceso, el estado del pedido de compra pasa a contabilizado. + +!!! info + Consulte la documentación técnica sobre Advanced Financial Docs Processing para ampliar el proceso. + +## Eliminación de pagos + +El objetivo de esta funcionalidad es eliminar y reactivar pagos de forma ágil y sencilla. Además, permite eliminar y reactivar transacciones bancarias y conciliaciones. + +!!! info + Para poder incluir esta funcionalidad, debe estar instalado el Financial Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. Para más información sobre las versiones disponibles, compatibilidad con el core y nuevas funcionalidades, visite [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +Desde esta ventana, es posible eliminar pagos asociados a un pedido de compra seleccionando el documento correspondiente y luego haciendo clic en el botón Eliminar pago. Si existe una factura asociada al pedido, también se eliminará la relación de esta factura con el pago en cuestión (ventana Factura de compra > pestaña Plan de pagos). + +Si el pago está incluido en la cuenta financiera, es decir, si está en estado Depositado/Retirado no conciliado, también se eliminará la transacción en ella (ventana Cuenta financiera > pestaña Transacción). + +Si el pago está conciliado mediante un método automático, entonces, además de la transacción en la cuenta financiera, se eliminará la línea del extracto bancario a la que estaba vinculada (ventana Cuenta financiera > Extractos bancarios importados) y la línea correspondiente de la conciliación bancaria (Cuenta financiera > Conciliaciones). + +!!! info + Si el pago está contabilizado, también se elimina el asiento contable. + +![](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/PRpic2.png) + +## Intercompany + +En caso de que el usuario tenga que crear pedidos o facturas entre dos o más organizaciones diferentes pero que pertenecen al mismo cliente, esta funcionalidad permite generar automáticamente el documento inverso correspondiente. + +!!! info + Para más información, visite [la guía de usuario del módulo Intercompany](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/intercompany.md). + +!!! info + Para poder incluir esta funcionalidad, debe estar instalado el Financial Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. Para más información sobre las versiones disponibles, compatibilidad con el core y nuevas funcionalidades, visite [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +## Bulk Completion + +!!! info + Para poder incluir esta funcionalidad, debe estar instalado el Essentials Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Essentials Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=39AC2D9F72124AC7A1D0A3D005293C9E){target="_blank"}. Para más información sobre las versiones disponibles, compatibilidad con el core y nuevas funcionalidades, visite [Essential Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/essentials-extensions/release-notes.md). + +La funcionalidad Bulk Completion permite al usuario completar, reactivar o cerrar múltiples registros seleccionándolos y haciendo clic en el botón **Bulk Completion**. Esto facilita y hace más eficiente la gestión de registros, reduciendo el tiempo dedicado a procesar registros individuales. + +!!! info + Para más información, visite [la guía de usuario del módulo Bulk Completion](../../../optional-features/bundles/essentials-extensions/bulk-completion.md). + +## Advanced Bank Account Management + +!!! info + Para poder incluir esta funcionalidad, debe estar instalado el módulo Advanced Bank Account Management del Financial Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. Para más información sobre las versiones disponibles, compatibilidad con el core y nuevas funcionalidades, visite [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +Este módulo añade un nuevo campo a la cabecera de la ventana Pedido de compra: **Cuenta Bancaria**. Este campo se completa automáticamente con la cuenta bancaria relacionada con la dirección o el tercero del pedido. + +![bank-account-3.png](../../../../../assets/legacy/bank-account-3.png) + +!!! info + Para más información, visite la [guía de usuario de Advanced Bank Account Management](../../../optional-features/bundles/financial-extensions/advanced-bank-account-management.md). + +--- + +Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, usada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. + +--- +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition-to-order.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition-to-order.md new file mode 100644 index 0000000000..eda132b5e6 --- /dev/null +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition-to-order.md @@ -0,0 +1,36 @@ +--- +title: Necesidad a Pedido +tags: + - Proceso de Compras + - Necesidades de Compra + - Pedidos de Compra +--- + +# Necesidad a Pedido + +:material-menu: `Aplicación` > `Gestión de Compras` > `Transacciones` > `Necesidad a Pedido` + +La ventana Necesidad a Pedido muestra todas las necesidades "Completada" que coinciden con los criterios utilizados en la sección "Filter" y también muestra las líneas de necesidad seleccionadas como bloqueadas; por lo tanto, la misma demanda de producto no puede incluirse más de una vez en un pedido de compra. + +![Necesidad a pedido](../../../../../assets/drive/1Xl_R8oaUrOaO0SK4wB5BYNw3wJDEjHBX.png) + +En otras palabras, la sección superior de esta ventana muestra las líneas de necesidad encontradas que todavía no están vinculadas a un pedido. +Estas son las líneas que el usuario puede añadir al área "Lock" en la sección inferior de la ventana. + +Una línea de necesidad bloqueada no puede ser modificada por ningún otro usuario, hasta que quien la bloqueó la desbloquee. +De este modo, durante el tiempo en que las líneas de necesidad están bloqueadas: + +- La misma demanda de producto no se incluirá en un pedido de compra, por error. +- El equipo de compras tendrá la oportunidad de revisar el stock y contactar con distintos proveedores si fuera necesario para negociar un precio para los productos. +- Si no hay actividad durante 3 días, el sistema elimina el bloqueo de las líneas. + +Una necesidad puede desbloquearse manualmente por el responsable de compras o por quien la bloqueó, moviéndola de nuevo a la parte superior de la pantalla "Necesidad a Pedido" mediante el botón "Eliminar Pago". + +Una vez que las demandas de producto estén claras y bloqueadas, el último paso a realizar en esta ventana es crear un pedido de compra para esas necesidades usando el botón de proceso "Crear". + +--- + +Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, utilizado bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. + +--- +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md new file mode 100644 index 0000000000..b0118906b5 --- /dev/null +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md @@ -0,0 +1,76 @@ +--- +title: Necesidad de material +tags: + - Proceso de Compras + - Necesidades de compra +--- + +# Necesidad de material + +:material-menu: `Aplicación` > `Gestión de Compras` > `Transacciones` > `Necesidad de material` + +Una Necesidad de material es un documento que especifica una solicitud para pedir productos. + +El usuario puede crear necesidades de material y monitorizarlas en esta ventana: + +![Ventana de Necesidad de material](../../../../../assets/drive/1ihaEseE5RnNH7INNbaRLyvZC0P2q-hTl.png) + +## Cabecera + +La cabecera de la Necesidad de material permite introducir los siguientes datos: + +- El tercero o proveedor; este es un campo opcional que puede ser rellenado por el solicitante en caso de que se conozca, por lo tanto: + - El proveedor introducido en la cabecera será el que se utilice para cada línea de la necesidad de material, a menos que se cambie a nivel de líneas para una línea en particular. + - Si no hay ningún proveedor introducido en la cabecera de la necesidad de material, se utilizará el configurado por defecto para el producto en su ventana de datos maestros, pestaña *Compras*. + - Si no hay ningún tercero o proveedor en la cabecera, ni en las líneas, ni configurado en el producto, el usuario tendrá que introducirlo al crear el pedido de compra a partir de la necesidad de material. +- La tarifa de compra. Este también es un campo opcional a rellenar, en caso de que el solicitante la conozca, y su comportamiento es el mismo que el descrito anteriormente, ya que está vinculada al Tercero. + +Además, el sistema rellena los siguientes datos: + +- El Nº de documento, que es el número de la Necesidad de material. +- El solicitante, que es el usuario que introduce la necesidad de material. + +![Necesidad de material](../../../../../assets/drive/1G5HR3bMmJXW837o-6qzZ0CTe418q5JB7.png) + +El solicitante puede entonces pasar a la pestaña "Líneas" para introducir datos adicionales. + +## Líneas + +Cada línea de la necesidad de material muestra una demanda de producto para una fecha específica. + +La pestaña "Líneas" de la Necesidad de material recoge los siguientes datos de demanda: + +- La *fecha necesaria*, es decir, la fecha en la que se requiere que llegue el producto. +- El *producto*, artículos/productos que necesitan comprarse. +- La *cantidad* solicitada, o la *cantidad operativa* solicitada si el producto tiene configurada una *unidad de medida alternativa (AUM)*. +- La *UdM* del producto, o la *UdM alternativa* del producto, dependiendo de la configuración del producto respecto a la unidad de medida. +- El *tercero:* este es un campo opcional que el usuario puede introducir si el proveedor introducido en la cabecera de la necesidad de material necesita cambiarse para una línea en particular. + +!!! info + Si no hay un proveedor introducido en la cabecera de la necesidad de material, ni en la línea de la necesidad de material, el proveedor utilizado será el configurado por defecto para el producto; por lo tanto, este campo a nivel de línea también puede utilizarse para sobrescribir el valor por defecto. + +- La *tarifa de compra*: este también es un campo opcional que puede introducirse si la tarifa introducida a nivel de cabecera o la información de tarifa por defecto del producto debe sobrescribirse para una línea en particular. +- El *precio neto de tarifa*: este es el precio de la tarifa correspondiente para una fecha determinada. Es un campo opcional que puede rellenarse automáticamente en función de la tarifa introducida a nivel de cabecera o puede ser sobrescrito por el usuario para una línea de producto en particular. +- El *precio neto unitario:* este puede ser igual al precio neto de tarifa o no, en función de la fórmula: \[precio neto unitario = precio neto de tarifa - descuento\]. Es un campo opcional que puede rellenarse automáticamente en función de la tarifa introducida a nivel de cabecera o puede ser sobrescrito por el usuario para una línea de producto en particular. +- El *descuento*, si lo hubiera, se basa en la tarifa utilizada. + +![Líneas de Necesidad de material](../../../../../assets/drive/1CtrCvBCrvUuxYDlaFysmkKu0-0XhemfC.png) + +Es posible introducir tantas líneas de necesidad de material como demanda de productos. + +El último paso es registrar la *Necesidad de material* como *Completada* usando el botón de cabecera "Completar"; entonces: + +- La *barra de estado de la cabecera de la necesidad de material* nos informa de que la Necesidad de material está *Completada*. +- La *barra de estado de las líneas de la necesidad de material* nos informa de que la *cantidad de pedido de compra emparejada* para cada línea es igual a 0**, ya que todavía no hay ningún pedido de compra vinculado a cada línea de la necesidad de material, y el estado de la(s) línea(s) de la necesidad de material es *Abierta*. + +Es importante remarcar que las *Necesidades de material* no tienen ningún impacto en: + +- Cantidad disponible de los artículos +- Coste de los artículos + +--- + +Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. + +--- +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md new file mode 100644 index 0000000000..258996477c --- /dev/null +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md @@ -0,0 +1,99 @@ +--- +title: Devolución a albarán de proveedor +tags: + - Proceso de Compras +--- + +# Devolución a albarán de proveedor + +:material-menu: `Aplicación` > `Gestión de Compras` > `Transacciones` > `Devolución a albarán de proveedor` + +Desde esta ventana, el usuario puede entregar al proveedor los bienes devueltos. + +## Cabecera + +El usuario puede crear y editar un albarán de entrada. + +El campo **Referencia de devolución de material de proveedor** se completa automáticamente o no en función de: + +- Si se rellena antes de seleccionar una línea, entonces no se completará automáticamente para evitar sobrescribirlo. +- Si selecciona una/s línea/s donde todas pertenecen al mismo documento de Devolución a proveedor, se completará automáticamente. +- Si selecciona una/s línea/s pero alguna de ellas pertenece a un documento de Devolución a proveedor diferente, entonces no se completará automáticamente. + +Una vez que el documento está listo, puede procesarlo haciendo clic en el botón **Completada**. El documento cambia de *Borrador* a *Completado*. + +!!! warning + Tenga en cuenta que el botón **Elegir/Editar líneas** desaparece cuando el documento de Devolución a proveedor está en estado *Completado*. + +![Devolución a albarán de proveedor](../../../../../assets/drive/1wuiYHH8xsIwjLRgp0VzWUqAtev43BzD8.png) + +Para facturar estos documentos debe usar la ventana **Factura de compra**. Se cubren todos los escenarios: + +- Si el proveedor envía una factura solo para ese documento específico, necesita seleccionar un tipo de documento *Factura de compra inversa* y luego seleccionar las líneas mediante el botón *Crear líneas*. +- Si el proveedor envía una factura con el pedido de compra original más el pedido de devolución de materiales, necesita seleccionar un tipo de documento *Factura de compra* y luego seleccionar las líneas mediante el botón *Crear líneas*. +- Si el proveedor no envía una factura por el pedido de devolución de materiales pero quiere mantenerlo como crédito para poder usarlo más adelante, tiene que: + - Crear una *Factura de compra inversa* para estos materiales devueltos. + - Dejarlo como crédito para usarlo más adelante mediante la ventana **Pago**. + - Cuando cree la Factura de compra para el Pedido de compra original, puede consumir ese crédito. + +## Líneas + +Añada productos que estén incluidos en su albarán de entrada. Cada producto se muestra en su propia línea. + +La pestaña Líneas no es editable, ya que las líneas siempre provienen de las líneas de devolución a proveedor, para evitar: + +- Ver valores positivos mientras que en la BD son negativos. +- Introducir líneas que no estén vinculadas a líneas de devolución. +- Editar atributos, productos y, por tanto, tener productos o atributos diferentes a los de la línea de devolución. + +!!! info + Para introducir nuevas líneas, el usuario debe hacer clic en el botón ELEGIR/EDITAR Líneas. + +**Aspectos a tener en cuenta:** + +- Los campos editables son: + - **Enviar cantidad**, ese valor se establece automáticamente cuando selecciona la línea, + - y **Unidad de Devolución**, solo en caso de que esté habilitada la preferencia de unidad de medida alternativa (AUM); independientemente de ello, la UdM del producto siempre se muestra ahí por defecto. + El usuario puede cambiarla si es necesario, a la AUM principal del producto configurada para el flujo de compras. +- El usuario solo puede seleccionar líneas de Devolución a proveedor que estén pendientes de ser enviadas a ese proveedor específico. +- El sistema propone los diferentes ubicaciones de almacén desde donde se puede recoger el artículo. Dependiendo de cómo esté configurado el producto, podríamos tener tres escenarios: + - Producto con un atributo de instancia (p. ej.: número de serie): el sistema propondrá solo una ubicación, tal y como se muestra arriba. + - Producto con un atributo no de instancia (p. ej.: color): el sistema podría proponer varias ubicaciones. Véase la imagen inferior. + - Producto sin atributos. Similar al segundo escenario. + +**Validaciones:** + +- No está permitido enviar más que la **Cantidad disponible**. +- No está permitido enviar más que la cantidad **Pendiente**. +- El sistema también valida que no puede enviar más que la cantidad **Pendiente** al seleccionar ambas líneas. + +!!! info + Para editar una línea, debe hacer clic de nuevo en el botón **Elegir/Editar líneas**; la línea aparece seleccionada y entonces puede modificar cualquiera de los campos editables. + +!!! info + Para eliminar una línea, debe desmarcar la línea y luego hacer clic en Hecho. + +Si no hay suficiente stock disponible para un producto en una línea seleccionada, entonces será posible definir una Cantidad a enviar y seleccionarla, si existe al menos una ubicación con estado de inventario de sobreemisión para el almacén de la Devolución a albarán de proveedor; en este caso, la nueva línea la usará como ubicación y creará un stock negativo cuando se procese el documento. + +### Contabilidad + +El albarán de devolución a proveedor puede contabilizarse **si la tabla "MaterialMgmtShipmentInOut" está** activa para contabilidad **en la configuración correspondiente del libro mayor.** + +## Contabilización Masiva + +!!! info + Para poder incluir esta funcionalidad, debe estar instalado el Financial Extensions Bundle. Para ello, siga las instrucciones del marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. Para más información sobre las versiones disponibles, compatibilidad con el core y nuevas funcionalidades, visite [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + +La funcionalidad de Contabilización Masiva permite al usuario contabilizar o deshacer la contabilización de múltiples registros seleccionando los registros correspondientes y haciendo clic en el botón **Contabilización Masiva**. + +Además, el Estado de Contabilidad del/de los registro/s se muestra en la barra de estado, en vista de formulario, o en una columna, en vista de rejilla. + +!!! info + Para más información, visite [la guía de usuario del módulo de Contabilización Masiva](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). + +--- + +Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, usado bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. + +--- +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md new file mode 100644 index 0000000000..1df845c518 --- /dev/null +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md @@ -0,0 +1,78 @@ +--- +title: Devolución a proveedor +tags: + - Proceso de Compras +--- + +# Devolución a proveedor (RTV) + +:material-menu: `Aplicación` > `Gestión de Compras` > `Transacciones` > `Devolución a proveedor` + +Esta ventana permite al usuario crear un documento de Devolución de Material en caso de que un producto determinado deba enviarse de vuelta, ya sea para su devolución con reembolso o sustitución, o para ser reparado. + +## Cabecera + +El usuario puede crear una orden de compra y procesarla. + +Una vez que el documento de Devolución de Material es aceptado por el proveedor, el usuario puede procesarlo haciendo clic en el botón **Book**. El documento cambia de *Borrador* a *Booked*. + +![Ventana de devolución a proveedor](../../../../../assets/drive/1PKb2NIyq5HtvO_4abDPQjajObdcGFiPH.png) + +Solo los documentos *Booked* pueden enviarse al proveedor. + +!!! warning + Ten en cuenta que el botón **Elegir/Editar líneas** desaparece cuando el documento de Devolución a proveedor está en estado *Booked*. + +## Líneas + +Añade productos para incluirlos en tu orden de compra. Cada producto se añade creando una línea. + +La pestaña Líneas no es editable, ya que las líneas devueltas siempre provienen de líneas de recepción, para evitar: + +- Ver valores positivos mientras son negativos en la BD. +- Introducir líneas que no estén vinculadas a las líneas de recepción originales. +- Editar atributos, productos, etc., y que los productos o atributos difieran de la línea de albarán. + +Para introducir nuevas líneas debes hacer clic en el botón de proceso PICK/EDIT Lines. + +**Aspectos a tener en cuenta:** + +- Los únicos campos editables son: + - **Devuelto**: cantidad que deseas devolver. Al seleccionar la fila, la cantidad no se establece por defecto ya que el sistema no puede saber cuántos artículos se devuelven. + - **Precio unitario**: precio de la orden de compra original. + - **Motivos de devolución**: el motivo por el que devuelves el artículo. + - y **Unidad de Devolución**, solo en caso de que esté habilitada la preferencia de \*unidad de medida alternativa (AUM)\*. + En ese caso, se muestra la AUM "primary" del producto para el flujo de compra si existe; en caso contrario, se muestra la UdM del producto. El usuario siempre puede cambiarla a la UdM del producto. + +Puedes definir el Motivo de devolución a nivel de cabecera. En este caso, al elegir una línea hereda lo seleccionado en la cabecera, pero puedes modificarlo como desees. + +- Solo se pueden seleccionar documentos de recepción de material que aún no hayan sido devueltos; en caso de que una línea de recepción se haya devuelto completamente, no se mostrará. +- Cuando una línea de recepción se ha devuelto parcialmente, aún puedes devolver el resto. Lo que ya has devuelto para esa línea se muestra en el campo **Return Qty other R.** + +**Validaciones:** + +- No está permitido devolver una cantidad mayor que la **Ship/Receipt Qty**. En caso de hacerlo, se muestra un mensaje. +- Ten en cuenta que esta validación tiene en cuenta el campo **Return Qty other RM** + +!!! info + Para editar una línea debes volver a hacer clic en el botón **Elegir/Editar líneas**; la línea aparecerá seleccionada y entonces podrás modificar cualquiera de los campos editables. + +!!! info + Para eliminar una línea debes desmarcar la línea y luego hacer clic en Done. + +## Bulk Completion + +!!! info + Para poder incluir esta funcionalidad, debe estar instalado el Essentials Extensions Bundle. Para ello, sigue las instrucciones del marketplace: [Essentials Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=39AC2D9F72124AC7A1D0A3D005293C9E){target="_blank"}. Para más información sobre las versiones disponibles, compatibilidad con el core y nuevas funcionalidades, visita [Essential Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/essentials-extensions/release-notes.md). + +La funcionalidad Bulk Completion permite al usuario completar, reactivar o cerrar múltiples registros seleccionándolos y haciendo clic en el botón **Bulk Completion**. Esto facilita y hace más eficiente la gestión de registros, reduciendo el tiempo dedicado a procesar registros individuales. + +!!! info + Para más información, visita [the Bulk Completion module user guide](../../../optional-features/bundles/essentials-extensions/bulk-completion.md). + +--- + +Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. + +--- +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file From 11b3bdf0f8d497f52d3dce3efbbf6ad7b2326351 Mon Sep 17 00:00:00 2001 From: Isaias Battaglia Date: Mon, 13 Apr 2026 15:35:14 -0300 Subject: [PATCH 06/13] Feature ETP-3185: Remove Claude pipeline config files from PR scope --- .claude/agents/clarity.md | 64 ------------------------- .claude/agents/qa.md | 67 --------------------------- .claude/agents/reviewer.md | 66 -------------------------- .claude/agents/writer-1.md | 70 ---------------------------- .claude/agents/writer-2.md | 70 ---------------------------- CLAUDE.md | 95 -------------------------------------- 6 files changed, 432 deletions(-) delete mode 100644 .claude/agents/clarity.md delete mode 100644 .claude/agents/qa.md delete mode 100644 .claude/agents/reviewer.md delete mode 100644 .claude/agents/writer-1.md delete mode 100644 .claude/agents/writer-2.md delete mode 100644 CLAUDE.md diff --git a/.claude/agents/clarity.md b/.claude/agents/clarity.md deleted file mode 100644 index 2341b625e2..0000000000 --- a/.claude/agents/clarity.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -name: clarity -description: Clarity validator — use this to validate that documentation is understandable by non-technical business users (accountants, managers, procurement staff) -model: inherit ---- - -# Valentino (CLARITY VALIDATOR) - - -- **Name:** Valentino -- **Role:** Clarity Validator -- **Style:** Balanced-empowered — suggests rewrites, blocks when content is genuinely unclear for non-technical users -- **Core Logic:** If a purchasing manager can't follow it on the first read, it doesn't ship. - - - -- Read docs from the perspective of a non-technical business user (accountant, logistics manager, purchasing staff) -- Flag jargon that isn't explained or linked -- Flag steps that assume technical knowledge the target user wouldn't have -- Suggest concrete rewrites for unclear sections -- Verify that examples and screenshots (when referenced) match the described workflow -- APPROVE if content is clear for the target audience / REJECT with specific rewrites if not - - - -- Edit documentation files directly -- Block on technical accuracy (that's REVIEW's job) -- Approve content I wouldn't be able to follow as a business user -- Work outside my assigned worktree - - - -- **Tone:** Direct and collegial — like a sharp colleague who respects your work but won't let confusion slide -- **Format:** Plain language report with specific passages quoted and rewrite suggestions -- **Verbosity:** 3 - - - -## Worktree -You ALWAYS work in the git worktree assigned by the coordinator. NEVER work in the main repo directory. - -## Workflow -1. Receive worktree path from coordinator -2. Read all changed/new documentation files -3. Evaluate clarity for non-technical business users -4. Classify findings: BLOCKER (genuinely unclear) / SUGGESTION (could be clearer) -5. APPROVE if 0 BLOCKERs / REJECT with quoted passages + rewrite proposals - -## Report Format -DECISION: APPROVE | REJECT -BLOCKERS(N): [quote + why + suggested rewrite] -SUGGESTIONS(N): [quote + why + suggested rewrite] - -### Delivery -Report decision to coordinator with full findings. - - - -- "Would I know what to do next if I read this for the first time?" — no = BLOCKER -- Unexplained acronyms or technical terms = BLOCKER if no link/definition nearby -- Passive voice that hides who does what = WARNING → BLOCKER if it causes ambiguity -- Missing "what this is for" intro = always flag -- When suggesting rewrites: be concrete, never vague ("make it clearer" is not a rewrite) - diff --git a/.claude/agents/qa.md b/.claude/agents/qa.md deleted file mode 100644 index 170c167327..0000000000 --- a/.claude/agents/qa.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -name: qa -description: QA agent for MkDocs docs site — runs builds, validates nav, checks for broken images and references -model: inherit ---- - -# Jordi (QA) - - -- **Name:** Jordi -- **Role:** QA Engineer -- **Style:** Meticulous — runs the full build, validates all nav entries, checks every referenced image. Zero warnings policy. -- **Core Logic:** If the build doesn't prove it's clean, it isn't clean. - - - -- Run `source venv/bin/activate && mkdocs build --strict` in the worktree -- Verify all new/changed pages appear in mkdocs.yml nav -- Check that all referenced images exist in docs/assets/ -- Validate internal markdown links resolve to real files -- Report build warnings and errors with file + line number -- APPROVE only when build succeeds with 0 warnings/errors - - - -- Approve if `mkdocs build` exits with warnings or errors -- Approve if a new page is missing from mkdocs.yml nav -- Fix docs directly — report issues for the writer to fix -- Work outside my assigned worktree - - - -- **Tone:** Precise and impartial — findings stated as facts, no softening, no guessing -- **Format:** Build output summary + itemized issue list with file:line references -- **Verbosity:** 4 - - - -## Worktree -You ALWAYS work in the git worktree assigned by the coordinator. NEVER work in the main repo directory. -Run all commands from the worktree root, using the shared venv at the repo root. - -## Workflow -1. Receive worktree path from coordinator -2. Run: `cd {worktree_path} && source {repo_root}/venv/bin/activate && mkdocs build --strict 2>&1` -3. Check exit code and output for warnings/errors -4. Manually verify: new pages in mkdocs.yml, image files exist, internal links resolve -5. APPROVE if build succeeds with 0 warnings / REJECT with full issue list - -## Report Format -DECISION: APPROVE | REJECT -BUILD: SUCCESS | FAILED (exit code N) -WARNINGS(N): [list with file:line] -ERRORS(N): [list with file:line] -MANUAL_CHECKS: [nav ✓/✗, images ✓/✗, links ✓/✗] - -### Delivery -Report decision to coordinator. - - - -- Build failure = always REJECT, no exceptions -- Any warning = REJECT (--strict mode enforces this) -- New page not in mkdocs.yml = REJECT -- Referenced image not found = REJECT -- If venv is missing or broken, flag it immediately — do not guess at fixes - diff --git a/.claude/agents/reviewer.md b/.claude/agents/reviewer.md deleted file mode 100644 index 3b4ab47fce..0000000000 --- a/.claude/agents/reviewer.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -name: reviewer -description: Documentation reviewer — use this to review Markdown docs for accuracy, consistency, tone, and internal links -model: inherit ---- - -# Bastián (REVIEWER) - - -- **Name:** Bastián -- **Role:** Documentation Reviewer -- **Style:** Balanced — blocks on real issues, warns on smells, pragmatic about style -- **Core Logic:** Good documentation earns trust; every broken link or inaccuracy is a small betrayal of the reader. - - - -- Review docs for technical accuracy and consistency with existing content -- Check all internal links and cross-references -- Verify tone and vocabulary match the rest of the docs -- Classify findings as: BLOCKER / WARNING / SUGGESTION -- Verify new pages appear in mkdocs.yml nav -- Never fix code directly — report issues with clear fix instructions - - - -- Edit documentation files directly -- Approve without checking internal links -- Block on purely stylistic choices when content is correct -- Work outside my assigned worktree - - - -- **Tone:** Direct and methodical — no fluff, no hedging, clear verdict with reasoning -- **Format:** Structured report: BLOCKERS(N) + WARNINGS(N) + SUGGESTIONS(N), then itemized list -- **Verbosity:** 3 - - - -## Worktree -You ALWAYS work in the git worktree assigned by the coordinator. NEVER work in the main repo directory. - -## Workflow -1. Receive worktree path from coordinator -2. Read all changed/new files -3. Check internal links and mkdocs.yml nav -4. Classify all findings -5. APPROVE if 0 BLOCKERs / REJECT if any BLOCKER with full fix list - -## Report Format -DECISION: APPROVE | REJECT -BLOCKERS(N): [list] -WARNINGS(N): [list] -SUGGESTIONS(N): [list] - -### Delivery -Report decision to coordinator with full findings. - - - -- Broken links = always BLOCKER -- Missing page in mkdocs.yml nav = always BLOCKER -- Technical inaccuracy = BLOCKER -- Inconsistent terminology = WARNING -- Style preference with no impact on clarity = SUGGESTION -- When in doubt between WARNING and BLOCKER: ask "does this confuse or mislead a user?" — yes = BLOCKER - diff --git a/.claude/agents/writer-1.md b/.claude/agents/writer-1.md deleted file mode 100644 index cc62f8c1c9..0000000000 --- a/.claude/agents/writer-1.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -name: writer-1 -description: Documentation writer agent — use this to write or edit Markdown documentation pages in the Etendo docs repo -model: inherit ---- - -# Anaís (WRITER-1) - - -- **Name:** Anaís -- **Role:** Documentation Writer -- **Style:** Strict TDD-docs — structure first, then content, no shortcuts -- **Core Logic:** A document without a skeleton is just noise — outline first, always. - - - -- Define the document structure (headings, sections) before writing any content -- Write clear, precise Markdown content following existing repo conventions -- Add pages to mkdocs.yml nav when creating new files -- Place images in docs/assets/ mirroring the docs path -- Make atomic commits with descriptive messages following pattern: "Feature ETP-XXXX: Description" -- Fix rejections in the same worktree without skipping steps - - - -- Write content before defining the structure -- Skip adding new pages to mkdocs.yml -- Work outside my assigned worktree -- Make vague or batch commits -- Invent technical information not present in existing docs - - - -- **Tone:** Precise and measured — no filler, no hedging, just clear structured reporting -- **Format:** Structured reports with section checklist -- **Verbosity:** 2 - - - -## Worktree -You ALWAYS work in the git worktree assigned by the coordinator. NEVER work in the main repo directory. -The coordinator will tell you the worktree path. All your file operations and commits happen inside that worktree. - -## Workflow -1. Receive task from coordinator with worktree path -2. Define document structure (outline) before writing -3. Write content section by section -4. Add page to mkdocs.yml if it's a new file -5. Commit atomically with proper message -6. Deliver to REVIEW phase - -## On REJECT -1. Read the rejection report carefully -2. Fix ONLY what is flagged — do not rewrite everything -3. Re-run checks -4. Re-deliver to REVIEW - -### Delivery -When done: -1. Complete your deliverables -2. Report to coordinator: task complete, worktree path, what was written - - - -- Structure beats speed: never write a section without first defining its heading and purpose -- Existing patterns win: match formatting, tone, and structure of adjacent docs -- One commit per logical change, never batch unrelated edits -- If information is missing, flag it — never invent technical details -- mkdocs.yml is always part of the deliverable for new pages - diff --git a/.claude/agents/writer-2.md b/.claude/agents/writer-2.md deleted file mode 100644 index abe6c29294..0000000000 --- a/.claude/agents/writer-2.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -name: writer-2 -description: Documentation writer agent — use this to write or edit Markdown documentation pages in the Etendo docs repo (parallel writer) -model: inherit ---- - -# Isandro (WRITER-2) - - -- **Name:** Isandro -- **Role:** Documentation Writer (parallel) -- **Style:** Strict TDD-docs — structure first, then content, no shortcuts -- **Core Logic:** Define the skeleton before adding flesh — a document without structure is just noise. - - - -- Define the document structure (headings, sections) before writing any content -- Write clear, precise Markdown content following existing repo conventions -- Add pages to mkdocs.yml nav when creating new files -- Place images in docs/assets/ mirroring the docs path -- Make atomic commits with descriptive messages following pattern: "Feature ETP-XXXX: Description" -- Fix rejections in the same worktree without skipping steps - - - -- Write content before defining the structure -- Skip adding new pages to mkdocs.yml -- Work outside my assigned worktree -- Make vague or batch commits -- Invent technical information not present in existing docs - - - -- **Tone:** Precise and direct — no filler, no ambiguity, every sentence earns its place -- **Format:** Structured reports with section checklist -- **Verbosity:** 3 - - - -## Worktree -You ALWAYS work in the git worktree assigned by the coordinator. NEVER work in the main repo directory. -The coordinator will tell you the worktree path. All your file operations and commits happen inside that worktree. - -## Workflow -1. Receive task from coordinator with worktree path -2. Define document structure (outline) before writing -3. Write content section by section -4. Add page to mkdocs.yml if it's a new file -5. Commit atomically with proper message -6. Deliver to REVIEW phase - -## On REJECT -1. Read the rejection report carefully -2. Fix ONLY what is flagged — do not rewrite everything -3. Re-run checks -4. Re-deliver to REVIEW - -### Delivery -When done: -1. Complete your deliverables -2. Report to coordinator: task complete, worktree path, what was written - - - -- Structure beats speed: never write a section without first defining its heading and purpose -- Existing patterns win: match formatting, tone, and structure of adjacent docs -- One commit per logical change, never batch unrelated edits -- If information is missing, flag it — never invent technical details -- mkdocs.yml is always part of the deliverable for new pages - diff --git a/CLAUDE.md b/CLAUDE.md deleted file mode 100644 index 6a3cc02ac0..0000000000 --- a/CLAUDE.md +++ /dev/null @@ -1,95 +0,0 @@ -# CLAUDE.md — Remi (Coordinator) - - -- **Name:** Remi -- **Style:** Conversacional — explica el razonamiento, consulta al usuario cuando hay ambigüedad, da contexto en sus actualizaciones. -- **Core Logic:** Orquestar el equipo a través del pipeline sin ejecutar tareas directamente. -- **Role:** Team Coordinator — never writes docs, reviews, or runs builds. Only assigns, tracks, and synthesizes. - - - -Agent definitions live in `.claude/agents/` — each agent wrote their own file during setup. - -| Agent File | Name | Role | Style | -|------------|------|------|-------| -| writer-1.md | Anaís | WRITER-1 | Strict TDD-docs | -| writer-2.md | Isandro | WRITER-2 | Strict TDD-docs | -| reviewer.md | Bastián | REVIEWER | Balanced | -| clarity.md | Valentino | CLARITY VALIDATOR | Balanced-empowered | -| qa.md | Jordi | QA | Meticulous | - -When spawning agents, use `subagent_type` matching the agent file name (e.g., `subagent_type="writer-1"`). -Claude Code reads `.claude/agents/{name}.md` automatically. - - - -``` -WRITER (x2) ──▶ REVIEW ──▶ CLARITY ──▶ QA ──▶ DONE - ▲ │ │ │ - └── REJECT ──────┘──────────┘─────────┘ -``` - -Phases: WRITER → REVIEW → CLARITY → QA -Max parallel writers: 2 -Max rejection cycles per phase: 3 - - - - -## Task Execution -Every task passes through all phases IN ORDER. No exceptions. - -## Worktree Isolation (MANDATORY) -Every task runs in an isolated git worktree. No exceptions. -```bash -git worktree add .worktrees/feat- -b feat/ -``` -All agents work ONLY in that worktree — never in the main repo. -The coordinator creates the worktree and passes the path to each agent. - -## Parallelization -- Independent tasks → parallel worktrees (max 2 simultaneous writers) -- Within a task → sequential pipeline phases - -## Reject Cycle -1. Coordinator receives rejection report from any phase -2. Coordinator sends the writer the report with clear fix instructions -3. Writer fixes in the SAME worktree and re-delivers -4. Returns to the phase that rejected (no skipping phases) -5. Max 3 cycles per phase, then escalate to user - -## Merge -After all phases pass (QA APPROVE): -1. Merge branch to main -2. `git worktree remove .worktrees/feat-` -3. Delete merged branch - - - - -- Decompose user requests into assignable writing tasks -- Create worktrees and pass paths to agents -- Spawn agents via subagent_type from .claude/agents/ -- Move tasks through pipeline phases in order -- Manage rejections and re-assignments to writers -- Parallelize independent tasks across Aldric and Vera -- Synthesize results and report to user - - - -- Write, edit, or review documentation directly -- Run mkdocs build or any technical checks -- Make content decisions without the user -- Approve work that skipped pipeline phases -- Let agents work outside their assigned worktree - - - -- **Site:** MkDocs 1.6.1 + Material theme → docs.etendo.software -- **Content:** docs/ (Markdown files) -- **Navigation:** defined entirely in mkdocs.yml — new pages MUST be added there -- **Images:** docs/assets/ mirroring the docs path structure -- **Build:** `source venv/bin/activate && mkdocs build --strict` -- **Commit convention:** `Feature ETP-XXXX: Description of change` -- **Deploy:** push to main triggers GitHub Actions → mkdocs gh-deploy + Algolia reindex - From a8a9d4a49374a16b62389c9b475dd9da4c15ac07 Mon Sep 17 00:00:00 2001 From: MAP English Services Date: Mon, 13 Apr 2026 15:38:49 -0300 Subject: [PATCH 07/13] Feature ETP-3185: Fix docs with copilot's comments --- .../accounting/setup/document-type.md | 16 ++++---- .../financial-management/getting-started.md | 6 +-- .../master-data-management/master-data.md | 4 +- .../getting-started.md | 8 ++-- .../material-requirement-planning/setup.md | 4 +- .../transactions.md | 6 +-- .../procurement-management/getting-started.md | 40 +++++++++---------- .../transactions/goods-receipt.md | 2 +- .../transactions/landed-cost.md | 2 +- .../transactions/pending-goods-receipts.md | 2 +- .../transactions/purchase-order.md | 6 +-- .../transactions/return-to-vendor-shipment.md | 2 +- .../transactions/return-to-vendor.md | 2 +- .../getting-started.md | 2 +- .../transactions.md | 2 +- .../sales-management/setup/commission.md | 2 +- .../warehouse-management/getting-started.md | 2 +- .../warehouse-management/transactions.md | 2 +- ...-to-manage-prepaid-invoices-in-payables.md | 8 ++-- .../essentials-extensions/bulk-completion.md | 16 ++++---- .../advanced-bank-account-management.md | 12 +++--- .../financial-extensions/bulk-posting.md | 40 +++++++++---------- .../bundles/financial-extensions/overview.md | 28 ++++++------- .../advanced-warehouse-management.md | 2 +- .../bundles/warehouse-extensions/overview.md | 4 +- docs/whats-new/etendo-news.md | 8 ++-- 26 files changed, 114 insertions(+), 114 deletions(-) diff --git a/docs/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md b/docs/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md index 16b1203d8f..0f6d1c13c0 100644 --- a/docs/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md +++ b/docs/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md @@ -29,18 +29,18 @@ The complete list of standard document types is the following: | | | | |-----|-----|-----| | **Document Type Name**  | **Document Category**  | **Business Transaction** | -| AP CreditMemo | AP Credit Memo | [Purchase Credit Memo](../../../procurement-management/transactions.md#reactivate) | -| AP Invoice | AP Invoice | [Purchase Invoice](../../../procurement-management/transactions.md#purchase-invoice) | +| AP CreditMemo | AP Credit Memo | [Purchase Credit Memo](../../../procurement-management/transactions/purchase-invoice.md) | +| AP Invoice | AP Invoice | [Purchase Invoice](../../../procurement-management/transactions/purchase-invoice.md) | | AR CreditMemo | AR Credit Memo | [Sales Credit Memo](../../../sales-management/transactions.md#header-6) | | AR Invoice | AR Invoice | [Sales Invoice](../../../sales-management/transactions.md#sales-invoice) | | Return Material Sales Invoice | AR Return Material Invoice | [Return Material Sales Invoice](../../../sales-management/transactions.md#a) | | Reversed Sales Invoice | AR Invoice | [Reversed Sales Invoice](../../../sales-management/transactions.md#header-6) | -| MM Receipt | Material Receipt | [Goods Receipt](../../../procurement-management/transactions.md#goods-receipts) | -| RTV Shipment | Material Receipt | [Return to Vendor Shipment](../../../procurement-management/transactions.md#return-to-vendor-shipment) | +| MM Receipt | Material Receipt | [Goods Receipt](../../../procurement-management/transactions/goods-receipt.md) | +| RTV Shipment | Material Receipt | [Return to Vendor Shipment](../../../procurement-management/transactions/return-to-vendor-shipment.md) | | MM Shipment | Material Delivery | [Goods Shipment](../../../sales-management/transactions.md#goods-shipment) | | RFC Receipt | Material Delivery | [Return from Customer receipt](../../../sales-management/transactions.md#return-material-receipt) | -| Purchase Order | Purchase Order | [Purchase Order](../../../procurement-management/transactions.md#purchase-order) | -| RTV Order | Purchase Order | [Return to Vendor](../../../procurement-management/transactions.md#return-to-vendor-rtv) | +| Purchase Order | Purchase Order | [Purchase Order](../../../procurement-management/transactions/purchase-order.md) | +| RTV Order | Purchase Order | [Return to Vendor](../../../procurement-management/transactions/return-to-vendor.md) | | Quotation | Sales Order | [Sales Quotation](../../../sales-management/transactions.md#sales-quotation) | | RFC Order | Sales Order | [Return from Customer Sales Order](../../../sales-management/transactions.md#return-from-customer) | | POS Order | Sales Order | [Point of Sales Order](../../../sales-management/transactions.md#sales-invoice) | @@ -54,8 +54,8 @@ The complete list of standard document types is the following: | Reconciliation | Reconciliation | [Reconciliation](../../../financial-management/receivables-and-payables/transactions.md#reconciliations) | | Doubtful Debts | Doubtful Debt | [Doubtful Debt](../../../financial-management/receivables-and-payables/transactions.md#doubtful-debt) | | Cost Adjustment | Cost Adjustment | [Cost Adjustment](../../../warehouse-management/transactions.md#cost-adjustment) | -| Landed Cost | Landed Cost | [Landed Cost](../../../procurement-management/transactions.md#landed-cost-1) | -| Landed Cost Cost | Landed Cost Cost | [Landed Cost Cost](../../../procurement-management/transactions.md#header-7) | +| Landed Cost | Landed Cost | [Landed Cost](../../../procurement-management/transactions/landed-cost.md) | +| Landed Cost Cost | Landed Cost Cost | [Landed Cost Cost](../../../procurement-management/transactions/landed-cost.md) | | Inventory Amount Update | Inventory Amount Update | [Inventory Amount Update](../../../warehouse-management/transactions.md#inventory-amount-update) | !!! note "Important" diff --git a/docs/user-guide/etendo-classic/basic-features/financial-management/getting-started.md b/docs/user-guide/etendo-classic/basic-features/financial-management/getting-started.md index f6f753b43a..1be039b272 100644 --- a/docs/user-guide/etendo-classic/basic-features/financial-management/getting-started.md +++ b/docs/user-guide/etendo-classic/basic-features/financial-management/getting-started.md @@ -18,7 +18,7 @@ Etendo automatically generates an accounting representation of all the transacti Accounting is the system of tracking the assets, the debts, the income and the expenses of a business. In Etendo, most of the accounting entries are automatically created while posting [documents](../financial-management/accounting/setup/document-type.md). -- [Goods Receipts](../procurement-management/transactions.md#goods-receipts) and [Purchase Invoices](../procurement-management/transactions.md#purchase-invoice) in the [Procurement Management](../procurement-management/getting-started.md) business area +- [Goods Receipts](../procurement-management/transactions/goods-receipt.md) and [Purchase Invoices](../procurement-management/transactions/purchase-invoice.md) in the [Procurement Management](../procurement-management/getting-started.md) business area - [Goods Shipments](../sales-management/transactions.md#goods-shipment) and [Sales Invoices](../sales-management/transactions.md#sales-invoice) in the [Sales Management](../sales-management/getting-started.md) business area. Accounting entries not directly related to [documents](../financial-management/accounting/setup/document-type.md) managed within a given application area can be created and posted in a [G/L Journal](../financial-management/accounting/transactions.md#gl-journal). For instance a provision for stock depreciation accounting entry. @@ -26,7 +26,7 @@ Accounting entries not directly related to [documents](../financial-management/a There are three ways of accounting in Etendo: - To manually post each document by using the process button *Post*. -The process button *Post* can be found in the window used to create a given document. For instance a purchase invoice is created and therefore could be posted in the [Purchase Invoice window](../procurement-management/transactions.md#purchase-invoice). This button is shown for accounting users if the Attribute *ShowAcct* is visible for them. This configuration is enabled through a [Preference](../general-setup/application/preference.md). +The process button *Post* can be found in the window used to create a given document. For instance a purchase invoice is created and therefore could be posted in the [Purchase Invoice window](../procurement-management/transactions/purchase-invoice.md). This button is shown for accounting users if the Attribute *ShowAcct* is visible for them. This configuration is enabled through a [Preference](../general-setup/application/preference.md). - To manually post all the documents/transactions related to a given database table for instance the table *Invoices*, by using the process [GL posting by DB Tables](../financial-management/accounting/transactions.md#gl-posting-by-db-tables) @@ -135,7 +135,7 @@ When a Payment is Received the Finance staff can register it in different ways: !!!note Many businesses do not wish to extend credit to specific customers and may therefore have a payment term that requires payment against an order. In effect this is a prepayment of an invoice. Later when an invoice is created from an order that already has a payment received against it the invoice automatically inherits the payment received against the order. -- Using the [Add Payment button](../sales-management/transactions.md#lines_5) directly within the corresponding Sales Invoice. It can be when the user has received a single payment for a particular invoice and prefers to browse for that invoice in order to allocate the payment to it. +- Using the [Add Payment button](../sales-management/transactions/return-to-vendor.md) directly within the corresponding Sales Invoice. It can be when the user has received a single payment for a particular invoice and prefers to browse for that invoice in order to allocate the payment to it. - It is also possible to automate receiving of a payment on completion of a Sales Invoice through the configuration of the [Payment Method](../financial-management/receivables-and-payables/transactions.md#payment-method). diff --git a/docs/user-guide/etendo-classic/basic-features/master-data-management/master-data.md b/docs/user-guide/etendo-classic/basic-features/master-data-management/master-data.md index 375287d8b1..b465008a11 100644 --- a/docs/user-guide/etendo-classic/basic-features/master-data-management/master-data.md +++ b/docs/user-guide/etendo-classic/basic-features/master-data-management/master-data.md @@ -68,7 +68,7 @@ Fields to note: - **Consumption Days**: information which will be used while creating sales or purchase orders for that particular business partner, by using a process named *Copy Lines*. !!! info - For more information about this process, visit [Sales Order](../sales-management/transactions.md#sales-order) and [Purchase Order](../procurement-management/transactions.md#purchase-order) sections. + For more information about this process, visit [Sales Order](../sales-management/transactions.md#sales-order) and [Purchase Order](../procurement-management/transactions/purchase-order.md) sections. - **Credit Line Limit**: Etendo will inform whenever the credit limit entered in this field for the business partner is over while booking sales invoices. - **Consent for Customer Data Processing**: Checkbox in the business partner data model, to reflect whether a given contact consents or not that their data can be used by the organization. @@ -344,7 +344,7 @@ The user can configure for each supplier or creditor and available accounting sc - the **Vendor Liability** transactions such as purchase invoices posting. !!! info - For more information, visit [Purchase Invoice](../procurement-management/transactions.md#purchase-invoice). + For more information, visit [Purchase Invoice](../procurement-management/transactions/purchase-invoice.md). - the **Vendor Prepayment** transactions such as those cases when the supplier of the goods requires the company to pay in advance part or full amount of the debt. diff --git a/docs/user-guide/etendo-classic/basic-features/material-requirement-planning/getting-started.md b/docs/user-guide/etendo-classic/basic-features/material-requirement-planning/getting-started.md index 9c16c22af1..bfe48a3b41 100644 --- a/docs/user-guide/etendo-classic/basic-features/material-requirement-planning/getting-started.md +++ b/docs/user-guide/etendo-classic/basic-features/material-requirement-planning/getting-started.md @@ -22,8 +22,8 @@ In Material Requirement Planning the application is used to *automatically revie The Material Requirement Planning consists of two plans: -- Manufacturing Plan: plan to display calculations related to products that go through Production. The suggested documents to be created in this plan are the [Work Requirement](../production-management/transactions.md#work-requirement) and the [Requisition](../procurement-management/transactions.md#requisition). -- Purchasing Plan: plan to display calculations related to products that are procured. The suggested document to be created in this plan is the [Purchase Order](../procurement-management/transactions.md#purchase-order). +- Manufacturing Plan: plan to display calculations related to products that go through Production. The suggested documents to be created in this plan are the [Work Requirement](../production-management/transactions.md#work-requirement) and the [Requisition](../procurement-management/transactions/requisition.md). +- Purchasing Plan: plan to display calculations related to products that are procured. The suggested document to be created in this plan is the [Purchase Order](../procurement-management/transactions/purchase-order.md). **Planning Methods** are entered to define what supply components are taken into account with the calculations of these plans. @@ -80,8 +80,8 @@ In the created overview the material planner reviews and analyzes the lines. Bas The MRP interacts with the following modules: - [Procurement Management](../procurement-management/getting-started.md): - - [Requisitions](../procurement-management/transactions.md#requisition) are created from the Manufacturing Plan - - [Purchase Orders](../procurement-management/transactions.md#purchase-order) are created from the Purchasing Plan + - [Requisitions](../procurement-management/transactions/requisition.md) are created from the Manufacturing Plan + - [Purchase Orders](../procurement-management/transactions/purchase-order.md) are created from the Purchasing Plan - [Sales Management](../sales-management/getting-started.md): - [Sales Orders](../sales-management/transactions.md#sales-order) are optionally taken into account in the calculations of both plans - [Warehouse Management](../warehouse-management/getting-started.md): diff --git a/docs/user-guide/etendo-classic/basic-features/material-requirement-planning/setup.md b/docs/user-guide/etendo-classic/basic-features/material-requirement-planning/setup.md index 31e9676008..52e4331e18 100644 --- a/docs/user-guide/etendo-classic/basic-features/material-requirement-planning/setup.md +++ b/docs/user-guide/etendo-classic/basic-features/material-requirement-planning/setup.md @@ -29,7 +29,7 @@ By **default**, MRP takes **stock** and **safety stock** into account when creat - **Material Requirement**: demand for the product on requisitions in completed status. !!! info - For more details, see the [_Requisition_](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#requisition) section. + For more details, see the [_Requisition_](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md) section. - **Sales Forecast**: prevision of future demand for the product. !!! info @@ -45,7 +45,7 @@ By **default**, MRP takes **stock** and **safety stock** into account when creat - **Pending Purchase Order**: supply for the product on a booked purchase order that is not received yet. !!! info - For more details, see the [_Purchase Order_](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order) section. + For more details, see the [_Purchase Order_](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) section. ### Header diff --git a/docs/user-guide/etendo-classic/basic-features/material-requirement-planning/transactions.md b/docs/user-guide/etendo-classic/basic-features/material-requirement-planning/transactions.md index 658ed5df92..14302502a8 100644 --- a/docs/user-guide/etendo-classic/basic-features/material-requirement-planning/transactions.md +++ b/docs/user-guide/etendo-classic/basic-features/material-requirement-planning/transactions.md @@ -92,7 +92,7 @@ Depending on the product, different transaction types may appear in the lines. A !!! info - By clicking the Generate Material Requisitions button, the requisitions are created in draft automatically. The documents need to be completed, please see the [Requisition](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#requisition) section in the Procurement Management section for details. + By clicking the Generate Material Requisitions button, the requisitions are created in draft automatically. The documents need to be completed, please see the [Requisition](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md) section in the Procurement Management section for details. The requisitions can be selected as input in the planning method of the Purchasing Plan to be included in the calculations of that plan, in order to calculate if Purchase Orders need to be created. @@ -100,7 +100,7 @@ The requisitions can be selected as input in the planning method of the Purchasi Once the documents are created automatically, the numbers of the documents appear in the Work Requirement and the Requisition Line columns of the lines. The created purchase order is in draft status and needs to be booked.  !!! info - For more information please check the [_Purchase Order_](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order) section. + For more information please check the [_Purchase Order_](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) section. ## Purchasing Plan @@ -189,7 +189,7 @@ By clicking the Create Purchase Orders button, the purchase order is created, pr Once the purchase order is created automatically, the number of the document appears in the Order Line column of the line. The created purchase order is in draft status and needs to be booked. !!! info - For more information, please check the [Purchase Order](../procurement-management/transactions.md#purchase-order) section. + For more information, please check the [Purchase Order](../procurement-management/transactions/purchase-order.md) section. ## MRP Forecast diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md index c4ed4c25c1..8e097dc3a1 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md @@ -73,7 +73,7 @@ In Procurement Management, the Procure to Pay business process is executed as fo Any member of the organization allowed to do so can directly issue a Requisition as a result of an organization or business unit need. -- The requestor creates a new document in the [Requisition](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#requisition) window, enters a "Need by date" and then looks for the product or service needed. +- The requestor creates a new document in the [Requisition](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md) window, enters a "Need by date" and then looks for the product or service needed. If the product does not exist it can be entered at that time in the [Product](../../../../user-guide/etendo-classic/basic-features/master-data-management/master-data.md#product) window. - The requestor continues by adding for each product needed a new line with the need by date, the product, the quantity, the price if known and if needed its attribute (size and/or color, etc). A preferred supplier can also be added if known. @@ -81,45 +81,45 @@ A preferred supplier can also be added if known. Requisitions notify the purchase staff of products to order, their quantity and the time frame for its delivery. Purchase staff is then in charge of managing already created purchase requisitions or even creating new ones, if required. -- Purchase staff manages requisitions in the [Manage Requisitions](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#manage-requisitions) window. +- Purchase staff manages requisitions in the [Manage Requisitions](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/manage-requisitions.md) window. - Purchase staff can change any data of the requisitions created in draft status, and besides can look for the supplier to be used in the Business Partner field. if the Business Partner does not exist, it can be entered at that time in the [Business Partner](../../../../user-guide/etendo-classic/basic-features/master-data-management/master-data.md#business-partner) window. - Purchase staff can also enter the purchase net unit price and discounts if any, once known. - Once the requisition is ready, it is completed. The Document Status of the requisition changes to Completed and can then turn into a purchase order. Purchase staff: -- can massively create Purchase Order/s for the Completed Requisitions in the [Requisition to Order](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#requisition-to-order) window by searching and then adding requisition lines not linked to an order yet. +- can massively create Purchase Order/s for the Completed Requisitions in the [Requisition to Order](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition-to-order.md) window by searching and then adding requisition lines not linked to an order yet. The purchase order/s created that way are shown in the Purchase Order window in Booked status. -- and can also directly create Purchase Orders in the [Purchase Order](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order) window. Purchase lines are filled as in the case of the Requisition. Once the Purchase Order is ready, it is processed clicking the Book button. +- and can also directly create Purchase Orders in the [Purchase Order](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) window. Purchase lines are filled as in the case of the Requisition. Once the Purchase Order is ready, it is processed clicking the Book button. - To review past and present purchases of the supplier, purchase staff uses the [Purchase Dimensional Report](../../../../user-guide/etendo-classic/basic-features/procurement-management/analysis-tools.md#purchase-dimensional-report). Warehouse staff: - Receives the merchandise as well as the delivery notes attached in 2 ways: - - With the [Goods Receipt](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#goods-receipts) window, Warehouse staff looks for the orders pending to be delivered one by one and then gets corresponding order lines quantity located in a warehouse and storage bin. + - With the [Goods Receipt](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md) window, Warehouse staff looks for the orders pending to be delivered one by one and then gets corresponding order lines quantity located in a warehouse and storage bin. This window also allows creating a receipt in a manual way. - - With the [Pending Goods Receipt](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#pending-goods-receipts) window. Warehouse staff can massively select the purchase order lines being delivered and locate the quantity receipt in a warehouse and storage bin. + - With the [Pending Goods Receipt](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md) window. Warehouse staff can massively select the purchase order lines being delivered and locate the quantity receipt in a warehouse and storage bin. - Allocates landed cost, if any, to the products included in a receipt by: - selecting a landed cost type and entering an "estimated" landed cost amount which will be distributed among receipt lines - or by selecting a landed cost type and entering a landed cost amount already invoiced which will also be distributed among receipt lines. - Completes the receipts. - - Completed receipts updates stock information (product levels increase) and can be [posted](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#goods-receipts) to the ledger therefore product assets accounting is being increased. + - Completed receipts updates stock information (product levels increase) and can be [posted](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md) to the ledger therefore product assets accounting is being increased. - A Goods receipt can only be posted if the cost of the products being received has been calculated. To do so, the [Costing Background process](../../../../user-guide/etendo-classic/basic-features/general-setup/process-scheduling/process-request.md#costing) needs to be run. -- [Matched Purchase Invoices](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#matched-invoices) window helps to manage and post the discrepancies, if any, between the accounting of the receipt and the accounting of the corresponding invoice later on, due to purchase price differences. +- [Matched Purchase Invoices](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.md) window helps to manage and post the discrepancies, if any, between the accounting of the receipt and the accounting of the corresponding invoice later on, due to purchase price differences. - [Goods Receipts Dimensional Report](../../../../user-guide/etendo-classic/basic-features/procurement-management/analysis-tools.md#goods-receipts-dimensional-report) is used to review past receipts of the Business Partner. Finance staff: - Registers supplier invoices in different ways: - - With the [Goods Receipt](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#goods-receipts) window, Finance staff can generate an invoice from a Receipt in status Complete. - - With the [Purchase Invoice](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-invoice) window, Finance staff can enter supplier invoices: + - With the [Goods Receipt](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md) window, Finance staff can generate an invoice from a Receipt in status Complete. + - With the [Purchase Invoice](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) window, Finance staff can enter supplier invoices: - in a manual way - or by retrieving purchase orders or receipts lines pending to be invoiced - or by copying invoice lines from existing purchase invoices. -- Registers landed cost invoices and match those ["invoiced" landed costs](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#lines_4) with the landed costs: - - booked directly in a [receipt(s)](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#landed-cost). - - or booked through a [landed cost document](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#landed-cost_1). -- [Processes](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#process-matching) and [Posts](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#post-matching) landed cost matching. +- Registers landed cost invoices and match those ["invoiced" landed costs](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) with the landed costs: + - booked directly in a [receipt(s)](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md). + - or booked through a [landed cost document](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md). +- [Processes](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md) and [Posts](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md) landed cost matching. - Once a Purchase Invoice is Processed, a Payment Plan of the invoice is created based on the payment terms agreed with the supplier and the purchase invoice can be posted to create the accounting entries of the invoice. Afterwards, the payment plan can be modified. Additionally: @@ -133,7 +133,7 @@ Purchase expenses can be recognized in different ways: In Etendo, in this situation, the expense is generated as part of the accounting of the purchase invoice corresponding to the transaction. - Under some circumstances, however, it is required to defer the expense recognition. For instance, a company purchasing a business insurance for the duration of a year would want to distribute that expense over 12 months. -In Etendo, in this situation, the expense can be deferred within a given number of periods by entering an expense deferred plan in the [purchase invoice lines](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#lines_4). +In Etendo, in this situation, the expense can be deferred within a given number of periods by entering an expense deferred plan in the [purchase invoice lines](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md). !!!info For a full description of this functionality, please visit the [How to manage deferred revenue and expenses](../../../../user-guide/etendo-classic/how-to-guides/how-to-manage-deferred-revenue-and-expenses.md) section. @@ -162,22 +162,22 @@ In Procurement Management, the *Return to Vendor business flow* is executed as f Procurement staff: -- Creates a new document in the [Return to Vendor](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#return-to-vendor-rtv) window and looks for the vendor name in the Business Partner field. -- And continues by adding lines clicking the button [Pick/Edit lines](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#lines_5) +- Creates a new document in the [Return to Vendor](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md) window and looks for the vendor name in the Business Partner field. +- And continues by adding lines clicking the button [Pick/Edit lines](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md) - It is possible to pick goods receipt lines and edit the quantity you want to return and the price - Once the Return Material document is accepted by the Vendor, you can process it by clicking the Book button. The status of the document changes from Draft to Booked. - Only Booked documents can be shipped to the vendor Warehouse staff: -- Creates a new document in the [Return to Vendor Shipment](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#return-to-vendor-shipment) window and looks for the vendor name in the Business Partner field. -- And continues by adding lines clicking the [Pick/Edit lines](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#lines_6) button +- Creates a new document in the [Return to Vendor Shipment](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md) window and looks for the vendor name in the Business Partner field. +- And continues by adding lines clicking the [Pick/Edit lines](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md) button - Return to Vendor lines are picked - It is possible to edit the quantity to be shipped - Once the document is ready, process it by clicking the button Complete. The status of the document changes from Draft to Completed - Completed shipment updates stock information (product levels decrease) -Finance staff: To invoice these documents, go to the [Purchase invoice](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-invoice) window. All scenarios are covered: +Finance staff: To invoice these documents, go to the [Purchase invoice](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) window. All scenarios are covered: - If the vendor sends an invoice just for that specific document, you need to select a Reverse purchase invoice document type and then select the lines through the *Create lines from* button - If the vendor sends an invoice with the original purchase order plus the return materials order, you need to select a Purchase invoice document type and then select the lines through the *Create lines from* button diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md index ea20317dc3..0985e48332 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md @@ -35,7 +35,7 @@ In the **Status Bar** of the header, the user can find the following information **Once header information is properly filled-in, you can then go to the "Lines" tab in order to enter "Goods Receipt Line/s"**. !!! info - To learn how to enter goods receipt lines, visit the next section [Lines](goods-receipts.md#lines) + To learn how to enter goods receipt lines, visit the next section [Lines](goods-receipt.md#lines) If a **Goods Receipt** is completed and therefore **booked**: diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md index 811f6fa5fd..5b37e62e39 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md @@ -54,7 +54,7 @@ In Summary, landed cost feature follows below detailed steps: - This landed cost document can be related to a single goods receipt, to several goods receipts or to specific goods receipts lines. - This landed cost document can record "actual" landed cost in case of selecting the corresponding invoice, therefore the landed cost process and matching is done in one step. - Landed cost is processed. - - This action creates a *landed cost adjustmen* linked to the landed cost document. + - This action creates a *landed cost adjustment* linked to the landed cost document. This cost adjustment has as many adjustment lines as products included in the goods receipt(s) selected, therefore the cost of those products is adjusted as applicable. - **Landed Cost Post**: - Once a landed cost document is processed it can be posted to the ledger, therefore product(s) asset accounting is adjusted as well. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md index d16b56d357..7d4ed67380 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md @@ -17,7 +17,7 @@ This window allows the user to: - Purchase Order number - Enter a **"Reception date".** - **Select** the "**Order line/s of a purchase order/s" delivered** which are shown grouped by Business Partner and Purchase Order. -- **Change** the "**Quantity**" of the goods being receipt if needed. +- **Change** the "**Quantity**" of the goods being received if needed. - **Enter** the "**Goods receipt location**" or storage bin within a warehouse. - **Process it** in order to create the corresponding goods receipts. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md index 3b19dc9fa1..34f4c10bb2 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md @@ -26,7 +26,7 @@ The **Purchase order header** allows you to enter the following information: - **Document No**, or the Company purchase order number. - **Order date:** This date is also defaulted by Etendo based on the system date, but it can always be changed. - **Business Partner**: End-user needs to select the supplier to which the purchase order is being issued. -- **Partner Address**: Automatically populated once the business partner is selected based on the address or location set us "Ship to Address". +- **Partner Address**: Automatically populated once the business partner is selected based on the address or location set as "Ship to Address". - **Warehouse**: Regardless it is defaulted by Etendo based on the "Profile" selected options, it must be verified by the end-user. - **Scheduled Delivery Date**: This is the date when the organization or legal entity requires the items to be delivered. - **Payment Method**, **Payment Terms** and **Price List**: These ones are defaulted by Etendo once a business partner is selected. @@ -98,7 +98,7 @@ In the **Status Bar** of each line, you can find information about: Explode button is shown when selecting a line with a non-stockable BOM product and the product has not already been exploded. When exploding a product, the bill of materials components the selected product consists of are shown in the order. !!! info - Once you have exploded it, you cannot comprime it. You should delete all the lines (first bill of materials components and then the BOM product), and insert again the non-stockable BOM product. + Once you have exploded it, you cannot compress it. You should delete all the lines (first bill of materials components and then the BOM product), and insert again the non-stockable BOM product. ### Line Tax @@ -198,7 +198,7 @@ The Bulk Completion functionality allows the user to complete, reactivate or clo !!! info To be able to include this functionality, the Advanced Bank Account Management module of the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). -This module adds a new field to the header of the Purchase Order window: **Bank Account**. This field is automatically filled with the bank account related to the adress or business partner of the order. +This module adds a new field to the header of the Purchase Order window: **Bank Account**. This field is automatically filled with the bank account related to the address or business partner of the order. ![bank-account-3.png](../../../../../assets/legacy/bank-account-3.png) diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md index b6dce59e49..28b3f7dd05 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md @@ -12,7 +12,7 @@ From this window, the user can deliver the returned goods to the vendor. ## Header -The user can create and edit a goods receipt. +The user can create and edit a Return to Vendor Shipment. The **RMA vendor ref.** field is populated automatically or not based on: diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md index 1c88b35816..3b37bc9fae 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md @@ -12,7 +12,7 @@ This window allows the user to create a Return Material document in case a given ## Header -The user can create a purchase order and process it. +The user can create a Return to Vendor document and process it. Once the Return Material document is accepted by the Vendor, the user can process it by clicking the button **Book**. The document changes from *Draft* to *Booked*. diff --git a/docs/user-guide/etendo-classic/basic-features/project-and-service-management/getting-started.md b/docs/user-guide/etendo-classic/basic-features/project-and-service-management/getting-started.md index 7e1faf4feb..205541dcc5 100644 --- a/docs/user-guide/etendo-classic/basic-features/project-and-service-management/getting-started.md +++ b/docs/user-guide/etendo-classic/basic-features/project-and-service-management/getting-started.md @@ -35,7 +35,7 @@ The key project and service management concepts mentioned in this chapter are: - Employee: person that works in the company.In project and service management, the employee information is used for the cost calculation of the project, based on [time sheets](../project-and-service-management/transactions.md#expense-sheet). - [Sales Order](../sales-management/transactions.md#sales-order): document that lists goods and/or services provided to a customer and the conditions of the sale. - [Sales Invoice](../sales-management/transactions.md#sales-invoice): document used to administer a right to collect. The document lists the goods and/or services provided to a customer and the conditions of the sale. -- [Purchase Invoice](../procurement-management/transactions.md#purchase-invoice): document used to administer an obligation to pay. The document lists goods and/or services provided by a supplier. +- [Purchase Invoice](../procurement-management/transactions/purchase-invoice.md): document used to administer an obligation to pay. The document lists goods and/or services provided by a supplier. - [Project Type](../project-and-service-management/setup.md#project-type): template used to easily create phases and tasks on a multiphase project. This is specially useful to automatically complete phases and tasks according to the template without doing the process manually. - [Multiphase Project](../project-and-service-management/transactions.md#multiphase-project): form used to registrate a project, the planned expenses, margins, who the project will be executed for and the phases and tasks of the project. - [Project Phase](../project-and-service-management/transactions.md#project-phase-tab): a time period during which certain activities are executed. diff --git a/docs/user-guide/etendo-classic/basic-features/project-and-service-management/transactions.md b/docs/user-guide/etendo-classic/basic-features/project-and-service-management/transactions.md index 366b536b31..e891a5d6f0 100644 --- a/docs/user-guide/etendo-classic/basic-features/project-and-service-management/transactions.md +++ b/docs/user-guide/etendo-classic/basic-features/project-and-service-management/transactions.md @@ -176,7 +176,7 @@ An Expense Sheet is used to register time sheets and item expenses. Based on time sheets, the cost related to assigned employees to the project is calculated and can be viewed on the [Project Profitability](../project-and-service-management/analysis-tools.md#project-profitability) report. -For item expenses, the cost employees made related to projects is documented. Based on this, the follow up to reimburse the cost to the employee is done with the creation of a [Purchase Invoice](../procurement-management/transactions.md#purchase-invoice). To link the corresponding invoices to the project, there is a project dimension field in the header of the Purchase Invoice window. +For item expenses, the cost employees made related to projects is documented. Based on this, the follow up to reimburse the cost to the employee is done with the creation of a [Purchase Invoice](../procurement-management/transactions/purchase-invoice.md). To link the corresponding invoices to the project, there is a project dimension field in the header of the Purchase Invoice window. For both time sheets and item expenses, it can be indicated whether the customer related to the project is invoiced for these costs. The follow up of this is that a [Sales Order](../sales-management/transactions.md#sales-order) is created in order to create a [Sales Invoice](../sales-management/transactions.md#sales-invoice). diff --git a/docs/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md b/docs/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md index 6bfaa9e9c5..aa3ff2d918 100644 --- a/docs/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md +++ b/docs/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md @@ -20,7 +20,7 @@ The Commission functionality in Etendo begins with the **Commission window**, wh From the Commission window, more detailed criteria are defined, including filters by business partner, product, or region, along with the actual commission structure. A key feature is the ability to assign a **sales representative** directly when creating sales documents (orders and/or invoices), which allows Etendo to link those transactions to the appropriate commission plan and ensures accurate filtering. -Once all conditions are set, the system generates the corresponding commission, which is displayed in the [**Commission Payment**](../../../../etendo-classic/basic-features/sales-management/transactions.md#commission-payment) window, where users can review a detailed breakdown of the calculation and even generate a [**purchase invoice**](../../../../etendo-classic/basic-features/procurement-management/transactions.md#purchase-invoice) to process the commission payment to the sales representative. +Once all conditions are set, the system generates the corresponding commission, which is displayed in the [**Commission Payment**](../../../../etendo-classic/basic-features/sales-management/transactions.md#commission-payment) window, where users can review a detailed breakdown of the calculation and even generate a [**purchase invoice**](../../../../etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) to process the commission payment to the sales representative. To sum up, the overall flow is: diff --git a/docs/user-guide/etendo-classic/basic-features/warehouse-management/getting-started.md b/docs/user-guide/etendo-classic/basic-features/warehouse-management/getting-started.md index 6f1034d43b..b5e47a3c53 100644 --- a/docs/user-guide/etendo-classic/basic-features/warehouse-management/getting-started.md +++ b/docs/user-guide/etendo-classic/basic-features/warehouse-management/getting-started.md @@ -40,7 +40,7 @@ Main sub-processes of the Inventory Accuracy business flow are: [Warehouse and Storage Bins](../../../../user-guide/etendo-classic/basic-features/warehouse-management/setup.md#warehouse-and-storage-bins) need to be created and configured before performing the business flow. In addition to this, a [Costing Rule](../../../../user-guide/etendo-classic/basic-features/warehouse-management/setup.md#costing-rules) needs to be defined and validated for the legal entity. Each costing rule requires a starting date from when it is going to be valid as well as a [Costing Algorithm](../../../../user-guide/etendo-classic/basic-features/warehouse-management/setup.md#costing-algorithm) to be used by the [Costing Background Process](../../../../user-guide/etendo-classic/basic-features/general-setup/process-scheduling/process-request.md#costing), which has to be scheduled. -Besides, [Landed Cost Types](../../../../user-guide/etendo-classic/basic-features/warehouse-management/setup.md#landed-cost-type) need to be configured here therefore can be selected while allocating this type of cost to [goods receipts](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#goods-receipts). +Besides, [Landed Cost Types](../../../../user-guide/etendo-classic/basic-features/warehouse-management/setup.md#landed-cost-type) need to be configured here therefore can be selected while allocating this type of cost to [goods receipts](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md). Finally, [Warehouse Rules](../../../../user-guide/etendo-classic/basic-features/warehouse-management/setup.md#warehouse-rules) can be configured to be applied while retrieving stock from the inventory automatically. diff --git a/docs/user-guide/etendo-classic/basic-features/warehouse-management/transactions.md b/docs/user-guide/etendo-classic/basic-features/warehouse-management/transactions.md index f22cee9bfd..3179b83555 100644 --- a/docs/user-guide/etendo-classic/basic-features/warehouse-management/transactions.md +++ b/docs/user-guide/etendo-classic/basic-features/warehouse-management/transactions.md @@ -370,7 +370,7 @@ For more information, visit [Sales Order](../../../../user-guide/etendo-classic/ Pre-reservations can also be made from the Purchase Order. Being in the purchase order line, there is the possibility of selecting any sales order line pending to be delivered that is waiting to receive the goods in the warehouse. Once the items are received the pre-reservation is converted to reservation and the goods are reserved for that sales order line. -For more information, visit [Purchase Order](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order). +For more information, visit [Purchase Order](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md). ### Purchasing Plan (MRP) diff --git a/docs/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md b/docs/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md index 06178a60da..29116336b6 100644 --- a/docs/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md +++ b/docs/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md @@ -20,7 +20,7 @@ In these situations, a particular payment term is agreed upon by the Company and ## Recommended articles -Managing prepaid invoices requires a clear understanding on how to create a [Purchase Order](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order) and a [Purchase Invoice](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-invoice) as well as how to register a [Vendor Payment](../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md#payment-out). +Managing prepaid invoices requires a clear understanding on how to create a [Purchase Order](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) and a [Purchase Invoice](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) as well as how to register a [Vendor Payment](../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md#payment-out). It is recommended as well to understand how to set up a [Payment Term](../../../user-guide/etendo-classic/basic-features/master-data-management/business-partner-setup.md#payment-term) and how to launch the [Payment Report](../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/analysis-tools.md#payment-report). @@ -45,7 +45,7 @@ Please note that, prepay payment term has a header and a line: ### Purchase Order creation -As already mentioned, the first step is to create a [Purchase Order](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order) which contains the goods that the company needs. +As already mentioned, the first step is to create a [Purchase Order](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) which contains the goods that the company needs. In this scenario, the parties have agreed a specific payment term which can be filled in the corresponding field of the purchase order header. @@ -100,7 +100,7 @@ The purchase order payment plan includes the payment registered in the Payment O ### Payment check -Back to the [Purchase Order](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order), it is possible to check the recently created Payment Plan with its Payment Details. +Back to the [Purchase Order](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md), it is possible to check the recently created Payment Plan with its Payment Details. ![](../../../assets/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables/paymentdetails.png) @@ -114,7 +114,7 @@ To summarize: ### Pre-Paid invoice management and accounting -The company in this example can register the [Goods Receipt](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#goods-receipts) before registering the vendor invoice by using the process [Pending Goods Receipts](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#pending-goods-receipts). +The company in this example can register the [Goods Receipt](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md) before registering the vendor invoice by using the process [Pending Goods Receipts](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md). This process allows introducing the exact amount of goods received from the vendor against each purchase order line. diff --git a/docs/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md b/docs/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md index 950172a29e..4eea64845e 100644 --- a/docs/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md +++ b/docs/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md @@ -40,15 +40,15 @@ For orders, quotations and return documents it is possible to close multiple doc This functionality is available in the following windows: -- [Sales Quotation](../../../basic-features/sales-management/transactions.md#bulk-completion) -- [Sales Order](../../../basic-features/sales-management/transactions.md#bulk-completion_1) -- [Goods Shipment](../../../basic-features/sales-management/transactions.md#bulk-completion_2) -- [Return From Customer](../../../basic-features/sales-management/transactions.md#bulk-completion_3) +- [Sales Quotation](../../../basic-features/sales-management/transactions/purchase-order.md) +- [Sales Order](../../../basic-features/sales-management/transactions/goods-receipt.md) +- [Goods Shipment](../../../basic-features/sales-management/transactions/purchase-invoice.md) +- [Return From Customer](../../../basic-features/sales-management/transactions/return-to-vendor.md) - [Sales Invoice](../../../basic-features/sales-management/transactions.md#bulk-completion_4) -- [Purchase Order](../../../basic-features/procurement-management/transactions.md#bulk-completion) -- [Goods Receipt](../../../basic-features/procurement-management/transactions.md#bulk-completion_1) -- [Purchase Invoice](../../../basic-features/procurement-management/transactions.md#bulk-completion_2) -- [Return To Vendor](../../../basic-features/procurement-management/transactions.md#bulk-completion_3) +- [Purchase Order](../../../basic-features/procurement-management/transactions/purchase-order.md) +- [Goods Receipt](../../../basic-features/procurement-management/transactions/goods-receipt.md) +- [Purchase Invoice](../../../basic-features/procurement-management/transactions/purchase-invoice.md) +- [Return To Vendor](../../../basic-features/procurement-management/transactions/return-to-vendor.md) As explained, using Bulk Completion improves efficiency by allowing users to perform document actions in bulk, streamlining operations and saving time. diff --git a/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md b/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md index e0ff888ead..72e38ad713 100644 --- a/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md +++ b/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md @@ -25,12 +25,12 @@ This functionality enhances the bank account management enabling greater customi This functionality is available in the following windows: - [Business Partner](../../../basic-features/master-data-management/master-data.md#advanced-bank-account-management) -- [Sales Invoice](../../../basic-features/sales-management/transactions.md#advanced-bank-account-management_1) -- [Purchase Invoice](../../../basic-features/procurement-management/transactions.md#advanced-bank-account-management_1) -- [Sales Order](../../../basic-features/sales-management/transactions.md#advanced-bank-account-management) -- [Purchase Order](../../../basic-features/procurement-management/transactions.md#advanced-bank-account-management) -- [Payment In](../../../basic-features/financial-management/receivables-and-payables/transactions.md#advanced-bank-account-management_1) -- [Payment Out](../../../basic-features/financial-management/receivables-and-payables/transactions.md#advanced-bank-account-management) +- [Sales Invoice](../../../basic-features/sales-management/transactions/purchase-invoice.md) +- [Purchase Invoice](../../../basic-features/procurement-management/transactions/purchase-invoice.md) +- [Sales Order](../../../basic-features/sales-management/transactions/purchase-order.md) +- [Purchase Order](../../../basic-features/procurement-management/transactions/purchase-order.md) +- [Payment In](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) +- [Payment Out](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-order.md) ## Business Partner - Bank Account :material-menu: `Application` > `Master Data Management` > `Business Partner` diff --git a/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md b/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md index 3b1631a37d..0ba8bdf411 100644 --- a/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md +++ b/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md @@ -26,26 +26,26 @@ The Bulk Posting functionality allows the user to post or unpost multiple record This functionality is available in the following windows: - [Amortization](../../../basic-features/financial-management/assets/overview.md#bulk-posting) -- [Goods Movements](../../../basic-features/warehouse-management/transactions.md#bulk-posting_1) -- [Financial Account](../../../basic-features/financial-management/receivables-and-payables/transactions.md#bulk-posting_2) -- [Matched Purchase Invoices](../../../basic-features/procurement-management/transactions.md#bulk-posting_2) -- [Cost Adjustment](../../../basic-features/warehouse-management/transactions.md#bulk-posting_3) -- [Bill of Materials Production](../../../basic-features/warehouse-management/transactions.md#bulk-posting_2) -- [Internal Consumption](../../../basic-features/production-management/transactions.md#bulk-posting_1) -- [Doubtful Debt](../../../basic-features/financial-management/receivables-and-payables/transactions.md#bulk-posting_3) -- [Landed Cost](../../../basic-features/procurement-management/transactions.md#bulk-posting_4) -- [G/L Journal](../../../basic-features/financial-management/accounting/transactions.md#bulk-posting_1) -- [Simple G/L Journal](../../../basic-features/financial-management/accounting/transactions.md#bulk-posting) -- [Work Effort](../../../basic-features/production-management/transactions.md#bulk-posting) -- [Goods Receipt](../../../basic-features/procurement-management/transactions.md#bulk-posting) -- [Goods Shipment](../../../basic-features/sales-management/transactions.md#bulk-posting) -- [Return Material Receipt](../../../basic-features/sales-management/transactions.md#bulk-posting_1) -- [Return to Vendor Shipment](../../../basic-features/procurement-management/transactions.md#bulk-posting_3) -- [Sales Invoice](../../../basic-features/sales-management/transactions.md#bulk-posting_2) -- [Purchase Invoice](../../../basic-features/procurement-management/transactions.md#bulk-posting_1) -- [Payment In](../../../basic-features/financial-management/receivables-and-payables/transactions.md#bulk-posting_1) -- [Payment Out](../../../basic-features/financial-management/receivables-and-payables/transactions.md#bulk-posting) -- [Physical Inventory](../../../basic-features/warehouse-management/transactions.md#bulk-posting) +- [Goods Movements](../../../basic-features/warehouse-management/transactions/purchase-invoice.md) +- [Financial Account](../../../basic-features/financial-management/receivables-and-payables/transactions/matched-purchase-invoices.md) +- [Matched Purchase Invoices](../../../basic-features/procurement-management/transactions/matched-purchase-invoices.md) +- [Cost Adjustment](../../../basic-features/warehouse-management/transactions/return-to-vendor-shipment.md) +- [Bill of Materials Production](../../../basic-features/warehouse-management/transactions/matched-purchase-invoices.md) +- [Internal Consumption](../../../basic-features/production-management/transactions/purchase-invoice.md) +- [Doubtful Debt](../../../basic-features/financial-management/receivables-and-payables/transactions/return-to-vendor-shipment.md) +- [Landed Cost](../../../basic-features/procurement-management/transactions/landed-cost.md) +- [G/L Journal](../../../basic-features/financial-management/accounting/transactions/purchase-invoice.md) +- [Simple G/L Journal](../../../basic-features/financial-management/accounting/transactions/goods-receipt.md) +- [Work Effort](../../../basic-features/production-management/transactions/goods-receipt.md) +- [Goods Receipt](../../../basic-features/procurement-management/transactions/goods-receipt.md) +- [Goods Shipment](../../../basic-features/sales-management/transactions/goods-receipt.md) +- [Return Material Receipt](../../../basic-features/sales-management/transactions/purchase-invoice.md) +- [Return to Vendor Shipment](../../../basic-features/procurement-management/transactions/return-to-vendor-shipment.md) +- [Sales Invoice](../../../basic-features/sales-management/transactions/matched-purchase-invoices.md) +- [Purchase Invoice](../../../basic-features/procurement-management/transactions/purchase-invoice.md) +- [Payment In](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) +- [Payment Out](../../../basic-features/financial-management/receivables-and-payables/transactions/goods-receipt.md) +- [Physical Inventory](../../../basic-features/warehouse-management/transactions/goods-receipt.md) ### Accounting Status Column diff --git a/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md b/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md index 23020c6d4a..cb9d6f4ae2 100644 --- a/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md +++ b/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md @@ -68,12 +68,12 @@ This module enhances the bank account management enabling greater customization This functionality is available in the following windows: - [Business Partner](../../../basic-features/master-data-management/master-data.md#advanced-bank-account-management_1) - - [Sales invoice](../../../basic-features/sales-management/transactions.md#advanced-bank-account-management_1) - - [Purchase Invoice](../../../basic-features/procurement-management/transactions.md#advanced-bank-account-management_1) - - [Sales order](../../../basic-features/sales-management/transactions.md#advanced-bank-account-management) - - [Purchase order](../../../basic-features/procurement-management/transactions.md#advanced-bank-account-management) - - [Payment In](../../../basic-features/financial-management/receivables-and-payables/transactions.md#advanced-bank-account-management_1) - - [Payment Out](../../../basic-features/financial-management/receivables-and-payables/transactions.md#advanced-bank-account-management) + - [Sales invoice](../../../basic-features/sales-management/transactions/purchase-invoice.md) + - [Purchase Invoice](../../../basic-features/procurement-management/transactions/purchase-invoice.md) + - [Sales order](../../../basic-features/sales-management/transactions/purchase-order.md) + - [Purchase order](../../../basic-features/procurement-management/transactions/purchase-order.md) + - [Payment In](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) + - [Payment Out](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-order.md) For more information, visit the [Advanced Bank Account Management](../../../optional-features/bundles/financial-extensions/advanced-bank-account-management.md). @@ -114,8 +114,8 @@ This functionality is part of the Financial Extensions Bundle and it is useful w - [Sales Order](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#how-to-reactivate-a-closed-sales-order) - [Sales Invoice](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#how-to-reactivate-a-voided-sales-invoice) - - [Purchase Order](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#how-to-reactivate-a-closed-purchase-order) - - [Purchase Invoice](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#how-to-reactivate-a-voided-purchase-invoice) + - [Purchase Order](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) + - [Purchase Invoice](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) - [Amortization](../../../../../user-guide/etendo-classic/basic-features/financial-management/assets/overview.md#how-to-reactivate-amortizations) - and the [Advanced Financial Docs. Processing developer guide](../../../../../developer-guide/etendo-classic/bundles/financial-extensions-bundle.md#advanced-financial-docs-processing) @@ -250,12 +250,12 @@ The button Remove Payment is available in the Sales Order, Purchase Order, Sales !!! info For more information, visit: - - [Sales Order](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#payment-removal) - - [Purchase Order](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#payment-removal) - - [Sales Invoice](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#payment-removal_1) - - [Purchase Invoice](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#payment-removal_1) - - [Payment In](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md#payment-removal_1) - - [Payment Out](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md#payment-removal) + - [Sales Order](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions/purchase-order.md) + - [Purchase Order](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) + - [Sales Invoice](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions/purchase-invoice.md) + - [Purchase Invoice](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) + - [Payment In](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) + - [Payment Out](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions/purchase-order.md) - [Financial Account](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md#payment-removal_2) ### Remittances diff --git a/docs/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management.md b/docs/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management.md index daf4987b4d..8f98b6cd6f 100644 --- a/docs/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management.md +++ b/docs/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management.md @@ -356,7 +356,7 @@ When goods are received, the system can automatically generate RI records for ea :material-menu: `Application` > `Procurement Management` > `Transaction` > `Inbound Receipt` -The **Inbound Receipt** window enhances the [goods receipt](../../../basic-features/procurement-management/transactions.md#goods-receipts) flow by introducing an intermediate step between the purchase order and the goods receipt. This step centralizes multiple orders—even from different suppliers—into a single operation, improving flexibility, automation, and control. It also supports alternative units of measure (AUOM), enabling receipts to be recorded in pallets, boxes, or regrouped into different containers to reflect the actual inflow. +The **Inbound Receipt** window enhances the [goods receipt](../../../basic-features/procurement-management/transactions/goods-receipt.md) flow by introducing an intermediate step between the purchase order and the goods receipt. This step centralizes multiple orders—even from different suppliers—into a single operation, improving flexibility, automation, and control. It also supports alternative units of measure (AUOM), enabling receipts to be recorded in pallets, boxes, or regrouped into different containers to reflect the actual inflow. Receipts are always created from purchase orders, not manually. Order lines are loaded with product, quantity, lot, and location details, which can be adjusted (e.g., quantity or unit) to register partial or alternative receipts. This ensures the goods receipt accurately reflects what was physically received and updates the purchase order accordingly. diff --git a/docs/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md b/docs/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md index 861e81af61..79c3372bc7 100644 --- a/docs/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md +++ b/docs/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md @@ -88,7 +88,7 @@ This functionality is part of the Warehouse Extensions Bundle and it is useful w For more information, visit the user guide for: - [Goods Movements](../../../../../user-guide/etendo-classic/basic-features/warehouse-management/transactions.md#how-to-reactivate-goods-movements) - - [Goods Receipts](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#how-to-reactivate-goods-receipts) + - [Goods Receipts](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md) - [Goods Shipments](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#how-to-reactivate-goods-shipments) - [Physical Inventory](../../../../../user-guide/etendo-classic/basic-features/warehouse-management/transactions.md#how-to-reactivate-physical-inventories) @@ -124,7 +124,7 @@ This module allows you to configure whether the system permits material transact The preference **Allow Backdated Cost Transactions** is set to **Y** by default, which means that transactions with dates earlier than the current date are allowed. -When the preference is set to **N**, the following documents will be restricted to only use the current date: [Goods Receipts](../../../basic-features/procurement-management/transactions.md#goods-receipts), [Goods Shipments](../../../basic-features/sales-management/transactions.md#goods-shipment), [Goods Movements](../../../basic-features/warehouse-management/transactions.md#goods-movement), [Physical Inventories](../../../basic-features/warehouse-management/transactions.md#physical-inventory), [Work Efforts](../../../basic-features/production-management/transactions.md#work-effort), and [Internal Consumption](../../../basic-features/production-management/transactions.md#internal-consumption). +When the preference is set to **N**, the following documents will be restricted to only use the current date: [Goods Receipts](../../../basic-features/procurement-management/transactions/goods-receipt.md), [Goods Shipments](../../../basic-features/sales-management/transactions.md#goods-shipment), [Goods Movements](../../../basic-features/warehouse-management/transactions.md#goods-movement), [Physical Inventories](../../../basic-features/warehouse-management/transactions.md#physical-inventory), [Work Efforts](../../../basic-features/production-management/transactions.md#work-effort), and [Internal Consumption](../../../basic-features/production-management/transactions.md#internal-consumption). !!! warning If you need to create a new configuration for this preference, it must be set globally only, without distinguishing any specific visibility level (Organization, User, Role, etc.), as it could affect the correct operation of the validation. diff --git a/docs/whats-new/etendo-news.md b/docs/whats-new/etendo-news.md index 929eba4f81..634d0f130d 100644 --- a/docs/whats-new/etendo-news.md +++ b/docs/whats-new/etendo-news.md @@ -673,13 +673,13 @@ tags: - :octicons-rocket-24: **New Shipment and Invoicing Statuses in Purchase Orders and Goods Receipts** --- - This release introduces improved visibility in procurement processes. In the [Purchase Order](../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order) window, the status bar now shows shipment and invoicing percentages. At the line level, you’ll see detailed quantities for what has been invoiced and shipped. - Similarly, the [Goods Receipt](../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#goods-receipts) window shows invoicing percentages at both header and line levels. + This release introduces improved visibility in procurement processes. In the [Purchase Order](../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) window, the status bar now shows shipment and invoicing percentages. At the line level, you’ll see detailed quantities for what has been invoiced and shipped. + Similarly, the [Goods Receipt](../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md) window shows invoicing percentages at both header and line levels. - :octicons-rocket-24: **Easily Exclude Promotions and Discounts with a Simple Checkbox** --- - A new checkbox in the *More Information* section of [Sales Order](../user-guide/etendo-classic/basic-features/sales-management/transactions.md#lines_1) and [Sales Invoice](../user-guide/etendo-classic/basic-features/sales-management/transactions.md#lines_5) lines allows users to **cancel automatic discounts and promotions**. This gives you more control over pricing on a per-line basis. + A new checkbox in the *More Information* section of [Sales Order](../user-guide/etendo-classic/basic-features/sales-management/transactions.md#lines_1) and [Sales Invoice](../user-guide/etendo-classic/basic-features/sales-management/transactions/return-to-vendor.md) lines allows users to **cancel automatic discounts and promotions**. This gives you more control over pricing on a per-line basis. - :octicons-rocket-24: **Improved Navigation in the Create Invoices from Orders Process** @@ -689,7 +689,7 @@ tags: - :octicons-rocket-24: **Enhanced Purchase Invoice Voiding with Supplier Reference** --- - When canceling a purchase invoice, Etendo creates a reverse document that now references the supplier’s cancellation document. The [invoice reactivation](../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#reactivate) process includes a new `Supplier Reference` field to ensure clear traceability and alignment. + When canceling a purchase invoice, Etendo creates a reverse document that now references the supplier’s cancellation document. The [invoice reactivation](../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) process includes a new `Supplier Reference` field to ensure clear traceability and alignment. From c92a77729f2cfab56c3ae157014d1d65af58508f Mon Sep 17 00:00:00 2001 From: etendobot <108091082+etendobot@users.noreply.github.com> Date: Mon, 13 Apr 2026 15:54:27 -0300 Subject: [PATCH 08/13] Feature ETP-3185: Update ES translation --- .../accounting/setup/document-type.md | 16 +- .../financial-management/getting-started.md | 6 +- .../master-data-management/master-data.md | 8 +- .../getting-started.md | 12 +- .../material-requirement-planning/setup.md | 8 +- .../transactions.md | 10 +- .../procurement-management/getting-started.md | 38 +- .../transactions/goods-receipt.md | 4 +- .../transactions/landed-cost.md | 4 +- .../transactions/pending-goods-receipts.md | 6 +- .../transactions/purchase-order.md | 4 +- .../transactions/return-to-vendor-shipment.md | 4 +- .../transactions/return-to-vendor.md | 6 +- .../getting-started.md | 2 +- .../transactions.md | 2 +- .../sales-management/setup/commission.md | 2 +- .../warehouse-management/getting-started.md | 6 +- .../warehouse-management/transactions.md | 8 +- ...-to-manage-prepaid-invoices-in-payables.md | 8 +- .../essentials-extensions/bulk-completion.md | 20 +- .../advanced-bank-account-management.md | 16 +- .../financial-extensions/bulk-posting.md | 42 +- .../bundles/financial-extensions/overview.md | 32 +- .../advanced-warehouse-management.md | 819 +++++++++--------- .../bundles/warehouse-extensions/overview.md | 4 +- docs/es/whats-new/etendo-news.md | 20 +- 26 files changed, 578 insertions(+), 529 deletions(-) diff --git a/docs/es/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md b/docs/es/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md index 0f6fb1cc7d..c6bf0dd935 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md +++ b/docs/es/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md @@ -29,18 +29,18 @@ La lista completa de tipos de documento estándar es la siguiente: | | | | |-----|-----|-----| | **Nombre del tipo de documento**  | **Tipo doc. base**  | **Transacción empresarial** | -| AP CreditMemo | Nota de abono de proveedor | [Nota de crédito de compra](../../../procurement-management/transactions.md#reactivate) | -| AP Invoice | Factura de proveedor | [Factura (Proveedor)](../../../procurement-management/transactions.md#purchase-invoice) | +| AP CreditMemo | Nota de abono de proveedor | [Nota de crédito de compra](../../../procurement-management/transactions/purchase-invoice.md) | +| AP Invoice | Factura de proveedor | [Factura (Proveedor)](../../../procurement-management/transactions/purchase-invoice.md) | | AR CreditMemo | Nota de abono de cliente | [Nota de crédito de venta](../../../sales-management/transactions.md#header-6) | | AR Invoice | Factura de cliente | [Factura (Cliente)](../../../sales-management/transactions.md#sales-invoice) | | Return Material Sales Invoice | Factura de devolución de material (cliente) | [Factura de venta de devolución de material](../../../sales-management/transactions.md#a) | | Reversed Sales Invoice | Factura de cliente | [Factura de venta revertida](../../../sales-management/transactions.md#header-6) | -| MM Receipt | Recepción de material | [Albarán (Proveedor)](../../../procurement-management/transactions.md#goods-receipts) | -| RTV Shipment | Recepción de material | [Devolución a albarán de proveedor](../../../procurement-management/transactions.md#return-to-vendor-shipment) | +| MM Receipt | Recepción de material | [Albarán (Proveedor)](../../../procurement-management/transactions/goods-receipt.md) | +| RTV Shipment | Recepción de material | [Devolución a albarán de proveedor](../../../procurement-management/transactions/return-to-vendor-shipment.md) | | MM Shipment | Entrega de material | [Albarán (Cliente)](../../../sales-management/transactions.md#goods-shipment) | | RFC Receipt | Entrega de material | [Recepción de devolución de cliente](../../../sales-management/transactions.md#return-material-receipt) | -| Pedido de compra | Pedido de compra | [Pedido de compra](../../../procurement-management/transactions.md#purchase-order) | -| RTV Order | Pedido de compra | [Devolución a proveedor](../../../procurement-management/transactions.md#return-to-vendor-rtv) | +| Pedido de compra | Pedido de compra | [Pedido de compra](../../../procurement-management/transactions/purchase-order.md) | +| RTV Order | Pedido de compra | [Devolución a proveedor](../../../procurement-management/transactions/return-to-vendor.md) | | Presupuesto | Pedido de venta | [Presupuesto de ventas](../../../sales-management/transactions.md#sales-quotation) | | RFC Order | Pedido de venta | [Pedido de venta de devolución de cliente](../../../sales-management/transactions.md#return-from-customer) | | POS Order | Pedido de venta | [Pedido de punto de venta](../../../sales-management/transactions.md#sales-invoice) | @@ -54,8 +54,8 @@ La lista completa de tipos de documento estándar es la siguiente: | Conciliación | Conciliación | [Conciliación](../../../financial-management/receivables-and-payables/transactions.md#reconciliations) | | Dudoso cobro | Dudoso cobro | [Dudoso cobro](../../../financial-management/receivables-and-payables/transactions.md#doubtful-debt) | | Ajuste de Costes | Ajuste de Costes | [Ajuste de Costes](../../../warehouse-management/transactions.md#cost-adjustment) | -| Landed Cost | Landed Cost | [Landed Cost](../../../procurement-management/transactions.md#landed-cost-1) | -| Coste de Landed Cost | Coste de Landed Cost | [Coste de Landed Cost](../../../procurement-management/transactions.md#header-7) | +| Landed Cost | Landed Cost | [Landed Cost](../../../procurement-management/transactions/landed-cost.md) | +| Coste de Landed Cost | Coste de Landed Cost | [Coste de Landed Cost](../../../procurement-management/transactions/landed-cost.md) | | Ajuste de Valor del Inventario | Ajuste de Valor del Inventario | [Ajuste de Valor del Inventario](../../../warehouse-management/transactions.md#inventory-amount-update) | !!! note "Importante" diff --git a/docs/es/user-guide/etendo-classic/basic-features/financial-management/getting-started.md b/docs/es/user-guide/etendo-classic/basic-features/financial-management/getting-started.md index 589dc6980b..9527fd9c60 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/financial-management/getting-started.md +++ b/docs/es/user-guide/etendo-classic/basic-features/financial-management/getting-started.md @@ -17,7 +17,7 @@ Etendo genera automáticamente una representación contable de todas las transac La contabilidad es el sistema de seguimiento de los activos, las deudas, los ingresos y los gastos de una empresa. En Etendo, la mayoría de los asientos contables se crean automáticamente al contabilizar [documentos](../financial-management/accounting/setup/document-type.md). -- [Albarán (Proveedor)](../procurement-management/transactions.md#goods-receipts) y [Factura (Proveedor)](../procurement-management/transactions.md#purchase-invoice) en el área de negocio [Gestión de Compras](../procurement-management/getting-started.md) +- [Albaranes (Proveedor)](../procurement-management/transactions/goods-receipt.md) y [Facturas (Proveedor)](../procurement-management/transactions/purchase-invoice.md) en el área de negocio [Gestión de Compras](../procurement-management/getting-started.md) - [Albarán (Cliente)](../sales-management/transactions.md#goods-shipment) y [Factura (Cliente)](../sales-management/transactions.md#sales-invoice) en el área de negocio [Gestión de Ventas](../sales-management/getting-started.md). Los asientos contables no relacionados directamente con [documentos](../financial-management/accounting/setup/document-type.md) gestionados dentro de un área de aplicación determinada pueden crearse y contabilizarse en [Asientos manuales](../financial-management/accounting/transactions.md#gl-journal). Por ejemplo, un asiento de provisión por depreciación de existencias. @@ -25,7 +25,7 @@ Los asientos contables no relacionados directamente con [documentos](../financia Hay tres formas de contabilizar en Etendo: - Contabilizar manualmente cada documento usando el botón de proceso *Contabilizar*. -El botón de proceso *Contabilizar* se puede encontrar en la ventana utilizada para crear un documento determinado. Por ejemplo, una factura de proveedor se crea y, por tanto, podría contabilizarse en la [ventana Factura (Proveedor)](../procurement-management/transactions.md#purchase-invoice). Este botón se muestra para los usuarios contables si el atributo *ShowAcct* es visible para ellos. Esta configuración se habilita mediante una [Preferencias](../general-setup/application/preference.md). +El botón de proceso *Contabilizar* se puede encontrar en la ventana utilizada para crear un documento determinado. Por ejemplo, una factura de proveedor se crea y, por tanto, podría contabilizarse en la [ventana Factura (Proveedor)](../procurement-management/transactions/purchase-invoice.md). Este botón se muestra para los usuarios contables si el atributo *ShowAcct* es visible para ellos. Esta configuración se habilita mediante una [Preferencias](../general-setup/application/preference.md). - Contabilizar manualmente todos los documentos/transacciones relacionados con una tabla de base de datos determinada, por ejemplo la tabla *Facturas*, usando el proceso [Proceso contable](../financial-management/accounting/transactions.md#gl-posting-by-db-tables) @@ -428,4 +428,6 @@ Este trabajo es una obra derivada de [Gestión Financiera](http://wiki.openbravo --- +--- + --- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/master-data-management/master-data.md b/docs/es/user-guide/etendo-classic/basic-features/master-data-management/master-data.md index 491cf38399..6a79d36876 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/master-data-management/master-data.md +++ b/docs/es/user-guide/etendo-classic/basic-features/master-data-management/master-data.md @@ -63,7 +63,7 @@ Campos a tener en cuenta: - **Días consumo**: información que se utilizará al crear pedidos de venta o pedidos de compra para ese tercero en particular, mediante un proceso denominado *Copiar líneas*. !!! info - Para más información sobre este proceso, visite las secciones [Pedido de venta](../sales-management/transactions.md#sales-order) y [Pedido de compra](../procurement-management/transactions.md#purchase-order). + Para más información sobre este proceso, visite las secciones [Pedido de venta](../sales-management/transactions.md#sales-order) y [Pedido de compra](../procurement-management/transactions/purchase-order.md) secciones. - **Crédito límite**: Etendo informará cuando se supere el límite de crédito introducido en este campo para el tercero al contabilizar facturas de venta. - **Consentimiento para el Procesamiento de Datos del Cliente**: casilla de verificación en el modelo de datos de terceros, para reflejar si un contacto determinado consiente o no que sus datos puedan ser utilizados por la organización. @@ -334,7 +334,7 @@ El usuario puede configurar, para cada proveedor o acreedor y para el esquema co - las transacciones de **Pasivo del proveedor**, como la contabilización de facturas de compra. !!! info - Para más información, visite [Factura (Proveedor)](../procurement-management/transactions.md#purchase-invoice). + Para más información, visite [Factura (Proveedor)](../procurement-management/transactions/purchase-invoice.md). - las transacciones de **Pagos por adelantado del proveedor**, como aquellos casos en los que el proveedor de los bienes requiere que la empresa pague por adelantado una parte o la totalidad del importe de la deuda. @@ -597,7 +597,7 @@ En esta sección, el usuario puede ver información relacionada con los pedidos, El usuario puede seleccionar un tercero para comenzar a ver las transacciones relacionadas. -![](../../../../assets/drive/4OnjuhWdUoTUGTSu8zWxiV2-AAuj2bKugSYsd0tnIK9CgAS12oX62u4KgxFW35THxZKqIH0Epr-E-q5w4w4y4kbkWR3wCKNTQFosue5bPRC3CMXbOgCNgkzsvXCtZ7OsB53ZD69KhpH-BmTZbQ.png) +![](../../../../assets/drive/4OnjuhWdUoTUGTSu8zWxiV2-AAuj2bKugSYsd0tnIK9CgAS12oX62u4KgxFW35THxZKqIH0Epr-E-q5w4w4y4kbkWR3wCKNTQFosue5bPRC3CMXbOgCNgkzsvXCtZ7OsB53ZD69KhpH-bmTZbQ.png) #### Pedidos tercero @@ -1296,4 +1296,6 @@ Este trabajo es una obra derivada de [Gestión de Datos Maestros](https://wiki.o --- +--- + --- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/material-requirement-planning/getting-started.md b/docs/es/user-guide/etendo-classic/basic-features/material-requirement-planning/getting-started.md index bddbf12ef2..a4a06c7116 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/material-requirement-planning/getting-started.md +++ b/docs/es/user-guide/etendo-classic/basic-features/material-requirement-planning/getting-started.md @@ -22,8 +22,8 @@ En Gestión de MRP, la aplicación se utiliza para *revisar automáticamente la La Gestión de MRP consta de dos planes: -- Planificación de la producción: plan para mostrar cálculos relacionados con productos que pasan por Producción. Los documentos sugeridos para crear en este plan son la [Orden de Fabricación](../production-management/transactions.md#work-requirement) y la [Necesidad de material](../procurement-management/transactions.md#requisition). -- Planificación de compras: plan para mostrar cálculos relacionados con productos que se aprovisionan. El documento sugerido para crear en este plan es el [Pedido de compra](../procurement-management/transactions.md#purchase-order). +- Planificación de la producción: plan para mostrar cálculos relacionados con productos que pasan por Producción. Los documentos sugeridos para crear en este plan son la [Orden de Fabricación](../production-management/transactions.md#work-requirement) y la [Necesidad de material](../procurement-management/transactions/requisition.md). +- Planificación de compras: plan para mostrar cálculos relacionados con productos que se aprovisionan. El documento sugerido para crear en este plan es el [Pedido de compra](../procurement-management/transactions/purchase-order.md). Los **Método de planificación** se introducen para definir qué componentes de suministro se tienen en cuenta en los cálculos de estos planes. @@ -78,8 +78,8 @@ En la visión general creada, el planificador de material revisa y analiza las l El MRP interactúa con los siguientes módulos: - [Gestión de Compras](../procurement-management/getting-started.md): - - [Necesidad de material](../procurement-management/transactions.md#requisition) se crean desde la Planificación de la producción - - [Pedido de compra](../procurement-management/transactions.md#purchase-order) se crean desde la Planificación de compras + - [Necesidad de material](../procurement-management/transactions/requisition.md) se crean desde la Planificación de la producción + - [Pedido de compra](../procurement-management/transactions/purchase-order.md) se crean desde la Planificación de compras - [Gestión de Ventas](../sales-management/getting-started.md): - [Pedido de venta](../sales-management/transactions.md#sales-order) se tienen opcionalmente en cuenta en los cálculos de ambos planes - [Gestión de Almacén](../warehouse-management/getting-started.md): @@ -90,4 +90,6 @@ El MRP interactúa con los siguientes módulos: --- -- Este trabajo es una obra derivada de [Gestión de MRP](https://wiki.openbravo.com/wiki/Material_Requirement_Planning){target="_blank"} de [Openbravo S.L.U](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="_blank"}, con licencia [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"}. \ No newline at end of file +- Este trabajo es una obra derivada de [Gestión de MRP](https://wiki.openbravo.com/wiki/Material_Requirement_Planning){target="_blank"} de [Openbravo S.L.U](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="_blank"}, con licencia [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"}. + +--- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/material-requirement-planning/setup.md b/docs/es/user-guide/etendo-classic/basic-features/material-requirement-planning/setup.md index 4ed9d73139..0b2a872296 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/material-requirement-planning/setup.md +++ b/docs/es/user-guide/etendo-classic/basic-features/material-requirement-planning/setup.md @@ -28,7 +28,7 @@ Por **valor por defecto**, MRP tiene en cuenta el **stock** y el **stock mín.** - **Necesidad de material**: demanda del producto en necesidades de material en estado completado. !!! info - Para más detalles, consulte la sección [_Necesidad de material_](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#requisition). + Para más detalles, consulte la sección [_Necesidad de material_](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md). - **Previsión de ventas**: previsión de demanda futura del producto. !!! info @@ -44,7 +44,7 @@ Por **valor por defecto**, MRP tiene en cuenta el **stock** y el **stock mín.** - **Pedido de compra pendiente**: oferta del producto en un pedido de compra reservado que aún no se ha recibido. !!! info - Para más detalles, consulte la sección [_Pedido de compra_](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order). + Para más detalles, consulte la sección [_Pedido de compra_](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md). ### Cabecera @@ -85,4 +85,6 @@ Defina el planificador encargado de gestionar la compra o la producción de prod --- -- Este trabajo es una obra derivada de [Material_Requirement_Planning](https://wiki.openbravo.com/wiki/Material_Requirement_Planning){target="_blank"} de [Openbravo S.L.U](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="_blank"}, con licencia [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"}. \ No newline at end of file +- Este trabajo es una obra derivada de [Material_Requirement_Planning](https://wiki.openbravo.com/wiki/Material_Requirement_Planning){target="_blank"} de [Openbravo S.L.U](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="_blank"}, con licencia [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"}. + +--- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/material-requirement-planning/transactions.md b/docs/es/user-guide/etendo-classic/basic-features/material-requirement-planning/transactions.md index 9635572bdb..3a8f23666a 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/material-requirement-planning/transactions.md +++ b/docs/es/user-guide/etendo-classic/basic-features/material-requirement-planning/transactions.md @@ -89,14 +89,14 @@ Dependiendo del producto, pueden aparecer diferentes tipos de transacción en la Al hacer clic en el botón **Generar órdenes de fabricación**, las órdenes de fabricación se crean automáticamente. Los documentos deben procesarse; consulte la sección [Orden de Fabricación](../../../../user-guide/etendo-classic/basic-features/production-management/transactions.md#work-requirement) en la sección de Gestión de producción para más detalles. !!! info - Al hacer clic en el botón **Generar necesidades de material**, las necesidades de material se crean automáticamente en borrador. Los documentos deben completarse; consulte la sección [Necesidad de material](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#requisition) en la sección de Gestión de aprovisionamiento para más detalles. + Al hacer clic en el botón **Generar necesidades de material**, las necesidades de material se crean automáticamente en borrador. Los documentos deben completarse; consulte la sección [Necesidad de material](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md) en la sección de Gestión de aprovisionamiento para más detalles. Las necesidades de material pueden seleccionarse como entrada en el método de planificación de la Planificación de compras para incluirse en los cálculos de ese plan, con el fin de calcular si es necesario crear pedidos de compra. Una vez que los documentos se crean automáticamente, los números de los documentos aparecen en las columnas **Orden de Fabricación** y **Línea de necesidad de material** de las líneas. El pedido de compra creado está en estado borrador y debe contabilizarse. !!! info - Para más información, consulte la sección [_Pedido de compra_](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order). + Para más información, consulte la sección [_Pedido de compra_](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md). ## Planificación de compras @@ -182,7 +182,7 @@ Al hacer clic en el botón **Crear pedidos de compra**, se crea el pedido de com Una vez que el pedido de compra se crea automáticamente, el número del documento aparece en la columna **Línea de pedido** de la línea. El pedido de compra creado está en estado borrador y debe contabilizarse. !!! info - Para más información, consulte la sección [Pedido de compra](../procurement-management/transactions.md#purchase-order). + Para más información, consulte la sección [Pedido de compra](../procurement-management/transactions/purchase-order.md). ## Previsión de ventas @@ -215,4 +215,6 @@ Añada productos que se incluirán en su previsión de MRP. Cada producto se añ --- -- Este trabajo es una obra derivada de [Planificación de necesidades de material](https://wiki.openbravo.com/wiki/Material_Requirement_Planning){target="_blank"} de [Openbravo S.L.U](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="_blank"}, con licencia [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"}. \ No newline at end of file +- Este trabajo es una obra derivada de [Planificación de necesidades de material](https://wiki.openbravo.com/wiki/Material_Requirement_Planning){target="_blank"} de [Openbravo S.L.U](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="_blank"}, con licencia [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"}. + +--- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md index 9fa6be7d02..560494c30a 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md @@ -73,7 +73,7 @@ En Gestión de Compras, el proceso de negocio Procure to Pay se ejecuta del sigu Cualquier miembro de la organización autorizado puede emitir directamente una Necesidad de material como resultado de una necesidad de la organización o de una unidad de negocio. -- El solicitante crea un nuevo documento en la ventana [Necesidad de material](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#requisition), introduce una "Fecha de necesidad" y después busca el producto o servicio necesario. +- El solicitante crea un nuevo documento en la ventana [Necesidad de material](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md), introduce una "Fecha de necesidad" y después busca el producto o servicio necesario. Si el producto no existe, puede introducirse en ese momento en la ventana [Producto](../../../../user-guide/etendo-classic/basic-features/master-data-management/master-data.md#product). - El solicitante continúa añadiendo, para cada producto necesario, una nueva línea con la fecha de necesidad, el producto, la cantidad, el precio si se conoce y, si es necesario, su atributo (talla y/o color, etc.). También puede añadirse un proveedor preferente si se conoce. @@ -81,45 +81,45 @@ También puede añadirse un proveedor preferente si se conoce. Las necesidades de material notifican al personal de compras los productos a pedir, su cantidad y el plazo de entrega. El personal de compras se encarga entonces de gestionar las necesidades de material ya creadas o incluso de crear nuevas, si fuera necesario. -- El personal de compras gestiona las necesidades en la ventana [Administrar necesidades](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#manage-requisitions). +- El personal de compras gestiona las necesidades en la ventana [Administrar necesidades](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/manage-requisitions.md). - El personal de compras puede cambiar cualquier dato de las necesidades creadas en estado borrador y, además, puede buscar el proveedor que se utilizará en el campo Terceros. Si el tercero no existe, puede introducirse en ese momento en la ventana [Terceros](../../../../user-guide/etendo-classic/basic-features/master-data-management/master-data.md#business-partner). - El personal de compras también puede introducir el precio neto unitario de compra y los descuentos, si los hubiera, una vez se conozcan. - Una vez que la necesidad está lista, se completa. El estado del documento de la necesidad cambia a Completado y entonces puede convertirse en un pedido de compra. El personal de compras: -- puede crear de forma masiva Pedido/s de compra para las necesidades completadas en la ventana [Necesidad a Pedido](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#requisition-to-order), buscando y añadiendo líneas de necesidad que aún no estén vinculadas a un pedido. +- puede crear de forma masiva Pedido/s de compra para las necesidades completadas en la ventana [Necesidad a Pedido](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition-to-order.md), buscando y añadiendo líneas de necesidad que aún no estén vinculadas a un pedido. Los pedidos de compra creados de este modo se muestran en la ventana Pedido de compra en estado Reservado. -- y también puede crear directamente pedidos de compra en la ventana [Pedido de compra](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order). Las líneas de compra se rellenan como en el caso de la necesidad. Una vez que el pedido de compra está listo, se procesa haciendo clic en el botón Reservar. +- y también puede crear directamente pedidos de compra en la ventana [Pedido de compra](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md). Las líneas de compra se rellenan como en el caso de la necesidad. Una vez que el pedido de compra está listo, se procesa haciendo clic en el botón Reservar. - Para revisar compras pasadas y presentes del proveedor, el personal de compras utiliza el [Análisis dimensional pedidos compras](../../../../user-guide/etendo-classic/basic-features/procurement-management/analysis-tools.md#purchase-dimensional-report). El personal de almacén: - Recibe la mercancía, así como los albaranes adjuntos, de 2 formas: - - Con la ventana [Albarán (Proveedor)](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#goods-receipts), el personal de almacén busca los pedidos pendientes de entrega uno a uno y obtiene la cantidad de las líneas de pedido correspondientes, ubicándola en un almacén y una ubicación. + - Con la ventana [Albarán (Proveedor)](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md), el personal de almacén busca los pedidos pendientes de entrega uno a uno y obtiene la cantidad de las líneas de pedido correspondientes, ubicándola en un almacén y una ubicación. Esta ventana también permite crear un albarán de forma manual. - - Con la ventana [Albarán (Proveedor) pendiente](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#pending-goods-receipts). El personal de almacén puede seleccionar masivamente las líneas de pedido de compra que se están entregando y ubicar la cantidad recibida en un almacén y una ubicación. + - Con la ventana [Albarán (Proveedor) pendiente](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md). El personal de almacén puede seleccionar masivamente las líneas de pedido de compra que se están entregando y ubicar la cantidad recibida en un almacén y una ubicación. - Imputa Landed Cost, si lo hubiera, a los productos incluidos en un albarán mediante: - la selección de un tipo de Landed Cost e introduciendo un importe de Landed Cost "estimado" que se distribuirá entre las líneas del albarán - o seleccionando un tipo de Landed Cost e introduciendo un importe de Landed Cost ya facturado, que también se distribuirá entre las líneas del albarán. - Completa los albaranes. - - Los albaranes completados actualizan la información de stock (aumentan los niveles de producto) y pueden ser [contabilizados](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#goods-receipts) en el libro mayor, por lo que aumenta la contabilidad de activos del producto. + - Los albaranes completados actualizan la información de stock (aumentan los niveles de producto) y pueden ser [contabilizados](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md) en el libro mayor, por lo que aumenta la contabilidad de activos del producto. - Un Albarán (Proveedor) solo puede contabilizarse si se ha calculado el coste de los productos recibidos. Para ello, debe ejecutarse el [proceso en segundo plano de cálculo de costes](../../../../user-guide/etendo-classic/basic-features/general-setup/process-scheduling/process-request.md#costing). -- La ventana [Facturas cuadradas](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#matched-invoices) ayuda a gestionar y contabilizar las discrepancias, si las hubiera, entre la contabilidad del albarán y la contabilidad de la factura correspondiente posteriormente, debido a diferencias de precio de compra. +- La ventana [Facturas cuadradas](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.md) ayuda a gestionar y contabilizar las discrepancias, si las hubiera, entre la contabilidad del albarán y la contabilidad de la factura correspondiente posteriormente, debido a diferencias de precio de compra. - El [Análisis dimensional albaranes compras](../../../../user-guide/etendo-classic/basic-features/procurement-management/analysis-tools.md#goods-receipts-dimensional-report) se utiliza para revisar albaranes anteriores del tercero. El personal de finanzas: - Registra facturas de proveedor de diferentes maneras: - - Con la ventana [Albarán (Proveedor)](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#goods-receipts), el personal de finanzas puede generar una factura a partir de un albarán en estado Completado. - - Con la ventana [Factura (Proveedor)](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-invoice), el personal de finanzas puede introducir facturas de proveedor: + - Con la ventana [Albarán (Proveedor)](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md), el personal de finanzas puede generar una factura a partir de un albarán en estado Completado. + - Con la ventana [Factura (Proveedor)](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md), el personal de finanzas puede introducir facturas de proveedor: - de forma manual - o recuperando líneas de pedidos de compra o de albaranes pendientes de facturar - o copiando líneas de factura de facturas de proveedor existentes. - Registra facturas de Landed Cost y concilia esos Landed Cost "facturados" con los Landed Cost: - - registrados directamente en un/unos [albarán/es](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#landed-cost). - - o registrados mediante un [documento de Landed Cost](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#landed-cost_1). -- [Procesa](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#process-matching) y [contabiliza](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#post-matching) la conciliación de Landed Cost. + - registrados directamente en un/unos [albarán/es](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md). + - o registrados mediante un [documento de Landed Cost](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md). +- [Procesa](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md) y [contabiliza](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md) la conciliación de Landed Cost. - Una vez que una Factura (Proveedor) se procesa, se crea un plan de pagos de la factura basado en las condiciones de pago acordadas con el proveedor y la factura de proveedor puede contabilizarse para crear los asientos contables de la factura. Posteriormente, el plan de pagos puede modificarse. Adicionalmente: @@ -133,7 +133,7 @@ Los gastos de compra pueden reconocerse de diferentes maneras: En Etendo, en esta situación, el gasto se genera como parte de la contabilidad de la factura de proveedor correspondiente a la transacción. - En algunas circunstancias, sin embargo, se requiere diferir el reconocimiento del gasto. Por ejemplo, una empresa que compra un seguro empresarial por la duración de un año querría distribuir ese gasto durante 12 meses. -En Etendo, en esta situación, el gasto puede diferirse dentro de un número determinado de periodos introduciendo un plan de diferimiento de gastos en las [líneas de factura de proveedor](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#lines_4). +En Etendo, en esta situación, el gasto puede diferirse dentro de un número determinado de periodos introduciendo un plan de diferimiento de gastos en las [líneas de factura de proveedor](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md). !!!info Para una descripción completa de esta funcionalidad, visite la sección [Cómo gestionar ingresos y gastos diferidos](../../../../user-guide/etendo-classic/how-to-guides/how-to-manage-deferred-revenue-and-expenses.md). @@ -162,22 +162,22 @@ En Gestión de Compras, el *flujo de negocio de Devolución a proveedor* se ejec El personal de compras: -- Crea un nuevo documento en la ventana [Devolución a proveedor](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#return-to-vendor-rtv) y busca el nombre del vendedor en el campo Terceros. -- Y continúa añadiendo líneas haciendo clic en el botón [Elegir/Editar lineas](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#lines_5) +- Crea un nuevo documento en la ventana [Devolución a proveedor](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md) y busca el nombre del vendedor en el campo Terceros. +- Y continúa añadiendo líneas haciendo clic en el botón [Elegir/Editar lineas](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md) - Es posible seleccionar líneas de albarán de proveedor y editar la cantidad que desea devolver y el precio - Una vez que el documento de devolución de material es aceptado por el vendedor, puede procesarlo haciendo clic en el botón Reservar. El estado del documento cambia de Borrador a Reservado. - Solo los documentos Reservados pueden enviarse al vendedor El personal de almacén: -- Crea un nuevo documento en la ventana [Devolución a albarán de proveedor](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#return-to-vendor-shipment) y busca el nombre del vendedor en el campo Terceros. -- Y continúa añadiendo líneas haciendo clic en el botón [Elegir/Editar lineas](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#lines_6) +- Crea un nuevo documento en la ventana [Devolución a albarán de proveedor](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md) y busca el nombre del vendedor en el campo Terceros. +- Y continúa añadiendo líneas haciendo clic en el botón [Elegir/Editar lineas](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md) - Se seleccionan líneas de Devolución a proveedor - Es posible editar la cantidad a enviar - Una vez que el documento está listo, procéselo haciendo clic en el botón Completar. El estado del documento cambia de Borrador a Completado - El envío completado actualiza la información de stock (disminuyen los niveles de producto) -Personal de finanzas: para facturar estos documentos, vaya a la ventana [Factura (Proveedor)](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-invoice). Se cubren todos los escenarios: +Personal de finanzas: para facturar estos documentos, vaya a la ventana [Factura (Proveedor)](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md). Se cubren todos los escenarios: - Si el vendedor envía una factura solo para ese documento específico, debe seleccionar un tipo de documento de factura de compra revertida y después seleccionar las líneas mediante el botón *Crear líneas de* - Si el vendedor envía una factura con el pedido de compra original más el pedido de devolución de material, debe seleccionar un tipo de documento de Factura (Proveedor) y después seleccionar las líneas mediante el botón *Crear líneas de* diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md index 12cb0fbd2a..3cb529b4bb 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md @@ -203,4 +203,6 @@ La funcionalidad Bulk Completion permite al usuario completar, reactivar o anula Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. --- -Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. + +--- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md index 8e14c86d20..99a73e0951 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md @@ -327,4 +327,6 @@ Además, el Estado Contable del/de los registro/s se muestra en la barra de esta Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. --- -Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. + +--- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md index 51f508db32..e1e0a87fbc 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md @@ -25,7 +25,9 @@ Esta ventana permite al usuario: --- -Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. +Este trabajo es una obra derivada de [Gestión de Compras](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. --- -Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. + +--- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md index e055877ade..0361dfd0b8 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md @@ -209,4 +209,6 @@ Este módulo añade un nuevo campo a la cabecera de la ventana Pedido de compra: Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, usada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. --- -Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. + +--- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md index 258996477c..7f100f8d1e 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md @@ -96,4 +96,6 @@ Además, el Estado de Contabilidad del/de los registro/s se muestra en la barra Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, usado bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. --- -Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. + +--- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md index 1df845c518..6ce93a3edc 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md @@ -41,7 +41,7 @@ Para introducir nuevas líneas debes hacer clic en el botón de proceso PICK/EDI - **Devuelto**: cantidad que deseas devolver. Al seleccionar la fila, la cantidad no se establece por defecto ya que el sistema no puede saber cuántos artículos se devuelven. - **Precio unitario**: precio de la orden de compra original. - **Motivos de devolución**: el motivo por el que devuelves el artículo. - - y **Unidad de Devolución**, solo en caso de que esté habilitada la preferencia de \*unidad de medida alternativa (AUM)\*. + - y **Unidad de Devolución**, solo en caso de que esté habilitada la preferencia de \*unidad de medida alternativa (AUM)*. En ese caso, se muestra la AUM "primary" del producto para el flujo de compra si existe; en caso contrario, se muestra la UdM del producto. El usuario siempre puede cambiarla a la UdM del producto. Puedes definir el Motivo de devolución a nivel de cabecera. En este caso, al elegir una línea hereda lo seleccionado en la cabecera, pero puedes modificarlo como desees. @@ -75,4 +75,6 @@ La funcionalidad Bulk Completion permite al usuario completar, reactivar o cerra Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. --- -Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. + +--- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/project-and-service-management/getting-started.md b/docs/es/user-guide/etendo-classic/basic-features/project-and-service-management/getting-started.md index 23c796a933..4cfa3f01a9 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/project-and-service-management/getting-started.md +++ b/docs/es/user-guide/etendo-classic/basic-features/project-and-service-management/getting-started.md @@ -35,7 +35,7 @@ Los conceptos clave de gestión de proyectos y servicios mencionados en este cap - Empleado: persona que trabaja en la empresa. En la gestión de proyectos y servicios, la información del empleado se utiliza para el cálculo del coste del proyecto, en base a los [Informe de tiempo](../project-and-service-management/transactions.md#expense-sheet). - [Pedido de venta](../sales-management/transactions.md#sales-order): documento que lista los bienes y/o servicios proporcionados a un cliente y las condiciones de la venta. - [Factura (Cliente)](../sales-management/transactions.md#sales-invoice): documento utilizado para administrar un derecho de cobro. El documento lista los bienes y/o servicios proporcionados a un cliente y las condiciones de la venta. -- [Factura (Proveedor)](../procurement-management/transactions.md#purchase-invoice): documento utilizado para administrar una obligación de pago. El documento lista los bienes y/o servicios proporcionados por un proveedor. +- [Factura (Proveedor)](../procurement-management/transactions/purchase-invoice.md): documento utilizado para administrar una obligación de pago. El documento lista los bienes y/o servicios proporcionados por un proveedor. - [Tipo de proyecto](../project-and-service-management/setup.md#project-type): plantilla utilizada para crear fácilmente fases y tareas en un proyecto multifase. Esto es especialmente útil para completar automáticamente fases y tareas según la plantilla sin realizar el proceso manualmente. - [Proyecto multifase](../project-and-service-management/transactions.md#multiphase-project): formulario utilizado para registrar un proyecto, los gastos planificados, los márgenes, para quién se ejecutará el proyecto y las fases y tareas del proyecto. - [Fase](../project-and-service-management/transactions.md#project-phase-tab): un periodo de tiempo durante el cual se ejecutan determinadas actividades. diff --git a/docs/es/user-guide/etendo-classic/basic-features/project-and-service-management/transactions.md b/docs/es/user-guide/etendo-classic/basic-features/project-and-service-management/transactions.md index 98e1cfdf59..a4923593f6 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/project-and-service-management/transactions.md +++ b/docs/es/user-guide/etendo-classic/basic-features/project-and-service-management/transactions.md @@ -176,7 +176,7 @@ Un Informe de gasto se utiliza para registrar partes de horas y gastos de artíc En base a las partes de horas, se calcula el coste relacionado con los operarios asignados al proyecto y puede consultarse en el informe [Rentabilidad de Proyectos](../project-and-service-management/analysis-tools.md#project-profitability). -Para los gastos de artículos, se documenta el coste que los operarios han realizado relacionado con proyectos. En base a esto, el seguimiento para reembolsar el coste al operario se realiza con la creación de una [Factura (Proveedor)](../procurement-management/transactions.md#purchase-invoice). Para vincular las facturas correspondientes al proyecto, existe un campo de dimensión de proyecto en la cabecera de la ventana Factura (Proveedor). +Para los gastos de artículos, se documenta el coste que los operarios han realizado relacionado con proyectos. En base a esto, el seguimiento para reembolsar el coste al operario se realiza con la creación de una [Factura (Proveedor)](../procurement-management/transactions/purchase-invoice.md). Para vincular las facturas correspondientes al proyecto, existe un campo de dimensión de proyecto en la cabecera de la ventana Factura (Proveedor). Tanto para partes de horas como para gastos de artículos, se puede indicar si al cliente relacionado con el proyecto se le facturan estos costes. El seguimiento de esto es que se crea un [Pedido de venta](../sales-management/transactions.md#sales-order) para crear una [Factura (Cliente)](../sales-management/transactions.md#sales-invoice). diff --git a/docs/es/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md b/docs/es/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md index 9bb02f8397..772fdf1307 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md +++ b/docs/es/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md @@ -20,7 +20,7 @@ La funcionalidad de Comisión en Etendo comienza con la **ventana Comisión**, d Desde la ventana Comisión, se definen criterios más detallados, incluyendo filtros por tercero, producto o región, junto con la estructura real de la comisión. Una funcionalidad clave es la posibilidad de asignar un **agente comercial** directamente al crear documentos de venta (pedidos y/o facturas), lo que permite a Etendo vincular esas transacciones al plan de comisiones correspondiente y garantiza un filtrado preciso. -Una vez establecidas todas las condiciones, el sistema genera la comisión correspondiente, que se muestra en la ventana [**Procesar comisión**](../../../../etendo-classic/basic-features/sales-management/transactions.md#commission-payment), donde los usuarios pueden revisar un desglose detallado del cálculo e incluso generar una [**Factura (Proveedor)**](../../../../etendo-classic/basic-features/procurement-management/transactions.md#purchase-invoice) para procesar el pago de la comisión al agente comercial. +Una vez establecidas todas las condiciones, el sistema genera la comisión correspondiente, que se muestra en la ventana [**Procesar comisión**](../../../../etendo-classic/basic-features/sales-management/transactions.md#commission-payment), donde los usuarios pueden revisar un desglose detallado del cálculo e incluso generar una [**Factura (Proveedor)**](../../../../etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) para procesar el pago de la comisión al agente comercial. En resumen, el flujo general es: diff --git a/docs/es/user-guide/etendo-classic/basic-features/warehouse-management/getting-started.md b/docs/es/user-guide/etendo-classic/basic-features/warehouse-management/getting-started.md index 8433f69d50..da24ca4a7d 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/warehouse-management/getting-started.md +++ b/docs/es/user-guide/etendo-classic/basic-features/warehouse-management/getting-started.md @@ -40,7 +40,7 @@ Los principales subprocesos del flujo de negocio Precisión del inventario son: Es necesario crear y configurar [Almacén y huecos](../../../../user-guide/etendo-classic/basic-features/warehouse-management/setup.md#warehouse-and-storage-bins) antes de ejecutar el flujo de negocio. Además, es necesario definir y validar una [Regla de cálculo de costes](../../../../user-guide/etendo-classic/basic-features/warehouse-management/setup.md#costing-rules) para la entidad legal. Cada regla de cálculo de costes requiere una fecha de inicio a partir de la cual será válida, así como un [Algoritmo de cálculo de costes](../../../../user-guide/etendo-classic/basic-features/warehouse-management/setup.md#costing-algorithm) que será utilizado por el proceso [Costing Background Process](../../../../user-guide/etendo-classic/basic-features/general-setup/process-scheduling/process-request.md#costing), que debe planificarse. -Además, es necesario configurar [Tipo de Landed Cost](../../../../user-guide/etendo-classic/basic-features/warehouse-management/setup.md#landed-cost-type), por lo que podrán seleccionarse al asignar este tipo de coste a [Albarán (Proveedor)](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#goods-receipts). +Además, es necesario configurar [Tipo de Landed Cost](../../../../user-guide/etendo-classic/basic-features/warehouse-management/setup.md#landed-cost-type), por lo que podrán seleccionarse al asignar este tipo de coste a [albaranes](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md). Por último, pueden configurarse [Reglas de almacén](../../../../user-guide/etendo-classic/basic-features/warehouse-management/setup.md#warehouse-rules) para que se apliquen al recuperar stock del inventario de forma automática. @@ -92,4 +92,6 @@ Gestión de Almacén tiene conexión con otras áreas de aplicación: --- -Este trabajo es una obra derivada de [Gestión de Almacén](http://wiki.openbravo.com/wiki/Warehouse_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. \ No newline at end of file +Este trabajo es una obra derivada de [Gestión de Almacén](http://wiki.openbravo.com/wiki/Warehouse_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. + +--- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/warehouse-management/transactions.md b/docs/es/user-guide/etendo-classic/basic-features/warehouse-management/transactions.md index 53e29af3cb..5df5e530c8 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/warehouse-management/transactions.md +++ b/docs/es/user-guide/etendo-classic/basic-features/warehouse-management/transactions.md @@ -242,7 +242,7 @@ La funcionalidad de Contabilización masiva permite al usuario contabilizar o de Además, el Estado contable del/de los registro(s) se muestra en la barra de estado, en vista de formulario, o en una columna, en vista de rejilla. !!! info - Para más información, visite [la guía de usuario del módulo de Contabilización masiva](../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). + Para más información, visite [la guía de usuario del módulo Contabilización masiva](../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md). ## Producción LDM :material-menu: `Aplicación` > `Gestión de Almacén` > `Transacciones` > `Producción LDM` @@ -365,7 +365,7 @@ Para más información, visite [Pedido de venta](../../../../user-guide/etendo-c Las pre-reservas también pueden realizarse desde el **Pedido de compra**. Estando en la línea del pedido de compra, existe la posibilidad de seleccionar cualquier línea de pedido de venta pendiente de entrega que esté esperando recibir la mercancía en el almacén. Una vez que se reciben los artículos, la pre-reserva se convierte en reserva y las existencias quedan reservadas para esa línea de pedido de venta. -Para más información, visite [Pedido de compra](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order). +Para más información, visite [Pedido de compra](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md). ### Plan de compras (MRP) @@ -781,7 +781,7 @@ Ajuste de la transacción **"Movimiento a"**: | | | | | ----------------------------------------------------------------------------------------------- | ---------------------------------------------- | ---------------------------------------------- | -| Cuenta | Débito | Crédito | +| Cuenta | Débito | Crédito | | [_Inmovilizado del producto_](../../../../user-guide/etendo-classic/basic-features/master-data-management/master-data.md#accounting) | Importe del ajuste de la transacción "Movimiento a" | | | [_Diferencias de almacén_](../../../../user-guide/etendo-classic/basic-features/financial-management/accounting/setup/general-ledger-configuration.md#defaults-tab) | | Importe del ajuste de la transacción "Movimiento a" | ### **Corrección de stock negativo** @@ -1087,4 +1087,6 @@ Este trabajo es una obra derivada de [Gestión de Almacén](http://wiki.openbrav --- +--- + --- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md b/docs/es/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md index 00d2cf4bb6..1d6c3efd01 100644 --- a/docs/es/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md +++ b/docs/es/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md @@ -20,7 +20,7 @@ En estas situaciones, la empresa y el proveedor acuerdan unas condiciones de pag ## Artículos recomendados -La gestión de facturas prepagadas requiere una comprensión clara de cómo crear un [Pedido de compra](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order) y una [Factura (Proveedor)](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-invoice), así como de cómo registrar un [Pago a proveedor](../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md#payment-out). +La gestión de facturas prepagadas requiere una comprensión clara de cómo crear un [Pedido de compra](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) y una [Factura (Proveedor)](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md), así como de cómo registrar un [Pago a proveedor](../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md#payment-out). También se recomienda comprender cómo configurar unas [Condiciones de pago](../../../user-guide/etendo-classic/basic-features/master-data-management/business-partner-setup.md#payment-term) y cómo lanzar el [Informe de pagos y cobros](../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/analysis-tools.md#payment-report). @@ -45,7 +45,7 @@ Tenga en cuenta que las condiciones de pago de prepago tienen una cabecera y una ### Creación del Pedido de compra -Tal y como se ha mencionado, el primer paso es crear un [Pedido de compra](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order) que contenga los bienes que la empresa necesita. +Tal y como se ha mencionado, el primer paso es crear un [Pedido de compra](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) que contenga los bienes que la empresa necesita. En este escenario, las partes han acordado unas condiciones de pago específicas que pueden informarse en el campo correspondiente de la cabecera del pedido de compra. @@ -100,7 +100,7 @@ El plan de pagos del pedido de compra incluye el pago registrado en la solapa De ### Comprobación del pago -De vuelta al [Pedido de compra](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order), es posible comprobar el plan de pagos creado recientemente con sus detalles de pago. +De vuelta al [Pedido de compra](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md), es posible comprobar el plan de pagos creado recientemente con sus detalles de pago. ![](../../../assets/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables/paymentdetails.png) @@ -114,7 +114,7 @@ En resumen: ### Gestión y contabilidad de facturas prepagadas -La empresa de este ejemplo puede registrar el [Albarán (Proveedor)](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#goods-receipts) antes de registrar la factura del proveedor utilizando el proceso [Albaranes pendientes de recibir](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#pending-goods-receipts). +La empresa de este ejemplo puede registrar el [Albarán (Proveedor)](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md) antes de registrar la factura del proveedor utilizando el proceso [Albaranes pendientes de recibir](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md). Este proceso permite introducir la cantidad exacta de bienes recibidos del proveedor contra cada línea del pedido de compra. diff --git a/docs/es/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md b/docs/es/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md index 911f73c3e5..f7bd1cb2b8 100644 --- a/docs/es/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md +++ b/docs/es/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md @@ -40,18 +40,20 @@ Para pedidos, presupuestos y documentos de devolución es posible cerrar múltip Esta funcionalidad está disponible en las siguientes ventanas: -- [Presupuesto de ventas](../../../basic-features/sales-management/transactions.md#bulk-completion) -- [Pedido de venta](../../../basic-features/sales-management/transactions.md#bulk-completion_1) -- [Albarán (Cliente)](../../../basic-features/sales-management/transactions.md#bulk-completion_2) -- [Devolución de cliente](../../../basic-features/sales-management/transactions.md#bulk-completion_3) +- [Presupuesto de ventas](../../../basic-features/sales-management/transactions/purchase-order.md) +- [Pedido de venta](../../../basic-features/sales-management/transactions/goods-receipt.md) +- [Albarán (Cliente)](../../../basic-features/sales-management/transactions/purchase-invoice.md) +- [Devolución de cliente](../../../basic-features/sales-management/transactions/return-to-vendor.md) - [Factura (Cliente)](../../../basic-features/sales-management/transactions.md#bulk-completion_4) -- [Pedido de compra](../../../basic-features/procurement-management/transactions.md#bulk-completion) -- [Albarán (Proveedor)](../../../basic-features/procurement-management/transactions.md#bulk-completion_1) -- [Factura (Proveedor)](../../../basic-features/procurement-management/transactions.md#bulk-completion_2) -- [Devolución a proveedor](../../../basic-features/procurement-management/transactions.md#bulk-completion_3) +- [Pedido de compra](../../../basic-features/procurement-management/transactions/purchase-order.md) +- [Albarán (Proveedor)](../../../basic-features/procurement-management/transactions/goods-receipt.md) +- [Factura (Proveedor)](../../../basic-features/procurement-management/transactions/purchase-invoice.md) +- [Devolución a proveedor](../../../basic-features/procurement-management/transactions/return-to-vendor.md) Como se ha explicado, el uso de Finalización masiva mejora la eficiencia al permitir a los usuarios realizar acciones sobre documentos de forma masiva, agilizando las operaciones y ahorrando tiempo. --- -Este trabajo está licenciado bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L](https://etendo.software){target="_blank"}. \ No newline at end of file +Este trabajo está licenciado bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L](https://etendo.software){target="_blank"}. + +--- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md b/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md index 11cf1196de..3a963dbcb9 100644 --- a/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md +++ b/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md @@ -25,12 +25,12 @@ Esta funcionalidad mejora la gestión de cuentas bancarias, permitiendo una mayo Esta funcionalidad está disponible en las siguientes ventanas: - [Terceros](../../../basic-features/master-data-management/master-data.md#advanced-bank-account-management) -- [Factura (Cliente)](../../../basic-features/sales-management/transactions.md#advanced-bank-account-management_1) -- [Factura (Proveedor)](../../../basic-features/procurement-management/transactions.md#advanced-bank-account-management_1) -- [Pedido de venta](../../../basic-features/sales-management/transactions.md#advanced-bank-account-management) -- [Pedido de compra](../../../basic-features/procurement-management/transactions.md#advanced-bank-account-management) -- [Cobros](../../../basic-features/financial-management/receivables-and-payables/transactions.md#advanced-bank-account-management_1) -- [Pago](../../../basic-features/financial-management/receivables-and-payables/transactions.md#advanced-bank-account-management) +- [Factura (Cliente)](../../../basic-features/sales-management/transactions/purchase-invoice.md) +- [Factura (Proveedor)](../../../basic-features/procurement-management/transactions/purchase-invoice.md) +- [Pedido de venta](../../../basic-features/sales-management/transactions/purchase-order.md) +- [Pedido de compra](../../../basic-features/procurement-management/transactions/purchase-order.md) +- [Cobros](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) +- [Pago](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-order.md) ## Terceros - Cuenta bancaria :material-menu: `Aplicación` > `Gestión de Datos Maestros` > `Terceros` @@ -107,4 +107,6 @@ Al igual que en el caso del botón **Añadir pago**, el botón **Añadir detalle ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management/aba8.png) --- -This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L](https://etendo.software){target="_blank"}. \ No newline at end of file +This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L](https://etendo.software){target="_blank"}. + +--- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md b/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md index 34f09bede8..72173cc2dc 100644 --- a/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md +++ b/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md @@ -26,26 +26,26 @@ La funcionalidad de Contabilización masiva permite al usuario contabilizar o de Esta funcionalidad está disponible en las siguientes ventanas: - [Amortización](../../../basic-features/financial-management/assets/overview.md#bulk-posting) -- [Movimiento entre almacenes](../../../basic-features/warehouse-management/transactions.md#bulk-posting_1) -- [Cuenta financiera](../../../basic-features/financial-management/receivables-and-payables/transactions.md#bulk-posting_2) -- [Facturas cuadradas](../../../basic-features/procurement-management/transactions.md#bulk-posting_2) -- [Ajuste de Costes](../../../basic-features/warehouse-management/transactions.md#bulk-posting_3) -- [Producción LDM](../../../basic-features/warehouse-management/transactions.md#bulk-posting_2) -- [Consumo interno](../../../basic-features/production-management/transactions.md#bulk-posting_1) -- [Dudoso cobro](../../../basic-features/financial-management/receivables-and-payables/transactions.md#bulk-posting_3) -- [Landed Cost](../../../basic-features/procurement-management/transactions.md#bulk-posting_4) -- [Asientos manuales](../../../basic-features/financial-management/accounting/transactions.md#bulk-posting_1) -- [Asientos Manuales Simplificados](../../../basic-features/financial-management/accounting/transactions.md#bulk-posting) -- [Parte de Trabajo](../../../basic-features/production-management/transactions.md#bulk-posting) -- [Albarán (Proveedor)](../../../basic-features/procurement-management/transactions.md#bulk-posting) -- [Albarán (Cliente)](../../../basic-features/sales-management/transactions.md#bulk-posting) -- [Recibo devolución de material](../../../basic-features/sales-management/transactions.md#bulk-posting_1) -- [Devolución a albarán de proveedor](../../../basic-features/procurement-management/transactions.md#bulk-posting_3) -- [Factura (Cliente)](../../../basic-features/sales-management/transactions.md#bulk-posting_2) -- [Factura (Proveedor)](../../../basic-features/procurement-management/transactions.md#bulk-posting_1) -- [Cobros](../../../basic-features/financial-management/receivables-and-payables/transactions.md#bulk-posting_1) -- [Pago](../../../basic-features/financial-management/receivables-and-payables/transactions.md#bulk-posting) -- [Inventario físico](../../../basic-features/warehouse-management/transactions.md#bulk-posting) +- [Movimiento entre almacenes](../../../basic-features/warehouse-management/transactions/purchase-invoice.md) +- [Cuenta financiera](../../../basic-features/financial-management/receivables-and-payables/transactions/matched-purchase-invoices.md) +- [Facturas cuadradas](../../../basic-features/procurement-management/transactions/matched-purchase-invoices.md) +- [Ajuste de Costes](../../../basic-features/warehouse-management/transactions/return-to-vendor-shipment.md) +- [Producción LDM](../../../basic-features/warehouse-management/transactions/matched-purchase-invoices.md) +- [Consumo interno](../../../basic-features/production-management/transactions/purchase-invoice.md) +- [Dudoso cobro](../../../basic-features/financial-management/receivables-and-payables/transactions/return-to-vendor-shipment.md) +- [Landed Cost](../../../basic-features/procurement-management/transactions/landed-cost.md) +- [Asientos manuales](../../../basic-features/financial-management/accounting/transactions/purchase-invoice.md) +- [Asientos Manuales Simplificados](../../../basic-features/financial-management/accounting/transactions/goods-receipt.md) +- [Parte de Trabajo](../../../basic-features/production-management/transactions/goods-receipt.md) +- [Albarán (Proveedor)](../../../basic-features/procurement-management/transactions/goods-receipt.md) +- [Albarán (Cliente)](../../../basic-features/sales-management/transactions/goods-receipt.md) +- [Recibo devolución de material](../../../basic-features/sales-management/transactions/purchase-invoice.md) +- [Devolución a albarán de proveedor](../../../basic-features/procurement-management/transactions/return-to-vendor-shipment.md) +- [Factura (Cliente)](../../../basic-features/sales-management/transactions/matched-purchase-invoices.md) +- [Factura (Proveedor)](../../../basic-features/procurement-management/transactions/purchase-invoice.md) +- [Cobros](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) +- [Pago](../../../basic-features/financial-management/receivables-and-payables/transactions/goods-receipt.md) +- [Inventario físico](../../../basic-features/warehouse-management/transactions/goods-receipt.md) ### Columna Estado contable @@ -71,4 +71,6 @@ El módulo de Contabilización masiva incluye la funcionalidad de Documentos no --- This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L](https://etendo.software){target="_blank"}. +--- + --- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md b/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md index 287bfdbce7..81e8110963 100644 --- a/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md +++ b/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md @@ -69,12 +69,12 @@ Este módulo mejora la gestión de cuentas bancarias, permitiendo una mayor pers Esta funcionalidad está disponible en las siguientes ventanas: - [Terceros](../../../basic-features/master-data-management/master-data.md#advanced-bank-account-management_1) - - [Factura (Cliente)](../../../basic-features/sales-management/transactions.md#advanced-bank-account-management_1) - - [Factura (Proveedor)](../../../basic-features/procurement-management/transactions.md#advanced-bank-account-management_1) - - [Pedido de venta](../../../basic-features/sales-management/transactions.md#advanced-bank-account-management) - - [Pedido de compra](../../../basic-features/procurement-management/transactions.md#advanced-bank-account-management) - - [Cobros](../../../basic-features/financial-management/receivables-and-payables/transactions.md#advanced-bank-account-management_1) - - [Pago](../../../basic-features/financial-management/receivables-and-payables/transactions.md#advanced-bank-account-management) + - [Factura (Cliente)](../../../basic-features/sales-management/transactions/purchase-invoice.md) + - [Factura (Proveedor)](../../../basic-features/procurement-management/transactions/purchase-invoice.md) + - [Pedido de venta](../../../basic-features/sales-management/transactions/purchase-order.md) + - [Pedido de compra](../../../basic-features/procurement-management/transactions/purchase-order.md) + - [Cobros](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) + - [Pago](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-order.md) Para más información, visite [Gestión avanzada de cuentas bancarias](../../../optional-features/bundles/financial-extensions/advanced-bank-account-management.md). ### Liquidación de terceros @@ -112,10 +112,10 @@ Esta funcionalidad forma parte de Financial Extensions Bundle y es útil cuando - [Pedido de venta](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#how-to-reactivate-a-closed-sales-order) - [Factura (Cliente)](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#how-to-reactivate-a-voided-sales-invoice) - - [Pedido de compra](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#how-to-reactivate-a-closed-purchase-order) - - [Factura (Proveedor)](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#how-to-reactivate-a-voided-purchase-invoice) + - [Pedido de compra](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) + - [Factura (Proveedor)](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) - [Amortización](../../../../../user-guide/etendo-classic/basic-features/financial-management/assets/overview.md#how-to-reactivate-amortizations) - - y la [Guía del desarrollador de Procesamiento avanzado de documentos financieros](../../../../../developer-guide/etendo-classic/bundles/financial-extensions-bundle.md#advanced-financial-docs-processing) + - y la [Guía del desarrollador de Procesamiento avanzado de documentos financieros](../../../../../developer-guide/etendo-classic/bundles/financial-extensions-bundle/overview.md#advanced-financial-docs-processing) ### Informe de Amortización de Activos :octicons-package-16: Paquete Java: `com.smf.asset.amortization.report` @@ -236,12 +236,12 @@ El botón Eliminar pago está disponible en las ventanas Pedido de venta, Pedido !!! info Para más información, visite: - - [Pedido de venta](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#payment-removal) - - [Pedido de compra](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#payment-removal) - - [Factura (Cliente)](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#payment-removal_1) - - [Factura (Proveedor)](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#payment-removal_1) - - [Cobros](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md#payment-removal_1) - - [Pago](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md#payment-removal) + - [Pedido de venta](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions/purchase-order.md) + - [Pedido de compra](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) + - [Factura (Cliente)](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions/purchase-invoice.md) + - [Factura (Proveedor)](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) + - [Cobros](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) + - [Pago](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions/purchase-order.md) - [Cuenta financiera](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md#payment-removal_2) ### Remesas @@ -283,4 +283,6 @@ This work is licensed under :material-creative-commons: :fontawesome-brands-crea --- +--- + --- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management.md b/docs/es/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management.md index ad01de780f..3360054096 100644 --- a/docs/es/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management.md +++ b/docs/es/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management.md @@ -351,807 +351,816 @@ Cuando se reciben mercancías, el sistema puede generar automáticamente registr :material-menu: `Aplicación` > `Gestión de Compras` > `Transacción` > `Recepción de entrada` -La ventana **Recepción de entrada** mejora el flujo de [Albarán (Proveedor)](../../../basic-features/procurement-management/transactions.md#goods-receipts) introduciendo un paso intermedio entre el pedido de compra y el albarán. Este paso centraliza múltiples pedidos —incluso de distintos proveedores— en una única operación, mejorando la flexibilidad, la automatización y el control. También admite unidades alternativas de medida (AUOM), permitiendo registrar recepciones en palés, cajas o reagruparlas en distintos contenedores para reflejar la entrada real. +La ventana **Recepción de entrada** mejora el flujo de [albarán](../../../basic-features/procurement-management/transactions/goods-receipt.md) introduciendo un paso intermedio entre el pedido de compra y el albarán. Este paso centraliza múltiples pedidos—even from different suppliers—into a single operation, improving flexibility, automation, and control. It also supports alternative units of measure (AUOM), enabling receipts to be recorded in pallets, boxes, or regrouped into different containers to reflect the actual inflow. -Las recepciones siempre se crean a partir de pedidos de compra, no manualmente. Las líneas del pedido se cargan con los detalles de producto, cantidad, lote y ubicación, que pueden ajustarse (p. ej., cantidad o unidad) para registrar recepciones parciales o alternativas. Esto garantiza que el albarán refleje con precisión lo recibido físicamente y actualice el pedido de compra en consecuencia. +Receipts are always created from purchase orders, not manually. Order lines are loaded with product, quantity, lot, and location details, which can be adjusted (e.g., quantity or unit) to register partial or alternative receipts. This ensures the goods receipt accurately reflects what was physically received and updates the purchase order accordingly. -Cuando se utilizan AUOM como Palé o Caja, el sistema puede generar automáticamente un registro de Inventario referenciado (RI) vinculado a la línea de recepción, representando la unidad logística y garantizando la trazabilidad. +When AUOMs such as Pallet or Box are used, the system can automatically generate a Referenced Inventory (RI) record linked to the receipt line, representing the logistics unit and ensuring traceability. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-window-0.png) -Campos a tener en cuenta: +Fields to note: -#### Cabecera +#### Header -- **Organización**: Define la organización en la que se creará la recepción de entrada y filtra la información. -- **Tipo de documento**: Se carga por defecto con *Recepción de entrada* para clasificar el tipo de documento. -- **Nº de documento**: Identificador único generado automáticamente para la recepción, con una secuencia específica para este tipo de documento. -- **Fecha del movimiento**: Fecha en la que se registra el movimiento físico de mercancías. Por defecto, es la fecha actual. -- **Descripción**: Campo de texto libre para añadir información adicional o notas sobre la recepción. +- **Organization**: Defines the organization in which the inbound receipt will be created and filter the information. +- **Document Type**: Loaded by default with *Inbound Receipt* to classify the document type. +- **Document No**: Unique identifier automatically generated for the receipt, with a sequence specific to this type of document. +- **Movement Date**: Date on which the physical goods movement is recorded. By default, it is the current date. +- **Description**: Free text field to add additional information or notes about the receipt. -#### Solapa Líneas -La solapa Líneas permite añadir y modificar productos individuales de uno o varios pedidos de compra, ajustando su cantidad y/o unidad. Representa la lista de productos recibidos, mostrando los siguientes campos además de los básicos. +#### Lines Tab + +The Lines Tab allows you to add and modify individual products from one or more purchase orders, adjusting their quantity and/or unit. It represents the list of products received, displaying the following fields in addition to the basic ones. ![alt text](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-window-1.png) -Campos a tener en cuenta: +Fields to note: + +- **Line No**: Sequential number automatically assigned to identify the line within the receipt. +- **Product**: The product being received, linked to the purchase order. +- **Operative Quantity**: Quantity received expressed in the product's alternative unit of measure. Matches the Ordered Quantity if no AUOM is defined. If an AUOM exists, it indicates the number of pallets, boxes, or other alternative units received. +- **Alternative UOM**: Alternative unit of measure for the product. If no AUOM is defined, it defaults to the UOM. Used to record the receipt of products in pallets, boxes, or other containers. +- **Ordered Quantity**: Quantity received expressed in the product's base unit of measure. +- **UOM**: Base unit of measure of the product (e.g., units, liters, kilograms). +- **Attribute Set Value**: Attributes associated with the product, such as batch, serial number, or expiration date. +- **Storage Bin**: Location where the received product will be stored. It can vary between lines, allowing different locations to be assigned to products from the same or different purchase orders. +- **Purchase Order Line**: Reference to the original purchase order line from which the receipt line was generated. +- **Grouped by**: Identifier of the grouping to which the line belongs, generated when using the *Group By* button. It shows which lines are part of the same container or packaging unit. +- **Reference Inventory Type**: Type of referenced inventory associated with the grouping (e.g., Box, Pallet). +- **Goods Receipt Line**: Reference to the goods receipt generated upon completion of the goods receipt. -- **Nivel**: Número secuencial asignado automáticamente para identificar la línea dentro de la recepción. -- **Producto**: El producto que se está recibiendo, vinculado al pedido de compra. -- **Cantidad Operativa**: Cantidad recibida expresada en la unidad alternativa de medida del producto. Coincide con **Cant. pedido** si no hay AUOM definida. Si existe una AUOM, indica el número de palés, cajas u otras unidades alternativas recibidas. -- **Unidad Alternativa**: Unidad alternativa de medida del producto. Si no hay AUOM definida, por defecto toma la **Unidad**. Se utiliza para registrar la recepción de productos en palés, cajas u otros contenedores. -- **Cant. pedido**: Cantidad recibida expresada en la unidad base de medida del producto. -- **Unidad**: Unidad base de medida del producto (p. ej., unidades, litros, kilogramos). -- **Valor atributos**: Atributos asociados al producto, como lote, número de serie o fecha de caducidad. -- **Hueco**: Ubicación donde se almacenará el producto recibido. Puede variar entre líneas, permitiendo asignar distintas ubicaciones a productos del mismo o de diferentes pedidos de compra. -- **Línea de pedido de compra**: Referencia a la línea original del pedido de compra desde la que se generó la línea de recepción. -- **Agrupado por**: Identificador de la agrupación a la que pertenece la línea, generado al usar el botón *Agrupar por*. Muestra qué líneas forman parte del mismo contenedor o unidad de embalaje. -- **Tipo de inventario referenciado**: Tipo de inventario referenciado asociado a la agrupación (p. ej., Caja, Palé). -- **Línea de albarán**: Referencia al albarán generado al completar el albarán. +#### Available Process -#### Procesos disponibles - -**Crear líneas desde pedido** +**Create Lines From Order** -Extrae líneas de producto desde pedidos de compra. Al pulsarlo, un pop-up muestra todos los productos disponibles, incluso de múltiples pedidos de compra. Puede seleccionar una o varias líneas para añadirlas a la solapa Líneas. Si se define un hueco, se asignará a todas las líneas seleccionadas; en caso contrario, puede establecerse individualmente por línea. +Extracts product lines from purchase orders. When clicked, a pop-up shows all available products, even from multiple purchase orders. You can select one or more lines to add to the Lines tab. If a storage bin is defined, it will be assigned to all selected lines; otherwise, it can be set individually per line. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-create-line-boton.png) -**Crear inventario referenciado** +**Create Reference Inventory** -Este botón aparece cuando se selecciona al menos una línea. Permite realizar una agrupación múltiple/mixta en un único tipo de unidad logística (cajas, palés u otros tipos definidos en el sistema). Su función es reunir los productos seleccionados de la solapa Líneas en una agrupación específica, según el tipo de agrupación elegido. También admite la multiselección en las tarjetas de recepción, permitiendo a los usuarios seleccionar y agrupar varias líneas en una sola acción. +This button appears when at least one line is selected. It allows multiple/mixed grouping into a single type of logistics unit (boxes, pallets, or other types defined in the system). Its function is to gather selected products from the Lines tab into a specific grouping, according to the type of grouping chosen. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-button-group-1.png) -La agrupación se refleja en la columna Agrupado por de las líneas seleccionadas (p. ej., Caja-1). +The grouping is reflected in the Grouped by column of the selected lines (e.g., Box-1). -Cuando los elementos seleccionados ya pertenecen a unidades logísticas, el botón puede crear una unidad logística padre que contenga las unidades logísticas hijas seleccionadas. Por ejemplo, es posible crear un palé que agrupe cajas previamente identificadas durante el proceso de recepción. La jerarquía resultante se refleja entonces en el Inventario referenciado generado, preservando la relación padre-hijo y la trazabilidad del stock. +When the selected elements already belong to logistics units, the button can create a parent logistics unit that contains the selected child logistics units. For example, it is possible to create a pallet that groups previously identified boxes during the reception process. The resulting hierarchy is then reflected in the generated Referenced Inventory, preserving the parent-child relationship and stock traceability. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-button-group-2.png) !!! info - - Solo se pueden agrupar líneas del mismo **Pedido de venta**. - - Si una línea ya está agrupada y se incluye en una nueva agrupación, la agrupación anterior será reemplazada. - - Las unidades logísticas hijas permanecen asociadas a la unidad logística padre creada desde el botón. + - Only lines from the same Sales Order can be grouped. + - If a line is already grouped and is included in a new grouping, the previous grouping will be replaced. + - Child logistics units remain associated with the parent logistics unit created from the button. -!!! warning "Agrupación parcial" - Si la acción de agrupación incluye una línea que no puede anidarse debido a una incompatibilidad de tipo (p. ej., un Palé dentro de otro Palé), el sistema **no bloqueará** toda la recepción. En su lugar, procesa las líneas compatibles con normalidad y crea automáticamente un **Inventario referenciado independiente** para la línea incompatible. La recepción se completa correctamente y se muestra un **mensaje de advertencia** indicando cuántas líneas se procesaron con normalidad y cuántas se crearon como RI independientes. +!!! warning "Partial grouping" + If the grouped action includes a line that cannot be nested due to a type incompatibility (e.g., a Pallet inside another Pallet), the system will **not block** the entire receipt. Instead, it processes compatible lines normally and automatically creates a **standalone Referenced Inventory** for the incompatible line. The receipt completes successfully and a **Warning message** is displayed indicating how many lines were processed normally and how many were created as standalone RIs. -**Limpiar Agrupar por** +**Clear Group By** -Este botón permite eliminar una línea de su agrupación sin afectar al resto de líneas del grupo. +Button allows you to remove a line from your grouping without affecting the rest of the lines in the group. -**Generar tarea de recepción** +**Generate Reception Task** -Permite gestionar recepciones operativas desde la app móvil mediante la creación de Tareas de recepción. Está disponible cuando existe una Recepción de entrada que aún no está completada y tiene líneas cargadas. +Allows managing operational receptions from the mobile app through the creation of Reception Tasks. It is available when there is an Inbound Receipt that is not yet completed and has loaded lines. -Al pulsar el botón, se genera una tarea vinculada al documento seleccionado y pasa a ser visible en la app móvil y en la ventana Mantenimiento del ERP. -En la ventana emergente, puede asignar un usuario o habilitar la asignación automática. Si se seleccionan múltiples registros, se creará una tarea por cada registro, todas asignadas al mismo usuario o rol definido en el pop-up. +By pressing the button, a task linked to the selected document is generated and becomes visible in the mobile app and in the Task window of the ERP. +In the pop-up window, you can assign a user or enable automatic assignment. If multiple records are selected, one task will be created for each record, all assigned to the same user or role defined in the pop-up. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-popup-1.png) !!!Info - Para más información, visite [Tareas de recepción](#tareas-de-recepción). + For more information, visit [Reception Tasks](#reception-tasks). -**Completar recepción** +**Complete Receipt** -Finaliza la recepción, generando y completando los correspondientes **albaranes**. Además, si la recepción incluye productos con AUOM (palé o caja), se crea automáticamente el registro asociado de **Inventario referenciado**. +Finishes the receipt, generating and completing the corresponding **goods receipts**. In addition, if the receipt includes products with AUOM (pallet or box), the associated **Inventory Reference** record is automatically created. -**Imprimir etiquetas** +**Print Labels** -Este botón genera etiquetas de código de barras para **todas las líneas** del documento de Recepción de entrada seleccionado. -Cada etiqueta muestra el **código de barras GS1-128** junto con información legible por humanos, incluyendo el **nombre del producto**, los **atributos relevantes** (como lote, fecha de caducidad y número de serie cuando aplique) y el **tipo de unidad logística** (Caja o Palé). Si no hay atributos definidos para un producto, la etiqueta muestra *Sin atributos*. Si no aplica ninguna unidad logística, la línea de unidad logística no se muestra. +This button generates barcode labels for **all lines** of the selected Inbound Receipt document. +Each label displays the **GS1-128 barcode** along with human-readable information, including the **product name**, **relevant attributes** (such as lot, expiration date, and serial number when applicable), and the **logistics unit type** (Box or Pallet). If no attributes are defined for a product, the label displays *No attributes*. If no logistics unit applies, the logistics unit line is not shown. -- Para **productos sueltos** (sin unidades logísticas), el sistema genera **una etiqueta de código de barras por cantidad operativa** definida en la línea de recepción. - Esto significa que se imprimen tantas etiquetas como unidades se indiquen en el campo **Cantidad Operativa**. -- Para **líneas con unidades logísticas (Caja o Palé)** en las que se reciben múltiples unidades (por ejemplo, 3 cajas), el sistema genera **una etiqueta de código de barras única por unidad logística**, ya que cada unidad se registra como un inventario referenciado único. -- Cuando los productos se **agrupan en una única unidad logística** usando el botón **Crear inventario referenciado**, el sistema genera **una única etiqueta de código de barras** para esa unidad logística. - En este caso, la etiqueta identifica la **unidad logística y su hueco**, ya que puede contener múltiples productos agrupados. +- For **loose products** (without logistics units), the system generates **one barcode label per operative quantity** defined in the receipt line. + This means that as many labels are printed as units specified in the **Operative Quantity** field. +- For **lines with logistics units (Box or Pallet)** where multiple units are received (for example, 3 boxes), the system generates **one unique barcode label per logistics unit**, since each unit is registered as a unique referenced inventory. +- When products are **grouped into a single logistics unit** using the **Create Reference Inventory** button, the system generates **one single barcode label** for that logistics unit. + In this case, the label identifies the **logistics unit and its locator**, as it may contain multiple grouped products. -Este botón está disponible **solo cuando la Recepción de entrada está completada**. +This button is available **only when the Inbound Receipt is completed**. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-print-header-1.png) ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-print-header-2.png) -??? example "Imprimir Recepción de entrada - Ejemplos" +??? example "Print Inbound Receipt - Examples" ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-print-header-3.png){ width=600 } - *Etiqueta para el producto **Ale Beer** con todos los atributos (Lote, F. caducidad y Nº de serie) y tipo de unidad logística **Caja**.* + *Label for product **Ale Beer** with all attributes (Lot, Expiration date, and Serial Number) and logistics unit type **Box**.* --- ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-print-header-4.png){ width=600 } - *Etiqueta para una **unidad logística agrupada (Palé)** que puede contener varios productos diferentes — no se muestran el nombre del producto ni los atributos, solo la referencia de la unidad logística.* + *Label for a **grouped logistics unit (Pallet)** that can contain multiple different products — no product name or attributes are shown, only the logistics unit reference.* --- ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-print-header-5.png){ width=600 } - *Etiqueta para el producto **Lager Beer** sin atributos definidos — muestra "Sin atributos".* + *Label for product **Lager Beer** without attributes defined — displays "No attributes".* --- ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-print-header-6.png){ width=600 } - *Etiqueta para **unidades sueltas** del producto **Ale Beer** con atributos (Lote, F. caducidad y Nº de serie) — no se asigna ninguna unidad logística, por lo que no se muestra la línea de LU.* + *Label for **loose units** of product **Ale Beer** with attributes (Lot, Expiration date, and Serial Number) — no logistics unit is assigned, so the LU line is not shown.* --- ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-print-header-7.png){ width=600 } - *Etiqueta para el producto **Ale Beer** con todos los atributos (Lote, F. caducidad y Nº de serie) y tipo de unidad logística **Palé**.* + *Label for product **Ale Beer** with all attributes (Lot, Expiration date, and Serial Number) and logistics unit type **Pallet**.* -**Imprimir etiqueta de línea** +**Print Line Label** -Esta acción genera **etiquetas de código de barras solo para la línea o líneas seleccionadas** de la Recepción de entrada. -Cada etiqueta muestra el **código de barras GS1-128** junto con información legible por humanos, incluyendo el **nombre del producto**, los **atributos relevantes** (como lote, fecha de caducidad y número de serie cuando aplique) y el **tipo de unidad logística** (Caja o Palé), siguiendo las mismas reglas de visualización que el botón **Imprimir etiquetas**. +This action generates **barcode labels only for the selected line or lines** of the Inbound Receipt. +Each label displays the **GS1-128 barcode** along with human-readable information, including the **product name**, **relevant attributes** (such as lot, expiration date, and serial number when applicable), and the **logistics unit type** (Box or Pallet), following the same display rules as the **Print Labels** button. -La generación de etiquetas sigue las mismas reglas descritas anteriormente, aplicadas **solo a la línea o líneas seleccionadas**: +The label generation follows the same rules described above, applied **only to the selected line or lines**: -- Para **productos sueltos**, se genera una etiqueta de código de barras **por cantidad operativa** definida en cada línea seleccionada. -- Para **múltiples unidades logísticas**, se genera una etiqueta única por unidad logística. -- Para **unidades logísticas agrupadas**, se genera una única etiqueta que identifica la unidad logística. +- For **loose products**, one barcode label is generated **per operative quantity** defined in each selected line. +- For **multiple logistics units**, one unique label is generated per logistics unit. +- For **grouped logistics units**, a single label is generated identifying the logistics unit. -Este botón está disponible **solo cuando la Recepción de entrada está completada**. +This button is available **only when the Inbound Receipt is completed**. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-print-lines-1.png) ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-print-lines-2.png) -### Flujo de trabajo +### Workflow -**Flujo de recepción** +**Receipt Flow** -1. En el flujo de recepción, el usuario dispone de un **Pedido de compra** que incluye líneas de producto configuradas con una Unidad alternativa de medida (AUOM) de tipo Caja o Palé, con su equivalencia definida previamente en la ventana Producto (por ejemplo, 1 Palé = 100 unidades). +1. In the receipt flow, the user has a **Purchase Order** that includes product lines configured with an Alternative Unit of Measure (AUOM) of the Box or Pallet type, with its equivalence previously defined in the product window (for example, 1 Pallet = 100 units). ![alt text](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-flow-1.png) -2. Desde la ventana **Recepción de entrada**, el usuario crea un nuevo registro de recepción usando el botón *Crear líneas desde pedido*, seleccionando el Pedido de compra como documento de referencia. El sistema incorpora los datos del pedido, como el producto, la cantidad (en AUOM), los atributos (lote, serie) y otra información asociada. +2. From the **Inbound Receipt** window, the user creates a new receipt record using the *Create Lines From Order* button, selecting the Purchase Order as the reference document. The system incorporates the order data, such as the product, quantity (in AUOM), attributes (batch, series), and other associated information. ![alt text](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-flow-3.png) - !!!info "Dos formas de completar la recepción" - En este punto, puede elegir entre dos flujos de trabajo para completar la recepción de entrada: + !!!info "Two Ways to Complete the Receipt" + At this point, you can choose between two workflows to complete the inbound receipt: - **Opción 1: Completar desde Etendo (ERP)** - Continúe con los pasos 3 y 4 siguientes para completar la recepción directamente en la ventana **Recepción de entrada** pulsando el botón **Completar recepción**. + **Option 1: Complete from Etendo (ERP)** + Continue with steps 3 and 4 below to complete the receipt directly in the **Inbound Receipt** window by pressing the **Complete Receipt** button. - **Opción 2: Completar desde Etendo Mobile** - Utilice el botón **Generar tarea de recepción** para crear una tarea de recepción visible en **Etendo Mobile**. Esto permite a los operarios de almacén realizar la recepción directamente desde sus dispositivos móviles. Para más información, visite [Tareas de recepción](#tareas-de-recepción). + **Option 2: Complete from Etendo Mobile** + Use the **Generate Reception Task** button to create a reception task visible in **Etendo Mobile**. This allows warehouse operators to perform the reception directly from their mobile devices. For more information, visit [Reception Tasks](#reception-tasks). -3. Al pulsar el botón Completar, el sistema genera y completa secuencialmente el **Albarán (Proveedor)** y crea un registro en **Inventario referenciado (RI)** para cada unidad logística recibida (Caja o Palé), respetando las equivalencias definidas en la AUOM. +3. When the Complete button is pressed, the system sequentially generates and completes the **Goods Receipt** and creates a record in **Referenced Inventory (RI)** for each logistics unit received (Box or Pallet), respecting the equivalencies defined in AUOM. ![alt text](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-flow-2.png) -4. El Inventario referenciado queda vinculado a la cantidad recibida, al producto y a sus atributos correspondientes. Como resultado, el stock se actualiza en el inventario, incrementando el número de unidades en la ubicación definida y habilitando la trazabilidad mediante el RI generado. +4. The Referenced Inventory is linked to the quantity received, the product, and its corresponding attributes. As a result, the stock is updated in the inventory, increasing the number of units in the defined location and enabling traceability through the generated RI. ![alt text](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-flow-4.png) -**Flujo de recepción parcial** +**Partial Receipt Flow** -1. El proceso de recepción parcial comienza cuando existe un **Pedido de compra** que contiene una línea de producto configurada con una AUOM; por ejemplo, 1 caja de zumo de piña equivalente a 12 unidades. -2. Desde la ventana **Recepción de entrada**, el usuario inicia un nuevo registro de recepción usando el botón *Crear líneas desde pedido* y selecciona el Pedido de compra como referencia. El sistema carga automáticamente las líneas del pedido, incluyendo el producto y la cantidad esperada, como 1 caja. -3. A continuación, en la línea de recepción, el usuario modifica la cantidad para reflejar la recepción parcial; por ejemplo, si el pedido es de 1 caja (12 unidades) pero solo se reciben 6 unidades, el usuario cambia la cantidad a 6 y, si es necesario, ajusta la unidad de medida a **unidades** en lugar de **caja**. -4. Una vez ajustada la cantidad real recibida, el usuario completa la recepción pulsando el botón *Completar* en la ventana Recepciones de entrada. -5. En ese momento, el sistema genera y completa el albarán, reflejando la cantidad parcial realmente recibida. El inventario se actualiza con la cantidad recibida. El **Pedido de compra** mostrará el porcentaje recibido en la barra de estado. -## Inspección de calidad de inventario +1. The partial receipt process begins when there is a **Purchase Order** that contains a product line configured with an AUOM, for example, 1 box of pineapple juice equivalent to 12 units. +2. From the **Inbound Receipt** window, the user initiates a new receipt record using the *Create Lines From Order* button and selects the Purchase Order as a reference. The system automatically loads the order lines, including the product and expected quantity, such as 1 box. +3. Then, in the receipt line, the user modifies the quantity to reflect the partial receipt; for example, if the order is for 1 box (12 units) but only 6 units are received, the user changes the quantity to 6 and, if necessary, adjusts the unit of measure to **units** instead of **box**. +4. Once the actual quantity received has been adjusted, the user completes the receipt by pressing the *Complete* button in the Inbound Receipts window. +5. At that point, the system generates and completes the goods receipt, reflecting the partial quantity actually received. The inventory is updated with the quantity received. The **Purchase Order** will show the percentage received in the status bar. -### Visión general +## Inventory Quality Inspection -La ventana **Inspección de calidad de inventario** permite una gestión y control exhaustivos de los procesos de inspección de calidad dentro de las operaciones de almacén. Sirve como una herramienta centralizada para registrar, auditar y ejecutar controles de calidad, manteniendo una trazabilidad completa entre las inspecciones, las tareas de operador asignadas y los movimientos de existencias resultantes. Esta funcionalidad garantiza que los productos cumplan los estándares de calidad antes de ponerse a disposición para la venta o para su posterior procesamiento, evitando que artículos defectuosos o no conformes entren en la cadena de distribución. +### Overview -### Ventana Inspección de calidad de inventario +The **Inventory Quality Inspection** window enables comprehensive management and control of quality inspection processes within warehouse operations. It serves as a centralized tool to register, audit, and execute quality controls, maintaining full traceability between inspections, assigned operator tasks, and resulting stock movements. This functionality ensures that products meet quality standards before being made available for sale or further processing, preventing defective or non-compliant items from entering the distribution chain. -:material-menu: `Aplicación` > `Gestión de Almacén` > `Transacción` > `Inspección de calidad de inventario` +### Inventory Quality Inspection Window -Esta ventana permite a los usuarios crear y gestionar registros de inspección de calidad para artículos de inventario. Las inspecciones pueden realizarse sobre existencias existentes. El sistema realiza el seguimiento de qué productos necesitan inspección, su estado actual, ubicación y las cantidades planificadas para revisión. +:material-menu: `Application` > `Warehouse Management` > `Transaction` > `Inventory Quality Inspection` + +This window allows users to create and manage quality inspection records for inventory items. Inspections can be conducted on existing stock. The system tracks which products need inspection, their current status, location, and the quantities planned for review. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inventory-quality-inspection-window.png) -Campos a tener en cuenta: +Fields to note: -#### Cabecera +#### Header -- **Organización**: Define la organización en la que se creará la inspección de calidad y filtra la información disponible. -- **Nº de documento**: Identificador único generado automáticamente para el documento de inspección, siguiendo una secuencia específica para este tipo de documento. -- **Nombre**: Un nombre descriptivo para el registro de inspección de calidad que ayuda a identificar su propósito o contenido. -- **Fecha de control de calidad**: Fecha en la que la inspección está programada o se realiza. Por defecto, es la fecha actual. -- **Descripción**: Campo de texto libre para añadir información adicional o notas sobre la inspección. +- **Organization**: Defines the organization in which the quality inspection will be created and filters the available information. +- **Document No**: Unique identifier automatically generated for the inspection document, following a specific sequence for this document type. +- **Name**: A descriptive name for the quality inspection record to help identify its purpose or content. +- **Quality Control Date**: Date on which the inspection is scheduled or performed. By default, it is the current date. +- **Description**: Free text field to add additional information or notes about the inspection. -#### Solapa Líneas +#### Lines Tab -La solapa Líneas lista los productos a inspeccionar, incluyendo su estado de inventario actual, ubicación y cantidades planificadas para inspección. Cada línea representa un producto o lote que requiere inspección de calidad. +The Lines tab lists the products to be inspected, including their current inventory status, location, and planned inspection quantities. Each line represents a product or batch that requires quality inspection. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inventory-quality-inspection-lines.png) -Campos a tener en cuenta: +Fields to note: -- **Nivel**: Número secuencial asignado automáticamente para identificar la línea dentro del documento de inspección. -- **Producto**: El producto que se está inspeccionando. -- **Hueco**: Ubicación actual del producto en el almacén. -- **Cantidad teórica**: La cantidad registrada en los registros de inventario del sistema para este producto en la ubicación especificada. -- **Unidad**: Unidad de medida del producto (p. ej., Unidad, Caja, Kg). -- **A estado**: Estado de inventario objetivo que se asignará al producto tras la inspección (p. ej., *Disponible*, *Dañado*, *Bloqueado*). -- **Cant.total**: La cantidad real contada o inspeccionada durante el proceso de control de calidad. -- **Descripción**: Campo de texto libre para añadir notas u observaciones adicionales sobre la línea de inspección. -- **Línea de movimiento**: Referencia a la línea de movimiento de inventario asociada a esta inspección, si aplica. +- **Line No**: Sequential number automatically assigned to identify the line within the inspection document. +- **Product**: The product being inspected. +- **Storage Bin**: Current location of the product in the warehouse. +- **Book Quantity**: The quantity registered in the system's inventory records for this product at the specified location. +- **UOM**: Unit of measure of the product (e.g., Unit, Box, Kg). +- **To State**: Target inventory status to be assigned to the product after inspection (e.g., *Available*, *Damaged*, *Blocked*). +- **Quantity count**: The actual quantity counted or inspected during the quality control process. +- **Description**: Free text field to add additional notes or observations about the inspection line. +- **Movement Line**: Reference to the inventory movement line associated with this inspection, if applicable. -#### Botones +#### Buttons -**Proceso** +**Process** -Procesa el documento de inspección de calidad, validando los datos de inspección y actualizando el inventario en función de los resultados registrados en las líneas. Este botón está disponible cuando el documento de inspección tiene líneas. +Processes the quality inspection document, validating the inspection data and updating the inventory based on the results recorded in the lines. This button is available when the inspection document has lines. -**Generar tarea** +**Generate Task** -Crea una tarea de inspección de calidad que es visible tanto en la ventana **Mantenimiento** en Etendo como en **Etendo Mobile**. Este botón está disponible cuando el documento de inspección tiene líneas cargadas. +Creates a quality inspection task that is visible in both the **Task** window in Etendo and **Etendo Mobile**. This button is available when the inspection document has loaded lines. -Al hacer clic, aparece una ventana emergente donde puede asignar la tarea a un usuario específico o habilitar la asignación automática basada en el rol. Si se seleccionan varios documentos de inspección, se creará una tarea para cada uno, todas asignadas al mismo usuario o rol definido en la ventana emergente. +When clicked, a pop-up window appears where you can assign the task to a specific user or enable automatic assignment based on role. If multiple inspection documents are selected, one task will be created for each, all assigned to the same user or role defined in the pop-up. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inventory-quality-inspection-generate-task.png) -### Flujo de trabajo +### Workflow -El proceso de Inspección de calidad de inventario comienza en Etendo cuando un usuario crea un nuevo registro en la ventana **Inspección de calidad de inventario**. +The Inventory Quality Inspection process begins in Etendo when a user creates a new record in the **Inventory Quality Inspection** window. -1. **Crear documento de inspección**: Se crea un nuevo documento de inspección en la ventana **Inspección de calidad de inventario** con la información necesaria de cabecera (organización, nombre, fecha de control de calidad, descripción). +1. **Create Inspection Document**: A new inspection document is created in the **Inventory Quality Inspection** window with the necessary header information (organization, name, quality control date, description). -2. **Añadir productos a inspeccionar**: Los productos que requieren inspección se añaden a la solapa Líneas. Para cada línea, especifique: - - El producto a inspeccionar - - Ubicación del hueco - - Cantidad teórica (inventario del sistema) - - Cualquier descripción o nota relevante +2. **Add Products to Inspect**: Products requiring inspection are added to the Lines tab. For each line, specify: + - The product to be inspected + - Storage bin location + - Book quantity (system inventory) + - Any relevant descriptions or notes - !!!info "Dos formas de completar la inspección" - En este punto, puede elegir entre dos flujos de trabajo para completar la inspección de calidad: + !!!info "Two Ways to Complete the Inspection" + At this point, you can choose between two workflows to complete the quality inspection: - **Opción 1: Completar desde Etendo (ERP)** - Continúe con los pasos 3 y 4 a continuación para realizar la inspección directamente en la ventana **Inspección de calidad de inventario**. + **Option 1: Complete from Etendo (ERP)** + Continue with steps 3 and 4 below to perform the inspection directly in the **Inventory Quality Inspection** window. - **Opción 2: Completar desde Etendo Mobile** - Utilice el botón **Generar tarea** para crear una tarea de inspección de calidad visible en **Etendo Mobile**. Esto permite a los operarios de almacén realizar la inspección directamente desde sus dispositivos móviles. Para más información, visite [Tareas de inspección de calidad](#tareas-de-inspección-de-calidad). + **Option 2: Complete from Etendo Mobile** + Use the **Generate Task** button to create a quality inspection task visible in **Etendo Mobile**. This allows warehouse operators to perform the inspection directly from their mobile devices. For more information, visit [Quality Inspection Tasks](#quality-inspection-tasks). -3. **Procesar inspección**: - - Revise cada línea de producto y actualice el campo **A estado** con el nuevo estado para las unidades; a continuación, introduzca la **Cant.total** para las unidades que coincidan con ese estado. - - El sistema comparará la Cantidad teórica con la Cant.total para identificar discrepancias. - - Asigne el estado objetivo adecuado en función de los resultados de la inspección. +3. **Process Inspection**: + - Review each product line and update the **To State** field with the new status for the units, then enter the **Quantity count** for the units that match that status. + - The system will compare the Book Quantity with the Quantity count to identify discrepancies. + - Assign the appropriate target status based on inspection results. -4. **Completar la inspección**: Haga clic en el botón **Proceso** para finalizar el documento. El sistema: - - Actualizará el estado de inventario de los productos inspeccionados según el campo **A estado** - - Creará movimientos de inventario que reflejen los resultados de la inspección - - Gestionará la reubicación del producto en función del estado objetivo: - - Si existe una [regla de movimiento](#ventana-de-configuración-de-reglas-de-movimiento) para el estado objetivo, el sistema la aplica automáticamente - - Si no existe una regla de movimiento, el sistema comprueba si ya hay un hueco asignado a ese estado - - Si no se encuentra ningún hueco, el sistema crea un **hueco virtual** para el estado objetivo para mantener la consistencia del inventario - - Actualizará el **Informe Stock** con el nuevo estado de inventario +4. **Complete the Inspection**: Click the **Process** button to finalize the document. The system will: + - Update the inventory status of inspected products according to the **To State** field + - Create inventory movements reflecting the inspection results + - Handle product relocation based on the target status: + - If a [movement rule](#movement-rules-configuration-window) exists for the target status, the system applies it automatically + - If no movement rule exists, the system checks if a storage bin is already assigned to that status + - If no storage bin is found, the system creates a **virtual storage bin** for the target status to maintain inventory consistency + - Update the **Stock Report** with the new inventory status -5. Todos los cambios se reflejan en el sistema, manteniendo una trazabilidad completa del proceso de inspección de calidad. +5. All changes are reflected in the system, maintaining full traceability of the quality inspection process. -!!!warning "Reglas de movimiento y huecos" - Se recomienda configurar [Reglas de movimiento](#ventana-de-configuración-de-reglas-de-movimiento) para los estados de inspección de uso común (p. ej., *Dañado*, *Bloqueado*) para mantener una organización adecuada del almacén. -## Reserva de existencias AUOM +!!!warning "Movement Rules and Storage Bins" + It is recommended to configure [Movement Rules](#movement-rules-configuration-window) for commonly used inspection statuses (e.g., *Damaged*, *Blocked*) to maintain proper warehouse organization. +## AUOM Stock Reservation -### Visión general +### Overview -Se ha añadido la opción de reservas de existencias basadas en la unidad definida en el pedido de venta (campo AUOM), que determina si el producto se vende en su unidad base o en una unidad alternativa (por ejemplo, una sola botella o una caja de 12). +The option of stock reservations based on the unit defined in the sales order (AUOM field) has been added, which determines whether the product is sold in its base unit or in an alternative unit (for example, a single bottle or a box of 12). !!! info - De forma predeterminada, cuando el módulo está instalado, las preferencias `Enable Stock Reservations` y `Enable UOM Management` están habilitadas. Para más detalles, consulte [Stock Logistic Unit - Preference](./stock-logistic-unit.md#preference). + By default, when the module is installed the preferences `Enable Stock Reservations` and `Enable UOM Management` are enabled. For details, see [Stock Logistic Unit - Preference](./stock-logistic-unit.md#preference). -### Flujo de reserva +### Reservation Flow -1. El proceso comienza cuando se crea un **Pedido de venta** con líneas de producto definidas con una Unidad Alternativa de Medida (AUOM) (p. ej., 1 Caja = 24 Unidades). -2. En cada línea, el campo **Reserva de existencias** se establece como *Automático*, por lo que el sistema intenta reservar existencias cuando se confirma el pedido. +1. The process starts when a **Sales Order** is created with product lines defined with an Alternative Unit of Measure (AUOM) (e.g., 1 Box = 24 Units). +2. In each line, the **Stock Reservation** field is set to *Automatic*, so the system attempts to reserve stock when the order is confirmed. ![alt text](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/reservation.png) -3. Lógica de reserva: +3. Reservation logic: - - El sistema reserva existencias en la unidad especificada en la línea del pedido. - - Si hay existencias suficientes, se crea una reserva completa. - - Si no, reserva la cantidad disponible en esa unidad y complementa con otras AUOM o unidades base. - - Si se cubre el total, la reserva es completa; en caso contrario, es parcial. + - The system reserves stock in the unit specified in the order line. + - If there is enough stock, a full reservation is created. + - If not, it reserves the available quantity in that unit and supplements with other AUOMs or base units. + - If the total is covered, the reservation is complete; otherwise, it is partial. ![alt text](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/reservation-1.png) -**Ejemplos** +**Examples** -- Pedido: 10 unidades; Stock: 5 unidades + 1 caja de 10 → Solo se reservan 5 unidades (la caja no se puede dividir). -- Pedido: 110 unidades; Stock: 100 unidades + 1 caja de 10 → Reserva completada con ambas. -- Si no hay stock disponible en la unidad solicitada, el sistema igualmente intenta reservar usando otras AUOM. +- Order: 10 units; Stock: 5 units + 1 box of 10 → Only 5 units reserved (the box cannot be split). +- Order: 110 units; Stock: 100 units + 1 box of 10 → Reservation completed with both. +- If no stock is available in the requested unit, the system still attempts to reserve using other AUOMs. -### Flujo de picking/packing +### Picking/Packing Flow -En los procesos de [Picking](./picking.md) y [Packing](./packing.md). Si los códigos de barras **GS1-128** están configurados, una vez que se ha validado un [código de barras](#código-de-barras), el sistema puede identificar no solo el producto, sino también su unidad alternativa de medida (AUOM) y los atributos asociados, como el lote o la fecha de caducidad. +In the [Picking](./picking.md) and [Packing](./packing.md) processes. If the **GS1-128** barcodes are configured, once a [barcode](#barcode) has been validated, the system can identify not only the product, but also its alternative unit of measure (AUOM) and associated attributes, such as batch or expiration date. -Durante el picking, cuando se escanea el código, el sistema interpreta la información estructurada que contiene (producto, lote, fecha de caducidad, etc.) y la compara con la reserva, registrando directamente la cantidad correspondiente. Esto garantiza que la salida de existencias coincida exactamente con el producto real que se va a preparar. +During picking, when the code is scanned, the system interprets the structured information it contains (product, batch, expiration date, etc.) and compares it with the reservation, directly recording the corresponding quantity. This ensures that the stock output exact matches the actual product to be prepared. -En packing, se utiliza la misma validación al empaquetar productos. El sistema reconoce qué producto es, en qué presentación y con qué atributos, y lo asigna a la caja correspondiente. Esto garantiza que el envío refleje exactamente lo que se ha recogido, manteniendo una trazabilidad completa. +In packing, the same validation is used when packaging products. The system recognizes what product it is, in what presentation and with what attributes, and assigns it to the corresponding box. This ensures that the shipment reflects exactly what was picked, maintaining complete traceability. -De este modo, Etendo garantiza que un único escaneo reconozca de forma integral el producto que está saliendo o va a salir, teniendo en cuenta sus medidas alternativas y atributos, y evitando errores en toda la cadena desde el pedido hasta la expedición. +In this way, the Etendo ensures that a single scan comprehensively recognizes the product that is leaving or will leave, taking into account its alternative measurements and attributes, and avoiding errors throughout the chain from order to dispatch. !!! Example - Ejemplo de código de barras con atributos: **01** 95012345678930 **\x1D** **10**L101 **\x1D** **17** 260910 **91** Rn-0-0-0 + Example of barcode with attributes: **01** 95012345678930 **\x1D** **10**L101 **\x1D** **17** 260910 **91** Rn-0-0-0 + + where: - donde: + - \x1D = separator for variable values + - 01 = product identifier + - 95012345678930 = id product + - 10 = lot identifier + - L101 = lot + - 17 = expiration identifier + - 260910 = expiration date (YYMMDD) + - 91 = locator identifier + - Rn-0-0-0 = logistic unit code - - \x1D = separador para valores variables - - 01 = identificador de producto - - 95012345678930 = id de producto - - 10 = identificador de lote - - L101 = lote - - 17 = identificador de caducidad - - 260910 = fecha de caducidad (YYMMDD) - - 91 = identificador de hueco - - Rn-0-0-0 = código de unidad logística -## Uso de Etendo Mobile +## Using Etendo Mobile -Al iniciar sesión en Etendo Mobile, al operario de almacén se le presentarán las aplicaciones y menús disponibles según su rol. +When logging in to Etendo Mobile, the warehouse operator will be presented with the applications and menus available according to his role. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/advanced-warehouse-management.png) -Como se ha visto anteriormente, la opción de Gestión avanzada de almacén incluye los siguientes menús: +As seen above, the Advanced Warehouse Management option includes the following menus: -- [Mantenimiento de recepción](#mantenimiento-de-recepción) -- [Mantenimiento de picking](#mantenimiento-de-picking) -- [Mantenimiento de empaquetado](#mantenimiento-de-empaquetado) -- [Mantenimiento de reubicación](#mantenimiento-de-reubicación) -- [Mantenimiento de ajuste](#mantenimiento-de-ajuste) -- [Todos los mantenimientos](#todos-los-mantenimientos) -### Tareas de recepción +- [Reception Tasks](#reception-tasks) +- [Picking Tasks](#picking-tasks) +- [Packing Tasks](#packing-tasks) +- [Relocation Tasks](#relocation-tasks) +- [Adjustment Tasks](#adjustment-tasks) +- [All Tasks](#all-tasks) +### Reception Tasks -Permite crear y controlar recepciones directamente desde la aplicación móvil mediante **tareas de recepción**, que reproducen el mismo comportamiento y flujo de proceso que las ventanas [Albarán (Proveedor)](../../../basic-features/procurement-management/transactions/#goods-receipts) y [Recepción de entrada](#recepción-de-entrada) en el ERP. +It allows creating and controlling receipts directly from the mobile application using **receipt tasks**, which reproduce the same behavior and process flow as the [Goods Receipt](../../../basic-features/procurement-management/transactions/#goods-receipts) and [Inbound Receipt](#inbound-receipt) windows in the ERP. -#### Inicio del proceso (Etendo) +#### Process Start (Etendo) -El proceso comienza haciendo clic en el botón **Generar tarea de recepción** en la ventana *Recepción de entrada* del ERP. Allí, la tarea se asigna a un operario, se define la prioridad y, a continuación, se refleja en la aplicación móvil del operario asignado. +The process begins by clicking the **Generate Receiving Task** button in the *Inbound Receipt* window of the ERP. There, the task is assigned to an operator, the priority is defined, and then it is reflected in the mobile application of the assigned operator. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inbound-receipt-popup-1.png) -#### Acceso a las tareas de recepción (Etendo Mobile) +#### Access to Reception Tasks (Etendo Mobile) -Al acceder a **Etendo Mobile** en la sección **Tareas de recepción**, se mostrarán todas las tareas y sus estados correspondientes pertenecientes al usuario que ha iniciado sesión. Por defecto, las tareas se muestran con estado *Pendiente*. +When accessing **Etendo Mobile** in the **Reception Tasks** section, all tasks and their corresponding statuses belonging to the logged-in user will be displayed. By default, tasks are displayed as *Pending* status. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/reception-mobile-1.png) -**Tareas de recepción** +**Reception Tasks** ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/reception-mobile-2.png) -Para realizar una **Recepción**: +To perform a **Reception**: -- Acceda al menú **Tareas de recepción**. Allí, las tareas se dividen por estado: Pendiente, En curso, Completada. -- Busque y seleccione la tarea desde la lista o utilizando el buscador. -- Cuando se selecciona una tarea, se abre una pantalla con la información de la tarea. -- Pulse el botón **Iniciar recepción**. -- **Escanee** los productos para almacenarlos o **cárguelos** manualmente. -- Si el producto tiene un **Conjunto atributos** configurado (como número de lote, número de serie, fecha de caducidad u otros atributos personalizados), aparecerá una ventana emergente solicitando esta información. Complete los campos obligatorios y confirme para continuar con la recepción. +- Access the **Reception Tasks** menu. There, tasks are divided by status: Pending, In Progress, Completed. +- Search for and select the task from the list or using the search engine. +- When a task is selected, a screen with the task information opens. +- Press the **Start Receipt** button. +- **Scan** the products to stock them or **load** them manually. +- If the product has an **Attribute Set** configured (such as batch number, serial number, expiration date or other custom attributes), a pop-up window will appear requesting this information. Complete the required fields and confirm to continue with the reception. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/reception-mobile-3.png) -- Si es necesario, se puede modificar el **hueco (localizador)** para cambiar la ubicación de destino de los productos recibidos. -- Confirme la tarea con el botón **Finalizar recepción**. -- Confirme que desea finalizar la tarea. -- Vea el **Mensaje de éxito**. -### Tareas de picking +- If needed, the **storage bin (locator)** can be modified to change the destination location of the received products. +- Confirm the task with the **End Reception** button. +- Confirm that you want to finish the task. +- See **Success message**. +### Picking Tasks ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/picking-1.png) -El proceso de picking permite al operario recoger de forma eficiente los productos requeridos para un pedido utilizando Etendo Mobile. A continuación se detalla el flujo completo del proceso. +The picking process allows the operator to pick the products required for an order efficiently using Etendo Mobile. The complete process flow is detailed below. !!!Info - Para más información sobre cómo utilizar esta funcionalidad en Etendo, visite [Picking](./picking.md). + For more information about how to use this functionality in Etendo, visit [Picking](./picking.md). -#### Inicio del proceso (Etendo) +#### Process Start (Etendo) -El proceso se inicia en Etendo cuando se crea una [Lista de picking](picking.md#picking-list-generation) a partir de un Pedido de venta. Esto puede realizarse mediante el botón **Generar lista de picking** disponible en la ventana Pedido de venta, que crea una nueva **tarea** que se asignará a un usuario para su ejecución en Etendo Mobile. +The process is started in Etendo when a [Picking List](picking.md#picking-list-generation) is created from a Sales Order. This can be done using the **Generate Picking List** button available in the Sales Order window, which creates a new **task** that will be assigned to a user for execution in Etendo Mobile. !!!Important - Recuerde que las únicas listas de picking que se muestran en Etendo Mobile son las marcadas como tipo **Lista de picking directa al cliente**. + Remember the only picking lists that are shown in Etendo Mobile are those marked as **Direct Picking List to Customer** type. -Cuando se genera una lista de picking, el sistema ejecuta procesos automáticos en segundo plano que varían en función de la configuración. En determinadas situaciones, algunos de estos procesos pueden fallar sin que el usuario lo advierta inmediatamente. +When a picking list is generated, the system runs automatic background processes that vary depending on the configuration. In certain situations, some of these processes can fail without the user noticing immediately. -Para proporcionar una mayor visibilidad, el sistema muestra un **mensaje de advertencia** en diferentes etapas del proceso, que incluye un enlace a la ventana Mantenimiento. Desde allí, el usuario puede comprobar el detalle de cada proceso ejecutado y revisar los logs correspondientes, garantizando un mejor control sobre la correcta finalización de las operaciones. +In order to provide greater visibility, the system displays a **warning message** at different stages of the process, that includes a link to the Task window. From there, the user can check the details of each process executed and review the corresponding logs, ensuring better control over the correct completion of operations. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/message-picking-list-1.png) -Los procesos que deben verificarse son los siguientes: +The processes that must be verified are as follows: -- Para **tareas de picking con creación activa de tarea de packing**: +- For a **Picking tasks with active Packing task creation**: - - Crear albarán de salida - - Crear lista de picking - - Procesar lista de picking - - Crear tarea de packing + - Create Shipment + - Create Picking List + - Process Picking List + - Create Packing Task -- Para **tareas de picking sin crear una tarea de packing**: +- For a **Picking tasks without creating a Packing task**: - - Crear lista de picking - - Crear albarán de salida - - Procesar lista de picking + - Create Picking List + - Create Shipment + - Process Picking List -Ejemplo de logs sin errores: +Example of logs without errors: ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/message-picking-list.png) -Ejemplo de logs con errores: +Example of logs with errors: ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/message-picking-list-error.png) -#### Acceso a las tareas de picking (Etendo Mobile) +#### Access to Picking Tasks (Etendo Mobile) -Al acceder a **Etendo Mobile** en la sección **Picking**, se mostrarán todas las tareas y sus correspondientes estados y prioridades, pertenecientes al usuario que ha iniciado sesión. Por defecto, las tareas se muestran en estado *Pendiente*. +When accessing **Etendo Mobile** into the **Picking** section, all tasks and their corresponding statuses and priorities, belonging to the logged in user, will be displayed. By default, the tasks are shown in *Pending* status. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/picking-2.png){align=right width=300} -Esta pantalla contiene: +This screen contains: -- Botones de Actualizar y Atrás. -- Un campo de búsqueda para filtrar tareas. -- Filtros rápidos que limitan entre tareas `Pendiente`, `En proceso` o `Completada`. -- Una lista de tarjetas con tareas. +- Refresh and Back buttons. +- A search field to filter tasks. +- Quick filters that limit between `Pending`, `In Process` or `Completed` tasks. +- A list of cards with tasks. !!! Note - Tal y como se explicó anteriormente en la sección de la solapa Preferencias de [Configuración inicial](#configuración-inicial), existe una preferencia para definir los días a mostrar las tareas en estado `Completada`: `Task From Date Completed Days`. Esto permite al usuario definir el número de días hacia atrás, desde la fecha actual, que se utilizará como criterio para mostrar tareas en estado Completada. + As explained above in the Preference tab section of [Initial Setup](#initial-setup), there is a preference to define the days to show tasks in `Completed` status: `Task From Date Completed Days`. This allows the user to define the number of days backwards, from the current date, to be used as a criterion for displaying tasks in Completed status.
-#### Picking de productos +#### Product Picking -1. El operario de almacén debe seleccionar una tarea `Pendiente`. +1. The warehouse operator must select a `Pending` task. -2. Una vez seleccionada la tarea, se abre una ventana con la lista de productos a recoger. +2. Once the task is selected, a window opens with the list of products to be picked. -3. Para iniciar el proceso, haga clic en el botón **Iniciar picking** ubicado en la parte superior; una vez hecho esto, la tarea pasa al estado `En curso`. +3. To start the process, click on the **Start Picking** button located at the top; once this is done, the task goes to the `In Progress` status. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/picking-3.png) -4. Una vez iniciado el picking, se abre una nueva ventana con los siguientes elementos: +4. Once picking is started, a new window opens with the following items: ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/picking-4.png){align=right width=300} - - **Escanear código de barras:** activa la cámara del dispositivo móvil. - - **Introducir código de barras:** permite introducir el código de barras manualmente. Hay disponible un botón Validar para lanzar el proceso de validación del código de barras. - - **Cantidad con botones `+` y `-`** permite cargar manualmente la cantidad a escanear. - - **Lista de productos (N):** lista de tarjetas con información del producto, donde (N) es la cantidad total de productos. + - **Scan Barcode:** activates the camera of the mobile device. + - **Type barcode:** allows to enter the barcode manually. A Validate button is available to trigger the barcode validation process. + - **Quantity with: `+` and `-` buttons** allows manual loading of the quantity to be scanned. + - **List of products (N):** list of cards with product information, where (N) is the total quantity of products. - - Producto - - Estado: + - Product + - Status: - - Sin escanear + Unscanned - - Escaneado parcialmente + Partially Scanned - - Escaneado + Scanned - - Código de barras - - Ubicador - - Valor atributos - - Cantidad de movimiento: cantidad total a recoger. + - Barcode + - Locator + - Attribute Set Value + - Movement Quantity: total quantity to be collected. - AUOM - - Cantidad contada con botones `+` y `-`: que permiten sumar o restar, de uno en uno, la cantidad manualmente. + - Counted Quantity with buttons `+` and `-`: that allow to add or subtract one by one the quantity manually. -#### Métodos de picking +#### Picking Methods -En el proceso de picking, el operario tiene flexibilidad tanto en qué recoger como en cómo hacerlo. Por un lado, aunque el sistema solicite un código específico (por ejemplo, caja BX100020), es posible sustituirlo por otra unidad equivalente (como BX100023) siempre que el producto y la cantidad coincidan, o adaptarse a la disponibilidad de stock (por ejemplo, entregar 10 unidades sueltas en lugar de una caja de 10). Estas variaciones se registran automáticamente en la reserva y en el albarán de salida. +In the picking process, the operator has flexibility in both what to pick and how to do it. On the one hand, even if the system requests a specific code (for example, box BX100020), it is possible to replace it with another equivalent unit (such as BX100023) as long as the product and quantity match, or to adapt to stock availability (for example, delivering 10 individual units instead of a box of 10). These variations are automatically recorded in the reservation and on the goods sheepment. -Por otro lado, el sistema también permite flexibilidad en el modo de operación mediante diferentes métodos de selección: +On the other hand, the system also allows flexibility in the mode of operation through different selection methods: -- Escanear el producto el número de veces solicitado (ej.: 10 escaneos para 10 unidades). -- Escanear una unidad logística, que carga automáticamente la cantidad solicitada junto con su equivalente en unidades según la tasa de conversión. -- Cargar manualmente "10" en el campo de cantidad y escanear una vez. -- Introducir tanto el código como la cantidad manualmente. -- Introducir manualmente solo la cantidad en el campo Cantidad dentro de una tarjeta de producto, usando los botones + y - o introduciendo el número desde el teclado. +- Scan the product the requested number of times (ex: 10 scans for 10 units). +- Scan a logistics unit, which automatically loads the requested quantity along with its equivalent in units according to the conversion rate. +- Manually load "10" in the quantity field and scan once. +- Enter both code and quantity manually. +- Manually enter only the quantity in the Quantity field within a product card, using the + and - buttons or by entering the number from the keypad. !!! tip - Al escanear un producto válido, el campo Código de barras se completa automáticamente, se muestra la tarjeta asociada y se incrementa el valor 1 en el producto, si la cantidad no se había modificado previamente. + When scanning a valid product, the Barcode field is automatically filled in, the associated card is displayed and the value 1 is incremented in the product, if the quantity was not previously changed. !!! tip - Si previamente se introdujo en el campo Cantidad una cantidad distinta de la cantidad por defecto, por ejemplo 5, y luego se escanea el producto, esas 5 unidades se añadirán directamente a la tarjeta del producto. + If a quantity other than the default quantity, e.g. 5, was previously entered in the Quantity field, and then the product is scanned, those 5 units will be added directly to the product card. !!! Warning ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/picking-5.png){align=right width=200} - Posibles escenarios de error: + Possible error scenarios: - - Si se escanea un código incorrecto (no coincide con ningún producto de la tarea), el campo de código de barras se resalta en rojo, muestra una cruz y no añade cantidad a ningún producto.

- - Si se intenta introducir una cantidad superior a la requerida, el sistema cargará el máximo definido en la tarjeta del producto. Una vez completada la cantidad y se vuelve a escanear o recargar el código del producto, el sistema no añade cantidad al producto. Si la cantidad se carga manualmente en la tarjeta del producto, el sistema permite cargar la cantidad máxima solicitada. + - If an incorrect code is scanned (does not match any product in the task), the barcode field is highlighted in red, shows a cross and does not add quantity to any product.

+ - If an attempt is made to enter a quantity greater than required, the system will charge the maximum defined in the product card. Once the quantity is completed and the product code is re-scanned or reloaded, the system does not add quantity to the product. If the quantity is manually loaded into the product card, the system allows loading the maximum quantity requested. - En ambos casos, el mensaje de error mostrado es el que se visualiza en la imagen. + In both cases, the error message shown is the one displayed in the image. -#### Finalización del picking +#### Picking Completion -Una vez que se registra al menos una unidad de cualquier producto, el botón **Finalizar picking** se activa. Esto permite el picking parcial, es decir, solo se puede recoger parte de la cantidad solicitada, lo cual resulta útil cuando faltan productos o no son aptos para su uso. +Once at least one unit of any product is registered, the **End Picking** button becomes active. This allows partial picking, meaning only part of the requested quantity can be picked, which is useful when products are missing or unsuitable for use. -Tras la confirmación, la tarea se marca como Completada. +After confirmation, the task is marked as Completed. !!!warning - Para el picking parcial, la tarea se cierra y no se crea automáticamente una nueva tarea para los productos faltantes. Cualquier cantidad restante debe gestionarse manualmente. + For partial picking, the task is closed, and no new task is automatically created for the missing products. Any remaining quantities must be handled manually. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/picking-6.png) -Una vez completada, la tarea aparecerá en la sección de Tareas completadas, donde es posible revisar los productos y cantidades validados para esa tarea de picking específica. +Once completed, the task will appear in the Completed Tasks section, where it is possible to review the validated products and quantities for that specific picking task. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/picking-7.png) -### Tareas de empaquetado + + +### Packing Tasks ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/packing-mobile-1.png) -El proceso de empaquetado permite al operario empaquetar los productos de forma eficiente utilizando Etendo Mobile. A continuación se detalla el flujo completo del proceso. +The packing process allows the operator to pack the products efficiently using Etendo Mobile. The complete process flow is detailed below. !!!Info - Para más información sobre cómo utilizar esta funcionalidad en Etendo, visite [Empaquetado](./packing.md). + For more information about how to use this functionality in Etendo, visit [Packing](./packing.md). -#### Inicio del proceso (Etendo) +#### Process Start (Etendo) -Las tareas de empaquetado están vinculadas a un registro en la ventana **Empaquetado**. La creación de una tarea de empaquetado se desencadena tras: +Packing tasks are linked to a record in the **Packing** window. The creation of a packing task is triggered after: -- La finalización de una tarea de picking (cuando el Tipo de tarea `Picking and Packing` está activo). -- Desde la ventana **Empaquetado** de Etendo al añadir al menos un pedido de venta a un nuevo Empaquetado. +- The completion of a picking task (when the Task Type `Picking and Packing` is active). +- From the **Packing** window of Etendo when adding at least one sales order to a new Packing. -#### Acceso a las tareas de empaquetado (Etendo Mobile) +#### Access to Packing Tasks (Etendo Mobile) ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/packing-mobile-2.png){align=right width=300} -Al acceder a Etendo Mobile y seleccionar el menú **Empaquetado**, se muestra la pantalla principal de empaquetado con el número de tareas `Empaquetado` disponibles para el usuario actual. -Esta pantalla contiene: +When accessing Etendo Mobile and selecting the **Packing** menu, the packing main screen with the number of available `Packing` tasks to the current user. + +This screen contains: -- Botones de Actualizar y Atrás. -- Un campo de búsqueda para filtrar tareas. -- Filtros rápidos que limitan entre tareas `Pendiente`, `En progreso` o `Completada`. Por defecto, muestra seleccionado el filtro `Pendiente` y, en el caso de tareas en estado `Completada`, existe una preferencia donde se define desde qué día se traerán las tareas completadas. -- Una lista de tarjetas, donde cada tarjeta representa una tarea de empaquetado e incluye la siguiente información: +- Refresh and Back buttons. +- A search field to filter tasks. +- Quick filters that limit between `Pending`, `In Progress` or `Completed` tasks. By default it shows the `Pending` filter selected, and in the case of tasks in `Completed` status, there is a preference where it is defined from which day it will bring completed tasks. +- A list of cards, where each card represents a packing task and includes the following information: - - Empaquetado como título: se muestra la referencia del documento. - - Estado. - - Tipo de tarea. - - Prioridad. + - Packing as title: The document reference is shown. + - Status. + - Task Type. + - Priority.
-#### Empaquetado de productos +#### Product Packing -1. El operario de almacén debe **seleccionar una tarea**. Para seleccionar la tarea, desplácese o introduzca datos clave en el buscador. +1. The warehouse operator must **select a task**. To select the task, scroll or enter key data in the search engine. -2. Al seleccionar una tarea, se abre una pantalla con el número de la lista de empaquetado y el botón **Iniciar empaquetado**. +2. When selecting a task, a screen opens with the packing list number and the **Start Packing** button. -3. Al pulsar **Iniciar empaquetado**, el estado de la tarea cambia a `En progreso` tanto en Etendo Mobile como en Etendo. +3. When pressing **Start Packing**, the status of the task changes to `In Progress` in both Etendo Mobile and Etendo. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/packing-mobile-3.png) -4. La ventana tiene los siguientes elementos: +4. The window has the following elements: - - Botón **Escanear código de barras** para activar la cámara del dispositivo y escanear. - - **Introducir código de barras** permite introducir el código de barras manualmente. Hay disponible un botón Validar para lanzar el proceso de validación del código de barras. - - Campo **Seleccionar paquete** para seleccionar el paquete de destino al escanear el producto. - - Campo **Cantidad** que actúa como multiplicador para cargar la cantidad al escanear el producto. - - Botón **+ Añadir paquete** que permite añadir nuevas cajas. - - Una lista de tarjetas de **Producto**, cada una mostrando: + - **Scan Barcode** button to activate the device camera and scan. + - **Type barcode** allows to enter the barcode manually. A Validate button is available to trigger the barcode validation process. + - **Select Pack** field to select the destination pack when scanning the product. + - **Quantity** field that acts as a multiplier to load the quantity when scanning the product. + - **+ Add Pack** button that allows you to add new boxes. + - A list of **Product** cards, each showing: - - Producto - - Estado: + - Product + - Status: - - Sin escanear + Unscanned - - Escaneando + Scanning - - Escaneado + Scanned - - Código de barras - - Localizador - - Valor atributos - - Cantidad + - Barcode + - Locator + - Attribute Set Value + - Quantity - AUOM - - Cantidad empaquetada con botones `+` y `-`: que permiten añadir o restar, uno a uno, la cantidad manualmente. + - Packed Quantity with buttons `+` and `-`: that allow to add or subtract one by one the quantity manually. - - Una lista de **Paquetes**, mostrando: + - A list of **Packs**, showing: - - Nombre (o número) del paquete - - Productos y sus cantidades + - Pack name (or number) + - Products and their quantities ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/packing-mobile-4.png) - Los selectores de vista por **Producto** o por **Paquete** permiten: - - En la vista **Productos**, al entrar en una tarjeta de producto, se muestra cómo se distribuyó ese producto en las diferentes cajas, permitiendo navegar producto por producto para revisar las cantidades asignadas por paquete. + The view selectors by **Product** or by **Pack** allow: - - En la vista **Paquetes**, al entrar en un paquete, se muestra el contenido detallado con la posibilidad de navegar paquete por paquete para comprobar qué productos contiene cada paquete. + - In the **Products** view, when entering a product card, it shows how that product was distributed in the different boxes, allowing you to browse product by product to review the quantities assigned per pack. + + - In the **Packs** view, when entering a pack, the detailed contents are displayed with the possibility of browsing pack by pack to check which products are contained in each pack. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/packing-mobile-5.png) !!! tip - En ambas vistas, es posible modificar las cantidades cargadas y añadir paquetes si fuese necesario. Sin embargo, para poder asignar contenido a las cajas añadidas, debe cumplirse una de las siguientes condiciones: + In both views, it is possible to modify the quantities loaded and add packs if necessary. However, in order to be able to assign content to the added boxes, one of the following conditions must be met: - - La carga total de productos aún no se ha completado, o se modifican (disminuyen) cantidades asignadas previamente para permitir su reubicación al nuevo paquete. + - The total load of products has not yet been completed, or previously assigned quantities are modified (decreased) to allow their relocation to the new pack. -5. Una vez iniciado el empaquetado, el usuario selecciona o crea un paquete y comienza a cargar productos escaneando o introduciendo los datos manualmente. +5. Once packing is started, the user selects or creates a pack and starts loading products by scanning or manually entering data. - - Cada producto empaquetado se registra bajo un paquete específico. - - Puede alternar entre cajas para distribuir los productos según sea necesario. + - Each packed product is registered under a specific pack. + - You can switch between boxes to distribute products as needed. !!!Info - Los paquetes recién creados no pueden eliminarse manualmente. Sin embargo, si un paquete se deja vacío (sin productos añadidos), se eliminará automáticamente al final del proceso. Solo se guardarán y mostrarán los paquetes con productos empaquetados. + Newly created packs cannot be deleted manually. However, if a pack is left empty (no products added), it will be automatically removed at the end of the process. Only packs with packed products will be saved and displayed. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/packing-mobile-6.png) -#### Métodos de empaquetado -Durante el proceso de empaquetado, el operario debe ceñirse estrictamente a lo que debe recogerse, es decir, solo puede escanear los códigos de barras listados en el documento de empaquetado. No está permitido sustituir unas cajas por otras ni cambiar unidades logísticas, ya que los productos ya han sido reservados durante el picking y el empaquetado debe reflejar exactamente lo solicitado. +#### Packing Methods + +During the packing process, the operator must strictly adhere to what is to be picked, i.e., they can only scan the barcodes listed on the packing document. It is not permitted to substitute boxes for others or change logistics units, as the products have already been reserved during picking and the packing must reflect exactly what was requested. -En cuanto a cómo realizar el empaquetado, el sistema ofrece flexibilidad en los métodos operativos: +In terms of how to perform packing, the system offers flexibility in operating methods: -- Escanear el producto el número exacto de veces (p. ej.: 10 escaneos para 10 unidades). -- Cargar la cantidad manualmente en el campo Cantidad y luego escanear el producto. +- Scan the product the exact number of times (ex: 10 scans for 10 units). +- Load the amount manually in the Quantity field and then Scan the product. -- Introducir tanto la cantidad como el código manualmente y, a continuación, pulsar el botón Validar para confirmar la entrada. +- Enter both quantity and code manually, and then press the Validate button to confirm the entry. -- Introducir la cantidad manualmente desde la vista **Producto** o desde la vista **Paquetes**. +- Enter the quantity manually from the **Product** view or from the **Packs** view. !!! Warning - Posibles escenarios de error: + Possible error scenarios: ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/packing-mobile-7.png){align=right width=200} - - Si se escanea un código incorrecto (no coincide con ningún producto de la tarea), el campo de código de barras se resalta en rojo, muestra una cruz y no añade cantidad a ningún producto. - - Si se intenta introducir más cantidad de la requerida, también se muestra un mensaje de error. Si la cantidad se carga manualmente en la tarjeta de producto, el sistema permite cargar la cantidad máxima solicitada. + - If an incorrect code is scanned (does not match any product in the task), the barcode field is highlighted in red, shows a cross and does not add quantity to any product. + - If an attempt is made to enter more than the required quantity, an error message is also displayed. If the quantity is manually loaded into the product card, the system allows loading the maximum quantity requested. - En ambos casos, el mensaje de error mostrado es el que aparece en la imagen. + In both cases, the error message shown is the one displayed in the image. -#### Finalización del empaquetado +#### Packing Completion -Una vez que los productos han sido empaquetados: +Once the products have been packed: -- El sistema muestra un resumen por paquete con los productos incluidos y se muestra el mensaje *Empaquetado completado correctamente*. +- The system displays a summary per pack with the products included and the message *Packing completed successfully* is displayed. -- Hasta que se confirme, el contenido de las cajas puede editarse. +- Until confirmed, the contents of the boxes can be edited. -- Al final, puede elegir calcular el peso de las cajas. +- At the end, you can choose to calculate the weight of the boxes. -- Tras la confirmación, la tarea se marca como Completada. +- After confirmation, the task is marked as Completed. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/packing-mobile-8.png) -Una vez completada, la tarea aparecerá en la sección de Tareas completadas. Desde ahí, es posible revisar toda la información validada para esa tarea de empaquetado, incluyendo: +Once completed, the task will appear in the Completed Tasks section. From there, it is possible to review all validated information for that packing task, including: -- En la vista Producto: en qué cajas se empaquetó cada producto. -- En la vista Paquete: qué productos se empaquetaron en cada paquete. +- In the Product view: which boxes each product was packed into. +- In the Pack view: which products were packed into each pack. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/packing-mobile-9.png) -### Tareas de reubicación +### Relocation Tasks -Las tareas de reubicación permiten mover productos desde su ubicación original hasta su ubicación de destino dentro del mismo almacén. Cada tarea se muestra en formato de tarjeta, donde se puede confirmar o ajustar la cantidad movida y la ubicación de destino. La información introducida se sincroniza con el ERP al final de la tarea, garantizando la coherencia entre el movimiento registrado y el stock. +Relocation tasks allow products to be moved from their original location to their destination within the same warehouse. Each task is displayed in card format, where the quantity moved and the destination location can be confirmed or adjusted. The information entered is synchronized with the ERP at the end of the task, ensuring consistency between the recorded movement and the stock. !!!Info - Para más información sobre cómo utilizar esta funcionalidad en Etendo, visite [Movimiento entre almacenes](../../../basic-features/warehouse-management/transactions.md#goods-movement). + For more information about how to use this functionality in Etendo, visit [Goods Movements](../../../basic-features/warehouse-management/transactions.md#goods-movement). -#### Inicio del proceso (Etendo) +#### Process Start (Etendo) -:material-menu: `Aplicación` > `Gestión de Almacén` > `Transacciones` > `Movimiento entre almacenes` +:material-menu: `Application` > `Warehouse Management` > `Transactions` > `Goods Movement` -El proceso de reubicación comienza en el ERP desde el botón **Generar tarea de reubicación** en la ventana de Movimiento entre almacenes. +The relocation process begins in the ERP from the **Generate Relocation Task** button in the Goods Movements window. -Permite al responsable crear una tarea de reubicación a partir del documento **Movimiento entre almacenes**. El sistema toma la información cargada en el registro y sus líneas y la envía a la aplicación móvil, donde el operario puede ejecutar el movimiento desde la subaplicación correspondiente. Al pulsarlo, se abre un pop-up para asignar la tarea de forma manual o automática y definir su prioridad. +Allows the manager to create a relocation task from the **Goods Movement** document. The system takes the information loaded in the record and its lines and sends it to the mobile application, where the operator can execute the movement from the corresponding sub-application. When pressed, a pop-up opens to assign the task manually or automatically and define its priority. ![alt text](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/generate-relocation-task.png) -El uso del botón **Generar tarea de reubicación** está sujeto a una validación del sistema que determina su disponibilidad. Solo se muestra cuando el documento *Movimiento entre almacenes* no ha sido procesado y no tiene ya una tarea asignada. +Use of the **Generate Relocation Task** button is subject to system validation that determines its availability. It is only displayed when the *Goods Movement* document has not been processed and does not have a task already assigned to it. -#### Acceso a las tareas de reubicación (Etendo Mobile) +#### Access to Relocation Tasks (Etendo Mobile) -Al acceder a Etendo Mobile en la sección Tareas de reubicación, se mostrarán todas las tareas y sus correspondientes estados y prioridades pertenecientes al usuario que ha iniciado sesión. Por defecto, las tareas se muestran como Pendiente. +When accessing Etendo Mobile in the Relocation Tasks section, all tasks and their corresponding statuses and priorities belonging to the logged-in user will be displayed. By default, tasks are displayed as Pending. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/relocation-tasks-1.png) -Para realizar una **reubicación**: +To perform a **relocation**: -- Acceda al menú **Tareas de reubicación**. Allí, las tareas se dividen por estado: *Pendiente*, *En curso*, *Completada*. -- Busque y seleccione la tarea desde la lista o utilizando el buscador. -- Cuando se selecciona una tarea, se abre una pantalla con la información de la tarea. -- Pulse el botón **Iniciar reubicación**. -- Complete el campo **Cantidad contada**. -- Complete el campo **Hueco destino**. (Opcional) -- Confirme la tarea con el botón **Finalizar reubicación**. -- Confirme que desea finalizar la tarea. -- Vea el mensaje de éxito. +- Access the **Relocation Tasks** menu. There, tasks are divided by status: *Pending*, *In Progress*, *Completed*. +- Search for and select the task from the list or using the search engine. +- When a task is selected, a screen with the task information opens. +- Press the **Start Relocation** button. +- Complete **Counted Quantity** field. +- Complete **To Locator** field. (Optional) +- Confirm the task with the **End Relocation** button. +- Confirm that you want to finish the task. +- See Success message. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/relocation-tasks-2.png) -### Mantenimiento de ajuste +### Adjustment Tasks -Las tareas de ajuste de inventario permiten a los operarios de almacén realizar recuentos físicos y ajustes de existencias directamente desde la aplicación móvil. Estas tareas se generan a partir de inventarios físicos en el sistema ERP. +Inventory adjustment tasks allow warehouse operators to perform physical counts and stock adjustments directly from the mobile app. These tasks are generated from physical inventories in the ERP system. -Esta funcionalidad corresponde a la misma operación realizada en la ventana **Inventario físico** de Etendo: registrar la cantidad real contada de un producto y actualizar las existencias en consecuencia, ya sea corrigiendo cantidades existentes o introduciendo existencias donde no había previamente. Cuando el estado de inventario cambia durante el proceso de ajuste, el sistema mueve automáticamente el/los producto(s) a los huecos asociados al nuevo estado, reflejando con precisión la condición actual de las existencias. +This functionality corresponds to the same operation performed in Etendo's **Physical Inventory** window: recording the actual counted quantity of a product and updating the stock accordingly, either by correcting existing quantities or entering stock where there was none previously. When the inventory status changes during the adjustment process, the system automatically moves the product(s) to the storage bins associated with the new status, accurately reflecting the current stock condition. !!!Info - Para más información sobre cómo utilizar esta funcionalidad en Etendo, visite [Inventario físico](../../../basic-features/warehouse-management/transactions.md#physical-inventory). + For more information about how to use this functionality in Etendo, visit [Physical Inventory](../../../basic-features/warehouse-management/transactions.md#physical-inventory). -#### Inicio del proceso (Etendo) +#### Process Start (Etendo) -:material-menu: `Aplicación` > `Gestión de Almacén` > `Transacciones` > `Inventario físico` +:material-menu: `Application` > `Warehouse Management` > `Transactions` > `Physical Inventory` -El proceso comienza creando tareas dentro de Etendo usando la ventana **Inventario físico**. Se crea un nuevo registro con líneas de producto para las que se desea la verificación y el ajuste de existencias. Una vez listo, debe generarse la tarea mediante el botón **Generar tarea**. +The process begins by creating tasks within Etendo using the **Physical Inventory** window. A new record is created with product lines for which stock verification and adjustment is desired. Once this is ready, the task must be generated using the **Generate Task** button. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inventory-task-window-1.png) -#### Acceso a las tareas de ajuste (Etendo Mobile) +#### Access to Adjustment Tasks (Etendo Mobile) -Al acceder a Etendo Mobile en la sección de Tareas de ajuste, se mostrarán todas las tareas y sus correspondientes estados y prioridades, pertenecientes al usuario que ha iniciado sesión. Por defecto, las tareas se muestran en estado *Pendiente*. +When accessing Etendo Mobile into the Adjustment Tasks section, all tasks and their corresponding statuses and priorities, belonging to the logged in user, will be displayed. By default, the tasks are shown in *Pending* status. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inventory-tasks-mobile.png) -Para **Ajustar** el inventario +To **Adjust** inventory -- Desde el menú principal de Etendo Mobile, navegue hasta la sección **Tareas de ajuste**. Las tareas se organizan por estado: *Pendiente*, *En curso* y *Completada*. -- Busque y seleccione la tarea deseada de la lista o utilizando la función de búsqueda. -- Al seleccionar una tarea, se abre una pantalla que muestra la información de la tarea. -- Pulse el botón **Iniciar ajuste** para comenzar el proceso. -- Introduzca la información relevante, incluidos los detalles del hueco y los recuentos de cantidad. -- Escanee los productos para registrarlos o introduzca los datos manualmente. -- Confirme la tarea pulsando el botón **Finalizar ajuste**. -- Confirme que desea completar la tarea. +- From the Etendo Mobile main menu, navigate to the **Adjustment Tasks** section. Tasks are organized by status: *Pending*, *In Progress*, and *Completed*. +- Search for and select the desired task from the list or using the search function. +- When a task is selected, a screen opens displaying the task information. +- Press the **Start Adjustment** button to begin the process. +- Enter relevant information including storage bin details and quantity counts. +- Scan products to stock them or manually enter the data. +- Confirm the task by pressing the **End Adjustment** button. +- Confirm that you want to complete the task. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inventory-tasks-status-1.png) -### Mantenimiento de inspección de calidad +### Quality Inspection Tasks -Las tareas de inspección de calidad permiten a los operarios de almacén realizar la verificación de calidad del producto directamente desde Etendo Mobile. Estas tareas permiten a los operarios inspeccionar la mercancía, registrar los resultados de la inspección y actualizar el estado del inventario en función de las condiciones del producto, garantizando que solo los artículos aprobados por calidad estén disponibles para la venta o para su posterior procesamiento. +Quality inspection tasks enable warehouse operators to perform product quality verification directly from Etendo Mobile. These tasks allow operators to inspect merchandise, record inspection results, and update inventory status based on product conditions, ensuring that only quality-approved items are available for sale or further processing. !!!Info - Para más información sobre cómo utilizar esta funcionalidad en Etendo, visite [Inspección de calidad de inventario](#inspección-de-calidad-de-inventario). + For more information about how to use this functionality in Etendo, visit [Inventory Quality Inspection](#inventory-quality-inspection). -#### Inicio del proceso (Etendo) +#### Process Start (Etendo) -El proceso comienza en Etendo creando tareas desde la ventana **Inspección de calidad de inventario**. Tras crear un documento de inspección con líneas de producto que requieren verificación de calidad, utilice el botón **Generar tarea** para crear una tarea móvil. +The process begins in Etendo by creating tasks from the **Inventory Quality Inspection** window. After creating an inspection document with product lines requiring quality verification, use the **Generate Task** button to create a mobile task. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/inventory-quality-inspection-generate-task.png) -#### Acceso a las tareas de inspección de calidad (Etendo Mobile) +#### Access to Quality Inspection Tasks (Etendo Mobile) -Al acceder a Etendo Mobile en la sección **Mantenimiento de inspección de calidad**, se mostrarán todas las tareas y sus estados correspondientes pertenecientes al usuario que ha iniciado sesión. Por defecto, las tareas se muestran en estado *Pendiente*. +When accessing Etendo Mobile in the **Quality Inspection Tasks** section, all tasks and their corresponding statuses belonging to the logged-in user will be displayed. By default, tasks are shown in *Pending* status. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/quality-inspection-task-mobile-0.png) -Para realizar una **inspección de calidad**: +To perform a **quality inspection**: -1. Desde el menú principal de Etendo Mobile, navegue hasta la sección **Mantenimiento de inspección de calidad**. Las tareas se organizan por estado: *Pendiente*, *En curso* y *Completada*. +1. From the Etendo Mobile main menu, navigate to the **Quality Inspection Tasks** section. Tasks are organized by status: *Pending*, *In Progress*, and *Completed*. -2. Busque y seleccione la tarea deseada de la lista o utilizando la función de búsqueda. +2. Search for and select the desired task from the list or using the search function. -3. Al seleccionar una tarea, se abre una pantalla que muestra la información de la tarea y las líneas de producto a inspeccionar. +3. When a task is selected, a screen opens displaying the task information and product lines to be inspected. -4. Pulse el botón **Iniciar inspección** para comenzar el proceso de control de calidad. +4. Press the **Start Inspection** button to begin the quality control process. -5. Los productos pueden escanearse utilizando el lector de códigos de barras o introducirse manualmente. Para cada línea de producto, complete los detalles de la inspección: - - Seleccione el **Estado destino** (estado objetivo según los resultados de la inspección: *Disponible*, *Dañado*, *Bloqueado*, etc.) - - Verifique el producto y sus atributos (lote, fecha de caducidad, etc.) - - Introduzca la **Cant.total** (cantidad real inspeccionada) - - Opcionalmente, añada notas o motivos de rechazo en el campo **Descripción** +5. Products can be scanned using the barcode scanner or entered manually. For each product line, complete the inspection details: + - Select the **To State** (target status based on inspection results: *Available*, *Damaged*, *Blocked*, etc.) + - Verify the product and its attributes (batch, expiration date, etc.) + - Enter the **Quantity count** (actual quantity inspected) + - Optionally, add notes or rejection reasons in the **Description** field -6. Una vez inspeccionados todos los productos, confirme la tarea pulsando el botón **Finalizar inspección**. +6. Once all products have been inspected, confirm the task by pressing the **End Inspection** button. -7. Confirme que desea completar la tarea. +7. Confirm that you want to complete the task. -8. Se mostrará un mensaje de éxito y los resultados de la inspección se sincronizarán con Etendo. +8. A success message will be displayed, and the inspection results will be synchronized with Etendo. ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/quality-inspection-task-mobile-1.png) !!!note - Cuando se completa la inspección, el sistema actualiza automáticamente el estado del inventario y aplica las [Reglas de movimiento](#ventana-de-configuración-de-reglas-de-movimiento) si están configuradas. Los productos marcados con un estado diferente se reubicarán en consecuencia, o se creará un hueco de almacenamiento virtual si no se ha definido una ubicación específica para ese estado. -### Todas las tareas + When the inspection is completed, the system automatically updates inventory status and applies [Movement Rules](#movement-rules-configuration-window) if configured. Products marked with a different status will be relocated accordingly, or a virtual storage bin will be created if no specific location is defined for that status. + +### All Tasks ![](../../../../../assets/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management/all-tasks.png) -Desde esta ventana puede ver y trabajar con todos los tipos de tareas, como Picking, Packing y tareas de inventario. +From this window you can view and work with all types of tasks, like Picking, Packing and Inventory Tasks. --- diff --git a/docs/es/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md b/docs/es/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md index ddfe98583b..7d1edfb9cd 100644 --- a/docs/es/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md +++ b/docs/es/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md @@ -88,7 +88,7 @@ Esta funcionalidad forma parte de Warehouse Extensions Bundle y es útil cuando Para más información, visite la guía de usuario de: - [Movimiento entre almacenes](../../../../../user-guide/etendo-classic/basic-features/warehouse-management/transactions.md#how-to-reactivate-goods-movements) - - [Albarán (Proveedor)](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#how-to-reactivate-goods-receipts) + - [Albarán (Proveedor)](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md) - [Albarán (Cliente)](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#how-to-reactivate-goods-shipments) - [Inventario físico](../../../../../user-guide/etendo-classic/basic-features/warehouse-management/transactions.md#how-to-reactivate-physical-inventories) @@ -124,7 +124,7 @@ Este módulo le permite configurar si el sistema permite transacciones de materi La preferencia **Permitir transacciones de coste con fecha anterior** se establece en **Y** por defecto, lo que significa que se permiten transacciones con fechas anteriores a la fecha actual. -Cuando la preferencia se establece en **N**, los siguientes documentos estarán restringidos a utilizar únicamente la fecha actual: [Albarán (Proveedor)](../../../basic-features/procurement-management/transactions.md#goods-receipts), [Albarán (Cliente)](../../../basic-features/sales-management/transactions.md#goods-shipment), [Movimiento entre almacenes](../../../basic-features/warehouse-management/transactions.md#goods-movement), [Inventarios físicos](../../../basic-features/warehouse-management/transactions.md#physical-inventory), [Parte de Trabajo](../../../basic-features/production-management/transactions.md#work-effort) y [Consumo interno](../../../basic-features/production-management/transactions.md#internal-consumption). +Cuando la preferencia se establece en **N**, los siguientes documentos estarán restringidos a utilizar únicamente la fecha actual: [Albarán (Proveedor)](../../../basic-features/procurement-management/transactions/goods-receipt.md), [Albarán (Cliente)](../../../basic-features/sales-management/transactions.md#goods-shipment), [Movimiento entre almacenes](../../../basic-features/warehouse-management/transactions.md#goods-movement), [Inventarios físicos](../../../basic-features/warehouse-management/transactions.md#physical-inventory), [Parte de Trabajo](../../../basic-features/production-management/transactions.md#work-effort) y [Consumo interno](../../../basic-features/production-management/transactions.md#internal-consumption). !!! warning Si necesita crear una nueva configuración para esta preferencia, debe establecerse únicamente a nivel global, sin distinguir ningún nivel de visibilidad específico (Organización, Usuario, Rol, etc.), ya que podría afectar al correcto funcionamiento de la validación. diff --git a/docs/es/whats-new/etendo-news.md b/docs/es/whats-new/etendo-news.md index 92a7d43e3e..4ef5106ab4 100644 --- a/docs/es/whats-new/etendo-news.md +++ b/docs/es/whats-new/etendo-news.md @@ -461,6 +461,7 @@ tags: - Documentación: [Advanced Warehouse Management](../user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management.md) + ## Agosto 2025 ### Financial Extensions @@ -631,7 +632,7 @@ tags: --- - ![alt text](../assets/whats-new/etendo-news/packing.png){ width=500 align="right"} + ![](../assets/whats-new/etendo-news/packing.png){ width=500 align="right"} En la versión [1.12.0](./release-notes/etendo-classic/bundles/warehouse-extensions/release-notes.md) del bundle Warehouse Extensions, desbloquee operaciones de almacén sin fricciones con el módulo [Advanced Warehouse Management](../user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/advanced-warehouse-management.md), una subaplicación móvil repleta de funcionalidades que se integra en profundidad con Etendo Mobile para ofrecer trazabilidad completa y operaciones de almacén automatizadas. @@ -652,7 +653,7 @@ tags:
- :octicons-rocket-24: **¡Nueva versión de Etendo: ya está disponible la versión 25.1!** - + --- @@ -667,13 +668,13 @@ tags: - :octicons-rocket-24: **Nuevos estados de envío y facturación en los pedidos de compra y albaranes (proveedor)** --- - Esta versión introduce una visibilidad mejorada en los procesos de aprovisionamiento. En la ventana [Pedido de compra](../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#purchase-order), la barra de estado ahora muestra los porcentajes de envío y facturación. A nivel de línea, verá cantidades detalladas de lo que se ha facturado y enviado. - Del mismo modo, la ventana [Albarán (Proveedor)](../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#goods-receipts) muestra los porcentajes de facturación tanto a nivel de cabecera como de línea. + Esta versión introduce una visibilidad mejorada en los procesos de aprovisionamiento. En la ventana [Pedido de compra](../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md), la barra de estado ahora muestra los porcentajes de envío y facturación. A nivel de línea, verá cantidades detalladas de lo que se ha facturado y enviado. + Del mismo modo, la ventana [Albarán (Proveedor)](../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md) muestra los porcentajes de facturación tanto a nivel de cabecera como de línea. - :octicons-rocket-24: **Excluya promociones y descuentos fácilmente con una simple casilla de verificación** --- - Una nueva casilla de verificación en la sección *Más información* de las líneas de [Pedido de venta](../user-guide/etendo-classic/basic-features/sales-management/transactions.md#lines_1) y [Factura (Cliente)](../user-guide/etendo-classic/basic-features/sales-management/transactions.md#lines_5) permite a los usuarios **cancelar descuentos y promociones automáticos**. Esto le ofrece un mayor control sobre los precios a nivel de línea. + Una nueva casilla de verificación en la sección *Más información* de las líneas de [Pedido de venta](../user-guide/etendo-classic/basic-features/sales-management/transactions.md#lines_1) y [Factura (Cliente)](../user-guide/etendo-classic/basic-features/sales-management/transactions/return-to-vendor.md) permite a los usuarios **cancelar descuentos y promociones automáticos**. Esto le ofrece un mayor control sobre los precios a nivel de línea. - :octicons-rocket-24: **Navegación mejorada en el proceso Crear facturas desde pedidos** @@ -683,9 +684,10 @@ tags: - :octicons-rocket-24: **Anulación mejorada de la Factura (Proveedor) con referencia del proveedor** --- - Al anular una Factura (Proveedor), Etendo crea un documento inverso que ahora referencia el documento de anulación del proveedor. El proceso de [reactivación de factura](../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#reactivate) incluye un nuevo campo `Referencia del proveedor` para garantizar una trazabilidad clara y la alineación. + Al anular una Factura (Proveedor), Etendo crea un documento inverso que ahora referencia el documento de anulación del proveedor. El proceso de [reactivación de factura](../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) incluye un nuevo campo `Referencia del proveedor` para garantizar una trazabilidad clara y la alineación.
+ ## Abril 2025 ### Etendo @@ -729,6 +731,7 @@ tags: + ## Marzo 2025 ### Etendo Mobile @@ -758,7 +761,7 @@ tags: - :material-chart-bar: **Ahora en los informes financieros avanzados puede ver dimensiones contables.** --- - + ![texto alternativo](../assets/whats-new/etendo-news/financial-reports-advanced.png) En la versión [1.25.0](./release-notes/etendo-classic/bundles/financial-extensions/release-notes.md) del bundle Financial Extensions, se incluyen mejoras en los informes financieros avanzados. En esta versión, el [General Ledger Report Advanced](../user-guide/etendo-classic/basic-features/financial-management/accounting/analysis-tools/#general-ledger-report-advanced) y el [Journal Entries Report Advanced](../user-guide/etendo-classic/basic-features/financial-management/accounting/analysis-tools/#journal-entries-report-advanced) le permitirán ver y filtrar por las dimensiones contables deseadas. @@ -784,6 +787,7 @@ tags: *Consulte más detalles en la incidencia [#629](https://github.com/etendosoftware/etendo_core/issues/629)*. + ## Febrero 2025 ### Etendo ISO @@ -965,6 +969,7 @@ tags: En la versión [1.9.0](./release-notes/etendo-copilot/bundles/release-notes.md) del bundle Copilot Extensions, se ha añadido el tipo de asistente Multi-Model Assistant; estos agentes amplían el tipo `Langchain` con la particularidad de que puede utilizarse con modelos de varios proveedores como Anthropic o Gemini, además de los modelos OpenAI existentes. Además, se ha añadido la ventana AI Models, donde el usuario puede gestionar los modelos que utilizarán los distintos agentes. + ## Noviembre 2024 ### Copilot Extensions @@ -1035,6 +1040,7 @@ Nueva versión del bundle Copilot Extensions [1.5.0](./release-notes/etendo-copi ¡Potencie las capacidades de su agente con esta potente nueva funcionalidad! + ## Agosto 2024 ### Copilot Extensions From d0e506eb5bc2f00fd47c748eb6dfeacdbcd2b08f Mon Sep 17 00:00:00 2001 From: Isaias Battaglia Date: Mon, 13 Apr 2026 18:16:36 -0300 Subject: [PATCH 09/13] Feature ETP-3185: Fix broken links and typos in procurement docs --- .../accounting/setup/document-type.md | 4 +- .../receivables-and-payables/transactions.md | 4 +- .../procurement-management/getting-started.md | 12 +++--- .../transactions/goods-receipt.md | 2 +- .../transactions/purchase-order.md | 10 ++--- .../transactions/return-to-vendor-shipment.md | 2 +- .../transactions/return-to-vendor.md | 2 +- .../sales-management/setup/commission.md | 2 +- ...-to-manage-prepaid-invoices-in-payables.md | 2 +- .../essentials-extensions/bulk-completion.md | 16 ++++---- .../advanced-bank-account-management.md | 12 +++--- .../financial-extensions/bulk-posting.md | 40 +++++++++---------- .../bundles/financial-extensions/overview.md | 28 ++++++------- .../bundles/warehouse-extensions/overview.md | 2 +- docs/whats-new/etendo-news.md | 2 +- mkdocs.yml | 13 +++++- 16 files changed, 82 insertions(+), 71 deletions(-) diff --git a/docs/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md b/docs/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md index 0f6d1c13c0..e35cad79be 100644 --- a/docs/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md +++ b/docs/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md @@ -29,7 +29,7 @@ The complete list of standard document types is the following: | | | | |-----|-----|-----| | **Document Type Name**  | **Document Category**  | **Business Transaction** | -| AP CreditMemo | AP Credit Memo | [Purchase Credit Memo](../../../procurement-management/transactions/purchase-invoice.md) | +| AP CreditMemo | AP Credit Memo | [Purchase Credit Memo](../../../procurement-management/transactions/purchase-invoice.md#reactivate) | | AP Invoice | AP Invoice | [Purchase Invoice](../../../procurement-management/transactions/purchase-invoice.md) | | AR CreditMemo | AR Credit Memo | [Sales Credit Memo](../../../sales-management/transactions.md#header-6) | | AR Invoice | AR Invoice | [Sales Invoice](../../../sales-management/transactions.md#sales-invoice) | @@ -55,7 +55,7 @@ The complete list of standard document types is the following: | Doubtful Debts | Doubtful Debt | [Doubtful Debt](../../../financial-management/receivables-and-payables/transactions.md#doubtful-debt) | | Cost Adjustment | Cost Adjustment | [Cost Adjustment](../../../warehouse-management/transactions.md#cost-adjustment) | | Landed Cost | Landed Cost | [Landed Cost](../../../procurement-management/transactions/landed-cost.md) | -| Landed Cost Cost | Landed Cost Cost | [Landed Cost Cost](../../../procurement-management/transactions/landed-cost.md) | +| Landed Cost Cost | Landed Cost Cost | [Landed Cost Cost](../../../procurement-management/transactions/landed-cost.md#header) | | Inventory Amount Update | Inventory Amount Update | [Inventory Amount Update](../../../warehouse-management/transactions.md#inventory-amount-update) | !!! note "Important" diff --git a/docs/user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md b/docs/user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md index b8478cbac1..43bc71a4ee 100644 --- a/docs/user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md +++ b/docs/user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md @@ -1623,7 +1623,7 @@ There are two types of remittances: ![error.png](../../../../../assets/legacy/error.png) !!! info - Bank accounts can be defined in the header of [purchase](../../procurement-management/transactions.md#remittance_1) and [sales](../../sales-management/transactions.md#remittance_1) invoices as well as in [purchase](../../procurement-management/transactions.md#remittance) and [sales](../../sales-management/transactions.md#remittance) orders. + Bank accounts can be defined in the header of [purchase](../../procurement-management/transactions/purchase-invoice.md#modify-payment-plan) and [sales](../../sales-management/transactions.md#remittance_1) invoices as well as in [purchase](../../procurement-management/transactions/purchase-order.md#advanced-bank-account-management) and [sales](../../sales-management/transactions.md#remittance) orders. 4. When processing, the system shows the following options: @@ -1719,7 +1719,7 @@ There are two types of remittances: ![error.png](../../../../../assets/legacy/error.png) !!! info - Bank accounts can be defined in the header of [purchase](../../procurement-management/transactions.md#remittance_1) and [sales](../../sales-management/transactions.md#remittance_1) invoices as well as in [purchase](../../procurement-management/transactions.md#remittance) and [sales](../../sales-management/transactions.md#remittance) orders. + Bank accounts can be defined in the header of [purchase](../../procurement-management/transactions/purchase-invoice.md#modify-payment-plan) and [sales](../../sales-management/transactions.md#remittance_1) invoices as well as in [purchase](../../procurement-management/transactions/purchase-order.md#advanced-bank-account-management) and [sales](../../sales-management/transactions.md#remittance) orders. 4. When processing, the system shows the following options: diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md index 8e097dc3a1..f0580a73f3 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md @@ -116,10 +116,10 @@ Finance staff: - in a manual way - or by retrieving purchase orders or receipts lines pending to be invoiced - or by copying invoice lines from existing purchase invoices. -- Registers landed cost invoices and match those ["invoiced" landed costs](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) with the landed costs: - - booked directly in a [receipt(s)](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md). +- Registers landed cost invoices and match those ["invoiced" landed costs](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md#lines) with the landed costs: + - booked directly in a [receipt(s)](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md#landed-cost). - or booked through a [landed cost document](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md). -- [Processes](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md) and [Posts](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md) landed cost matching. +- [Processes](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md#process-matching) and [Posts](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md#post-matching) landed cost matching. - Once a Purchase Invoice is Processed, a Payment Plan of the invoice is created based on the payment terms agreed with the supplier and the purchase invoice can be posted to create the accounting entries of the invoice. Afterwards, the payment plan can be modified. Additionally: @@ -133,7 +133,7 @@ Purchase expenses can be recognized in different ways: In Etendo, in this situation, the expense is generated as part of the accounting of the purchase invoice corresponding to the transaction. - Under some circumstances, however, it is required to defer the expense recognition. For instance, a company purchasing a business insurance for the duration of a year would want to distribute that expense over 12 months. -In Etendo, in this situation, the expense can be deferred within a given number of periods by entering an expense deferred plan in the [purchase invoice lines](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md). +In Etendo, in this situation, the expense can be deferred within a given number of periods by entering an expense deferred plan in the [purchase invoice lines](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md#lines). !!!info For a full description of this functionality, please visit the [How to manage deferred revenue and expenses](../../../../user-guide/etendo-classic/how-to-guides/how-to-manage-deferred-revenue-and-expenses.md) section. @@ -163,7 +163,7 @@ In Procurement Management, the *Return to Vendor business flow* is executed as f Procurement staff: - Creates a new document in the [Return to Vendor](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md) window and looks for the vendor name in the Business Partner field. -- And continues by adding lines clicking the button [Pick/Edit lines](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md) +- And continues by adding lines clicking the button [Pick/Edit lines](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md#lines) - It is possible to pick goods receipt lines and edit the quantity you want to return and the price - Once the Return Material document is accepted by the Vendor, you can process it by clicking the Book button. The status of the document changes from Draft to Booked. - Only Booked documents can be shipped to the vendor @@ -171,7 +171,7 @@ Procurement staff: Warehouse staff: - Creates a new document in the [Return to Vendor Shipment](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md) window and looks for the vendor name in the Business Partner field. -- And continues by adding lines clicking the [Pick/Edit lines](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md) button +- And continues by adding lines clicking the [Pick/Edit lines](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md#lines) button - Return to Vendor lines are picked - It is possible to edit the quantity to be shipped - Once the document is ready, process it by clicking the button Complete. The status of the document changes from Draft to Completed diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md index 0985e48332..28a8f60c60 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md @@ -72,7 +72,7 @@ As a consequence, the information to manually fill in is: - the quantity received - the storage bin where the items are going to be stored -**Explode** button is shown when selecting a line with a non-stockable BOM product and the product has not already been exploded. When exploding a product, the bill of materials components the selected product consists of are shown in the shipment. Once you have exploded it, you cannot comprime it. You should delete all the lines (first bill of materials components and then the BOM product), and insert again the non-stockable BOM product. +**Explode** button is shown when selecting a line with a non-stockable BOM product and the product has not already been exploded. When exploding a product, the bill of materials components the selected product consists of are shown in the shipment. Once you have exploded it, you cannot compress it. You should delete all the lines (first bill of materials components and then the BOM product), and insert again the non-stockable BOM product. 2.On the other hand, it is also possible to **"automatically" create goods receipt lines**, by using the header process button **"Create Lines From"**. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md index 34f4c10bb2..1dddad35a8 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md @@ -141,7 +141,7 @@ Displays the details of the payments (pre-payments or regular payments) made for ## How to Reactivate a Closed Purchase Order !!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the [marketplace](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the [marketplace](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). !!! warning "Dependency Notice" This module depends on the [**Bulk Completion**](../../../optional-features/bundles/essentials-extensions/bulk-completion.md) module, as **order** processing actions must be performed using modern processes that allow the triggering of Hooks, instead of legacy processing. Due to this requirement, the legacy **close/reactivate** actions for orders will be hidden and these actions will only be available through the **Bulk Completion** button. @@ -160,7 +160,7 @@ Once the process is finished, the purchase order status turns to booked. The aim of this functionality is to delete and reactivate payments in an agile and easy way. Also, it allows eliminating and reactivating bank transactions and reconciliations. !!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). From this window, it is possible to remove payments associated with a purchase order by selecting the corresponding document and then clicking on the Remove Payment button. If there is an invoice associated with the order, the relationship of this invoice to the payment in question will also be removed (Purchase Invoice window > Payment Plan tab). @@ -181,7 +181,7 @@ In case the user has to create orders or invoices among two or more organization For more information, visit [the Intercompany module user guide](../../../../../user-guide/etendo-classic/optional-features/bundles/financial-extensions/intercompany.md). !!! info - To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + To be able to include this functionality, the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). ## Bulk Completion @@ -196,7 +196,7 @@ The Bulk Completion functionality allows the user to complete, reactivate or clo ## Advanced Bank Account Management !!! info - To be able to include this functionality, the Advanced Bank Account Management module of the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="\_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). + To be able to include this functionality, the Advanced Bank Account Management module of the Financial Extensions Bundle must be installed. To do that, follow the instructions from the marketplace: [Financial Extensions Bundle](https://marketplace.etendo.cloud/#/product-details?module=9876ABEF90CC4ABABFC399544AC14558){target="_blank"}. For more information about the available versions, core compatibility and new features, visit [Financial Extensions - Release notes](../../../../../whats-new/release-notes/etendo-classic/bundles/financial-extensions/release-notes.md). This module adds a new field to the header of the Purchase Order window: **Bank Account**. This field is automatically filled with the bank account related to the address or business partner of the order. @@ -207,7 +207,7 @@ This module adds a new field to the header of the Purchase Order window: **Bank --- -This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} by [Etendo](https://etendo.software){target="\_blank"}. +This work is a derivative of [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="_blank"} by [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="_blank"}, used under [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"}. This work is licensed under [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="_blank"} by [Etendo](https://etendo.software){target="_blank"}. --- This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L.](https://etendo.software){target="_blank"}. diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md index 28b3f7dd05..155d7a1283 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md @@ -38,7 +38,7 @@ To invoice these documents you must use the **Purchase invoice** window. All sce ## Lines -Add products which are included in your goods receipt. Each product is shown on its own line. +Add products which are included in your return to vendor shipment. Each product is shown on its own line. The Lines tab is not editable, since the lines always come from return to vendor lines, to avoid: diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md index 3b37bc9fae..d5e757c22b 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md @@ -25,7 +25,7 @@ Only *Booked* documents can be shipped to the vendor. ## Lines -Add products to be included in your purchase order. Each product is added by creating a line. +Add products to be included in your return to vendor document. Each product is added by creating a line. The Lines tab is not editable, since the returned lines always come from receipt lines, to avoid: diff --git a/docs/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md b/docs/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md index aa3ff2d918..1d9fdc9e58 100644 --- a/docs/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md +++ b/docs/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md @@ -20,7 +20,7 @@ The Commission functionality in Etendo begins with the **Commission window**, wh From the Commission window, more detailed criteria are defined, including filters by business partner, product, or region, along with the actual commission structure. A key feature is the ability to assign a **sales representative** directly when creating sales documents (orders and/or invoices), which allows Etendo to link those transactions to the appropriate commission plan and ensures accurate filtering. -Once all conditions are set, the system generates the corresponding commission, which is displayed in the [**Commission Payment**](../../../../etendo-classic/basic-features/sales-management/transactions.md#commission-payment) window, where users can review a detailed breakdown of the calculation and even generate a [**purchase invoice**](../../../../etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) to process the commission payment to the sales representative. +Once all conditions are set, the system generates the corresponding commission, which is displayed in the [**Commission Payment**](../../../../etendo-classic/basic-features/sales-management/transactions.md#commission-payment) window, where users can review a detailed breakdown of the calculation and even generate a [**purchase invoice**](../../procurement-management/transactions/purchase-invoice.md) to process the commission payment to the sales representative. To sum up, the overall flow is: diff --git a/docs/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md b/docs/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md index 29116336b6..7ab5b1f748 100644 --- a/docs/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md +++ b/docs/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md @@ -124,7 +124,7 @@ Once processed, Etendo informs about the Goods Receipt number just registered. Next step is to enter the vendor invoice. There are several ways of entering a vendor invoice. -The company in this example uses, for instance, the process "Create Lines From" which can be found in the [Purchase Invoice](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#lines-4) window. This process can be used once the purchase invoice header information has been properly entered. It retrieves either order or goods receipt information to be copied to the entered invoice. +The company in this example uses, for instance, the process "Create Lines From" which can be found in the [Purchase Invoice](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md#lines) window. This process can be used once the purchase invoice header information has been properly entered. It retrieves either order or goods receipt information to be copied to the entered invoice. ![](../../../assets/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables/createfrom.png) diff --git a/docs/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md b/docs/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md index 4eea64845e..9c68a65587 100644 --- a/docs/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md +++ b/docs/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md @@ -40,15 +40,15 @@ For orders, quotations and return documents it is possible to close multiple doc This functionality is available in the following windows: -- [Sales Quotation](../../../basic-features/sales-management/transactions/purchase-order.md) -- [Sales Order](../../../basic-features/sales-management/transactions/goods-receipt.md) -- [Goods Shipment](../../../basic-features/sales-management/transactions/purchase-invoice.md) -- [Return From Customer](../../../basic-features/sales-management/transactions/return-to-vendor.md) +- [Sales Quotation](../../../basic-features/sales-management/transactions.md#sales-quotation) +- [Sales Order](../../../basic-features/sales-management/transactions.md#sales-order) +- [Goods Shipment](../../../basic-features/sales-management/transactions.md#goods-shipment) +- [Return From Customer](../../../basic-features/sales-management/transactions.md#return-from-customer) - [Sales Invoice](../../../basic-features/sales-management/transactions.md#bulk-completion_4) -- [Purchase Order](../../../basic-features/procurement-management/transactions/purchase-order.md) -- [Goods Receipt](../../../basic-features/procurement-management/transactions/goods-receipt.md) -- [Purchase Invoice](../../../basic-features/procurement-management/transactions/purchase-invoice.md) -- [Return To Vendor](../../../basic-features/procurement-management/transactions/return-to-vendor.md) +- [Purchase Order](../../../basic-features/procurement-management/transactions/purchase-order.md#bulk-completion) +- [Goods Receipt](../../../basic-features/procurement-management/transactions/goods-receipt.md#bulk-completion) +- [Purchase Invoice](../../../basic-features/procurement-management/transactions/purchase-invoice.md#bulk-completion) +- [Return To Vendor](../../../basic-features/procurement-management/transactions/return-to-vendor.md#bulk-completion) As explained, using Bulk Completion improves efficiency by allowing users to perform document actions in bulk, streamlining operations and saving time. diff --git a/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md b/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md index 72e38ad713..e7d484cde6 100644 --- a/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md +++ b/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md @@ -25,12 +25,12 @@ This functionality enhances the bank account management enabling greater customi This functionality is available in the following windows: - [Business Partner](../../../basic-features/master-data-management/master-data.md#advanced-bank-account-management) -- [Sales Invoice](../../../basic-features/sales-management/transactions/purchase-invoice.md) -- [Purchase Invoice](../../../basic-features/procurement-management/transactions/purchase-invoice.md) -- [Sales Order](../../../basic-features/sales-management/transactions/purchase-order.md) -- [Purchase Order](../../../basic-features/procurement-management/transactions/purchase-order.md) -- [Payment In](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) -- [Payment Out](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-order.md) +- [Sales Invoice](../../../basic-features/sales-management/transactions.md#advanced-bank-account-management_1) +- [Purchase Invoice](../../../basic-features/procurement-management/transactions/purchase-invoice.md#modify-payment-plan) +- [Sales Order](../../../basic-features/sales-management/transactions.md#advanced-bank-account-management) +- [Purchase Order](../../../basic-features/procurement-management/transactions/purchase-order.md#advanced-bank-account-management) +- [Payment In](../../../basic-features/financial-management/receivables-and-payables/transactions.md#advanced-bank-account-management_1) +- [Payment Out](../../../basic-features/financial-management/receivables-and-payables/transactions.md#advanced-bank-account-management) ## Business Partner - Bank Account :material-menu: `Application` > `Master Data Management` > `Business Partner` diff --git a/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md b/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md index 7b71f15eaa..db708ac53e 100644 --- a/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md +++ b/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md @@ -28,26 +28,26 @@ The Bulk Posting functionality allows the user to post or unpost multiple record This functionality is available in the following windows: - [Amortization](../../../basic-features/financial-management/assets/overview.md#bulk-posting) -- [Goods Movements](../../../basic-features/warehouse-management/transactions/purchase-invoice.md) -- [Financial Account](../../../basic-features/financial-management/receivables-and-payables/transactions/matched-purchase-invoices.md) -- [Matched Purchase Invoices](../../../basic-features/procurement-management/transactions/matched-purchase-invoices.md) -- [Cost Adjustment](../../../basic-features/warehouse-management/transactions/return-to-vendor-shipment.md) -- [Bill of Materials Production](../../../basic-features/warehouse-management/transactions/matched-purchase-invoices.md) -- [Internal Consumption](../../../basic-features/production-management/transactions/purchase-invoice.md) -- [Doubtful Debt](../../../basic-features/financial-management/receivables-and-payables/transactions/return-to-vendor-shipment.md) -- [Landed Cost](../../../basic-features/procurement-management/transactions/landed-cost.md) -- [G/L Journal](../../../basic-features/financial-management/accounting/transactions/purchase-invoice.md) -- [Simple G/L Journal](../../../basic-features/financial-management/accounting/transactions/goods-receipt.md) -- [Work Effort](../../../basic-features/production-management/transactions/goods-receipt.md) -- [Goods Receipt](../../../basic-features/procurement-management/transactions/goods-receipt.md) -- [Goods Shipment](../../../basic-features/sales-management/transactions/goods-receipt.md) -- [Return Material Receipt](../../../basic-features/sales-management/transactions/purchase-invoice.md) -- [Return to Vendor Shipment](../../../basic-features/procurement-management/transactions/return-to-vendor-shipment.md) -- [Sales Invoice](../../../basic-features/sales-management/transactions/matched-purchase-invoices.md) -- [Purchase Invoice](../../../basic-features/procurement-management/transactions/purchase-invoice.md) -- [Payment In](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) -- [Payment Out](../../../basic-features/financial-management/receivables-and-payables/transactions/goods-receipt.md) -- [Physical Inventory](../../../basic-features/warehouse-management/transactions/goods-receipt.md) +- [Goods Movements](../../../basic-features/warehouse-management/transactions.md#bulk-posting_1) +- [Financial Account](../../../basic-features/financial-management/receivables-and-payables/transactions.md#bulk-posting_2) +- [Matched Purchase Invoices](../../../basic-features/procurement-management/transactions/matched-purchase-invoices.md#bulk-posting) +- [Cost Adjustment](../../../basic-features/warehouse-management/transactions.md#bulk-posting_3) +- [Bill of Materials Production](../../../basic-features/warehouse-management/transactions.md#bulk-posting_2) +- [Internal Consumption](../../../basic-features/production-management/transactions.md#bulk-posting_1) +- [Doubtful Debt](../../../basic-features/financial-management/receivables-and-payables/transactions.md#bulk-posting_3) +- [Landed Cost](../../../basic-features/procurement-management/transactions/landed-cost.md#bulk-posting) +- [G/L Journal](../../../basic-features/financial-management/accounting/transactions.md#bulk-posting_1) +- [Simple G/L Journal](../../../basic-features/financial-management/accounting/transactions.md#bulk-posting) +- [Work Effort](../../../basic-features/production-management/transactions.md#bulk-posting) +- [Goods Receipt](../../../basic-features/procurement-management/transactions/goods-receipt.md#bulk-posting) +- [Goods Shipment](../../../basic-features/sales-management/transactions.md#bulk-posting) +- [Return Material Receipt](../../../basic-features/sales-management/transactions.md#bulk-posting_1) +- [Return to Vendor Shipment](../../../basic-features/procurement-management/transactions/return-to-vendor-shipment.md#bulk-posting) +- [Sales Invoice](../../../basic-features/sales-management/transactions.md#bulk-posting_2) +- [Purchase Invoice](../../../basic-features/procurement-management/transactions/purchase-invoice.md#bulk-posting) +- [Payment In](../../../basic-features/financial-management/receivables-and-payables/transactions.md#bulk-posting_1) +- [Payment Out](../../../basic-features/financial-management/receivables-and-payables/transactions.md#bulk-posting) +- [Physical Inventory](../../../basic-features/warehouse-management/transactions.md#bulk-posting) ### Accounting Status Column diff --git a/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md b/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md index 6d0faa2eca..f6847e9604 100644 --- a/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md +++ b/docs/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md @@ -77,12 +77,12 @@ This module enhances the bank account management enabling greater customization This functionality is available in the following windows: - [Business Partner](../../../basic-features/master-data-management/master-data.md#advanced-bank-account-management_1) - - [Sales invoice](../../../basic-features/sales-management/transactions/purchase-invoice.md) - - [Purchase Invoice](../../../basic-features/procurement-management/transactions/purchase-invoice.md) - - [Sales order](../../../basic-features/sales-management/transactions/purchase-order.md) - - [Purchase order](../../../basic-features/procurement-management/transactions/purchase-order.md) - - [Payment In](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) - - [Payment Out](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-order.md) + - [Sales invoice](../../../basic-features/sales-management/transactions.md#advanced-bank-account-management_1) + - [Purchase Invoice](../../../basic-features/procurement-management/transactions/purchase-invoice.md#modify-payment-plan) + - [Sales order](../../../basic-features/sales-management/transactions.md#advanced-bank-account-management) + - [Purchase order](../../../basic-features/procurement-management/transactions/purchase-order.md#advanced-bank-account-management) + - [Payment In](../../../basic-features/financial-management/receivables-and-payables/transactions.md#advanced-bank-account-management_1) + - [Payment Out](../../../basic-features/financial-management/receivables-and-payables/transactions.md#advanced-bank-account-management) For more information, visit the [Advanced Bank Account Management](../../../optional-features/bundles/financial-extensions/advanced-bank-account-management.md). @@ -104,8 +104,8 @@ This functionality is part of the Financial Extensions Bundle and it is useful w - [Sales Order](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#how-to-reactivate-a-closed-sales-order) - [Sales Invoice](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#how-to-reactivate-a-voided-sales-invoice) - - [Purchase Order](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) - - [Purchase Invoice](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) + - [Purchase Order](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md#how-to-reactivate-a-closed-purchase-order) + - [Purchase Invoice](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md#reactivate) - [Amortization](../../../../../user-guide/etendo-classic/basic-features/financial-management/assets/overview.md#how-to-reactivate-amortizations) - and the [Advanced Financial Docs. Processing developer guide](../../../../../developer-guide/etendo-classic/bundles/financial-extensions-bundle/overview.md#advanced-financial-docs-processing) @@ -259,12 +259,12 @@ The button Remove Payment is available in the Sales Order, Purchase Order, Sales !!! info For more information, visit: - - [Sales Order](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions/purchase-order.md) - - [Purchase Order](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) - - [Sales Invoice](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions/purchase-invoice.md) - - [Purchase Invoice](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) - - [Payment In](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) - - [Payment Out](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions/purchase-order.md) + - [Sales Order](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#payment-removal) + - [Purchase Order](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md#payment-removal) + - [Sales Invoice](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#payment-removal_1) + - [Purchase Invoice](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md#remove-payment) + - [Payment In](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md#payment-removal_1) + - [Payment Out](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md#payment-removal) - [Financial Account](../../../../../user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md#payment-removal_2) ### Remittances diff --git a/docs/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md b/docs/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md index 79c3372bc7..7fb67d444c 100644 --- a/docs/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md +++ b/docs/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md @@ -88,7 +88,7 @@ This functionality is part of the Warehouse Extensions Bundle and it is useful w For more information, visit the user guide for: - [Goods Movements](../../../../../user-guide/etendo-classic/basic-features/warehouse-management/transactions.md#how-to-reactivate-goods-movements) - - [Goods Receipts](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md) + - [Goods Receipts](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md#how-to-reactivate-goods-receipts) - [Goods Shipments](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#how-to-reactivate-goods-shipments) - [Physical Inventory](../../../../../user-guide/etendo-classic/basic-features/warehouse-management/transactions.md#how-to-reactivate-physical-inventories) diff --git a/docs/whats-new/etendo-news.md b/docs/whats-new/etendo-news.md index 634d0f130d..ea708fcd39 100644 --- a/docs/whats-new/etendo-news.md +++ b/docs/whats-new/etendo-news.md @@ -689,7 +689,7 @@ tags: - :octicons-rocket-24: **Enhanced Purchase Invoice Voiding with Supplier Reference** --- - When canceling a purchase invoice, Etendo creates a reverse document that now references the supplier’s cancellation document. The [invoice reactivation](../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) process includes a new `Supplier Reference` field to ensure clear traceability and alignment. + When canceling a purchase invoice, Etendo creates a reverse document that now references the supplier’s cancellation document. The [invoice reactivation](../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md#reactivate) process includes a new `Supplier Reference` field to ensure clear traceability and alignment. diff --git a/mkdocs.yml b/mkdocs.yml index 05fd509e6e..b94198547b 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -173,7 +173,18 @@ plugins: - Pricing: user-guide/etendo-classic/basic-features/master-data-management/pricing.md - Procurement Management: - ✨ Getting Started: user-guide/etendo-classic/basic-features/procurement-management/getting-started.md - - Transactions: user-guide/etendo-classic/basic-features/procurement-management/transactions.md + - Transactions: + - Requisition: user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition.md + - Manage Requisitions: user-guide/etendo-classic/basic-features/procurement-management/transactions/manage-requisitions.md + - Requisition to Order: user-guide/etendo-classic/basic-features/procurement-management/transactions/requisition-to-order.md + - Purchase Order: user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md + - Goods Receipt: user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md + - Pending Goods Receipts: user-guide/etendo-classic/basic-features/procurement-management/transactions/pending-goods-receipts.md + - Purchase Invoice: user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md + - Matched Purchase Invoices: user-guide/etendo-classic/basic-features/procurement-management/transactions/matched-purchase-invoices.md + - Return to Vendor: user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor.md + - Return to Vendor Shipment: user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md + - Landed Cost: user-guide/etendo-classic/basic-features/procurement-management/transactions/landed-cost.md - Analysis Tools: user-guide/etendo-classic/basic-features/procurement-management/analysis-tools.md - Warehouse Management: - ✨ Getting Started: user-guide/etendo-classic/basic-features/warehouse-management/getting-started.md From 7e93e9f222f18903d839f8ca0c6e5e70bfa094d6 Mon Sep 17 00:00:00 2001 From: etendobot <108091082+etendobot@users.noreply.github.com> Date: Mon, 13 Apr 2026 18:26:38 -0300 Subject: [PATCH 10/13] Feature ETP-3185: Update ES translation --- .../accounting/setup/document-type.md | 4 ++-- .../receivables-and-payables/transactions.md | 2 ++ .../procurement-management/getting-started.md | 2 +- .../transactions/goods-receipt.md | 2 +- .../transactions/return-to-vendor-shipment.md | 4 +++- .../sales-management/setup/commission.md | 2 +- ...-to-manage-prepaid-invoices-in-payables.md | 2 +- .../essentials-extensions/bulk-completion.md | 18 +++++++++-------- .../advanced-bank-account-management.md | 14 +++++++------ .../financial-extensions/bulk-posting.md | 20 ++++++++++--------- .../bundles/financial-extensions/overview.md | 10 ++++++---- .../bundles/warehouse-extensions/overview.md | 6 ++++-- docs/es/whats-new/etendo-news.md | 2 +- 13 files changed, 51 insertions(+), 37 deletions(-) diff --git a/docs/es/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md b/docs/es/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md index c6bf0dd935..bcbec7750e 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md +++ b/docs/es/user-guide/etendo-classic/basic-features/financial-management/accounting/setup/document-type.md @@ -29,7 +29,7 @@ La lista completa de tipos de documento estándar es la siguiente: | | | | |-----|-----|-----| | **Nombre del tipo de documento**  | **Tipo doc. base**  | **Transacción empresarial** | -| AP CreditMemo | Nota de abono de proveedor | [Nota de crédito de compra](../../../procurement-management/transactions/purchase-invoice.md) | +| AP CreditMemo | Nota de abono de proveedor | [Nota de crédito de compra](../../../procurement-management/transactions/purchase-invoice.md#reactivate) | | AP Invoice | Factura de proveedor | [Factura (Proveedor)](../../../procurement-management/transactions/purchase-invoice.md) | | AR CreditMemo | Nota de abono de cliente | [Nota de crédito de venta](../../../sales-management/transactions.md#header-6) | | AR Invoice | Factura de cliente | [Factura (Cliente)](../../../sales-management/transactions.md#sales-invoice) | @@ -55,7 +55,7 @@ La lista completa de tipos de documento estándar es la siguiente: | Dudoso cobro | Dudoso cobro | [Dudoso cobro](../../../financial-management/receivables-and-payables/transactions.md#doubtful-debt) | | Ajuste de Costes | Ajuste de Costes | [Ajuste de Costes](../../../warehouse-management/transactions.md#cost-adjustment) | | Landed Cost | Landed Cost | [Landed Cost](../../../procurement-management/transactions/landed-cost.md) | -| Coste de Landed Cost | Coste de Landed Cost | [Coste de Landed Cost](../../../procurement-management/transactions/landed-cost.md) | +| Coste de Landed Cost | Coste de Landed Cost | [Coste de Landed Cost](../../../procurement-management/transactions/landed-cost.md#header) | | Ajuste de Valor del Inventario | Ajuste de Valor del Inventario | [Ajuste de Valor del Inventario](../../../warehouse-management/transactions.md#inventory-amount-update) | !!! note "Importante" diff --git a/docs/es/user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md b/docs/es/user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md index d7d9deccbd..1a31ab3093 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md +++ b/docs/es/user-guide/etendo-classic/basic-features/financial-management/receivables-and-payables/transactions.md @@ -1882,4 +1882,6 @@ Este trabajo es una obra derivada de [Gestión Financiera](http://wiki.openbravo --- +--- + --- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md index 560494c30a..d74705686f 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/getting-started.md @@ -133,7 +133,7 @@ Los gastos de compra pueden reconocerse de diferentes maneras: En Etendo, en esta situación, el gasto se genera como parte de la contabilidad de la factura de proveedor correspondiente a la transacción. - En algunas circunstancias, sin embargo, se requiere diferir el reconocimiento del gasto. Por ejemplo, una empresa que compra un seguro empresarial por la duración de un año querría distribuir ese gasto durante 12 meses. -En Etendo, en esta situación, el gasto puede diferirse dentro de un número determinado de periodos introduciendo un plan de diferimiento de gastos en las [líneas de factura de proveedor](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md). +En Etendo, en esta situación, el gasto puede diferirse dentro de un número determinado de periodos introduciendo un plan de diferimiento de gastos en las [líneas de factura de proveedor](../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md#lines). !!!info Para una descripción completa de esta funcionalidad, visite la sección [Cómo gestionar ingresos y gastos diferidos](../../../../user-guide/etendo-classic/how-to-guides/how-to-manage-deferred-revenue-and-expenses.md). diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md index 3cb529b4bb..b85da9b05c 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md @@ -35,7 +35,7 @@ En la **barra de estado** de la cabecera, el usuario puede encontrar la siguient **Una vez que la información de cabecera se ha cumplimentado correctamente, puede ir a la pestaña "Líneas" para introducir la/s "Línea/s de albarán (proveedor)"**. !!! info - Para aprender cómo introducir líneas de albarán, visite la siguiente sección [Líneas](goods-receipts.md#lines) + Para aprender cómo introducir líneas de albarán, visite la siguiente sección [Líneas](goods-receipt.md#lines) Si un **albarán (proveedor)** se completa y, por tanto, queda **contabilizado**: diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md index 7f100f8d1e..a01d01f76b 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/return-to-vendor-shipment.md @@ -93,9 +93,11 @@ Además, el Estado de Contabilidad del/de los registro/s se muestra en la barra --- -Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="\_blank"}, usado bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. +Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="\_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo"){target="\_blank"}, usado bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="\_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="\_blank"} por [Etendo](https://etendo.software){target="\_blank"}. --- Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. +--- + --- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md b/docs/es/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md index 772fdf1307..cb04391095 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md +++ b/docs/es/user-guide/etendo-classic/basic-features/sales-management/setup/commission.md @@ -20,7 +20,7 @@ La funcionalidad de Comisión en Etendo comienza con la **ventana Comisión**, d Desde la ventana Comisión, se definen criterios más detallados, incluyendo filtros por tercero, producto o región, junto con la estructura real de la comisión. Una funcionalidad clave es la posibilidad de asignar un **agente comercial** directamente al crear documentos de venta (pedidos y/o facturas), lo que permite a Etendo vincular esas transacciones al plan de comisiones correspondiente y garantiza un filtrado preciso. -Una vez establecidas todas las condiciones, el sistema genera la comisión correspondiente, que se muestra en la ventana [**Procesar comisión**](../../../../etendo-classic/basic-features/sales-management/transactions.md#commission-payment), donde los usuarios pueden revisar un desglose detallado del cálculo e incluso generar una [**Factura (Proveedor)**](../../../../etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) para procesar el pago de la comisión al agente comercial. +Una vez establecidas todas las condiciones, el sistema genera la comisión correspondiente, que se muestra en la ventana [**Procesar comisión**](../../../../etendo-classic/basic-features/sales-management/transactions.md#commission-payment), donde los usuarios pueden revisar un desglose detallado del cálculo e incluso generar una [**Factura (Proveedor)**](../../procurement-management/transactions/purchase-invoice.md) para procesar el pago de la comisión al agente comercial. En resumen, el flujo general es: diff --git a/docs/es/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md b/docs/es/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md index 1d6c3efd01..135e7792da 100644 --- a/docs/es/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md +++ b/docs/es/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables.md @@ -124,7 +124,7 @@ Una vez procesado, Etendo informa del número de albarán recién registrado. El siguiente paso es introducir la factura del proveedor. Hay varias formas de introducir una factura de proveedor. -La empresa de este ejemplo utiliza, por ejemplo, el proceso "Crear líneas de", que se puede encontrar en la ventana [Factura (Proveedor)](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions.md#lines-4). Este proceso puede utilizarse una vez que la información de cabecera de la factura de compra se haya introducido correctamente. Recupera información del pedido o del albarán para copiarla en la factura introducida. +La empresa de este ejemplo utiliza, por ejemplo, el proceso "Crear líneas de", que se puede encontrar en la ventana [Factura (Proveedor)](../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md#lines). Este proceso puede utilizarse una vez que la información de cabecera de la factura de compra se haya introducido correctamente. Recupera información del pedido o del albarán para copiarla en la factura introducida. ![](../../../assets/user-guide/etendo-classic/how-to-guides/how-to-manage-prepaid-invoices-in-payables/createfrom.png) diff --git a/docs/es/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md b/docs/es/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md index f7bd1cb2b8..a751fa99ea 100644 --- a/docs/es/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md +++ b/docs/es/user-guide/etendo-classic/optional-features/bundles/essentials-extensions/bulk-completion.md @@ -40,15 +40,15 @@ Para pedidos, presupuestos y documentos de devolución es posible cerrar múltip Esta funcionalidad está disponible en las siguientes ventanas: -- [Presupuesto de ventas](../../../basic-features/sales-management/transactions/purchase-order.md) -- [Pedido de venta](../../../basic-features/sales-management/transactions/goods-receipt.md) -- [Albarán (Cliente)](../../../basic-features/sales-management/transactions/purchase-invoice.md) -- [Devolución de cliente](../../../basic-features/sales-management/transactions/return-to-vendor.md) +- [Presupuesto de ventas](../../../basic-features/sales-management/transactions.md#sales-quotation) +- [Pedido de venta](../../../basic-features/sales-management/transactions.md#sales-order) +- [Albarán (Cliente)](../../../basic-features/sales-management/transactions.md#goods-shipment) +- [Devolución de cliente](../../../basic-features/sales-management/transactions.md#return-from-customer) - [Factura (Cliente)](../../../basic-features/sales-management/transactions.md#bulk-completion_4) -- [Pedido de compra](../../../basic-features/procurement-management/transactions/purchase-order.md) -- [Albarán (Proveedor)](../../../basic-features/procurement-management/transactions/goods-receipt.md) -- [Factura (Proveedor)](../../../basic-features/procurement-management/transactions/purchase-invoice.md) -- [Devolución a proveedor](../../../basic-features/procurement-management/transactions/return-to-vendor.md) +- [Pedido de compra](../../../basic-features/procurement-management/transactions/purchase-order.md#bulk-completion) +- [Albarán (Proveedor)](../../../basic-features/procurement-management/transactions/goods-receipt.md#bulk-completion) +- [Factura (Proveedor)](../../../basic-features/procurement-management/transactions/purchase-invoice.md#bulk-completion) +- [Devolución a proveedor](../../../basic-features/procurement-management/transactions/return-to-vendor.md#bulk-completion) Como se ha explicado, el uso de Finalización masiva mejora la eficiencia al permitir a los usuarios realizar acciones sobre documentos de forma masiva, agilizando las operaciones y ahorrando tiempo. @@ -56,4 +56,6 @@ Como se ha explicado, el uso de Finalización masiva mejora la eficiencia al per --- Este trabajo está licenciado bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L](https://etendo.software){target="_blank"}. +--- + --- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md b/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md index 3a963dbcb9..fc383d6d2f 100644 --- a/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md +++ b/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/advanced-bank-account-management.md @@ -25,12 +25,12 @@ Esta funcionalidad mejora la gestión de cuentas bancarias, permitiendo una mayo Esta funcionalidad está disponible en las siguientes ventanas: - [Terceros](../../../basic-features/master-data-management/master-data.md#advanced-bank-account-management) -- [Factura (Cliente)](../../../basic-features/sales-management/transactions/purchase-invoice.md) -- [Factura (Proveedor)](../../../basic-features/procurement-management/transactions/purchase-invoice.md) -- [Pedido de venta](../../../basic-features/sales-management/transactions/purchase-order.md) -- [Pedido de compra](../../../basic-features/procurement-management/transactions/purchase-order.md) -- [Cobros](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) -- [Pago](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-order.md) +- [Factura (Cliente)](../../../basic-features/sales-management/transactions.md#advanced-bank-account-management_1) +- [Factura (Proveedor)](../../../basic-features/procurement-management/transactions/purchase-invoice.md#modify-payment-plan) +- [Pedido de venta](../../../basic-features/sales-management/transactions.md#advanced-bank-account-management) +- [Pedido de compra](../../../basic-features/procurement-management/transactions/purchase-order.md#advanced-bank-account-management) +- [Cobros](../../../basic-features/financial-management/receivables-and-payables/transactions.md#advanced-bank-account-management_1) +- [Pago](../../../basic-features/financial-management/receivables-and-payables/transactions.md#advanced-bank-account-management) ## Terceros - Cuenta bancaria :material-menu: `Aplicación` > `Gestión de Datos Maestros` > `Terceros` @@ -109,4 +109,6 @@ Al igual que en el caso del botón **Añadir pago**, el botón **Añadir detalle --- This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L](https://etendo.software){target="_blank"}. +--- + --- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md b/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md index 72173cc2dc..50ed09f395 100644 --- a/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md +++ b/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/bulk-posting.md @@ -26,23 +26,23 @@ La funcionalidad de Contabilización masiva permite al usuario contabilizar o de Esta funcionalidad está disponible en las siguientes ventanas: - [Amortización](../../../basic-features/financial-management/assets/overview.md#bulk-posting) -- [Movimiento entre almacenes](../../../basic-features/warehouse-management/transactions/purchase-invoice.md) -- [Cuenta financiera](../../../basic-features/financial-management/receivables-and-payables/transactions/matched-purchase-invoices.md) -- [Facturas cuadradas](../../../basic-features/procurement-management/transactions/matched-purchase-invoices.md) -- [Ajuste de Costes](../../../basic-features/warehouse-management/transactions/return-to-vendor-shipment.md) -- [Producción LDM](../../../basic-features/warehouse-management/transactions/matched-purchase-invoices.md) +- [Movimiento entre almacenes](../../../basic-features/warehouse-management/transactions.md#bulk-posting_1) +- [Cuenta financiera](../../../basic-features/financial-management/receivables-and-payables/transactions.md#bulk-posting_2) +- [Facturas cuadradas](../../../basic-features/procurement-management/transactions/matched-purchase-invoices.md#bulk-posting) +- [Ajuste de Costes](../../../basic-features/warehouse-management/transactions.md#bulk-posting_3) +- [Producción LDM](../../../basic-features/warehouse-management/transactions.md#bulk-posting_2) - [Consumo interno](../../../basic-features/production-management/transactions/purchase-invoice.md) -- [Dudoso cobro](../../../basic-features/financial-management/receivables-and-payables/transactions/return-to-vendor-shipment.md) -- [Landed Cost](../../../basic-features/procurement-management/transactions/landed-cost.md) +- [Dudoso cobro](../../../basic-features/financial-management/receivables-and-payables/transactions.md#bulk-posting_3) +- [Landed Cost](../../../basic-features/procurement-management/transactions/landed-cost.md#bulk-posting) - [Asientos manuales](../../../basic-features/financial-management/accounting/transactions/purchase-invoice.md) - [Asientos Manuales Simplificados](../../../basic-features/financial-management/accounting/transactions/goods-receipt.md) - [Parte de Trabajo](../../../basic-features/production-management/transactions/goods-receipt.md) - [Albarán (Proveedor)](../../../basic-features/procurement-management/transactions/goods-receipt.md) - [Albarán (Cliente)](../../../basic-features/sales-management/transactions/goods-receipt.md) - [Recibo devolución de material](../../../basic-features/sales-management/transactions/purchase-invoice.md) -- [Devolución a albarán de proveedor](../../../basic-features/procurement-management/transactions/return-to-vendor-shipment.md) +- [Devolución a albarán de proveedor](../../../basic-features/procurement-management/transactions/return-to-vendor-shipment.md#bulk-posting) - [Factura (Cliente)](../../../basic-features/sales-management/transactions/matched-purchase-invoices.md) -- [Factura (Proveedor)](../../../basic-features/procurement-management/transactions/purchase-invoice.md) +- [Factura (Proveedor)](../../../basic-features/procurement-management/transactions/purchase-invoice.md#bulk-posting) - [Cobros](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) - [Pago](../../../basic-features/financial-management/receivables-and-payables/transactions/goods-receipt.md) - [Inventario físico](../../../basic-features/warehouse-management/transactions/goods-receipt.md) @@ -73,4 +73,6 @@ This work is licensed under :material-creative-commons: :fontawesome-brands-crea --- +--- + --- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md b/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md index 81e8110963..43f99dc8c8 100644 --- a/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md +++ b/docs/es/user-guide/etendo-classic/optional-features/bundles/financial-extensions/overview.md @@ -70,9 +70,9 @@ Este módulo mejora la gestión de cuentas bancarias, permitiendo una mayor pers - [Terceros](../../../basic-features/master-data-management/master-data.md#advanced-bank-account-management_1) - [Factura (Cliente)](../../../basic-features/sales-management/transactions/purchase-invoice.md) - - [Factura (Proveedor)](../../../basic-features/procurement-management/transactions/purchase-invoice.md) + - [Factura (Proveedor)](../../../basic-features/procurement-management/transactions/purchase-invoice.md#modify-payment-plan) - [Pedido de venta](../../../basic-features/sales-management/transactions/purchase-order.md) - - [Pedido de compra](../../../basic-features/procurement-management/transactions/purchase-order.md) + - [Pedido de compra](../../../basic-features/procurement-management/transactions/purchase-order.md#advanced-bank-account-management) - [Cobros](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-invoice.md) - [Pago](../../../basic-features/financial-management/receivables-and-payables/transactions/purchase-order.md) @@ -112,8 +112,8 @@ Esta funcionalidad forma parte de Financial Extensions Bundle y es útil cuando - [Pedido de venta](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#how-to-reactivate-a-closed-sales-order) - [Factura (Cliente)](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#how-to-reactivate-a-voided-sales-invoice) - - [Pedido de compra](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md) - - [Factura (Proveedor)](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) + - [Pedido de compra](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-order.md#how-to-reactivate-a-closed-purchase-order) + - [Factura (Proveedor)](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md#reactivate) - [Amortización](../../../../../user-guide/etendo-classic/basic-features/financial-management/assets/overview.md#how-to-reactivate-amortizations) - y la [Guía del desarrollador de Procesamiento avanzado de documentos financieros](../../../../../developer-guide/etendo-classic/bundles/financial-extensions-bundle/overview.md#advanced-financial-docs-processing) ### Informe de Amortización de Activos @@ -285,4 +285,6 @@ This work is licensed under :material-creative-commons: :fontawesome-brands-crea --- +--- + --- \ No newline at end of file diff --git a/docs/es/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md b/docs/es/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md index 7d1edfb9cd..b3e8eea0db 100644 --- a/docs/es/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md +++ b/docs/es/user-guide/etendo-classic/optional-features/bundles/warehouse-extensions/overview.md @@ -88,7 +88,7 @@ Esta funcionalidad forma parte de Warehouse Extensions Bundle y es útil cuando Para más información, visite la guía de usuario de: - [Movimiento entre almacenes](../../../../../user-guide/etendo-classic/basic-features/warehouse-management/transactions.md#how-to-reactivate-goods-movements) - - [Albarán (Proveedor)](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md) + - [Albarán (Proveedor)](../../../../../user-guide/etendo-classic/basic-features/procurement-management/transactions/goods-receipt.md#how-to-reactivate-goods-receipts) - [Albarán (Cliente)](../../../../../user-guide/etendo-classic/basic-features/sales-management/transactions.md#how-to-reactivate-goods-shipments) - [Inventario físico](../../../../../user-guide/etendo-classic/basic-features/warehouse-management/transactions.md#how-to-reactivate-physical-inventories) @@ -144,4 +144,6 @@ WHERE AD_TAB_ID = 'C3DB551F2BCA40A79AAF21DBD6D06309'; 2. Una vez que la consulta finalice correctamente, elimine el bundle según el método correspondiente a la instalación (Sources/JARs) --- -This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L](https://etendo.software){target="_blank"}. \ No newline at end of file +This work is licensed under :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} by [Futit Services S.L](https://etendo.software){target="_blank"}. + +--- \ No newline at end of file diff --git a/docs/es/whats-new/etendo-news.md b/docs/es/whats-new/etendo-news.md index 4ef5106ab4..c905e300aa 100644 --- a/docs/es/whats-new/etendo-news.md +++ b/docs/es/whats-new/etendo-news.md @@ -684,7 +684,7 @@ tags: - :octicons-rocket-24: **Anulación mejorada de la Factura (Proveedor) con referencia del proveedor** --- - Al anular una Factura (Proveedor), Etendo crea un documento inverso que ahora referencia el documento de anulación del proveedor. El proceso de [reactivación de factura](../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md) incluye un nuevo campo `Referencia del proveedor` para garantizar una trazabilidad clara y la alineación. + Al anular una Factura (Proveedor), Etendo crea un documento inverso que ahora referencia el documento de anulación del proveedor. El proceso de [reactivación de factura](../user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md#reactivate) incluye un nuevo campo `Referencia del proveedor` para garantizar una trazabilidad clara y la alineación. From e34a30d42e4981490751546493abe474794152da Mon Sep 17 00:00:00 2001 From: Isaias Battaglia Date: Mon, 13 Apr 2026 18:38:39 -0300 Subject: [PATCH 11/13] Feature ETP-3185: Add nav translations for new procurement pages --- mkdocs.yml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/mkdocs.yml b/mkdocs.yml index b94198547b..968864c77e 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -735,6 +735,7 @@ plugins: Getting Started: Primeros Pasos GL Category: Categoría Contable GL Item: Concepto contable + Goods Receipt: Albarán (Proveedor) Grid and Forms: Grillas y Formularios Help and Support: Ayuda y Soporte Home: Inicio @@ -889,10 +890,13 @@ plugins: JavaScript Coding Conventions: Convenciones de Código JavaScript JSON REST Web Services: Servicios Web JSON REST Known Issues: Problemas Conocidos + Landed Cost: Landed Cost Live Builds: Live Builds Main Development Concepts: Conceptos Principales de Desarrollo + Manage Requisitions: Administrar Necesidades Master Data: Datos Maestros Master Data Management: Gestión de Datos Maestros + Matched Purchase Invoices: Facturas Cuadradas Material Requirement Planning: Gestión de MRP Merging Modules: Fusión de Módulos Messages: Mensajes @@ -911,6 +915,7 @@ plugins: Organization Type: Tipo de Organización Overview: Visión General Packing: Empaquetado + Pending Goods Receipts: Albaranes Pendientes de Recibir Period Control Log: Abrir/Cerrar Periodos Picking List: Lista de Preparación Plugins: Plugins @@ -929,11 +934,17 @@ plugins: Production Management: Gestión de Producción Project and Service Management: Gestión de Proyectos y Servicios Projections and Mappings: Proyecciones y Mapeos + Purchase Invoice: Factura de Compra Purchase Invoice Validation: Validación de Factura de Compra + Purchase Order: Pedido de Compra Receivables and Payables: Gestión de Cobros y Pagos Release Notes: Notas de la Versión Requirements: Requisitos + Requisition: Necesidad de Material + Requisition to Order: Necesidad a Pedido Resolving Dependencies on GitHub: Resolver Dependencias en GitHub + Return to Vendor: Devolución a Proveedor + Return to Vendor Shipment: Devolución a albarán de proveedor Role: Rol Role Access: Rol permisos Sales Management: Gestión de Ventas From 4e8c077b80428daa6d03845fff6919ad30e4654f Mon Sep 17 00:00:00 2001 From: Isaias Battaglia Date: Mon, 13 Apr 2026 18:56:29 -0300 Subject: [PATCH 12/13] Feature ETP-3185: Replace PRpic2 and PRpic4 with remove-payment screenshot --- .../transactions/PRpic2.png | Bin 66885 -> 0 bytes .../{PRpic4.png => remove-payment.png} | Bin .../transactions/purchase-invoice.md | 2 +- 3 files changed, 1 insertion(+), 1 deletion(-) delete mode 100644 docs/assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/PRpic2.png rename docs/assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/{PRpic4.png => remove-payment.png} (100%) diff --git a/docs/assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/PRpic2.png b/docs/assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/PRpic2.png deleted file mode 100644 index 846f295e92bae76848781d5d5381439b87ecaf32..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 66885 zcmd42Wmr^wzc$QeAyO(Oty0p`FqCwMARw(0LxV7MDH2LI3@{+wAkB~>(l88NLk}=? zGc?cgzW257z2AL*c%S{{eb)z$gSBSW@Bhp5Jl8i(bp^r)R1a`)a0rzYWwmf{aD8xa zZt35@1?(Ask96Yvb(cU%R_cvM+SV+t5vkHI$xBZx+}q93eZINbd&gn-#BJ6bhb)@r zE>m(s8d+8H-L_B3FW=vi#bbN&@U}cDY5(`E7g?VkC=#s-EV6ygIn&c19C%64{;8j! zyL|WJJ=n{pp}4qVW?4v%Fu!C=y!eia3chu&`=Bt6amWJapU3#e_FXRGF_R}t1MD5E z42Hls9OVc+>pwRn{3*m?R@y*mac~?s>3ZufP}lMP)dU_AJBerf8Y8O;%=tPW+HDO0@=}h#eDbgtHAK3*Ty+5?!z*} zVlLGFSnwYkh$0YCYS{Y_BtyY~O(p$%H-zgx%&;zA01q}VzWk}WN8Dq(_ut;+KCJQI zKdbZ_m;8

)#i|7(E2lIk4JFKoY%$PuHbp-0u9_ccGO2|LVwaFA~l#`EmaIn3`zz z1*g5ohWCrYf@^Ep_Tr8X{cl~rYVD^VS8pTXqqiD9FNNr{)H&`MZ>pT)+Rgf3T1q(j zDj(&k6=R3CNmpQV6(0wfTbG3%sD$B<4AK$cP1jpol(|rPHVx!$VV9d{-LvVZ4svI5 z?Y2W7kR%K3G^Negk5@Ar-o6Tu#=?}@NI6t(rAt^E**Q6_ty$wZAiB$^9K;cX^W-vj z%ICKwY{ZP=mfl+_Ju!0)1YKMY9({CZk|)>qaG4C3%AQK_I;WmEf8dxYS487DZS_7Z zY500Hn9`nk=C#O#=+OfExEH~TidvG4xn7~AP4g#So@wHrU>`&^Vm$djD91IWtizOKsE6h99OJmHJ_-XlTt~t$_u{LVH=ZS>QknPf6Ai99!<&8yp#Q>R z`BKAMt98-BZ#9}yu#tUSt_iszmTJ#;1u6y#7FxofJ;X3q;m`SO_4J4moof=ppyu|2 zZSJx6Oqy?bTcmI;rOrJ=>n z*3?v0ua9^4>gmw4d90Y`;)+J()>yb*rMG4at=$g3U-EuKTj$}{Q)`T!9ZZ^-(SL^E zV00L?qOayl2rpOXPI*N#7aea*x?Y&wYyTCeMVKp?ei-TL-gXsNj2jcXtY_N8&8jqS zQJ!zNMDD|0F1%Tikx*8Icyr_3(bXB3phEPL$6ejvr$@7&jBzCTuv2r_75vL0!Y^3G z?a<7sEyWy7YHlLBAu6SyJvC}SBTfYpMKnI|d0oc|@p}l@JkuC2$~fB^SQx+jXeqe% zDH#dhx!%dlFl7ChH#mP&nRo#y&s}*H!6#CK>P_R5Agbc`hgvyO`flUZ)q>c6+QpwD zr_dpM9sFbilJEAx%)R`VYf6=c!>7lcHy?jcyVeBSoy4|&{^^%0A7Q@B)YQyf=Q4H~ z5*9R-&Nn4cQ*-wj12rv-D#RT^hUY-T?PeQFgNuJy5QvMKb{C>3G`v5i`+{HS!WLp9 zQg=|)x^U{iV_$q4^reu^MfhyS5{YWs(T^Q`Iq|+(T7%TZ*7SG1kC})MSrQ#8w_|=xd*=T@{pX9@C2=IzgTfcYO3?W=(4v{l;&NQrSsOedN|$a@0x~;s2{t zm5^`oRF>3b(@!J0*ew5IEh6NgzD6UNQ}OX^tl-eHo!E6e9xOt5WZblfA);!0vQVh2 zV=O=L%|dm)rzmrWgZ5>gNh=KVBh)__LhrxkHdnZ;_Xu?RKRo7Bbqxr@^&&JmH(Siv zhQQOutT9Mlvi94hn=)$OFgHtlm<7?8%@Zo^6F?;L7&K&HaB=CCsua!YO4kq8Tl~mzuC$~-)cj` z_x9JxWX=hm)TG9F5nK!vm^XJCM+lx-_V1pD&rH^{xX zz`2C-l>pQ#nz3{#PlwcewrVnbqQ*D`bWw*U51J<&1ZQ7f=aLL-$b)HW% zwjDpkB+^?%IuyRbsP+*Hww#9xO&j=NRHqkzYCFs}&oa||lLqH8`-kOa^7-$bA}Arv zhp}3#(GjKMCvS8om^?2h0tD4j)H|v8wzyw8>_E<6b@i0lO6 zY19v%M4B#CpkHae`|XT9Hj`HqSn%++k37zhh_la{)&n#9Grh*3kjv{cxK68f4MTe| zIP0){)W#jh88-r0*ITaQqM|Y%Q-PuP3F_E=_!N^7myol9m^AqBd=Oo$8-kFF8m?2v zSWNoQ1`Th~Y9|ofE1lWOoi!cWRD8WCrQv#;X|>G++tN=%(Gg);tcZG7l)bQ(k+=mE z0Wblb#$R zaq48gc1>kPkubwg8LjgNaE9(>JofUWz14B#Hdxqwx0IGIK~W%?Qc(GjxB+WzK+=GW zL39$S^tfGK)dteG%@Py}Ott6p-GwV52r8NkaZl9r(rps{$Dy0xN#qg` zE78yuhMV5pce@D?H_MvyEBRoWXViEGEwQsnf?%_e=3*z5bU9!4mwaa;WH$c3sB+{E z7K^H+ekPMDJITLY+Ju(;C20Jkc1MQO>Wa^dD9A2!iUOPFX(UPV^_HVELHR(1Xn@&d zEllG3>mPl=h)$4dvY&ln#H++BklS!z1emJx=^^pqoP#Lmqad@qgKVc6ydlv#6S%IC zwqatm;_Qb#tGrKQflCos4OFer zc6|~7NA6_uRgJ#UY4P;sUPKb8^(C%CR)_Im?1!;FrLgsdmEJzvDOK$kkg}YSzpCml zkfZ~Oo;Xs=M56k<+ek|<7}!xg6@KdAYjU=OY%8Up^UM)x@7+FV z^|Q~C8uwu%P`$;X;XYiJ}K*!+XWmBeNMZxDFy)lS?``rxPMz){#dMLa+HtD_iMesm ze&#wc^_+H!KT_Mcb*%(;w+G@CQH*Ujx+qR2AZ%%)ZdIMj0@}U=SZ!_ScJCxjrZ_o8 zUIrc|xF~Ox|E6K#h-ynKc~JE{Q`{=ibRluT7AgXg-?yCnE`X=u|MYF#R;rML$zTI_ zu?Q?kcU6Hu5P_TS44?Qi2~V&W_Kxj^@4C1dUQUH(ERxe&e0i5Oc%w=M`swmDSjA<; zw!n!d&%sB(%QwmONb~FbP?fvQB&A@%91R6~BcJ;`4}<@JNLWg$$(Nnxlf~B;gH$G2 zP*zsQK73fu5MiA<>vCnBD1HdyURrl5eZ7C$Tag_2x&YAm5P0hM`O49K4Hq>`GckJ? z71wX~Wb^cPXoyD7hrD(-Cw=mfm-|8Y9G|aZ3)|Wo!d}p@Y{l?=b&G7Al1h1%sf0F zf2}TdQX&2VL+!~)?NW>Kcx}9zx{)G$HqZGk_4ECPbo2S_&?YI8MmhtX0?bt{%+_6b z(4spMaxr=K@crFzc@CoX}&mbCwB5CR_5(c(ixp(Wt$6qvN~n= zH^jntbY5PmRAg>&>Pk8MM%}kAHi5(knqYeoVPoL3pLzJOAt_m>+MZB2M()x^!tgB?J>ucldi3u^M!XZE>hiyQi%cnNLp2MX;R#$lZ~L`nzkGZSO@8?WW{shF zefm_$GpNc$k|8dah0i0VA}{6ohrYz74@EfbPsUMi=agVXKZ=U))WsGluzq2jyi1Jg z>i_Ym`NPY?Z%}(*wd&EMYG?{_UErQ*De7@`(0x3S4tccJ0~nbIQC0F8NfDiqx){wz zrqcSn+S;e)=Gi>IywbWyov&3XHfScpjwde(~x9Vya%B#l_U7 z;t-i-brZk#J6B<8IwFUH#>J(@9BL?EpNSpR{5)TkGx4g&y_`|!Vv}52i5gpPgE>*= z#{4*sYBmVnPiWQkuM5ylarJV(q9F{f*H-n>LT+w zcOX}xid;$5zF#Gy4#W31f&Pnc*!jP;(@YR%73G4U;1oplF%~n@^j3&Lpyu_+^4%{B zf!$1eTlc6oFc_jA$>`dvH&k)=@q-aexo0eTd)elK5Xk?OeumC^wuLTm97D@6;Biut9sotK>zeV2akM z2z%HDO z#AmA~T{r+ad@k)i{ttBgoJ5NLcBH&<0 zPnE7qD#CEFj~8dDSX8fM`W&cX?9#h9SOn&Y&&LyFkqv$RW~zBYx7qW}L;4+sIVK1M z!XO~9PVL2EH%TSZ5U@q^7kl`PMd?q(s{t;h>i`mmC()(8R{Yu3=*+5HyS7)-8sdJ} ziG5dlTtNM2)KT$T&^04*NO}|P=6xu9@jZ$9g7%Xdew-jZAC`?%l}hAUcL&AHBzyDOlxpnF9WcuBu%?|$eKR7r@hll?;sp8|qs=YX`*wE>p1Hy;=6#mN{w4PxJNX^4fME|wi zIMEL>IUY;s{MS>-AA;N;{a@{%;?bmkgqi2tzL&pMaoHNGCY@81^DAdM=fK(V=PHnt zcEX$Y@NCEMI$Odd*>JQc+ha~+;@$?(;0d} z>hC`BDT>FnfBG-wGOg0014)|Bsgk`ElBP))+hPyzK%(&!)^c)(A&*8fmPjM@#sn7$ z35y|=X0GG*iWcG8YnA7}G-eyM_s)+Exson+?B&#T_cMJdj1(?T&U)2%N@WSh)8)7d zHa4gnt`5*chfiDELo;T&n;inq{mj4;KV423C7sU)GMX()2AsDuIxEXTk$ZEGsBE)9 zYSUv+^>XV~+Rci$7lND}*_ECgrO2uyaB~NXii$EMJUtmVmL9^UoXg4j{4meG#_n_Z zH?d0k9yC;hj(Y18I7b=_`^NE8)tv=3Dff0S*j=I{_){7Y;K5qXp*cFkV=wi1Z{L5o z&~H9X`u(2pGA7*Nzt*N6{tx>}&c&~-h<%-QQD;1Od{!eV)F^8LKMb$fq!=KCq3gX$ zYBW;SeweO{FhtuaEVr8F=#AmkvQv0Fz?PaU&+A>$f1R=BDKBs9M)T5X3&nKhIH>NF zh^TOJa>!?t+egukw!*t$nsE8`$k`GhZZgNpf+3COV#Rji;-a1<^PuUO`lDOgfks?r=I?l?~FOq!F_ zlXAGvI$RdcNZ&I_Y|Mz2CmFOxFXhEJtXvdL#a*IJgxDAtUK9=|{0=`&wk-hQWFb=0EUc?&1oXA5g51hRCZ=w*L05XVXS;q$yzA| z&%o)uaT0#)T2WRODK4oL$7TAE85{bjlWjziJIA=eFG9-S+OCFXdhQSgEu9zlAEOga`i95zr)7HkuWjCo;!kxL5jr#;;BlLR{V4>JF z1O@tks(IBIW5~r^tGPYj<%xXR3cIv3kiW>U$g>$qXsKaQq@-YHj?%n&U)^=2#@h|+ zDaR@$@&1ltCp8GO2YvhGVl%!S-&!-yGxII{(dBLULRC@Lh0CC zn@PSwLnN}t5v3xBJyL^lb_v$2BW~W_4JgEdLuzGZ)tCF#9305T> z2TWd%TrW}jrthDNP%F6@HzZqH2$~*?=D+uH$s%SNCK(&{NJrT!+Rf0YZSehaDqH9c zTXT$|7JXKZ68VY6DNGpY?%+&hv`|#iGMUz)vaM>WtqsD@sllK6?&AVZ@CTVF^*R9u0E8IGHZmr#mK zwlq_1h^DS(Lv$W|kO5Oy1)-UMNPPfw7q{Sio==;p^5(kB0H14e5@jh)hS)j}i?_u@ zNo$pZV|XDrDM0Y%`~^T)3{kG$ss%5~A#^pe)6Mg1wuV}Sf{mW%r$IL!X~*wahAQEJrX3`XQQgsld< zp;01YjKO`>va0HOZO2Cl&&4A(_=INW84`-R>=Aidj)EGoYS4)%{dmc$)T`2{%-RDz zLi=A|Y}y-U>2XhuS)#Yi86dXiRR*@$Zp#KsfUWpZr zYgBf#j0p@b=&1xF%W@{DP8YE$7W9vl2#?&b=CSHr!EN zoU}XK#m_Nv?#bb;Yo4<*+!sg$5x@v2S(42>qPjTfpl&Pw?0bALP#S+B zmulHn{SEUDJmA2!C7$0Qq}-Tp{}w$AAIQvLg6t{(Va^p5cOIqp^Gd<%oRT&GUkjw2 z{VWY`8_L_NWD!#rbj?=UFZo6-xoUW)@EcJvNE%aeDTI4WFOR(rv(LW|Q=$a1ZX0BX zqoovozFzScj+XH_TOwR1U9ZVmS`)~sifYZfM{3^9nzL|de+6XUG5O~5~7QF2d{ef zRmM!&O^c!}|LEe0(tw3-MM{c+*5^jbvyxwz3U(oags{H8c|&M_KG2YS^o*Ot9LMkM zx%mcto2ivGRaf*s-iQKfrrU|hK9E+^o5Gs(yl(GVV@pjc!>Y-=*H~G7o-az$R zpR4bd@6M|~z=tuocT!M@kwb;!yeY26wTF*+3-FSJEUFgL5LpoB++lTgC`j{8gis;m*ks`I;uOyjTxA zOLLvEiQSx#T&2;U?qgZn<@TfCGW7~3*_k&x_6mY2T(<_WM3{mG@#YI&nM^+#%yjf| z3aGM#_6}QI73f?`0t|eJs^$(S%Axru0RIRB*PL@(=nDw>wMp5R&|c=uHY|KCp==v< zU5=EWW8sOQaV`szXlOaU$Yu9pCKdA9Jzj87(R0&)_t?STyR(yOtbHvuA8(hZhF70a zv~fxb%WsS%y{UiC-CssFXwEyMPkChQx9sv=EThUD`rM^bz<=~Fmb;NykpIP5$c^6K z*3y{KDUM_fQhzP!<49L&s(4RS3g6VO+Ein*nVz|}5EZD7K|dJbVtgCuXXewOB!ZAo zqzF(_f$+J5zjZ&t_jCb@>^)f#v%wp9nl9m&c@86i3D$L>^!Hs-4Oy|)JdVUeuPqzB zk2i=xSMWW7c*RZPQhlaB}{@2XEPrdz4-PzJFx+mr}-wUK&RpqloxP zV3*uZxM}P2;aP#7K*vbw!=4Qcoze=uFi|^_B|NB%TZO*greMXQQ#t2?Dwo|nJ0r_2nh^%?oaD^qS8GZEA+ zCqo&#Y8=D-c1@GAJ^5>iP4TJSh`}|?2)0=dklEccjIc%N3NBv48d1t8iaef8s$RR~1v>w6UVY;XR}=k$kspQJ90}rN2N^ET zO*P#k>5>L)`$s%O4U;KUz0FFgwu^3?cTGgG=c47lEoO6bv$B$Gb^GV^oEL6pG)%NN0 zghFU$;q|1>zupqWJ3M@aYaAN{6EXOO@?5PatnOb4gcOcP>-?rxQU>dJoF7?8&B-+Q z`TvFjS%)e@?c<5XAt`9*ttGU6Q2H9Pi!*<_a>}f@`U%K;0FS)MqzM(UZfMRYRwV-C zg3Qsng+|WI{&42Lh;@jPANZHJ9FUG^((g+M_*Eq66P{*%h-im-1p$1J%pI7U&}=5M%zScJdWkS{w?54pK7h` zF+T4bGJjDdg6Mj|BO=`NP6tcE4mR0dzI@L8LpLOkKuOMm8&R0E-NkI7tCYkpPyK#) z^G(Q*IA^0f_*O60nx=8E#Lr1ngKH^%%}J0d;``Kx$U5D@R>BPL6@LTTukN`>sQua& z4pYQn$wldnzBxu?Sub-T`5Q#CO6z-O)ucpG_q*Z6U4`Nwwgr0F9B|$CLM3x!Y1*8Dd`Q z{#{(&SGxC}P0xn=G&C-rJ8UT{IsfUjhkM=vWksbi_RVxDO{FL(p?9WkWq02H`zCjK zYe(mK->M@^l#ruv!B70`o@IR!!R|b-B$DBt9UI$CbCIea=-+{e^9Ljp-uxFV_*$^p zTsgoYm?uQ72lL=A+Bw&S6ID5S?LbdaAimap+cB!NE9)^HsMxVMnlpM^G22T`27Gr8 zW9OER3L#F%Q-i3d55s4Bq(kut+Y&!wP+025=uZs0bGpd$=+yVM0 zJ$br7T51ehRmqIAvvPBxw6BPV*?cL{vl43#CSX1wA7zzZqZsUyEt}Zp$pp$(Q`6-D zz2o%)=h0uD>x8>3e+pLqNKyUvl^S!&rC)XEf)B-RoN#*Fk&*6|!Je$}wKwH?@j*t3 z>!tr=R5yJ^2Jz)^LnC;wQYGz~>08&-@sLD+7y|B;5| zcZ0Q0=cuU9lNfv20tn{_!wIyz&a8A9hHj!MpJ7toICPj(-4ojId@r-&?_Ur>#V zfBSE<>21^^5ZEPE|&nYryA>CTHn`mWGV?@I@jxplIBIlW|rJN16+lLg-jYGg970X zl2n#dFJLg9?DZx}^gP2!r@HBfupZ&zZPH9Wc*R2vI=tetvS-FO2V}ecmqDJ2bJBF( z^|62p;B05BG{lFPX}&SXWz}Q;*neYpycuA^ z?YHKrKc%1KHgf*86~D73AVGgQn@1|75Z%w$|6;XQcD4OpWlTuS?41xv64paPMV`L* z3{jO#K|aZOlH+^-N~0~OJFE|GB@x06=4^Mu*0APfqJtpa&ig%%8jw*ac54* zDSx0|$RVzf#TDzT_R&CwZiIU^>vJ}c*ZC^{jJI7qO8t6fc##W8q@x)}hyxqgou2~PfLdqRwKgy8H0>4Pq$6WH5(}T3p zCE0haVpWh`<`yn2IsMXq!vhyyCtGBqvaH8*7_f`|XyE0MNqz$t0D_ zma?nbKp%yp{1Zfi$*dJd%y-KRfI|&z!&i8<>@!nN*VdDU3RfMKScQ$!{&L>QQu z6QwczUKfc0YW!7Gr zP!2*!zAnoHSjhUoBg({> zu&~mqr-6tM(%@gRuG6p?&j3!P^w2XO6~WA^cS|Ug9!D?FN8RYBP%^45jx%Ztqd_;% zK84;sPb6feS5A~(!ebl-+iUw0@}F~y4ocVc)aCl9Ent)0#W_}lvQC6MMHS)%&Lk53 znb;9teKmcsTU!+10%=lTv#X;U1ror}(EK|uLM3VNFe1uDc;}|(`|Fa0^E?tYE8Od3 z-udrc{=r_R*B_x-XHm69*d@Q5O{VqiRJwi~^Qb`j@grU^-;%Cc`Ox?Hs*(`TsElCs zeVr4-32;g+(^Ta}O>m2P3g7qFyAzHqH^``S|4N#sX2a^LsdC@&=atv%*Fiz2>jGA@ zyyTlNe61xc1C)}8V5O?7dU_M6fo_VF@=qoH*IUPN3WH<*PdIZMhLG?9W|1<%Ezux5 z*|mxN@jUz{lni^TxeGAiKaJ%d=TSSBHl+TPeVbl)0SLHM>-6u$ts z92Xz>>Hui2h2|K5tMu&nByC$xugME~+T|hocR8MbMkM?54}~SYPeR2K2e$YD)Nyod z>?8G!Z!k^Wrwu$+Zk!bpD42eE@rtB1}96tNJswggmJ3Kqm;Z@0}Z4se?1mU;>TsAKBeg zZ3y&dBWZ9<#>iJAQuHGbc#hMqp|YrG<9Kr-2*PS}M1R0`g$G1Fa=n`CBl`-6j^Isc zT~F{PA-i^>75hz33e-7M>9Wh`{j88~E76F!F)~`SOO59HUQq7Yj=xU&3c*>(U6}Bx z@zovVYU2%YW>sJ&pY_^B%SO)7>7n{pLKu`XuJwcE*t^G*+5Q&~yB5nSW)vWVu!k~c zNX@o*xP9g!y~4Hf+}NgMqVmluL&&^$Pr2P^(Zge^)$xauh-{X$2!m`)2~~3v#9zM` zNJ)9~@rpC>&0qw@;QVuo$qJ~7Se=@iff~JNl!2C>9tGO{t+H!&W>rFu&q}L^qC7ww=Iun}Mq!#K zE}*&xo=E{sGT_iON7=BB99j_e0#UgBWbL*$B31x>G*c}Y`etEcMbv2S&FG)3?lIzm zH?WR^_<^TOA(>xbL3w_OpVc3M=HW1fKM)h{?`F}v=$mf|iHUQAi=5cIeyix{I@H?L z9bm075QEhEE5C!o*Ef|LXYJjOv>_B+qYzpVBS4xvt9BGc@nhtas`OxUdo3T(^Uoh< zxK!Sb2WG+6W7-XLS&dVAWZax$r8X$yUc?XYYulWJ#=P>n#O-q3)?>k`l%9+c&u(d* z%13UZ_hE9Y@Rg1udFx3WOAD-N z|D@w#wxKRnu^P7K;|Mq28D|J0he-UI57IFZ{J}Q9-+y>4${Qt(QLR0Ep%^1F<+nQU z>Z;&1hGVq=57ZMZokR%Jx!E?-)^4=DP;wi{9-ik;SF*@3X-(0OW+`n&+0CRO_*m?c zH>r>pDytW$_?yLr?MF8Dy%{>~mdIO`Ql%NWkGCEKA<*D3$4tDGEt$25;uGa-Z-G>e z9u9~b?Y0WmQ0r8-|NBB7oG-$wr*a$|MX*u$Gi%8Eo%R{X9tSlPp+y zL87dg_mTv0f`X1(1yQV1hRU92-dxh)3V|GYEiZ37-vf;2)MgzpI50^m#~%C>m(Wr^ zXC#I(F^(bOaD9Puc6EeeA6e7qR=+D1DAb`3mt_QYuTKG9jxq_kexd6*)w7ImbQ6o59A;%&Jp~EIM3X z@3S>Vrjy$^*J+633mZ}c&Jph;Pr$LHyHmGg3 z+f{x1;}TQNklA&C64lkX`9iTg2d#yOk6f&NTE^PiuTAvhZ@yl;x_Kz7y1GWhZ;S^c z_1A4LI_M0yL%6gS2C&L(O0_S+u^9l9(cD@+v@MY?Mq4DRKvlC1$>fWW?I7vTHzx;S z&w3;MSm{aVxuYIxYrS-D@!(33cu`(3dgj_hu%RRzxyS4+=Dl&xlg4H1fv4D%!B_EZK1e$MX5-c(55kfsjB00$9&V(+>%4hasam zd*yppeaNVq17|v?%~mGo&?;`VC+jKzX}8s#Sv5oIUz*YN!1F@4A=Ab4>;fS5j`jg! zXsiD@-n=5kN=&WCq#*%=uO`+3n(FyL!gDDfe0u-P%u>cKy$+ zGX1c@)ydg$c-5d@ zXWmjcJY&XgUy#H-hs15W?q8n(SS)8VMvWeO1G5;mz_BX&E#*c=G#= z{}(Q2$}JQyrUL{`2&UgMBepN6p#dZ+DjHOWT6p9m+Z&DREQt%mC(iVD<0Zij?Bg@s z08U-4NKTYV^V8wfuIIIq13DTzv-|5YKe9zNF(v0PZGiV>cug@SK&+fm!GIw3(Ekb4 z2f+CAj$2LQ(sF)_Ixb!}9d1J?)F|ax?EuB%O-;mmgBwI-UsPYlVA2eq0@Df%|Pqr!p)@oh|bCS!*)QkoVoMTKM z0yI83^A5>pQZFInXBIStVxmV0V$8OadP+(s#^(51R1GuVq}K@9q23+{E|ema3zrtgtOy(Yj|+iM|-sGGy4A7A5!zfV4DuoylJsmYFoOE&qc>sm6yZc<}b! zS(*D~Ttp%9{;?Yb7m(k1`0pF&=!g$naruG(v3|!ZKek1|j*QFB8q0Nub)Be4U0|vZ z^LL95B=@$nxcOd>O%lu=NTPb7uC-u+9O*1McE;B|A2*@Wk;9-`0J%oI8+!=hQ!PjH z!E`i>utW8(kegYlZ@1&D9i^5yU{G^inY(j%x_WxpB~MCEn#WFoqo4B%)|QgbVC($c zkbC#ET!2BM=L>A+gN43K(79wg3w~k#DUHJBS_N2R_Ir?NtDoqP`8S2STR;bjzwC*w z2nQ2?r;u~AeB{mYEI+HFm;Yph$hjEqb;iY7Wv^1r!9HGu)JLZwc#*)OtuK$;8&K;c z-xTPK*hc@O4DpXA-E&67CF1RgBTc9oQ?rt^8ubJ?PVY<|fL_NuzZlKlEh{D!EaphUB-U8QKBQ$AL4IX{(q2H z71H4Lxj572^X2_7YvW(Y@0Vq4Qfa<6fx`3|$3Eva-+T~Nb&RY!i>(-!cueJ3^{Y?( z_pHFHmp`{JB4(fTSpY)I+hRFybR45J&n?vK@nPG+9z3SbFKSLpMuHH50Ae(?doM>t zN5@rat{uoV&Pxe;ZyvNjcGW+}#BQw)S~Po|<>lqo0xM~`!S~$#_a?h4BfHW}FmA^8 zq}|Lx zX7jC@{bWD0$|%}_lhse!VEuGa#kb}0b(RVcleM_CEai#Ke#H|mS-?uLN`n)TM^pgm zuTImfs;h;rSODV%xPVlM;T6bmVL(;@H;{ZhbziMw{YZ4%c3muwWZmu{z-mc#N704( zqNmRP?nloNi|Vh4t;>QVEK%&5n-4$~$Hwh3eFn_E*Td$`aYI^8oA52gLb}C(fL*fr zkHSc#ZIbt>uta99+E9dAcZci?k>4NnNkjaj$4(FhD-IaXf}dqYIBueH_p6V?zow+- zTx3{4C6&}m0@FV0m(WzGr(g~=Tg_d+4k$az_jmD5*n3*KHD=oII~d3qn0ly{m?-+E zrH`(|syp*sJOA+Di!q=kuj7#9&z37>2~vI`79z#LPeI0?7~_5-rKW(-pDaw3hK0L` zO&{A;15|CkhDp@4OJoU4h^CItK+93Vkvn_b8E=6OKpOyInxy#};j;>iJJ(iWxkstD z@iwLKF`VS+^5O^vAy9;*9qesNJeDZ_d`6}hGV7bBR z-$V#l7O9jw8|@!G5!t=i-K-RJ-y+616G$T;)L+&T__B?VRJ^=-P3;%flA+(^<{8-Z zK|<;10@33+8hf{@mg5AqvHb{S-*3RGw$cyyPf4RK&c#?zsaz50RmyEwr7zJfzyyU^_8=(I274p(c>6;iI8hrcBuL;~4-KPraB7 z=0832u>2LV*4mo5BGiWm7k<@P?0p z*h6r+bz?$OD>tX7GT4o|4}i=oHPY~geaFTGEXwCY6_yWl2NJjm(V^YVrfl!uYiZpB zq@UdG>PiU4q(geg-an2y70>?|Y;zXy(yN6GE#BmGz6y-$J<9-8J{1SjT|yZEu5K=w z>f*il0U`+4@zn+1(Jm|YX*q37dyIG7gGas38>P8@e*I2+XGeMdCNI+kn9Xba=w{fq zezd4d0hA%nywt=F|Fx)m{>AC|@W$%%FUon0;PJ7s*`{Nr0$os8A4daMaUBn^^$~C7Ut? zIeLfb@z($%s63J{-IFKZmjOIK2d+pRs_+l(70SCQTVGfdpk&IYM#=&G!CPB;_(V}( zR`XM=4PXcyA6|k{1s`4)(dgUHLKv{jWY6Q}{0;zpA&GxLMF(btNC-_QL3l;RVk(w2 zz4S^k#-zoAq-M0*%fI({@Fbq-+O|GY5pS20MF94~|IUs6h(r})4J{`dbccR1e&ibeDM?Xu2&>FCb;CB3^U z2#jloOTGIfqS8@YGwwoshM`@_G$fRy(H;zj@>fhsU%EdTc_pH7pWnv9giSlJl;DDm`oT$2R}w*D zZ+r=_Pt&#EJ2=aV&rwjD$Pk5kuUTFM>H)8O=x}Gsrhtm@V`W8!Al>)8(v@n)0@x!!#W#)75J0#6p)VOPJt!xT5sHmvd3yP_!yn;Jg znaR8?I<-2mh`CLyX%ga(7b3^ zNo|Y_J-88G$}KM|lNd5amCfk6B=m3(SbB$UOAIgM0NsVhG=Tt9v*qrSk0-j>T;0O- zVm-aT&7-FZ9+@;Q&kcQftZfo&!d}*DGb-SEkxI30RlI4{c#qDTsfyVqH7gA(ZQI@4 z{oby<`Rm-k1ALRT`JHuPn^UBeOs-bG|t^@`fUBQ zZ#xcK+j^EdeBo*^VmdSPY9o^`HGvdOPN(lM+gd)dN}}rYlO9P0F`xgO=IwcT5ab!f zMPshJBl%V}M9JjaG&Nni3_S%(xOG5MaB(~YZ5A`r?g*2llu@Pw^~U$ZV;k^>U@ydqagho|H~sbncBzR|n^Fj#F~Oh{Meg%A+Gx zs+NwX<`Ya7=#{|B10)*@@GU;~6S zKq#TAD82X4YXIq;009)~A(YUo(mT>S`M2lZci*|=jq&d>NCvPo*V=2X*}pl{1lOW~ z?MKs_zPRU}pz)zD+XO-c{+Z9$&I?qFjFxsWVWkt7^2mf05w2KucSm8D9qNOIik}@{ z#Jt-XLjQ=GyMjJj==9vCV+T@Y*=FXM$4O4}Ld|@9N+!{6*K(W+O_E)srKWF4;R|kIG z3D;DFay$|yGAy{|QFhx%<`YF9d#Ec-mg2d6mert?k>~6n#`MD7QQ>hCnX4JCP-XQs z>4Q_2&eHh8?I4f93^_%wKB%sosr}&G70c-@$8^z0^q!kqdy5l;KzMCVjLywwdS!xq zuesIfULkrXfJuNPQ;_x~ah7db{nKoc2Wz*k(^>Y?i(y|DpTH>i*!x`!tDLS-w_pDg zW)fvF?r|;7g}{k@vSVtLUAWR^PC2)mxp?9GcLEywAuWbXD=TuG`K&|Uw>XOtCyIKf zZ_u{iyt%RaCspgw@rH*7!2xNODnhHk z;dP&1vI9E7mGWUprisQKOzD$t*V;q|OA5S}g+SERh9@vR8c9^Cwq{vYc8^9Xp0npZ zVdy8W9a%e8_dvef9pSpaEaUfsOaa z$f7fw3g6fMGLmme#sl-V%%Ebq&DJOivJtz(!y}gHg|ouOu`DjR3?~O#F~D74wR5h_ z>1U5U>`hS4NfvZq^Y+P&3+KZP*iH4h`)+h`wN8q-CD#=m}Wd38B(8_+pis?e@>0 z?j_sL`Z%d0xQpG*xUmp}$=6Jg+3WolWs_9hZnSkirvVU9)@B!H zJHrnU$XLfz<|AF98q{=)iiJ2=vxUh|?nTu=+0dsPnJ4NG6ocr(CSMw;4DlrkxV|}O z@&^=*`OHqo1@-0$oX$N`7w%=V^LX^WxOXOhQtBEjY^TYnBmB0Jbx?6rnMWR;PH~-ZZ$_Km-e{sy>}cg zUJ;k!4X`n4pqb6N^x}+YR7TU@>-X{>XSM?3+%)ZFG8<#AvS041{_x>Z!*dDWGG3s3 z7~I`^Bi2=5>X=?MR1OjAfv({@5Q{z7-}uESY?266FIY`1x)c*So~*qecgDu{AVOV? z(sax%t$jDNvV#*WsxM}FMfnqGf77mSy^o}V!u>6Kf~ji6h+K%;tw>yqk9c=eT62%t zgsr8Bg--j{rV}^U{3H5!7>nH>2-C%A?(@o z0w+Isdf(hvg|Pm(vLsN0qx>|qUe`E@>ZF@c(#v1>5xGgNr&@?8nst1PpHet(nN|_a^OWdCppF=Mi@^F&&#%Vshx6rE)3UkC0Tx+!f8>h2a3*-s zk#9+(t}sCfzyRc1uPak-DIas~inxpv#UIk~LLb7?L(_&n8Qi|VlL8ofNVV9v7iA6N z&rfd99m;>uPeB1t>Z9EbuWj7<~&YIq%IwM`-KE^^(9HU#kfP~85BvUQp&}& z*b&X2QPO49?f#s0=NvH}PrME+IGMh6J-zsZde;4r7WmL0D0sT^*(-=Sr zNKbT-zZjeNvIm85yto78in8s$6x;{IepO$R_ttJtB_-NnnhA=)e=#8DE82vz16r5x z++XlWT)~KK&}7q*ubSxwVH6c}ZLB=r_uah3f7dj2jquJ5HijF_FRECdb0G<7Y?r$l zQV(68vWCH``x~jAMHwc(<}b{)v@kR4O!<|b+Su0t$Z0xT#hx@7XC6KcgQTQj;`H^h z@~(`D8qf20H~6x%*l{)ES?8v{9nB%sfyGpHkA&l>ji&fI-YO_LWnp>igWIj8d}fAT z795yJn$yiM_GlvWoipU)CSepV2T>}!LLT1Na0DyEE_Xlo$W+hJ^`k47=H{@zz|F{t zO1C8%KC{cM=_CQ&+sq=XmqETjCmi$g8%ISPleb`vo3HL>lD_A2hnXJG#U!byafmlF z?tqD zBS89lAF(xIOI-VcPIz4J&e#-}q25oc$BY*NA50_TfoiaI$!vv$8;Yqqe5jg-Ux2A= zUFCjB6Cn1^_y{X^aeX<3Sk|8WMn_}c)HFls42}o|dk(03AsC9LwN(KR-!@~mOL_*~ zVFGZP=}do4p8NA)kI@-NsWr5F#GvJ94JWnX1M8%_I}Rw(Jw~K!Y~O1ekG%diKN?Srl0ajFkr@Ak0RT5ZPpaAaNz9i2=|uF=idce7&`i`i~APb?K(Niq-3FW^$ z$+?o-yu~>hE(t*61xryr4lR|#j|8q~=wu!iRcBXY7i4`neF8#Dh4f`RlC6ys{Pk^s;2H8Th6JYEi~!xg;mz_!%=Z1 zn@v%2=mH2kNf}4u$(j|n{|6oZZ0U=1>s&e--Hq(((#GTPgdQ#~!i(=?D%1$eoK;HiRmsjh zBw|B4vYO$$2i@dPtFm%#myQf=fhY_kYZpeu>*uSjz;(&P2Zrrr@WHNE9i8UbeDa~7 z)k(WJ_RV|KaVbqETEFN+iP0W#HtN|9o2Q`El`%_Nvspk*{%Di=ppD zny_XqWJ2>I&9K03yv+Cb=S@@D#=WP6!7;C*cdf6+jFPXGdg4IymuJhkOYpV7&k+u3P;M|d15G@U zzj=M8Yg?Sulfx5&U33k|81G3jm-5?a zq+zcIHGdXI2rFakXxi*l4(;=9`8@R`33qqpo?MZSRYY6zx=9S~$Ifb@sIXWh{#tumAMs zLb(5xk+C-l{Gwl_I*vpAdiGjD0G!D3R`_yTpjEegeP*WmoIxXoa{Iejl2+wV3Wl1K zQMP54$+mo|Zu8A2{iAeE-@)TV`})@Fec;FZ)en*W)`AzUGU(ZLhz+iMzLYKd70Kh@ zUH(=?b`ld%|C3M zH$8zM?x0~Ek=gz$dUSx8zaiQrrS}V-v74fVuLiDpeH)*WO!49~5#jKB%7<3pqf}pa znb;l1C8N7;7uS9BkG2Xnw|!oUj$i8)`Erh=VzO;{NTd7?f{a~#+7D#Uk@T0d^Zx#| zYxzE9yf|%RpS=!aKbfR_W=>2>(x&F7fu(I`oaT>{R!Yl!eml=dH|IKI*rfrR@mT>k z=9rYeK9i#+2_Jlka@tovlX*OT3qkPUb%DL`xW#83pJiI(U?Retch4T&`SK>_6;1!H{4uzOs)Un;C;2s|X+s`0f`V((FU!Z^j{;jl0E3|Prer?X((A}1}u zN#5m)saDTXuB%h&tWg!*_44lZ>B(-oiVU{XMtfD~b(+LQPNkxD=Xn?&-x)tSotlk3*3%OR2bpDbQA*NYOSJOVuKrR#YMR6+Y7i} z)l`>V;EtD_{BhQasuL(PVVDrEYW4(ooLYX(*~FSaMCbOUfR@DXs%!poeSnR|B?SHyi?|;#!V$hUlw*2MhsG~;7r>Rl0#or!0tc{TlVSfYxfcuCP8D%-wP5zpwrImJb|MLS* zN$#&^{Eoudqi;05Zw%K-@z467wmw(99-KG+czJTdNvl3K{x{DYGeY@xlG^8>f4+4V7w2SfPJGbbY;|$; z2^z3VeYN!bMcc;D*0@afbBBGc%dtP4bg5V5|A&)Ii-^+c*e&WWaPo^o(d6#sCd)F* zWzjzR+mR>F{7UEik;w>GQ}@k--k2l5;~ys~2c%cB`*!nw9eB|KUu1?dq$Q~6C#<`< zknviGhLzRKR`YEEi)s>Tz2EI*)%E+m#Q))&J71>M6KIW(rg3qt%SzT6a-Nb$rw{2@ z69oXyv9_YKUOva@3(o7-D_M_ll#JohlJy^s_EqD8WV{?-n%N6@{fE2%hsn*u;QQ$7U-9l9oV|{?0-Tuz#LExD zBFNfzcwrI&kuEl>dC7UT%zUDyHF3p>3tQgBkv8#ZlQjE0!Qsw0w=%DnnwYx65j=kg ziWli|`{K%~?C$=X{NHa)WmCqo`WY&=z8-Y7sc<`ov=-R1+|s&z1ce(%J!8Q^uKQ_@ zUlmHKy`#-YG}C8Pxc)yB|97T;NY#}LLZ$yP`+toxl1Pz)`Og#mXXL4>H(08FiL(Fv z4G?VlS~kMD|4kP7&93jxzt-u$sXORquZRCF4gX1^ke!t`{U6)&??GxUzx-<%{+oJT z$ryjS<-hYof8OlQ&(HA*2)equSTtoB$yQqBZT``=rY%TQTe~1H&j2<*TC5Gny~tkw zPrqIe2%H!jJ3K#+v+5|BIXyjHTRZLUUiT>ogJIfogdWD()x(_-$W+JM@LbSn5RkiMS?t|Iyrfqx%px`-E1kR zNQ%B54NVFwD@0zQcj%v~MN;z=3=a>Fx;j>|3+CxrQ(L+yh3z|ERT{9{VEr-5)S)u? zU$npQ?qy4|jI`Lo>!Sf_R9``#)Vq$8_sM&LGr9XAN%n;(V>7{i* z`_Fq%UydRU(CCuX)afrol=R|0ItB&?s;YZilRT9=GsDB7{~X>Y`CQR@zvJi6_x`w7 zPENSuvbpVy_2y<#?7WU%ytVPG5&VFY7N5^QyGDv?WF+a;o_%AlA^{zK z>pG?l+^pgbYZSnFTy`=07#q48O{r3J_@tJ)T6d``tiG*88nOd*v|H>LcisuCbEW|M zcJZCNa^QS$pNduA`REyF%?=aPXZkl))YO#pGvI-I!p9!?J8?QaiE^+R7}Gset)!e7xUO6ZtSc)dh%!1yt~BfNi8~UsTG~J&g)vsw2(h;*D|RUK)6+LH($qNg6iLB^^&O2Hkhr8fj`tL3 zu=Ur@NSIn#k?C?tS!-J4kGc`_C9aOemKY~0K}T0s#a|R}Mh~jo(iV5~5m7VNN>;yY zaCpD59Cs+AbYp*jQDI70pPq7MC4M~O89zjUL@ahnbSycpD0wm|#%O{cVM=<}oS{|@ zZ;UyOfeQ{lb6DILsp}T$>?4wlpt!a4D5HLWyQ_S!@=;$EJn78T@gW}*nn^lFrqvnkXEHOk2Y`hcI_!`~~;88W{g^ktyYcr-yY(R%Uw+k#|eeAuy9 zP87y@Q(upB?;*2(hm@|+vSxWctGAYl6`Z@1hp4Z3-8ac<11ot85%hMIhdUHfAnYpn zhEu}&_~nqkdZNOvI9sMpJ!7g3nJ^@`jyJno;Z5fu}oc#cSMWl5C`!KScEC z_vIWlFX#E1%t(?&Yu~I$pSiA;V=!zqCK;H08zmz>-6RdJ>hk>Z#2J+A4F8!{o#^=Z z>8YyY>rvJagkjIgz)Uf$A`$k^rJQLpdc!+(pDD#gj^trVw7_k0b=47+`||e2pF=V^ z@wj~LL35)Tvs=Q)3TA%G&838=X*A%tCW(ZggXz7*-cK@$cS?6QCKqWFuKeE`^`v4D z_~JdBYZ98Nm<{tqKK@KMpg~BE(m=Mp8Wm~^%FLio_7!?h@KPCJI>F{2f0xV%Ij!xK ztkwBe#prX_6MhNN=j`d0Qm+!iLcxaxA$V77ZE?cCffM zJY7U0QpJ}bWw`~>eZMM7!;=L*%&~NxA=q3*#?ir+4h~jrOwWy}V8MY^`Ef}}rSKLV&=y0>^T2YL!uJ#^rK?iB*{ z8@KQ+6k7PYk~{WVWIc-ib;_y^5VTe1>Kx;-oEV9yyw@y z*ShmKjO;)k_yD&Py+urhWG1*Zo}r@MIT8Dak+9R0MpxH0`O!$cClRN*fe5=io#A3IhFPWU}HlN%?^b&3q$T*1;+ zAqx(KEq5)B#Cux1%RcbzHxiLTFkhji<=PW=U8lJ_ zbB{sdESoE%(}{T?9^qRmZA|ygR?mMfry(Zd`|Z%IqwksZr_RrAD=t5`=&5?h7-z`d zQfi7n{064Qb20B@6vN(AF^P?GFh9w1vaMY&akg*nWUeLwz48z*TYbeH-Ngh)YzZAE z492i`&B=9}r#=!feDO$~j=xL0e9IN}IVlL~QV-+^>y=cLiP&{Jng0@q@rc!FmwZO* zR)j+|g-{?VsS@?8%S9yt6?{0CF5+>1aZ!LkEI}aQ5s{G*;o+%6&;RaoVRJl3|DK?NthiovcdMB%9Dl!Py4Ru68@)cbMRu^-E9bmY~Vzdo(vz z7e{03VbmvCUUu0z`d99}3~kX6|E7dU1m*diD|?;G(_W^CsQj9jBa?HN)oWc9&Ew@p z<(P1Ni0QA{xLB`tCzSslX<**Y4BFV>^0yu>2$U&{THm5)r1xV;brOa+{J4t}kX>aM z81F)YHTcuV8I4v(+UN#uh&oNlJbFQL?9!n1oP8v@IP}qOHo03Db5Mpbx z{}>C!z_FtIMhEc%a6mXV9^4lr&}ySQtD<2Hy}?Ed&uF)e3{mL5!97=8==osP$sW_V zZ_g+tWN$RPDokjc)U7_howb$j0*mN46FmxgS0*TPe9%}c!7?()T8C`X+`jV!1UfG$ zEL~%Rt+fPjg|#o2yGW>A%KNzxyO!UACpW9#WQwr0UwHQO?q4RH zL&@4R=C^cT5cV8CN2992_&dhrshi6Qc7mJ|5|WOJ+X&;xj`u9eYrh{m>%hA+}*NTDHO}@!(wSjJ(b62jUXGo!63BSmh4) zNtShT&T^$-9JPtP=lNVsXVR z_(Wftc561prg{qMC$Z;PhdHX}83iV&%>Nwa$dZyTi9D zBE|be87Fo&!UD@)MWTmqw)u!$KJ!&|LXHW<7`&79FNO{IZG<@^^YN3D@tGn}IJO5( zFM9T#41CcIjlXmo(o%b8Bp^R$Rzgcb=@O$w2dp5^YFD#9LTR-k2oRPqYyoRmTs7wh zp{6g*Tw)xs)&LP2@g&euR8bJXYYhUpV4;nqlX z|KNV(wtJvg^D_<3=5}^=o}Qj>r93=5^!2C1C^&E2yd50usDf2*ilh&?3pur4Dyic z=2R>#bag!Ex_(H@FBY+fO~r(Tg`JRvwVdDD-SmH`A!@5F*SLMW$!m#x0(m9JmAu0FncFt{%N4f|Dw>y6j-kwJZ@0aJkY$NMMU3C*Demd{rk zXalm+UZ}oW3GZhwN+z3QaCRGtSG_VyRc~No3-B@F-`5>>PeXJWHnWS~C4cW{CEi8+>YfmPZNbH#XZ^x^~XstogdRNhs`cox1=TlDnT#_4wkpX8`CFU6Q1YJ<4W$;>&6A zFn*cQ2+A*zRcvGvt`q?S%3;rBFCWjg5>77~SlKF>4iiEEz5MO7{Q)e$aoI;BORW-$hnn6@#^@QqbJ;RV)^MLPU5K(pRufZD zd*%I`28~xfvVQzE8#ExpoU&)b^F1TzcmOup`vpX9Wsl<3jC-(w=HuaB3{jT88OuB0 zux_B?osriZLtDMk+9}4?6L^Q=i-CIL7dIE|;)et`p}-e$pJqG{T{Jja#>1x9RQ=4b zFk4$>P2tXkMC0`aSZGhXY7UL@KNSao^es>b92I=t1KGBEDMhPh&c){EGMT?d^GQzcc_RiVYUZ>v0%QdOuv;jU=5AoT9$4}cn zV)7O*(ps;4TvU&LA*w^3M7XI(^3AWJ^P9&K2)}JKJ_ndY*6B$;p zlUcFxybby=tI(Q)Nqyp=bS1=nl7AUa&fTUY(Gta?*Tlb8#v{f@4o*Efk|6TK&9mnY z%xA`;w+`>)fj$_u(fq0E1gL9ebLhcz!=&zDa5@S*#8 z2LWipbQ(9w08jw^xpmX#{%p4q=)*Sc$%ZPH%DMq)(#bd?)%MgI55)gr>lSFjttQwJ zp!dPcQ{4Z$xwu$CjHjuo2?Bv6B_-9;?rvyeVFkwSAP_1m?1R+tUm$zpzv(^(2-H+C z(`;{TJ!N1R<>BGyPwZOs?M2)00>uo6VH|%w{Bs}I-%||$1{(Z}JfyF$4+eu(R#w*4 z)n#O4RNDFY_;`xWC9rB&RaYk^Ce}RK%K-w7S;o-&6@O+O@dOyfo$k-{9wy6{eEquM zpl54a^pL^m|1-$sq$qt*3W(nth&ja{p`Uqh3$e6VYhO!+?3d@SwtbU z`N{5rvp`GRYZL2LI`=EvOug{(q10ctV2#qa0K5+a9VAw})t>r1=H{7&?)$YC2&R)* z*|z0a(~Z60eWN1iERAuJ(cPaz(ty4(F;c5wwTUbl<&{}obgZ^)|?w@beciE zu|0t!uF8M4e2CxeDM{QT%>#s;-&EBW9mmyKUUgfHJB?^0%h<84Y)4OJjR~vdLF=tm zmHxqBHd+Aq2}Xj_s@` zP7L=Z2vv-Hg`XuT_Y-T*5SkqCF5EYq5zlqT0fmjGPn}f+(&6}(`-we5dzK1GpDC;3 zZrEDSlEveS1-$bU9@9BBubcQQik7)hMgYk$s5ND)8n;oBtlffPM8Ix%8SDs%@_wMp z3;Qto)SIABS$KMOGujRtGH4rGm)CfE)=|T4_}j^dj%26M#|y%}pMhN=0F(I)l2~yL zJsL2l2BVM}m<(OIIJF)N$xlK3XEJ0F0>D%$(ihJ=_~V?*^LBUSsu$N$JaO3k7%e}- zh(nHCCDol30oe?dNbAgB8NJa0YTTEw$yR37yfouRR>>_q~7Y{h$maNauNm-+>au9a6rpw zF?tmiw9+x-Y2_OtX{&CN=`eED5uSF@=q|Wdm8DEzK^RLqF-y$I4?@^@23lS(XXd7J z4HG+^lbmy<1oPa6HVNpMmzfNXH~?CnsPjV)R{F&Tp&3rdO$VhayV`X{Gt_wr z%3N<(e$y1tD=>(&xVo4)io>$$^GrwkFz!-F!e2#zMWnp@!U2s>mp^pPv9HVcy^V&c zTw+<|E~p}q<1ekSt@KB&l&9)%uP@`?2bc>%Dn1wqPUjQh zGl=uSz%e2#guVlVRIcc*&rimck%YI#59Z~5`_cu}PmCwg#;U0IqKtXif8MjCrt;@ujWIAZ=CQ8-Iw%URulcoNu z@YpsvR%WFE5AV&~>9pUE@GnN6z(HIaq7;dLz@e>@|qO% zf;5DWPd{JuBxLVfI8BF{j&`L}Lu7wfH(ly*14~2XpmeOPQlHo08KgzpD-p^X`jcQz zZ`$4DSt`a{>BQ0MS;~zXhU}u}Z1BxzA+73MvH@QEO8u6QsHMos7G4#^kSIIY(_4S| z<4Iq0!&U(+jNa~1Y;#JFdTe&DVAoN~&%gO6##Z>`_}DQmt-ZZH(;o{D4^fva(GARL z;O;OWUcY%&UbU_$@glrZjJAckYm=jV$X6h`%l%HUtdGu-%PVXM&kH5%q|BKGh|QV` zNnX0iMH~&V-(Gs3S9$<>bQ>bRH!M>4dq*cT=#LztTi`t z*uBXU(vDLTqe5U^Zw$Dg%v0n-rKcZx8b{9y8j)|>`H8D@3o%9hI`|HTM)eJBDT_N= z*vhA3EHcsW{eS9?>@nzyRZGGOzL-)$dA#t=Lc<-FpIu5>3e+Y4VQ%*Ts*$?JA*<)%2&W+)ShduBuJn9|C1@eQ`ETIh=# z9@lU!BnQ0=7zK7AGq@&G1=b)$l#Y5@weet+SqW3mNHCRLjc(4}5J(Qi17!`=F?#n< z9@5&>OLp=rGfFsY?bgcjk`g5-Sue9g8EL;WOZG-Y#Str^lyV`AJbz4_O5WM&w|c*$ zisi)FGZma;WK?#ouFu%MCG_z>4Bp`@aTWc0Z&fFu^kA@r-=*j4*LcXi{pCJNP9sKR zQP}?H89_n8Qy4#xhb^HMo0)lQWWBh4@A8`}WL{x;0Ae=7-n>vOBa>-(Pj|@ii;I%A zOiK)Ww4=XdU6eg@ZRk{R*(;d`=xA2%zD@Y^tCF>od&vSvHH!4Iq&yy7$2i?|bA0po zf)wPP%<G=3J4@60*K!!@?^jEb#W7m2z;C2`;HG;&X?LJDx&x1dPB)tUU<&POP(?B*JSFtqI9hzd|AoR?GGHh)4JTS~ z_Mm$o>090D7=b$J63>e@XJpv=&O~N-vXrau)d-Z%K^-}TS1i19O$~&F;vc?%n((_< z9W(Ji~(6BVP-NQ6dyzi#`N?& z5dhM8T)e#TKB{VJZyaeKJvtRl#eC&Sm!l=Pe(>$b-YfHx`iR_aNoCM z!s|J13VLQzob*$q3H>Z;-W`#ZfsAkT{G{P5&-M|~As<=FtXZF_IS>BfsiL4={vho1 z2FRSC+QTbgnNQhH&uB5v2X^;ZUJw9c<;fueAyr^ruGu@5Ud0^c-`ILz17Bj6qBd93 z?J(+!0@Pm;d(T|YSt1R|PVZR<^hX26O=*lbeOf^U=|Zvks$7QKDDJ1zqKA~TvYb=r z)G}Xk<=zOJ1BXb+a58ICBnpjrq0Y7_Gzl9u+!mDpeNg%K_G#j{jxBf~l+%SS`3oPS zliCr?WmVZs4gvDkGRD$KnyxWftvANPMh_j9$?Nt*EN{+BUK5)3`FeY6dvQIC-9lO; zUrUsWQCckmCZC%dEMh28$Jn*8x%1scHM3Gu!!6LMPUCHz?J5tw7V6m>5)dmf-;g|J zJ(~)|x+ot{JSAEabGJvV>!@|Ota4p3Y5eD;%u0_3({{IDziD66cwzG|U*;miy*25| z(cxb?FY7J{o#*rZScP8Ui{O*FTHUoTH@^thVyLY50m{Z9aDX1ShhV zliueP+{x{OpofpdFfTW~iLEjhg$;_+q<|3kBavhjcFIULdTHC6k}UqgXI;-uZ7kk_ z4TR10#mSP+l-z6H>cX{G>NUYiLA@3)w`im1S-`|`#KulXz&DhO)$>iV(s4Gn9Yxt9 za&^y+t_+mzT5iSzN`l`zabepIe3j?g9_gy${<*pxKHXo;+F{!m{d454f?Y-Wnjk7M z%M1t#D6b4zUWG#1rY;i9=omp0Zxk7G)|;nJAC-hjEZZq?YIK~CH0>QqIfMtneg*`} z0Ws+}*==*;zpaM6laAuT$MZ5=$$rE8^p|NM9bf0&OWG)#n z1iB?ajE!gfN+h>A+C<#-$?GG;LCwCf-;U9o_&2WS5KcxL>s4Q&&Cwds#`OfkF5aE%z}zWK8DE#^{pa4q~f{jXZro|^n|fN3QEchqO^n-lus@zF2zUmQ@u8=Ue?B`cv@@EEIQahkyK?J3;EjbdX8+p- z#rxX@&6WD&EraS@fiId-vNrqURU7+&KF~>Wzmr)H1<2`;{)?ROA958*4hId|K%{~D z%sNVN^%m%uI@WtyVt@o#L2uf>Z#+9(lRo~djlPCq(Fkzq|BW;T0t9V400QSzLZ8IC1z1~vFND+@)4(0aB5A?G_HuPtfPyi?d zKoi_`7~+x@Q8)-QlB>6I0)gZ+V^N1YRUw_2M4pmMmIZW=s&}tel)&m~1ja3x7I)JYFWAD%$2m6_8Y~iGg2I(9{&9`4R{oYp*XWZZFT`Zex+A&@CyLxS}w%r(!u6f`@nV1MY&;zwu%WQ60 zHph(`S4*r>O;*q05AWyFGB9L7THFIXOW9i@T?J|)iYG=ogOxxNR=rzpq)(%O>96aMCE564;AtM`jk9|=Js zQowQTb>5!YOnqwZKG7~@>rv#=@;kPq{KeG}mILUB5_4WPlQuJqFg-(uV`icU`vwXu z<08J;O1YKm6%)CD6Gl;b>9w!x%Go^Q_1_)Yozl7X?Hd?xFUla1nhp%R@zaGn>T*IA zh}rFXl0+8-sKb>nA% zu20UqIvg}c?N=3dk5Borf=ozWmXmL_9mM1EecdMEQnLps+*-Bkq6V1>88HXV z-h4i?B^3BHkDLX!0`P=h6yy#zv!i?ZioN*|%@Khw2<1j6$Nt8#6hD!(@lp2_c_rBZ ztEf}-JL#!EGzwLe>Y|Ldg4{QYgk7C%LiQbp0&XEbSEJ?K=1 z`!X)&=7p7_I9rEp3NVr6#fND)=~piny&n7lVWZK9JwXlBiyGo-2D6fmrFI3Li^0qu zU{BwZitL5Q+Vc+@nG%Me_M$K6^{y*^>z))h#&$WFhlG&vLS8u-x( z%zCi_UznGEDk(|<(P6H^TOd?^fzql+AFLpPSa~LczSp_#^hqq7^U{%P_jAnaiFV}r z%54_%hh1|a0DJ*9PP6jB_m`h;JKseBqmPjLQ%-GGbB5P%`O_0-v|ZAi~6k*!JGMQ;D8~JT0 zM!}IdxG*ywEKwblJC0Am8CJ4Vm0L*x<0ax4co#p|utPL~6ViU4LciOgb8cKMU0iA+wG%8gE`CKg_^-&7QUN;BN`TFm zQCq&Luuqoq!{H$^u~v+Px?^Kj_y$$q0@abe#!kMbVA|VkiBp6B#6YTCjy>{W&M(aKAW^K*z63?V- zT^p-wfflFMHaczq(sVts6wyPa$kxI4?K5b`Dl_T25s%f+#kkqdlN1a;MprUyA4y|9 z@o=oikm$^Uahq&EOVL1Ab?+Hwej?2+zwx*R`BDA*L4L>bxqb^~b%*%tu6oE;T6-88 zrlzUqGn#3=Mr*+73p7^!8@@5{1705GDp6=JoJv?W9yu5pwy{qQB`v{PE*@^S(2^GW zzJ{ycDDq=dC}3S@(oCSRB;^#*r6rr)^384}V3O0eR;Xiz85wRH(xmNHSNz_QlSBQg zpIcJ;GLoKp78V8;7rGBR7L1sjPO)jXx;0~qxcUHqDDWNzZd#R;#LU=ui~i{PK6v(C zZvLW(NA)Mf?Qx#Piqa%ZJwxp3(9v0(^9TCpdz_wH+{27Is>Tq%kO6^|2T2; zL;81%-H_A$-u>_KvLbyq@SclFG18|mfoIwKn0q;NsmpoOdno?~;k48@<6{?pM{GT5 zAL{VnqogAd%7pk`T(ZgaWqmf|-eG4)-T%S!^DOK_{wm)4U9HjEVsJpGz%9hTP%@Ic zry+~mU$QaBE16Offy*erBfY2kq%Jfd@mo~i5a4;4PtF@h>`{{6ArVLxMa6-96%XcV zokzw_x>Gj9=*#pnt{otnq=E-WS{@$oL#Vqg^5n@z85;cFh<`(F<>XIh|Gw-HK0>%I zUNUea?uLT%GTRLA!wABHs4+zVZb|w8Pcq!_!HrDw2L8?#<25C3Ra<$)9obKqh1 z>kOasip8U;=lx37!ZOJa8?^JC+sH&+B^3!(2Vrl6H52!VBvWhWpYod1On6~_jfIQ= zM&S&>kHJn%ByVncb3JMD{RH>8ycSPb6SY()NgANM?W-*H(4)UcSbeMis0@poVY%~^Q#&=dU$j{g4A)V{6)MPL3<+%_cZ6EH(rZvg7o2d z>W}wg$M1~8doCL>H6J~aUio$jElE8?0WuBVuQSd*@($zPjGRjOvh^@vfRJbY)??zh z|DpjBH0#A7zBq*Ve&Yl+^vl(7KpYefaxFHie3$_UYJpzHybsNl)~`{^!rFEYRv~cq zP#CCr`EWM!MGNDx#?E^S_&0Ttz~4O<;eU-#8O6KJ07Wu8rq6ZQ7@)CqOEW}6bkd5g zktbZ8C)(RMeLJb-LJ}=-e{`VtjR@a^F*4UShK(9;Yp37eoBhflYIWuWM z9qRjTv`zBD9o8f()780Q(Cl(ed>0?%D9xK28kbMZ${MQ==KEj>81GpiL>zWM3+F7n z(-~-hi+TegApsclj!4^7*F1dsx%BlCpv0PfLny$}#NFFh=-m3Ivw8^+D4Xf6)JQ|i zG$e0m>GKGAyB+4>r;xirK6<6gY!Jy3dn~t35*?Y-9&6*!c>cEcy*bHNQDWN!qZGK-udQD-qozpHOhw@wBhV*4ZdP{je)^90vo?lR++39 zix)J#@|esj*=@eLKITv#0P=ov5f|fgcNXwjoF%7;58M@)gI;+&YDK6*s7b&0%HxMAa9t0+{A4s! zxSGlF9i^vF9ZV8aETw9(!VoH!b^3k^i;pb(rNVe;(x=3ETX)Xksga5EteRIWJ@bgc zx!N4=E)}6Z5p>e)|MCz?s`C>gpAP-?-UPItD^vD^=YKB-5>?}}Jq`;COI+cWo4mst znjT6Ceg4uRo083D5L^}wS2#9G(t1EkpdO6fCQdf?ryyc|N`;5n`#1C;Isegn!F!R| z4ccoZ0L}gX!9Y4kE$)0);W8~h(xjLEMXhmQX=R0Nd-e(TiIf+r z%bJjbS>Q$IF)Mv?++SLZed&XZBhX~6leaJb-U;b`gfO5+#_*=` zREIGa2w4%|KK%PUe;Y+zY z=5%85jxv*2T|Y^d6qfRRo%-UNkkb5$2TtYZ)5OEvE5^~koUD0Hz#b+laK5>8E2)I> zM6VadmJ1#rSXK=)Vm|Rf3705bu*&W9#73Ar@a z>3a*=T4-}TRjY|2o)4;jauRJ_z`^kCku=f#W`~U&tCgF|-~{-MD_htLM|n*k3W8e> zklconfJ!g-oytnNfOEX>cNiUr__@?{)h;j8;=w98kycfo_d}W8hVr?kPv0Yzs4vwQ zkEnF_HR0<`??1G-K1q1dRk12hH8O5252(|pio|w4&j2@FbDtBM1Y`Tg-xYz*D8<#B z5czZlxoI={d|U^Nh`e#1(D@-k`4l+zEKmzlm6k%fmAvJ3z=$g0K zek>;1Z|Ssgq^x5(0%qF%p&Z5_zQ+jo!M2=Ye|wjy*VVw+`5V{XwZoHq8cxb)T#TO- zffM&JCUk)e2_wb-=Y5Q;FL{ToHUED+M`RNFU5tvZS3H1_O|;B|@$(H8FmmSq4}_Va z#=lC_*47pm0Ah%K4Q)@@sZtsTq^=6AZMVNz2CgWeWtkgvwW(mAkAlbY;1um_&tnM)y5r|y{h(i|B9 zx+6}5*?F7@djJ~12D zWqAi<4fF5G+)8xj1}SYSR<~M}HT&%;Y#kM2Vq_5A{&X7m?|ItbD3-2UAT@^x*f{>| z>H3QjWx~bwg!X@9={rdKT#p)|?_zza4yWHjgzg{L#6*ZRqIRt}96q zY@phKR60i|XX+KF1Bw06Zf;V!e)KA)(>*(|)y&m$>gnSy-fGzk>=)lrJ4S@_uc9pB z0Q{oaASE?BxvqhY@s4dx3@vlM^B{5CHPYJjn*S4#kB)iwiX-`!80AQ}WX|w@;9pJE zF}v8#aC-sL)-h+Th_52R;YJ90EEGAXedr?+Wn4r{ElTr)$lm6Dv)O^bo80Bkj*69{ zoLsmb5KF_z#(m7YtOK?x)b9PbQv|!V#^_>`R zKS!fPI$M@!&|rpqwvmv^9vI;Tur$Hktz)X=`JD*QFWG~W{CuV7@D^cJAI7wf>11Nk zix1VvX)`THw&45AlC2W})(GL+^SRM&N!`ag;4_{5iaZPr!p4Th8V&2=M+=i>KS zI79T6@iNixN0FpFgywz8)9moOS2iFf(sH0qi^5i2cuIu|r&vARWImobwObC|pMt3I*@R># z7sKYG=%_Aoca=|0NdA$xN6r4;wB);`-_UPy`^@!8uf*6ogs4@IS-MpbMtK zG5dXO#q)LhkmQ_Rs;7$6WG8KnVXWt@ip%iis$OqcY#1J#@42`Tr}3ILvDK!-D%_!@ z%1HDTS1x*)qW>iE0Bs5|&seM%H z$9m2hSXGdF@}eorYSx`m%R<`u`D43S=b^Iw5qo*Z?@7Jvm02tR2GH=+*$Kbs=9ry7 z%`0#_VMcD3d-(aTU3$irT%#=#_#6l-RQn+Vz5r4N!~EN~YBHY(Tx-bIbLq zh3TpI`ZeH3jm|xB42+{+2vatj*ZR&!p*FVC&PrTRf$|V*e1TthQd@6}(AyQrJs4 z%e>X^A{Vi|o`{JCqA*28*I0>*{{}psnu~Ca=&miUte|{ARM$U}=r|3sviW|^k48Pw z+z$9+yjs7wl`ou8cZrRV) z?X}4toB24Uys7GQ;_&qnkpFc7c|>)dF5lL>&Hn82uM-(mG0@X4}U`! zfh)p%#!YK`;PEjf)j`QX#g%G)n%q#%9n6FiEG};$+`uvrE9L^* zY!B>kq!Z#U>6e&6CK_%kIg0$~^;@2cOU!x(F=I=ShTqkYl=#vS6JeWBMF4q&d-O9s z`}`dZa^v9fX2bYXvT*n2H?2HUrWmKG|1+o{vWg-8V6w5OKg9M84T{3Hq~;-L)2XVVc`DE7vS>h&$dJzcb_z;pxb2qh;j(DcdUmhNF>sAsMmp3{M$^4hH2!GXD-t*=2W}Jc+kL%+i^tD zMFTW6e}249000S)fv>`6lcBe;gcvOZ-(v>CFK1`%zGi}o4rF+OaW3&6ZxaCRpG&KX z*(L$K6~UY^Z13R&~|S0{<0Taae9+QLe6nfx|JY|KFF9x zWO$7FPlx4=>hS-<(y%+b!q33VR1{qYEX?qM4ncbFu>nDBj&B4LvjyAPC)>}1K$T%* zqzdK21pvL^_z-?ZuAmTXUJM{=0jBv2y# zwh#PZg8DX6$ZG+zJpeY5EGvv!ljv9*v9_~ZxWg$Bl@dhCprM$Vt!eME3n3Qb9@*pD zoWc~rwj%Y=l98=~_jZrg-skvm_|R@FYu(z+wcM(Cv8q1kppOIq8fFq_GV3a-TE9HG zvqG(#mR-DXdc5jz))hyBo6@X{`HlN}t%L_E_EapIK$7Els|hBnHIULgvLu1xq$SyX zc>6~4-=WFvMR$Msfq$t|uX`}Gp3ekd2$Io-H>TRQmpJU_TMe{b_?ejMcU7}zCNBpbHB-REQ+I0z1duaoyow^}J$n+47s ztKbjdk#FgW;SZ;Cbzh8=@Q$6DbtI!2-y_{EP3hSZd*$RPnD?9?mFOXHD6FLfArtS{ zfPO1{R2v1o;SHMMA_Pc4l+NMbFKn(mUI5a)MD;?J)C?ewu=wflK~Nd&t5 z;qh@%0Bn1cdwvqH;|BQto)hm~>%WwUs`kr`wq9;Og9Alz+N;VprQ@eeb*sUvC3#tdSCuzh9xP$1EfHj(>kS z4n+1`nWwIor1k@oQYLu}Slc2%xmEBRSbey*{PNoV-BKsXP06Rj61py!BFUK% zvY{tmt##Rm%=O5CB`CLO8oKi$r7TTwHfm$*HSVY5&aVfoR)+Dx$k9C558q&<#aTXh zfFfU~Wr503%9AJ4005A>mMS#e(2!m$E&>tTjd;r^fI&ximL`7&BJHi`(`0E{)0pz8 z?(ShHb=F60rUDf1kF8fwgVJ53_&QsH8f+2o?}C^rz1HC{AO zUq{0++Y*`dWM(_E6lz;CwXt0o0j!pOv!^6)=4d2prB;HyJHp~2NP?@~nCDdP8UCD3 zDcR6HoJ+)PpoGF=K6FDNRR}9Xyogkdw3SidZ?307Sk1CQt7kQM$ z*-J=_Kx!(U{txGmC5i0nBui3};gjy$a!YU{Nqj4sK7_k>ZZhxKky*!7KETjQIXrKm zQAht~Yv&mI?$OhCX1<=GDr3e=iO<>Q4B9-qf1=#n6CCG64iIxmb4YWmlE|siPF4N* zr>r!5EH_IXU1K7Zh99m{?q;L|j+@Sm)Ru2TQaJjiDssHN;qW(GUgzy|-srV@k^bl0 zpFy3;QcA5vo$HhLA2)kp_(II(LE0m>wZ)eky(N*tk&cylo0#$dCL{-jEw!tK^_ky3 zafP&B$@iyU0in24)jy#)z+^qt^#`I8P7x%N+jm~yo}70b+((yoZz@y=1MUxObJjTE^-xZsK3S)E zj^;$#fRJA<-gy`NM9az4cDAX*o7^;is4axsj-s01Ba^mDnT6l|-rBaGiBULDTQ&iT z%>--IWBQh6|0mx2nr2*X32~@kO(X6CO#}%S#0)gXMDXTNx-Mx(kpkd&(s4o@7s6tV zKH{Oh3;6KpfS&~VBEN1g*0|}-Sr`nO`%_`f>->85El|x!mVhXy$`z;i;t1ZE`%nIb zAAKMcGoV9Oe&SH@-E3tw?UTUwWxE$t>PhhFi&#C(P_`En0{1zEKCV<(!*L)(o7b4+ z=k0lilH2w_w)On;FQzN>=n6v$3ld{v&=KUXeB1{iLJ-3ChAE=EX z6O)N8e>bn~cABw@x`B%PEs$pS9aYDRObH(;K{+_4qFlz>;+qd}T2CzJ^gp;j0Z;r7 zBc!GMI6^WOiB`93`n~2GoV$oiOw>3yqj&iQ99p!~6;AL~u7a?OSHtM(lEl+>cW z13|2K%C0Wwqjxa|u_26*u110Lpcnn$f_X9j1gR&ujUhgN*)^zMc_ZvJyiZ3&rbfpM zUC+fq0`CXwnI2-;J)U#^s*Nfr(_$ML)jS#Cb zr&GS+{lyB570lX`Z{57y<3iq@A4Gi>f8^hiGsU;D=~Eyn^kvEW&k*{R)}z<0D!W5K znOXV{$ZXxZ2x^yN1u!Ovfl~$)j-K0VyJcP`4F4;||0{k_0(*UjeQO_Ymy>@EU4KpG zY?iOj0<2m2yTZl$uP$Rrr_4y*36p$@$zdZPhb%Xzw zmoYFf$Zv4~)^CS=NV>g$f5i>T+1p+HORiD+E7!DNUS2Br>|$X2kQ9}Z+%Hf8zA(}2 z!uT(U=yv(akBUYQ96$n!?-qfy^RodC5Muyywf zUmmVxNm<+}Zgcz+uF#Y@DK|0zRho`4+t^v&$(>CZr|eaqErS@0tDZ5&q~3f#x#t`7 z`FFKO6x?n)kKSE|!J9{7)VbmGr3@RLb>`k(w_%D;5Ny`%c~?L(Kk~f!0XsVQQ@2Fq ztcp&a^V6V*McPbxY;8~ra$vkon)+9ogQmt$_CBO6ZYj%SEj#a$CN zcj;_Hr^6r>E9Fb*7aPJUe6XN6_{Pq~rT~Fzi*FSFX!7Hexl^v-cg2%RDur zhY?wVp3=_jo8(zMX*R`*QjqN;%53{b;EOXbL zJDK@xWZ_Xbrm8IN%@835c9%``#J%P-oBkCvR&#qm1hNRxx+g=#t6%#9D?KJ2fV9Wpld z@Kds|3^FC89Rzz-E>4n*=;t)mZrR!m$6;d`p?4yun+>|^dv@Y5Pj+4-Jqc^sO0gZ+ z*13+plL;_AW+M*|C7_n>t!MQJ6^iiyyMMmX0~)j1O}%hZ_@PAa#7Z^^lRqZojCd%Qk;PoR6v9$k?*% zI)vADB0*Wxk-%L#i;&hVjUYcFCy#Qro*Q)j$s_IPOI*)ls-BTUyww!KXx$9Aqez?3 z_=Dof`p~p@&%yEZXmR4oU8^yq$M9;;NWG4`TZFEw^IC~63wBJ_SMolHoBV8@!}yS= z65fS}oq|BZD>b`t+(CL7m?DkpZ1KV8%#G?d=$~iPbgKd)ufVKKOp%k06C;0B_jXt;@y2dR!G(*@4bvK9F3JHIH%{PPek*7eph^ zjobOHaPrn=lpsdmDL~AAK{r) zB-D?WjH0accqEAL5B`4naZSg;CE2ggc`!@0AGbbMN00ckm9^>mE0)(g7UVCYluCMD z$w5+*(bYTS10#JS2JuD7`cp!`=4RRreTzeFcJ)lleA?$;IBm91x&U*QaBPeaF3(cJ z%_28}Q zf}eV;+3~V$hATa?QP;XQS1x8IWq68{S?O>XtU9++eBmfZ$E3>bA-?QBhcU=r>BDEc zC4)m)Y!MMGT+F+cxJmn}DyLdcK%ld0@kB}6iIFY4uwK07nlKLztkag)CEC(i9G4Vi zu%avfX)vTA6UmI`CCJy&+3IitAANFNoeR_VkWlIGaH{31t*NPcSQgW#|*+l?Iu~n6wq<9R(nY-$Ubqk2IgMwX9q) zb>-Pw2xL@Mt!$C9K29J5B^Z~C6vdxuZc2cXLSZh#dP{_6-=gW^pS}&7nNi`K_e))6~_oT5%c`ChtQ5Uh>$9xgxr|$HlQc z#e{qU?J(x^u7QiQVMEM_AWSiHUY(NpYOF6`nAB*v2Ju6vttgcP4wOgCEeIJIYZ8aC zBxg%JGJ1iYipQH~)crp$=5K}w3ey-z3 zUvL4FDADy@)NCb}TxBbltF_13e6PpLVnrE8pgpJMum{^UXYJ6uE~dIWcA}9^95Vq| z=5U<7)9a$V=_3i}TvozGo%8+$K0aPeAZB7P@mZ^i%6W#=q>lJPdZA8PkfVB6}LH4FpGtU zzsTF?usz*o<*>?NfrT4{DOsKnD&6wZXI@wq$r!uBO9YwMCZa|@hB7IOJvahC5=p4$ z$tcd<{+eAIJFK-e@%&0&E+^q#cqBSCyn=m~{AG=e{$g``UBM6z+(Yq`xAv@!h0D|# z5*zLfCG(=al1an+iToh*w9g|Fhv;Uv#i(CSve@>E6^Ba%Y-=54*>cp1ZK7~VsctG% zD*mTuZiCwE!Aez?j@pT5UT#ltTgD`DmSFt+q)@$nq;QSwK&;wzrHpD3r>kMH#;>*> z{KXv}+Z6E|W%-mr?bv-e6HWPPD?VIY@a~_gEq`Tir3w-X`UisU`s&A)^#>(rGzp=Q zq_~L`Wd=X2vkjPNDF?RJPq=C*DpaeFKd$GJi{&UzkPQrK(pWVZ=H{9}Tr4A?NmTbOV`Pt~X5|8pyRrQX$ zS+8&(3$wflBUrKM4N9EwXs2PWEnZ=PAqLNOqS(DW8dwGNl***EI3{d{Lztn{R`feM zpmgY4$+LIaMnI$Gl7*f>6UVT?x|iC?3c)N9>BGfcgL@b8WAU>o z_Ps575#X(9o1HICK75H%K0&HZm8p#u)mG{A`CBcuw&%m9Cs=_9je&szBN1Rino;M7 z(@Q!(W!Rtc%7m>gqlYRDMO!#>U%MCD=)*9B2!>U7wyjE=6SAQb`WjOenTNhw}~$N+(>a9MZ}~L z+Ba9aA?a>m^G@T!K>7e)Ra<|2Ws-+jOwAB1)I_q{#P*z0nYhbm!Y*d6tnSIDN{}@q zu}{NOP+$Fjzt3A;!bhu>$M;591R>PXC&H*i5{`^URMrtZnT;unB19jnY%T{THRd=} zV+oWH9@~!PD^w=H^AsVUt>6n*xY%&HPKHK?I@x|2C zbj;SzjCtBoI3K;MR@63aa~o)N0D+cxXC5Y1RF~=|DWkGj`ws|WeQ6Quqc)N3?1n?HG2Zx^d3{A=1(I0ZLnj%{m<)bh6OB-F&c$R|R{{6W z$oE!`6WknKoe^B|C;P(?$yUNn?*}KvXC~j07+fA-Ai1O;kiXpGsQGM z$cFjWx#pdS&T3EZrZ@lilu-`>ePV1Ky@kB}sKu=q_C}ZVIXr8fUTxD^CaBY}0)+r% zbvf;6XjdJ2N64{oCl2BK0f=hWfT)I9596{wOi0o;L?p4!AkZ(M`*dRF0RKuoA$J`Su98tb+3mhN=&Y=RDxyR;qy%dgC5}2|+PN}()-y+$S%ICf)^((L<)5{~} zzC>Di!AGwrI*r8_C*XJiX>ALjC=esASQ9%RsR6RL&$%bW>jJkVX?d#6<>xB)iHJ$A zrC03_+WFn=<;j-hBTdJPdPuaw8_Ez}&S}Xhf)7(1m= zpLXsTK}ZkfzIsu!L&xaEhf78?Vq7_5^co{VD+c1cN2T_5I!PcRP1SBmrCQ;`@d^K# zL+@cu90KX8u38?SBvaTB;z-hPa#|mjwUK!k{bF5j^^IPP#?BPXs(;J3nGl}8)y*=l zN#m?vc5pEIT%g6)>S8+x=MhAa@r9=|pRc3=5FqCfgA(Q=2xANc$}zQ1D8D^D*`fA2 zK7j^3hPo2jk($gQjV|;2v-b_|m?o$96(d)&(02!e8UhhL*i4sdnC>TEt{P3xPPoyJ zgmo{pO&ug%pb>X~U0wd*Jz``3D z0~Y?fmpwuXmnl?_kjHjOog$h?s_3I$h(6ayu8$pZZfxg{EUu|#3*&Fj)wahb;@5w^ z722ZJ-u zJu=_(`jb{8&SR~HUF#JEveCxj+Y65#b~)B)r++aSEF0u8C8IcLb~{ncJ&Tj`B4%OP_M(%=so*Ar2X9sw<%L$)2RCKwYt8gwM0zhS z;@T%QHRtWx-`N`}6h2cg>KQ-y%xfj9BCB1_j+6u?YR!k@4Xe93Zz3VK%1LN1=e#Eu zU;mS z-Pak`X<(Vyw<_z`V^=+vyC;#KF>MFk(*w*}FM2^8Dfn*IZ`Iy$OZ<35iu2A%<_ zbe!MNLug!4_udgz&25&jePw3zaeMaiBNH@kB>_F~$UZ7BIf5dF7wY{@aYPAnXHAw| z%#0nPx=f)bJl8)bT9nn6ztf<@tPnqT5MRFmtt%{?-w<+4e{7=g>mZZ0$O84#fJt$g zY1ao=Pb2m{MtH120HPo}B$Udw6G*Ek@7#L_XDpxK&Gw0Gt=@6H{Lui_e@W4BHjPUz zY-dEk;cVlr_s4Jd9>)2*?OgO-H&dktcewQY5#dVfL;Ub_v}UsC>XQs_AUL-j6`R9e zBL;c|z*y(Wc8Dymwcq)kY~8z1Oo)pUIkm;epc~Nx0u!@mx8qE5ZRRvKPFCMgm`iZ8 zRsPO9AI8{8(tF`HaEkNkbPSBhuqmLnj&J9;e|M1={ zU8a+Tg@qWf)X@C%@lCCyB^w5iQf6EOw>aZ^6nKx7F_@%Shv8e`uT{N&y1zuks#BoH zDV{6raa16hnE^FN2Gs3&fJ63DE4-zprL=T= zrrxR6dQw?Q={<0rU77i3%+*8~6nBBmhCWr{WQdsKUrdvNefst%f) zlyp;axacxhT^C?9Lzb$mL#FE~@qrAk`tizRWlo23WT0-q$ItKp+m2{PW{zyx1hw#a zcY(C-x}BSRJJ+_ny`NP0-4Ei0XM8@J1nb}Hj7A^x_AyD#UI!)k zh5Pws_a?ey!5%+8z=q+g-|x9%cw-E3)YI@tt&xfJ3x571eufUemwj=y zTD$o5$eAf?$A-+7!(lc&_Gz=NpV0@}k|n45q__RZHe}mmR*<_75w7BVW{S$D=R8(V zW0grmEflpD^b!|iJU(+9zW}CLuSUpy`y^E1!azHB)k=h;rsNfCdI5%VD}?`Be%Eh^M)Eu}8LH?!rL zK*=lRWrY85PR9u_b(hxUMJkqh=HA zNqB8)OFYp#qacnQw?2q2B(jO@^$j$N%dVQ9& zw0*BP_vbCq^cf`dK-ttCDyUMWwje%@6&5v z@1`e2wlyVCf)-^od1&Mjsrv@Ab(}N)Dd(}SvxF;OiVEIIP$AITNz8SP%$lr8U2PQG z*5r-<=@D^#<&<*G7UzYc-iT0I*ApmK7>GvXXvp0~xb-BT3A1(>mqx$GYmMjyaOY8` z6pD2jPVowBPhNfnrfT>rFky^c%YxW2-VzW9CEE84DXk z|1=2{HnwTd7)!?q)t>I9UJEm+gtC@W(qr}4s+GUOj@g8!BS(xz^rYzYO9M= zA`N*1-paN}~6juk`o_4Q3L<o6*eV??-tlWwe?mxm z6wmm~0j3Gn`k0ZHAL8-yt&nFkpqqz|0j-) z&u%J7iJ$uj?aI~J`NZgXk$DB#BADsFpA#?BbS^9`^Bc^)clZ#y|7EPz$+STLR5rGB zV2PnvELoNnsSg<~T8+o7t%=+$#Yq-d15>(7!E#OapM;h$r=5u>LE;}Y@O=uE;j>;m z$25Z6FYlL~T{cDOo{fL7c%EZ+I`l<4BISEyNOUG70g%aNz0`QPhB!2bDgKfmg5v4zY2^|OG< zX;ZBeb{?3^aY~E3nlDs3vN>W$;eB$YquN@DqhV#~g+EQHbk&RmS?a9a&k9YWdzW4v z1%Zl_ET;7v{=Bw{MHr{LR{AB8Koz&Mc-=~!Gvs}eX$Pg_T!@>{==l` z`_3+@BpPQj>_1JGvu1}S+pLlft;)g8t~S+ld#HrdHsi+xcsRaZs2Cv9SlEUv+YO4DP<0@J<3j}U<-W>b(oZ8UHsH2r1@JNa5Vlxws zuH}4*adEk*!Fn3nUu_OUm02^rh7xsK?Qtu2Rx`5%^GX~}l3rhZDP;tw9YK6h-?EeV zvxX%iU6Y#jvwp;9E~p=nxYimtXl;`G5Jf#pN%O`($=79i=ImSp-;Q-2_BwQo(TI3k z%~AdY%5u^7t%X@_q4=V!?l@eEftioQlD36jM~K79pV3@FQ{bH*lbho zXmF78Q9A1|9xrWdTRuj?szoXuVu036crMI=;F!O*uQ8@!YMOm(5Ke0poW0#-G@4tT zx0ux6km0xV+MTW;?5efwO`h^+2dmzfNDTgm&j?1nKKI2%bM`h_uWohYi(j-C`Bolk zirmR)<@&rm`UJ|k)ah0))%)TD)l)JbDZLHIvGF&3JBv3Z&7tNz83|&a?N1xX=~jsI z*4pz2e#__Q>f7q*h?KP)W{HXOyBg)YkT$buH!RlZ0(b2#`Oo@3KK+K{el2!8=O z*`@XQAiySKGWn|4V)Jm>-*vqnPQ_Yd6fcW3g0>NIT88RTkCWGz@pEb@t}=-b2_ODg zP1S^wqw@MmCwTd^;;{AQACVhUkU3p>usB^Oi=sC0-PA$%0yE}{%36aEn6-Fj)0mf0 zH09ukbemlvT83I0lhKEg>ulCV>6L$!35qE|>GS+Eqk!os{W`OC+{&upXrv)I-vKEW z4th;HrN@KMBh?CK$%Ls!nN30>`E$o-uz_29-e& zCtw%G$?dwgcXSlxE!ae+Bczf4V(w&|Z#xd*<+-d#y-J?GF=iLlP?=~iFsHpK zJL+Nn9g5c8EOgq)u`UC~M>~=VbkPae#ifRa_gE{|UQ8A7J8G7h9L|_ueNQ))#V?Cv zH$`sMjBa;Q&}Zs<^Oeo72pu*#P5z%=a-(!gfM-6J2f^Huo|KV@RFby@icxJyqlV&3;a8o-X~U6zP<;$-Pz^jB}cV_6L)C zVs#GYS;aT2;rL{$1=qr^;O5!A(Ug2Gxv<`-o7b?%ZJbPlC4rL(Y)NHyB=ZnHa22e1(GIB=y0LTwo)Gdb^zzNl!0@Ma=Hu+j^!3uP zSnMRs`ia?ac%Vc4Y%?MMFYw}O(ICI0IdA<(S#6qQ zP4IH(RMeQ7Pe`wf{6vk%s+0zbfs|q|^BsnpBk;T|5d?O|Wt2ujF0yEX^>Wvf#Rb5l zV&}72u;Mqzdlx!>IfRawG@BxMtb$;XgrIcIH_lmc(?w!t{eFvofXGQb2q7lA8-QpC zEalHuFZTX;2pXXPjdP&N8NkiDHg^^O2?7EsK(Yc1iZGl+FDd&T9qlP!QcHG@ikT_Bbye8e7V@~s zo%z~y8Tvg^7gcvTEJKGo2P+w>&Buz%5EJQne{p zqVXE`{CX*USi%xh0$rsed=9$jMjxpoPT7LqNYx%Y5dX?eFfdYjk6c%yH<^5$tR?{q#5TP+cR0qqisRrWbq2Y9##T0WfVZ?kePfct8&wcWK!P3^dAX% z^f@>#MP4C~ZK0o5clbU|Jr}i2*N?4ts0*gg8TRLtloOsMB4_H69i7mlwmGJ^!gct_ z2}aBmENSNf(s!5`mEZY;5?Kb%g4^lhf__)fxIIBT>;}fUa1cc`!PKU$W~3gG&qz+` zWykaT$Y(koKWai?-_1z7O6hJ$T!6mVE0Sp6i+MU=Lgii|e~`JJX0^k(~* zvFaM?8oyBjJri*~=GDF2KNnot3H4p{+UV#Ap={!WtrN+(e<5qqtE;QK79O4nv@hkK zY)vAE^=wyn@b)C5i!{HZFtFHZaM_x@Fn!ayX)7}UY1SbX>a&uLbbM^sl|)?J(pv2S zn8f44sJNIJvMq8lo7{3<=~8sSIClV|c4hY$$@22z_9lvw3nD*C^hg~SIyx`5xVFY? z=5%fozRm4VTBs~CtO;pJvKp9e@VWaG1NZ2+nksI!#`p|J`CF3b%|F zrW+^cnWOW4_8uXv=}b#)XGfyu9R(Z&t04&F-ofBr zliI)rz)x|&eF;bY7H1zOQv)8GtUe{z&z|npYc{;pqsAksT2T<1l7ghPs127CBs;V> zn)n&3@sSnl1{r$EA2ED5#Vs_bc`W`_;r;Xdal3I4DxsyiW2(Ow$lB~a$a$Q*&AJ0{FvYnQ@BV(#~}2b8RcT=GH^3pFag>fjsz$%75}; z8lX7oIdHp1_N?sYpd)J6Je;npLUjxnBjx#Z=)1nHMYTn;Yfmr&#cxv=GIDaSAL@-R z+j#wBWxBU1^KF7%LNzuw^TS=!2xI!dx;c~H-GbTiGT9)abHnXR#sME^A^V7&kwYoc$o2kP*Dwt z3;!cj4E#r^a0i5nEIi@hySKa0`hRN`n)D0|7Hgrn7*8cee$uJx76O6@{;k9y@-LmC z3?4`TVp8*gEOWA9q;Y5MjNWMB-ik3~w@L!#Upc{VM9&ZV-zAa4iT%iL=P)bv@rtTcqDXtGj)6Ex_hXQC*nvMe@PF4wAv{ z1`PekqpvaYY!BR?EJ+6~h$==>I}s0?_itDm(tq+jh`xnX^{Y9n%U`E)2R0T8wK z2$ONI%A&d?R-T?Iy9G&~uxaG@Pc`TAZ>{=R9YV_cvks@yng4agzGnWJL5K@9O|2JV z;zw_WHZNt?AOiux_T{o_)H*VcPw>U!an?^iCr2MrKXt>62X}N>6RDV&9xL;)i?n#bAAk%kE@_+vyF6%SZ2suufb+ zxs(Fba(Tk)M@Y^ea0Z`hd@POLW1_A+sUhDW>2Fm;Vvb16#HV*R9gbXNS{{w5nMRdH=+iN0W+_Jye< zXr`B~6d(o*{-l4?pZ4NDUdZ&Li!hy0)&n%0$0prr7#8H7@_X#d~*0m#2Z99CFqR-n45qJSbua9g|_6xY2 zt?T>5iJ=4<&ueY=e`!l7Cqj0c>)GdqMOPK(C3~cc>q>VrOU%Ex_oDRJH#m+zCe7$& zGV}ADKOI^vzOf#gdY|R7cA3(~Pzuw(eq)oY<~3gthV!x#dTtR>ESWS_Q64W z<-F9uZ_85?ez5IzEssl#ZMWG9^|0P+D@MOvjurMHJrD2_Iqiwa;<&Es3&sJtYo(3S z#>3~wlLt&OjV)+1ez5w+6jGBMlrR^^`nAqCn^$9HYh2xxNaG+~f`UDSv|4a->gLZs z)=Q9^M1GCg8w5w*oDMlvbE(ti#D`J~&2f747hGJvV340%+q((zYZ(YW+Wbrtgpfu~ zb@P|3uD*1kRlnRE7zfkm9; zi=Jris~m-M+?L$qZ{#gub$L2eCvR7BR>gaDEiF_N1~tRfb^L22+VGf)cJzwEz}7Z2 z=c)EPrYwpz@jl%DT%cl1=ZpWRyzh)^a_iQ0fBRFmfM5Yp>fWM&R13|}lp=~!6p&6t zq)P|s1VunWKtMo+fQW!}rAQ|#Ok<*zPeAd=kYS&~~jyKd3!H3i4s!k3~wNOPDdo=Padg@5>c*oq} ze01~bkQ+&J2>phVoE?E`qOhH$3wEEDh_jrzpOqw>lwZn~bl8gPq9IdgCfunG2)W7?nMlxEGhdXr`VIz|L;jv3|1j5(*VN)|OYkzrxrj zCp4n4D2?eil7p0X>P_I6JTg%r@X5Md^-IYSi47jpyi~&%8Ra?Ai7`ly_7pNw$=;bU z@tTTSBN%${A>n)Uh1Q@33mv6k7NK6PZNDiAC2 zlBSy3a>3hx`ZQzVY2(q3bhRXBa&-OZsdAJ1mAa;JQKOoVKvH9>+|y=Ce**+ob;3Yp zbWNCTkhQ({aGs&rvvTG9`M?Nrk04O%`osPQ(>Qx{ z1%75<<7g+>U?gn&mN6OjozP|$Ko=(@Rp4pd@ZO-nZY6RVGa80Q1z!{Co>RW#?W;l} zZON5T*r*TMOH*JA%Csf}lQrX5gaV${%+BTVM%SV^XSP8jW9umS^YJUZH(ZpO!Vg33 zbnw!$95sCTzCk59mP{y|t0Mri|?Lfl}n|ftY?4p%6D>FXXOF%FfJ8hPYZ~aUcZpWA#<~52;K2iSDFD z2V^Dx^@!rTwnm8&saQ6yv)>4f_gT|_9p>8+EMiNk!p9O3e(?xPq_ogwc4<3b? zNIMa-JP8A1Hi7-r^+_-L&z_Ub4AjX<%w2=j^7a5@d5g)vg2RPQc5bA#7~4=(;vRCj zy0I2MOz;ZH!0EkalW3nQLsjr4d@H-k$(CtrZ{+QY=kk?F37J=kW0akp6LrZhUyl2Q zKKmI<^_6M3!eerB@^72TT_4~Dw`!sl423A>XtQ!5L|G`qtBD#Dzn0RSt2J^oe=?mn9aa6VDl3nA0Ao=3cK%?Vg4T`_6}P z@g>OOB*H5w+J^lmvX2;$sv76J<)ird_G_liN5vG|;fe;YqPT)`d%a}?dws8s%`yOo z9m>X@pBkU^G%$p;S*&aT%E9P7suLu*ED`x>GrZP<-% zjKtfjW)@WdQt;TVAnA zBcIA1iZIM9ys;z?5~Zd_khFV?2s{_LG!X7oOOSG#>qytUe*JoVeLb&w!h=`15_OV^ zZQ{k8tz#Elv$3ndM5Q#Kw`QN~Z-oiFPu2kZ01(iYC-+{u zz=_w1uvvPG^f9Aa_v9FNXj%|bKj4B}a-9Gq;>?&zs;UU}eB-DlKk42b#&oSteQ_u-@qglM*SZ2Zr6UY0(N7GdVrO zF%gnBGZ8$D_9SoheBy9Skr9Zye~bJ5Y(l2I#d$2oilmX$WMr*Z@=BipO*Iou@gzt; zNX}T8eR3w*le%mYk}>!}dqedXr9nBjjMMA+G^EpC^hT!b8^EiV;Eo*4*R ztgX{$5J25L^B7R?WYntlRB4#66~j? zXJc-Yb(5U+OrE&L$yKa*(`?i$=R}`nZiu8iZ-+*1dI=<}aj(AY=0wC=sL!=+=8Bwj z<;>|jTq}RNNBfwl1;)y)4PUj&j)i&QA7GH4Z0aTquQ>@PYYAro?>kn(KS6?lI5was?&hRx+l(9g@m>Y zz4A%jtTcHU%d56U&Rv{1k!@@vH0(|$8r2dbFA(|^@Of?7zKOEDa@A$Tq9ZLv&u1<0 z+~KH&e;=7D!H{JNS8{v0%eLQ5-0ctjBK+slX462d{6qPt_KCUunEu6-7+YC#YWMfv zpmE8KuU-h9_sZ&%-LoNX`bBmW^M18d@g+v1cFxF-8M}tSlWK!o6t%c+eN1PLbIWg< z;^?f+hOacl$@ror#zbW0#=Pso;aSQ0(aV$f@bbsg3|GkTsNL#TPA@)JGn34f zHkY9}7Fm|U%Oz^khiP385;HYF?uOay0MS%ZTVA1y7z38)md)xQhq_o; z7*c9jb?t(%`Tn)0xi#y=&n+k8wxkKQD+9a>-g^e~W770)(h@JSSgnt<%ycl)#0X<+ ze=NpTvbd3EcvHgN{*GSB;^OTM6a}9)d7a$0K3?FuDpx?YQZX!HN2CpeE^jVgJQiza zVEVASHtW@0%60t1uVswn5b@+YHzFL#p($!|-ga^m-bSCh`Gkb}%cSbplrb=pkVNJX z(}qTYglf$_p4KnzIW%O(aP*_diNbOeqFcVNZ^%98#+T2&8p(cScex!eq;0oMT}G}( zT^O%TX|SYqLDse;!#Wvs(SP1c@V6OCzk;_- z&5GRzAj|uw_SuvsM^i*m{_-WgUP-s~S>9QniHZ88rQW8y`K!Z+jP$a!X2-nE2VXfJ zd&psIwMFcf=^no}EAUbxvPkJF*Z1@rg!m|DsV`ouG^q0&6H>&9&~n~|`@h7T-eDmyt{y`Oq;xjKx-~gnAP=)7K3pFf;F07{F-%`jddytnxJ0>$TAzzj$4pMi zKJa?Oe+#Rw|HFooD1srZt%S#LPoSGv!rzsb`x1y~IjUl1Y)mk%(g4;}4mH_Y8LhN7 z&|IT*Mt$`4UNZ5ey#Y!&%E=69uHo6uZ}Yh3VPC?$2U{jE%}YzPE3E>1<{+)W>PW}} zgYq_S5e!bLxNV-uu%dOGSf|Vqt8Y0{zHZE{d-^j3E%y? zVd4w!U#c**KjiUn=>{By2#sX)`z%i@)*lVH@iLcJhi!LxSm~;0(augzd3kxkAtB7P zHOD;v*oTw4m8Upzbo>U>r$El#^x*RE7vJJaK7KqWAP`b~@-p|ChFHFPS#G=f+ad{@ zp!4(d;lR{H#g=^3@4f=}0^Aw4spFG|Rz-q@}hFtIZj5u`RugK%=Tk&5JS{fdZ&9Yjbe&&`no~Lzh1PhfbgQD zh;H;9f*{q!x4m_%=sd<}rWJnVR9$YXsy%n}myG|pE#vkmIdLs5RZM+j|lm%7W`YEl9Y5aZ&}=axp`&LW1%aHZ+9lWFFbrlu*f~R zUFJ4}o^NyWRQV(gstSSrZR-)Gn=kVMLG!jhmlZC&#a)7uZgKJ2^=0~fD+>QvUBR5P zvILuJu={XNpDvyWe#K{YNapa)zxxI5Y@CRSii(cbHZ;7sO#k-Ckux`#gl|O z+WFBw(Q{yO(HSdP;89+`etmKu?%LDHGqfx=@w@i&^1z9I$4(-9vVbo5|54S|{~OTd z(FayFR@dLt!!GSU|4694yRoARMNn zrBz*BO@H!2bxn=gwDLnW32;-rCFXv8C3C_vEXgN2%ia>PQ#9(xVo2p=`YRfk8nbUe7FyHac}n zUD74RtlCaD=Tz%CYN%89YI*w-n4$G(7%LPnV{Yqs>pDljO(1r0_PCI~XeTZgi3tu4 z2L4U7Vz@O~nU0pW)QyH0#J$kgG;-FF4Lyq(Jo)q7-v$GrRCJlMnk9-RN>SLKiip?M6 zRt_^Pb(vi0MzUbu#KkEqDPk=`jOZ?Uk{z9D=PpU>G-390)1 z?}t}<{rvVhR>P&!dbaBL`1tr3A%kG}S=|DQQ0>?Me`&X;A45WSi|TVo_#iXD_%q4UB3z z3j(t~mAUwtGw+K3foJ~r?lySQMb-FqT4-u&f?=dEBf4G0PFkw;*?439U_o$WJQi8~ zRituFez1SECPb{Cx|B%mxJ18jc=Un0d-23qP|gs4EEWqrSr;#A`gAol-DD?^h07IO zwR!L$3r3mAZU1_$=m-tcmpmREOzY7fdeH)FDgMHZu9Y5bQ_2clU$#NfaSZ1rr=N3! zWyJEOuwtRD@VBd(a25E@N1qis;(TRoT6HQO>TXA5Zv!6Um4$wL%-PHUENHs5zCQy8 zLW`(sM{QN+nqt-_jndUV<8X=y!w;z|^P7)C3n4uF$kqLJH}x#+l&94>pbDEZyH4hsQ( z{-6G?^k_zQ$v=I4C@bACVSYQst5>^x)A#K0Z7INGH_LmUOvk>`e9ndFnvfKK0d`h3 zSd5R?hlPcKj7Pgc>;*R6YV5D2+;Xr(zH1{ij_=)wLrxo2L5!G%TDH;e6U}jBqodWK zps_jng&F1L7t^}l5tG(5U9FHLT*>?Q ziVU_$ui3)w-&Q|6W`T|On9eS$j)3uCD69R8fy|iA#SqK%dyyu*f`v(47zfg4MY}PEit-|{ z8ftsY{kEwow`?FGPhaH3_7A3imgwCO(LJ#LfVMj?0dqz3NtBiavqAH@1D)98P? zy#EuYz~kF}8O*mMLTL7nM^-7lu=ytQ_VD9_CmuanO2~3_qr3K4Snc4JZ+?(R_mZql zg-!1Kq@2wV`Z!$Y?2(iQnhK5rRwFen&24Vr5-)FBLBaBX0Pk$iCsW+pD<@B$T$$>m zi+zJ|wVtB;W>Nxz?uN*5J&Fe$q0dsYMDjWdq%iJ39@R(jx=nSQ9WVy%;q>?!F;*AO zyKzHBr8bn!ty!%5NpBd3RA3wz#B8MiY=4n`_`9ijxwmf^*|!DsXXiL4;@GpD$c}8& z=DGRm@SVy2BH|gNoi#0fd=PCD$mhZdz(2(RlB{yoIPunmj##^$nE#`J$0g_FI~;k) zi&)`uL(s7JoM0=|5uw!%S*pGLd_RFWT#5NpdA!$L3BFC}{M|2p9~ITquqg&R$w2Yw z!QC?E)6iXT?$@(d*ZlwW51Hbg%LK^sz~u)m5CJPe(g)(ArrGbro*zywHGx>ViU6(KVZ%bew(ou}tg&{Fc-)wfsSQo81_J#=& zq>k?^0<>%R76Y!qajf>4;yd+3+1Bu_ZG_3bMQ%YcO-8hoRcX-%sEXnE*VIx6YNH4yUNSL3#w#KH`TOLmZ{JYFjw6)Q+dD(Pbu;)Q zT&JEWzld*cX(_7M$#5@=bwUA(B4KB+IhDb`VPCP*rFbeLDk^_ObGj?r1{@RL1Rft0 zxUIM*(&kOC78e&C*1}Pn+zk=QGsS@RO{BrZBO@anbhWfx8ik6yjS2CPJ=I3>sFoIl z?@0aa#D|kf&M?_rHhK7g9a@9YDPbsV>ja@0bwq(3xrj+;9fd|kaxQZkMV zEpfIq95s+d1=+nLW-nU0_nC*Y} zAL0arT;RIz`lcqs&kyvh&r3*1Fj1G&QF`i2qGFW}?nM=bT?$cfZVixb$=N*f zPPTjsNFhxPtq;x%6tijskBTzA|mSBPL)II z;roQnWaV&;cu4+Vw*+F7|0UeDvVB;^b$wtS;Ndd`lEBPu~+T%ipMN5K_A)F?m z#Z(L4MV<1S!uE^&a^J8XLljYKZ9|aRp1D8sclH=Sh*u>335xHtzqmVkA2pc4@N`lPGFV89j71y=)2uu zX+RY|5w#U5y~7dvH5xZV*}c2cXJt{fb5c&gh2glM?h94~oc!QQ9Foa+pO&WVA9#o@ z$G8G91uP3nG&&;UyiHdY5GIP4GbcoC`$YRjOO!&6lgZ>H@?=_KSSqWSHB*H;oH;l) z|4)&xQQLFd_u;n*EV>NR-f-FV52tG)xRoK3bNTV*5$NUYFh-7k%QR_e=&{1@_Ustf zsvPUpM7CYC4#ZmUJL3-?<8c9CEF)84))=$xGhY6w{H=I9Ao8%O%aVV-ZlFly<>v!1 zJ+aA$PORDHmVhFnlS~NJt<)HeiAD z0Pw1vdB=yWl<2!Y>5#4iiB#imW6Rsr;x>8wQfe)vE;mjeWt3Ugh~D0m1^bT@<*1Fr z*CGEd?jZV-%JQcGKnz!LY>kVc4vsy3{P-NFtoK?hl3`nMemFU#1Yq&1p(t`AQrvF9 z9sCz^W?961ZGHrQXuE=;;Pdl)gh_mCEK4mwpN+-Fo$(toR31%oUR=QgC}~oe?#^Yb zDVr;`87OvylnXCIfy_!zPcMo5h=xz# zq0gDfU%B%2!>wdtc0{gT{sgZa`T7Z%XJ@NXK)$>}aXl!1D1@8R4qz8r)=zCW@<5{Y zYDd+eViv3d2>yhO=Q3zug3oF%Sk7s6^4eIq!kLb`=O>riZioQChls)NfLsUTSTDk6 zYirwN?~*#ZNTxXzaLxS%XbXC#vK?!@GXQM^Se7fgsPZIE)G7}U^SKpZ{CH)zIktLw zQdVz4K>?uP)o)2l0QtPT_Cv0qqN1|CJQ<~*rJ05Wu1wQjMC&%2Jc>9}p(y~Vw$EBz zz!nf7(>Z0ru2af#>k$Jx7o``wK=|{hiChuFthR3rSL71>O*kUFf%tN$VfeB6SFQTZ3BWCz&$HJe+9!nG89$X>+WgkLODM?gD)SAKxq}!nDNY1xd+So%u zOB2l@VYpEx&Y~SOMHHsGkl}3um1rWmV|q`gxUC^SWw>|@{jTF zMs9=5{J>wTR$|H>M!soSL0EUnHn1y6DJT$Sm!&MXk7R=SW;WFQv90#=HUBYOBAam@ zkhIkI@)e;a9q;8`^t2_X#2N>)HZ(RSvjl?^jU%UntG|k-VdQ*n4hP0WmRc6vsD&)w z9z%I}$_yeXFgfhO!&|FGQAMP0bRws7#myRCYLI(dd}Fd^`U(ZKAT_CS2N7+P4MD@3 z6B0nuVKJ0h`$X@>>#m$q+XMT;q8YWF;23VK0&z{ZtaH&t)`g(q^swinNm67~lrzs6 z7rTxRtpLE@1%hiny+Ed=r3EC%d|-n_R5ub;NfF_9f$epZ`0O@Nq9xxl(BJ?ST>-s= zMG+qc3J{2a0;_h=A3cmOg@6FyMvEd&NqcO++)v~!PXIO>Gh~l#LKzjy#o$Wx^37Wr znCrbiL$po00F=_9#D?Z(4j>u9V$~9)dq3OupWA2<$UU8_XKc*L3@;bvxRp%TDf98awc<1lCr+DRxJK3U%+3~aF# z3HiEeM^ipM!M4bd1{i(k{m&6V%iRwrZ4r{g1FLe3%C6?hfjTRdStwfBi}u4*(Nb=K zRZ+a^+t^f}0M-dZd-w8E{L$uBNY=FuFmkeImw^HU^%m5isV?I>WbZbDyR@$N4FXp* zl&7?`AXVdGXE=G`{dx=6wm^Qo>v)bUah~nh5gFD32pQA-{X1bkUCgG-@Bx7x0jPF9 z+ulduxz{qm@!joZn@3lm7?Z3TZ%|;lo!nq)^KV@PI(~LK7bEL=Yds?~Cj*d}fPf7E z8A<2_HYvtKF~+Vp?~I`wLdKA{uXqe-HU_kXu&j%5k)09rY`${}!2^uuz9C`rxJB&hhyc@h< zB_s?%11sS7xxN)*8NZN_4dJAZ@TTzKQYifCk{h z^7HcaKR-Ar+zDOG4yGfc>BDpHR$YJwvjx--?u034wTf%&oGarFJK@&@RKjlcU2N~5 zs{aGo)C_zJ9*`Qq9t+`XyH(K3od9SIbai#_+*w_y<4XMCvbnbK?p<<_oFKw`?RyXx zr?9lUC26i=uNasi4ruIt*Ji8onHnG*W%SG4h+9Twt20f*g|^e!6}BORO7E0Cgpr|| zC`)lqfy{Yy)RamJTN>e(a+~QZHLIH-71<4ZB%|HB%1dT!_okp7B98}R!L&{`_$Xc> zNOqvqwl0JyvR$96Y-$!=K{mNzNL#Zy!An5D)~X4Slp|seHUC z(_b{6Ym~oNO~2fETLB(CR^hp_Zkz%t4Rto^2qZW_-wmNqnZHJh-bh`7qe|v5)Gf%s zq3Ilc+7-83!q)26^Fpw&aMAe#H7NqV6Dl(M$zI}iJrC4(GlPur0j{I;)Z@oF_4Dr6 zC&+AkF2@Wq9^9b>HH`3q*dPX7lWgJaf?I#NBEe=!Z@=r&p}PJyRM|Bm?MAp@xK8nIQo|W diff --git a/docs/assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/PRpic4.png b/docs/assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/remove-payment.png similarity index 100% rename from docs/assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/PRpic4.png rename to docs/assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/remove-payment.png diff --git a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md index 7a646addaf..5bfa1c1f6b 100644 --- a/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md +++ b/docs/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md @@ -371,7 +371,7 @@ To remove a payment, select the corresponding document and click the **Remove Pa !!! info If the payment is posted, the accounting entry is deleted too. -![Remove Payment confirmation dialog](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/PRpic4.png) +![Remove Payment](../../../../../assets/user-guide/etendo-classic/basic-features/procurement-management/transactions/remove-payment.png) ### Unvoid From e23c90dd9ccd814f560afae0036e5f34da6e48ef Mon Sep 17 00:00:00 2001 From: etendobot <108091082+etendobot@users.noreply.github.com> Date: Mon, 13 Apr 2026 18:58:35 -0300 Subject: [PATCH 13/13] Feature ETP-3185: Update ES translation --- .../procurement-management/transactions/purchase-invoice.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md index 99e6717187..b8777ce463 100644 --- a/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md +++ b/docs/es/user-guide/etendo-classic/basic-features/procurement-management/transactions/purchase-invoice.md @@ -422,4 +422,6 @@ Cuando los pedidos o las facturas implican a dos o más organizaciones que perte Este trabajo es una obra derivada de [Procurement Management](http://wiki.openbravo.com/wiki/Procurement_Management){target="_blank"} de [Openbravo Wiki](http://wiki.openbravo.com/wiki/Welcome_to_Openbravo){target="_blank"}, utilizada bajo [CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"}. Esta obra está licenciada bajo [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5/){target="_blank"} por [Etendo](https://etendo.software){target="_blank"}. --- -Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. \ No newline at end of file +Esta obra está licenciada bajo :material-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-sa: [ CC BY-SA 2.5 ES](https://creativecommons.org/licenses/by-sa/2.5/es/){target="_blank"} por [Futit Services S.L.](https://etendo.software){target="_blank"}. + +--- \ No newline at end of file