Hinweis
Diese Unterlage dient nur zu Informationszwecken. Bei Verwendung zu anderen Zwecken lehnt SIEVERS-SNC Computer & Software GmbH & Co. KG jede Gewährleistung wegen Sach- und Rechtsmängeln ab. SIEVERS-SNC Computer & Software GmbH & Co. KG lehnt jede Haftung für direkte und indirekte Schäden - sei es aus Vertrag oder aus Gesetz - ab, die in Verbindung mit der Anwendung und sonstiger Nutzung dieses Handbuchs entstehen können. Dieses Handbuch kann bei Bedarf ohne vorherige Ankündigung von SIEVERS-SNC Computer & Software GmbH & Co. KG geändert werden.
Die beschriebenen Programme dürfen nur gemäß den Lizenzbedingungen angewendet oder kopiert werden.
Dieses Dokument ist zur Unterstützung von Endanwendern, Vertrieb und Service sowie Entwicklern erstellt und kann diesem Personenkreis ohne Änderungen überlassen werden.
Copyrightvermerk
Copyright © 2025 SIEVERS-SNC Computer & Software GmbH & Co. KG, ein Unternehmen der SIEVERS-GROUP, Hans-Wunderlich Str.8, D-49078 Osnabrück. Alle nicht ausdrücklich gewährten Rechte sind vorbehalten. Publiziert von SIEVERS-SNC Computer & Software GmbH & Co. KG.
For better overview, we have moved a few setup fields from the Load Carrier area to the Internal Transports area. The following fields are affected:
In the last release we introduced colored work indicators on the menus. Gray meant: There is something to do; Green meant: There is nothing to do. This color choice led to confusion for many users. For this reason, we decided to swap the colors. Now the colors mean:
Previously, only A7.1 displayed whether an inventory item was blocked. We have now also implemented this functionality on A7.2 and A7.3.
When a user presses the ESC key on their mobile device in the Mobile main menu, the login screen is opened. If automatic login via the Business Central user is activated, the user is immediately logged in again. This may not be desired by the user. For this reason, we have deactivated this function when calling the login screen via ESC.
The Mobile system now behaves as follows:
When scanning during stocktaking, incorrect entries can occasionally occur. Users reported to us that they sometimes have the quantity field focused and then accidentally scan the carrier code again. This causes the carrier code to be entered in the quantity field. To prevent this, there are now the following new checks on the quantity field:
If one of the checks is positive, a corresponding error message is issued.
It is now also possible to create a PTU on page A4.3 line processing. Use the menu entry A1 or the F5 key on the device for this purpose.
We have taken further steps to make the processing of Outbound Stock Post lines in production supply in C1.2 and C1.3 more efficient and user-friendly. For this purpose, a cumulative display of Outbound Stock Post lines was introduced, which groups move job lines with identical parameters (storage place, item, lot no., variant, expiration date and serial number). This reduces the scanning effort, simplifies operation and minimizes operating errors. The switch to the new view is made via a new setup field in the SIEVERS WMS Setup in the Production area:
Accordingly, the quantities in C1.3 are also displayed cumulated.
It is now possible to create a new SU directly in C1.2 and C1.3. For this, it is necessary to activate the following setup in the SIEVERS WMS Setup in the Production area:
As a result, a new carrier with the type SU and the default inventory measure defined in the SIEVERS WMS Setup is created.
In the menu of the A4 pages in SIEVERS WMS Mobile, there has been the possibility for some time to spontaneously create a new PTU during picking without having to use a blank barcode. With this release, we are now introducing the associated setup option in the SIEVERS WMS Team Card in the Picking & Packing area:
For technical reasons, in the past the hotkey functions of the SIEVERS WMS Mobile system were first created as CTRL + letter combinations and then linked to the F-keys of the scanners with a so-called keymapper. We and our customers have had problems with this keymapper more often recently, so we have now created an option field in the SNC Mobile Setup:
For test and development purposes, this option can be switched off. In operation, however, we recommend switching this option on, as there are fewer problems with the function keys. The reason for this is that the keymapper on the mobile devices is no longer used and therefore cannot fail.
If a storage place is scanned during stocktaking in B5.3, the system automatically takes over the current time into the Counted at field in the cycle counting list. If the user now leaves the interface without having entered a quantity, the time still remains and is no longer updated even with later entry.
We have fixed this circumstance by automatically clearing the Counted at field as soon as the user leaves the position without counting.
Previously, it was not possible to enter the threshold value 0 in the fields for Quantity difference % or Value difference (LCY), as this number was interpreted by the system as No value set. This meant that a 0% tolerance could not be set. We have now fixed this circumstance by implementing the following innovations:
If Load Carriers or inventory items are blocked or unblocked, this action now also affects existing move job lines. The blocking code is therefore set or removed in these move job lines.
Picking documents are now displayed in all tables with two leading zeros, for example -001 instead of -1. This has the effect that the sorting is now correct everywhere. Previously, for example, the 10th document was sorted between the 1st and 2nd.
A new report has been implemented that enables the determination and generation of production replenishment. This completely separates the replenishment of the rest of the warehouse from production.
The following filter options for storage places are available:
If no filter field is filled, the report checks and creates replenishment move jobs across all production storage places. The calculation and creation of replenishment corresponds to that of the regular Check replenishment report.
For some time now, it has been possible to specify a scrap quantity for output journal and Finish product. If there is a need, there is now the possibility to specify a scrap code. This scrap code is transferred to the corresponding field in the item journal line when creating the output journal.
In the SIEVERS WMS Setup in the Production area, the associated setup field Scrap code necessary has been implemented. Activating this field means that when specifying a scrap quantity, the scrap code must be entered.
An error has been fixed that prevented entering or changing a shipping agent in the warehouse shipment for customers without a predefined shipping agent.
An error has been fixed where inventory items were incorrectly reserved on PTU or SSCC, which led to inconsistent data.
We have fixed an error that caused the job queue entry that updates the warehouse shipment status to not always start correctly.
An error has been fixed that caused individual warehouse receipt lines to be incorrectly removed in A1.2.
We have fixed an error that caused the deactivation of Mobile functions per user to no longer work correctly.
It has been fixed that picked quantities in an SLT for serial picking were displayed as empty in warehouse shipment planning.
We have replaced an incorrect icon in the toolbar on mobile devices.
A display error has been fixed so that after scanning a blank barcode in A3.3, the entry of carrier data is now displayed correctly immediately.
We have fixed a problem that caused the fields “Storage place code finished products” and “Inbound Stock Post strategy code finished products” not to be pre-filled according to the stored hierarchy in the production order line.
When calling the storage place occupancy of an empty Load Carrier, no error message is displayed anymore, instead a note appears that no inventory item is available.
We have fixed a process error that caused A1.2o to continue to be displayed instead of A1.2 after posting a warehouse receipt in A1.2o and then calling a new warehouse receipt.
We have fixed an error that caused the field focus in C2.2k to get into a loop.
