http://help.sap.com/saphelp_nwmdm71/helpdata/en/4b/f768714caa20dfe10000000 a42189b/content.htm http://www.sapmdm.sapag.co.

in/sap-mdm-xi-integration/sap-mdm-xi-r3-integration/

SAP SRM http://help.sap.com/saphelp_srmmdm10/helpdata/en/44/ec6f42f6e341aae10000000 a114a6b/frameset.htm Syndication http://forums.sdn.sap.com/thread.jspa?threadID=437538&tstart=416

http://www.sapmdm.sapag.co.in/uncategorized/mdm-syndication/ BPM http://saplab.org/2009/10/10-bpm-frequently-asked-questions-faq/ SAP MDM Business Content http://wiki.sdn.sap.com/wiki/display/SAPMDM/SAP+Business+Content

SAP MDM / BI integration http://forums.sdn.sap.com/thread.jspa?threadID=1768755

you can use some different metods as is: 1) connect directly from BI to outbound/inbound SAP MDM directory 2) use MDM ABAP API for read/edit/add data from/to mdm repository 3) use SAP NetWeaver PI and MDM PI Adapter for data exchange between MDM and BI More about integration you can read here:

http://help.sap.com/saphelp_nw70/helpdata/en/45/5d3bfaa9ef3bdfe10000000a1553f7/frameset. htm
and here:

http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/956cd09521062de10000000a42189d/fr ameset.htm
and here:

http://help.sap.com/saphelp_nwmdm71/helpdata/en/43/1346e6ca856f40e10000000a422035/fra meset.htm

Please refer Step by step integration of BW with MDM:

Integrating MDM with BI - Part 1 Integrating MDM with BI - Part 2 Integrating MDM with BI - Part 3
Also, Please refer below Wiki:

http://wiki.sdn.sap.com/wiki/display/BI/Integrating+BI+with+MDM

From our experience the new release of SAP NetWeaver Master Data Management 7.1 SP06 will better address the customers needs and helps Camelot ITLab to create Master Data Management scenarios in a much more efficient and effective way through increasing overall system improvement, performance and stability. Built on the stable basis of SAP NetWeaver Master Data Management 7.1 SP05 the new support package is the next step to a holistic Master Data Management approach. Amongst others, Camelot ITLab sees the major enhancements in: Data Manager

Increased usability for mass operations by enabling modifications on failed records whilst showing one consolidated error message. Massively improved matching performance by narrowing down the matching range through required rules. MDM Server

Enhanced system availability through an improved locking mechanism. The locking strategy will enable slicing for mass operations and runs on table level which will not lock the entire repository like in the past.

An event notification service is created in order to send alerts to attached systems

Improved archive / unarchive performance showed performance gains up to 50% in Camelot ITLabs tests.

Improved performance through multi-threaded parallel matching.

MDM Import Server

Enhanced memory footprint while importing XML files. The XML files are not flattened any more. MDM Java API

Enhanced API functionality enabling developers to gain from overall improvements

----------------------------------------------------------------------------------------------------------------------------------------There 1) 2) 3) 4) 5) are also lots of different documents that can be generated: BBP (Business Blue Print As Is and To Be), Configuration guide, End User Manual, Project Plan, Solutions Map, etc.

Data-quality analysis Project scoping, planning and estimation Master-data modeling and taxonomy creation Implementation of business rules and matching strategies to enable data consolidation Development and roll-out of data, data-process governance and methodologies Services in data cleansing, validation, enrichment and classification, including certified third party data-quality services Definition, design and configuration of MDM system architecture Tuning and optimization of MDM performance Custom API and SOA development services

SAP EP MDM Integration .

In the customized way you can create your own Webdynpro screens and use the MDM Java API to integrate with MDM. You need to deploy the MDM_JAVA_API sca files on WAS as matching with your MDM version. Then you can use these API to call your MDM functions through portal.

In the standard way :SAP has some pre-delivered content to integrate with MDM .so you can use the MDM std IViews to integrate MDM with EP. In this standard approach you need to deploy the std business packages sca files that are available with the MDM version. On doing this you can use the std archives on portal to call MDM functionalities from EP, so you can have for eg an MDM search IView or MDM result set IView etc.

The Deployments that are needed on portal for integrating with MDM are:

MDM_JAVA_API 70 SP2 .sca for search and configuration UI BPMDMTECHN06_2.sca BPMDMAPPL06_2.sca

As you have finished the deployment, there are few configuration needed to be set so that you can start using MDM components on Portal.

Lauch Go.bat i.e. Visual Administrator and logon using your administrator credentials.

Go to services > Connection container > MDM Factory

Select the Porperties Tab and set the server details and maximum allowed connection i.e. pooling properties.

Now Go to Services > Monitoring, here you can see the up-to-date information on MDM deployed components. You can also see the errors in the deployments if any.

With this your MDM deployment on portal is completed. In the next article we will see portal side configurations to connect to MDM repositories.

The Business content provided by SAP, for integration of EP MDM. The landscape could be EP as a front end with MDM acts as a backend for it. Using the standard IViews the fields in the MDM can be displayed in EP side. Depending on the type of fields, you can customise the display of fields at the EP side.

Using the concepts of MDM Workflow or UWL or Guided procedures, you can implement the CMDM scenario. In this case you dont need PI.

SRM MDM Catalog:

BP_SRM 7.1 SP2 SRM_MDM_CAT 3.0 SP2 MDM_JAVA_API 7.1 SP1

Hi Himanshu, Please Check following things : 1--> For automatic syndication, MDM syndication server service must be running. 2--> you have defined the Processing Type Property in the outbound port as "automatic". 3--> You have defined the format of output file as "XML schema" and specified the XML schema name while creating port. For Automatic syndication Steps are as follows: 1--> Create a syndication map.(If u want to use any standard map then this step can be excluded.) 2--> Open MDM console and select the ports table (Repository --> Admin-->ports). Add a new port here. 3--> Define the type of port as outbound and specify client system name. 4--> Define the saved syndication map name using which syndication server will syndicate the master data to the outbound port. 5--> Define the format of output file. We can select one from fixed text, delimited text, access, excel, xml, xml schema as output file format. 6--> At last define the type of processing for syndication server. It can be manual or automatic, But for automatic syndication it should be manual. After this, save the port and start the syndication server service. This will start syndication of records as selected by the syndication map on the port. Hope this will help you. Revert back to me for further queries. Thanks, Shiv