KUMAVISION base#
See also the following ChangeLogs#
28.1.6310.0 - 2026-05-19#
Hotfix
- UDI: The “Create Field Mapping” function does not work during data import (#17686, KBA-2937)
Obsolete fields are now ignored. - Checking the posting date in service lines for KBA types results in an error (#17699, KBA-2942)
The posting date from the header is now pre-filled for KBA types (like Bundle). - Dispatch Order Wrong Value of Goods (#17715, KBA-2946)
The quantity in the delivery order was not included in the calculation of the value of the goods. Now the "Qty. to Handle (Base)" is used for the calculation.
28.1.6252.0 - 2026-05-12#
Hotfix
- Inventory Summary - Performance (#17658, KBA-2846)
Optimized the performance of the Inventory Summary recalculation. Recalculations now take only a few minutes, even with extremely large volumes of data. - Location Code from Ship-to Adress (#17660, KBA-2933)
When searching for a location code using the order type, the location code from the ship-to address is now taken into account, not just the customer.
28.1.6241.0 - 2026-05-11#
Hotfix
- An irritating confirmation message appears when creating a quote request without a vendor in certain (#17373, KBA-2866)
The order of validation has been changed. - When Responsibility Center is selected on the Sales Renewal Quote, Dimension from Customer Contract (#17386, KBA-2868)
For documents from the Subscription Billing module, no default Salesperson is currently set, as this would override the dimensions from the Subscription Billing module. - HTML Layout vs. Optimizer (#17392, KBA-2873)
If a Word document is added to a master layout and used as the body template for “Send Email,” it is rendered as HTML. This caused an error in the Layout Optimizer. - Single parcel shipment partially ignores posting type from Dispatch&Carrier Setup (#17403, KBA-2823)
When posting single-parcel shipments, the posting option configured in the setup was ignored and always invoiced. This has been fixed, and the setup is now correctly respected, allowing delivery-only postings. - An blanked order line number without an blaniked order number results in an error in the subsequent process when posting the order (#17412, KBA-2881)
To prevent errors later in the process, checks for blnaket order links have been added to the req. worksheet and the order release process. - Dispatch Order - Incorrect weight calculation for lines "Only net weight and <> base unit" (#17443, KBA-2783)
Fixed incorrect weight calculation for lines with non-base units where only net weight was considered. - Signal values in the production overview (#17444, KBA-2755)
During an analysis of the calculation function, it was discovered that a value had not been calculated. This has been corrected. - Dispatch Order - Incorrect weight calculation when changing the 'Qty. to Handle' (#17448, KBA-2782)
Fixed incorrect weight calculation across all related fields when changing the “Qty. to Handle”. - Sales Price from Blanket Order to be adopted regardless of “no” vote (#17452, KBA-2883)
MS Standard previously retrieved the sales price from the blnaket order. This is now prevented. This is also done for purchasing. - Apply template to the item/customer/vendor list when mandatory field check is enabled (#17502, KBA-2897)
The user cannot assign an item, customer, or vendor from the list if the mandatory field check has been successfully completed. If there is a single record in the selection that meets the criteria, it is identified; otherwise, a message is displayed indicating the number of affected records. - Converting a quote to an order with alternative lines and item charge assigment results in follow-up (#17510, KBA-2903)
Item charge assignment lines are no longer created for alternative lines. If a line is converted to an alternative line, the assignment is deleted. The same applies when transferring data to an invoice or order (therefore, no data upgrade is necessary). - Archived Calls: "Finishing by" field is not filled (#17588, KBA-2914)
The “Finishing by” field is now populated with the logged-in USER ID in the same way as the “Finishing Date.” - Putaway - Vendor Shipment No. and Quantity not correct (#17598, KBA-2912)
Fixed an issue where Vendor Shipment Numbers were not correctly retrieved in a specific configuration. Additionally, problems with quantity display were resolved.
Change
- Multiple Shipment No's for Sales Order in Dispatch Reports (#16713, KBA-2338)
If the dispatch order consists of multiple shipments, multiple shipping numbers can be printed on it. - Extension of Sales Order Types to include Location Code, Shipping Agent Code and Shipping Agent Serv (#17021, KBA-2729)
Using the sales order types, the Location Code, Shipping Agent Code, and Shipping Agent Service Code fields in sales documents can be filled in differently from the default values. - Default Shipment Method Code in the Dispatch Order via Transfer Routes (#17286, KBA-2843)
The shipment method code can now be predefined via the transfer routes. - Item: Quantity in Transfer Order (#17381, KBA-2870)
The quantities in the transfer order were made available on the item card using the Flowfields "Qty. in Transfer (Inbound)” and “Qty. in Transfer (Outbound)” fields. - VLOG and BEO Interface Curency from Setup (#17405, KBA-2879)
For the XML Nodes: zoll_waehrung and send_warenwertwaehrung we take the Currency ISO Code depending from the new field "ISO Currency Code" in the Dispatch Setup. - The KVSKBAAssignedUserID is not transferred when creating assembly orders from the planning worksheet (#17523, KBA-2872)
The logic from the other line was also added to the assembly orders. - Telemetry Signal for Dispatch Order Provider (#17531, KBA-2817)
New telemetry signal for used dispatch provider. - Posted Dispatch Order - Adjusting the info box (#17540, KBA-2890)
The info box for the posted dispatch order has been updated to match that of the unposted order. - Tariff No. at Posted Purchase Return Shipments (#17592, KBA-2908)
The tariff no. and country of origin can now be printed on posted purchase credit memos and return shipments. - BEO - Track Login Table (#17636, KBA-2926)
The login package table is now included in the posted dispatch, allowing the used table in the transfer to be traced. - Description of payment terms in document reports (Master Layout) (#17638, KBA-2797)
If desired, the description of the payment terms can now also be printed on the sales invoice. This must be configured in the payment terms settings.
28.0.6049.0 - 2026-04-10#
Change
- Value of goods in Dispatch Order (#15425, KBA-2344)
The value of goods determination logic for dispatch orders has been extended. All relevant documents that can be used are now supported. - Remove changes and obsolete elements (#17073, KBA-2780)
The KBA has been updated to comply with BC28, and obsolete KBA elements have been removed. - Adressblock Company Information in Document Reports (Master Layout Reports) (#17117, KBA-2498)
In the company data, you can now control whether your own address should be printed in the header of the master documents. This option is now independent of printing on company letterhead. - Conversion quote without vendor to new MS functionality (#17151, KBA-2801)
A similar function was implemented in the standard with BC28, so the KUMAVISON base functionality must be deactivated. - Activate Transfer Order Feature (#17175, KBA-2813)
This feature is no longer a feature and is enabled for all customers. - Purchase Get Order Lines copy own Data (#17181, KBA-2816)
The “Get Order Lines” function in the purchase invoice now also includes the KBA fields and additional records. - Changes Attributes at Variants (#17338, KBA-2803)
Microsoft's new item attributes for item variants have integrated KUMAVISION's functions for minimum and maximum values as well as print control. - Notice of limitations at workting with Match Order Lines (#17348, KBA-2859)
We don't block the feature, but we inform the user about the limitations. - Mandatory field check with a condition on the primary key (#17349, KBA-2861)
The field check has been modified so that conditions on primary key fields also work.