How Can Central and Local Provider Easily Be Combined

How Can Central and Local
Provider Easily be Combined?
Applies to
SAP NetWeaver Business Warehouse 7.30 (BW7.30) SP05 and SAP NetWeaver Business Warehouse
Accelerator 7.20 (BWA7.20)/HANA 1.0 running as a database for SAP NetWeaver BW 7.3 SP05
Summary
This article describes how Central Provider (e.g. PartProvider of a MultiProvider) and Local Provider (e.g.
Flat Files) can easily be combined in a new data model inside a BW Workspace. It addresses the Business
Analyst in the line of business. As a prerequisite we recommend reading the article What is a BW
Workspace? from this article series.
Authors: Silvia Bratz, Klaus Nagel

Company: SAP AG
Created: September 2011
Version: 1.0
Author Biographies
Silvia Bratz: Development Project Manager, TIP In-Memory Platform BW (SAP AG).
Silvia Bratz joined SAP 12 years ago and began working as a technical SAP consultant for Business
Intelligence. Today, she is a member of the BWA and Data Management team.
Klaus Nagel: Development Manager, TIP In-Memory Platform BW (SAP AG).

Klaus Nagel joined SAP 10 years ago and started as a Developer in the BW team. He now holds the position
of a Development Manager and leads the BWA and Data Management team.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2011 SAP AG 1
How Can Central and Local Provider Easily be Combined?
Table of Contents
1. Introduction ............................................................................................................................................................ 3
2. Scenario .................................................................................................................................................................. 3
2.1. Description .............................................................................................................................................................. 3
2.2. New Data Model (CompositeProvider) ....................................................................................................................... 3
3. Scenario Data .......................................................................................................................................................... 4
3.1. MultiProvider .......................................................................................................................................................... 4
3.2. InfoObjects Customer and Product ......................................................................................................................... 5
3.3. Local Flat Files .......................................................................................................................................................... 6
4. Familiarize with the BW Workspace ........................................................................................................................... 7
4.1. Start the Application ................................................................................................................................................. 7
4.2. Switch Workspace .................................................................................................................................................... 7
4.3. Investigate Settings .................................................................................................................................................. 8
5. Create Local Provider.............................................................................................................................................. 10
5.1. Start the Application ............................................................................................................................................... 10
5.2. Select File .............................................................................................................................................................. 10
5.3. Change Columns .................................................................................................................................................... 11
5.4. Confirmation ......................................................................................................................................................... 12
6. Create CompositeProvider ...................................................................................................................................... 12
6.1. Start the Application ............................................................................................................................................... 12
6.2. Select Provider ....................................................................................................................................................... 12
6.3. Model CompositeProvider ...................................................................................................................................... 13
6.4. Edit Fields .............................................................................................................................................................. 16
6.5. Create Query ......................................................................................................................................................... 16
6.6. Check and Save ...................................................................................................................................................... 17
6.7. Confirmation ......................................................................................................................................................... 17
7. Execute Queries ..................................................................................................................................................... 18
8. Related Content ..................................................................................................................................................... 20
Copyright............................................................................................................................................................................ 21
2011 SAP AG 2
1. Introduction
A BW Workspace is a kind of small sandbox which IT defines. IT sets the boundaries, IT sets the amount of
resources that a BW Workspace can consume and exposes some of the central data models to the BW
Workspace (data of the models and their related semantics). The BW Workspace exposes the central data
in a logical fashion only. The data is not copied over into the BW Workspace, which means that no data
replication is needed.
The goal is to enable the Key Business Users to use this functionality in a dedicated and separated
environment, which is deeply embedded and integrated in the existing BW landscape. The BW Workspaces
bridge the gap between the architected and the departmental data marts. Therefore, Workspaces are
integrated, independent and, as the usage of the SAP Business Warehouse Accelerator is mandatory, they
are completely in-memory.
2. Scenario
2.1. Description
Let us assume that you are working as a global sales account manager for a company, selling computer
hardware and corresponding accessories.
In the central enterprise data warehouse, the SAP NetWeaver BW sales data for 2010 and 2011 is provided
in InfoCubes with a MultiProvider on top.
Additionally, the central SAP NetWeaver BW provides the companys central ABC Rating information of
customers worldwide in an InfoProvider, but you have an own ABC Rating available in a file you would like
to use to enrich the central sales data with your local information and report on the merged data.
Moreover, your company has not yet completely integrated the inventory management system and
therefore the SAP NetWeaver BW is not yet supplied with inventory data. The colleagues from the
inventory department provide you with the corresponding information (in stock, out of stock, ordered) per
product via flat file which you additionally want to merge with the BW sales data.
In order to keep the scenario simple and focus on the key aspects of the functionality we do not consider
details like time criteria or joins of key figures, but stick to an easy master data attribute enrichment
example.
A BW Workspace has been created for your team by the IT department in the BW Workspace maintenance
inside the SAP NetWeaver Business Warehouse. Furthermore the IT department provided the SAP
NetWeaver Business Client and corresponding roles for access to the BW Workspace Designer.
2.2. New Data Model (CompositeProvider)
BW Workspace Scenario Content: Different Providers and Relationships
2011 SAP AG 3
3. Scenario Data
3.1. MultiProvider
The MultiProvider Sales Total [ZTE11WSOA] consists of two PartProvider containing sales
data for the years 2010 and 2011. The important InfoObjects which we use to join our local file
information are Product and Customer.
2011 SAP AG 4
3.2. InfoObjects Customer and Product

The InfoObjects Customer and Product contain the following data.
InfoObject Customer (ZTE11CUST)
InfoObject Product (ZTE11PR)
2011 SAP AG 5
3.3. Local Flat Files
The local flat file Customer_ABC contains the technical key Customer as well as the
customer ABC Rating information.
The local flat file Inventory_Data contains the technical key Product as well as the product
availability information.
2011 SAP AG 6
4. Familiarize with the BW Workspace
4.1. Start the Application

When launching the SAP NetWeaver Business Client, an overview and short description of the
available applications of the BW Workspace Designer is displayed.
4.2. Switch Workspace

Under application Workspace-Tools and tab strip Switch Workspace have a look if you are
assigned to the correct BW Workspace.
2011 SAP AG 7
4.3. Investigate Settings
First of all you would like to verify the settings of your BW Workspace, in order to check how
much space on BWA/HANA has been assigned for the requested analysis and if a prefix has
been defined etc.
It is especially important to investigate if the correct central data (i.e. the MultiProvider with
its corresponding PartProvider) has been assigned.
Under My Workspace and tab strip Settings you can investigate the settings of the BW
Workspace which have been maintained by the IT department.
2011 SAP AG 8
Field Remark
Tab strip Settings Tab strip Settings
Workspace Technical name of the Workspace
Workspace Prefix A Workspace Prefix can be defined in the Workspace Maintenance but
is not mandatory. In case it is defined, it has to be used for all objects
created in the Workspace. Per default, the first three characters of the
technical name of the Workspace are derived. Nevertheless this can be
overwritten.
Expiry Date An expiry date can be defined to limit the lifetime of a Workspace. You
are informed how many days the Workspace is still alive. When the
expiry date is reached the Workspace is locked for usage.
MultiProvider A MultiProvider can be assigned but this is also not an obligatory

setting.
In case a MultiProvider is assigned:
All its PartProvider are transferred automatically but you have to at
least select one PartProvider by checking the relevant check box in
tab strip Central Provider (a later usage of these InfoCubes is not
mandatory).
The links (field links and connection type UNION) are taken over
automatically.
Analysis Authorizations defined on the MultiProvider level are taken
into account.
Queries defined on MultiProvider level can be used as Referenced
Queries
Maximum memory and The BW/BWA Administrator can limit the amount of memory to be used
number of providers on BWA/HANA by locally created objects in a Workspace. Also the
number of objects to be used can be restricted in order to prevent
uncontrolled growth.
Backup of data If the BW/BWA Administrator has set this flag, all locally uploaded data
in the Workspace is also saved on the BW database and can be
recovered from there should any BWA indexes be lost/corrupt.
2011 SAP AG 9
Under My Workspace and tab strip Central Provider you can have a look which central data
provider have been assigned to the BW Workspace by the IT department.
5. Create Local Provider

In the following chapter we are going to describe the straight forward way, how a flat file (MS Excel
or CSV format) can be uploaded in the BW Workspace Designer.

Start the application Create Local Provider and choose File as a source.
5.2. Select File

In this step you browse the file and transfer it.
2011 SAP AG 10
The technical name and description of the provider is proposed automatically.
5.3. Change Columns

The two columns of the file containing both character values have been analyzed by the
system and type Character String has been determined. Here you can decide on further data
type options and you can deselect columns.
2011 SAP AG 11
5.4. Confirmation
A Local Provider has been created. You can display the data directly or execute a query on the
Provider.
Finally we create another Local Provider by uploading the inventory file data. For this we can
also use the Link under Next Steps.
6. Create CompositeProvider
Now we will merge the just uploaded Local Provider data with the central sales data located in
the SAP NetWeaver Business Warehouse system. This is done by modeling a
CompositeProvider. Furthermore, during the modeling process, you will generate two queries
on top of the CompositeProvider.

Start the application Create CompositeProvider and skip the optional step of using a query as
template.
6.2. Select Provider

Select the MultiProvider Multiprovider: Sales Total [ZTE11WSOA] as well as the Local
Provider Customer_ABC [[T00]CUSTOMER_ABC and choose a technical name and
description.
2011 SAP AG 12
6.3. Model CompositeProvider
Supporting information about the CompositeProvider Model

The MultiProvider which has been assigned under settings in the BW
Workspace maintenance represents the UNION part of the CompositeProvider. This means
that all its fields have been brought over to the CompositeProvider definition and make up
the basis. During assignment of a MultiProvider under Central Provider in the BW
Workspace maintenance it is possible to exclude InfoObjects. This is reflected in the BW
Workspace Designer meaning that only these fields selected in the maintenance are
available in the CompositeProvider model.
For the Local Provider to be joined, binding type Inner Join is proposed.
2011 SAP AG 13
The screen displays all fields of the Local Provider to be joined with the fields of the
CompositeProvider.
If no link from the Local Provider field with the CompositeProvider field is created yet, the
value <not linked> is displayed in column Field of CompositeProvider. In this column you can
choose a suitable field from the CompositeProvider. If the field is just a display field and does
not represent a join condition, then you can check the box Dedicated Field.
The links between CompositeProvider and the actually linked Provider are displayed in a
graphical view below the field table. The graphical view is refreshed every time a link is
changed.
We choose customer as field of the CompositeProvider to link it to field Customer of the

Local Provider. Field ABC Rating is taken over as a Dedicated Field.
2011 SAP AG 14
Supporting information about the Mapping Proposer
If you use the mapping proposal by pressing Details Complete Proposal the system
comes to the same conclusion automatically.
The mapping proposer can analyze the metadata, data content and existing or historical
data models and shows the analysis results.
2011 SAP AG 15
6.4. Edit Fields

In this screen field names can be changed as well as some settings concerning units and
currencies can be maintained for special scenarios which we will discuss in another article.
6.5. Create Query

In the next step we are going to create a Standard and a Reference Query. Details will be
discussed in another article.
These queries can immediately be used for reporting after having activated the
CompositeProvider.
2011 SAP AG 16
6.6. Check and Save

Here you can have a look at all your configurations.
6.7. Confirmation
The CompositeProvider is ready for use now.
The second file can be connected in the same way. Also you can let the system support you
with the help of the Mapping Proposer. This will be discussed in more detail in another article
on the BW Workspaces.
2011 SAP AG 17
7. Execute Queries
In SAP BusinessObjects Analysis for MS Office Client e.g. we can execute the queries created in the
BW Workspace Designer as well as any other query which has been defined on top of the
CompositeProvider.
Standard Query
Reference Query
Calculated key figure
Drill-down to:
Calendar Year/Month
and
Customer
Available dimensions
for drill-down
Referenced query Sales Margin [ZTE11SALES_MARGIN]
2011 SAP AG 18
Calculated key figure
Drill-down to:
Calendar Year/Month,
Customer
and ABC Ranking Available dimensions
for drill-down with
characteristic ABC
Ranking in addition
Reference Query My First CompositeProvider Reference 3 [$T00WSPE3_REF3]
2011 SAP AG 19
8. Related Content
http://www.sdn.sap.com/irj/sdn/bwa
http://www.sdn.sap.com/irj/sdn/edw
The help.sap.com Link to the BW Workspaces will be updated here when available!
2011 SAP AG 20
Copyright
Copyright 2011 SAP AG. 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 AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document
serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (SAP
Group) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group 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.
2011 SAP AG 21

How Can Central and Local Provider Easily Be Combined

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

How Can Central and Local Provider Easily Be Combined

Uploaded by

Copyright:

Available Formats

How Can Central and Local

Provider Easily be Combined?

Authors: Silvia Bratz, Klaus Nagel

Klaus Nagel: Development Manager, TIP In-Memory Platform BW (SAP AG).

2.2. New Data Model (CompositeProvider)

BW Workspace Scenario Content: Different Providers and Relationships

3.2. InfoObjects Customer and Product

InfoObject Product (ZTE11PR)

3.3. Local Flat Files

4. Familiarize with the BW Workspace

4.1. Start the Application

4.2. Switch Workspace

4.3. Investigate Settings

Workspace Technical name of the Workspace

MultiProvider A MultiProvider can be assigned but this is also not an obligatory

5. Create Local Provider

5.1. Start the Application

5.2. Select File

The technical name and description of the provider is proposed automatically.

5.3. Change Columns

6.1. Start the Application

6.2. Select Provider

6.3. Model CompositeProvider

Supporting information about the CompositeProvider Model

We choose customer as field of the CompositeProvider to link it to field Customer of the

Supporting information about the Mapping Proposer

6.4. Edit Fields

6.5. Create Query

6.6. Check and Save

Calculated key figure

Referenced query Sales Margin [ZTE11SALES_MARGIN]

Calculated key figure

Reference Query My First CompositeProvider Reference 3 [$T00WSPE3_REF3]

You might also like