General

• Dosing priority for semi-finished goods
  The dosing priority for semi-finished goods was not always handled correctly.
• Booking: Resolve negative stock
  Resolving a negative stock on receipt must not consider booking indicators for the negative stock.
• Booking: Resolve planning
  Resolving a planning on receipt must take over the original timestamp of the planning.
• Recipe optimization: Container optimization
  Some detail data of the involved components were not adequately considered.
• Material availability check
  The consideration of open orders must only be done in the manager.
• Barcode generation
  The base number was limited to 7 digits but can range from 6 to 9 digits.

Manager

• Stock detail
  The use of objects from the tree was not always correct after a refresh.
• Components
  When copying components, process recipes were sometimes copied twice.
• DB revision
  When activating a new manager for the first time, depending on the existing data model, a revision upgrade may potentially be carried out. The revision version should only be increased if everything has worked properly.
• Configuration
  The ESApack setting "Hide pause button" was persisted internally with a slightly incorrect identifier (unnecessary space).

Material flow manager

• Production scale strategy: LD optimization
  The container calculation may generate additional automatic containers if the minimum number of containers has not been reached yet.

Transit depot booking

• Initialization check
  The module may only start operation if certain infrastructural requirements are met. The check on the version of the booking functionality was not always correct, and the error message was also misleading.

General

• Database Schema Information
  An internal functionality for querying database schema information has been improved to handle longer-lasting network disruptions more stably.
• Recipe Optimization - Residual Quantity Calculation
  The tolerance of the scale is now taken into account in the residual quantity calculation.
• Bizerba ST
  An issue in the BIZERBA ST scale driver has been fixed (DecodeReceiveData).
• Booking - Date Conversion
  A data type conversion of a date value within a booking was not correctly performed in a specific case.
• LHM Relocation - Article Base Unit
  In an LHM relocation, only the base unit of the last article in an LHM was persisting in the operations.
• Database Connection Data
  When using multiple threads, it could happen in a specific constellation that after a longer module runtime, the database connection data was internally lost. The module then had to be restarted.
• Recipe Optimization - Access Violation
  An access violation could occur during optimization on a piece scale when no scale was available.
• System Server: LHM Print - Production Date
  The production date was not correctly determined.
• MoveRT: Relocation with Source Batch Code - Additional Check
  When setting 'Relocation with source batch code (valid only for one source and one destination),' only the current position list was checked for the presence of 2 positions. However, it was possible that already completed positions were no longer included here. Therefore, an additional check is now performed.
• Transit Depot Booking: Warehouse Operations
  When determining the relevant data, warehouse operations are now also included to prevent unintentional bookings due to time-related issues.
• Trade: Gassner DMA03 - Timeout
  A timeout issue in the DMA03 scale driver has been fixed.

Manager

• Feedback - Email
  The email address has been updated.
• Goods Receipt Piece
  An issue with entering a supplier batch code in goods receipt piece has been fixed. Commas are no longer allowed for the number of packages.
• Edit Dosing Order
  It could happen that a specified change in the batch quantity was not applied. There is now a configuration setting that determines whether the 'Order Description 2' can be changed retroactively in general or only per batch.
• Define Packaging Units - Search Filters
  The search filters of the displayed tables were not functioning correctly.
• Order Planning - Moving Orders
  When moving orders, in certain rare cases, a necessary SQL statement to update the sort code could not be successfully executed.
• Stock Inventory - Data Unavailable
  If data cannot be retrieved for certain points in the stock inventory query, it is now handled better.
• Stock by - Filter: LHM Number
  In the 'Stock by' view, a filter must be specified to limit the amount of data. LHM Number is now considered a relevant filter in this regard.
• Evaluation Packing Orders
  Archived bookings were not taken into account.
• Load Piece - Go to
  'Go to' did not work with individually customized column definitions.
• Mass Change Expiry Date Extension
  An issue with the mass change of expiry date extension has been fixed.
• Relocation
  A relocation from 'non-batch-managed' storage locations could trigger an access violation in a specific case.
• Transport Orders
  Routes were not displayed for manually created TAs if 'CodeBaseUnit' was not defined.
• Storage Location Audit
  An SQL statement could not be executed in databases with older version or compatibility levels.
• Operator Log Entry Goods Receipt
  The operator log entry that occurs when deleting goods receipt entries was not correct.

ESA Logistics

• Transport Item Dialog - Expiry Date
  An issue with disabled expiry date at the Transport Item dialog has been fixed.
• Web: Relocation Expiry Date
  When relocating non-batch-managed storage locations, it could happen that the expiry date was not correctly evaluated.
• Persist Transport Entries
  A timestamp when persisting transport entries is now uniformly done with the time of the DB system instead of the local system time.

MFM

• Identification Strategy - Order Reference
  It could happen that the order reference was not correctly determined from the available data.
• Reservation of AKL Boxes - Gram Scale
  The weight values from gram scales were not correctly handled.
• Production Scale Strategy - Contamination
  When a container was checked for contamination and the distance to the 1st route destination was duplicated, an error could occur.

GENERAL

• Note Tree View
  In surfaces with a tree view, it could happen that a note was not displayed during a mouseover event.
• Booking - Negative Stock Resolved by Receipt
  In cases of "Negative stock resolved by receipt," the QSId must be taken into account.
• Order Acknowledgment
  An error in an SQL statement during the process of acknowledging an order was fixed (start of dosing).
• Operator Log Entries
  It could happen that operator log entries were not made if the entry exceeded the allowable maximum size.
• Booking - Archiving of Stock Movements with Batch Code
  Issues could arise during the archiving of stock movements within a booking when a batch code was specified and it was present with different upper/lower case letters.
• Booking - Unlocking
  When unlocking items, it could happen that information texts and label assignments were lost.

MANAGER

• Emptying Storage Location
  Issues could arise when emptying a storage location in relation to LHMs present, depending on the licensing variant.
• Edit Order
  When editing an order, it could happen that the order description_2 of individual batches was overwritten.
• Dosing Order Creation - Expiry Date
  The initialization of the expiry date during the creation of dosing orders was not correct.
• Packaging Units
  The editing form for packaging units was improved.
• Transfer Orders (RT) - Operator Log Entries
  Operator log entries are now made for changes in transfer orders.
• Transport Orders
  An error could occur when editing transport order positions if a column definition was active.
• Packaging Orders
  The target date was not queried from the database when displaying packaging orders.
• Evaluation of Packaging Orders
  Several improvements were made to the evaluation of packaging orders (e.g. avoiding duplicate entries).

MFM

• PWS - LD Optimization
  If the remaining quantity was less than the minimum scale weight, issues with LD optimization could occur with automatic components.

RT8BE

• Missing End Time in Logging of Actual Quantity during Intermediate Emptying
  If no end time is specified by the PLC, it is assumed to be the current time.

ESACOM

• FIFO Order Violated
  The batch code requirement was always set. This resulted in non-FIFO booking, but always booking the dosing quantity from the 1st batch code in stock.

General

• Troubleshooting with Logging SQL Problem
  When encountering an SQL problem, the line number was not correctly output in the logging.
• Delete warehouse occupancy
  When checking if a LHM still has active warehouse processes, reservations or plans were not
  considered separately.
• Conversion problem with XML booking
  During a data type conversion via an XML booking, incorrect booking timestamps could occur.
• Loader-Lock Booking DLL
  When using the external booking DLL, a locker lock could occur, preventing the correct unloading
  and thus preventing a proper shutdown of accessing modules.

Manager

• Dialog 'Loading equipment'
  The check for invalid characters in the description has been improved.
• Infrastructure version check
  By using an unauthorized older Manager module, the check value of the
  infrastructure version check could be falsified.
• SQL problem when editing relocations
  During the editing of a relocation, the result of an SQL query could be incorrectly calculated under certain
  data constellations.
• Incorrect check when overwriting a configuration file
  An incorrect check allowed unauthorized overwriting of a configuration file. This
  functionality is not used in current production or by end users.
• Search field in warehouse movements
  The search field in the warehouse movements was limited to 15 characters.
• SQL problem relocation overview
  The result of an SQL query in the relocation overview could, under certain data constellations, lead to
  an excessive quantity in the sum of departures or entries.

MFM

• Competition check
  In a specific competition check, the warehouse location of a LHM is now also considered.
  • Rounding error in calculation of container quantity
  Due to a rounding error, the calculation of container quantity in a production scale strategy
  could be incorrect.
• Update of LHM number in order
  The update of the LHM number in the order has now been slightly adjusted to avoid colliding with the order
  sequence check during route release. In such a case, it could happen that the correct sequence
  was bypassed.
• Buffering at another level
  When buffering at another level, in rare cases, the transport type could be incorrect during route release.
• Deadlock in route release
  In a certain constellation (HDC removal via IDMP directly), a deadlock could occur in route release.
• Route release: Check on source lift warehouse location
  Lift warehouse locations, which are not transported with the transport type 'Lift', should only be considered if
  they are already released.

ESAcom

• Batch code search
  A bug in an internal batch code search without LHM was fixed.
• Incorrect booking timestamp in batch code selection
  The booking timestamp could be mistakenly taken from the original timestamp of the
  relevant batch code during batch code selection.

System server

• Missing batch codes in standard relocation
  In the standard relocation, it could happen that batch codes were missing in the 'Relocation_Pos' table. The
  corresponding archive table was not considered in the relevant logic.
• Memory leak
  Due to an unexpected logical error, a memory leak of the automatic component acknowledgment
  could occur. Such a logical error is now also brought to the operator as a warning in the system messages for
  awareness.

Licensing

• Access authorization
  Individual modules required full access to the license. Now read access is sufficient.

Logistics

An issue with a localized resource could lead to a runtime error in a specific IIS configuration.