Dev/Test/Prod Instances of SAC?

[Joel_B]

10:53 AM

I am curious how many SAP Analytics Cloud customers run more than 1 Tenant/Instance, such as Development/Test/Production, as you would with any other SAP product? At the very least, how do you test upcoming monthly or quarterly releasees?

I ask because I am being told that the SAC product has no licensing capability to support named user licenses across multiple tenants for this dev/test/production purpose. For example, we have purchased two tenants so far and two different blocks of licenses. One of our tenants is development and test and the second tenant is for production. Though, the same named user configured on both tenants counts as two licenses, meaning we are being told we have to pay double for the named users who wish to develop or support content.

Can the community confirm: If you run more than 1 tenant, do you have to pay multiple times for named users?

[DebjitSingha · Accepted solution]

Hello joel.blackthorne3,

You will need two separate set of licenses for two environments. Each SAP contract mention tenant based license bundle. This means you have to pay by per user per tenant. Although test tenant license cost is less, compared to prod tenant.

For more info on multiple tenant, lifecycle and users setup check below blogpost.

SAP Analytics Cloud – Landscape Architecture & Life-cycle Management

Thanks,

Debjit

[mfoeken]

Hi Joel,

I have many customers that use more than 1 tenant to connect to different dev-qa-prod instances of their source systems. And yes, as confirmed by Debjit, each tenant has its own license with named/concurrent users. It's logical that SAP changes per user per tenant: each tenant is hosted through a hyperscaler which charges a running fee. That's completely different from running your own infrastructure and hosting a solution.

Kind regards,

Martijn van Foeken | Interdobs

[Dilan]

Hello ,

what about if we only have one system, could we use the workspaces as dev and prod? So one workspace would be dev and the other one prod and we could transport from dev workspace to prod workspace. Is this an approach we could go if we only have one system?

Thanks

Dilan

[N1kh1l]

A minimum of 2 system is required for proper lifecycle management of SAC artifacts. SAC artifacts are linked with each other based on ID. So even a copy of same story with same name will have 2 different id's. So it will be really a tedious job (almost impossible ) to do a proper lifecycle management using Folder/workspaces. Below is an excerpts from one of best practice note around lifecycle management.

Hope it helps !!

Nikhil

[former_member813100]

Hi All,

Can you recommend the right approach for testing if we have 2 tenants(dev and prod) however we want to get a user acceptance done by connecting the s/4hana test environment with the same live models and corresponding stories(we see the option of changing the connection for models) what is the recommended approach.

[VijayetaSharma]

If you are going with two tenant then, one option would be to change "data source" for live connection. For import connection you do not have flexibility to simply switching the DS. Instead you have to change the connection details. This means during UAT development on same connection name wont be possible.

I see may clients connect SAC to test environment and leave Dev out of the landscape altogether.

If your requirement needs a SAC Dev setup of some kind, another option would be to unitize "Space" connect in SAC. This way same tenant can have two separate section for Dev and QA respectively.

Cross space communication is not possible. In your case this may turn out to be advantagious.

Thanks,

Vijayeta

[Jay_Gandhi]

^{Hi there,}

Apologies for my earlier post, a license is indeed needed for EACH tenant.

Jay