SAP Knowledge Base Article - Public

2136036 - How to Request a New System

Symptom

You want to request a new Test or Production tenant but do not know how what option to select or how to request it.

Environment

SAP Business ByDesign, SAP Hybris Cloud for Customer

Reproducing the Issue

  1. Go to Service Control Center work center
  2. Select the Systems view
  3. Select Request Creation
  4. You have different options for tenant request scenario

Resolution

We have provided the details of the tenant request scenario in this document.

Note:

Details of the types of data in this document:

   1. Configuration Data:

       Scoping and Fine Tuning stored in the Implementation Project in the Business Configuration workcenter in SAP Business ByDesign or SAP Hybris Cloud for Customer system.

   2. Flexibility data:

       Customizations such as extension fields in SAP Business ByDesign or SAP Hybris Cloud for Customer system.

   3. Level 0 data, Master Data include the following objects in SAP Business ByDesign system:

  • Locations
  • Job Definitions
  • Organization Structure
  • Transport Lanes
  • Transport Zones
  • Bank Directory
  • Product Category Hierarchy

   4. Level 0 Data, Master Data include the following objects in SAP Hybris Cloud for Customer system:

  • Job Definitions
  • Organization Structure
  • Product Category Hierarchy   

 

Production system request scenarios:

For production system request, only the below scenarios are allowed. This is because production systems cannot be requested with full master data copy.

1. Initial Production Tenant / Empty Production System

Data Source: Initial System        

This is relevant for initial implementation. This can be used after go-live but no merge back capability.

In this case, no solution profile nor data are copied from Source system (Test system) to the Target system (Production system).

  • Business Configuration settings: No
  • Level 0 data: No
  • Flexibility data: No
  • Transactional data: No
  • PDI Solutions created in the test tenant must be uploaded again in the Production Tenant.

 

2. Production Tenant with Solution Profile Copy from Test Tenant

Data Source: Initial System (Copy Solution Profile)

In this case, data is copied from the Source system (Test Tenant) to the Target system (Production Tenant). No merge back capability.

  • Business Configuration settings: Yes
  • Level 0 data: Yes
  • Flexibility data: Yes
  • Transactional data: No 
  • PDI solutions created in the Test Tenant must be uploaded again in the Production Tenant and scoped in Business Configuration. They are not copied automatically.

When a solution profile is copied to a new production tenant, the following additional activities automatically occur:

  • Extension fields and screen layout adaptations made via key user tools are copied as long as there are no extension fields and/or screen layout adaptations already made in the new production tenant
  • Form adaptations are copied
  • Level 0 data, master data is copied to a staging area where the user can choose to import the pre-populated data migration templates or ignore them.  

 

Test tenant request scenarios:

1. Initial Test Tenant / Empty Test System

Data Source: Initial System

This is relevant for initial implementation. This is used after go-live but no merge back capability.

In this case, no solution profile nor data are copied from Source system [Test Tenant] to Target system [Test Tenant].

  • Business Configuration settings: No
  • Level 0 data: No
  • Flexibility data: No
  • Transactional data: No
  • PDI solutions present in the Source Tenant must be uploaded again in the Target Tenant.

 

2. Initial Test Tenant with Solution Profile

Data Source: Initial System (Copy Solution Profile)

Business Configuration settings are copied from the Solution Profile ID mentioned in the request. The Solution Profile ID corresponds to the Implementation Project in the Business Configuration workcenter that is to be copied. This Solution Profile is deployed into the Target tenant, that is, the scoping and fine tuning done in the Solution Profile is activated in the Target tenant. No merge back capability.

No data is copied from Source system [Test Tenant] to Target system [Test Tenant].

  • Level 0 data: No
  • Flexibility data: No
  • Transactional data: No
  • PDI solutions present in the Source test tenant must be uploaded again in the Target test tenant.

 

3. Copy of Source Tenant

Data Source: Copy of Source System

This is a complete copy of the Source system [Test/Production]. This option allows you to create change projects in the target test system.

It is useful when you want to have a permanent test system to do tests, but do not intend to replicate the changes to your production. This option cannot be used for a change project scenario. That is, it is not possible to merge the changes made in the test system back to your production system. In this case, there is no connection to productive tenant.

  • Can only be test system type
  • Triggers full copy (with solution profile and data) of a single source tenant 
  • Can be relevant for initial implementation
  • Could be used after go-live but no merge back capability

All scoping and master data are copied from the Source to the Target tenant.

  • Business Configuration settings: Yes
  • Level 0 data: Yes
  • Flexibility data: Yes
  • Transaction data: Yes
  • PDI solutions present in the Test/Production are also copied to the Target Test tenant.

Note:

Source tenant must be taken down for 4 hours outside of the normal maintenance window.

Recommended for data migration testing when initial test tenant cannot be used

 

4. Copy of Source Tenant (Copy Solution Profile):

Data Source: Copy of Source System (Copy Solution Profile):

This is a new Test tenant as copy of production where, the test tenant will have the production data with change project solution profile.

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.

This is the Test tenant creation with change project functionality such as merge back of changed business configuration, where upon completion of the configuration and testing in the Test tenant, the Change Project is merged back to the Production.

All scoping and master data including the source solution profile will be set as main in the target tenant and deployed.

Below are copied from the Source system [Test/Production Tenant] to the Target system [Test Tenant].

  • Business Configuration settings: Yes
  • Level 0 data: Yes
  • Flexibility data: Yes
  • Transaction data: Yes
  • PDI solutions present in the Source Tenant must be uploaded again to the Target Tenant.

Note:

A downtime of 4 hours is required for source tenant, which is outside of the normal maintenance window.

Recommended for requesting new change project test tenants

If a test tenant hosts an already copied/active change project, no other change project can be copied to this test tenant unless the change project is Cancelled or completed. 

 

Additional Information

  • Once the customer signs up with SAP, Test tenant is delivered to the customer.
  • To get a new reference system (demo tenant), partner should send an e-mail to CloudPartnerEdge@sap.com . Upon receipt of this e-mail, the relevant team will send a form to the partner, and they will be required to fill the same. Once the form is received, the partner edge team will create the ICP request and the process will be driven by the SAP Cloud Operations team, until the tenant provisioning is completed.
  • If Partner want to have a Partner tenant either to use it for demo to the client or to test the ruggedness of the product, Partners should send an email to CloudPartnerEdge@sap.com . Once the request is received, the concerned team will validate the request based on the contract and the requirement and will further proceed by delivering the Tenant to the Partner.

 

Restrictions During Upgrade

  • Business Configuration is possible at any time in both test and productive tenant but without data transfer between the tenants. 
  • Incidents will no longer be closed as part of the upgrade process.
  • No merge back for Change Projects possible while test tenants are upgraded, and production tenants are not

 

SAP strongly recommends the following:

  • Do not terminate or request a test tenant or productive tenant during the time between Test-Upgrade and Productive-Upgrade
  • Avoid a Go-Live during this phase during the time between Test-Upgrade and Productive-Upgrade
  • Avoid applying SAP Cloud Applications Studio add-ons during the time between Test-Upgrade and Productive-Upgrade
  • No productive data transfer (migration) during productive upgrade weekend. Therefore, do not perform any migration activities during the upgrade weekend.
  • When system upgrades are planned for test and production system, do not request new tenants (2 days before the start of the test system upgrade and 2 weeks before the upgrade of production system). 

See Also

For further information you may refer blog

Keywords

Tenant request, Request test system, Request Production system , KBA , tenant request , system request , AP-RC-BCT , Business Config. Tools (SAP Business ByDesign , How To

Product

SAP Business ByDesign all versions ; SAP Cloud for Customer all versions

Attachments

how to request a new system_CN.pdf