How I can develop "Client" at SAP S/4 HANA cloud public (3SL)?

[focustakashi]

How I can develop "Client" at SAP S/4 HANA cloud public (3SL) which is a basic idea for On Premise for integration testing and migration testing?
I don't have any idea to plan to do integrationtesting and migration testing & rehearsal with S/4 HANA cloud public because I have only implementation expriences with On Premise version.
Please kindly give your high level guidances for implementation approach at "Realization and Deploy" phases and any instractions.

[Marco_Valencia · Accepted solution]

Hi Takashi,

In SAP S/4HANA Cloud, public edition you can't create clients like in on-premise. However, SAP is planning to offer in the near future a concept called "Parallel Project Line" which will allow you to have a new tenant in Dev and Test systems which will allow you to have a parallel project line to execute testing. Please understand this is the current state of planning and this plan is subject to change.

Hope this helps,

Marco

[focustakashi · Accepted solution]

Hi Marco,
Thank you for your prompt answer. I'm very sorry not to have the "Parallel Project Line" with the current version today.
And I'm slightly wondering how I can develop implementation planning for Realization and Deploy" phases for my customer. Because I have no idea about this except for the time-sharing approach among the testing team, migration team, and other teams. I think it must take a longer duration rather than paralleled scheduling.

Regards,

Takashi

[George_Yu]

Hi Takashi,

Q: can I have a sandbox tenant for a short period of time?

Although I am not a salesperson, but I think it is possible. This is the beauty of SaaS, pay as you go. The first PPL tenant is included, and the subsequent ones are additional charge.

Q: Multiple tenants in Dev system?

At this moment, we are sure there will be one tenant serving PPL. Additional PPL tenants are possible, although no details yet. We have to wait and see how much will be offered in PPL tenant(s),vs. main tenants 100 and 080.

Regards,

George

[George_Yu]

Hello Takashi,

You are correct. Generally speaking, you have one tenant on each system:

• Dev tenant on Dev System
• Test tenant on Test System
• Production Tenant on Production System

However, there is a slight variation here:

• Dev-100 tenant for configuration on Dev System
• Dev-080 tenant for extensibility (ABAP development) on Dev System
• In the future, Dev-120 tenant for parallel project line on Dev System

You don't have more than one tenant on Test and Production Systems. You cannot get two test tenants on Test System even you are willing to pay for it.

To do testing, we plan to offer a sandbox tenant for you, but it is not included in the transport system.

In essence, we advise our customers to have a cloud mindset, i.e., trying to do things in a new way and not bringing in all the practices from the on-premise world. Not all of these practices work in the SaaS world.

Regards,

George

[focustakashi]

Hi George,

I got clear on this. As you mentioned, the SaaS world is a quite new world from our experienced on-premise world. Learned it. 😉

Then I would slightly more request your help and comments for my additional questions next.

First of all, it must be for my current actual project,
According to your offering, I can purchase a sandbox tenant license additionally for any of my testing, although it cannot transfer any data to any original tenants at Dev/Test/Prod system.
Is it possible to purchase the sandbox tenant license(s) as temporary purchasing meant to use it(them) during the project such as testing term? Because I would avoid making costs for temporary staffs.

And 2nd, it must be for your future delivery solution,
You are going to provide an extensional tenant for the "parallel project line" as one of the new releasing.
I'd like to know whether you have the plan to have multiple tenants in the Dev system.
And if so, is it whether the tenant has any restrictions such as the maximum number of tenants in Dev system, data transfer limitation, performance capacity, access accounts, internal/external integrations, and so on?

Please kindly help with this.

Regards,

Takashi

[George_Yu]

Hi Takashi,

In the on-premise R/3 or S/4HANA systems, you can add/create new clients on the same system, so that these clients share the same ABAP codes but keep their own client-dependent data. Except 1 production client per software contract, you can have as many Dev clients or Test clients as you like. This concept doesn't exist in the SaaS world, or somehow is different.

In the SaaS world, we have tenants (no clients!). For a customer, you get Dev, Test and Production tenants with a subscription, for example. You are only entitled to have 3 tenants, no less and no more. Your tenants share the underlining ABAP codes with other customers. This is similar as on-premise world, but two tenants on the same system belong to two customers.

Now you want to add a new tenant, say Dev2. This is not that easy. For example, you cannot join the existing transport layer with Dev at present time. Later on, when we provide "parallel project line" as Marco mentioned, you will have the possibility of requesting Dev2 and Dev3 tenants. Then cloud ops people will build a transport layer including newly added Dev2 and Dev3 tenants, so that all changes can eventually be transported to the same production tenant.

Hope this helps.

Regards,

George

[focustakashi]

Hi George,
Thank you for your bit detailed explanation here. As my initial understanding, you said there are only 3 tenants in 3SL meant Dev, Test, and Prod tenants, NOT 3 tenants in each as Dev, Test, and Prod.
If I'm going to have some tenants for example in the Testing system layer, I have to procure licenses as I request, even though those are not connecting to each to transfer any data.

I wish I could get the SAP solution for this issue soon.

Thank you and Regards,

Takashi

[FernandaKlauck]

Hi Takashi,

In addition to Marco´s explanation, you can find more details about all Activate phases instructions in this link: Roadmap Viewer (sap.com).

Kind regards,

Fernanda

[focustakashi]

Hi Fernanda,

Thank you for your supportive answer. I'll check it again.

Regards,
Takashi