Many companies have consulted with me on their SAP improvements. What I suggest always is to classify on a high-level - 5 things, before strategizing what and how.
Let me elaborate on how I help companies form a simple strategy to improve their SAP ecosystem, based on the defined categories. There will be some overlap between categories and it's logical.
PROCESSES THAT RUN CORRECTLY
These are processes that are defined and refined nicely and they work fine for your company's purpose. Key questions to ask:
PROCESSES THAT ARE ERROR-PRONE
These are processes that have high degree of errors - users are repeatedly entering incorrect or incomplete data. Key questions:
PROCESSES WHERE CUSTOM REQUIREMENTS ARE KNOWN
These are custom process or report requirements that are too specific to your company needs. Key questions:
PROCESSES YET TO BE DEFINED
Processes that are not yet mapped on SAP. Key questions:
UNKNOWN
These are processes that you don't know you need or have somehow ignored as part of your ecosystem to operate even better. Key questions:
Of course, at high-level, these seem like mamoth challenges to overcome and perhaps not so relevant, since there's no obvious model implementation you can follow for your discrete company rules and procedures. My suggestion is to see how several companies work continuously on strategies driven from these (and more) key questions and build a robust framework that's easy to consume, operate, and change too.
I'll be placing GuiXT in the above context and show how this can be done, in future posts.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 |