You are on page 1of 52

SAP S/4HANA

SAP BW
Dec 2016
English

Integration Scenarios
Between SAP S/4HANA
and SAP BW
Building Block Configuration Guide

SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany

SAP Best Practices
Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide

1.1.1 Copyright

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

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. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional
trademark information and notices.

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 SE or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only warranties for SAP SE 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 platform 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, which speak only as of their dates, and they should
not be relied upon in making purchasing decisions.

© SAP SE Page 2 of 52

SAP Best Practices
Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide

Icons

Icon Meaning
Caution

Example

Note

Recommendation

Syntax

External Process

Typographic Conventions

Type Style Description
Example Words or characters quoted from the screen. These include field names,
screen titles, pushbuttons labels, menu names, menu paths, and menu
options.
Textual cross-references to other documents.
Example Emphasized words or expressions.
EXAMPLE Technical names of system objects. These include report names, program
names, transaction codes, table names, and key concepts of a programming
language when they are surrounded by body text, for example, SELECT and
INCLUDE.
Example Output on the screen. This includes file and directory names and their paths,
messages, names of variables and parameters, source text, and names of
installation, upgrade and database tools.
Example Exact user entry. These are words or characters that you enter in the system
exactly as they appear in the documentation.
<Example> Variable user entry. Angle brackets indicate that you replace these words and
characters with appropriate entries to make entries in the system.
EXAMPLE Keys on the keyboard, for example, F2 or ENTER .

© SAP SE Page 3 of 52

SAP Best Practices
Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide

Contents
1. Purpose.................................................................................................................................. 6
2. Prerequisites.......................................................................................................................... 6
3. Integration of SAP S/4HANA and BW when S/4HANA and BW in Different DBs...................8
3.1 SAP HANA Smart Data Access and Modeling via Open ODS Views..............................8
3.1.1 Architecture.............................................................................................................. 8
3.1.2 Usage....................................................................................................................... 9
3.1.3 Recommendations / Findings...................................................................................9
3.1.4 How to Implement.................................................................................................. 10
3.1.4.1 Establish Smart Data Access..........................................................................10
3.1.4.2 Create and Refine Open ODS Views..............................................................15
3.1.4.3 Create BEx Query........................................................................................... 24
4. Integration of SAP S/4HANA in BW when BW Embedded in SAP S/4HANA.......................26
4.1 Modeling-free via ODP Transient Provider....................................................................26
4.1.1 Architecture............................................................................................................ 26
4.1.2 Usage..................................................................................................................... 26
4.1.3 Recommendations / Findings.................................................................................27
4.1.4 How to Implement.................................................................................................. 27
4.1.4.1 Create BEx Query........................................................................................... 29
4.1.4.2 Define BEx Query Definition...........................................................................29
5. Integration of SAP S/4HANA and SAP HANA Live in BW.....................................................31
5.1 Usage............................................................................................................................ 31
5.1.1 Recommendations / Findings.................................................................................31
5.2 SAP BW and SAP S/4HANA and SAP HANA Live Deployed Across Different SAP
HANA Instances....................................................................................................................... 33
5.2.1 Architecture............................................................................................................ 33
5.2.2 How to Implement.................................................................................................. 33
5.2.2.1 Establish Smart Data Access..........................................................................33
5.2.2.2 Create Open ODS Views Based on SAP HANA Live......................................33
5.2.2.3 Create Open ODS Views Based on SAP S/4HANA........................................34
5.2.2.4 Consume Open ODS Views in a Composite Provider.....................................34
5.2.2.5 Create BEx Query........................................................................................... 38
5.3 SAP HANA Live and SAP BW in the Same SAP HANA DB..........................................39
5.3.1 Architecture............................................................................................................ 39
5.3.2 How to Implement.................................................................................................. 39
5.3.2.1 Establish Smart Data Access..........................................................................39
5.3.2.2 Create Open ODS Views Based on SAP HANA Live......................................39
5.3.2.3 Create Open ODS Views Based on SAP S/4HANA........................................40
5.3.2.4 Consume SAP HANA Live Views and Open ODS Views in Composite Provider
40

© SAP SE Page 4 of 52

SAP Best Practices
Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide
5.4 SAP S/4HANA and SAP BW in the Same HDB with Separate Standalone BW............41
5.4.1 Architecture............................................................................................................ 41
5.4.2 How to Implement.................................................................................................. 41
5.4.2.1 Establish Smart Data Access..........................................................................41
5.4.2.2 Create Open ODS Views Based on SAP HANA Live......................................41
5.4.2.3 Create Open ODS Views Based on SAP S/4HANA........................................42
5.4.2.4 Consume Open ODS Views in a Composite Provider.....................................42
6. Sample Content.................................................................................................................... 43
6.1 Integration of SAP S/4HANA in BW when SAP S/4HANA and BW in Different DBs.....43
6.1.1 Prerequisite Software Component.........................................................................43
6.1.2 Prerequisite Notes.................................................................................................. 44
6.1.3 In BW’s Underlying SAP HANA, Establish Smart Data Access to SAP S/4HANA..44
6.1.3.1 Add BW’s Underlying SAP HANA Database in SAP HANA Studio..................44
6.1.3.2 Create Remote Source...................................................................................46
6.1.4 Create Logical System in BW.................................................................................46
6.1.5 In BW, Create DB Connect Source System Based on Smart Data Access to SAP
S/4HANA.............................................................................................................................. 47
6.1.6 Check Namespaces /PIM/ Prior to Activating Business Content............................48
6.1.7 Activate BW Content..............................................................................................50
6.1.7.1 Prerequisite: Check BW Activation User’s Role with BW Authorization Objects
Assigned 50
6.1.7.2 Assigning Source System for Activation..........................................................50
6.1.7.3 Activating Info Provider...................................................................................50
6.1.7.4 Activating BW Query.......................................................................................51

© SAP SE Page 5 of 52

You need the following authorization in SAP HANA:  System privilege: CREATE REMOTE SOURCE Software prerequisites:  Transient Provider based on SAP HANA ODP: BW/NW 7. For this guide there are two main situations for the integration of BW and SAP S/4HANA:  SAP BW and SAP S/4HANA in two different DBs  SAP BW embedded in SAP S/4HANA Please be reminded that in this document. all the system/model information are just used as sample here. you need to use your own server/model information in your environment.40 SP5 © SAP SE Page 6 of 52 . there is a possibility for consuming data from SAP S/4HANA in Business Warehouse. 3. This guide is based on the need of implementing scenarios for the interoperability between SAP BW Models and SAP HANA Models where data owned and modeled within BW and data owned and modeled within native SAP HANA tools interact. Prerequisites The following add-in must be installed in SAP HANA Studio:  Required features  Mylyn Commons SDK  Mylyn Task-Focused Interface  EMF Model Query SDK  Web Services Tools  ABAP Development Tools  BW Modeling Tools For specifics and prerequisites visit SAP Note 1954169 – BWMT – Installation details. Purpose If you have Business Warehouse already running and also want to have the benefits of SAP S/4HANA.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide Integration Scenarios Between SAP S/4HANA and SAP BW 2.30  Composite Provider: available with BW/NW 7.

40 SP5.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide  Open ODS View: available with BW/NW 7. Materialization option available with SP8 © SAP SE Page 7 of 52 .

© SAP SE Page 8 of 52 .SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 4.1 SAP HANA Smart Data Access and Modeling via Open ODS Views Use cases:  Transactional and master data from SAP S/4HANA Analytics Virtual Data Model consumed by BW Open ODS view  This scenario is valid for BW and SAP S/4HANA deployed across different SAP HANA instances (prerequisite: SAP HANA SDA configured) 4.1.1 Architecture The pictures below shows the architecture for this scenario. Integration of SAP S/4HANA and BW when S/4HANA and BW in Different DBs 4.

historical data / plan data) by utilizing SAP HANA Composite Provider Open ODS Views can be materialized in BW if required.g. DataStore object (Advanced) and BW Transformation (requires SAP BW 7. Generation of data flow with DataSource.g. e. for snapshot scenarios 4.3 Recommendations / Findings  Recommended to implement Open ODS Views based on SAP S/4HANA ABAP CDS interface / reuse views  Distinguish between transactional and master data (attribute and text) views and create associations accordingly  Start with the Open ODS Views for master data (attribute and text).g. hierarchy node variables o Exceptions and conditions o Currency conversion during report execution o Report-to-Report Interface.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 4.2 Usage Integrating BW and SAP S/4HANA Analytics across different SAP HANA instances with Open ODS Views and SAP HANA Smart Data Access. then proceed with transactional Open ODS Views  SAP Client needs to be added to the key of all Open ODS Views and needs to be uniquely filtered  Use BEx Query on top of Open ODS Views / Composite Provider to take advantage of full set of reporting features: o Restricted & calculated key figures o BEx variables e. Consumption of SAP S/4HANA Analytics transactional and master data views by SAP BW. …  Open ODS View provides functionality to switch from virtual access to persistence.1.40 SP 8 or higher) © SAP SE Page 9 of 52 .1.  Real-time (transactional and master) access to SAP S/4HANA OLTP data with the help of Open ODS views consuming SAP S/4HANA Analytics CDS views  Flexible. hierarchies)  Takes full advantage of BEx reporting capabilities  Security handled by BW authorization  Optional: Transactional data from SAP S/4HANA Analytics can be enhanced with data stored in BW DataStore object (e. agile modeling through Open ODS Views  Capability to enrich data from SAP S/4HANA Analytics views with BW managed master data (e.g.

In BW.4.1 Add SAP HANA System in SAP HANA Studio This is a basic step before creating BW Project in SAP HANA Studio.1. For more information.1. This enables bringing content from different EDW landscapes together without any replication.SAP HANA Smart Data Access or help.com . the object privilege CREATE VIRTUAL TABLE is required  It is recommended to create the remote source with the HANA SAP<SID> user. If the remote source has not been created by the HANA SAP<SID> user. the system privilege CREATE REMOTE SOURCE is required  For creating virtual tables.1. then the HANA SAP- <SID> user needs the object privilege CREATE VIRTUAL TABLE.com - HANA SDA in BW 4.1 Establish Smart Data Access Requirements:  For creating remote sources. we discuss how to implement this scenario. granted by the owner of the remote source 4.1. 1) Open SAP HANA Studio and go to SAP HANA Modeler perspective (Window -> Perspective -> Open Perspective -> Other) 2) Right-click the left margin and choose “Add System…” © SAP SE Page 10 of 52 . The following steps describe how to integrate BW and SAP S/4HANA Analytics across different SAP HANA instances with Open ODS Views and SAP HANA Smart Data Access.4.sap. visit: help.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 4.sap.4 How to Implement In this section. SAP HANA Smart Data Access is used as a data source for Open ODS Views.

SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 3) Then enter your system information 4) Click Next > and enter your user information. click Finish © SAP SE Page 11 of 52 .

right click and select New Virtual Table.1. 3) Enter a Source Name and choose the Adapter Name. © SAP SE Page 12 of 52 . also enter the User Name and the Password 4) Click the Save Editor icon in the upper right-hand corner of the screen. Port. Here we select HANA (ODBC). enter values for Server.2 Create Remote Source 1) Open SAP HANA Modeler Perspective in SAP HANA studio 2) Open Provisioning -> Remote Sources.4.4. Database Name.1.. right click Remote Sources and select New Remote Source…. The remote source has been created successfully For details on how to connect the databases for SAP HANA Smart Data Access as remote sources see the SAP HANA Administration Guide -> System Administration and Maintenance Information -> SAP HANA Administration Guide (About SAP HANA Smart Data Access -> Adding Remote Data Sources) 4.1..3 Create Virtual Tables from Remote Objects 1) In the Systems view Catalog <Schema_Name> Tables.1.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 4.

database. This creates a virtual table. © SAP SE Page 13 of 52 . select the remote source.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 1) Enter a Table Name and click Browse… 2) A dialog box appears. 3) Click the Save this Editor icon in the upper right hand corner of the screen. and table The source name and the remote object are filled in automatically by the names of the components chosen in the previous step. The new virtual table will appear in the tree view Catalog <schema> Tables.

SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide You can continue the research via creating Open ODS View based on this virtual table just like other local tables. © SAP SE Page 14 of 52 .

4.4.2 Create and Refine Open ODS Views 4.2.1.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 4.1 Establish BW Project in SAP HANA Studio 1) Open BW Modeling perspective in SAP HANA studio 2) Right-click on the project explorer and choose New -> Project or click on the icon above. and then select BW Project 3) Attach the corresponding SAP HANA system to the BW project manually or by selecting a connection from SAP Logon © SAP SE Page 15 of 52 .1.

The next steps describe how to create Open ODS Views in SAP HANA Studio.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide Make sure that the SAP HANA database has been added as a system to the SAP HANA systems view of the SAP HANA administration console and make sure that a database user has been assigned to the SAP HANA system.4.2 Create Open ODS View for Master Data For creating Open ODS Views.1. 1) Open SAP HANA Studio and go to the BW Modeling perspective (Window -> Open perspective -> Other) a) Select the InfoArea of interest in your BW Project b) Click right and select New ->Open ODS View © SAP SE Page 16 of 52 .2. you have to use a modelling tool. 4.

SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 2) Specify an appropriate technical name and description: a) Define Semantics as “Master Data” b) Choose Source Type “Virtual table using SAP HANA Smart Data Access” 3) Define Remote Source (SAP S/4HANA system). DB Object Schema and Source System (Select DB Object Schema where the CDS Views are located) 4) Select the SAP S/4HANA Open CDS View representing the master data (example: I_CUSTOMER_CDS) as DB Object Name in the appearing pop-up window after clicking Browse… © SAP SE Page 17 of 52 .

SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide © SAP SE Page 18 of 52 .

They can be moved to target folders by drag and drop.3 Define Key Fields for Master Data Open ODS View 1) Define key fields a) Representative Key Field b) Characteristics (Key): Additional compounded keys (like MANDT) As default all output fields of the SAP S/4HANA Open CDS View are assigned as Characteristics for the Open ODS View.2. © SAP SE Page 19 of 52 .1.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 4.4.

SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 4.4. by:  Defining Text Fields as part of the view fields  Changing the technical names for the view fields  Adding field associations for view fields if applicable.4 Refine and Activate Open ODS View for Master Data 1) You can now further refine your Open ODS View e.1. with other Open ODS Views or BW InfoObjects  Setting the view field as authorization relevant  Changing the reporting properties such as key / text display 2) Now you can activate the Open ODS View Define Open ODS Views for all Master Data views that you want to associate to your transactional Open ODS View.5 Create Open ODS View for Transactional Data Create an Open ODS View of type “Facts” for the transactional SAP S/4HANA Open CDS View similar to the previous steps. 1) Open SAP HANA Studio and go to the BW Modeling perspective (Window -> Open perspective -> Other) a) Select the InfoArea of interest in your BW Project b) Click right and select New -> Open ODS View © SAP SE Page 20 of 52 . e. 4.4.g.1.g.2.2.

DB Object Schema and Source System 4) Select the SAP S/4HANA Open CDS View representing the facts (example: ISALESDOC) as DB Object Name Characteristics and Key Figures will be automatically assigned to the appropriate structure folders based on the output field definition of the SAP S/4HANA Open CDS View. © SAP SE Page 21 of 52 .SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 2) Specify an appropriate technical name and description: a) Define Semantics as “Facts” b) Choose Source Type “Virtual table using SAP HANA Smart Data Access” 3) Define Remote Source (SAP S/4HANA system).

to the previous created master data Open ODS Views) © SAP SE Page 22 of 52 .SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 4.4.g.2.6 Maintain View Fields and Field Associations for Open ODS View 1) Define key fields 2) Define the currency and unit fields The currency and unit need to be defined in the Open ODS View if you want to see it come together in the BEx query 3) Maintain field associations (e.1.

in SAP BusinessObjects Analysis. Remember to restrict your data by MANDT in all BEx Queries. edition for Microsoft Office. combining the information with BW InfoProvider) or implement BEx Queries directly and consume them e. click Browse and search for the Open ODS View of interest b) Combind the InfoObject to the corresponding view c) Select Field Name and click ok 4.g.7 Activate Open ODS View Now you can activate the Open ODS View and you can either reuse it in a CompositeProvider (e. © SAP SE Page 23 of 52 .g.2.1.4.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide a) Choose Assocaiton With.

4.3 Create BEx Query 1) Open BExQuery Designer and create a new Query 2) Choose you preferred InfoArea and Open ODS View 3) Define the BEx Query using e. cell definition  Conditions and exceptions 4) Fix restriction in “Characteristic Restrictions” © SAP SE Page 24 of 52 . rows.1. variables  Free characteristics.:  Filer.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 4. formulas. columns  Restricted & calculated key figures.g. structures.

SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 5) Save BEx Query and execute © SAP SE Page 25 of 52 .

1 Modeling-free via ODP Transient Provider Use cases:  To simply display and use SAP S/4HANA Analytics consumption / query views without any further investments  Mainly to leverage BEx capabilities and valid for embedded BW setup 5.  Supports BEx variables  Supports restricted key figures  Supports exceptions and conditions  Supports currency conversion  Supports BW Report-to-Report interface  Supports SAP S/4HANA Analytics privileges BW Hierarchies. 5.1.1. Integration of SAP S/4HANA in BW when BW Embedded in SAP S/4HANA 5.2 Usage Transactional data provisioning via SAP S/4HANA Analytics Open CDS View in BEx Query. Consumption of SAP S/4HANA Analytics Open CDS views in BW via ODP transient provider. node variables and BW analysis authorizations are not supported Query not based on BW InfoObjects).SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 5. © SAP SE Page 26 of 52 .1 Architecture The picture below shows the architecture for this scenario.

we discuss how to implement this scenario.g.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 5.3 Recommendations / Findings  All SAP S/4HANA CDS views are automatically exposed as a ODP transient InfoProvider and can be used in the BEx Query Designer to define custom queries  Quick way to add BW functionality without using BW modeling objects  It is recommended to implement BEx queries based on SAP S/4HANA Analytics CDS consumption / query views  Input parameters / variables defined in SAP S/4HANA Analytics CDS view must be defined in the Bex Query as static filter e.4 How to Implement In the section below.1.1. It’s derived from the ODP metadata definition automatically and dynamically. as the transient provider is generated with same technical name in all systems 5. by a fix value or mandatory variable  BW analysis authorizations & BW hierarchies are not supported  BEx Queries created on ODP Transient Provider can be transported through the SAP S/4HANA landscape. There is no additional modeling necessary. Background Information The ODP Transient Provider is a specific InfoProvider type for Operational Analytics. For a preview of the Transient Provider: 1) Call transaction RSRTS_ODP_DIS 2) Select ABAP Core Data Services as ODP Context and select I_CUSTOMER_CDS as ODP Name by browsing 3) Execute 4) A preview of the Transient Provider for the selected Operational Data Provider is displayed in a tree structure © SAP SE Page 27 of 52 .

SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide © SAP SE Page 28 of 52 .

1. structures.1 Create BEx Query Open Business Explorer Query Designer and select a View from an Info Area or search for a specific View: Please note that all SAP S/4HANA CDS views are automatically exposed as ODP transient InfoProvider! In BEx Query Designer they are reachable under: “2C” + <SQL-Name>.2 Define BEx Query Definition 1) Define the BEx Query using e. variables  Free characteristics.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 5.4.g. formulas. rows. You can find examples in the following table: Open ODS View CDS Views (SQL CDS Views in Name) BExQuery ZS4CUSTOMER (Customer Master Data) I_CUSTOMER_CDS 2CI_CUSTOMER_C DS ZS4_SO_HDR (Sales Document Header) ISDSALESDOC 2CISDSALESDOC ZS4CURRENCY (Currency) IFICURRENCYTEX 2CIFICURRENCYTE T XT 5. columns  Restricted & calculated key figures.:  Filer. cell definition  Conditions and exceptions © SAP SE Page 29 of 52 .4.1.

SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 2) Fix restriction in “Characteristic Restrictions” 3) Save BEx Query and execute © SAP SE Page 30 of 52 .

g. Otherwise you will have to model the Open ODS Views based on SAP HANA Live and SAP S/4HANA first. model and refine these Open ODS Views based on SAP HANA Live and SAP S/4HANA and how to consume them in a CompositeProivder. Integration of SAP S/4HANA and SAP HANA Live in BW Use cases:  To use SAP S/4HANA and SAP HANA Live combined  Can be used when SAP S/4HANA and SAP HANA Live are in different SAP HANA DBs than BW  Can be used in mixed case (BW located in same SAP S/4HANA or SAP HANA Live DB)  It also can be used when you have all systems based on the same HDB 6.g.  Real-time (transactional and master) access to SAP S/4HANA OLTP data with the help of Open ODS views consuming SAP S/4HANA Analytics CDS views  Flexible. hierarchies)  Takes full advantage of BEx reporting capabilities  Security handled by BW authorization  Optional: Transactional data from SAP S/4HANA Analytics and SAP HANA Live can be enhanced with data stored in BW DataStore object (e.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 6.g. you can reuse your modeled Open ODS Views in a CompositeProvider later. historical data / plan data) by utilizing SAP HANA Composite Provider If you already use SAP HANA Live and did the configuration for the integration with BW by modeling Open ODS Views. agile modeling through Open ODS Views  Capability to enrich data from SAP S/4HANA Analytics views with BW managed master data (e. 6. This chapter describes. how to create. then proceed with transactional Open ODS Views  SAP Client needs to be added to the key of all Open ODS Views and needs to be uniquely filtered  Use BEx Query on top of Open ODS Views / Composite Provider to take advantage of full set of reporting features: o Restricted & calculated key figures o BEx variables e. hierarchy node variables © SAP SE Page 31 of 52 .1 Usage Consumption of SAP S/4HANA and SAP HANA Live transactional and master data views by Open ODS Views in BW in a Composite Provider.1 Recommendations / Findings  Recommended to implement Open ODS Views based on SAP S/4HANA ABAP CDS interface / reuse views  Distinguish between transactional and master data (attribute and text) views and create associations accordingly  Start with the Open ODS Views for master data (attribute and text).1.

Generation of data flow with DataSource. …  Open ODS View provides functionality to switch from virtual access to persistence.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide o Exceptions and conditions o Currency conversion during report execution o Report-to-Report Interface. DataStore object (Advanced) and BW Transformation (requires SAP BW 7.40 SP 8 or higher) © SAP SE Page 32 of 52 .

2. 6. At step 3 where you define the data source for Open ODS View. For guided configuration.2 (Create and Refine Open ODS Views).1.1. The following steps will guide you through creating Open ODS Views for SAP HANA Live and SAP S/4HANA models and how to consume them in a Composite Provider. 6. just select the Remote Source for your SAP HANA Live system and a SAP HANA Live View as DB Object Name. you will have to configure SAP HANA Smart Data Access first.1 Architecture The picture below shows the architecture for this scenario.2 Create Open ODS Views Based on SAP HANA Live The steps for establishing a SAP BW project and creating Open ODS Views based on SAP HANA Live views are similar to the SAP S/4HANA integration with BW across different SAP HANA instances.2.2.2.4.4.2.2 SAP BW and SAP S/4HANA and SAP HANA Live Deployed Across Different SAP HANA Instances 6. 6. please refer to chapter 4. © SAP SE Page 33 of 52 .2. The procedure is described in chapter 4. Then define the Open ODS Views similar to the described SAP S/4HANA modeling.1 (Establish Smart Data Access).2 How to Implement For this scenario we use Smart Data Access to establish connection to SAP S/4HANA and SAP HANA Live system.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 6.1 Establish Smart Data Access In case you have SAP HANA Live and SAP S/4HANA running on another SAP HANA instance than SAP BW.

1.2 (Create and Refine Open ODS Views). For consumption of these Open ODS views follow the steps which are described in this chapter. choose “New” -> “CompositeProvider” 2) Define Composite Provider and define the operation type you want to execute (Here we choose Union) © SAP SE Page 34 of 52 .4 Consume Open ODS Views in a Composite Provider 1) In the context menu of your BW project.2. 6. fulfill the procedure described in chapter 4.3 Create Open ODS Views Based on SAP S/4HANA To create Open ODS views based on SAP S/4HANA views.2.4.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 6.2.2.

4) Scenario tab Setting © SAP SE Page 35 of 52 . Setting External View to ‘X’ leads to the generation of a SAP HANA view which can be consumed through SQL. Scenario and Output). 3) General tab Setting On the general tab we have to specify whether we want to have an external view and some runtime properties such as semantic properties and NLS or Cache usage.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide In the next step you see that the screen is divided into 3 tabs (Overview.

c) Define the output structure of the CompositeProvider by dragging and dropping objects in the graphical editor section from the left to the right © SAP SE Page 36 of 52 . You specify which fields from these PartProviders should be used as output columns of the CompositeProvider. Enter the name of the Open ODS View you want to search for.. we can add Open ODS Views.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide On the Scenario tab page. BW InfoProviders or SAP HANA Views. a) Right-Click on Union and choose Add. b) In the ‘Add Provider’ window. Choose OK when you’ve found the matching item. you can select the participating InfoProviders or SAP HANA models.

real-time key figure from Open ODS Views based on SAP S/4HANA or SAP HANA Live. for characteristics. As an additional scenario. you can drag objects from both sources onto the same destination to do a union. 2) Output tab Setting In the Output tab you can specify for each individual field in the output structure associations to other objects such as InfoObjects. For example. to do an integrated analysis.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide Drag from both Open ODS Views based on SAP S/4HANA and Open ODS Views based on SAP HANA Live Views to create a union. a) Define associations to existing InfoObjects or OpenODSViews b) Choose ‘Association with’ and Select an object with which we you to associate the field in the next screen c) By associating an InfoObject of type keyfigure the field of the CompositeProvider inherits for example the aggregation behavior of the associated object as well as currency or quantity related settings © SAP SE Page 37 of 52 . You can drag historical key figure from BW InfoProvider. you can also add a BW InfoProvider to the CompositeProvider you created in the previous steps. OpenODSViews or you can assign constants.

SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 3) Activate CompositeProvider After activating you are now ready to query the CompositeProvider 6. please refer to chapter 4.4.5 Create BEx Query Create BW query on top of the CompositeProvider you created in previous steps. 1) Open BExQuery Designer and create a new Query based on the CompositeProvider 2) Fix restriction in “Characteristic Restrictions”.2.3 (Create BEx Query). There needs to be a fix restriction in the “Characteristic Restrictions” in the BEx Query (either per fix filter or more dynamically by using BEx Variables) 3) Drag out the required fields for analysis 4) Execute the query to check the result For more details on how to create a Query in BExQuery Designer. © SAP SE Page 38 of 52 .1.2.

The following steps will guide you through creating Open ODS Views for SAP S/4HANA and SAP HANA Live models using Smart Data Access and local tables and how to consume them in a Composite Provider.3. 6.3.2 Create Open ODS Views Based on SAP HANA Live SAP HANA Live models can be consumed in a Composite Provider directly or modeled as Open ODS Views.2.4.1 Architecture The picture below shows the architecture for this scenario where SAP HANA Live can be combined with SAP S/4HANA and be consumed by BW in a Composite Provider.2 (Create and Refine Open ODS Views). in the fields for source definition. 6.1 Establish Smart Data Access In case you have SAP S/4HANA running on another SAP HANA instance than BW. you will have to configure SAP HANA Smart Data Access first.3.3 SAP HANA Live and SAP BW in the Same SAP HANA DB 6. please refer to chapter 4. 6.3. In case of modeling. When the Open ODS View wizard for creation pops up. please insert your SAP HANA Live Remote Source and SAP HANA Live DB Object Name. please refer to chapter 4.2 How to Implement For this scenario we use Smart Data Access to establish connection to SAP S/4HANA system.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 6.1. © SAP SE Page 39 of 52 . For guided configuration.1 (Establish Smart Data Access). When BW an SAP HANA Live are located in the same SAP HANA database you can directly use SAP HANA Live views or use the local tables for modeling Open ODS Views based on SAP HANA Live and establish connection to SAP S/4HANA system via Smart Data Access.4.1.2.

proceed how it is described in chapter 4.2 (Create and Refine Open ODS Views).1.2.2. When the CompositeProvider is created you can add your SAP HANA Live Views directly to the CompositeProvider by setting the “External SAP HANA View” field on true. Please refer to chapter 6. 6. For consumption of Open ODS views follow the steps which are described in the next step.4 Consume SAP HANA Live Views and Open ODS Views in Composite Provider The steps for creating a CompositeProvider are similar to the other integration scenarios for SAP S/4HANA and SAP HANA Live in BW.3. In this use case.4.3.2.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 6. © SAP SE Page 40 of 52 .3 Create Open ODS Views Based on SAP S/4HANA To create Open ODS views based on SAP S/4HANA views.2. SAP BW and SAP HANA Live are located in the same SAP HANA DB.4 (Consume Open ODS Views in a Composite Provider).

6. For guided configuration. Then define the Open ODS Views similar to the described SAP S/4HANA modeling.4. please refer to chapter 4.2 Create Open ODS Views Based on SAP HANA Live The steps for establishing a BW project and creating Open ODS Views based on SAP HANA Live views are similar to the SAP S/4HANA integration with BW across different SAP HANA instances. The following steps will guide you through creating Open ODS Views for SAP S/4HANA and SAP HANA Live models using Smart Data Access and local tables and how to consume them in a Composite Provider.4.4.1 Architecture The picture below shows the architecture for this scenario.4. © SAP SE Page 41 of 52 .4.1.1 (Establish Smart Data Access). you will have to configure SAP HANA Smart Data Access first.1. The procedure is described in chapter 4.4 SAP S/4HANA and SAP BW in the Same HDB with Separate Standalone BW 6.2 How to Implement For this scenario we use Smart Data Access to establish connection to SAP HANA Live system.1 Establish Smart Data Access In case you have SAP HANA Live running on another SAP HANA instance than BW.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 6.4.2. 6. 6.2 (Create and Refine Open ODS Views). At step 3 where you define the data source for Open ODS View.2. just select the Remote Source for your SAP HANA Live system and a SAP HANA Live View as DB Object Name like in the picture below.

3 Create Open ODS Views Based on SAP S/4HANA Before SAP S/4HANA Models can be consumed in a Composite Provider they have to be modeled in Open ODS Views.4. 6. Please refer to chapter 6. Select different Source Type (-> Database Table or View) in step 3.2 (Create and Refine Open ODS Views).SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 6.4 (Consume Open ODS Views in a Composite Provider).4 Consume Open ODS Views in a Composite Provider The steps for creating a CompositeProvider are similar to the other integration scenarios for SAP S/4HANA and SAP HANA Live in BW.4.2.2.4.2. How to create Open ODS Views as it is described in chapter 4.1.2. © SAP SE Page 42 of 52 .

sap. click Installation. Sample Content 7.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 7. CBW is BWoH 740 system (100 is BI client of BW).1 Integration of SAP S/4HANA in BW when SAP S/4HANA and BW in Different DBs Use The following is a sample for the Integration of SAP S/4HANA in BW when SAP S/4HANA and BW in different DBs. Currently. select the checkbox. Download it with SAP Download Manager. Please download the BP-BW 740 latest Vx version.com/swdc  Click "Software Downloads"  "SAP Software Download Center"  "Installations and Upgrades"  "Software Downloads"  Search BP-BW 740 and choose the latest BP-BW 740Vx (eg: "BP-BW 740V3" ).1. the previous released CDS view (released earlier than SAP © SAP SE Page 43 of 52 . In future version’s SAP S/4HANA 1611+ based on higher versions’ NetWeaver (7.50. there are following limitations in case of leveraging this solution architecture for BW and SAP S/4HANA integration (BW on HANA via smart data access connection to remote SAP S/4HANA’s CDS SQL view in SAP HANA Database):  CDS with parameters are not supported in this solution architecture.52+). go to http://service. activate predefined BI Content based on Source system (QE40000000) 7. It is necessary to configure the following steps for integration:  In CBW/100‘s underlying SAP HANA database. create smart data access connection (eg: S4H_QE4) to QE4’s underlying SAP HANA database (eg: hostname is qe4hanahostxxx). then choose Add to Download Basket. QE4 is a SAP S/4HANA system. To install BP-BW 740V2 or above SP. SAP NETWEAVER 7.4 SP13+ and BI_CONT 757 SP08+ are required. Please follow following configurations to install predefined content. Open ODS View will only show the SQLViews of CDS Views without parameters. perform the following steps:  In your Web browser.  In CBW/100.  The content in this sample is tested via SAP S/4HANA 1511 on premise version with Netweaver 7.1 Prerequisite Software Component To install predefined BW content for the integration with SAP S/4HANA. it is necessary to install BP-BW 740V2 or above SP. create DB connect Source system (eg: QE40000000) based on smart data access connection (S4H_QE4)  In CBW/100. since the latest version always includes the fixes to previous issues. For example. Please refer details in SAP Note 2198480 (point 12).  In the Download area. create logical system QE40000000  In CBW/100. To download BP-BW 740V2 or above Vx BW addon component (RDS BW BI CONT Addon) deployed in this solution.

granted by the owner of the remote source 7. cbwhostname) Instance Number The instance number of BWoH’s HANA database (i. Establish Smart Data Access to SAP S/4HANA Requirements:  For creating remote sources. 7. then the HANA SAP- <SID> user needs the object privilege CREATE VIRTUAL TABLE.e: 00) User Name The user name of BWoH’s HANA database Password The password of BWoH’s HANA database 4) Click Finish. due to the new possibility for the client handling in CDS views. please check whether it is mandatory to set CDS client to fetch data from SQL view of CDS by executing the following SQL in SAP HANA Studio of SAP S/4HANA’s HANA database.3.3 In BW’s Underlying SAP HANA.1. SELECT TOP 1000 * FROM "SAPQE6". BWoH’s HANA database (eg: CBW) has been added in SAP HANA Studio © SAP SE Page 44 of 52 .1Add BW’s Underlying SAP HANA Database in SAP HANA Studio 1) Open SAP HANA Studio and go to SAP HANA Modeler perspective (Window -> Perspective -> Open Perspective -> Other) 2) Right-click the left margin and choose “Add System…” 3) Then enter your system information: Host Name The hostname of BWoH’s HANA database (i.. the object privilege CREATE VIRTUAL TABLE is required  It is recommended to create the remote source with the HANA SAP<SID> user.1. then the CDS view is supported on SAP S/4HANA 1611+. the system privilege CREATE REMOTE SOURCE is required  For creating virtual tables. For example. SAP S/4HANA system ID is QE6: set 'CDS_CLIENT' = '910'. If the remote source has not been created by the HANA SAP<SID> user. As a result. or else it is not supported. If it is still able to return data without setting 'CDS_CLIENT'.1.2 Prerequisite Notes Please check and install the following notes accordingly: 2190154 BW & HANA Smart Data Access: F4-Help does not work after HANA Upgrade to SP9 or SP10 2259897 Field Compoundings in a CompositeProvider are lost after save 2236260 BW CompositeProvider does not support RAW(16) data type 7.e. To validate whether CDS view is still supported on SAP S/4HANA 1611+ under this solution architecture.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide S/4HANA 1611) is not supported in this solution architecture."ISDSLSORDERITEM".

SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide © SAP SE Page 45 of 52 .

The remote source (eg: S4H_QE4) has been created successfully 5) In SAP HANA Studio for BWoH’s HANA instance (eg: CBW). qe4hanahostxxx) Port The port number of SAP S/4HANA’s HANA database (i. run the following GRANT CREATE VIRTUAL TABLE.3.1. also enter the User Name and the Password. DROP ON REMOTE SOURCE "S4H_QE4" TO "SAPCBW". 7.4 Create Logical System in BW It is necessary to create a logical system (eg: QE40000000) in BW (eg: CBW/100) for the DB connection source system creation based on the smart data access to SAP S/4HANA. Port. enter values for Server.. right click Remote Sources and select New Remote Source….e: 30215) User Name The user name of SAP S/4HANA’s HANA database Password The password of SAP S/4HANA’s HANA database 4) Click the Save Editor icon in the upper right-hand corner of the screen.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 7. 3) Enter a Source Name and choose the Adapter Name. Source name The name for smart data access connection (eg: S4H_QE4) Server Name The hostname of SAP S/4HANA’s HANA database (i.1.e. Database Name.2 Create Remote Source 1) Open SAP HANA Modeler Perspective in SAP HANA studio 2) For BWoH’s HANA instance (eg: CBW). Here we select HANA (ODBC). open Provisioning -> Remote Sources. 1) Access the transaction using: Transaction code SPRO © SAP SE Page 46 of 52 .

choose one of the following navigation options in the SAP BW system: Transaction Code RSA1 SAP BW Menu Modeling  Data Warehousing Workbench: Modeling 1) Choose Modeling. it is necessary to maintain this entry in table RS3DREL as following: Run T-code SM30. 2) Choose Source Systems. and click New Entries button. input Table/View as RS3DREL. 7. if necessary. System Name <Logical system>. 4) In the Name column. 3) In the Log System column. 4) Choose the Context menu (right-click). 7) Select an existing request or create a new request.0 in the Source system Type list.1. enter a name for the logical system that you want to create. for example QE40000000 Remote Source SAPQE4 5) Save your entries and a transport request for Workbench appears.5 In BW. if necessary.0 (You can also use other naming reserved for SAP HANA DB based on customization) If you are not able to find HDB 1. enter a description of the logical system. 6) Make the following entries and click continue: Field Entry Logical System Name The logical system created for DB connect to SAP S/4HANA via smart data access. eg: QE40000000 Source system Name Eg: Remote Source SAPQE4 Source System Type and Release Eg: HDB 1.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide IMG menu SAP NetWeaver  Application Server  IDoc Interface / Application Link Enabling (ALE)  Basic Settings  Logical systems  Define Logical System 2) Choose New entries.0 Long Description Eg: Sap HANA DB Content Exists Selected © SAP SE Page 47 of 52 . set the display to change. A transport request for Customizing appears. Release Eg: 1. 6) Select an existing request or create a new request. Create DB Connect Source System Based on Smart Data Access to SAP S/4HANA To carry out the activity. 5) Choose Create. 3) Select the entry DB connect in the window on the right. Input following in New Entries: Details of Added Entries screen: Field Entry Source Type Eg: HDB Source Sys. Log.

select the Modifiable value from the dropdown to change the value. 7) In DB Connect Parameters dialog. eg <NULL> DB Owner Schema SAP<SID>. Eg: SAPQE4 8) As a result. 5) If the namespace /PIM/ does not display Modifiable. The Global Setting must be set to Modifiable to allow the Namespace/Name Range area to be modified. Contact your system administrator to resolve this authorization issue. verify that the following entry is present: Namespace Gen NS BW appl. 2) On the Transport Organizer Tools screen. System type Activ Long Description e /PIM/ /B756/ BW PAR X Namespace for SAP © SAP SE Page 48 of 52 . otherwise you cannot change the namespace Modifiable column value for /PIM/. Locate the namespace /PIM/ and verify that it is set to Modifiable. 7) In the BW Partner Namespaces section.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide Field Entry SourceSys Type DB Connect Click Save Button to save above new entry. you do not have the authorization to view it or make changes in the activities included in this folder. 6) Go to transaction BW Namespace Maintenance (transaction code RSNSPACE). Source system has been created (eg: QE40000000) 7. If the Administration folder is not displayed. SID is for the SAP S/4HANA.1. choose Transport Organizer Tools  Administration  Display/Change Namespace. in the Modifiable column.6 Check Namespaces /PIM/ Prior to Activating Business Content Procedure 1) Go to transaction for Transport Organizer Tools (transaction code SE03). make the following entries and click Apply button: Field Entry Connection Type HANA Smart Access Remote Source Eg: S4H_QE4 Remote DB The Remote DB name. 3) Ensure that the following entries are present and the repair license available: Namespace Namespace Short Text Namespace owner /B756/ BWGEN generation namespace for /PIM/ SAP SAP standard /PIM/ SAP BP-BW740Vx SAP 4) Go to transaction Transport Organizer Tools (transaction code SE03) and choose Transport Organizer Tools  Administration  Set System Change options.

create by choosing the Create Partner NS pushbutton and adding the previously listed entries. © SAP SE Page 49 of 52 .SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide packaged objects: /PIM/ BW content 8) If the entry is not present.

1.7 Activate BW Content 7. 2) In the Select source systems dialog box.7.3Activating Info Provider 1) To activate Business Content:.1. 7. proceed as follows:  At the top of the right-hand frame. choose Collection mode and select Collect Automatically. choose one of the following navigation options: SAP BI Menu Information Systems  Business Information Warehouse  Modeling  Data Warehousing Workbench: Business Content Transaction Code RSORBCT 2) On the Data Warehousing Workbench: Business Content screen. it is necessary to check and ensure BW user’s role has the following authorization objects: BW Authorization objects Description S_RS_HCPR (SAP HANA Authorizations for working with CompositeProvider authorizations) CompositeProviders and their subobjects S_RS_ODSV (Open ODS view) Authorizations for working with Open ODS Views Please go to http://help. and search and find the details in chapter Authorizations for Modeling with BW Modeling Tools.1.  In the middle frame. make sure that the checkbox in the Selected column is selected only in the row containing the source systems you need to load data from. choose Grouping and select In Data Flow Before.com/nw74 .7.  In the left frame. choose Edit  Source System Assignment from the context menu.  At the top of the right-hand frame. Select the following objects: © SAP SE Page 50 of 52 . 3) In the <System ID>/<Client> Data Warehousing Workbench: BI Content dialog box: a. choose one of the following navigation options: SAP BI Role Menu Modeling  Data Warehousing Workbench: Business Content Transaction Code RSORBCT Then carry out the following steps: 1) In the Data Warehousing Workbench: BI Content view. it means that you need to select the DB connection source system for the smart data access to SAP S/4HANA. For example: QE40000000 3) Choose the Continue pushbutton. expand the object type and double-click Select Objects.1.sap. Here.2Assigning Source System for Activation To assign a source system.1Prerequisite: Check BW Activation User’s Role with BW Authorization Objects Assigned To install and use BW content for SAP S/4HANA integration. select Object types.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide 7.7. 7.

Make sure that the current job has finished successfully before you proceed with the activation of further objects. in SM37. please check and ensure the Activation version of Composite Provider is available by following steps: 1) Run transaction RSORBCT. the job status is Cancelled and error messages appear in the job log. and choose Modeling .4Activating BW Query 1) Access the transaction using one of the following navigation options: SAP BW Menu Modeling  Data Warehousing Workbench: Business Content © SAP SE Page 51 of 52 . choose the Continue pushbutton. You have started a background job to activate the Business Content. 7. As a result. 6) In the Information dialog box. choose Do Not Check. choose Version as A. If the Remote Activation in the Source System <…> dialog box appears. 5) In the Install Business Content in the Background dialog box. 7) Choose Exit and use SM37 to monitor the job until the job is finished. choose Install and select Install in Background. Result The following objects and before data flows have been activated Technical Name Object Type Description /PIM/SH_CP01 Composite Provider Sales Overview /PIM/SH_OV02 Open ODS view Sales Document Header /PIM/SH_OV03 Open ODS view Sales Order Items /PIM/SH_OV01 Open ODS view Material After successful activation.7. If the Exceeded runtime when collecting objects dialog box appears. Choose the proper package if the dialog box asking to assign the package appears. 4) At the top of the right-hand frame. try to execute step 4 again in the front end by choosing Install and selecting Install. 4) In Support Functions for Modeling Tools screen. chick activate icon button. c. d. Choose Transfer selections. 2) Search and find Composite Provider via Technical Name /PIM/SH_CP01 3) Right click Composite Provider /PIM/SH_CP01. Activate version is generated. choose Yes. choose Yes. If.SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide Technical Name Object Type Description /PIM/SH_CP01 Composite Provider Sales Overview b.1. choose Change.

b. 3) In the Selection of Query Objects dialog box: a. expand Query elements  Query and double-click Select Objects. c. 4) At the top of the right frame. choose Install and select Install in Background. Result Check and confirm all these Queries have been activated Technical Name Object Type Description /PIM/SH_CP01_Q0001 BW Query Sales Overview © SAP SE Page 52 of 52 .SAP Best Practices Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide Transaction Code RSORBCT 2) On the Data Warehousing Workbench: Business Content screen: a. At the top of the right frame. c. select Object types. choose Continue. In the middle frame. Select all the following queries: Technical Name Object Type Description / Query Sales Overview PIM/SH_CP01_Q0 001 b. choose Collection mode and select collect automatically. Choose Transfer. d. At the top of the right frame. choose Grouping and select Only Necessary Objects. In the left frame. If the Exceeded runtime when collecting objects dialog box appears.