In this unit, we will be discussing types of solutions, what they are, and how we can use each of them. SAP ByD Solution Type
SAP ByD Solution Type
What is a Solution?
A solution is the package of development for the SAP Cloud Applications Studio. It will have the collection of different development objects that you will build and create and maintain. And then we can move this content to another tenants, whether it be a test or production, etc.
Solutions are packages of development items
Three solution types:
- Solution Template,
- Customer-Specific Solution,
- Patch Solution.
- In a solution template, you can create all development content that you want to reuse in a customer-specific solution, for example business objects, actions, and events. This allows you to easily start the development of customer-specific solutions by reusing common development content.
- The development of a solution template would continue through different upgrades. So if you have a solution template you can continue to maintain it through each release. So we can continue to be updated and deployed over and over again.
- When you have completed your template, you must download it to be able to import it into a solution. A template always has the status In Development and therefore you don’t need to create a patch of a template. When you create a new solution or open an existing solution or a patch, you can import the items of your template into this solution or patch.
What you can’t do with a Solution Template
- You can’t switch on the admin mode for a solution template. Therefore, you can’t define analytics content or create a mashup in a solution template.
We will see the admin mode in later article
- You can’t create BC sets using SAP BCOs in a solution template.
- If you create a business object extension in a solution template, you can’t use the following functions:
- Enhance Enterprise Search
- Enhance Forms
- Enhance Report
- Enhance Screen
What you need to know when you import a Solution Template
- The solution template and the solution, into which you import the items of the solution template, 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 example:
[table id=5 /]
Create a Solution Template
- Logon into SDK.
- On the Administration toolbar, click Create Solution icon( ).
The Create Solution dialog box opens.
- Select the Solution Template type.
- Enter the customer and a description for the solution template.
- Select the deployment unit in which you want to create your template and click OK.
- Enter your contact information and click OK.
Your solution template is created.
Download a Solution Template
When you have completed your template, you need to download the template before you can import its items to a solution.
- In the studio, log on to the tenant where you created the template, and open the template.
- In the Solution Explorer, right-click the template and select Check In All Files.
- Select Administration -> Implementation Manager.
- On the Implementation Manager toolbar, click the Assemble and Download button.
- Enter a file name to save the template as a .zip file locally.
The system checks the template for consistency and then downloads all the items in the template to
the .zip file.
Import Items of a Solution Template
After you have downloaded a solution template, you can import this template to add its items to any of your solutions.
- Log on to the tenant where you want to import the items of your template to a specific solution.
- Create a new customer-specific solution or open an existing solution. Please note that the solution must have the status In Development.Please note that the solution template and the solution, into which you import the items of the solution
template, 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.
- In the Implementation Manager, click the Import Solution Template button and select the.zip file of the template that you have downloaded before.
The items of the template are added to the solution.
Customer Specific Solution
- This is the main type of solution that we’ll work with in the Cloud Applications Studio.
- You can design and develop customer-specific solutions to enhance SAP’s standard cloud solution for a specific customer. In the studio, you can create a solution in which all items that you develop or changes that you make to existing entities are stored.
- It’s a solution that’s only for one particular customer. For example, if I develop something for customer A, I cannot take that same customer-specific solution, and deploy it to customer B’s tenant.
- This type of reuse of a customer-specific solution is not allowed. If I have that type of scenario, I would want to use a solution template, in which case I would develop a solution template, and then I could apply it to customer A’s tenant as well as to customer’s B’s tenant. So a customer-specific solution, it can contain any kind of content, including anything that requires Admin Mode. And then I can apply that to a customer’s production tenant or to other test tenants.
Create a Customer Specific Solution
- Logon into SDK
- On the Administration toolbar, click Create Solution Icon( ).
The Create Solution dialog box opens.
- Select the Customer-Specific Solution type.
- Enter the customer and a description for the solution.
- Select the deployment unit in which you want to create your solution and click OK.
- Enter your contact information and click OK.
Your solution is created.
This relates to a customer-specific solution. A patch is needed if you want to make changes or corrections to a customer-specific solution after it has been assembled. The customer-specific solution is in maintenance mode and you can only make restricted changes for certain content types.
In Future article, we will go deep into what a patch solution really is, what all it can contain, and the development within patch solution.
Create a Patch
- On the Implementation Manager toolbar, click the Create Patch button.The system creates a patch solution and copies all files in your solution to a new namespace within the patch solution. The namespace is generated automatically and cannot be changed.
The patch solution is created in the background and this process may take some time. Click Refresh in the Implementation Manager tool window to update the solution status.
- In the Implementation Manager, open the patch solution by clicking the Open button next to the Patch Solution field.
- In the patch solution, make your changes. Then activate the patch solution.
- You can test specific solution content in the studio using the preview function. To test your patch solution in the SAP cloud solution, you have to enable the solution on the test tenant as follows:
- In the Implementation Manager, click the Enable button next to the Solution Enablement for Business User in Cloud Solution field. The “Disabled” changes to an “Enabled” and the patch solution is enabled on the test tenant instead of the original solution.
- In the SAP cloud solution, log on to the test tenant with your business user. You will be able to see your patch solution in place of the original solution.
- Complete your testing.
- On the Implementation Manager toolbar, click the Assemble and Download button. The system assembles the patch using the namespace of the original solution and downloads it to a .zip file. This allows you to copy your corrections back to the original solution.
- In the studio, log on to the production tenant on which the original solution is active, and click the Upload button on the Implementation Manager toolbar.Select the .zip file containing the patch. The system uploads the .zip file with your corrections and checks for any compatibility issues. The solution has the status In Deployment and the solution version number is updated.
- In the Implementation Manager, select the solution and click Activate.
A customer-specific solution is in maintenance mode, if it has been assembled and downloaded; the solution status is Assembled. You can make changes to the solution in a patch; however, you can only make restricted changes to certain content types. These change and delete restrictions ensure that you do not make changes to a solution that could lead to loss of data or create inconsistencies or errors on a customer’s production tenant.
When your solution is in maintenance mode, you can delete the following items:
- Business Configuration Object
- Business Configuration View
- Code List Data Type
- Embedded Component
- Script File (ABSL)
- Web Service
- Mass Data Run Object
- UI Switch
- Tax Decision Tree
- customer-specific fields
- data source created by an administrator in the cloud solution
- key figure created by an administrator in the cloud solution
That’s all about Basic of the SAP Cloud Application Studio. In upcoming article, we will discuss about Detailed view of SAP Business ByDesign.
Don’t forget to subscribe and leave your comment to improve this article.