SAP AG 1

SAP AG 2007
SRM 6.0
BRF Wor k f l ow Conc ept
SAP AG 2
SAP AG 2007
Obj ec t i ves
Target Audience:
SAP SRM consultants
Partner SRM consultants
Prerequisites Knowledge:
SRM implementation experiences
SRM 6.0 overview
Objectives:
Explain Workflow changes in SRM 6.0
Configure new SRM 6.0 Workflow
SAP AG 3
SAP AG 2007
BRF Overview
Workflow Configuration
Transition from old Workflow to BRF
BRF Enhancements
New WFL features in SP01
SAP AG 4
SAP AG 2007
I nt r oduc t i on
The Business Rule Framework (BRF) is a framework. By way of
their application class, applications must be registered in the BRF
to be able to use the services of the BRF.
The BRF is a cross-line tool
The BRF comprises a runtime environment and a maintenance
environment.
The basic idea of the BRF is to offer the possibility of freely
configurable rules being processed at certain business events,
known as BRF events (or simply events).
The BRF is available as of WebAS 6.20 Ext. Set 2
The BRF is an event-controlled runtime environment for processing rules. You can assign any number of
rules to each event, whereby a rule normally consists of a Boolean expression and an action. If the
expression returns the value TRUE, the action is executed.
The BRF also contains a maintenance environment in which you can edit and configure BRF objects. You
can configure both technically oriented as well as business process oriented rules. This means that you
configure the rules in the maintenance environment, and the rules are processed in the runtime
environment.
The BRF is object-oriented and therefore offers appropriate enhancement mechanisms that are
modification-free and upgrade-independent.
"BRF event" is the term for a calling point from within the application to the BRF. This linkage is fixed,
and the call is synchronous. For this reason, a BRF event should not be viewed like ABAP-OO or the
"Observer Pattern" where an event only represents a loose linkage between two software components.
SAP AG 5
SAP AG 2007
SRM Wor k f l ow Fr amew or k
UI
SRM 5.0 SRM 6.0
UI
Business Object Layer
PDO Layer
PD Layer PD Layer
New SRM Workflow Framework
Workflow Basis Engine Workflow Basis Engine
Old SRM Workflow Framework
BAdI
*
One type
of template
Multiple
types
of templates
*) UI means in this context not the ITS UI, but the UI layer to a business object. In SRM 5.0 the SC has a function
group BBP_SC_UI_ITS and BBP_SC_APP.
PDO Layer = Procurement Document Objects Layer
Targets of the new Workflow Framework:
Improve maintainability - Remove complexity of coding (more than 100 interfaces, complex BAdI
Interface, no API)
Review the workflow requirements
- Create a map of required functionality
- Keep and improve functionality, but discontinue features with little business gain but high code
complexity
Introduce a new, easy implementation concept at customer side
Improve architecture for future requirements - Scalability
Integrated with new SRM Architecture
The new PDO (Procurement Document Objects) layer comprises the already existing PD layer as well as
the business logic which was previously distributed among the user interface and application level. The
business logic contained in the PDO layer is provided by means of services offered by business objects
(BO). Each business object is related to one of the procurement documents of the existing PD layer. The
application layer coding is split up between PDO and the presentation layer. Although the new architecture
concept is strong enough to cover all existing screens (based on ITS, BSP and Dynpro) it has been decided
to leave the old UI and the existing PD layer intact. PDO achieves the following goals:
- A clear separation of UI and business logic.
- The business logic is concentrated in one place.
- A step towards service-oriented architecture.
- A meta-data driven UI (regarding field and action control).
- An API (at the business logic layer) that is suitable to support large objects at the UI.
SAP AG 6
SAP AG 2007
Loc at i on of Busi ness Logi c
SRM 5.0 SRM 6.0
Previously SRM had been divided into a user interface, application and procurement document (PD) layer.
Although each layer has a specific purpose, each layer including the user interface layer contains business
logic. This leads to inconsistent implementations of those portions of the business logic that need to be re-
implemented for different presentation layers (like Excel up-/download, GUI or ESA). Furthermore, it is
expected that those portions would even need to grow in the future.
One of the fundamental concepts of the new architecture is that all business functionality shall be
concentrated in one layer and that this layer should provide all additional information (like which field can
be changed or which action can be called) necessary to control the behavior of the GUI or other
presentation layers. Throughout this document we refer to that kind of additional information as meta-data.
Meta-data depends mostly on document states, processing mode and customizing.
SAP AG 7
SAP AG 2007
Easier to configure
Reduced complexity of implementation options
through standardization
Complete new user interface and Combined
document completion (purchaser and
specialists) and financial approval (manager)
processes
Out-of-the-box, multilevel approval (without
having to code) capabilities
Introduction of new business rule framework
(BRF)
Offline approval via Duet
Dont need in depth workflow knowledge
Enhanc ement s and Busi ness Benef i t s
Enhanc ement s i n mySAP SRM 6.0
Standardized
approval processes
to reduce complexity
Reduced total cost of
ownership
Faster
implementation
cycles
Compliance with
regulations
(Sarbanes-Oxley Act,
accessibility, and
audit requirements)
Busi ness Benef i t s
SAP AG 8
SAP AG 2007
Bac k & For t h Func t i on, I nqui r y and Rec al l
New workflow with combined specialist completion and financial approval
processes. Completion process must precede approval process.
Approver has Inquire and Edit option in Completion Process.
When Requester need to change the SC, you can recall by clicking the
Change/Edit button or access the SC directly (via the POWL) and edit it.
Approval
Process
Completion
Process
Approve
Reject
Approve
Reject
Inquire
Edit
Change/Recall
Requester Approver
Accept/Adjust
Accept/Adjust
S
p
e
c
i
a
l
i
s
t
F
i
n
a
n
c
i
a
l
Change/Recall
Accept/Adjust
SAP AG 9
SAP AG 2007
Appr oval Pr evi ew and Rec al l Popup
Approval Preview
Recall Popup
when you edit a
document which is
in approval
SAP AG 10
SAP AG 2007
Por t al I nbox and New UI
SAP AG 11
SAP AG 2007
Gener al Gui del i ne
New customer SRM60
Define Process Level table with BRF
Upgrade customer who use SAP standard workflow
Migration program is available
Upgrade customer who developed custom workflow template
Manually migrate it to Process Level table and BRF
Upgrade customer who developed N-step BADI
Manually migrate it to Process Level table and BRF
Or
BADI Adapter is planned in later SP
SAP AG 12
SAP AG 2007
Ver y Si mpl e Over vi ew
Configuration Data
BRF Objects
Application
BRF Maintenance
Rule Creation
Events, Rules,
Expressions,
Actions, Rulesets
Maintenance Screens
Application Data
BRF RunTime
Rule Evaluation
Application Context
Information
SAP AG 13
SAP AG 2007
BRF Obj ec t s
The main objects of the BRF are:
Event
evaluate and change data
hundreds of predefined events are available
Expression
return results
can be nested
Rule (not used in SRM)
0..n rules can be assigned to each event
a rule evaluates a condition in an expression to perform an action
Rule Set (not used in SRM)
group of rules
Action/Actions (not used in SRM)
an action is a BRF object
does something automatically
Definition of Event:
Events are points in the program of the application using the BRF at which there should be the possibility of using
rules to evaluate current data and possibly make changes.
BRF events and their relevant contexts are therefore defined by the developers of the application.
Within the application, SAP offers hundreds of events that have been preconceived by developers and that can be
"refined" by customers.
Within an application, calling an event triggers the BRF.
Definition of Rule:
(For practical purposes), any number of rules can be assigned to each event. It is also permissible not to assign
any rule
In the BRF the following principle is regarded as a rule:
- if <Expression> then <Action> or
- If a condition defined by an <Expression> is true, then the assigned <Action> is performed.
The BRF supports the possibility of parameterizing rules.
Definition Rule Set:
The rule set concept offers the option of grouping rules that are connected in the business sense but distributed
over several events, and then activating or deactivating them together.
Examples: Rule set used for payment check, coverage check, invoice check
Definition Expression:
An expression in BRF terms is an object that returns a result of a primitive type. Expressions can also be nested.
This means that there are expressions that access other expressions, and expressions that do not access any other
expressions (final expressions). Expressions can be split into value requests (VR) and operations (OP).
Definition:
An action is a BRF object. An action is characterized by the fact that is does something automatically. Initially,
actions have nothing to do with Activity Management.
Examples: Function module (BRF), Create/cancel task (Claims), Trigger BOR event (Claims
SAP AG 14
SAP AG 2007
BRF at Runt i me An Ex ampl e
Actions
Ausdruck
Ausdruck
Program Flow
Event
Regel
Regel
Regel
Rule
Expression Expression
Aktion
Aktion
Aktion
Action
Expression
To each event,
a number of
rules is assigned
A Rule works like,
if <expression>
then <action>
An Application using BRF
raises Events
Not used in SRM WF
BRF
In SRM, the boolean expression result (True/False)
is given back to the calling ABAP class in the application
Expression
SRM: Event calls
expression directly
The BRF is a Runtime and Maintenance Environment for the Processing, Implementation and Configuration
of Technical and Business Rules
An SAP Application using BRF raises BRF-Events
To each BRF-Event, an arbitrary number of Rules can be assigned.
A Rule works like: If <boolean Expression> then <Actions>
An Expression is an object that returns a result.
Expressions may be nested.
Usually, the result type is primitive (C, N, B, I, ...)
An Action is an object, that acts on another (usually non-BRF) object.
Actions may use Expressions as Parameters.
Rulesets are Collections of Rules belonging to e.g. one buisness process, but distributed over multiple
Events.
SAP AG 15
SAP AG 2007
BRF Overview
Workflow Configuration
Transition from old Workflow to BRF
BRF Enhancements
1. Basis Workflow Settings
2. Business Rule Framework Settings
3. Workflow Settings
New WFL features in SP01
SAP AG 16
SAP AG 2007
Conf i gur at i on Bl oc k s
Application
SAP
Business
Workflow
SRM
Process
Level
Definition
BRF
Process
Level
Process Control
WS40000014
Process Level
WS40000015
Approval
WS40000016
Event
Event
APL
WF
PL
BRF
Completion
WS40000017
Approve/Reject
Approve/Reject
Responsible
Decision Type
Expression
Expression
Expression Expression
Adjust (w. pot.
Restart)
Accept/Recall
S
h
o
u
l
d

n
o
t

c
h
a
n
g
e
M
a
i
n

C
o
n
f
i
g
u
r
a
t
i
o
n
Create SC
Process
Scheme
Event /SAPSRM/CL_WF_PDO.
READY_FOR_WORKFLOW
SAP AG 17
SAP AG 2007
Sol ut i on Manager I MG Conf i gur at i on
WF
BRF
PL
Solution Manager
IMG
IMG Path: Supplier Relationship
Management -> SRM Server ->
Cross-Application Basic Settings ->
SAP Business Workflow (New)
See Appendix for
Basic Workflow settings.
Nothing new.
SAP AG 18
SAP AG 2007
I ni t i al i ze BRF
If you want to implement the BRF in a client other than client 000,
you have to perform the following activities first:
Logon to your productive client (for example: 100)
Start report BRF_INITIALIZE
Remove the Simulation flag.
Execute the report
Please note:
If you want to initialize the workflow in several clients, you have to execute this report in all required
clients (except 000).
SAP AG 19
SAP AG 2007
BRF Overview
Workflow Configuration
Transition from old Workflow to BRF
BRF Enhancements
1. Basis Workflow Settings
2. Business Rule Framework Settings
3. Workflow Settings
New WFL features in SP01
SAP AG 20
SAP AG 2007
New BRF: Sol ut i on Manager I MG Conf i gur at i on
WF
Solution Manager (/nSOLAR02)
SRM Server IMG (/nSPRO)
1.1
1.2
1.3
1.4
only documentation,
no step execution
WF = Basis Workflow Settings
BRF = Business Rule Framework Settings
PL = Processing Level Settings for Workflow
SAP AG 21
SAP AG 2007
Mak i ng Set t i ngs f or Basi s Wor k f l ow
Basis workflow settings are settings that you have make
to set up your business workflow, regardless of the
component:
Check prefix numbers
Three-digit prefix numbers are used to uniquely identify workflow
templates and tasks.
Maintain standard settings for Workflow
Run report Perform Automatic Workflow Customizing
Set Active Plan Version
Check plan versionCheck whether your plan version is set to
'01'
Copy BRF objects
Execute report BRF_TRANSPORT_SIMPLE
Basis workflow settings are settings that you have make to set up your business workflow, regardless of the
component:
Check prefix numbers
Three-digit prefix numbers are used to uniquely identify workflow templates and tasks. For the new
SRM workflow, the prefix number '400' is used and must be active.
Example
- Main SRM Approval Process Template (40000014)
- Task SetLevelStatus (40007962)
Perform standard checks
You can perform extensive checks to see whether the settings for the standard business workflow are
complete. To do so, run report Perform Automatic Workflow Customizing. You can also process each
step individually.
Check plan versionCheck whether your plan version is set to '01', which is the active plan version. All
delivered workflows are automatically in this plan version.
Copy BRF objects
Execute report BRF_TRANSPORT_SIMPLE to copy BRF objects to your sandbox system.
SAP AG 22
SAP AG 2007
Organizational Management objects are identified by an eight-digit number.
For tasks, workflows, rules and task groups, this number consists of a three-digit
prefix number followed by a five-digit number which is determined by internal
number assignment.
The complete number must be unique across systems and clients. From a technical
point of view, the uniqueness of the number is ensured by the prefix number.
Select a unique prefix number in your customer number range for each system and
each client.
The table with the prefix numbers is connected to the object catalog, ensuring that
the prefix numbers are unique within the system infrastructure.
1.1 Mai nt ai n Pr ef i x Number s
Logon to your SRM client
Define Prefix Numbers
SAP AG 23
SAP AG 2007
1.2 Mai nt ai n St andar d Set t i ngs f or SAP Busi ness Wor k f l ow
Logon to your SRM client
Execute the Automatic Workflow Customizing
RFC Destination WORKFLOW_LOCAL_<client> will be created
All these
customizing
settings are
performed
automatically
SAP AG 24
SAP AG 2007
1.3 Set Ac t i ve Pl an Ver si on
System default is 01. You do not need to change it.
Just check it.
Only one of the plan versions created in the system is active at a given time.
The workflow system regards this plan version (with its contents) as the
only valid plan version.
SAP AG 25
SAP AG 2007
1.4 Copy BRF Obj ec t s
Logon to your SRM client
Run Report:
BRF_TRANSPORT_SIMPLE
Enter Application Class:
SRM_WF
The report copies BRF Objects
from client 000 to your current
client
Run this report once for each
client in your SRM system (except
client 000)
Execute this report to transport SRM-specific Business Rule Framework objects (BRF) to a sandbox system.
SAP AG 26
SAP AG 2007
BRF Overview
Workflow Configuration
Transition from old Workflow to BRF
BRF Enhancements
1. Basis Workflow Settings
2. Business Rule Framework Settings
3. Workflow Settings
New WFL features in SP01
SAP AG 27
SAP AG 2007
New BRF: Sol ut i on Manager -> I MG Conf i gur at i on
BRF
Solution Manager (/nSOLAR02)
SRM Server IMG (/nSPRO)
2.1
2.2
2.3
only documentation,
no step execution
WF = Basis Workflow Settings
BRF = Business Rule Framework Settings
PL = Processing Level Settings for Workflow
SAP AG 28
SAP AG 2007
I mpor t ant BRF Tr ansac t i ons
Maintenance Workbench: BRF
Overview: BRF_OVERVIEW
Other: BRF{EVT|ACT|EXP|}{01|02|03}
SAP AG 29
SAP AG 2007
2.1 Def i ne Event s
Create a new event, assign an Impl. Class, Appl.Class, Group (optional)
Events are used to execute Processing Levels and to determine the
processing of the workflow. Therefore, each processing level is assigned
to an event. Example: If a PO exceeds 1,000.00 Euro a managers approval
is required
SAP AG 30
SAP AG 2007
2.2 Def i ne Ex pr essi on
With Expressions, it is determined if a processing level must be executed.
The result of an expression is compared with a value.
These values are usually obtained from SRM document fields
(e.g. total order value)
Valid expressions are:
Constant
Value
SAP Formula
Interpreter
(boolean)
Range
Function Module
(e.g. to determine
values from SC)
Constant
Returns a fixed value, for example the limit of a shopping cart.
Value
Returns a value, for example the total value of the shopping cart.
SAP formula interpreter
Returns a boolean value that specifies whether or not the total value of the shopping cart is smaller than
1,000.00, for example.
Range expression
Returns a boolean value that specifies whether or not the spending limit of the processor has been
exceeded, for example. The expression that contains the spending limit is checked.
Function module
Using a function module that contains expressions as parameters, the parameter values of BOR object
Shopping Cart (BUS2121) can be imported and returned.
SAP AG 31
SAP AG 2007
2.3 Def i ne Gr oups
Pre-defined Group: 0SCHEME_DECISION
Groups are used to cluster BRF-Objects depending on their area and
purpose
However, Groups are not required for an approval workflow
SAP AG 32
SAP AG 2007
BRF Overview
Workflow Configuration
Transition from old Workflow to BRF
BRF Enhancements
1. Basis Workflow Settings
2. Business Rule Framework Settings
3. Workflow Settings
New WFL features in SP01
SAP AG 33
SAP AG 2007
New BRF: Sol ut i on Manager WFL Conf i gur at i on
PL
Solution Manager (/nSOLAR02)
SRM Server IMG (/nSPRO)
only documentation,
no step execution
3.1
3.2
3.3
3.4
WF = Basis Workflow Settings
BRF = Business Rule Framework Settings
PL = Processing Level Settings for Workflow
SAP AG 34
SAP AG 2007
3.1 Ac t i vat e Wor k f l ow
Activate the main SRM workflow WS40000014 and its event links
Check the results
SAP AG 35
SAP AG 2007
3.1 Set Gener al Task
Set general task:
General SRM Tasks are TS 400007936, 43, 44, 52, 53, 54
Please Note: All SRM-based WF tasks start with TS4
Please note:
The SRM 6.0 (Core Process Manager) uses BRF only to decide if a workflow is started.
SAP AG 36
SAP AG 2007
3.2 Def i ne Fi l t er Val ues f or Busi ness Add-I n
In this step, you specify the BAdI filter that enables you to determine
the user to be assigned to a workflow task in Define Process Levels.
There are 11 predefined samples.
View: /SAPSRM/BD_WF_SC_AGENTS
SAP AG 37
SAP AG 2007
3.3 Det er mi ne Pr oc essor
This Business Add-In (BAdI) is used in the SRM Workflow
component (SRM_EBP_WFL).
You can use this BAdI to assign SRM purchasing documents (or
separate parts of these documents) to agent groups for (parallel)
approval. You can either display existing Agents or perform an
implementation enhancement by creating new Agents.
You want to assign all users of a specific user role to approve each individual item of the complete
document (decision type 2 in the process level configuration (transaction /SAPSRM/WF_PROCESS or
view cluster /SAPSRM/VC_WF_P):
Use method /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_AREA_TO_ITEM_MAP to return an
activity area (specified by an area GUID) together with the item GUID
'00000000000000000000000000000000' indicating that you want all items to be processed by the
approver. The mapping information about which user role is identified by a certain area ID must be
stored for the agent retrieval later on (See the information below.).
Use method /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID to
return all users of your user role as responsible approvers. For this step, use the previously saved
mapping information.
Optional: use method
/SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_RESP_RESOLVER_PARAMETER_F4 to provide
an search help for user roles in the Responsibility Resolver Parameter field in the process level
configuration (transaction /SAPSRM/WF_PROCESS or view cluster /SAPSRM/VC_WF_P). With
method /SAPSRM/IF_EX_WF_RESP_RESOLVER~CHECK_RESP_RESOLVER_PARAMETER
you can add an input check to this field.
SAP AG 38
SAP AG 2007
Level Conf i gur at i on at Desi gn Ti me (Ex ampl e)

Item-Based
Decision
for Partial
Document
Item-Based
Decision
for Partial
Document
Item-Based
Decisions for
Entire
Document
Item-Based
Decisions for
Entire
Document
Approval
decision type

Next director in PD-Org Total Value
exceeds Euro
2000,-
Director approval Approval 40
Next line manager in PD-
Org
Total Value
exceeds Euro
400,-
Line manager
approval
Approval 30
Users with role
BBP_STALIT_DEPAR
TMENT
Product
category 012
exists (IT
Equipment)
IT Department
completion (of IT
equipment)
Completion 20
Purchasers of purchasing
group 500000002
Free text item
exists
Purchaser completion
(of free text
requirements)
Completion 10
Responsible agents Business Rule Description
Process
(type)
Level
SAP AG 39
SAP AG 2007
3.4 Def i ne Pr oc ess Level s Busi ness Obj ec t
A Process Level is level within a completion or approval process.
During the approval process, a document run through every
process level (1-3). Each level can consist of several steps
First Step Select Business Object BUS2121 Shopping Cart
SAP AG 40
SAP AG 2007
3.4 Def i ne Pr oc ess Level s Eval uat i on I D
Second Step Determine Evaluation ID, for example 9EV_SC_00S
The Evaluation ID specifies the ID of the event that triggers the
workflow. The specific events are defined in the Business Rule
Framework (BRF).
SAP AG 41
SAP AG 2007
3.4 Def i ne Pr oc ess Level s Sc hema
Third Step Schema Definition
Availalbe Schemas
in SP01
SAP AG 42
SAP AG 2007
3.4 Def i ne Pr oc ess Level s Sc hema
With SP01 the following schemas are available:
Schema BUS2121_EX01 (Completion & Approval)
Schema BUS2121_EX02 (Budget Workflow)
Schema BUS2121_EX03 (n-step Spending Limit)
Schema BUS2121_EX04 (1-Step Spending Limit Approval)
Schema BUS2121_EX05 (no approval for total values < doc. owner's
spend.-limit)
Schema BUS2121_DUET
SAP AG 43
SAP AG 2007
3.4 Def i ne Pr oc ess Level s
Process Level Configuration (SPRO customizing)
Level Type (Completion, Approval)
Responsibility Resolver name (User, Role, Manager, )
Business Rules Framework (level validation)
Task ID (predefined OR customer own)
Decision Type
Example:
Secretary approves shopping cart
Purchasing group member approves shopping cart, because event
(SC Value > 1,000.00 EUR) was exceeded
Manager approves shopping cart, because event (SC Value > 5,000.00 EUR)
exceeded
Process Level Type
Specifies the process level type.
The following levels types are available:
Completion process
Process during which work items are created when a document requires approval. You can delete items,
but you cannot change the document itself.
Approval process
Process during which work items are created when a document is incomplete. Changes to header or item
data of the document are allowed. Incomplete documents are supplemented by the relevant processor.
The level type automatically determines the underlying workflow template.
Responsibility Resolver Name
Specifies the technical user assigned to the workflow task through a filter of Business Add-In Determine
Agents (Manager, Secretary, and so on).
Responsibility Resolver Parameter
Specifies the return value of the Business Add-In filter, that is, the user retrieved from the organizational
structure
EvaIuation Identifier
Specifies the ID of the event that triggers the workflow. You can define events in the Business Rule
Framework (BRF).
Workflow Task Identifier
Specifies the ID of the underlying workflow task.
Decision Type:
Determines which user approves what during a workflow process. For example, a document can be
approved by a single user as a block or by multiple approvers on an item basis.
SAP AG 44
SAP AG 2007
BRF Overview
Workflow Configuration
Transition from old Workflow to BRF
BRF Enhancements
New WFL features in SP01
SAP AG 45
SAP AG 2007
Adopt i on of new Wor k f l ow f or Ot her Busi ness Obj ec t s
In SP01 the new workflow is now available for
Shopping Carts
Purchase Orders
Purchase Contracts
Bid Invitations
Vendor Bids
Therefore, the workflow transitions has to be performed for these
objects.
Note: The old workflow will be still in use for invoice and confirmation
will be available in SP02
SAP AG 46
SAP AG 2007
Tr ansi t i on St eps f r om SRM 5.0 t o SRM 6.0 (Over vi ew )
The SRM 5.0 BAdI-Workflows are not supported in its original
form any more
There is a new concept to adapt the approval workflows to
customer expectations (mainly configuration and
programming)
Approval Workflows must be switched to the new SRM
Workflow as soon as the new UI for the BO is introduced
After the Upgrade from SRM 5.0 to SRM 6.0 there is the need
to stop the old workflows and re-start the new workflows
The following reports are provided to do the switch
/SAPSRM/PR_WF_MIGRATION_CFG (migrates the workitems)
/SAPSRM/WF_COND_MAPPING (migrates the start conditions)
The transistion tasks are>
For Workflow Team:
- provide workflow functionality
- configure workflow
- do the showcase implementation for Shopping Cart BO
For BO owner:
- bring together workflow and business logic
SAP AG 47
SAP AG 2007
Tr ansi t i on Const r ai nt s
New SRM Workflow Framework and new Business
Objects are tied together, thus:
New Business Objects (Web Dynpro UI) have to use new SRM
Workflow Framework
Old PD documents (ITS UI) have to use the old SRM Workflow
Framework
It is not planned to combine old and new technologies!
After switching to new workflow old workflow items are no
longer usable
Please note:
Process Levels must be perviously defined, as they are
a prerequisite for the transition
SAP AG 48
SAP AG 2007
Mi gr at e Wor k f l ow I t ems (Deac t i vat e ol d WF I t ems)
Report: /SAPSRM/PR_WF_MIGRATION_CFG
This report searches for workitems, sets them to CANCELLED and starts
the respective new workitem (with the GUID of the old workitem document).
1. Perform a simulation and check the results
2. Perform the final conversion and check the results
(Set toggle)
3. Test the results
SP01
The following workflows are updated, provided that their status is set to 'Ready' or 'Waiting':
Without approval (WS10000060)
One-step approval (WS10000129)
Two-step approval (WS10000031)
Spending limit for SC (n-step) (WS14000109)
Multi-step approval workflow for shopping cart (WS14000133)
Multi-step approval of individual SC items by responsible approver (WS14500015)
Completion of shopping cart by purchaser (WS14000044)
Prerequisites
You must have completed the process level configuration in the Implementation Guide for mySAP
Supplier Relationship Management, as described in SRM Server -> Cross-Application Basic Settings ->
SRM Workflow (New) -> SRM Workflow Settings -> Define Process Levels.
SAP AG 49
SAP AG 2007
Chec k i ng t he Wor k i t em Mi gr at i on
Check the contents of Table: /SAPSRM/D_WF_001
After the report /SAPSRM/PR_WF_MIGRATION_CFG
with the Set Toggle option, the previously mentioned
Business Objects must be set to NEW_WF_ACTIVE = X
SP01
SAP AG 50
SAP AG 2007
Mi gr at e ol d Wor k f l ow Condi t i ons t o new Wor k f l ow
Report /SAPSRM/WF_COND_MAPPING
Reads start conditions (/nSWB_COND) from SRM 5.0 Workflow
and transfers them into SRM 6.0 BRF Expression Formulas
(e.g. 1- and 2-step Approval, Spending Limit and SC Completion,
also for Contracts, Purchaser Order etc.)
Uses entries from the Process Level table /SAPSRM/C_WF_MAP
with one Completion Approval and two Approval steps
Please Note:
The Report does not create any
BRF Objects. They must exist
already.
The Report creates the step-tables
and the schematas.
SAP AG 51
SAP AG 2007
Upgr ade Pr oc edur e f or Non-BAdI -Wor k f l ow s
Important notes for the prerequisites and documentation for
SRM 60 workflow
SP00 note 1006051
SP01 note 1025611
Exceptions:
If errors occure during the mirgration of the WF because start
conditions could not be mapped with the shipped BRF Expressions
please follow the steps according to
SAP note 1015211
SAP AG 52
SAP AG 2007
BRF Overview
Workflow Configuration
Transition from Old Workflow to BRF
New WFL features in SP01
BRF Enhancements
SAP AG 53
SAP AG 2007
Al er t i ng
Alerts are now supported with SP01
Customizing is the same as in release SRM 5.0
The alerts appear in the UWL of the resp. person in the portal
Note:
Notifications will not be available in SP01 or SP02 because of a technical issue regarding the UWL. Development
is working on a solution.
SAP AG 54
SAP AG 2007
Al er t i ng
Example:
Alert for approval workflow if
latest end is reached
IMG: SRM Server Cross-
Application Basic Settings Event
and Event Schema for Alert
Management
SAP AG 55
SAP AG 2007
Of f l i ne Appr oval w i t h DUET
In SRM 6.0 SP01 Shopping Cart approval with DUET is available
Employee can approve SC directly out of the MS Office Inbox without
loggin on to SRM
MS Office Inbox
Preview pane
SAP AG 56
SAP AG 2007
Of f l i ne Appr oval w i t h DUET
Approval email in detail
SC Details
Link to SRM
application
Approve / Reject buttons
As you can see from screen shot above, you have 2 buttons: Approve Shopping Cart and Reject Shopping
Cart.
Shopping Cart Detail will hide/unhide the application pane you see to the right.
Application pane to the right shows additional Shopping Cart information such as approval overview and
budget data
SAP AG 57
SAP AG 2007
BRF Overview
Workflow Configuration
Transition from old Workflow to BRF
New WFL features in SP01
BRF Enhancements
SAP AG 58
SAP AG 2007
Busi ness Add-I ns f or Wor k f l ow
BAdIs for new workflow new in SP01
BAdI: Deadlines fr Ereignisse festlegen
You can use this Business Add-In (BAdI) to calculate the different deadlines that
are used in a completion or appoval process
BAdI: Prozessstufenkonfiguration
You can use the BAdI to build your own runtime version of the process schema on
the basis of the design time process schema as defined in Customizing
BAdI: Prozessneustarts verwalten
You can use this BAdI to avoid a complete process restart after a
document change
Determine Shopping Cart Value for Purchasing Budget Workflow
This BAdI allows you to implement your own method for determination of the value
of a shopping cart
SPRO SRM Server Business Add-Ins
SAP Business Workflow (New)
Determine Shopping Cart Value
This BAdI allows you to implement your own method for determination of the value of a shopping cart.
This value is then transferred to a database table (BBP_URSBDGT) for comparison with the user budget.
This table then contains the total of all purchases by a certain user within a calendar period (field
AMOUNTSPENT).
During implementation of the BAdI, you can define whether all items of the shopping cart are to be
considered during calculation of the value, and determine which items of the shopping cart are to be
written to the update table described above. This selective update can be necessary in the following cases:
Shopping cart items are assigned to different account assignment objects.
Shopping cart contains items with different product categories.
SAP AG 59
SAP AG 2007
BRF Hel p
See help.sap.com ->SAP ERP Central Component
->Cross-Application Services->Business Rule Framework
SAP AG 60
SAP AG 2007
F
e
a
t
u
r
e
s

a
n
d

F
u
n
c
t
i
o
n
s
Time
+ New workflow for
Shopping Cart:
+ n-step Approval
+ Completion Approval
+ Budget Approval
SP00
+ Dynamic Spending Limit
Approval (Shopping Cart)
+ Alerting & Notifications
+ Offline Approval with Duet
+ Upgrade Procedure for
Non-BAdI-Workflows
+ Adoption of new workflow
for other business objects
SP01
+ Reviewer Workflow
+ New Workflow for
Confirmation & Invoice
SP02
-
+
+
Wor k f l ow Feat ur es Over Ti me
New workflow capabilities will evolve from service pack to
service pack
SAP AG 61
SAP AG 2007
Summar y
Contents
mySAP SRM Workflow Concept
Now you are able to:
Explain the differences between the old and new Workflow
(BRF) concept
Describe the transition to the new Workflow (BRF) concept
Perform the initial BRF configuration
Understand how BRF enhancements are performed
SAP AG 62
SAP AG 2007
I mpor t ant Dat abase Tabl es
Application classe: TBRF000(T), TBRF100(T)
Events: TBRF110(T)
Expressions: TBRF150(T)
Actions: TBRF170(T)
(Concrete) action: TBRF171
BRF-object where-used list: TBRF200
Event<->Expression<->Action (Rule): TBRF210
Rule Sets: TBRF280(T)
Rule set<->Event<->Expressions<->Actions: TBRF310
Versioning information: TBRF320(T)
BRF-Workbench: BRFWB*
Profile network graphic: TBRF500
SAP AG 63
SAP AG 2007
Copyr i ght 2007 SAP AG. Al l Ri ght s Reser ved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p,
System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC
are trademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C

, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.
Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments,
and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this
document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items
contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This
limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in
these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.