Sizing MDG Consolidation Business Partner, Version 1
Transcript of Sizing MDG Consolidation Business Partner, Version 1
Sizing Guide
Document Version: 1.0 – 2016-07-12
CUSTOMER
Sizing MDG Consolidation Business Partner, Version 1.0
2
CUSTOMER
© 2016 SAP SE. All rights reserved.
Sizing MDG Consolidation Business Partner, Version 1.0
Disclaimer
Disclaimer
Some components of this product are based on Java™. Any code change in these components may cause
unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these
components.
Sizing MDG Consolidation Business Partner, Version 1.0
Typographic Conventions
CUSTOMER
© 2016 SAP SE. All rights reserved. 3
Typographic Conventions
Type Style Description
Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
Example Emphasized words or expressions.
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when they
are surrounded by body text, for example, SELECT and INCLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as
they appear in the documentation.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system.
EXAMPLE Keys on the keyboard, for example, F2 or ENTER .
4
CUSTOMER
© 2016 SAP SE. All rights reserved.
Sizing MDG Consolidation Business Partner, Version 1.0
Document History
Document History
Version Date Change
1.0 2016-05-11 First Version
1.0 2016-07-12 Correction in chapter 3.3
Sizing MDG Consolidation Business Partner, Version 1.0
Table of Contents
CUSTOMER
© 2016 SAP SE. All rights reserved. 5
Table of Contents
1 Introduction ...............................................................................................................................6 1.1 Functions of SAP Master Data Consolidation ..................................................................................... 6 1.2 Architecture of SAP Master Data Consolidation ................................................................................. 7 1.3 Factors that Influence the Performance .............................................................................................. 8
2 Sizing Fundamentals and Terminology .......................................................................................9
3 Initial Sizing for SAP Master Data Consolidation ....................................................................... 10 3.1 Assumptions ......................................................................................................................................... 11 3.2 Sizing Guideline for SAP Master Data Consolidation ....................................................................... 12 3.3 Guidance for Calculation ..................................................................................................................... 12 3.4 Standardization .................................................................................................................................... 14
3.4.1 CPU and Memory Sizing ..................................................................................................... 14 3.5 Matching ............................................................................................................................................... 15
3.5.1 CPU and Memory Sizing ..................................................................................................... 15 3.6 Best Record Calculation ...................................................................................................................... 17
3.6.1 CPU and Memory Sizing ..................................................................................................... 17 3.7 Validation .............................................................................................................................................. 18
3.7.1 CPU and Memory Sizing ..................................................................................................... 18 3.8 Activation .............................................................................................................................................. 19
3.8.1 CPU and Memory Sizing ..................................................................................................... 19 3.9 Disk Sizing ............................................................................................................................................20 3.10 User Interaction - Additional Sizing Requirements........................................................................... 21 3.11 NW Gateway and Fiori Frontend Server Sizing ................................................................................. 21 3.12 Consolidation of > 10.000K Records ................................................................................................. 21
6
CUSTOMER
© 2016 SAP SE. All rights reserved.
Sizing MDG Consolidation Business Partner, Version 1.0
Introduction
1 Introduction
SAP MDG Consolidation enables you to enrich and standardize your business partner data. The solution helps you
to identify and merge duplicate records to produce the best possible master data records. You can validate and
load consolidated data into any target system. You can also integrate SAP MDG, Consolidation with MDG, Central
Governance.
1.1 Functions of SAP Master Data Consolidation
SAP MDG Consolidation enables you to consolidate your master data using a sequence of process steps adapted
to your requirements. Each individual process step can be configured. You can use SAP MDG Consolidation as a
standalone application or in combination with SAP MDG, central governance.
SAP MDG Consolidation offers the following optional process steps:
1) Standardization: Standardization normalizes and enriches address data. Additionally, a check ensures that
specific addresses actually exists.
2) Matching: Matching checks data from the source systems and the active area for duplicates. Records that are
considered to be duplicates are displayed in match groups. The match review is a part of matching where you
check match groups for possible duplicates.
3) Best Record Calculation: Best record calculation results in a best record containing the cumulated, most
accurate data for each match group as identified by matching. This calculation follows a well-defined process
based on a set of rules.
4) Validation: Validation checks if the quality of a record is sufficient to meet the requirements defined in the back-
end system. If the quality requirements are met data can be saved, if not, corrections and data enrichment may be
required.
5) Activation: Activation adds the records to the system's active area. You can specify how the system proceeds
with different types of records in configuration for SAP MDG, consolidation.
Note
Whether certain process steps are used in your consolidation process and the order of their occurrence is
specified in the configuration of SAP MDG Consolidation. For information on how to configure SAP Master
Data Governance, Consolidation, see Configuring SAP Master Data Governance, Consolidation.
Sizing MDG Consolidation Business Partner, Version 1.0
Introduction
CUSTOMER
© 2016 SAP SE. All rights reserved. 7
1.2 Architecture of SAP Master Data Consolidation
Master Data Consolidation is meant to enable easy import and consolidation data from additional systems that
should be brought under central governance within a central MDG instance. The scope of consolidation for
MDG8.0 is business object Business Partner (including Customer and Vendor Master Data). Consolidation is built
as a multi-domain product.
HANA
Browser
NW AS ABAP
IM in HANA
NW BC
Governance (ABAP WD + Fiori)
ETL
Configuration UI
Design Time API
Model + Config
Runtime
Standard. Match
anyDB
Fuzzy Search
NW 7.40 Basis
IM in HANA Services
Side Effect DataStandard. Matching
MDG_FND
Governance Application
Addr. Enrichment
Cleansing Extensions
Consolidation (Fiori)
MDG_APPL
MDG_UX
MDC (requires SAP_APPL or SCORE)
BAS Interface Adapter
Standard. Matching
BRC
Adapter
BRC
Consolidation Application
BP + Customer Data Model
Source + Best
Process Logic
Suite BP Adapter
Validation Activation
(incl. MDG CR)
UI Backend
(OData)
Process
UI
Review
UIs
IM in HANA Services Adapter
Standard. Matching
Fuzzy
Adapter
Matching
BAS Interface
Standard. Matching
Figure 1: MDG Consolidation for Business Partner, high-level architectural overview
Blue: Existing MDG functions
Pink: Functions provided by IM in HANA
Orange: Existing standardization and matching functions
Green: Scope of release MDG8.0
8
CUSTOMER
© 2016 SAP SE. All rights reserved.
Sizing MDG Consolidation Business Partner, Version 1.0
Introduction
1.3 Factors that Influence the Performance
Besides the common sizing guidance in the following chapters there are further factors that may influence the
overall system performance:
The sizing measurements are based on 10 parallel background work processes. When increasing the number of
available work processes the system might get into locking situations e.g. during the Activation step. As impact,
the throughput could not evolve as expected (no linearity given at a certain point). The break-even point cannot be
clearly defined due to system specific sizing setups and parameters.
It is recommended to set up parallel background processes statically in the system profile. Further it is
recommended to avoid using dynamic background process assignments.
The sizing guidance for the Matching step is based on the assumption of 10% matches. If you expect more than
10% matches the resource consumption may slightly increase.
It is recommended to split the actions activation (the last step in Master Data Consolidation) and replication of
data. Especially when processing high volumes of data, an immediate replication of activated records may
influence the performance and throughput of the processing step activation.
Sizing MDG Consolidation Business Partner, Version 1.0
Sizing Fundamentals and Terminology
CUSTOMER
© 2016 SAP SE. All rights reserved. 9
2 Sizing Fundamentals and Terminology
SAP provides general sizing information on the SAP Service Marketplace. For the purpose of this guide, we
assume that you are familiar with sizing fundamentals. You can find more information at service.sap.com/sizing
→ Sizing Guidelines → Presentations and Articles.
This section explains the most important sizing terms, as these terms are used extensively in this document.
Sizing
Sizing means determining the hardware requirements of an SAP application, such as network bandwidth, physical
memory, CPU processing power, and I/O capacity. The size of the hardware and database is influenced by both
business aspects and technological aspects. This means that the number of users using the various application
components and the data load they put on the server must be taken into account.
Benchmarking
Sizing information can be determined using SAP Standard Application Benchmarks (www.sap.com/benchmark).
Released for technology partners, benchmarks provide basic sizing recommendations to customers by placing a
substantial load upon a system during the testing of new hardware, system software components, and relational
database management systems (RDBMS). All performance data relevant to the system, user, and business
applications are monitored during a benchmark run and can be used to compare platforms.
SAPS
The SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes the
performance of a system configuration in the SAP environment. It is derived from the Sales and Distribution (SD)
Benchmark, where 100 SAPS is defined as the computing power to handle 2,000 fully business processed order
line items per hour. (For more information about SAPS, see www.sap.com/benchmark → Measuring in SAPS).
Initial Sizing
Initial sizing refers to the sizing approach that provides statements about platform-independent requirements of
the hardware resources necessary for representative, standard delivery SAP applications. The initial sizing
guidelines assume optimal system parameter settings, standard business scenarios, and so on.
Expert Sizing
This term refers to a sizing exercise where customer-specific data is being analyzed and used to put more detail
on the sizing result. The main objective is to determine the resource consumption of customized content and
applications (not SAP standard delivery) by comprehensive measurements. More information can be found here.
Configuration and System Landscaping
Hardware resource and optimal system configuration greatly depend on the requirements of the customer-
specific project. This includes the implementation of distribution, security, and high availability solutions by
different approaches using various third-party tools. In the case of high availability through redundant resources,
for example, the final resource requirements must be adjusted accordingly.
There are “best practices” which may be valid for a specific combination of operating system and database. To
provide guidance, SAP created NetWeaver configuration guides (service.sap.com/instguides → SAP NetWeaver).
10
CUSTOMER
© 2016 SAP SE. All rights reserved.
Sizing MDG Consolidation Business Partner, Version 1.0
Initial Sizing for SAP Master Data Consolidation
3 Initial Sizing for SAP Master Data Consolidation
The hardware requirements are derived from resource consumption measurements in internal SAP systems
using an SAP-specific configuration and data set. The sizing guide was created measuring all five process steps of
a theoretical master data consolidation for business partners.
The steps contain one to three different adapters which the customer can choose for execution. Each adapter was
measured separately. For providing a t-shirt sizing small to extra-large processes were used. The range is
between 10,000 records in a process up to 10,000,000 records.
The consolidation steps/adapters generate load on both the ABAP server and on the SAP HANA server side. Both
requirements are listed separately. By executing consolidation, adapters load is generated for the triggering user
as well as for the background users.
SAP HANA database sizing is calculated using the required SAP HANA server memory and based on the list of
certified SAP HANA hardware.
Sizing MDG Consolidation Business Partner, Version 1.0
Initial Sizing for SAP Master Data Consolidation
CUSTOMER
© 2016 SAP SE. All rights reserved. 11
3.1 Assumptions
The sizing was done with 10 dialog processes in parallel. The configuration of package sizes can be found in the
configuration guide of Master Data Consolidation for Business Partner.
Note
It is not recommended to use less than 10 dialog processes in order to guarantee a high-performing
processing.
Running consolidation processes or steps in parallel requires you to sum up the individual sizing requirements,
When using non-concurring processes, the requirement of the highest consumption should be taken.
Initial consolidation process runs often require a high number of SAPS and memory due to the targeted data load.
Consolidation runs during normal business may require less hardware consumption.
Example
A customer introduces SAP Master Data Consolidation. For a first consolidation of records the customer
requires hardware to consolidate 3.000.000 records. After this initial consolidation the customer plans to
consolidate 10.000 records per month. An initial sizing based on 3.000.000 records would create
unnecessary TCO at usual business consolidation runs of 10.000 records. Discuss a possible situation
with your hardware partner for an appropriate solution and system sizing.
The Matching in Master Data Consolidation was done based on the assumption of 10% matches for the total
number of records/measurement.
For scenarios which are executed by concurrent users, the SAPS for ABAP server, Frontend Server, and SAP
HANA database are calculated with a guarantee factor of 65%, which means that there is 35% extra capacity
planned to handle peaks and to try to ensure no degradation of response time due to CPU queuing effects.
This factor/buffer is usually not used for background jobs, In Master Data Consolidation most load is caused by
background jobs and it is recommended to use the factor here as well - especially when you plan to increase the
number of work processes beyond 10.
The ABAP server initialization memory for buffers, caches etc. is considered with an offset of 4 GB and meets the
recommendations for minimum ABAP server memory. The ABAP Memory [GB] in this sizing guideline is the gross
memory including the offset.
In addition to the data tables loaded by the SAP HANA database into main memory the SAP HANA database has
to allocate additional main memory at runtime of an application for monitoring, statistical data, SQL script
execution, and materialization of data. This memory offset is defined at 40GB.
12
CUSTOMER
© 2016 SAP SE. All rights reserved.
Sizing MDG Consolidation Business Partner, Version 1.0
Initial Sizing for SAP Master Data Consolidation
3.2 Sizing Guideline for SAP Master Data Consolidation
The application SAP Master Data Consolidation consists of several steps and step-dependent adapters.
Depending on which steps are chosen to be part of customer's consolidation process, different step adapters
need to be selected that are processing the step jobs.
Typically, the Master Data Consolidation is distributed over five steps: Standardization, Matching, Best Record
Calculation, Validation, and Activation of consolidated records.
For the steps Standardization, Matching, and Best Record Calculation there are different adapters available such
as BAS Interface, IM in HANA, or Fuzzy Matching.
The sizing requirement are calculated based on the chosen steps and adapter combinations.
Single sizing requirements for concurrent steps need to be summed up in order to get the total sizing requirement
for your customer installation.
Example
A customer decides to run a consolidation of 150.000 records split in 6 processes due to country
dependencies. One process containing 100K records and 5 processes containing 10K records.
If all processes need to run in parallel, the sizing requirements of each need to be summed up.
When the 100K process should be finished first and then the 5 10K processes should run, the highest
resource consumer determines the final sizing setup.
If all processes run non-concurrently, aspects of TCO versus throughput should be taken into
consideration.
3.3 Guidance for Calculation
Master Data Consolidation for business partner records consists of several steps that determine the total sizing
requirements for your system.
1) Specify the typical scenarios for an initial master data consolidation and for usual consolidation business cases
that occur on a recurring timeframe. Determine the sizes (# of records) and the used steps and the chosen step
adapters.
2) Calculate the application server and SAP HANA database server requirements for the specified processes for
each step. Take the highest consumer for application server and database server within one process.
2.1) Sum up the requirements of all possible concurrent processes.
3) Calculate the disk requirement for the database and add the resource consumption to your SAP HANA server
calculation.
4) Calculate the application server requirements for user interactions and add them to the application server
requirements (step 2).
5) Calculate the gateway server requirements independently.
Sizing MDG Consolidation Business Partner, Version 1.0
Initial Sizing for SAP Master Data Consolidation
CUSTOMER
© 2016 SAP SE. All rights reserved. 13
Table 1: Example of a sizing calculation
Example Calculation for 5.000.000 Records
Conditions # of processes 1 # of records 5.000.000
# of steps 5 Size of 1 record 17,1 kB
# of users 100 # of user actions/h 100
# of dialog processes 10
Step Calculation
Application Server SAP HANA Server
CPU [SAPS] MEMORY [GB] MEMORY [GB]
Standardization
IM in HANA
500 10 100
Matching
IM in HANA
150 8 55
Best Record
Validation
7.500 6.5 56
Validation 50.000 19 n/a
Activation 50.000 54 n/a
Step Calculation for highest consumer
Application Server SAP HANA Server
CPU MEMORY MEMORY
50.000 SAPS 54 GB 100 GB
Disk Size Calculation HANA Server
Initial Load 5 Process Steps Memory Offset MEMORY
85.5 GB 427,5 40 GB
Total 555 GB
Application Server Calculation
Application Server
CPU MEMORY
2.000 SAPS 4 GB
Total Calculation for Application Server and HANA Database
Application Server SAP HANA Server
CPU MEMORY MEMORY
52.000 SAPS 58 GB 655 GB
14
CUSTOMER
© 2016 SAP SE. All rights reserved.
Sizing MDG Consolidation Business Partner, Version 1.0
Initial Sizing for SAP Master Data Consolidation
3.4 Standardization
The SAP Master Data Consolidation process step Standardization provides two different adapters customer can
choose for processing: BAS Interface and IM in HANA. Choose an adapter, determine the process size, and
concurrent process executions. Sum up the requirements of each (parallel) execution to determine the maximum
CPU and memory requirement for this step.
Example
If you have non-concurrent executions such as 50.000 records to be consolidated in week 1 and 20.000
records in week 2, then the maximum requirement should be taken.
3.4.1 CPU and Memory Sizing
Table 1
Records per Process Standardization - BAS Interface
ABAP Server SAP HANA Server
CPU in [SAPS] Memory in [GB] Memory in [GB]
Small (0–10.000 records) 10 4 4
Medium (>100.000 records) More - it is recommended to use IM in HANA.
Note
The CPU resource requirements for higher throughput can be calculated applying a linear extrapolation.
Memory consumption on SAP HANA is plus 0.2 GB per 10.000 records. Memory consumption on ABAP is
plus 0.3 GB per 100.000 records.
Table 2
Records per Process Standardization - IM in HANA
ABAP Server SAP HANA Server
CPU in [SAPS] Memory in [GB] Memory in [GB]
Small (0–10.000 records) 10 4 4
Medium (10K–100K records) 10 4 5.5
Large (100K–1.000K records) 100 5 19
X-Large (>1.000K records) More - please see recommendation.
Recommendation
Up to 10.000.000 records a SAP HANA database with at least 1TB of memory is recommended.
Sizing MDG Consolidation Business Partner, Version 1.0
Initial Sizing for SAP Master Data Consolidation
CUSTOMER
© 2016 SAP SE. All rights reserved. 15
3.5 Matching
SAP Master Data Consolidation process step Matching provides three different adapters customer can choose
for processing - BAS Interface, IM in HANA, and HANA Fuzzy. Choose an adapter, determine the process size and
number of parallel executions. Sum up the requirements of each (parallel) execution to determine the maximum
CPU and memory requirement for this step. At non-concurrent execution plans, the highest requirement wins.
3.5.1 CPU and Memory Sizing
Table 1
Records per Process Matching - BAS Interface
ABAP Server SAP HANA Server
CPU in [SAPS] Memory in [GB] Memory in [GB]
Small (0–10.000 records) 5 4 4
Medium (>10.000 records) More - it is recommended to use IM in HANA or Fuzzy Matching.
Note
The CPU resource requirements for higher throughput can be calculated applying a linear extrapolation.
Memory consumption on SAP HANA is plus 0.15 GB per 10.000 records. Memory consumption on ABAP
is plus 0.3 GB per 100.000 records.
Table 2
Records per Process Matching - IM in HANA
ABAP SAP HANA Server
CPU in [SAPS] Memory in [GB] Memory in [GB]
Small (0–10.000 records) 5 4 4
Medium (10K–100K records) 10 4 4.5
Large (100K–1.000K records) 30 4.5 11
X-Large (>1.000K records) More - please see recommendation.
16
CUSTOMER
© 2016 SAP SE. All rights reserved.
Sizing MDG Consolidation Business Partner, Version 1.0
Initial Sizing for SAP Master Data Consolidation
Table 3
Records per Process Matching - HANA Fuzzy
ABAP SAP HANA Server
CPU in [SAPS] Memory in [GB] Memory in [GB]
Small (0–10.000 records) 20 4 4.6
Medium (10K–100K records) 50 4 5.2
Large (100K–1.000K records) 500 4.3 12.5
X-Large (>1.000K records) More - please see recommendation.
Note
Memory consumption is calculated with a plus of 4GB buffer offset
Recommendation
Up to 10.000.000 records a SAP HANA database with at least 1TB of memory is recommended.
Sizing MDG Consolidation Business Partner, Version 1.0
Initial Sizing for SAP Master Data Consolidation
CUSTOMER
© 2016 SAP SE. All rights reserved. 17
3.6 Best Record Calculation
SAP Master Data Consolidation process step Best Record Calculation provides by default one adapter to
calculate the best records. Determine the process size and number of parallel executions. Sum up the
requirements of each (parallel) execution to determine the maximum CPU and memory requirement for this step.
At non-concurrent execution plans, the highest requirement wins.
3.6.1 CPU and Memory Sizing
Table 1
Records per Process Best Record Calculation for Business Partner
ABAP SAP HANA Server
CPU in [SAPS] Memory in [GB] Memory in [GB]
Small (0–10.000 records) 10 4 4
Medium (10K–100K records) 100 4 4.5
Large (100K–1.000K records) 1.500 4.3 11.2
X-Large (>1.000K records) More - please see recommendation.
Note
Memory consumption is calculated with a plus of 4GB buffer offset.
18
CUSTOMER
© 2016 SAP SE. All rights reserved.
Sizing MDG Consolidation Business Partner, Version 1.0
Initial Sizing for SAP Master Data Consolidation
3.7 Validation
SAP Master Data Consolidation process step Validation provides by default one adapter to validate business
partner records. Determine the process size and number of parallel executions. Sum up the requirements of each
(parallel) execution to determine the maximum CPU and memory requirement for this step. At non-concurrent
execution plans, the highest requirement wins.
3.7.1 CPU and Memory Sizing
Table 1
Records per Process Validation for Business Partner
ABAP SAP HANA Server
CPU in [SAPS] Memory in [GB] Memory in [GB]
Small (0–10.000 records) 200 4 n/a
Medium (10K–100K records) 2.000 4 n/a
Large (100K–1.000K records) 14.000 4.5 n/a
X-Large (>1.000K records) More - contact SAP or hardware vendor
Note
CPU resource requirements for 10.000K records can be calculated with approx. 50.000SAPS by a given
server CPU power of 2.200SAPS per single CPU or better. The memory consumption raises by additional
5GB for 10.000K records.
Recommendation
When validating more than 10.000.000 records it is recommended to use high performing CPUs that
operate on 2.200 SAPS per single CPU or better.
It is further recommended to split consolidation processes that exceed 10.000.000 records into several
packages and runs.
Sizing MDG Consolidation Business Partner, Version 1.0
Initial Sizing for SAP Master Data Consolidation
CUSTOMER
© 2016 SAP SE. All rights reserved. 19
3.8 Activation
SAP Master Data Consolidation process step Activation provides by default one adapter to activate business
partner records. Determine the process size and number of parallel executions. Sum up the requirements of each
(parallel) execution to determine the maximum CPU and memory requirement for this step. At non-concurrent
execution plans, the highest requirement wins.
3.8.1 CPU and Memory Sizing
Table 1
Records per Process Activation for Business Partner
ABAP SAP HANA Server
CPU in [SAPS] Memory in [GB] Memory in [GB]
Small (0–10.000 records) 1.100 4.2 n/a
Medium (10K–100K records) 11.000 4.8 n/a
Large (100K–1.000K records) 22.000 7 n/a
X-Large (>1.000K records) More - contact SAP or hardware vendor
Note
CPU resource requirements for 10.000K records can be calculated with approx. 50.000SAPS by a given
server CPU power of 2.200SAPS per single CPU or better. The memory consumption raises by additional
7GB for 10.000K records.
Recommendation
When validating more than 10.000.000 records it is recommended to use high performing CPUs that
operate on 2.200 SAPS per single CPU or better.
It is further recommended to split consolidation processes that exceed 10.000.000 records into several
packages and runs.
20
CUSTOMER
© 2016 SAP SE. All rights reserved.
Sizing MDG Consolidation Business Partner, Version 1.0
Initial Sizing for SAP Master Data Consolidation
3.9 Disk Sizing
The required disk/memory size on the SAP HANA database depends on the amount of business partner master
data records that need to be loaded and consolidated. To calculate the required space for SAP Master Data
Consolidation for Business Partner specify the amount of data to be loaded and the average size of a record, or
the total size of all loaded records.
1) Data to be consolidated is stored in source tables. The size of the source tables is nearly equal to the size of the
data you have loaded for consolidation, Depending on the option when creating a consolidation process, you can
keep or delete the source data after the process is finished. This option shall be taken into account by calculation.
2) The internal process tables keep the original records in their current state (delta) for each step. So multiply
your initially calculated size for the number of chosen process steps. Add this requirement to the first one.
3) The activation of a consolidation process requires the initially calculated size of the loaded data less the size
saved by successful matches. If you plan having more than 20%, a recalculation might be useful, otherwise use
the delta as buffer offset.
4) Lastly there is a buffer offset for Master Data Consolidation-specific internal processing tables which can be
specified at 2GB in total.
The size requirements of step 2) and 4) are required for a running process. Once a process is finished they can be
subtracted from the calculation of total disk size growth.
Example
A customer plans an initial consolidation of 5.000.000 records. The source records are loaded from different
systems into a SAP Master Data Consolidation system. Each record requires 17.1 kB (source: Master Data
Governance Sizing Guide) which is a total requirement of 85.5 GB for the complete set.
A consolidation process with Standardization, Matching, Best Record Calculation, Validation, and Activation is set
up. The disk requirement is as following:
1) 85.5 GB for loading into source tables. The source table is deleted afterwards.
2) Initial calculation multiplied by the number of process steps from Standardization to Validation: 342 GB.
3) Activation with anticipated 5% matches (approx. minus 4GB not taken into consideration) is calculated with
85.5 GB.
4) Buffer offset of 40GB valid for all processes and counted once.
5) Buffer offset for Master Data Consolidation specific tables with 2GB.
In this example, the peak disk space requirement for consolidating 5.000.000 business partners would be 555
GB.
When the process is finished 342 GB from internal process tables are freed again. When the source data will be
deleted from consolidation system by checking that option at process start, an additional 85.5 GB are freed and
only the consolidated and activated data remains in the system for replication.
Note
Again, an initial sizing may not meet your requirements for daily business. Specify both, initial and usual business
requirements, and discuss possible hardware options with your hardware vendor.
Sizing MDG Consolidation Business Partner, Version 1.0
Initial Sizing for SAP Master Data Consolidation
CUSTOMER
© 2016 SAP SE. All rights reserved. 21
3.10 User Interaction - Additional Sizing Requirements
SAP Master Data Consolidation is very economical in terms of user interaction hardware requirements. A full t-
shirt sizing would not be appropriate here, therefore a high load scenario is taken for your reference. Let's assume
that 100 business users accept or reject each 100 match groups in one hour. The business case would require an
additional application server capacity of 2000 SAPS (at 65% load) and a maximum of 4 GB memory. The network
traffic would be 16.6 kB/sec which meets a bandwidth of 1.3 Mbit.
Creating, saving or deleting processes do not cause a significant resource consumption in combination with the
total sizing. The same is valid for configuring or changing configurations and adapters.
Note
CPU and memory resource requirements for higher throughput can be calculated applying a linear
extrapolation. It is not recommended to undercut the recommendations described above.
3.11 NW Gateway and Fiori Frontend Server Sizing
The low resource consumption on user interaction level is reflected on the frontend server sizing, too. It is
recommended to provide 1.3 times of resource capacity compared to the application server but not lower than
3000SAPS and 6 GB of memory for the given example of 100 users with total 10.000 actions/h. The network
traffic for the gateway server must be handled in this example with a bandwidth of 13 Mbit.
Note
CPU and memory resource requirements for higher throughput can be calculated applying a linear
extrapolation. It is not recommended to undercut the recommendations described above.
3.12 Consolidation of > 10.000K Records
When you plan an initial consolidation of more than 10.000.000 records it is recommended to split the
consolidation processes into several pieces of 10.000.000 due to TCO reasons.
Example
You plan to consolidate 45.000.000 records. Split the consolidation into 5 processes with 9.000.000
records each. You can choose any size smaller than 10.000K records per package. Run the processes
sequentially.
www.sap.com/contactsap
© 2016 SAP SE. 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.
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.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered
trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System ads, 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, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,
ByDesign, SAP Business ByDesign, and other SAP products and
services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE in Germany and in
several other countries all over the world. 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 SE 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.