The initial tenant provided to the customer is the Test Tenant. Once the relevant stage is reached in implementation, the Production Tenant can be requested from the Service Control Center Workcenter (WoC) -> Systems WoC View
[
Explanation for the different kind of data mentioned in the Blog Post are as follows
1) Configuration Data : Scoping and Fine Tuning stored in the Implementation Project in the Business Configuration WoC.
2) Level 0 Data ; Master Data incluidng the following objects
I. Locations
ii. Job Definitions
III. Organization Structure
IV. Transport Lanes
V. Transport Zones
VI. Bank Directory
VII. Product Category Hierarchy
3) Flexibility data : Customizations such as extension fields
]
Tenant options for Production Tenant Request
1. Initial Production System
In this case, data (Configuration, Level 0 and Flexibility) is not copied from the Source system (Test Tenant) to the Target system (Production Tenant). No transactional data is copied.
PDI Solutions :PDI Solutions created in the test tenant have to be uploaded again in the Production Tenant.
2. Production Tenant with Solution Profile Copy from Test Tenant.
In this case, data (Configuration, Level 0 and Flexibility) is copied from the Source system (Test Tenant) to the Target system (Production Tenant). No transactional data is copied
PDI Solutions : PDI solutions created in the Test Tenant have to be uploaded again in the Production Tenantand scoped in Business Configuration. They are not copied automatically.
Tenant Options for Test Tenant Request
1. Initial Test Tenant
In this case, data (Configuration, Level 0 and Flexibility) is not copied from Source system [Test Tenant] to Target system [Test Tenant].
No transactional data is copied.
PDISolutions : PDI solutions present in the Source Tenant have to be uploaded again in the Target Tenant.
2. Initial Test Tenant with Solution Profile
In this case, Level 0 data and Flexibility data is not copied from the Source system [Test Tenant] to the Target system [Test Tenant]. However, the Configuration data is copied from the 'Solution Profile Id' mentioned in the request. The 'Solution Profile Id' corresponds to the 'Implementation Project' in the Business Configuration WoC that is to be copied. This 'Solution Profile' is deployed into the Target tenant, i.e the scoping and fine tuning done in the 'Solution Profile' is activated in the Target tenant.
No transactional data is copied.
PDI Solutions : PDI solutions present in the Source test tenant have to be uploaded again in the Target test tenant.
3. Copy of Source System
This is a complete copy of the Source system [Test/Production] (ie Configuration, Level 0 and Flexibility data) to the Target Test Tenant.
Transaction data is also copied from the Source to the Target tenant.
PDISolutions : PDI solutions present in the Test/Production are also copied to the Target Test tenant.
4. Copy of Source system with Solution Profile.
In this case, Level 0 data and Flexibility data is copied from the Source system [Test/Production Tenant] to the Target system [Test Tenant]. However, the configuration data is copied from the 'Solution Profile Id' mentioned in the request. The 'Solution Profile Id' corresponds to the 'Implementation Project' in the Business Configuration WoC that is to be copied. The 'Solution Profile' is deployed to the Target tenant, i.e. the scoping and fine tuning done in the selected 'Solution Profile' is activated in the Target tenant.
Transactional data is also copied from the Source to the Target tenant.
PDI Solutions: PDI solutions present in the Source Tenant have to be uploaded again to the Target Tenant.
This option is used after Go-Live for Remote Change Projects.The Change Project 'Implementation Project' should be provided in the 'Source Solution Profile Id' during request. On completion of the configuration and testing in the Test tenant, the Change Project is merged back to the Production.