Skip to content

KUMAVISION trade#

See also the following ChangeLogs#

26.1.3060.0 - 2025-05-14#

Hotfix

  • Comments are not displayed in Rental Reports (#14267, TRD-782)
    When using Sales Lines of Type = 'Comment' in a Rental Document, those lines are not displayed in the printed report. This ticket resolves this issue.
  • Demand Forecast: Refine Filtering Logic from Specific to General Criteria during Demand Planning Calculation (#14441, TRD-776)
    Adjusted the filtering logic for Demand Forecast Schedule Lines within the "Calculate Demand Forecast" action. If Sales Type and Sales Code are used as filtering criteria, the system now applies a stepwise fallback: it first tries to match both Sales Type and Sales Code, then only the Sales Type (with an empty Sales Code), and finally both fields with empty values. This improves resilience when no specific match is found in the setup. Additionally, an issue was fixed that previously prevented the calculation of demand for the upcoming year, ensuring that future demand planning is now possible without restrictions.

Change

  • Page "Variant Quick Entry" shows blocked variants (Purchase, Sales, Transfer) (#12489, TRD-636)
    The "Variant Quick Entry" page currently displays variants that are marked as blocked (e.g. for Purchase, Sales, or Transfer), leading to errors when attempting to process these variants. To resolve this, the "Variant Quick Entry" page will be updated to filter out variants where the "Blocked" field is set to 'Yes', ensuring that only unblocked variants are shown and processed correctly.
  • Event in InsertFreightCostLine in FreightCostMgt.Codeunit.al (#14189, TRD-772)
  • Drop Shipments & Special Orders with Alloy Surcharge (#14206, TRD-679)
    When creating a purchase order for a drop shipment, the alloy surcharge for the item was not automatically included. This issue occurred when using the drop shipment function from a sales order, even if the alloy surcharge was correctly configured for purchasing. In contrast, the surcharge was correctly resolved when creating the order via the requisition worksheet. The same issue also affected special orders. This ticket implements a solution to ensure the alloy surcharge is now properly added during drop shipment creation, regardless of the method used.
  • Remove check on Posted Sales Invoices in Rental Item Ledger Entry when a Sales Line is getting deleted (#14265, TRD-780)
    When the Rental Order is fully invoiced it gets deleted by the Microsoft Standard. In this process there's a check on the Sales Lines if they have attached Rental Item Ledger Entries with Posted Sales Invoice numbers - if this is the case, an error will be thrown. This check got removed with this ticket.
  • Exchange Price for Alloy Surcharge at time of recording (#14271, TRD-677)
    Alloy surcharge handling was extended to automatically capture valuation details such as calculation timestamp, factor, and price when the "Activate in Sales" option is enabled. These enhancements were implemented in sales quotes (including archive), sales orders (including archive), posted sales shipments, posted sales invoices, and posted sales credit memos.
  • Alloy Surcharge: Copy Sales & Purchase Document Lines (#14278, TRD-745)
    With the implementation of this ticket, alloy surcharges are now correctly handled when using the "Copy Document" feature, both with and without recalculating lines.
  • More Information on Planning Data in Requisition Worksheet (#14317, TRD-754)
    The Item Planning FactBox has been made visible in the Requisition Worksheet, similar to how it is available in the Planning Worksheet. Additionally, for the Requisition Worksheet only, the Untracked Quantity is now calculated and displayed.
  • Purchase Quote - Optional without Purchase Price (#14328, TRD-751)
    A switch can be set in the "Purchases & Payables Setup" to disable price finding in purchase quotes. The setting is inherited in the purchase document and can be overridden there if necessary. In the "Requisition Worksheet", the quotes are already created without a price using the “Create Purchase Quotes” function.
  • Rental Item Availability: Improve error message when "Finishing Time" in Service Order is empty (#14356, TRD-795)
    Implemented a validation to check whether the "Finishing Time" field on the Service Order is empty before calculating rental availability. If the field is missing, a meaningful error message is shown instead of triggering a system error. This improves user guidance and prevents system crashes during rental availability checks or when adding a new rental line.
  • Rental Item Availability: Use field "Service Time (Hours)" to determine the hours of an Rental Item (#14364, TRD-796)
    Replaced the service duration calculation (for the Rental Item Availability) in the RentalManagement codeunit with the standard field "Service Duration (hrs.)" in the Service Header table. This change ensures a more accurate and reliable calculation, especially for service durations spanning multiple days, as the standard field considers additional factors beyond a simple time difference between start and end time. This was identified in TRD-795.
  • Implement flatrate bonus with type revenue (#14374, TRD-797)
  • Events in KVSTRDDemandPlanningMgt and KVSTRDItemChangingSuggestMgt (#14400, TRD-794)
    Event publisher "KVSTRDOnBeforeCalculateWeightedUsagePerDay" added in codeunit "KVSTRDItemChangingSuggestMgt". Removed internal accessibility from codeunit. Event publishers "KVSTRDOnAfterGetCalculatedForecastQuantity" and "KVSTRDOnAfterGetFiltersFromDemandPlanningParameter" added in codeunit "KVSTRDDemandPlanningMgt".
  • Check Sales Order on Status = 'Open' when changing Freight Cost Code (#14402, TRD-800)
    A validation was added to prevent changes to the Freight Cost Code in the Sales Header once the Sales Header is no longer in status "Open".
  • Don't show Rental Documents in standard Sales & Transfer Document list pages (#14417, TRD-801)
    Sales and Transfer documents now exclude Rental Documents in their list pages, similar to the filtering already implemented for rental documents. This adjustment requires the new rental functionality (KUMAVISION Feature Management) to be activated.

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)