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.
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
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.
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.