![Deadlines ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
More Related Content
Viewers also liked
Viewers also liked (20)
Similar to 12 01 deadline
Similar to 12 01 deadline (20)
Recently uploaded
Recently uploaded (20)
12 01 deadline
- 7. Modeling Deadline Monitoring User Decision Result 2 Result 1 obsolete latest end reached Set “Deadline reached“ flag Set work item to obsolete Flag set Work item set to obsolete
- 11. SAP Workflow Course PwC Consulting TM refers to the management consulting services businesses of the member firms of the worldwide PricewaterhouseCoopers organisation. 2001 PricewaterhouseCoopers. All rights reserved.
Editor's Notes
- requested start earliest possible time for start processing; implemented by the system requested end requested deadline for completion of processing of a workflow latest start latest deadline for starting processing a workflow latest end latest deadline for completion of processing of a workflow The deadlines are specified with reference to the start of the workflow or work item or an individual expression.
- “ Deadline” is a functionality, which is only available in a workflow. First - System-wide setting During runtime the deadline functionality is triggered by the job “SWWDHEX”. This job can run as periodic job, like once every hour. With transaction SWU3 you can read the help for this job and schedule it. Second - Integrate your task into a workflow. Third - Define the deadline for this step. During runtime the system will start the deadline functionality after the next run of the job “SWWDHEX”
- Standard case (simple deadline) - deadline agent informed If one of the deadlines set is missed, the deadline agent is informed. The monitored work item is not yet completed. The missed deadline does not change the status of the monitored work item. Modeled case: If one of the deadlines set is missed, modeled subsequent actions should be run which render further processing of the monitored work item superfluous. When defining the monitored step, the exception processing obsolete must be selected and any appropriate subsequent steps implemented. The data on deadline setting must be maintained. An outcome description must be entered for the deadline to be monitored. After the “missed deadline event,” a step of the type “process control” must be defined in which the processing of the monitored work item is obsolete. The deadline agent is not notified automatically. The wizard “Model deadline monitoring” helps to include necessary steps.
- ‘Deadline’ is a functionality which is only available in a workflow. First - Integrate your task into a workflow. Second - Define the deadline for this step. Change to the appropriate tab. Change to the included tab “Modeled” Provide the new outcome “TOO LATE!” Change to the tab “Outcome” and Activate the outcome “Processing obsolete”. Third - Integrate your “Escalation Step” into the workflow after the “obsolete” outcome . Hint : You may use the workflow wizard for deadlines to do the second and third activity. This will insert the “obsolete” outcome into your workflow. During runtime the system will start the deadline functionality after the next run of the job “SWWDHEX”. Runtime activities of the modeled deadline scenario: After the deadline has occurred, the work item for your monitored step is terminated! The workflow system will continue after the “obsolete” outcome of the terminated step. Hint - Since only one of those two steps is active during runtime, the work item is never available to the agents of both steps.
- The wizard will help you to create a modeled deadline. The basic idea is as follows: The step to be monitored is terminated by a missed deadline alternative steps should be included