In SAP S/4HANA Cloud, public edition, you need to deploy scope items in both the customizing and development tenants, but they are not deployed separately in the sense of independent activations. Instead, the customizing tenant acts as the initial system where you define the scope and make initial configurations. The development tenant is then activated to mirror the customizing tenant, allowing for development and testing of changes before they are transported to the customizing tenant or potentially to a test/production environment.
In SAP S/4HANA Cloud public, custom roles are primarily created and managed within the Customizing Tenant, which is the primary workspace for business process configuration and key user extensibility. While the Development Tenant is used for ABAP development, including developer extensibility, custom roles are generally not created there.
The customizing tenant uses customizing requests and software collections for moving configurations, while the development tenant uses workbench requests. This ensures a clear separation of concerns.
some more glance on TR's created during deployment:
https://community.sap.com/t5/enterprise-resource-planning-q-a/deployment-of-organizational-structure-from-development-tenant/qaq-p/14015683#:~:text=Accepted%20Solutions%20(1)-,Accepted%20Solutions%20(1),learning%20page%20and%20the%20KBA:
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.
No comments:
Post a Comment