Skip to Content
avatar image
Former Member

How much time used to establish the solution manager env for a new ERP implementation project

Hi,

I'd like to know your number of consulting day used on Solution Manager for the first time.

As a BASIS guy in a consultant firm, we always deliver custom the latest - 1 version bits to customer. That means, we have to have solution manager up and running before installing ERP.

But we found that longer time need to complete our initial installation due to solution manager. We need to

1. Install Solution Manager (<1 day)

2. Upgrade Solution Manager using SUM (>3 days)

3. System Prep and Basic Configure (2~3 days, there are some "note implement" and sync stuff took much time)

4. Install ERP DEV. (<0.5 day)

5. Register DEV into SLD and do "Managed System Configure", Solution Configure, Mopz , just for upgrade xml and approval.

(depends on experience and version of SLM, could be 2 days to 2 weeks)

6. After installation of PRD, do again Managed System Configure for PRD, and configure EWA.
(depends on experience and version of SLM, could be 1~3 days)

OK, we usually took 2~3 weeks (or 10~15 man days) to deal with solution manager. Almost cost 30%~50% of total BASIS MDs for a new implementation project. Some PM even question us why BASIS spent 50 days (20-days overrun) in a new ECC implementation project (including P/Q/D/SLM installation , authorization (PFCG) config and adjustment, and handover)


I think Solution Manager really need a baby sitter, it's too complex, only for mid-large scale company.

Before convincing our PM and customer, I'd like to know other's number. If you have experience on that, please share your number.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Jun 02, 2015 at 03:09 PM

    OK, things getting worse.

    Now SAP sales push HANA as the only choice under ERP (new implementation), customers are forced to use SLM with Sybase ASE.... they don't like it, very few know about ASE.

    Can they install their own database (MSSQL, Oracle...) for SLM ? without any charge ?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Matt Fraser

      Matt,

      Thank you for sharing so much.

      Yes, it takes much time to update. I really hate SUM's shadow system concept for Initial Setup Update because we don't care downtime (nobody use it !). 3 days ago, I started to update by separating Java and ABAP Stack (Run SUM as javaonly option to update Java Stack, and then run SAINT to update ABAP Stack)..... It is still running the last step XPRA_EXECUTION now. I guess the total runtime will be 4 days. If I can't tune some parameter for parallel tp, could be faster.

      It is a huge SP level update (from SSP04 to SPS13) and the open transaction hold very long, so my logsegment (SAP ASE) blow up twice and lots of troubleshooting needed during the update path.

      I wish to have SLM7.1 SR2. Before that happen, I'll export this updated bits for new installation (SystemCopy it!).

      Thanks

  • Jun 10, 2015 at 01:38 AM

    Wei-Shang,

    I would like to confirm your estimated efforts to setup an SAP environment.

    Honestly - it takes me a bit more time with all the preparation, checking and implementing OSS notes and post-processing.

    Yes - during the project lifetime I have a dedicated FTE for SolMan - just to manage SolMan and support the functional consultants.

    The benefit for the PM is that everything is proper documented, we have the monitoring, reporting and alerting landscape ready, we use lots of the self services before Go-Live and the transition to BAU runs smoother.

    This reduces the risk and _saves_ costs...

    cheers

    Kay

    Add comment
    10|10000 characters needed characters exceeded