BPF Process Objects

A ProProcess process consists of the following objects.

Graphic	Object	Description

Graphic	Object	Description
	Process	The process is the top object. It is started either automatically due to data changes or manually by a user or an interface. Since every ProProcess process also starts an SAP Business Workflow, the process is first created in the status created and then set to the status ready and then to the status started by the start of the workflow. The end of the process is indicated either by the status completed or the status canceled. If an error occurs during processing that must be corrected by an administrator, the process is stopped and set to the status errored. The process is locked against all changes until an administrator fixes the problem.
	Branches (exclusive Gateway)	Branches can be used to control the path of the process.
	Parallel section	A parallel section can be used to divide the process into several parallel paths that can be driven independently of each other.ge aufgeteilt werden, die unabhängig von einander vorangetrieben werden können.
	Part process	Part processes are used to divide the process into smaller logical units. At the same time, various settings can be made within part processes as to how the activities can be processed and how the work affects the further course of the part process.
	Sub processes	If processes are chained together, then the chained process is shown in the process graphic.
	Activities	Activities are the actual carriers of tasks to be executed. An activity can be assigned to several users, whereby only exactly one person is allowed to process the activity at any time. In an activity 1 - n tasks are defined, which are (under certain circumstances optionally) to be completed. When a user starts working, the activity or SAP work item is automatically reserved and therefore disappears from the inbox of all other possible agents. Depending on the settings, an activity is automatically completed after the tasks have been processed or must be manually acknowledged by the user.
	Tasks	In each activity there is at least one task. Tasks contain the concrete tasks, whereby in the simplest case this is only an instruction that must be manually marked as completed. However, tasks are also possible that execute an action directly in the system fully automatically and can also automatically determine and set the status based on internal checks.

-

Each object has a status at runtime. The status is always managed and set automatically by the system. On the one hand, the status from the associated SAP workflow is synchronized, but also the status between individual objects within their hierarchy. In addition, the processing of activities or tasks leads to automatic status changes that reflect the concrete status of the work progress.

Only the completion of tasks and activities may be required manually, depending on the settings. Special functionalities are available for this purpose.

The status network is basically structured as follows:

Initialization

Icon	Process step	Description

Icon	Process step	Description
	Initialization	Created (All objects, automatic): The object has been created, but it is not yet ready because the corresponding workflow object has not yet been created.
	Initialization	Ready (All objects, automatic): The object is ready, the corresponding workflow object exists.
	Processing	Started (All objects, automatic): Work on the object has been started.
	End	Completed (All objects): The object has been completed regularly. The status is set manually on tasks and activities depending on the settings. The other objects "inherit" the status automatically.
	End	Rejected (Subprocesses, Activities, Tasks): The object was rejected. The status is set manually on tasks depending on the settings.
	Ende	Skipped (activities, tasks, automatic): The object was automatically skipped ahead of time. The status is applied to activities if the parent sub-process is set up to finish before all activities are completed. For (optional) tasks, the status is set when the activity is terminated manually.
	End	Terminated (process, subprocesses, activities, tasks, automatic): Processing of the object has been terminated. The status is normally applied to the process only if a termination has been explicitly modeled and achieved in the process. However, an administrator can "hard" abort a process at any time. This will cause all objects that are still running to be terminated prematurely.
	Error	(Temporary) Faulty (process, activities, automatic): The object has been marked as faulty due to a situation that cannot be resolved. As soon as an object is faulty, the process is always set to faulty as well. The special status temporarily faulty is set if an error has occurred but can be automatically corrected at a later time. This constellation generally occurs when locks prevent data from being changed. A job scheduled in the background checks these objects periodically and attempts to correct the errors. If this is not possible even after several attempts, the process is finally marked as faulty.