business process procedures - sap service …sapidp/... · web viewfor details on how to connect...

SAP S/4HANA

SAP BW

Dec 2016

English

Integration Scenarios Between SAP S/4HANA and SAP BW

SAP SEDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices

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

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 of

SAP Best Practices


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 of

SAP Best Practices


Contents1. 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.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.4 Consume SAP HANA Live Views and Open ODS Views in Composite Provider40

© SAP SE of

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.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 of

SAP Best Practices


Integration Scenarios Between SAP S/4HANA and SAP BW

1. PurposeIf you have Business Warehouse already running and also want to have the benefits of SAP S/4HANA, there is a possibility for consuming data from SAP S/4HANA in Business Warehouse.

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.

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.

2. PrerequisitesThe 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.

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.30

Composite Provider: available with BW/NW 7.40 SP5

© SAP SE of

http://service.sap.com/sap/support/notes/1954169

SAP Best Practices

Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide Open ODS View: available with BW/NW 7.40 SP5, Materialization option available with

SP8

© SAP SE of

SAP Best Practices


3. Integration of SAP S/4HANA and BW when S/4HANA and BW in Different DBs

3.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)

3.1.1 ArchitectureThe pictures below shows the architecture for this scenario.

© SAP SE of

SAP Best Practices


3.1.2 UsageIntegrating BW and SAP S/4HANA Analytics across different SAP HANA instances with Open ODS Views and SAP HANA Smart Data Access.Consumption of SAP S/4HANA Analytics transactional and master data views by SAP BW.

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, agile modeling through Open ODS Views

Capability to enrich data from SAP S/4HANA Analytics views with BW managed master data (e.g. 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.g. historical data / plan data) by utilizing SAP HANA Composite Provider

Open ODS Views can be materialized in BW if required, e.g. for snapshot scenarios

3.1.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), 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.g. hierarchy node variables

o Exceptions and conditions

o Currency conversion during report execution

o Report-to-Report Interface, …

Open ODS View provides functionality to switch from virtual access to persistence. Generation of data flow with DataSource, DataStore object (Advanced) and BW Transformation (requires SAP BW 7.40 SP 8 or higher)

© SAP SE of

SAP Best Practices


3.1.4 How to ImplementIn this section, we discuss how to implement this scenario. 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.

In BW, SAP HANA Smart Data Access is used as a data source for Open ODS Views. This enables bringing content from different EDW landscapes together without any replication.

For more information, visit: help.sap.com - SAP HANA Smart Data Access or help.sap.com - HANA SDA in BW

3.1.4.1 Establish Smart Data AccessRequirements:

For creating remote sources, the system privilege CREATE REMOTE SOURCE is required

For creating virtual tables, 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, then the HANA SAP-<SID> user needs the object privilege CREATE VIRTUAL TABLE, granted by the owner of the remote source

3.1.4.1.1 Add SAP HANA System in SAP HANA StudioThis is a basic step before creating BW Project 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…”

© SAP SE of

http://help.sap.com/saphelp_nw74/helpdata/en/bb/df686dc0d94f779b5c11d06753da95/content.htm

http://help.sap.com/saphelp_nw74/helpdata/en/bb/df686dc0d94f779b5c11d06753da95/content.htm

http://help.sap.com/saphelp_hanaplatform/helpdata/en/a0/7c7ff25997460bbcb73099fb59007d/content.htm?frameset=/en/a0/7c7ff25997460bbcb73099fb59007d/frameset.htm&current_toc=/en/00/0ca1e3486640ef8b884cdf1a050fbb/plain.htm&node_id=642&show_children=true#jump642

SAP Best Practices


3) Then enter your system information

4) Click Next > and enter your user information, click Finish

© SAP SE of

SAP Best Practices


3.1.4.1.2 Create Remote Source 1) Open SAP HANA Modeler Perspective in SAP HANA studio

2) Open Provisioning -> Remote Sources, right click Remote Sources and select New Remote Source….

3) Enter a Source Name and choose the Adapter Name. Here we select HANA (ODBC), enter values for Server, Port, Database Name, also enter the User Name and the Password

4) Click the Save Editor icon in the upper right-hand corner of the screen. 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)

3.1.4.1.3 Create Virtual Tables from Remote Objects1) In the Systems view Catalog <Schema_Name> Tables, right click and select New

Virtual Table...

© SAP SE of

SAP Best Practices


1) Enter a Table Name and click Browse…

2) A dialog box appears, select the remote source, database, and table

The source name and the remote object are filled in automatically by the names of the components chosen in the previous step.

3) Click the Save this Editor icon in the upper right hand corner of the screen.

This creates a virtual table. The new virtual table will appear in the tree view Catalog <schema> Tables.

© SAP SE of

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 of

SAP Best Practices


3.1.4.2 Create and Refine Open ODS Views

3.1.4.2.1 Establish BW Project in SAP HANA Studio1) 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 of

SAP Best Practices


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.

3.1.4.2.2 Create Open ODS View for Master DataFor creating Open ODS Views, you have to use a modelling tool. The next steps describe how to create Open ODS Views in SAP HANA Studio.

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 of

SAP Best Practices


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 of

SAP Best Practices


© SAP SE of

SAP Best Practices


3.1.4.2.3 Define Key Fields for Master Data Open ODS View1) Define key fields

a) Representative Key Fieldb) 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. They can be moved to target folders by drag and drop.

© SAP SE of

SAP Best Practices


3.1.4.2.4 Refine and Activate Open ODS View for Master Data1) You can now further refine your Open ODS View e.g. 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, e.g. 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.

3.1.4.2.5 Create Open ODS View for Transactional DataCreate 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 of

SAP Best Practices


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), 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 of

SAP Best Practices


3.1.4.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.g. to the previous created master data Open ODS Views)

© SAP SE of

SAP Best Practices

Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide a) Choose Assocaiton With, 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

3.1.4.2.7 Activate Open ODS ViewNow you can activate the Open ODS View and you can either reuse it in a CompositeProvider (e.g. combining the information with BW InfoProvider) or implement BEx Queries directly and consume them e.g. in SAP BusinessObjects Analysis, edition for Microsoft Office.

Remember to restrict your data by MANDT in all BEx Queries.

© SAP SE of

SAP Best Practices


3.1.4.3 Create BEx Query1) Open BExQuery Designer and create a new Query

2) Choose you preferred InfoArea and Open ODS View

3) Define the BEx Query using e.g.:

Filer, variables

Free characteristics, rows. columns

Restricted & calculated key figures, formulas, structures, cell definition

Conditions and exceptions

4) Fix restriction in “Characteristic Restrictions”

© SAP SE of

SAP Best Practices


5) Save BEx Query and execute

© SAP SE of

SAP Best Practices


4. Integration of SAP S/4HANA in BW when BW Embedded in SAP S/4HANA

4.1 Modeling-free via ODP Transient ProviderUse 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

4.1.1 ArchitectureThe picture below shows the architecture for this scenario.

4.1.2 UsageTransactional 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.

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, node variables and BW analysis authorizations are not supported Query not based on BW InfoObjects).

© SAP SE of

SAP Best Practices


4.1.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.g. 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, as the transient provider is generated with same technical name in all systems

4.1.4 How to ImplementIn the section below, we discuss how to implement this scenario.

Background Information

The ODP Transient Provider is a specific InfoProvider type for Operational Analytics. It’s derived from the ODP metadata definition automatically and dynamically. There is no additional modeling necessary.

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) Execute4) A preview of the Transient Provider for the selected Operational Data Provider is

displayed in a tree structure

© SAP SE of

SAP Best Practices


© SAP SE of

SAP Best Practices


4.1.4.1 Create BEx QueryOpen 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>.

You can find examples in the following table:

Open ODS View CDS Views (SQL Name)

CDS Views in BExQuery

ZS4CUSTOMER (Customer Master Data) I_CUSTOMER_CDS 2CI_CUSTOMER_CDS

ZS4_SO_HDR (Sales Document Header) ISDSALESDOC 2CISDSALESDOC

ZS4CURRENCY (Currency) IFICURRENCYTEXT

2CIFICURRENCYTEXT

4.1.4.2 Define BEx Query Definition1) Define the BEx Query using e.g.:

Filer, variables

Free characteristics, rows. columns

Restricted & calculated key figures, formulas, structures, cell definition

Conditions and exceptions

© SAP SE of

SAP Best Practices


2) Fix restriction in “Characteristic Restrictions”

3) Save BEx Query and execute

© SAP SE of

SAP Best Practices


5. 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

5.1 UsageConsumption of SAP S/4HANA and SAP HANA Live transactional and master data views by Open ODS Views in BW in a Composite Provider.

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, agile modeling through Open ODS Views

Capability to enrich data from SAP S/4HANA Analytics views with BW managed master data (e.g. 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.g. 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, you can reuse your modeled Open ODS Views in a CompositeProvider later.

Otherwise you will have to model the Open ODS Views based on SAP HANA Live and SAP S/4HANA first. This chapter describes, how to create, model and refine these Open ODS Views based on SAP HANA Live and SAP S/4HANA and how to consume them in a CompositeProivder.

5.1.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), 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.g. hierarchy node variables

o Exceptions and conditions

© SAP SE of

SAP Best Practices

Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide o Currency conversion during report execution

o Report-to-Report Interface, …

Open ODS View provides functionality to switch from virtual access to persistence. Generation of data flow with DataSource, DataStore object (Advanced) and BW Transformation (requires SAP BW 7.40 SP 8 or higher)

© SAP SE of

SAP Best Practices


5.2 SAP BW and SAP S/4HANA and SAP HANA Live Deployed Across Different SAP HANA Instances


5.2.2 How to ImplementFor this scenario we use Smart Data Access to establish connection to SAP S/4HANA and SAP HANA Live system. 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.

5.2.2.1 Establish Smart Data AccessIn case you have SAP HANA Live and SAP S/4HANA running on another SAP HANA instance than SAP BW, you will have to configure SAP HANA Smart Data Access first. For guided configuration, please refer to chapter 3.1.4.1 ( Establish Smart Data Access ) .

5.2.2.2 Create Open ODS Views Based on SAP HANA LiveThe 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. The procedure is described in chapter 3.1.4.2 ( Create and Refine Open ODS Views ) .

At step 3) where you define the data source for Open ODS View, just select the Remote Source for your SAP HANA Live system and a SAP HANA Live View as DB Object Name. Then define the Open ODS Views similar to the described SAP S/4HANA modeling.

© SAP SE of

SAP Best Practices


5.2.2.3 Create Open ODS Views Based on SAP S/4HANATo create Open ODS views based on SAP S/4HANA views, fulfill the procedure described in chapter 3.1.4.2 ( Create and Refine Open ODS Views ) . For consumption of these Open ODS views follow the steps which are described in this chapter.

5.2.2.4 Consume Open ODS Views in a Composite Provider1) In the context menu of your BW project, choose “New” -> “CompositeProvider”

2) Define Composite Provider and define the operation type you want to execute (Here we choose Union)

© SAP SE of

SAP Best Practices


In the next step you see that the screen is divided into 3 tabs (Overview, 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. Setting External View to ‘X’ leads to the generation of a SAP HANA view which can be consumed through SQL.

4) Scenario tab Setting

© SAP SE of

SAP Best Practices

Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide On the Scenario tab page, you can select the participating InfoProviders or SAP HANA models. You specify which fields from these PartProviders should be used as output columns of the CompositeProvider.

a) Right-Click on Union and choose Add..

b) In the ‘Add Provider’ window, we can add Open ODS Views, BW InfoProviders or SAP HANA Views. Enter the name of the Open ODS View you want to search for.

Choose OK when you’ve found the matching item.

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 of

SAP Best Practices


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. For example, for characteristics, you can drag objects from both sources onto the same destination to do a union.

As an additional scenario, you can also add a BW InfoProvider to the CompositeProvider you created in the previous steps. You can drag historical key figure from BW InfoProvider, real-time key figure from Open ODS Views based on SAP S/4HANA or SAP HANA Live, to do an integrated analysis.

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, OpenODSViews or you can assign constants.

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 of

SAP Best Practices


3) Activate CompositeProvider

After activating you are now ready to query the CompositeProvider

5.2.2.5 Create BEx QueryCreate 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”.

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, please refer to chapter 3.1.4.3 ( Create BEx Query ) .

© SAP SE of

SAP Best Practices


5.3 SAP HANA Live and SAP BW in the Same SAP HANA DB

5.3.1 ArchitectureThe 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. 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.

5.3.2 How to ImplementFor this scenario we use Smart Data Access to establish connection to SAP S/4HANA system. 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.

5.3.2.1 Establish Smart Data AccessIn 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. For guided configuration, please refer to chapter 3.1.4.1 ( Establish Smart Data Access ) .

5.3.2.2 Create Open ODS Views Based on SAP HANA LiveSAP HANA Live models can be consumed in a Composite Provider directly or modeled as Open ODS Views.

In case of modeling, please refer to chapter 3.1.4.2 ( Create and Refine Open ODS Views ) . When the Open ODS View wizard for creation pops up, in the fields for source definition, please insert your SAP HANA Live Remote Source and SAP HANA Live DB Object Name.

© SAP SE of

SAP Best Practices


5.3.2.3 Create Open ODS Views Based on SAP S/4HANATo create Open ODS views based on SAP S/4HANA views, proceed how it is described in chapter 3.1.4.2 ( Create and Refine Open ODS Views ) . For consumption of Open ODS views follow the steps which are described in the next step.

5.3.2.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. Please refer to chapter 5.2.2.4 ( Consume Open ODS Views in a Composite Provider ) .

In this use case, SAP BW and SAP HANA Live are located in the same SAP HANA DB. 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.

© SAP SE of

SAP Best Practices


5.4 SAP S/4HANA and SAP BW in the Same HDB with Separate Standalone BW


5.4.2 How to ImplementFor this scenario we use Smart Data Access to establish connection to SAP HANA Live system. 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.

5.4.2.1 Establish Smart Data AccessIn case you have SAP HANA Live running on another SAP HANA instance than BW, you will have to configure SAP HANA Smart Data Access first. For guided configuration, please refer to chapter 3.1.4.1 ( Establish Smart Data Access ) .

5.4.2.2 Create Open ODS Views Based on SAP HANA LiveThe 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 procedure is described in chapter 3.1.4.2 ( Create and Refine Open ODS Views ) .

At step 3) where you define the data source for Open ODS View, 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. Then define the Open ODS Views similar to the described SAP S/4HANA modeling.

© SAP SE of

SAP Best Practices


5.4.2.3 Create Open ODS Views Based on SAP S/4HANABefore SAP S/4HANA Models can be consumed in a Composite Provider they have to be modeled in Open ODS Views.

How to create Open ODS Views as it is described in chapter 3.1.4.2 ( Create and Refine Open ODS Views ). Select different Source Type (-> Database Table or View) in step 3).

5.4.2.4 Consume Open ODS Views in a Composite ProviderThe steps for creating a CompositeProvider are similar to the other integration scenarios for SAP S/4HANA and SAP HANA Live in BW. Please refer to chapter 5.2.2.4 ( Consume Open ODS Views in a Composite Provider ) .

© SAP SE of

SAP Best Practices


6. Sample Content

6.1 Integration of SAP S/4HANA in BW when SAP S/4HANA and BW in Different DBs

UseThe following is a sample for the Integration of SAP S/4HANA in BW when SAP S/4HANA and BW in different DBs. Please follow following configurations to install predefined content.

For example, QE4 is a SAP S/4HANA system. CBW is BWoH 740 system (100 is BI client of BW). 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).

In CBW/100, create logical system QE40000000

In CBW/100, create DB connect Source system (eg: QE40000000) based on smart data access connection (S4H_QE4)

In CBW/100, activate predefined BI Content based on Source system (QE40000000)

6.1.1 Prerequisite Software ComponentTo install predefined BW content for the integration with SAP S/4HANA, it is necessary to install BP-BW 740V2 or above SP. To install BP-BW 740V2 or above SP, SAP NETWEAVER 7.4 SP13+ and BI_CONT 757 SP08+ are required.

To download BP-BW 740V2 or above Vx BW addon component (RDS BW BI CONT Addon) deployed in this solution, perform the following steps:

In your Web browser, go to http://service.sap.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" ), click Installation.

In the Download area, select the checkbox, then choose Add to Download Basket. Download it with SAP Download Manager.

Please download the BP-BW 740 latest Vx version, since the latest version always includes the fixes to previous issues.

Currently, 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, Open ODS View will only show the SQLViews of CDS Views without parameters. Please refer details in SAP Note 2198480 (point 12).

The content in this sample is tested via SAP S/4HANA 1511 on premise version with Netweaver 7.50. In future version’s SAP S/4HANA 1611+ based on higher versions’ NetWeaver (7.52+), the previous released CDS view (released earlier than SAP S/4HANA 1611) is not supported in this solution architecture, due to the new possibility

© SAP SE of

http://service.sap.com/swdc

SAP Best Practices

Integration Scenarios Between SAP S/4HANA and SAP BW: Configuration Guide for the client handling in CDS views. To validate whether CDS view is still supported on SAP S/4HANA 1611+ under this solution architecture, 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. For example, SAP S/4HANA system ID is QE6:

set 'CDS_CLIENT' = '910';

SELECT TOP 1000 * FROM "SAPQE6"."ISDSLSORDERITEM";

If it is still able to return data without setting 'CDS_CLIENT', then the CDS view is supported on SAP S/4HANA 1611+, or else it is not supported.

6.1.2 Prerequisite NotesPlease 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

6.1.3 In BW’s Underlying SAP HANA, Establish Smart Data Access to SAP S/4HANA

Requirements:

For creating remote sources, the system privilege CREATE REMOTE SOURCE is required

For creating virtual tables, 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, then the HANA SAP-<SID> user needs the object privilege CREATE VIRTUAL TABLE, granted by the owner of the remote source

6.1.3.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.e., cbwhostname)

Instance Number The instance number of BWoH’s HANA database (i.e: 00)

User Name The user name of BWoH’s HANA database

Password The password of BWoH’s HANA database

4) Click Finish. As a result, BWoH’s HANA database (eg: CBW) has been added in SAP HANA Studio

© SAP SE of

SAP Best Practices


6.1.3.2 Create Remote Source 1) Open SAP HANA Modeler Perspective in SAP HANA studio

2) For BWoH’s HANA instance (eg: CBW), open Provisioning -> Remote Sources, right click Remote Sources and select New Remote Source….

3) Enter a Source Name and choose the Adapter Name. Here we select HANA (ODBC), enter values for Server, Port, Database Name, also enter the User Name and the Password.

Source name The name for smart data access connection (eg: S4H_QE4)

Server Name The hostname of SAP S/4HANA’s HANA database (i.e., qe4hanahostxxx)

Port The port number of SAP S/4HANA’s HANA database (i.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. The remote source (eg: S4H_QE4) has been created successfully

5) In SAP HANA Studio for BWoH’s HANA instance (eg: CBW), run the following

GRANT CREATE VIRTUAL TABLE, DROP ON REMOTE SOURCE "S4H_QE4" TO "SAPCBW";

6.1.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.

1) Access the transaction using:

Transaction code SPRO

© SAP SE of

SAP Best Practices


IMG menu SAP NetWeaver Application Server IDoc Interface / Application Link Enabling (ALE) Basic Settings Logical systems Define Logical System

2) Choose New entries.

3) In the Log System column, enter a name for the logical system that you want to create.

4) In the Name column, enter a description of the logical system.

Log. System Name

<Logical system>, for example QE40000000 Remote Source SAPQE4

5) Save your entries and a transport request for Workbench appears.

6) Select an existing request or create a new request, if necessary. A transport request for Customizing appears.

7) Select an existing request or create a new request, if necessary.

6.1.5 In BW, Create DB Connect Source System Based on Smart Data Access to SAP S/4HANA

To carry out the activity, choose one of the following navigation options in the SAP BW system:

Transaction Code RSA1

SAP BW Menu Modeling Data Warehousing Workbench: Modeling1) Choose Modeling.

2) Choose Source Systems.

3) Select the entry DB connect in the window on the right.

4) Choose the Context menu (right-click).

5) Choose Create.

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.0 (You can also use other naming reserved for SAP HANA DB based on customization)

If you are not able to find HDB 1.0 in the Source system Type list, it is necessary to maintain this entry in table RS3DREL as following:

Run T-code SM30, input Table/View as RS3DREL, set the display to change, and click New Entries button. Input following in New Entries: Details of Added Entries screen:

Field Entry

Source Type Eg: HDB Source Sys. Release Eg: 1.0

Long Description Eg: Sap HANA DB

Content Exists Selected

© SAP SE of

SAP Best Practices


Field Entry

SourceSys Type DB ConnectClick Save Button to save above new entry.

7) In DB Connect Parameters dialog, make the following entries and click Apply button:

Field Entry

Connection Type HANA Smart Access Remote Source Eg: S4H_QE4Remote DB The Remote DB name, eg <NULL>

DB Owner Schema SAP<SID>, SID is for the SAP S/4HANA. Eg: SAPQE4

8) As a result, Source system has been created (eg: QE40000000)

6.1.6 Check Namespaces /PIM/ Prior to Activating Business Content

Procedure1) Go to transaction for Transport Organizer Tools (transaction code SE03).

2) On the Transport Organizer Tools screen, choose Transport Organizer Tools Administration Display/Change Namespace.

If the Administration folder is not displayed, you do not have the authorization to view it or make changes in the activities included in this folder. Contact your system administrator to resolve this authorization issue.

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 standard

SAP

/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.Locate the namespace /PIM/ and verify that it is set to Modifiable.

5) If the namespace /PIM/ does not display Modifiable, in the Modifiable column, select the Modifiable value from the dropdown to change the value.

The Global Setting must be set to Modifiable to allow the Namespace/Name Range area to be modified; otherwise you cannot change the namespace Modifiable column value for /PIM/.

6) Go to transaction BW Namespace Maintenance (transaction code RSNSPACE).7) In the BW Partner Namespaces section, verify that the following entry is present:

Namespace Gen NS BW appl. System type Active Long Description

/PIM/ /B756/ BW PAR X Namespace for SAP packaged objects:

© SAP SE of

SAP Best Practices


/PIM/ BW content

8) If the entry is not present, create by choosing the Create Partner NS pushbutton and adding the previously listed entries.

© SAP SE of

SAP Best Practices


6.1.7 Activate BW Content

6.1.7.1Prerequisite: Check BW Activation User’s Role with BW Authorization Objects Assigned

To install and use BW content for SAP S/4HANA integration, 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 CompositeProvider authorizations)

Authorizations for working with CompositeProviders and their subobjects

S_RS_ODSV (Open ODS view) Authorizations for working with Open ODS Views

Please go to http://help.sap.com/nw74 , and search and find the details in chapter Authorizations for Modeling with BW Modeling Tools.

6.1.7.2Assigning Source System for ActivationTo assign a source system, 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, choose Edit Source System Assignment from the context menu.

2) In the Select source systems dialog box, 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. Here, 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.

6.1.7.3Activating Info Provider1) To activate Business Content:, choose one of the following navigation options:

SAP BI Menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Business Content


2) On the Data Warehousing Workbench: Business Content screen, proceed as follows:

At the top of the right-hand frame, choose Grouping and select In Data Flow Before.

At the top of the right-hand frame, choose Collection mode and select Collect Automatically.

In the left frame, select Object types.

In the middle frame, expand the object type and double-click Select Objects.

3) In the <System ID>/<Client> Data Warehousing Workbench: BI Content dialog box:

a. Select the following objects:

© SAP SE of

http://help.sap.com/nw74

SAP Best Practices


Technical Name Object Type Description

/PIM/SH_CP01 Composite Provider Sales Overview

b. Choose Transfer selections.

c. If the Exceeded runtime when collecting objects dialog box appears, choose the Continue pushbutton.

d. If the Remote Activation in the Source System <…> dialog box appears, choose Do Not Check.

4) At the top of the right-hand frame, choose Install and select Install in Background.

5) In the Install Business Content in the Background dialog box, choose Yes.

6) In the Information dialog box, choose Yes.

If, in SM37, the job status is Cancelled and error messages appear in the job log, try to execute step 4 again in the front end by choosing Install and selecting Install. Choose the proper package if the dialog box asking to assign the package appears.

7) Choose Exit and use SM37 to monitor the job until the job is finished.

You have started a background job to activate the Business Content. Make sure that the current job has finished successfully before you proceed with the activation of further objects.

ResultThe following objects and before data flows have been activated


/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, please check and ensure the Activation version of Composite Provider is available by following steps:

1) Run transaction RSORBCT, and choose Modeling .2) Search and find Composite Provider via Technical Name /PIM/SH_CP01

3) Right click Composite Provider /PIM/SH_CP01, choose Change.

4) In Support Functions for Modeling Tools screen, choose Version as A, chick activate icon button.

As a result, Activate version is generated.

6.1.7.4Activating BW Query1) Access the transaction using one of the following navigation options:

SAP BW Menu Modeling Data Warehousing Workbench: Business Content

© SAP SE of

SAP Best Practices



2) On the Data Warehousing Workbench: Business Content screen:

a. At the top of the right frame, choose Grouping and select Only Necessary Objects.

b. At the top of the right frame, choose Collection mode and select collect automatically.

c. In the left frame, select Object types.

d. In the middle frame, expand Query elements Query and double-click Select Objects.

3) In the Selection of Query Objects dialog box:

a. Select all the following queries:


/PIM/SH_CP01_Q0001 Query Sales Overview

b. Choose Transfer.c. If the Exceeded runtime when collecting objects dialog box appears, choose

Continue.

4) At the top of the right frame, choose Install and select Install in Background.

ResultCheck and confirm all these Queries have been activated


/PIM/SH_CP01_Q0001 BW Query Sales Overview

© SAP SE of

business process procedures - sap service …sapidp/... · web viewfor details on how to connect...

Documents