Pull Correct Ship Via from Sales Order into Pack

Hi All,
We have updated shipping methods for a few customers. As a result, we have updated the customer record to show the new ship vias. We realized that old sales orders that have already been created, have the old ship vias based on the old customer ship vias.

So I pulled a list of the offending sales orders, and updated their ship vias to match their customer’s ship vias.

After I did this, I expected that my shipping packs would pull in the correct ship via based on either the updated customer record, or the updated sales order. Instead, new packs are still pulling in the old ship via. This is all in the Customer Shipment Entry screen.

Has anyone else experienced this? If so, did you find a resolution? What do I have to change, so that the ship via is correct when a new pack is created? Thanks a bunch for your time!
Nate

Gah! I just noticed there is a ship via at the release level. I bet this is the problem. Chime in if you have any ideas.

1 Like

Some changes to OrderHed will automatically flow down (some request confirmation first).

Some of the lower level order info (on releases or details), is allowed to be null. And when it is, it is assumed to use the value from next higher level. This might be your issue.

For example:

Head.ShipVia = 001
Detail_1.ShipVia = <null>
Detail_1.Rel_1.ShipVia = <null>
Detail_2.ShipVia = 002
Detail_2.Rel_1.ShipVia = <null>

I’m thinking that Line1, Rel1 uses ShipVia 001, while Line2, Rel1 would use 002

Updating Head.ShipVia to 003, would only cause Line1, Rel1 to use 003. Line2, Rel1 would still use 002

edit

I should have used NeedBy date, as I know that one follows my example better.

2 Likes

Yes, I am sure that is it. I am updating all the releases and that seems to be fixing the packing slip issue.