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

Similar Messages

Change Management in Implementation project

Hi all,
Have any one used change request management in implementaion project?How to transport tp's in that?is it the same way as we do in maintenance project?How the transport request will be tracked?
Thanks in advance,
Avinash.

Hi,
This is how it happens
Maintenance projects
You want to make changes in systems as part of your planned maintenance period, and import all these changes simultaneously into production systems at the end of the maintenance period. For this purpose, you want to create a maintenance cycle, which is represented by a task list in the Schedule Manager.
A maintenance cycle is the period of time in which you:
Make changes in maintenance systems
Include these changes in new transport requests
Import these requests into follow-on systems for testing
At the end of a maintenance cycle, all transport requests are imported into the production system at the same time. Subsequently, the maintenance cycle can be closed manually and a new one can be created, if necessary (but only in compliance with the rules of the change requests that belong to the maintenance cycle).
Implementation, template, and upgrade projects
You want to make changes in systems as part of your project, and import all these changes simultaneously into production systems at the end of the project. For this purpose, you want to create a task list in the Schedule Manager.
With the help of this task list you:
Make changes in development systems
Include these changes in new transport requests
Import these requests into follow-on systems for testing
At the end of a project, all transport requests are imported into the production systems at the same time.
Task lists are generated automatically upon your request. If you use the Service Desk, the Service Desk transaction for managing cycle phases is also generated.
Check this link.
http://help.sap.com/saphelp_sm32/helpdata/en/ca/5b194746aa41dc9d3154da36b2f381/content.htm
Feel free to revert back.
--Ragu

Change Request Management in Implementation projects or not?

Hello guys,
We are starting a Change Request Management project at a customer. We discuss in the blueprint phase whether we should be using it only for maintenance activities, and not for implementation projects. We have some people that can be working both in maintenance and also in projects at the same time.
We want to understand whether that scenario is possible and also whether is advisable. We want to have control over the process, and therefore we should be restricting the creation of Transport Orders through SE01 so that we know that transport requests are created only by change document action.
What are the drawback, difficulties, considerations you may consider in making that decision? Is it logic to work that way or is it better just to implement it for the whole installation, including implementation projects?
Esteban Hartzstein
Edited by: Esteban Hartzstein on Jan 20, 2010 3:37 PM
Edited by: Esteban Hartzstein on Jan 20, 2010 3:39 PM

We want to have control over the process, and therefore we should be restricting the creation of Transport Orders through SE01 so that we know that transport requests are created only by change document action.
this you can do either via SE03 / Display/Change Request Attributes / SAP_TMWFLOW Request created using Change Manager X X / Defaul for all client = Mandatory
or
you can achieve this by just activating the CHaRM in SolMan ( solar_project_admin / system landscape / CHARM)
Nesimi

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

ChaRM and test management in implementation projects

Hi
I am doing implementation projects in solution manager. i have activated charm in the project so as to transport all the changes related to the project with the project lifecycle.
I have got confusions regarding CHarm and Test MAnagement.. when we activated CHaRM the tester can logon to the system and perform testing and pass the Change Document to the next phase.
What is the standard flow when both CHaRM and TEst Management for a project exists??
Thanks

Please can someone tell me how to use TEST MANAGEMENT and ChaRM for Implementation Project together??
Edited by: Hasan Sidra on Jan 2, 2012 11:11 AM
Edited by: Hasan Sidra on Jan 2, 2012 11:11 AM

Change Management integration with Project Administration

Hi,
Could someone help me understand the integration of Change Management and Project Administration within Solution Manager, pls? I would be very grateful for a sample process to demonstrate the complete workflow. Eg.
1) Support Messages is created
2) Change Request is created from Support Message
3) A project is created for the Change Request
4) ??? What about the blueprint, configuration, testing, learning features? How do they integrate with CHARM?
x) at the end, how does the project created for the Change Request integrate with the project that documents the business process? I mean, if the actual processes of an R/3 system are documented in a SolMan project, and a Change Request is processed, how do I modify the general project with the change project?
This is absolutely not clear either in the on-line help or in the book "SAP Solution Manager"
Thanks in advance,
Adam

Hi,
> 1) Support Messages is created
https://websmp206.sap-ag.de/~sapidb/011000358700000035912008E.sim
> 2) Change Request is created from Support Message
https://websmp206.sap-ag.de/~sapidb/011000358700002931432006E.sim
> 3) A project is created for the Change Request
https://websmp206.sap-ag.de/~sapidb/011000358700005479242006E.sim
> 4) ??? What about the blueprint, configuration, testing, learning features? How do they integrate with CHARM?
> x) at the end, how does the project created for the Change Request integrate with the project that documents the business process? I mean, if the actual processes of an R/3 system are documented in a SolMan project, and a Change Request is processed, how do I modify the general project with the change project?
I am not quite clear what exactly is your requirement here. Change Request Management and Project management are different in their ways. You can handle the documenation tasks through your project management and ChaRM is used for the changes.
https://websmp206.sap-ag.de/~sapidb/011000358700000059722008E
https://websmp206.sap-ag.de/~sapidb/011000358700006819152005E
Rajeev

Solution Manager for Implementation project

Hello,
I want to know how we should use solution manager for an implementation project. I am aware about the ASAP methods and the transactions in solman system for each phase. I have starting trouble like how to and where to start with? My ECC systems are not yet installed. Still we can go ahead with Blueprint creation and definition of roadmaps etc. Currently, it is done on paper. If anybody has done an implementation project through solution manager, could you please give me some hints how to start ? I repeat I am aware of the transactions but dont know what to add there in solar01/02 when the process are not defined/system not installed. Please guide me.
Rajeev

Hi Rajeev,
You're correct; you can start building the Business Blueprint without SMSY having all the systems that are 'to-be'. As long as you enter logical components in the project landscape with the correct product versions, you can replace those with the actual components once they have been installed. The BPR needs those product versions in the blueprint when you load the relevant scenario's. Once loaded, you can start documenting the scenario's, place the processes and process steps not used out of scope or delete them entirely and define custom scenario's, processes and process steps.
When the Blueprint has been completed with relevant design documentation, the Configuration transaction can be used to document how you actually configure the systems and, of course, to configure them from Solution Manager. The system landscape officially has to be definitive at the end of the Blueprint phase, unless you won't be configuring the systems centrally from Solution Manager.
The Solution is actually not necessary for a clean implementation; the Project will eventually lead to the solution. Once the systems are all configured and documented in SSM, you create the Solution and upload the project documentation into it in the Solution Directory.
Let us know how you get on!
Kind regards,
Patrick

How to use solution manager in upgrade projects

Hi,
How to utilize/use the solution manager in upgrade project like R/3,BW,CRM or entire landscape.
if we are upgrading the r/3 4.6c to ecc6 and bw3.5 to bi7.0 how to use the solution manager
please help and thanks in advance.
Edited by: MAHIPAL REDDY on Jan 1, 2009 1:28 PM

Hi,
Check [this document|https://websmp208.sap-ag.de/~sapdownload/011000358700002696532005E/310_320_SOLMAN_URMP_EN.doc]. This will help you to proceed further.
This is a detailed documentation on using Solution Manager for your upgrade project.
This will solve your problem.
[This Pdf |https://websmp208.sap-ag.de/~sapdownload/011000358700000208052007E/Upgrade_FAQ_SolMan_70.pdf]of FAQs on upgrade project is rich in information.
Feel free to revert back.
--Ragu
Edited by: Raguraman C on Jan 3, 2009 5:27 PM

Using Media Manager to condense project

Hi All,
So I'm working on a doc that has about 5+ TB of footage stored on a server. The director is travelling out of country for a little while, and wants to get everything that's being used onto his 1 TB drive, so that he can edit/make adjustments while he's out of town. I've been told using media manager is the way to do this, however I've only tried using it once, and it totally didn't do what I hoped, so I wanted to know if anyone has any tips for this sort of thing. Before anyone asks, Yes I read the manual and it didn't make my first attempt at MM work any smoother.
Basically, I need to create smaller .mov files from the larger files the clips are referenced from, without losing the original larger files, then take the new small ones and put them on a drive so they can travel. Any suggestions would be GREATLY appreciated. Thanks
Austin

I don't know why the link isn't working now.
You can subscribe/download from MacBreak Studios podcast through iTunes. They have many great videos. Take a look at them.

Documents used / prepared in an implementation project

Hi experts,
I would like to know what are the main / imp documents we prepare in an implementation project viz. BPML, etc
Could someone send me the list and functionality of the docs ?
Regards
Mahesh.

Hi
Could anybody help me on this?
Mahesh

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

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

Link between implementation project configuration (SOLAR02) and ChaRM?

Dears;
We want to benefit from listing all IMG Objects and developments in an implementation project (SOLAR02) to control our transports as we have ChaRM activated on the affected systems.
But there seems to be no link/control which has several consequences:
*Status of "changes" in ChaRM and related developments in the implementation project have to be tracked seperately
*There is no link between the development in the project (SOLAR02) and the created TR.
*There is no limitation/control in the content of the TR if it concerns items not listed in your project => how to check if the project is up-to-date?
Are my assumptions correct? Or am I forgetting something?
What is the experience in maintaining changes (transports) for implementation project? On what level? Linked with the structure in Solar02 or completely independant?
I have done quite some reading around the topics but documentation around project management via SolMan and ChaRM via SolMan seems never to be really connected? (only the overall status of the project and the activation of charm via SOLAR_PROJECT_ADMIN)

>
Jett Jiang wrote:
> 1. Active Change Request Management. the inter-connect is in SOLAR_PROJECT_ADMIN.
> 2. Use normal correction to control the TRs and updates the documents at the same time.
Thank you for the reply. Concerning these points:
1) This is done... No questions there
2) The "and" in your sentence means that I myself have to do both things? So there is no link?
So this does mean that (what my understanding was) I have to create a normal change via ChaRM but under the project for example a certain business scenario. That developers work on all topics related and should "remember" that if they put something under that transport they should verify if this is documented in the SOLAR02?
If then the change is put to testing they should manually update the status of everything related to this transport in the SOLAR02...

SAP - Organisational Change Management History

Having been involved in many SAP Projects as a change management specialist, I have often wondered how either the consulting house I am contracting to, or the client get their ideas about change management in SAP projects.
Some believe it lies in the domain of industrial psychologists who want to help people 'embrace change'. Others believe that it is mainly about communications.
I would love to hear different viewpoints about how SAP Change Management developed over the years and why people have gotten so confused about the role change management plays in SAP projects.
For me SAP ASAP details the Change Management deliverables, however very few people actually know how to execute these plans or what they are supposed to achieve.
I think the problem with how people view change management, is that it is a soft subject and is therefore highly flexible and can be done by anyone.
I listed the Change Management deliverables in my blog /people/swen.conrad/blog/2006/06/01/business-analyst-133-aris-for-netweaver-133-business-process-expert-133 .
Why is it that people do not adhere or use these deliverables?
With Kindest Regards
Paul Wilson

Hi Paul
Brilliant topic and one that in my experience is still not understood completely by clients and SI companies alike. My fundamental belief is that until an ERP implementation is viewed as a business transformation initiative, then change management is always going to be a 'nice to have' work-stream heavily focused on project communication and training. This is only the 'tip of the iceberg' in change terms and often projects start stalling or experiencing difficulties across the stakeholder landscape as other key areas of change management have been completely neglected. My experience in developing and executing the CM work-stream for an ERP project is outlined below:
1. Defining the scope of the ERP change programme and clearly articulating why the ERP implementation is taking place.
2. Starting Business Engagement and Business Readiness activities at the beginning of the ERP implementation is a key success factor. In many instances I have seen this activity either done poorly or not done at all until later on the project, creating a completely dis-engaged Key User community.
3. Developing a detailed definition of the changes that the new ERP system will introduce into the organisation and conducting a high level Change Impact Analysis to determine the degree of change coming in respect to people, processes, technology and infrastructure.
4. Designing and building the ERP solution so that it can deliver the strategic goals of the organisation. At this stage it is vital to involve the business in designing a 'fit for purpose' ERP solution.
5. Vitally important is getting the business to work with the ERP core project team to prepare adequately for go live. Making sure that all activities for cutover are completed in a timely manner, the business is engaged and the end users are aware of post go live support arrangements is a key role of the change management function.
6. CM is then fully involved in supporting post go live activities. Working closely with the business to identify business as usual owners is an important activity for the CM team. Measuring the system performance and ensuring business benefits are being realised is an ongoing task of the CM function until handover to the BAU teams.
7. Documenting the lessons learnt and manage the transition from the Programme to business as usual is the concluding stage for CM activities.
These CM themes are fundamental in making the ERP change programme a true success but can only happen if there is total commitment from top leadership to run the initiative as a proper business transformation effort..

ChaRM on implementation Projects

Hello
I have a conceptual question regarding the use of ChaRM on Implementation projects.
We are using ChaRM and have ensured that CTS is driven from Solution Manager i.e transport requests can only be created from corrections (SDMI). To date all SDMI's have been created as follow on documents to Change Transactions (SDCR). Going forward we would like to differentiate genuine changes (Changes to scope after blueprint sign off) from implementation activities driven from blueprinted requirements.
Whilst we see benefit from approval workflows for genuine changes, it is quite a chore to create SDCR's for all regular implementation work which is implicitly approved by signed off blueprint.
It is also difficult for us to then differentiate Changes from Implementation SDCR's.
Can anyone see a problem with all implementation tasks being generated directly as SDMI's with no preceding SDCR whilst leaving genuine changes as SDCR generated corrections?
The only one I can think of so far is that there is workflow that sets the status on an SDCR when the SDMI has been through it's lifecycle although I'm not sure how the system would behave if there is no SDCR.
Thanks
Mark

Hello,
for the first please use SDMJ. SDMI is old.
You can create SDMJ directly without SDCR and his approval workflow. There is no problem.
It is not really clear how to work with Implementation projects and "changes".
There are two known scenarios:
Implementation project (phase of the application management life cycle is "Implementation"):
If you have an really Implementation project for an Implementation of for example an new SAP product you should use an "Implementation project". It is not a change request!
Here you work with the known IMG-projects, blueprint, project phases.....
The transport process is realized via bc-sets. It means you create all you "changes" in bc-sets.
Implementation project (phase of the application management life cycle is "Optimization"):
Here you can use also the "Implementation project"
You can create SDMJ directly without SDCR and his approval workflow. There is no problem.
The transport process is realized via transport requests.
I guess the different between this two scenarios is the transport process.
Hope this is helpful.
Best regards
Thomas

Use Change management in implementation project

Similar Messages

Maybe you are looking for