Has anyone else had issues with FedEx LTL shipments not returning charges recently? We’ve had several instances/days of this…causing headaches for our accounting department. The web service reply will process the shipment (returning a tracking number) but also pass through a warning message (see below) and $0 into the Actual Charge and Billable Charge fields.
“ReturnStatus”:“WARNING”,“ReturnMessage”:“Unable to obtain courtesy rates.”
It’s of course been problematic for any shipment where the billing method is “Prepay & Add”. QS does not flag this as an error or display the warning message. We’re working on something in Kinetic to catch these shipments before they are marked “shipped” and sent to accounting but wondering if we aren’t the only ones.
“It’s a known behavior between Quick Ship and Kinetic that ‘info’ messages like this are not recognized by Kinetic. It only accepts success or failure, not informational or warning messages that could be acknowledged.”
The message/warning is populated on the ‘FedExFreightLTL_CreateOpenShipmentReply_XXXXX.xml’. It displays the severity as ‘WARNING’ instead of ‘FAILURE’ which seems to be what they are talking about.
They did create a Epicor Idea for me (KIN-I-4776) but with only 3 votes (2 from my org)…I thought I might be going crazy.
We just got it and can only do single pallets, so shipping calls the local office like they always have. I have a ticket that has been open for a while and just installed QS 2024.1 today to test if the issue is fixed.
can you link the idea here tyler so we can all vote on it. I find that hard to believe because they have always had messages that pop up, but is it just the kinetic interface? Now you have me wanting to go check everything.
We just freight directly out of Kinetic so I honestly don’t know if anything displays on the QS UI. But once we were made aware by our accounting team it was right into SQL to check for any prepay & add shipments where billable charges were $0 (then the XML files to diagnose).
No unfortunately. The route we were going to go down as a stop gap (which full disclosure might not be the best solution) was to just create a directive in Epicor that would throw a warning/error based on ShipHead.PayFlag & ShipHead.MFFreightAmt. Might use Erp.BO.FreightService.UpdateFreightedShipment but not 100%.
Greg, my other condition I am missing is whether they actually used quick ship or not… cause we ship things with other tools… so what is something that always has a value when QuickShip is used,… MFTransNum?
I think adding/referencing ShipHead.MFTransNum would do the trick (like you mentioned). Also, I’ll have to test but I think as long as it’s a post processing directive on Erp.BO.FreightService.UpdateFreightedShipment it could work.