srm workflow

8/12/2019 Srm Workflow

http://slidepdf.com/reader/full/srm-workflow 1/39



Lack of transparency

Long lead times

Lack of deadline monitoring

High costs



1. Triggering event2. Terminating event



There are three types of agents : Possible agent

Responsible agent

Excluded agent



|

Tasks

Single step

Multistep

Standard Task(TS)

Customer Task(T)

Workflow Template(WS)

Workflow Task(WF)

Tasks are used to describe a business process



|

Customer Task (Type T) Standard Task (Type TS)

Workflow Task (Type WF) Workflow Template (Type WS)

Created by customer Created by SAP and customer

With validity period Without validity period

Client-dependent Client-independent

Must be linked to its possible Must be linked to its possible

agents when it is defined agents when it is defined



|



Transaction: SWDDMenu Path:Tools Business Workflow Development Definition tools Workflow Builder



Business activities

Internal process control



Activity Can be a single step task with basic business functionality Can be a multi-step task, which reference to a workflow definition

User Decision

This provides an opportunity for user interaction with the system. The response to this decides the selection of the subsequent step.

Document from template PA document is created from a document template using variables in

the text that are filled during program execution.

Web Activity Selected container elements are posted using http protocol in XML or

SOAP message

Sub workflow An activity which refers to a workflow rather than a task

|



Condition Branch on the basis of control information from the runtime dependent

context of the workflow. An attribute of this object can also be accessed for condition evaluation Condition evaluation can be done by

Field comparison e.g constants , object attribute, system fields

Multiple condition In contrast to condition, multiple condition makes it possible for the

workflow definition to branch in more than two branches.

For evaluation of the multiple condition, the value of the basis ofcomparison is checked at runtime against the comparison values andbranched accordingly.

|



WHILE Loop Steps are processed repeatedly until the conditions contained in the

WHILE step no longer apply.

Until Loop Steps are processed repeatedly until the condition contained in the UNTIL

step is true.

Fork Used for parallel processing branches.

Only a part of the parallel processing branches actually has to run tocontinue the workflow.

Dynamic parallel processing is also possible

|



Event Creator An event is created when this step in the workflow is reached.

Other workflows can be started as a reaction to the event created in this

step. This event must be the triggering event of the relevant workflow tasksand/or templates.

WAIT for event Used to stop the whole execution of the workflow until the event is created

in the system. Used to wait for events for parallel processing

|



Containers store information and allow the exchangeof that information among the different componentsof a workflow process.

The information is stored as a data element andprocessed at runtime through binding



Bindings administer the flow from one container toanother. Bindings are defined at time ofimplementation and are used at runtime.



|

How workflow gets executed



Workflows provide easy and flexible implementationof approval processes.

Approval processes typically run on several processlevels.

Throughout these process levels, a document canrequire different kinds of checks and can involveagents with different roles



Shopping Cart Purchase Order

Goods Receipt

Service Confirmation

RFx / Bid Invitation

RFx Response / Bid

Auction

Contract Project (Category Management)

Invoice



You define the process schema at design time,specifying all possible process levels a document has topass through before it can be released.

For each business object, one or more process schemascan be defined.

If there is more than one process schema for onebusiness object, the system chooses the appropriate

one using the rules defined in the Business RuleFramework (BRF)



With the help of the BRF, the system determines whether or not a specific process level needs to becarried out. At design time, BRF events are definedand business rules are assigned to them.

The process level evaluation runs in loop cycles and isrepeated each time a process level is finished, providedthat no level restart has been requested.



The BRF is an event-controlled runtime environmentin which the system processes certain rules.

Example : Possible expression (“Address is incomplete“):

(street = initial) OR (postal code = initial), in other words, ifone of the two fields is initial, the value of the expression isTRUE.

● Possible actions ('Complete Address'):

The system displays a message that the address is incomplete



The Business Rule Framework contains the followingcentral objects:

Application Class

Implementing class

Event Context

Expression

Action

Rule

Rule Set



The system determines the agents responsible forcompleting or approving purchasing documents.Depending on your Customizing settings, more thanone person can be responsible for the items in one

document . Agent determination is carried out using Business

Add-In (BAdI) Define Agents (/SAPSRM/BD_WF_RESP_RESOLVER), which youcan use to make your own process level-specificimplementations.



There are four decision types: Decision for entire document

Item-based decision for entire document

Overall decision for partial document

Item-based decision for partial document

srm workflow

Documents