Skip to content

KUMAVISION trade#

See also the following ChangeLogs#

26.4.3333.0 - 2025-08-15#

Hotfix

  • Duplicate Assembly Orders Created After Changing Sales Order Type Due to Incorrect Location Handling (#15329, TRD-891)
    When changing the Sales Order Type, the system no longer retains the Location originally determined via the item-user-location mapping. Instead, the Location from the Sales Order Header is used, resulting in the creation of a second assembly order. This leads to duplicate assembly orders being linked to the same sales order. While one of them is correctly processed upon posting, the other remains open and cannot be deleted or processed further, as its originating order no longer exists. This change ensures that the Location from the item-user-location mapping is preserved and that only a single assembly order is created for the sales order.

Change

  • Error When Entering Rental End Date: No Rental Items Available Despite Unlimited Capacity (#14856, TRD-848)
    Fixed an issue where an error was shown when entering a rental end date in a rental line, incorrectly indicating that no rental items were available - even though items with unlimited capacity existed. The validation logic has been adjusted to correctly take unlimited capacity into account.
  • Add Sales Line Reference to Rental Item and fix "Rental Sales Document" field reset (#14949, TRD-857)
    Added the field "Rental Sales Document Line No." to the Rental Item table to complete the set of related sales document information. Also adjusted the rental item card to display relevant line info when applicable. Additionally fixed an issue where rental sales fields were not cleared correctly after cancellation of a rental delivery or return.
  • Implement event in "CalculateRentalQuantityByUnitOfMeasure" in codeunit KVSTRDRentalManagement (#15339, TRD-895)
    Implemented event: KVSTRDOnElseUnitOfMeasureCodeInCalculateRentalQuantityByUnitOfMeasure(RentalItemNo: Code[20]; ItemCategoryCode: Code[20]; NoOfRentalItems: Integer; UnitOfMeasureCode: Code[10]; StartingDate: Date; StartingTime: Time; EndingDate: Date; EndingTime: Time; IgnoreCalendar: Boolean; var RentalQuantityToReturn: Decimal)

26.4.3304.0 - 2025-08-07#

Hotfix

  • Incorrect Bonus Calculation Due to Wrong Quantity Tier Selection for Sales Bonus Agreements (#15029, TRD-864)
    The issue where an incorrect bonus agreement line was used for calculating the bonus amount - despite quantity-based tiers being defined - has been resolved. The system now reliably selects the appropriate quantit tier based, ensuring accurate bonus calculation according to the defined thresholds.
  • Item Suggested Retail Price: Error at Copying Item (Record already exists) (#15251, TRD-889)
    Fixes an issue where copying an item with suggested retail prices led to an error due to duplicate primary key values. With the feature “Item Suggested Retail Price with Country Code” enabled, the table’s primary key was changed to a sequential ID. However, the copy logic did not correctly generate a new unique ID, resulting in a conflict. This has now been resolved by ensuring that a new ID is properly assigned during the copy process.

Change

  • Show Notification when using Duplicate GTIN (EAN) (#12655, TRD-653)
    A notification was implemented to inform users if a GTIN (Global Trade Item Number) or an EAN (European Article Number) entered already exists in the Item table. This check is triggered when entering a value in the field "GTIN" in the item card or when applying an item template. If a duplicate is detected, a notification is displayed indicating the item number that is already associated with the GTIN. The notification can be deactivated individually via the "My Notifications" page, under the setting titled "Duplicate GTIN Check for Items".
  • Removed logic for determining VAT & Gen. Bus. Posting Group from Ship-to Address depending on "Bill-to/Sell-to VAT Calc." setting in General Ledger (#14113, TRD-760)
    The previously implemented logic (introduced with KUMAVISION trade 26.0.2993.0) that derived the VAT Business Posting Group and General Business Posting Group from the Ship-to Address, depending on the "Bill-to/Sell-to VAT Calc." setting in the General Ledger Setup, has been removed. This reverts the behavior to a simplified and more predictable logic, eliminating the dependency on the "Sell-to/Buy-from No." setting.
  • Documentation for public procedures and Integration-Events (#14567, TRD-819)
  • Obsolete vendor fields "KVSTRDMinimum Order Value" and "KVSTRDCarriage Free Limit" (#14588, TRD-820)
    The fields "KVSTRDMinimum Oder Value" and "KVSTRDCarriage Free Limit" in the Vendor table are set to Obsolete-State = Pending. Fields an functions will be moved in the KUMAVISION Base App.
  • Translation table for Item Charges & Alloy Surcharges (#14962, TRD-656)
    A translation table has been implemented for item charges and alloy surcharges. This enables multilingual support by linking translations to the original entries. Translations have been added for both sales and purchase line item charges as well as for alloy surcharges. The translations for alloy surcharges are also applied within Drop Shipment and Special Order processes.
  • Minimum Sales Order Value with Sales Order Type Blank (#14966, TRD-861)
    The system currently requires a defined Sales Order Type in the "Minimum Sales Order Values" table in order to apply a minimum order value. However, it should be possible to define a minimum sales order value without specifying a Sales Order Type. This default value should apply to all sales order types that do not have a specific minimum value defined or where the application of a minimum order value has been explicitly excluded via the sales order type flag.
  • Optimize logic for determining the valid Minimum Sales Order Value (#15009, TRD-862)
    The logic for determining the applicable Minimum Sales Order Value has been optimized to better respect the prioritization from specific to general conditions. Previously, in cases where a specific rule (e.g. for a particular Customer or Customer Group) should have applied, a more general rule (e.g. All Customers) was used. The updated implementation ensures that more specific Minimum Sales Order Value rules (e.g. Customer, Customer Group) take precedence over general ones (e.g. All Customers), preventing unjustified surcharges.
  • Incorrect insurance price calculation when unit differs from associated rental line (#15032, TRD-867)
    This change fixes an issue where insurance prices were incorrectly calculated when the unit of the insurance line differed from that of the associated rental line. The calculation now properly accounts for unit discrepancies, ensuring that the insurance price reflects the intended pricing based on rental duration and unit consistency.
  • Implement Prompt for Recalculating Lines When Copying from Vendor History (#15033, TRD-868)
    When copying a document from the vendor history to a new one, users are now prompted to decide whether the lines should be recalculated.
  • Convenient Reduction of Quantity of item with Alloy Surcharge after partial delivery/ deliveries (#15054, TRD-871)
    The quantity of an item line with alloy surcharge can now be reduced to the shipped/received and invoiced quantity. The corresponding surcharge lines are automatically adjusted through validation. Manual changes to the surcharge line quantity remain restricted, as consistency between item and surcharge quantities is enforced. Additionally, an event subscriber previously overriding standard behavior was removed to prevent incorrect automatic updates of ship/receive and invoice quantities.
  • Error Message When All Item Replacements Have a Starting Date After the Working Date (#15123, TRD-877)
    When the available stock quantity of the base item is insufficient to cover the requested sales quantity, a selection menu is usually shown to choose from possible replacement items. Before this replacement selection menu is triggered, the system now performs a validation to check whether any replacement items are valid based on their defined start dates. If all replacement items have a start date later than the current working date, the selection logic is skipped entirely: no menu is shown, and the original item and quantity remain unchanged. This change prevents confusion and unnecessary error prompts when no valid replacements are available at the time of the transaction.
  • Update Valuation Date Logic for Alloy Surcharge Handling (#15136, TRD-875)
    This update introduces a Valuation Date field for managing alloy surcharges in sales-related tables and procedures. Users are now prompted to select a relevant valuation date when handling alloy surcharge data. Depending on the document type, the system allows choosing between the posting date (for invoices and credit memos), the order date (for all other document types) or the work date.
  • Remove internal from functions (#15228, TRD-888)
    Remove the “internal” of the some functions in Codeunit 5157184 "KVSTRDCalcUnitCostMgt" to make them usable outside the app.

26.3.3206.0 - 2025-07-08#

Hotfix

  • Automatic setting of "Qty. to Ship" or "Qty. to Receive" in Alloy Surcharge during document copy causes posting error (#14842, TRD-833)
    When a sales or purchase credit memo was created which used "Copy Document" and the source included an Item with an Alloy Surcharge, the system automatically set the "Qty. to Ship" or "Qty. to Receive" through internal logic. This led to an error message preventing the document from being posted. With this ticket, the issue has been fixed - the "Qty. to Ship" and "Qty. to Receive" is no longer set automatically in this context, ensuring the document can be posted successfully.
  • Wrong Dimensions in Alloy Surcharge Drop Shipment & Special Order line via Requisition Worksheet (#14844, TRD-839)
    When using the “Get Sales Orders” report within the Requisition Worksheet to create drop shipment or special orders, there is an option field called “Retrieve dimensions from”, which allows users to choose between the values “Item” and “Sales Line”. Previously, the option “Item” was not fully supported. As a result, the dimension values for Alloy Surcharge lines were incorrectly inherited from the Sales Line instead of the corresponding item charge dimensions, leading to inconsistent dimension assignments in the resulting purchase order. This issue has been corrected with this ticket. The system now properly supports the “Item” option.
  • Error when creating Return Order related documents with Alloy Surcharge: Duplicate record in purchase line (#14912, TRD-851)
    Fixed an issue where creating Return Order related documents from a Sales Return Order with an item including an alloy surcharge caused a duplicate record error in the purchase line table.

Change

  • Not Billable: Update to integrate new KBA feature (#14448, TRD-805)
    Updated the zero position logic to support the new KBA feature toggle, while maintaining compatibility with the previous implementation.
  • Error in Sales Order with Mandatory Field Check and Minimum Order Value (#14740, TRD-828)
    If an order is created for a customer with a minimum order value and the order value is below this minimum, an error message appears when the mandatory field check window opens at the same time.
  • Revision Item Planning Suggestion (#14785, TRD-799)
    A new field called “Reorder Period” was added to the item card and the stockkeeping unit. This field is now used in the Item Planning Suggestion instead of the previously used “Time Bucket”. The existing “Time Bucket” remains unchanged and continues to be used in standard planning. An upgrade routine was implemented to copy current “Time Bucket” values into the new “Reorder Period” field.
  • Make procedure "FindSuggestedRetailPrice" external available (#14787, TRD-818)
    Made procedure "FindSuggestedRetailPrice" external available and provided a summary.
  • MSRP recording by country/region code (#14795, TRD-702)
    The definition of Manufacturer's Suggested Retail Price (MSRP) has been extended by adding a Country/Region code. This enables price differentiation based on regional market conditions such as taxes, import duties, logistics costs, or competitive factors - even within the same currency zone. Due to primary key constraints in the existing table structure, the change has been implemented using a new table with a sequential key. Activation is managed via the KUMAVISION Feature Management.
  • Alloy Surcharge: Action for recalculating Unit Price & Cost in Purchase & Sales Documents (#14817, TRD-817)
    Introduction of a new line-level action for both purchase and sales documents to recalculate alloy surcharge prices based on the current setup of the customer or vendor card. The visibility of this action depends on the "Enable in Sales" or "Enable in Purchase" fields in the Alloy Surcharge Setup. In addition, the "Copy Document" report now includes an option to recalculate alloy surcharge prices for copied lines. If no valid price is found during recalculation, the price will be cleared and a user message will be shown. The existing logic from TRD-677 (Exchange Price for Alloy Surcharge at time of recording) was incorporated into this enhancement. Manual recalculation remains possible for Return Orders via the new line-level action.
  • Removal of fragments from Standard-Feature "Alternative Customer VAT Registration" (#14830, TRD-825)
    With BC version 25, Microsoft introduced the "Alternative VAT Posting Setup" for customers as part of the standard functionality. However, since the trade365 solution already handles VAT calculation based on the Ship-to address, this new feature was disabled. Currently, the corresponding menu entry "Alternative Customer VAT Registration" is still visible in the "Tell Me" but has no functionality. In addition, when entering a deviating country code in the ship-to address of a customer, a notification appears. However, clicking on "Add" does not result in any further action. Additionally, when accessing the "Alternative Customer VAT Registration" page or when clicking "Add" (Hinzufügen) in the notification triggered by entering a deviating country code in the ship-to address of a customer, no action occurs. Instead of failing silently, a meaningful error message will now be shown to inform the user that this functionality is not available due to the custom trade365 implementation.
  • Periodic Invoicing: Extend and implement logic for new invoicing interval types (#14845, TRD-840)
    The Next Billing Date calculation functionality has been extended to support new types: "Half Monthly" and "Decade". A new option field allows selecting between a date formula, half monthly or decade interval. Depending on the selection, the "Date Formula" field becomes either editable or locked. Additionally, the calculation logic for determining the "Next Billing Date" has been updated to reflect the new interval types. The enum used for the interval type is extensible to support future additions and an event publisher was provided.
  • Periodic Invoicing: Deletion and update logic for unposted invoices (#14847, TRD-842)
    Implemented logic to ensure that unposted invoices are automatically deleted when removing entries from the KVSTRDPeriodicInvoicingLog page. Additionally, related fields in the periodic invoicing process are now correctly updated during deletion and posting actions (e.g., clearing the unposted invoice number, setting the "Posted User ID", and considering the "Via Periodic Billing" flag in the Sales Header).
  • Periodic Invoicing: Add sales order number to created document lines (#14848, TRD-843)
    The sales order number is now included in the summary lines and document lines generated by periodic invoicing.
  • Activate Rental Item for production items (output) (#14855, TRD-847)
    Extended the activation logic for rental items to support production output postings. The system now identifies relevant postings of type "Output" and verifies whether they are completely invoiced before allowing activation. An error message is displayed if invoicing is incomplete.
  • Add events for fixed asset initialization and service item creation (#14956, TRD-859)
    Added integration events "KVSTRDOnBeforeInitAndInsertFixedAsset" and "KVSTRDOnBeforeInsertServiceItemInCreateServiceItem" for fixed asset initialization and service item creation to enable customization during rental item activation processes.

26.2.3129.0 - 2025-06-13#

Change

  • General performance and stability improvements.

26.2.3112.0 - 2025-06-10#

Change

  • Misc. fixes for new rental functions (#14638, TRD-821)
    Misc. fixes and improvements for new rental functions.
  • Service - comfort functions for warranty (#14659, TRD-270)
    You can now also define a standard warranty duration for the service item group. This has a higher priority than the value in the service setup. The warranty duration on an item tracking still has the highest priority. Users are now prompted to keep the warranty start dates for parts and labor in sync in case one is changed. If a service item is created via the “Create service item” function in the service item line, any warranty data entered is also saved. If warranty data is subsequently entered for a service item, the user is now asked whether this should be copied to existing service item lines (data that has already been entered manually is NOT overwritten). Other minor adjustments have also been implemented.

26.1.3087.0 - 2025-05-26#

Hotfix

  • Periodic Invoicing with Alloy Surcharge (#14452, TRD-806)
    During testing of Periodic Invoicing, it was observed that the Alloy Surcharge is incorrectly allocated. Although this issue had already been resolved for standard Sales Invoices, the Periodic Invoicing process appears to assign the "AlloySurchAttachToLineNo." incorrectly. It is suspected that the Shipment Lines are not being properly retrieved. This issue has been resolved with the implementation of this ticket.

Change

  • Copy Document: Block functionality when using a Rental Document (as source or target) (#14393, TRD-798)
    Copying rental documents (as source or target) is currently disabled due to the complexity of specific rental-related data structures (e.g. insurance fees, rental item BOM, availability checks and different billing types). These elements cannot yet be reliably handled during automated copying. The restriction applies to both the classic and redesigned Rental module (see KUMAVISION Feature Management). An event "KVSTRDOnAfterIsCopyDocumentAllowedForRental" has been introduced to allow controlled overriding where needed. This event got added to the report "Copy Sales Document".
  • User permission to edit sales prices and discounts (#14440, TRD-802)
    User-specific permissions for editing sales prices, discounts, and Zero Positions in sales documents have been implemented. The necessary permission flags were added to the User Setup, allowing control over the editability of relevant fields. By default, all permissions are enabled and must be explicitly revoked. An upgrade and install routine was introduced to initialize the default values in existing environments. Additionally, the editability of the invoice discount amount in the Sales Statistics and Sales Order Statistics pages is now controlled based on the user’s setup. Due to technical limitations in the Microsoft standard, it is not possible to distinguish between sales and purchase contexts in the VAT Amount Line. As a result, a direct validation with user feedback cannot be implemented. Instead, the fields are made non-editable when permission is missing, without displaying an error or information message to the user.
  • Line split function in sales and purchase documents (#14502, TRD-190)
    A new “Split line” action has been created in the lines section of sales quotes, sales orders and purchase orders. This makes it possible to split the quantities of one line into a second. This can be useful if, for example, the shipment date of part of the items changed. Reservations and item tracking are taken into account and can also prevent splitting at the same time.
  • Add Salespersons/Purchasers in (Registered) Detailed Bonus Calculation Lines (#14503, TRD-803)
    The salesperson/purchaser code should be visible in the detailed bonus calculation lines. It should also be transfered into the registered lines.
  • Bonus Entries (Sum) and Quantity Bonus Credit Memos (#14504, TRD-804)
    There should be a new field “Bonus order type” in the "Sales & Receivables Setup" and the "Purchases & Payables Setup". All created bonus credit memos should be assigned this order type. Furthermore, there should be fields on the customer and vendor card that show the total amount of the bonus entries (bonus amount) and the number of credit memos (delimited to the new order type).

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

  • 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)