abdullah azzouni, principal consultant december, 2013...• change request steps for rule-based...

Abdullah Azzouni, Principal ConsultantDecember, 2013

MDG BRF+ Decision Tables

© 2014 SAP AG or an SAP affiliate company. All rights reserved. 2

Agenda

Introduction


MDG Customization Tables

Process to be Modeled

How to Model for MDG BRF+ Decision Tables

Process Re-modeled

Model to Next-Step Decision Table

Model to Dialog-Step-Agent Decision Table

Model to Background-Step Decision Table

References

MDG BRF+ Decision TablesIntroduction


Introduction

• BRF+ is a generic tool; not specific to MDG.

• MDG utilizes BRF+ in many ways; one of which is to determine theworkflow process and handling agents.

• Workflow template WS60800086 was built specifically for MDG to use theBRF+ application in order to dynamically control MDG processes. Thisworkflow template is not to be changed using conventional workflowdevelopment tools.

• From the view point of MDG, this workflow template is a black box. TheBRF+ application is the window through which MDG controls the behaviorof the process.

• Each MDG change request type has its own BRF+ application builtautomatically by the corresponding MDG IMG node to have the sameapplication structures.


Introduction – Cont.

• The key elements in each applications are three decision tables: a table todetermine the next step, a table to determine dialog step agents, and atable to determine background step type.

• These tables work with some MDG customization tables.

MDG BRF+ Decision TablesMDG BRF+ Decision Tables



• Next Step Decision Table14 columns*

• Input Columns• Previous Step• Previous Action• Change Request Priority• Change Request Reason• Change Request Rejection Reason• Change Request Parent Step• Change Request Parent Step Agent Group

• Result Columns• Condition Alias• New Step• New Change Request Status• Hours to Completion• Merge Type• Merge Parameter• Dynamic Agent Selection Service

* For simplicity reasons, only columns in bold are considered in this how-to guide


MDG BRF+ Decision Tables – Cont.

• Dialog Step Agent Decision Table5 columns*

• Input Columns• Condition Alias

• Result Columns• Agent Group• Step Type• Agent Type• Agent Value




• Background Step Type Decision Table4 columns*

• Input Columns• Condition Alias

• Result Columns• Agent Group• Processing Pattern• Service Name




How do these tables work?• First, find out what my next step is.

Workflow

Next-StepDecision

Table

- Prev. Step- Prev. Action

- Condition Alias- New Step- New Status



How do these tables work?• Second, where is the condition alias defined?

Workflow

Cond. Aliasin agent orbackground

table?

AgentTable

Back-groundTable

- Step Type- Agent (Type & ID)

- Processing Pattern

Cond. Alias

Cond. Alias

MDG BRF+ Decision TablesMDG Customization Tables



• Status of Change Request V_USMD130CMaster Data Governance General Settings Process Modeling Change Requests Edit Statuses of Change Requests



• Priorities of Change Request V_USMD210CMaster Data Governance General Settings Process Modeling Change Requests Define Priorities for Change Requests



• Reasons of Change Request V_USMD211CMaster Data Governance General Settings Process Modeling Change Requests Define Reasons for Change Requests



• Rejection Reasons of Change Request V_USMD212CMaster Data Governance General Settings Process Modeling Change Requests Define Rejection Reasons for ChangeRequests



• Actions for Change Request UIs V_USMD220CMaster Data Governance General Settings Process Modeling Change Requests Define Actions for Change Request UIs



• Step Types and Assigned Actions V_USMD230C & V_USMD2301Master Data Governance General Settings Process Modeling Change Requests Define Step Types and Assign Actions



• Change Request Steps for Rule-Based Workflow V_USMD202C_SSWMaster Data Governance General Settings Process Modeling Change Requests Define Steps for Rule-Based Workflow

MDG BRF+ Decision TablesProcess to be Modeled



Requester

Approver

Reviewer

Start

End


Things to note:

- Decision tables model the workflow behavior. The requester step triggersthe start of the workflow. So, technically, the requester step is outside theworkflow.

- All output options of each step must be modeled completely.

- Status of each step must be modeled.

- Background steps such as activation and verification need to be modeled.


MDG BRF+ Decision TablesHow to Model for MDG BRF+ Decision Tables


Each step in the diagram needs to contain the following:

How to Model for MDG BRF+ Decision Tables

<Step Number>

<Condition Alias>

<Step/Process Type>

<Status> <Action>

<Action>

MDG BRF+ Decision TablesProcess Re-modeled


Background Step

Dialog Step

Process Re-modeled

00Request

10REV

3

20APP

2

30ACT05

60COM

99

40RES

4

50RLB08

02 01

03

05

06 06

05

06

05

04

03

03

31

<> 3107

07 08

02

*

REV: Review RES: ResubmitAPP: Approve RLB: RollbackACT: Activate COM: Complete

MDG BRF+ Decision TablesModel to Next-Step Decision Table


Model to Next-Step Decision Table

00Request

10REV

3

20APP

2

30ACT05

60COM

99

40RES

4

50RLB08

02 01

03

05

06 06

05

06

05

04

03

03

31

<> 3107

07 08

02

*

Prev. Step Prev. Action Cond. Alias New Status New Step00 … REV 02 10


Model to Next-Step Decision Table – Cont.

00Request

10REV

3

20APP

2

30ACT05

60COM

99

40RES

4

50RLB08

02 01

03

05

06 06

05

06

05

04

03

03

31

<> 3107

07 08

02

*

Prev. Step Prev. Action Cond. Alias New Status New Step10 05 APP 01 20



00Request

10REV

3

20APP

2

30ACT05

60COM

99

40RES

4

50RLB08

02 01

03

05

06 06

05

06

05

04

03

03

31

<> 3107

07 08

02

*

Prev. Step Prev. Action Cond. Alias New Status New Step10 06 RES 03 40



00Request

10REV

3

20APP

2

30ACT05

60COM

99

40RES

4

50RLB08

02 01

03

05

06 06

05

06

05

04

03

03

31

<> 3107

07 08

02

*

Prev. Step Prev. Action Cond. Alias New Status New Step20 03 ACT 05 30



00Request

10REV

3

20APP

2

30ACT05

60COM

99

40RES

4

50RLB08

02 01

03

05

06 06

05

06

05

04

03

03

31

<> 3107

07 08

02

*

Prev. Step Prev. Action Cond. Alias New Status New Step20 04 RES 03 40



00Request

10REV

3

20APP

2

30ACT05

60COM

99

40RES

4

50RLB08

02 01

03

05

06 06

05

06

05

04

03

03

31

<> 3107

07 08

02

*

Prev. Step Prev. Action Cond. Alias New Status New Step40 07 REV 02 10



00Request

10REV

3

20APP

2

30ACT05

60COM

99

40RES

4

50RLB08

02 01

03

05

06 06

05

06

05

04

03

03

31

<> 3107

07 08

02

*

Prev. Step Prev. Action Cond. Alias New Status New Step40 08 RLB 06 50



00Request

10REV

3

20APP

2

30ACT05

60COM

99

40RES

4

50RLB08

02 01

03

05

06 06

05

06

05

04

03

03

31

<> 3107

07 08

02

*

Prev. Step Prev. Action Cond. Alias New Status New Step30 31 COM 05 60



00Request

10REV

3

20APP

2

30ACT05

60COM

99

40RES

4

50RLB08

02 01

03

05

06 06

05

06

05

04

03

03

31

<> 3107

07 08

02

*

Prev. Step Prev. Action Cond. Alias New Status New Step30 <> 31 REV 07 10



00Request

10REV

3

20APP

2

30ACT05

60COM

99

40RES

4

50RLB08

02 01

03

05

06 06

05

06

05

04

03

03

31

<> 3107

07 08

02

*

Prev. Step Prev. Action Cond. Alias New Status New Step50 … COM 06 60



Table after completing all steps and branchesPrev. Step Prev. Action Cond. Alias New Status New Step00 … REV 02 1010 05 APP 01 2010 06 RES 03 4020 03 ACT 05 3020 04 RES 03 4040 07 REV 02 1040 08 RLB 06 5030 31 COM 05 6030 <> 31 REV 07 1050 … COM 06 60

MDG BRF+ Decision TablesModel to Dialog-Step-Agent Decision Table


Model to Dialog-Step-Agent Decision Table

00Request

10REV

3

20APP

2

30ACT05

60COM

99

40RES

4

50RLB08

02 01

03

05

06 06

05

06

05

04

03

03

31

<> 3107

07 08

02

*

Cond. Alias Group Step Type Agent Type AgentREV 1 3 US <user name>


Model to Dialog-Step-Agent Decision Table – Cont.

Cond. Alias Group Step Type Agent Type AgentREV 1 3 US <user name>APP 1 2 AG <security role>RES 1 4 SU INIT

Table after completing all steps

Possible Agent Types• US: User (User Master)• O: Organizational Unit (Org. Structure)• C: Job (Org. Structure)• S: Position (Org. Structure)• AG: Role (Security Role)• SU: Special User (INIT: Initiator, LAST: Previous Agent)

MDG BRF+ Decision TablesModel to Background-Step Decision Table


Model to Background-Step Decision Table

00Request

10REV

3

20APP

2

30ACT05

60COM

99

40RES

4

50RLB08

02 01

03

05

06 06

05

06

05

04

03

03

31

<> 3107

07 08

02

*

Cond. Alias Group Processing PatternACT 1 05


Model to Dialog-Step-Agent Decision Table – Cont.

Cond. Alias Group Processing PatternACT 1 05RLB 1 08COM 1 99

Table after completing all steps

Possible Processing Types• 01: Dialog (not applicable for this background step table)• 02: Call synch method• 03: Call sub-workflow• 04: Call data replication• 05: Activate (don’t bypass snap shot)• 06: Activate (bypass snap shot)• 07: Validate change request• 08: Rollback change request• 98; Error• 99: Complete

MDG BRF+ Decision TablesSummary


Summary

• BRF+ is a generic tool; MDG utilizes BRF+ in many ways – Change Requestworkflow routing is one of them

• This document shows a simple example; the key point here is how the decisiontables tie back to the different customization tables

• Columns that were ignored can be used in modeling the process; they were justleft out for the simplicity of this example – for example, priority can be used sothat the same action on a CR could result in different paths for high priority thanfor low priority

MDG BRF+ Decision TablesReferences


References

SCN: http://scn.sap.com/community/mdm/master-data-governance

MDG Extensibility Guide: http://scn.sap.com/docs/DOC-7858

SAP Help: http://help.sap.com/mdg


© 2014 SAP AG or an SAP affiliate company.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 or anSAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additionaltrademark information and notices.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,and SAP AG or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG orSAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products andservices, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business outlined in this document or any relatedpresentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP AG’s or its affiliatedcompanies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may bechanged by SAP AG or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertaintiesthat could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-lookingstatements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.


© 2014 SAP AG oder ein SAP-Konzernunternehmen.Alle Rechte vorbehalten.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne dieausdrückliche schriftliche Genehmigung durch SAP AG oder ein SAP-Konzernunternehmen nicht gestattet.

SAP und andere in diesem Dokument erwähnte Produkte und Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken odereingetragene Marken der SAP AG (oder von einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen Ländern weltweit.Weitere Hinweise und Informationen zum Markenrecht finden Sie unter http://global.sap.com/corporate-de/legal/copyright/index.epx.

Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten.

Produkte können länderspezifische Unterschiede aufweisen.

Die vorliegenden Unterlagen werden von der SAP AG oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschließlich zu Informations-zwecken. Die SAP AG oder ihre Konzernunternehmen übernehmen keinerlei Haftung oder Gewährleistung für Fehler oder Unvollständigkeiten indieser Publikation. Die SAP AG oder ein SAP-Konzernunternehmen steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die in derVereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzlicheGarantie zu interpretieren.

Insbesondere sind die SAP AG oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer zugehörigen Präsentationdargestellte Geschäftsabläufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu veröffentlichen. Diese Publikation odereine zugehörige Präsentation, die Strategie und etwaige künftige Entwicklungen, Produkte und/oder Plattformen der SAP AG oder ihrer Konzern-unternehmen können von der SAP AG oder ihren Konzernunternehmen jederzeit und ohne Angabe von Gründen unangekündigt geändert werden.Die in dieser Publikation enthaltenen Informationen stellen keine Zusage, kein Versprechen und keine rechtliche Verpflichtung zur Lieferung vonMaterial, Code oder Funktionen dar. Sämtliche vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch diedie tatsächlichen Ergebnisse von den Erwartungen abweichen können. Die vorausschauenden Aussagen geben die Sicht zu dem Zeitpunkt wieder,zu dem sie getätigt wurden. Dem Leser wird empfohlen, diesen Aussagen kein übertriebenes Vertrauen zu schenken und sich bei Kaufentscheidungennicht auf sie zu stützen.

abdullah azzouni, principal consultant december, 2013...• change request steps for rule-based...

Documents