Technical

Initial Signoff
Analysis
Discovery

You are
HERE Sizing and Technical Assessment
Migration Planning Readout Onboarding

RISE with SAP S/4HANA Cloud, private edition

Sales & Services Authorization Enablement
BoM Validation
Cloud Architecture & Advisory Team (CAA), March 2023

INTERNAL – Authorized for Partners

Learning Objectives

RISE with SAP S/4HANA Cloud, private edition, will hereafter be referred to as “PCE”.

After finishing this course, you should be able to:

➢ Use the PCE PAM as a validation tool to confirm the BoM, and

➢ Locate and download the PCE template architecture files.

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | INTERNAL - SAP and Partners Only 2
Overview

The activities for the BoM validation process are:

1) Receiving the PCE BoM
2) Using the PCE PAM as a validation tool to confirm the BoM, and
3) Locating and reviewing the PCE template architecture files

Locate &
Receive Validate
Review
PCE BoM PCE BoM
Templates

1 2 3

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | INTERNAL - SAP and Partners Only 3
1) Receive the BoM

The Partner Cloud Architect will receive a PCE-specific Bill of Materials (BoM).

The following information is required for every line item:

▪ PCE product ID (aka material codes or SKUs)
▪ PCE product description
▪ Unit and quantity (usually FUEs, number of documents, or revenue)

* Product ID’s are liable to change between versions

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | INTERNAL - SAP and Partners Only 4
2) Validate the BoM

For this step you will need access to the PCE Product Availability Matrix (PCE PAM)
▪ Ensure you are referencing the latest Version of the PDF file from the PCE Wiki.
▪ Use <ctrl F> to search for the SKU’s provided to you in the BoM
▪ The PDF informs you about the SKU including whether infrastructure components are required, if it is a
license item or an add-on and useful information in the notes section such as prerequisites etc.
▪ You must now translate the output above into an architecture and if PCE compliant, move onto the next step.

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | INTERNAL - SAP and Partners Only 5
3) Locate and review the PCE templates

For this step you will need access to the PCE Templates.

Manoeuvre to the CFU briefcase in the ‘Technical Landscape’ section of the PCE Wiki. Here you will find the
PDF the landscape PDF files that correspond to the components that you have validated in the BoM.

For the example on the previous slide, you would access files in a folder structure like this one:

PCE add-ons will be covered in a separate PCE enablement session.

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | INTERNAL - SAP and Partners Only 6
Summary

Now, you should be able to:

▪ Know what information you need to receive in a PCE-specific BoM
▪ Know how to validate the BoM against the PCE Product Availability Matrix (PCE PAM)
▪ Understand how this translates to PCE architecture requirements
▪ Locate & download the release- and platform-specific PCE templates for the selected sizing tier

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | INTERNAL - SAP and Partners Only 7
Thank you.
Please reach out to your Regional SAP Partner CAA in case of any additional clarifications/questions
Follow us

www.sap.com/contactsap

© 2022 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.