Skip to Content
Product Information

SAP Business Technology Platform: Upgrading from Feature Set A to B

What is new with cloud management tools feature set B?

You may have already read (see Cloud Management Tools – Feature Set Overview) that cloud management tools feature set B brings many new and long-awaited functionalities to SAP BTP, which fulfils the needs for managing large account structures and for the automation of cloud management tasks. To name a few of these enhancements:

  • Directories are an additional entity to support more granular account structures and provide efficient management of your users and entitlements.
  • Custom properties that allow you to assign of additional data, such as ‘Cost Center ID’ or ‘Owner’ to directories and subaccounts.
  • APIs and a command line interface (sapcp CLI) that gives you programmatic access to SAP BTP. APIs and CLI are the basis for any automation of administrative tasks and integrations with controlling systems.

We’re excited to announce that we’ve now started upgrading enterprise accounts from the existing cloud management tools feature set A to the renovated cloud management tools feature set B.

What does the upgrade mean?

Upgrading means that the SAP BTP cockpit and your account structure will be updated to the enhanced feature set B version.

During the upgrade, services that are activated on SAP BTP are not impacted by the upgrade and they will work without any disruption. However, while the upgrade is running, you won’t be able to manage your account structure, or activate and deactivate services. Optimally, the upgrade of each account should be completed within a couple of hours or at the most within one day.

For safeguarding the upgrade, our SAP cloud operators conduct a preflight check to ensure that everything is primed for the upgrade. All existing feature set A capabilities are supported in feature set B with the exception of a custom IdP for platform users (see Bringing your corporate identity to platform users). If this feature is in use in your feature set A account, we’ll have to postpone the upgrade to a later time once it’s supported. It is planned to release this feature on feature set B later this year. Custom IdPs for application user is already supported in feature set B so this shouldn’t be a problem for upgrading your account.

For preparing and conducting the version upgrade, no effort is required on your side. SAP monitors each version upgrade closely.

How to apply for the upgrade?

We have already started with the first set of customer accounts. Since SAP’s first priority is to ensure that the version upgrade works well, only a limited number of customers will be upgraded at the same time. Hence, it should be assumed that the upgrade phase will take several months.

All accounts will be upgraded to the new feature set B version, majority will be an upgrade without prior notice since there is no impact on service runtime availability. Nevertheless, please note if you like to get for your account upgraded, you have the option to issue a support incident so that your request be addressed sooner. In this case, please open a BCP support incident on the component BC-NEO-CIS-OPS and all further communication will then be done via this channel. For these upgrade requests, the standard SLA metrics do not apply.

For additional information about the upgrade process and about which details you need to include in the request, please read this SAP Note (3027721).

You must be Logged on to comment or reply to a post.
  • Dear Stephan,

    you said

    All existing feature set A capabilities are supported in feature set B with the exception of a custom IdP for platform users (see Bringing your corporate identity to platform users)

    We do have custom IdP (Azure AD) setup for Marketing Cloud (bundled IAS), C4C, SAC (bundled IAS) and IBP (bundled IAS). We (in my opinion) do not use the custom IdP for Logon to the BTP cockpit, so when we log onto "" I Use my SAP Passport SSO (my S-User) to log on.

    Am I correct that a switch to Feature Set B would not affect all the services that are authenticated via custom IdP (MKT, C4C, SAC, IBP)