Skip to content

KUMAVISION trade#

See also the following ChangeLogs#

26.0.2993.0 - 2025-04-17#

Hotfix

  • Item Planning Suggestion: Incorrect Calculation of "Calc. Consumption per Day" (#14159, TRD-724)
    There is an issue with the calculation of the "Calc. Consumption per Day" field when an item is defined as an Item Replacement. In such cases, the system incorrectly derives the reference date from the Item Replacements start date instead of the expected user-defined date. If the start date of the Item Replacement is empty, the calculated consumption is set to 0, which can be misleading. Additionally, the displayed consumption quantity does not always match the Item Ledger Entries, leading to inconsistencies when reviewing the data. To ensure accurate calculations, the system should always derive the reference date from the user-defined value, regardless of any Item Replacement start date.

Change

  • Alloy Surcharge: Provide events for overwriting Alloy Surcharge Quantity (#14090, TRD-759)
    Added events: KVSTRDOnBeforeGetQuantityForAlloySurchargePurchaseLine(var ItemPurchaseLine: Record "Purchase Line"; var QuantityToReturn: Decimal) KVSTRDOnBeforeGetQuantityForAlloySurchargeSalesLine(var ItemSalesLine: Record "Sales Line"; var QuantityToReturn: Decimal) KVSTRDOnBeforeInsertItemChargeAssignmentPurchInInsertItemChargeAssignmentPurch(var ItemChargeAssignmentPurch: Record "Item Charge Assignment (Purch)"; var ItemPurchaseLine: Record "Purchase Line"; var AlloySurchargePurchaseLine: Record "Purchase Line") KVSTRDOnBeforeInsertItemChargeAssignmentSalesInInsertItemChargeAssignmentSales(var ItemChargeAssignmentSales: Record "Item Charge Assignment (Sales)"; var ItemSalesLine: Record "Sales Line"; var AlloySurchargeSalesLine: Record "Sales Line")
  • VAT Bus. Posting Group from Ship-to Adress depending on Bill-to/Sell-to VAT Calc. in General Ledger (#14113, TRD-760)
    The logic for determining the VAT Business Posting Group and General Business Posting Group from the Ship-to Address has been adjusted to respect the setup defined in the General Ledger settings. Previously, the determination of the posting groups was incorrectly performed based on the Ship-to Address, regardless of the field "Bill-to/Sell-to VAT Calc." in the General Ledger Setup. With this fix, if the configuration is set to "Sell-to/Buy-from No.", VAT & Gen. Business Posting Group from the Ship-to Address will be considered - if the field is not set to "Sell-to/Buy-from No." the VAT & Gen. Business Posting Group will not be considered from the Ship-to Address.
  • New Container Card with additional Informations about Volume and Maximum Weight (#14139, TRD-762)
    Introduced a new Container Card allowing users to capture additional information such as volume and maximum weight. These fields are currently for informational purposes only and are not included in any calculations.
  • "Not Billable" changes in Process (#14168, TRD-732)
    When a Sales Order is released, the minimum order value is added. If the corresponding amount is calculated as a percentage – this can result in a line amount of 0, for example, if the total order value is 0. The problem in this scenario: The newly added line is set to "Not Billable" = 'No'; this means that if the system is configured to check for "Not Billable" positions during order release (field: "Check Not Billable at Release" in "Sales & Receivables Setup"), an error occurs and the Sales Order cannot be released. As a solution, a new field was added to the "Sales & Receivables Setup": "Minimum Order Value at Zero Amount" If this value is set to 'Yes': When the total Sales Order amount is 0, a new line is still added – provided that a fixed amount is to be inserted. However, if the amount is to be determined as a percentage, then no new line is added. If this value is set to 'No': When the total Sales Order amount is 0 and all lines have "Not Billable" not equal to 'No', then no new line is added – regardless of whether a fixed or percentage-based amount is defined for the minimum order value. Additionally, the line quantity is changed by the report "Reduce Sales Quantity on Single Shipment". This change triggers a validation by the KUMAVISION base. If the quantity is changed, "Not Billable" is automatically set to 'No'. This behavior has been modified by KUMAVISION base and got resolved.

26.0.2956.0 - 2025-04-09#

Hotfix

  • Item Planning Suggestion: "Use Historical Item Ledger Entries" is not properly considered (#14028, TRD-749)
    The field 'Use Historical Item Ledger Entries' on the Request Page for the action 'Calculate Lines' in the 'Item Planning Suggestion' is not respected when it is automatically set to 'Yes' by the saved report settings. With the implementation of this ticket, the field is now correctly taken into account in this scenario.

Change

  • Bonus Agreements (#8622, TRD-182)
  • Expand Rental Setup (#12867, TRD-472)
  • Changes in Rental Items (#12952, TRD-476)
  • Event Request: Add "KVSTRDOnAfterGetRecordWarehouseShipmentHeader" in report KVSTRDCleanUpWhseShipments (#13902, TRD-737)
  • Alloy Surcharge with Over-Receipt (#13933, TRD-671)
  • Number Series for Rental Documents (#13936, TRD-735)
  • Rental Item BOM (#13937, TRD-693)
  • Block Rental-Item (#13938, TRD-595)
  • FollowUp-Service only in premium licence processable (#13939, TRD-467)
  • Create capacity on rental item / rental item card (#13940, TRD-475)
  • Alloy Surcharge: Changes to Invoices, Credit Memos and Return Orders (Purchase & Sales) (#14000, TRD-746)
    With the implementation of this ticket, the field 'Attached to Line No. (Alloy Surcharge)' is now correctly set when retrieving invoiceable shipment (invoice) or Return Receipt/Shipment lines (credit memo). Additionally, when retrieving Shipment Lines for a Return Order, a quantity reconciliation now also takes place between the item line and the corresponding alloy surcharge line. Both aspects have been implemented for both sales and purchasing.
  • Event Request: Add events to skip creating alloy surcharge lines in Codeunit "KVSTRDAlloySurchargeMgt" (#14069, TRD-756)
  • Event Request: KVSTRDOnBeforeOnPreDataItemCustomer in report "KVSTRDPeriodicInvoicing" (#14070, TRD-757)
    Added event: KVSTRDOnBeforeOnPreDataItemCustomer(var PostingDate: Date; var ReplacePostingDate: Boolean; var ReplaceDocumentDate: Boolean; var SkipDateChecks: Boolean)