MDM landScape

Hi,
We are planning to implementSRM-MDM catalog. So we are going to have NW Java/Oracle DB on Linux server.
And NW MDM 7.1 on Windows & Oracle DB on linux.
So totally 4 servers - NW Java, Oracle DB, NW MDM 7.1 , oracle DB.
Will there be any issues implementing DB on linux & MDM 7.1 on windows. WIll i face connection issues. Will there be any issues migrating repositories in cases i need to move to different servers.
Any help on this is appreciated.
Thanks for your help,

Hello Kobby
Just follow installation guide :
for unix
https://websmp102.sap-ag.de/~sapidb/011000358700001668492008E
for windows:
https://websmp102.sap-ag.de/~sapidb/011000358700001668482008E
Befor you start your migration process you should freez your repositories and make archive.
Than you should unarchive your repositories on new landscape.
Regards
Kanstantsin Chernichenka

Similar Messages

SRM-MDM catalog 3.0 - Installation Process

Hi All,
I'm in the process of installing SRM-MDM catalog 3.0 but I'm not sure about the correct installation process.
The SRM-MDM catalog 3.0 installation guide indicates that the following instances are mandatory for SRM-MDM Catalog system:
1- Java system with the central instance, the central services instance, the database instance
2- MDM Server, and MDM Import Server
We have covered the first point by installing an SRM 7.0 JAVA system. Regarding the second requirement, I have some doubts in the way it should be completed. What we did so far was to install the SRM-MDM catalog 3.0 from the MDM 7.1 installation master. So, we now have two MDM server instances: MDS and MDIS.
I'm stuck now. I'm not sure on how to connect my SR-MDM system to the JAVA DB (created in step 1) to create a new MDM schema within it. This makes me wonder if I've followed the correct process. Could you please clarify and explain which steps should be performed to get my SRM-MDM system up and running? Actually my main concern is..Should I first install a MDM system as it's described in MDM IG, and after that perform the installation of the SRM-MDM catalog as I've already done in step 2?
Hope being clear enough I'll wait for your suggestions.
Thanks and regards

Hi Diego.
The Installation Note Number for SRM-MDM Catalog 3.0 is : 1177779. The recommended steps would be to follow how the Installation Guide recommends you to do so.
But still your assumption is correct. MDM landscapes and Java landscapes are both different set of categories to be installed to make the Catalog scenario to be successfull.
Step 1: Make sure you have the back end database server(SQL/Oracle/???) is installed.
Step 2: Make sure all the MDM components(MDS, MDIS, etc) is installed.
Step 3: Make sure Java WebAS is installed correctly.
Step 4: Now deploy the Catalog SCA and MDM Connector deployed in the Java WebAS.
Step 5: You can unarchive and load the repository.
Step 6: Try to launch the catalog using the URL provided to check and make sure if the connection is fine.
Also what Masa has mentioned is the communication path how the whole process is achieved technically and that doesn't mean that it has to be in the same order which he has mentioned. The below sequence is just an path to describe how the communication is achieved technically.
User -> Browser(Search UI deployed on AS Java) -> (Java API on AS Java) -> MDM Server -> MDM Repository -> DB
Relating Masa's path with the above steps
User ->
Browser(Search UI deployed on AS Java) -> Step 3 and 4
(Java API on AS Java) -> Step 3 and 4
MDM Server -> Step 2
MDM Repository -> Step5
DB-> Step 1
Hope this helps.
Regards
Bala
Edited by: chandar_sap on Aug 30, 2010 6:16 PM

Steps to connect a CRM system with MDM

Hi everybody,
I've got a problem here : I should build a connection between a CRM system and MDM (get the data in several tables in the CRM system, normalize them in MDM and then put them back in the CRM).
What would the steps I've got to do to achieve that ? Do I need XI between the two systems ? Do I have to map the tables before sending them in MDM (and how could I do that ?)
Thank you for all the help you can give me
Seb

Hi
The Universal Worklist (UWL) iView is part of the KMC (Knowledge Management and Collaboration), capability of SAP NetWeaver. The integration of the SAP NetWeaver MDM workflow with UWL will be provided with SP04. This will provide the ability to expose SAP NetWeaver MDM workflow steps in the SAP Universal Work List (UWL). These jobs may run from the BPM process or can be launched inform within SAP NetWeaver MDM. UWL is defined as the main consolidated Inbox for SAP users, being the main location to monitor jobs directly activated in SAP NetWeaver MDM, or connected to a process that integrates with SAP NetWeaver MDM.
Using the SAP NetWeaver Portal UI, show a summarized list of all workflow (WF) jobs/tasks from all systems of SAP NetWeaver MDM Landscape per user - one single UI for all my tasks. The UWL is already integrated with other major SAP products, like R/3, SAP CRM, mySAP ERP, etc.
https://sapportal.wdf.sap.corp/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/infocenters/ws%20ptg/ptg/platform%20ecosystem/industry%20standards/projects%20and%20programs/business%20process%20management/index.html
First of all, you must set a RFC connectivity between CRM and backend system:
o     Create system users for remote connection (RFC_CONN). This user must have SAP_ALL authorization.
o     Create RFC connections in CRM system.
Go to transaction SM59 on CRM side and click on 'create' button. Set RFC destination name to the back-end system <sid>CLNT<client> (eg. R3DCLNT200), connection type to 3 (abap / R/3 connection) and fill the target host to your back-end system. On the Logon/Security tab, add the RFC_CONN user created in the previous step. Save your settings.
o     Create RFC connections in the back-end system.
Go to transaction SM59 on the back end and click on 'create' button. Set the RFC destination name to CRM system <sid>CLNT<client> (eg. CR1CLNT300), connection type to 3 (abap / R/3 connection) and fill in the target host to your back-end system. On the Logon/Security tab, add the RFC_CONN user created in the previous step. Save your settings.
o     Create a logical system name in CRM.
Go to transaction SPRO -> SAP Implementation Guide -> Customer Relationship Management -> CRMServer -> Technical Basic Settings -> ALE Settings -> Distribution -> Basic Settings -> Logical Systems -> Define Logical System Add a new value:
Save your settngs.
o     Create a logical system name in the back end.
Go to transaction SPRO -> SAP Customizing Implementation Guide -> SAP Web Application Server -> Application Ling Enabling -> Sending and Receiving Systems -> Logical Systems -> Define Logical System Add a new value:
Save your settngs.
2.
3.     Middleware parameters setup Go to transaction SM30 on backend system and choose table CRMCONSUM. Add the following values:
4.     Next, choose CRMSUBTAB for subscription table for the Up and Download Object and add the following values
User     ObjectName     U/D     Obj. Class     Function     Obj. Type     Funct. Name
CRM     empty     Download     Material     empty     empty     CRS_MATERIAL_EXTRACT
CRM     empty     Download     Material     empty     empty     CRS_CUSTOMIZING_EXTRACT
CRM     empty     Download     Material     empty     empty     CRS_SERVICE_EXTRACT
Next, choose CRMRFCPAR for definitions of RFC Connections and add the following values
User     ObjectName     Destination     Load Type     INFO     InQueue Flag     Send XML
CRM     *     SR1CLNT300     Initial Download     SR1CLNT300     X     Send XML
CRM     *     SR1CLNT300     Request     SR1CLNT300     X     Send XML
CRM     MATERIAL     SR1CLNT300     Initial Download     SR1CLNT300     X     Send XML
Leave all other field empty.
Now, configure filtering for the material master:
Choose the CRMPAROLTP table for CRM OLTP Parameters and add the following values:
Parameter name     Param. Name 2     Param. Name 3     User     Param. Value     Param. Value 2
CRM_FILTERING_ACTIVE     MATERIAL     empty     CRM     X     empty
Now we must edit the table for the application indicator. Go to transaction SE16N on the back-end side and choose table TBE11. Search or add an application component BC-MID and edit activity settings (field AKTIV = X).
Save your settings.
8.     Enterprise buyer with/without CRM In this activity, you define whether you are running the Enterprise Buyer and CRM in the same system. This might accelerate the Master Data download performance. If you are using CRM in the client, then skip this activity.
In the CRM system run transaction BBP_PRODUCT_SETTINGS, deselect 'Test mode' and choose the Execute button.
The system generates a report containing all tables that have been deactivated.
9.     Generate repository objects With this procedure, you generate the middleware function modules (BDoc Object Type) for the material master.
Go to transaction SMOGGEN and choose object PRODUCT_MAT and PRODUCT_SRV. Generate services for all object categories.
Please let me know your email id, i shall send you this document
Regarsd
Rehman
Reward Points if Useful

MDM 7.1 on HP-UX Archiving on a daily basis

Hi all,
We are migrating a MDM landscape from Windows to HP-UX.
We used to run CLIX .bat files scheduled on the Windows Server to perform daily archive of our repositories.
As CLIX is only available for Windows Plataform (you can check the MDMCX7100*.ZIP from http://service.sap.com/swdc), we need to find a way to perform Repository Archiving natively on our HP-UX environment.
Is there a HP-UX tool, or MDM commands we can schedule on our HP-UX Server?
(We were recommended to run CLIX commando from our workstations, but is not really an option we can consider)
Thanks in advance
Yours faithfully,
Cristian Marin

If anyone my find this helpfull,
CLIX is installed as a native tool of the MDM Server, so all we had to do was to rebuild our CLIX commands under (sh) shell.
Below you may find the code we have modifiy it to replace the final a2a file.
#!/bin/sh
#El archivo resultante queda en la ruta
#/usr/sap/MDP/MDSXX/mdm/archives
FECHA=`date +%F_%T`
clix cpyArchive "<mdm-host>:<mdm-password>" "<REP_NAME>:<SID>:Oracle:system:<oracle-system-password>" -A <REP_NAME>_$FECHA.a2a
Good luck!
Cristian Marin

SRM 7.0 on NW 7.01 with SAP MDM 3.0 Catalog

Hello,
We are implementing the following Components:
SRM 7.0
MDM 7.1
BI
PI 7.0
Portal 7.0
We are currently live with ECC 5.
We will be using the SAP MDM Catalog along with SRM. We will be also implementing MDM to use for Master Data Cleansing. I wanted to know whether we will need to install the SAP MDM Catalog on the SRM7.0 system or can we install it on the MDM 7.1 system and then connect it to SRM?
Any pros/cons if we can use it as part of the MDM landscape?
Thanks in advance.

Hi Sheldon,
Great question. Technically speaking, you can certainly use your SRM-MDM repository on the main MDM 7.1 system. However, the following cons apply:
1. Even though it contains several core components from Netweaver (NW) MDM, SRM-MDM Catalog is being developped by SAP as a separate product. The patch releases between SRM-MDM and NW MDM are also not in synch (at least that's the current situation). Therefore, if you have both applications on one MDM system, you will have an undesired dependency related to applying new patches - which may lead to some issues.
2. Performance of one application will be impacted by the load on the other one.
3. Down time of one application will impact the users of the other one.
4. Upgrades will be more difficult to handle.
On my recent project, the direction from SAP was to use two different systems - one for SRM-MDM, one for NW MDM.
Cheers,
Serguei

MDM 5.5 SP06 Support on SRM 7.0

Hi
We are using SRM 3.0 (EBP 4.0) with requisite catalog to maintain the catalog
We are going to upgrade SRM to SRM 7.0 and would like to use our existing MDM 5.5 SP06 lanscape (It is being currently used to maintain our company Product Master)
Can someone tell me that the latest SRM version 7.0 can use existing MDM Landscape without any issue
We have very small size of Catalog which we are using with SRM 3.0
Thanks in advance
Thanks
Deelip

Hey Deepali,
I informed you about best practice and SAP's recommendations.
My thoughts on WHY SAP RECOMMENDS SEPARATE LANDSCAPE FOR SRM-MDM CATALOG are as follows:
1. Version strategy of SRM-MDM Catalog is different from MDM Product version strategy. And from my experience what i have seen, compatible package of SRM-MDM Catalog is released with in 1-2 month of release of normal MDM. You may face a situation that a new version of MDM is available but SRM-MDM Catalog version compatible to this MDM version is not released..
For example, As of now, MDM 7.1 SP05 is the latest version, but latest version SRM-MDM Catalog version is based on MDM 7.1 SP04 and as of now MDM 7.1 SP05 is not yet supported for SRM MDM Catalog.
2. if You face any compatibility problem or issue in SRM-MDM Catalog and have to upgrade MDM patch to fix it, then it will disturb your other master data object processes too.
3. SRM-MDM Catalog UI should be compatible to MDM Server Version and is based on a specific MDM Release. You may face a situation that SRM-MDM Catalog package not exactly matching your MDM Server version.
Please check the version mapping note for SRM-MDM Catalog 2.0 and MDM 5.5. this will explain this point in a better way..
SAP Note 1083126 - Version mapping SRM-MDM Catalog 2.0 to SAP MDM 5.5
But, on the other side, i don't see any technical restriction in using SRM-MDM Catalog with other Master data objects (* if you can get SRM-MDM Catalog package matching to your MDM server version)
So, you can also use same MDM server in above case.
Hope this will clearify things more...Revert if any further question...
Best Regards,
Shiv

How to determine using MDM rich client OR thin client?

We want to save but also want to make sure nothing missing
SO could you tell me how to decide rich client or thin client?
Thanks!

Hi Jessica,
MDM Rich Clients: A rich client is a networked computer that has some resources installed locally (MDM Components) but also depends on other resources distributed over the network (MDM SERVER). It Provides rich functionality.
e.g MDM Components (MDM Console, MDM Import Manager, MDM Data Manager and MDM Syndicator)
MDM Thin Clients: If a user only needs to perform select tasks and does not need all the functionality of a standard computer or program, a thin client may be the right tool for the job. e.g. SAP Enterprise Portal (Iviews for Search and Read access)
You can verify that MDM Components are Rich clients and SAP Enterprise Portal is a Thin client on page 4/41 Components in a MDM landscape as given in below link:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/284a5534-0601-0010-da9f-b70996d5ce90?quicklink=events&overridelayout=true
Regards,
Mandeep Saini

MDC Mapping

Hi:
One of my customer was asking me this regarding to their implementation of MDM landscape...
Based on what we have seen in the XI repository depending on the target MDC-system a specific CREMAS version is used.
The MDM configuration guide talks about mappings like "CremdmCremdm03ToMDMBusinesspartner" for 4.6 MDCs and "CremdmCremdm04ToMDMBusinesspartner" for 4.7 MDCs
So the questions are:
1.
What in case the MDCs are using
a) earlier CREMAS versions (which is definitly the case for SRS-systems => sending CREMAS01 to Fusion). Do the MDCs need to change their custominzing - need to switch the format or do we need to adjust XI-content?
b) IDOC extensions are used (that is probably a more theoretical case) - same question.
Thanks if you can give me some answer...
Regards
Dawei

Hi Dawei,
In general, both scenarios require enhancements on the MDC, the XI and the MDS.
If you look at the master guide it states that MDM 3.0 supports R/3 releases 4.6C and higher, which means CREMDM03 and higher. Earlier versions, 4.0B to 4.6B, can be supported on a project basis but SAP Development must be involved.
As for your second question. If IDOCs are extended and this data is relevant for MDM, then there are a series of enhancements that must be made in the MDC, the XI and the MDS. The document "Extending The Business Partner in MDM 3.0" is available at http://service.sap.com/instguides -> SAPNetWeaver -> Release 04 -> Installation -> SAP MDM and provides step by step instructions to do this.
Hope this helps!
Richard

SRM-MDM Catalog Installation/Landscape

Hi,
We are currently having the following landscape in place with regards to the SRM, MDM and SRM-MDM Catalog :
Server 1 : SRM 5.0 Running   (HP-UX)
Server 2:   Enterprise Portal running with MDM Content and SRM-MDM Catalog JAVA components (HP-UX)
Server 3:   Standard MDM Server installation (Windows 2K)
We have configured everything according to the notes and guides (including the guide from Sudhendu Pandey), but when we try to configure the Search UI in Webdynrpo, the java components cannot connect to the MDM host and we are getting just the connection failed error.
My questions are :
1)   Can we run with the above landscape or is it necessary to have the SRM-MDM Catalog Java components installed on the same server as MDM.
2)   Do we have problems with versioning of the MDM server and the SRM-MDM java components ? We already replaced the MDM_JAVA_API with the correct one, but I do not have a newer version of the other api.
3)   Do I need to configure anything on the MDM server to get this running ?
Thanks in advance for your help
Regards
Raymond

Hi Foh,
Apologies for my late reply, but I was travelling. Thanks for this tip. We were using the latest versions for the MDM Portal Content, but the API for the SRM-MDM catalog was different.
I have updated this API with the latest version (Patch 3 HF 1) and now I can logon to the MDM server and I see the MDM Repositories. However if I now try to logon to one of the repositories he gives me the same error that the Login has Failed. The user that I am using is the default one coming with the SRM-MDM repository (Admin).
Regards
Raymond

Does MDM APIs work in CE 7.2 landscape?

Hello Experts,
We have a requirement to fetch data from MDM tables and display in WD Java applications. We have to use MDM APIs for that. Our landscape is as follows:
Portal server is on CE 7.2
MDM Server version is 7.1 SP05
Now, the major problem is, in order to establish a connection to repository by MDM API, we need to provide "MDM System Alias" in the code. This alias is for the system of type MDM created in portal system administration --> System Config.
As far as I know, we need this alias created if we want to establish a connection. But following documentation on help.sap.com says that MDM Business Package isn't supported for CE 7.2 version. And until we deploy MDM BP, system template of type MDM isn't avaialble on portal.
http://help.sap.com/saphelp_mdm71/helpdata/en/5e/48a04270600d31e10000000a1550b0/frameset.htm (See the Prerequisites section)
What should we do in this case? Is it so that MDM APIs are not supported for CE 7.2 version at all? Or is there any other way to achive it?
Please help me with your valuable inputs.
Thank You,
Ameya
Edited by: Ameya Pimpalgaonkar on Jun 21, 2011 12:12 PM
Edited by: Ameya Pimpalgaonkar on Jun 21, 2011 12:14 PM

Hello Kanstantsin Chernichenka,
Thank you very much for the reply. There is no way I can do this in SP 05? or do I have to upgrade to SP7 only? I am not sure if we can upgrade to SP7 that's why I am a bit concerned.
And it is supported in SP07 means that I can deploy a business package for MDM on CE 7.2, only if MDM SP is 07?
Ameya
Edited by: Ameya Pimpalgaonkar on Jun 21, 2011 12:54 PM

5 system landscape for MDM?

We are in the process to layout infrastructure for release 2 of our transformation project for ECC, MDM, PI, BODS. We are debating on possible solutions
1) typical 5 system landscape like below.
DEV->QA->PRD
DEV2->QA2
DEV2, QA2 are project landscape and others are maintenance landscape. After project testing, changes from QA2 will be moved to DEV, QA, PRD
2) dual landscape
Here, layout is same as option 1 but for go live changes will be moved directly from QA2 to PRD.
I like to know what are the pros/cons of each approach.

Hi Subin,
The first approach is a lot easier to manage and involves lesser risks.
Also as Vag rightly points that in case of different Vendors co-ordination is also an important point to consider before designing such a landscape.
We too used the first approach and once our major change was done,we merged the systems which in your case are DEV2 and QA2.This was a much cleaner approach.
Thanks,
Ravi

Enrichment Adapter: MDM 5.5 Adapter in 7.1 landscape

Hello Experts
Is it possible to use an MDM 5.5 built Enrichment Adapter, in a MDM 7.1 landscape?
Thanks
Swarna

Hi Swarna,
MDM 7.1 Enrichment Architecture is compatible with Enrichment Adapters built for MDM 5.5.
Regards
Orit

Why MDM in homogenous or single system landscape

<b>Hai expertise,
If at all i need to include MDM in a organization which include only SAP system.. what are all the advantages i will get out of MDM...
In single system landscape we use MDM at the time of upgradation of system..
Any advantages other than that???</b>

Govada - You said that you have single system (SAP) landscape for your client...
but you have not clarified if you have other SAP systems like CRM,SRM,BW implemented for your client..If so..MDM will be helpful for consolidating and harmonizing master data across systems..
But if you client has only one R/3 system installed , MDM may not be useful...
Rule of thumb : MDM is fit for the scenarios where you have your Master data residing/being maintained by diffrent systems. (R/3 has its own customer maintainance and CRM has its own..) in this case MDM is of best use.
Cheers,
Aravind

Landscape of MDM?

what is mean by Landscape of MDM?
please explain me in detail? and
where it is useful?

http://help.sap.com/saphelp_mdm550/helpdata/en/46/ba16538b0a1514e10000000a114a6b/content.htm
See above link.
rewards if useful.
BR,
Alok

Best Practice to transport MDM Workflows trough a 3-tier Landscape

Hello Experts,
I wanted to ask you for some Best practices to transport MDM Workflows from D-to Q/P?
Well besides the Archive/Unarchive method because we want to keep the Data of P in the repository
and do not want to import the whole.
Any ideas? Points are for sure!!
Best regards
Carsten

Hi Carsten,
Currently with the MDM 5.5 version the only transport mechanism that will allow you to export your Workflows from the development server to the Production or Quality is the Archieve/Unarchieve method.
but this methods archives the data as well along with the workflow.There is no such method to exort the workflow alone.
But with the onset of the MDM 7.1 there are new transport mechanism included and hopefully they address this issue.
A work around that i can think of at this moment:
- If you have your development server as your Master rep and the Production server as your slave
- Then you can call the workflow from the D to the P.If you do not have any data presntly in the dev.
- and then Normalize the Productions server to make it an individual master rep with its own data.
I am not sure how well this solution will help but just a suggestion....
Hope It Helped
Thanks & Regards
Simona Pinto

MDM landScape

Similar Messages

Maybe you are looking for