3284300 - Subscribing to SAP Build Process Automation (BPA) from SAP Business ByDesign

You are trying to scope SAP Build Process Automation (BPA) in a tenant, however the system throws the below error when you finish the scoping changes:

"SAP Process Automation scoping not permitted; SAP Intelligent RPA already exists for tenant XYZ. See KBA 3284300." (XYZ represents another tenant from your landscape)

or

SAP Process Automation scoping not permitted; SAP Intelligent RPA already exists for multiple tenants. See KBA 3284300

or

Adding SAP IRPA to scope not allowed; use SAP Process Automation

SAP Business bydesign

1. Go to Business Configuration work center.
2. Go to Implementation Projects view.
3. Select the active implementation project.
4. Click on the Edit Project Scope button.
5. Proceed to the Scoping section.
6. Expand the scoping elements Communication and Information Exchange -> Integration with External Applications and Solutions.
7. Check the checkbox for Integration Scenarios for Cloud Solutions from SAP.
8. Proceed to the Questions section.
9. Expand Communication and Information Exchange -> Integration with External Applications and Solutions, and click on Integration Scenarios for Cloud Solutions from SAP.
10. Check the checkbox for the question "Do you want to enable integration with SAP Build Process Automation (BPA)?".
11. Finish the scoping changes.

Cause 1:
You are scoping BPA in same tenant where iRPA is also scoped, or iRPA is scoped in at least one of your tenants under the same account, including the decommisioned tenants.

Each customer account is entitled to have either SAP Intelligent RPA (iRPA) or SAP Build Process Automation (BPA).

Cause 2:
Each tenant landscape (that is, the group of tenants that are grouped in the same SAP Account and are visible in Service Control Center -> Systems) is entitle for the use of either iRPA or BPA. It is currently not possible to have both features scoped, even in different tenants.

It seems that BPA is being scoped in this tenant, however iRPA is already scoped in one of your tenants from this landscape. This needs to be adjusted in order to proceed.

Cause 3:

The BPA/iRPA scoped tenant could have the Restore Point collection enabled.

In order to scope BPA, user needs to descope iRPA in all the tenants and then proceed with the BPA scoping.

Please note that once you iRPA is descoped then all the environment, agent, package, projects, custom bots and any enhancement on top of standard bots will be deleted, and the setup needs to be done again in BPA.

Also ensure to deactivate the Restore Point Collection before proceeding with merging the change project (BPA/iRPA scenario).

Once the tenant that contains the iRPA scoping is identified, the descoping can be performed following the steps below:

1. Go to Business Configuration work center.
2. Go to Implementation Projects view.
3. Select the active implementation project.
4. Click on the Edit Project Scope button.
5. Proceed to the Scoping section.
6. Expand the scoping elements Communication and Information Exchange -> Integration with External Applications and Solutions.

The iRPA can be removed from the scoping by unchecking the checkbox for Integration Scenarios for Cloud Solutions from SAP.

If you are using any other integration features, you can proceed to the next steps to remove only iRPA from the scope:

7. Proceed to the Questions section.
8. Expand Communication and Information Exchange -> Integration with External Applications and Solutions, and click on Integration Scenarios for Cloud Solutions from SAP.
9. Uncheck the checkbox for the question "Do you want to enable integration with SAP Build Process Automation (BPA)?".
10. Finish the scoping changes.

Note: If you have verified that the above mentioned configurations are correct and are still experiencing issues, please report a case to SAP Support.

SPA, iRPA, scoping, scoping not permitted, BPA , KBA , spa, irpa, scoping, scoping not permitte , AP-ML-RPA-PRV , ByDesign - Robotics process Automation - Tenant Provisioning , Problem