I noticed something interesting when I changed a Ship To search field to only show Active (Inactive = False) ShipTos. Even if I mark a customer Inactive, it still shows as Active. I then tried to do a PreProcessing Directive off of Customer Update that has a condition to check if Inactive is True, if so, Fill the ds.ShipTo table with the data from the Customer table, because ds.ShipTo passes as empty on a regular Customer update. I passed ds.Customer.CustNum as ds.ShipTo.CustNum, Company to Company, Inactive to Inactive, and left ShipToNum as expression “” because the BAQ shows the ShipToNum as blank for the Customer ShipTo but I get a 'Duplicate Ship To ID or invalid Characters in Ship To ID" error. Any thoughts on this?
Ideal turn out would be: If I mark a Customer as Inactive it would also mark that Customer as inactive in the ShipTo table. Below is a screenshot of the BAQ that returns the Customer and both of its ShipTos. The Customer is Inactive but its ShipTo is active, and I can’t find a way to inactivate it.
It sounds like this is getting interpreted as adding a new ShipTo … but the default ShipTo (ShipToNum = "") already exists.
You might have to use the ShipTo BO service to get all the ShipTos for this Customer and update them to Inactive … and you might have to do this in a Function if the Customer and ShipTo BOs don’t play nice together
I do not know what the Inactive flag does on the Customer. It’s new and have not played around with it. Before that flag, it was controlled with the “Valid” fields. Make the Customer NOT a Valid Ship To and see what happens.
Interesting. If you notice in your screen shot, the NULL Ship To is already Inactive. My guess is that is because that Ship To is controlled on the main Customer screen and you marked it Inactive.
I think I already know the answer, but will ask anyway. Are either of the ones that are active Alternate Ship Tos on the Customer or Alternate Ship Tos on another Customer?
Yes this is true. Where Inactive is Checked, that means it is Inactive. The screenshot is showing the Customer is Active in the ShipTo table, and the Customer’s ShipTos are Inactive in the ShipTo table
So, the Customer is Inactive, but the Ship To is not. That is odd. I would think that setting the Customer as Inactive would make the Ship To inactive. I wonder if it is a sequence thing? If you make the Customer active again and then inactive, what happens?
Clarification, setting the Valid fields means they cannot be selected on new transactions (SO, Invoice, etc).
That no-name ShipTo is just the first ShipTo - created using the Customer info when the Customer is created, right? - it seems like you’re treating it differently from the other ones
You can actually change the address on the NULL ship to by changing the address on the main customer page. Technically, it is different than the others as you cannot edit it on the Ship To page.
Yes that is true, but it still shows up in Miscellaneous shipment and that’s where I am trying to prevent people from shipping to Inactive ShipTos.
Yeah I found that when I edit the Customer it passes a dataset for ds.ShipTo. It doesn’t change the inactive status though. Might just require me to hit my head on it until something shakes out. I have tried populating the dsShipTo but it doesn’t like the ShipToNum being missing.
Yeah, I just tested and could not get it to be inactive. I would put in a ticket and have them tell you how to make it inactive. My guess is that they do not know either.
I did put in an Idea to make the initial ship to a “real” ship to, but I would not hold your breath.
