MASTER DATA GOVERNANCE (MDG) FOR FINANCE

DOCUMENT IDENTIFICATION

Author Document Location (path/name)

Version Status Date (YYYY-MM-DD) Document Classification

0.1 Draft 2016-05-25 Confidential

REVISION HISTORY

Version Date Description

0.1 May 25, 2016 Initial draft

TABLE OF CONTENT

1. PROCESS DESCRIPTION ............................................................................................... 1

1.1 MDG Business Process Requirements ...................................................................... 1
1.2 Business Process Description .................................................................................... 2
2. FUNCTIONAL & TECHNICAL SOLUTION DESIGN ........................................................ 2
2.1 MDGF Activation and Initial Configuration .................................................................. 2
2.2 Master Data Governance Framework Considerations ................................................ 3
2.3 Data Model and User Interface (UI): .......................................................................... 5
2.4 CR Types and Workflow ............................................................................................ 8
2.5 Data Quality Validation and Business Rules ............................................................ 16
2.6 Search and Duplicate Check .................................................................................... 19
2.7 Data Replication ...................................................................................................... 22

1. Process Description
1.1 MDG Business Process Requirements
The overall Process Requirements are listed below. Specific requirements will be noted in the sections where they
apply.

1 of 28
  Employ a standardized Governance framework to manage the lifecycle of master data changes for the in-
scope objects through a formalized Change Request (CR) process
 Capture the required master data for each object and leverage a standard User Interface (UI)
 Utilize consistent workflow processes for the creation and maintenance of master data
 Enable duplicate checking during the creation process
 Enforce data quality through data validations during the creation and maintenance processes
 Replicate approved master data to the ECC systems
 Provide Change History and Process-Based Metric Reporting
 Facilitate Administrative functions for system monitoring, error handling and system enhancements

There are a number of Business Processes that need to be supported, and some of the detail applies to all processes
and some details apply to specific processes. The following sections will capture both the shared components and
the process specific considerations.

1.2 Business Process Description

The high level solution design provides a system to capture, store and replicate the following finance related data
(MDG-F).

 GL Accounts (Chart of Account and Company Code levels)

 Auto Created Primary Cost Elements (from P&L GL Accounts)
 Secondary Cost Elements and the associated Hierarchies
 Cost Centers and their associated hierarchy
 Profit Centers and their associated hierarchy

2. Functional & Technical Solution Design

2.1 MDGF Activation and Initial Configuration

Activate Business Functions through transaction code SFW5. Refer below screen shot.

2 of 28
Set-up Workflow via SWU3 transaction code

2.2 Master Data Governance Framework Considerations

Figure 1 below illustrates the meta-model for a MDG data model. The standard MDG-Finance data model, “0G”, was
used.

3 of 28
 Hierarchy usage

* 1
1 * 1 1..* * 1 Data
Data model Entity types Attributes
Elements

*
*
Relations

Figure 1

The Entity Type is the next level down within a data model and in many ways resembles a typical table in a RDBMS.
An Entity Type consists of Attributes, which are analogous to the columns within a RDBMS table. The Attributes are
further defined by a Data Element, which provides the connection to the ABAP Data Dictionary. This link to the ABAP
Data Dictionary allows MDG to leverage the existing ABAP Data Elements, which can reduce the implementation
effort for custom objects. In the ABAP Data Dictionary each Data Element is further defined by a Data Domain (not
shown above).

The actual Data Model design can be found in the MDGIMG transaction.
Within MDG the Data Model is a foundational component, but there are a number of other components that tie
together to deliver the overall solution. These components and how they are related are shown in Figure 2.

Figure 2 – MDG Framework Components

The arrangement of the various components listed above is generic for all data objects within MDG. For MDGF the
standard delivered content was used in all areas with specific developments in the following areas:

 Change Request Types and Steps

 Workflow templates
 BRF+ Validations
 Work Center Services (i.e. role-based menu items)

4 of 28
Figure 3 - High Level Data Flow

The structure of this section allows for the capture of each of the business processes that the solution supports and
the specific details for each data object covering the following content areas:
 Data Model
 User Interface Design
 Business Process Design
 Workflows and Processors
 Change Request Types
 Data Quality & Business Rules
 Replication

2.3 Data Model and User Interface (UI):

The data model used is the standard SAP MDGF data model, which can be found on the help site. A condensed
version of this content is included below and also contains the standard mapping from MDG to the associated IDoc
used for master data replication.

http://help.sap.com/erp2005_ehp_06/helpdata/en/29/f1c8229b3f45488921a4376a71afd4/content.htm?fra
meset=/en/ad/d9b1d07d1b4aec9fd44020739e776b/frameset.htm

The Data Model Design can be found in the MDGIMG transaction at the following location:

5 of 28
6 of 28
The Configured UI Model can be found in the MDGIMG transaction at the following location:

7 of 28
 2.4 CR Types and Workflow
2.4.1 Finance Objects MDGF Change Request
The Requester Group may receive inputs from a variety of sources, which could lead to the initiation of a change
request (CR) in MDG by a Requester. For each of the objects the change request can cover the creation of a new
object or the modification of the master data of an existing object. The objects covered in this process design are the
following:
 GL Accounts (Chart of Account and Company Code levels)
 Auto Created Primary Cost Elements (from P&L GL Accounts)
 Secondary Cost Elements and the associated Hierarchies
 Cost Centers and their associated hierarchy
 Profit Centers and their associated hierarchy

The workflows and processors for each object are determined by a Change Request Type. The following CR Types
were created for this solution.

8 of 28
The configured CR Types can be found in the MDGIMG transaction at the following location:

Each workflow has a specific number of steps which need to be configured in the following MDGIMG location. One
note about the number of steps is that the design of the workflow determines the number of steps, and this
configuration activity reflects the workflow design.

9 of 28
10 of 28
The next MDGIMG activity is to assign the processors to each of the workflow steps. This is done by CR Type and
step and links the workflow to the User.

11 of 28
12 of 28
The workflow templates used WS75700040 which is one of the standard workflows with MDGF.
The workflow developer transaction SWDD is used to display/configure the various workflows. The workflows used
were a copy of the standard MDGF workflow WS75700040 which was then modified to meet the requirements.

13 of 28
The control of what actions can be performed at each change request step is dictated by the Status at each process
step. The following are the standard delivered SAP Statuses.

Status Status Description Status Meaning of Permission

Code Permissions (Request data can always be changed)
00 To Be Evaluated Change of Object Can change object list, but no changes to
List master data attributes allowed
01 To Be Considered and Approved Change of Object Can change object list, but no changes to
List master data attributes allowed
02 Changes to Be Executed Execution of Can change object list and any master data
Changes attributes
03 To Be Revised Change of Object Can change object list, but no changes to
List master data attributes allowed
04 Final Check to Be Performed No Processing Cannot change object list nor master data
05 Final Check Approved No Processing Cannot change object list nor master data
06 Final Check Rejected No Processing Cannot change object list nor master data
07 Activation Failed No Processing Cannot change object list nor master data
08 Approved, to Be Replicated No Processing Cannot change object list nor master data
09 Dependent Data to Be Execution of Can change object list and any master data
Processed/Approved Changes attributes
10 To Revise: Perform Changes Execution of Can change object list and any master data
Changes attributes
11 Process Errors After Activation Execution of Can change object list and any master data
Changes attributes
12 Approved, Contact Person to Be No Processing Cannot change object list nor master data
Processed
99 No Status Set No Processing Cannot change object list nor master data

In general, the last step of the workflow (i.e. the Approval step) does not allow any changes to be made to the object
list nor the master data attributes. The processors before the final step have access to change both the object list and
the master data attributes.

The MDGIMG location for the configuration activities is shown below.

14 of 28
15 of 28
 2.5 Data Quality Validation and Business Rules
This is where you set up validations to be performed, by entity type, while processing a change request.

From MDGIMG:

16 of 28
After clicking on “Define Validation and Derivation Rules”’, you see:

MDGF Specific Error/Warning Messages

For the Finance objects MDGF has 200+ validation messages that are delivered. By default they all generate an
Error.

In MDGIMG, select “Make Basic Settings for Controlling Validations”:

17 of 28
Navigate to application area “USMDZ3”:

18 of 28
The message is changed to a warning by changing the “E” in the “Standard” column to a “W”.

2.6 Search and Duplicate Check

Duplicate Checking was enabled is based upon the short description.

19 of 28
First the Search Application is defined for all of the data objects.

20 of 28
Lastly each Entity is assigned to its Match Profile and Search Mode (DB).

21 of 28
 2.7 Data Replication
The replication of the approved master data is achieved through IDoc processing from MDG to the target ECC
systems. The steps to configure the replication are provided at the help.sap.com link below.

http://help.sap.com/erp_mdg_addon61/helpdata/en/a6/d5e860201547e1972d745385282d4a/content.htm?frameset=/
en/77/29AD50E6542F3CE10000000A44538D/frameset.htm

Prerequisites:

2.7.1 Set Up RFC Connections

Set up RFC connections in the MDG hub and MDG target systems:
1. Run transaction SM59 (configuration of RFC connections) and provide the required RFC destination details.
2. Define the logical systems in Customizing for SAP Net Weaver. Run transaction SALE and then choose
Basic Settings ->Logical Systems ->Define Logical System. Enter all target systems as logical systems.
3. Run transaction SALE and assign the logical system to a client under Basic Settings ->Logical Systems -
>Assign Logical System to Client.
Procedure
The following steps are required to configure ALE for MDG-F (transaction SALE) in the MDG hub and MDG target
system.
Create a Distribution Model
To create a new distribution model in the MDG hub, carry out the following steps in both systems:
1. Run transaction SALE (Display ALE Customizing) and choose Modeling and Implementing Business
Processes ->Maintain Distribution Model and Distribute Views. Alternatively, run transaction BD64 (Display
Distribution Model).
2. In editing mode, create a new model. Choose Create Model View. Enter a short text and a technical name.
3. Choose Add Message Type for the newly created model. Enter the logical sender system and receiver
system and add a message type from the following table. Repeat this step for all required IDoc message
types. Afterwards, save your entries.

IDoc Message Type Description

GLMAST Master data G/L accounts (Master IDoc)

COSMAS Master cost center

COGRP1 Cost center groups

COELEM Cost element master data

COGRP2 Cost element groups

PRCMAS Profit center master record

COGRP6 Profit center groups

4. After you have saved your settings, you need to generate a partner profile. Choose Environment->Generate
Partner Profiles. Select the model view you just have saved and enter the target system. Select immediate
processing for the output mode and inbound parameter. Choose the pushbutton Execute.
5. After you have generated the necessary partner profile, choose Edit ->Model view ->Distribute to distribute
this model view to your target system.

22 of 28
 6. Enter the target system and repeat step 4 to generate partner profiles on the MDG client.

2.7.2 Define Business Systems

In the client of the MDG hub, a business system for the target client needs to be created as follows:
1. Call transaction MDGIMG.
2. Goto General Settings ->Data Replication ->Define Custom Settings for Data Replication ->Define Technical
Settings ->Define Technical Settings for Business Systems.
3. Choose the pushbutton New Entries.
4. Enter the business system, logical system, and RFC destination for the target client.
5. Mark the line of the newly defined business system and select the folder Define Bus. Systems, Bos. Enter all
desired business object types:

Business Object Type Description

158 Cost Center

229 Profit Center

892 General Ledger Account Master

983 Cost Element

984 Cost Element Group

895 Cost Center Group

896 Profit Center Group

6. Mark each business object type and choose the folder Define Bus. Systems, BOs, Communication Channel.
Choose the pushbutton New Entries and select the communication channel as Replication via IDoc. Repeat
this for all defined business object types.
7. Save your entries.

23 of 28
24 of 28
2.7.3 Create Replication Models
After the distribution model and the business system have been defined in the client of MDG hub, it is now possible to
create a replication model for each IDoc type:
1. Call transaction MDGIMG.
2. Goto General Settings ->Data Replication ->Define Custom Settings for Data Replication ->Define
Replication Models.
3. For each defined replication model, mark the line of the replication model and select the folder Assign
Outbound Implementation. Choose the pushbutton New Entries. Assign the corresponding outbound
implementation to each replication model you have defined:

Outbound Implementation Description

1012 General Ledger Account Master IDoc

1102 Cost Centre IDoc

1112 Cost Centre Group Hierarchy IDoc

1182 Cost Element IDoc

1192 Cost Element Group Hierarchy IDoc

1122 Profit Centre IDoc

1132 Profit Centre Group Hierarchy IDoc

4. Save your entries

5. Activate Replication Model
The configured Out Bound Implementation and Replication Model can be found in the MDGIMG transaction at the
following section:

25 of 28
26 of 28
27 of 28
28 of 28