master data governance 6.1 for material_ performance tweaks

8/11/2019 Master Data Governance 6.1 for Material_ Performance Tweaks

http://slidepdf.com/reader/full/master-data-governance-61-for-material-performance-tweaks 1/23

Master Data Governance 6.1 for Material:

Performance Tweaks



www sap com

TABLE OF CONTENTS

APPLIES TO ..................................................................................................................................................... 3

SUMMARY ........................................................................................................................................................ 3

MOTIVATION .................................................................................................................................................... 4

HARDWARE REQUIREMENTS AND SYSTEM PERFORMANCE ................................................................. 5

REFERENCE SYSTEM ..................................................................................................................................... 5

APPLICATION CONFIGURATION AND UIBBS .............................................................................................. 7

STATE OF BUILDING BLOCKS AND LAZY LOAD ........................................................................................ 9

DIRECT CALL OF OVP .................................................................................................................................. 11

IGNORE WIRING ............................................................................................................................................ 11

Prerequisite .................................................................................................................................................... 11

Change Application Configuration .............................................................................................................. 12

Copy Component Configuration of Wiring UIBB ....................................................................................... 12

Change Configuration of MDG Material Layout ......................................................................................... 13

CBA Adjustments .......................................................................................................................................... 15

Delete Personalization .................................................................................................................................. 17

CUSTOM UIBBS ............................................................................................................................................. 19

CUSTOM CODE .............................................................................................................................................. 19

UI PRICE TAGS .............................................................................................................................................. 19

PERFORMANCE NOTES ............................................................................................................................... 20

UPGRADE TO MDG 7.0 ................................................................................................................................. 20

RUNNING AN EHP6 UI IN AN MDG 6.1 SYSTEM ........................................................................................ 20

RELATED CONTENT ..................................................................................................................................... 22



Master Data Governance 6.1 for Material: Performance Tweaks

APPLIES TO

Master Data Governance for Material Master Data (MDGM) – MDG6.1 for SAP ERP 6.0.

SUMMARY

This document outlines several performance tweaks you can use to accelerate the startup of theMDG Create or Change Material scenarios. As the measurements are taken from a dedicated andunique test environment figures may not be transferable to 1 to 1 to your system.

Author: Jan PoeschelCompany: SAPVersion: 1.23History: Minor wording changes (version 1.23)

Added CBA adjustments for chapter IGNORE WIRING (version 1.22)Minor text adjustments (version 1.21)




MOTIVATION

Master Data Governance for Material master data enables customers to create, change, or deletesmaster data records and put them under governance. For a controlled roll-out of material data inand across enterprises a governance model is needed to guarantee that the correct data is put inthe right place. In this context, the governance of material usage in processes is as important for

master data as governance targeted to avoid duplicate or incorrect material records.Displaying major parts of the material master data requires more system resources than a simplereport or transaction. Therefore we assume, in terms of performance, the major point of interest forcustomer is the runtime consumption until the material master data is completely shown andeditable on screen. In our case, this means the time it takes the Material Overview Page (OVP) tofully load.Taking this point into consideration, measurements were taken on SAP performance systems andanalyses were made regarding the application scaling and how much resources a single stepconsumes. Besides the official sizing guide for customer system landscapes, this guide focuses onthe MDGM application and how it can be accelerated. The findings are based on the “CreateMaterial” scenario but can also be applied to the “Change Material” scenario. Change Materialconsumes a similar but lesser amount of system resources and should be less critical.

Because Create/Change Material is not a sub-second application displaying the material masterdata, the development group identified some best practices for tweaking the application on thecustomer side. Note that SAP delivers a nearly complete material master data model and based onthat all possible UI building blocks. Customers adjust the standard application configurationstailoring them to their current business needs.




HARDWARE REQUIREMENTS AND SYSTEM PERFORMANCE

Before tweaking the Create or Change Material application in your system, please follow the SizingGuide for MDG Material. It provides guidelines for the hardware required to run a Materialgovernance scenario. For example: if you have less than 10 active users running 200 processesan hour, you require approximately 5GB of Memory for this scenario. Whereas, if you have more

than 10 users creating 750 processes an hour you require about 9GB of memory.You can find the Sizing Guide here: www.service.sap.com/sizing

REFERENCE SYSTEM

Once you setup your system, you should check how the application scales on it. This guideprovides you some reference figures supporting you in the early stages to find the correcthardware setup. When you don't meet the following reference figures, please adjust your systemlandscape before continuing, otherwise you won’t reach the ideal and targeted performance. The reference system is based on a SUN operating system with 4 virtual Intel E7- 4807 CPUs(each 1.8GHZ) and a physical memory size of 32 GB. Ideally, the system should not be underload, to prevent inaccuracy in measuring.

As mentioned before, the following tweaks focus on starting the material overview page. Usuallyyou start the initial page of Create/Change Material where you select a material ID and a changerequest type. We skip this step as it is not performance critical and directly start the materialmaster. Therefore, create a shortcut/favorite in your SAP Menu for the following application:Web Dynpro Application: MDG_BS_MAT_OVP Application Configuration: BS_MAT_OVP_03Parameters: ACTION=CREATE, USMD_CREQ_TYPE=MAT01

Figure: SAP Menu Favorite

We use the pre-delivered SAP application and configuration, which consists of the maximum offields covering the complete model. There are no tweaks so far. This enables us to compareclosely to the standard runtimes.

http://www.service.sap.com/sizing







Note: For this and all further comparisons, follow the common guidelines for measuringperformance. This means, check the system is ready for measurements, there should be noimports, not much user traffic, high system load, or any jobs scheduled. You can check

common parts using transaction Z_MEC. Note that this transaction may not be present in allreleases. For preparation, create runs in advance to fill buffers and avoid generating ofprograms or sub-routines (For example, after imports).

When single measurements of your complete measurement series differ in more than 15%your system is too unstable for further measurements. You should continue analyzing thereasons for this.

Measurements taken with transaction SAT do not consider the network traffic and bowserrendering time. Please be aware that all following reference figures take these two optionsinto account. They were recorded using the SUPA tool.

First comparison point: the application startup should not take longer than 7 seconds if you have asimilar or better system setup than the reference system.When you reach the range of 7 seconds, please retrieve the statistical record for one of themeasurements using transaction STAD. Here examine the following figures:

Response Time: Is the total response time without network and rendering efforts

CPU Time: Should be the biggest block in terms of response time

DB req. Time: MDG-M has a very healthy relation to database runtime. The value here

should be 10% and less in relation to the given CPU time. The DB time can be up to 20%

the better the total CPU runtime develops

Overhead: The waiting time and roll processes are defined here as “overhead”. You can

calculate them by subtracting CPU and DB time from Response Time. The proportion

should be 5 to 10% maximum.




When you not meet these figures, the starting point of your analysis is the STAD result. Here youcan easily see what direction your investigation may take. Is the DB time too high or too unsteady? Are your CPU capacities too low? Watch out for “extreme” deviations. One exception is when youget response times much lower than 7 seconds, the single relations behave different. For example,having a sub 6 seconds run, the CPU scales at 80% and the DB time at 17%.You also gain higher response times when you have enhanced the underlying data model MM withyour own entities. The values here base on the standard data model of MDG6.1 and therefore werecommend checking your application before any enhancement. When you already enhanced themodel MM, you can try to interpolate your figures using the scalability report of the MDG-MPerformance Guide for release MDG7.0.

Figure: STAD record taken as example

Please note that a STAD record often consists of more than one entry, as the application and/or

backend triggers round trips. When you refresh your application using F5 you can find out therange of the statistical record sets. You will need to sum up the figures.

Note: MDG Material scales very well with available CPU power. This means that not only do freeprocesses positively influence the response time but also the single CPU core power. In ourreference measurements a slightly higher core frequency (1.8 to 2.1 GHZ) and a moreavailable cores decrease the response time.

APPLICATION CONFIGURATION AND UIBBS

Once your system is setup and the application scales similarly to the reference measurement you

can continue focusing on the application configuration. As mentioned before, SAP delivers themaximum configuration covering all data model entities. However, not all scenarios require allmaterial master data.The customer should define possible scenarios for the involved roles and business users. The pre-delivered roles have broad access to master data. It is possible for the customer to narrow access(and modify the UI accordingly) to just the required information for a given business role. These“focused roles” would mean that UI building blocks not required for a given role are not renderedand therefore not taking up system resources. Please see below the available building blocks andhow they may scale. All UIBBs are collapsed and lazy load is set to “enabled”:




UI Building Block Comment

(Initial Load)

Change Request

Material Basic Data

Nearly half of the total runtime is consumed by initial load, changerequest, and basic data. This cannot be cut.

Plants The second largest block is represented by the material plant level – 12UIBBs in total.

Distribution Chain The distribution chain is spread over 6 UIBBs and consumes the thirdlargest block of total runtime.

Dimensions, InternalComment, Basic Text

This level contains three building blocks consisting of 7 UIBBs in totaland has medium impact on runtime.

Valuation The valuation level is spread over 4 UIBBs and has medium impact onruntime.

GTIN, Descriptions Those are represented by 2 UIBBs and have minimal impact on runtime.

Quality Inspection Can be neglected in terms of runtime.

MARA Sales, MARAPurchasing

Those are represented by 2 UIBBs and have minimal impact on runtime.

Classification Can be neglected in terms of runtime.

Table: UI Building Block Runtime Consumption

The initial load of the material master with the required UIBBs for change request and materialbasic data consumes approximately half of your total runtime. This part cannot be cut. You can try

to accelerate this part by upgrading your hardware in terms of operating power.The following blocks are from interest. Even if you decide not to remove complete blocks but onlyseveral UIBBs out of them you may gain a noticeable improvement in your total runtime. Analyzethe need of the mentioned topic blocks, or even of parts of the blocks, and remove unused objectsto improve runtime.

Note: In the floorplan manager (FPM) you can easily take the SAP standard configurationBS_MAT_OVP as template for your own configurations when you use the deep-copyfunction. Make sure to have the configurations copied for OVP, CBA and Layout. Afterwards,remove unused UIBBs and assigned wiring information.




STATE OF BUILDING BLOCKS AND LAZY LOAD

Our reference measurement refers to the maximum configuration with all UIBBs collapsed andlazy-load active. SAP delivers the standard configuration with this setup; see the correspondingWDP configuration MDG_BS_MAT_OVP_03 as an example. Even if the maximum configuration isavailable, the state and the lazy-load prevent the system from loading the complete UIBBs. They

are only fully loaded when expanded.This setup initially saves a lot of runtime. Therefore, please decide which UIBBs are importantenough to be loaded in advance. Every UIBB that is collapsed can save a certain amount ofruntime. In general the following rules apply for UIBBs:

When the UIBB is not assigned to the configuration, the corresponding feeder is not called

When the UIBB is assigned but collapsed, the feeder creates an instance for a later use

When the UIBB is expanded, the feeder runs and the UIBB takes part at the FPM phase

model. Time consuming sub-routines as GET_DATA or FLUSH are processed. The

maximum possible runtime for an initial load is consumed

Note: Changing the state of the UIBBs from “expanded” to “collapsed” not only saves runtime butalso up to one third (and more) of application server CPU time for a medium or full-blownstandard UI.

HIERARCHICAL UIBesides the standard flat layout which SAP delivers there is a second configuration availablecontaining the same UIBBs but ordered in a hierarchical way. Its Web Dynpro configuration (WDC)ID is MDG_BS_MAT_OVP_03H. The configuration is used by default in the Change Material

scenario and shows only the most common UIBBs on the first screen. Further UIBBs and detailsare accessible using the “Details” button. Thus, the runtime taken up displaying of UIBBs can befurther reduced to only what is required.If this kind of layout suits your needs, you can also use it for the Create Material Scenario. Thehierarchical UI can save additional runtime and resources compared to the process oriented (flat)UI. It furthermore saves up to 12 MB of memory consumption – per user process and startup.Database accesses and traffic and also rendering time are not influenced in a recognizable way.

Note: You can deep-copy the standard hierarchical configuration MDG_BS_MAT_OVP_03H andadjust it further to your needs. Removing unused UIBBs and setting the state to “collapsed”with “lazy load” may multiply the amount of saved runtime. This differs from case to case. Bysimply using the proposed layout you may already save additional runtime and +10MB of

memory per process.

GOVERNANCE SCOPEIn MDG6.1 you can define a “Governance Scope”. Using a governance scope, entities and fieldscan be put under governance. If entities are not governed their fields are disabled on the UI and inthe staging area. SAP delivers a special BC set which reduces the scope from MDG 6.1 to EhP6for model MM. When doing please verify that the used UI configuration shows the EhP6 layout aswell. Otherwise you may lose performance advantages here.

Note: Using the Governance Scope for single entities does not have a large impact on

performance. Reducing the scope in a dimension like the EhP6 scope may save 4 MB ofmemory.




MEMORY CONSUMPTION

Memory consumption depends highly on the configuration you have chosen and the states of thesingle UIBBs. Beginning at the smallest possible configuration, the minimum memory consumptionis 50 MB for one single process. Here only the UIBBs “Change Request” and “Basic Data” arepresent on the screen – it doesn’t matter if they are expanded or collapsed.If you use the full standard UI configuration, 128 MB of memory are consumed per start-up. If youcollapse all UIBBs (except the Change Request UIBB) you can save up to 40 MB per start-up.The following chart shows how much memory consumption you may save at start-up

… when using collapsed UIBBs as default

… when removing un-used UIBBs

The levels describe the existence of several logical blocks on the UI. The difference to the previouslevel describes the consumption of a logical block – such as 8 MB for Valuation UIBBs in theexpanded state.

Basic: All Level 9: Removed Valuation UIBBs

Level 8: Removed Plants UIBBs

Level 7: Removed Distribution Chain UIBBs

Level 6: Removed Quality Inspection

Level 5: Removed MARA Sales and Purchasing

Level 2: Change Request and Material Basic Data only

Figure: Memory Consumption expanded vs. collapsed

Note: Removing un-used UIBBs saves you up to 32 MB of memory consumption as in the casefor all Plant UIBBs. Using the UIBB state “collapsed” instead of “expanded” saves youadditional memory. Multiply the saved amount of memory per process with your users andprocesses to adjust your original sizing plans and achieve a lower-cost environment. Thesefigures highly depend on the model you are using – here the standard SAP delivered

data model at MDG 6.1 release without any further enhancements is assumed.




DIRECT CALL OF OVP

In some business cases it may be useful to start the Material Governance from the Initial Screenas proposed in the pre-delivered PFCG roles. In the Initial Screen you can select materialtemplates, determine the change request type, or preselect organization level values.The change request process usually starts on an initial screen with a certain change request typeselected (see chapter “Configuration and UIBB”) When there is no need for template data and thematerial number shall be retrieved internally then you can start the change request process directlywithout processing the Initial Screen. This saves you time getting directly to the master data.

Figure: Parameters of Application MDG_BS_MAT_OVP

To do this, create a reference in your userroles and add the material master datagovernance (see also our performanceexample):

WD Application: MDG_BS_MAT_OVP

WD Configuration: BS_MAT_OVP_03(or customer-specific)

Parameters:* ACTION,USMD_CREQ_TYPE

IGNORE WIRING

The Floorplan Manager framework, which is the basis of the MDG Material user interface, offersthe ability to suppress the processing of UIBB wirings when those UIBBs are collapsed. So whenthe parameter is set, the UIBB’s wiring is only processed when expanded. Activating this optionsaves valuable CPU and memory resources by ignoring collapsed (and thus unused) UIBBs andsignificantly speeds up the MDG Material start-up. For more information on wiring, please see thecorresponding documentation in the SAP Help Portal.

This function is part of the SAP standard delivery at MDG7.0 SP1 and higher releases. For existingMDG6.1 installations manual effort is required as customers copy and modify the SAP deliveredstandard configuration and adjust them to their needs. (See also SAP Note 1943327).

The example is based on the standard SAP delivered configuration for MDG Material without anycustom enhancements. The example describes how to change the UIBB wiring of the SAPstandard configuration. If a customer uses another wiring source UIBB other than the standard one(“Basic Data”) then the steps need to be done comparable. You can identify the wire source UIBBbased on the used connector class: /PLMU/CL_FRW_W_CONN_URL.

Prerequisite

Assure that SAP Note 1943327 or Service Pack 7 or higher of MDG6.1 is installed on your system.The SAP Note adds the required FPM parameter FPM_IGNORE_WIRE_SOURCE to the standard

WebDynpro application MDG_BS_MAT_OVP. This is required for activating the function in themost convenient and minimally invasive way.

http://help.sap.com/saphelp_nw70ehp3/helpdata/en/DB/4E8F9861FB43D7BD07B768810CEC98/content.htm







To assure the parameter is correctly inserted into your system check the WebDynpro applicationparameters of MDG_BS_MAT_OVP (For example, using Repository Browser SE80). As thefollowing screenshot shows, the parameter FPM_IGNORE_WIRE_SOURCE should be availableand set to <blank>.

Figure: MDG_BS_MAT_OVP application parameters

Activating this option requires minor adjustments in the UI logic in order to assure a continuoususer experience. Please also install SAP Note 1944691 or Service Pack 8 or higher of MDG6.1.

Change Application Configuration

After installing the required SAP Note access your custom application configuration in changemode and search for the application parameter FPM_IGNORE_WIRE_SOURCE. Activate it byentering value “X” and save the configuration.

Figure: Application configuration parameters

Copy Component Configuration of Wiring UIBB

The example is based on the copy of the standard MDGM component configuration of Material“Basic Data”. This step is always required as long as customer hasn’t implemented another wiringsource UIBB. In this case do the steps in a similar manner.

Copy the SAP standard component configuration MDG_BS_MAT_MATERIAL_FORM_03 forMaterial “Basic Data” into a custom namespace.




Figure: Component Configuration MDG_BS_MAT_MATERIAL_FORM_03

Change Configuration of MDG Material Layout

Access your custom component configuration that is a deep-copy of the delivered SAPconfiguration BS_MAT_OVP_LAYOUT_03 in change mode. In the tab “Overview Page Schema”access the section that contains the UIBB which the wire source – in our example this is sectionMAT_SECTION for MDG_BS_MAT_MATERIAL_FORM_03 and component FPM_FORM_UIBB_GL2. Insert the recently copied component configuration and copy all attributes from thesource/original UIBB to the copy.

Figure: Overview Page Schema

After, access tab “Toolbar Schema” and replicate all toolbar elements according to the copied

UIBB.

Figure: Toolbar Schema




These steps were taken because this instruction intends to set the original UIBB to be a“technical/hidden UIBB” assur ing that “Basic Data” wiring runs even if all UIBBs are collapsed. Theoriginal UIBB is hidden (set to “technical”) and the copy is the replacement. This way is chosen asit creates the least adjustment efforts.

Now the source/original UIBB is prepared for being technical. Access it and change the followingtwo attributes:

Attribute Value

Hidden Element Hidden but Processed in Event Loop (Technical)”

Rendering Type Without Panel

Figure: Set UIBB to technical UIBB

Save the changes.

The final step to activate the wiring of the technical UIBB is done in the tab “Wire Schema”.Choose “Add Wiring” and add the following wiring from source to copied UIBB. The attributes forBasic Data are:

Attribute Value

Component FPM_FORM_UIBB_GL2Configuration Name <copied configuration ID>

Source Component FPM_FORM_UIBB_GL2

Source Configuration Name MDG_BS_MAT_MATERIAL_FORM_03

Port Type Lead Selection

Port Identifier MARA

Connector Class /PLMU/CL_FRW_W_CONN_DEFAULT

Filter Mode Do not filter (default)




Figure: Create Wire Schema

In order to avoid a possible double-tagging access the UIBB which is set to value “technical”,select field MATNR and remove the check flag in attribute “Tag by Feeder class”. If this option isstill checked, the attached Side Panel won’t show any data due to a double tagging of the originaland the copied UIBB.

Figure: Delete double tagging at field material

Save the changes made.CBA Adjustments

The Material Delete case (mark for deletion) requires an adjustment at the context-basedadaptions (CBA) functionality to guarantee an errorless processing. If you do not require the mark-for-deletion functionality or use it very seldom, you may think about still using your un-optimizedconfiguration for this single case. You can adjust your PFCG role accordingly.

Access your custom OVP configuration component, go to section “MAT_SECTION” on the tab“Overview Page Schema” and access your recently created copy of Material Basic Data (FormUIBB) with the wrench option “Configure UIBB”. Activate the “Adaption & Comparison” view. If thiswas successful it should look like the following screenshot:




Figure: Adaption View

Mark line type “Basic Configuration” and press button “Add”. Uncheck option “Applies to all values”for section “Log. Action” and insert logical action DELETE. Press OK to confirm the changes.

Figure: Adaption for logical action Delete

Repeat this step: Mark type “Basic Configuration” again and add an adaption for section “Type ofChg. Request” with value MAT0B.

As CBA settings are/cannot be copied when copying UIBBs, compare your copy with the SAPstandard UIBB and enhance or delete where necessary. Therefore select the adaptions made,compare the element list and attributes for their completeness and similarity of your copy and theSAP standard UIBB.




Figure: Adaption element list and element attributes

For a better understanding of the comparison and adjustment steps, let’s take the assumption thatan unmodified SAP delivered Form UIBB was copied. Then the following steps would be required.For adaption “DELETE” this may mean that all groups but “General Data” need to be deleted fromthe element list. Within the group further superfluous elements would need to be deleted and a“Marked for Delete” element would need to be added. The second adaption “MAT0B” may requireadding elements for “Marked for Deletion” and/or a re-arrangement of elements order.

Note: If deleting a material is a little used business case, you may think about still using thestandard UI configuration for in order to avoid CBA changes at your main configuration.

Delete Personalization

Now it is important to delete all user personalization in system that refers to the processedconfiguration. Otherwise this will lead to heavy inconsistencies. You can do this using the WDapplication WD_ANALYZE_CONFIG_USER. Start the application and insert the configurationname you are changing (the custom copy of SAP standard configurationMDG_BS_MAT_OVP_03). Mark and delete all entries appearing, as shown in the figure below.

Figure: Delete personalization

Accessing the MDG Material overview page will now not lead to errors. For a quick cross checkyou may rename the Basic Data UIBB in the step before to “Basic Data <with random text>” to seethat your copied UIBB is displayed and the original is hidden and used as technical UIBB.




Figure: MDG Create Material copied UIBB

The Starting the material maintenance should now be significantly faster than before. You cancompare the runtime with transaction STAD.

Figure: Statistical record

Note: Activating this function saves you a significant part of CPU runtime and memoryconsumption for all collapsed UIBBs. Open UIBBs are fully processed and do not benefit fromthe function. Please be aware that the resources are consumed once you open a collapsedUIBB during runtime. The advantage is that only used UIBBs are processed and consumesystem resources.




CUSTOM UIBBS

Most often the standard material master data model is enhanced with customer specific fields.Besides the model extension, UI configurations and programming are needed to bring the fieldsonto the screen. Different UI controls consume a different amount of system resources. Note thatSAP created a buffering note especially for customers that heavily extended the standard model in

order to reduce the runtime consumption. Check that SAP Note 1756538 is applied to your systemif you are below MDG6.1 SP03.

CUSTOM CODE

There are several points for customers to extend the existing code base. Follow the standard ABAP programming guidelines and maintain a strong focus on performance-efficient programming.You can find more information here: www.service.sap.com/performance When creating your own UIBB feeder or when using the cross-entity BADI in MDG make sure toaccess any data model related data using the Convenience API (Provided by MDG AF). Note thatdirect accesses are not buffered.In your feeder implementations you should raise an FPM event only one time for each round-trip (if

possible) in order to avoid processing the event several times. Check the FPM event queue (asdescribed below).Within your service provider implementation buffer results from triggered FPM actions.When you trigger a round-trip not intending to re-load UIBB data, you have the option to skip thedata retrieval. Use the parameter SKIP_RETRIEVE of method BEFORE_GET_DATA for this.

UI PRICE TAGS

Here some “UI Pricing Trends” that may support your decision when designing your own UIBBs.Each UI element is measured here with reference to the consumed Browser CPU Time(Rendering). The following values are taken on a dedicated test environment – nevertheless youcan use them to get a feeling what certain elements may cost and how they scale on a clientbrowser.

The runtime consumption is described here as very low and low (< 1 ms) and high (up to 35 ms).

UI Element RuntimeConsumption

Used Browser

Button Very low Inter Explorer 8 and 9

Input Field Very low Inter Explorer 9

Drop Down by Key Low Inter Explorer 9

Panel Low Inter Explorer 9

Group Low Inter Explorer 9

Tab per Tabstrip Low Firefox 10

Calendar Medium Inter Explorer 9

ALV High Inter Explorer 8Table High Inter Explorer 9

Table: UI Elements and their Price Tags (Source: SAP Central Performance Team)

The following browsers were in focus:

Firefox 3.6, 4.0 and 10.0.1

Internet Explorer 7, 8 and 9.

Generally speaking, the browser scales and performs better with the latest release. You should getthe lowest client CPU consumption (and the best performance) with Internet Explorer 9.

http://www.service.sap.com/performance







PERFORMANCE NOTES

In order to assure having applied all released performance SAP Notes, please update to the latestrelease available. If you cannot upgrade to at least SP7 check that the following SAP Notes areapplied.

SAP Note Description1793913 Buffering of Metadata

1756538 Performance: Slow startup of OVP

1919860 Performance: Buffer for maintenance status

1928760 The "hidden"-property indic. has to be inactive by default

1929051 Performance improvement when reading the model details

1934475 Performance improvement of the methodget_mapping_of_rmapped_enties(cl_mdg_bs_mat_smt)

1935141 MDG Material UI Performance: Field Properties

1935698 Performance improvement for methods

GET_NODE_MFIELDS_FOR_ENTY and GET_MFIELDS_FOR_NODE(creation of a buffer)

1940444 Performance: Use parameter FPM_IGNORE_WIRE_SOURCETable: MDG 6.1 Performance Notes until SP7

UPGRADE TO MDG 7.0

The question may occur if it is better to upgrade to the next higher release for performancereasons, in this case MDG7.0. The next release offers you a slightly larger data model coveringmore material master data entities such as Document Management System (DMS) integration.These enhancements may require slightly more system resources when you use them all inparallel. See the corresponding information in the available sizing guide.

Compared to MDG 6.1 release MDG7.0 runs faster. During MDG7.0 development there weremany performance improvements which could not all be down-ported to 6.1 or require manualadjustments such as the “ignore-wiring” parameter.Installing MDG7.0 SP1 and higher assures you to benefit automatically from all performanceimprovements and provides you a fast MDG Material release including the bonus of additionalfunctions.

RUNNING AN EHP6 UI IN AN MDG 6.1 SYSTEM

Customers may also upgrade their MDG installation to MDG 6.1 and continue using the EHP6model scope and UI. Here it is of interest how the EHP6 configuration behaves in the environmentof a massively extended MDG 6.1 system.

During performance testing the EhP6 configuration and the governance scope functionality wereused to reduce the UI to an EhP6 scope. The measurement was taken for the step from InitialScreen to the Create Material overview page. An upgrade to MDG 6.1 on the test system costs an EhP6 configuration user less than 0.3seconds of additional total runtime. The memory consumption rises by 15MB per user andprocess. The CPU consumption remains stable or decreases slightly. The results are valid for thestep from Initial Screen to the Overview screen.

Note: Using the EhP6 configuration and UI in an MDG 6.1 upgraded system consumes (at thesame hardware) a small amount of total runtime more and causes a slight plus of 15MB of

used memory – per process and user for the mentioned step. This plus on system resourcesmay be absorbed by tweaking your application according to this guide.




Please be aware that the figures above are taken from a test environment and cannotbe used 1:1 for comparisons outside of it. They should serve as trend or outlook forwhat may happen for an upgrade on an optimized system.




RELATED CONTENT

Master Data Governance for Material - OverviewMaster Data Governance in SDNMaster Data Governance Sizing Hints ABAP Performance Guide

MDGM UI ExtensionMDGM Model ExtensionMDGM New Entity Types

http://scn.sap.com/docs/DOC-15084

http://scn.sap.com/community/mdm/master-data-governance











http://scn.sap.com/community/mdm/master-data-governance




www sap com

© 2013 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

BusinessObjects Explorer, StreamWork, SAP HANA, 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 Business Objects Software Ltd. Business Objects is an SAP

company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL

Anywhere, and other Sybase products and services mentioned herein

as well as their respective logos are trademarks or registered

trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are

registered trademarks of Crossgate AG in Germany and other

countries. Crossgate is an SAP company.

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 AG 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.

master data governance 6.1 for material_ performance tweaks

Documents