Start of Content Area

Process documentation Process Model Flow  Locate the document in its SAP Library structure

Purpose

A process model is the basis on which a process is executed.

Prerequisites

You have set up a system administrator for the workflow by accessing Customizing for the SAP Web Application Server and choosing Business Management ® SAP Business Workflow ® Maintain Standard Settings. For more information on SAP Business Workflow, see the reference documentation.

You have activated the workflow events triggered automatically by the HR Process Workbench during processing by accessing Customizing for Payroll and choosing Background Processing With HR Process Workbench ® Activate Type Linkages for Workflow Events.

Note

The events in question are JOB_STARTED, JOB_ENDED, JOB_ABORTED, and STEP_ENDED. They control technical processing for a process model. For example, the JOB_STARTED event is triggered automatically when you start a process. The STEP_ENDED event is triggered when a process step is concluded.

These events are not identical to the workflow events that you can use for a wait point or to schedule a process or process step. For more information on these events, see Event.

Process flow

  1. A process model starts with a selection program. The selection program can be started in the background or directly from the HR Process Workbench. It triggers the JOB_STARTED workflow event, starts the process, and transfers process control to a function module, which is otherwise known as the process manager.
  2. The process manager determines the process step that follows the selection program, and starts the accompanying program in the background.
  3. If several sets are processed in a process step, the program processes the steps at the same time. When processing concludes for a set, the program always triggers the JOB_ENDED event. The program does not return control to the process manager until all of the sets have concluded with the JOB_ENDED event.
  4. The process manager triggers the STEP_ENDED event. It checks the status of the process step and determines whether it is followed by other process steps. A container transfers the information from one process step to the next. The contents of the container are always saved so that information on individual steps is not lost.
  5. The process manager starts the next process step with the information from the container and from the results tables of the parent step.
  6. The system keeps repeating steps 3, 4, and 5 until the process reaches a process step without a child step.

Result

The process based on the process model is concluded. An overview of the status of individual process steps is displayed in the HR Process Workbench. Notification is sent to particular persons, depending on the definition of the individual process steps.

End of Content Area