Connecting Cloud Tenant

Let's simplify the concept of tenant architecture. Typically, a customer operates with at least two tenants: one for testing and another for production. Inside SAP, various development environments exist, such as development, staging, and productive environments. However, regardless of the naming conventions, the code line remains consistent across all tenants. The testing environment is essentially a mirror of the production setup, ensuring a seamless transition between the two.

In the world of on-premise systems, familiar transport rhythms dictate the movement of developments from the QA system to production, often with lengthy cycles, perhaps twice a year. Contrarily, cloud solutions, especially in industry cloud contexts, witness more dynamic deployments, occurring every two to four weeks. This accelerated cycle brings new capabilities to the solution regularly. While certain discussions about feature toggling are ongoing for specific industry cloud solutions, this functionality is not yet available for SAP Order Management Foundation and SAP Order Management Solution for Automotive.

Feature toggling, a potential future addition, could allow customers a preview in a specific tenant, granting early access to functionalities. However, the code line remains the same, and any differences stem from activated or deactivated features in a particular tenant. It's crucial to emphasize that before any deployment to production, SAP conducts rigorous automated testing, running hundreds of tests daily. If issues arise during these tests, deployment is postponed until all tests return positive results, ensuring a robust and error-free production system.

SAP designates maintenance windows for certain applications, indicating potential downtimes of up to two hours on Friday evenings. In practice, the downtime is often minimal, with instances like OMF experiencing only 25 minutes of downtime in the last four years. Users generally do not perceive significant interruptions during deployments, and the impact is usually limited to the introduction of new buttons or fields.