What's new in version 2602.2.0.0

Resolved issues

The following issues have been resolved in this release.

ID	Description
366102	The system fails to populate the Location default dimension values on the Physical Inventory Journal lines when executing the Adv. Calculate Inventory action.
368041	The system fails to post a Warehouse Receipt when the document contains multiple lot numbers of the same item with incomplete item tracking reservations, resulting in an incorrect validation error.
371026	The system fails to reset the License Plate status from Picked to Open after a warehouse pick is cancelled, blocking subsequent picks from being created for the same item.
374601	The system fails to propose lot numbers when using the AutoFEFO function for a document line that uses a higher Unit of Measure (e.g., CRATE) than the Unit of Measure stored in Bin Contents (e.g., BOTTLE), resulting in no lots being assigned.
376051	An error occurs when registering the Warehouse Put-Away for items with a different Purchase and Put-Away Unit of Measure when using License Plates with multiple Lot numbers.
376645	An error occurs when processing an ad hoc movement for a mixed license plate. This issue occurs because the reason code is not copied from the journal batch template to the warehouse journal when the item reclassification journal is created during the movement.
374968, 370143	The system does not apply the correct local date when setting the registering date and posting date on warehouse journal lines and item journal lines created by scanner transactions, including ad hoc movements, direct put-aways, pick registrations, bin movements, and production output. The system incorrectly uses the Business Central work date instead of the user's local date, resulting in incorrect transaction dates when the scanner server operates in UTC and the user's timezone differs from UTC.
371396	The system fails to assign tracking correctly when the Assign Tracking by FEFO action is used on a production order component of a firm planned production order.Additionally, the system incorrectly increases the Quantity Per field value on the Prod. Order Component page each time the action is selected. This issue occurs because the action filters reservation entries by an incorrect source subtype value, which causes duplicate tracking reservations to be created.