You are on page 1of 26

SAP Master Data Governance,

Financial Data
Implementation And Set–up of MDGF

April 2010
Objectives

At the end of this unit, you will be able to:


 Identify the mandatory customizing activities for setting up a
standard process in MDGF
 Reproduce alternative ways to set up MDGF processes

© 2010 SAP AG. All rights reserved. / Page 2


Agenda

1. Prerequisites
2. Setting up the process
- Data Modeling
- UI Modeling
- Process Modeling
- Data Replication
3. Optional MDGF settings
- Data Modeling
- Process Modeling

© 2010 SAP AG. All rights reserved. / Page 3


Agenda

1. Prerequisites
2. Setting up the process
- Data Modeling
- UI Modeling
- Process Modeling
- Data Replication
3. Optional MDGF settings
- Data Modeling
- Process Modeling

© 2010 SAP AG. All rights reserved. / Page 4


Business Functions in The Switch Framework

MDGF Business Functions


 Central System
 FIN_MDM_ACC
 FIN_MDM_ORG
 Client System(s)
 FIN_MDM_SOA_CU
 FIN_MDM_SOA_ORG

Please refer to the


documentation of the
business functions for further
details.

© 2010 SAP AG. All rights reserved. / Page 5


Settings in Other Systems

The MDGF solution is set-up in an ERP-System but can closely interact with
products from SAP NetWeaver:

 MDGF Client Systems: To be able to receive data from the central MDGF system, settings
need to be made in the clients. Please refer to the following RKT sessions:
 “Setting-up the Replication of Master Data” in the general section of the learning map

 NetWeaver Enterprise Portal: The EP can act as User Interface. Certain settings have to be
done there. Please refer to the following RKT sessions:
 “Portal Integration Guide for MDG” in the general section of the RKT learning map.

 NetWeaver Business Information: The MDGF reports are executed on a BI system. In order to
enable the reports, settings have to made in the BI system. Please refer to the following RKT
sessions:
 “Setting-up NetWeaver BI reporting for MDGF” in MDGF section of the learning map.

© 2010 SAP AG. All rights reserved. / Page 6


Agenda

1. Prerequisites
2. Setting up the process
- Data Modeling
- UI Modeling
- Process Modeling
- Data Replication
3. Optional MDGF settings
- Data Modeling
- Process Modeling

© 2010 SAP AG. All rights reserved. / Page 7


Change Process With Editions And
Change Requests

Master data
specialist
Corporate
Accountant
Corporate Master Corporate Master Corporate
data Administrator data Administrator Accountant
Collect
Create Change comments
Request
Create Adjust
edition Change Release Distribute Adjust
in in
Requests Approve edition edition target
target
Final by system
system
approval business
Master data Master data
steward steward
Execute changes
- Single Maintenance
-Hierarchy Maintenance
- Mass Change

Master data specialist

© 2010 SAP AG. All rights reserved. / Page 8


MDG/MDGF Customizing

Customizing for MDG/MDGF can be found in


the IMG under:
 Cross-Application Components
 Processes and Tools for Enterprise Application
 Master Data Governance
 General Settings
 Master Data Governance for Financials

The mandatory settings for MDGF are


maintained in the „General Settings“ part of
the IMG-tree.

Specific MDGF settings to adapt the solution


to special needs can be maintained in the
„Master Data Governance for Financials“ part
of the IMG-tree.

© 2010 SAP AG. All rights reserved. / Page 9


MDG/MDGF Customizing: Data Modeling

The central object of MDGF is


the data model. In it the entity
types (like accounts, cost
centers etc.) are defined.
 SAP ships two standard data
models for MDGF: 0F and 0G.
 0G is the most recent data
model for financial entities and
includes Chart of account data
as well as organizational units.
 In activity “Edit Data model” you
define and activate a data
model to map master data in
the system, along with its
properties and relationships.
The system uses this data
model to generate database
tables in which the master data
can be stored.
© 2010 SAP AG. All rights reserved. / Page 10
MDG/MDGF Customizing: Data Modeling

There are two data models


related to MDGF:
 0F: Chart of accounts
 0G: Chart of accounts
and Org. Units.

Data models need to be


activated to be usable.

You may copy and adapt


the standard data models
0F/0G for your needs.

© 2010 SAP AG. All rights reserved. / Page 11


MDG/MDGF Customizing: UI Modeling

Go to “Edit UI Configuration”
in IMG-branch “UI Modeling”.

The UI configuration
MDG_0G_Financials is the
standard UI configuration
for financial entities. It is
shipped together with MDGF.

The UI configuration
determines the look & feel
of the user interface.

You do not need to make any


changes to it but may copy
and adapt it to your needs.

See RKT session „Setting-Up


and extending User Interface
models”
© 2010 SAP AG. All rights reserved. / Page 12
MDG/MDGF Customizing: Process Modeling

Before you can implement


the workflow the customizing
for Edition and Change
Request need to be
performed.
 Define an edition type if you
want to use editions
 Define Change Request types
to meet your requirements
 If you want to use Adobe
Interactive forms to be used
in the process make the
appropriate settings
 Make the necessary settings
for the SAP Business Workflow
 Other settings in this IMG-tree
can be used to adapt the
process to your needs.

© 2010 SAP AG. All rights reserved. / Page 13


MDG/MDGF Customizing: Edition Type

To set up an edition you


can do the following:
 You define the data model
for which the edition type is
valid.
 You define whether an edition
is valid for one or more periods
or for a date-specific time
period.
 You specify which entity types
can be edited within the
editions of the new edition type.
 You can retire edition types if
they should no longer be used.
 You can define data slices.
Data slices narrow down the
entities of an entity type that
can be maintained in
an edition.

© 2010 SAP AG. All rights reserved. / Page 14


MDG/MDGF Customizing: Change Request
Type

There are two change requests types available for the process. The
behavior of the process is controlled via the change request:
 The data model in which a change request is to be valid
 Whether the user needs to specify which entities can be processed
 Whether only a single entity can be changed with the change request
 Which workflow template should be used when editing the change request
 Which entity types can be changed with the change request
 If an interactive PDF-based form (form-based change request) should be used for
processing the change request, or if a UI configuration should be used
You may copy an available CR and adapt it to your needs.
© 2010 SAP AG. All rights reserved. / Page 15
MDG/MDGF Customizing: Form–Based CR

In this Customizing activity, you edit the


scenarios that build the technical basis for the
form-based creation of change requests. The
scenario determines which form is used and
which fields are displayed in the form. You
use different versions to control the validity of
a scenario.

SAP delivers a set of scenarios and Adobe


forms
for the data model 0G.

You may copy scenarios and adapt them for


your
own requirements.

Please refer to the RKT session “Setting-up


form-based change requests” for additional
© 2010 SAP AG. All rights reserved. / Page 16
information.
MDG/MDGF Customizing: Workflow Settings

The following settings need to be


done to enable the simple MDGF
workflow (WS75700027):
 Activate the type linkage
 Configure Workflow tasks
 Define the workflow step numbers
 Assign processors to the workflow steps

Three workflow templates are


shipped with MDGF:
 Simple workflow (see above)
 Rule based workflow: Please refer to the
RKT session “Setting-up Change
Request and Workflow” in the general
section of the learning map.
 Advanced workflow: Please refer to
MDGF RKT material of EhP4

© 2010 SAP AG. All rights reserved. / Page 17


MDG/MDGF Customizing: Workflow Settings

Activate Type Linkage: You need to process this Customizing activity if


you have assigned a workflow template to a change request type. If so,
you must adjust the type linkage here.

Configure Workflow Tasks: In this Customizing activity, you specify that


tasks, which are not background tasks, are general tasks.

© 2010 SAP AG. All rights reserved. / Page 18


MDG/MDGF Customizing: Workflow Settings

To set up the simple workflow you need to perform these steps:

Define Workflow Step Numbers: You create the workflow step numbers for
your workflow and enter a short description for them. The workflow step
numbers you created are then available when you assign the workflow step
number and processor.
Configure Workflow Tasks: In this Customizing activity, you assign
processors to the individual workflow step numbers for each type of change
request. This determines which tasks the processors need to perform.
Processors can also be organizational entities from SAP Orgmanagement.
© 2010 SAP AG. All rights reserved. / Page 19
MDG/MDGF Customizing: Data Replication

The Customizing activities for data replication enable you to specify how data is
replicated to one or more target systems.
 Define Custom Settings for Data Replication: Here you define communication-
relevant settings for business systems involved in data replication, create replication
models, and define business object settings.
 Enhance Default Settings for Outbound Implementations: Here you reference
existing outbound implementations or define your own ones. Each replication model
you define can consist of one or more outbound implementations.
For more details on setting up the distribution please refer to the RKT session “Setting-
up the Replication of Master Data”.
© 2010 SAP AG. All rights reserved. / Page 20
Agenda

1. Prerequisites
2. Setting up the process
- Data Modeling
- UI Modeling
- Process Modeling
- Data Replication
3. Optional MDGF Settings
- Data Modeling
- Process Modeling

© 2010 SAP AG. All rights reserved. / Page 21


MDG/MDGF Customizing: Data Modeling

Other settings that may be


relevant for data modeling are.
 Define Authorization
Relevance per Entity Type
 Youdetermine how the
system is to use the MDG
generic authorizations
(based on the USMD_MDAT
authorization object)
 You define which key fields
and attributes the system is
to use for the authorization
check.

© 2010 SAP AG. All rights reserved. / Page 22


MDG/MDGF Customizing: Process Modeling

Other settings that may be relevant


for data modeling are.
 DefineValidation and
Derivation Rules: define the
validations and derivations for a data
model. Validations ensure that the
master data is consistent. You use
derivations to calculate values for
resolved attributes from other
resolved attributes, thereby
simplifying data entry.
 BAdI:Define Validations/
Derivations: 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
from the values of other fields in the
master data
© 2010 SAP AG. All rights reserved. / Page 23
MDG/MDGF Customizing: Process Modeling

Other settings that may be relevant for


data modeling are.
 Define
Priorities for Change
Requests: Define priorities, which users
can select when editing a change
request.
 Define
Reasons for Change
Requests: Define reasons for changes,
which users can select when creating a
change request.
 Define
Rejection Reasons for
Change Requests: Define reasons for
rejecting change requests, which users
can specify when rejecting such a
change request
 Define
Print Form for Change
Requests: Define your own custom form
for printing change requests
© 2010 SAP AG. All rights reserved. / Page 24
Lesson Summary

This unit covered the necessary and optional settings to


implement MDGF

© 2010 SAP AG. All rights reserved. / Page 25


© 2010 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein
may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries,
eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+,
POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,
MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, 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 SAP France 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.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the
express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies,
developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or
development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other
items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these
materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links
contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.
© 2010 SAP AG. All rights reserved. / Page 26