of 612

TZMDG1 SAP MDG Training Material

Published on January 2017 | Categories: Documents | Downloads: 69 | Comments: 0
188 views

Comments

Content


MDM Positioning, Overview and Roadmap
October 2011
TZMDG1 – SAP Master Data Governance
Introduction
Material number: 50108298
Version 97
SAP Class Week of March 12, 2012
This very first session of our workshop will describe SAP Master Data Governance
within the context of the complete portfolio of SAP’s solutions for Master Data
Management, and how MDG contributes to this portfolio. We will see what MDG is
built for and why its value proposition is so unique.
In order to understand this we will also briefly discuss MDG’s capabilities and
architecture. But you will see that this first session is going to be very high level. Bare
with us, you will get your hands “dirty” with real hands on experience and very
detailed information on MDG in the course of the later sessions and the next days.
But on purpose, we will start from a “Bird’s Eye” perspective to help you understand
the big picture first before going into details.
Accordingly, this session will focus on just highlighting capabilities and architecture to
explain why we built it this way. You will understand how customers can integrate
MDG into their existing SAP landscape – either as a central hub or on top of an
existing SAP ERP. We will also discuss the scope of the 2010 shipment of MDG and
which master data domains it covers.
SAP Class Week of March 12, 2012
While most of this presentation is about today‘s products, this presentation also
contains a few forward-looking statements. That is why we had to include this legal
disclaimer.
SAP Class Week of March 12, 2012
MDM has been on the market for quite a while, but its relevance for companies is
rising steadily. Gartner shares this point of view they state that By 2014, 66% of
Fortune 1000 companies will have deployed two or more MDM solutions.
So, there is a big market momentum for MDM. And with SAP’s end-to-end solution
portfolio in place, there is a big momentum for SAP to support customers also in this
segment.
SAP Class Week of March 12, 2012
So what is master data management all about. It is a strategic approach to enable
organizations to gain overall consistency of their different master data that is spread
across a diversified system landscape. With MDM you get one central view and a
trusted knowledge about this data. Using this knowledge, you can streamline
business execution and analytical processes in the enterprise.
This way you can solve a multitude of business pains associated with inconsistent
master data:
You can increase sales effectiveness by consolidating and aligning your customer
data and get your customer-facing processes up to speed.
You can optimize procurement decision for example, when you know all across the
enterprise what you purchase from which supplier and at which quantities.
Or you can streamline your go to market activities when your product data is
consistent across your application landscape.
And as already pointed out, you can optimize business analytics and decision
making processes when you can base your strategic business decisions on solid
master data.
SAP Class Week of March 12, 2012
As you have seen on the slide before, Master Data Management is not just a topic for our customers’ IT
departments. As a matter of fact, we – SAP – often times FIRST talk to the CIO’s department about
MDM. But most of the times the main drivers behind customers’ master data initiatives, are certain
Lines of Business. So when approaching organizations to discuss MDG, make sure that the LoBs get
involved as early in the process as possible.
Here are some examples that we have seen customers talking about. Financials: Many companies are
trying to accomplish a fast Financial Close. On the other hand they struggle with inconsistent de-central
definitions of Financial entities like charts of accounts or profit centers that they do have to map and
translate each and every time during the financial closing and financial consolidation process. It would
obviously help them to speed-up their financial close if they had consistent and reliable data that is only
maintained once centrally and then used everywhere. Sales: If you head sales for a certain product line
or a region, you do not want to see the same customer being confused by addressing them multiple
times based on duplicates in your system with different IDs. Also sending just-in-time deliveries to the
wrong address of a customer will negatively impact their experience with your company and impact
your business. Supply Chain: Imagine you are desperately waiting for a supplier to provide you with
critical materials for your productions process and you are already frustrating your customers as they
are waiting for you. But at the same time, you have tons of stock of the exact same material sitting on
the shelf somewhere else in your company – you just do not know as it is listed under a different
material number. Or imagine you cannot start producing a new product, because you company does
not control how new material masters are created in the system, and Engineering does not know that
you are waiting for them to maintain a few missing attributes.
So the main driver behind MDM initiatives often is an LoB – and actually that is the way it always
should be. What the CIO or IT department is going to be interested in, is more topics like: Can I
automate the maintenance process, so that I or the LoB have to throw less people on it? Can I provide
the LoB with a flexible solution that I can adapt to their changing needs? Can I provide them with tools
that will hinder them from doing mistakes and will ensure the data quality that business needs? Do I
have the necessary skills in my team to implement and run that solution?
SAP Class Week of March 12, 2012
The approaches that we see companies take towards Master Data Management are
manifold. Some just want to periodically consolidate master data from multiple systems, and
then identify duplicates and map their keys. For example, they might consolidate customer
master data in order to run a marketing campaign only once per customer or they might
consolidate supplier data once a year for a global spend analysis. Often times, as soon as
they have all data in one place they start data quality initiatives like address cleansing or
finding typos. And after the central correction they might harmonize the master data in their
de-central systems by distributing the cleansed attributes. On the other hand some
organization decide for central management of critical master. This typically dramatically
reduces the maintenance effort: only once centrally instead of multiple duplicates de-
centrally. But it also means a strong governance body to align the understanding of master
data and its attributes across the organization. Many companies do a mixture of approaches
for different master data domains. For example periodically consolidate de-centrally
maintained customer master data and central maintenance of master data for new products.
To tackle these manifold issues around master data, SAP offers an integrated solution Suite
for Master Data Management. We intend to best support each of the master data initiatives at
our clients. In this context, we do have solutions that are best for consolidation of master data
in very heterogeneous system landscapes, we do have solutions for data quality
management in a central data store, and others that are best for central maintenance of
master data that shall be ready for use in the context of the SAP Business Suite. <Walk the
audience through the bullet points if you like>
Now let’s talk about more details of this solution suite and its value proposition to our
customers.
SAP Class Week of March 12, 2012
We are often using this slide to explain the value proposition of our master data management solution portfolio:
One element is what we call Embedded Master Data Management: Each customer using SAP Business Suite has
a need for process-centric MDM that is embedded in their business applications. Embedded MDM provides
centralized master data creation, maintenance and governance for master data that shall be ready for use in SAP
Business Suite. We are offering this support out-of-the-box for selected data domains, such as financials, material,
and supplier. Other domain types such as customer are planned. Embedded MDM is a natural extension of the
business processes running in SAP Business Suite by adding pre-built master data creation, change, and
distribution processes and stewardship.
The focus of Enterprise Master Data Management is to extend the reach of MDM beyond the central management
of master data to application and system agnostic contexts. Enterprise MDM supports all domains for master data
consolidation, harmonization and stewardship, covering business initiatives such as mergers & acquisitions,
divestitures, supply chain optimization, or support for central analytics. This extended Enterprise MDM approach
incorporates and complements embedded MDM.
We want to support both value propositions with our products. As you might see, in the Embedded MDM space
we, SAP, have a huge advantage. We know how the master data will be used in the business processes of the
SAP Business Suite. And we know the meanings of the various master data attributes and we know their allowed
values. Accordingly in this area we can provide our customers with more out-of-the-box capabilities of a solution
regarding validation of master data attributes during creation, or regarding valid combination of attributes, and so
on.
In the Enterprise MDM area, the need is much more for a very flexible infrastructure where companies can design
tailor-made solutions according to their specific needs and system landscape. The solution here might be less pre-
thought by SAP less integrated into the SAP Business Suite, but easy to handle also by that part of a company’s
IT department that seldom touches an SAP system.
SAP Class Week of March 12, 2012
So how do our products fit into this picture?
SAP Master Data Governance provides ready-to-run governance applications for specific
SAP master data domains. SAP Master Data Governance applications are tailored for central
data maintenance so that the data is ready for use in SAP Business Suite environments. SAP
MDG covers the needs of embedded MDM.
SAP NetWeaverMaster Data Management is the proven multi-domain solution for master
data management in application-agnostic contexts and heterogeneous environments. The
combination of SAP NetWeaverMDM and SAP MDG will typically cover all requirements of
enterprise MDM.
In short, we can say that SAP offers a holistic MDM solution suite with a broad coverage
across master data domains, industry needs and system architectures. For example:
Different approaches for different domains, like: consolidate customer
master data for campaigns using NW MDM, central material master data
maintenance in MDG for New Product Design and Introduction (NPDI)
Different project phases, like: master data consolidation after a Merger or
Acquisition in NW MDM, central MDM in SAP MDG after the master data
has been consolidated
Different approaches by master data attributes: few global attributes in an
Enterprise-wide NW MDM system distributed to all non-SAP systems and to
one SAP MDG hub, many additional SAP-specific attributes centrally
managed in that MDG hub and then provided to all SAP systems
SAP Class Week of March 12, 2012
SAP NetWeaver Master Data Management is a generic multi-domain infrastructure
that provides flexible capabilities in data modeling, data quality and integration while
complying with data governance and stewardship principles.
The current release 7.1, with the support of multiple main tables provides extended
flexibility for data modeling and complex objects, allowing you to employ a single
master-data management repository for multiple data domains.
NetWeaver MDM is in particular suited for one of or periodic consolidation and
harmonization initiatives where you mass de-duplicate master data from multiple
source in the organization and where the outcome is improved data quality as well as
providing the basis for centralized analytics or other initiatives.
The tool also allows to build people-centric processes on top of the data repository,
for example for data stewardship purposes.
SAP NetWeaver Master Data Management is an MDM solution that we already
provide for a several years now. It is in use by a couple of hundred customers.
SAP Class Week of March 12, 2012
There is one more thing regarding NW MDM that I would like to mention here, as we
see many customers using both SAP MDG and NW MDM in combination and you
come across this at one of your future projects:
The Support Package SP6, that we released on NW MDM 7.1 by early 2011, has a
very dedicated focus on performance, stability, and supportability. We have worked
very closely with more than a dozen customers on these improvements. The results
speak for themselves: Customer validation tests revealed dramatic improvements in
import performance, fastening matching operations and batch processing.
In addition, there are new capabilities to streamline message reporting in support
(MDM Info Collector providing a comprehensive snapshot of the MDM system), and a
new Configuration Assistant tool that helps to streamline MDM Configuration in a
wizard-like manner.
So I would encourage you to drive for implementation of SP6 whenever you come by
any NW MDM installation.
SAP Class Week of March 12, 2012
One important part of our solution portfolio with a strong support for our master data
management product is SAP BusinessObjects Data Services.
Data Services is SAP’s strategic data integration and data quality solution. With its
capabilities to access, transform, cleanse, and enrich any type of data and its data
profiling, impact analysis and data lineage features SAP BusinessObjects Data
Services is perfectly suited as a data integration and data quality layer with in any
embedded or enterprise MDM initiative.
For example, you might want to use Data Services in Extract, Transform, and Load
(ETL) scenarios to load master data into a central repository. And Data Services can
be used for data quality and enrichment. The data quality engine in DS might inform
users about duplicate data sets and DS’s rich address enrichment features supports
users in entering correct addresses for their business partners.
SAP Class Week of March 12, 2012
And then of course the element of SAP’s master data management solution portfolio that we
will spend the rest of this workshop on: SAP Master Data Governance.
SAP Master Data Governance is a family of process-centric applications that provide
centralized governance for selected master data domains based on SAP's standard data
models. The applications come with a native integration with the Business Suite, using
existing business logic and customer-specific configuration for validation of master data while
it is being created. MDG supports central maintenance processes that ensure that the master
data is fit for use in SAP Business Suite processes, but can of course also be distributed to
non-SAP systems.
MDG provides out-of-the-box data models, validations, user interfaces, and workflows, and in
addition also allows for customized processes in order to ensure a consistent definition and
governance of master data in the organization. This, together with the distribution of the
master data, can replace the often error-prone process of manually maintaining master data
in multiple systems. All changes to master data are also recorded for later auditing purposes.
As mentioned before MDG may complement NetWeaver MDM in Enterprise MDM scenarios
and Business Objects Data Services may be used together with MDG, for example for data
quality and erichment.
SAP Class Week of March 12, 2012
Let’s have a look at the typical maintenance process in MDG: The process typically starts when a user
requests new master data or changes to existing master data. Or when changes to master data are
requested through data flowing into the system through an API.
At this moment a so called “MDG Change Request” is created. This change request is the container
that keeps all intended changes in a “staging area”, separate from the productive master data. This
ensures, that all changes are only used in production after the final approval. Via workflow the change
request is then handed over from one person to the next, in order for everyone to contribute their
knowledge to complete the master data. The good thing about change requests is also that data can be
stored “incomplete” in between. This means, that the company can decide how many people shall
contribute and who contributes what – regardless if the SAP ERP could save the master data in the
current status.
During the maintenance the data is always validated by the system. This validation re-uses existing
business logic and the customizing settings in the Business Suite system, but can also integrate
various services for data enrichment and cleansing: For example addresses could be checked for
correctness against reference data from an SAP BusinessObjects Data Services system. Companies
can also add their own validation rules, like all material numbers need to follow a certain pattern etc.
At some point in time the workflow will meet a person for approval of the changes. Only after the
approval the data is moved from the staging area into the productive master data and can then be used
in business processes and replicated to other systems. Often we see that organizations only put a
subset of all master data attributes under central governance. The other attributes can then be enriched
in the receiving systems according to the local needs.
SAP Class Week of March 12, 2012
J ust to give you a first glance at the solution, here we see a first screen shot of the
MDG solution. This is the welcome screen when a user starts working in MDG – in
this case MDG for Supplier Data. The design of MDG is user-centric with work
centers that provide work lists and include easy search capabilities as well as the
necessary applications / or services.
On the right hand side you can see a work list that provides the user with exactly
those MDG Change Requests that currently wait for him or her to take action on
them.
On the left hand side you see the menu that allows the user to launch the applications
within MDG – like “Create a New Supplier” or “Do Mass Changes on Many Suppliers”.
Users will typically either work down their work list triggered by the system, or they
might be triggered by other events – like a supplier calling and asking to change their
address. In that case they will use the menu to start the according Change Request
themselves. We also included a powerful search application in MDG. This will help
users to identify whether a potential new supplier already exists in the system and will
prevent them from creating duplicates.
There is two ways to access MDG as an end-user, as we provide the according roles
for the SAP Enterprise Portal, as well as for the NetWeaver Business Client (NWBC).
SAP Class Week of March 12, 2012
This is a second screen shot. This time we see the user interface of an MDG Change
Request. As said before, the Change Request is the container that bundles the all
data changes of one change process.
In this example the user wants to change some attributes of an already existing
material master record.
The small popup in the lower right corner tells us that – while the business
consistency check has been successfully passed – the system warns the user that he
or she might be creating a duplicate to an existing material in the database.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
I would now like to take you through some of the product’s capabilities, that we
believe make MDG a very attractive offering – especially for our Business Suite
customers
In the course of the next couple of slides we will discuss questions like: What does
“out-of-the-box” mean in this context? What are domain-specific applications that
come with an “Integrated Object Model”? How do we enable Governance in a way
that allows for collaboration and better data quality? How do we support data
replication? And how do we allow customers to re-use our (and their own) past
investments and do we allow them to extend the standard?
SAP Class Week of March 12, 2012
What does “out-of-the-box” meant in the context of MDG?
Our customers regularly complain about the high cost for implementing and running our
solutions. This is also an issue when they are investigating MDM Solutions of our
competitors. With SAP MDG we have a clear advantage here, as we offer MDG in way that
you can for example co-deploy it with existing SAP ERP system.
MDG is easy to consume and ready to run. It comes with standard roles, workflows, pre-
defined workflow inboxes for processing change requests, with user interfaces for data
maintenance or approval, interfaces for integration to BusinessObjects Data Services and so
on. This allows customers to immediately start with a proof-of-concept. And it avoids one of
the probably most costly parts of any other MDM implementation – the reuse of existing
processing logic in the back-end.
But regardless of its out-of-the-box nature, at the same time MDG is very flexible and this
flexibility comes at a low price tag. There is many things you can change by configuration: for
example by adapting workflows, or validation rules in BRF+. For many of this adaptations you
do not need to change or create any coding.
MDG’s pre-delivered “best practice” data models are based on the models in the SAP
Business Suite and hence are already proven in the SAP business context across multiple
applications and industries.
To a large extend, MDG behaves like master data applications in the Business Suite already
do, especially in the sense that MDG uses the exact same validations that existing master
data transactions use.
In order to replicate the data from MDG into other systems, it uses established replication
mechanisms (like existing IDoc templates) and thus provides out-of-the-box integration
mechanism into the Suite, but of course also the means to replicate to non-SAP systems (for
example using Enterprise Services).
SAP Class Week of March 12, 2012
This slide is more intended to be a quick reference for you and an overview about the
current standard data models that we deliver with MDG in the “Suite 7 Innovation
2010” version of MDG. Later in this course we will cover the master data domains in
MDG in much more detail.
J ust a few words here: MDG in its current version covers the domains Financials,
Material and Supplier. We shipped the second release of MDG for Financials Data,
now covering Chart of Accounts, General Ledger Accounts and their Hierarchies,
Companies, Profit and Cost Centers and their Hierarchies, as well as Cost Elements
and their Hierarchies. Material and Supplier are contained in MDG for the first time
with the current release. For Material the focus is on identifying attributes of the
material master as well as some attributes for material classification. The Supplier
model is based on the generic business partner but also contains ERP-specific
attributes like Purchasing Data or Company Code Data.
SAP Class Week of March 12, 2012
SAP MDG is a solution that enables collaborative stewardship through integrated workflows. The
workflows orchestrate the process across multiple users who each contribute with their knowledge to
creation or change of master data. MDG is based on ABAP technology and embedded into SAP ERP.
This means that companies can make use of the system in order to adapt the MDG processes
according to their business needs based on existing SAP business logic. They can also use existing or
new ABAP code to extend the standard MDG logic. They can combine validations based on SAP
business logic, with other freely defined validation rules. All this will help to create the right data quality
from the very beginning.
As said before, MDG keeps all changed data in the “Staging Area” until it is approved. MDG also allows
defining which sets of validations are executed at which step of the workflow. Hence MDG allows to
store incomplete data, or data that will only be validated later – while keeping it separate from
production data. This means that companies can freely define which people in which roles will
contribute to the overall process, and who needs to enter in the final format for the system and who is
allowed to already enter some data to the best of their knowledge and experts will check that data later
supported by the system. Still no corrupt data will go into production without being checked by the
system and approved by the gate keepers.
Although MDG provides a lot out-of-the-box capabilities with its data models, user interfaces,
workflows, validations and so on, all this can easily be adapted to the specific company’s needs for
example by changing the workflows, or by assigning different validations.
MDG uses the SAP Business Workflow and makes use of the flexibility but as well of the reporting
capabilities of this tool.
The processes could be linear – like in our generic example – or can work in a distributed way, e.g.
different departments or different locations maintain or approve only the part of the data for which they
are responsible. This is defined within the roles e.g. of a business user, a master data steward or a
master data manager.
Processes and roles can be adapted and tailored based on customer needs and can span across the
enterprise to accommodate the business networks our customers act in today.
SAP Class Week of March 12, 2012
Through the mentioned capabilities and the flexibility to adapt them, MDG allows to
ensure exactly that data quality that a given company defines in their Information
Governance initiatives.
Examples include: Duplicates are being avoided from the very beginning. And this
duplicate prevention can even be done based on our high quality detection algorithms
that include fuzzy logic from SAP Enterprise Search, or phonetic search and
standardization of data as provided by BusinessObjects Data Services (Data Quality).
Data can be enriched or addresses can be validated using BusinessObjects Data
Services’ rich postal validation content. All data can also be validated based on
companies custom-defined validation rules (like integrity rules, derivations or other
simple checks) using the rule modeling tool of SAP’s Business Rules Framework Plus
(BRF+).
SAP Class Week of March 12, 2012
Once you have maintained and approved the master data on the central MDG
system, you might want to replicate the data to all SAP and non-SAP systems that will
need the master data. MDG comes with a framework that supports the organization
and execution of this data replication – it is called Data Replication Framework (DRF).
With MDG, we of course did not want to invent yet another way to do this replication,
but we intended to better support customers in managing the distribution they already
do today. Accordingly the DRF framework sits on top of the established replication
mechanisms that SAP customers have already been using for a long time (like ALE
IDoc) and newer ones like Enterprise Services. The purpose of MDG’s DRF is to help
our customer keeping track of what needs to be distributed where, and what has been
distributed successfully or not – regardless of the various replication mechanisms
used underneath. In DRF, systems can subscribe to the distribution of master data
based on certain filter criteria – like only materials for plant 1000 with material type
FERT are distributed to system XYZ.
In addition MDG can handle things like key mapping (in order to keep different
historical keys for existing master data in de-central systems and at the same time
only maintain the data once centrally). It also manages value mapping (in order to
allow distribution into systems that might have a different understanding of the values
of an attribute, for example material type FERT in one system might be called PROD
in other systems).
DRF also helps in monitoring the distribution, and in resolving errors.
SAP Class Week of March 12, 2012
A major focus of MDG has been put on re-use and extensibility.
But re-use does not only mean re-use for us in SAP development. Yes, we are re-
using the existing ERP coding to validate entered data and we are often re-using the
existing tables to store the active data after approval.
But more importantly it is also about re-use for our customers: They can re-use
extensions that they have already made to SAP master data in the Business Suite
and they can include these extensions directly in the MDG data models. They can re-
use the own business logic that they have created in SAP Business Suite for example
to validate newly created master data.
We know that each and every SAP customer has made extensions to SAP’s standard
master data model. And that many companies have very specific master data creation
and change processes. Accordingly, MDG offers the flexibility and extensibility
features to adapt the standard to their needs. The big value proposition here is that
we allow our customers to do these extensions and still benefit from MDG out-of-the-
box capabilities.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
On the next couple of slides, we will discuss the scope of MDG in the version that has been shipped
with SAP Business Suite 7 Innovation 2010. We will talk about the domains of Financials, Material, and
Supplier. We will cover the option to create own custom master data models, and we will briefly talk
about architecture and deployment options.
As mentioned before, MDG for Financial Data shall help the Finance organization at a company to
speed up the Financial Close. In order to do so, MDG provides means to centrally create financial
entities and to distribute these entities to de-central systems. Through this companies can assure that
these entities are consistently used across all Financial systems – including operational systems,
planning, reporting or financial consolidation systems.
One major issue in this process companies are often facing, is to establish a collaborative environment
in which financial experts can discuss new entities, can control that no unnecessary entities are
created, and that provides a complete audit trail for all changes. MDG addresses exactly these issues.
It acts as a gate keeper for the creation of new entities, where colleagues can request the creation of
new entities. They can attach documents that describe the need for a new entity – like a new account
that you would need do to legal reasons in a given country. Experts can comment the change requests
in order to agree on approval or rejection. And all this is kept for auditors to understand the changes –
maybe even years later.
Another typical need in the Financials area is to group many change requests and to release them at
the same time. For example, all changes belonging to next quarters chart-of-accounts shall become
effective together. MDG offers the concept of “Editions” for that purpose. You can assign multiple
change requests to one Edition. Then each of the change requests can be approved (or rejected), but
the approved changes will only become productive as soon as the complete Edition is approved.
Again, in Suite 7 Innovation 2010, MDG for Financial Data covers Chart of Accounts, General Ledger
Accounts and the respective Hierarchies, Companies, Profit and Cost Centers and their Hierarchies, as
well as Cost Elements and their Hierarchies.
SAP Class Week of March 12, 2012
MDG for Supplier Data addresses the need of organizations to control the process of proper creation of
new suppliers or change of existing supplier data. Typically this process will include multiple people
with different expertise, who all need to contribute in the right order and at the right point in time.
Typically different people would maintain purchasing data (like when orders with this supplier would be
paid at which terms) than financial data (like tax regulations in the context of this supplier). Without
MDG, organizations are struggling to distribute this maintenance work between the right people, but at
the same time to inform the involved people to ensure timely maintenance. They are having a hard time
ensuring that no suppliers are being used in business processes, before all maintenance tasks have
been completed.
MDG allows companies to define workflows and roles to separate the work between knowledgeable
people. Each of them gets informed when to contribute. They are even informed until when they need
to finish their task based on Change Request priorities or Service Level Agreements. The data is kept
separate from production data, ensuring that no purchase orders can be posted until the data is
sufficiently complete. Through it flexible rule framework for validations, MDG allows to ensure exactly
the needed data quality at the right point of the process. And MDG supports the user in avoiding
duplicates, to ensure that every supplier is only maintained in the system once. Through its Key
Mapping capabilities MDG also helps to avoid double maintenance for existing duplicates in the system
landscape. The entry can be maintained once in MDG and then distributed to the receiving systems
using the specific keys of each systems, without the need to change historic keys in the de-central
systems.
In Suite 7 Innovation 2010, MDG for Supplier Data focuses on general supplier data, generic business
partner data (like identification, tax numbers, bank details, addresses) as well as on some ERP-specific
data (like data related to the company code or purchasing organization). Besides just search, display,
and maintenance of single instances of suppliers, you can also process mass changes involving many
suppliers. Business Objects Data Services is of specific value here, as it will help companies to
increase the quality of address data for their supplier base.
SAP Class Week of March 12, 2012
Material master data is a very complex thing. In some organizations, more than 20
people need to contribute to the maintenance of a single material master. Especially
for introduction of new products many companies are struggling to ensure that all that
information is maintained properly and completely before the new material is used in
the various business processes. To make it even more complex, different data has to
be complete in order to use the material in production planning, or in sales order
processing, or in shipments. This complexity demands for a solution that organizes
the process of the data maintenance across multiple users and allows to absolutely
avoid that data is being used before it is ready.
As discussed in more detail on the last slide, MDG will help these organizations to
manage exactly this complexity. Customers can use the standard MDG content as a
very good starting point and then create their specific processes, typically defining
multiple Types of Change Request in MDG for various usage scenarios. In Suite 7
Innovation 2010, MDG for Material Data comes with a certain set of identifying
attributes of the material master as well as some attributes for material classification.
We expect that customers will want to extend that scope based on MDG flexibility
features.
SAP Class Week of March 12, 2012
MDG provides out-of-the-box applications for chosen master data domains. These
applications are built by SAP using a dedicated framework: the Master Data
Governance Application Framework. With Suite 7 Innovation 2010, this framework
has been opened up for customers to build their own MDG applications based on
their own master data models. These custom models could be completely self-
defined by the customer, they could be extensions of the standard models in MDG, or
the models could be standard SAP ERP models, where SAP has not (or not yet) built
the standard MDG content.
Customer can use the framework to define the appropriate data models, then
generate the staging area and user interfaces based on these models. They can
define appropriate workflows and the roles that will provide access to the user
interfaces. They can use DRF to distribute the data that has been maintained. They
can build their own validations, or extend existing ones based on the Business Rules
Framework (BRF+). Finally, there are also Business Add-Ins (BAdIs) provided, to
include custom ABAP code into MDG’s processes.
SAP Class Week of March 12, 2012
This pictures shows an overview of the general architecture of MDG. We will not go
into detail here, as that will be the scope of the next lesson.
J ust a few things to mention here: Same as the main SAP Business Suite
components, MDG is built on top of the Application Server for ABAP (AS ABAP).
Parts of MDG are in a software layer “underneath SAP ERP” and can be re-used by
ERP’s applications. Other parts of MDG are in a software layer “on top of ERP” and
can re-use existing ERP coding, like for example the build-in validations for ERP-
related master data do. MDG makes use of components of SAP Information
Management portfolio like for example for fuzzy searches it can use Enterprise
Search or it leverages Business Objects Data Services for address validation.
MDG provides HTML-based user interfaces based on WebDynpro for ABAP as well
as roles that can be accessed either through the SAP NetWeaver Portal or through
the NetWeaver Business Client.
MDG’s Data Replication Framework manages the distribution of master data to SAP
and non-SAP systems using technologies like ALE IDoc or Enterprise Services.
SAP Class Week of March 12, 2012
In Suite 7 Innovation 2010 we ship MDG as part of the Enhancement Package 5 for SAP
ERP 6.0. This means whenever a customer wants to install MDG they need to install this
Enhancement Package. This also means, the system where the customer runs the MDG
processes technically always is a full SAP ERP system.
We see three typical ways how customers deploy MDG in relation to their existing system
landscape. Either they decide to introduce a completely new system – a dedicated master
data hub. Also this system technically is a complete SAP ERP system. They will only use the
MDG functionality on this system and distribute the master data to their systems where they
run their business processes. Second possibility would be that a customer decides to pick an
existing SAP ERP system for a certain master data domain and runs MDG on this system.
This system will then be mastering the data for that particular domain – for example for
Material Data. The approved data that comes out of MDG’s processes would then directly be
available to the business processes that run on that system and would be distributed to all
other systems that need it.
A special flavor of the second case would be customers who only run one single SAP ERP
system. They might want to co-deploy MDG with that system – that is they upgrade that
system to Enhancement Package 5 and switch on MDG’s Business Functions. Even if they
would not want to distribute the master data to any receiving system (which rarely will be the
case), even then they would benefit a lot from MDG: They would still be able to separate
incomplete or not-approved data from production data through MDG’s staging, they could use
MDG’s workflows to distribute the maintenance to multiple people, they could flexible
enhance the validations beyond SAP’ ERPs hard coded checks, they would benefit from the
improved prevention of duplicates, and so on.
SAP Class Week of March 12, 2012
J ust to summarize the scope of MDG in Suite 7 Innovation 2010 again:
We are covering Financial, Supplier, and Material Data with a dedicated scope per
domain. This scope can be enhanced by customers. We provide processes on single
master data instances as well as mass changes. There are means to load mass data
into MDG as well as means to distribute the master data that has been processes by
MDG. MDG comes with an integration to Enterprise Search as well as Business
Objects Data Services.
All provided workflows, user interfaces, and validations can be adapted by customers
to their specific needs.
In addition to that, MDG provides a framework for customers to build their own MDG
applications based on their own data models.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
We are approaching the end of this session. This slide is just trying to summarize why
we think that we have a very unique offering with SAP MDG, that is unrivalled in the
market when it comes to central MDM for SAP-centric data.
In short:
MDG is an out-of-the-box solution integrated into the customers SAP Business
Suite context.
It provides all the needed ingredients for a collaborative governance solution that
ensures high data quality through being both: process-centric as well as user-
centric.
It comes with a framework and all the common services that companies will need
to optimize the solution to their needs.
And all this comes at a low TCO for the customer, as MDG behaves like the SAP
ERP application they are already using today.
SAP Class Week of March 12, 2012
This slide is trying to summarize the value proposition of SAP MDG and trying to call
for action:
Wherever possible, organizations should strive for central master data
management for their most critical data. Through this they can eliminate the root
causes for business problems resulting from bad data.
MDG is the out-of-the-box solution to their needs.
MDG is built to be integrated into the customers SAP landscape.
Although being out-of-the-box, MDG is the platform that provides the flexibility
their organization needs.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
While the rest of this workshop is going to be on the Enhancement Package 5 version
of MDG, let me give you a quick view on the product roadmap. Nedless to say that
this is the planned roadmap and plans can change, so please take this with caution.
I already talked about the scope of Enhancement Package 5, with the next release
we intend to extend the scope per domain (Financial, Material, Supplier) as well as to
introduce SAP Master Data Governance for Customer Data. We are working on the
framework towards improved extensibility and flexibility. In addition, we plan to
improve search, master data distribution, and analytics.
In the future the focus shall be on further completion of the data models and
potentially more domains, also looking into industry-specific extensions. Of course we
will be further extending the framework‘s capabilities as well as analytics. We are
thinking of providing MDG for selected reference data (like units of measurement) and
about obile access to the MDG processes where it makes sense (like requesting the
creation of new supplier master data by entering a business card, or approval steps
or alike).
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
The business challenges aroundmaster data are manifold and span from process
disruptions via high maintenance cost to compliance issues.
This is the reason while we put an emphasis on the governance aspect during the
development of the MDG solution
We developed this solution in close corporation with some of SAP’s key customers
that are using the business suite and I will to come to this again towards the end of
this presentation
So the clear focus of MDG is to provide a solution that is “f i t for use wi t h SAP f i t for use wi t h SAP
Busi ness Sui t e and SAP ERP Busi ness Sui t e and SAP ERP”
Complementing and extending the business scenarios that SAP NetWeaver MDM
covers, MDG provides a native out-of-the box integration with the SAP Business
suite and SAP ERP.
We ensure this by reusing the proven SAP data model together with existing
business logic and configuration to validate the master data in the various domains
Providing transparency and ensuring compliance is achieved by the integrated
staging & approval process that also provides a central audit trail.
And of course existing authorization and distribution mechanisms can be reused
while adding specific capabilities.
To better understand how reduced maintenance effort while having higher data
quality can be achieved using SAP MDG, let’s have a look at the generic
maintenance process:
SAP Class Week of March 12, 2012
Mary is a business user in the purchasing department of an engineering company and she
needs to add a new supplier to order some samples. She as already talked to their sales
department and now wants to initiate a purchase order in the SAP ERP or SRM. For this she
needs to ensure that the supplier data is available and correct. She has already searched in
the companies supplier directory using the MDG search capability and did not find this
supplier, so its really new.
She maintains some key information including address, communication details and contact
persons. This data is kept in the so-called “staging area” and is now validated in a second
step. This validation re-uses existing business logic, but can also integrate external services
for data enrichment and cleansing – ideally provided by Business Objects’ Data Quality and
Address Services.
Now the collaboration starts and the request for the new supplier is sent to other parts of the
organization that are in charge of adding data and/or approving the request.
This approval process is auditable and in most cases at least a two-man rule is ensured.
Once the data is complete and approved it is activated in the MDG system.
After this activation the replication to the connected business systems is started – either
immediately or in a scheduled manner.
Depending on the setup of the local systems the data can be adapted and enriched there as
well.
So from a user perspective this process pattern is quite straight forward. But we had to follow
and ensure some key elements to achieve this ease-of-use and I will briefly go through them
so that you get a better understanding and also a glimpse of the solution itself.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Find here the visual representation of the MDG for material data model that is
delivered for this enhancement package.
The model is based upon the widely used SAP ERP/ECC “material master”.
SAP Class Week of March 12, 2012
The scope of Master Data Governance for Financials is defined for master data used in financial
accounting, financial consolidation and planning like e.g. the chart of accounts and the accounts, and
organization unit like companies, profit centers and cost centers.
In SAP ERP Enhancement Package 4, the scope of Master Data Governance for Financials includes
the central maintenance of chart of accounts and accounts and the related objects, both, for
consolidation and operational systems (see following slides for more detail).
In SAP ERP Enhancement Package 5, the scope of Master Data Governance for Financials includes
the central maintenance of cost element and organizational unit including companies, profit centers
and cost centers.
Major Financial Entity Types (Usage 1):
GL Account->1.GL Account(Company Code Dependant part) 2.Financial Statement Item 3.
Company
FS Item Hierarchy->Financial Statement Item
Consolidation Group->Consolidation Unit->1. Company 2. Profit Center
Profit Center Group->Profit Center
Cost Center Group->Cost Center->Profit Center
Cost Element Group->Cost Element
Other Financial Entity Types not on the slide (Usage 1):
Breakdown Category
Breakdown Category Set
Consolidation Characteristic
Financial Reporting Structure
Financial Reporting Structure Item
Transaction Type
Hierarchy top nodes: Profit Center Hierarchy, Cost Center Hierarchy, Cost Element Hierarchy,
Consolidation Group Hierarchy
FSI Hierarchy and Consolidation Group Hierarchy have corresponding objects in ERP. The other
hierarchies don’t.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Although MDG delivers a new SOA based framework with ERP EhP5 other
technologies for extraction and load are still available and can be considered if
appropriate (for example „pure ALE“ technology (via transactions BD10 or BD14),
LSMW, SAP BusinessObjects Data Services). These might be sufficient for loading
data in non-SOA based format (e.g. csv-files or, IDoc-XML) into the active area. The
new framework allows additionally for direct load of data in the SOA-format into active
area or staging (which is not available via other technologies).
Be aware that master data (as well as key- and value-mapping) can be extracted from
clients as well as from the MDG system. Extracting data from MDG is used to allow
Consolidation and Data Quality Services through additional components (like NW
MDM or SBOP Data Services). See „Data Quality“.
SAP MDG stores data in one of two persistencies: Staging Area or Active Area. Data
in the staging area is not ready for consumption and usually has to be approved by a
Master Data Steward to be sent to the Active Area.
ESB (Enterprise Service Bus; Middleware), NW MDM (NetWeaver Master Data
Management) or SBOP DS (SAP BusinessObjects Data Services) are optional
components. Additional implementation steps are necessary to build scenarios based
on these components.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
IPS: Information Platform Services (fka miniBOE)
BIP: Business Information Platform (fka BOE)
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Main Process of Master Data Governance is the maintenance of master data in a central
MDG hub.
This process consists of the following steps:
1. Maintain master data in a staging area (see following slide)
2. Execute validations in the existing business logic and/or in external services
3. Approval of the newly created or changed master data by another user that is determined
and triggered by workflow.
With approval, master data are activated. This means they are transferred from staging to
the active area.
4. After approval (maybe scheduled) data are replicated to target systems.
5. Adaptations in local systems are currently not yet integrated in the workflow process in
the central hub.
SAP Class Week of March 12, 2012
The active area contains all master data that can be used operationally (either in the central
system itself or after replication to other operational systems).
Any changes or creation of new data in the MDG hub is done with a Change Request. In the
change request, a requestor and other processors can enter general information about the
requested change like reasoning, priority etc.
When a change request for existing object instances is created, these objects are copied into
the staging area. All changes to existing objects or newly created objects are only stored in
the staging area.
The execution of validation can be triggered:
By request of the processor of a change request with immediate messages
At save of a change request with immediate messages
After save in a separate background step of the workflow with display of an error log in the
next online processing step.
Workflow configuration determines the user for approval of the change request. With
approval, the master data are activated:
All master data that have been changed or newly created with the change request are
transferred from staging into the active area.
Change documents are created for staging and active area.
After activation, master data can be replicated, either immediately or scheduled.
SAP Class Week of March 12, 2012
The workflow process for change request can be configured differently for specific
applications and by the customer.
The change process may start with a special request step for occasional users. In this step,
they do not enter actual master data, but just explain in text form, what kind of change they
request.
Then the change request is sent by workflow to a master data expert, who enters the actual
changes.
Then the change request can be processed as described before.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
For master data that are maintained with editions, every change request has to be assigned
to a specific edition.
An edition has to be created, before any change request can be created.
Several change requests can be assigned to one edition
Change requests describe the business reason for changing master data and control the
approval and change process. They can contain a description, attachments and comments.
When all change requests for an edition are finally approved or withdrawn, then the edition
as a whole can be released. Then no further change requests can be created for this
edition.
The replication to local systems can either be triggered by the approval of the single
change request or for the edition as a whole.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
A user selects his role
You enter the start screen of the first work center (The service map provides intro for
beginners)
Typically processes are triggered from links in the work center that are structured in a menu
Since MDG always starts with a work list, processes can also be triggered from this work
list
The roles in MDG are structured the same way (financials having one additional work
center for editions)
Customers typically configure their own roles – we deliver the maximum content in every
role
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Part of the solution strategy are principles that represent the people-centric and flexibility
goals of the solution.
This is not specific to the data domains, but holds true for the overall SAP MDG solution.
In general the processes of the solution can be adapted and tailored to the customer needs.
This includes:
Workflows that are even linear, can be distributed or even started ad hoc
Clear roles and responsibilities following a task-oriented approach
Process steps can be added, either reusing existing logic or using a flexible rules-engine
The data in the governance process is separated but transfer to operational database is
done in very controlled mode
In summary this fosters Flexibility and User Acceptance while ensuring Governance
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Search – First Step to Pristine Data Quality
Search is the initial action, if a user wants to “do something” with the data.
Several Flavors Supported via Search Provider Concept
Standard provider: Enterprise Search incl. Fuzzy Search
Customers can integrate their own search providers
SAP Class Week of March 12, 2012
The display function enables you to display the details for a single entity in the Master Data
Governance system.
You can enter a known ID or search for a entities based on their ID or description.
Additional information can be fetched incl.
Switch to edit mode: You can switch from displaying the entity to editing it. You can also
access the mass change service from this screen.
Show relevant MDG data: You can display the change documents, replication log, key
mapping, and duplicate check results for the chosen entity.
Switch between active and inactive versions: You can switch between active (stored in the
active area) and inactive (stored in the staging area) versions of the entity. This action is
only possible if the entity is part of an ongoing change request.
SAP Class Week of March 12, 2012
You can select change requests for display by several selection criteria.
SAP Class Week of March 12, 2012
The selected change request is displayed with the assigned object.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
A requestor can see all change request that he has created with “My Change Requests”.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
In the general process “Create Change Request” a change request of any type can be
created.
The Change Request Type determines among other:
Data of which data model and which entity types can be maintained
The Workflow template to be used
Optionally the UI configuration
At the creation of the change request, the requestor only describes, what shall be changed
(or created). But he does not enter the actual master data.
In the second step a master data expert can enter the actual master data according to the
description of the requestor.
The workflow can also contain additional steps for additional users in order to enter
comments or specific master data.
The submit for final approval may be triggered by a certain processor or by some automatic
rule.
If the final approver rejects the change request, a special step for “Rework” can be triggered.
The processor for rework can decide about corrections and resubmit or withdrawl of the
change request.
After final approval, master data are activated and can be replicated to local systems.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
This is an optional step.
If the requestor cannot identify the objects to be changed or created, he can skip this step.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Mass change is a special transaction to change one or more attributes of several object
instances to the same value.
In this example the same material group is assigned to selected materials.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Hierarchies can be maintained for most entity types in MDGF and for supplier.
Several hierarchies or versions of a hierarchy can be defined for the same entity type.
Hierarchies can be replicated to other systems by download.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Duplicate Prevention:
Tailored Matching via Provider Concept
Providers can be selected per data model and entity type
Re-use of search providers e.g. Enterprise Search or BAS-DES (SAP BusinessObjects)
Specific / custom providers
Validation Exmples:
Code lists – Valid regions for country
Simple checks (e.g. format based) – postal code in Germany 5 digits (built-in)
Modeled rules via Business Rules Framework (BRF+)
Programmed in customer-specific code (BadI)
Data Enrichment – Example is taken from Supplier:
Address Enrichment
Re-use of BAS-PAV interface
Simple check and selection lists (extension)
Integration with SAP BusinessObjects Data Quality Management
Tax J urisdiction Code
Re-Use of existing interfaces / providers
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
In general Master Data Governance has a build-in component for data replication, the Data
Replication Framework (DRF).
For the exchange of the financial data we rely on this new framework and a SOA-based
communication.
For supplier data we have the choice of using the new SOA services or reuse existing
techniques like ALE.
For MDG for material data, the replication from the MDG hub to the connected ERP and ECC
client systems is currently done exclusively using ALE in order to minimize the effort for the
customers in upgrading the connected systems.
Customers can use this out-of-the box integration between SAP systems without the need for
expensive middleware solutions.
For more sophisticated transformation and routing requirements, customers may want to
included SAP NetWeaver Process Integration (NW PI) in their replication and distribution
landscape.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
In a change request for a specific object type, the change request data and the new master
data can be entered in one step on one screen.
The workflow can contain additional steps for additional users in order to enter comments or
specific master data.
The submit for final approval may be triggered by a certain processor or by some automatic
rule.
If the final approver rejects the change request, a special step for “Rework” can be triggered.
The processor for rework can decide about corrections and resubmit or withdrawal of the
change request.
After final approval, master data are activated and can be replicated to local systems
SAP Class Week of March 12, 2012
Change Request data and new master data can be entered on one screen.
The area for the change request data can be collapsed and expanded by a so-called toggle
button.
SAP Class Week of March 12, 2012
The change request workflow can also be configured with intermediate approval steps.
Details are described in the processes for supplier.
SAP Class Week of March 12, 2012
The change request workflow can also be configured with parallel approval steps for specifc
parts of data. The process ends, when all parallel approval steps have been decided.
Details are described in the processes for supplier.
SAP Class Week of March 12, 2012
The slide outlines the features of Master Data Governance in general. All features are
described in separate presentations of the RKT Learning Map for EhP5.
Some are shown with examples from the different domains on the following slides but as well
focusing on the business value and the pain points they solve.
SAP Class Week of March 12, 2012
“Thank you for attending this learning unit.”
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
The services in the work center are assigned to a Business Activity.
The business activity determines:
Data Model
Change Request Type
(Several Change Request Types can be assigned to one Business Activity.
In that case, the user has to select the Change Request Type that he wants to use.)
The Change Request Type determines:
The workflow template
The data model and the entity types
The possible workflow steps can be defined in the workflow or in the change request type.
The processor is determined per workflow step.
The UI Configuration can be determined per entity type for the change request type. A default
UI configuration can be assigned to a user per data model.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
MDG CHANGE REQUEST PROCESSI NG
TZMDG1 – Exercise 1.3
Exercises / Solutions
Ingo Rothley / SAP AG
Exercise: Run MDG material processes in the Training
Systems
At the end of this exercise you are able to:
Logon to the training system
Use the search capabilities of MDG (Enterprise / TREX search)
Run MDG change requests with examples from Material domain
You are acting as a business user of the logistics department. You are
supposed to maintain material master data of an enhanced product line.
All objects of this exercise are named with ##. Please replace this with
your group number:
## = Group Number = 01 – 30
Parameters valid throughout the Exercise(Replace ##with your two-digit
Team Number):
Logon to the SAP System [….]
Username: [….]
Password [….]
In MDG you are able to work with the internet based NetWeaver
Business Client (NWBC) or via the enterprise portal
SAP Class Week of March 12, 2012
2
Bef or e You St ar t : Connec t t o t he Tr ai ni ng Landsc ape
The SAP Training Landscape has been moved to the Cloud. To connect to the SAP MDG (ERP) system via SAP GUI
or via the according NetWeaver Business Client or NetWeaver Portal, you will first need to connect to a computer that
also is located in that Cloud. All programs that you will launch during the exercises below will actually be executed on
that computer – not on the PC in this room. We will use Windows Terminal Server (WTS) to connect to the Cloud.
Accessing the training computer in the Cloud
There are separate instructions for every training course available depending on the training location. The following is
the most common way if you want to go through this exercise; but your instructor might have more details.
If you are using the PCs in the training room, you first you need to log on to the SAP training environment on WTS. You
will typically find a “Training Area” where some ”Common Training” is located.
Within this WTS or if you are within the SAP Network, please start the remote desktop connection directly from your
computer. Choose “run” from the start menu. Open “mstsc”. Computer […computer ID of this course …] e.g.: “RA-
ECC605TX-001”
You will enter the WTS environment. Then you will see a popup, asking you for a user and password. Please make
sure to use the same group number (“train-##”) that you are assigned to in the MDG backend. The password to be
typed in is “initial ”. If asked whether you trust the computer that you are about to connect to, please answer “yes”.
Hint: As long as you are logged on at the WTS under a certain user ID, you are blocking this user on the
WTS. Nobody else can use these credentials until you properly log off from the WTS. Please make sure
that you always use Start Log Off [computer ID]\train-## to end your session on the WTS. Please
never just close that WTS window – which would leave the session running on the WTS.
Ex erc i se 1: Act i vat e your User i n t he Tr ai ni ng Syst em
In this exercise, you will activate your own user and verify the necessary roles and authorizations of your user in order
to run MDG in that sandbox system.
Find the RKT Trai ning system
Please open SAP Logon and create a new Connection for the system “ZME” if not already there.
Hint: We will start this exercise by accessing the landscape via SAP GUI for Windows. You will also be able
to access ZME via the SAP NetWeaver Portal or via the NetWeaver Business Client.
Acti vate your personal user and verify the necessary authori zations
Please logon to MDG backend system ZME with your user ID TZMDG1-## with ##representing your group number.
We recommend to change the password to the course ID “TZMDG1” or the course+group ID “TZMDG##”
Verify that your user is capable of running business transactions of all domains of MDG:
SAP Master Data Governance for Financial Data: Role: ___________________________
SAP Master Data Governance for Material Data: Role: ___________________________
SAP Master Data Governance for Supplier Data: Role: ___________________________
Access the corresponding enterprise portal and verify the necessary roles
Please logon to Portal with your user ID TZMDG1-## with ##representing your group number.
http://portal-zme.wdf.sap.corp:50000/irj/portal should already be available in your browser’s favourites.
Password is identical with the just changed backend password.
Add the portal to your browser favorites if not yet available in order not to re-type it.
The corresponding portal roles for your portal user are already assigned. (The according portal roles are:
“Financial Master Data Manager”, “Material Master Data Manager”, “Supplier Master Data Manager”, and
“ERP Common”.)
SAP Class Week of March 12, 2012
3
Ex erc i se 2: Sear c h f or Mat er i al and c hange i t
Your company is in the CD manufacturing business and has enhanced an existing product line. Before you can add
further products you want to ensure that the main lab has enough capacity to ensure the quality of the new products.
Therefore you want to move the q-processes of the existing product line “Demo CD” to another q-lab.
This and the following processes can all be done using your training user. Typically this would be shared
responsibility and segregation of duties, so the individual steps would show up in different work lists. For
simplification we allowed every training user to process all steps. This allows you to work either from the
work list or from “My Change Requests” to process the approval steps.
Search for the Demo CD
Start your search in the Material work center.
How many materials with description containing “Demo” do exist ? ________________________
Narrow down your search to materials starting with “ACT” in their ID.
Change Material ACT-DCD-##and assign “Laboratory 2” as the Lab/Office. Submit the change and run through the
approval process.
You might want to trigger this activity directly from the search results
Review your change in the ERP backend using transaction MM03 “Display Material”.
Ex erc i se 3: Searc h f or Mat er i al and t r i gger a copy
Your company is in the CD manufacturing business and has enhanced an existing product line. Therefore additional
master data needs to be maintained in order to reflect the business in the ERP backend system. You now also want to
manufacture Mini-CDs and therefore you need the correct labels.
Search for the CD labels
Start your search in the Material work center.
How many materials with description containing “label” do exist ? ________________________
Narrow down your search to Raw material (ROH), how many? ________________________
Finally you are only interested on CD labels of your group ##in the material group 00213,
please note the material IDs ________________________
Copy an existing label to a new material “ Mini-CD”
Copy one of the materials to the new label for Mini-CDs (Material ID ACT-MCD-xx). Adjust the descriptions.
Submit and approve the change request.
SAP Class Week of March 12, 2012
4
Sol ut i on t o Ex er c i se 1
SOLUTION: Find the RKT Training system
Please open SAP Logon and create a new Connection for the system “ZME” if not already there.
SOLUTION: Acti vate your personal user and veri fy the necessary authorizations
Please logon to MDG backend system ZME with your user ID TZMDG1-## with ##representing your group number.
You will be prompted to change your password.
Now launch transaction SU01 for User Maintenance.
In transaction SU01, please enter your User ID and press “Display” (that little glasses symbol above / F7). Navigate to
the “Roles” tab. You will see (at least) the following roles assigned to your user:
SAP Class Week of March 12, 2012
5
SOLUTION: Access the corresponding enterprise portal and verify the necessary roles
Please logon to Portal with your user ID TZMDG1-## with ##representing your group number.
http://portal-zme.wdf.sap.corp:50000/irj/portal
The corresponding portal roles for are: “Financial Master Data Manager”, “Material Master Data Manager”, “Supplier
Master Data Manager”, and “ERP Common”.)
SAP Class Week of March 12, 2012
6
Sol ut i on Ex er c i se 2: Searc h f or Mat er i al and change i t
Your company is in the CD manufacturing business and has enhanced an existing product line. Before you can add
further products you want to ensure that the main lab has enough capacity to ensure the quality of the new products.
Therefore you want to move the q-processes of the existing product line “Demo CD” to another q-lab.
Search for the Demo CD
Start your search in the Material work center.
Add search attribute “Medium Text” and choose relation operator as “contains” and enter search attribute value for this
field as “Demo” as shown under & click on the Search button
SAP Class Week of March 12, 2012
7
How many materials with description containing “Demo” do exist ? _________82_______________
Narrow down your search to materials starting with “ACT” in their ID.
Change Material ACT-DCD-##and assign “Laboratory 2” as the Lab/Office. Submit the change and run through the
approval process.
Maintain the Change Request Header data, adjust the Lab/Office and submit the change request:
SAP Class Week of March 12, 2012
8
From the result either navigate to the “Show My Change Requests or close and go to your workflow inbox. This is now
shown:
Start the workflow item by clicking on the hyperlink or use the “Process Change Request” button.
SAP Class Week of March 12, 2012
9
From here you can activate.
Review your change in the ERP backend using transaction MM03 “Display Material”.
Sol ut i on Ex er c i se 3: Searc h f or Mat er i al and t r i gger a c opy
SAP Class Week of March 12, 2012
10
Your company is in the CD manufacturing business and has enhanced an existing product line. Therefore additional
master data needs to be maintained in order to reflect the business in the ERP backend system. You now also want to
manufacture Mini-CDs and therefore you need the correct labels.
As a long term and loyal SAP customer, your company has decided to use Master Data Governance for this!
Search for the CD labels
Start your search in the Material work center.
Add search attribute “Medium Text” and choose relation operator as “contains” and enter search attribute value for this
field as “label” as shown under & click on the Search button
How many materials with description containing “label” do exist ? ___________132_____________
Narrow down your search to Raw material (ROH), how many? ____________72____________
SAP Class Week of March 12, 2012
11
Add additional search attribute “Material Type” by clicking on the (+) button and enter search attribute value for this as
“ROH (Raw Materials” either directly or choosing via F4 help and then click on the “Search button” to get the result list
as shown below.
Finally you are only interested on CD labels of your group ##in the material group 00213,
please note the material IDs __ ACT-BCD-##, ACT-LCD-##___
Add additional search attribute “Material Group” by clicking on (+) button and then enter attribute value as “00123”
Copy an existing label to a new material “ Mini-CD”
Copy one of the materials to the new label for Mini-CDs (Material ID ACT-MCD-xx). Adjust the descriptions.
Submit and Approve the change request.
SAP Class Week of March 12, 2012
12
From the search result list shown above, select the record and then select the “Copy” button on the result list tool bar.
SAP Class Week of March 12, 2012
13
You might want to trigger this activity directly from the search results
SAP Class Week of March 12, 2012
©2011 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, 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 other
countries.
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 registered
trademarks of Business Objects Software Ltd. in the United States and in other countries.
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.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors
or omissions with respect to the materials. The only warranties for SAP Group 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.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
The roles ensures that only the necessary steps can be started.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
The services in the work center are assigned to a Business Activity.
The business activity determines:
Data Model
Change Request Type
(Several Change Request Types can be assigned to one Business Activity.
In that case, the user has to select the Change Request Type that he wants to use.)
The Change Request Type determines:
The workflow template
The data model and the entity types
The possible workflow steps can be defined in the workflow or in the change request type.
The processor is determined per workflow step.
The UI Configuration can be determined per entity type for the change request type. A default
UI configuration can be assigned to a user per data model.
SAP Class Week of March 12, 2012
You must configure the change requests that have been imported using the BC-set as
described in the corresponding section of this document.
Depending on your company’s requirements you might want to adjust and enhance the
default values.
The following information describes the minimal settings for a basic governance process. For
more detailed information on each customizing activity, see the relevant documentation for
that customizing activity.
1. Review and/or define which statuses the change requests can have, and which
processing options are enabled for those statuses. Optionally, you can add new statuses
to be used in the change request types defined in the next step.
For more information, see Customizing for Master Data Governance under
General Settings Process Modeling Change Requests Edit Statuses of Change
Requests
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
4. Optionally, you can define priorities, reasons, or rejection reasons for change requests.
You can enter codes and a short description in order to tag or classify your change requests.
These codes can later be used for change request analytics (process quality analysis). They
also can be used to influence the workflow-driven processes, for example, depending on the
priority of a change request you can decide if it requires special processing.
Perform the following activity in Customizing for Master Data Governance under
General Settings Process Modeling Change Requests Define Priorities / Reasons /
Rejection Reasons for Change Requests
5. Optionally, you can define print forms for change requests. By default the form
USMD_EDITION_CREQUEST is used. This is relevant only if your own or multiple print
forms are required.
For more information see Customizing for Master Data Governance under
General Settings Process Modeling Change Requests Define Print Form for Change
Requests
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
There are two types of search options available.
Embedded Search (included in SAP NetWeaveron a local system)
SAP NetWeaverEnterprise Search (run centrally)
If you want to use Embedded Search, run the following activity in Customizing under
SAP NetWeaver Search Embedded Search
Search Engine Service
This needs to be done if you are running a central SAP NetWeaverEnterprise Search system
and you connect other SAP NetWeaversystems with Embedded Search to the central
system. Follow the steps as described in customizing under
SAP NetWeaver Search Search Engine Service
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP delivers the following three standard templates for MDG which are located in SAP_APPL. You
need to activate these templates and prepare them for indexing.
Material (MATERIAL) – for the active data residing on the standard tables MA* and related objects
Material Template for MDG (MDG_MATERIAL) – for the inactive material data linked to the MDG
change requests
Supplier Template for MDG (MDG_BUSINESS_PARTNER) – for the inactive supplier / BP data
within change requests
For more information, see:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/72/b595166625664fbdc110d54639f27b/frameset.ht
m
If the TREX_ADMIN user is not available, create it with the required roles as mentioned in the SAP
OSS note 766516for the target system
Connect to the TREX installation:
During TREX installation an RFC-destination for the TREX has been created. Verify via SM59 in the
TCP/IP connections section that it exists and can be linked.
Link the ABAP System to this TREX destination. For more information see Customizing for SAP
NetWeaverunder
Search Embedded Search Set TREX Destination
Alternatively you can run the report ESH_ADM_SET_TREX_DESTINATION.
Create and index the connectors
Open the Connector Administration Cockpit in Customizing for SAP NetWeaverunder
Search Embedded Search Modeling, Administration, and Monitoring Open Administration
Cockpit
alternatively you can use transaction ESH_COCKPIT.
Open the “Template Modeler” via the Hyperlink
Use the “Find” function to locate the two templates
SAP Class Week of March 12, 2012
c. Via menu “Actions” use the option “Create Connector” to create a search connector for the
corresponding templates.
The search connectors will be created in the background via a job.
The job can be monitored in via the Administration Cockpit
Note: The connectors need to be created starting from the highest software component. If
SAP_APPL is not the highest one (e.g. when EA-APPL or PLM/WUI is active) you need to
navigate to the template within this path to ensure consistency.
SAP Class Week of March 12, 2012
d. Go back to the Administration Cockpit – the two Connectors “Material” and “Material
template for MDG” are now visible and in status “preparing”.
Via menu “Actions” use the option “Schedule Indexing” and use the Input Form.
There choose the option for immediate indexing and the recurrence period.
You can also activate real-time indexing if the sizing, parameters and performance of the
system allow for this.
Transfer the settings to the relevant Object Types and start indexing.
Repeat this for the “Material template for MDG” .
In the Administrator Cockpit the status has changed to “Indexing”.
After successful indexing the status changes to “active”.
The Object Type “USER_AUTHORIZATION” cannot be indexed real-time. So ensure that for
this Object time regular scheduling e.g. every hours is active.
This ensures that new users will be able to retrieve the data during search from TREX.
Otherwise they will not get back any results.
SAP Class Week of March 12, 2012
e. Control successful indexing. Status has changed to “Active”.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
MDM home on SDN is a perfect means of communication to customers. It keeps all relevant
information plus links to collaborative WIKI and forum spaces.
SAP.com also provides an up-to-date picture of NW MDM and MDG
SAP Class Week of March 12, 2012
Customers and prospects will have their first encounter with MDM and MDG via sap.com.
Here they can find
a high level description
Factsheets and solution briefs
self-running demos
and customer testimonials not only for NW MDM (available now) but as well for MDG – we
are convinced they will appear soon
SAP Class Week of March 12, 2012
The SDN discussion forum is an external community space where information, software
issues and ideas are shared. SAP MDG has entered the space. You may watch and actively
participate in the forum.
SAP Class Week of March 12, 2012
And to provideyou with a summaryof the completeMDM story, we havepublisheda
summaryarticle and an FAQ documentthat covers commonquestions that maycome up
whenengagingwithcustomers…
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
For example, we haveopeneda dedicatedMDM communityon J ive whichis controlledby
solutionmanagement. This communityis intendedas your informationstorethatholds up-to-
datepresentationson MDM (either positioningand software-related)
SAP Class Week of March 12, 2012
In additionwe haveset up a comprehensiveMDM WIKI that provides you withall relevant
links to get preparedin terms of positioning, consulting-relevantquestions, use of demos etc.
SAP Class Week of March 12, 2012
Finallywe havepreparedeasyto consumee-learningkits for thefieldcollegues, so that they
canprepare themselves for customer interactions and positioningtheupcomingMaster data
governanceapps…
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Live Customers
1 MDGF EhP4 – Agribusiness/Food (US)
1 MDGF EhP5 – Consumer Products (US)
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
2_48
SAP Class Week of March 12, 2012
2_48
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
MDM home on SDN is a perfect means of communication to customers. It keeps all relevant
information plus links to collaborative WIKI and forum spaces.
SAP.com also provides an up-to-date picture of NW MDM and MDG
SAP Class Week of March 12, 2012
Customers and prospects will have their first encounter with MDM and MDG via sap.com.
Here they can find
•a high level description
•Factsheets and solution briefs
•self-running demos
•and customer testimonials not only for NW MDM (available now) but as well for MDG – we
are convinced they will appear soon
SAP Class Week of March 12, 2012
The SDN discussion forum is an external community space where information, software
issues and ideas are shared. SAP MDG has entered the space. You may watch and actively
participate in the forum.
SAP Class Week of March 12, 2012
And to provideyou with a summaryof the completeMDM story, we havepublisheda
summaryarticle and an FAQ documentthat covers commonquestions that maycome up
whenengagingwithcustomers…
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
For example, we haveopeneda dedicatedMDM communityon J ive whichis controlledby
solutionmanagement. This communityis intendedas your informationstorethatholds up-to-
datepresentationson MDM (either positioningand software-related)
SAP Class Week of March 12, 2012
In additionwe haveset up a comprehensiveMDM WIKI that provides you withall relevant
links to get preparedin terms of positioning, consulting-relevantquestions, use of demos etc.
SAP Class Week of March 12, 2012
Finallywe havepreparedeasyto consumee-learningkits for thefieldcollegues, so that they
canprepare themselves for customer interactions and positioningtheupcomingMaster data
governanceapps…
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Live Customers
1 MDGF EhP4 – Agribusiness/Food (US)
1 MDGF EhP5 – Consumer Products (US)
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
2_48
SAP Class Week of March 12, 2012
2_48
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Master Data Governance – Documentation
Overview
(the following links lead to English versions as default; Version as of 06-July-2011)
MDG Documentation
KW Documentation
Application Help EHP5 (incl. configuration documentation)
http://help.sap.com/erp2005_ehp_05/helpdata/en/7c/a94fabb8274d738d994c2bc1c4cf7a/frameset.htm
Business Functions:
All MDG BFs in KW:
http://wbhelp.sap.com/ERP2005_EHP_05/helpdata/EN/E1/3D16C63EF142A88AA41524073A038F/frameset.htm
Business Packages (for the Enterprise Portal)
http://help.sap.com/erp2005_ehp_05/helpdata/en/9a/a02b9a81f346479ad4f9fc59a2a760/frameset.htm
MDG Note for EhP5
MDG General Note for EhP5
1473138 (MDG central documentation note which provides links to other notes, documents, etc)
https://service.sap.com/sap/support/notes/1473138
EhP5 SP03: Rel ease & informati on note
1541825 - Master Data Governance Ehp5 SP03: Release & information note
https://service.sap.com/sap/support/notes/1541825
MDG as part of ERP Guides
Guide for ERP EhP5:
Master Guide, Upgrade Master Guide, Installation Guides, Upgrade Guides
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000735870&_SCENARIO=0110003587000000
0202&
ERP EHP5 Release notes:
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000731802&_SCENARIO=01100035870000000
202&
ERP central notes on enhancement packages
http://service.sap.com/~sapidb/011000358700000951782009E/TABLE_EHPNOTES.htm
MDG-is part of the generic ERP Solution Operations Guide (SOG):
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000671165&
Operations Guide
for SAP enhan...
MDG is part of the generic ERP Security Guide:
http://service.sap.com/~form/sapnet?_SHORTKEY=01200252310000090525&
Chapter for MDG:
http://help.sap.com/erp2005_ehp_05/helpdata/en/4b/675927dae72b5fe10000000a42189c/frameset.htm
SAP Class Week of March 12, 2012
Specific Guides
FIN Upgrade Guide
1456270 (FIN Upgrade Note) https://service.sap.com/sap/support/notes/1456270
Config Guides
Are part of the standard documentation, sometimes internal versions with screenshots do exist.
MDG overall documentation (Configuration & Application, incl. Configuring Master Data Governance for Custom
Objects)
http://help.sap.com/erp2005_ehp_05/helpdata/en/7c/a94fabb8274d738d994c2bc1c4cf7a/frameset.htm
Configuration Guide General Settings (incl. enhancement)
http://help.sap.com/erp2005_ehp_05/helpdata/en/4b/81f46cb11a41c38dd53db5b0cc6ea9/frameset.htm
Configuring MDG for Financials
http://help.sap.com/erp2005_ehp_05/helpdata/en/ad/d9b1d07d1b4aec9fd44020739e776b/frameset.htm
Configuring MDG for Material
http://help.sap.com/erp2005_ehp_05/helpdata/en/b2/9a55fd374848a1b70679180b08514b/frameset.htm
Configuring MDG for Supplier
http://help.sap.com/erp2005_ehp_05/helpdata/en/70/47f6938f70420f801be80a0df9fc30/frameset.htm
Extensibility – Cookbook
MDG Extensibi lity Center in SDN:
http://www.sdn.sap.com/irj/sdn/master-data-governance?rid=/webcontent/uuid/f0801486-9562-2e10-54b1-
9c123497f1a7
BLOG Version by Lars Rueter
Material http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/24038
Supplier Part 1: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/24172
Supplier Part 2: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/24175
Original MDG Extensibility Guide as of May 2010
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b0679444-883a-2e10-faae-
b881c0f36c2b&overridelayout=true
BI Content
MDG Financial BI Content
http://help.sap.com/erp2005_ehp_05/helpdata/en/4a/658c756455260be10000000a42189b/frameset.htm
Main other sources of content for MDG
WIKIS (SAP internal only)
MDG WIKI:
https://wiki.wdf.sap.corp/wiki/display/MDG/Documents+and+Learning
Field WIKI:
https://wiki.wdf.sap.corp/wiki/display/GFOSolutionBD/Master+Data+Management+Solutions
RKT Learning Maps
http://service.sap.com/RKT-ERP
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000732299&
Master Data Governance - General
http://service.sap.com/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000531382010E
Master Data Governance for Financials
http://service.sap.com/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000531392010E
Master Data Governance for Material
http://service.sap.com/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000531402010E
Master Data Governance for Supplier
http://service.sap.com/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000531412010E
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
The data model in MDG can contain:
Exactly the same attributes as the corresponding customizing table or
Only Id, description and maybe selected other attributes of the corresponding customizing
table or
Additional attributes that are not part of the corresponding customizing table.
The attributes that are defined in the data model are maintained in MDG.
Data can be sent out by DRF. The outbound implementation can be generated via RIF.
The RFC for the inbound implementation in target systems can be generated by RIF in the
MDG system. It can then be copied into the target system.
Additional functionality of the inbound RFC:
Update only those attributes that are maintained in MDG. Other attributes must not be
overwritten.
Create (or select) a transport request for transport to other operational systems
The view cluster maintenance for the corresponding customizing tables should be
enhanced with the following functionality:
Creation of new objects or deletion of objects should not be possible any more, as creation
and deletion should only be triggered from MDG
The attributes that are maintained in MDG should not be changed any more. (unless
values from MDG are only regarded as default values).
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
TYPE1:
For “Main table(s)” and/or any table to be maintained in MDG
No Qualifying relationships (Only Leading & Referencing)
TYPE2:
For Lookup data to be maintained in MDG but without attributes
TYPE3:
For Lookup data to be maintained outside of MDG without attributes
TYPE4:
No Key Fields
Used for Type1 extension/qualification
For qualified table data, text data extensions for Type#1.
Only 1 Leading relation can be created, and 1 qualifying is required ; others have to be
qualifying or Referencing
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
As an example we will extend the (Type1) entity MATERIAL by the following entity ZZMARC
and attributes
LVORM: Flag Material for Deletion at Plant Level
XCHAR: Batch management indicator (internal)
DISMM: MRP Type
DISPO: MRP controller
DISLS: MRP Lot Size
SAP Class Week of March 12, 2012
The entity and the attributes correspond to fields of table MARC and should also being
displayed in the UI.
The types of entities are indicated in the numbered circles.
The keys of MARC table are material number and plant number, so you will find here
a leading relationship (type 1) from Material to Plant Data, which means you will be able to
maintain plant data within a material master. This relationship also defines one of both keys
for Plant Data.
a qualifying relationship (type 4) from Plant to Plant Data. This relationship defines the other
key of Plant Data.
The rest of relationships here are of type Referencing (type 3). They can be considered
equivalence to the customizing tables in ERP system.
SAP Class Week of March 12, 2012
The relationships can be defined as follows:
Using relationships with the relationship type Referencing, you specify that the from-entity
type is an attribute of the to-entity type.
If you use Leading or Qualifying as the relationship type, you specify that the from-entity type
is on a higher level than the to-entity type. The from-entity type is automatically taken as the
key in the generated tables in this case.
The difference between the relationship types Leading and Qualifying is only relevant for to-
entity types with storage and use type4. The master data of these to-entity types is processed
in the context of the entity type that is assigned using the leading relationship.
===
Attributes can be added only for Type 1 and Type4
Type 1 has only Leading and Referencing relationship
Type1 does not have Qualifying relationship
Type 4 must have one(only?) Leading Relationship
Type4 must have one Qualifying Relationship and can have more
Type4 can have any type of relationship – Leading, Qualifying, Referencing
Type2 Leading relationship allowed
Type2 does not have Qualifying relationship
If E2 has a key of E1 as a PK then use Leading relationship
If E2 has a key of E1 as a PK and E2 is Type 4 - then only Qualifying relationship
If E2 has a key of E1 but no PK, then use
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
The UI will be configured with the FloorplanManager. The FloorplanManager (FPM) is a
Web Dynpro ABAP application that provides a framework for developing new Web Dynpro
ABAP application interfaces consistent with SAP UI guidelines.
An FPM application is composed of a number of different Web Dynpro components (most of
which are instantiated dynamically at runtime). However, the following two components are
always present:
a floorplan-specific component (FPM_GAF_COMPONENT or FPM_OIF_COMPONENT)
a component for the Header Area (FPM_IDR_COMPONENT)
In simple terms, the configuration of an FPM application is the configuration of these two
components.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
The services in the work center are assigned to a Business Activity.
The business activity determines:
Data Model
Change Request Type
(Several Change Request Types can be assigned to one Business Activity.
In that case, the user has to select the Change Request Type that he wants to use.)
The Change Request Type determines:
The workflow template
The data model and the entity types
The possible workflow steps are defined in the workflow.
The processor is determined per workflow step.
The UI Configuration can be determined per entity type for the change request type. A default
UI configuration can be assigned to a user per data model.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
CUSTOM OBJ ECTS
TZMDG1 – Exercise 2.1
Exercises / Solutions
Alfred Schaller / SAP AG
Exercise(s):Configure custom object and run creation
process
At the end of this exercise you are able to:
Define a data model for custom objects in MDG
Create a UI configuration in MDG
Define and execute a simple change process in MDG
You as the Business Process Expert of a travel agency are now supposed
to implement a change process for airline data because these data shall be
maintained in a governance process
All objects of this exercise are named with ##. Please replace this with
your group number:
## = Group Number = 01 – 30
Parameters valid throughout the Exercise(Replace ##with your two-digit
Team Number):
Logon to the SAP System [….]
Username: TZMDG1-##
Password: initial
In MDG you are able to work with the internet based Netweaver
Business Client (NWBC) or via the enterprise portal
SAP Class Week of March 12, 2012
2
Ex erc i se 1
You have to define a data model for the master data of an airline.
Define the data model ##(X#for 0#, Y#for 1#and Z#for 2#).
Start editing with transaction SM34 View Cluster VC_USMD001S, so that you do not lock the complete table of data
models for other groups.
In a classroom situation, please ensure that only one data model is activated at a time and wait for activation until the
other group has finished their creation.
The requirement is to implement a simple model of an airline (carrier) that should include a few fields an attributes
You would need of course an ID
A text for description
A URL shall be added
The carrier should include an existing lookup table for a currency
Pl ease pl an a data model and
check how many and what entity types you need
what is their relationship
which of the fields are automatically available via an entity type
and which additional attributes need to be modeled
--------------------------------------- Space for your model -----------------------------------------------
--------------------------------------- Space for your model -----------------------------------------------
Defi ne Entity Type “ Arline”
Create a new entity type CARR for the object “Airline” with these properties:
It shall be changeable via Change Requests, and a data base table shall be generated for it.
Validity for editions is not needed.
The identification is defined with the data element S_CARR_ID.
Hierarchies are not needed.
A text with length of 20 characters shall not be language-dependent. (Please use “Medium text”)
Fill the description with “Airline”
For other properties leave default values.
Add an optional attribute “URL” to this new entity type with data element S_CARRURL.
Defi ne Entity Type “ Currency”
Create an entity type CURRENCY for the possible currency codes that can be assigned to an airline.
The table of currency codes that shall be used already exists.
It shall not be changeable via MDG.
It is defined with the data element S_CURRCODE.
Fill the description with “Currency”
For other properties leave default values.
SAP Class Week of March 12, 2012
3
Define a relationship from the entity type CURRENCY named CARR_CURR to the entity type CARR, so that exactly 1
currency must be assigned to every airline. It shall be possible, to assign the same currency to several airlines.
(You could enter any other name for CARR_CURR, but then you would later have to adapt the UI configuration after
copy from data model Z9.)
Acti vate and display Data Model
Save and activate your data model.
Display an over view of your data model using report USMD_DISPLAY_DATA_MODEL.
Ex erc i se 2
You have to define a UI Configuration for the single object maintenance of an airline with an MDG change request.
Create UI Configuration
Please use the UI Configuration Z9SF of data model Z9 as a template for the creation of your UI configuration.
You should name your configuration ##SF (X#for 0#, Y#for 1#, Z#for 2#).
Please name the configuration for your Identification Region ##SF_IDR, and for your Object Instance Floorplan
##SF_OIF. Open the complete tree and name your form ##SF_CARR
Create your configuration as a local object.
Assign your configuration to your data model ##that you defined in Exercise 1.
Configure the Form UIBB so that:
The text of the airline shall be displayed in the first line.
The width of the URL on the screen shall be limited to 30 elements.
Show a preview of the UIBB.
HINT: you can navigate between the different views (E.g. component und UI configuration) via path / bread-crumbs
below the toolbar
Finally test your UI configuration.
Ex erc i se 3
You have to define a change process for the maintenance of an airline with an MDG change request.
Create Change request type
Create a new change request type ##SF that can be used for your data model ##with these properties:
One change request shall only be used for processing one single airline.
You do not want to maintain an object list at the creation of the change request.
The main entity typ is CARR
The change process shall consist of the steps: Create, Maintain, Approve, and the optional step “Revision”
(after rejection). These steps are defined in workflow template WS75700040.
On Entity type level for the entity type CARR the UI Configuration shall be used, that you defined in Exercise 2.
Assign processor to workflow steps
For test purposes, all workflow steps of your change request type shall be processed by yourself.
Assign your user-id to all 3 steps of the standard simple workflow of your change request type.
Personalize your user with defaults
For easy testing, maintain defaults for data model and UI Configuration in your user.
In the personalization of your user for SAP Master Data Governance enter your data model ##as standard data model.
For that data model enter your UI Configuration ##SF, your change request type ##SF and the entity type CARR.
SAP Class Week of March 12, 2012
4
Ex erc i se 4
Test creation of an airline with the change request type that you have configured.
In order to process the following step use the generic change processing offered within the financials role.
Create Change request
Create a change request of your change request type for the creation of an airline.
Enter any id for the new airline.
Enter any text, why you need to create the airline.
Enter any name and currency for the airline.
Submit your change request.
Process Change request
Look for the change request in your inbox in NetWeaver Business Client.
Select the change request.
Enter a URL for the airline.
Finalize the change request.
Approve Change request
Look for the change request in your inbox in NetWeaver Business Client.
Select the change request.
Check the data that you have entered before.
Approve the change request.
Review your entri e(s)
Search and display your new created entities.
Review the change documents / audit trail for your entrie(s)
Ex erc i se 5
You may want to create your own Business Activity, link your Change Request Type to that Business Activity and
create your own menu entry using this.
SAP Class Week of March 12, 2012
5
Sol ut i on Ex er c i se 1
You have to define a data model for the master data of an airline.
Define the data model ##(X#for 0#, Y#for 1#and Z#for 2#).
The requirement is to implement a simple model of an airline (carrier) that should include a few fields an attributes
You would need of course an ID
A text for description
A URL shall be added
The carrier should include an existing lookup table for a currency
Pl ease pl an a data model and
check how many and what entity types you need
what is their relationship
which of the fields are automatically available via an entity type
and which additional attributes need to be modeled
--------------------------------------- Space for your model -----------------------------------------------
Data Model ___
Entity Type Entity Type
CARR (Type 1)
Fields:
ID (automatically provided via domain of data element
Text (via Entity Type attributes)
URL (attribute of leading entity type
CARR_CURR 1:n relationship to CURRENCY (Type 4)
--------------------------------------- Space for your model -----------------------------------------------
Start editing with transaction SM34 View Cluster VC_USMD001S, so that you do not lock the complete table of data
models for other groups.
Enter your data model ##:
SAP Class Week of March 12, 2012
6
Defi ne Entity Type “ Arline”
Create a new entity type CARR for the object “Airline” with these properties:
It shall be changeable via Change Requests, and a data base table shall be generated for it.
Validity for editions is not needed.
The identification is defined with the data element S_CARR_ID.
Hierarchies are not needed..
A text with length of 20 characters shall not be language-dependent. (Please use “Medium text”)
For other properties leave default values.
Add an attribute “URL” with data element S_CARRURL.
Select “New Entries”:
Enter properties:
SAP Class Week of March 12, 2012
7
Select level “Attributes”, select “New Entries” and enter the attribute “URL”:
SAP Class Week of March 12, 2012
8
Defi ne Entity Type “ Currency”
Create an entity type CURRENCY for the possible currency codes that can be assigned to an airline.
The table of currency codes that shall be used already exists. It shall not be changeable via MDG.
It is defined with the data element S_CURRCODE.
Define a relationship from the entity type CURRENCY to the entity type CARR, so that exactly 1 currency must be
assigned to every airline. It shall be possible, to assign the same currency to several airlines.
Go back to level “Entity Types, select again „New Entries“ and enter properties of entity type CURRENCY:
Select ”Relationships”, select “New Entries”, and enter the relationship:
SAP Class Week of March 12, 2012
9
Acti vate and display Data Model
Save and activate your data model.
Display an over view of your data model.
Select “Save” and “Activate”. If the system prompts for a Workbench Request, create a new one or select any existing
request of your own requests.
For Display of the data model, start report USMD_DISPLAY_DATA_MODEL via transaction SA38 and select your data
model ##on the next screen:
SAP Class Week of March 12, 2012
10
SAP Class Week of March 12, 2012
11
Sol ut i on Ex er c i se 2
You have to define a UI Configuration for the single object maintenance of an airline with an MDG change request.
Create UI Configuration
Please use the UI Configuration Z9SF of data model Z9 as a template for the creation of your UI configuration.
You should name your configuration ##SF (X#for 0#, Y#for 1#, Z#for 2#).
Please name the configuration for your Identification Region ##SF_IDR, and for your Object Instance Floorplan
##SF_OIF.
Create your configuration as a local object.
Assign your configuration to your data model ##that you defined in Exercise 1.
Configure the Form UIBB so that:
The text of the airline shall be displayed in the first line.
The width of the URL on the screen shall be limited to 30 elements.
Show a preview of the UIBB.
Start transaction MDGIMG and select “Edit UI Configuration”:
SAP Class Week of March 12, 2012
12
Select data model Z9 and UI Configuration Z9SF and select “Create with Template”:
Expand all configurable components. Then overwrite the proposed names for the target configuration and select “Start
Deep-Copy”:
On the PopUp select “Local Object”:
SAP Class Week of March 12, 2012
13
Close the window, refresh the list of UI Configurations, select your new UI configuration, which should appear in the list
under data model Z9, and select “Edit”:
On the next screen, select “Change”:
SAP Class Week of March 12, 2012
14
Select tab “Application Parameters” and enter your data model ##in parameter USMD_MODEL:
SAP Class Week of March 12, 2012
15
Save your configuration, select tab “Structure”, mark the line OIF_COMPONENT and select “Go to Component
Configuration”:
Select “Configure UIBB”:
Select “Configure Group”:
SAP Class Week of March 12, 2012
16
Move field TXTMI up:
Mark Element Airline URL and enter the required width.
Then save your configuration
SAP Class Week of March 12, 2012
17
Go back to your OIF configuration and select “Show UIBB Preview”:
SAP Class Week of March 12, 2012
18
SAP Class Week of March 12, 2012
19
Sol ut i on Ex er c i se 3
You have to define a change process for the maintenance of an airline with an MDG change request.
Create Change request type
Create a new change request type ##SF that can be used for your data model ##with these properties:
One change request shall only be used for processing one single airline.
You do not want to maintain an object list at the creation of the change request.
The change process shall consist of the steps: Create, Maintain, Approve, and the optional step “Revision” (after
rejection). These steps are defined in workflow template WS75700040.
For the entity type CARR the UI Configuration shall be used, that you defined in Exercise 2.
Select in the IMG “Create Change Request Type”, select “New Entries” and enter your change request type:
Go to level “Entity types”, select “New Entries” and enter the entity type CARR with your UI configuration:
Save your data. If the system prompts for a Customizing Request, create a new one or select any existing request of
your own request.
Assign processor to workflow steps
For test purposes, all workflow steps of your change request type shall be processed by yourself.
Assign your user-id to all steps of your change request type.
SAP Class Week of March 12, 2012
20
Select in the IMG “Assign Processor to Workflow Step Number”:
Select “New Entries” and enter your user id for your change request type for workflow steps 1 – 3:
SAP Class Week of March 12, 2012
21
Personalize your user with defaults
For easy testing, maintain defaults for data model and UI Configuration in your user.
In the personalization of your user for SAP Master Data Governance enter your data model ##as standard data model.
For that data model enter your UI Configuration ##SF, your change request type ##SF and the entity type
CARR/Airline.
Start transaction SU01, select tab “Personalization” and scroll down to object key R_FMDM_MODEL:
Double click on personalization object “SAP Master Data Governance”, enter your data model ##as Standard Data
Model. You can also enter your UI Configuration and change request type as defaults.
SAP Class Week of March 12, 2012
22
You can also enter the same personalization in a role, but please do not do this here because this change will affect all
users of that role:
The user can later change the personalization:
SAP Class Week of March 12, 2012
23
Sol ut i on Ex er c i se 4
Test creation of an airline with the change request type that you have configured.
In order to process the following step use the generic change processing offered within the financials role.
Create Change request
Create a change request of your change request type for the creation of an airline.
Enter change request header information and any id for the new airline, press next
Enter any text, why you need to create the airline, press next
SAP Class Week of March 12, 2012
24
Enter any name and currency for the airline, press next.
Check your data and submit your change request.
Process Change request
Look for the change request in your inbox in NetWeaver Business Client.
Alternatively you can use the link “Show my change Requests”
Select the change request.
Enter a URL for the airline.
Finalize the change request.
Approve Change request
Look for the change request in your inbox in NetWeaver Business Client.
Select the change request.
Check the data that you have entered before.
Approve the change request.
Review your entri e(s)
Search and display your new created entities.
Review the change documents / audit trail for your entrie(s)
Sol ut i on Ex er c i se 5
You may want to create your own Business Activity, link your Change Request Type to that Business Activity and
create your own menu entry using this.
Please see the slides in the corresponding chapter where it is explained.
SAP Class Week of March 12, 2012
©2010 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, 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 other
countries.
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 registered
trademarks of Business Objects Software Ltd. in the United States and in other countries.
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.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors
or omissions with respect to the materials. The only warranties for SAP Group 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.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
MDAF Rule-Based WorkflowWS60800086
MDAF-Sub-Workflow for RBWF WS60800091
Validation Workflow WS75700019
Change Request Workflow in FMDM WS75700027
Single Object Workflow WS75700040
Financials Advanced Workflow WS75700043
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
The services in the work center are assigned to a Business Activity.
The business activity determines:
• Data Model
Change Request Type
(Several Change Request Types can be assigned to one Business Activity.
In that case, the user has to select the Change Request Type that he wants to use.)
The Change Request Type determines:
• The workflow template
• The data model and the entity types
The possible workflow steps are defined in the workflow.
The Status of the change request and the workflow step are used in the process logic of the
workflow in order to determine:
• The possible actions in the UI
• The next workflow step
• The next change request status
SAP Class Week of March 12, 2012
In addition to allowing workitems to be displayed and administered, the integrated inbox
supports the full mail functionality of SAPoffice.
The workitem manager is responsible for processing workitems, including the deadline
monitoring. Activities can also refer to methods that run in the background, and in this case
the workitem manager initiates the call to the background processes.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Set up or check the Business Rule Framework Plus (BRFplus)
1. Run transaction BRF+ (BRFplus Workbench) and switch to expert mode by choosing Workbench User
Mode.
2. Select object MDG_BS_ECC_SUPPLIER_WF_CUSTM. If this is not already in your repository, search for it
in the menu. To search, choose Workbench Open Object.
In the search, enter the following values, and from the search result select
MDG_BS_ECC_SUPPLIER_WF_CUSTM.
- In the Customizing Objects field, enter X.
- In the Name field, enter MDG*.
3. Add the selected object to your repository. From the Workbench menu, choose Add Current Objects to
Favorites.
4. If the search result does not contain MDG_BS_ECC_SUPPLIER_WF_CUSTM, export the content from client
000. Run the BRF+ transaction in client 000 and search for MDG_BS_ECC_SUPPLIER_WF_CUSTM as
described above.
To export the content from client 000, do the following:
- Right-click on the application in the repository, and from the Tools menu, choose XML Export.
- Choose Include Referenced Objects, generate xml-file, and download it to your PC.
- To import the content to your MDG main client, in the test client run the BRF+ transaction and from the
Tools menu, choose XML Import.
- Select your xml-file and click Upload File (you can also assign it to a transport request or run a check-
import first).
5. Assign agents to a decision table.
- In the BRF+ transaction, go to application MDGS: Customizing WF and choose Expressions Decision
table: <get agents> .
- Maintain agents (for example, the users or organizations used in SAP NetWeaver Portal role assignment),
for all change request types, and their created workflow steps. For example, not mentioned =not maintained,
initial.
- The picture above shows the change request types and their workflow steps. The entries either refer to a
single user by using object type US or to a complete organizational unit by using the object type O.
Note: There are no entries relevant for change request type SUPPL0A.
SAP Class Week of March 12, 2012
The badi checks the layer we are on so if its ERP then it checks the BRF+customizing else it
evaluates the users maintained in IMG.
SAP Class Week of March 12, 2012
The change request workflow can also be configured with intermediate approval steps.
Details are described in the processes for supplier.
SAP Class Week of March 12, 2012
The change request workflow can also be configured with parallel approval steps for specifc
parts of data. The process ends, when all parallel approval steps have been decided.
Details are described in the processes for supplier.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Master Data Governance allows the flexible usage of the SAP Business Workflow.
Two forms of business workflow exist:
1) Standard Business Workflow – including default content delivered for Supplier and Financials
2) Rule-based Workflow – including default content delivered for Material
In both cases, SAP provides default workflows for simple tasks and organizations. Flexible customizing setting
enable the use of both flavors for all domains, so it is also possible to, for example, use the rule-based workflow
for Supplier or use standard business workflow for Material.
The workflow is linked to and can be defined by change request type (see the chapter on setting up change
request types).
In MDG for Material the process is a two-step approval that is following the two-man rule (Vier-Augen-Prinzip)for
governance purposes.
1) The business user requests the creation of a material or the change of material data. After completing the
input, the business user “submits” the change request.
2) The master data expert is notified through his worklistthat a new change request is created. The expert
reviews the data, can change or enhance it, and “approves” the change request
Since the expert needs to be able to send back the request for clarification, an additional branch for revision and
re-submit is included in the standard workflow. This process can be described as following:
1) The business user requests the creation of a material or the change of material data. After completing the
input, the business user “submits” the change request.
2) The master data expert is notified through his worklistthat a new change request is created. The expert
reviews the data, can change or enhance it, and then sends the review back for “revision” and clarification
purposes
3) The business user can decide to cancel the request (For example in cases where a suitable material already
exists and duplication is undesirable) or adjust the data and “re-submit” the request
4) The master data expert can again review and revise the request – if the data is complete and correct the
expert will approve the change request.
MDG uses the standard workflow inbox or personal worklists. Therefore individual assignments and manual
dispatching can be used as well. This flexibility allows to handle exceptions and to concentrate the setup and
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
2. Check that the following business activities are in your system and that they are assigned to the default data model MM.
MAT1, MAT2, MAT6, MATA
For more information, see Customizing for Master Data Governance under
General Settings Process Modeling Change Requests Create Business Activity
3. Create new change request types for data model MM, or validate after import using the business configuration set (BC-Set).
For more information, see Customizing for Master Data Governance under
General Settings Process Modeling Change Requests Create Change Request Type
Alternatively, you can run system transaction SM34 and view cluster VC_USMD110.
The following settings should exist in the substructures of the change request types:
MAT01:
Entity type: MATERIAL
UI Config: MDG_MM_APP_BS_MAT_GEN
Msg. Output: "W Issue Error Messages as Warnings"
Business Activity: MAT1 Create Material
MAT02:
Same as for MAT01
Business Activity: MAT2 Process Material
MAT06:
Same as for MAT01
UI Config: MDG_MM_APP_BS_DEL_GEN
Business Activity: MAT6 Mark Material for Deletion
MAT0A
Same as for MAT01
UI Config: <leave emtpy>
Msg. Output: "W Issue Error Messages as Warnings"
Business Activity: MATA Process Multiple Materials
MAT0B
Same as for MAT01
UI Config: <leave emtpy>
Msg. Output: "W Issue Error Messages as Warnings"
Business Activity: MATB Import Material
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
This picture illustrates the representation of the standard two-step-with-revision / two-man-rule (Vier-
Augen-Prinzip) process in the rule-based workflow BRFplus.
It explains the steps, status and actions that are represented in the decision tables of BRFplus.
The steps (manual or automated) are represented by the chevrons (except final step 99)
The statuses (visible in lists and inbox) are represented by the flags
The actions (triggered by user or automated) are the description on the arrows
The change request has a status assigned for every step and you move from one step to the next via
actions.
Step 00: the business user initiates a change request by starting to create or change a material. As
long as the data is saved in “draft” mode, it is only visible to the initiator. Technically it is kept in
some cluster tables for temporary storage.
Action Submit: only when the change request is submitted, the workflow is triggered and the data is
transferred into the staging area. If not stated the status is 02: Changes to be executed
Step 90: the master data expert verifies and enhances the data
Acti on 09: the expert triggers the activation of the data. System tasks (not shown in here) ensure that
the data is validated before physical activation, and that inconsistencies, potential duplicates, un-
governed changes in the backend are detected and made visible to the expert via messages and
error log.
Step 91: an automated workflow task activates the data in the active area. If successful the status “05:
Final check approved” is set
Actions in the background complete the workflow
Final step 99: workflow is finished and change request no longer active.
The revision steps are explained on the next page. SAP Class Week of March 12, 2012
3. Maintain your content in the decision tables, reflecting your governance process.
Alternatively you can also import pre-delivered SAP content from client 000 using the XLS
export and import functionality in the BRFPlus Workbench.
Example: The example on these two slides / pages represent a simple 4-eye 2-step
approval process with revision capability.
The following describes the minimal settings for the relevant change request type. Open
Decision Table. There are three decision tables available:
DT_NON_USER_AGT_GRP_MAT01
DT_SINGLE_VAL_MAT01
DT_USER_AGT_GRP_MAT01
DT_NON_USER_AGT_GRP_MAT01 and DT_SINGLE_VAL_MAT01 are pre-filled with
the standard configuration on the automated steps and on the follow-up determination of
BRF+. The follow-up determination can either result in an automated step or in a user task
that will be made visible as a workflow.
In the table DT_USER_AGT_GRP_MAT01, the users involved in master data governance
need to be included so that they can execute the workflow tasks.
Maintain agents, (for example the users or organizations in the section Portal Content and
Portal Role Assignment in this document) for all change request types and their created
workflow steps.
Each "condition alias" as defined in the DT_SINGLE_VAL_MAT01 needs at least one
processor either automatic or user (group). Therefore, for all non-automated steps at least
one entry needs to exist.
SAP Class Week of March 12, 2012
MDG for material uses advanced workflow capabilities by combining the SAP Business
Workflow with the SAP Business Rule Framework plus (BRFplus).
As a prerequisite you have made the necessary general settings for workflows and defined
the organizational plan in Customizing for SAP NetWeaverunder
Application Server Business Management SAP Business Workflow .
Prerequisite: Check that the steps for Rule-Based Workflow are imported by the BC-Set by
running the following activity in Customizing:
General Settings Process Modeling Workflow Rule-based Workflow Define Steps
for Rule-Based Workflow .
Default steps for all change request types are the following:
0 – 90 – 91 – 92 – 93 – 95 – 99 – Details see slide.
Note: Due to technical restrictions further settings currently cannot be included in the BC-Set
processing.
1. Generate the decision tables and rules for each change request type either in
Customizing or by running the system transaction USMD_SSW_RULE.
2. Check existence of SAP example structures. If required, export the content from client
000 and import into your hub client.
3. Maintain your content in the decision tables, reflecting your governance process.
Alternatively you can import pre-delivered SAP content.
SAP Class Week of March 12, 2012
1. Generate the decision tables and rules for each change request type either in
Customizing or by running the system transaction USMD_SSW_RULE.
General Settings Process Modeling Workflow Rule-based Workflow Configure
Rule-Based Workflow
SAP Class Week of March 12, 2012
2. Check existence of SAP example structures. If required, export the content from client 000 and import into
your hub client:
1. Call transaction BRF+(or BRFplus)
2. Using the menu, switch to Expert mode by choosing WorkbenchUser Mode .
3. Select object USMD_SSW_CATA_MAT01: If this is not already in your repository, search for it using the
menu. Choose Workbench Open Object . For detailed selection enter the following values:
Object Type CA: Catalog;
Name: USMD_SSW_CATA_MAT*.
4. From the search result, select USMD_SSW_CATA_MAT01
5. Add selected object to your repository. From the menu choose, Workbench Add Current Objects to Favorites
If the search result does not contain USMD_SSW_CATA_MAT01, export the content from client 000. Run
the BRFplus transaction in the 000 client and search for USMD_SSW_CATA_MAT01 as described
above. To export the content from client 000, do the following:
a) Right-click on the application in the repository, open the context menu and choose Tools XML
Export
b) ChooseInclude Referenced Objects. Generate the xml-file and download it to your PC
To Import the content in your MDG main client run the BRFplus transaction
a) From the menu, choose: Tools XML Import
b) Select your xml-file and click Upload File (you can also assign it to a transport request or run a
check-import first)
6. Repeat this for all relevant Change Request Types including
MAT01 - Create Material
MAT02 - Process Material
MAT06 - Mark Material for Deletion
MAT0A - Process Multiple Materials
MAT0B – Import Materials
SAP Class Week of March 12, 2012
3. Maintain your content in the decision tables, reflecting your governance process.
Alternatively you can also import pre-delivered SAP content from client 000 using the XLS
export and import functionality in the BRFPlus Workbench.
Example: The example on these two slides / pages represent a simple 4-eye 2-step
approval process with revision capability.
The following describes the minimal settings for the relevant change request type. Open
Decision Table. There are three decision tables available:
DT_NON_USER_AGT_GRP_MAT01
DT_SINGLE_VAL_MAT01
DT_USER_AGT_GRP_MAT01
DT_NON_USER_AGT_GRP_MAT01 and DT_SINGLE_VAL_MAT01 are pre-filled with
the standard configuration on the automated steps and on the follow-up determination of
BRF+. The follow-up determination can either result in an automated step or in a user task
that will be made visible as a workflow.
In the table DT_USER_AGT_GRP_MAT01, the users involved in master data governance
need to be included so that they can execute the workflow tasks.
Maintain agents, (for example the users or organizations in the section Portal Content and
Portal Role Assignment in this document) for all change request types and their created
workflow steps.
Each "condition alias" as defined in the DT_SINGLE_VAL_MAT01 needs at least one
processor either automatic or user (group). Therefore, for all non-automated steps at least
one entry needs to exist.
SAP Class Week of March 12, 2012
Each "condition alias" as defined in the DT_SINGLE_VAL_MAT01 needs at least one processor either
automatic or user (group).
Therefore, for all non-automated steps at least one entry needs to exist, see following example (not
mentioned =not maintained keep initial):
DT_USER_AGT_GRP_MAT01/2/6/A:
COND_ALIAS AGENT_GROUP STEP_TYPE USER_TYPE USER_VALUE
3 001 4 [Revise] US <USER ID>
1; 5; 7 001 5 [Activate] US <USER ID>
Include all users and the user-related step-types (SAP default: 4, 5) according to their tasks in your company.
Alternatively you can use as User_Type organizational units “OR” as defined in the organizational
management of your system.
The following step types do exist:
Step Type Short Descript.
1 Check
2 Approve
3 Process
4 Revise
5 Activate
These are now the automated steps to cover background activities. Be aware that in this example the
COND_ALIAS 5 (error) triggers two steps. One User Agent activity – to take care about the error as well as
the automated activity below to complete and finish the Workflow.
DT_NON_USER_AGT_GRP_MAT01/2/6/A:
COND_ALIAS AGENT_GROUP PROCESS_PATTERN
2 001 05 [Activation]
4; 5; 6 001 99 [Complete (Sub-)Workflow]
8 001 08 [Roll back change request]
Repeat this for all relevant change request types. In the standard delivery these are the 4 change request
types: MAT01, MAT02, MAT06, MAT0A, MAT0B.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
A change request describes the business reasons for a required change of master data and controls
the approval and execution of the actual changes.
Change request ensures audit ability of any change: what, when, who, why..
In the general process “Create Change Request” a change request of any type can be created.
The Change Request Type determines among other:
Data of which data model and which entity types can be maintained
The Workflow template to be used
Optionally the UI configuration
The generic pre-delivered workflow processes the change requests in the following way:
At the creation of the change request, the requestor only describes, what shall be changed (or
created). But he does not enter the actual master data.
In the second step a master data expert can enter the actual master data according to the
description of the requestor.
The workflow can also contain additional steps for additional users in order to enter comments or
specific master data.
The submit for final approval may be triggered by a certain processor or by some automatic rule.
If the final approver rejects the change request, a special step for “Rework” can be triggered.
The processor for rework can decide about corrections and resubmit or withdrawl of the change
request.
After final approval, master data are activated and can be replicated to local systems.
SAP Class Week of March 12, 2012
The slide outlines the features of Master Data Governance in general. All features are
described in separate presentations of the RKT Learning Map for EhP5.
Some are shown with examples from the different domains on the following slides but as well
focusing on the business value and the pain points they solve.
SAP Class Week of March 12, 2012
The scope of Master Data Governance for Financials is defined for master data used in
financial accounting, financial consolidation and planning like e.g. the chart of accounts
and the accounts, and organization unit like companies, profit centers and cost centers.
In SAP ERP Enhancement Package 4, the scope of Master Data Governance for
Financials includes the central maintenance of chart of accounts and accounts and the
related objects, both, for consolidation and operational systems (see following slides for
more detail).
In SAP ERP Enhancement Package 5, the scope of Master Data Governance for
Financials includes the central maintenance of cost element and organizational unit
including companies, profit centers and cost centers.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
From Master Data Governance for Financials, the Consolidation Chart of Accounts can be
distributed into:
Consolidation System
BI System (maybe from consolidation system)
Local ERP system (for mapping of GL accounts of local operational CoA)
From Master Data Governance for Financials, Hierarchies can be distributed into:
Consolidation System
BI System (maybe from consolidation system)
In the local ERP systems, the GL accounts of local operational CoAs can be mapped to the
group accounts in the consolidation CoA.
If all or some local ERP systems use the same operational CoA, it can also be maintained in
SAP Master Data Governance and distributed to the local ERP systems.
In this case the GL accounts are mapped to the group accounts of the consolidation CoA in
SAP Master Data Governance.
In this case also the Financial Statement Version for the operational CoA can be maintained
in SAP Master Data Governance and distributed to the local ERP systems.
Financial Customizing for GL accounts can to be transported into the SAP Master Data
Governance system (for input help and check).
SAP Class Week of March 12, 2012
MDG PROCESSES
TZMDG1 – Exercise 3.2a
Exercises / Solutions
Ingo Rothley / SAP AG
Exercise: Run first MDG financials processes in the
Training Systems
At the end of this exercise you are able to:
Use your user in NWBC & portal on the training system
Find further change request related information in the system
Run a first change request in financials
You are acting as a business user of the financial department. You want
to request a new Account because you have a new business opportunity
that requires this data.
All objects of this exercise are named with ##. Please replace this with
your group number:
## = Group Number = 01 – 30
Parameters valid throughout the Exercise(Replace ##with your two-digit
Team Number):
Logon to the SAP System [….]
Username: [….]
Password [….]
In MDG you are able to work with the internet based NetWeaver
Business Client (NWBC) or via the enterprise portal
SAP Class Week of March 12, 2012
2
Bef or e You St ar t : Connec t t o t he Tr ai ni ng Landsc ape
The SAP Training Landscape has been moved to the Cloud. To connect to the SAP MDG (ERP) system via SAP GUI
or via the according NetWeaver Business Client or NetWeaver Portal, you will first need to connect to a computer that
also is located in that Cloud. All programs that you will launch during the exercises below will actually be executed on
that computer – not on the PC in this room. We will use Windows Terminal Server (WTS) to connect to the Cloud.
Accessing the training computer in the Cloud
Please start the remote desktop connection directly from your computer.
Choose “run” from the start menu. Open “mstsc”. Computer […computer ID of this course …]
for first teach in Walldorf starting March 1
st
this is: “RA-ECC605TX-001”
You will enter the WTS environment. Then you will see a popup, asking you for a user and password. Please make
sure to use the same group number (“train-##”) that you are assigned to in the MDG backend. The password to be
typed in is “initial ”. If asked whether you trust the computer that you are about to connect to, please answer “yes”.
Hint: As long as you are logged on at the WTS under a certain user ID, you are blocking this user on the
WTS. Nobody else can use these credentials until you properly log off from the WTS. Please make sure
that you always use Start Log Off [computer ID]\train-## to end your session on the WTS. Please
never just close that WTS window – which would leave the session running on the WTS.
Ex erc i se 1: Act i vat e your User i n t he Tr ai ni ng Syst em
In this exercise, you will activate your own user and verify the necessary roles and authorizations of your user in order
to run MDG in that sandbox system.
Find the RKT Trai ning system
Please open SAP Logon and create a new Connection for the system “ZME” if not already there.
Hint: We will start this exercise by accessing the landscape via SAP GUI for Windows. You will also be able
to access ZME via the SAP NetWeaver Portal or via the NetWeaver Business Client.
Acti vate your personal user and verify the necessary authori zations
Please logon to MDG backend system ZME with your user ID TZMDG1-## with ##representing your group number.
We recommend to change the password to the course ID “TZMDG1” or the course+group ID “TZMDG##”
Verify that your user is capable of running business transactions of all domains of MDG:
SAP Master Data Governance for Financial Data: Role: ___________________________
SAP Master Data Governance for Material Data: Role: ___________________________
SAP Master Data Governance for Supplier Data: Role: ___________________________
Access the corresponding enterprise portal and verify the necessary roles
Please logon to Portal with your user ID TZMDG1-## with ##representing your group number.
http://portal-zme.wdf.sap.corp:50000/irj/portal
Password is identical with the just changed backend password.
The corresponding portal roles for your portal user are already assigned. (The according portal roles are:
“Financial Master Data Manager”, “Material Master Data Manager”, “Supplier Master Data Manager”, and
“ERP Common”.)
Add the portal to your browser favorites in order not to re-type it.
SAP Class Week of March 12, 2012
3
Ex erc i se 2: Fi nd i nf or mat i on on Edi t i ons
Now you can start working like an end-user in your MDG working environment. Since the training system is a copy like
the RKT sandbox, the data is quite similar. In the last exercise you already learned how to find some basic information
related to MDG Change Requests. Let us explore the training system further and have a look at the editions that are
used for time-dependent data – currently used only in the financials area.
Start the MDG work center for Financials
Either use the SAP NetWeaver Business Client (transaction code NWBC in the system), or use the access via the SAP
NetWeaver Portal to navigate to the Financials Work Center of MDG.
Verify information on Editions
How many editions can you see overall. How many released editions do exist?.
If the counter of the tab is zero, you might need to rerun the query to initialize it for your user ID.
What type of objects and how many are assigned to one Edition
What type of objects are related to the Edition “RKT DEMO 1” ? ___________________________
___________________________
___________________________
How many Group Accounts are assigned to this Edition? ______________
Which change requests were related to one Edition and what is their status
Which change requests had been related to the edition “RKT DEMO 1”? ______________
What is the processing status of change request with ID 22 ? ___________________________
How many user interactions took place in the workflow to reach this status: ______________
Which Work Item ID activated the data of this change request in the background? ______________
Ex erc i se 3: Creat e a new Cost Cent er f or a Sal es Of f i c e
You company wants to open up a new sales office in the beautiful city of Montréal mid of this/next month. You know
that you need to have at least one cost center for this ready in time so that all expenses can be booked correctly.
Make sure that the right Data Model 0G is assigned to your user master incl. a valid UI configuration
Create the new cost center using MDG Change Requests.
SAP Class Week of March 12, 2012
4
Create a change request for the new cost center and maintain mandatory information
Use the single processing (not using Forms) in this exercise (CR type 0G_W003).
Pick the right Edition
Controlling Area should be “CO N. America”
Cost Center ID 300##
On the detailed screen enter the following data:
Department Montreal
Cost Center Category Sales (3)
Company Code IDES (4000)
Business Area BA##
Functional Area Sales (1000)
Person Responsible TZMDG1
You want to make sure that the description is maintained in English and French.
Optionally you would can some attachments & links.
Optional ly: send CR back for revisi on and wait for processing
If your neighbor team agrees, send CR back for revision, requesting some change or addition
Optionally: resend CR after adjustment and wait for approval
Add / change some data and resend the CR. Have a look at the workflow to see what’s happening in the background.
Process the change request f or the new cost center of your neighbor (group ID + 1)
Find the correct change request via the work list. Assign and process the request.
Approve the change request for the new cost center of your neighbor (group ID + 2)
Find the correct change request via the work list. Approve the request.
Verify that your change request is visible in the edition
Make sure your cost center’s CR is assigned and visible in the edition
DO NOT CHANGE the Edition – Instructor will rel ease it once all CRs are ready and approved
Veri fy that your cost center i s acti ve in the backend.
Make sure your cost center is visible in the backend system.
Room for your notes & questions:
SAP Class Week of March 12, 2012
5
Sol ut i on t o Ex er c i se 1
SOLUTION: Find the RKT Training system
Please open SAP Logon and create a new Connection for the system “ZME” if not already there.
SOLUTION: Acti vate your personal user and veri fy the necessary authorizations
Please logon to MDG backend system ZME with your user ID TZMDG1-## with ##representing your group number.
You will be prompted to change your password.
Now launch transaction SU01 for User Maintenance.
In transaction SU01, please enter your User ID and press “Display” (that little glasses symbol above / F7). Navigate to
the “Roles” tab. You will see (at least) the following roles assigned to your user:
SAP Class Week of March 12, 2012
6
SOLUTION: Access the corresponding enterprise portal and verify the necessary roles
Please logon to Portal with your user ID TZMDG1-## with ##representing your group number.
http://portal-zme.wdf.sap.corp:50000/irj/portal
The corresponding portal roles for are: “Financial Master Data Manager”, “Material Master Data Manager”, “Supplier
Master Data Manager”, and “ERP Common”.)
SAP Class Week of March 12, 2012
7
Sol ut i on t o Ex er c i se 2
SOLUTION: Start the MDG work center for Financials
Either use the SAP NetWeaver Business Client (transaction code NWBC in the system), or use the access via the SAP
NetWeaver Portal to navigate to the Financials Work Center of MDG.
SOLUTION: Verify information on Editions
How many editions can you see overall. How many released editions do exist?
You see (at least) the following list with the number on the tab indicating the number of entries =i.e. editions.
Number of released Editions is 0 according to the tab, but you can tell by the status in the list that this is not correct.
So please refresh the view. Now the result will be correct:
You can also adjust, copy, delete queries by using “Change Query” function.
SOLUTION: What t ype of objects and how many are assigned to one Edition
Select the Edition RKT DEMO 1 by clicking on the hyperlink from the list.
SAP Class Week of March 12, 2012
8
The “Where-Used List” will bring up the object list.
You find the three entity types that are related to the Edition
What type of objects are related to the Edition “RKT DEMO 1” ? __Group Chart of Accounts____
__Chart of Acconts___________
____Group Account___________
If you switch now to “Group Accounts” you can either count …. or use the navigation bar on the right which tells you the
number of entries once you click on the bar and start scrolling:
How many Group Accounts are assigned to this Edition? _____30_______
Close the window to complete this part of the exercise.
SOLUTION: Which change requests were related to one Edition and what is their status
SAP Class Week of March 12, 2012
9
There are (at least) two ways to find this out. Quickest way from current “Display Edition” window is described here. But
you can also go via the “Display Change Request” service and enter the edition. Don’t forget to uncheck the “No
finalized change request” flag in this case.
From “Display Edition” choose the “Edition History”. Now a graphic view (J ava based, this is one of the very few
exceptions where MDG uses J ava) is opened. Among others you can navigate here to the list of assigned change
requests as well:
Mark the bar in the timeline section. Press “Change Requests of an Edition”.
Which change requests had been related to the edition “RKT DEMO 1”? ___12 & 22________
What is the processing status of change request with ID 22 ? __Final Check Approved__________
For the information on the workflow mark the relevant line and press “Workflow Log”
By default you see the steps that required user interaction. You can see the processor and the decision he/she made.
If you scroll to the right, you see further audit information. Via “Settings” you can customize the via, adjust it to your
needs and save the layout for future usage (you can mark it as default view).
How many user interactions took place in the workflow to reach this status: ______4_______
SAP Class Week of March 12, 2012
10
Now you should have a look at the “Background Steps”. They also include the system workflow steps.
For more details on the Work Items themselves you could use the hyperlink. From there you can do trouble-shooting if
workflow is not working correctly, get to the system messages or find out which were the possible agents of a workflow
step.
Which Work Item ID activated the data of this change request in the background? ___949660________
SAP Class Week of March 12, 2012
11
Sol ut i on t o Ex er c i se 3
SOLUTION: Create a change request for the new cost center and maintain mandatory information.
Optionally you can assign a Due Date, Priority and Reason. These elements can be used later for analytical purposes.
Some Explanation is mandatory, optionally you can add some attachments or link to relevant information.
Because we are in “Single Processing” you directly can start with the maintenance of the master data. You do not need
to specify the objects – this has already been done in the entry screen.
Enter the mandatory fields accordingly.
SAP Class Week of March 12, 2012
12
You want to make sure that also user logged on in other languages get a good description, so you add this:
You check your work and submit it to the next processor.
SAP Class Week of March 12, 2012
13
You receive the confirmation of the change request ID and now you can navigate to your CRs to track the progress:
Don’t forget to close the window – otherwise your desktop will be & look crowded soon ….
Optionally: send CR back for revision and wait for changes
If your neighbor team agrees, send CR back for revision, requesting some change or addition
Optional ly: resend CR after adjustment and wait for processi ng
Add / change some data and resend the CR. Have a look at the workflow to see what’s happening in the background.
SOLUTION Process the change request for the new cost center of your neighbor (group ID + 1)
Find the correct change request via the work list. Assign and process the request.
SAP Class Week of March 12, 2012
14
In the list of change request now all new CRs are displayed since all users / groups are assigned to all tasks.
In order to comfortably find the CR of the next team, simply use the “Filter” functionality of the Portal/NWBC. Select for
“*nn” with nn =##+1.
Mark the entry line. You can now directly access the CR via the hyperlink or ensure that you are the only processor
using the “Assign To Me” functionality. Now you can start processing and add some missing information. The
assignment helps that no parallel work is going on an that you have clear responsibility for the current CR step.
Review the data, change it (whether an approver is allowed to change or not is controlled via the customizing of the
step), add comments in the change request and have a look at the change documents (which of course makes more
sense in the case of changing an existing entity).
Finalize the processing using the corresponding button and hand over to final approval.
Approve the change request for the new cost center of your neighbor (group ID + 2)
Find the correct change request via the work list. Approve the request.
SAP Class Week of March 12, 2012
15
In this step you realize that changes to the object are no longer allowed. Only notes or attachments can be added.
SOLUTION Verify that your change request is visible in the edition
Make sure your cost center’s CR is assigned and visible in the edition. See Exercise 2.
DO NOT CHANGE the Edition – Instructor will rel ease it once all CRs are ready and approved
SOLUTION Verify that your cost center is a) acti ve / b) acti ve in the backend.
Make sure your cost center is active. Use the “Search Entity” option in the “Change Request” work center.
SAP Class Week of March 12, 2012
16
Pick the entity type “Cost Center” and use the Edition as Filter criteria.
The newly released cost centers shall be active:
SAP Class Week of March 12, 2012
17
To check if it is active in the backend system, use the following path.
SAP Class Week of March 12, 2012
18
Until the distribution of FIN data is maintained completely this will not work because of “ Flexibility
Option” of financial master data in MDG
SAP Class Week of March 12, 2012
©2011 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, 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 other
countries.
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 registered
trademarks of Business Objects Software Ltd. in the United States and in other countries.
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.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors
or omissions with respect to the materials. The only warranties for SAP Group 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.
SAP Class Week of March 12, 2012
MDG FI NANCI ALS
TZMDG1 – Exercise 2.3b
Exercises / Solutions
William Cao / SAP
Exercise(s):
At the end of this exercise you are able to:
Overview the attributes and the content of an edition
Create different type of change requests with edition based on
business requirement
Approve change request
Distribute master data to target system
You as the operation manager of the service department are now
supposed to request a new cost center because of the expansion of the
business.
All objects of this exercise are named with ##. Please replace this with
your group number:
## = Group Number = 01 – 30
Parameters valid throughout the Exercise(Replace ##with your two-digit
Team Number):
Logon to the SAP System [….]
Username: TZMDG1-##
Password: initial
In MDG you are able to work with the internet based Netweaver
Business Client (NWBC) or via the enterprise portal
SAP Class Week of March 12, 2012
2
Ex erc i se 1
Exerci se Objectives
After this exercise, you can create a PDF form change request which asks for a new cost center.
Business Example
As an operation manager of the sales division, you need to request a new cost center that corresponds to the new
service region “East State” that will be established from the beginning of next quarter.
Task 1:
Check and find the right edition that fit for new cost center.
1. Please take a look at the work center “Editions”. Try to find out the edition that is valid from the beginning of
next quarter.
What is the name of that edition?
_________________________
Hi nt: if there are several editions starts from the same time, compare the column “Status”. The
editions with “In Process” status are able to create change request in them.
2. Select the line of the edition you identified above, what is the value of the column ‘Number’?
_________________________
Hi nt: At the right bottom of the edition list, there is a “Refresh button” which will update the edition
list.
Task 2:
Create a change request for a new cost center.
1. In the work center of “Change Request”, click on “Create Change Request”
2. Enter the description of the change request, select change request type “Process Cost Center - Form”, input
the edition you identified in task 1. Click next step.
3. Enter the reason for this change request, why the new cost center is needed. Click next step.
4. In the PDF form, input the following values:
Controlling Area 0001
Cost Center CC_ES_##
Description (short) Cctr ES ##
Description (medium) Cost Center East State ##
Company Code 0001
Department Service Dept
Cost Center Category Service
Currency USD
User Responsible Your user ID
Person Responsible Your full name
SAP Class Week of March 12, 2012
3
Leave the other fields as default, and click next step.
5. Review what has inputted, click Submit.
6. Record the change request number:
_________________________
7. Go to the work center Change Request, start My Change Request, click on the just created change request to
review it. Input the following value.
Business Area External Services
8. Complete the processing.
What is the “Status” column of this change request in My Change Request now?
_________________________
Task 3:
Ask your neighbor (team) to approve your change request.
1. Review what has inputted, click Approve.
SAP Class Week of March 12, 2012
4
Ex erc i se 2
Exercise Objectives
After this exercise, you can see your newly created cost center is distributed to the target system.
Business Example
After all the change requests that created from all the departments are approved, the master data steward will
release the data of that edition to target systems to make them available for business use.
Task 1:
Check in the target system, make sure the requested cost center is not there yet.
1. Start transaction KS03
Note: if being asked for controlling area, input 0001.
2. Input the cost center ID CC_ES_##.
3. A message should inform you that CC_ES_##doesn’t exist in controlling area 0001.
Task 2(done by trainer):
When all the trainees have done task 1, the trainer will do the following:
1. Release the edition
2. Distribute the data(including cost center you have created)
3. Show the replication log in distribution monitor.
Task 3:
Verify that your requested cost center is in the target system now.
1. Start transaction KS03
2. Input the cost center ID CC_ES_##.
3. The cost center should be displayed. Check if the attributes you have inputted in exercise 1 are successfully
distributed.
SAP Class Week of March 12, 2012
5
Sol ut i on Ex er c i se 1
Task 1:
Check and find the right edition that fit for new cost center.
3. Please take a look at the work center “Editions”. Try to find out the edition that is valid from the beginning of
next quarter.
What is the name of that edition?
_________________________
Hi nt: if there are several editions starts from the same time, compare the column “Status”. The
editions with “In Process” status are able to create change request in them.
4. Select the line of the edition you identified above, what is the value of the column ‘Number’?
_________________________
Hi nt: At the right bottom of the edition list, there is a “Refresh button” which will update the edition
list.
Task 2:
Create a change request for a new cost center.
9. In the work center of “Change Request”, click on “Create Change Request”
10. Enter the description of the change request, select change request type “Process Cost Center - Form”, input
the edition you identified in task 1. Click next step.
11. Enter the reason for this change request, why the new cost center is needed. Click next step.
12. In the PDF form, input the following values:
Controlling Area 0001
Cost Center CC_ES_##
Description (short) Cctr ES ##
Description (medium) Cost Center East State ##
Company Code 0001
Department Service Dept
Cost Center Category Service
Currency USD
User Responsible Your user ID
Person Responsible Your full name
Leave the other fields as default, and click next step.
13. Review what has inputted, click Submit.
14. Record the change request number:
_________________________
15. Go to the work center Change Request, start My Change Request, click on the just created change request to
review it. Input the following value.
SAP Class Week of March 12, 2012
6
Business Area External Services
16. Complete the processing.
What is the “Status” column of this change request in My Change Request now?
_________________________
Task 3:
Ask your neighbor (team) to approve your change request.
2. Review what has inputted, click Approve.
SAP Class Week of March 12, 2012
7
Ex erc i se 2
Exercise Objectives
After this exercise, you can see your newly created cost center is distributed to the target system.
Business Example
After all the change requests that created from all the departments are approved, the master data steward will
release the data of that edition to target systems to make them available for business use.
Task 1:
Check in the target system, make sure the requested cost center is not there yet.
4. Start transaction KS03
Note: if being asked for controlling area, input 0001.
5. Input the cost center ID CC_ES_##.
6. A message should inform you that CC_ES_##doesn’t exist in controlling area 0001.
Task 2(done by trainer):
When all the trainees have done task 1, the trainer will do the following:
4. Release the edition
5. Distribute the data(including cost center you have created)
6. Show the replication log in distribution monitor.
Task 3:
Verify that your requested cost center is in the target system now.
4. Start transaction KS03
5. Input the cost center ID CC_ES_##.
6. The cost center should be displayed. Check if the attributes you have inputted in exercise 1 are successfully
distributed.
SAP Class Week of March 12, 2012
©2010 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, 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 other
countries.
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 registered
trademarks of Business Objects Software Ltd. in the United States and in other countries.
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.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors
or omissions with respect to the materials. The only warranties for SAP Group 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.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Defi ne Search Applicati ons
Use
In this activity, you can create additional search applications for the Search for Entities (Web Dynpro
application USMD_ENTITY_SEARCH) in addition to the database search provided.
For each search application, you can assign an access class that the system should use for the search.
The system derives the access class from the data model.
Using the Business Add-In BAdI: Search of Entities (USMD_SEARCH) you can influence the search
attributes and the toolbar for the search result.
Requirements
If you do not want to use any of the access classes provided for a search application, you have created
your own access class in the ABAP Workbench.
Standard settings
SAP provides search applications, including one for an address search and one for Enterprise Search.
Acti viti es
1. To define a search application, you choose New Entries and create a new entry in the customer
namespace.
2. Select the access class and specify whether freeform search and (or) fuzzy search are allowed in
the search application.
Example
You can, for example, configure your own search applications for your own customer-specific search
provider.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
BAdI: Define Validations/Derivations
Use
This Business Add-In (BAdI) is used in the Master Data Governance (CA-MDG) component.
You can use this BAdI to create customer-specific checks on entities, change requests, and editions. You also can use this BAdI to define that certain field values are to be derived fromthe values of other
fields in the master data:
When an entity is checked, the method CHECK_ENTITY is called once for each entity type of the changed master data. In this method you define all rules for checking the entities in the data model.
When checking a change request, the following methods are called consecutively:
CHECK_CREQUEST_START
CHECK_CREQUEST (once for each entity type of the changed master data in the change request)
CHECK_CREUQEST_FINAL
When checking an edition, the following methods are called consecutively:
CHECK_EDITION_START
CHECK_EDITION (once for each entity type of the changed master data in the edition)
CHECK_EDITION_FINAL
Standard settings
In the standard system, the BAdI implementation USMDZ3_RULE_BADI is activated for the delivered data model 0F. The implementation is automatically executed for this data model.This BAdI is filter
dependent. The data model (MODEL) and the entity type (ENTITYTYPE) serve as filters.This BAdI is not for multiple use.
BAdI Implementations
USMDZ3_RULE_BADI
The BAdI implementation is located in the enhancement implementation USMDZ3_IMP_RULE_SERVICE_BADI.
Activities
Information about the implementation of BAdIs in the context of the enhancement concept is available in the SAP Library for SAP NetWeaverunder BAdIs - Embedding in the Enhancement Framework.
BAdI implementation MDG_BS_BP_DESCRIPTION
You use the BAdI method IF_EX_USMD_RULE_SERVICE~DERIVE_ENTITY fromthe BAdI implementation MDG_BS_BP_DESCRIPTION to derive the business partner description froma business
partner’s name and address.
If you want to create a customer-specific BAdI implementation for the same filter value (ENTITYTYPE =BP_HEADER), deactivate the BAdI implementation MDG_BS_BP_DESCRIPTION before activating
the customer-specific BAdI implementation.
If you want to mostly retain the function of the BAdI implementation MDG_BS_BP_DESCRIPTION as delivered by SAP, and want to ensure that you receive corrections fromSAP Notes, youcan derive a
customer-specific implementing class fromimplementing class CL_MDG_BS_BP_DESCRIPTION and redefine methods as required.
BAdI implementation MDG_BS_BP_TAXJ URCODE
You can use the BAdI method IF_EX_USMD_RULE_SERVICE~DERIVE_ENTITY fromthe BAdI implementation MDG_BS_BP_TAXJ URCODE to derive the tax jurisdiction code fromthe address.
If you want to create a customer-specific BAdI implementation for the same filter value (ENTITYTYPE =AD_POSTAL), deactivate the BAdI implementation MDG_BS_BP_TAXJ URCODE before activating
the customer-specific BAdI implementation.
If you want to mostly retain the function of the BAdI implementation MDG_BS_BP_TAXJ URCODE as delivered by SAP, and want to ensure that you receive corrections fromSAP Notes, you can derive a
customer-specific implementing class fromimplementing class CL_MDG_BS_BP_TAXJ URCODE and redefine methods as required.
BAdI implementation MDG_BS_SUPPL_ACCGRP_ID
You can use the BAdI method IF_EX_USMD_RULE_SERVICE~DERIVE_ENTITY fromthe BAdI implementation MDG_BS_SUPPL_ACCGRP_ID to derive the account group and the vendor number from
the business partner.
If you want to create a customer-specific BAdI implementation for the same filter value (ENTITYTYPE =BP_HEADER), deactivate the BAdI implementation MDG_BS_SUPPL_ACCGRP_ID before activating
the customer-specific BAdI implementation.
If you want to mostly retain the function of the BAdI implementation MDG_BS_SUPPL_ACCGRP_ID as delivered by SAP, and want to ensure that you receive corrections fromSAP Notes, you can derive a
customer-specific implementing class fromimplementing class CL_MDG_BS_SUPPL_ACCGRP_ID and redefine methods as required.
See also
This BAdI uses interface IF_EX_USMD_RULE_SERVICE. For more information, display the interface in the Class Builder.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Configure Duplicate Check for Entity Types
Use
In this Customizing activity, you configure the duplicate check for an entity type. On the basis
of a data model (for example BP or MM) you define which search mode the system must use
and which thresholds (percentages) are to apply:
Records that have a matching score lower than the low threshold are not considered as
duplicates.
Records that have a matching score that lies between the defined low and high threshold are
considered as potential duplicates.
Records that have a matching score higher than the high threshold are not allowed by the
system as they are considered to be identical.
For business partners (for example supplier), the following search providers can be used:
Data base search: Choose setting DB.
Enterprise search: Choose setting ES.
Business Address Services (BAS): Choose the setting AD. This setting ensures that the
system searches for potential duplicates on the basis of the BAS-DES interface.
For Material only Enterprise Search (ES) can be used as search provider for duplicate check.
Requirements
In the Customizing activity Define Search Applications, you have defined search applications
and have assigned access classes.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
1
DEEP DI VE – DATA QUALI TY
TZMDG1 – Exercise 3.1
Exercises / Solutions
[Author Name] / SAP AG
Exercise: Create BRF+ Rules for Check and Derivation
At the end of this exercise you are able to:
To create BRF+Rules
Assign the rules to functions
Check, if rules are processed
You are acting as a business user of the material department. You are
now supposed to do the following because you like to check your
material and to derive some defaults.
All objects of this exercise are named with ##. Please replace this with
your group number:
## = Group Number = 01 – 30
Parameters valid throughout the Exercise(Replace ##with your two-digit
Team Number):
Logon to the SAP System [….]
Username: TZMDG1-##
Password: initial
In MDG you are able to work with the internet based Netweaver
Business Client (NWBC) or via the enterprise portal
SAP Class Week of March 12, 2012
2
Ex erc i se 1 Bui l d Val i dat i ons / Der i vat i ons
Ruleset is already assigned to the Check and Derive Material.
Your group will create a new rule which should be linked to the Ruleset.
Build Check
1. Start transaction ‘SPRO’ or ‘MDGIMG’
2. Go to the navigation path Cross-Application Components -> Processes and Tools for Enterprise Applications -
> Master Data Governance -> General Settings -> Data Quality and Search -> Define Validation and Derivation
Rules
3. Enter the Data Model as ‘MM’ and click on ‘Start’ and navigate to the FMDM_MODEL_MM node
4. Create a Rule by right clicking on the node and navigating to the path Create Object Node -> Create Rule
5. Enter the name of the rule following the naming convention ‘TZMDG1_XX_01_Rule_Check_Mat’ where XX
represents the team name. Chose name, short text and text. Click on “Create”. On the next window click on
‘OK’
6. Create a rule: ‘If the User is TZMDG1-XX (where XX represents the group name) and Labor is initial then raise
a message, that the field is mandatory’.
Step 1: Click on node ‘No condition assigned. Assign Condition …’ in the Detail section on the right.
Select from Use value range from/Default object /Current User and set it equal to your group-user.
Step 2: Click on ‘Change Condition/Add more condition’ and change the operators by clicking <1>or
<2>and change it to <1>and <2>
Step 3: Click on the sign next to ‘…‘and select from Use value range from/Select Context Parameter.
Choose LABOR and set ‘is initial’. (from the pop-up dropdown)
Step 4: Then: Click on ‘Add’ and ‘Perform action/Create’. Choose Type ‘Log Message (Act)’. Chose
name (Starting with TZMDG1_XX), short text and text. Click on ‘Create and navigate to the object’.
NOTE: You may be asked to save the Rule. Please save it and hit okay.
Step 5: Enter a text for the message, like: Please maintain labor. The Type should be a Warning.
Step 6: Save and activate the log message.
Step 7: Go Back to the rule. Save and activate the rule.
7. Now you have to assign your rule to the ruleset which is used in the Function ‘CHECK_MATERIAL’ . For this
navigate in the catalog to ‘Trigger Function/CHECK_ENTITY/CHECK_MATERIAL’. Navigate to the ‘Assigned
Rulesets’ tab and click on the assigned ruleset: ‘RS_Check_Material_TZMDG1‘. Click on ‘Insert Rule/Select’
and choose your rule. Save and activate the ruleset.
Build Deri vations
1. Start transaction ‘SPRO’ or ‘MDGIMG’
2. Goto the navigation path Cross-Application Components -> Processes and Tools for Enterprise Applications ->
Master Data Governance -> General Settings -> Data Quality and Search -> Define Validation and Derivation
Rules
3. Enter the Data Model as ‘MM’ and click on ‘Start’ and navigate to the FMDM_MODEL_MM node
4. Create a Rule by right clicking on the node and navigating to the path Create Object Node -> Create Rule
5. Enter the name of the rule following the naming convention ‘TZMDG1_XX_02_Rule_Derive_Mat’ where XX
represents the team name. Chose name, short text and text. Click on “Create”. On the next window click on
‘OK’
6. Create a rule: ‘If the User is TZMDG1-XX (where XX represents the group name) and Industry type is initial
then set it to ‘M’.
Step 1: Click on node No condition assigned. Assign Condition …in the Detail section on the right.
Select from Use value range from/Default object /Current User and set it equal to your group-user.
Step 2: Click on ‘Change Condition/Add more condition’ and change the operators by clicking <1>or
<2>and change it to <1>and <2>
Step 3: Click on the sign next to ‘…‘ and select from Use value range from/Select Context Parameter.
Choose MBRSH and set ‘is initial’.
SAP Class Week of March 12, 2012
3
Step 4: Then: Click on ‘Add’ and ‘Assign Value to Context/Select Context Parameter’. Choose MBRSH
and set it to ‘M’
Step 5: Save and activate the rule.
7. Now you have to assign your rule to the ruleset which is used in the Function ‘DERIVE_MATERAL’. For this
navigate in the catalog to ‘Trigger Function/Derivation/Derive_Material’. Navigate to the ‘Assigned Rulesets’
tab and click on the assigned ruleset: ‘RS_Derive_Material_TZMDG1 ‘. Click on ‘Insert Rule/Select’ and
choose your rule. Save and activate the ruleset.
Ex erc i se 2 Cr eat e Mat er i al and c hec k rul es
Create Materi al
1. Execute transaction ‘NWBC’ and click on ‘SAP_MDGM’
Click on ‘Create Material’
Optional: You may be required this option below:
a. Assign the Data Model ‘MM’ and UI configuration to the user master record by clicking on ‘Change
Model’
b. Create a change request using the change request type ‘MAT01’
2. Enter basic data for the material. Check and Submit the change request.
3. Check, if your derivation rules are executed.
4. Click on ‘Check’.
5. Check, if your check rules are executed.
[
SAP Class Week of March 12, 2012
4
Sol ut i on Ex er c i se 1
Build Check
1. Start transaction ‘SPRO’ or ‘MDGIMG’
2. Go to the navigation path Cross-Application Components -> Processes and Tools for Enterprise Applications -
> Master Data Governance -> General Settings -> Data Quality and Search -> Define Validation and Derivation
Rules
3. Enter the Data Model as ‘MM’ and click on ‘Start’ and navigate to the FMDM_MODEL_MM node
4. Create a Rule by right clicking on the node and navigating to the path Create Object Node -> Create Rule
SAP Class Week of March 12, 2012
5
5. Enter the name of the rule following the naming convention ‘TZMDG1_XX_01_Rule_Check_Mat’ where XX
represents the team name. Chose name, short text and text. Click on “Create and Navigate to Object”. On the
next window click on ‘OK’
6. Create a rule: ‘If the User is TZMDG1-XX (where XX represents the group name) and Labor is initial then raise
a message, that the field is mandatory’.
Step 1: Click on node ‘No condition assigned. Assign Condition …’ in the Detail section on the right.
Select from Use value range from/Default object /Current User and set it equal to your group-user.
Step 2: Click on ‘Change Condition/Add more condition’ and change the operators by clicking <1>or
<2>and change it to <1>and <2>
SAP Class Week of March 12, 2012
6
Step 3: Click on the sign next to ‘…‘and select from Use value range from/Select Context Parameter.
Choose LABOR and set ‘is initial’. (from the pop-up dropdown)
SAP Class Week of March 12, 2012
7
Step 4: Then: Click on ‘Add’ and ‘Perform action/Create’. Choose Type ‘Log Message (Act)’. Chose
name (Starting with TZMDG1_XX), short text and text. Click on ‘Create and navigate to the object’.
NOTE: You may be asked to save the Rule. Please save it and hit okay.
Step 5: Enter a text for the message, like: Please maintain labor. The Type should be a Warning.
SAP Class Week of March 12, 2012
8
Step 6: Save and activate the log message.
Step 7: Go Back to the rule. Save and activate the rule.
7. Now you have to assign your rule to the ruleset which is used in the Function ‘CHECK_MATERIAL’ . For this
navigate in the catalog to ‘Trigger Function/CHECK_ENTITY/CHECK_MATERIAL’. Navigate to the ‘Assigned
Rulesets’ tab and click on the assigned ruleset: ‘RS_Check_Material_TZMDG1‘. Click on ‘Insert Rule/Select’
and choose your rule. Save and activate the ruleset.
SAP Class Week of March 12, 2012
9
SAP Class Week of March 12, 2012
10
Sol ut i on Ex er c i se 2
[resuse the exercise text and include text and screenshots of the sol ution]
1. Start transaction ‘SPRO’ or ‘MDGIMG’
2. Goto the navigation path Cross-Application Components -> Processes and Tools for Enterprise Applications ->
Master Data Governance -> General Settings -> Data Quality and Search -> Define Validation and Derivation
Rules
3. Enter the Data Model as ‘MM’ and click on ‘Start’ and navigate to the FMDM_MODEL_MM node
4. Create a Rule by right clicking on the node and navigating to the path Create Object Node -> Create Rule
5. Enter the name of the rule following the naming convention ‘TZMDG1_XX_02_Rule_Derive_Mat’ where XX
represents the team name. Chose name, short text and text. Click on “Create”. On the next window click on
‘OK’
6. Create a rule: ‘If the User is TZMDG1-XX (where XX represents the group name) and Industry type is initial
then set it to ‘M’.
Step 1: Click on node No condition assigned. Assign Condition …in the Detail section on the right.
Select from Use value range from/Default object /Current User and set it equal to your group-user.
SAP Class Week of March 12, 2012
11
Step 2: Click on ‘Change Condition/Add more condition’ and change the operators by clicking <1>or
<2>and change it to <1>and <2>
SAP Class Week of March 12, 2012
12
Step 3: Click on the sign next to ‘…‘ and select from Use value range from/Select Context Parameter.
Choose MBRSH and set ‘is initial’.
Step 4: Then: Click on ‘Add’ and ‘Assign Value to Context/Select Context Parameter’. Choose MBRSH
and set it to ‘M’
SAP Class Week of March 12, 2012
13
Step 5: Save and activate the rule.
7. Now you have to assign your rule to the ruleset which is used in the Function ‘DERIVE_MATERAL’. For this
navigate in the catalog to ‘Trigger Function/Derivation/Derive_Material’. Navigate to the ‘Assigned Rulesets’
SAP Class Week of March 12, 2012
14
tab and click on the assigned ruleset: ‘RS_Derive_Material_TZMDG1 ‘. Click on ‘Insert Rule/Select’ and
choose your rule. Save and activate the ruleset.
SAP Class Week of March 12, 2012
15
SAP Class Week of March 12, 2012
EXTRACTI ON, LOAD
AND DATA REPLI CATI ON
TZMDG1 – Master Data Governance
Exercises / Solutions
SAP AG
SAP Class Week of March 12, 2012
2
Introduction
The exercises below will guide you through configuration and monitoring steps for Initial Load and Data Replication.
Parameters valid throughout the exercises (replace XX with your two-digit Team Number):
Logon to the SAP System ZME:
o Client 800 (MDG Hub)
o Client 900 (Client System)
Ex erc i se 1 – Ex t rac t i on and Load
This exercise leads you through one example of extracting data from a client system to the MDG Hub system. Be
aware that this is usually done for “many” objects at once (either for initial load or for a delta load). Usually this would
also happen “scheduled” (using e.g. the scheduled reports RSEOUT for extraction and RMDG_FILE_UPLOAD_BG for
load).
Parameters valid throughout the Exercise (Replace XX with your two-digit Team Number):
Material: MAT_XX
Supplier: SUPPLIER_XX
Create a Material in the Client Syst em
Log on to ZME, Client 900.
Start transaction MM01. Create a material: MAT_XX (Basic Data 1 and Basic Data 2).
Extract the Materi al
Start transaction BD10. Send material MAT_XX to logical system MDGMAT (this will create an XML-File). Be aware
that for Business Partners (as well as for Key- and Value-Mapping) there is also the SOA-based extraction report
“RMDG_EXTRACTOR_BG”.
Check the Extraction
Start transaction BD87. Search for the XML File created by you. Search for your material number and the name of the
XML-File. You can either do this via BD87 (you need to click through the IDocs) or you can use transaction WE09
(search in Segment E1MARAM, Field MATNR for your material number)
Import the Material (into MDG Hub – Client 800)
Log on via Portal or the NetWeaver Business Client.
Go to “Material Governance” “Data Replication” “File Import”.
Choose File System “Application Server”, Select your file and add the file to “Selected Files”.
Click Next. Select Persistence Choice “2 – Active Area” and “Start Upload”. You could also choose “1 – Staging Area”
and the Material Change Request Type (this would result in a change request which has to be approved).
Check the log.
Veri fy that the material has been l oaded
Go to “Material Governance” “Display Material” (assign data model MM and the UI configuration if needed) or check
using transaction MM02 in client 800.
SAP Class Week of March 12, 2012
3
Ex erc i se 2 – Dat a Repl i c at i on
This exercise leads you through the main configuration and monitoring steps of the Data Replication Framework.
Create a Supplier
Request and approve a supplier (Supplier_XX). Note down the Business Partner Number.
Configure your replication model (MDG Hub – Client 800)
Start Transaction DRFIMG. Navigate to “Define Replication model”.
Create the following entry: ZRM_XX
Text: Team XX Replication model
Log Days: 15
Navigate to “Assign Outbound implementation” and assign the outbound implementation 986_3 (Replication via
Services). Save your entry.
Assign the target system ZME_900 to the outbound implementation.
Assign Outbound Parameter: Press “Get default settings” and assign “Outbound Parameter Value =100” for
“Outbound Parameter PACK_SIZE_BULK”.
Save your replication model.
Go to transaction SE38 and activate your replication model by using Report “ZR_ACTIVATE_REPLICATION_MODEL”.
This workaround is needed to create more than one replication model with the same business object type and target
system.
Check if the replication model has been activated (transaction DRFIMG).
Mai ntain Filter for your repli cation model
Start Transaction DRFF (or go to “Supplier Governance” “Data Replication” “Define Filter Criteria”).
Select your Replication model ZRM_XX. Create a filter that does not filter your business partner (e.g. Business Partner
=“99999”).
Replicate Data
Start transaction DRFOUT. Select your Replication model ZRM_XX. Execute.
Check if the Business Partner you have selected is replicated. Analyze the application log to find out details on the
filtering of objects.
Adjust the filter and replicate again. Start Transaction DRFF (or go to “Supplier Governance” “Data Replication”
“Define Filter Criteria”). Use the Business Partner Number that has been created for your supplier (Supplier_XX).
Start transaction DRFOUT. Select your Replication model ZRM_XX. Execute.
Check if the Business Partner you have selected is replicated. Analyze the application log.
Check the Replication Status also in the Replication Status Monitor: “Supplier Governance” “Data Replication”. It will
show you the replication status as well as the Object ID in the client system.
Check in the client system (ZME Client 900). Transaction “BP”.
SAP Class Week of March 12, 2012
4
Ex erc i se 3 (Dat a Repl i c at i on Ex t ensi bi l i t y - opt i onal )
Introduction
The exercises will guide you through the steps that are necessary if an additional filter for the data replication should be
implemented. All steps have been prepared and the parameters valid throughout the exercise (replace XX with your
two-digit Team Number) are:
Replication model: ZRM_EXT_XX
Outbound Implementation: ZOI_BPS_XX (Class: ZCL_OI_BP_SOA_TRAINING_XX)
Filter Object: ZFO_BP_XX
Segment Filters: ZFO_BP1_RO (BP Role), ZFO_BP2_CC (Company Code), ZFO_BP3_PO (Purchasing Org)
Filter Class: ZCL_BP_FILTER_TRAINING_XX
Filter Structure: ZTRAIN_S_DRF_SERVICE_FLT
Search Term 1 for Business Partner: TRAINING_XX
Create your Outbound Implementation
Start Transaction DRFIMG. Navigate to “Enhance Default Settings for Outbound Implementations” ->“Define
Outbound Implementations”. Create Outbound Implementation “ZOI_BPS_XX”.
Outbound Implementation Class: “ZCL_OI_BP_SOA_TRAINING_XX”.
Communication Channel “Replication via Services”.
Service Operation “986”
Business Object Type: “986 - Business Partner including Relationships”
Filter Object: “ZFO_BP_XX”
Create your Repli cation Model
Start Transaction DRFIMG. Navigate to “Custom settings for Data Replication” ->“Edit Replication model”.
Check the following entry:
Replication model: ZRM_EXT_XX. Description “Replication Model Group XX”.
Outbound implementation: “ZOI_BPS_XX”.
Assign Receiver System “ZME_900”
Assign Outbound Parameter: Press “Get default settings” and assign “Outbound Parameter Value =100” for
“Outbound Parameter PACK_SIZE_BULK”.
Save and activate your replication model. If it cannot be activated from DRFIMG, go to transaction SE38 and activate
your replication model by using Report “ZR_ACTIVATE_REPLICATION_MODEL”. This workaround is needed to
create more than one replication model with the same business object type and target system.
Familiari ze yourself with the Master Data to be replicated
Start Transaction BP. In the locator on the left side, search for a Business Partner with Search Term 1 =
TRAINING_XX. Note down the number of this business partner.
Display the business Partner in the role FLVN00 “CVI FI Vendor”. Navigate to the company-code specific data and
check for which company codes data exist. Note down the displayed vendor number (which can be different from the
business partner number).
Mai ntain Filter for your repli cation model
Start Transaction DRFF. Select your Replication model ZRM_EXT_XX.
Check which fields are available for filtering data. Enter the business partner number from step 1 as filter criteria. Save
and close the screen.
Replicate Data
Start transaction DRFOUT. Select your Replication model ZRM_EXT_XX. Execute.
Check if the Business Partner you have selected is replicated. Analyze the application log to find out details on the
filtering of objects. The Business Partner has not been replicated as the payment terms are not maintained.
SAP Class Week of March 12, 2012
5
Maintain Filter Configuration
Start transaction DRFIMG:
Navigate to the filter object via
Enhance Default Settings for Outbound Implementations
o Define Filter Objects
Select your filter object ZFO_BP_XX and choose the node “Assign filters”.
Change the filter type to “Explicit Complex Filter” and add the “General Filter Parameter =
ZTRAIN_S_DRF_SERVICE_FLT”. Double-click the structure definition and check that the field “payment terms” is
included in the structure.
Change Filter Class to read Filter Criteri a and apply
Navigate from the filter configuration to your filter class ZCL_BP_FILTER_TRAINING_XX. Edit the method
IF_DRF_FILTER~APPLY_FILTER. Uncomment the coding lines marked in the code (“Start/End uncomment for
Extensibility Exercise”). Note: there are two coding blocks that have to be changed. Save and activate the class.
Mai ntain Filter for your repli cation model
Start Transaction DRFF. Select your Replication model ZRM_EXT_XX (you might want to add the Replication Model
ID via “Settings” if the replication model description is not unique).
Add “Payment Terms =0001”. Save and close the screen.
Adapt the Master Data to be replicated
Start Transaction BP to maintain your Business Partner (Search Term =“TRAINING_XX”).
Display the business Partner in the role FLVN00 “CVI FI Vendor”. Navigate to the company-code specific data. Change
the payment terms for Company code 3000 to “0001”.
Replicate Data and anal yze log
Start transaction DRFOUT. Select your Replication model ZRM_EXT_XX. Execute. Check that the Business Partner is
replicated. Analyze the application log for any other errors.
Adapt the filter such that the Business Partner will not be replicated. Repeat the replication and check the log.
SAP Class Week of March 12, 2012
6
Sol ut i on 1 – Ex t r ac t i on and Load
This exercise leads you through one example of extracting data from a client system to the MDG Hub system. Be
aware that this is usually done for “many” objects at once (either for initial load or for a delta load). Usually this would
also happen “scheduled” (using e.g. the scheduled reports RSEOUT for extraction and RMDG_FILE_UPLOAD_BG for
load).
Create a Material in the Client Syst em
Log on to ZME, Client 900.
Start transaction MM01. Create a material: MAT_XX (Basic Data 1 and Basic Data 2)
Extract the Materi al
Start transaction BD10. Send material MAT_XX to logical system MDGMAT (this will create an XML-File). Be aware
that for Business Partners (as well as for Key- and Value-Mapping) there is also the SOA-based extraction report
“RMDG_EXTRACTOR_BG”.
Check the Extraction
Start transaction BD87. Search for the XML File created by you.
SAP Class Week of March 12, 2012
7
Search for your material number and the name of the XML-File. You can use transaction WE09 (search in Segment
E1MARAM, Field MATNR for your material number).
Import the Material (into MDG Hub – Client 800)
Log on via Portal or the NetWeaver Business Client.
Go to “Material Governance” “Data Replication” “File Import”.
Choose File System “Application Server”, Select your file and add the file to “Selected Files”.
SAP Class Week of March 12, 2012
8
Click Next. Select Persistence Choice “2 – Active Area” and “Start Upload”. You could also choose “1 – Staging Area”
and the Material Change Request Type (this would result in a change request which has to be approved).
Check the log.
SAP Class Week of March 12, 2012
9
Veri fy that the material has been l oaded
Go to “Material Governance” “Display Material” (assign data model MM and the UI configuration if needed) or check
using transaction MM02 in client 800.
SAP Class Week of March 12, 2012
10
Sol ut i on 2 – Dat a Repl i c at i on
This exercise leads you through the main configuration and monitoring steps of the Data Replication Framework.
Create a Supplier
Request and approve a supplier (Supplier XX). Note down the Business Partner Number (here: 3019).
Configure your replication model (MDG Hub – Client 800)
Start Transaction DRFIMG. Navigate to “Define Replication model”.
Create the following entry: ZRM_XX
Text: Team XX Replication model
Log Days: 15
Navigate to “Assign Outbound implementation” and assign the outbound implementation 986_3 (Replication via
Services). Save your entry.
SAP Class Week of March 12, 2012
11
Assign the target system ZME_900 to the outbound implementation.
Assign Outbound Parameter: Press “Get default settings” and assign “Outbound Parameter Value =100” for
“Outbound Parameter PACK_SIZE_BULK”.
Save your replication model.
Go to transaction SE38 and activate your replication model by using Report “ZR_ACTIVATE_REPLICATION_MODEL”.
This workaround is needed to create more than one replication model with the same business object type and target
system.
Check if the replication model has been activated (transaction DRFIMG).
SAP Class Week of March 12, 2012
12
Mai ntain Filter for your repli cation model
Start Transaction DRFF (or go to “Supplier Governance” “Data Replication” “Define Filter Criteria”.
Select your Replication model ZRM_XX. Create a filter that does not filter your business partner (e.g. Business Partner
=“99999”).
Replicate Data
Start transaction DRFOUT. Select your Replication model ZRM_XX. Execute.
Check if the Business Partner you have selected is replicated. Analyze the application log to find out details on the
filtering of objects.
SAP Class Week of March 12, 2012
13
Adjust the filter and replicate again. Start Transaction DRFF (or go to “Supplier Governance” “Data Replication”
“Define Filter Criteria”.
Start transaction DRFOUT. Select your Replication model ZRM_XX. Execute.
Check if the Business Partner you have selected is replicated. Analyze the application log.
Check the Replication Status also in the Replication Status Monitor: “Supplier Governance” “Data Replication”. It will
show you the replication status as well as the Object ID in the client system (here: 115).
SAP Class Week of March 12, 2012
14
Check in the client system (ZME Client 900). Transaction “BP”.
SAP Class Week of March 12, 2012
15
Sol ut i on Ex er c i se 3
Create your Outbound Implementation
Start Transaction DRFIMG. Navigate to “Enhance Default Settings for Outbound Implementations” ->“Define
Outbound Implementations”. Create Outbound Implementation “ZOI_BPS_XX”.
Outbound Implementation Class: “ZCL_OI_BP_SOA_TRAINING_XX”.
Communication Channel “Replication via Services”.
Service Operation “986”
Business Object Type: “986 - Business Partner including Relationships”
Filter Object: “ZFO_BP_XX”
Create your Repli cation Model
Start Transaction DRFIMG. Navigate to “Custom settings for Data Replication” ->“Edit Replication model”.
Check the following entry:
Replication model: ZRM_EXT_XX. Description “Replication Model Group XX”.
Outbound implementation: “ZOI_BPS_XX”.
Assign Receiver System “ZME_900”
Save and activate your replication model. If it cannot be activated from DRFIMG, go to transaction SE38 and activate
your replication model by using Report “ZR_ACTIVATE_REPLICATION_MODEL”. This workaround is needed to
create more than one replication model with the same business object type and target system.
SAP Class Week of March 12, 2012
16
Familiari ze yourself with the Master Data to be replicated
Start Transaction BP. In the locator on the left side, search for a Business Partner with Search Term 1 =
TRAINING_XX. Note down the number of this business partner.
Display the business Partner in the role FLVN00 “CVI FI Vendor”. Navigate to the company-code specific data and
check for which company codes data exist. Note down the displayed vendor number (which can be different from the
business partner number).
Mai ntain Filter for your repli cation model
Start Transaction DRFF. Select your Replication model ZRM_EXT_XX.
Check which fields are available for filtering data. Enter the business partner number from step 1 as filter criteria. Save
and close the screen.
SAP Class Week of March 12, 2012
17
Replicate Data
Start transaction DRFOUT. Select your Replication model ZRM_EXT_XX. Execute.
Check if the Business Partner you have selected is replicated. Analyze the application log to find out details on the
filtering of objects. The Business Partner has not been replicated as the payment terms are not maintained.
Maintain Filter Configuration
Start transaction DRFIMG:
Navigate to the filter object via
Enhance Default Settings for Outbound Implementations
o Define Filter Objects
Select your filter object ZFO_BP_XX and choose the node “Assign filters”.
Change the filter type to “Explicit Complex Filter” and add the “General Filter Parameter =
ZTRAIN_S_DRF_SERVICE_FLT”. Double-click the structure definition and check that the field “payment terms” is
included in the structure.
SAP Class Week of March 12, 2012
18
Change Filter Class to read Filter Criteri a and apply
Navigate from the filter configuration to your filter class ZCL_BP_FILTER_TRAINING_XX. Edit the method
IF_DRF_FILTER~APPLY_FILTER. Uncomment the coding lines marked in the code (“Start/End uncomment for
Extensibility Exercise”). Note: there are two coding blocks that have to be changed. Save and activate the class.
SAP Class Week of March 12, 2012
19
Mai ntain Filter for your repli cation model
Start Transaction DRFF. Select your Replication model ZRM_EXT_XX (you might want to add the Replication Model
ID via “Settings” if the replication model description is not unique).
Add “Payment Terms =0001”. Save and close the screen.
Adapt the Master Data to be replicated
Start Transaction BP to maintain your Business Partner (Search Term =“TRAINING_XX”).
Display the business Partner in the role FLVN00 “CVI FI Vendor”. Navigate to the company-code specific data. Change
the payment terms for Company code 3000 to “0001” (choose it from the F4 help if you are not able o type it in).
SAP Class Week of March 12, 2012
20
Replicate Data and anal yze log
Start transaction DRFOUT. Select your Replication model ZRM_EXT_XX. Execute. Check that the Business Partner is
replicated. Analyze the application log for any other errors.
Adapt the filter such that the Business Partner will not be replicated. Repeat the replication and check the log.
SAP Class Week of March 12, 2012
©2010 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, 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 other
countries.
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 registered
trademarks of Business Objects Software Ltd. in the United States and in other countries.
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.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors
or omissions with respect to the materials. The only warranties for SAP Group 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.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Documentation can be found here: SAP ERP Cross-Application Functions / Cross Application
Components / Master Data Governance
Working with Master Data Governance
General Functions
Mass Data Load
Supplier
Mass Data Load
Financials
File Upload
File Download
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Although MDG delivers a new SOA based framework with ERP EhP5 other technologies for
extraction and load are still available and can be considered if appropriate (for example „pure
ALE“ technology (via transactions BD10 or BD14), LSMW, SAP BusinessObjects Data
Services). These might be sufficient for loading data in non-SOA based format (e.g. csv-files
or, IDoc-XML) into the active area. The new framework allows additionally for direct load of
data in the SOA-format into active area or staging (which is not available via other
technologies).
Be aware that master data (as well as key- and value-mapping) can be extracted from clients
as well as from the MDG system. Extracting data from MDG is used to allow Consolidation
and Data Quality Services through additional components (like NW MDM or SBOP Data
Services). See „Data Quality“.
SAP MDG stores data in one of two persistencies: Staging Area or Active Area. Data in the
staging area is not ready for consumption and usually has to be approved by a Master Data
Steward to be sent to the Active Area.
ESB (Enterprise Service Bus; Middleware), NW MDM (NetWeaver Master Data
Management) or SBOP DS (SAP BusinessObjects Data Services) are optional components.
Additional implementation steps are necessary to build scenarios based on these
components.
SAP Class Week of March 12, 2012
Although MDG delivers a new SOA based framework with ERP EhP5 other technologies for
extraction and load are still available and can be considered if appropriate (for example „pure
ALE“ technology (via transactions BD10 or BD14), LSMW, SAP BusinessObjects Data
Services). These might be sufficient for loading data in non-SOA based format (e.g. csv-files
or, IDoc-XML) into the active area. The new framework allows additionally for direct load of
data in the SOA-format into active area or staging (which is not available via other
technologies).
Be aware that master data (as well as key- and value-mapping) can be extracted from clients
as well as from the MDG system. Extracting data from MDG is used to allow Consolidation
and Data Quality Services through additional components (like NW MDM or SBOP Data
Services). See „Data Quality“.
SAP MDG stores data in one of two persistencies: Staging Area or Active Area. Data in the
staging area is not ready for consumption and usually has to be approved by a Master Data
Steward to be sent to the Active Area.
ESB (Enterprise Service Bus; Middleware), NW MDM (NetWeaver Master Data
Management) or SBOP DS (SAP BusinessObjects Data Services) are optional components.
Additional implementation steps are necessary to build scenarios based on these
components.
SAP Class Week of March 12, 2012
Roles mentioned here are suggestions how the existing role “Master Data Manager” can
further be divided into smaller sub-roles.
SAP Class Week of March 12, 2012
Transformation only needed for supplier data coming from SAP releases <ERP EhP5 and
only if SAP NetWeaver MDM should be used for Consolidation Services.
In EhP5 there is no need to transform Material IDocs.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Depending on the releases of the SAP client systems different scenarios are possible. The following
slides should cover three common scenarios.
Be aware that MDG-F does not use the Data Export / Data Import Framework. It uses the File
Upload / File Download functionality.
See „Initial Load of the MDG-F System“ and the
documentation for further information.
Documentation: Working with Master Data Governance / Financials / File Upload and File
Download
Be aware that for Business Partners also transaction „BUPA_SEND“ is available which
includes full address data.
SAP Class Week of March 12, 2012
Note: These prerequisites are also needed for extratcions based on CREMAS and
CREMDM.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
For a high data volume this program should be scheduled (choosing periods with a small
number of online users interacting with the system). See transactions SM36 and SM38.
Extractor will write files to the logical directory MDG_INITIAL_LOAD (needs to be created
using transaction “FILE” - assignment of logical directories).
You can use transactions CG3Y download and data from the application server to your local
file system.
Number of selected objects might differ from selection (e.g. existing Business Partner
Relationships will extracted as well which leads to one additional object per relationship).
Relationships are stored in different files. Be aware that there are dependencies between the
object files and the relationship files. These files can be uploaded in one upload process.
Additional selection fields can be added through transaction MDG_DL_OBJ - Define Object
Types for Data Load.
SAP Class Week of March 12, 2012
Object Type
Usually the object type is a master data object like „Supplier“ but the extractor can also
extract Value- and Key-Mapping as well as customizing data that is bound to the master data
objects.
Value-Mapping is used to extract customizing code lists from a client system. These can be
used in the MDG system for mappings that are performed in data replication processes (see
„Data Replication for MDG”). Choose object type “VM” for this.
Key-Mapping extraction is usually used to extract information about duplicates from the MDG
system to an external Data Quality Service. Choose object type „IDM“ for this.
Customizing (reference) data can be extracted via „Additional objects“ in the variant.
Export Type
Usually „Export to File“ for mass data. If „consumption by a service“ is chosen the data will be
send via the respective service.
Delta Extraction
Be aware that the delta extraction depends on the variant. A new variant will always select
the objects according to the select options!
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Displaying files: If the XML files cannot be displayed in a browser, open them in an editor
(e.g. notepad) and save them from the editor.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Converter uses the logical directory MDG_TRANS_SOURCE and will write files to
MDG_INITIAL_LOAD (needs to be created using transaction “FILE” - assignment
of logical directories).
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP NW MDM and SBOP Data Services are optional components delivering consolidation
and data quality services.
For consolidation services the focus would be on NW MDM (Matching, Merging, Validations,
Enrichment) which can be extended by SBOP DS capabilities (additional services for
extraction, transformation, matching, validations, enrichment).
For data quality services there are two additional use cases where these additional
components can support (not shown here):
Duplicate checks in the master data creation process - focus on SBOP DS
Data Quality checks in regular batch runs (extracting data from MDG,
matching/merging/validation/enrichment, loading cleansed data in MDG) - NW MDM and/or
SBOP DS (depending on use case)
SAP Class Week of March 12, 2012
Extractor Framework: MDG Extractor and related capabilites (e.g. BD10, BD14,
MDM_CLNT_EXTR, MDMGX)
Transformations: For client releases <ERP EhP5 a transformation into the SOA format is
needed (see file converter). Note: For this value mapping has to be uploaded from the client
system to the MDG system. Additionally a transformation from the SOA format to a business
partner repository is needed.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Converter: User defined transformation. Usually there is no additional transformation needed
in this step (if the format is a SAP standard format - either IDoc or
SOA based).
Object Type Handler: Object specific implementation (for example for supplier or material).
Usually the object type is a master data object like „Supplier“ but the upload also upload
Value- and Key-Mapping. See „Extractor“ for a description how to extract Mapping.
SAP Class Week of March 12, 2012
For a high data volume this program should be scheduled (choosing periods with a small number of
online users interacting with the system). See transactions SM36 and SM38.
Directory can be chosen from logical directories defined in transaction FILE. Consider creating several
directories which are object specific or even specific for load processes. Be aware that files will not be
removed from the directory by the upload process.
You can use transaction CG3Z to upload data from your local file system to the application server.
Filename Filter: make sure that there are either only files in the directory that belong to your load
process or limit the number of chosen files by using an appropriate filter (e.g. *167110.xml if you only
want to select the file with this ID; or *BusinessPartner*.xml if you only want to chose suppliers)
Supported message formats
BusinessPartnerSUITEBulkReplicateRequest
BusinessPartnerRelationshipSUITEBulkReplicateReq (relationships are stored in separate files and
can be uploaded in the same upload process)
CREMDM
CREMAS (single records only)
MATMAS
CLFMAS
SAP Class Week of March 12, 2012
Converter
Third party systems may not be able to create message types supported
during the MDG Upload. You should consider either to perform external
transformations to one of the supported formats or implementing a
converter BADI for the upload. Converter and BAdI can be defined in the
MDG IMG (General Settings / Mass Data Load)
Duplicate Check: This option uses the same configuration which is used for the duplicate
check in the master data creation process. It is not yet suitable for high volume data quality
checks (please consider external data quality services).
Choices for potential duplicates:
1. Post as New Record - The selected record will be posted as a new record
2. Create Key Link - Creates a key-mapping entry for the selected record and the first
potential duplicate
SAP Class Week of March 12, 2012
After the upload the log can be checked using transaction SLG1 (Application Log).
Errors and duplicate proposals can be checked in transaction /SAPPO/PPO2 (PPO - Post
Processing / FEH – Forward Error Handling).
Reprocessing can be done in /SAPPO/PPO2 (select multiple entries with Shift / Mouseclick
or CTRL / Mouseclick) or via /SAPPO/RESUBMIT (for batch processing)
FEH might have to be enabled: FEHV_ACTIVE (use transaction SM31)
The creation of key mappings can be checked using transaction MDG_ANALYSE_IDM
(Search Key Mapping).
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Shortcut to DRF Customizing: transaction DRFIMG.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Recommended approach if mapping in the client is available.
SAP Class Week of March 12, 2012
Recommended approach if mapping in the client is not available (earlier releases or non-SAP).
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Overview of the most important set-up steps for service based communication. Please refer to
MDG Configuration Guide and/or the service communication documentation for more details.
Cross-Application Components Processes and Tools for Enterprise Applications Enterprise
Services Point-to-Point Enablement for Asynchronous Enterprise Services Activate Support
for Point2Point Communication and set the flag to active in provider and consumer system.
Use transaction SOAMANAGER to create profiles, accounts and scenario configurations.
For detailed information please check „How to Develop, Monitor and Debug WS Consumer and
Provider” on http://sap.sdn.com.
SAP Class Week of March 12, 2012
Overview of the most important set-up steps for service based communication. Please refer to
MDG Configuration Guide and/or the service communication documentation for more details.
Cross-Application Components Processes and Tools for Enterprise Applications Enterprise
Services Point-to-Point Enablement for Asynchronous Enterprise Services Activate Support
for Point2Point Communication and set the flag to active in provider and consumer system.
Use transaction SOAMANAGER to create profiles, accounts and scenario configurations.
For detailed information please check „How to Develop, Monitor and Debug WS Consumer and
Provider” on http://sap.sdn.com.
SAP Class Week of March 12, 2012
Overview of the most important set-up steps for service based communication. Please refer to
MDG Configuration Guide and/or the service communication documentation for more details.
Cross-Application Components Processes and Tools for Enterprise Applications Enterprise
Services Point-to-Point Enablement for Asynchronous Enterprise Services Activate Support
for Point2Point Communication and set the flag to active in provider and consumer system.
Use transaction SOAMANAGER to create profiles, accounts and scenario configurations.
For detailed information please check „How to Develop, Monitor and Debug WS Consumer and
Provider” on http://sap.sdn.com.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Define Technical Settings and Replication Models will be shown in the next slides.
Define Business Object Settings is needed if the ALE change pointer should be connected to the
DRF change pointers. This is provided for downward compatibility to ALE scenarios. If ALE
change pointers are not used (because e.g. the business object changes are always restributed
after the change request is approved) there is no need to maintain these settings.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
The Replication Log is based on the (reuse component) Application Log
It is not always necessary to assign a data model. This field is currently only used for data models
in MDG for Financials.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
In addition to filters you can subscribe objects that will be replicated. This can be used to
subscribe data from legacy systems that does not fit into the filtering system.
SAP Class Week of March 12, 2012
In non-harmonized scenarios business objects do have different Object IDs. The key mapping in
MDG takes care of the mapping. In this example the Business Partner (a supplier) does have the
BP Object ID „3140“ (and the Supplier ID „102668“) in the MDG Hub and the Object ID „4766“ in
the client system.
After a client copy key mappings needs to be adjusted (on the hub as well as on the client
system) with transaction MDG_ADJ UST_IDM.
SAP Class Week of March 12, 2012
Value Mapping is used to overcome differences in the configuration of the systems in the system
landscape. One example would be a code „0001“ for the title „Ms.“ in system A and a code „0002“
in system B. DRF will map these codes according to settings maintained in the value mapping.
In order to support easier maintenance it is possible to upload code lists that originate from client
systems. This can be done through the extractor framework or manually.
Master Data Governance can be found in the IMG (transaction SPRO): Cross-Application
Components, Processes and Tools for Enterprise Applications
SAP Class Week of March 12, 2012
Overview of the most important ALE customzing steps. Please refer to the ALE documentation for
more details.
SAP Class Week of March 12, 2012
Overview of the most important set-up steps for service based communication. Please refer to
MDG Configuration Guide and/or the service communication documentation for more details.
Cross-Application Components Processes and Tools for Enterprise Applications Enterprise
Services Point-to-Point Enablement for Asynchronous Enterprise Services Activate Support
for Point2Point Communication and set the flag to active in provider and consumer system.
Use transaction SOAMANAGER to create profiles, accounts and scenario configurations.
For detailed information please check „How to Develop, Monitor and Debug WS Consumer and
Provider” on http://sap.sdn.com.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
Overview of the most important set-up steps for service based communication. Please refer to
MDG Configuration Guide and/or the service communication documentation for more details.
Cross-Application Components Processes and Tools for Enterprise Applications Enterprise
Services Point-to-Point Enablement for Asynchronous Enterprise Services Activate Support
for Point2Point Communication and set the flag to active in provider and consumer system.
Use transaction SOAMANAGER to create profiles, accounts and scenario configurations.
For detailed information please check „How to Develop, Monitor and Debug WS Consumer and
Provider” on http://sap.sdn.com.
SAP Class Week of March 12, 2012
Usually the data replication is started with the option „Changes“. The system will evaluate
„change pointers“ to create the „object list“ consisting of business objects to be replicated. The
replication of business object „BO A“ to system „S1“ will reset the change pointer which means
that this business object will only be replicated (in option „Changes“) again if it has been changed
after the last replication.
In order to avoid the non-intentional replication of large amounts of data the option „Limit Changes
Using Time Interval“ can be used. This might be necessary if mass changes did occur that should
not be replicated during business hours - as this might have a negative impact on the overall
system performance.
SAP Class Week of March 12, 2012
This replication mode is used if business object changes (or creations) should be sent
immediately after the Change Request has been approved. It allows for realtime replication to
client systems.
SAP Class Week of March 12, 2012
Additionally to the usage in a background job for a „scheduled“ replication, transaction DRFOUT
can also be used to manually replicate data. But for this purpose there is also a Web UI offered by
MDG which can be started in the Portal by the Master Data Steward.
SAP Class Week of March 12, 2012
Transaction DRFLOG offers comprehensive logging capabilities that can be used by the Master
Data Administrator to resolve technical problems. It offers drill down capabilitites into related logs
like ALE and PI Logging.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
DRF can be integrated into the CCMS monitoring which enables the triggering of alerts as well as
the integration of 3rd party (non SAP) monitoring tools.
SAP Class Week of March 12, 2012
The replication status provides a user interface that allows the Master Data Steward to check the
replication status of specific objects. This allows a business object related monitoring - which is
different from the replication log which has a more technical view with a focus on data replication
runs that might include many business objects.
If the user interface shows too much information, personalize your view – using „Settings“.
Problems that are identified here usually have to be evaluated by a Master Data Administrator
using the DRFLOG transaction.
There is also a SAPGUI transaction for the administrator for the replication status: DRFRSD
which shows more technical details. Be aware that the object type code handling might differ
depending on the business object. E.g. the Business Partner is handled in general by object type
986 which is used in the SAP GUI but is automatically exchanged by object type 147 in the Web
UI .
SAP Class Week of March 12, 2012
In addition to the replications status MDG also offers a Replication Log in the Web UI. It offers
some additional capabilities for the Master Data Steward to drill deeper into problems in the data
replication if needed. A drill down into technical details is not possible and would usually be done
by the Master Data Administrator (using the SAPGUI transation DRFLOG).
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
The mass change service allows to replace the selected materials and their selected content
with a new value per field for all selected materials.
Updating multiple materials is a two step process; you first create a change request for
multiple materials using this service, then you use the Mass Change service to enter the
details for the changes you want to make.
How to create a change request is described in more detail in the generic learning units for
MDG but as well on the previous services e.g. for the Create Material service.
Here we focus on the Mass Change service itself:
1. Open the Mass Change screen: Select the Mass Change link from the Material
Governance work center.
2. Select materials to include: Use the Selections list to choose the materials you want to
include in your change request. Click the Next button to continue.
3. Refine your selection: Use the Scope of Selection table to review your chosen materials
and remove any materials you do not want to include in your change request. Note that if
a material you have selected already exists in the staging area, this change request
overwrites it. A warning about this overwrite appears when you attempt to execute the
changes. Click the Next button to continue.
4. Define values: Choose the attributes you wish to change and the value you wish to set
them to. To do this, enter the new value in the Replace With column of the attribute you
want to change. This value is set for the attribute in each material you selected. Note that
only attributes available for mass change are visible on this screen. Click the Next button
to continue.
5. Check and execute: Review your changes. If you are happy with them, click the Execute
Changes button to submit your change request.
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
SAP Class Week of March 12, 2012
MDG FOR MATERI AL
TZMDG1 – Exercise 3.3
Exercises / Solutions
Ingo Rothley / SAP AG
Exercise: Run MDG material mass processes
At the end of this exercise you are able to:
Use the search capabilities of MDG (Enterprise / TREX search)
Run MDG Material change requests incl. mass changes
Maintain & Search for Key Mapping Information (optionally)
You are acting as a business user of the logistics department. You are
supposed to maintain material master data of an enhanced product line.
All objects of this exercise are named with ##. Please replace this with
your group number:
## = Group Number = 01 – 30
Parameters valid throughout the Exercise(Replace ##with your two-digit
Team Number):
Logon to the SAP System [….]
Username: [….]
Password [….]
In MDG you are able to work with the internet based NetWeaver
Business Client (NWBC) or via the enterprise portal
SAP Class Week of March 12, 2012
2
Ex erc i se 1: Searc h f or Mat er i al and t r i gger a copy
Your company is in the CD manufacturing business and has enhanced an existing product line. Therefore additional
master data needs to be maintained in order to reflect the business in the ERP backend system. You now also want to
manufacture Mini-CDs and therefore you need the correct labels.
As a long term and loyal SAP customer, your company has decided to use Master Data Governance for this!
Search for the CD labels
Start your search in the Material work center.
How many materials with description containing “label” do exist ? ________________________
Narrow down your search to Raw material (ROH), how many? ________________________
Finally you are only interested on CD labels of your group ##in the material group 00213,
please note the material IDs ________________________
Copy an existing label to a new material “ Mini-CD”
Copy one of the materials to the new label for Mini-CDs (Material ID ACT-MCD-xx). Adjust the descriptions.
Submit and Approve the change request.
You might want to trigger this activity directly from the search results
Ex erc i se 2: Mass Change -
Your company is not only broadening their products, but also needs to invest in quality. Therefore a new Lab G##has
been built and needs to be assigned to the CD Labels.
Preparati on: Create a new change request for material changes.
You need to create a new change request of the correct type to later on link the material object list during mass change
to this change request. Make a reasonable description and note down the ID ________________________
Execution: Change the Verify information on Editions
Start a mass change for the 3 Labels ACT-BCD-##, ACT-LCD-##and ACT-MCD-##
Which are the (at least) two alternatives how this can be started _________________________________
___________________________________________________________
___________________________________________________________
Opt i onal Ex er c i se 3: Mai nt ai n & Sear c h f or Key Mappi ng
I nf or mat i on
Unfortunately your material keys are not harmonized and synchronized across the company. You had always some
XLS-Lists on your desktop to not confuse the materials across the system. In order to be able to distribute the material
changes correctly, key mapping information now needs to be maintained in MDG.
Search for key mappings
The BI system is connected as system ID BI_900.
What is the key of material ID ACT-BCD-30 in this target system? ____________________________
Create a similar mapping for your CD labels
SAP Class Week of March 12, 2012
3
Create / maintain key mapping for your 3 CD Label materials ACT-BCD-##, ACT-LCD-##and ACT-MCD-##for the BI
target system (in this case represented in the 900 client of the training box).
Optionally: distribute your materials to the BI client using ALE
Not sure if this is possible – probably need to final ize some settings
Room for your notes & questions:
SAP Class Week of March 12, 2012
4
Sol ut i on Ex er c i se 1: Searc h f or Mat er i al and t r i gger a c opy
Your company is in the CD manufacturing business and has enhanced an existing product line. Therefore additional
master data needs to be maintained in order to reflect the business in the ERP backend system. You now also want to
manufacture Mini-CDs and therefore you need the correct labels.
As a long term and loyal SAP customer, your company has decided to use Master Data Governance for this!
Search for the CD labels
Start your search in the Material work center.
Add search attribute “Medium Text” and choose relation operator as “contains” and enter search attribute value for this
field as “label” as shown under & click on the Search button
SAP Class Week of March 12, 2012
5
How many materials with description containing “label” do exist ? ___________132_____________
Narrow down your search to Raw material (ROH), how many? ____________72____________
Add additional search attribute “Material Type” by clicking on the (+) button and enter search attribute value for this as
“ROH (Raw Materials” either directly or choosing via F4 help and then click on the “Search button” to get the result list
as shown below.
Finally you are only interested on CD labels of your group ##in the material group 00213,
please note the material IDs __ ACT-BCD-##, ACT-LCD-##___
Add additional search attribute “Material Group” by clicking on (+) button and then enter attribute value as “00123”
Copy an existing label to a new material “ Mini-CD”
Copy one of the materials to the new label for Mini-CDs (Material ID ACT-MCD-xx). Adjust the descriptions.
Submit and Approve the change request.
SAP Class Week of March 12, 2012
6
From the search result list shown above, select the record and then select the “Copy” button on the result list tool bar.
SAP Class Week of March 12, 2012
7
You might want to trigger this activity directly from the search results
SAP Class Week of March 12, 2012
8
Sol ut i on Ex er c i se 2: Mass Change -
Your company is not only broadening their products, but also needs to invest in quality. Therefore a new Lab G##has
been built and needs to be assigned to the CD Labels.
Preparati on: Create a new change request for material changes.
You need to create a new change request of the correct type to later on link the material object list during mass change
to this change request. Make a reasonable description and note down the ID ________________________
SAP Class Week of March 12, 2012
9
Execution: Change the Verify information on Editions
Start a mass change for the 3 Labels ACT-BCD-##, ACT-LCD-##and ACT-MCD-##
Which are the (at least) two alternatives how this can be started _____search______________________
_____________mass change service____________________________
_____________assign objects during creation of the CR ____________
SAP Class Week of March 12, 2012
10
SAP Class Week of March 12, 2012
11
SAP Class Week of March 12, 2012
12
SAP Class Week of March 12, 2012
13
Sol ut i on Ex er c i se 3: Mai nt ai n & Searc h f or Key Mappi ng
I nf or mat i on
Unfortunately your material keys are not harmonized and synchronized across the company. You had always some
XLS-Lists on your desktop to not confuse the materials across the system. In order to be able to distribute the material
changes correctly, key mapping information now needs to be maintained in MDG.
Search for key mappings
The BI system is connected as system ID BI_900.
What is the key of material ID ACT-BCD-30 in this target system? ___9ACT-BCD-30 ____________
SAP Class Week of March 12, 2012
14
Create a similar mapping for your CD labels
Create / maintain key mapping for your 3 CD Label materials ACT-BCD-##, ACT-LCD-##and ACT-MCD-##for the BI
target system (in this case represented in the 900 client of the training box).
SAP Class Week of March 12, 2012
15
Optionally: distribute your materials to the BI client using ALE
SAP Class Week of March 12, 2012
©2011 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, 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 other
countries.
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 registered
trademarks of Business Objects Software Ltd. in the United States and in other countries.
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.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors
or omissions with respect to the materials. The only warranties for SAP Group 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.
SAP Class Week of March 12, 2012

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close