SAP Workflow - BO

8/15/2019 SAP Workflow - BO

1/58

SAP WORKFLOW


2/58

Course Contents

Workfow Overview Business Object Repository Task Builder Workfow Builder Customizing Workfow Testing

Business Workplace Organizational Plan Workfow dministration


3/58

WORKFLOW OVERVIEW


4/58

Workfow Overview !e"nition #$amples Components

Tools


5/58

Workfow !e"nitionWorkflow is defined as the automation of a business

process, during which documents , information or

tasks are passed from one participant to another foraction, according to a set of procedural rules.

Workflow ensures that the right work is sent to the

right person at the right time in the right sequence

with the right information.


6/58

W%en is Workfowneeded &When a business process is executed repeatedly

When different people are involved in different parts

of the process and co-ordination is required in aspecific sequence

When the users need to be reminded of what theyneed to do

When the duration of the process is critical anddeadlines have to be met


7/58

'ow does it work&When the workflow runs it creates work items which

are like e-mails, buto they have the advantage that they contain the intelligence

needed to execute the relevant task with the correct datawhen the operational user executes them,

o they disappear on their own when they have been executed by someone.

o These work items can be received in the R! businessworkplace, "# $utlook, %otus &otes, or work itemnotifications can be distributed by e-mail.


8/58


9/58

Business in ((

Client / Agent in

SAP

Email to manager

Approval

cycle

SAPManager 1

PR approvalLevel-1

Email sent

Approves

SAP

PR approval

Level-2

Manager 2

Final

approval

System

Automatic POcreation

(backroun!"

in #AP

Emails to Vendor &

Manager with PO

as attachment

Confirmation from

Vendor after receipt

of email

Purc$a%e Enineercreate% PR


10/58

(aterial i!oc .rom t%ird party system

Applicationserer

SAP i!oc

reading

starts

&$eck% '$et$er

material %$oul! be

create!

Emailsent to

third

party

O

)E#

Material gets created in

SAP ia Posting

Email sent to third party

& MM manager

"#rther posting

incl#ding $OM creation

Sending File

%hird Party

System


11/58

Enter otification of

A'sence (Employee)

Approed(*ead of !ept)

+pdate Personnel !ata

,ithdraw otification

-eise otification of

A'sence (Employee)

-es#'mit for approal

(Employee)

!ecision regarding f#rther

processing (Employee)

Yes No

YesNo

otification of

A'sence


12/58

Workflow definition consists '

#tep ()rontend*

Task +usiness $bect "ethod (+ackend*

,or.flow !efinition Components

,or.flow

Step%as. $O

Method

Workfow !e"nition Components


13/58

What ' What activity need to be performed n what $rder ' $rder in which work should flow.

With what obect ' &eed to find suitable +$Who does ' erson who can execute the task

When ' workflow should be triggered

/ 0uestions for any +usiness/ 0uestions .or any Business Process


14/58

Workflow provides a number of tools for defining and

analy1ing workflows as well as for monitoring

operation. They are2

Workflow +uilder Task +uilder +usiness $bect +uilder

+usiness Workplace

,or.flow Tools Workfow Tools


15/58

Workflow +uilder t is for displaying and making changes to workflows. We can make

#mall extensions directly to the original workflows supplied by #3,

such as carrying out your own agent assignments or changing deadline

monitoring.

Task +uilder

Task is an interface between workflow step and +$ method. Task can

be executed in )oreground (3gent assignment* or in +ackground

(Workflow #ystem*.

+usiness $bect +uilder +usiness $bects are used to make the functions of the R! #ystems

available to a workflow.



16/58

+usiness WorkplaceThis is the area where the end user receives information about the

activities they are to carry out. This provides them with a central

overview of all the activities that they are authori1ed to carry out.

They can commence the activities from here.



17/58

-mportant T1 Codes

2W+!3 ll Workfow related

2W!!3 Workfow Builder

2BWP3 Business Workplace2W453 6eri.y Workfow customizing

2WO73 Business Object Builder

2W-7 3 Work -tem !isplay2W4!3 Consistency C%eck o. Workfow


18/58

-mportant Tables

2WWW-'#! 3 'eader Table

2WWW-8#9T 3 Work -tem gents

2WW+O8'-2T 3 'istory o. a work item


19/58

*+I#IE## O*,E&REPO#IOR)


20/58

Business Object Repository

$bect Type

4ey )ields

3ttributes"ethods

5xceptions

5vents6elegation

5xercise


21/58

Object Type )2WO7*

t7s a data with which you want to work in a

workflow (e.g. urchase $rder*.


22/58

Object Type )2WO7*


23/58

mplementation & -elease of the O'0ect type-mplementation and Release o. Object

Type


24/58

Release 2tatus

(odeled 3 9ot accessible at runtime#$ecution not possible*

-mplemented3 Only .or tests or -nternal

use : possibly unstable Released 3 Released .or use Obsolete 3 ;unctionality %as been

replaced

Release 2tatus


25/58


26/58

ttributes

6atabase 3ttribute6atabase attributes are read from

the associated application table and

buffered in the obect. #ource code

is generated beforehand by the+usiness $bect +uilder for this

purpose.


27/58

!atabase ttributes

#ource code is generated in the implementation program to read the datefrom the application table.

f the attribute is derived from a field in a table whose key fields do notcorrespond to or only correspond partly to the key fields of the obecttype, the extensions in the implementation program are not sufficient

The source code between 85T9T3+%59R$5RT= and5&69R$5RT= is generated entirely from the definition data. Theform select9table9>table name? is also generated automatically for the

actual database access. The macro 5@T9$+;5:T9&$T9)$A&6 returns the exception

B$bect not foundB. This exception corresponds to the TCDD message$%EFG

!atabase ttribute


28/58

6irtual ttribute

The data declaration is generated from the definition dataand is used as a runtime buffer.

The implementation between 85T9R$5RT= and5&69R$5RT= must be created manually, since there isno other definition information. The obect reference to bereturned, in particular, must be created explicitly via themacro #W:9:R53T59$+;5:T.

+oth the +usiness $bect +uilder runtime buffer Bobect-salesgroupB and the associated container elementB#ales8roupB must be completed for data transfer.

6irtual ttribute


29/58

ttribute=s implementation


30/58

-mplementation Program

in BOR


31/58

(et%ods

With a method you define a function with which youcan edit, create, search for or delete an obect of thisobect type.

=ou cannot edit a method in the list of methodsdisplayed, which was inherited from the #uper type oran interface. +ut you can redefine an inherited method by selecting it and choosing . =ou can then edit the

method.

(et%ods


32/58

Creating a methodCreating a (et%od


33/58

2ync%ronous (et%od

Results returned directly to calling program

Return of exceptions possible

3ll the methods that do not write their changes to the

database via the update task ndicates that the activity is complete when the method

execution is finished


34/58

The implementation between

+58&9"5TH$6 and

5&69"5TH$6 is generated from

the definition data. The macro

#W:9R5)R5#H9$+;5:T mustalso be called after the application

functionality for synchronous

methods that can change obect

attributes, in order to delete the

obect buffer.

2ync%ronous (et%od


35/58

sync%ronous (et%odResult can only be returned via an event$nly restricted exceptions possible

3synchronous methods are always necessary if the

encapsulated application functionality uses updatingndicates that the activity is not complete until a

terminating event is received


36/58

Import

Parameter%

E.port

Parameter%

Re%ult% E.ception%

#/nc$ronou%

0et$o!

A%/nc$ronou%

0et$o!

Communication .or

(et%ods


37/58

ParametersParameters


38/58

Results

Results are only relevant .or

sync%ronous met%ods

-t can be linked to possible

outcomes in workfow

Results


39/58

Eceptions#$ceptions


40/58

&o source code is generated for

triggering an exception.

5very exception must correspond

to a TCDD message.

Ap to four parameters, which

correspond to the four parametersof the TCDD message, can be

transferred with the

5@T9R5TAR& macro.

The triggering of exceptions is

the same for all error types.

Eceptions#$ceptions


41/58

Temporary Error

5rror occurs when certainsystem resources are notavailable

Application Error

5rror exists in the calledapplication. (5xample2 There isno authori1ation to edit the

obect* System Error

nconsistencies exist between theobect type definition and themethod call. (5xample2"andatory method parametersfor the method call have not beenset*

Eceptions#$ceptions


42/58

Eents

An occ#rrence of a change of a state of o'0ect Eg

P- created3 PO released

#vents


43/58

+ist o. Business Objects

2WO5


44/58

(acro=s to be used

$nly macros from >cntnDC? may be used to manipulate obectsand containers.

6ata 6eclaration2I 6ata2 >$b9ref? T=5 #W:9$+;5:T

:reate a $bectI #W:9:R53T59$+;5:T >ob9ref? >ob9type? >ob9key?

Reference an $bectI #W:985T9$+;5:T9T=5 >ob9ref? >ob9type?

I #W:985T9$+;5:T945= >ob9ref? >ob9key?

Refresh $bectI #W:9R5)R5#H9$+;5:T >ob9ref?

(acro=s to be used


45/58

(acro=s to be used

3ttribute access2 #W:985T9JT3+%59KR$5RT= >$b9ref? >attribute? >value?

:all a "ethod #W:9:3%%9"5TH$6 >ob9ref? >method? >container?

6efine :ontainer #W:9:$&3T&5R >cont? #W:9:R53T59:$&T3&5R >cont?

Reading and setting elements #W:985T#5T 5%5"5&T >cont? >element? >value?


46/58

!elegation Super Type The obect type from which attributes and methods are inherited

is called the #uper type

Sub type

The #ubtype inherits components from the super type. Has the

same 4ey field as its super type. ( Has extended functionality*

Delegation

6elegate the #uper type to subtype. 6efine subtype anddelegation. 6elegation BcoversB the original super type.

=ou :ontinue to use the super type

!elegation


47/58

TASK BUILDER


48/58

Task Builder2tandard Task

Triggering #vent Terminating #vent

gent ssignment


49/58

2tandard Task2ingle step task

Represents an activity

ssociated wit% object type > it=s one o.met%ods

Triggering event is associated

T%ere can be any number o. standard tasksin a

template


50/58

2tandard Task !e"nition 2tandard task can %ave .ollowing attributes3 !ialog task ? Background 2ync%ronous ?sync%ronous

Con"rm end o. processing3 pop up bo$ will appear a.tere$ecution o. work item !ialog attribute is de"ned by t%e attac%ed met%od

property Result Type .or t%e met%od?#$ception o. .unction modules

can become output .or t%e task

sync%ronous task re@uires terminating events Background task are accomplis%ed by W;,BTC'

)2ystem*


51/58

Task Creation


52/58

ssigning Object Type

and (et%od


53/58

Triggering #vent


54/58

Terminating #vent .or

sync%ronous Task


55/58

gent ssignment


56/58

gent ssignment


57/58

(aintain gentgent can be maintained in .ollowing ways 4ser

Aob

Position

Rule

#$pression


58/58

Organization PlanOrganization PlanPosition

gent assignment

Documents

SAP Workflow - BO