Now this is probably a matter of preference more than anything, but while playing in the OpenSAP class, the big styles they keep working with are the master/detail list vs. the list. The best way to describe the difference is an iOS application (one left is a list pane, on the right are the details) vs. a full on list (full screen table). Now, what I am trying to figure out is if I keep my applications in the same format as I originally designed them. The supervisor transaction is probably the best example.
In the original application, I provide the mass change option to update multiple orders at one time, or run availability on multiple orders, etc… if you build something in a master/detail version, you lose this functionality. On the flip side, it is pretty easy to update orders one at a time. Execution is clearly a master/detail scenario in my mind, but for the supervisor, I’m curious how you might feel? If I were executing this on a computer only, I’d probably go with the list format, because I like the mass change option. But since the goal is to be device agnostic, do I give up on the mass change? I could certainly provide the functionality to reschedule all, run availability on all… but not on selected orders.
My question to all of you… if you were managing the service shop, would you be using mass change of orders very often? Reschedule selected orders? Run material availability on multiple orders?
Love to hear your opinions,
Thanks for reading,
Mike