Exercise : 1 - Using SAP HANA Studio:-

This section includes an exercise on look and feel of SAP HANA Studio. In this exercise you will log on to the
WTS server, and get familiar with navigating in SAP HANA Studio. You will complete the exercise by creating
your own Information Package.

Procedure:-
1. If you logon via VDI landscape please follow the instruction given by your instructor otherwise logon to the WTS
landscape
• Go to Start-Menu
• Start menu: Choose Common-Training

2. Remote Desktop into Server

• Create a remote desktop connection to another desktop (connection information will be given by the
instructor)
• Start the Remote Desktop Connection as shown in the screenshot on the right side.
• Use the path: Start Menu → All Programs → Accessories.

3. In the next screen you have to choose one of the available remote desktop servers.
Note: Type the name of the Server (specified by your instructor).
• Click → Connect.

4. In the Remote Desktop Connection dialog box enter user name and password given by the instructor.

.5. Now you are on the right desktop and can start the SAP HANA Studio by going to Start → Studio.

6. Open Administration Console.

7. Register a new System.

Right Click within the Navigator view and choose → Add System....
• Enter the Hostname, Instance Number and Description as given by the instructor.
Click → Next.

8. Enter your credentials as given by your instructor.

9. Change your initial password

• Minimum 8 characters
• Must contain capital and small letters
• Must contain numbers
• Example: Abcd1234

Note: If your HANA system is not properly connected to the SAP HANA Studio (status is red), choose Refresh
from the context menu If necessary, close and reopen the SAP HANA Studio.

10. The first customization you should do is now to adjust the default setting of the
default client in the studio preferences
.
Therefore go in the top menu and choose Window → Preferences...
11. Next, expand the Modeler node in the tree and click on Default Model Parameters
Now ensure that the client is 800.
• Maybe you must change it from dynamic to 800. Press the button Apply.
12. The whole perspective setup can be maintained via the Window menu on top.
• You have access via Window → Open Perspective → Other to all pre-delivered and saved perspectives.
• Please, open Modeler perspective.

13. To switch easily between different perspectives you can click on the toolbar on top on
the corresponding button

• Each open perspective will be shown here.

14. For the SAP HANA Studio the central point of Access is the Navigator View, which is
usually placed on the left side of the screen.

• In the Navigator tree you can incorporate several SAP HANA instances directly connected with the
appropriate user.

• Note that there are two main sections in the navigation tree.

– The Catalog node navigates to the physical tables, views, etc.

– The Security node navigates to users and roles.

– The Content node navigates to Attribute Views, Analytic Views,

Calculation Views, Procedures and Analytical Privileges

Note: The Content node is only visible inside the Modeler perspective.

Note: Per default the catalog objects are filtered by privileges.

15. The “Catalog” contains all Database schemas.

• Each Schema contains a folder for Column Views, Procedures, Tables and Views.

16. The Folder “Content” contains the Information Model packages.

• Each package can contain a folder for Attribute Views, Analytic Views, Calculation Views, Analytic Privileges
and Procedures,
• Open one Analytic View and notice the structure.
• Switch between the Semantics, Logical Join, and Data Foundation. Inspect the Output frame.

17. The Administration console reflects the pre-delivered Administration Perspective.

• To get to this screen, choose the Navigate tab followed by a click on the 'administrative’ icon (looks like
tools).
‘• Dependent on your user’s privileges, in this perspective you have options to administrate the SAP HANA
Instances.

Exercise : 2 - SAP BW Tables in SAP HANA:-

1. In the “Navigator” Tree, expand the node “Catalog”.

2. Expand the node for the “SAPCIA” schema and then expand the “Tables” folder within that schema.
3. This shows the first set (1000) of all SAP BW tables in that schema. All BW tables are in HANA
4. Right-click the “Tables” folder and select Filter from the context menu. This opens a dialog box.
5. In that dialog box, you can enter a table name.
•
Note: You are opening the list of tables within schema “SAPCIA”, so we are searching for tables within the
SAPCIA schema.
• Therefore, do not specify the Schema name in the search field.
• Enter “/BIC/” in the input field and confirm with OK.

Exercise : 3 - HANA-Optimized DataStore-Object:-

1. Logon to the BW on HANA system.

Start SAP Logon

2. Select CIA as your BW system.

3. User and password will give by your instructor.

4. Use transaction RSA1 and navigate to your Info Area BW Training → User
Area → Group ##. Create your own DSO.
• Technical name: U##DSO1
• Description: U## DSO for Purchase Orders
• Use 0EPM_DS01 as a template.
(NULL not O)
Activate your new DSO Object.
You have now created a new standard (non-HANA-optimized) DSO.

5. Open the “Manage” view for your DSO.

6. Get the table names from your standard DSO. Write down the “table names”.

7. Open SAPCIA schema in the HANA modeler and find the original DSO table on DB side. Use the filter
dialog to find them.
8. Open the table definition and the data preview for you tables to control the content.

9. Click on the Export SQL icon to display the corresponding SQL statement in the table definition screen. The
SQL statement describes the create procedure for this table.

10. Control the volume of the “Active” table in the “Runtime” tab based on the “Definition” view
.Your active table has no data records at the moment.

11. Back to the BW system, create a dataflow for your DSO object and connect the DSO with the existing Data
Source 0EPM_PO.
Navigate to DSO 0EPM_DS01.
(NULL not O)

12. Use the dataflow copy tool to copy the transformation Choose Downwards and No to skip the collection of
DTPs and Info Packages.

13. Click on Continue for the first steps and choose YOUR DSO U##DSO1 as a target.

14. Copy the existing transformation.

15. Start the activation process direct in dialog

16. Navigate to your DSO U##DSO1. Refresh the tree. Check your transformation.

17. Create a DTP for loading data from the existing Data Source 0EPM_PO into your DSO. The Data Source
already contains data Set the DTP to Extraction Mode Full (to allow for several data loads of he same data for
comparison between non-HANA-optimized DSO and HANA-optimized DSO).
18. Start the DTP and check the load process.

19. Activate your DSO data and check the performance via activation log.

20. Display the DSO data from HANA side.

21. Now it is time to migrate the “normal” DSO to a HANA optimized DSO object.

Start transaction RSMIGRHANAD and run the program

RSDRI_CONVERT_CUBE_TO_INMEMORY.

22. Choose your DSO U##DSO1 and the displayed settings and start the migration process
.
23. Open DSO Maintenance. Check Settings. Should be “In-memory optimized” and SID-enabled = “SID
generation during activation””. If not SID-enabled: Check the setting and re-activate DSO

24. Start the DTP again. Activate the data and check the activation log again.

Nearly zero activation time!!

25. Check the change log data in BW and on HANA side.

26. Where you can find the Changelog on HANA side now?

It is a “Column View.

Exercise : 4 - HANA-Optimized InfoCubes:-

1. Create your Cube U##CUBE1 in your own Info Area U##.

Technical name: U##CUBE1
Description: U## Open Purchase Orders
Template: 0EPM_C01
Activate your new cube.

2. Copy the existing transformation based on cube 0EPM_C01.

3. Choose your new cube U##CUBE1 as the target of the transformation and your DSO U##DSO1 as a
source. Activate the transformation.

4. Create a DTP using standard settings and load the data from your DSO into your cube.

5. Check the cube model with transaction LISTSCHEMA.

6. Are there real dimension tables?

7. Check the Info Cube tables directly on HANA side. Use the SAP HANA Studio and define a filter for your
cube (Schema SAPCIA).

Exercise : 5 - HANA-Optimized SPO:-

1. Create your own DSO-SPO.

Technical name: U##SPO
Description: U## SPO one per quarter
Template: U##DSO1
Mark the check box “Semantically Partitioned”!

2. You want to create HANA optimized DSO objects. Please mark the corresponding checkbox.

3. Set field 0CALDAY as a additional key field. Save the DSO

4. Select the partitioning field 0CALDAY.

5. Add four partitions from 01.2011 to 12.2011 (Quarter of a year).

01.01.2011 – 31.03.2011
01.04.2011 – 30.06.2011
01.07.2011 – 30.09.2011
01.10.2011 – 31.12.2011.

6. Start the activation from the wizard.

7. Create the transformation and use your DSO U##DSO1 as a source.

8. Complete the transformation and assign 0D_NW_CA to 0CALDAY. Activate your transformation

9. Create a DTP template Description: U##DTP Template

10. Use “Data Store Object” as Data Source and save the template.

11. Assign your DTP template to all DSO Part Providers. Generate all DTPs.

12. Create a process chain.

13. Assign your four DTPs per drag and drop to your process chain.

14. Generate the process chain. Use the default start process and set the parameter for scheduling to
“Immediate”.

15. Move to the process chain maintenance.

16. Start the process chain and verify the result.

Exercise : 6 - HANA VirtualProvider:-

1. Create a Virtual Provider in your Info Area U## to support direct reporting on a HANA View.

Business Case: Direct reporting on non-SAP data stored in HANA.

2. Technical name: U##VCUBE1

Description: U## Virtual Provider
Check the radio button Based on HANA Model.

3. Click on button Details and choose

Package: training. general
HANA Analytic View SALES_DATA_001.

4. Choose following Info Objects direct and add them to the data model to create a smart view into the data.
5. Dimension 1
0D_SOLD_TO
0D_MATERIAL

6. Key figures
0D_NETVAL_S
0D_QUANT_B

7. Assign the HANA attributes and key figures to the BW Info Objects (mapping).
8. First the attributes. Please use the F4 value help.
9. Second the key figures.
10. Activate your new Virtual Provider. Ignore warning messages about field length.
11. Display data based on RSA1. Select some fields for preview.

Exercise : 7 - TransientProvider:-

1. Create a Transient Provider for direct reporting on a HANA model via BEx or BI reporting without any
additional BW content in RSA1

First, create your own HANA model, creating a copy from an existing analytic view in HANA studio

Technical Name: SALES_DATA_##

Description: SALES_DATA_##
Template: SALES_DATA_001.

2. Save and activate the new view.

3. Switch to the BW system and call transaction RSDD_HM_PUBLISH. Create a new Analytic Index
.Catalog (package): training.general
SAP HANA Information Model: Analytical View SALES_DATA_##
Click on Create.

4. Confirm the suggestion for naming for the Analytic Index (Transient Provider), i.e., SALES_DATA_##.

5. Save the new Transient Provider in your Info Area U##.

6. Check the new Transient Provider by using a BEx report. Start the BEx Query Designer: Start → All
Programs → Business Explorer→ Query Designer

7. Use your BW user and password

It takes some seconds for the first time.

8. Search for your new Transient Provider @3SALES_DATA_##

Hint: If you change something in your Analytic Index or create another one sometimes you must restart the
Query designer for refresh.

9. Create and save a query U##_TP1, using your own suggestions for columns and rows. Test your query via
transaction RSRT in BW.

Exercise : 8 - CompositeProvider:-

1. Call transaction RSLIMOBW for creating a Composite Provider.

2. Create a new Composite Provider. Technical name: U##_CP1
3. Take your Analytic Index SALES_DATA_## and your cube U##CUBE1 per drag and drop to the right side.
Use UNION as binding type
.
4. Choose the following fields from your cube (drag and drop)
• Product ID
• Order Currency
• Gross Order Amount.

5. Assign the following fields from your Transient Provider.

Product ID (Map Product ID to Product ID (EPM Demo))
Currency
Amount

6. Change the properties assignment for field Amount.

7. Activate your new Composite Provider and start a data preview.

Exercise : 9 - DB Connect:-

1. Create a DB Connect Data Source against HANA DB.

In RSA1, navigate to the Data Sources tree for the DB Connect source system
HDB7211.

2)From the context menu of the application component ZBW_TRAINING,

create a new Data Source.

Technical name: U##_DS1

Data type: Transaction Data
Description: U## HANA DBC Data Source.

3. Change to the tab Extraction

Type DB user _SYS_STATISTICS (upper case) and select the HANA internal table HOST_VOLUME_FILES.

4. Please check all data types that have been assigned by the proposal. Change four of them according to the
screenshot.

.5. Activate the Data Source.

Use the data preview tab to control the access.
You can see the save point files from the HANA DB itself.

Exercise : 10 - Create Workspace:-

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 they are completely in-memory.
Scenario:-
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 Net Weaver BW sales data (Purchase Orders) in Info Cubes
with a Multi Provider on top.

Additionally, the central SAP Net Weaver BW provides the company’s central ABC Rating information of
customers worldwide in an Info Provider, 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 Net
Weaver 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 Net Weaver Business Warehouse. Furthermore, the IT department provided the SAP Net
Weaver Business Client and corresponding roles for access to the BW Workspace Designer.

Procedure
1. Open transaction RSWSP. Create your own Workspace.
Technical name: U##_Workspace

2. Assign following settings.

Description: U## First Workspace
Workspace Prefix: U##
Multi Provider: 0EPM_MP01
Maximum Memory: 1 MB
Maximum Number ..: 10
Master Data Allowed: √

3. Check the usage for the “Central Provider”. This provider will be the master or “Central Provider” for further
scenarios.
4. Activate the SAP BW Workspace and leave the transaction. Otherwise you lock the workspace.

Exercise : 11 - Workspace Designer to Create Local Providers From A

File:-
Now you are in the role as a Business User. You want to use the predefined BW Workspace. In this Exercise,
you will upload your own data to create Local Providers.

First please copy three files for preparation to your local “Documents” folder

• Business_Partner_Team.CSV
• Product_Status.CSV
• Business_Partner_ABC.CSV

Naviagte to folder Documents - HANA - BW362. Use user training and password hana read only for
authorization check. Save/Copy these files to your local “Documents” folder.
Procedure
1. Open the Net Weaver Business Client to start the BW Workspace Designer.

Start → All Programs → Net Weaver Business Client 3.5

Hint: The BW Workspace Designer can be started either via the “NW Business Client” or the “SAP Portal”. If
you use the Business Client, no Java Stack or SAP Portal installation is necessary.

2. First, establish a connecting to the SAP BW system.

Name: BW on HANA
URL: http://wdflbmt7211.wdf.sap.corp:54080/NWBC
Type: ABAP
Client: 003
Language: DE or EN

3. Logon to BW system by using your BW user account.

User: USER##
Passw:“ your new passw.”

4. Verify that you are assigned to your workspace “U## First Workspace” (U##_WORKSPACE) by clicking on
tab “Workspace Tools”, choose your workspace and click on Save button

5. Click on tab “My Workspace” to create three “Local Providers” based on CSV files.

The first Local Provider is for the team information. Witch team is responsible for a customer. They have been
stored the data in a local flat file that you want to use for the new “Local Provider”.

Click on the Create button.

6. The source type “File” is correct for your case. Press Continue.

7. Click on Browse to find the flatfile and select Business_Partner_Team.csv from your folder Documents
.
8. Log In for the file system and use the following parameters to load the flat file
• User : training
• Password : hanareadonly
Header: 1
First Data Row: 2
Separator: , (comma!!)
Name: U##_BP_TEAM
Description: U## Business Partner Team
Click on Next

9. In the second step choose the data type “Character String with Leading Zeros” for “Business Partner” to fill
up the data with leading zeros and choose Length 10 for the field length
Click on Upload Data.

10. Click on Display Data for checking the data quality. Now you have created your first local provider
.
11. The second Local Provider is for the ABC rating information. Each customer assigned to a rating group for
internal categorization. They have been is stored the data in a local flat file that you want to use for the new
“Local Provider”.
Click on Create button

12. The source type “File” is correct for your case. Click Start.

13. Click on Browse to find the flat file and select “Business_Partner_ABC.csv” from folder “Documents”.

14. Use the following parameters to load the flat file:

Header: 1
First Data Row: 2
Separator: , (comma!!)
Name: U##_BP_ABC
Description: U## Business Partner ABC
Click on Next.

15. In the second step choose the data type “Character String with Leading Zeros” for “Business Partner” to fill
up the data with leading zeros and choose Length 10 for the field length
Click on Upload Data.

16. Click on Display Data for checking the data quality. Now you have created your second local provider
.
17. The third Local Provider includes information about “Inventory Management”. The standard “Inventory
Management” is not in used at the moment and you must upload local information via flat file.
Click on Create button.

18. The source type “File” is correct for your case. Click Start.

19. Click on Browse to find the flat file and select “Product_Status.csv” from your folder “Documents”.

20. Use the following parameters to load the flat file:

Header: 1
First Data Row: 2
Separator: , (comma!!)
Name: U##_P_STATUS
Description: U## Product Status
Click on Next.

21. In the second step choose the data type “Character String with Leading Zeros” for “Product” to fill up the
data with leading zeros and choose Length 10 for the field length.
Click on Upload Data.
22. Click on “Display Data” for checking the data quality. Now you have created your third local provider
.
23. At last check that there are three local providers in your workspace. Choose “My Workspace” and tab
“Local Providers”.

Exercise : 12 - Workspace Designer to Create A Local Provider From A

BW DataSource:-
1. First we need an approval from the BW IT department. They must allow data access to an BW Data Source.
.
Switch to the BW System into transaction RSWSP. Edit your BW Workspace U##_WORKSPACE and sselect
the Data Source using Drag & Drop 0EPM_EMPLOYEE as a Central Provider.
Activate your changes.
2. Switch to the Workspace Designer in the Net Weaver Business Client. Create another local provider in your
BW Workspace by selecting a BW Data Source as a source.
.3. Select the “Employee” Data Source given by the BW Administrator.
Name: U##_LOCAL_DataS
Description: U## Local DataSource Employee (CIACLNT003).

4. Confirm the suggestions in the following step and Upload Data.

5. Control your new local provider in your Workspace.

Exercise : 13 - Workspace Designer to Create A CompositeProvider

The next step is to combine the SAP BW data with your own data, based on the
“Central Provider” and your “Local Provider”.
Procedure:-

1. Switch to the tab Composite Providers Click on Create to create a Composite Provider.

2. In this case we do not need a query as a template. Please click on Start directly.

3. Use the following data:

Name: U##_SALES1
Description: U## Sales Analysis 1 (local)
Choose all relevant providers (Excluding provider based on BW Data Source)
Click on Next

4. In the next step you must define the relations between the “Central Provider” and your local providers
.The proposal for the relation type “Inner Join” is correct. Click on “Generate Proposal” for each local provider
to choose the right field, relation between the “Central Provider” and your locals.

5. Choose the default suggestions to analyze and find the proposals automatically. If you want to assign the
fields by your own, you can click on the Detail for Links button

.6. Check the relationships between the “Central Provider” and your local
providers.
1. Table View
2. Graphical View.

7. Click on Next.

8. Change the field description from “Ctry” to “Country” and check the key, figure assignments at the bottom of
the list
.
Ignore warning messages about missing compounding fields.
Click on Next.
9. In the following step, you can create a first “default” query for your new Composite Provider. Use “Standard”
for the query type and confirm the following suggestions, by clicking Next

Your new query $U##_SALES1 is now generated.

10. In the last step, please check the model and your settings for a last time. You can display the data, too.

Click on Save and Activate

11. Ignore warning messages.
Your Composite Provider is now ready to use.

Exercise : 14 - Consume CompositeProvider Using SBO Analysis for

MS Excel:-
1. Open Analysis for Microsoft Excel in your MS Windows menu.
Start → All Programs → SAP Business Objects → Analysis for Microsoft Excel
2. Click on tab “Analysis”.
3. In the next steps you must select your SAP BW system as source. Click on Insert and choose Select Data
Source
.
4. Skip the next popup.

5. Select CIA (SAP BW system) and click on next.

6. Use your SAP BW user and password

7. Search for your default query $U##_SALES1 and click OK.

8. Define the following row structure

9. Enjoy your first BW Workspace result.

Exercise : 15 - Case Study – EPM Model

1. ItelO is an international retail company with several subsidiaries world-wide that buys and sells computers
and accessories via a web shop. It organizes its daily business activities using SAP software. Now, reporting
should be realized using an SAP Net Weaver Business Warehousing solution As a consultant, you need to
design an Enterprise Data Warehousing architecture that not only supports the current reporting requirement
with good performance, but also supports the unkown for future reporting requirements.

Requirement Analysis:-
In a first step, you have conducted a requirements analysis. As a result you now know that reporting should
particularly answer the questions listed below. You need to evaluate whether a given reporting requirement
belongs to strategic or operational reporting and whether it operates on mass data or on selective data

• How much time passes on average per month between a purchase order and goods delivery? Is there a
trend over the years?
• How fast can we deliver after a sales order, dependent on product or supplier?

• How reliable are our suppliers in terms of quantity, quality, and speed of delivery?

• Turn-over of products on stock: Fast sellers, slow sellers?

• Current stock per product, i.e. product availability?

• Sales revenue per employee, per customer, per product, per region in different time periods (week, month,
quarter)?

• Total weight and volume of goods delivered per city and month?

• Sales quantity in pieces per product and week?

• Status of sales order?

• Outstanding invoice amounts?

Business Process and Source Data Analysis
In a second step, in order to get an overview of the business process and available source data, you have
asked IT to provide you with the necessary information on the business model and its implementation on ERP
side.
They give you the following list
Master Data
• Product: Main table SNWD_PD, Data Source 0EPM_PROD
• Employee: Main table SNWD_EMPLOYEES, Data Source
0EPM_EMPLOYEE
• Business Partner: Main table SNWD_BPA, Data Source 0EPM_BP
• Organizational Structure: SNWD_COMPANY and
SNWD_ITELO_DEPTS

Transaction Data
• Purchase Order: main tables SNWD_PO and SNWD_PO_I, Data Source 0EPM_PO
A purchase order has five different status tags:

1. Approval Status (initial, approved, rejected)

2. Confirmation Status (initial, confirmed, sent, cancelled)

3. Lifecycle Status (closed, new, in progress, rejected, cancelled)

4. Order Status (initial, delivered)

5. Invoicing Status (initial, invoiced)

• Purchase Order Invoice: main tables SNWD_PO_INV_HEAD and

SNWD_PO_INV_ITEM.

• Sales Order: main tables SNWD_SO and SNWD_SO_I.

• Sales Order Invoice: main tables SNWD_SO_INV_HEAD and SNWD_SO_INV_ITEM

• Storage Bin: main table SNWD_STOCK.

Exercise : 16 - Design LSA for Case Study:-

1. Create a draft of the BW architecture for transaction data only to realize the requirements from the case
study under consideration of the LSA principles

using the data flow modeling tool.

Info Area: BW Training → User Area → Group ## (T_BW → T_USERS→ U##)

Technical name: U##_DF_EPM

Description: U## Data Flow EPM case study

It is sufficient to use object templates, since we are not going to implement the complete scenario. The
purpose is to design the Enterprise Data

Warehousing Architecture.

When sketching your architecture, feel free to use all the available Info Provider types to represent the different
layers, and also keep in mind that logical partitioning can contribute to a good performance. Where adequate,
you may incorporate the existing Info Providers, Data Sources, and data flows.
Exercise : 17 - LSA → LSA, powered by SAP HANA
1. Inspect your LSA for the Enterprise Procurement Model from the previous Unit. A technical migration to SAP
Net Weaver BW, powered by SAP

HANA has been conducted.

1. Which steps do you have to undertake as a minimum from an application point of view?

2. Where do you expect performance improvements and why?

3. How can you streamline your Enterprise Data Warehouse to arrive at a consistent flexible EDW core?

2. Solution:

1. Migrate Info Cubes, DSOs, and SPOs to HANA-optimized objects.

.
• Load performance (DSO activation, update Info Cubes no DIM-IDs).

• Query performance: Reading from columnar tables in memory is much faster and evaluation of aggregations
and calculations is done using the HANA engine

.
3. Inspection of the Business transformation Layer transformations shows:

• For Sales Orders: Quantity Conversion takes places. If this can be moved to the query - because the result
needs not be stored permanently – the Sales Order Info Cubes (or Info cube-SPO) can be deleted. The Sales
Order Multi Provider then sits directly on the Propagator DSO-SPO.

• Purchase Orders: The Order Lifecycle Status is determined using a routine. Thus, the transformation is
necessary and the Info Cubes cannot be deleted

.• Invoices: The transformationen are only 1:1. The Info Cubes (or Info Cube-SPOs) can be deleted.

Exercise : 18 - LSA, powered by SAP HANA → LSA++(Optional)

1. Throughout the course, you have created a number of Info Providers for your version of the Enterprise
Procurement Model (EPM) Enterprise Data Warehouse. Into which LSA++ layer would you file your BW
objects?

Which reporting scenario does the Info Provider support?

1. Virtual Provider: U##VCUBE1, U## Virtual Provider Solution: Open ODS Layer. Sales data in real time.
Could be combined Solution: Open ODS Layer. Sales data in real time. Could be combined and agile current
data.

2. Transient Provider: @3SALES_DATA_##, SALES_DATA_##

Solution: Same as for Virtual Provider but less integration with BW data model, because transient Info Objects
are used without mapping to existing BW Info Objects

.
3. Composite Provider: U##_CP1, U## Composite Provider
Solution: Agile Data Mart Layer. Union of Open Purchase Orders data from Info Cube (EDW core; architected
data mart layer) with agile sales data from Transient Provider (open ODS layer). The way the Composite
Provider is built does not conform to best practice, since the Info Cube is directly used. According to best
practice, the Info Cube should be wrapped in a Multi Provider (virtual wrap layer). Then, the Composite
Provider should be created on top of the Multi Provider and the Transient Provider (virtual composition layer).

4. DB Connect Data Source: U##_DS1, U## HANA DBC Data Source

Solution: Open ODS Layer. All Data Sources reside in the open ODS layer that serves as the LSA++
successor of the data acquisition layer in LSA. Since we do not know how the data will be consumed, the
reporting scenario cannot be specified at this stage. It may be possible to create a Virtual Provider based on a
DTP with direct access or to utilize the Data Source as the first object of an EDW core staging process

5. Local Provider:
• U##_BP_TEAM, U## Business Partner Team
• U##_BP_ABC, U## Business Partner ABC
• U##_P_STATUS, U## Product Status

Solution: BW Workspace Layer. Additional departmental local master data that enhances the business partner
master data and the product master data are uploaded into BW and may be accessed by members of the
department.

.
6. Composite Provider: U##_SALES1, U## Sales Analysis 1 (local)
Solution: Virtual Composition Layer. The Central Provider – of the BW Workspace that has been used – is a
Multi Provider that serves as a wrap on top of an Info Cube holding Open Purchase order data (EDW core;
architected data mart layer). It is combined with an inner join to local data from the Local Providers within the
given BW workspace (BW Workspace layer). This supports departmental reporting, where corporate data shall
be enhanced with local data that are of relevance only for a given single department: “I want to enhance the
BW report with my own Excel data.”

Exercise : 19 - Optional: LSA++, Evaluation of Additional Reporting

Scenarios
1. How would you incorporate the following scenarios into your LSA++?

1. For a special marketing campaign in Italy, Spain, Greece, and Turkey, the products delivered have been
enhanced with local give-aways. A list has been manually created which type of give-away has been packed
to which sales order delivery. The local sales executives now want to know, whether the time between two
sales orders of their customers has been reduced in the month after the campaign as compared to
the months before the campaign, to evaluate the effectiveness of the campaign. In addition, they want to know
whether the type of give-away has had an influence on customer behaviour.

2. Your Bangalore-based company has sales agencies in almost all countries of the world. However, in most
countries, the number of sales workforce is very small, so that a few employees cover the whole
country. Only the Indian market is large enough to split the country into sales regions. According to corporate
reporting guidelines, the corporate sales reports only report on country level. Consequently, the flexible
consistent EDW core uses the country as its most granular geographic Info Object. For the Indian market,
sales reporting should be permanently enhanced by incorporating the Indian sales region into the model,
without remodelling the central EDW core so as to not affect reporting in all other countries.
3. The Chinese New Year is approaching. Since in the US market, many customers of the ITelO Company are
of Chinese background, the local Sales department has conducted a text pattern search on the names of
all US customers. The external text mining tool returned all customers whose names suggest a Chinese
background as a CSV file. A mailing has been delivered to this group of customers, suggesting an ITelO
analyse the effect of the campaign by comparing the sales volumes product as a gift for Chinese New Year.
Now the sales executive wants to for the group of “Chinese” customers this year with the previous year
as well as the sales volume per customer for the group of “Chinese” customers versus “non-Chinese”
customers.