MDM 5.5: Performance problems while loading repositories solved through SP5 & Technical Changes Steffen Ulme

MDM 5.5: Performance problems while loading repositories solved through SP5 & Technical Changes
Steffen Ulme

In this blog I will document the performance improvements which we made at a MDM-project with a very large repository. Maybe you have also problems with your repository (MDM 5.5 < SP5) regarding:
- Loading the repository,
- Adding/ Deleting fields via the SAP MDM Console,
- Modifying record values via the Portal Busienss Package.

If you have these problems, switching to MDM5.5 SP5 can solve these difficulties.

Let me describe our system landscape:
We used MDM5.5 SP4 with a very large repository (~200 tables, many taxonomy records). We had bad response times within the Portal UI as well as it took very long to add or delete fields within the SAP Console. The mayor problem was that it took around 3 hours to load the repository after it was stopped. This handicaped the project team very much, because during the loading of the repository nobody was able to work with it.

Solution description
To enhance the performance we implemented the following tasks:
1. Upgrade to MDM 5.5 SP5: We decided to upgrade to MDM5.5 SP5. Together with the upgrade we made the following

2. Landscape changes:
- we devided the Portal and the MDM Server into two machines, and
- we installed a new database on the local MDM-server.
Further we checked the repository modelling and changed the follwoing technical settings in the repsoitory in order to enhance the performance:

3. Keywords: Set the property "Keyword" for all repository fields to "None" if there is no need to set it to "Normal".

4. Sort Index Exists: Change "Sort Index Exists" for all fields from "Normal" to "None", excepts the fields which should be sorted via the result set in the Data Manager (e.g.: Name, Description, ID). The sort index enables the sorting of the data in the named column in the Data Manager

5. Display fields: Reduce the number of display fields within the repository. Reduce the number in all tables! (also in lookup, qualified tables as well as the main table)

6. Delete unused tables and fields: Check your repository if there are unused tables or not used fields. You should delete these fields and tables.

As a summary these are the reasons for the huge performance improvements:
- Upgarde to MDM 5.5 SP5,
- extra hardware (previously MDM was installed with Portal on one Box),
- newly installed Database SW => repository was newly unarchived => no fragments
- Technical Changes in the repository.


I hope that these experience will help you in your project if you have the described performance problems.

Steffen Ulmer

Steffen Ulmer is a SAP NetWeaver Technology Consultant.

A General Idea on SAP Master Data Management By Ron Victo

Working across Sap heterogeneous forums systems at multiple places, SAP Master Data Management leverages accessible IT assets in business-critical data, delivering greatly reduced data repairs charges and very useful for sap business jobs. Moreover, by ensuring cross-system data consistency, SAP Master Data Management speed ups the implementation of business processes for jobs. SAP MDM is a key enabler of SAP Enterprise Service-Oriented Architecture forums.

SAP is at present on its second iteration of MDM software. Facing restricted acceptance of its primary release, SAP changed path and in 2004 purchased a small vendor in the PIM space known as A2i. This code has happen to the basis for the presently shipping SAP MDM 5.5, and for itself, most analysts believe SAP MDM to be more of a PIM than a broad MDM product at this time.

The components & tools of SAP NetWeaver master data management integrates business courses across the comprehensive value chain, delivering features and functions to help: Master data consolidation, Synchronization and distribution of master data , Centralized management of master data, Administration of master data, Management of internal content, Catalog search, Print catalog customization , Multichannel syndication of product catalog content, Business process support and Business analytics and reporting.

There are five normal execution scenarios:

Content Consolidation, Central Master Data Management, Master Data Harmonization, Rich Product Content and Global Data Synchronization With the SAP (MDM), you can:

1. Control customer relationships efficiently through streamlined visibility across various systems 2. Simply allocate master data to assigned systems through automated distribute and subscribe models 3. Lessen the number of part masters maintained worldwide by removing duplicates 4. Analyze and statement on spending by part, supplier, or other master data 5. Negotiate superior sourcing contracts based on analytical insights 6. Lessen supply chain charges by ensuring exact exchange of data involving manufacturers and dispensers or dealers. SAP Master Data Management is the basis for harmonized, reliable information that can be offered to client applications across the enterprise. It offers you a great way to attain information steadiness across your business or jobs and IT landscape. It enables improved decision-making, translating chance charges into gains, and reducing the charge of IT maintenance. SAP Master Data Management allows you to go with information across myriad applications and topographies -- whether that details resides in SAP, non-SAP, or legacy applications. Therefore, you can lessen costs, develop decision-making, and attain business goals on jobs. The sap news says that SAP (MDM) increases the sap jobs search and by training this sap certified course education module, it supports and gives more vacancies for permanent sap jobs for all developers or trainers worldwide.

Ron Victor is a SEO copywriter for SAP jobs
He written many articles in various topics like SAP news,SAP Forums,SAP Articles.For more information visit sap employment
Contact him at ron.seocopywriter@gmail.com.

Article Source: http://EzineArticles.com/?expert=Ron_Victor

MDM - Road Ahead Ketan Phanse

MDM - Road Ahead
Ketan Phanse

The road ahead for MDM seems bright and shiny... atleast as per a recent survey published by MDM Institute!http://www.tcdii.com/0809milestonesonmdmroadmap.html

So as SAP MDM continues to be rated as one of the most valued SAP skills, MDM's market would continue to mature and grow in 2008-09. What does that mean for all of us?

• As more verticals/industries would move into MDM we will see more niche master data objects being mastered. Some of them can be Patients for Healthcare, Well for Oil & Gas, MRO for Manufacturing, Fixed Assets for Service industry etc. This would mean that the limited repositories provided by SAP would not be sufficient. More functional knowledge and expertise would be required to model such niche repositories.
• One of the strong business case for MDM is M&A and in 2007-08 we saw lot of M&A within the MDM space itself! The SAP-BO, Microsoft-Siperian, Oracle-Cognos etc would enhance the functionalities of these core MDM products. This means a fast continuous skills upgrade for us and to keep pace with the technology. It started with SAP ERP, then to BI, SRM and now Business Objects. To learn all these new technologies as they begin to integrate with SAP MDM would be a task we all need to be upto for.
• As mentioned in the roadmap, throughout 2009-10, skill shortages will greatly inflame project costs as demand for data stewards, enterprise data architects, & individuals with data governance experience outstrip market supply. Hence SAP MDM Consultants on the SI side must try to build an identity for themselves on their skill set and experience.

These are some of the learning’s/outlooks we must look forward in MDM trends in up-coming years. The roadmap also throws light on SOA, data governance for MDM etc. Given all this speculation & competition, one can hope that SAP MDM continues to mature and out-pace and out-perform its competitors in technology, capability and functionalities!

Ketan Phanse is a SAP MDM Business Analyst in Wipro Technologies

MDM - Road Ahead
Ketan Phanse

Upgrade MDM on Discovery System to SP6 Markus Gerber

Upgrade MDM on Discovery System to SP6
Markus Gerber

The Discovery System gives you a great opportunity to get in touch with enterprise SOA. To use the latest software, the one on the Discovery System needs to be updated. For MDM, it is not a big deal doing so.

The easiest way to upgrade your MDM installation is following the SAP NetWeaver MDM 5.5 SP6 Upgrade Guide. The most important information are in chapter 4 (Preparation) and chapter 5 (Upgrade Process). If you only use the Out-of-the-Box demonstrations from the Discovery System, there is no need to adapt the API Calls. If you already have own scenarios on the system, be sure to check before the upgrade if any API Calls need to b e adjusted.

After upgrading the MDM Server as described in the Upgrade Guide, you should upgrade the MDM Portal content as well. Download and deploy on the J2EE server the following components:

• JavaAPI
  MDM 5.5 SP06 Java API Patch 2 Hotfix 6
• WebUI (Change Tracker App)
  MDM 5.5 SP06 Web UI Patch 2 Hotfix 5
• Web Services
  MDM 5.5 SP06 Web Services Patch 2
• Portal Content (iViews, ...)
  MDM 5.5 SP06 Application Patch 2 Hotfix 6
  MDM 5.5 SP06 Technology Patch 2 Hotfix 6

Be sure to restart the J2EE server thereafter, otherwise some components won't be activated.

After the MDM upgrade to SP6, check that all the scenarios are working like they were before.

Markus Gerber is a Business Technology Consultant at SAP Switzerland.

Upgrade MDM on Discovery System to SP6
Markus Gerber