5.0 DLL shipment Backout object on shipment in 'S' status sets order to booked status (1.)
Symptoms: 5.0 DLL - When using Shipment Backout object a shipment in status 'C' (confirmed shipped) will reset OE Order to status 4 (Picked.) If shipment is in status 'S' (Shipped) it resets the OE Order to status 1 (Booked) and also reset order lines to unpicked. Shipment should return to status 4 with no update to lines.
UPS Alert: 120900 or 120901 and Contract Rate write back
When contract rate is selected to be written back to the ERP and the UPS API returns Alert 120900 or 120901, a $0 value is returned to the contract rate. If alert 120900 or 120901 is returned, we should write back the list rate to the ERP.
POP Object UpdateOEWithFullProduction option writes incorrect qty to ship to order when UOM is different
Example Selling UOM = 5, Production UOM = 1, an OE qty of 12 will create a POP order for a qty of 60 (5 (Sls UOM) * 12 (OE Qty Ord)) When reporting and the option set to True it writes 60 back to order. When it should divide that number by Sales UOM. With option set to false and reporting it does update Qty To Ship with correct amount of 12 (POP Rpt Qty / Sales UOM)
POP Pull with selling UOM is incorrectly calculating the Bin Trx Qty
After reporting Production in WiSys and selling UOM >1, the incorrect qty value is being written to the bin the BinTrx record. When user confirm ships order in Macola they are presented with the Bin allocation screen due to incorrect value.
Recipient account not being passed to Agility Shipping
When using a Recipient account while shipping in Agility Shipping FedEx the Account Number and Recipient's information was not being supplied to the FedEx API resulting in the error “ShippingChargesPayment Payor - The payor’s account number is invalid”