This blog is intended and targeted towards basis consultants who are new to RISE with SAP and wanted to have a basic understanding on the same.
This PART1 blog mainly focuses on RISE with SAP basics, a deep dive into PCE architecture,HA,DR ,Networking ,sizing,Infrastructure scaling
Migration strategy, execution,timeline and AMS will be covered in the next blog- PART 2
Acronyms that will be used across this blog are below:
PCE or SAP S/4HANA Private Cloud Edition
SAP S/4HANA cloud or SAP S/4HANA public cloud or SAP S/4HANA Cloud Essentials
Hyperscalers: Iaas cloud provider (AWS,Azure,GCP, Alibaba)
BOM: Bill Of Materials
FUE: Full Usage Equivalent
SUD: Service use Description
R&R: Roles and Responsibilities
RACI: Responsible, Accountable, Consulted, Informed
CPEA: Cloud Platform Enterprise Agreement Credits
TCO: Total Cost of Ownership
For better understanding the entire blog is created in a question and answer format for quicker understanding for the readers.
SECTION1: INTRODUCTION 1.What is RISE with SAP? 2.What is included under RISE with SAP? 3.What are the RISE with SAP cloud deployment options available? 4.What are the available cloud providers(hyperscaler) valid for RISE? When can the customer make a choices on their own and when they can not? 5.What are the key driving factors that must be considered while choosing between RISE with SAP S/4HANA public Vs private cloud(PCE)? 6.What are the upgrade related constrains between SAP S/4HANA public and private cloud ? 7.What are the key differences between SAP S/4HANA cloud(also called as SAP S/4HANA Public cloud) , SAP S/4HANA PCE(also called as private cloud edition) and SAP S/4HANA on-premise deployment? SECTION 2:PCE 8.What is PCE?(SAP S/4HANA Private Cloud Edition) 9.What a customer can expect with buying a subscription of RISE with SAP S/4HANA PCE? 10.What are the scope of tasks that are under partner for a customer who has subscribed to RISE with SAP S/4HANA PCE? 11.What will happen to the active SAP licenses that a customer owns when they want to transition to RISE with SAP? SECTION 3: ARCHITECTURE, AVAILABILITY SLA,DR for PCE 12.How does my customers architecture looks like in RISE with SAP S/4HANA PCE deployment model?What are the key design principles involved? 13.How is PEC production availability percentage of 99.7% is calculated by SAP? Why can not SAP provide a SLA of 99.9 or more? 14.What is the scope of partners in case of a Disaster recovery? 15.What are the services that customers get from SAP when they opt for a DR service with PCE? SECTION 4:NETWORKING 16.What are the information that must be provided by the customers to SAP for establishing the connection between customer environment and PCE environment? 17.What are the network services that are bundled with the PCE? 18.Who is responsible for the provisioning of the required network connectivity to RISE with SAP S/4HANA Cloud, private edition) from customer landscape.?\ 19.How is customer network gets connected to PCE hyperscaler network? SECTION 5:SIZING AND MAPPING OF FUE: 20.What is FUE in RISE with SAP S/4HANA ? 21.What are the differences between standalone packages and upsell packages? 22.What is Rosetta Stone file used for? 23.How to determine the T-shirt size to be subscribed under RISE for SAP S/4HANA for a customer? 24.How does PCE handles with customer request for infrastructure scalability?
1.What is RISE with SAP?
In my own simple terms, RISE with SAP is an offering from SAP which helps the customers to shift their ERP workloads to cloud on an infrastructure provider of customer’s choice(in case of Private cloud) along with converting it into S/4HANA cloud deployment. This bundles the underlying cloud Iaas cost, SAP’s license cost, SAP provided managed services, client 000 basis management , CPEA credits based on usage, innovative tools that will help the customers to turn to an Intelligent enterprise etc all under one contract under one SLA as monthly subscription.This also helps in unmatched reduction of TCO for customers.
RISE with SAP is not a product. It is not a Iaas or Paas or Saas but a combination of all 3 => Business Transformation as a service
In SAP terms “RISE with SAP is a customer first , partner centric delivery approach that helps the customer to transform into an Intelligent Enterprise. This bundles SAP S/4 HANA Cloud(public/Private), infrastructure that runs on a hyperscaler of customer choice(AWS,Azure or GCP),Business process intelligence , tools(Custom code Analyzer,SAP readiness check,SAP Learning hub), SAP Business Network starter pack and SAP business technology platform all under ONE contract.”
Source Image: SAP
2.What is included under RISE with SAP?
RISE with SAP either on public or private cloud includes tools and services, SAP business process intelligence reports for process analysis improvements, CPEA(Cloud Platform Enterprise Agreement Credits) based on the private(min 4K to 16K per annum) or public cloud edition(min 2K to 16K credit per annum) value.This also includes business network starter pack.
Source Image: SAP
3.What are the RISE with SAP cloud deployment options available?
RISE with SAP cloud deployment options include below offerings:
1.Public Cloud Deployment:
a.RISE with SAP S/4HANA Cloud (formerly SAP S/4HANA Cloud, essentials edition)
b.RISE with SAP S4HANA Cloud for experience management
2.Private Cloud Deployment
a.RISE with SAP S/4HANA Cloud, private edition (from hear on referred as PCE)(Main focus of this blog)
b.ERP private cloud(Applicable for customers who want to move their workload to cloud under RISE, but not yet ready for a S/4 HANA transformation)
Source Image: SAP
4.What are the available cloud providers(hyperscaler) valid for RISE? When can the customer make a choices on their own and when they can not?
With RISE with SAP under public cloud, customer does not get to decide on the underlying infrastructure provider for their workloads unlike for PCE editions . With PCE , choice of cloud providers are under customer control.
Below are the deployment options and the choices available:
A.SAP S/4HANA Public Cloud deployment:
b.SAP data center
B. SAP S/4HANA Private Cloud deployments
a.Hyperscaler data center (chosen by the customer)
ii.Amazon Web Services
iii.Google Cloud Platform
b.SAP data center
c.Customer’s own data center for regulated industries
Source Image: SAP
RISE with SAP(Public cloud):
For Public Cloud, the data center is pre-selected for the customer based on a variety of factors.
RISE with SAP(Private cloud):
For Private Cloud, customers can choose their infrastructure provider: hyperscaler data center or SAP data center. The Infrastructure as a Service (IaaS) provider hosts servers, storage, and other virtualized computing resources where the SAP S/4HANA software is installed. Customers do not have to buy hardware or employ in-house experts to maintain it when hosting their solution in a third-party infrastructure.
5.What are the key driving factors that must be considered while choosing between RISE with SAP S/4HANA public Vs private cloud(PCE)?
For a customer who are ready to embrace the future of ERP with a new implementation and pre-defined content, the choice must be RISE with SAP S/4HANA public cloud (Cloud essentials).
For a customer who wants to realize the innovation and cloud value along with retaining their investments by converting their existing systems , then PCE is the best fit (RISE with SAP S/4HANA private Cloud Edition)
In a much more simpler terms ,any new customers or customers who are looking for new greenfield implementation, RISE with SAP S/4HANA public cloud is the preferred choice . For the brown field implementation, SAP S/4HANA PCE is suitable.
NOTE:RISE with SAP S/4HANA public cloud is a Saas ERP offering from SAP
Source Image: SAP (Points of departure between public and private cloud options for RISE:)
6.What are the upgrade related constrains between SAP S/4HANA public and private cloud ?
For a RISE with SAP S/4HANA public cloud edition a minimum upgrade frequency is 4 times per year unlike PCE where it is 5 years once. With public cloud customer does not have the option to avoid upgrades .
So, any customers who do not want a forced yearly 4 times (min frequency) upgrade must not go for public cloud edition of RISE.
Source Image from SAP
7. What are the key differences between SAP S/4HANA cloud(also called as SAP S/4HANA Public cloud) , SAP S/4HANA PCE(also called as private cloud edition) and SAP S/4HANA on-premise deployment?
-SAP S/W license is covered under monthly subscription model in SAP S/4HANA public and private cloud unlike on-premise deployment that uses perpetual software deployment
-Implementation for all the 3 deployments can be done by either SAP or Partner or customer themself
-Content ownership in case of public cloud is with SAP, unlike PCE edition or on-premise edition where the ownership is with the partners
-For SAP S/4 HANA PUBLIC edition, application managed service, content lifecycle management, product support,technical operations and infrastructures is entirely under the control of SAP and also included as a part of monthly subscription default fee.
-In PCE S/4HANA edition,application management services and content management service is still under Partner and is not included in the subscription. However, product support, technical management and underlying infrastructure is covered as a part of subscription and will be under SAP control.
Key URL for all the technical documentation for PCE
8.What is PCE?(SAP S/4HANA Private Cloud Edition)
RISE with SAP S/4HANA PCE is an acronym of RISE with SAP S/4HANA Private Cloud Edition.
For a customer who wants to be part of RISE with SAP program and wants to realize the innovation and cloud value along with retaining their investments on their existing environment by converting or migrating the same to cloud as SAP S/4HANA, then PCE is a best fit.(Refer Q5).
NOTE:Any customers who are ready for a fresh implementation(green field), then the direction much be SAP S/4 HANA public cloud.
PCE is a standardized HCE environment which is a private managed cloud solution.Customers here will be provided with a non-overlapping private IP space.The PCE environment will be integrated into the customer private DNS using a dedicated (eg. “hec.customer.com”) DNS zone.Customer’s internal network will be integrated into PCE using a private connectivity.
The key take aways are
-With PCE customer can choose the hyperscaler (cloud provider) of their choice, But can not reuse any of their existing contract that they might have with this cloud provider
-The customers will be charged per FUE / user (FUE will be covered in details later in this blog)
-This is a subscription based licensing
-Migrations can be performed with the help of partners
NOTE: One must not get confused with SAP S/4HANA public cloud (SAP S/4HANA cloud or Essential cloud(ES)), PCE is not a internet-only / Saas solution unlike SAP S/4HANA public cloud which is a Saas ERP solution from SAP
9.What a customer can expect with buying a subscription of RISE with SAP S/4HANA PCE?
PCE provides software support, infrastructure management and technical managed services in one single monthly subscription. This ensures a cumulative availability percentage of 99.7% (includes infrastructure, managed services etc) for production environment and 99.5% for non-production environment.DR is not a mandatory component in RISE. However , it is available as an upsell package along with standalone RISE component SAP S/4HANA PCE.
This will help to customer to reduce their TCO, along with utilizing SAP’s capabilities with the managed services support.From a basis perspective, as a partner basis consultant, we will not be provided with OS access .Also all the tasks related to client 000 will be performed by SAP only.
10.What are the scope of tasks that are under partner for a customer who has subscribed to RISE with SAP S/4HANA PCE?
RISE with SAP S/4HANA PCE is a customer first , partner centric approach.
From a basis standpoint , while installation & upgrade, technical landscape deployment, high availability & business continuity are under SAP’s scope, anything other than this , which is functional basis is under partner’s scope. Also SAP does not provides ABAP or functional related support while it does provides the required tools etc.We are also responsible for any performance tuning or any other tasks related to any client other than ‘000’.
Below image depicts the list of activities under partner’s scope in a RISE with SAP PCE implementation. (For SAP’s scope , please refer to image in Q.9)
11.What will happen to the active SAP licenses that a customer owns when they want to transition to RISE with SAP?
For such customers who hold a valid on-premise license ,but wants to move under SAP’s RISE program, SAP has come up with a “Cloud Extension Policy”. With this the customers will be allowed to partially terminate their on-premise licenses and associated maintenance payments (services including SAP® Enterprise Support, SAP Standard Support, or SAP Product Support for Large Enterprises) in conjunction with a purchase of a subscription to cloud solutions from SAP. The
transaction requires an expanded investment with cloud solutions from SAP.
SECTION 3: ARCHITECTURE, AVAILABILITY SLA,DR for PCE
12.How does my customers architecture looks like in RISE with SAP S/4HANA PCE deployment model?What are the key design principles involved?
Below are some of the architecture diagram I have created for better explanation purpose for various hyperscalers.With PCE we get a DEV,QA and a PROD system as a part of subscription
NOTE:Below diagrams were created only for explanation purpose of underlying concept and need not have to be the exact in the actual deployment as this depends on various factors like the T-shift size of the system, any upsell package that customer has bought eg:DR, Additional application server etc.
A.PCE on Azure:
Infrastructure HA SLA's provided by Azure: 1.Single VM in one availability zone with premium disks provides a SLA of 99.9% 2.Two VMs spread across availability set in 1 availability zone in 1 region provides a SLA of 99.95% 3.Two VMs spread across 2 availability zones in one region provides a SLA of 99.99%
B.PCE on AWS:
Infrastructure HA SLA’s provided by GCP:
1.Single compute engine in one zone provides a SLA of 99.5%
2.Two compute engines spread across 2 zones provides a SLA of 99.99%
C.PCE on AWS:
Infrastructure HA SLA's provided by AWS: 1.Single EC2 instance in one availability zone provides a cumulative SLA of 90% on a hourly basis 2.Two EC2 instances spread across 2 availability zones provides a SLA of 99.99%
For reference only: Source Image: SAP
Other architecture basics with RISE with SAP S/4HANA PCE:
1.Auto healing will be enabled for each production VM/compute engine in Azure and GCP respectively. Similarly, EC2 instance auto-recovery is enabled for all the production instance. The main functionality of this is to move the defective instances in cloud (hardware) to a healthy host in case of unavailability.This is done at the hypervisor level. However, these are not application aware
2.Availability of other components like VPN gateway, storage,Load balancer is assured by using redundancy in these components
2.AWS only supports near-dr functionality within the same region. Azure and GCP only supports far region dr across 2 different regions
3.The guaranteed HA SLA of production system of 99.7% does not includes the monthly planned maintenance of 4 hrs despite the fact that , maintenance need not have to happen every month
4.DR is optional under RISE with SAP program.
5.DR SLA for Azure and GCP: RPO=30 minutes, RTO=12 hrs. There is an option for the customer to go for RTO upto 4 hrs. In case of AWS, the RPO=0 and RTO = 12 hrs.Even in AWS RTO can be reduced to 4 hrs based on customer’s request
6.In RISE with SAP, only SAP can invoke a DR strategy. Customer can not decide on the same .If SAP invokes DR , the infrastructures will be failed over to the DR region with the indicated RPO and RTO by SAP
13.How is PEC production availability percentage of 99.7% is calculated by SAP? Why can not SAP provide a SLA of 99.9 or more?
Availability percentage is calculated by multiple factors. In general AWS provides 99.99% of infrastructure availability for EC2 when it is distributed between 2 availability zones . In Azure, 99.99% is guaranteed for the VMs when the VMs are distributed between 2 availability zones ,99.95% when the same is distributed between availability sets in one availability zone and 99.9% SLA for single VMs deployed on premium storage .In GCP , compute engine in different zones guarantees 99.99% and single instance provides SLA of 99.5%. Similar SLAs are also valid for each of the components at network layer, storage layer, security layer etc. All these SLA are not application aware. But these play a key role in the application availability but not the only deciding factor.
The PCE SLA of 99.7% includes a cumulative SLA of SAP application, underlying infrastructure,network etc and hence can not be compared against any of the individual components (Compute, network,storage,security) SLA.
Link to SAP S/4HANA PCE SLA:
14.What is the scope of partners in case of a Disaster recovery?
In PCE environment, as partner will not be provided OS level access , all the infrastructure and client 000 related tasks can be performed only by SAP.As specified earlier only SAP can declare on a DR situation because only SAP can make estimations on the damage to a data center and the time frame it requires to establish a regular operation in that data center again, considering overall data loss, limited operation capabilities, limited software life cycle management, no access to non-production systems, legal aspects, etc.
Below are the tasks that only SAP can perform :
-Implement disaster recovery setup according to architecture blueprint and contractual specifications
-Develop disaster recovery procedures (data center and tech system infrastructure only)
-Ongoing management of disaster recovery architecture: monitoring of data replication to secondary site including troubleshooting
-Ongoing management of disaster recovery architecture: maintenance and change management for systems at secondary site to ensure system consistency including troubleshooting
-Execute Disaster Recovery Tests (data center and technical system infrastructure only). This is performed on request up to a maximum of 1 time per year.
-Execution of productive failover in case of an officially declared disaster
NOTE:As specified ,DR is not part standard PCE package. It is an optional service that customer can opt-in.
15.What are the services that customers get from SAP when they opt for a DR service with PCE?
Below are some of the services provided by SAP for DR upsell package . For more please refer R&R document.
-Disaster Recovery solution
-100% mirrored standby capacity
-Shared DNS service with zone transfer
-Management of communication lines within SAP Cloud infrastructure
-RTO of 12 hours
-RPO of 30 minutes
-Yearly DR failover test (technical)
16.What are the information that must be provided by the customers to SAP for establishing the connection between customer environment and PCE environment?
In order to enable the customer network to be integrated with PCE environment , SAP needs below details from the customer
-Customers are required to provide an IP address space composed of:
- A network segment with a minimum /22 network mask (1022 usable IP addresses), for provisioning the S/4HANA PCE servers, and
- A network segment with /27 network mask (30 usable IP addresses), for backup purposes
NOTE:The following IP address ranges cannot be assigned to a customer’s PCE network and must NOT be used in customer’s remote network environment, to avoid potential routing issues.
-Customers must provide their DNS domain.SAP will create a sub-domain nder the customer’s internal DNS domain to host all PCE servers.Eg. Customer’s existing internal DNS domain is ‘<customer>.corp’. Sub-domain at PCE will be: ‘sap.<customer>.corp’
– To set up conditional zone-forwarding on PCE DNS servers (dedicated to customer) customer must provide the IP address of on-premise DNS servers.
-VPN template will be provided by SAP for which customer must help with the handshaking parameters
-Customer must provide FQDN for each system that needs to be available via internet along with customer SSL signed by public CA
-The CIDR IP block provided by the customer upfront must be large enough to cover the expected growth during the contractual period
-This block must not be used in any on-premise networks
-As soon as this CIDR block is sent to SAP, the same must be blocked by the customer for PCE usage
-These IPs can not be changed after deployment unless SAP rebuilds all the affected systems from the scratch which will result in additional fees as per R&R matrix.
-An average of 3 IP addresses are consumed for each server
-Subnets larger than /16 and smaller than /22 are not supported in PCE
17.What are the network services that are bundled with the PCE?
The following network scope and additional services are included in the PCE scope by default and is part of PCE subscription.
This scope could be adjusted further, depending on the requirements
Service Use Description
Azure Sample only: (Refer SUD for more details)
AWS sample only:
GCP Sample only:
18.Who is responsible for the provisioning of the required network connectivity to RISE with SAP S/4HANA Cloud, private edition) from customer landscape.?\
- Access to S/4HANA private cloud edition via S2S VPN or MPLS is customer’s responsibility (SAP provides the endpoint; Customer is responsible for the provisioning of the required network connectivity to RISE with SAP S/4HANA Cloud, private edition).
- Network sizing and architecture is customer’s responsibility. Customer’s end of the network costs are not included in the quotes
- In case of internet level access (e.g. Fiori) customer domain is required. SAP will use WAF and will require SSL certificate; customer is responsible to provide the CA signed certificate
For more information refer R&R:
19.How is customer network gets connected to PCE hyperscaler network?
All the hyperscaler provides S2S VPN where encrypted traffic traverse through the public internet.
When it comes to private connection , below are the options that are provided by each cloud provider.
1.Azure:Express Route connection.Another option is VNET peering , If customer already have some systems in Azure
2.AWS:Direct Connect connetion.Express Route connection.Another option is VPC peering , If customer already have some systems in AWS
3.GCP:Direct/Partner interconnect.Another option is VNET peering , If customer already have some systems in GPC
Below is a overview of SAP S/4HANA PCE network related connection details.
Image from SAP
SECTION 5:SIZING AND MAPPING OF FUE:
20. What is FUE in RISE with SAP S/4HANA ?
FUE(Full User Equivalent) is the number of user units that is used in RISE with SAP S/4HANA to choose from the various target t-shirt sizes that SAP provides as Standard or upsell packages. This is similar to user type in quicksizer. This is a metric used to calculate the number of users authorized to access specified solution capabilities. It denotes a standardized user.
The SAP S/4HANA Enterprise Management Cloud, private cloud edition (PCE), subscription is priced based on the number of Full Usage Equivalents (FUE). Different user types can be converted to the standard FUE metric using a pre-defined ratio. The number of FUE subscribed by the customer is documented in the order form that will be sent to SAP by customers
Below is the list of user type and their FUE equivalent.
Under RISE program, there is always a need to subscribe for the minimum mandatory FUE for each implementation. Below are the details on the same
NOTE:Source: SAP •All SAP S/4HANA Cloud use types can be purchased by one license material: SAP S/4HANA Cloud for Enterprise Management •This license material has the metric Full Usage Equivalents (FUE) •One unit of SAP S/4HANA Cloud for Enterprise Management i.e. one FUE can be allocated to different use types with a specific weighting factor •Customer can re-allocate their users to avoid shelf-ware during their life-cycle
21.What are the differences between standalone packages and upsell packages?
For pricing and identification purpose, each line item for BOM(Bill of Material) will have an identification number that is called as Material code or product code or SKU.Each of these materials can either be a standalone offering or an offering that has an mandatory prerequisite that must be met.
To be specific, The standalone solutions are bundles consisting of software licenses, infrastructure, and managed services. They are here referred to as standalone packages.Offerings that have a prerequisite are here referred to as upsell packages
A standalone package has several components:
- SAP product landscape including software licenses and hardware
- Connectivity packages for network integration
- Load Balancers – if applicable for the product
- Additional services – dependent on the package.
Review the Service Use Description (SUD) for details.https://www.sap.com/docs/download/agreements/product-policy/css/service-specifications/rise-with-sap-s4hana-cloud-private-edition-service-description-guide-english-v8-2021.pdf
Example of a standalone PCE package purchase by a customer XYZ:
B.Upsell packages:(Need a mandatory standalone package)
Upsell packages are supplementary packages and cannot be sold without underlying standalone packages.
a.License-only packages contain only additional licenses and do not require additional infrastructure.Example: “SAP S/4HANA Cloud, Digital Access, private edition”.
b.Add-on packages are packages that need an add-on to be installed on S/4HANA.Example: “SAP Extended Warehouse Management, industry add-on for SAP S/4HANA Cloud, private edition”.
c.Infrastructure packages require additional infrastructure to be deployed.Example: “SAP S/4HANA Cloud, disaster recovery, private edition”.
Frequently used infrastructure upsell packages are as shown below
To find the entire list of standard and upsell packages refer CFU breif case.https://jam2.sapjam.com/wiki/show/b0g64q32oJAqPonOxVKroM
22.What is Rosetta Stone file used for?
Rosetta Stone is an SAP internal file that helps in identifying customer’s existing OP Software License landscape to similar PCE solutions. This is critical as the first step towards identifying the BOM for the RISE program. However this tool need not be a single point of truth. The partners using this tool must always get the mapping validated by the pre-sales and the regional pricing contact that they work with.
Steps to use this tool:
1. Download the Rosetta Stone Mapping Tool from the below URL.https://jam4.sapjam.com/groups/about_page/4uGux6yFeAM33gOcGFuf2J
2.Partner must work with their MSE / IAE to complete the mapping as this is an internal tool as on date.
3.Copy the Material Number and Description of the software the customer owns (obtained from current SAP internal reporting), paste that data into the “Current Customer
License Scope” titled columns
4. Results will populate to the right. The tool will return results for current ERP On Prem Materials, current S/4HANA On Prem Materials, and current S/4HANA Cloud PE cloud MCs
Sample output: Link: https://d.dam.sap.com/s/p/a/11oF6TZ/Part_1_Sales_Process_Rise_with_SAP_S4HC_PE_HANDOUT.pdf
23.How to determine the T-shirt size to be subscribed under RISE for SAP S/4HANA for a customer?
a.Download the SUD guide
b.Decide upon the required standalone package and upsell packages. (Refer to previous question)
c.Make a note of the usage sizes and the T-shirt sizes .
Eg:For S/4HANA PCE
d.Understand the SKU T-shirt size.
Eg:(From the above diagram)When SAP deploys a system of size XS, the memory can be upto 256GB for production ,quality and development system.This SAP S/4HANA system landscape can have upto 3 PAS(1DEV.1QA.1PROD)
e.Understand the other element that we will be provided with this SKU (eg, Does this allows the customer to opt for a DR, other network related items that the chosen SKU provides)
f.From the customer landscape , understand the user type per system and arrive at the final FUE per system.
g.Compare the above SUM with the t-shirt sizes. With 70FUE, the XS T-shirt size must be chosen.
h.Now what is the exact components that will get deployed with the SAP S/4HANA PCE, XS size.
To find this, we have to look for the templates provided by SAP in the CFU breifcase link.https://jam2.sapjam.com/groups/3IiiOqF98Y0P2WYtz4pUZG/content?folder_id=szrmDvd1OtfsXnZlooJuvb
From that navigate to the SKU of the choice and choose the relevant files with respect to the Hyperscaler chosen.
i.Below is what we get after deploying SAP PCE of T-Shirt size XS.
Below is a depiction of the result of deployment of above configuration
S/4HANA PCE(Private Cloud Edition) is a single tenant deployment of SAP on a dedicated virtual network, in a customer specific dedicated subscription(Azure) or Project(GCP) or account(AWS) which is owned and managed by SAP.
- 3 system landscape deployment (DEV,QA,PROD) . Customer can optionally purchase additional environments to address their specific requirements.
- The target T-shirt sizing is in general based on the license metrics. For more information please refer SUD (https://www.sap.com/docs/download/agreements/product-policy/css/service-specifications/rise-with-sap-s4hana-cloud-private-edition-service-description-guide-english-v8-2021.pdf
- This being a private cloud offering , is created on a customer provided private CIDR address range which is a non-overlapping address block with customer’s on-premise network
- Customer must connect to PCE using a dedicated private network link either via a S2S VPN or dedicated access options such as Direct Connect (AWS), ExpressRoute (Azure), Cloud Interconnect (GCP) .
- Name resolution is configured by creating a dedicated zone under customer’s internal DNS domain(hec.<customer domain>)
- PCE access to public internet is restricted to specific use cases. Mobile users can be enabled for Fiori applications via a secure web application firewall upon customer request. Internet outbound is allowed for cloud Integrations using secure protocols and connecting to other SAP Cloud solutions (Such as Ariba, Concur, SuccessFactors etc.)
- SAP Adobe document services are leveraged from SAP Business Technology Platform by default (“Forms as a Service”). Required integration via SAP Cloud Connector is delivered as part of customer landscape in cloud.
- Customer has an option to subscribe to DR for their production environment in cloud. Failover sites are configured with data replication from productive environments and with equal infrastructure capacity
24.How does PCE handles with customer request for infrastructure scalability?
In PCE, target sizing is generally based on the license usage tier. If there is a need to scale up of HANA systems, it is possible by subscribing either to a higher usage tier or to additional system extensions.
Example: Options for a customer who are in Size “XS” to get upgraded to “S”:
1.Subscribe to higher usage tier
2.Subscribe to system extension packages
Some of the frequently used extension packages are as below
Migration and related methodology will be covered in part 2.
Thanks for reading!