Beruflich Dokumente
Kultur Dokumente
Welcome, Guest
Login
Register
Previous Next
When you create a new project in SAP Solution Manager, you select the project type Template Projects.
When defining the project framework, you assign project team members, roles, and responsibilities. This is the same as in implementation projects.
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/05/21/template-management-part-i
1/7
3/2/2014
In template projects, there is an additional tab, Template, in the project administration transaction, where you define the templates required in your project.
Templates serve as containers for global, standardized and harmonized business processes and the underlying system landscape in which they Operate. Template projects provide the environment to managed one or more templates.Create your own template by click "create new" button.
For each of these templates, you can control the visibility by switching between the statuses Closed and Open. A closed template is still being worked on by the template application team and, therefore, can currently not be transferred to any other rollout project. Only templates that are open for public use can be used by other rollout projects to jump-start template implementation.
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/05/21/template-management-part-i
2/7
3/2/2014
To be able to control the use of global attributes, you need to activate the Global Rollout Functionality on this tab.
These attributes define the global coverage of a business scenario or process, and allow you to control the extent to which a dedicated business scenario or process can be changed in an implementation project
The easiest way to jump-start your global process design is to use SAP predefined implementation content from the Business Process Repository.
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/05/21/template-management-part-i
3/7
3/2/2014
Along your global business process structure, you assign your templates to the process structure, so that all business process-related content is stored in the desired template for later rollout and/or shipment. This is done in the Template column, where you assign one or more templates to business scenarios.
You can set the global attribute for each business scenario, process or process step, to determine the scope of process changes in local roll-out projects.
Now make your own Business process steps for Campaign Management from the business process repositary.
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/05/21/template-management-part-i
4/7
3/2/2014
Define your own subnode attribute setup under pass on global attributes.
like, a)Creating and assigning BC Sets (Business Configuration Sets) to your process structure. b)Assigning related IMG (SAP Implementation Guide) activities, to fine-tune your configuration.
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/05/21/template-management-part-i
5/7
3/2/2014
c)Assigning global customer-specific developments like programs,transactions, etc. d)Creating standard test cases (manual or automatic) and assigning them to your process structure as well.
All these different pieces of pre-configuration can be launched in the rollout projects to accelerate local template implementation. The pre-configuration can be applied either 1:1, such as for BC Sets, or can be used as a copy reference, upon which local material can be built, e.g. for test cases.
The template is only then visible, and thus usable by the rollout projects. If you are not using the same SAP Solution Manager for your rollout projects, collect the templates into transport requests and transport them to the other SAP Solution Manager System. This ends the creation of the template project.The detail configuration to implement the Local Rollout projects are
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/05/21/template-management-part-i
6/7
3/2/2014
discussed in Part II.
1922 View s
Products: sap_solution_manager
Share
Tw eet
Like
2 Comments
Tridip Chakraborthy Apr 20, 2011 7:11 AM
Hi It was great reading your post and am happy to see that our thoughts on templatization, doesnt matter what form, helps re-use and help standardization and fast tracks processes I have posted one similar to this, do read it and let me know if you feel that SOLMAN can help drive templatization capabilities across different SAP Platforms How important are Templates to the SAP Procurement Community Part 1 regards, Tridip
Like (0)
Detailed enough to understand!!!! Enjoyed it !!!! Keep up the good Work. Regards Shaielsh Mamidwar
Like (0)
Copyright
Follow SCN
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/05/21/template-management-part-i
7/7