Sap s 4 hana client strategy

Client strategy
Daniel Boehm, Raquel Martinez, Van Vi Version 3.2
SAP S/4HANA RIG December 2017

© 2016 SAP SE or an SAP affiliate company. All rights reserved. 3
Public
Objective
 The intent of this presentation is to show the different client settings available to comply with
customer requirements, recommendations of SAP and in some cases, requirements for setting up SAP
S/4HANA best practices.
Depending on the customer requirements the best scenario should be chosen and adapted. Please
also note the content are what the RIG have recommended and seen implemented on various project
implementations. There maybe other options that are not documented but are viable based on
customer requirements.
 Applicable releases
✓ SAP S/4HANA 1511
 Intended group of readers
✓ Consultants

Public
Assumptions
 Please refer to the Embedded SAP BW Definition and Positioning presentation for product
management recommendations for the embedded BW client inside S/4HANA instance. In
general there are two scenarios:
✓Separate client for embedded BW
✓On the same client according to certain use cases including BPC optimized for S/4HANA (see ” Assumptions – Client
Distribution” slide)
Nevertheless for building an Enterprise Data Warehouse with SAP BW, SAP recommends to
use a separate SAP BW system
 All outlined client strategies are based on 4-tier system landscapes with Sandbox, Development,
Quality Assurance and Production environments, the following slides will show the different options
for client configuration on each one of these environments
 Additional clients for training or different project phases could be added to the Quality assurance
environment at the Project team discretion. This is outlined in the Quality assurance client box with
“…..” to illustrate additional client can be created.

Public
Assumptions – Client Distribution

Public
Documentation for Embedded Analytics and BPC for S/4HANA
Finance
 Configuration Steps for S/4HANA Analytics – 2289865
Note: If the application shall be used in a distributed S/4HANA system landscape (separate Gateway frontend
server) note 2106016 needs to be considered.
 Setup SAP BPC optimized for S/4 HANA Finance and Embedded BW Reporting (aka
Integrated Business Planning for Finance) - 1972819

Public
Typical Possibilities on 4 Tier Landscape Setup
Sandbox Development
Quality
Assurance
Production
Transports Transports
1
2
3
4
1
2
1
2

Public
Client classification
We have identify different client types according to their main purpose and adjust the settings according
to that classification. The figures below describe each one of the client classifications used in this
document.
Explore
• Client to review
solution
functionality to
confirm
business
requirements
that met with
standard SAP
Best Practices.
• Intended to
provide the
platform to run
solution design
workshops to
capture,
prioritize, and
document
requirements
and gaps
Embedded
Analytics
(BW)
• Client to
enable the
necessary
configuration
for real time
analytics on
the live
transactional
data.
• Will host VDM
(Virtual Data
Models)
Configuration
(Config)
• Client intended
to build the
solution
environment
that is based
on the
business
processes and
requirements
identified using
SPRO
Development
• Client to
create and
test the
additional
enhancement
s to complete
the solution
environment
that is based
on the
business
processes
and
requirements
Unit
Test
/
Test
• Client to test a
complete
solution
environment
that is based
on the
business
processes and
requirements
identified
Production
• Client used
for
production
operation

Public
Sandbox environment settings
System Landscape
Client Settings
 Purpose:
▪ This setting is planned for systems
in Proof of Concept (PoC)
▪ Access planned for all team
members on the Project
▪ No sensitive data is expected to be
hosted in this client
Note: If in the future you want to separate the
embedded BW from the S4 to a standalone BW
system, a separate client is required.

Public
Development environment settings – Option 1
System Landscape  Purpose:
▪ This setting is planned for development system which
could be used for different projects waves
▪ Access planned according to team members role in
the implementation.
▪ No sensitive data is expected to be hosted in the
development or Config client
▪ BW client is separated as per recommendations
▪ Unit test client is meant to test the changes done in
the first 2 clients allowing to test while the project
team keeps working on separate clients

Public
Client settings
S/4HANA OP Backend Server
Development
020 – Config
030 – Development
040 – BW
050 – Unit

Public
could be used for different projects waves but have
limited hardware resources
the implementation.
client 020

Public
Client settings

Public
could be used for different projects waves using SAP
Activate methodology
▪ Access to Explore client would allow the setting of
test data for the explore phase of the project
client 020, where the implementation team will do the
configuration and enhancements
the other clients allowing to test while the project
▪

Public
Client settings
Development
020 – Config
030 – Development
040 – BW
050 – Unit

Public
could be used for different projects waves using SAP
Activate methodology
▪ Access to Explore client would allow the setting of
test data for the explore phase of the project
the implementation.
development or Config client
▪ BW client is separated as per recommendations

Public
Client settings
Development
020 – Config
030 – Development
040 – BW
050 – Unit

Public
Quality Assurance environment settings – Option 1
System Landscape
Client settings
 Purpose:
▪ This setting is planned for quality system which is not
planned to be used for different projects waves.
▪ Test client is meant to test the changes done in the
development system
Note: If in the future you want to separate
the embedded BW from the S4 to a
standalone BW system, a separate client is
required.

Public
System Landscape
 Purpose:
▪ This setting is planned for quality system which could
be used for different projects waves , additional test
client could be added for training purposes.
▪ Separate BW client allows to setup an strict control
on the test client(s) configuration
▪ Test client is meant to test the changes done in the
development system

Public
Client settings

Public
Production environment settings – Option 1
System Landscape
Client settings
 Purpose:
▪ This setting is planned for production system.
▪ BW client in place with production configuration to
save up hardware resources
Note: If in the future you want to separate the
embedded BW from the S4 to a standalone BW
system, a separate client is required.

Public
▪ This setting is planned for production system.
▪ BW client is separated from the production client to
allow a better control on the embedded related
activities in the production environment and also to
be prepared in case additional clients could be
required

Public
Client settings

Public
Transport Route Example 1
Sandbox
Development
Quality
Assurance
Production
Transports
Transports
4
1
1

Public
Transport Route Example 2
Sandbox
Development
Quality
Assurance
Production
Transports
Transports
4
2
2

R
I
G
EGIONAL
MPLEMENTATION
ROUP
Thank you Contact Information
Daniel Boehm
S/4HANA RIG Americas
daniel.boehm@sap.com
Raquel Martinez
ra.martinez@sap.com
Van VI
van.vi@sap.com

Sap s 4 hana client strategy

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Sap s 4 hana client strategy

Similar to Sap s 4 hana client strategy (20)

Recently uploaded

Recently uploaded (20)

Sap s 4 hana client strategy