2136036 - How to Request a New Tenant for SAP Business ByDesign or SAP Cloud for Customer

 "Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

You want to request a new test or productive tenant, but do not know which option to select or how to request it.

• SAP Business ByDesign
• SAP Cloud for Customer

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

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 Cloud for Customer system.

   2. Flexibility data:

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

   3. Level 0 data, Master Data include the following objects in SAP Business ByDesign (ByD) 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 Cloud for Customer (C4C) system:

• Job Definitions
• Organization Structure
• Product Category Hierarchy   

Tenant request can be triggered from Service Control Center work center by following the below steps:

1. Log in to the Tenant. 
2. Go to the Service Control Center work center.
3. Click Systems view.
4. Select the system and click Request System.
5. In the popup window, select the details as shown in the below screenshot and click Ok.

Productive system request scenarios:

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

1. Initial Productive System / Empty Productive 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 Tenant (Test Tenant/Productive Tenant) to the Target Tenant (Productive Tenant).

• 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 Productive Tenant.

Note: No Downtime required for the Productive tenant setup.

2. Productive 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/Productive Tenant) to the Target system (Productive Tenant). No merge back capability.

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

When a solution profile is copied to a new productive 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 productive tenant
• Form adaptations are copied
• In Business ByDesign tenant, the 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.  
• In Cloud for Customer tenant, the data are not copied to a staging area, but are directly imported to the target (productive) tenant.
• Also Business Users will not get copied to the new Productive Tenant.

 Note: No Downtime required of Source system for the Productive tenant setup.

 

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.

 Note: No Downtime required for the Productive tenant setup.

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.

 Note: No Downtime required of Source System for the Productive tenant setup.

3. Test Tenant as 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. It is not possible to merge the changes made in the test system back to your production system.

• Can only be test system type.
• Triggers full/clone 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 1:

• 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.

Note 2:

If the user only requests a new test tenant via “Copy of Source Tenant” then you get a “Standalone test tenant” without connection to the production tenant.

 

• Select Copy All Attachments to include Attachment tables in the copy. This is excluded by default(recommended). Selecting this option will drastically increase the source downtime required for tenant copy.

• Choose Copy Change Documents to include Platform Change Document in the copy. This is excluded by default(recommended). Selecting this option will drastically increase the source downtime required for tenant copy.

Note 3:

If you want to create a 1 to 1 copy of the productive system, it is probably best to choose data source "Copy of Source System". This would then also include the BC solution profile without having to specify that explicitly, but also all other data such as runtime data.

If this is not desired outcome and you only want to copy the solution profile (and maybe some other data), then probably the user first needs to create the new system as initial system, then implement all the partner PDI solutions in the created target system.

Later, trigger the copy of the BC solution profile as separate process, by copying the BC solution profile including the configuration for the partner solutions that only works if the partner solutions match in both the tenants.

4. Remote Test Tenant with Solution Profile

Data Source: Copy of Source System (Copy Solution Profile) (Not directly selectable. See below information)

• This process results in a new Test Tenant as Copy of Production where, the Test Tenant will have the production data and a Change Project Solution Profile.
• This option is used after Go-Live for Remote Change Projects. On completion of the configuration and testing in the Test tenant, the Change Project is merged back to the Production.

This scenario cannot be enabled within one step, but by the following way:

1. Request a new Test Tenant via scenario Copy of Source Tenant first.
2. After the tenant is delivered, start the copy of a change project via button Copy Solution Profile.

After the change project is copied to the test tenant, the Remote Change Project scenario with Merge Back functionality is enabled. (If only a new test tenant via Copy of Source Tenant is requested, a standalone test tenant without connection to the production tenant is done).

Note:

• This replaces the former, combined process Copy of Source Tenant (Copy Solution Profile). 
• Also if the test tenant already exists, Copy Solution Profile can be used to copy the change project to the test tenant and to enable the Remote Change Project scenario with Merge Back functionality.

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). 

Restriction regarding tenant types:

New tenant request process is only available for customer tenants. This functionality is NOT supported for demo, reference or partner development tenants.

Important Note: 

• Initial User Credentails will only be sent in the scenario's Tenant Type Test & Production and Source as Initial System & Initial System Copy Solution Profile, and these credentails will be sent to available IT Contacts from the Contacts under Service Control Center work center.
• Initial User credentails will not be sent when you request new test tenant with source as Copy of Source system, it is advised to use the same Business User ID and passwords as of your source system.
• If you still want to reset the Initial User ID password in the second scenario, you can raise the incident to SAP Support with the details.

For further information please refer the below links:

Blog: Tenant Creation Scenarios – ByD/C4C.

C4C Customer Experience Wiki: Requesting a new tenant

Tenant request, Request test system, Request Production system, C4C tenant, ByD tenant , KBA , new tenant , new system , production tenant , test tenant , tenant request , system request , SRD-CC-CI-CCS , ByD Service Control Center , LOD-CRM-ADM , Administration UI , AP-RC-BCT , Business Config. Tools (SAP Business ByDesign , How To

SAP Business ByDesign all versions ; SAP Cloud for Customer add-ins all versions ; SAP Cloud for Customer core applications all versions