SAP S/4 HANA Master Data Governance
CUSTOMER
2022-12
MDG, DATA QUALITY MANAGEMENT
AUTOMATED CREATION OF CUSTOMER DATA FOR BUSINESS PARTNERS
WITH DERIVATION SCENARIOS
Applies to SAP CAL Solution S/4 HANA OP 2021 FPS01 release and above
TABLE OF CONTENTS
Background information ........................................................................................................ 3
Demo Script ............................................................................................................................. 3
1.1
1.2
1.3
1.4
Accessing the SAP Fiori Launchpad................................................................................. 3
Explore an existing derivation scenario for business partner data .............................. 5
Create a new derivation rule for dunning data ............................................................... 10
Use the derivation scenario in a consolidation or mass process ............................... 21
2
Background information
With SAP MDG on SAP S/4HANA 2021 FPS1, the functionality of defining derivations for business
partners and products has been delivered.
Features in a nutshell:
➢ Derivation rules are introduced to derive the value(s) of single or multiple fields. This
includes the ability to mark the derived value as a default value. Derivation rules can also
create and update dependent entities (for example, create a storage location if a plant is
created).
➢ Derivation scenarios are provided to combine derivation rules into executable and
manageable units. This facilitates lifecycle management, configuration, and data
maintenance by business users.
➢ Derivation scenarios can then be used in mass processing and consolidation, for example to
automate the extension of materials to plants or to create customer data for a business
partner.
This demo script will show you how to create a new derivation rule in an existing derivation
scenario. In a derivation scenario that is set up to derive customer data and company code data
from general business partner data, you will create a rule that derives dunning data.
Once the derivation scenario is enhanced, you can apply it in a consolidation process or a mass
process.
Further information on derivation scenarios can be found here.
Demo Script
1.1 Accessing the SAP Fiori Launchpad
Explanation
Screenshot
Logon to the CAL
S/4HANA system using the
information below:
• Client: 100
• User: MDG_EXPERT
• Password: Welcome1
3
Explanation
Screenshot
Double-click the URL for
the SAP Fiori Launchpad in
the menu.
The system will start a
browser with the URL of
the SAP Fiori Launchpad.
Then log on once more
with the information
provided above.
The system will take you to
the SAP Fiori Launchpad.
If required, scroll to the title
Data Quality Management
for Business Partners to
access the tiles for the
functions of this demo
script.
4
1.2 Explore an existing derivation scenario for business partner data
Explanation
Screenshot
Click on the tile Define
Derivation Scenarios
Business Partners in the
group Data Quality
Management for Business
Partners.
Search for derivation
scenario
‘BP_CUSTOMER_DATA’
and click on it.
5
Explanation
Screenshot
Check the details in the
general information tab to
understand the purpose of
the derivation scenario.
Select the section
Derivation Rules to see
which rules have been
defined already.
All these rules are enabled
for execution. If they are
applied, some general
business partner data will
be changed by rule
BUT000_CHANGE. With
rule BUT100_NEW the
customer role will be
assigned to the business
partners in scope of the
scenario. Etc.
The sequence number
defines the sequence of
execution. This means rule
KNA1_NEW can rely on
data created with rule
BUT100_NEW.
The result table is the table
where the data is created
or changed. Click on the
Button “Show More per
6
Explanation
Screenshot
Row” to view the result
table.
Click on one of the
derivation rules to see its
details.
With the rule KNA1_NEW
you create new entries in
the result table Customer
General (KNA1).
The rule should be
executed for all data in the
scope of the scenario.
Thus, the scope
expression of the rule can
be left initial.
7
Explanation
Screenshot
Click on the Fields section
to check the condition and
result fields of the rule.
These fields are used to
generate decision tables,
which can be accessed in
the Implementation
section. In this example,
the values for the account
group KTOKD and the
authorization group
BEGRU shall depend on
the business partner
grouping BU_GROUP.
By clicking on a decision
table, you navigate to the
BRFplus Workbench. Here,
you can maintain the
values for the derivation
rules.
Click on ? to get assistance
on the topic of derivation
scenarios.
Thus, you get explanations
for some of the UI
elements.
8
Explanation
Screenshot
And you get quick access
to detailed topics on
help.sap.com.
9
Explanation
Screenshot
1.3 Create a new derivation rule for dunning data
Explanation
Screenshot
In this example we create a
derivation rule that is used
to create new dunning data
for the previously created
company code data
(created with rule
KNB1_BY_KNA1). The
dunning data shall depend
on the company code.
Click on the Edit action on
the derivation scenarios’
object page.
Remark: If you want to
delete an existing rule, the
rule status needs to be
changed to Disabled. Then
the Delete action is
available.
10
Explanation
Screenshot
As we want to create new
data, we use a derivation
rule for tables.
Click on the Create action
in the section for Derivation
Rules for Tables.
Enter a rule ID and a rule
name.
Select the rule base table
Company Code
(Customer), and the result
table Dunning (Customer)
You can add further details
as shown on the
screenshot. They are not
mandatory.
11
Explanation
Screenshot
To add condition fields,
click on Add above the
Condition Fields table.
12
The derived values shall
depend on the company
code. Thus, search for the
company code field and
select it.
In the Result Fields table,
the key fields Company
Code and Dunning Area for
the dunning data were
added automatically.
To add result fields, click
on the Add button above
the result fields table.
Search for the Dunning
Procedure (MAHNA) and
select it.
13
Save the rule by clicking
first on Apply then on
Save.
14
To start the process of
implementation, change
the status of the rule:
Select the new rule, click
on Set Status and select
To Be Implemented.
Note: This action is only
available in display mode.
Navigate to the rule's
details. In the
Implementation section,
click on Create Decision
Table. With this action, the
BRFplus decision tables
will be generated in the
background.
15
While the generation is
running you cannot edit the
derivation scenario. Once
the generation is finished,
you can access the
generated decision tables
by clicking on them.
In case the generation
keeps running for a long
time, you can use the
actions Show Generation
Status and Show
Application Log to analyze
the issue. With Cancel
Generation you can stop
the process.
Click on the link for the
condition decision table.
You navigate to the
BRFplus Workbench.
16
Click on Edit.
To insert a new row, click
on +.
Use the Direct Value Input
option to maintain the
value ‘0001’ for the
Company Code.
17
For the Condition Group
maintain the value
SAP_AG via Direct Value
Input. This is a freely
defined text and will be
reused in the result
decision table.
Maintain an additional row
for all company code
values that are not equal to
0001. Use NOT_SAP_AG
as Condition Group value.
Click on Save and navigate
back to the derivation
scenario by clicking on < in
the header bar.
The Condition Decision
Table status has changed
to Inactive Changes.
Click on the result decision
table to maintain the values
in the BRFplus Workbench.
18
Proceed as for the
condition decision table.
For the Condition Decision
Table (decision group) use
the values you defined in
the condition decision
table.
Enter value 0001 for the
dunning procedure and
select space as the default
dunning area.
For the Company Code
use the value from the rule
base table KNB1.
Choose Select Context
Parameter and search for
the company code in the
context.
Select the company code
from KNB1.
19
Add a second line that
defines the behavior for
company codes that are
not equal to 0001.
Choose Save and navigate
back to the derivation
scenario.
Now both decision tables
are in status Inactive
Changes.
They will be activated with
the approval of the
derivation rule.
Details see here.
Select the rule and set the
status to To be Reviewed.
Then, set the status to To
be Approved.
Then, set the status to
Approved.
Now the decision tables
are in status Active.
20
If you want to enable the
rule for execution, switch
on the Execution switch.
Now, with the next
execution of the derivation
scenario, dunning data will
be created.
1.4 Use the derivation scenario in a consolidation or mass process
To apply the derivation scenario, you need a consolidation or mass process that has a derivation
step. There are preconfigured templates which include such a step.
Demo script Apply validation rules and derivations in consolidation of Business Partner data,
describes how to apply the derivation scenario in a consolidation process. In that script, the
business partners will be created within the script.
If you already have business partners in the system and want to execute a derivation scenario
within a mass process, follow the steps described below.
Explanation
Screenshot
Prerequisite: Business
partners that fulfill the
scope condition search
term 1 starts with
MARKETING are available.
If no suitable business
partners exist, create them,
for example with the app
Manage Business Partners
in Business Partner
Master.
21
Explanation
Screenshot
Navigate to Master Data –
Business Partner/Mass
Processing and click on tile
Manage Mass Processes
Business Partners.
Click on Create Process to
create a new process with
template SAP: Change BP
Data with Derivation. Click
on Save.
Maintain at least one Field
in Scope and click on
Continue.
22
Explanation
Screenshot
Select business partners
that fulfill the scope
condition of the derivation
scenario (Search Term 1
starts with Marketing).
Click Start.
In this example, 5 records
are selected. Click on
Continue to execute the
next step, which is the
derivation step
23
Explanation
Screenshot
You see the result of the
derivation step.
Dunning Data were newly
created (5 Inserted Rows).
As the other customer data
existed already you see
only unchanged rows.
If you want to activate the
data process to the next
steps with Continue.
24
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 platforms, 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/copyright for additional trademark information and notices.