cloud tenant landscape

R1308 Tenant Landscape

October 2013

R1308 Changes Overview

Please hold all questions until the end of the presentation

© 2013 SAP AG. All rights reserved. 3

Limitations for Number of Test Tenants

Beginning with r1308, the number of “work” test tenants allowed per customer is limited to one per productive tenant.* This is in effect for SAP Business ByDesign, Cloud for Customer, Cloud for Financials and Cloud for Travel and Expense customers.

* The number of production tenants purchased via Enterprise Standard Edition (multiple productive tenants purchasable) and Enterprise Private Edition (package with maximum of ten productive tenants) subscriptions are taken into account.

For the purpose of this presentation, there are two types of test tenants: Work test tenants: Temporary test tenants that are available free of charge and

meant for managing the lifecycle of the SAP Cloud solution (i.e. implementations, training, change projects, etc.)

Permanent test tenants: Test tenants that are purchased separately by the customer, have no expiration date and are used to manage integration and/or customizations using SAP Cloud Applications Studio


Selling Permanent Test Tenants

Permanent Test tenants need to be purchased as usual as an additional material number in the quote.

Customers can order more than one permanent test tenant SAP Cloud for Customer: A permanent test tenant is purchased with material number

8000567 (Cloud for Customer, Test Tenant) or with 8000660 (360 Customer, on-demand version bundle, which includes one 8000567). The permanent test tenant (8000567) is required when integration is in scope and/or the project requires customization via the SDK (8000570, now called SAP Cloud Applications Studio).

SAP Cloud for Travel and Expense: A permanent test tenant is purchased with material number 8000094. It is recommended when integration is in scope and/or the project requires customization via the SDK.

SAP Business ByDesign and SAP Cloud for Financials: No product code exists for permanent test tenant

It is NOT possible for a customer to purchase an additional test tenant on a temporary basis (i.e. “work” test tenant).

Please direct all questions related to selling permanent test tenants to SAP Cloud Sales Operations.


New Functions in Service Control Center Work Center

Three new functions have been introduced in the Systems view in order to enable the new tenant processes for customer tenants only*: “Request Creation” of a new tenant “Request Termination” of an existing tenant “Copy Solution Profile” from one tenant to another

* Other types of tenants, such as internal tenants, cannot use the SCC work center to request/terminate tenants.


Controls

If a user submits a tenant request via the Service Control Center (SCC) work center which results in the customer exceeding his allotted number of tenants, then an error message will be returned that an existing tenant must be decommissioned first.

An exception can be requested via an incident from your SAP Cloud solution. Please note:

Incident must include source tenant URL, decommissioning date for new tenant and why the exception is being requested (turnaround time depends on incident priority and if all details are included in the request)

SAP Cloud Hosting will request approval from Platinum Engineering prior to fulfilling the request (will take one business day in CET)

Examples of exceptions:

1. Prior to cutting over in the production tenant, the financial data migration must be fully tested in a tenant that has no transactions

2. Customer’s go-live is dependent on new functionality in the latest release, requiring you to install a new release now instead of waiting until scheduled upgrade

3. A new installation is required to mitigate risk of customer’s go-live and upgrade occurring around the same time

Refer to Appendix A for examples of when tenants are requested and limits are applied.


R1308 Tenant Provisioning Changes

# In r1305 and prior Effective starting with r1308

1 First customer tenant that was handed over after subscription was booked was the production tenant

First customer tenant that is handed over after subscription is booked in CRM@SAP is test tenant which cannot be set live

2 Some implementations request a new production tenant during the implementation to replace the initial production tenant

All implementation projects must request a production tenant since the initial tenant is now a test tenant

3 Additional tenants are requested via the Request System button under Business Configuration

Request System button is automatically redirected to new UI in the SCC work center

4 A customer’s test and production tenants reside on the same system

Process is the same for SAP Business ByDesign and Cloud for Financials. SAP Cloud for Customer and Cloud for Travel and Expense customer’s test and production tenants are on separate systems.


R1308 Tenant Decommissioning Changes

In r1305 and prior Effective starting with r1308

Test tenants are automatically triggered for decommissioning (in 14 days) once the “Close Project” activity is completed

Tenants are no longer automatically triggered for decommissioning; a user must request termination via SCC work center

Initial production tenant is automatically triggered for decommissioning (in 14 days) after a new system request is submitted for a replacement production tenant

Tenants are no longer automatically triggered for decommissioning (but a replacement production tenant is no longer relevant for implementations)

Implementation Tenant Landscape

Starting with r1308


VERIFYPREPARE REALIZE LAUNCH

1 Configure solution 4 Request production tenant 7 Cutover to production (inc. DM)2 Configure test integration 5 Reload level 0 data & finish FT

3 Test data migration & scenarios 6 Configure production integration

Implementation Cloud System Landscape 2 Tenants Implementation

CLOUD TEST TENANT

CLOUD PRODUCTION TENANT

C

1 3 4

5

C

C C

ON PREMISE QA SYSTEM ON PREMISE PRODUCTION SYSTEM

C

67

C

2

C

ScopeVerification

SolutionAcceptance

ReadinessAcceptance

Go-Live

Sub-scription booked


For Step 4 in Previous SlideRequest Production Tenant

First, click Request

Creation button

Then select:• Solution Profile Source System

ID = test tenant• Source Solution Profile ID =

always Initial Implement

Refer to Appendix B for more details related to this type of system request.



1 Configure solution, inc. integration 4 Request new tenant as full copy 7 Configure production integration2 Request production tenant 5 Configure test integration 8 Update required config changes

3 Reload level 0 data & finish FT 6 Test data migration & scenarios 9 Cutover to production (inc. DM)

Implementation Cloud System Landscape3 Tenants Implementation Recommended Approach

CLOUD TEST TENANT #1


3 4

756


2


C C

C

C

C

ScopeVerification Solution

Acceptance

ReadinessAcceptance

Go-Live

C

C C


8

1

9

C




Creation button


ID = test tenant #1• Source Solution Profile ID =




For Step 4 in Previous SlideRequest New Test Tenant as Copy of Production

Then select:• Data Source = production tenant


Creation button




1 Configure solution 4 Enter level 0 data & communications; finish FT 7 Reload level 0 data & finish FT2 Configure test integration 5 Test data migration & scenarios 8 Configure production integration

3 Request new test tenant 6 Request production tenant 9 Cutover to production (inc. DM)

Implementation Cloud System Landscape3 Tenants Implementation Alternative Approach



12

78

9

5 6


3


C C

C

C

C

C

ScopeVerification Solution

Acceptance

ReadinessAcceptance

Go-Live

C

C C


4


For Step 3 in Previous SlideRequest New Tenant with Solution Profile only

Then select:• Source System = test tenant #1• Source Solution Profile ID =

Initial Implement


Creation button

Test System





Creation button


ID = test tenant #2• Source Solution Profile ID =




Copy Solution Profile Behavior

When a solution profile is copied, the following behavior occurs:

1. Scope is copied

2. All fine-tuning settings that have a Repetition Required setting of No are copied, for example:

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

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

B. Form adaptations are copied

C. Level 0 master data is copied to a staging area where the user can choose to import the pre-populated data migration templates or ignore them. This includes the objects:

Bank Directory Org Structure Transport Zones

Jobs Product Categories Transport Lanes

Tenant Landscape After Go-Live

Starting with r1308


After Go-Live

After the SAP Cloud solution is live for productive use:

1) The “First Implementation” project should be closed in the Business Configuration work center, and

2) A termination request should be submitted for all “work” test tenants (not permanent test tenants)

First, select the tenant

Then click Request Termination button and the tenant will be set to

"DIP - decommissioning in progress" immediately


Request Termination Details

Only tenants with a System Type = Test can be terminated

At least one tenant has to remain per solution and customer (i.e. cannot delete initial test tenant if production tenant not yet created)

Proceed with caution: Partner solutions in the terminated tenant cannot be retrieved after termination

Decommissioning is started immediately with physical deletion in 14 days

Once submitted, the termination request cannot be retracted via the UI; instead, open a very high incident from your SAP Cloud solution (note this is applicable only if physical deletion has not yet occurred)

Once the termination request is submitted, the tenant no longer counts towards the customer’s tenant allotment

Recommended when the test tenant allotment is reached and a new test

tenant is needed


Configuration Changes After Go-Live

Going forward, configuration changes are made one of two ways:

a) Minor changes can be made immediately, or

b) More complex changes must be made via a change project, which is a control that is introduced to mitigate risk to the live SAP Cloud solution

The subsequent slides provide tenant landscape options for change projects when a test tenant is (optionally) used.


Option 1: New Test Tenant as Copy of Production

CLOUD PRODUCTION TENANT 1

3 4 5

72

Solution profile & flex/ex copied & deployed

6

1 Create change project (CP), selecting scope and activities 7 Modify key user access rights; Perform adaptation; Migrate basic and master data

2 Request new test tenant linked to change project solution profile 8 Complete re-opened fine-tuning activities

3 Complete configuration 9 Activate solution4 Test data migration 10 Migrate transaction data; Modify end user authorizations5 Test end-to-end scenarios 11 Close change project ; Go live with new solution6 Merge solution profile 12 Request deletion of change project test tenant

8 9 121110Access to change project activity list

prohibited

Access to change project activity list prohibited

Performed during scheduled business downtime

NEW CLOUD TEST TENANTHas production data with change project solution profile




For Step 2 in Previous Slide…


Creation button

Then select:• Data Source System ID =

production tenant• Solution Profile Source System

ID = production tenant• Source Solution Profile ID =

change project



ON PREMISE QA SYSTEM

Option 2: Re-Use Existing Test Tenant

PERMANENT CLOUD TEST TENANT


3

4

5

ON PREMISE PRODUCTION SYSTEM

72


Solution profile is linked to CP 6

1 Create change project, selecting scope and activities 7 Modify key user access rights; Perform adaptation; Replicate/Migrate basic and master data

2 Request change project solution profile be linked to test 8 Complete re-opened fine-tuning activities

3 Complete configuration 9 Activate solution4 Refresh On Premise data (optional) 10 Replicate/Migrate transaction data; Modify end user authorizations5 Test data replication/migration; Test end-to-end scenarios 11 Close change project6 Merge solution profile 12 Go live with new solution

8 9 121110




Performed during scheduled business downtimePerformed during scheduled business downtime



First, click Copy Solution Profile

button

Then select:• Source System = production

tenant• Source Solution Profile ID =

change project• Target System = permanent test

tenant

Refer to Appendix B for more details related to copying the solution profile.


PERMANENT CLOUD TEST TENANT

ON PREMISE QA SYSTEM

Option 3: New Test Tenant with Data from Test


3

4

5

ON PREMISE PRODUCTION SYSTEM

72


6

1 Create change project (CP), selecting scope and activities 7 Modify key user access rights; Perform adaptation; Replicate/Migrate basic and master data

2 Request new test tenant linked to change project solution profile 8 Complete re-opened fine-tuning activities

3 Complete configuration 9 Activate solution4 Refresh On Premise data (optional) 10 Replicate/Migrate transaction data; Modify end user authorizations5 Test data replication/migration; Test end-to-end scenarios 11 Close change project ; Go live with new solution6 Merge solution profile 12 Request deletion of change project test tenant

8 9 121110Access to change project activity list

prohibited



CLOUD “WORK” TEST TENANTHas test data with change project solution profile



Data copied

CP solution profile linked




Creation button

Then select:• Data Source System ID =

permanent test tenant• Solution Profile Source System

ID = production tenant• Source Solution Profile ID =

change project


Questions?


Q&ASlide 1 of 3

Q1: How does this change impact customers who signed prior to r1308?

A1: Once upgraded to r1308, new tenant requests submitted via SCC work center will have the tenant limitation applied. Existing test tenants will remain but if number of test tenants exceeds limitation, then SAP will work with customer to reduce the number.

Q2: If I complete the Close Project activity for a r1305 implementation, will the test tenant automatically be decommissioned in 14 days?

A2: Yes, the processes for versions prior to r1308 remain the same.

Q3: Is the restore point process the same (i.e. request via FT activity and kept for 14 days)?

A3: Yes, nothing changed

Q4: If a permanent test tenant is purchased by the customer, how many test tenants are delivered once the subscription is booked?

A4: The permanent test tenant and the “work” test tenant are handed over. If the “work” test tenant will not be used as is, then you can request termination.

Appendix AExamples of test tenant limitation


ExamplesFor Customers with Permanent Test Tenants

Example 1:

Customer’s Subscriptions per CRM: 1 permanent test tenant subscription

1 production tenant subscription

Customer’s Current Landscape: 1 test tenant

1 production tenant

Action: User submits new system request for a test tenant via the Service Control Center work center

System Reaction: New system request is accepted because 1 test tenant is allowed, in addition to the permanent test tenant

Example 2:

Customer’s Subscriptions per CRM: 1 permanent test tenant subscription

1 production tenant subscription

Customer’s Current Landscape: 2 test tenants

1 production tenant


System Reaction: Error returned that an existing test tenant must be decommissioned before a new test system can be requested


ExamplesFor Customers without Permanent Test Tenants

Example 3:

Customer’s Subscriptions per CRM: 1 production tenant subscription

Customer’s Current Landscape: 1 production tenant


System Reaction: New system request is accepted because 1 test tenant is allowed

Example 4:

Customer’s Subscriptions per CRM: 1 production tenant subscription

Customer’s Current Landscape: 1 test tenant

1 production tenant




ExamplesFor Customers with Enterprise Edition Subscriptions

Example 5:

Customer’s Subscriptions per CRM: 2 production tenant subscriptions

Customer’s Current Landscape: Production tenant A

Production tenant B

1 test tenant

Action: User submits new system request for a test tenant via the Service Control Center work center in either tenant

System Reaction: New system request is accepted because total allowed test tenants is 2

Example 6:

Customer’s Subscriptions per CRM: 2 production tenant subscriptions

Customer’s Current Landscape: Production tenant A

Production tenant B

2 test tenants

Action: User submits new system request for a test tenant via the Service Control Center work center in either tenant


Appendix B

Options in the Service Control Center work center Systems view


Request Creation

When requesting a new tenant (referred to as “system” in the UI), there are four options available.

First, click Request Creation button


New System Option 1Data Source: Initial System (Copy Solution Profile)

Can be system type of test or production

Source solution profile is copied and deployed

No data is copied Relevant for initial

implementation Could be used after go-live but

no merge back capability is possible

When requesting data source Initial System (Copy Solution Profile):

Recommended for requesting production

tenants


New System Option 2Data Source: Copy of Source System

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 is possible

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

When requesting data source Copy of Source System:

Recommended for data migration testing when initial test tenant cannot

be used


New System Option 3Data Source: Copy of Source System (Copy Solution Profile)

Can only be test system type Source solution profile is copied and

deployed (the change project solution profile can be selected)

Source data is copied (source tenant for solution profile can be different)

Relevant for initial implementation Relevant for change project, including

merge of solution profile back into production

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

When requesting data source Copy of Source System (Copy Solution Profile):

Recommended for requesting new change

project test tenants

Remark: 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.


New System Option 4Initial System Data Source

Can be system type of test or production

No solution profile is copied No data is copied Is relevant for initial implementation Could be used after go-live but no

merge back capability is possible

When requesting data source Initial System:


Implementation Projects

The Request System button in the Business Configuration work center Implementation Projects view seamlessly launches the new Request Creation UI.


New Copy Solution Profile Only FunctionSlide 1 of 2

A user can request a copy of a solution profile from tenant A be applied to existing tenant B.

First, click Copy Solution Profile button


New Copy Solution Profile Only Function Slide 2 of 2

Source solution profile is copied and deployed to an existing test tenant (production tenant cannot be selected as target)

No copy or refresh of data is possible (the data in the existing test tenant remains as is)

Relevant for initial implementation Relevant for change project,

including merge of solution profile back into production

Consistency check is applied – only consistent solution profile can be copied

Recommended for testing a change project in an

existing test tenant

Remark: 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.

cloud tenant landscape

Documents

additional test tenant

tenant request

existing test tenant

new tenant processes

permanent test tenantsap

sap cloud solution

source tenant url

customer tenants