Implementation Project steps

Can anyone guide me the how to do an implementation project in Solution Manager.. means is there any document that provide step by step guide??
Kindly share !!
Thanks
Sidra Hasan

Hi Sidra,
the following blog posts may help you:
Business Process Blueprinting from SAP Solution Manager
Business Process Blueprinting from SAP Solution Manager
SAP Solution Manager 4.0 Project Management - Business Blueprint Phase (couldn't find the part 1 but the other two parts may help you a lot).
pt II -> SAP Solution Manager 4.0 - Project Preparation Phase (Part II)
pt III -> SAP Solution Manager 4.0 Project Management - Business Blueprint Phase (Part III)
SAP Solution Manager - Roadmaps Introduction (Part I)
SAP Solution Manager - Roadmaps Introduction (Part I)
kind regards, Fabricius

Similar Messages

  • What are the roles in CRM implementation Project(all generic extractions)

    Hi Gurus,
    Now I am placed from a support project from BW (CRM) implementation project(all are generic extractions).
    & I am also new to implementation project.
    what are the neccessary steps to be taken when we are implementing BW for CRM.
    Gurus please clarify my doubts.
    1. what are the steps in implementation project in detail(as a developer).
    2. what are the sizes of the cubes,ODS & How to decide them.
    3. what are the neccessary steps for Master data & Transaction data.
    4.How to make the functional specifications for Infoobjects,cubes,ODS,Remote cubes,Multiproviders.
    5.can we change to delta loads to full loads if yes what happens to existing data.
    6.How flat file extraction used in the case of crm& how to do ascii format.
    7.What are the steps to be taken when we are creating Queries & Reports in BW CRM.
    It's very urgent.
    thanks = points.
    Bwcheta.

    1. what are the steps in implementation project in detail(as a developer).
    U have to basically to the techinal design after understnading the functional designs and implemnet the same( creating infoobjects, datatargets, datasources, queries etc.). Then u have to load data and do the unit testing on the same.
    2. what are the sizes of the cubes,ODS & How to decide them.
    Completely the business reqmnet and the data that the client wants to load.
    3. what are the neccessary steps for Master data & Transaction data.
    U have to understand ur master data and transaction data on the basis of whch u have create ur infoobjects and load data in them and finally in the datatarget.
    4. can we change to delta loads to full loads if yes what happens to existing data.
    Sure u can do that by choosing Full update in the infopkg. It will just load the complete data instead of changed records.
    *Hope it helps.

  • What are the Things required for BI 7.0 Implementation project

    Hi Friends,
                      Can any one suggest me
    1.What are the Things required for BI 7.0 Implementation project?
    2.System Configurations & Hardware Components?
    3. Any additional steps...
    plz suggest me.
    Regards

    Hi lakshmi,
    http://csc-studentweb.lrc.edu/swp/Berg/articles/PM_2006_upgrade_NW2004s_Bjarne_Berg_v12.ppt#426,3,Why Upgrade u2013 end of supportu2026
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d163a7-0301-0010-d9b0-98f692ea3c60
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
    https://wiki.sdn.sap.com/wiki/x/JYk
    Check the following links.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    check the following
    http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
    business content
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/g-i/how%20to%20co-pa%20extraction%203.0x
    https://websmp203.sap-ag.de/co
    http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm

  • How to represent and document BI, SBOJ in an implementation project

    Hello
    We are working in an implementation project modeling all the scenarios, proceses and process steps.  We want to represent as well all the BI, SBOJ and BPC information.  We are thinking of creating specific scenario for those.  We would like to get inputs about best practices regarding representation of BI and so on in Solution Manager, how to prepare the blueprint, what type of "functional" documentation, technical one, etc..  Then, how to manage the different objects in SOLAR02, what is available in config tab, development tab, only documents or we can have access from SOLAR02 to the different objects, and then navigate?  I would like to have your view on this subject.
    Regards
    Esteban Hartzstein

    You might get better help asking on [email protected]

  • CTS Mgmt in SolMan for an Implementation Project?

    Hi,
    In an Implementation Project, if we need to use Solution Manager for CTS, is there any pre-requisites?
    To be more clear, the project is still in the development stage and has not gone-live. The SolMan project type will be "Implementation" project(not a maintenance project). In this scenario, how the development/customization request will be moved across the landscape?
    What are the steps to be followed?
    Any inputs in this regard will be greatly appreciated.
    Thanks a lot in advance.
    best regds,
    Alagammai.

    Hi Avinash,
    Again thanks a lot for your timely help.
    So, all transports relating to an implementation project can be moved using the CHARM feature of SolMan. Nice )
    (ii) Whenever I create Implementation or Maintenace project in my SolMan system, I am not finding this "Change Request" tab under "System Landscape" tab. What could be the problem? Is that becos CHARM is not configured in my system?
    (iii) As you told while we create the transport route in the satellite systems, do we do it in the regular way? Or is there any modifications need to be done as we have to use it with CHARM? (sorry, might seem to be a silly question... but, as I am not aware of it...)
    (iv) Also, you have listed a number of steps to be done. Are these steps to be done in the SolMan system?
    (v) Is there any link or document describing this process? Do you have any document of your own? If so, can you pls send the same to my email id [email protected]?
    Thanks & Best regds,
    Alagammai.

  • Info on activities involved in various stages in Implementation Project

    Hi,
    I need some detailed information on activities involved in various stages in a SAP Implementation.
    I have seen the earlier threads in the forum on this Topic,but they are very brief.
    It will be very helpful for me if someone can provide some detailed document on practically what is done in those stages.
    Thanks in advance,
    Ashish

    Hi,
    Based on ASAP methodlogy.
    1)Project Preparation
    2)Business Blue print preparation
    3)Realization
    4)Final preparation
    5)Post go-live support.
    Project Preparation:Phase 1 initiates with a retrieval of information and resources. It is an important
    time to assemble the necessary components for the implementation. Some
    important milestones that need to be accomplished for phase 1 include
    u2022        Obtaining senior-level management/stakeholder support
    u2022        identifying clear project objectives
    u2022        architect an efficient decision-making process
    u2022        creating an environment suitable for change and re-engineering
    u2022        building a qualified and capable project team.
    Senior level management support:
    One of the most important milestones with phase 1 of ASAP is the full agreement
    and cooperation of the important company decision-makers - key stake holders
    and others. Their backing and support is crucial for a successful implementation.
    Clear project objectives:
    be concise in defining what your objectives and expectations are for this venture.
    Vague or unclear notions of what you hope to obtain with SAP will handicap the
    implementation process. Also make sure that your expectations are reasonable
    considering your company's resources. It is essential to have clearly defined
    ideas, goals and project plans devised before moving forward.
    An efficient decision making process:
    One obstacle that often stalls implementation is a poorly constructed decision-
    making process. Before embarking on this venture, individuals need to be clearly
    identified. Decide now who is responsible for different decisions along the way.
    From day one, the implementation decision makers and project leaders from
    each area must be aware of the onus placed on them to return good decisions
    quickly.
    Environment suitable for change and re engineering:Your team must be willing to
    accept that, along with new SAP software, things are going to change, the
    business will change, and information technology enabling the business will
    change as well. By implementing SAP, you will essentially redesign your current
    practices to model more efficient or predefined best business practices as
    espoused by SAP. Resistance to this change will impede the progress of your
    implementation.
    Business Blue Print Preparation:SAP has defined a business blueprint phase to help extract pertinent information
    about your company that is necessary for implementation. These blueprints are in
    the form of questionnaires that are designed to probe for information that
    uncovers how your company does business. As such, they also serve to
    document the implementation. Each business blueprint document essentially
    outlines your future business processes and business requirements. The kinds
    of questions asked are germane to the particular business function, as seen in
    the following sample questions:
    1) What information do you capture on a purchase order?
    2) What information is required to complete a purchase order?
    Accelerated SAP question and answer database:
    The question and answer database (QADB) is a simple although aging tool
    designed to facilitate the creation and maintenance of your business blueprint.
    This database stores the questions and the answers and serves as the heart of
    your blue print. Customers are provided with a customer input template for each
    application that collects the data. The question and answer format is standard
    across applications to facilitate easier use by the project team.
    Issues database:
    Another tool used in the blueprinting phase is the issues database. This
    database stores any open concerns and pending issues that relate to the
    implementation. Centrally storing this information assists in gathering and then
    managing issues to resolution, so that important matters do not fall through the
    cracks. You can then track the issues in database, assign them to team
    members, and update the database accordingly.
    Realization:With the completion of the business in phase 2, "functional" experts are now ready
    to begin configuring SAP. The Realization phase is broken in to two parts.
    1) Your SAP consulting team helps you configure your baseline system, called the
    baseline configuration.
    2) Your implementation project team fine-tunes that system to meet all your
    business and process requirements as part of the fine tuning configuration.
    The initial configuration completed during the base line configuration is based on
    the information that you provided in your blueprint document. The remaining
    approximately 20% of your configuration that was not tackled during the baseline
    configuration is completed during the fine tuning configuration. Fine tuning usually
    deals with the exceptions that are not covered in baseline configuration. This final
    bit of tweaking represents the work necessary to fit your special needs.
    Configuration Testing:
    With the help of your SAP consulting team, you segregate your business
    processes into cycles of related business flows. The cycles serve as independent
    units that enable you to test specific parts of the business process. You can also
    work through configuring the SAP implementation guide (IMG). A tool used to
    assist you in configuring your SAP system in a step by step manner.
    Knowledge Transfer:
    As the configuration phase comes to a close, it becomes necessary for the
    Project team to be self-sufficient in their knowledge of the configuration of your
    SAP system. Knowledge transfer to the configuration team tasked with system
    maintenance (that is, maintenance of the business processes after Go-live)
    needs to be completed at this time.
    In addition, the end users tasked with actually using the system for day-to-day
    business purposes must be trained.
    Final Preparation:As phase 3 merges into phase 4, you should find yourselves not only in the midst
    of SAP training, but also in the midst of rigorous functional and stress testing.
    Phase 4 also concentrates on the fine tuning of your configuration before Go-live
    and more importantly, the migration of data from your old system or systems to
    SAP.
    Workload testing (including peak volume, daily load, and other forms of stress
    testing), and integration or functional testing are conducted to ensure the accuracy
    of your data and the stability of your SAP system. Because you should have begun
    testing back in phase 2, you do not have too far to go until Go-live. Now is an
    important time to perform preventative maintenance checks to ensure optimal
    performance at your SAP system.
    At the conclusion of phase 4, take time to plan and document a Go-live strategy.
    Preparation for Go-live means preparing for your end-users questions as they
    start actively working on the new SAP system.
    Post Go-live Support:The Go-live milestone is itself is easy to achieve; a smooth and uneventful Go-live
    is another matter altogether. Preparation is the key, including attention to what-if
    scenarios related not only to the individual business processes deployed but also
    to the functioning of technology underpinning these business processes and
    preparation for ongoing support, including maintenance contracts and
    documented processes and procedures are essential.
    Regards
    Ravi Shankar.

  • Use Change management in implementation project

    Hello SolMan Experts,
    I have a requirement that I need to do an implementation through solution manager. I want to develop objects in my R/3 systems using solution manager. I have seen a thread where someone told that Change request is not possible in implementation but we have an option to create a change request with development(Implementation).
    Should I create a change request development(Implementation) for each development happening for the project?
    Please help.
    Thanks in advance
    Farzan

    Hi Farzan,
    While I am not able to give you further technical know-how on your specific question, I would like to share a word of caution though.
    In my experience, activating ChaRM within an active Implementation Project poses problems if you have to change the 'System Landscape' of the project midway.
    For instance, if you had 3 Logical Components listed in the tab Sys. Landscape of the Implementation Project, activated ChaRM, and later, you decide to add one more Logical Component, it does reset the CTS counters to '0' and you have to do a few steps manually, to restore it to what it should be.
    I am not sure if this is due to a bug or if this is a known constraint. I for one, can't foresee any Implementation Project which can effectively freeze the Sys. Landscape scope by end of Blueprint phase. In long projects, due to afterthoughts and various pressures, one may end up tampering with a few Logical Components well into Realisation phase.
    You may like to check with SAP over OSS and ask them for recommended approach.
    As a recap, yes it is possible to activate ChaRM in Implementation project technically. However, if it is indeed a recommended approach, I am not so sure.
    Regards,
    Srini

  • Template Project Usage in Implementation Project

    hi,
    I have defined the Template project in Solar_project_admin. Now how I can use this template project in Implementation project.
    What are the steps of copying the template project into implemenation project.
    Regards
    PK

    Hi Aditya,
    Many Thanks. I am new to this feature ( Template project & roll out).  My requirement is like, I need to define one template project & same has to be rolled out in other contries implementation projects. This is in a broder sense.
    Now what are the steps to go about. How to proceed.
    Will there be only one Solution Manager or different countries will have sepearte Solman. Will one Solman will do all rollouts.
    Can you give me some useful stuff as a biginner, how the project management is used  ( especially Template project & roll out )
    Regards
    PK

  • Adjust changes in Implementation Project  back to Template Project

    Hello All,
    Please can you help with transaction SA_PROJECT_UPGRADE, the case is as follow:
    STEP 1
    - Template project is created including process structure and documents, template is activated
    - Implementation project: is created derived from template project.
    - In Template project: Change in pocess node made: added an new process node
    - Run SA_PROJECT_UPGRADE with checked box "New Version of Original" and chosen project: Implementation project
    - Implementation project:  the yellow boxes appears on the appropriate place and button "adjust to original" is used.
    So far, so good
    STEP 2
    - Implementation project: a new process node is added, project is saved
    - Run SA_PROJECT_UPGRADE with checked box "'Current Version in Project" and chosen project: Implementation project
    - Template project: no changes are visible in SOLAR01 or SOLAR02
    - In SOLAR01: settings -> User specific -> box checked "Dislay changes made in project"
    So far, NOT good.
    Resume:
    - using transaction SA_PROJECT_UPGRADE from Template -> Implementation Project works according documentation
    - using transaction SA_PROJECT_UPGRADE from Implementation Project -> Templates does not work according documentation
    Does anybody recognise this?
    Or do I oversee something?
    System: SSM 4.0 updated to SP13
    Thanks in advance
    Rutger Koppelaar

    Hi Rutger (& all others watching this thread),
    I would like to make certain corrections to one of the points posted by me:
    2) Within a Template Project, any actual changes to the document does not offer itself as a 'change' while doing comparison on Implementation Project. In other words, after a given Scenario and all its associated documentation are copied into an Implementation project, if a given document at a given node needs to be edited, it's better to create a new document and upload it in Template Project than to open & change the same document. If the same document is edited, the Compare and Adjust cannot see that as 'difference'.
    On the above point, I have now see better/different results with my recent work; not sure if this is version/ support package specific.
    Environment:
    SolMan 4.0
    SAP_BASIS - Release 700 Level 0013
    SAP_ABA - Release 700 Level 0013
    ST - Release 400 Level 0014
    Assumption: Both the Template and Implementation Projects are in the same SolMan instance and not a case where the Template is being transported into another instance!
    Findings (please bear with this verbose description; one day I intend creating a Blog instead, to list all these points):
    (1) In General Documentation Tab of Template Project, any changes made is instantly visible in General Documentation Tab of the Implementation project - not even dependent on running SA_PROJECT_UPGRADE transaction
    If you indeed run this transaction - in foreground or background, and later check the Implementation Project, it would not highlight that node as having undergone any change. However, if you double click the document itself, you'd be pleasantly surprosed that it opens the most updated version you maintained in the Template Project. No need for 'Compare and Adjust'.
    (2) In Test Cases Tab - any change you make to Test Document in Template Project is again instantly available for the Implementation Project that had inherited the document, provided no manual changes were done to that document in the Implementaiton Project directly. Again, no need to run SA_PROJECT_UPGRADE transaction or the subsequent 'Compare and Adjust' function
        2a) If, however, the Test Document was altered in Implementation Project subsequently, the chain gets broken (in my understanding so far), and any subsequent changes made in Template Project does not become 'instantly' visible in Implementation Project - the two behave as though they are different documents
              In such a case, if you desire to 'restore' the supremacy of Template Project's contents, run SA_PROJECT_UPGRADE transaction, and after the background job finishes, visit Implementation Project concerned. The node where the Documents differ is not highlighted (unfortunately).  However, if you are aware of that node, and hit  'Compare and Adjust' button the ensuing Window does tell you with a # sign on the right hand panel that the Document has indeed changed in the original. You can 'adjust' that and save.
    Once this is done, and also you vow to not change the document in Implementation Project directly, the link between the two is kind of re-established. Any subsequent alterations you make in the Test Case at Template Project would be instantly visible from Implementation Project, as before !
    I have tried to explain precisely what I experiemented and found. I hope this works consistently
    The ways in which Document linkages are established and pointers to KW object IDs work is rather inscrutable for me, without ABAP support.
    I'll update any further findings here.
    Please keep a watch.
    Thanks and regards,
    Srini

  • Change Request Management for Implementation Project

    Hello gurus!
    I have a problem with execution change request in implementation project.
    I have created Implementation project and task list for him."Change request management" is active for this project.
    I can create document Change Request, but I can not to create Correction linked with Task plan...
    Dmitry.

    HI,
    Have you verified if your project definition is setup correctly ? Please verify with some of the steps available in the blogs
    First steps to work with Change Request Management scenario
    /people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
    Change Request Management scenario: Usual questions
    https://weblogs.sdn.sap.com/cs/junior/view/wlg/15116
    Change Request Management scenario: Working examples
    /people/dolores.correa/blog/2009/07/23/change-request-management-scenario-working-examples
    Hope this helps.
    Cheers
    Sh

  • What exactly Implementation project means ?

    I am having very limited knowledge on Implementation project!
    I know EWM Module as i am doing automation testing. i just wanted to know what exactly EWM implementation project means? what are the steps involved?

    Hello Manjunath
    A project implementation for EWM requires definitions regarding structure of warehouse, in order to customize it based on a business blueprint. Then you start to change the system and test system behaviour. You must perform tests and finally move solution to production (this is a short resume of ASAP methodology).
    Best regards
    Carlos Díaz

  • Managing the administration in implementation projects

    Hi all,
    I have been using the Solution Manager in implementation projects for 2 years now. However, I'm having difficulty on managing the project schedule using the administration tab in transaction solar01 and solar02:
    1.     Unlike MS project, for example, you cannot define a connection/ link between the structure elements, which means that if you have to change the start time for a process in the administration tab, i.e.,  it has no effect on the other processes/ steps' start time, even when you know that there should be an effect.
    2.     You cannot put partial person days, for example 1.5 PD or 0.4 PD.
    3.     As far as I know, if you export the project structure to a MS Project file, it is not possible to import the changes made in the file back to the Solution Manager.
    For that reasons, some customers and project managers prefer to export the project structure to MS Project and manage the project schedule and resources in that separated file.
    I would appreciate it if you could give me an advise based on your experience, on how to better manage the times in an implementation project, using the Solution Manager.
    Thank you,
    Adi

    Hi Adi,
    I have also been using SolMan since May 2004 (from 3.1 days). Unfortunately, in my view, the functionality of Admin Tab hasn't kept up in pace as with other features of SolMan.
    My suggestion is not to use it for active day-to-day tracking for the limitations you have pointed out as also for it not being the best-of-breed to manage Project Plans of a multi-location, multi-stream project.
    I have, at best, used Admin Tab for Keywords and Team members - for information sake.
    Also, if you use a Template Project -> Implementation Project copy, Admin tab is not included as part of 'Compare and Adjust' functionality - which means that if the same Team Members and Keywords are required on Implementation Project, you cannot get them inherited.
    I am sorry that my answer kind of confirms your findings and helplessness as  opposed to providing any solution. But, that's my honest sum-up as well.
    Regards,
    Srini

  • XI Implementation project plan

    Hi All,
    Can somebody help in getting a typical XI implementation project plan, to understand the complexity and risks involved in the implementation
    Regards
    Anjul

    As far as I know there is now such thing as an implementation plan, but there are several steps that you should always carry out when introducing XI.
    First of all, know why you wanna use it. See how many interfaces are there in the landscape, what kind of information is exchanged between the different systems, how frequently are messages sent from one system to another, how big are these... If you would like to know details about the size of the hardware involved, you should have a look at service.sap.com/quicksizer, which will give you a first idea about the size of the machine you should run on.
    Bear in mind how many system you would like to have, prd,dev,qas etc and how to carry out transports between them.
    Don't forget that you should have a backup strategy, an archiving strategy, disaster-recovery strategy and proper authorization concept in mind.
    But if you are looking for a special document I cannot help your further.
    Regards,
    Jaime

  • Realization phase in Template/Implementation project

    Hello!
    We have completed our blueprinting in SM40 on a project which was created as a template project. Now to kick-off realization phase, should we create a new implementation project out of the template..or ..just configure the project as a template itself...
    What are the pros and cons? What is the right way of doing it..
    Appreciate any advise/inputs.
    Thanks.
    Mike

    Hi Mike,
    in the template project every customizing element has the attribute global / harmonized / local.
    Even if a rollout directly with the template project is possible (never heard of that), you would loose one of the greatest advantages of the global rollout functionality:
    When copying the template project into an implementation project, all customizing elements set as global are "locked" and can not be changed by the local support teams. The ones with attribute "local" can (details see attribute specification). Thus you ensure that local settings can be applied and global processes remain as defined.
    Next step is to centrally develop a new version of the template for roll-out, while your maintenance teams can work with the implementation project(s).
    Another decision is to use one Implementation project for all roll-out candidates (pro: all relevant documentation in one project; con: documents need to be well arranged for not to loose track) or several Implemenation projects for each roll-out candidate (con: scattered documentation; pro: easy overview per roll-out candiate).
    Hope this clarifies a bit...
    Regards
    Christoph

  • Implementation Project with ChaRM

    Hello,
    I'm on Solution Manager 7 EHP1 SP 6 and  all configuration work for ChaRM has been completed.  I've been following the DEMOs from SDN and SOLMAN-RKT and with some exceptions (some steps/screens are either no longer required or assumed); which leads me to believe that up to this point everything is working as is it should.
    I'm still a little fuzzy when it comes to Implementation Projects.  I have the following questions:
    1. How are Non-IMG changes (Workbench) assigned to a project.
         a.  solar_project_admin -> System Landscape -> IMG only create a Customizing Request
    2. In the Normal Corrections Demo, corrections are initiated through CRMD_ORDER, is this so during an Implementation Project?
    3. In the DEMO there appears to be a Workflow notification process between task, is this active by default?
    I know that's a lot all at once, but I finally got some momentum behind this and I want to keep it going.  Thanks in advance for any information you can provide; points will be awarded.
    Jose

    Hi Jose,
    1. How are Non-IMG changes (Workbench) assigned to a project.
    a. solar_project_admin -> System Landscape -> IMG only create a Customizing Request
    Once you have created a Change Request transaction (SDCR), you will be able to select the follow up change document, Normal correction (SDMJ) or U'gent Correction (SDHF) for example. Then you will create a transport request under this change document. This transport request will be available in the development system where you will perform your changes. For new objects the system will ask the transport request when you are creating the object, for changes in an existing object the system will ask for the transport request when save the change.
    2. In the Normal Corrections Demo, corrections are initiated through CRMD_ORDER, is this so during an Implementation Project?
    Yes, you can use CRMD_ORDER to create new change requests (SDCR) and select the Normal correction (SDMJ) in the subject field. Once this change request has been approved the Normal Correction will be created automatically. However you can create a new change request from a support message (SLFN) for example.
    3. In the DEMO there appears to be a Workflow notification process between task, is this active by default?
    I'm not sure if I have understood this last question, by default ChaRM doesn't have notifications. But you can setup this in the same way of support notification. Please take a look at the following link:
    Sending E-Mail from Support Message
    /people/dolores.correa/blog/2007/09/18/sending-e-mail-from-support-message
    Best regards,
    Fernando

Maybe you are looking for