Limitations of SRM-MDM by NOT using Windows + SQL Server

[Former Member]

Hi all,

our consultants told us, that there are some sort of "limitations" if we install SRM-MDM other platforms than Windows + SQL Server; as example we were told, that e. g. the upload of BMECat files is not possible.

Is that true? If yes, where can I get a full list of "platform dependent" limitations?

We don't want to go for Windows nor SQL-Server if possible at all...

Thanx!

Regards,

--

Markus

[Former Member · Accepted solution]

Hi

<u>Incase you are using SRM 6.0, then -></u>

SAP SRM 6.0 is a big step forward for SRM: SRM 6.0 is the first SAP software to rely on the new user interface technology WebDynpro and the Web Application Server, rather than the previous ITS. It is also based on the completely new business rule framework (BRF) to define approval workflows. These changes are intended to improve usability and simplify workflow administration / customization, leading to better acceptance and lower TCO for our customers. However, the move to these new technologies is also a complex change and as a result, the product has experienced delays.

With our most recent development milestone - service pack 2 in mid-July 2007 - we have made lots of progress towards completion; however, we estimated that the product was still not yet ready for Ramp-Up. As a result, we decided to release the product only in beta shipment and to a very limited set of customers (14 in total) who are being closely monitored by our development organization. Seven of these customers are actually planning to go live on the current beta shipment.

Based on the progress made so far with Service Pack 2, we feel that we should be able to start the official Ramp-Up process on December 10th, 2007 - the target ship date for Service Pack 03. By that time, we should already have 3+ live customers, so new customers starting their projects will benefit from the experiences acquired from previous implementations.

<u>Time plan and Recommendations</u>

1. Ideally, we recommend that new and upgrade SRM customers wait for the start of Ramp-Up for SRM 6.0 SP03 (Dec 10th, 2007) rather than starting a project with the previous release SRM 5.0. SRM 6.0 offers many benefits compared to SRM 5.0 and should be easier to use + maintain. An Online scoping questionnaire will be available from mid October in the SAP Service Marketplace as usual.

2. The number of Beta shipment customers is strictly limited and therefore we do not intend to ship Service Pack 2 to any additional customers besides the 14 customers currently in Beta.

3. Implementation partners can request a demo license of the current support package 2 in the partner portal. They can set up their sandbox systems and familiarize with the new technology upfront before they enter into customer projects from Dec. 10.

"Should you have any further questions please contact your local SAP account executive"

<u><b>Also Please have a look at:</b></u>

<b>https://websmp102.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000692229&</b>

<u>Target Release to customer: Q4, 2007

Target Completion date Ramp-Up: Q1, 2008</u>

https://forums.sdn.sap.com/click.jspa?searchID=4313192&messageID=3226958

[original link is broken]

https://forums.sdn.sap.com/click.jspa?searchID=4313192&messageID=1757063

https://forums.sdn.sap.com/click.jspa?searchID=4313133&messageID=3408029

https://forums.sdn.sap.com/click.jspa?searchID=4313192&messageID=2857409

https://forums.sdn.sap.com/click.jspa?searchID=4313133&messageID=3442957

https://forums.sdn.sap.com/click.jspa?searchID=4313133&messageID=3687977

Do let me know.

Regards

- Atul

[markus_doehr2 · Accepted solution]

Hi Atul,

we won´t got for the RamUp, too expensive (RamUp manager, too much organization and bureaucracy). We have done quite a few RampUps in the past and it was not really what we are expecting it to be.

In the "early days" there was the FCS - the First Customer Shipment - where SAP was happy to have customers for beta/gamma tests but now we need to pay for that, for unfinished software, for an organization behind and for the weekly reports etc. Our experiences in the past just showed, that it´s not really worth it, and even less in the case of SRM.

--

Markus

[Former Member · Accepted solution]

Hi Markus,

as a SRM-MDM consultant I can give some detailed information: MDM server was originally designed and coded for windows systems, and by porting it to other OS like AIX, Linux etc., some issues regarding the different OS architecture occured. In the early days of SRM-MDM 1.0 (2006) especially the search performance was worse on non-windows systems.

As I have a customer running the system on SLES 9 (Suse Linux) since March, we can consider these issues as solved.

For a detailed overview about the supported OS/DB/Hardware look at service.sap.com/pam -> MDM 5.5. Please note that Itanium/IA64 is not supported for any OS/DB combination.

Regards,

Florian

[markus_doehr2 · Accepted solution]

Hi Florian,

thank you very much for that statement.

In fact, we want to implement on SLES 10 (or SLES 9 if necessary) with MaxDB, this is our main platform for all our system (aside from some Solaris/X64 systems).

I think, there was a misunderstanding between us and the consultant, either in the sense, that the consultant thought, he need to work physically with the MDM client/console/whatever tool on the system where the MDM <b>server </b>resides or the consultant not aware of the fact, that the MDM clients/console/whatever is not client/server enabled.

What we plan is, that we have two MDM-SERVERS (test/dev + production) and ONE Windows server acting as terminal server for both those systems so we don't have the necessity do distribute the clients across different PCs where people actually work with the MDM console/client/whatever.

--

Markus

[masa_139]

Hello Markus,

SAP MDM has server components and client components. MDM Server components runs on MaxDB, MSSQL, Oracle, DB2 with Unix, Linux, Windows, IBM OS. MDM clients needs Windows client and Excel if the data file is Excel. Clients components does not need any DB.

I think your consultant was talking about MDM client components.

Please check SAP Service Marketplace.

<a href="http://service.sap.com/mdm">http://service.sap.com/mdm</a>

<a href="http://service.sap.com/pam">http://service.sap.com/pam</a>

Regards,

Masa

[markus_doehr2]

Hi Masayuki,

thank your for your answer.

The consultant was talking about the SERVER but maybe he´s not aware of the client/server architecture.

--

Markus