Recommended Tenant landscape strategy

[Former Member]

Does SAP recommend the use of a (chargeable) productive test tenant when integrating C4C with CRM or ECC?

My understanding is that C4C license comes with a free temporary "working" test tenant. I wonder how people have justified a permanent chargeable Test tenant in their landscape for an hybrid C4C/on premise scenario.

Please share your experience.

[former_member3555 · Accepted solution]

Hello Thierry

You are correct.  For integration customers we recommend that you purchase a permanent test tenant.  That gives you the flexibility to change your integration, try out new scenarios, and not have to impact your productive tenant.    This permanent test tenant is an extra cost, but probably worth it if you have integration.  Especially if you are adding additional scenarios over time.

Regards

Ginger

[Former Member · Accepted solution]

Can't a customer get a temporary test tenant after going live? Or can they only get this tenant for the initial implementation?

[former_member3555 · Accepted solution]

Hi Thierry

Yes - you get a temporary test tenant for the go-live and then for upgrades - I think about 2 weeks each.   So, if you don't change much in the integration, that might work.

-ginger

[angela_sparkman · Accepted solution]

You can request a temporary test tenant at any point in time, as long as you don't exceed a total of 1 test tenant (plus the number of permanent test tenant subscriptions purchased).  A test tenant is automatically used for the initial implementation.  Currently we do not automatically provide test tenants for upgrades - it is up to the customer to request a test tenant if one does not already exist. This can be done via the Service Control Center work center in the production tenant.

The benefit of a permanent test tenant is that the communications with the ERP test system stay in tact.  If a customer requests a new test tenant as a copy of the production tenant, then the communications, mapping, etc. are also copied.  Then someone must update all of that to be specific to the ERP test system.

If you haven't already done so, check out the System Landscape and Upgrade Process presentations that are linked in the Infrastructure wiki (you have to login into the Business Center to access it).

[Former Member · Accepted solution]

Big thanks for this clarification.

Can we specify how long we need the temporary test tenant for?

Other than for integration scenario, could another use case be to extend a solution with the SDK after the initial go live? Or do you need to pay for a productive test tenant for this?

Thanks

[angela_sparkman · Accepted solution]

The time period isn't set on a test tenant - the customer triggers the decommissioning via the Service Control Center whenever he wants.

I think that a permanent test tenant subscription is required when SDK solution extensions are in scope.

[former_member3555 · Accepted solution]

I don't think the time period is completely open on a test tenant - I remember one customer that wanted to keep it but it had been over a month so they couldn't unless they switched to permanent test tenant.