I am assuming that you are implementing OEM version which comes free with SAP NW. If yes, I will strongly recommend you to invite Redwood or their partner to your site. They typically come down and advice you on how to implement, impart training. They will be best positioned to derive a strategy which ensures the success of the software.
Now coming down to specifics of your question. In any organization whose core operations is not Information Technology, end users should not have access to start, monitor jobs. What they should be able to do is schedule their reports in BW or submit some kind of report in R/3 as background job. Nothing more than that.
1) Note that they do not have visibility for system resources
2) They do not understand trade offs between different jobs when system resources are scare. (For example, in month end situations, you would want the FI jobs to run fast rather than MM jobs running. At the same time not all FI jobs all that crucial than some PP jobs and so on.)
3) Monitoring jobs and scheduling is a IT responsibility, the core responsibility of end users is business. We are actually increasing Cost of operations by moving work from monitoring team to end users.
This applies to any scheduling tool.
To make Redwood implementation more successful, you need to collaborate with Functional, Technical SAP consultants to form Scripts and job chains. Operations team (or Monitoring team) should start their work only after all jobs have been designed and have run successfully for few runs.
Each organization has different problems about batch cycles and the consultants need to study these situations and recommend best strategy to make redwood a success.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.