SAP Business Technology Platform (SAP BTP) is a platform focused on turning data into actionable business plans, particularly by leveraging tools found in an intelligent enterprise. SAP BTP contains many solutions, tools, and products under its umbrella. In this post, we’ll look at the deployment options for the different SAP Business Technology Platform development environments. By SAP PRESS.
The structure of the SAP BTP provisioning in terms of global account, subaccounts, and spaces—any configuration like connecting to a specific on-premise system or security setup, is specific in a subaccount instance of the platform. So, if you’re deploying an application which is, say specific to finance, then it’s better to have a separate subaccount for finance only. If the same subaccount is used for all areas, there is a chance of configurations getting overwritten or conflicts and confusion arising.
This guide then describes:
- Deployment on SAP BTP, Neo environment
- Deployment on SAP BTP, Cloud Foundry environment
- Deployment on SAP BTP, Kyma
- Deployment on SAP BTP, ABAP environment
For every environment like development, test, and production, you need separate subaccounts. In fact, since each subaccount would be linked to the core instance of the underlying transactional system, which may be on-premise SAP S/4HANA, for example. Ideally, you have one-to-one linkages between the environments of this SAP S/4HANA instance and the corresponding subaccount. This approach ensures testing with the backend systems and security, all in sync, with no deployment risks.
[Read More]