What to do: |
|
![]() |
As a prerequisite for the following example you must have completed the example Create a Work Request/Work Order! |
![]() |
Since a process is automatically generated from a process template, it is only required to assign a process template to the work request/work order! |
![]() |
It is not possible to assign a process to a work request/work order without a process template! |
![]() |
Click | .
![]() |
Search for the work request EWR-1000. The work request mask opens. |
![]() |
Change to the ![]() |
field and
click
![]() |
Choose an | number from the selection menu.
In the example the ID number is 869 for the process template Order. | |
The process template name will be displayed when clicking the | field or when saving the entries.|
![]() |
To save the entry click |
![]() |
The process template 869 - Order is assigned to the work request EWR-1000 -Purchase Requisition. |
When saving the process template, a process is automatically assigned to the work request. | |
![]() |
Select The mask opens, displaying the process assigned to the work request/work order. ![]() |
from
the context menu to display the process.
![]() |
The process 861 - Order is assigned to the work request EWR-1000 - Purchase Requisition. |
![]() |
When the work request is set to the state 120 | In Approval the assigned process is started. Selecting from the context menu will then open the Process in Execution mask! |
![]() |
When a Work Request/Work Order is created, a process instance is automatically created from the selected process template and started (Process in Definition)! |
![]() |
The process template cannot be changed when being saved! |
![]() |
When the Change Management is active, a process template cannot be assigned to a preliminary but only to a persistent work order! Therefore, a process template that is assigned to a Work Request is not automatically copied to the preliminary Work Order! This is also the case when the Work Request is released and the preliminary Work Order becomes a persistent one! |