How To Fill MDG Rule-Based Workflow Decision Tables

Abdullah Azzouni, Principal Consultant
December, 2013
MDG BRF+ Decision Tables
2014 SAP AG or an SAP affiliate company. All rights reserved. 2
Agenda
Introduction
MDG BRF+Decision Tables
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
Introduction
Introduction
BRF+ is a generic tool; not specific to MDG.
MDG utilizes BRF+ in many ways; one of which is to determine the
workflow process and handling agents.
Workflow template WS60800086 was built specifically for MDG to use the
BRF+ application in order to dynamically control MDG processes. This
workflow template is not to be changed using conventional workflow
development tools.
From the view point of MDG, this workflow template is a black box. The
BRF+ application is the window through which MDG controls the behavior
of the process.
Each MDG change request type has its own BRF+ application built
automatically by the corresponding MDG IMG node to have the same
application structures.
Introducti on Cont.
The key elements in each applications are three decision tables: a table to
determine the next step, a table to determine dialog step agents, and a
table to determine background step type.
These tables work with some MDG customization tables.
MDG BRF+Decision Tables
Next Step Decision Table
14 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+ Deci sion Tables Cont.
Dialog Step Agent Decision Table
5 columns*
Input Columns
Condition Alias
Result Columns
Agent Group
Step Type
Agent Type
Agent Value
Background Step Type Decision Table
4 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-Step
Decision
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. Alias
in agent or
background
table?
Agent
Table
Back-
ground
Table
- Step Type
- Agent (Type & ID)
- Processing Pattern
Cond. Alias
Cond. Alias
Status of Change Request V_USMD130C
Master Data GovernanceGeneral Settings Process Modeling Change Requests Edit Statuses of Change Requests
Priorities of Change Request V_USMD210C
Master Data GovernanceGeneral Settings Process Modeling Change Requests Define Priorities for Change Requests
Reasons of Change Request V_USMD211C
Master Data GovernanceGeneral Settings Process Modeling Change Requests Define Reasons for Change Requests
Rejection Reasons of Change Request V_USMD212C
Master Data GovernanceGeneral Settings Process Modeling Change Requests Define Rejection Reasons for Change
Requests
Actions for Change Request UIs V_USMD220C
Master Data GovernanceGeneral Settings Process Modeling Change Requests Define Actions for Change Request UIs
Step Types and Assigned Actions V_USMD230C &V_USMD2301
Master Data GovernanceGeneral Settings Process Modeling Change Requests Define Step Types and Assign Actions
Change Request Steps for Rule-Based WorkflowV_USMD202C_SSW
Master Data GovernanceGeneral Settings Process Modeling Change Requests Define Steps for Rule-Based Workflow
Requester
Approver
Reviewer
Start
End
Things to note:
- Decision tables model the workflow behavior. The requester step triggers
the start of the workflow. So, technically, the requester step is outside the
workflow.
- 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.
How to Model for MDG BRF+Decision Tables
Each step in the diagram needs to contain the following:
How to Model for MDG BRF+ Decisi on Tables
<StepNumber>
<Condition Alias>
<Step/Process Type>
<Status> <Action>
<Action>
Process Re-modeled
Background Step
Dialog Step
Process Re-modeled
00
Request
10
REV
3
20
APP
2
30
ACT
05
60
COM
99
40
RES
4
50
RLB
08
02 01
03
05
06
06
05
06
05
04
03
03
31
<>31 07
07 08
02
*
REV: Review RES: Resubmit
APP: Approve RLB: Rollback
ACT: Activate COM: Complete
00
Request
10
REV
3
20
APP
2
30
ACT
05
60
COM
99
40
RES
4
50
RLB
08
02 01
03
05
06
06
05
06
05
04
03
03
31
<>31 07
07 08
02
*
Prev. Step Prev. Action Cond. Alias New Status New Step
00 REV 02 10
Model to Next-Step Decision Table Cont.
00
Request
10
REV
3
20
APP
2
30
ACT
05
60
COM
99
40
RES
4
50
RLB
08
02 01
03
05
06
06
05
06
05
04
03
03
31
<>31 07
07 08
02
*
10 05 APP 01 20
00
Request
10
REV
3
20
APP
2
30
ACT
05
60
COM
99
40
RES
4
50
RLB
08
02 01
03
05
06
06
05
06
05
04
03
03
31
<>31 07
07 08
02
*
10 06 RES 03 40
00
Request
10
REV
3
20
APP
2
30
ACT
05
60
COM
99
40
RES
4
50
RLB
08
02 01
03
05
06
06
05
06
05
04
03
03
31
<>31 07
07 08
02
*
20 03 ACT 05 30
00
Request
10
REV
3
20
APP
2
30
ACT
05
60
COM
99
40
RES
4
50
RLB
08
02 01
03
05
06
06
05
06
05
04
03
03
31
<>31 07
07 08
02
*
20 04 RES 03 40
00
Request
10
REV
3
20
APP
2
30
ACT
05
60
COM
99
40
RES
4
50
RLB
08
02 01
03
05
06
06
05
06
05
04
03
03
31
<>31 07
07 08
02
*
40 07 REV 02 10
00
Request
10
REV
3
20
APP
2
30
ACT
05
60
COM
99
40
RES
4
50
RLB
08
02 01
03
05
06
06
05
06
05
04
03
03
31
<>31 07
07 08
02
*
40 08 RLB 06 50
00
Request
10
REV
3
20
APP
2
30
ACT
05
60
COM
99
40
RES
4
50
RLB
08
02 01
03
05
06
06
05
06
05
04
03
03
31
<>31 07
07 08
02
*
30 31 COM 05 60
00
Request
10
REV
3
20
APP
2
30
ACT
05
60
COM
99
40
RES
4
50
RLB
08
02 01
03
05
06
06
05
06
05
04
03
03
31
<> 31 07
07 08
02
*
30 <>31 REV 07 10
00
Request
10
REV
3
20
APP
2
30
ACT
05
60
COM
99
40
RES
4
50
RLB
08
02 01
03
05
06
06
05
06
05
04
03
03
31
<>31 07
07 08
02
*
50 COM 06 60
Table after completing all steps and branches
00 REV 02 10
10 05 APP 01 20
10 06 RES 03 40
20 03 ACT 05 30
20 04 RES 03 40
40 07 REV 02 10
40 08 RLB 06 50
30 31 COM 05 60
30 <>31 REV 07 10
50 COM 06 60
00
Request
10
REV
3
20
APP
2
30
ACT
05
60
COM
99
40
RES
4
50
RLB
08
02 01
03
05
06
06
05
06
05
04
03
03
31
<>31 07
07 08
02
*
Cond. Alias Group Step Type Agent Type Agent
REV 1 3 US <user name>
Model to Dialog-Step-Agent Decision Table Cont.
Cond. Alias Group Step Type Agent Type Agent
REV 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: J ob (Org. Structure)
S: Position (Org. Structure)
AG: Role (Security Role)
SU: Special User (INIT: Initiator, LAST: Previous Agent)
00
Request
10
REV
3
20
APP
2
30
ACT
05
60
COM
99
40
RES
4
50
RLB
08
02 01
03
05
06
06
05
06
05
04
03
03
31
<>31 07
07 08
02
*
Cond. Alias Group Processing Pattern
ACT 1 05
Model to Dialog-Step-Agent Decision Table Cont.
Cond. Alias Group Processing Pattern
ACT 1 05
RLB 1 08
COM 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 (dont bypass snap shot)
06: Activate (bypass snap shot)
07: Validate change request
08: Rollback change request
98; Error
99: Complete
Summary
Summary
BRF+is a generic tool; MDG utilizes BRF+in many ways Change Request
workflow routing is one of them
This document shows a simple example; the key point here is how the decision
tables tie back to the different customization tables
Columns that were ignored can be used in modeling the process; they were just
left out for the simplicity of this example for example, priority can be used so
that the same action on a CR could result in different paths for high priority than
for low priority
References
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.
Thank you
Contact information:
Abdullah Azzouni
Principal Consultant
Palo Alto, CA
a.azzouni@sap.com
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 an
SAP 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.epxfor additional
trademark 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 or
SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and
services, 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 related
presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP AGs or its affiliated
companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be
changed 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 uncertainties
that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking
statements, 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 Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die
ausdrckliche schriftliche Genehmigung durch SAP AG oder ein SAP-Konzernunternehmen nicht gestattet.
SAP und andere in diesem Dokument erwhnte Produkte und Dienstleistungen von SAP sowie die dazugehrigen Logos sind Marken oder
eingetragene Marken der SAP AG (oder von einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen Lndern 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 knnen Softwarekomponenten auch anderer Softwarehersteller enthalten.
Produkte knnen lnderspezifische Unterschiede aufweisen.
Die vorliegenden Unterlagen werden von der SAP AG oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschlielich zu Informations-
zwecken. Die SAP AG oder ihre Konzernunternehmen bernehmen keinerlei Haftung oder Gewhrleistung fr Fehler oder Unvollstndigkeiten in
dieser Publikation. Die SAP AG oder ein SAP-Konzernunternehmen steht lediglich fr Produkte und Dienstleistungen nach der Magabe ein, die in der
Vereinbarung ber die jeweiligen Produkte und Dienstleistungen ausdrcklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zustzliche
Garantie zu interpretieren.
Insbesondere sind die SAP AG oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer zugehrigen Prsentation
dargestellte Geschftsablufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu verffentlichen. Diese Publikation oder
eine zugehrige Prsentation, die Strategie und etwaige knftige Entwicklungen, Produkte und/oder Plattformen der SAP AG oder ihrer Konzern-
unternehmen knnen von der SAP AG oder ihren Konzernunternehmen jederzeit und ohne Angabe von Grnden unangekndigt gendert werden.
Die in dieser Publikation enthaltenen Informationen stellen keine Zusage, kein Versprechen und keine rechtliche Verpflichtungzur Lieferung von
Material, Code oder Funktionen dar. Smtliche vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch die
die tatschlichen Ergebnisse von den Erwartungen abweichen knnen. Die vorausschauenden Aussagen geben die Sicht zu dem Zeitpunkt wieder,
zu dem sie gettigt wurden. Dem Leser wird empfohlen, diesen Aussagen kein bertriebenes Vertrauen zu schenken und sich bei Kaufentscheidungen
nicht auf sie zu sttzen.

How To Fill MDG Rule-Based Workflow Decision Tables

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

How To Fill MDG Rule-Based Workflow Decision Tables

Uploaded by

Copyright:

Available Formats

Abdullah Azzouni, Principal Consultant

You might also like