Skip to content

KUMAVISION trade#

See also the following ChangeLogs#

27.1.3528.0 - 2025-11-14#

Change

  • Price and Discount Origin in Sales and Purchase Line (#15757, TRD-908)
    In order to provide more transparency regarding the origin of prices and discounts, the solution has been extended to include references to the price lists used in both sales and purchase lines. For each line, additional information is now stored to indicate from which price list and price list line the sales or purchase price, as well as the discount, has been derived. This enhancement ensures that users can clearly trace whether a value originates from a price list and, if so, from which one. If no price list is involved in the calculation, the new fields remain empty and are cleared by code to avoid misleading information. The implementation covers all relevant tables and pages in sales and purchasing processes, including order, blanket order, invoice, credit memo and archive lines. It is important to note that this functionality is only supported for price calculation methods provided by Microsoft and KUMAVISION Base; when using third-party solutions, compatibility must be ensured with the respective provider.
  • Deprecation and Replacement of "Production Blocked" Boolean Field with New Enum Field (According to Microsoft Standard) (#15777, TRD-939)
    With the release of this ticket, the Boolean fields for "Production Blocked" has been deprecated and replaced by the corresponding standard Enum field. All existing references to the deprecated field have been updated accordingly, affecting areas such as catalog imports, catalog items and the item lifecycle. A data upgrade has also been provided to ensure compatibility and seamless migration.
  • Line split check (#15889, TRD-951)
    A new Boolean field "Line Splitted" is was inserted in the sales and purchasing line to identify lines that has been split or are created by "Split line". When the function is executed, the value is set to true. The field is not visible by default but it can be displayed by the user via personalization. The price origin and line discount origin are only temporarily set to "Manual" to prevent a new price calculation. At the end of the function, the original value is set in both lines.
  • New Events and internal removements for codeunit "KVSTRD Item Replacement Mgt." and codeunit "KVSTRD (#15931, TRD-957)
    In code of the “ Item Replacement” area, several events have been added and the “internal” flag has been removed from some functions and/or objects to make them usable from outside the KUMAVISION trade solution.
  • "Show Shipment Dates in Calendar Weeks" will not be correctly transferred from the Sales Header to new Sales Lines created by business logic (#16035, TRD-950)
    With this release, the field "Show Shipment Dates in Calendar Weeks" will now be correctly inherited from the Sales Header to all newly created Sales Lines, even when these lines are generated automatically through business logic rather than direct user input. This ensures consistent data transfer for functionalities such as freight cost calculation, minimum order value adjustments or similar automated processes. Previously, the field remained empty in such scenarios, potentially leading to inconsistent behavior unless each project implemented custom handling. The enhancement improves reliability and reduces the need for individual adjustments in these cases.
  • Manual Insert Sales Minimum Order Value for Prepayment (#16036, TRD-958)
    In the context of sales orders with activated minimum order value logic, a new action named "Add Minimum Order Value Line" has been implemented. This adjustment ensures that users can manually add a minimum order value line before releasing the sales order, enabling the correct calculation and inclusion of the minimum order amount in the prepayment invoice. The functionality is only available when the minimum order value feature is activated in the Sales & Receivables setup.
  • Event Request: Add Event After Filtering Record “Rental Item” in LookupRentalItemFromSalesLine (#16065, TRD-964)
    An event has been added to the LookupRentalItemFromSalesLine function in codeunit KVSTRDRentalRedesignManagement (5157200) to allow filtering of the "Rental Item" record before the lookup is opened. This enhancement enables external subscribers to apply custom filters to the data set shown in the lookup, ensuring more flexible and context-specific behavior based on the calling logic.
  • Wrong reservation quantity in blanket sales order (#16108, TRD-965)
    If an item has the setting “Reserve” = “Always” and is entered in a blanket sales order, the reservation entry of the blanket order line contains an incorrect quantity after an order is created for a partial quantity. This requires that "Can Reserve on Blanket Sales Orders" in the "Sales & Receivables Setup" is set to True.

27.0.3457.0 - 2025-10-13#

Hotfix

  • "Qty. to Handle"-Error when creating a Pick (#15750, TRD-930)
    This modification fixes an error that occurred when creating a pick if the "Synchronize Qty. to Handle in Whse. Activities" switch was enabled in the "Inventory Setup" and the user selected the "Do not fill quantity to handle" option on the request page.

Change

  • Add "Consumption Counter" Fields in Rental Item Card (#15531, TRD-911)
    The "Consumption Counter" fields are now shown in the rental item card. Which of the fields are displayed depends on the setting of the invoicing type field.
  • Removed logic due to removed KBA feature (KBA-1973) (#15567, TRD-918)
    Due to the removal of certain KBA fields (see KBA-1973), related application logic has been cleaned up accordingly. This includes the removal of filters and conditions referencing the now-removed field KVSKBAQtyCancelled in both transfer and rental shipment processes. The affected logic was used to distinguish between canceled and posted shipment lines. With the deprecation of the underlying KBA feature, all associated application code has been adjusted or removed to align with the updated data structure.
  • Invoice Discount and Payment Term Code in Price Information (#15721, TRD-928)
    This ticket introduces enhancements to the Customer Price Information page by adding two new fields: the "Invoice Discounts Exist" and the "Payment Terms Code" from the corresponding customer. The "Invoice Discounts Exist" field is displayed as a read-only lookup based on the customers data. Additionally, the customer's payment terms are now shown to provide further context. These fields are purely informational and do not influence any pricing or transactional logic.
  • Exclusion of Individual Customers from Minimum Profit Check (#15731, TRD-907)
    This change introduces the possibility to exclude specific customers from the Minimum Profit check. For these customers, the check will not be performed either at document level or at line level. To support this, a new flag is added to the customer card that indicates "Minimum Profit Check Disabled". During sales document release, the system evaluates this flag and skips the check accordingly. In addition, it becomes configurable whether the Minimum Profit Check and the associated order release archive should be used at all. If deactivated, no checks are executed and no release archive is generated, which helps avoid unnecessary processing and improves system performance, especially in wholesale scenarios with a high volume of daily sales orders.