Skip to main content
This guide walks you through the end-to-end setup of SAP Build Process Automation in an SAP Business Technology Platform (SAP BTP) environment. It is intended for SAP BTP administrators who need to configure entitlements, provision service instances, assign user roles, and prepare the environment for process automation projects. You will complete the following:
  1. Add SAP Build Process Automation entitlements to your subaccount
  2. Create a service instance and application subscription
  3. Verify entitlements, instances, and subscriptions
  4. Assign role collections to a business user
  5. Install the automation agent
  6. Activate Generative AI capabilities
Prerequisites:
  • Administrator access to an SAP BTP global account and subaccount
  • A Cloud Foundry environment with a Dev space already created
  • A business user account to assign role collections to

Procedure 1: Add Entitlements for SAP Build Process Automation

Before you can use SAP Build Process Automation, add the required service plans as entitlements to your subaccount.
1

Open Entitlements

Open the SAP BTP Cockpit and select your subaccount (for example, InclusionCloudDemo01). In the left sidebar, click Entitlements.Entitlements page for the InclusionCloudDemo01 subaccount
2

Open the Add Service Plans dialog

Click Edit, then click Add Service Plans.Add Service Plans button highlighted on the Entitlements page
3

Search for SAP Build Process Automation

In the Add Service Plans dialog, type process auto in the search bar and select SAP Build Process Automation from the results.Add Service Plans dialog with SAP Build Process Automation selected
4

Select all five plans

Select all five of the following plans:
PlanPurpose
standardMain service plan
build-default (Application)Build plan for the application subscription
automation-attendedRun bots in attended mode
automation-unattendedRun bots in unattended mode
advanced-userAccess to process visibility workspace
Five plans selected for SAP Build Process Automation
5

Save your entitlements

Click Add 5 Service Plans, then click Save on the Entitlements page to apply the changes.Entitlements page with unsaved changes and the Save button visible
You can return to the Add Service Plans dialog at any time to add additional plans — such as storage, standard-user, api-calls, or addon (for UiPath connectivity) — depending on your requirements.

Procedure 2: Create the Service Instance and Subscription

With entitlements in place, create both a service instance and an application subscription for SAP Build Process Automation.
1

Open Instances and Subscriptions

In the left sidebar, click Instances and Subscriptions.Instances and Subscriptions highlighted in the sidebar
2

Create the service instance

Click Create. In the New Instance or Subscription dialog, configure the fields as follows:
  • Service: SAP Build Process Automation
  • Plan: standard
  • Runtime Environment: Cloud Foundry
  • Space: Dev
  • Instance Name: SAP Build Process Automation
Click Create.Instance creation dialog with all fields filled in
3

Wait for the instance to be created

The new instance appears in the Instances section with a status of Creation in Progress. Wait for the status to change to Created before continuing.Instances and Subscriptions page showing the new instance with "Creation in Progress" status
4

Create the application subscription

While the instance is being created, click Create again to set up the application subscription. In the dialog, select SAP Build Process Automation as the service and build-default as the plan, then click Create.New Instance or Subscription dialog with build-default plan selected
5

Wait for the subscription to reach Subscribed status

The subscription appears in the Subscriptions section with a status of Processing. The deployment may take several minutes.Subscriptions section showing SAP Build Process Automation with Processing status
Do not proceed to the next procedure until the subscription status shows Subscribed. If the status does not appear to update, navigate away from the Instances and Subscriptions page and return to refresh it.
In typical scenarios, you may activate SAP Build Apps first and then activate Process Automation. This guide covers standalone Process Automation activation, which is also a valid configuration.

Procedure 3: Verify Your Configuration

Once provisioning is complete, confirm everything is correctly configured before assigning roles.
1

Verify the Subscriptions table

Go to Instances and Subscriptions and verify that the Subscriptions section shows:
ApplicationPlanStatus
SAP Build Process Automationbuild-defaultSubscribed
SAP Document AIdefaultSubscribed
2

Verify the Instances table

In the Instances section, confirm that both instances are present and show Created status:
InstanceServicePlanRuntimeSpaceStatus
SAP Build Process AutomationSAP Build Process AutomationstandardCloud FoundryDevCreated
SAP Document AISAP Document AIpremium_editionCloud FoundryDevCreated
Instances and Subscriptions overview showing all services and statuses
3

Verify Entitlements quotas

Navigate to Entitlements and confirm the SAP Build Process Automation plans are listed with their assigned quotas:
PlanAssigned
automation-attended1 unit
build-default (Application)3 units
advanced-user1 unit
automation-unattended1 unit
Entitlements page showing SAP Build Process Automation quotasYou are now ready to assign roles to your business users.

Procedure 4: Assign Role Collections to a Business User

Users need specific role collections assigned before they can access SAP Build Process Automation.
1

Confirm Subscribed status

In the SAP BTP Cockpit, confirm that the SAP Build Process Automation subscription shows the status Subscribed.Subscriptions and Instances page with Subscribed status confirmed
2

Open the Users screen

Go to Security > Users in the left navigation pane. Identify the business user you want to grant access to.Users screen showing business user accounts and identity providers
3

Assign role collections

Select the user, then click to assign a role collection. In the Assign Role Collection dialog, select all of the following role collections:
  • ProcessAutomationAdmin
  • ProcessAutomationDelegate
  • ProcessAutomationDeveloper
  • ProcessAutomationExpert
  • ProcessAutomationParticipant
  • UAA_Token_Exchange
Click Assign Role Collection to apply.Assign Role Collection dialog with all Process Automation roles selected
Assign only the role collections that match each user’s responsibilities. For example, a developer needs ProcessAutomationDeveloper, while an end user who only triggers processes needs ProcessAutomationParticipant.

Procedure 5: Access the App and Install the Automation Agent

With roles assigned, open the SAP Build Process Automation application and set up the automation agent.
1

Open SAP Build Process Automation

Go to Instances and Subscriptions and click on the SAP Build Process Automation subscription to open the application.
2

Select your identity provider and sign in

When prompted, select your identity provider and sign in with your credentials.Identity provider selection screen
3

Explore the SAP Build lobby

Wait for the SAP Build lobby to load. Once it appears, you can click Create to start a new project. Available project types include:
  • Application
  • Automated Process
  • Joule Agent and Skill (if subscribed)
  • Business Site (if subscribed) SAP Build lobby with project creation options
4

Navigate to Control Tower > Agents

To install the automation agent, navigate to Control Tower in the left navigation pane, then select Agents.Control Tower Agents page with Register Agent option
5

Download and install the agent

Click Go to Download Page and follow the three-step process:
  1. Install the agent — Download and run the installer for your operating system.
  2. Allow the extension — Enable the required browser extension and restart your browser.
  3. Register — Register the agent to your SAP Build Process Automation tenant. Agent download page showing three installation steps
A technical user account is required to complete agent registration. Contact your administrator if you do not have one.
6

Verify the agent appears in Control Tower

After registration, return to Control Tower > Agents and confirm that your agent appears in the list.Control Tower Agents screen showing the registered agent list

Procedure 6: Activate Generative AI Capabilities

SAP Build Process Automation includes optional Generative AI features you can enable from the Control Tower.
1

Open the Generative AI tile

In the SAP Build Control Tower, locate the Tenant Configuration section and click the Generative AI tile.Control Tower Tenant Configuration with the Generative AI tile highlighted
2

Accept the AI Usage Terms and Conditions

In the AI Usage Terms and Conditions dialog, review the terms, check the I have read the terms and conditions box, then click Accept.AI Usage Terms and Conditions dialog with Accept button
3

Confirm Generative AI is enabled

Confirm that the Enable Generative AI toggle is switched on. The page displays the activating user and the activation date and time.Generative AI configuration screen showing enabled status and activation detailsOnce enabled, Generative AI capabilities are available across your tenant, including:
  • Creating and summarizing processes
  • Generating customized forms
  • Receiving UI suggestions
  • Enhancing Joule Agents
Explore the additional configuration options available in the Control Tower, such as Destinations, Mail Server, SAP Cloud ALM, External Authentication, Agent Groups, and API Keys — these allow you to further customize and extend your automation environment.Control Tower configuration overview showing all available tiles

FAQ

The status typically moves from Processing to Subscribed within a few minutes, but may take longer depending on system load. Navigate away from the Instances and Subscriptions page and return to refresh the status if it appears stuck.
No. Assign only the role collections that match each user’s responsibilities. For example, a developer needs ProcessAutomationDeveloper, while an end user who only triggers processes needs ProcessAutomationParticipant. Granting unnecessary roles can expose functionality that is not relevant to that user’s work.
The standard plan is used to create a service instance, which enables API-level access via Cloud Foundry. The build-default plan is used to create the application subscription, which provides access to the SAP Build Process Automation web interface. You need both for a fully functional setup.
Yes. A technical user account is required to register the agent to your tenant. If you do not have one, contact your SAP BTP administrator before beginning the agent installation steps.
Yes. Navigate to Entitlements > Edit > Add Service Plans at any time to add additional plans such as storage, standard-user, api-calls, or addon (for UiPath connectivity). Adding plans later does not disrupt your existing configuration.