Release Notes Automotive 39.9

Handling Units

Handling-unit processing

• Fix for posting error caused by inconsistent Shipment/Source mapping (Mixed Master). Posting a Warehouse Shipment could sporadically fail with the error “Sales Shipment Header already exists.” The root cause was a faulty synchronization logic for Mixed Master pallets: after building a Mixed Master from singles of several sales orders and unregistering / re-registering the loading-equipment assignment, a Shipment No. could be mapped to the wrong source order. Until now, affected records were corrected manually via SQL. The synchronization now assigns Shipment Nos. uniquely per Source No., so Warehouse Shipment posting runs stably.

• Fix for label printing after partial Warehouse Shipment posting. After posting a Warehouse Shipment, the printing of VDA labels and goods tags could fail in certain cases. The root cause was a too coarse post-processing logic: the Posted flag on Loading Equipment assignments was only set when every Warehouse Shipment line could be cleaned up. In mixed constellations (for example a sales line outside the Automotive cleanup branch, or a line with shipped quantity 0), the flag stayed empty for all lines – including the actually shipped ones – and downstream print/filter flows broke. Until now this was fixed manually via SQL. The post-processing now marks the loading-equipment assignments of the actually shipped lines as Posted on a per-line basis, so label printing runs reliably.