Using Templates
Purpose
This process describes the use of a template. You can use templates:
● As a customer:
○ You create a template and use it in one or more implementation projects as the basis of the Business Blueprint.
○ You create a template in a system and transport it into other systems as the basis for the Business Blueprint of a project, e.g. in a Global Rollout.
● As a partner:
You can create templates and deliver them as partner templates for customer projects.
You can base new templates on any other template, whether delivered by SAP or created yourself.
Prerequisites
You have setup your system landscape.
For further information about restrictions in the use of templates and template projects, see the SAP note 603336.
Process Flow
Define a template
...
1. Create a project of type Template Project in the Solution Manager Project Administration.
Assign a name in the customer namespace to your templates. We recommend the namespace /…/. You should only use one namespace for the objects in a project.
2. You can base your new template on an existing template in the Scope tab in the Project Administration.
3. Create a project structure in the transaction Business Blueprint, and assign transactions, URLs, documentation and (only if you use the SAP Quality Center by HP) busness test requirements, to project structure elements.
4. To reuse documents in other projects, assign them in the Gen. Documentation tab.
The Project Documentation tab is only part of the current project, and not part of the template. Documents in the Project Documentation tab are not put in the template, and can therefore not be reused in other projects.
5. Assign, for example, BC Sets, IMG activities and test cases, to project structure elements, in the Configuration transaction.
Other objects are created in the component systems by the Solution Manager. These include BC Sets, user transactions, programs and CATTs. Proceed as follows in the component systems:
● Create a transportable package with transport recording, for each template and logical system.
Assign names in the /.../ namespace, if it exists. Use the same namespace when naming your packages.
● Create a separate package and a separate transport request for objects which are to be used in several templates.
● Assign the objects to the package as they are created.
● Create a transport request for each template and logical system, and record the objects in them, so that you can transport them into the correct component systems later.
6. Create one or more templates in this template project, in the Templates tab in the Project Administration.
7. Assign templates to the scenarios with the possible entries help in the Structure tab in the Business Blueprint transaction, to copy the scenario structures into your template. You can assign several templates per scenario.
8. Set the visibility of the template in the Project Administration to Public in the Templates tab, to make them visible system-wide.
9. Deliver your template in the Templates tab in the Project Administration.
This is not necessary if you reuse the template in the Solution Manger in which you created it.
10. Create a new version of the template in the Project Administration, to further develop it.
Reusing a template in the same Solution Manager system
Public templates are visible system-wide and can be used in any project, system-wide (see the Templates tab).
...
1. Create a project in the Project Administration of the Solution Manager in which the template was created.
2. Proceed as described in steps 4-6 of the Performing an Implementation Project with the Template in the Target System section.
Reusing a template in another Solution Manager system
For example, you send the template and its objects into another system, in a global rollout, as the template for the Business Blueprint of a project there.
Transport a template into another system landscape
...
1. Send the objects, e.g. BC Sets or CATTs, which you have created in the source Solution Manager component systems, to the target Solution Manager component systems, e.g. from the headquarters component systems to the subsidiary component systems, in a global rollout:
a. Analyze your project in the source Solution Manager, and specify the object types which you created in the component systems, and the components which you use, for the configuration and test case assignments in the template project.
b. Test the template in a test system:
i. Transport the transport requests from the component systems into a test system, in which the same products and product versions are installed as in the target component systems.
ii. To test whether the objects have been assigned to the project structure, choose the transaction Business Blueprint (SOLAR01) → Environment → Refresh Buffer in the test system. The system lists assignment errors in an error log.
c. If the test is successful, send the transport requests from the test system to the target component systems.
2. Release the transport with the template and send it into the target system.
Performing an implementation project in the target system with the template
...
1. Import the transport with the template into the target Solution Manager system.
2. Import component system requests for the template, into the component systems.
3. Create an implementation project in the target system Project Administration.
4. Search for the template or templates which you want to implement, in the Template Selection tab in the Project Administration.
5. Select the scenarios which were created in the source system for this template, in the Template Selection tab in the Project Administration.
The system copies the structure and the assignments from your templates, in the Business Blueprint and Configuration transactions.
6. Perform the configuration in the target Solution Manager component systems.
7. If the template has changed, compare the new version of the template with the project structure and the assigned objects of your target system, and copy changes if required.