MDM with BPM
Product Master Data
Agenda
1. MDM and BPM
2. The Demo Scenario
The Sample Process
System Architecture
The Sample Repository
3. How to implement an MDM Process on CE
BPM
BRM
Tools to access MDM from BP
Agenda
1. MDM and BPM
2. The Demo Scenario
The Sample Process
System Architecture
The Sample Repository
3. How to implement an MDM Process on CE
BPM
BRM
MDM & BPM
Master Data Challenges
Master Data Management
has to deliver a solution for
supporting business
processes
which requires
high quality of master data
to avoid
Reduced sales effectiveness
Suboptimal / ineffective decision
Delayed Go-to-Market steps
SAP Master Data Management (MDM) together with SAP Business Process
Managament (BPM offer options to optimize MDM internal tasks with integration of
user processes for activities like
Create
Update
Delete
for different master data objects.
After maintenance of master data the regular user interactions are
approval
and
reworking
steps. This one may be done by
different users
from
varying
departments
depending on specific data in the relevant master data records.
MDM & BPM
Pain Points for MDM Processes
On projects using SAP Master Data Management the following pain points are stated:
Standard workflows for unspecified master data objects cannot be delivered
MDM Workflows are not usable across systems
MDM Workflows cannot be used in WEB scenarios without additional implementations
MDM & BPM
How to make users happy
The shipped
demo scenario
is designed to demonstrate maintainance of
master data
as a solution with integration of different SAP Systems
with a WEB based UI for maintenance and approval implemented on SAP
NetWeaver Composite Environment (SAP CE – is able to avoid client rollout and
provides adaptable user interfaces)
with validations to ensure data quality requirements.
Benefits:
Strong inbound and outbound capabilities within SAP MDM Import & Syndication.
Decision Rules can be adapted during runtime supported by SAP Busines Rules
Management
Processes handled by SAP Business Process Management (SAP BPM) as
integrator.
Agenda
1. MDM and BPM
2. The Demo Scenario
The Sample Process
System Architecture
The Sample Repository
3. How to implement an MDM Process on CE
BPM
BRM
Agenda
1. MDM and BPM
2. The Demo Scenario
The Sample Process
System Architecture
The Sample Repository
3. How to implement an MDM Process on CE
BPM
BRM
Tools to access MDM from BP
The Sample Process
Maintenance of Product Master Data
Product master data are to be
created from scratch or as a copy of an existing product
updated
Creation and update require approval
Approver depends on product category
In case of rejection rework or cancelling of the process should be possible
Approved product data should be syndicated in order to synchronize them with a
backend system (for instance ERP)
MDM is the master system for product numbers, a key mapping with the backend
systems should be maintained
Agenda
1. MDM and BPM
2. The Demo Scenario
The Sample Process
System Architecture
The Sample Repository
3. How to implement an MDM Process on CE
BPM
BRM
System Architecture
Involved Systems
PI7.3
MDM7.1
CE7.3
MDM WebService MDM Java API
MDM Syndication
IDoc or ES
Intermediate Message Event
(WebService)
Agenda
1. MDM and BPM
2. The Demo Scenario
The Sample Process
System Architecture
The Sample Repository
3. How to implement an MDM Process on CE
BPM
BRM
Tools to access MDM from BP
MDM Demo Repository
Products+Partners
The shipped
SAP MDM DEMO-Repository
contains two
different master data objects:
Products and
PARTNERS
All
product
related parts are shipped as
Standard SAP MDM Business Content for Products.
All
PARTNER
related parts are extensions made by SAP Consulting.
The purpose for this part is to
demonstrate capabilities in SAP MDM
.
All related tables are in UPPER case letters.
MDM Tuples are only used in this context.
To understand the Repository structure the next two slides show
the important parts of the data model.
MDM Data Model of Demo-Repository
MDM Data Model of Demo-Repository
MDM Reference Data I
Products
Most of existing reference data used by Products are imported from IDES system.
For the Taxonomy Table Categories and its Attributes and related images and
properties we used examples related to the imported products.
MDM Reference Data II
Partners
The Reference data used for Partners were created manually.
BANK ACCOUNTS:
contains 31 real existing bank names and their Bank Codes.
CONTACT TYPES:
outlines possible type of contacts to segregate detailed information
about a specific partner
FORMS OF ADRESSES:
defines possible values for appellation of a person like
Mr., Mrs., Dr. Prof. etc.
PHONE TYPES:
defines a set of possible phone communication types like
Faximile, landline phon, mobile, skype etc.
MDM Reference Data III
Additionals & empty Reference Tables
DOCUMENT STORAGE
This table is used to provide an example for predefined sets of attached documents like a list of
logos etc. Entries are made manually. This is more or less to demonstrate how such a complex
structure can be used easily.
Because of restrictions in shipments of particular reference data tables are keept empty:
•
Category Hierarchies
•
Class Hierarchies
•
Classes
Usage of Outbound Interface
Syndication of Product Records
To demonstrate the capability of providing master data to external systems there is
implemented an SAP MDM Syndication for Products which delivers XML content.
MDM Validations
MDM Validations are used to assure data quality and data consistency.
Error-Validations will prevent to change a record which will not fit all the requirements.
Warnings are used to inform the user about missing data or unsuitable data
combinations.
MDM Validation Construct requires
to deliver a „false“ Value to get the
Validation message.
So a negation of the construct is
required to implement.
The validation on the right prevents
from storing any records which may
Agenda
1. MDM and BPM
2. The Demo Scenario
The Sample Process
System Architecture
The Sample Repository
3. How to implement an MDM Process on CE
BPM
BRM
From Operational Efficiency to Business Agility
Business
Agility
Business Process Reengineering
Enterprise Resource Planning
Operational
Efficiency
Business Network Transformation
Business Process Platform
1990s 2000s 2010s
End-to-end SOA Infrastructure – TODAY
Enabling Managed Process Flexibility
Service & Event
SOA
SOA Inter-
operability
Service Bus
User Interface
Service & Event
Composition
Business Process
Management
UI Composition
Information
Composition
Business Rules
Management
Desktop
Mobile
Portal
Forms
Wiki/Blog
Pervasive
Voice
Search
A
p
p
lic
a
ti
o
n
M
o
n
ito
ri
n
g
SOA Design
Governance
Connectivity &
SOA Management
C
o
m
p
o
s
it
io
n
E
n
v
iro
n
m
e
n
t
e
s
s
e
gra
ti
on
SOA
Composition
Java Application
Server
Robust, enterprise-
class
Java EE 5
application server
Eclipse Development
Environment
SAP NetWeaver
Developer Studio
: Eclipse
based development and
modeling environment
Model-Driven Development and Deployment With
SAP NetWeaver Composition Environment
Pr
o
c
e
s
s
e
s
Event Flow / Rules
Role
SAP NetWeaver
BPM
for process
composition
SAP NetWeaver
BRM
for rules
composition
V
ie
w
s
Portal and Web
Forms
Mobile
and Voice
Analytics
SAP NetWeaver Visual
Composer
for
model-driven UI development
(incl. analytics and voice)
Web Dynpro Java
SAP Interactive
Forms
by
Adobe
Federated
Portal
Network
Enterprise Services
Repository
and Registry
(ESR)
B
u
s
Se
rv
ic
e
s
New
service
Service
façade
Data
service
Enterprise
service
Basic
service
SAP Composite
Application
Framework
(CAF)
business object
modeling
Service Composer
service simplification,
adaptation, and
composition
Agenda
1. MDM and BPM
2. The Demo Scenario
The Sample Process
System Architecture
The Sample Repository
3. How to implement an MDM Process on CE
BPM
BRM
SAP NetWeaver Business Process Management
Delivered with SAP NetWeaver Composition Environment
Composition of “own practices”
State-of-the art business process composition
Embedded in an integrated composition environment
Superior integration with SAP Business Suite
Direct path from business view to process execution
■
Nothing “lost in translation”
■
Dynamic role-based views
■
Single active model
■
Flexible execution
■
Business Rules management (BRM)
■
Embedded rules in process to drive process agility
Automate processes where users are interacting with multiple systems:
Employee on-boarding, vacancy-to-hire, asset management, budget preparation,
forecasting, and automated procurement process
Handle critical business exceptions and events: Project issue management,
high-value claim, out-of-stock, and hourly worker exceptional scheduling
Common use cases / patterns
Processes that involve paper forms and approvals:
Loan applications, new customer accounts, and vacation requests
A
p
p
-C
e
n
tr
ic
e
n
tri
c
DESIGN PARTNERS
SAP NetWeaver BPM - Components
Direct path from business view to
process execution
Model and execute rule-based composite
business processes
Business-friendly graphical modeler based
on business process modeling notation
(BPMN)
Combine human interaction and system
integration in one model
Support key process concepts (workflow,
event, task, rules, context, roles, and UI)
throughout their life cycle
Process UI generation out of the process
context (data types)
Process reporting with defined reporting
Process server
Process
composer
Process
Desk
Process
desk
Key Process Meta Model Concepts
BPMN
Process
Context
Rules
Workflow
& Task
Create Claim Analyze Budget Impact Analyze Resource ImpactWorkflow
& Task
Create Claim Analyze Budget Impact Analyze Resource ImpactUI
UI
Data
Event
Product 15 min - order Product 15 min -Roles
Rules
Roles
Workflow
Event
Data
Process
Context
Rules
Roles
Workflow
Event
Data
Process
Context
Out of stock Product 15 min Reple- nish-ment order Out of stock Product 15 min Reple- nish-ment orderBusiness Process Modeling Notation
Orchestration and Choreography
Choreography
Modeling interaction between pools (not flow of
control!)
Representation as message flow
Orchestration
Modeling a process
flow of control in a single
internal (active) pool
Business Process Modeling Notation
Pools and Lanes
Pool
A Pool contains a single „BPMN- Process“
A sequence flow is constrained in exactly one pool
A Process diagramm may contain several pools
Differentiation between „active“ and „inactive“
(descriptive) pools
Only one active pool per model
A pool generally represents a logical collection of roles,
organizational units and systems
Lane
A pool may be divided into lanes
A lane generally represents a role or
an organizational unit
Business Process Modeling Notation
Gateways
Exclusive
Choice
Exclusive
Choice
Business Process Modeling Notation
Activities
Automated
Activity
Automated
Activity
Notification
Human
Activity
Human
Activity
Embedded
Subprocess
Business Process Modeling Notation
Events
Start
Event
Intermediate
message
Event
End
Event
Business Process Modeling Notation
Artifacts
Data Object for
Key Mapping
Data Object for
Approver Determination
Data Object for
Agenda
1. MDM and BPM
2. The Demo Scenario
The Sample Process
System Architecture
The Sample Repository
3. How to implement an MDM Process on CE
BPM
BRM
SAP NetWeaver
Business Rules Management (BRM)
Two Ways to Model Rules
Model Rules in the Context of a Business
Process using the Process Composer
Model rules as an independent rules
project using the Rules Composer
Many Ways to Integrate
Use Rules through an Automated Activity
Model Functions driven by Business
Rules
Use rules based mapping
Rules
Composer
Process
Desk
Rules
Management
Why Business Rules Management?
Externalize business rules from application code
Encapsulate rules as re-usable services
Increases flexibility, efficiency and control
Management and monitoring of rules is a critical
component of BPM
Serving business and IT
Why SAP NetWeaver BRM?
Robust tool for central business rules
management
Integrated path from process to rule
Perfect fit into SAP NetWeaver
Composition Environment
Enter Business Rules Management …
With BRM
You Get
Externalize
critical business
rules
Agile and maintainable
Systems
Model
executable
complex
business rules
Automate key business
decisions
(Centrally) manage business
rules
Consistent application of
corporate policy and
government regulations
Business Users can model
and manage critical business
rules
Visibility, accountability and
Error free Business
Rules
Roles
UI
Workflow
& Task
Event
Data
Process
Context
Create Claim Analyze Budget Impact Analyze Resource ImpactRules
Roles
UI
Workflow
& Task
Event
Data
Process
Context
Create Claim Analyze Budget Impact Analyze Resource Impact Out of stock Product 15 min Reple- nish-ment order Out of stock Product 15 min Reple- nish-ment orderSAP NetWeaver BRM & SAP NetWeaver BPM –
Integration Overview
Rules in BPM – Some Use cases
Complex rule based Decisions (Pricing, Credit Decisions etc.)
Responsibility Determination ( Rule based Task Assignment)
Recognition of Business Events
Routing Rules (Receiver Determination)
Parameter Thresholds & Tolerance (Constraint Rules)
Many Ways to Model Rules
Model with Rules Composer & use as a Rules Service
Model in the Context of a Business Process
And, Many Ways to Integrate
Rules Services through an Automated Activity
Use Rules as Mapping Transforms
Use Rules through EJB Functions
Use Rules from Human Task User Interfaces
The Rules Manager
Agenda
1. MDM and BPM
2. The Demo Scenario
The Sample Process
System Architecture
The Sample Repository
3. How to implement an MDM Process on CE
BPM
BRM
MDM Java API
API enables interaction with the
Master Data Server (MDS) to
perform various operations.
Exposes a granular and
comprehensive set of functions for
basic operations (searching/editing
data), advanced functionality
MDM Web Dynpro Components
Ready to use WD components for the following views/tasks:
Item Details – shows the field values of a MDM record
Result Set – shows a list of records, for instance the result of a search
Search
– provides a search form with different search criteria
Match – search for duplicate records
Compare – compare two records
Merge – merging similar records for consolidation
MDM Web Dynpro Components can be consumed :
by other custom Web Dynpro components to create a Web Dynpro application which can run
as a standalone application or in a portal environment.
directly by BPM
MDM Web Dynpro Components can be customized by:
MDM Web Dynpro Components
MDM Web Dynpro Components
Dashboard Application
Initial Screen
Wrapper Application
Result List
Search Form
Dashboard Application
Item Details Screen
Wrapper Component
When to use WD Components for MDM?
WD Components for MDM
+
–
Fast development
Fast adaption to schema
changes
You don‘t need to care about
MDM access
You get all dropdowns for free
Changing the UI by configuration
Mature in functionality, SAP has
responsibilty for errors
Restrictions regarding the layout
Configuration cannot be changed
for one componen instance ->
impacts on design
Configuration needs to be
transported separately
Custom Development
+
–
UI fits exactly to your needs
High development effort
Access to the MDM has to be
developed manually (access
layer with MDM Java API or
MDM Web Services)
All drop downs have to be
developed manually (MDM
lookups)
If you are satisfied with funtionality and the look&feel of the
standardized UI
If you have strong restrictions on time and budget
If you need a high sophisticated UI with funtionality that
If you are working with a staging area for performance reasons (Writing
to the MDM is the very last step)
MDM Web Services
Service-Enabling of MDM
Based on SOAP (Simple Object Access Protocol) and WSDL (Web Service description
Language) standards
No coding needed
Synchronous access to MDM
Generated Web Services are schema specific.
They can connect to every MDM server with the appropriate repository.
Operations for the same table can be bundled into one single service.
Provide the following capabilities:
Data management
– create, read, update, and delete (CRUD operations)
Access to central key mapping – create, read
Checkout management
– checkout, check in, join checkout, unjoin checkout
Consolidation of records using the matching functionality
Execution of assignments
Validation
MDM Web Services
MDM Web Services
Agenda
1. MDM and BPM
2. The Demo Scenario
The Sample Process
System Architecture
The Sample Repository
3. How to implement an MDM Process on CE
BPM
BRM
Performance
MDM projects require partly bespoke implementations. Especially MDM Data
Modelling (in MDM repository) and the assigned Business Processes will need
custom specific implementation.
To prevent performance issues within MDM solutions reviewing is recommended for
•
MDM Data Model
•
BPM Process implementations
The implemented Demo scenario uses CheckOut/CheckIn procedures in MDM.
This will produce additional load and may have to be prevented in case of massive
amount of change processes in repositories with lots of records.
Performance issues can be detected/
prevented by ordering SAP MDM
GoLive Assessment which will guide
customers through a set of MDM
Specific questions –
References
MDM Java API
http://help.sap.com/javadocs/MDM71/index.html
Web Dynpro Components for MDM
How to Build Web Applications Using MDM Web Dynpro Components
MDM and BPM
How to Integrate Master Data Management (MDM) and Business Process Management (BPM)
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 c omponents of ot her software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix ar e trademarks or r egistered trademarks of IBM Corporation.
Linux is the registered trademark of Linus T orvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are ei ther trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of O racle 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 r egistered trademarks of C itrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W 3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Oracle Corporation.
JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their
© 2011 SAP AG. All rights reserved
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or r egistered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.
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 var y.
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 ac curacy or c ompleteness of the information, text, graphics, links, or ot her 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 t hese 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 h ot 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.
