1.1. General
Solution templates are a type of solution created to reuse content which are generic and common across solutions. A solution template contains similar objects like a customer specific solution. It contains source artifacts to be reused (for example: business objects, actions) can be imported into customer specific one off solutions or multi customer solutions which enables to rapidly start development.
For ex – you can create a solution template with reuse libraries, or industry specific objects and later during development import it into specific customer solution.
Solution templates cannot be directly deployed in a productive tenant. It must be imported into customer solution and deployed to production.
1.2. Use cases
A partner who has several customers with similar functionality can create a solution template and include and organize the common objects which are needed for all the customers. The partner then can create customer specific solutions in customer/partner tenant and import the solution templates. By this the partner saves time/effort because there is no need to develop the common objects for each customer again.
Customers can also use solution templates, e.g. if they have different tenants for subsidiaries in different countries, then a customer specific solution might be quite similar in all these tenants except some country specific parts.
1.3. Main differences to customer-specific solutions
- No native extensibility with extensibility framework (no enhance forms/report/screen,...)
- No analytics content
- No Mashup
- No BC set using SAP BCOs
- No lifecycle, no patch solution, always in version 1
- BAC element not mandatory, but optional
- Can be imported into solutions of different customers
- No upload of template to productive tenant
- Re-import of template overwrites the target artifacts
1.4. Lifecycle:
1.4.1. Create Solution template
In the studio use the ‘Create Solution’ button and then choose Solution Type ‘Solution Template’.
Once the solution is created, you can add the content and activate the solution template.
1.4.2. Check in All files:
Right click on the solution and check in.
1.4.3. Assemble and download the template:
From the menu, open “View”->Implementation Manger.
Implementation Manger, Click Assemble and Download ( can also be done from Implementation manager toolbar)
1.4.4. Import Template:
When the template has been created, assembled and downloaded as a zip file, create or select a customer-specific solution or multi-customer solution as target solution. The template (zip file) can be imported into the target solution. Afterwards the target solution contains the objects of the template.
1.5. Note:
The solution template and the solution, into which you import the items of the template
- must be based on the same cloud solution from SAP
- must have been created for the same deployment unit. However, if you have created your solution template in the Foundation deployment unit, the solution can have any deployment unit.
You can import a solution template into the studio version in which it has been created and into the two subsequent versions. For ex : if you have an exported template (zip file) of 1711 version, you can import it in 1711, 1802, 1805. This is validation is only in case the file is locally downloaded. However, if it was in the system, it would have automatically upgraded with standard upgrade.
If an item in the solution has the same name as in the template, the system replaces the item in the solution with that of the template.
Please note the following exceptions:
- If an item with the same name exists in another folder of the solution, the system doesn't import the item.
- If the template contains a BAC element and the solution already has a BAC element, the system doesn't import the BAC element of the template.
New solution type as you cannot change the customer ID of a solution (neither in studio nor as backend report) partner must choose solution type at the beginning if content shall be reusable.
- SAP Managed Tags:
2 Comments
