on 11-06-2007 7:36 AM
Hi All,
1) Can anybody give me link for benefits of MDM. How it can help an industry in betterment of master data and also help them to avoid creation of duplicates.
2) Once the data is cleansed & harmonized in central master data management and then distributed to client systems.How can one prevent creation of duplicates in client systems.
3) Ideally where the master data should be created when there is a fresh load of master data - in client systems or central master data manager.What is recommended?
Regards,
Priti
Hi Priti Deshmukh ,
These r the details regarding MDM
SAP NetWeaver MASTER DATA MANAGEMENT :
SAP NetWeaver Master Data Management (SAP NetWeaver MDM) is an enabling foundation for enterprise services and business process management providing a single version of the truth for customer, product, employee, supplier, or user-defined data objects.
Working across heterogeneous systems at disparate locations, SAP NetWeaver Master Data Management ensures cross-system data consistency through interactive distribution. It integrates business processes across the extended value chain, delivering features and functions to enable:
Master data consolidation Consolidate master data for companywide analysis and reporting. SAP NetWeaver Master Data Management consolidates and cleanses master data objects from disparate systems. After consolidation, it stores information from different systems in a centralized repository. Related rich content can be included to augment the data store.
Synchronization and distribution of master data Enable consistent data maintenance and distribution to ensure permanent harmonization of master data. Using global attributes, you can ensure that all systems receive the same master data during distribution and enrich the distributed data objects with additional attribute values in the target systems. Distribution can be controlled, visible, and traceable, with active status management at each distribution step.
Centralized management of master data Supports companywide quality standards by ensuring that central control of master data begins as soon as the data is created. Centrally created master data can subsequently be distributed to client systems as required using interactive distribution.
Administration of master data Manage master data without custom code. A powerful interface supports administrative tasks such as data exception handling and assignment of role-based access to business processes and information. Data managers use the interface to configure data source merging, business rules, and distribution details to downstream applications.
Management of internal content Collect and centralize all your content including parametric information and rich content such as images, paragraphs of text, PDF documents, and organizational intelligence about content in an enterprisewide repository.
Catalog search Deploy intuitive interfaces that help you locate items internally, publish Web catalogs on e-commerce storefronts and in supplier enablement programs, and integrate easy-to-search catalogs into e-procurement solutions all from a centralized repository, and all at speeds surpassing normal SQL-based queries.
Print catalog customization Disseminate product information directly from a centralized catalog repository to popular desktop publishing programs, and automatically generate fully formatted and populated page layouts.
Multichannel syndication of product catalog content Publish restructured and reformatted extracts or incremental updates of your product catalog content and distribute them to trading partners in several delimited text and XML formats on an unscheduled or regular basis.
Business process support Enable communication in a heterogeneous environment, and insert master data into other systems.
Business analytics and reporting Leverage synchronized data for reliable analysis and accurate reporting.
The following web-sites which give u detailed knowledge on MDM. I hope it surely helps u.......
(This web-site gives introduction to MDM, Master Data Operations, Master Data Integration,Master Data Quality )
http://help.sap.com/saphelp_mdm550/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
/people/nitzan.levi/blog/2005/06/20/the-story-of-mdm55
/people/sap.user72/blog/2005/06/14/worlds-fastest-and-shortest-introduction-to-netweaver-mdm-55
/people/ravikumar.allampallam/blog/2005/09/06/mdm-client-content-manager--different-modes
http://www.sapnetweavermagazine.com/archive/Volume_03_(2007)/Issue_02_(Spring)/v3i2a12.cfm?session=
http://www.sap.com/platform/netweaver/pdf/BWP_SB_Data_Unification.pdf
*********Pls reward points if u find this useful
cheers!
gyanaraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Priti,
2+3) CMDM as central system only makes sense, if you only use MDM for your data creation. You should disable the decentral data creation in all of your client systems. Technically, this can be easily done by setting the master data create transactions to readonly in the SAP system customizing. if you do not want your user to see the MDM as tool, you can implement your own UIs, maybe a Guided Procedure to create the Master Data. The user will then see a nice, browser based UI where he can create the data and doesn't really know, that he's using MDM. If you still create the master data in the client system, you'll have to do the work twice. Either you need to check during the creation if the data already exists in MDM, or you have to extract the new master data from your client system, send it to MDM, do a deduplication, and update the client system again.
BR Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
After cleansing and de-duplication of master data in central master data manager, the data is sent back to client systems but in this case duplicates would only be removed in Central Master Data Manager.What about the duplicates that already exist in client systems , they remain as it is or is there any way to mark them for deletion but it is not possible to go manually and mark them for deletion.Is there any way to mark the duplicate records from deletion so that the duplicate master data would not be used for day to day transaction bookings.
Regards,
Priti
Hi Priti,
Q - <i>in client systems , they remain as it is or is there any way to mark them for deletion but it is not possible to go manually and mark them for deletion.Is there any way to mark the duplicate records from deletion so that the duplicate master data would not be used for day to day transaction bookings</i>
It is not possible to delete these duplicate records because of transactional data with which they are involved. Also for legal purposes.
During merging the original record entries are not lost. Thus MDM system can send updated info to source systems with a flag deleted/not to be used .
Hence these records will not be used in daily transactions.
Hope this helps,
+ An
Hi,
>>>>1) Can anybody give me link for benefits of MDM.
check out this mdm overview
>>>>2) Once the data is cleansed & harmonized in central master data management and then distributed to client systems.How can one prevent creation of duplicates in client systems.
you need to make use of MDM in your client system
during one of the MDM presentations in teched I heard that
new CRM will use MDM to check for duplicates somehow
so it looks like it will be incorporated into client application
Regards,
michal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.