Explaining SAP Business Technology Platform Providers (Regions) and Universal Model Activation

Objective

After completing this lesson, you will be able to activate Universal Model in your Subaccount.

SAP Business Technology Platform Providers and Regions

SAP BTP Providers (Hyperscaler) and Regions

Amazon Web Service (AWS)

Microsoft Azure

  • Brazil (São Paulo); cf-br10
  • Canada (Montreal); cf-ca10
  • Europe (Frankfurt); cf-eu10
  • Europe (Frankfurt); cf-eu11 (EU access only)
  • South Korea (Seoul); cf-ap12
  • U.S. East (VA); cf-us10
Divider

Default Capacity Unit Upon Subscription: 1859

Default Memory Upon Subscription: 64GB

  • Europe (Netherlands); cf-eu20
  • Singapore; cf-ap21
  • U.S. East (VA); cf-us21
Divider

Default Capacity Unit Upon Subscription: 1859

Default Memory Upon Subscription: 64GB

Google Cloud Platform (GCP)

Alibaba

U.S. Central (IA); cf-us30

Divider

Default Capacity Unit Upon Subscription: 1859

Default Memory Upon Subscription: 64GB

China (Shanghai); cf-cn40

Divider

Default Capacity Unit Upon Subscription: 1859

Default Memory Upon Subscription: 64GB

In SAP Business Technology Platform (SAP BTP), region selection, and provider (hyperscaler) choices are critical for optimal performance and compliance. This lesson covers the available providers, region options, default resource allocations, and considerations for selecting the best region for your business needs.

Understanding Providers and Regions

Providers (Hyperscalers):​

Definition: Providers, also known as hyperscalers, are cloud platforms that host SAP BTP services. They offer the infrastructure and capabilities required to run SAP applications.​

Available Hyperscalers:

  • Amazon Web Services (AWS)
  • Microsoft Azure
  • Google Cloud Platform (GCP)
  • Alibaba Cloud

Regions:

Definition: Regions refer to specific geographic locations where the hyperscaler data centers are situated. Choosing the right region ensures compliance with data residency laws and optimizes performance by reducing latency.​

Reference and Updates:

Current as of July 2024: The list of available providers and regions is periodically updated. Always consult the reference section for the most current information.​

Demo Reference:

In our system demo, the subaccount region is Europe, Netherlands, with the hyperscaler being Microsoft Azure.​

Default Resource Allocation​

Memory Allocation:

Default Allocation: Upon subscription, SAP BTP allocates 64 GB of memory by default.​

Dividing Resources:​

If you have multiple tenants, the total memory capacity (for example, 64 GB) must be distributed among them according to your contract.​

Example: If you have two tenants, you can allocate 32 GB to each or any other distribution that fits your needs, but the total must not exceed 64 GB.​

Expanding Resources:​

Increasing Memory: You can request an increase in memory allocation based on your requirements, but it must remain within the limits specified by your contract.​

Overage Costs: Exceeding the contracted memory size incurs extra charges.​

Choosing the Right Region

Geographical Proximity:​

Optimize Performance: Select a region near your business operations and data sources to minimize latency and enhance performance.​

Data Residency: Ensure compliance with data residency and regulatory requirements by choosing a region that aligns with local laws.​

Example:

Business in Europe: For a European business, choosing a region in Europe (for example, Europe, Netherlands) is ideal for regulatory compliance and performance optimization.​

Provisioning

Definition:

Provisioning: In the context of SAP BTP, provisioning refers to the allocation and management of memory and computational resources within a tenant based on the overall capacity purchased under the subscription contract.​

The image shows a screenshot of the SAP Productivity and Performance Management Cloud Preview interface. It displays various configuration options and settings related to productivity and performance management.

Purpose:

Resource Management: Ensures that the tenant's memory and CPU resources are scaled appropriately to meet performance and usage requirements.​

Avoid Performance Bottlenecks: By increasing the allocated memory, you can prevent performance issues and testing failures.

Steps to Provision Memory

Accessing Provisioning:

Navigate to Administration: Log in to the SAP BTP Cockpit and go to the administration section.​

Access Provisioning Settings: In the standard model, provisioning settings can be found under the Setting tab within the Provisioning section.​

Example Scenario: Managing a 512GB contract.

Understanding Default Capacity:

Default Memory Capacity: By default, each tenant is set with 64GB of memory.​

Contract Capacity: If your contract entitles you to 512GB of total memory, the default setting of 64GB per tenant means that any processes exceeding this limit fails unless provisioning is adjusted.

Increase Memory Capacity:

Navigate to Provisioning: Under administration, access the provisioning settings.​

Increase Capacity: Adjust the memory allocation from the default 64GB to a higher value within your contract limit. For example, if performance testing requires more memory, increase it to the required amount.​

Ensure Smooth Performance: It ensures that your processes and performance tests do not hit memory limits prematurely.

Managing the Memory Allocation:

Entitlement Limits: Your total memory allocation across tenants cannot exceed the 512GB limit specified in your contract.​

Dividing Memory: You can split your total memory (for example, 512GB) across multiple tenants based on needs. For example, you might allocate 100GB to one tenant, 200GB to another, and distribute the remaining memory accordingly.

Increasing Beyond Contract Limit:

Additional Costs: If you increase memory capacity beyond the 512GB limit, you incur extra costs.​

Provisioning Confirmation: Once you increase the memory, the system prompts a confirmation indicating that extra charges apply for exceeding the contracted limit.

Decreasing Provisioned Memory:

No Direct Option: While you can increase memory allocation through the provisioning settings, there is no direct option to decrease it back.​

Request Support: To decrease the memory, you must submit a request to SAP support.

The Steps to Activate the Universal Model

Initial Setup:

Subscription: Upon subscribing to SAP PAPM, you initially have access to the standard model.​

Universal Model: Activation of the Universal Model requires extra steps to request and enable the feature.

The image shows a screenshot of the SAP SuccessFactors interface, highlighting the Standard Model section and prompting users to activate the SAP FieldGlass Cloud Universal Model for their tenants. The screen displays various configuration options and settings.

Required Information for Activation:

  • Subdomain
  • Tentant ID
  • Subaccount ID
  • Provider Region
  • Environment

Steps:

Gather Required Information:

Subdomain: It is the specific subdomain allocated to your SAP BTP tenancy.​

Tenant ID: A unique identifier for your tenant in SAP BTP.​

Subaccount ID: The identifier for your specific subaccount within the global account.​

Provider Region: The geographical region where your services are hosted, for example, Europe, Netherlands with Microsoft Azure.​

Environment: The environment details where PAPM is set up (for example, Development, Production).

Raise a Support Request:

Prepare Information: Ensure all the above details are accurately gathered.​

Customer Incident: Open a customer incident in the SAP Support Portal to request the activation of the Universal Model.​

Submit Details: Provide the collected information in the support request. It includes the subdomain, tenant ID, subaccount ID, provider region, and environment.

Await Confirmation:

Support Team Actions: The SAP support team processes your request.​

Granting Access: Upon validation, the support team activates the Universal Model for your PAPM subscription.

Verify Activation:

Log into BTP Cockpit: Once access is granted, log in to your SAP BTP cockpit.​

Check the Administration Section: Navigate to the administration section within your standard model.​

Universal Model Visibility: You now see the Universal Model section available, indicating successful activation.