Exploring SAP NetWeaver BW on SAP HANA in
combination with SAP BusinessObjects BI 4.x
Content`s
Disclaimer... 4
1 Introduction ... 5
2 Logon Details ... 6
3 Connecting to your environment ... 7
3.1 Remote Desktop Connection - Windows 7 ... 7
3.2 Windows XP: ... 8
4 Starting and Stopping systems ... 9
5 Starting your SAP NetWeaver BW and SAP HANA system ... 11
6 Data modeling scenarios for BW Administrators ... 12
6.1 Scenario 1 – Converting a regular InfoCube to an In-Memory Optimized InfoCube... 12
6.2 Scenario 3 – Creating a Semantically Partitioned Object (SPO) ... 17
7 Using Mixed Scenarios with SAP NetWeaver BW on SAP HANA... 28
7.1 Scenario 1 – Using a Composite Provider to join Transient Provider with a Data Store Object ... 29
7.2 Scenario 2 – Create a Virtual Provider based on HANA Model with an aggregated view ... 44
7.3 Scenario 3 – Create a BEx Query and leverage the counting functions of the OLAP Engine... 55
7.4 Scenario 4 – Reporting on a Transient Provider using BI Authorizations ... 60
7.5 Scenario 5 – Create / Change a Composite Provider Join Type ... 75
7.6 Scenario 6 – Using a Composite Provider to join with Master data to display Navigational Attributes ... 80
8 Using BW Workspaces with SAP NetWeaver BW on SAP HANA ... 82
8.1 Scenario Overview ... 82
8.2 Scenario 1 – Check and Validate the BW Workspace definition ... 83
8.3 Scenario 2 – Upload Customer ABC rating file ... 86
8.4 Scenario 3 – Upload temporary Inventory file and join with Central Sales and Customer rating ... 99
9 BI scenarios for business analysts / managers... 107
9.1 Configuring your mobile device ... 107
9.1.1 Installation on iOS: ... 107
9.1.2 Installation on Android: ... 107
9.1.3 Configuring Mobile BI ... 108
9.2 SAP Lumira with SAP NetWeaver BW on SAP HANA ... 109
9.2.1 Exercise 1: Connect to the SAP HANA model ... 109
9.3 SAP BusinessObjects Explorer with SAP NetWeaver BW on SAP HANA... 126
9.3.1 SAP BusinessObjects Explorer – Exercise 1 ... 126
9.4 SAP BusinessObjects Predictive Analysis with SAP NetWeaver BW on SAP HANA ... 137
10 BI Scenarios for Power Users ... 152
10.2.3 Exercise 2: Create your first hierarchical Crystal Reports ... 170
10.3 Web Intelligence and SAP NetWeaver BW ... 183
10.3.1 Scenario Overview ... 183
10.3.2 Exercise 1: Creating your first Web Intelligence report with SAP NetWeaver BW data ... 183
10.3.3 Exercise 2: Creating your first hierarchical Web Intelligence report with SAP NetWeaver BW data .... 197
10.4 SAP BusinessObjects Analysis, Edition for Microsoft Office and SAP NetWeaver BW ... 207
10.4.1 Download of SAP BusinessObjects Analysis, edition for Microsoft Office ... 207
10.4.2 Installation of SAP BusinessObjects Analysis, edition for Microsoft Office ... 209
10.4.3 Exercise 1: Creating your first workbook ... 210
10.4.4 Exercise 2: Using SAP BW Workspaces with SAP BusinessObjects Analysis, edition for Microsoft Office 234 10.5 SAP BusinessObjects Analysis, edition for OLAP... 240
10.5.1 Exercise 1: Creating your first report using SAP BusinessObjects Analysis, OLAP edition ... 240
10.6 SAP BusinessObjects Explorer with SAP NetWeaver BW on SAP HANA ... 259
10.6.1 Exercise 1: Configuring central SAP HANA connectivity ... 259
10.6.2 Exercise 2: Creating a connection for SAP HANA using the Information Design Tool ... 262
10.6.3 Exercise 3: Creating an Information Space on top of SAP NetWeaver BW ... 265
10.7 SAP BusinessObjects Design Studio with SAP NetWeaver BW on SAP HANA ... 281
10.7.1 Exercise 1: Creating your first application ... 281
10.7.2 Exercise 2: Create your second mobile dashboard ... 296
10.8 Importing the SAP NetWeaver BW model to SAP HANA ... 304
10.8.1 Exercise 1: Importing a InfoProvider into SAP HANA as analytical model ... 304
Disclaimer
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. This presentation is not subject to your license agreement or any other service or subscription agreement with SAP. SAP has 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's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP 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. This
document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP´s willful misconduct or gross negligence.
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.
1
Introduction
This document outlines the necessary steps to connect to your SAP NetWeaver BW on SAP HANA landscape in combination with SAP BusinessObjects BI 4.x.
The systems that are being used are: - SAP NetWeaver BW 7.34 - SAP HANA SP07
- SAP BusinessObjects BI 4.1 SP02 The document is split into three sections:
- The first part is targeting mainly DWH managers that are interesting in those data modeling scenarios that are now possible with SAP NetWeaver BW on SAP HANA.
- The second section is focused towards BI / DWH managers interested in the final results that are now possible with SAP NetWeaver BW on SAP HANA and SAP BusinessObjects BI 4.x.
- The third section is focused more towards BI / DWH implementation teams and power users that are interested in learning on how to create the new data models and the BI content.
2
Logon Details
The following table shows all the required logon credentials.
SAP BusinessObjects BI4 System
BI4 Server Name SBOP41.dummy.nodomain BI4 Administrator administrator
BI4 Administrator Password Welcome! (case sensitive) BI4 Administrator Authentication Enterprise
BI4 SAP Credentials Demo
BI4 SAP Credentials Password Welcome! (case sensitive) BI4 SAP Credentials Authentication SAP
BI4 Operating System User DEMO BI4 Operating System Password Welcome! SAP NetWeaver BW System
SAP BW System ID A4H
SAP BW Server Name abapci.dummy.nodomain SAP BW Client Number 001
SAP BW System Number 00
SAP User ID DEMO
SAP User password Welcome! (case sensitive) SAP HANA System
SAP HANA System ID HDB
SAP HANA Server Name hanadb.dummy.nodomain SAP HANA System Number 02
3
Connecting to your environment
To start your hands-on activities follow these steps to establish a Remote Desktop connection to the hosted environment. In the following sections we show the needed steps to start Remote Desktop Connection on your operating system.
3.1 Remote Desktop Connection - Windows 7 1. Click Start.
2. Select Programs.
3. Select Accessories.
4. Select Remote Desktop Connection.
5. Enter the given IP number for the SAP BusinessObjects BI Server / Client into the field Computer. 6. Click Options.
7. Navigate to the tab Display.
8. Ensure the Display Configuration setting is moved to the far right so that it says Full Screen. 9. Click Connect.
3.2 Windows XP: 1. Click Start
2. Select Programs.
3. Select Accessories.
4. Select Communications.
5. Select Remote Desktop Connection.
6. Enter the given IP number for the SAP BusinessObjects BI Server / Client into the field Computer. 7. Click Options.
8. Navigate to the tab Display.
9. Ensure the Display Configuration value is moved to the far right so that it says Full Screen. 10. Click Connect.
4
Starting and Stopping systems
In the SAP Cloud Appliance Library you can find the complete details for your systems, such as the IP numbers and you are able to start and stop the system based on your needs, which is important to control the costs.
On the tab Instances you can find the entry for the deployed solution. Please note that there is only one entry, as this is treated as a solution.
By clicking on the line item on the tab instances, you can then see the complete details of the instances that were created and you are also able to receive the IP Addresses for each of the system (left hand side).
In case you would like to suspend, restart, or terminate the systems, it is highly recommended that such tasks are performed using the SAP Cloud Appliance Library and not directly in the Amazon AWS Management Console as in that way configurations such as the IP numbers are automatically assigned to the correct systems.
You can find the options to suspend, restart, or terminate the systems in the SAP Cloud Appliance library on the tab Instances as part of the entry for your system.
5
Starting your SAP NetWeaver BW and SAP HANA system
After you started the systems on SAP HANA Marketplace the SAP HANA and SAP NetWeaver BW system will be started automatically, but there might be a situation where you would like to stop, start, or simply restart the systems. The following steps show you how to start the systems.
1. Logon using Remote Desktop to your client environment.
2. After you logged on to the environment you can see the icon for the SAP Management Console on the desktop.
3. Double-Click on the icon.
4. Select the A4H instance.
5. Select the menu Action > Start to start the SAP NetWeaver BW instance.
6. When asked to provide user credentials, use the Linux OS user a4hadm listed at the beginning of this document. You can use the same steps to start the SAP HANA system HDB by using the user hdbadm.
6
Data modeling scenarios for BW Administrators
In the next set of scenarios you will learn more about the new data modeling capabilities of SAP NetWeaver BW on SAP HANA.
6.1 Scenario 1 – Converting a regular InfoCube to an In-Memory Optimized InfoCube In this section we will convert a regular InfoCube to an In-Memory Optimised InfoCube.
1. Go to transaction “RSA1”
Note:
Select “InfoProvider” in the left hand pane, if it is not already. This should display several folders on the right hand pane.
2. Under the “IMO_CUBE” InfoArea locate the cube “Convert to IMO CUBE”.
3. Right click on your Cube and select “Display”.
4. Under the “Settings”
sectionyou see one entry indicating it’s a standard InfoCube.
5. Using the menu “Extras” and select the option “Information (logs/status)”
6. In the new popup screen click “Dictionary/DB status”
7. This new popup screen should display the different tables that form this regular InfoCube.
Notice the ‘F – Fact table’ and the ‘E – Fact table’ and the various dimension tables are displayed as expected.
Take a screen shot of these tables to compare it later.
8. Back out of the two popup screens to display the InfoCube in display mode (Click Enter or
twice)
Ensure you are in display mode for the cube before you proceed to the next step.
9. Use the “Goto” menu and select the option
“Conversion to SAP HANA-Optimized”.
10. In this new screen you should already see the technical name of your InfoCube populated for the option “Standard
InfoCube”.
With the default options selected click “execute”
(Hit F8 or )
Confirm the popup message indicating it was successfully activated. 11. Back out of this screen to
go back to the InfoCube display mode.
Notice that there is a new entry under the “Settings” section named “Subtype” indicating this is now a “SAP HANA Optimized Infocube”
12. Now let’s look at the new tables that make up the In-memory Optimized InfoCube.
To locate the tables, use the menu Extras -> Information (Logs/status) -> Dictionary/DB status. Notice that now the
InfoCube is made up of only 2 tables.
Of this the “D” table is where technical information like Request ID and other related information. The “F” table is where the transaction data resides (master data SID’s and key-figures).
13. Go back to the Data Warehousing Workbench and notice that your cube has a new icon indicating it is an In-memory Optimized InfoCube.
6.2 Scenario 3 – Creating a Semantically Partitioned Object (SPO) In this section we will create a new Semantically Partitioned Object (SPO).
Explanation Screenshot
Step: Create a SPO object based on InfoCube
1. Call transaction “RSA1”. Create a new InfoArea. For this right mouse click in the blank space below the existing InfoArea and select “Create InfoArea…” In the popup screen enter the following values: InfoArea: IMO_SPO
Long description:
Semantically Partitioned Objects
2. Once created successfully, the screen should look like this.
3. Use a right mouse click on this InfoArea and select “Create InfoCube…”
4. In the popup screen provide a technical name for the SPO.
Use the following naming convention “SPO_01”. Provide an appropriate description “Semantically Partitioned Infocube”. For the Template option us the technical name of the InfoCube that was
converted to the In-memory Optimized InfoCube in exercise 2 [CUBE_01]. Under the “InfoProvider Type” select “Semantically partitioned”.
Click to create the object.
On the popup screen enter “0CALYEAR” and hit enter.
Hit continue at the bottom of the screen.
6. From the second pane click “Maintain Partitions”
7. In the popup screen select and transfer “0CALYEAR” from the left hand side to the right hand side.
Then click ok at the bottom of the screen.
8. In the new pane create partitions to accommodate the previous year, current year and next year. To create new partitions
click .
9. Add appropriate years to the “From” column as shown here in the screenshot on the right hand side.
10. Click “Save” at the top of the screen.
11. Next from the second pane click “Start Activation”. This will create the necessary number of part providers of type InfoCube.
12. You should receive a confirmation popup screen indicating the necessary part providers were created.
Click to “continue”.
13. Now under the section “Further Options” the option “Create Transformation” should be enabled. Click “Create Transformation” to create transformations between these part providers and the source.
As an example let’s use the InfoCube created in
exercise 2 as the source for these part providers.
Note:
In the section “Target of the Transformation” the Object Type “InfoSource”
is selected. This is a dynamically generated InfoSource which is used to connect the source and these part providers.
Click to continue.
14. A generic transformation is created.
Note:
A customer would modify this transformation as necessary to include any business logic.
Click to activate this transformation.
Accept any warnings that you receive.
15. Once the transformation is activated successfully the next option “Create Data Transfer Process" is enabled. Click this to create a Data Transfer Process (DTP) to load each of the part providers.
16. Under the section “DTP Template” create a new template which allows to load from an InfoCube (as a source) to a InfoCube (as a target)
Note:
The reason we are not using a standard template is because it is used to load data from a DataSource. In this case we have chosen to load from an InfoCube. Hence the need to build a new DTP
template.
17. On the popup screen enter an appropriate description. Enter “CUBE_2_CUBE” to create a unique template. Hit “Enter” to continue. 18. In the popup screen make
sure “InfoCube” is selected as an option for the “Data Source”.
Accept the default values for the rest of the sections. Click “Save” to continue.
19. Next task is to create a DTP for each of the part provider using the template DTP that we just created.
For this first make sure the “InfoCube” template is selected.
Second select all the part providers that are created under this SPO.
Third select the source InfoCube.
Lastly click “Assign” to create DTP for each part provider.
20. This should assign a DTP to each of the part providers. Select the inactive DTP’s and click “Generate”.
21. All the DTP’s should now be assigned and active.
22. Click “Create Process Chain” on the “Object maintenance” pane. This will create a process chain and assign all the DTP’s in there.
23. Select all the DTP’s and click on “Add” in the right hand pane to add them to the process chain that will be created.
24. These DTP’s should now appear in the right hand pane.
Note: Using a combination of ‘Path’ & ‘Sequence’ columnsyou can change the order in which the DTP’s are executed (in series or parallel).
Click “Save” at the top to assign the DTP’s to the process chain.
25. The DTP’s should now be assigned to the process chain.
26. Click “Generate”. . This should take you to a new screen.
In this screen click “Change Selection”.
27. In the new popup screen click “Immediate” and hit
“Save”.
Click on the “Maintain Start Process” screen.
Click the “Back” button, which should take you back to SPO
28. All the components of the object maintenance should now be active.
29. Now to go transaction “RSPC” and look up the process chain that was generated.
You should be able to locate it in the “Generated By Semantically
partitioned Object” folder in the “Unassigned Nodes” folder
You will notice that as expected the DTP’s will now run in parallel
7
Using Mixed Scenarios with SAP NetWeaver BW on SAP HANA
In the following scenarios we will combine data from SAP NetWeaver BW (Budget Information) with data stored in a HANA table (Actuals).
The actuals are stored in a HANA table which is updated by credit card data in real-time. Based on this Expense table the session will work with two HANA calculation views:
CalcView 1 (Detailed) : expenses per employee including employee ID
CalcView 2 (Aggregated): expenses per cost center including an employee counter
Beside the real-time data we also have normal staged BW data where the cost budget for each cost center is been planned:
7.1 Scenario 1 – Using a Composite Provider to join Transient Provider with a Data Store Object
Explanation Screenshot
Step:
Create a Transient
Provider to publish the
HANA model to BW
1. Login to the system Launch the SAPLogon pad
on the desktop
and choose the BW system. Please use the following user to logon
DEMO
Note:
If you want to go directly to the query built on the composite provider (which uses the Transient provider & DSO), use query - Z361_CP1_MST_1 (Actuals & Budgets using Transient provider) in Step 28
2. Go to transaction “RSDD_HM_PUBLISH”
Note:
This is the new transaction to maintain Transient Provider for BW on HANA to publish HANA models to BW.
You can either use the transaction code or browse via your assigned user menu to the transaction “RSDD_HM_PUBLISH - Publish SAP HANA Model” 3. Under package select
“eim361”.
Note: Use the F4 help to look up the value rather than type it in, as the values are case sensitive. For SAP “HANA
Information Model” select “STUDENT00_1”
Note:
This is the detailed analytical view where the expenses for each employee are shown. 4. Click “Create” -
Accept the default name for the new Analytic Index and hit enter
5. In the new screen the details of the Analytic Index are displayed.
An analytical index is a data container whose data is stored in HANA and is used to generate a Transient Provider in BW.
6. In the “Properties” tab change the Description to “STUDENT00_1 - Actual Expenses in Detail”
7. Select the InfoArea “TPCP”
(Transient + Composite Provider)
8. Navigate to the “Chars.” and “Key Figs” tabs to notice the fields that are imported from HANA Analytical view.
Note:
No changes needed here, accept the defaults .
9. Click to “save” the Transient Provider
Step:
Create a Composite
Provider to join DataStore
Object and Transient
Provider
1. Go to transaction
“RSLIMOBW” to create a Composite Provider
2. Provide a technical name for the Composite Provider. Use the following naming convention “Z361C00_1”
Note:
The maximum length is 10 characters.
Click Enter or hit Create
3. This is a new environment to build join models via the Composite Provider. The box shown with the name of your Composite Provider indicates the output area. Meaning any fields on which you want to report on is added to this.
4. Expand the left hand pane to display all the available InfoProvider to have a better overview. Under the “TPCP – Transient + Composite Provider” info-area you will see 2 providers as shown.
5. Under the InfoArea “TPCP” select your Transient Provider “STUDENT00_1” created in the prior steps.
Drag the Transient Provider to the right hand pane (in the white space), which is the modeling area.
6. A popup screen to select the join type should appear. This join type is the relation of the Transient Provider to the Output / further object to join.
Change Binding Type to “Union” and click confirm
.
Note: Even though Union is selected here, this is just adding the selected objects as the left part of the join condition.
7. Now the Transient Provider should be available in the modeling area.
Note: Ensure the “Join Type” “union” shows up in the title of the
Transient Provider.
8. From the left hand pane now drag and drop “Cost Center Allocation – Budget”DataStore Object – “ZBDGT”to the modeling area like you did for the Transient Provider.
9. Make sure the Binding Type is set to “Join”.
10. Use the default value for the Alias Name.
in which type (Inner, Outer, Union). The default is “Inner Join”.
12. Now both objects are available for modeling a Composite Provider. In the modeling area you see now all necessary objects:
1. All fields of your Transient Provider 2. Output / target list to define the structure or result of your Composite Provider 3. All InfoObjects of the DataStore Object
Note: Notice that the title of the second objected added has ‘Inner Join’. 13. Drag and drop the field
“COST_CENTER” of the Transient Provider to the Output in the middle.
Note: Also make sure you drag from the DSO to the output and not the other way around.
In addition also add the following fields to the output: EMPLOYEE EXPENSE_TYPE CURRENCY CALMONTH AMOUNT
The output should now have all the fields mentioned above from the Transient Provider in the output.
14. Map the fields of the “ZBDGT DSO” to the Output by drag and drop.
Note: Also make sure you drag from the DSO to the output and not the other way around.
Start byconnecting “Cost Center” from the DSO to the output field
COST_CENTER. This will define a join condition on these two fields.
15. Second join the “Calendar year/month” field of the DSO to output field “CALMONTH”.
With this the necessary fields for join condition are defined correctly.
16. Now add “Currency Key” and “Company code” to the output.
Note: Make sure you add “Currency Key” to the output without a join. Basically dragging them to the bottom of the output list. As this will result in
querying only records where common currencies exist.
Note: If the currency and unit fields are added
17. Finally add key figure “Amount” of the DataStore Object to the output. (Do not join the two Amount fields, since we need both of them as separate fields).
Note:
The system automatically recognizes that “Currency Key” is the corresponding currency for the Key Figure and assigned it by itself. 18. Change the properties of
the “Output” fields. Use a right-click and open the context menu on the “Amount” field (of TransientProvider) and, select the menu Change Property -> Change.
This key figure coming from TransientProvider is showing the actualvalue hence change the name and long description to
“Actuals”
Since there is no currency key assigned so far, please select “CURRENCY”.
19. Do the same for the other “Amount” field from the DSO which is Budget values. Change the description to Budget
20. All join types and output field are now assigned. You screen should like this.
21. Change the Description of your CompositeProvider to “Actuals & Budget” & under Info-area select “TPCP”
Save and activate
Note:
The Name is generated automatically with syntax
@3Z361C00_1
22. After activation make sure you receive a success message at the bottom of the screen.
23. Click (Display Data).
24. Select “Cost Center” & “CALMONTH” as characteristics and “Actuals” & “Budget” as "KeyFigures for output.
Step:
Create Query on top
of Composite Provider
1. Launch the BEx Query Designer tool from the menu Start > Programs > Business Explorer
Logon to the BW System “NW 7.4 SP5 Developer Edition” with the given user id.
2. Create a new BEx query based on your Composite Provider “Z361C00_1” 3. Search for technical name
“@3Z361C00_1” and create a new query
4. Select the following characteristics and key figures and drag and drop
them correspondingly to the Columns and Rows like shown here: Free Characteristics CURRENCY Currency Company Code CALMONTH EXPENSE_TYPE Rows COST_CENTER EMPLOYEE Columns Actuals Budget
5. Save the query and name it “Z361_CP1_00_1”
Description: “Actuals & Budget per Employee”
6. Check the results by executing the query in transaction “RSRT”and insert your Query “Z361_CP1_00_1”
Change “Query Display”to “HTML”and click on “Execute”
You should now see a similar out as shown here.
7.2 Scenario 2 – Create a Virtual Provider based on HANA Model with an aggregated view
Explanation Screenshot
Step: Create VirtualProvider to publish the HANA model to BW
1. Call transaction “RSA1” and create a Virtual Provider. Use a right-click and open the context menu
on InfoArea “TPCP ( Transient + Composite Provider)”and selectthe menu“Create Virtua lProvider”
Note:
If you want to go directly to the query built on the composite provider (which uses the Virtual provider
& DSO), use query - Z361_CP2_MST_1 ( Actuals & Budgets using Virtual provider ) in Step 35
2. Enter “Z361V00”as thetechnical name for the VirtualProvider.
Enter “Costs per Cost Center” as thedescription. Under “InfoProvider Type”
Note:
This is a new option for BW on HANA systems, which allows users to pick a HANA view.
Select the corresponding radio button.
Press “Details”to specify the details to our HANA view.
3. Select under “Package” the value “eim361”.
Select under “HANA Information Model” the HANA view :
“STUDENT00_2”
Confirm your selection.
Note: This is the only chance to select the view to create the provider, once selected it cannot be change.
4. Click “Create” to create the Virtual provider.
5. Under the InfoCube maintenance screen add the following InfoObjects via direct Input to the
corresponding dimension: Use a right mouse click on “Dimension1” and select the menu option
“InfoObject Direct Input” and enter the following InfoObjects in the list:
ZCOSTCTR ZEMPLOYEE ZEXPND_TY Use a right mouse click on the Time dimension and select the menu option “InfoObject Direct Input” and enter the following InfoObject in the list:
0CALMONTH
Use a right mouse click on the “KeyFigures”folder and select the menu option “InfoObject Direct Input” and enter the following InfoObjects in the list:
ZAMT
ZCOUNTER
6. Finally the following InfoObjects should be assigned to your VirtualProvider as Characteristics and Key Figures.
“Provider-Specific InfoObject Properties”.
8. For each BW field under the column “Attribute Name (HANA)” select via input help the corresponding attribute view in HANA and assign them: 0CALMONTH – CALMONTH 0CURRENCY – CURRENCY ZCOSTCTR – COST_CENTER ZEMPLOYEE – EMPLOYEE ZEXPND_TY – EXPENSE_TYPE
Note: Make sure you use the value help to select the right fields rather than type it in. As mentioned earlier the field names in BW need not match field names in HANA.
9. Do the same now for the KeyFigures.
Maintain field mapping of the HANA Model to the BW key figures.
Use a right-click to open the context menu of folder Key Figures and select the menu option “Provider-Specific InfoObject Properties”.
For each BW field under the column “Attribute Name (HANA)” select via input help the corresponding attribute view in HANA and assign them :
ZAMT – AMOUNT
ZCOUNTER
10. “Activate” your Virtual Provider.
Accept the warnings and activate the Virtual Provider.
11. Use a right-click and open the context menu for your InfoProvider and select “Display Data” or call transaction “LISTCUBE” and select all InfoObjects to check if the direct access is working.
Note:
A VirtualProvider is a direct access to the source system. In the shown scenario we are accessing during the selection on our VirtualProvider a HANA View.
Step: Create a Composite Provider based on a Virtual Provider and a Data Store Object
1. Go to transaction
RSLIMOBW to create your second CompositeProvider with name:
“Z361C00_2”
2. Close a few panes to ensure the right InfoProvider tree is displayed and you have enough screen space to model the composite provider correctly.
Note: Ensure that you are left with a pane that says ‘Analytical Index Selection’ for the InfoProvider tree. 3. From the left hand pane
locate the virtual provider “Z361V00” and drag & drop it to the modeling area. 4. Select as Binding Type the
value “Union”and confirm
5. Drag and drop the
DataStore Object “ZBDGT” to the modeling area. Select as Binding Type the value “Join” and leave the default Alias Name. Confirm your selection 6. Drag and drop all the fields
of the Virtual Provider (Left object) to the “Output” like shown.
7. Map the InfoObjects of the DataStore Objects (right objects) to the “Output”. Join fields “Cost Center” from both the objects by dragging the field from the right side on top of the field present in the output. Similarly drag and drop “Calendar year/month” from right on top of the “Calendar Year/Month” field in the output. Add “Currency key” and “Amount” as separate fields by dragging them to the bottom of the list in the output.
Note: Adding fields to the bottom of the list will ensure there is no join on fields.
8. Change the display properties of the output fields.
Rename the amount of Virtual Provider as “Actuals”
Rename the amount of DataStore Object as “Budget”
Rename field “Counter” to “No_Emp” with description “No. Employees”.
To rename a field use right mice click on the field in the output pane and select “Change” under “Change Property” menu.
In the popup screen under name and description provide the appropriate values.
9. Change the description “Actuals & Budget with Employee Count” and under Info-area select “TPCP”.
10. Save and “activate” your CompositeProvider
Note: The name is generated automatically with syntax the
11. To display Data click . In the next screen click “Fld Select for Output” and in the following screen select the check box against fields Cost Center, Budget, Actual and Counter fields and execute at the top. Click execute in the next screen to display data.
Note:
Counter is now showing the counted result of all
employee values
aggregated by Cost Center. The calculation is
happening in the HANA layer and BW is receiving the calculated aggregated value without any
transparency on how this aggregation is happening.
Step: Create a BEx Query based on your second Composite Provider and leverage BW master data
1. Launch the BEx Query Designer from the menu
Start > Programs > Business Explorer and create a new Query based on your Composite Provider “Z361C00_2”.
Choose the menu “Query
New”.
Find your Composite Provider with technical name “@3Z361C00_2” and create a new query.
2. Assign the characteristics and key figures to the corresponding areas. Free Characteristics Calendar Year/Month Rows Cost Center Key Figures Actual Amount Budget Amount Counter
3. Select the InfoObject “Cost Center” and choose the properties tab “Hierarchy”
Note:
Since both VirtualProvider and DataStore Object are using BW InfoObjects you can now leverage BW master data.
4. Assign the Cost Center Hierarchy to the InfoObject
Note:
Full BW master data
features with VirtualProvider are possible, example Nav. Attributes as well
The property window should now look like this.
5. Save your query with the name
“Z361_CP2_00_2” – “Actuals & Budget per Cost Center (HANA Counter)”
6. Go to transaction “RSRT” and validate your result by executing the result
Note:
7.3 Scenario 3 – Create a BEx Query and leverage the counting functions of the OLAP Engine
Explanation Screenshot
Step: Create a BEx Query including an employee counter parsed by the OLAP engine to compare the two counting options (BW and HANA)
1. Create new BEx query based on your first Composite Provider. Search for your CompositeProvider “@3Z361C00_1”
Note:
If you want to go directly to the query built on the composite provider (which uses the Transient Provider & DSO), use query - Z361_CP1_MST_2 (Actuals & Budgets using BW OLAP for Employee counter) in Step 10
2. Assign the InfoObjects to the corresponding query area like shown in the screen shot on the right hand side.
3. Create a newCalculated Key Figure for counting the employees per Cost Center. Use a right mouse click on the element Key Figures in the left hand InfoProvider pane and choose “New Calculated Key Figure”
4. A new calculated Key Figure is created and the “Properties” pane will appear.
5. Enter the following description and technical name under tab “General”: Description: “Employee Counter”
Technical name: “Z361_CKF_00_1” Click edit and enter “1” as the value.
6. Next go to the
“Aggregation” tab and choose:
Exception Aggregation: “Counter for all Detailed Values”
Ref. Characteristics: “Employee”
Select check box “Calculation After Aggregation”. Confirm the values by clicking “OK”.
1. Drag and drop your calculated key figure “Employee Counter” to the columns as well and save your query.
Click on the “Save All” button at the top to save both the calculated
key-figure and the query.
7. On the popup for “Save your calculated key-figure” provide a technical name and description and click OK
Description: “Employee Counter”
Technical Name:
“Z361_CKF_00”.
8. Save your query with the name “Z361_CP1_00_3” and description “Actuals & Budget per Employee (BW Counter)”
9. Check and validate your result via transaction “RSRT”
10. Compare the different implementations.
Open a second screen for transaction “RSRT” and execute Query
“
Z361_CP2_00_2” to compare the results. By executing both queries you’ll probably recognize that the overall result ofQuery result - Z361_CP1_00_3
additional employees coming from /or where are they excluded?
Drill down in query to get further details in both queries: Filter on CostCenter “C01” and “D01” Drill down by “Employee” Note:
The Drill down shows you that there are employees which are assigned two times to a cost center. See employee “80018” who is assigned to “D01” and “C01”.
The difference is now that BW exceptional aggregation is counting the distinct employees and calculating the sum line accordingly, which is the right way to count number of employees.
So, when you have a key figure calculated in HANA and combining that with BW features like Hierarchy aggregation, we have to make sure that we aren’t mixing up different types of aggregations. In this case the solution would be to suppress the summation line because the aggregation for itself happening in HANA.
Drill down - Z361_CP1_00_3
Drill down - Z361_CP2_00_2
7.4 Scenario 4 – Reporting on a Transient Provider using BI Authorizations
Explanation Screenshot
Step: Create a Transient Provider leveraging BW Authorizations
In this section we will create BI Analysis authoriztaion and necessary role to query restricted amount of data.
1. Go to transaction “RSD1”
And enter “ZCC_AUTH” in the InfoObject field
Click the create button or click the hotkey F7 If this characteristics already exists click ‘Maintain’ and go to step 4
2. In the popup screen enter description “Cost Center – Auth”
Click “Continue” or hit enter.
3. In the next screen under the general tab
select “CHAR” for Data Type
enter “10” for Length.
4. In the second tab “Business Explorer” select
“AuthorizationRelevant” check box.
5. Click “Activate” or hotkey Ctrl+F3 .
This should activate this info-object successfully.
6. Similarly change the following info-objects to be marked as authorization relevant
0TCAACTVT - Activity in Analysis Authorizations
0TCAACTVT - Activity in Analysis Authorizations 0TCAVALID - Validity of an Authorization
0TCAVALID - Validity of an Authorization 0TCAIPROV - Authorizations for InfoProvider 7. Go to transaction RSECADMIN
Click “Ind. Maint.” Button
8. Enter “ZCC_AUTH” in the field “Authorization:” Click “Create”.
9. In the next screen for short description enter “CC Authorization”
10. In the bottom half of the screen, click “Insert Row”
11. Double click on “ZCC_AUTH” to enter values that you want to restrict on.
Click on insert row
12. For the “Including /
Excluding” column, use the default value “Include”.
13. For “Operator” choose the value help and select “BT”
14. For the “From” field enter value “E01” & for “To” field enter “E99”
15. Click Save button at the very top.
16. Click the “Back” button . This should take you back to the main analysis authorization screen.
17. Click the button to insert special
characteristics. This should add the following info-objects to the list (0TCAACTVT, 0TCAIPROV, 0TCAVALID) with necessary authorization as show above. 18. Click “Activate” at the top. This will successfully create a new authorization object. Ensure the status of the object is “Active”
19. Click the “Back” button . This should take you back to the authorization object maintenance screen.
20. Click the “Back” button . This should take you back to the Analysis
Authorization management screen.
Click the “User” tab.
21. Click “Role Maintenance” button.
22. Enter “DEMO” in the Role field
23. In the popup screen type “DEMO_AUTH”
Click Copy All
24. Now click the change button to modify the
“DEMO_AUTH” role.
25. Under the “Authorizations” tab, click “Change
28. Expand this entry all the way through and click on
29. In the popup screen replace the value ‘*’ with value “ZCC_AUTH”.
30. The entry should now look like this.
31. Click the Save button at the very top.
32. Accept the default values for the popup screen.
33. Click the Generate button at the top.
34. Click Generate on the popup screen.
35. Click the back button . This should take you back to Role Maintenance screen.
36. Under the “User” tab ensure user “DEMO” is in the list. Click “User comparison” button.
37. On the popup screen click “Complete comparison”
38. Once you receive a success message, close the popup screen.
39. Ensure now that the Authorizations & User tabs have a green traffic light.
40. Now click the ‘Back’ button. This should take you back to “Role Management” screen. Type DEMO for role and click the change button
41. Under the “User” tab highlight the row for the user DEMO and click the
42. Click the Save button at the top.
43. Click the “User
comparison” button and then “Complete
Comparison” on the popup screen. Ensure you receive a success message.
44. Now click the “Back” button twice. This should take you back to the “Analysis Authorization management” screen.
In this section we will change the existing transient provider.
1. Change your existing TransientProvider Go to transaction
“RSDD_HM_PUBLISH”and select the Catalog “eim361” and the HANA Information Model “STUDENT00_1”
Note:
HANA views can only published once via
TransientProvider, therefore we have to change the existing one.
2. Go to tab “Chars.” and assign InfoObject “ZCC_AUTH” to the field “COST_CENTER”under the Ref. InfoObject column. Click “Save”.
Note:
3. Make sure that the
authorization flag is turned on for Transient Provider. 4. Create a new BEx query
based on TransientProvider “@3STUDENT00_1”.
5. Go to the BEx query designer and search for your TransientProvider “@3STUDENT00_1”.
6. Turn the technical names on.
Note: The fields of the TransientProvider are offered as a
“Characteristic Catalog” which is the field’s definition maintained in
7. Select all the objects offered by your TransientProvider and distribute them into the corresponding query areas.
Note:
8. There is no integration into BW master data, beside the reference InfoObject Cost Center.
9. Create a new Authorization
variable.
Use a right mouse click on the folder “Characteristic Value Variable” under COST_CENTER and select the menu option “New Variable”.
In the properties pane, provide a technical name and description for the variable.
Technical name: “ZCC_AUTH_VAR” Description: “Cost Center Auth Variable”.
For Processing Type select “Authorization” from the drop down.
Click the “Details” tab in the properties pane. Under Basic Settings for Variable Represents select
“Selection option” from the drop down box.
Click “Save” on the properties pane.
10. Select the Authorization Variable for Cost Center and add it to the
“Characteristics Restrictions”. This will utilize analysis authorization to populate appropriate values based on the roles assigned to the user during query
execution. Expand field
“COST_CENTER” in your characteristic catalog and select the characteristic value variable
“ZCC_AUTH_VAR”.
Drag and drop it to the filter/ characteristic restriction.
Note:
Since Cost Center is modeled and referencing to the InfoObject master data we also have Display Attributes available. 11. Save your query with
technical name “Z361_TP1_00_4”and descriptions “Actuals with Authorizations”
12. Go to transaction “RSRT” and execute query “Z361_TP1_00_4” with Query Display“HTML”
13. You will see the variable prepopulated with values to which the user has access to.
15. Go to transaction “SU01” – User maintenance and enter “DEMO”
16. Click the change button to modify the “DEMO” user and replace the “DEMO_AUTH” role with the standard “DEMO” role. 17. Click the remove button
to remove the “DEMO_AUTH” role. 18. After replacement the user
roles should look like this.
19. Click the save button at the top to save the
changes.
Now that the standard role has been assigned. Run the query again and notice that you have full access and you can see much more data.
20. Check and validate your result via “RSRT”
Note:
sufficient authorizations you’ll see the following results.
7.5 Scenario 5 – Create / Change a Composite Provider Join Type You can now choose between two optional scenarios.
Scenario 5a - Create a new CompositeProvider with new join type
Scenario 5b- Change your existing Composite Provider with the new join type
Explanation Screenshot
5a. Step: Create a new Composite Provider with new join type
Note:
If you want to go directly to the composite provider (which uses the Transient Provider & DSO with left outer join), use provider - Z361C_MST3 (Actual & Budget (Left Outer Join)) in Step 6
1. Go to transaction “RSLIMOBW” to create your second CompositeProvider with name: .
Use the technical name “Z361C00_3”
2. Add the Transient Provider “STUDENT00_1” and the DSO object “ZBDGT” to the right hand modeling pane. Follow the same steps as Scenario 1 where you created a Composite Provider.
3. Now add the following fields from the Transient Provider to the output: Cost Center Employee Expense Type Currency Calmonth Amount
Add the following fields from the DSO object to the output : Calendar Year/Month Currency key Cost Center Amount
Note:
As indicated in the screen (and as mentioned earlier) only join on Cost Center & Calendar Month only. You can follow the same steps mentioned in Scenario 1 of creating a composite provider.
4. Change the connection type to “Left Outer Join”. For this use a right mouse click on the title of the DSO object and select the menu option ‘Left Outer Join’ from ‘Connect as….
5. Change the description of the Composite Provider to “Actuals & Budget LEFT OUTER JOIN”
6. Save and activate . Verify your result.
7. What is the impact of the join type?
Explanation Screenshot
5b. Step: Change your existing Composite Provider
Note:
If you want to go directly to the query on composite provider (which uses the Transient Provider & DSO with left outer join), use query - Z361_CP3_MST_1 (Actuals & Budgets (Left Outer Join)) in Step 4
1. Start transaction “RSA1”.
2. In the InfoArea “TPCP” locate the Composite Provider “Z361C00_1”
3. Use a right-click on the InfoProvider and select the menu “Change”.
4. Use a right mouse click on the title of the DSO object and select “Left Outer Join” from the menu “Connect as…”
5. “Save” and “activate” .
6. Start transaction “RSRT” 7. Run query
“Z361_CP1_00_1” to verify the result
8. What is the impact of the changed join type?
7.6 Scenario 6 – Using a Composite Provider to join with Master data to display Navigational Attributes
Explanation Screenshot
Step: Create a new Composite Provider with Master Data join
1. Create a new Composite Provider “Z361C00_4” Go to transaction “RSA1”. Select the InfoArea “TPCP”. Use a right click and select the menu to create a new Composite Provider or use transaction
“RSLIMOBW” to create a new Composite Provider
2. Add your Transient Provider “STUDENT00_1” as
“Union” and master data object “ZCOSTCTR” as binding type “Join”
Add the following fields from the Transient Provider:
Cost center Employee Calmonth
3. Map the field “Cost Center” from the master data to the Output field
COST_CENTER. Notice that now the navigational attributes are available to be added to the output.
Join Controlling area and Business area to the output. 4. Change the description to:
“Actuals with CC attributes“
Save and activate
5. Display data to validate to ensure you can view the navigational attributes.
Note:
Since navigational attributes are not supported for TransientProvider this approach helps you to overcome this gap.
8
Using BW Workspaces with SAP NetWeaver BW on SAP HANA
8.1 Scenario OverviewA BW Workspace is a dedicated area in a BW system where new models can be created based on central BW and local data (e.g. flat files). Workspaces can be maintained and controlled by IT and used by local departments to react quickly to new and changing requirements. Workspaces can bridge the gap between central governance requirements and local flexibility needs.
There is no need to copy central data of the SAP NetWeaver BW to the BW Workspace. The administrator simply assigns the relevant InfoProviders in a BW Workspace. Local data can be uploaded in the BW Workspace Designer by the key user in the line of business and can then be merged in new data models.
Local Provider BW central, BWA-indexed InfoProvider BW central InfoProvider, assigned to Workspace CompositeProvider
8.2 Scenario 1 – Check and Validate the BW Workspace definition
Explanation Screenshot
Step:
Validate the BW
workspace that is already
created
1. Login to session system Open the SAPLogon pad
on the desktop
and choose the BW system. Please use the following user to logon
DEMO
2. Go to transaction “RSWSP”.
Enter DEMO01 and hit display.
3. The setting tab is displayed by default. Below is a brief description of the fields in this tab.
Field
Tab strip ‘Settings’ Remark 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 PartProviders 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 (explanation will follow later in the ‘Model CompositeProvider’
from there should any BWA indexes be lost/corrupt.
4. The second tab is “Central provider”.
This includeS any multiprovider and its underlying part providers that can be used in building a “Composite Provider”.
5. The next tab is ‘Local Providers’.
This contains any providers that are
generated once users start to upload data to the workspace.
6. The next tab is
“CompositeProvider”. This has any Composite provider created as a result of join activity in the workspace.
7. Finally the “Users” tab. This has the list of users who have different kinds of access to this workspace.
8.3 Scenario 2 – Upload Customer ABC rating file
Explanation Screenshot
1. Launch the ‘NetWeaver Business Client’ application.
You can locate it in the start menu or search for it in the windows start menu.
2. Connect to the BW system using and the ID and password provided.
3. Your initial screen should look something like this.
4. Click “Workspace
Designer” which will display additional options under it.
6. This will launch a new tab with the workspace which you have access to.
7. If a default workspace has not been setup you will receive an error message, please proceed to next step.
If you do not receive any error message, continue to step 9.
8. If you receive an error message, use the following steps to associate your ID with the correct workspace. If you do not receive any error message, continue to step 6.
Close the tab and click on ‘Workspace Tools’
In the next screen from the list select the radio button next to your workspace and click ‘Save’ at the top. Users can also use this technique to change the workspace they are working on from various workspaces
they have access to. Once you have saved the changes, close the tab. Launch “My Workspace” again.
9. Click on the tab “Local Providers” to upload the “Customer Rating” file.
10. Click ‘Create’.
11. In the next screen from the drop down box select “File”. Click ‘Continue’ to proceed. Accept any popup message you get.
Note:
If you receive a security warning, click Yes on the popup.
Any additional popup requesting to install Add-ons click on ‘Install’. After the installation is complete, close the window.
12. Under file name locate the “Customer ABC Rating” using the “Browse” button and then click “Transfer File”.
That should upload the data file.
Note:
The file for this exercise is located in “DATA_FILES” directory on the desktop. If the file is not present, use the following screen shot to create a text file and name it
“Customer_ABC_Rating.csv”
13. The resulting screen should look like this
14. Next provide the following properties regarding the file. Header = 1
First Data Row = 2
Separator (CSV) = ;
Field Delimiter Character (CSV) = “ Decimal Display (CSV): Period Date Display (CSV): MM-DD-YYYY
15. Also accept the defaults for the provider properties. Click Next.
16. Click ‘Next’ at the top of the screen
17. Accept the default setting and click “Next”.
18. For the moment do not select the check box options and click “Upload and Activate Provider”.
19. During upload you will receive a progress bar indicating the status of the upload.
20. Confirm that you receive a success message indicating the data has been loaded successfully.
21. Click on ‘Display Data’, this should bring up a popup screen indicating the data was uploaded successfully. After validation close the popup window.
Step: Create Composite Provider combining the ‘Local provider’ just created and the ‘Central Provider’
22. Next click ‘Create Composite Provider’
or
close this tab and launch “My Workspace” again and click “Create” under the tab “Composite Provider”. 23. Click “Continue” for the first
step choosing the option “No proposal”.
24. In the next step under “General Data” section provide a technical name and description for the composite provider. Technical name:
WS_CP00_1
Description:
Workspace 00 CP1
25. Under “Provider” section select the check box besides “Main Provider” and also
26. Click “Next” at the top to continue. In the next screen under the “Selected Providers” section click “Details of Links” button.
27. In the next screen click “Details” for Customer field.
Note:
If you receive a security warning, click Yes on the popup.
28. In the Popup screen select “Customer” and click ok.
29. Select the check box under column “Dedicated Field” for the row “ABC Rating” indicating it’s a dedicated field from ABC rating data. 30. Click “Apply” at the
top of the screen, this should take you back to the composite provider
modeling screen.
Click “Check” at the top of the screen to confirm the composite provider has no errors.
31. In the bottom section the “Tabular Overview” tab should now indicate that the two fields from the file “Customer_ABC_Rating” provider are part of the output.
32. You can also click the “Graphical View” tab to see the same as a picture.
33. Click “Next” at the top and accept the default values in the next screen.
34. Click ‘Next’ at the top. In this screen for type of query from the dropdown select “Standard” and accept the default values.
Note:
Make a note of the query technical name that is generated by the system. 35. Click “Next” at the top. 36. In the following screen click
“Display Data”.
37. The following popup screen will display the result of the join condition using
composite provider. Once validated click “Close”.
38. Click ‘Save and Activate’ at the top to confirm the changes.
39. Confirm that you receive a success message.
40. Go to transaction “RSRT” and execute the standard query created in the previous step.
Note:
Use the technical name of the query that was created earlier in step 34.
41. Add Customer and ABC Rating field to view the data.
8.4 Scenario 3 – Upload temporary Inventory file and join with Central Sales and Customer rating
Explanation Screenshot
1. Go back to your workspace home screen and click on “Local Provider” tab. 2. Click on “Create” to upload
a new file.
3. Click “Continue” in the next step as we will be uploading a new file.
4. In the next step under section “File” click
“Browse” to locate the file “Inventory_Data.csv” and click “Transfer File”.
Note:
The file for the exercise is located in ‘DATA_FILES’ directory on the desktop. If the data file is not present, create a file using the following screen shot.
5. Next accept the defaults under the “Property” section.
Click ‘Next’
at the
6. Accept the default for field type and description and click “Next”.
7. Click “Upload and Activate Provider” at the top of the screen without selecting any other options.
8.
