If these people work at a firm like Accenture that just outsources the technical challenge, coding skills become completely unnecessary.
Also, a ton of the industry is built around the risk of something unexpected happening after you push the button (as mentioned below) and distributing blame if the end-result isn't precisely what customers anticipated (the old "Nobody gets fired for buying IBM" adage)
It may seem backwards to people outside of giant organizations, but it is a necessary aspect of modern business (and there are tons of industries that make more money while generating less value for society).
Many times what is needed is to let go of a sensible technical approach and just help the organization go where it is trying to go. It may not make sense technically, but it makes sense to the org, and that sort of matters more. I find my knowledge of good architecture often just makes it more painful to watch the code go through the inevitable logjams, rewrites, and process failures that are a crucial part of an organization “feeling” it’s way through a very complex multi-dimensional domain that includes many considerations that have nothing to do with code.
I think in many ways, people with less technical skills can do that better, to live in the meta space.
My brain keeps getting dragged down into the “why can’t we just do the sensible, minimal, technically correct thing that needs to happen for this problem to go away”. But the answer is “because the org doesn’t see the problem the way you do”.
What good is it if I can solve problems no one else in the organization even recognizes as problems?
And yes SAP is bad but it is also something that will do most stuff you need to do and follow the right laws when you do it.