JDK 11 is required for Broadleaf release trains 1.7.0-GA, and beyond.
JDK 17 is supported for Broadleaf release trains 1.8.1-GA, and beyond.
Fixed the ability to update the safetyStock via an inventory import.
Fixed a validation bug that allowed the creation of multiple SkuInventory records with matching SkuRef (externalId, skuCode, etc.) values for a single InventoryLocation. Please refer the [_how_to_fix_your_inventory_data_state] section below for more details.
Execute the query below in the inventory database to detect the duplicate inventory entries:
SELECT S1.*
FROM INVENTORY.BLC_SKU_INVENTORY S1
JOIN
(SELECT LOCATION_ID, SKU_CODE, COUNT(SKU_CODE)
FROM INVENTORY.BLC_SKU_INVENTORY
GROUP BY LOCATION_ID, SKU_CODE
HAVING COUNT(*) > 1) S2
ON S1.LOCATION_ID = S2.LOCATION_ID AND S1.SKU_CODE = S2.SKU_CODE
ORDER BY S1.LOCATION_ID;|
Note
|
The above SQL query assumes that your SkuInventory records use the skuCode field to reference skus. However, if you leverage other sku reference fields, make sure to execute the same query, swapping out SKU_CODE for EXTERNAL_ID, UPC, EAN, or GTIN.
|
If duplicate records are identified, then you’ll want to archive/remove SkuInventory (BLC_SKU_INVENTORY) records so that only one remains for each combination of sku reference (SKU_CODE, EXTERNAL_ID, UPC, EAN, or GTIN) and inventory location. We don’t have specific opinions about which record is kept, but we recommend that you ensure the related quantities are accurate.