Introduction

SAP BTP ABAP Environment (aka Steampunk) supports now two options for partners to deliver products to their customers.

Partners build side-by-side extensions and deliver them as multitenant software-as-a-service (SaaS) solutions. This option is considered as a service offering. The partner is fully responsible for the development and production including the operations of the multitenant SaaS solution. The customers can adapt the mutlitenant SaaS solution to their business using key-user extensibility.

There are also use cases where customers want to operate the partner solution in their own environment or have the need for more comprehensive enhancement of the partner solution using developer extensibility in addition to key user extensibility to meet the customer business needs. The right way for partners to deliver such products is the newly available software delivery option, called “Add-On Product” (first announced as “Installable Product”). It allows partners to provide their solution to customers as a software offering (“Add-On Product”) and not as a service. The partner solution offered as software is available for all the customers to whom it was sold by the partner. The customer installs and operates it in his own SAP BTP ABAP Environment systems. The market place for partner solutions delivered as an Add-On Product is the SAP Store. A prerequisite to benefit from the new software delivery option is a SAP PE Build contract for the respective partner.

Overview about the two delivery options for commercial partners:

CharacteristicMultitenant SaaS SolutionAdd-On Product (New Option)Offering typeService SoftwareRuns in BTP Global Account owned by PartnerCustomerOperations responsibility PartnerCustomerSchedule upgrades/patches responsibilityPartner CustomerInfrastructure costs taken by PartnerCustomerExtensibility optionKey-user extensibilityDeveloper extensibilityCommercial prerequisitesContract for productive useSAP PE Build contract with SAP Store enhancementProduct offering in SAP Store is mandatoryNoYes

A partner can offer the same product as a multitenant SaaS Solution and as an Add-On Product at the same time for different customers. With such a hybrid approach, a partner can fulfill both, requirements of smaller customers for a standardized service at minimum infrastructure costs and requirements of bigger customers regarding developer extensibility and running the product in the customer’s infrastructure.

What is SAP PE Build?

SAP offers various partner programs and models. One of these is the SAP PartnerEdge program. The SAP PartnerEdge program has four different tracks, depending on the partner’s focus. These tracks are Sell, Build, Service, and Run. To deliver the Add-On Product on the SAP BTP ABAP Environment, the partner requires the SAP PE track “Build”. Using any other track is not possible.

The SAP PartnerEdge Build program provides SAP partners access to resources, services, and benefits to successfully collaborate with SAP. SAP PartnerEdge – Build is a licensing and GTM model for partners that design, develop, and commercialize applications and software that extend the value of SAP applications. The model features standard terms and fixed revenue share pricing. Partners can publish solutions in the SAP Store, so that customers can consume the products through them. The provision of the Add-On product is only permitted and possible via the SAP Store.

The PE Build Track provides several benefits for the partner.

Onboarding support: Resources include development and test licenses, advisory and support services, installation and migration guides, and SAP Open Source offerings on GitHub.

Enablement tools: Help is at hand with support and help portals, how-to guides, developer communities, the SAP Cloud Appliance Library tool, and SAP API Business Hub.

Training resources: You can hone your skills using the openSAP platform, the SAP Enterprise Architecture Explorer site, and SAP Learning Journey guides.

Requirements and Licensing

Partners must meet some requirements to participate in the PE Build Program. These requirements include the following:

Valid due diligenceNeed to agree to the SAP PartnerEdge program agreementsCompletion of compliance trainingsThe Accounts payable is in good standingFulfillment of the compliant partnership requirementsPaying of the annual program feeMaintenance of ongoing generic and track-specific program requirementsPrerequisites for publishing on SAP store.

The respective prices for a partner vary because they depend on the BTP services used, the revenue share, and the annual fee. You can find more information about pricing, revenue share and annual contributions here. All information about the Terms & Conditions is available here

The following material numbers are required for an SAP BTP ABAP environment.

License TypeMaterial numberMaterial nameMetricBlock sizeMin. blocksPE Build8006181SAP BTP ABAP Environment, runtime GB Memory16 GB1PE Build8006182SAP BTP ABAP Environment, persistence GB Memory16GB2

The minimum setup of a system is 16 GB runtime (ABAP runtime) and 32 GB persistence (HANA Cloud memory). This is why customers and partners have to buy at least 1 unit of 16 GB runtime and 2 units of 16 GB persistence in order to get started.

Furthermore, the partner also needs authorization to make their own software available via the SAP Store.

Any partner selling a GTM-ready solution must adhere to paying a revenue share to SAP according to the price list for the Build track of the SAP PartnerEdge program, regardless of whether SAP facilitated the customer transaction (for example, through an SAP sales representative) or not.

How does the partner provide the Add-On Product?

The approach for developing and building an Add-On Product is the same as for the multitenancy SaaS product. The partner development is done via the BTP Global Account and then the Landscape Portal is used to build the product based on the developed custom software component(s).

From then on, the process differs from that of the multitenancy SaaS product.

The partner registers the Add-On Product in the SAP Solution Hub and maintains all necessary data for provision in the SAP Store. The partner is getting access to the SAP Solution Hub via the mandatory SAP PE Build contract. In the final step, the partner publishes the product in the Landscape Portal.

What does the customer need to do?

The customer needs to select the product from the SAP Store and needs to contact the partner via the respective form in the SAP Store. After selling the product by the partner to the customer, a signed Amendment to SAP Business Technology Platform Supplemental Terms and Conditions for ABAP Add-ons is required of the customer. This amendment is automatically part of the SAP Business Technology Platform Supplemental Terms and Conditions for new BTP contracts and renewed BTP contracts with signed date on April 23, 2025 or later. This is also true for all SAP Build contracts.

For customer BTP contracts signed before April 23, 2025, the customer (or the partner on behalf of the customer) need to create a customer ticket for component BC-CP-ABA. This customer ticket represents a service request for SAP to initiate a DocuSign process that the customer signs the required above-mentioned amendment. Please specify in the ticket:

Purpose: Sign amendment for ABAP Add-ons Customer name and ID (if the ticket was created by the partner on behalf of the customer)Contact email address on customer side who will be the recipient for the DocuSign process

The amendment needs to be signed only once per customer and is independent of the vendor of the product to be installed. The customer can only see the product in the Landscape Portal if the amendment is signed.

The customer is responsible to install the product and to trigger the installation of both upgrades and patches provided by the partner. After the initiated purchasing process via SAP Store, all these lifecycle activities are supported by the Landscape Portal. The Landscape Portal is part of the SAP BTP ABAP Environment and does not cause additional costs.

Further information:

If you want to apply for the SAP PartnerEdge Build program, please use the online application form or refer to the SAP Partner Portal.

You can find more technical information about the Add-On Product

In the documentation of the Landscape Portal, applications for product lifecycle managementIn the recording of the Devtoberfest Session: Building Partner Products on SAP BTP ABAP Environment

Disclaimer: Information provided in this blog post serves as general overview only and does not replace legal agreements between SAP and its contractual parties. As this blog post is updated in an irregular fashion, it cannot serve as single point of truth. Please refer to your assigned SAP account/partner manager for most up-to-date information, especially regarding applicable licensing and pricing models. IntroductionSAP BTP ABAP Environment (aka Steampunk) supports now two options for partners to deliver products to their customers.Partners build side-by-side extensions and deliver them as multitenant software-as-a-service (SaaS) solutions. This option is considered as a service offering. The partner is fully responsible for the development and production including the operations of the multitenant SaaS solution. The customers can adapt the mutlitenant SaaS solution to their business using key-user extensibility. There are also use cases where customers want to operate the partner solution in their own environment or have the need for more comprehensive enhancement of the partner solution using developer extensibility in addition to key user extensibility to meet the customer business needs. The right way for partners to deliver such products is the newly available software delivery option, called “Add-On Product” (first announced as “Installable Product”). It allows partners to provide their solution to customers as a software offering (“Add-On Product”) and not as a service. The partner solution offered as software is available for all the customers to whom it was sold by the partner. The customer installs and operates it in his own SAP BTP ABAP Environment systems. The market place for partner solutions delivered as an Add-On Product is the SAP Store. A prerequisite to benefit from the new software delivery option is a SAP PE Build contract for the respective partner. Overview about the two delivery options for commercial partners:CharacteristicMultitenant SaaS SolutionAdd-On Product (New Option)Offering typeService SoftwareRuns in BTP Global Account owned by PartnerCustomerOperations responsibility PartnerCustomerSchedule upgrades/patches responsibilityPartner CustomerInfrastructure costs taken by PartnerCustomerExtensibility optionKey-user extensibilityDeveloper extensibilityCommercial prerequisitesContract for productive useSAP PE Build contract with SAP Store enhancementProduct offering in SAP Store is mandatoryNoYesA partner can offer the same product as a multitenant SaaS Solution and as an Add-On Product at the same time for different customers. With such a hybrid approach, a partner can fulfill both, requirements of smaller customers for a standardized service at minimum infrastructure costs and requirements of bigger customers regarding developer extensibility and running the product in the customer’s infrastructure. What is SAP PE Build?SAP offers various partner programs and models. One of these is the SAP PartnerEdge program. The SAP PartnerEdge program has four different tracks, depending on the partner’s focus. These tracks are Sell, Build, Service, and Run. To deliver the Add-On Product on the SAP BTP ABAP Environment, the partner requires the SAP PE track “Build”. Using any other track is not possible. The SAP PartnerEdge Build program provides SAP partners access to resources, services, and benefits to successfully collaborate with SAP. SAP PartnerEdge – Build is a licensing and GTM model for partners that design, develop, and commercialize applications and software that extend the value of SAP applications. The model features standard terms and fixed revenue share pricing. Partners can publish solutions in the SAP Store, so that customers can consume the products through them. The provision of the Add-On product is only permitted and possible via the SAP Store. The PE Build Track provides several benefits for the partner. Onboarding support: Resources include development and test licenses, advisory and support services, installation and migration guides, and SAP Open Source offerings on GitHub. Enablement tools: Help is at hand with support and help portals, how-to guides, developer communities, the SAP Cloud Appliance Library tool, and SAP API Business Hub. Training resources: You can hone your skills using the openSAP platform, the SAP Enterprise Architecture Explorer site, and SAP Learning Journey guides. Requirements and LicensingPartners must meet some requirements to participate in the PE Build Program. These requirements include the following:Valid due diligenceNeed to agree to the SAP PartnerEdge program agreementsCompletion of compliance trainingsThe Accounts payable is in good standingFulfillment of the compliant partnership requirementsPaying of the annual program feeMaintenance of ongoing generic and track-specific program requirementsPrerequisites for publishing on SAP store. The respective prices for a partner vary because they depend on the BTP services used, the revenue share, and the annual fee. You can find more information about pricing, revenue share and annual contributions here. All information about the Terms & Conditions is available hereThe following material numbers are required for an SAP BTP ABAP environment. License TypeMaterial numberMaterial nameMetricBlock sizeMin. blocksPE Build8006181SAP BTP ABAP Environment, runtime GB Memory16 GB1PE Build8006182SAP BTP ABAP Environment, persistence GB Memory16GB2The minimum setup of a system is 16 GB runtime (ABAP runtime) and 32 GB persistence (HANA Cloud memory). This is why customers and partners have to buy at least 1 unit of 16 GB runtime and 2 units of 16 GB persistence in order to get started. Furthermore, the partner also needs authorization to make their own software available via the SAP Store. Any partner selling a GTM-ready solution must adhere to paying a revenue share to SAP according to the price list for the Build track of the SAP PartnerEdge program, regardless of whether SAP facilitated the customer transaction (for example, through an SAP sales representative) or not. How does the partner provide the Add-On Product?The approach for developing and building an Add-On Product is the same as for the multitenancy SaaS product. The partner development is done via the BTP Global Account and then the Landscape Portal is used to build the product based on the developed custom software component(s). From then on, the process differs from that of the multitenancy SaaS product. The partner registers the Add-On Product in the SAP Solution Hub and maintains all necessary data for provision in the SAP Store. The partner is getting access to the SAP Solution Hub via the mandatory SAP PE Build contract. In the final step, the partner publishes the product in the Landscape Portal. What does the customer need to do?The customer needs to select the product from the SAP Store and needs to contact the partner via the respective form in the SAP Store. After selling the product by the partner to the customer, a signed Amendment to SAP Business Technology Platform Supplemental Terms and Conditions for ABAP Add-ons is required of the customer. This amendment is automatically part of the SAP Business Technology Platform Supplemental Terms and Conditions for new BTP contracts and renewed BTP contracts with signed date on April 23, 2025 or later. This is also true for all SAP Build contracts.For customer BTP contracts signed before April 23, 2025, the customer (or the partner on behalf of the customer) need to create a customer ticket for component BC-CP-ABA. This customer ticket represents a service request for SAP to initiate a DocuSign process that the customer signs the required above-mentioned amendment. Please specify in the ticket:Purpose: Sign amendment for ABAP Add-ons Customer name and ID (if the ticket was created by the partner on behalf of the customer)Contact email address on customer side who will be the recipient for the DocuSign processThe amendment needs to be signed only once per customer and is independent of the vendor of the product to be installed. The customer can only see the product in the Landscape Portal if the amendment is signed. The customer is responsible to install the product and to trigger the installation of both upgrades and patches provided by the partner. After the initiated purchasing process via SAP Store, all these lifecycle activities are supported by the Landscape Portal. The Landscape Portal is part of the SAP BTP ABAP Environment and does not cause additional costs. Further information:If you want to apply for the SAP PartnerEdge Build program, please use the online application form or refer to the SAP Partner Portal.You can find more technical information about the Add-On ProductIn the documentation of the Landscape Portal, applications for product lifecycle managementIn the recording of the Devtoberfest Session: Building Partner Products on SAP BTP ABAP Environment Read More Technology Blog Posts by SAP articles

#SAP

#SAPTechnologyblog