Professional Documents
Culture Documents
SAP ABAP Workflows Day 1
SAP ABAP Workflows Day 1
Agenda
▪ Day – 1 :
– What is workflow?
– Business Object
– Data flow
▪ Day – 2 :
– Workflow Builder
– WF Template, Task, Agents, Rules, deadlines, program exits
▪ Day – 3 :
– Workflow example
– Workflow Trouble shooting
– Important Transactions
Introduction
▪ Workflow ensures that the right work is sent to the right person at the
right time in the right sequence with the right information
What?
What question refers to each activity to be executed – it could be a task, a user
decision, email notification or document generation activity? A task might
execute a transaction, a report, a function module, BAPI or a method called
within the program code. A task is used to define an activity that can be
executed within a workflow definition or independently as a single step.
▪ When?
Events tell the workflow an activity has happened so that the workflow can
react to it. Event is the change in state of a business object instance. Events
are used when a business application may need to tell the workflow engine to
start a business process, or when an activity is finished, or when that an activity
that was started is no longer required.
▪ In what order?
A Workflow definition describes the business process to be mapped and its
order. A Workflow definition consists of individual, sequential steps for a
business process and is maintained via workflow builder. The workflow
definition is like a flowchart that controls the order in which the individual steps
are executed and any temporary data needed along the way. The workflow
container is used to hold all temporary data. A workflow definition consists of a
triggering event (which starts the workflow) and steps.
▪ Who?
Who refers to the recipients of a work item established by the system at
runtime. The recipients (selected agents) are derived from the intersection of
possible agents and responsible agents barring excluded agents .The recipient
who actually executes the work item is termed as the Actual Agent. To decide
who should receive a work item and execute the task, we generally use
organization plans or roles.
▪ Business Objects
▪ Workflow definition
▪ Tasks
▪ Events
▪ Agents
▪ Workitems
You can derive subtypes from object types. Subtypes inherit all of the
characteristics (attributes), methods and events of the original object type.
You can add characteristics (attributes), methods and events to subtypes. On
the above slide, .Cargo plane. and .Passenger plane. are subtypes of the
object type.
In the interface of the task that is currently being executed (a step in the
workflow which executes methods), the object instance is always addressed
using the _WI_OBJECT_ID variable.
▪ Events: It signifies that action has happened and also signifies the change
in status of document. For example: Purchase Order Created, so Created is
an event. Purchase Requisition approved signifies the change in status of
Purchase order, Approved is Event here.
▪ Triggering Event:
Event which triggers workflow is called Triggering event.
▪ What it is?
Once Business object is decided and it is also ascertain that on which event
workflow should trigger, it is configured for workflow template using
transaction PFTC under “Triggering Event” Tab.
▪ What is binding?
In workflow terms, the word binding represents, assignment between elements of
two different containers. Binding editor is used to define binding between elements
of different containers.
▪ Workflow Container:
– Binding can be defined from Workflow to Event Container.
– Binding can be defined from Workflow to Task Container.
– Binding can be defined from Workflow to Rule Container.
▪ Event Container:
– Binding can be defined from Event container to Workflow Container.
– Binding can be defined from Event container to Task container.
▪ Task Container:
– Binding can be defined from Task to Workflow container.
– Binding can be defined from Task to Rule container.
– Binding can be defined from Task to Method container.
▪ Method Container:
– Binding can be defined from Method to Task container and method container.
▪ Rule Container:
– Binding can be defined from Rule container to Workflow container.