General Workflow for Documents
Purpose
You can use this workflow scenario to support Employee Self-Service (ESS) approval processes that are processed in the Time Management document database.
You can currently use the workflow for the following applications:
Implementation Considerations
· The scenario depicts processing of Leave Requests in the standard system. You can use it as a model for processing Clock-In/Out Corrections.
· This section describes the processing steps specific to the workflow. For a general description of the process of creating leave requests and clock-in/out corrections, see the related documentation.
· Due to the special technical structure of the document database, you may be able to use the document processing processes and send the information to those involved in the process without needing a workflow.
For more information, see Processing Leave Requests.
Process Flow
...
1. When an employee submits a new leave request, the system starts a workflow, under the LeaveRequest Web Dynpro application.
2. Once the approver has processed the request, the workflow continues, using the LeaveRequestApprover Web Dynpro application.
3. Once the leave has been successfully posted to the Absences (2001) and Attendances (2002) infotypes, the workflow is completed by the RPTARQPOST report (Leave Requests: Post).
If the infotype records could not be posted, the workflow notifies the administrator of the error. Once the error has been corrected, the report terminates the workflow.
If employees have not processed work items with rejected approvals, you can use the RPTARQSTOPWF report (Leave Requests: Stop Current Workflows) to terminate the workflows.