Deployment of Organizational Structure from Development Tenant

[adnanmaqbool]

Dear All

We have created an Organizational Structure having 7 company codes and around 300 organizational units in Development - Customizing (Implementation) system.

Now what is the use of creating such a huge organizational structure in development - development tenant once again manually while the organizational structure of customizing tenant has already been transported to QAS system.

Which Organizational Structure will be considered as final on QAS system, the one created in customizing tenant or development tenant.

[arunacheemala7 · Accepted solution]

The assumption is that development system doesn't need all the configuration as the development will be done on selected areas. Also, the configuration is expected to be done in the customizing tenant and so there is no need to transport from development tenant to customizing tenant. We do however understand, the concern with the initial setup and at this point as you said you have to activate the development tenant as well.

We do recommend activating the development tenant just like the customizing tenant so that when you develop something it will work in the customizing tenant.

Also currently there's no option available to copy the organizational structure from Customizing to Development, Each and every step like defining your scope, setting up primary finance settings and setting up organizational structure all this steps have to be performed manually for each project in Central Business Configuration.

we are working on this in the future.

Checkout below SAP learning page and the KBA:

3324929 - Not able to Import Collection into Customizing/Development Tenant (3SL) - SAP S/4HANA Clou...

Processing Transports in SAP S/4HANA Cloud Public Edition

[adnanmaqbool · Accepted solution]

Hi arunacheemala7 , thanks for detail reply, how we will avoid the scope and organization structure created on development tenant to move to QA as the scope and organizational structure created on customizing tenant has already moved to QAS and is the final one.

[George_Yu · Accepted solution]

Hi @adnanmaqbool ,

It is a fair question. We usually explain this topic in an architecture overview, what is the purpose of each tenant, and how CBC configuration impacts them, and the transport system setup. However, there is no guardrail to limit you on how many orgs you can create for the Development Project in CBC, because it really depends on your use case. 

On the other hand, when you deploy your CBC configurations to the Development Tenant, there is no transports created for you to release/export these configurations to the Test Tenant and Production Tenant. This is a kind of hard guardrail to prevent you from moving development org configurations to the T and P tenants. From Development Tenant, you can only create and export development transports (ABAP codes) to the downstream tenants.

Hope this explanation helps. 

Regards,

George