rtftftftfdrtrdtdtrdp363 solutiyftdtdtdtdtdtdtddons

8/12/2019 RtftftftfDrtrdtdtrdP363 Solutiyftdtdtdtdtdtdtddons

1/44

SAP MASTER DATA GOVERNANCE

FRAMEWORK CONFIGURATION AND

WORKFLOW DEVELOPMENT

RDP363

SolutionMichael Boettcher, MDG Product ManagementDavid Quirk, MDG Solution Management


2/44

2

INTRODUCTION

Make master data governance workflow design more of a configuration and less of a development effort. Withbusinesses needing process transparency and business process efficiency, workflows are critical aspects of

governance. They are the backbone for introducing transparency to manage master data because without some typeof process control, the management of master data is often completely unstructured, neither guided nor controlled.Creating workflows has been very expensive, at times hard-coded and often inflexible, putting a lot of effort in coding,thereby proving to be semi-automated processes. These semi-automated processes can be replaced by a flexibleprocess, especially if the workflow is based on an integrated rules management.

SAP Master Data Governance combines the SAP Business Workflow tool with the capabilities of business rulesframework (BRFplus). This combination of SAP Business Workflow and BRFplus is referred to as rule-based workflow.Since the technology of rule-based workflow is based on single-stack solutions, you dont need to worry about settingup complex landscape environments. Rule-based workflow provides flexible processing and easy configuration.Decisions take place iteratively based on the current state of the workflow; the status of the change request, and userinteractions and the flow is determined by decision tables populated by end-users.

Additionally, SAP Master Data Governance comes with a powerful framework allowing configurations across all

aspects of the change request process including UI configurations; custom validations and additional actions andstatus values presented to an end user.

In this session, you will be introduced to the concepts of SAP Master Data Governance's configuration framework andrule based workflow. You will make several change request configurations as well as setup the workflow decisiontables by enhancing an already existing workflow with an additional step. You will also learn to define your own actionand user interface for the additional process step.

Session Outline

Goal: The exercise below will guide you through customer specific enhancements of a predefined Master DataGovernance Process. This will include:

Adding a new process step includingo a step specific User Interfaceo a step specific action called Check Quotao changes to the Rule Based Workflow

The exercises must be completed in sequence as they build upon each other. Additional hint when working with therule based workflow: always save and activate your work


3/44

3

Naming Convention

Assignment of Group NumbersUser IDs Change Request Types

Group

Number

User ID Change

Request Type

Group

Number

User ID Change

Request Type

Group 01 RDP363-01 SFZ01 Group 31 RDP363-31 SFZ31































4/44

4

Logon information

nn= Group number from 0160

Replace nnwith your two-digit group number

Logon to the SAP System M18 Client 800

Username: RDP363-nn

Password: welcome (If prompted to change your password please change it to RDP363-nn)

Logon with SAP NetWeaver Business Client 3.5

Please logon to the system using SAP NetWeaver Business ClientDesktop (NWBC) in version 3.5 from the startmenu or using the shortcut on the desktop:

Do not use NWBC 4.0

NWBC 4.0 uses a new design and layout, so that you will not be able to follow the description of the exercise andparticularly the screenshots in the solution section.

Additional Note: When creating flight connection data, use the naming convention nn## where nn = your group numberand ## = a number of your choosing, different for each connection you create.


5/44

5

Exercises - Overview


6/44

6

BACKGROUND REFERENCE MATERIALFAMILIARIZE YOURSELF

WITH THE SETUP

Reference material

See below for the background setup done for this exercise.

Background

.

Change Request Type

Change Request Type SFP01 has been copied to SFZXX (replace XX with your group number) and the underlyingWorkflow template has been exchanged to Workflow-Template WS60800086 (which is used as the template for RuleBased Workflows). The switch to the Rule Based Workflow has been done to:

enable the SAP Customer to take advantage of the BRF (Business Rules Framework) which allows BusinessExperts with limited technical knowledge to adapt the MDG Workflows

show how easy it is to switch from a regular (Business Workflow based) process to a Rule Based process(Business Workflow + BRF)

The Copy has been done through the Master Data Governance Implementation Guide (transaction MDGIMG)Create Change Request Type:


7/44

7


8/44

8

Change Request Type SFP01 has been copied to SFZXX (replace XX by your group number):

The Workflow Template has been exchanged (using the template for the Rule Based Workflow):

SFZXX


9/44

9

Be aware that the standard UI Configuration has been defined in the Change Request Type:

Define the Change Request Steps.This has been done through this IMG activity:


10/44

10

To simplify the configuration the step definition of an existing Change Request Type can be copied and adapted to thespecified by the process definition (original - before adaptation):

Adapted to this process


11/44

11

For regular Business Workflow-based processes it would be necessary to assign processors to the Change RequestSteps through the MDG IMG activity Assign Processor to Workflow/Change Request Step number.

For regular Business

Workflow based processes

only. Not needed here.


12/44

12

For the Rule Based Workflow this is been done in the BRF plus (more specific: in the decision tables). The BRF plusconfiguration also can be started from the MDG IMG:


13/44

13

The Single Value Decision Table shows what happens if the process is in a specific step (here: 01 - Add ConnectionDetails) and an action (like 05 Finalize Processing) is triggered by a pushbutton on the corresponding UI:

For Finalize Processing the system moves into Change Request Step 03 Approve and the new Change RequestStatus is 04 Final Check to be performed. The Condition Alias links the 3 decision tables together. For examplehere the condition alias is set to APP which is used to determine the user responsible for executing this step from theUser Agent Decision Table.

The User Agent Decision Table shows for Condition Alias APP that the system will change into CR Step 2 ApproveChange Request and that the processor will be a special user, specifically the Initiator/Last-Step User of the workflowprocess.


14/44

14

Note: This is done to simplify the definition of this exercise. Typically the workflow would be sent to users with aspecific role/position in the organization, shown here as a reference for you (not applicable to this exercise). In thiscase, shown below, the processor would be defined by all users that are assigned to position 50010131- FlightOperations Manager.

As a further reference, not needed for this exercise, any relevant users would need to be assigned to the relevantorganizations (transaction PPOME):

Organization: Search for Flight*. Check if your user is assigned to the positions: Flight Product Manager, FlightApplication Expert, and Flight Operations Manager

If it is not assigned:

Search for your User

Drag&Drop User

Hint: You can display the Organization ID by clicking on Column Configuration (Icon on the upper right corner).

Repeat this for all positions.

Save


15/44

15

Run the applicationStart the application (transaction NWBC => Governance for Flight Data Model). Replace XX with your group number.

Request:

SFO

LH XX01


16/44

16

Process:


17/44

17

Approve:


18/44

18

Background Completed!

You have executed the pre-configured business process flow and understand the design of the rules based workflowbuilt via the decision tables.

Further Info for Technical Experts

Generated TablesIf you are curious to see where the data is stored. Take a look at the MDG persistency. By using transactionMDG_DATA_MODEL enter the data model as SF and you shall be directed to the MDG repository.


19/44

19

EXERCISE 1SIMPLIFY THE REQUESTORS USER INTERFACE

Solution Exercise 1

See below for the step-by-step solution in detail.

Step-by-step Solution

Simplify the Requestor UI by providing him only those fields that he has knowledge of.

There are several ways to simplify the process, e.g.:

Configure the UI (and remove the Checks for this field)

Exchange the UI (and remove the Checks for this field). We will do this in order to demonstrate how a verydifferent UI could be attached to a change request step very easily

Simplified User Interface (this has been prepared for you)

The standard UI Configuration has been copied to a customer specific configuration:


20/44

20


21/44

21

Exchange the UI in the first step of your Change Request Type


22/44

22

Run the application againthe new UI will be shown:


23/44

23

Exercise 1 Completed!

You have attached a simple user interface to the requestor process step, by following the below mentioned steps someof them were already done for you.

- Create a copy of the template configuration for the generic MDG UI USMD_ENTITY_VALUE2, including copiesof the configurations for the contained components FPM_OIF_COMPONENT and FPM_IDR_COMPONENT.

- Link the application configuration to the appropriate process step


24/44

24

EXERCISE 2ENHANCE THE DECISION TABLES WITH THEADDITIONAL PROCESS STEP AND ACTION

Solution Exercise 3

See below for the step-by-step solution in detail

Step-by-step Solution

In this exercise we enhance the process we executed in Exercise 1. The processor of Change Request Step 01 -Processing should add a landing quota. Depending on his knowledge he might be able to do this easily or it might bea problem for him which slows down the process. Therefore a new Change Request Step should be introduced thatadds the flexibility to forward the task of checking the landing quota to a specialist that is able to do this easily.


25/44

25

Add new field to the Data Model (this has been prepared for you)You can open the Configuration Workbench and have a look at enhanced data model SF:


26/44

26

Add a new User Interface (this has been prepared for you) - ZMDG_SF_APPL_FLIGHT_CQ


27/44

27

Use this UI Configuration (ZMDG_SF_APPL_FLIGHT_CQ) in the Change Request Steps- 01 - Processing- 03 Final Check

And use the simple one (ZMDG_SF_APPL_FLIGHT_RQ) in the 02 Revision Change Request Step, as thishas tobe carried out by the requester again (if the request gets rejected).

Now the field is available for the processor. But he might not be able to get this information. So he needs to be able toforward that task to somebody else. For this we need to introduce a new CR Step (and corresponding actions) and linkit to the Workflow. In order to reduce the complexity of the exercise the same UI will be used as in step 01 Processing.


28/44

28

Add new Change Request Step (to be done by you Change Request Type specific)

Add CR Step for the Landing Quota Specialist:


29/44

29

Add new Action (this has been prepared for you)

In order to navigate from the Processor Step to the Landing Quota Step actions need to be defined. This has beenprepared as this is a global setting that can be reused by all Change Request Types. Please check the followingentries:


30/44

30

Add new Change Request Step Type (this has been prepared for you)

A new Step Type has been created to link the CR Step to the Actions. Please check:


31/44

31

Assign Actions:

Add Status (this has been prepared for you):

New Status for the Landing Quota Step:


32/44

32


33/44

33

Enhance the Rule Based Workflow (to be done by you)

The new step type has to be used in step 01 Processing as this is the place where the new CR Step 04 CheckLanding Quota should be initiated (via the Action CQ Check Landing Quota).

For this you need to change the BRF decision tables for the rule based workflow:

Note: This is case sensitive, be sure to enter an upper case X.


34/44

34

Save and activate

If you run the process again, the new action should appear on the UI (but cannot be executed in the moment).


35/44

35

In order to activate the new CR step, it has to be added to the BRF decision table. The rule is: If the (previous) stepcurrently is 01 Processing / Add Connection Details and the (previous) action is CQ Check Quota move to thenew step 04 Check Landing Quota

Add this line to the decision table:

Step1:


36/44

36

Step 2:

Save and activate (ignore warnings).

The Condition Alias QUO is needed to start the User determination. The assigned Step Type will be a reuse of 03 Process as this has the original actions assigned (w/o Check Landing Quota).

Save and activate!

We also need to add the configuration to navigate from the Landing Quota Confirmation to the Approvestep. Extrahintyou can copy and paste the current definition for the CR Previous Step 01 and Previous Action 05 andsimply change the new value for the copied row for CR Previous Step 04.


37/44

37

Or, using hint:

Add the Step specific UI Configuration:

Note: First exit and re-enter the MDGIMG transaction. Due to caching in the IMG, the newly defined step 04

will only show after this is done.

With this you are done and can run the new process (see next pages)


38/44

38


39/44

39

Requesterreduced UI complexity


40/44

40

Processoradditional field (full UI) and additional action to include more processors

Select Check Quota option. Window will close but step has been processed.


41/44

41

Processor / Check Landing QuotaFull UI with actions to Finalize Processing / Send for Revision


42/44

42

Approverfull UI (with Landing Quota Confirmation ID)


43/44

43

Exercise 3 Completed!

You have understood the nuances behind configuring, building and changing the Rule Based Workflow decision tablesvia adding a new process step including a step specific action called Check Quota in this exercise


44/44

2012 by SAP AG. All rights reserved.

SAP and the SAP logo are registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo are trademarks orregistered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and the Sybase logo are registered trademarks of Sybase Inc.Sybase is an SAP company. Crossgate is a registered trademark of Crossgate AG in Germany and other countries. Crossgate is an SAP company.

rtftftftfdrtrdtdtrdp363 solutiyftdtdtdtdtdtdtddons

Documents