When users would like to see four measures on a dashboard based on their selection we could leverage Tableau parameters and containers to achieve it.

There are four measures; two are in percent format and rest are in integer formats.

Integer formats can be shown in a pie charts such that each dimension can divide itself into different pie and the entire pie chart can be the whole.

However this depiction of data does not appeal to audience when showing a Percent. Simple bar graphs would be apt to show the percent for different dimensions.

In the below scenario we have 4 measures that users wish to see. RORAC and NIM are percent. Acquisitions Amount and Units are Integers.

This is how the appearance of the dashboard should be.

 

Final view of the dashboard should be based off the selection:
  

 

Creating Sheets:

Create a Pie chart for Acquisitions amount and Total Units. Name the sheet as ‘Pie chart’

Using the parameter called Selection metric, trigger Acquisitions amount or total units field into the angle of pies.

 
 

The field named Z in the rows and column shelf is an empty field that enables us to hide the sheets.

This field would be a discrete dimension. (To change the properties a field right click on field name for options). 

 
 

Create a bar graph for NIM and RORAC. Name the sheet as ‘Bar Chart’

Using the parameter called Selection metric, trigger NIM or RORAC fields as the size of the bars.

 
 

Now we have 2 charts for 4 different metrics.

Based on the selected metric different charts should appear.

Creating calculated fields for hiding different sheets:

Create two calculated fields based on Selection metric parameter.

On for filtering the entire bar chart sheet and other for filtering entire pie chart sheet.
  

Drag the bar chart filter into filters pane of Bar chart sheet. Select at least and type ‘1’ as value.

 

Do the same for pie chart. Drag the pie chart filter into the Pie chart graph and so the same.

If the sheet disappears it is because the filter is working and the selection is set to a different parameter. 

Creating a Dashboard: 

• Open a new dashboard. Drag and drop the vertical container from the objects pane on the left bottom on to the dashboard. 

 

• Drag the Bar chart on to the dashboard. Make sure that the fit is set to entire view on the dashboard. This will help the worksheet occupy the entire space on the dashboard.

 

• Next Drop the Pie chart on to the dashboard. Make sure you drop the pie chart at the bottom of the bar chart. Make sure that the highlighted space appears on the bottom while dropping. 

  

• Change the selection from RORAC to Acquisitions amount or Units. This will give Pie chart.

 

• Also make sure the fit is set to Entire view as shown for bar graph.

By this we can give the user to access many graphs depending upon the type of measures they would like to see.

 

SAP BW WORKSPACE:

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.

Purpose:

This article will guide you through the implementation of BW workspaces, provide an overview of the different steps, people to involve in your organization, as well as step-by-step instructions on the back end configuration.

OVERVIEW:

BW Workspaces are dedicated areas in a BW system where new models can be created based on central BW and local data files (i.e. flat files).  The BW Workspace environment itself needs to be created, maintained, and controlled by IT.  Once IT setup the BW Workspace, then the business users can subsequently use the BW Workspace to combine data from BW with data in flat files in order to react quickly to new and changing requirements.

Table summarizes the responsibilities of IT and the business. BW Workspaces do not need to be transported.  Therefore, they bridge the gap between the need for central governance and flexibility.
 
Creating SAP BW Workspace:
The following should be considered when setting up BW Workspaces, Composite Providers,
and Queries:
Enter the technical code /NRSWSP in the SAP BW system it takes you to the Workspace.
The technical names of BW Workspaces should start with the same prefix as used for the associated InfoArea that owns the BW Workspace.  This will make it easier to identify which BW Workspace belongs to which InfoArea and Click on create.
  
Figure 1: Naming the BW Workspace
Leave the Workspace Prefix field blank when creating the BW Workspace (see Figure 2).  When it is set, all objects in the Workspace will start with that prefix, which will reduce the number of characters available for naming the objects.  This property cannot be changed after the BW Workspace has been saved.  It can only be changed at the time that the BW Workspace is being created.

1. As BW Workspaces always involve the Business perspective and the IT perspective, use the Contact 1 and Contact 2 fields respectively. This will allow transparency on who to contact with questions/issues about the BW Workspace or its contents.
2. CSV files uploaded to the BW Workspace should also start with the same prefix in order for the authorizations to be easily managed.
3. The Expiry Date for a BW Workspace should be set to expire at a fixed date after it has been created.

 

                                                        Figure 2: Prefix for Workspace Provider Field
Click on the Central Providers will take you to the below screen. Here Click on the tree symbol it displays the all the fields of the MultiProvider, you can make any changes if required to display the fields. 
          

Here we go through detailed steps for the configuration of BW Workspaces, the security setup and the creation of the BW Workspace itself.
In order to include ABAP WebDynpro application the following procedure needs to be followed in order to make sure that the Web Dynpro application for BW Workspaces works properly:
Additionally, the following ICF services for the BW Workspace Designer application (which is a Web Dynpro application) need to be enabled via transaction SICF:

• RSL_UI_MY_WORKSPACE
• RSL_UI_CREATE_COPR
• RSL_UI_CREATE_PROVIDER
• RSL_UI_CHANGE_WORKSPACE
• RSL_UI_CHANGE_QUERIES

The above ICF services can be found at the location /default_host/sap/bc/webdynpro/sap      

• To Activate the services Rigth click on the serive and click activate service.

   

• Create the authorization roles (see the next section)
• In the SICF handler list handler CL_WDR_MAIN_TASK is defined for the webdynpro node.
• Assign the users the appropriate roles
• Confirm the parameters in Internet Communication Manager (ICM) are set to
• Activate the service myssocntl via transaction code SICF.

 Activate the service myssocntl via transaction code SICF.

  

Log on the ABAP Webdynpro via url.

location /default_host/sap/bc/webdynpro/sap and give system,client,user and password to log in.
 
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.
Create Local Provider: 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. Enter the proposed type as Template Query and click on Continue.
 
In this step Click on ‘Choose File’ you browse the file and click transfer file.It automatically sets the path,Local provider Name and description and click Next.
 
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.

Confirmation: Click on the Upload and Activate Provider.
 
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’. 

Create Composite Provider:  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 Composite Provider. Furthermore, during the modeling process, you will generate two queries on top of the Composite Provider.
Start the Application Start the application ‘Create Composite Provider’ and skip the optional step of ‘using a query as template’.
 
Select Provider: Select Provider Select the MultiProvider as well as the Local Provider and choose a technical name and description. Click on next.
 
Model Composite Provider:  
The MultiProvider which has been assigned under ‘settings’ in the BW Workspace maintenance represents the UNION part of the Composite Provider. This means that all its fields have been brought over to the Composite Provider 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 Composite Provider model. For the Local Provider to be joined, binding type ‘Inner Join’ is proposed.
Here you can view the details of the Main Provider by clicking over Details of the Main Provider it shows fields of Main Provider and links.
 

If you click on the Generate provider it automatically generate the Data Choose the Generate Provider, settings and click on Ok.
 
Click on the Details of Links shows Links for the Provider and Join field Analysis.
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.
 
Click on the next. Here you can edit the name of the fields if needed then click on next.
 
This is the last screen to create a Standard and a Reference Query. Choose the Type of query is Standard. Queries once created here cannot be edited, they are transcended which mean they are automatically adjusted when the Composite Provider changes.  
Reference Query is a restricted and calculated key field defined in a globally or centre provider are also available. Admin can reuse it to create a new query.
 
 It creates the Query as follows. These queries can immediately be used for reporting after having activated the Composite Provider.
 
Check and Save:
The Composite Provider is ready for use now.
 

Swapping Sheets Based on Selection 

When users would like to see four measures on a dashboard based on their selection we could leverage Tableau parameters and containers to achieve it.

There are four measures; two are in percent format and rest are in integer formats.

Integer formats can be shown in a pie charts such that each dimension can divide itself into different pie and the entire pie chart can be the whole.

However this depiction of data does not appeal to audience when showing a Percent. Simple bar graphs would be apt to show the percent for different dimensions.

In the below scenario we have 4 measures that users wish to see. RORAC and NIM are percent. Acquisitions Amount and Units are Integers.

This is how the appearance of the dashboard should be.

 

Final view of the dashboard should be based off the selection:
  

 

Creating Sheets:

Create a Pie chart for Acquisitions amount and Total Units. Name the sheet as ‘Pie chart’

Using the parameter called Selection metric, trigger Acquisitions amount or total units field into the angle of pies.

 
 

The field named Z in the rows and column shelf is an empty field that enables us to hide the sheets.

This field would be a discrete dimension. (To change the properties a field right click on field name for options). 

 
 

Create a bar graph for NIM and RORAC. Name the sheet as ‘Bar Chart’

Using the parameter called Selection metric, trigger NIM or RORAC fields as the size of the bars.

 
 

Now we have 2 charts for 4 different metrics.

Based on the selected metric different charts should appear.

Creating calculated fields for hiding different sheets:

Create two calculated fields based on Selection metric parameter.

On for filtering the entire bar chart sheet and other for filtering entire pie chart sheet.
  

Drag the bar chart filter into filters pane of Bar chart sheet. Select at least and type ‘1’ as value.

 

Do the same for pie chart. Drag the pie chart filter into the Pie chart graph and so the same.

If the sheet disappears it is because the filter is working and the selection is set to a different parameter. 

Creating a Dashboard: 

• Open a new dashboard. Drag and drop the vertical container from the objects pane on the left bottom on to the dashboard. 

 

• Drag the Bar chart on to the dashboard. Make sure that the fit is set to entire view on the dashboard. This will help the worksheet occupy the entire space on the dashboard.

 

• Next Drop the Pie chart on to the dashboard. Make sure you drop the pie chart at the bottom of the bar chart. Make sure that the highlighted space appears on the bottom while dropping. 

  

• Change the selection from RORAC to Acquisitions amount or Units. This will give Pie chart.

 

• Also make sure the fit is set to Entire view as shown for bar graph.

By this we can give the user to access many graphs depending upon the type of measures they would like to see.

 

VP Product Management, SAP EDW (BW/HANA) June 2017

 

This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP’s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. 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. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or gross negligent.

History of SAP BW:

   

SAP BW/4HANA – Architecture

              

SAP BW/4HANA is…

• a new (innovation) code line
• not part of and does not depend on a NetWeaver delivery
• based the ABAP application server and SAP HANA
• running on premise or in the cloud
• not the legal successor of SAP BW powered by SAP HANA
• the “logical successor” of SAP BW powered by SAP HANA

SAP BW/4HANA Highligths

SAP BW/4HANA Roadmap – Delivered with SPO in Q3 2016
 

SAP BW/4HANA Roadmap:

SAP BW/4HANA Roadmap – Delivered with SP2 in Q4 2016
 

SAP BW/4HANA Roadmap – Delivered with SP4 in Q2 2016
 

SAP BW/4HANA Roadmap – Planned for in Q4 2017
 

SAP BW/4HANA Roadmap – Future Innovations
 

Paths to SAP BW/4HANA

• New installation
• System Conversion
• Land Transformation

Paths to SAP BW/4HANA:

Paths to Convert Your System:
 

• All BW customers can start NOW
• Customers on SAP BW powered by SAP HANA have a head-start
• Customers can convert at their own pace – benefiting gradually from HANA – optimizations

SAP BW/4HANA Starter Add – On:

The “SAP BW/4HANA Starter Add-on” (f.k.a. “SAP BW, Edition for SAP HANA”) is prerequisite for In-Place Conversions.

BW MODE:

• All restrictions temporarily disabled.

Compatibility Mode:

• Unsupported object types cannot be created.
• Existing scenarios can continue running as before.
• Unsupported objects can be changed when adding them to a white list.

B4H Mode:  

• No imports of unsupported Object types.
• White list is not relevant any more.

Ready-For Conversion:   

• System is ready for component upgrade.

Next Steps:

SAP BW/4HANA Transfer Toolbox – planned for Q2 2017
 

Migration to SAP BW/4HANA

Outlook – Conversion Support – In Place Conversion
 

 Migration to SAP BW/4HANA

Outlook – Conversion Support – Remote Conversion

  

Planned Roadmap for SAP BW/4HANA Transfer Toolbox:
  

SAP BW/4HANA & Analytics:
Postioning and Integration 

SAP BusinessObjects
 

SAP BW/4HANA & SAP S/4HANA: 

SAP S/4HANA Embedded Analytics + SAP BW on SAP HANA or SAP BW/4HANA

Comprehensive Operational + Historical Analytics and Planning Powered by SAP HANA

  

                          All analytics requirements fulfilled with one unified solution

               Data integration scenarios are possible in multiple hybrid system setups

Content implications for SAP S/4HANA (with SAP BW on HANA and SAP BW/4HANA)

• All extractors not blacklisted(2333141-SAP S/4HANA 1610:Restrication Note ) are enabled for SAP BW on HANA and SAP BW/4HANA*
• All custom developed objects for extraction have to be verified and adapted to the new SAP S/4HANA relevant structures.

 

  

The SAP BW Composite Provider is used to bring the data together from in-memory data targets/InfoProviders. This InfoProvider can leverage both union and join operations to combine.
 

Purpose of Composite provider:  one modeling InfoProvider (semantic layer) combining BW and HANA objects with either Join or Union.     

UNION and JOIN operations are executed in HANA and not the application server. BEx queries can be created on Composite Providers as on any other BW InfoProviders.
 

Modeling Scenario using Composite Provider:

With the new Composite provider it is possible to realize the dream of storing the same data only once at least for this scenario. The following case shows how we can model the same scenario using a composite provider and thus make use of the calculation capabilities of HANA DB.

In transaction RSLIMOBW, we create a Composite provider that uses the 3 Data store objects, Sales Transaction, Customer Master and Product Master as shown below.
 

How this works:

• The Sales transaction DSO is taken in the Composite Provider with Binding Type “Union”. By default there should be at least one Info provider of type Union in the Composite provider.
• The fields of Sales Transaction DSO are dragged into the Central Composite Provider.
• The Customer Master and the Product Master DSO are added to the Composite provider with the binding type “Join”.
• Master data fields required in the composite provider are dragged and dropped into the composite provider. (These are the fields for which look-ups were written in the original scenario).
• The fields Customer number and Calmonth are used as Join fields and a join condition is drawn between the Sales DSO and the Customer Master.
• Similarly Product number and Calmonth are joined from the Product DSO with the composite provider.
• In this way, the composite provider will contain all the records present in the Sales transaction DSO with the corresponding attributes filled based on the Calendar Month.
• The Joins and Unions are executed at the query execution time. UNION and JOIN operations are executed in HANA DB.
• Note that SID generation option should be checked in the DSO for it to be available as a data provider for Composite provider.

Benefits of Composite Provider over MuliteProvider:

• BW InfoProviders can be combined using JOIN operation allowing us to create new scenarios not possible or very expensive with standard techniques (Multiprovider, InfoSet)
• Composite providers can be modeled using the DSOs in the EDW layer itself.
• The time taken for performing look-ups to derive attributes is also saved during loading.
• Ability to combine BW InfoProviders and HANA tables/views via UNION or JOIN
• Faster and simpler data modeling – successor to MultiProvider and InfoSet
• Reduce database size: virtual modeling capabilities as opposed to data flows
• Flexibility : Further to what is shown above and as in the case with most of the real time systems, not just one DSO loads to a cube. In that case, a Multiprovider is created on top of these DSOs can also be used in the Composite provider to deliver the desired results
• Supports usage of inventory key figures and planning scenarios.

Creation of Composite provider.

Log on to the BW Modeling Perspective with your BW credentials and attach your HANA system using the context menu on your top project level folder, choosing the option Attach HANA system, without which you will not be able to include native SAP HANA models in your Composite Provider.

Navigate to InfoArea under BW Project → Context menu → New → Composite Provider.
 

Enter the Composite Provider name and description. Click Next.
 

Then  click on the Add sign, you will be prompted if you want to select an InfoProvider or HANA view. To perform a search, enter ‘?’ and you will see a list of available objects. Select any object that you want to add to the Composite Provider.

Similarly, add an InfoProvider to your Composite Provider. Next is to add the fields from Source to Target by dragging the fields. You can use Expand all to expand all the objects added. You can also apply a filter to search a particular field.” Note that at least one field should be drop on join condition”.

Composite Provider created by using JOIN.
 

Composite Provider created by using UNION.
 

Go to the output tab and you can see the mapping of added objects.
 

Next is to check and activate BW object.
 

To preview the data in HANA Studio, use the magnifying glass icon in the upper right corner → Show Preview.
 

You can also analyze the result in the Problems log of this perspective.
 

Open ODS views:
Open ODS views enable you to define BW data models for objects like database tables, database views or BW DataSources (for direct access). These data models allow flexible integration without the need to create InfoObjects.
       
Purpose of Open ODS view: Faster agile modeling capabilities when using external data sources.

ODS Views allow to consume external data sources in BW without staging, combine data sources with BW models and physically integrate (load) external data sources by creating DataSources.

Open ODS view allows data sources to be virtually consumed without the need for a separate BW persistence for the data. These data models can be located in a database schema (of the SAP HANA database in BW), which is not managed by BW. Alternatively, the models can be located in other databases, which can be connected to the SAP HANA database in BW using SAP HANA Smart Data Access.
Benefits of Open ODS View:

• Flexible and easy integration of external data models
• Agile modeling combining infoObjects and field based modeling
• Integrated modeling environment between HANA and BW
• Enhanced business flexibility by supporting “the logical EDW”
• Reduces data modeling efforts .

Creation of Open ODS View:
Open ODS views enable you to define BW data models for objects like database tables, database views or BW DataSources (for direct access). These data models allow flexible integration without the need to create InfoObjects.
Go to SAP HANA studio → BW Modeling Tools.
To create an Open ODS, right-click on your InfoArea and choose Open ODS view.
  

Provide the following details such as technical name of the DataSource, Descripation and select Semantics and Source type and click on finish.

Now click on the Facts and look into the details of the source. 

Next is to check and activate BW object.

You can also analyze the result in the Problems log of this perspective.
   

ABAP programmers create SQL DDL source and activate to create CDS views in SAP HANA Studio running on Eclipse known as Core Data Services view. SAP HANA database provides great performance boosts for transactional and analytics processes on ERP systems. CDS views, user defined functions, stored procedures are created on HANA database using SAP ADT tools including SAP HANA Studio. ABAP developers can not create CDS view or change DDL sources of SAP HANA repository objects using SE11 transaction.

What does DDL stands for?

In database terminology, DDL stands for Data Definition Language which differs from DML, Data Manipulation Language.

As you can guess, SQL DDL or SQL Data Definition Language commands enables developers and database administrators to manage metadata operations like creating database objects including tables, views, function, stored procedures, etc. Using an appropriate SQL DDL command database professionals can alter existing database objects or delete them ,too.

Backup or restore operations, and many other SQL commands related with database tasks rather then tasks with manipulating data are SQL DDL statements.

On the other hand, DDL commands are directly related with data itself. The transactions taking place on a database table, like inserting a new row, or updating data in a table, deleting data from table, MERGE commands are Data Manipulation Language commands, aka DML statements.

SQL Server developers use Transact-SQL, Oracle developers use PL/SQL for DDL and DML tasks.
Now with SAP HANA, ABAP programmers can create DDL objects like SQL Views, Stored Procedures, User-Defined Functions (skalar functions or table valued functions) on database level.
To create database objects on SAP HANA database, ABAP developers will use SQL DDL afterwards.

What does CDS stands for?

CDS stands for Core Data Services in SAP HANA database terminology.
CDS documents are design-time source code files showing the definition and SQL DDL source of the database objects SAP HANA developers want to create.
When an ABAP programmer creates a CDS document, a SQL DDL source file with .hdbdd file extension.

When the SAP HANA developer activates CDS file (Core Data Services) a corresponding runtime object (a database catalog object) is created in the current database schema.

Create CDS View in SAP HANA Studio

First of all, launch SAP HANA Studio

CDS views are different than database views
In SE80 Object Navigator SAP transaction, ABAP programmers can create database view or using SE11 tcode classic views can be edited in ABAP Workbench tool.
On the other hand, to create a DDL source like creating a CDS view, SAP HANA Studio is the required IDE for developers.

After SAP HANA Studio started, you can connect to target SAP system where you want to create the CDS view.
Add the ABAP Package into the Project Explorer window of the Eclipse integrated development environment.
I want to create a local ABAP dictionary object, so I’m going to add the new CDS view into my local package.

As you can see in below SAP Hana Studio ABAP perpective screenshot, I’ve already imported local package $TMP into the project.

Right click on the package. Follow context menu selections: New > Other ABAP Repository Object
 

Choose DDL Source under Dictionary objects node. Then click Next for following screen in the wizard. We will create a Data Definition  document using this selection.
 

Enter the view name and a description for your new DDL SQL view.
Click Next if you want to transfer this ABAP dictionary to an other system with a transport request.
 

As expected since I’m creating my first CDS view in local ABAP package, $TMP no change recording is enabled for package $TMP.
If I was creating an object to distribute to other SAP systems like productive systems, I will be choosing an existing transport request number or create a new transport request here.
Click Next.
 

Last screen in the wizard enables ABAP programmers to choose a template to create DDL SQL View easily. There are a few numbers of templates with short explanations and code samples. Then Click on finish.
 

After you select your SAP HANA SQL DDL source template, click Finish button.
In Eclipse on a new window the starting source codes for the DDL SQL view is displayed.
 

You see the DDL source is listed among local package objects under node:
$TMP > Dictionary > ABAP DDL Sources nodes.

Until we activate the DDL Source document After we activate ABAP DDL source, corresponding DDL SQL view will be shown under Views node.

Note: It is important to notice that the DDL Source name of the view definition is “ZODATA_DEMO_PARAMS”.
We define the DDL Source name right after “define view” statement.

On the other hand, the CDS view name which will be generated as an ABAP repository object is different.
ABAP programmers define the CDS View name visible on SE11 transaction is set at the first line of the template.
@AbapCatalog.sqlViewName is used to define the SAP CDS View name.

Please use different names for DDL Source name and CDS View name in the code.
Otherwise, during activation ABAP programmers will get an exception preventing the CDS view creation and which is not very informative.

Note: I have named the CDS view as “ZODATA_DEMO_PARAMS” which is different than the DDL Source name ”ZV_ODATA_DEMO_P”.

1. Add @AccessControl.authorizationCheck: #NOT_REQUIRED (line3)
2. Add the annotation @OData.publish: true above the DEFINE VIEW statement (line5).

After adding the annotation to CDS View save and activate the view.
 

Now the view has generated objects but the service “ZODATA_DEMO_PARAMS_CDS “ is not active.

To active the CDS view log on to the back end system and use the transaction code – /n/IWFND/MAINT_SERVICE.

Enter the System Alias here it is “LOCAL_PGM” and Technical Service Name ”ZODATA_DEMO_PARAMS_CDS” .

Then click on Get Services.
 

Select the Service display below and click on ‘Add Selected Services’.
 
 

In the next window, At Creation Information give the Package Assignment “$TMP” and click on continue.
 

Hence the Service “ZODATA_DEMO_PARAMS_CDS” as been created.
 

To display CDS view data, right click on CDS View name, and choose Open Data Preview in context menu.
 

Enter the P_CARRID:
 

Here is sample data for CDS view displayed in Data Preview tool in SAP HANA Studio.

Composite Providers are used to combine multiple InfoProviders using Join or Union operations. When you use SAP BW on HANA, one of the InfoProvider should use in-memory database and the data in composite providers can be used for reporting and analysis.

When you use SAP BW with non-HANA database, then BWA is a prerequisite to create Composite Providers. The primary advantage of Composite Providers is that you can create new complex business scenarios by converting an existing InfoProviders.

We can convert an existing Multi Provider to Composite Provider by following procedure.

Log on to SAP BW system and enter the Transaction code: SE38 it takes you to the below Screen.
 

In the  above Screen enter the Program name RSO_CONVERT_IPRO_TO_HCPR to convert the InfoProvider to Composite Provider and Click on Execute.

Enter the name of the Source InfoProvider and Target InfoProvider.Set the Execution Mode to Tranfer Infoprovider and quries,retain query names. Click on execute .
 

The following Screen displays all the logs of the Composite Provider.
 

 Now Active the Composite Provider /change the version M to A.
 

Hence the Composite Provider is created.
 

Click on the Display Data to preview.
 

Advantages:

• Support of planning functionalities for UNION cases
• Possibility to create a Composite Provider on top of Composite Providers (only UNION supported)
• Use of Open ODS views as Source Objects and allowing JOINS to be used
• Support of navigational attributes (familiar to the use of navigation attributes in MultiProviders)
• Support of input parameters when Open ODS views are used as source objects.

Requirement

Considering Fiori Launchpad as global point of entry for SAP applications, Users always want to see analytical content in the same place. To avoid users launching Business Objects documents via portal or BI Launchpad separately, this document outlines the process of integrating Fiori with Business Objects

Tools used

SAP Business Objects enterprise – BOBJ 4.1 SP4

Design studio – 1.6 SP02

SAP Gateway, Fiori

 Architecture

 

Configuration – (Assuming, the sapgateway protocol is https (which is most likely to be))

Configuring BOBJ Platform

Enable https on BOBJ web application server, no backend https is required.  I am using Tomcat in this example

• Use Keytool in tomcat java home bin directory to create a self-signed keystore

 

keytool -genkey -alias tomcat -keyalg RSA –keystore keystore.jks.

This command will create a self-signed keystore named keystore.jks under keytool home   directoty

• Please export self-signed certificate in .crt format.

keytool -export -alias tomcat -keystore keystore.jks –file https.crt

This command will create https.crt in same directory.

• Generate SSO certificates and keystore files using PCKS12 tool

Windows location : \SAP BusinessObjects Enterprise XI4.0\java\lib

Windows Command :  “\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\bin\java” -jar PKCS12Tool.jar -alias bobj -storepass password -dname CN=BOS

The above command generates keystore and cert.der files .

Stop the tomcat, navigate to /conf/server.xml . Edit the server.xmlfile as below

Uncomment the https entries and add below parameters.

keystoreFile=”keystore.jks” keystorePass=”password”

 

Restart the tomcat , https links should work .

Configuring Fiori server

Install the https.crt ( certificate generated from keystore.jks )  into fiori abap stack using the below command at OS level

sapgenpse.exe maintain_pk -p -a https.crt

Configure SAP gateway to forward the requests to BOBJ platform.

wdisp/system_ = SID=BOE, EXTSRV=https://bod:8443 SRCSRV=*:8000 SRCURL=/BOE/

On the ABAP front end server using T code Strustss002 , please import the SSO certifictes generated by BOBJ Platform.

Setting up single sign on on BOBJ Platform

1) Add the ABAP front end as the entitlement system in CMC

2) Import the required Roles and keystore in CMC

3) Setup SAP ABAP stack to send SAP Logon Tokens

Now create a Tile in Fiori Launchpad, redirecting to BOBJ Design studio Opendocument link.  The navigation should work seamlessly

 

Shiva Prasad Aluri

Url to access – http://server:port/BOE/BILaunchpad

Security Changes – Yes, new right needs to be granted 

Old Version – No confusions please, Classic BI launchpad still available and can be used for many advanced functions. In my opinion, new launchpad is strictly a consumer interface.

First Look 

Changing preferences 

Go to User profile > Click on settings

The setting are very similar to classic BI Launchpad. 

    Users can set preferred Landing tab

    Pixels for web-based look

    Hide/show totals for Analysis OLAP

By default the landing page navigates to Home Tab (with Show all selected). Users can change the documents to view as below

Context Menu 

Context menu of Tile/document can be launched by clicking the 3 dots at bottom on each tile, which lists all the properties of the document

Context menu is similar to right-click on report in classic BI. Below options available under the context menu

Working with Categories

Document tiles in new BI Launchpad can be grouped by categories.( Standard BOBJ categories). Security can be configured at CMC level. Documents can be tagged to categoris from context menu.

Once the document is assigned to a category . changing the landing page view to categories will display all categories .

Viewing standard BI folders

Once you login to BILaunchpad, select Folders Tab which displays all the folders for which the account has access to.

 

Bharat Sunkari

Managing Partner – Tek Analytics