1 - S/4HANA Cloud, private edition

1. Overview
Note: ECS Delivery, please do not use this wiki page as ECS release information for PCE SKUs. This Wiki
only serves as tool for CAAs to check compatability for customers up to release S/4 HANA 2020, currently.
Private Cloud edition customers can have a release which is outside of this Wiki page and is an available release
in ECS e.g. currently S/4 HANA 2021. CAAs would have to check compatibility of any other PCE SKUs
requested by customer on releases not maintained in this wiki page.

S/4HANA Private Cloud Edition (PCE) a standardized ECS environment, which is

• A private managed cloud solution

• Using private IP space, non-overlapping, to be provided by the customer
• Integrating into the customer private DNS using a dedicated (eg. “sap.customer.com”) DNS zone
• An extension of the customer’s internal network through private connectivity
• Absolutely not an internet-only / SaaS solution, which would rather be S/4 Cloud ES / MTE

Key unique selling points are

• charged per FUE / user to the customer

• subscription based licensing
• allows partners to migrate into PCE

2. News & Announcements

Date Updates
9 February 2024 Updated section 7.1 Portfolio with a new topic "Can PCE Deals being sold
without S/4HANA or HANA ?"
Updated 4.2.3 Capacity confirmation needed during BOM validation... with additional
28 March 2023
note.
Updated section 4.3.4 (Memory Extension & Additional Tiers) - revised the table in item
21 March 2023
#1
New JAN 23 PL with SKU replacement on hold. "Old SKUs are still valid. New updates
23 January 2023
coming
12 December Updated section 4.3.7 Guidance for SAP S/4HANA Cloud, extended edition installed base
2022 customers moving forward.

INTERNAL – Authorized for Partner

 Updated section 4.3.4 point #1 footnote (anything above 6TiB for AWS and Azure will
need minimum 3 years duration.).
14 November
Updated section 4.3.4 point #8 (scale down scenarios when using Memory Extension).
2022
Updated section 4.3.8 for important notes when comes to DR relevant(connection
packages-network connectivity)

3. Commercialization process
More details about the process can be found in Jam. It is expected to be familiar with the solution itself before
opening a request: Cloud Service Description Guides

4. Deployment Information
4.1. Portfolio & Roadmap
4.1.1. SKU overview with price list release on Major SKU from 10/23

• S/4 HANA PCE Solution Mgmt team published an overview with the latest guidance on the different
S/4 HANA SKUs

4.1.2. Specific Guidelines for RISE with SAP S/4HANA Cloud, private edition, base option
(SKU 8014072)

• No hyperscaler
o Default motion is SAP DC
o C4C can be used only in countries/MU’s where there are data sovereignty issues or no SAP
datacenter option is available
For C4C deployment scenario
• NEW: For default delivery timeline please see ECS Document
• 512GB is the maximum memory size per HANA database, per Tier, per Solution - possible as of 30-
Sep-2022, until 31-Dec-2022.
• The primary solution in scope for each opportunity must be S/4 HANA XXS.
• Standalone packages are allowed – e.g SAP S/4HANA Cloud for extended warehouse management,
extra stack, private edition - (8013804)
• No upper limit on number of solutions per opportunity.
• Memory extensions are only allowed up to max 512 GB per DB server. With memory extension, if DB
memory size is greater than 512GB, then custom CDD process must be followed

4.2. Committed Delivery Date (CDD)

4.2.1. Standard Committed Delivery Dates (CDD)

4.2.1.1. for general PCE Hyperscaler deployment are maintained Provisioning Timelines Document

INTERNAL – Authorized for Partner

4.2.1.2. for RISE with SAP S/4HANA Cloud, private edition, base option (SKU 8014072) on SAP
DC please follow 4.1.2

4.2.2. Custom CDD request needed for

4.2.2.1. Custom-specific image deployment

Avoid as much as possible non-standard builds. In some specific cases like non-standard image delivery,
it’s inevitable. For those cases be aware that the standard CDD’s do not apply. You need to have a PQA
engagement being created DURING the sales cycle to process CDD requests and handle capacity planning
with GDO via PQA process. SAP Best Practices deployment or EML deployment don’t require customer-
specific CDD requests. See additional detail on SAP EML and other SAP delivered template solutions in
SAP S/4HANA Cloud, private edition

4.2.3. Capacity confirmation needed during BOM validation...

SAP S/4 HANA, private cloud edition (PCE) - Provisioning Timelines#CapacityCheckInformation

4.2.4. NEW: Best Practices (no custom CDD required any longer)

Check out latest dates as per standard delivery document from GDO and BP Wiki. For BP activation
aligned during Sales cycle (2nd scenario) the following extra days apply:

• 2 working days to cover BP preparation efforts on delivery side

4.3. Specific deployment/upsell information:

4.3.1. Additional App Server (link)

4.3.2. Startup Package

4.3.3. Long Term Backup Demonstration

4.3.4. Memory Extension & Additional Tiers

1. [Important] CAA to check the memory extension table to determine the number of memory extension
required to reach the target HANA size.

2. Memory Extension is allowed for HANA Sizes up to 12TiB only.

Anything beyond 12TiB cannot be handled by Memory Extension rather such deals need to switch to
PCE Tailored Option.
This rule is applicable to all New PCE Packaged Customers and also for the existing PCE Packaged
Customers.

Short Term Selling

(Min duration 3 Azure AWS GCP
months)

INTERNAL – Authorized for Partner

 Supported Up to 6 TiB Supported Up to 6 TiB Supported Up to 6 TiB
Additional non-Prod
& Prod Tier >6TiB are not supported >6TiB are not supported >6TiB are not supported
for short-term. for short-term. for short-term.
Supported Up to 6 TiB Supported Up to 6 TiB
Supported Up to 12 TiB
Memory Extension
>6TiB are not supported >6TiB are not supported
for short-term. for short-term.

3.

4. Following are the SKUs for Memory Extensions – this is strictly meant for PCE Packaged ( not for
Tailored Option )
SAP Cloud, memory extension for non-productive tiers, private edition - (8011727)
SAP Cloud, memory extension for productive tiers, private edition - (8011726)

5. CAAs are able to use these Memory Extension SKUs for all the solutions which has HANA as the
database.

6. Memory Extensions SKUs can be used as “Short-term SKU or Early ending SKUs” as mentioned in the
Short-term SKU guidance within this wiki.

7. Memory Extensions (ME) in PCE packaged does not works the same way as the System Extension in
S/4HANA Cloud, extended edition (EX).
ME will only scale up the HANA Memory Size in the block of 256GiB but it never change the t-shirt
sizing.
e.g. Customer who are in XXS now and subscribed 1 ME package for Prod does not bring customer
from t-shirt XXS to XS.
Also, please check the rules for additional App servers when using Memory Extension (See 4.3.1 Slide
#5)!

8. CAAs can use Memory Extensions together with the Additional Tier SKUs.
The rule of thumb is always start with the closest t-shirt size of the existing Additional Tiers SKUs.

Scenario #1 : Customer expecting a 768GiB additional tier for S/4HANA.

CAA should always get the closest SKU.

In this case CAA will suggest the “1 x 512GiB additional tier SKU” + “1 x memory extension SKU” in
order to get a 768GiB additional tier.

Scenario #2 : Customer expecting a 1TiB additional tier for S/4HANA.

CAA should always get the closest SKU.
In this case CAA will suggest the “1 x 1024GiB additional tier SKU”.
(It would never be possible to use memory extension to reach to a target HANA size where the target
HANA size already have dedicated SKUs in the pricelist).

Scenario #3 : Months after the initial contract signed based on Scenario #2 , customer submit a Change
Request and would like to scale up the 1TiB additional tier to 2TiB.
In this situation, the only way out is to remove the 1TiB additional tier SKU and add the 2TiB additional
tier SKU. (Contract Replacement process)
INTERNAL – Authorized for Partner
 Memory Extension SKUs cannot be used in this scenario.

Scenario #4 : Customer subscribed additional tier 512GiB in the initial contract. Few months later,
customer raise a Change Request (CR) to scale up this 512GiB additional tier instance to 768GiB.
IN this situation, the same in Scenario #1 will be followed. Customer will buy 1 x Memory Extension.

9. “Section 4.2.3 Capacity confirmation needed during BOM validation” within this wiki should be
followed.

10. In the situation where it is relevant to scale down the HANA memory, please take note of what scenarios
is allowed.
ECS support to scale down the HANA (e.g. in a scenario of temporary memory extension SKU being
used) as long as the HANA VM is 4TiB and below. No ticket approval will be required.
Important: ECS will not be responsible to reduce the customer data of the system (e.g. via DVM /
Archiving), and this will be customer's responsibility. ECS will only scale down the HANA VM size
based on the contract after customer has reduced the data.

Scenario #1 : Customer signs a contract with e.g. 256GB and DB is growing beyond the original T-
Shirt over time.
Using the memory extension SKU, the customer can receive an upsell that temporarily extends memory
to 512GB (for e.g. 6 months) until housekeeping (customer's responsibility) brings the DB size back to
256GB T-Shirt.

Scenario #2 : Customer signs a "brownfield" contract.

a. The FUE mapping and Sizing point to XXL Size and customer buys XXL. Even if the customer
executes archiving/cleanup the size cannot be reduced as we cannot reduce FUEs.

b. FUE mapping points to L Size but sizing requests XXL HANA size. Customer plans archiving
project during the runtime of the contract.
Solution: Customer buys L for whole contract duration and temporarily extends memory according
project plan, i.e. putting short term SKU “on-top” L-sized HANA. In case of project plan changes
additional upselling of the temp SKU in 3 months increments is possible.

4.3.5. 99.9% SLA Guidance

4.3.6. Converting existing contracts(HEC/EX/STE) to S/4HANA Cloud, Private Edition

4.3.7. SAP Connection packages

Two SKUs of connection packages has been released to the price list recently. One is for non-Production
Tier and another one is for Production Tier.
Customer can only select ONE of the support solutions.

In SDG, the "VPN Connection" and "Direct Line" were listed in both SKU but there is no concept of
Prod / non-Prod in ECS for network connectivity.
As aligned with Solution Management, CAA can use the non-Production SKU to get the network
connectivity (VPN / Direct Line) entitlement.

INTERNAL – Authorized for Partner

 As aligned with Solution Management and ECS, it is possible to use "SAP Connection packages" to scale
up the existing connectors as well as long as the costs of scaling up doesn't exceed the costs of the
additional connectors.
example
Customer already have 1 non-Prod DS agent and 2 Prod DS agent currently. These DS agent has 16GiB
RAM for each. Now customer want to scale up all these DS agents to 32GiB each.
As long as the "cost of 1 x non-Prod DS agent (32GiB each)" is lower than the "cost of 2 x non-Prod DS
agent (16GiB each)" and also the "cost of 2 x Prod DS agent (32GiB each) " is lower than the "cost of 4 x
Prod DS agent (16GiB each)" then we will be able to use the "SAP Connection Packages" to scale up
from 16GiB to 32GiB for the DS agents by including the following SKUs to the CR for this particular
example.
1 x 8014268 SAP Connection Package for productive tiers, private cloud edition
1 x 8014275 SAP Connection Package for non-productive tiers, private cloud edition

Important notes when comes to DR relevant(specifically to network connectivity)

Scenario #1 : If customer doesn’t require DR to be included in their contract then customer will need to
subscribe the following SKU to get the additional VPN/MPLS in Primary : SAP Connection Package
for non-productive tiers, private cloud edition - (8014275)

Scenario #2 : If customer requires DR to be included in their contract then customer will need to
subscribe the following SKU to get the additional VPN/MPLS in Primary & Secondary : SAP
Connection Package for productive tiers, private cloud edition - (8014268) + the DR SKUs will
come on top.

Scenario #3 : In case customer purchases DR as upsell (e.g. via change request) then customer will need
to subscribe the additional quantity of following SKU to get the additional VPN/MPLS in Secondary :
SAP Connection Package for non-productive tiers, private cloud edition - (8014275)

4.3.8. Disaster Recovery Services in RISE PCE

The following table provides an explanation on what is commercially available with respect to Disaster
Recovery services in RISE Private Cloud.

INTERNAL – Authorized for Partner

 * the non-standard RISE PCE deal process must be followed e.g. CDD requested before contract
signature. As the landscape templates for SDDR are currently not created each deal where SDDR is
required needs to follow the non-standard deal process for PCE. Meaning, CDD is created in advance of
contract signature. This allows the teams from GDO to validate that the correct architecture for SDDR is
specified in PQA.

** Please refer to the delivery template of Short Distance DR

4.3.9. Phased Disaster Recovery

Please refer to RISE DR Phasing Guidance.

[19-Feb-2024] Added information for the scenario for "PCE Customer" who doesn't
have CS/ERS separation and wanted to SDDR with CR process / DR SKU.

[19-Dec-2023] Updated guidance for Agents/Connectors SDDR, Phased SDDR & SDDR as Upsell.

For Delayed/phased SDDR, it is mandatory to have the CS/ERS separated from day 1 until the SDDR
start date. Until the time the PCE package templates are updated, customer will need to subscribe the SAP
Connection Package (PROD) to achieve the separation, i.e. add SKU 8014268 from day 1 till start of DR
phase. This is applicable for NW Hana systems and for all Hyperscalers.

4.3.10. CS/ERS separation in PCE Packaged and PCE TO.

PCE Packaged

There is an on-going exercise (as per Dec-2023) to update the PCE package's templates to have the
CS/ERS separation but until that happen, please use the following guidance for PCE packaged.
INTERNAL – Authorized for Partner
 CS/ERS separation in PCE packaged is not mandatory if it is not currently in the template. (in case for
SDDR and 99.9% scenarios, please refer to the respective templates).

If customer has pressing need of CS/ERS separation (e.g. lock entries replication) but the current template
doesn't have it, then customer will need to subscibe the SAP Connection Package (PROD) to achieve the
separation (i.e. Add SKU 8014268)

For Delayed/phased SDDR, it is mandatory to have the CS/ERS separated from day 1 until the SDDR
start date. Until the time the PCE package templates are updated, customer will need to subscribe the SAP
Connection Package (PROD) to achieve the separation, i.e. add SKU 8014268 from day 1 till start of DR
phase. This is applicable for NW Hana systems and for all Hyperscalers.

4.4. Software Stack Information

The software stack, software release levels and general compatibility contained in each PCE SKU is managed
by SAP Solution Management.

Software Stack Information has been moved to a dedicated XLS file. As updates will happen frequently, it is
recommended to always download the latest version.

The PCE Software Stack is a reference for CAAs during the presales phase and sales to delivery handover, to
determine the software stack and release levels to be deployed for individual customers. It is not an asset to be
followed by ECS delivery and operations.

4.5. Partner Extensions & Add-ons

Latest certified partner Add-ons are listed here:

• Partner Addons for EX (also applying to PCE)

• S/4 HANA Partner Add-ons

4.6. Default Build Parameters

• Greenfield Customers:

•
o Refer default build parameters maintained in the document for the standard build (non-image
based approach).
o Refer default build parameters maintained in the document for the image based approach.

Customer checklist with customer build input is mandatory during S2DHO for the greenfield system
build.

• Standard build comes with standard parameters and no Business Function activation done (as indicated
in PCE Provisioning Document). Any additional activities must be requested by the customer via SR’s
after contract start-date.
• The first S/4HANA sandbox system is provisioned from an image with default parameters and it is
recommended not to deviate. If there are more S/4HANA sandbox systems, it's recommended to follow

INTERNAL – Authorized for Partner

 the naming same convention as defined for S/4HANA Additional Tenant in extended edition - default
parameters for first S/4HANA sandbox system:
o ABAP SAPSID: SS1
o HANA SID: HS1
o Web Dispatcher SID: W01
o ABAP client: 100

• Brownfield Customers: Based on customer's environment that is migrated.

• For IBP scenarios the EIM DP Server is not deployed on S/4 in PCE and therefore the DP Agent SID
need not be same as DP Server SID.

4.7. SAP Model Company applicability to PCE

See a dedicated WIKI page SAP EML and other SAP delivered template solutions in SAP S/4HANA Cloud,
private edition for more information about EML/MC in S/4HANA Cloud, private edition.

4.8. SAP Best Practice activation in PCE

See a dedicated document page "SAP Best Practice activation in PCE / advanced R&R " for more information
about BP activation in S/4HANA PCE.

4.9. Cloud Application Services (CAS)

CAS can be delivered with a PCE deal in two ways, 1) using pre-defined fixed scope/fixed priced packages or
2) using custom packages.

4.10. Requesting "additional services" via SR

Current R&R is holding a Category called "additional services", These services can be requested by the
customer via SR and billing is done in arrears. Any Service request raised by a PCE customer for the R&R
category “additional services” will be handled ECS internally (CDM & PL) and does not require any CAA
involvement!

4.10.1. How to handle Additional Data Handover (BASIC_1.8.13)

Additional Data Handover consists of two cost components:

Cost #1: Infrastructure

1.
1. File system Storage – for the backup to be taken (ECS SE has confirmed that this storage can be
Filesystem storage and no need to use the HANA DB storage)
2. Object Store - to move the backup from filesystem to Object store and provide the access to
customer

Cost #2: Additional Service

As part of the Additional Data Handover process there are two options to get the backup:

INTERNAL – Authorized for Partner

 Option #1: Download the last successful backup from the Networker+DDvE to the DB server, then copy to
Object Store. From there customer can copy the backup to their network.

Option #2: Run a new backup and the backup will be stored on the DB server then copied to Object store.
From there customer can copy the backup to their network.

In both these options the storage for DB server and Object store needs to be priced.

In case object store cannot be used then can mount the storage to app server or IaaS Server and then copy
the backup from app server/IaaS server to customer network.

5. Migration
5.1. General information
• Important: Storage requirements in the light of migration needs to be part of the BOM. Pls check the
guidance for short term SKUs
o GCF guidance in EEI (Early Ending Items) can be found here
o For further guidance on storage pls see the General information on Migration scenarios with
Rise!
• New: General information on Migration scenarios with
• ECS supported migration approaches for "Partner-Led" and "SAP Services"
• Partner JAM Site with information for Partners (coming soon)

7. Useful Information
7.1 Portfolio
• Can PCE Deals being sold without S/4HANA or HANA ?
The general guiding principle is as below:
1) costs need to be covered
2) pricelist prerequisites cannot be dropped as they ensure both, cost coverage and also technical
feasability/requirements.

Summarized these scenarios to 3 categories and with examples below:-

Cat #1 Extra Stack Solutions based on S/4HANA with Setup Costs included - 100% Standalone
solutions by purpose and design (where this makes sense from business perspective and
commercialization reflects this as well)
Examples: 8012529 SAP Payroll Processing, private cloud edition, extra stack; 8013708 SAP Global
Trade Services, edition for HANA, private edition; 8013792 SAP Manufacturing Execution Cloud,
private edition. These have been commercialized "standalone" which refers to "Setup Costs for
datacenter included", thus no RISE prerequisite in pricelist. Can be sold to customer that start their

INTERNAL – Authorized for Partner

 RISE Journey with HCM.

Cat #2 Extra Stack Solutions with RISE as prerequisite (as they don't include Setup Costs for a new
datacenter and should be always sold in a RISE context) - here, the RISE prerequisite could be dropped
in rare exceptional cases, if the Startup and Connectivity SKU is being sold on request.
Example: 8012626 SAP Fiori Hub for HANA, private cloud edition (XS)

Cat #3 Private Cloud Solutions which can be sold independently, also w/o a RISE context:
Examples: 8016403 SAP Teamcenter by Siemens, 1-100 Small, private cloud edition; 8016017 [&
8016043] SAP BusinessObjects Business Intelligence, private cloud edition, connection [standard user];
8008735 SAP BW/4HANA Cloud, base package, private edition

INTERNAL – Authorized for Partner