Hi Jitendra
I will try an answer based on my experience....
Answers to question 1:
You are right to mention that Workflow Admin and Workflow Developer are two different 'Roles'. It really depends on the organization setup if they want to assign both roles to one guy or if they want two different resources for this . It also depends on how many workflows are there to be monitored and if there are regular ongoing requirements for new developments.
In my view, if there are continuous developments ongoing for workflow and there are many workflows to be monitored, it is better to divide these two roles between two people.
Workflow Developer Roles and Responsibilities:
- Understand requirements
- Suggest best practices
- Develop and Configure workflow related tasks
- Unit test
- Support User testing, enable and handover
- Bug fix and go live support
Workflow Admin Roles and Responsibilities:
- Responsible for the overall health of the workflow system – i.e. that workflows and supporting batch jobs operate with optimal efficiency
- Responsible for the scheduling and execution of standard workflow batch jobs
- Responsibility for Universal Worklist inbox administration and configuration
- Responsibility for Email Notification of Extended Emails' configuration and scheduling
- Responsible for the configuration of the workflow environment (i.e. non-process-specific settings for workflow such as the workflow RFC destination and workflow Event Queue)
- Proactive correction of misdirected and orphaned workflows
- Proactive resolution of workflows in error
- Reactive response to reported workflow issues where Help Desk has been unable to resolve issues
- Responsibility for producing and monitoring agreed process metrics, such as SLAs
Workflow administration activities may be split between:
- A technical administrator - responsible for overall health and troubleshooting of workflows in error
- Business administrators - responsible for redirecting misdirected workflows in their process area
Answer to Question 2
To start developing workflows, you just need SWU3 done. Rest depends on your actual workflow requirement/development
- SWU3 for all workflows
- SWE2 - When your workflows are event based (yes - most of them will be)
- SWEC - When your events are change documents based
- SCOT - email settings if you are sending emails from workflows (outside of the SAP System)
- SMQS/SM59 - you really do not need to do anything here, these are just for monitoring and to check (out of many steps) when something goes wrong
The list can really go on and on - it all depends on the individual workflow requirements, but SWU3 is the mother transaction - this sets the Workflow Environment and without the config there, the workflow will never work.
Regards,
Modak
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.