BRF Workflow Concept

SAP AG 1

SAP AG 2007

SRM 6.0 BRF Workflow Concept

SAP AG 2

SAP AG 2007

Objectives

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 OverviewWorkflow ConfigurationTransition from old Workflow to BRF

BRF EnhancementsNew WFL features in SP01

SAP AG 4

SAP AG 2007

Introduction

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 maintenanceenvironment.

The basic idea of the BRF is to offer the possibility of freelyconfigurable 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 Workflow Framework

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 FrameworkBAdI

*

One typeof template

Multipletypes

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 functiongroup BBP_SC_UI_ITS and BBP_SC_APP.

PDO Layer = Procurement Document Objects Layer

Targets of the new Workflow Framework:y Improve maintainability - Remove complexity of coding (more than 100 interfaces, complex BAdI

Interface, no API)y Review the workflow requirements

- Create a map of required functionality- Keep and improve functionality, but discontinue features with little business gain but high code

complexityy Introduce a new, easy implementation concept at customer sidey Improve architecture for future requirements - Scalabilityy 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

Location of Business Logic

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

Enhancements and Business Benefits

Enhancements in 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)

Business Benefits

SAP AG 8

SAP AG 2007

Back & Forth Function, Inquiry and Recall

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

z Approvez Reject

z Approvez Rejectz Inquirez Edit

z Change/Recall

Requester Approver

z Accept/Adjustz Accept/Adjust

Special

ist

Financia

lz Change/Recall

z Accept/Adjust

SAP AG 9

SAP AG 2007

Approval Preview and Recall Popup

Approval Preview

Recall Popup

when you edit a document which is

in approval

SAP AG 10

SAP AG 2007

Portal Inbox and New UI

SAP AG 11

SAP AG 2007

General Guideline

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 BRFOr BADI Adapter is planned in later SP

SAP AG 12

SAP AG 2007

Very Simple Overview

Configuration DataBRF Objects

Application

BRF MaintenanceRule Creation

Events, Rules, Expressions,

Actions, Rulesets

Maintenance Screens

Application Data

BRF RunTime

Rule Evaluation

Application ContextInformation

SAP AG 13

SAP AG 2007

BRF Objects

The main objects of the BRF are:

Eventz evaluate and change dataz hundreds of predefined events are available

Expressionz return resultsz can be nested

Rule (not used in SRM)z 0..n rules can be assigned to each eventz a rule evaluates a condition in an expression to perform an action

Rule Set (not used in SRM)z group of rules

Action/Actions (not used in SRM)z an action is a BRF objectz does something automatically

Definition of Event:y 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.y BRF events and their relevant contexts are therefore defined by the developers of the application.y Within the application, SAP offers hundreds of events that have been preconceived by developers and that can be

"refined" by customers.y Within an application, calling an event triggers the BRF.

Definition of Rule:y (For practical purposes), any number of rules can be assigned to each event. It is also permissible not to assign

any ruley In the BRF the following principle is regarded as a rule:

- if then or- If a condition defined by an is true, then the assigned is performed.

y The BRF supports the possibility of parameterizing rules. Definition Rule Set:y 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.y Examples: Rule set used for payment check, coverage check, invoice check

Definition Expression:y 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 otherexpressions (final expressions). Expressions can be split into value requests (VR) and operations (OP).

Definition:y 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.y Examples: Function module (BRF), Create/cancel task (Claims), Trigger BOR event (Claims

SAP AG 14

SAP AG 2007

BRF at Runtime An Example

Actions

AusdruckAusdruck

Program Flow

Event

RegelRegel

RegelRule

Expression Expression

AktionAktion

AktionAction

Expression

To each event, a number of

rules is assigned

A Rule works like,if then

An Application using BRFraises 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 callsexpression directly

The BRF is a Runtime and Maintenance Environment for the Processing, Implementation and Configurationof 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 then An Expression is an object that returns a result.y Expressions may be nested.y Usually, the result type is primitive (C, N, B, I, ...)

An Action is an object, that acts on another (usually non-BRF) object.y 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 OverviewWorkflow Configuration

Transition from old Workflow to BRF

BRF Enhancements

1. Basis Workflow Settings2. Business Rule Framework Settings3. Workflow Settings

New WFL features in SP01

SAP AG 16

SAP AG 2007

Configuration Blocks

Application

SAP Business Workflow

SRM Process

Level Definition

BRF

Process Level

Process ControlWS40000014

Process LevelWS40000015

ApprovalWS40000016

Event Event

APL

WF

PL

BRF

CompletionWS40000017

Approve/RejectApprove/Reject

Responsible

Decision Type

Expression ExpressionExpression Expression

Adjust (w. pot. Restart)

Accept/Recall

Shou

ld n

ot c

hang

eM

ain

Con

figur

atio

n

Create SC

Process Scheme

Event /SAPSRM/CL_WF_PDO. READY_FOR_WORKFLOW

SAP AG 17

SAP AG 2007

Solution Manager IMG Configuration

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

Initialize 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:

y If you want to initialize the workflow in several clients, you have to execute this report in all requiredclients (except 000).

SAP AG 19

SAP AG 2007



BRF Enhancements



SAP AG 20

SAP AG 2007

New BRF: Solution Manager IMG Configuration

WF

Solution Manager (/nSOLAR02)

SRM Server IMG (/nSPRO)

1.11.2

1.31.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

Making Settings for Basis Workflow

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 WorkflowRun report Perform Automatic Workflow Customizing

Set Active Plan VersionCheck 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 numbersy 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.

y Example- Main SRM Approval Process Template (40000014)

- Task SetLevelStatus (40007962)

Perform standard checksy 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.

y 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 objectsy 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 Maintain Prefix Numbers

Logon to your SRM client

Define Prefix Numbers

SAP AG 23

SAP AG 2007

1.2 Maintain Standard Settings for SAP Business Workflow


Execute the Automatic Workflow Customizing

RFC Destination WORKFLOW_LOCAL_ will be created

All thesecustomizingsettings areperformedautomatically

SAP AG 24

SAP AG 2007

1.3 Set Active Plan Version

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 Objects


Run Report: BRF_TRANSPORT_SIMPLE

Enter Application Class: SRM_WF

The report copies BRF Objectsfrom client 000 to your currentclient

Run this report once for eachclient in your SRM system (exceptclient 000)

Execute this report to transport SRM-specific Business Rule Framework objects (BRF) to a sandbox system.

SAP AG 26

SAP AG 2007



BRF Enhancements



SAP AG 27

SAP AG 2007

New BRF: Solution Manager -> IMG Configuration

BRF



2.12.2

2.3



SAP AG 28

SAP AG 2007

Important BRF Transactions

Maintenance Workbench: BRF

Overview: BRF_OVERVIEW Other: BRF{EVT|ACT|EXP|}{01|02|03}

SAP AG 29

SAP AG 2007

2.1 Define Events

Create a new event, assign an Impl. Class, Appl.Class, Group (optional)

Events are used to execute Processing Levels and to determine theprocessing of the workflow. Therefore, each processing level is assignedto an event. Example: If a PO exceeds 1,000.00 Euro a managers approvalis required

SAP AG 30

SAP AG 2007

2.2 Define Expression

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 determinevalues from SC)

ConstantReturns a fixed value, for example the limit of a shopping cart.

ValueReturns a value, for example the total value of the shopping cart.

SAP formula interpreterReturns a boolean value that specifies whether or not the total value of the shopping cart is smaller than 1,000.00, for example.

Range expressionReturns 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 moduleUsing 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 Define Groups

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 Enhancements



SAP AG 33

SAP AG 2007

New BRF: Solution Manager WFL Configuration

PL




3.13.2

3.33.4


SAP AG 34

SAP AG 2007

3.1 Activate Workflow

Activate the main SRM workflow WS40000014 and its event links

Check the results

SAP AG 35

SAP AG 2007

3.1 Set General 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 Define Filter Values for Business Add-In

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 Determine Processor

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):

y 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.).

y 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.

y 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 Configuration at Design Time (Example)

Item-Based Decisionfor Partial Document

Item-Based Decisionfor Partial Document

Item-Based Decisions for Entire Document

Item-Based Decisions for Entire Document

Approval decision type

Next director in PD-OrgTotal Value exceeds Euro 2000,-

Director approvalApproval40

Next line manager in PD-Org

Total Value exceeds Euro 400,-

Line manager approval

Approval30

Users with role BBP_STALIT_DEPARTMENT

Product category 012exists (IT Equipment)

IT Department completion (of IT equipment)

Completion20

Purchasers of purchasing group 500000002

Free text item exists

Purchaser completion (of free text requirements)

Completion10

Responsible agentsBusiness RuleDescriptionProcess (type)Level

SAP AG 39

SAP AG 2007

3.4 Define Process Levels Business Object

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 Define Process Levels Evaluation ID

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 Define Process Levels Schema

Third Step Schema Definition

Availalbe Schemasin SP01

SAP AG 42

SAP AG 2007

3.4 Define Process Levels Schema

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 Define Process Levels

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 cartPurchasing group member approves shopping cart, because event

(SC Value > 1,000.00 EUR) was exceededManager approves shopping cart, because event (SC Value > 5,000.00 EUR)

exceeded

Process Level TypeSpecifies 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 processProcess 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 ParameterSpecifies the return value of the Business Add-In filter, that is, the user retrieved from the organizational structure

EvaIuation IdentifierSpecifies the ID of the event that triggers the workflow. You can define events in the Business Rule Framework (BRF).

Workflow Task IdentifierSpecifies 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 OverviewWorkflow ConfigurationTransition from old Workflow to BRF

BRF EnhancementsNew WFL features in SP01

SAP AG 45

SAP AG 2007

Adoption of new Workflow for Other Business Objects

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 confirmationwill be available in SP02

SAP AG 46

SAP AG 2007

Transition Steps from SRM 5.0 to SRM 6.0 (Overview)

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>y For Workflow Team:

- provide workflow functionality

- configure workflow

- do the showcase implementation for Shopping Cart BO

y For BO owner:- bring together workflow and business logic

SAP AG 47

SAP AG 2007

Transition Constraints

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 area prerequisite for the transition

SAP AG 48

SAP AG 2007

Migrate Workflow Items (Deactivate old WF Items)

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 results2. 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':y Without approval (WS10000060)y One-step approval (WS10000129)y Two-step approval (WS10000031)y Spending limit for SC (n-step) (WS14000109)y Multi-step approval workflow for shopping cart (WS14000133)y Multi-step approval of individual SC items by responsible approver (WS14500015)y Completion of shopping cart by purchaser (WS14000044)

Prerequisitesy 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

Checking the Workitem Migration

Check the contents of Table: /SAPSRM/D_WF_001

After the report /SAPSRM/PR_WF_MIGRATION_CFG with the Set Toggle option, the previously mentionedBusiness Objects must be set to NEW_WF_ACTIVE = X

SP01

SAP AG 50

SAP AG 2007

Migrate old Workflow Conditions to new Workflow

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 anyBRF Objects. They must existalready.The Report creates the step-tablesand the schematas.

SAP AG 51

SAP AG 2007

Upgrade Procedure for Non-BAdI-Workflows

Important notes for the prerequisites and documentation forSRM 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 OverviewWorkflow ConfigurationTransition from Old Workflow to BRFNew WFL features in SP01BRF Enhancements

SAP AG 53

SAP AG 2007

Alerting

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

Alerting

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

Offline Approval with 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 SRMMS Office Inbox

Preview pane

SAP AG 56

SAP AG 2007

Offline Approval with DUET

Approval email in detailSC Details

Link to SRMapplication

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 OverviewWorkflow ConfigurationTransition from old Workflow to BRFNew WFL features in SP01BRF Enhancements

SAP AG 58

SAP AG 2007

Business Add-Ins for Workflow

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: ProzessstufenkonfigurationYou 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 verwaltenYou can use this BAdI to avoid a complete process restart after adocument change

Determine Shopping Cart Value for Purchasing Budget WorkflowThis 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:

y Shopping cart items are assigned to different account assignment objects.y Shopping cart contains items with different product categories.

SAP AG 59

SAP AG 2007

BRF Help

See help.sap.com ->SAP ERP Central Component

->Cross-Application Services->Business Rule Framework

SAP AG 60

SAP AG 2007

Feat

ures

and

Fun

ctio

ns

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

- +

+

Workflow Features Over Time

New workflow capabilities will evolve from service pack to service pack

SAP AG 61

SAP AG 2007

Summary

Contentsz mySAP SRM Workflow Concept

Now you are able to:

z Explain the differences between the old and new Workflow (BRF) concept

z Describe the transition to the new Workflow (BRF) conceptz Perform the initial BRF configurationz Understand how BRF enhancements are performed

SAP AG 62

SAP AG 2007

Important Database Tables

Application classe: TBRF000(T), TBRF100(T) Events: TBRF110(T) Expressions: TBRF150(T) Actions: TBRF170(T) (Concrete) action: TBRF171 BRF-object where-used list: TBRF200 EventExpressionAction (Rule): TBRF210 Rule Sets: TBRF280(T) Rule setEventExpressionsActions: TBRF310 Versioning information: TBRF320(T)

BRF-Workbench: BRFWB* Profile network graphic: TBRF500

SAP AG 63

SAP AG 2007

Copyright 2007 SAP AG. All Rights Reserved

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.

/ColorImageDict > /JPEG2000ColorACSImageDict > /JPEG2000ColorImageDict > /AntiAliasGrayImages false /DownsampleGrayImages true /GrayImageDownsampleType /Bicubic /GrayImageResolution 150 /GrayImageDepth -1 /GrayImageDownsampleThreshold 1.50000 /EncodeGrayImages true /GrayImageFilter /DCTEncode /AutoFilterGrayImages true /GrayImageAutoFilterStrategy /JPEG /GrayACSImageDict > /GrayImageDict > /JPEG2000GrayACSImageDict > /JPEG2000GrayImageDict > /AntiAliasMonoImages false /DownsampleMonoImages true /MonoImageDownsampleType /Bicubic /MonoImageResolution 300 /MonoImageDepth -1 /MonoImageDownsampleThreshold 1.50000 /EncodeMonoImages true /MonoImageFilter /CCITTFaxEncode /MonoImageDict > /AllowPSXObjects true /PDFX1aCheck false /PDFX3Check false /PDFXCompliantPDFOnly false /PDFXNoTrimBoxError true /PDFXTrimBoxToMediaBoxOffset [ 0.00000 0.00000 0.00000 0.00000 ] /PDFXSetBleedBoxToMediaBox true /PDFXBleedBoxToTrimBoxOffset [ 0.00000 0.00000 0.00000 0.00000 ] /PDFXOutputIntentProfile () /PDFXOutputCondition () /PDFXRegistryName (http://www.color.org) /PDFXTrapped /False

/Description >>> setdistillerparams> setpagedevice

BRF Workflow Concept

Documents

Transcript of BRF Workflow Concept