Download as pdf or txt
Download as pdf or txt
You are on page 1of 12

Week 3: What Else You Should Know About

Unit 5: SAP BW Hybrid Integration


SAP BW hybrid integration
Your task

▪ You need to build a landscape including SAP BW


and SAP Datasphere
▪ To do so, you need to learn how to use BW queries
in SAP Datasphere and how to use remote
authorizations

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2


SAP BW hybrid integration
Customer journey

Status Quo To-Be Architecture


SAP BW or SAP BW/4HANA SAP BW or SAP BW/4HANA SAP Datasphere

Analytics Layer Analytics Layer Data/Business Layer


Hybrid Federation
Staging Layer Including Staging Layer Including and reuse
Combining SAP BW or Spaces
ABAP Extensions ABAP Extensions
SAP BW/4HANA with of
Any DB SAP HANA Any DB SAP HANA metadata
SAP Datasphere Extractors Extractors Extractors APIs
SAP Cloud/On-Premise & SAP Cloud/On-Premise & SAP Cloud/On-Premise &
Any Sources Any Sources Any Sources

Switch from hybrid to SAP Datasphere with SAP BW bridge

SAP BW or SAP BW/4HANA SAP Datasphere


New Reuse &
Analytics Layer Data/Business Layer
Integration Move
Capability Staging Layer Including
ABAP Extensions
Tool-supported conversion Spaces
including data SAP BW Bridge
Replace SAP BW or Any DB SAP HANA
SAP BW/4HANA with Extractors Extractors APIs
SAP Datasphere SAP Cloud/On-Premise & SAP Cloud/On-Premise &
Any Sources Any Sources

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3


SAP BW hybrid integration
SAP BW query to SAP Datasphere

Add-ons SAP Analytics Cloud SAP Analytics Cloud

SAP BW/4HANA SAP Datasphere – Core

Remote Table Based on CompositeProvider

Analytical Dataset – View


BW/4 Objects Customer Extensions

Optional creation
Query Code (ABAP) Analytic Model
CompositeProvider Data Layer
DataStore
Analytical Dataset

ABAP Business Layer

SAP HANA SAP HANA Cloud

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4


SAP BW hybrid integration
SAP BW hybrid integration

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5


SAP BW hybrid integration
Remote authorizations

▪ Significant investment and effort already spent in


existing authorization concepts in various source
systems
▪ Customers do not want to redundantly define
authorizations in SAP Datasphere; they want to
leverage their existing concepts
▪ Remote authorizations of SAP Datasphere
significantly reduce effort implementing row-level
security
▪ First shipment focuses on replication of analysis
authorizations from SAP BW/4HANA to
SAP Datasphere

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6


SAP BW hybrid integration
Remote authorizations – high-level process flow

Analysis Authorizations Remote Authorization


Persisted Share
in SAP BW/4HANA (Wizard)

Leverage existing analysis Permission table in Step-by-step assistance Protected view can be shared
authorizations in SAP BW/4HANA ▪ Use Remote ▪ Allow further consumption /
SAP BW/4HANA ▪ Relevant information for Authorization Wizard to developments by sharing the
▪ Leave SAP BW/4HANA each analysis generate data access protected view to other spaces
authorizations untouched Authorization is persisted controls (DAC)
▪ Execute transaction in permission table (users, ▪ Generated DAC are
RSDWC_DAC_RSEC_GEN authorized values, automatically assigned
InfoProviders) to the selected view of
▪ Select scope of
users/InfoProviders for the InfoProvider to be
which authorizations should protected
be transferred to the
permission table
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7
SAP BW hybrid integration
Remote authorizations – prerequisites and limitations

Prerequisites
▪ Remote authorizations are available for connected
SAP BW/4HANA 2.0 systems
▪ Systems must be connected via an SAP ABAP or
SAP BW connection to SAP Datasphere

Limitations
▪ Remote tables imported from an SAP BW/4HANA
model transfer connection cannot be protected using
the wizard for remote authorizations
▪ Only analysis authorizations applied to
characteristics used in InfoProviders (ADSO objects)
and CompositeProviders can be imported (not
authorizations defined on queries as an InfoProvider
or on navigational attributes)

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8


SAP BW hybrid integration
Remote authorizations

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9


SAP BW hybrid integration
What you have learned in this unit

▪ How to build a landscape including SAP BW and


SAP Datasphere
▪ How to use BW queries in SAP Datasphere
▪ How to use remote authorizations

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10


Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2023 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.

You might also like