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.
You have set up your Landscape Management.
For more information about restrictions when using templates and template projects, see SAP Note 603336.
1. In Project Administration in SAP Solution Manager, you create a project of type Template Project.
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 on the Scope tab page in Project Administration.
3. Create a project structure in the Business Blueprint transaction and assign transactions, URLs, documentation, business functions, and (only if you use SAP Quality Center by HP) business test requirements to the project structure items.
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 on the Project Documentation tab page are not included in the template and cannot, therefore, be used in other projects.
5. In the Configuration transaction, assign BC Sets, IMG activities, and test cases (for example) to project structure elements.
The managed systems will contain objects in addition to those from SAP Solution Manager. These may include BC Sets, user transactions, reports, or CATTs. Proceed as follows in the managed systems:
● Create a transportable package with transport recording for each template and logical system.
Assign names in the /.../ namespace, if available. Use the same namespace when naming your packages.
● Create a separate package and a separate transport request for objects that are to be used in several templates.
● Assign the objects to the relevant package as they are created.
● Create a separate transport request for each template and logical system, and record the existing ones in the relevant transport request so that you can later transport them to the correct managed systems.
6. Create one or more templates in this template project on the Templates tab page of Project Administration.
7. On the Structure tab page of the Business Blueprint transaction, use the input help to assign templates to the scenarios to copy the scenario structures to your template. You can assign several templates per scenario.
8. Set the visibility of the template in Project Administration to Public on the Templates tab page so that they can be viewed throughout the system.
9. Deliver your template on the Templates tab page in Project Administration.
This is not necessary if you use the template in the SAP Solution Manger system in which you created it.
10. Create a new version of the template in Project Administration to further develop it.
Public templates can be viewed throughout the system and used system-wide in any project (see Templates Tab).
1. Create a project in Project Administration of the SAP Solution Manager system 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.
As part of a global rollout, for example, you send the template and its associated objects to another system so that the template can be used as the basis for the business blueprint of a project.
1. Send the objects (such as BC Sets or CATTs) that you have created in the managed systems from the source SAP Solution Manager system to the managed systems of the target SAP Solution Manager system. For example, in the case of a global rollout, from the managed systems of the company headquarters to the managed systems of the subsidiaries:
a. Analyze your project in the source SAP Solution Manager system and specify the object types that you created in the managed systems, as well as the components that 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 managed systems to a test system that contains the same products and product versions as the managed target system.
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 managed target systems.
2. Release the transport with the template and send it into the target system.
1. Import the transport with the template into the target SAP Solution Manager system.
2. Import transport requests for managed systems that belong to the template into the respective managed systems.
3. In Project Administration in the target system, create an implementation project.
4. Find the template(s) that you want to implement on the Template Selection tab page in Project Administration.
5. On the Template Selection tab page of Project Administration, select the scenarios that were created in the source system for this template.
The system copies the structure and the assignments from your templates to the Business Blueprint and Configuration transactions.
6. You configure the settings in the managed systems that belong to the target SAP Solution Manager.
7. If the template has been changed, compare the new version of the template with the project structure and the assigned objects of your target system, and accept any necessary changes. For more information, see Compare and Adjust with Source.