Tenant Creation Scenarios – ByD/C4C
The standard SAP Business ByDesign, Cloud for Customer and Cloud for Travel and Expense subscriptions include:
•Test tenants
•Productive tenants
New tenants can be requested by a user via the Service Control Center work center, Systems view.
When you click on button Request Creation, a pop-up will be displayed where you can choose the System Type of the system for which you will request.
Users can also Request System via Business Configuration Work center, Implementation projects view.
In standard, all the Enterprise Support Cloud Editions customers are entitled for one test tenant per production tenant.
Production System can only be requested in two types:
- Initial System
- Initial System (Copy Solution Profile)
Test System can be requested in four types:
- Initial System
- Initial System (Copy Solution Profile)
- Copy Source System
- Copy Source System (Copy Solution Profile)
In the Data Source Field , you will find Four options to choose from, Below we can see the options and the description (what it is meant for):
1. Copy of Source System :
This option will provide you a 1:1 copy of your source system, it means: copy of all scoping and master data of the source system.
Basically it will provide a clone of the source system. This option is useful when you want to have a permanent test system to do tests, but don’t intend to replicate the changes to your production. This option cannot be used for a change project scenario. It is not possible to merge the changes made in the test system back to your production system.
Production system requests are not allowed since it is not possible to request production systems with Master Data. The extension data (extension fields) is copied only in this option.
2. Copy of Source System (Copy Solution Profile) :
This option will provide you a new system with full data and with a particular solution profile (Implementation Project) to be deployed in the new test tenant. This option should be used for change project testing scenario. Production system requests are not allowed for this this option since it is not possible to request production systems with Master Data.
With this option it is possible to have a new test system which has production tenant data(Master & Transactional) and solution profile from a test system, to have such a test system, you will need to choose production tenant as a source system ID and you can choose a existing test tenant from which the solution profile need to be selected in solution profile source system ID and then you can choose the solution profile ID which you want to copy.
3. Initial System :
This option provides you an empty system, without master and scoping data.
Production system requests are allowed for this option.
4. Initial System (Copy Solution Profile)
This option provides you an empty system without master data with a particular solution profile (Implementation Project) to be deployed in the new tenant. L0 Data will also be copied in case of production tenant request.
- L0 Data is uploaded to the Migration Workbench Staging area and is not automatically committed to the tenant
- L0 Data can be reviewed, edited and even entered in staging, manually or using templates. Be aware that raw data entry and elaborate migration scenarios do require expert knowledge.
- Data upload can and should be simulated before uploading and so committing to the Production Tenant
Production system requests are allowed for this option.
Above are the four options that will guide the users to choose the system options correctly and proceed with the tenant creation request. Apart from this we also have an option for Copy solution profile between the existing tenants:
Users can now copy the solution profile (i.e. business configuration) from existing tenant A to existing tenant B via the Service Control Center work center, Systems view. This opens new possibilities for change projects when a customer has purchased an additional test tenant. The user can create a change project in the production tenant, request the solution profile copy to the additional test tenant, configure and test the new solution in the additional test tenant and then merge the configuration changes back into the production tenant. Only a test tenant can be selected as the target tenant for a solution profile copy – it is NOT possible to copy a solution profile to the production tenant.
Often , Users wants to know exactly which data will be copied, will their customization will be copied or not , So in the below tenant creation matrix, you will be able to understand all the present tenant creation scenarios and possibilities.
Kindly refer to the SAP Knowledge Base Article ID: 2136036 – How to Request a New System to know the specific details of data which is copied.
I hope this document will give a clear picture of the system options available for the tenant creations.
Thanks,
Shashank Singor
Can you confirm if the Level 0 data - Locations include the logistics layout under it in the solution profile copy?
Hello Olivia,
Further you can refer the KBA: 2136036 - How to request a New Tenant for SAP Business ByDesign or SAP Cloud for Customer from Service Control Center.
Regards,
Ankit K
Hello,
Can you explain which option should be used if we want to copy one test tenant in another tes tenant (but not from customer, from Partner in order to have different teams working on different solution versions but with the same config.+master data involved, can we do that?). Thank you in advance. Regards.
Hello Rosa,
Only customer purchased systems are listed in the Systems view under Service Control Center work center and only those systems can be chosen as source tenants, partner systems are not listed in the systems view hence you can not request.
Further, if you are eligible for additional test tenants you can select Copy of Source system in the Data Source field.
Further request you to refer the KBA: 2136036 - How to request a New Tenant for SAP Business ByDesign or SAP Cloud for Customer from Service Control Center.
Regards,
Anki K
Hello,
Does communication system, communication arrangement and communication scenario gets copied across as well while copying from test to Prod tenant ? If not, is there anyway to achieve this or communication system, communication arrangement and communication scenario need to be redone in Prod tenant ?
Regards,
Jay