Template project reference in Implementation Project

Hi,
I have defined Template Project & created Business Blueprint hierarchy for the same.
Now I need to refer the Template Project in Implementation Project.
1) How to refer Template Project in Implementaion Project ?
2) Can I get the Template Project reference in Implementation Project automatically in Scope OR do I need to do some settings ? Currently I am not able to see the Template Project in Scope.
Regards
P Kumar

Hi Kumar,
Refer below links. Should be useful and also I am assuming that you have created master template and you want to refer master in local implementation project.
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/05/21/template-management-part-i
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/05/21/template-management-part-ii
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/05/21/template-management-part-iii
Master template should be visible in local implementation project under scope automatically.
Thanks
Sateesh.

Similar Messages

Linking solution manager projects with CHARM implementation project

Hi Guys,
Currently i am working in CHARM implementation project, i have created one CHARM implementation project with urgent correction and i am able to create the Transport request and release the transport request succesfully and i am able to move it to quality system successfully. But my customer is asking to link the solution manager project to CHARM implementation project.
Earlier before implementing CHARM they have implemented project managent in solution manager, during that project they have created so many projects which are currently running, now they want those projects to be linked CHARM implementation project.
When ever they create a transport request through CHARM they want the TP to be saved under a respective project which they are using currently. but according to my knowledge the TP can be saved under CHARM implementation project only.
Now i want to know whether the projects created in SOLAR_PROJECT_ADMIN can be linked to CHARM implementation project. Pls give ur valuable inputs as it is very urgent.
Thanks&Regards
Raju

Hello,
We have implemented this with two systems landscape where in we have in place a Solution Manager Dev system and Solution manager Production system both are SOLMAN 4.0 with SP12. So the path for us to move the changes is from Development Systems to Production system.
We have ChaRM between the Dev and production. We reapplied the satellite system concept. For us the Solution manager Prod is a satellite systems all the changes that we move from Development system to Production systems is tracked with necessary documentation in the ChaRM process.
Yes, I agree with you that this is not any big magic. Working with two SOLMAN implementation, I strongly feel that SAP needs to have well rounded ChaRm processes. We have robust Change Management Process, but when we moved to ChaRM we were limited functionality of the ChaRM processes.
I had approached and did some research on how other companies are implementing the same process. Most of them have almost the same process for tracking SOLMAN changes. I am still look out for improved process to manage SOLMA changes.
Hope this helps!!! Thanks
Vish

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

ManualResetEvent and Using a project reference in Shared Project?

I recently just started writing an Universal App for the first time, and it’s also my first time with C# (most of my mobile experience is in Java and Android). I was reading a post on SQLite-WinRT:
http://andywigleyblog.azurewebsites.net/?p=53.
I’m having trouble with two things:
ManualResetEvent seems to be available for Windows Phone Silverlight, but not a part of the Windows Modern App APIs. I’ve searched in the available .NET APIs, but System.Threading doesn't have ManualResetEvent for modern apps.
For Universal Apps, App.xaml.cs is located in the Shared Project Reference. However, from the shared project reference, I need to access a reference SQLiteWinRT, but the reference is in my modern app project, so I can't access it using 'using'. How do I
access this reference from a Shared Project Reference?
Edit: #2 I was able to figure out. I had to add SQLiteWinRT to both Windows 8 and Windows Phone project.
Edit: #1 Turns out it is available. Under System.Threading. Windows dev/center search just can't find it. (－‸ლ) The docs are very confusing.

Hi Qoheleth07,
Thanks for sharing the solution with us, I will mark Matt's reply to close this question, if you still have questions to ask, please feel free to let us know :)
Thanks for your understanding,
--James
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Copy teammembers and keywords from template to implementation project

Hello All,
When adding structure elements (business scenarios, etc) from a template project to an implementation project, the data on the administration tab is not copied with it.
When selecting a specific scenario from the template we need to be able to also copy the keywords and team members to the implementation project.
1) Is this possible without custom development
2) If we use custom development. How can I link a structure element to its Administration tab data (keywords and team members) in ABAP?
Thanks
Jurjen

If you copy the entire project using SOLAR_PROJECT_ADMIN, and then delete out of scope scenarios using SOLAR01, then the administration data can be copied over. Note, however, that this only works for the initial project copy. Subsequent changes to the information on the Administration tab in the Repository cannot be carried over to the projects using SA_PROJECT_UPGRADE. Another restriction is that you can't copy a template project to an implementation project. Also, if you want to use further template functions such as the Global Attributes, then you have to bring scenarios in using the template functions, where this data is not copied over.

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

Not able to see General Documentation in Implementation Project

Hi All,
I've created one Template Project and one Implementation Project. Now I've added some documents to Template Project - General Documentation Tab. Ideally this newly added documents should be appeared in Implementation Project - General Tab. But in my case I am not able to see this newly added documents. Is there any reason behind this? What should I do to make them visible in Implementation Proj - General Documentation tab?
Another question is, If a document from Project Documentation tab is deleted by pressing 'Delete Row' button (not actual 'Delete' button), how can I retrieve that document? How can I see the list of all deleted documents?
Thanks in advance!
Shaun
Edited by: shaun99 on Feb 16, 2012 4:28 PM

Hi Shaun,
For the implementation project, please read the session "USING THE TEMPLATES" in the wiki page for template projects, where it explains how to update your project with the changes made in the template project.
-http://wiki.sdn.sap.com/wiki/x/gRkMDg
regarding the download, I'm not aware of any easy way to do mass download of the documents. Maybe in SI80 you could do such thing but I believe you would only be able to filter by the folder where the documents are phisically stored and as you're using a template project, all the documents are stored in the folder SOLAR00, shared along with solutions and etc..
more info about this in the wiki page for documents in solar01 and solar02:
-http://wiki.sdn.sap.com/wiki/x/rBoMDg
Kind regards, Fabricius

ChaRM Maintenance Project & Implementation Project - How to select ?

Hi,
I am having an Interesting issue.
I have defined two ChaRM Projects, One is Maintenance Project (ZCHARMIDES) & One is Implementation project (ZCHARM_NC).
Implementation project (ZCHARM_NC) I defined today itself & Maintenance Project I am using for last 2 months.
In both the projects I have same logical component.
Now When I am creating a Change Request & authorizing it, it is generating Normal correction based on subject. But by default its taking Task list M000000001 which belongs to Maintenance Cycle, But I want to select Implementation Project, how to select this.
My issue is why system is not asking me to select project ( Maintenance & Implementation) even though the logical component is same.
I want to select Implementation Project - I000000114 for checking Normal Corretion.
Regards
Praveen Khot(PK)

Hi PK,
It depends on the subject which you are selecting. A normal correction type in the subject field is related to the maintenance project. And hence, when you have only one maintenance project with that landscape, it automatically gets assigned to that maintenance project.
In order to select the implementation project, your subject would look like Development (Implementation) (unless customized) and only then the follow on correction type would be the normal correction in the implementation project.
Per the standard functionality of ChaRM, you will not be able to see the pop up to choose amongst one of the project types for a CR.
Regards,
Sneha Vyas.

How to transport Implementation project template changes?

Hello All,
I have made changes to the project template (added doc types, assigned status schemas) for Implementation projects in my dev system by going to SOLAR_PROJECT_ADMIN > Goto > Project Template > Implementation projects. I want these values to be the standard values whenever I start a new Implementation project.
When I save my changes, I am not prompted for a transport request, nor can I find any transport option in the menu. Do these project templates need to be manually configured in my test and production systems, or is there another way of assigning the changes to a transport that I cannot figure out?
Thanks in advance,
Michele

Hi,
Just enable the GLOBAL field for the values which you want to be available for all the implementation projects.
e.g
You created a documentation type which is having global field tick so it will be available for all
Hope it helps
Regards
Prakhar

How to connect Template project and Implementation project

Hi Experts,
     I would like to know how to connect Template project and Implementation project
    in Solution maneger.   Please help.
Best regards,
   Gaito

Hey Gaito,
great. Now that you have a template project, you need to create one or more templates within the project template.
Go to tab Templates (of your Templ Proj) and activate 'Global Rollout Functionnality' to be able to use the templates.
Create a new template thanks to button create. Visibility will be set to red 'private'. You ll have to set it to visible so it becomes visible from your implementation project.
You ll see when trying to do that next message 'No scenarios/configuration structures assigned to the template XXXX'. That means that in SOLAR01 you did not define a scenario that ll be used in template you re trying to create
In order to do that go to SOLAR01 for template project, select/create scenarios in tab structure and set in column template value of your template (the one you re creating in SOLAR_PROJECT_ADMIN) and in Global Attribute set value t Global
You l definitely find more info on this in sap document SMI310 (course). I don t know if you can find it on internet
Hope this helps
Regards
Khalil

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

How to map business scenarios from implementation project to template project

Hi
We have a template project and in this we have maintained few business scenarios. And also some specific scenarions are configured in the implementation project. Now we need to make template project as Global Template and for this we need map all existing scenarios in implementation project to template project.
Please suggest how we can map from implementation project to template project.
Thank you

Hello,
Along with Sandeep recommendation, you can do it by several ways.It all depends on how are the current projects organized.
Did you create the template project and then rolled out the templates to the impl. project?
In case you want to update these scenarios in the Template project based on the changes you performed in te Impl. Project, you can use the Compare & Adjust functionality.
You can Copy Scenarios from one project into another by using the right click/context menu directly in the node in solar01.
If you just want to copy the structure, you could export the Impl. project structure in solar_project_admin by using the "fill business blueprint" functionality, then adjust the structure similarly for the template project and upload.
and so on..
regards,
Fabricius

Defining System Landscape in Implementation Project

Hi
I want to ask about defining System Landscape of an implementation project in solution manager.
I have assigned the logical Component in Systems tab.
I want to ask about creating the IMG Project in Sstems Landscape tab,, Is it compulsory to create IMG project for the new Implementation Project??? Why we create IMG Project?? Is it compulsory??
Please guide
Regards
Sidra Hasan

Hi,
Implementation Project u2013 A project to implement SAP solution as a part of regular implementation or a roll out. This is considered for single-site implementations. Predefined scenarios can be selected from template projects.
It is not compulsory to create these projects in solution manager that depends upon your implementation strategy.
Thanks
Sunny

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.

Deleting document from general documentation tab in implementation project

Hello,
We tried to delete a document from gen. documentation tab in an implementation project, since the gen. documenation tab is greyed out, we couldn't do so. The document is a link from a template project, we tried to delete it (by using the trash can icon) from there first, but the system says "the document is still in use".
Does anyone of you know how to delete a document which has been linked to implementation projects based on a template project?
Regards, Li

Hi Li,
Here's a solution you can try for your problem.
Go to your template project in SOLAR01and mark the line of the document you want to delete and press the remove button (red minus icon).
Then go to your implementation project and go to the same place where that linked document is. Click on the <b>Adjust to Original</b> icon (looks like two little boxes with two arrows pointing down.) when you click on this icon, you will get a pop-up window where on the left hand side is your template (original) and the right your implementation (current). On the left, you will see a blank line with the red minus icon and on the left you will see the document you are trying to remove. select that line and click on "Adjust selected entries" icon that's in the middle of the screen.
Notice both lines became blank, once that's done, click on complete icon at the bottom.
You're document has been removed from your implementation project.
Note: This is the only way that I have found for this issue. This does not mean that the document was completely deleted from Solution Manager....just the link to your project. If ever in the future you want to link it back, you can still find it with SOLAR_EVAL.
Please let me know if this worked for you.
Regards,
Salpi

Template project reference in Implementation Project

Similar Messages

Maybe you are looking for