Key Concepts - SAP Business Workflow

download Key Concepts - SAP Business Workflow

of 17

  • date post

    12-Jan-2016
  • Category

    Documents

  • view

    33
  • download

    5

Embed Size (px)

description

SAP Business Workflow - for novice consultants

Transcript of Key Concepts - SAP Business Workflow

  • Generated by Jive on 2015-08-17+02:001

    SAP Business Workflow: Workflow Recipe forPassionate Starters - Part I (Spice up!!)Posted by Aspire WF May 18, 2012Dear Reader,

    This is PART I of 4 part blog series drafted keeping passionate Workflow beginners in mind to give a betterpicture& right start about SAP Business Workflows.

    What is Workflow?Workflow is an automation tool wherein we can map the existing business process and automate it end to end.

    Benefits: User initiating the process need not bother about next level approvers involved in the process.

    Workflow will take

    care of finding the right approver and sending the workitem/Mail for his action/information Deadline monitoring is a workflow feature which helps to attach a timeline for approver to take action.

    Cases where

    no action is taken after deadline expiry can be handled by escalating the workitem superior or notifysomeone that deadline has expired. This aids for better & faster business progress

    Workflow ensures that the right work is brought in the right sequence at the right time to the rightpeople

    SAP Business Workflow can also be used to respond to errors and exceptions - it can start whenpredefined events

    occur(SWUY Tcode)

    Automatic Workflow Customizing:

    Tcode: SWU3

    Purpose: Before jumpstarting with Workflow development we need to ensure that workflow customizingsettings are inplace. These settings are prerequisite for proper triggering & execution of workflow.

    Fig: SWU3 Tcode

  • SAP Business Workflow: Workflow Recipe for Passionate Starters - Part I (Spice up!!)

    Generated by Jive on 2015-08-17+02:002

    Mostly this customizing activity is done by Basis team. Reason being that SAP user id used for this activityshould have SAP_ALL & SAP_NEW authorization.

    Fig: Maintain Runtime Environment

  • SAP Business Workflow: Workflow Recipe for Passionate Starters - Part I (Spice up!!)

    Generated by Jive on 2015-08-17+02:003

    Configure RFC Destination:The workflow runtime system always executes its tRFC (transactional RFC) calls on the logical destinationWORKFLOW_LOCAL_xxx (xxx stands for the three-digit number of the client). The workflow runtime systemonly operates within one client. The naming for the logical destination guarantees that these names are uniqueacross the system. Executing this activity will create the logical RFC destination WORKFLOW_LOCAL_xxx ifit does not yet exist. The user WF-BATCH is assigned to this destination.

    WF-BATCH:

    WF-BATCH is a background system user which should have SAP_ALL authorization. All background activitiesrelated to workflow are executed using this user id. Perform automatic customizing will create this user id if itdoes not exist in system.

    Fig: Maintain Workflow System Administrator

  • SAP Business Workflow: Workflow Recipe for Passionate Starters - Part I (Spice up!!)

    Generated by Jive on 2015-08-17+02:004

    We can maintain Workflow admin either as a Role/Org Unit/ Job/Position/Workcenter/User as seen above.Whoever is maintained as WF Admin will get a notification mail in their business workplace (SBWP Tcode)whenever a workflow runs into an error. Based on this notification mail relevant troubleshooting can be done.An example error notification mail sent to WF Admin will look as below,

  • SAP Business Workflow: Workflow Recipe for Passionate Starters - Part I (Spice up!!)

    Generated by Jive on 2015-08-17+02:005

    From above mail we can understand that for workflow WS92000001 triggering event TRIGGERWFof business object ZBUS2012 is not maintained. Troubleshooting for this case will be to enable theLinkage Activated checkbox in SWE2 Tcode. This checkbox enabling means that workflow is correctlylinked to the event & will look as below,

    Fig: Event Linkage activation in SWE2 Tcode

  • SAP Business Workflow: Workflow Recipe for Passionate Starters - Part I (Spice up!!)

    Generated by Jive on 2015-08-17+02:006

    Maintain Active Plan Version:

    Only one of the plan versions created in the system can be active. This plan version (with its contents) is seen by the workflow system as the only valid plan version. 01 is set as the active plan version.

    Classify Decision Task as General:

    TS00008267 Standard SAP Task for User Decision step in workflow. This task has to be made as General task since it does not have any possible agents as standard.

    Note: While maintaining agents for tasks in workflow either we need to make it as General Task or assign possible agents for the task. General Task means that all users in the SAP System are allowed as possible agents of these tasks. The agent restriction must be performed by selecting Responsible Agents in the step definition.

  • SAP Business Workflow: Workflow Recipe for Passionate Starters - Part I (Spice up!!)

    Generated by Jive on 2015-08-17+02:007

    Document Generation/Form Integration:

    SAP Tasks (TS70008298, TS71007944, TS71007945, TS71007946 and TS71007954) are used for Document from Template step & Tasks (TS70008112, TS70008113, TS70008114 and TS70008115) are used for Form step in workflow. These tasks are made as General Task.

    Maintain Time Units:

    Units of measurement and time that are used by the SAP System can be maintained here.

    Schedule Background Job for Missed Deadlines:

    Background Job SWWDHEX is executed regularly as per the time interval maintained in this activity to check whether new deadlines have been missed since the last time it ran.

    Schedule Background Job for Work Items with Errors

    There are 3 possible error types in Workflow namely Temporary error, Application error and System error.

    Temporary Error: Error that occurs when certain system resources are not available. For e.g. Personnel no to be processed by approver is already being processed by another user.

    Application Error: Error that occurs when an error exists in the called application. For e.g. There is no authorization to edit the object.

    System Error: Error that occurs if there are inconsistencies between the business object type definition and the method call. For e.g. Mandatory method parameters for the method call have not been set.

    Background Job SWWERRE is executed regularly as per time interval maintained in this activity to,

    Notify workflow system administrator in the event of application errors and system errors Restart background workitems with temporary errors

    Schedule Background Job for Condition Evaluation:

  • SAP Business Workflow: Workflow Recipe for Passionate Starters - Part I (Spice up!!)

    Generated by Jive on 2015-08-17+02:008

    Conditions for work item start and work item end is checked via a background job. Background job SWWCOND is scheduled with the standard parameters in this activity.

    Schedule Background Job for Event Queue:

    Events used to trigger workflow are managed via Event queues. The background job for the event queue is scheduled with the standard parameters in this activity.

    Schedule background job for clearing report:

    Background job SWWCLEAR is used to deletes all job logs of the following background job:

    SWWCOND Work item rule monitoring SWWDHEX Work item deadline monitoring SWWERRE Work item error monitoring

    After scheduling, the background is executed once a day at 00:00 hours.

    Maintain Prefix Numbers:

    An example WF template id will look as WS92100001. WS is the prefix which refers to Workflow template id. Remaining 8 digits are made up of 2 parts. First 3 digits should be maintained manually in this activity. Remaining 5 digits are generated automatically by SAP which is a running no. We can define one prefix number per system (DEV/QAS/PRD) and client (100/200 etc...).

    Check Number Ranges:

    This check routine determines whether there is a number range for workflow tasks and customer tasks. If the status of this check has the status error, we can correct the error as follows:

    Use the report RSCLTCOP to copy all the content of the T77* tables from the client 000 into the

    relevant client. Carry out the Customizing for personnel planning and workflow again.

    Check Entries from HR Control Tables:

    This check routine determines whether the Organizational Management control tables are complete which is necessary for the workflow system to be functional. Report RHTTCP77 is executed for the same. If there are errors in the output of report RHTTCP77 regarding the transport objects PDST or PDWS, it means that the relevant entries are not maintained in table SOBJ. Report RHSOBJCH can be used to rectify these errors. Note that with these errors the workflow is executable in the current system, but crucial information is not transported in the event of transports into other

  • SAP Business Workflow: Workflow Recipe for Passionate Starters - Part I (Spice up!!)

    Generated by Jive on 2015-08-17+02:009

    systems.

    Maintain Additional Settings and Services:

    Maintain Web Server:

    If we want to execute workflows that use WebFlow functions (separate step type Web Activity is available in workflow), we have to define a Web Server for the SAP System. This step has to be maintained manually and cannot be executed automatically using Perform automatic customiz