KUMAVISION factory#
See also the following ChangeLogs#
26.2.2502.0 - 2025-06-11#
Hotfix
- Fixed bug Calculation of the remaining time field in FA routing (#14450, FCY-1852)
- Fixed bug the start and end date of planning level 1 and following is recalculated when changing the date fields on level 0. (#14514, FCY-1737)
- Fixed bug that the component quantity is emptied when setting the “Supplier” provision type via E+D change synchronization (#14539, FCY-1872)
- Fixed bug date error when posting goods receipt and goods issue depending on the selected region (#14555, FCY-1896)
- Fixed bug calculation of the production type field (master data) in the E+D order (#14565, FCY-1887)
- Fixed bug that when changing the “Work Center” via the etagis interface, the previous work steps are not updated (#14660, FCY-1923)
- Fixed bug that a production order with reference to a project and stored shipping units cannot be completed (#14661, FCY-1921)
- Update to BC26.1 was blocked by the mandatory field check of the work center groups, work centers and G/L account tables if not all fields required for the check were available (#14681, FCY-1912) see update note
- Fixed bug when creating a purchase order from the project plan line, the “Expected goods receipt date” is filled when creating the associated reservation (#13849, FCY-1730)
Change
- The “Outline” function in the project has been discontinued and set to obsolete (#14064, FCY-1774)
- The creation of a production order from the order costing and the project plan line has been standardized (#14261, FCY-1835)
- The fields “Planned Shipment Date” and “Shipment date” have been inserted as FlowField on the project plan line and display the value from the linked sales line (#14398, FCY-1663)
- The function “alternative VAT entry” and the function extension for controlling the VAT-relevant fields in connection with the delivery address of the KUMAVISION factory have been synchronized (#14442, FCY-1848)
- The “Extended capacity requirement” field is displayed on the EDOrderRouting page (#14468, FCY-1866)
- When creating a purchase order in the purchase request, the system checks whether an allocation exists. If there is no allocation, an error message is displayed. (#14482, FCY-1861)
- Error message vendor no. cannot be activated for ‘Project planning line’ with ‘Line type billable’ added (#14485, FCY-1873)
- Error message updated when closing project (#14515, FCY-1849)
- External work orders and stock transfer orders can be created directly from E+D order planning using the “Create orders” function (#14518, FCY-1680)
- Functions for attribute creation have been made available for use in the API pages (#14520, FCY-1891)
- The function “Copy E+D document” of the KUMAVISION factory has been extended by the field “Cost price per unit” in the FA routing (#14549, FCY-1895)
- When using the stock transfer order types, the system checks whether the “Function update: Stock transfer types” is activated in the KUMAVISION function management (#14585, FCY-1894)
- The function "Project items for Zlg. Tolerance/account" function, which can be activated for both sales and purchasing, is set to obsolete and discontinued. (#14586, FCY-1814)
- Display of the status of the project task line in the Gantt Viewer (#14587, FCY-1865)
- Project/plant construction-specific fields in the sales order line are only visible if the KUMAVISION factory plant construction solution is active (#14620, FCY-1918)
- The field ‘E+D production type’ was shown in the pages of the E+D order (#14632, FCY-1847)
- The publisher ‘OnCalcMfgItemOnBeforeCalculateCosts’ in the code unit ‘KVSFCYCalculateStandardCost’ has been extended by additional parameters (variables) (#14708, FCY-1937)
- License warning enlarged in project task status warning if plant engineering not licensed (#14711, FCY-1938)
Update Note The mandatory field check of the tables Work Center Groups, Work Centers and G/L Account will be adapted to KUMAVISION base. As a result, it is necessary to run the mandatory field check again for the aforementioned tables. This is done as part of the update, provided that all the fields entered for the check are available. Otherwise, the check is skipped during the update and must then be initiated separately via the “Mandatory field check” function on the respective list.
26.1.2407.0 - 2025-05-16#
Hotfix
- Action "Documents" in plant engineering did show documents which did not belong to the project. (#13843, FCY-1725)
- Fixed production order statistics with non-activated item costing (#14049, FCY-1785)
- Changed "Navigate Doc.-Proc.-ID" in the sales order (#14115, FCY-1802) If multiple sales documents were given the same process document ID an error could occur if one of them was a blanket order
- Changed automatic assignment of serial no. on production order status change (#14202, FCY-1783) If a serial no. was automatically assigned on production order status change, the serial no. assignment was not correctly created. This could lead to unexpected requisition lines in the planning worksheet.
- Fixed wrong error message after transferring requisition lines (Artikelversion) (#14292, FCY-1834) If an item with an item version in the planning worksheet was transferred to a requisition worksheet a wrong error message was displayed
- Fixed creation of a purchase order confirmation line (#14432, FCY-1850) If a purchase order was created by a purchase quote, an icorrect purchase order confirmation line was created.
Change
- Tracking entries will not be created twice from project planning lines and connected sales orders (#13800, FCY-1721)
- Changed error handling on assigment of a sales line to a job planning line in conjunction with item tracking (#13875, FCY-1719) If a sales line with an item with item tracking policy "Tracking Only" or "Tracking & Action Msg." was assigned to a job planning line, a wrong error message was shown.
- Changed behaviour of report KVSFCYDetailedCalculation (#14067, FCY-1750)
Report KVSFCYDetailedCalculation did not respect the status of production BOM versions und routing versions. Instead always the last versions were used. The calculation date was also not respected, the report used always workdate. - Added creation of setup und demo data (#14169, FCY-1543)
- Added date conficts in rolecenter service (#14204, FCY-1813)
A new cue was created in rolecenter service to show date conflicts. - Added new function "Set Project Location" in project tasks and project planning lines (#14217, FCY-1712)
Adding funktion to select Project Location for Project Tasks and Project Planning Lines. - Changed behaviour of creation of position no. in sales order (#14243, FCY-1829) If a sales document was created from project planning lines with different project task the resulting sales order lines could be numbered worng. Sum lines all had a position based on one of the project tasks.
- Changed deafult values on "Type" in Project Teams (#14259, FCY-1831) The Name could be shown incorrectly
- TellMe was changed to not show calculate trafiic lights was (#14286, FCY-1837)
- Set Job No. in Job Type to obsolete (#14289, FCY-1808)
- Enabled traffic lights pick on warehouse shipment (#14300, FCY-1843)
- Changed error message on creation of sales document from project (#14340, FCY-1845) If a user tried to create a sales line from project planning lines, which were already transferred to a sales document, a wron error message was shown
- Changed action "Routing" in E+D-Order Lines (#14435, FCY-1779) If routing was shown from a E+D-Order line, the wrong lines could be shown
26.1.2403.0 - 2025-05-14#
Hotfix
- Fixed Upgrade of Source Location (#14436, FCY-1855) Table source location was removed in KUMAVISION base V26. A new table source location was added in KUMAVISION factory V26 instead. The automatic upgrade of data from the old table to the new table failed and no data was upgraded, this was fixed in current version.
26.0.2299.0 - 2025-04-14#
Hotfix
- Fixed bug on "Copy E+D-Document" (#14103, FCY-1798) Not all field were copied on function
Change
- Redesign Source Location (#11669, FCY-1341) The table KVSKBASourceLocations was removed, another tble KVSFCYSourceLocations was added and all functionality was moved to the new table
- Removed obsolete subscriber to Requisition Line (#13863, FCY-1732)
- Removed all references to "Direct in Sales" und "Direct in Purchase" in table G/L Account (#13885, FCY-1734) Fields were removed by KUMAVISION Base, therefore all references had to be removed
- Changed calculation functions to support future compatibility to microsoft standard (#13948, FCY-1758)
- Removed obsolete etagis-handling (#13953, FCY-1761)
- Removed obsolete PDM code (#13954, FCY-1762)
- Removed obsolete configurator code (#13963, FCY-1763)
- Removed "Page Break" and "Font Style" (#13966, FCY-1770)
- PDM-Interface was expanded by Stockkeeping Units (#13979, FCY-1768) An API-Page "apiStockkeepingunit" was added, which enables external systems to add stockkeeping units.
- BC26: Artikel ohne Lagerbestand + Lagerhaltungsdatenkosten vs. Kalkulation (#14027, FCY-1775)
To avoid problems, it is prevented to activate one of the new flags in "Manufacturing Setup" namely "Include Non-Inventory Items to Produced Items", "Finish Order without Output" and "Load SKU Cost on Manufacturing" together with the Calculation Module in "KUMAVISION Module Setup";. - Respect new "Flushing Method" in traffic light picks (#14036, FCY-1764) The functionality "Traffic Lights Pick" was changed to respect the new "Flushing Method" of "Pick and Manual"
- Removed obsolete permissions (#14050, FCY-1786)
- Removed references to obsolete actions (#14051, FCY-1787)
- Fixed call to calculation in Page "Job Planning Lines" (#14066, FCY-1733)
On the "Job Planning Lines" subpage, the action group "Calculation" was hidden. The visibility is now fixed and the included actions "Calculate Manufacturing Calculation" and "Calculate Tracking Lines" are accessible. - Page TrafficLightAssignCard was added to enable users to change the traffic light images (#14077, FCY-1792)
- Respect code fix in KBA (KBA-2049) in FY-code (#14084, FCY-1790) Kumavision Base fixed the handling of Warehouserequestlines to respect "Completely Handled" in source documents, this change had to be respected in factory-code