You manage your templates in this tab. You release finished templates, and transport them. You create new versions of templates, and archive old versions.
By default, templates that you are currently editing are not visible system-wide. To make a template visible system-wide, change its visibility to Public. You can put a public template in the scope of any project, system-wide.
You are in Project Administration (transaction code SOLAR_PROJECT_ADMIN), in your template project.
You create new templates and change existing ones with pushbuttons.
If you activate the global rollout functionality, you can lock your templates completely or partially against changes in the subsidiaries, in the Business Blueprint. A global attribute that is assigned to a structure element is copied as well as standard.
For further information, see Global Rollout with a Template in the Define Template in the Company Headquarters section.
As long as a template has the visibility status Private, you can make the following assignments, with Template Attributes:
● Solution Packages
This enables you to make a preselection and assign these attributes to the structure elements in the Business Blueprint. You can only assign Business Processes to Solution Packages.
You can also display, create, change and delete documents, and assign documents to the templates, with Documents (see also Edit Documents).
You publish a completed template system-wide with the Change Visibility pushbutton.
If you change the visibility of a template from Private to Public, the system updates the system landscape data of the template. At the same time the system conducts a consistency check of the assigned attributes. The template is visible system-wide in the Scope tab in the Project Administration. The visibility status is displayed by an icon in the Templates tab.
You transport the template with the Deliver pushbutton using the template collector. The template collector leads you through all the steps required to collect and transport templates. For more information about each step, see the template collector documentation.
Collect the relevant system role and language information, in the template collector. Asssign the template to an existing transport request in your project, or create a new one. If you create a new transport request, it can be of the type Workbench or Transport of Copies. Release this transport request in the Transport Organizer.
You create a new version of a public template with the Increase Version Counter pushbutton to preserve the status of the old template and proceed with the new version.
When you create a new version of a template, you can archive the old version to be able to compare different versions later.
You can call the logs of the release background jobs (template_ship) and archiving (template_archive) with the Call Job Log pushbutton.
You have released your template for reuse. You can now reuse the template in the same SAP Solution Manager system, transport it in your system landscape, or deliver it to your subsidiaries, in order to harmonize processes, customizing and other system settings company-wide.