Depiction of a business process flow in Personnel Administration
and Personnel Development
using elements from HCM Processes and Forms
.
A process object groups the ISR and form scenarios with the link in a workflow template. For each process, there is a workflow template that defines the process flow.
Note
The process can be viewed in different ways and can mean the following:
From a business point of view, the process is the basis for implementing a process. Therefore, the business flow should exist as a process description at the start of the implementation.
From an implementation point of view, the process is the technical representation of the business point of view, using Customizing and using elements from HCM Processes and Forms
.
From a user point of view, the process is the user performing an implemented process, for a specific employee and a specific validity date. When performing the process, the system creates a process object. As a result, the system makes the master data changes defined in the process for the employee concerned.
SAP provides a range of sample processes. For more information, see Sample Processes in HCM Processes and Forms.
You use the Process
object to depict a business process flow, using components from HR Administrative Services
. Note that some properties in the process flow cannot be changed during the process; you must first make the settings in Customizing for the following components:
ISR Scenario (for Adobe form types)
Form Scenario
Workflow Template (in the workflow steps)
Start Application
Form Application
For the process itself, the following information is entered in Customizing:
Name of the process
Validity period of the process
Workflow template that is used when starting the process
Form scenario(s) of the process
Note
A process can have only one type of form scenario. It cannot have form scenarios with different form types.
Other Customizing settings include the following:
Grouping processes in process groups.
You can assign process groups to the start applications, and use them to control authorizations. Assigning process groups to start applications enables you to provide various processes for different portal roles (manager, employee, HR Administrator).
Note
Only the HR administrator role is valid for roadmap forms.
Settings for the collision check, parallel run, and restricting the frequency of processes
Options for withdrawing processes if errors occur
Figure 1.1: Structure of a Process
Figure 1.1 shows the elements that structure a process, and which process-specific settings are necessary in Customizing.
ISR scenario
For more information about the functions of the ISR scenario, see ISR scenario.
Form scenario
When using several forms within a process, the data transfer from form to form can be determined using Customizing. For more information about the functions of the form scenario, see form scenario.
Workflow template
In the workflow template, you model the workflow steps for which you configure the specific workflow tasks and rules for determining agents, and to which you assign appropriate form scenarios.
Start application
In the process-specific Customizing of the start application, you determine which users can start a process and which start application (for the employee, manager, or HR Administrator roles) is available to a process at the start.
Digital Personnel File (DPF)
In the process-specific Customizing for the transfer to the DPF, you determine if the forms and attachments created in a process should be sent to the DPF. When using multiple forms or attachment types, a partial transfer is also possible.
Note
The Digital Personnel File (DPF) is not yet supported for the roadmap form. Therefore, a DPF will not be created when a process using this form type is completed.
You make the settings for the different elements and functions in Customizing for HR Administrative Services
under and under .
For more information about Design Time, see Design Time for Processes and Forms.
The following table lists the elements of a process based on an example.
The information for the following example corresponds to the provided Transfer
sample process.
Elements of the Transfer
sample process
Element | Example (Name and ID) |
---|---|
Process | Transfer (ORG_CHANGE) |
ISR Scenario | Transfer (SOC1) |
Form Scenario | Transfer (SOC1) |
Workflow Template | Transfer (WS17900427) |