Before you can proceed with the development of the add-on, you have to perform several preliminary steps.
-
Register the development namespaces before any system is set up. To start the actual add-on development process, you have to set up the system landscape and global account structure for development. For pipeline automation, set up a CI/CD server, in this case a Jenkins server.
-
Create one or more software components that make up the add-on in the namespaces registered for you. In this scenario, namespaces are required for both the add-on product name and software components. You can register these namespaces with the development namespace/license keys tool.
-
Purchase the SAP BTP, Cloud Foundry environment entitlements necessary for the account setup, which includes the service ABAP environment for development. The ABAP environment (service plan
saas_oem), Application runtime, SaaS provisioning, ABAP Solution service as well as the Landscape Portal are used for providing the SaaS app.We recommend using the browser-based IDE SAP Business Application Studio for UI development. In this case, additional configuration is required to enable developers to use this service.
Once you’ve completed these steps, you can start developing an add-on.
- To register a namespace, you need an S-user in SAP One Support Launchpad with authorization to reserve a development namespace. See SAP note 1271482.
- To set up global accounts for development and poduction, you need two global accounts on the SAP Business Technology Platform with the corresponding entitlements for services and applications. See Entitlements and Quotas.
- To create ABAP instances, you have to set up the account structure in the global account for development, and assign entitlements for each subaccount. See Configure Entitlements and Quotas for Subaccounts.
- To develop UIs, you need an entitlement for SAP Business Application Studio and an assignment to a subaccount for development. See SAP Business Application Studio.
- To set up transports from the development to the test system, you need a test system and optionally a pipeline in a Jenkins CI/CD server that is provisioned using a Cx Server to automatically import new changes. See Jenkins and Cx Server.
- To set up add-on development, you need a development system.