SAP Workflow Definitions

Here are the Basic definitions of SAP Business Workflow

SAP Business Workflow

Is a tool for the automization of business processes.

Workflow Builder

Is a tool that is used to define, access and or modify workflow definitions in a graphical format.

workflow template :

- Basic data of the workflow definition. This includes specifications on buffering reporting data,
  on automatic forwarding, and so on.
- The specification of triggering events. If the specified event enters the system, the workflow   

   starts, if the event is actively linked to the workflow.
- Initial values
- Specifications for the interface (workflow and event container)
- A link to the corresponding workflow definition, that is, the specification of the individual workflow steps that are to be executed.

workflow definition

n The workflow definition is created in the Workflow Builder and is displayed graphically in a network.

Biniding :

The binding defines the data exchange between the different containers in a workflow.

Every time you integrate a task into a workflow, you have to make sure that the correct data is transported into the task container when the work item is started and back to the workflow container when the work item is completed.

Task - abbreviation TS:

Refer one method of an object type and represent one step in the business process.

n Tasks are used to describe a business process.  Tasks can be executed one after the other in the business process. Parallel steps can, however, also be defined.

n Tasks are designed as client-independent and time-independent, reusable modules.

n A task refers to a method of an object type.

n A task has to have possible agents referring to the organizational model or all SAP users (general task

n If an asynchronous method call is used for the task, the method does not return confirmation of completion to the calling system.The work item is also not completed.
An asynchronous method has to make the notification of completion known using an event.
This event has to be entered as a 'terminating event' for the task.

n Triggering events are only required if the task is to be started independently of the workflow definition.
Such events can be found in R/3 in error handling of IDOCs, for example.

Workflows - abbreviation WS,

n represent the business process and consist of a sequence of individual tasks and control steps.

n workflow templates are also client-independent and time-independent.

Task groups :

Logically connected tasks are grouped together in task groups. Task groups can have a description text. The use of the task group can therefore be precisely documented.

Task groups are also useful for defining the search range for the Business Workflow Explorer.

Terminating Events

n A terminating event applies to one instance of a task only, that is, to one specific work item. The key of the work item, therefore, has to be given to the terminating event.

n have to assign terminating events to each asynchronous task. The system recognizes by the triggering event that the method call is completed.

n Synchronous tasks need terminating events if it is not guaranteed that the processing on which the work item is based is executed by the workflow system exclusively.