PUBLIC

How-To: Extend MDG for FI Contract Account by

a New Field

Applicable Releases:
From MDG 9.1 SP01 and S/4HANA 1709

Version 2.0
October 2022
Document History

Document Version Description

1.0 First official release of this guide (November 2017)

1.1 Layout update (November 2019)
2.0 Layout update (October 2022)
1. BUSINESS SCENARIO ............................................................................................................................................................. 4
2. STEP BY STEP EXPLANATION FIELD EXTENSION WITH NEW FIELD ......................................................................................... 5
2.1. CREATE NEW FIELD IN CI INCLUDE .......................................................................................................................................... 5
2.2. EXTEND MDG DATA MODEL ................................................................................................................................................ 5
2.3. GENERATE STRUCTURES ....................................................................................................................................................... 6
2.4. CREATE FIELD MAPPING ...................................................................................................................................................... 7
2.5. ADD NEW FIELD TO UI ........................................................................................................................................................ 9
2.6. CHECK FOR MANDATORY FIELDS WITH BRF+ .......................................................................................................................... 10
3. ADDITIONAL INFORMATION ............................................................................................................................................... 16
3.1. FURTHER READING ........................................................................................................................................................... 16
3.2. SAP NOTES .................................................................................................................................................................... 16

3
1. BUSINESS SCENARIO
SAP Master Data Governance provides business processes to find, create, change, and mark master data for deletion.
It supports the governance of master data in a central hub and the distribution to connected operational and business
intelligence systems.

The processes are workflow-driven and can include several approval and revision phases, and the collaboration of all
users participating in the master data maintenance.

This How To Guide describes the solution to enhance MDG FI Contract Account with new fields.

4
2. STEP BY STEP EXPLANATION FIELD EXTENSION WITH NEW FIELD
The following explanation shows you how to include a custom field into MDG.

2.1. Create New Field in CI Include

The following CI includes can be enhanced with a new field:
- CI_FKKVK of table FKKVK (*)
- CI_FKKVKP of table FKKVKP
- CI_FKKVKP2 of table FKKVKP
- CI_FKKVKP_SP1 of table FKKVKP
- CI_FKKVKP_FIS of table FKKVKP
- CI_FKKVKP_UK of table FKKVKP
*If you want to enhance the CI_FKKVK include for table FKKVK, first read SAP Note 2859822.

Run transaction SE11, and enter table FKKVK or FKKVKP. Double-click the CI include you want to extend. If the CI
include was not enhanced before, choose “Yes” in the dialog box to create the structure. Enter a description, and add
the new field. Save and activate your changes.

2.2. Extend MDG Data Model

Run transaction MDGIMG, and select the activity “Edit Data Model” under Master Data Governance, Central Governance
 General Settings  Data Modeling.

Select data model “BP”, and double-click the “Entity Types” sub-node in the dialog structure. Depending on the table in
which you enhanced the CI include, select either entity type “FKKVK” or “FKKVKP”. Double-click “Attributes” in the dialog
structure. Choose the “New Entries” button to create a new entry.
To add your attribute, enter “ZZ“ followed by the technical name of the data element, e.g., “ZZDOKAR”. Save your
changes.

Double-click the “Entity Types” sub-node. Choose “Activate”. Choose “Adjust Staging Area of linked Change Requests”,
and select “Yes” in the dialog box.

5
2.3. Generate Structures
Run transaction MDGIMG, and select the activity “Generate Data Model-Specific Structures” under Master Data
Governance, Central Governance  General Settings  Data Modeling.

Select data model “BP”, and double-click the “Structures” sub-node in the dialog structure. Depending on the table you
enhanced in step 1, select all “FKKVK” or “FKKVKP” entity types. Choose the “Generate Selected Structures” button.

6
2.4. Create Field Mapping
Run transaction MDGIMG, and select the activity “Extend Mappings” under Master Data Governance, Central
Governance  General Settings  Data Modeling.

Choose “Mapping”  “Open”.

7
Enter “MDG_FICA_2API”, and choose “OK”.
In the table, select the mapping step “FKKVK” or “FKKVKP”, and choose “Details”.

Open the “Transformations” tab, and choose “Edit”. Choose “Add” to create a new transformation. This will add a new
row to the table. Select “Field Mapping” as the Transformation Type.

8
Expand both trees in the target structure table and in the source structure table. In the target structure, select the field
you created in the CI include (step 1). In the source structure, select the field you created in the data model (step 2).
Choose “Map”. This will add a new row to the table “Field Mapping”.

Choose “Save”.

Choose “Mapping”  “Open”. Enter “MDG_FICA_2STA”, and choose “OK”.

Select the mapping step “FKKVK” or “FKKVKP”, and choose “Details”.
Open the “Transformations” tab, and choose “Edit”. Choose “Add” to create a new transformation. This will add a new
row to the table. Select “Field Mapping” as the Transformation Type.
Expand both trees in the target structure table and in the source structure table. In the target structure, select the field
you created in the data model (step 2). In the source structure, select the field you created in the CI include (step 1).
Choose “Map”. This will add a new row to the table “Field Mapping”.
Choose “Save”.

2.5. Add New Field to UI

Run transaction NWBC, and select “SAP_MDGFICA_MENU”. Select “Search Contract Account”. Choose “Search”.
Select one of the contract accounts.

If you added the new field to the table FKKVK, you could enhance the account header area of the contract account.
If you added the new field to the table FKKVKP, you could enhance the following areas of the Business Partner UI:
Account Management, Payments, Taxes, and Dunning/Correspondence. Choose “Details” to open the business partner
data (if you created a new contract account, choose “New”).
Determine the area where you want to place your new field.

Use SE80 and open package MDG_ECC_FICA_BOLUI MDG_FICA_OVP. Select the FPM Application Configuration
MDG_OVP_FICA and Start Configurator and choose Display. Click on the Configuration MDG_FICA_OVP.

9
Select the UIBB, which you want to enhance.
Choose “Additional Functions”  “Create Customizing” in the header menu.

Enter a description. Select a transport. Choose the “Repositories” button in the header menu to display all repository
objects in a split view.

Add the new field, which is displayed in the view on the left, to the UI using drag and drop. In the “Attribute” area, select
“Drop-Down List Box” as the display type. In the “Action Assignment” Area select “FPM_REFRESH (Refresh)” as “FPM
Event ID for on Select”.
Choose “Save”.
Close all UI configuration windows, and close the business partner UI. Re-open the contract account, and choose
“Details” in the business partner area to verify that the new field was correctly added to the UI

2.6. Check for Mandatory Fields with BRF+

You can add a check on field level to make sure that the fields contain values. This check turns regular fields into
mandatory fields. To add a check for mandatory fields, do the following (the field “Business Area” is used as an example):

Run transaction MDGIMG. Select the activity “Define Validations and Derivation Rules” under General Settings  Data
Quality Search  Validations and Enrichments.

10
Enter Data Model “BP”, and choose “Continue”. Open the “Catalog” tab, and expand the “Trigger Function” node. Right-
click the “Check Entity” node to open the context menu. Select “Create Object Node”  “Create Function”.

11
In the “Name” field, enter “CHECK_FKKVKP”. Note that the name must adhere to the naming convention
CHECK_<entity>. Since the field “Business Area” belongs to the entity “FKKVK”, the name of the Business Area is
“CHECK_FKKVKP”. The connection of the field to an entity is defined in the data model (see chapter Field Extension
with New Field, step 2).

In both the “Short Text” and the “Text” field, enter “CHECK_*”. Substitute “*” for the entity to which the field belongs, e.g.,
“CHECK_FKKVKP”. Choose “Create and Navigate To Object”. In the dialog box, choose “OK”.

Choose “Edit”, and choose “Add Existing Data Object”. Enter the name of the of the field’s entity for which you want to
create a new check. For example, enter “FKKVKP” for the search criterion “Name”. Choose “Search”, and select the
relevant entity.

Choose “OK”. Open the “Assigned Rulesets” tab, and choose “Create Ruleset”. In both the “Name” and “Text” field, enter
“BUSINESS_AREA_RULESET”. In the “Short Text” field, enter “BUSINESS_AREA_RULE”.

12
Choose “Create And Navigate To Object”. In the dialog box, choose “Yes”. In the “Rules” area, select “Insert Rule” 
“Create”.

Enter a description for the rule, and select “Assign Condition”  “Use Value Range From…”  ”Context” ”More…”.
Select the field for which you want to create a check.

13
In the drop-down menu next to the field name, select “is initial”. For “Then”, select “Add”  “Perform Action”  “Create…”.

Select “Log Message (Action)” as “Type”. Enter a name for the object, e.g., “MSG_BUSINESS_AREA”, as well as a short
text and text. Choose “Create And Navigate To Object”.

14
Enter a meaningful message text, e.g., “Enter a value for Business Area”, and choose “Type” “Error”. Choose “Save” and
“Activate” in the header area to activate the error message.
Choose “Back” to navigate to the rules again. Choose “Save” and “Activate” again to activate the rules.
Choose “Back” to navigate to the function again. Choose “Save” and “Activate” again to activate the function.

15
3. ADDITIONAL INFORMATION
3.1. Further Reading
Information on SAP MDG on SAP S/4HANA
• Exchange knowledge: SAP Community | Q&A | Blog
• Try SAP Master Data Governance on S/4HANA for free: Trial Version
• Learn more: Latest Release | Webinars | Help Portal | How-to Information | Key Presentations

SAP Roadmap Explorer

• Please see the roadmap for SAP Master Data Governance

Related Information
• Learn more: Floorplan Manager for Web Dynpro ABAP | How to Adapt FPM | FPM Blog | How-to Information |
Service Mapping Tool | SAP S/4HANA Cookbook CVI |

3.2. SAP Notes

In addition to the detailed explanations written in this document, please see the following SAP Notes for further
important information.

Note Number Note Description

Functional restrictions in MDG for Business Partner / Customer / Supplier with SAP
2313368
Master Data Governance 9.0
Functional restrictions in MDG for Business Partner / Customer / Supplier with SAP
2472845
Master Data Governance 9.1
Functional restrictions in MDG for Business Partner / Customer / Supplier in SAP Master
2656712
Data Governance 9.2 and on SAP S/4HANA 1809
Functional restrictions in MDG for Business Partner / Customer / Supplier on SAP
2816557
S/4HANA 1909
Functional restrictions in MDG for Business Partner / Customer / Supplier on SAP
2925030 S/4HANA 2020
Functional restrictions in MDG for Business Partner / Customer / Supplier on SAP
3070003 S/4HANA 2021
3194967 MDG Customer Connection 2021 for S/4HANA 2022
3043582 MDG Customer Connection 2020

16
www.sap.com/contactsap

© 2022 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National
product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein.
This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may
be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on
these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/trademark for additional trademark information and notices.