Build 570.3

Hot Fixes 6

Release Date 3/4/2025

B209787 - Inventory Count preload form not showing bin field if default location is a non-binned warehouse

B209787     3/4/2025

Inventory Count preload form not showing bin field if default location is a non-binned warehouse

If the default warehouse is a non-binned warehouse and the users clears to the warehouse field and chooses a binned warehouse, the bin field will not appear. The default setting has been removed from the form to fix the issue. The form can be customized to add this feature in for customer who only have binned warehouses.

E209672 - Add Pallet support to SAP Preload Inventory Count Process

E209672     3/4/2025

Add Pallet support to SAP Preload Inventory Count Process

Adding support for pallet counting to the new preload inventory counting process that was created for SAP inventory counting

E209804 - Add SQL Server 2022 Support to the SAP SQL Product Updater

E209804     3/4/2025

Add SQL Server 2022 Support to the SAP SQL Product Updater

SAP Business One FP2411 added support for SQL Server 2022. The product updater now supports this new version of SQL Server.

Release Date 2/19/2025

B209795 - Updated FedEx CountryCodes for US Territories

B209795     2/19/2025

Updated FedEx CountryCodes for US Territories

Updated wsPkgCountryCodes tables for FedEx shipping to US Territories

B209796 - Fulfillment Manager Delivery creation fails if order has deleted lines (Error: Invalid row)

B209796     2/19/2025

Fulfillment Manager Delivery creation fails if order has deleted lines (Error: Invalid row)

If Sales Order has deleted lines, users were seeing an error that referenced an invalid row when shipping.

Release Date 2/10/2025

B209807 - Error when posting a production receipt from preload referencing the [IGN1.TranType][line: 0]

B209807     2/10/2025

Error when posting a production receipt from preload referencing the [IGN1.TranType][line: 0]

When posting from production receipt preload error about : Transaction type should be filled only in production complete transaction [IGN1.TranType][line: 0],Object was setting the BaseLine number on the posting document which causes an error if the document type is a Production Receipt. This was previously fixed for single transaction objects but was not fixed in the post from preload

Enhancements 5

E209461 - Add setup for shipping account by customer in Agility Shipping

E209461     2/10/2025

Add setup for shipping account by customer in Agility Shipping

Added setup to allow different Agility Shipping accounts based on Customer and Location. The 1st check will be for an account that is present for Ship From Location and the Ship To Customer. The 2nd check will be for an account that is present for the Ship To Customer. The 3rd check will be for an account that is present for Ship From Location. If no account exists for any of those scenarios, the account information from the Carrier Settings will be used.

E209770 - New method to Delete Production Order Line

E209770     2/10/2025

New method to Delete Production Order Line

Created a new method to delete order lines from production orders

E209771 - New method to Add Production Order Line

E209771     2/10/2025

New method to Add Production Order Line

Created new method to add order lines to production orders

E209774 - New method to Cancel Production Order

E209774     2/10/2025

New method to Cancel Production Order

Created new method to cancel production orders

E209777 - BOPurchaseOrder Validation: GoodsReceiptValidatePOItem - Improve Performance

E209777     2/10/2025

BOPurchaseOrder Validation: GoodsReceiptValidatePOItem - Improve Performance

Update BOPurchaseOrder Validation: GoodsReceiptValidatePOItem to use DoQuery in place of DiAPI objects to reduce locking and improve performance.

Resolved Issues 2

B209237 - Goods Receipt PO Item Validation does not Accept Barcode that is not default barcode

B209237     2/10/2025

Goods Receipt PO Item Validation does not Accept Barcode that is not default barcode

When using the goods receipt PO form in SAP B1 both HANA and SQL, If the user scans a barcode that is not the default barcode in the Item Master then the validation sometimes fails.,When receiving against a line of a PO that has a value in POR1.CodeBars, only the barcode in POR1.CodeBars of that line will return as a valid barcode. If two lines have the same ItemCode but different POR1.CodeBars values, the appropriate line will automatically be returned based on the POR1.CodeBars value.,When receiving a line of a PO that has no value in POR1.CodeBars but the item is set up with a UoMCode, ALL valid barcodes in OBCD that match the ItemCode AND UoMEntry on the POR1 will validate as a valid barcode. If multiple POR1 exists for an ItemCode and UoMEntry, the user might be force to choose the appropriate line to receive against during item validation.

B209769 - BOInv Validations: ValidateItemWarehouse - Improve Performance

B209769     2/10/2025

BOInv Validations: ValidateItemWarehouse - Improve Performance

Update Form Studio BOInv Validations: ValidateItemWarehouse to use DoQuery in place of DiAPI objects to reduce locking and improve performance.