SAP Build Process Automation is available via Free Tier and of course as a payed version. Therefore the service has several service plans to distinguish between the usage types and to measure the consumed services.
In this blog post I will explain the different service plans and how they are related to each other. Let me start with a short overview which shows all the available service plans in the entitlements section of a sub-account.
You can see that we have nine service plans for SAP Build Process Automation. If you like to start with the free tier version of the solution you need two service plans:
"free (Application)" and
"standard".
"free (Application)" enables you to subscribe to the service and
"standard" enables you to create a service instance. You need both for the full usage of all capabilities of SAP Build Process Automation.
IMPORTANT: "standard" is a free of charge service plan, but "standard (Application)" is a charged plan!
This brings us directly to the update path from free tier to a payed version. For a detailed view on the procedure please refer my earlier explanation in this
blog post.
For a full productive usage of SAP Build Process Automation you need the
"standard (Application)" and the
"standard" plan, where the
"standard (Application)" service plan enables you to subscribe to the service.
Depending on your planned automation scenarios you need the following service plans in addition:
"advanced-user": advanced user are able to design, monitor, administrate the solution and
access the process visibility workspace.
"standard-user": standard user are process participants who trigger, approve or contribute to a process instance
"automation-unattended": This service plan allows you to use automations (bots) in unattended mode.
"automation-attended": This service plan allows you to use automations (bots) in attended mode.
The
"advanced-user" and the
"standard-user" service plans includes the access to the SAP Build Workzone standard edition and a certain number of API calls and storage. Normally there is no need for an additional licensing.
In case you have API call or storage intensive use cases and the included quota is not high enough, you need the
"api-calls" and
"storage" service plans. These service plans are as of today only available via subscription not via CPEA/PAYG. We will add the plans to CPEA/PAYG in the course of next months.
I hope this explanation helps to understand the structure of the service plans for SAP Build Process Automation better.
For more information on SAP Build Process Automation, please refer to the following resources: