One of our marketing people noticed that the Single Sale Order Listing report offers Location(s) as a parameter. Assuming this to be based on department, she ran it and was concerned that an order she expected wasn't shown. By leaving that parameter blank, the order shows up - as it is, in fact, in the system. This led her to question why such an order was "in the wrong department in the first place" and that it could cause much consternation down the road.
And, so. Where does the location(s) parameter pull from exactly and where would I change that, assuming it really needs to be changed (as this issue has never come up before in the 3+ years I've been working here)?
Thank you for your assistance in advance, as always, Tessiturians.
BONUS ARTHROPODIC TRIVIA: The housefly hums in the middle-octave key of F.
Based on what it looks like in my local system, I think it's pulling from the location in TX_MACHINE_LOCATION for the machine or host name, depending on how it's set up, where the order was created. The location dropdown choices come from TR_LOCATION.
That's exactly where it is coming from. I was assigning users to departments using the TR_LOCATION table to assist in tracking department ticket sales statistics. But now with T-Stats 2.0 we are using the Solicitor Name parameters under Ticket Orders and Package Orders for this purpose.
Duane