SAP BW on HANA Materials

BW350HSAP BW powered by SAP HANA - Data Acquisition

PARTICIPANT HANDBOOKINSTRUCTOR-LED TRAINING

Course Version: 15 Course Duration: 5 Day(s) Material Number: 50136498

0

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]


0



SAP Copyrights and Trademarks

© 2016 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://globall2.sap.com/corporate-en/leRal/copvright/index.epx for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE's or its affiliated companies' strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

iii© Copyright. All rights reserved.



http://globall2.sap.com/corporate-en/leRal/copvright/index.epx

Typographic Conventions

American English is the standard used in this handbook.

The following typographic conventions are also used.

Th is information is displayed in the instructor's presentation

Demonstration □Procedure V

VV

Warning or Caution

Hint

A

ORelated or Additional Information

Facilitated Discussion l»

User interface control Example text

Window title Example text

iv © Copyright. All rights reserved.



Contents

vii Course Overview

1 Unit 1: SAP BW and HANA Data Acquisition

315

2029355569738794101110

Lesson: Introducing BWExercise 1: Log in to BW and Navigate in the Data Warehousing Workbench

Lesson: Introducing HANAExercise 2: Connect to HANA Studio and the BW Modeling Tool

Lesson: Explaining Data Acquisition in SAP BW Exercise 3: Build a Basic Data Flow

Lesson: Explaining SAP HANA Optimized Data StagingExercise 4: Work with HANA-Optimized Transformation Rules

Lesson: Comparing & Migrating 3.x to 7.x Data Flow Components Lesson: Using Data Transfer Process Delta and Debug Settings

Exercise 5: Use an Error DTP Lesson: Introducing Data Replication in HANA

117 Unit 2: Data Acquisition with the SAP BW Service API

119 Lesson: Connecting and Configuring SAP Source Systems123 Lesson: Displaying the Configuration of the SAP BW Service API129 Lesson: Modeling Generic DataSources135 Exercise 6: Create a Generic DataSource for Attributes148 Lesson: Explaining Business Intelligence (Bl) Off the Shelf Content169 Lesson: Loading Hierarchies from ECC176 Lesson: Examining the Transfer of GL Data182 Lesson: Adapting Bl Content DataSources191 Exercise 7: Adapt a DataSource200 Lesson: Implementing Process Chains for BW on HANA209 Exercise 8: Build a Meta Chain with Delta Merge

225 Unit 3: Delta Data Flow Management

226 Lesson: Describing Delta Management230 Lesson: Explaining Terms and Basic Processes of Delta Enabled

DataSources251 Exercise 9: Analyze Delta Information for DataSources260 Lesson: Configuring Logistics Data Extraction (LO Cockpit)275 Lesson: Configuring Generic Delta DataSources281 Exercise 10: Load Transaction Data with Generic Delta

© Copyright. All rights reserved. v



295

297

304313331343359363380395399

409

410421432437452

469

471499527545560571578592609

623

624631643

654657

665

666672677680

Unit 4: Data Acquisition with ODP and SLT

Lesson: Describing Data Acquisition with Operational Data Provisioning - ODPLesson: Analyzing Operational Delta Queue (ODQ)

Exercise 11: Analyze an ODP/ODQLesson: Replicating Data with SAP Landscape Transformation (SLT)

Exercise 12: Load, Filter, and Transform via SLT Lesson: Acquiring Data in Real Time with SLT

Exercise 13: Transfer Data in Real Time to SAP BW via SLT Lesson: Learning the details of Real Time Data Acquisition (RDA) Lesson: Extracting into BW Using ODP - SLT

Exercise 14: Work with ODP type HANA Information Views

Unit 5: Flat File Data Transfer

Lesson: Accessing Data from a Flat FileExercise 15: Create Direct Access to a Flat File Data Source

Lesson: Loading Flat File HierarchiesExercise 16: Load with the Hierarchy Framework

Lesson: Using Workspaces for Local Flat File Loads

Unit 6: Additional Data Acquisition Techniques

Lesson: Positioning HANA SDI Capabilities for BWExercise 17: Stream Data with Smart Data Integration

Lesson: Integrating SAP Data Services and SAP BWExercise 18: Import Data to SAP BW via SAP Data Services

Lesson: Positioning DB ConnectExercise 19: Transfer Data with DB Connect

Lesson: Positioning Universal Data (UD) Integration Lesson: Explaining XML-Based Extraction

Exercise 20: Acquire Data Using a Web Service DataSource

Unit 7: Data Mart Interface and OpenHub

Lesson: Positioning the Data Mart Interface Lesson: Implementing OpenHub Destinations

Exercise 21: Export from a BW InfoProvider to a Native HANA Table

Lesson: Exporting a Hierarchy with OpenHubExercise 22: Export a Hierarchy with OpenHub

Unit 8: Overview of BW Transports

Lesson: Describing the BW Transport System Landscape Lesson: Managing BW Transports Lesson: Troubleshooting Transport Strategies Lesson: Determining Object Versions and Metadata

© Copyright. All rights reserved.



Course Overview

TARGET AUDIENCEThis course is intended for the following audiences:

• Systems Architect

• Project Manager

• Consultant All Roles

• Application Consultant

• Development Consultant

• Technology Consultant

• Support Consultant

• Data Consultant

• Developer

• Solution Architect

• System Administrator

• Technology Consultant

• Trainer

© Copyright. All rights reserved.



viii © Copyright. All rights reserved.



UNIT 1 SAP BW and HANA Data Acquisition

Lesson 1

Introducing BW 3Exercise 1: Log in to BW and Navigate in the Data Warehousing Workbench 15

Lesson 2

Introducing HANA 20Exercise 2: Connect to HANA Studio and the BW Modeling Tool 29

Lesson 3

Explaining Data Acquisition in SAP BW 35Exercise 3: Build a Basic Data Flow 55

Lesson 4

Explaining SAP HANA Optimized Data Staging 59Exercise 4: Work with HANA-Optimized Transformation Rules 73

Lesson 5

Comparing & Migrating 3.x to 7.x Data Flow Components 87

Lesson 6

Using Data Transfer Process Delta and Debug Settings 94Exercise 5: Use an Error DTP 101

Lesson 7

Introducing Data Replication in HANA 110

UNIT OBJECTIVES

• Introducing BW

• Introducing SAP HANA

• Discuss SAP BW Data Flow Components

© Copyright. All rights reserved. 1



Unit 1: SAP BW and HANA Data Acquisition

• Describe how SAP BW transformation rules can be SAP HANA-optimized

• Migrate 3.x to 7.x data flow

• Explain the Data Transfer Process(DTP) Delta Settings

• Debug with the Data Transfer Process

• Compare SLT, SDI, and SDA

2 © Copyright. All rights reserved.



Unit 1 Lesson 1

Introducing BW

LESSON OBJECTIVESAfter completing this lesson, you will be able to:

• Introducing BW

SAP Business Warehouse (BW)The goal of the implementation of classic data processing systems is, the acceleration, cost reduction, and automation of processes in individual business areas. This is achieved by Enterprise Resource Planning (ERP) systems and other software tools. The result is that these ERP systems, CRM systems, banking and credit card systems, and Corporate Governance regulations have exponentially increased the data volumes that require analysis. Some consider this a negative; others, like SAP, think that this enormous amount of electronic information is of benefit.

In parallel, ever-increasing globalization, and the increasing decentralization of organizations has created the need to recognize market trends and to collect information about competitors. This allows the company to react quickly to changes in market conditions. In this Internet age, efficient information processing is important to maintain an advantage over competitors.

Due to continuous innovation in data processing, information is stored in a more detailed format. As a result, there is a need to reduce and to structure this data, so it can be analyzed meaningfully. The analysis necessary to create business intelligence from the collected raw data requires a varied tool set.

Decision makers in modern, globally operating enterprises realize that their survival depends on the effective use of this information. Unfortunately, this information is often spread across many systems, and sometimes many countries, making effective use of information difficult. This is the challenge that modern business intelligence systems attempt to meet. Extensive solutions are required to cover the entire process, from the retrieval of source data to its analysis. Enterprises must be concerned with metadata (business and technical attributes and descriptions of objects) across the enterprise. In addition, they need to consolidate and create homogenous global master data, as well as massive amounts of transaction data, in differing degrees of aggregation.

In heterogeneous system landscapes, a particular challenge is the extraction and preparation of consolidated transaction data and master data from different source systems. The increasing demand for high-quality business information means that, in addition to an integrated data collection process, detailed data analysis and multimedia presentation options are also required. The demand for business intelligence solutions that incorporate all of these features is immense.

SAR40





Cd)Eco>_

>c

LU0)>

0)Q .O

BusinessStrategy

Payment processina Sales order

Billing

Goods issue

:essing O

« r ~% Oe i o

Picking Transportation

OLTP

oAvailabilitycheckailOutbounddelivery

cOJEcOk_

>cL U0)>Ek_

£c

OLAP

Generation DataWarehouse

Homogenization

Cleansing

Knowledge

Figure 1: OLTP and OLAP Environments

The business intelligence software relies on the data that comes from the source systems, but this information cannot easily be used for targeted analysis. Therefore, the source data is, initially, cleansed, technically and semantically prepared (homogenized). The data is then stored in the Data Warehouse component of the business intelligence software. Analyzing this information with strong and flexible reporting tools then helps to better understand the enterprise information and create knowledge. This knowledge may help the organization define, or redefine, its business strategy, and support the business processes derived from it. The online transaction processing (OLTP) environments (ERP) and the online analytical processing (OLAP) environments (Business Intelligence) are interdependent entities. The figure, OLTP and OLAP Environment shows how both environments interact.

SAP Business Warehouse (also known as SAP NetWeaver Business Warehouse or SAP BW) is the cornerstone of SAP’s strategic Enterprise Data Warehouse solutions and runs on industry standard RDBMS and SAP's HANA in-memory DBMS. It delivers reporting, analysis, and interpretation of business data that is crucial to preserve and enhance the competitive edge of companies by optimizing processes and enabling them to react quickly to meet market opportunity.

In SAP BW, you can integrate, transform, and consolidate relevant business information from productive SAP applications and external data sources. SAP BW provides you with a high- performance infrastructure that helps you evaluate and interpret data. Decision makers can make well-founded decisions and identify target-oriented activities on the basis of the analyzed data.

In BW, fields are referred to as InfoObjects. There are two main types of InfoObjects: Key Figures and Characteristics.

Key Figure InfoObjects provide values to be calculated or evaluated such as: Quantity (OQuantity) Amount (OAmount).

Characteristic InfoObjects are business reference objects that are used to analyze key figures such as: Cost center (OCostCenter) and Material (OMaterial). Characteristics represent master data in general.




Lesson: Introducing BW

• There are up to three types of Master Data a Characteristic can have: Attributes, Text, and Hierarchies.

• There are three types of technical characteristics: time, technical, and units.

• Time Characteristic InfoObjects form the timeframe for many data analyses and evaluations. They are delivered with BW Content. Examples of time characteristics InfoObjects include: Calendar day (OCalDay) Calendar year (OCalYear) or fiscal year (OFiscYear). Delivered InfoObjects are preceded by a 0 (zero). Technical InfoObjects include request id for example. Units are used for units of currency or unit of measure.

• In general, custom InfoObjects are preceded by a letter such as Z.

• Characteristics can have related fields called Attributes. Attributes can either be for display or they can be navigational. For example, responsible person is a display attribute for cost center.

• InfoObjects are grouped by InfoArea and by Catalog.

• Characteristics can either store data or they can access data virtually.

• InfoProviders provide data to reports via Business Explorer Queries for example.

• InfoProviders can be tables that contain data or they can be views on tables.

• InfoProviders are grouped into folders called InfoAreas.

• Examples of InfoProviders include:

InfoCubes: these contain actual data from ECC for example.

Standard InfoCubes are read optimized while Real Time InfoCubes contain planning data for example. Real time InfoCubes are write optimized. Virtual InfoCubes do not store data but are used to access data directly from ECC for example.

- Open ODS Views: These do not store data. They are used to access real time data virtually.

DataStore Objects(DSO): in reporting scenarios, DSOs contain more detailed data in general. In planning scenarios, DSOs contain planning data and/or comments for example.

DSOs for planning are set to Direct Input. There are standard, write optimized, and direct update type DataStore Objects.

MultiProviders: these do not contain data; they are used as a virtual reporting layer and to union multiple underlying InfoProviders.

- Composite Providers: these do not contain data; they are as a virtual reporting layer and to union/join InfoProviders and/or HANA views.

- Advanced Data Store Objects: aDSOs store data; and an aDSO can be configured to mimic an InfoCube or a Standard DSO for example.

HybridProviders: These provide historical and real time data. These are made up of either a Standard InfoCube and Virtual InfoCube or a Standard InfoCube and DSO.

BW InfoSets: These are virtual objects used for data joins.

© Copyright. All rights reserved. 5 SAB




• If you need a join or union — Use a Composite Provider

• If you need to store transaction data — Use an Advanced DataStore Object

• If you need to view data from an external source — Use an Open ODS View

• Master Data — Use a Characteristic InfoObject

Modelers use the Advanced DataStoreObject (ADSO) for modeling the persistence of new end-2-end scenarios on BW 7.5 on HANA. The ADSO combines functions from the InfoCube and the DSO (classic) and provides further enhancements, such as modeling on InfoObjects as well as on simple fields. In the context of SAP HANA and BW, the ADSO will become the central object for modeling persistence layers and replace the traditional BW InfoProviders with persistence (InfoCubes, DSO classic, Persistent Staging Area). The existing traditional InfoProviders will still be available additionally to the non-disruptive evolution to the EDW architecture based on ADSOs.





Traditional InfoProviders include:

• DataStore Object: Stores transaction data on detailed level, Examples include: sales order data on item level.

• InfoCube: Stores transaction data on aggregated level, Examples include: sales amounts and quantities per month.

• MultiProvider: Provides view on data of several InfoProviders, Examples include: sales amounts in Germany and the USA.

(0Query Query Query

Definition Definition Definition

Reporting

t Data Warehouse

□ D Composite Provider Dq (Join/Union)

Characteristic d P InfoObjects

Advanced DataStore Objects

Source Systems

Figure 4: BW on HANA InfoProviders





SAP BW Three Layers Architecture

Table 1: Targets of a Data Warehouse Solutions

Layer Details

Reporting Layer Flexible data analysis

• Quality of information (flexible analysis tools)

Standardized and uniform reporting tool

Performance (ad-hoc) reporting

Analytical services (data mining, and planning)

Data Layer Redundant data storage

Relief of source systems

• Data history

• Performance

Reporting specific data preparation

• Homogenization (data type, currency)

• Cleansing

Compression

Extraction Layer Data provisioning across different source systems

• Integration

The BW server allows you to examine the relationships of data across all areas of your organization. OLAP technology permits multidimensional analyses according to various business perspectives. To support these goals, the architecture of SAP BW in general, and the warehouse component in particular, is well-structured and robust. In the following sections you will get to know the basic architecture of SAP BW, and learn more about the different layers of this architecture.

The SAP Business Warehouse architecture is structured in the following three layers:

• Sourcing the data

• Storing data in the warehouse

• Reporting on the data with reporting tools

When working with the SAP BW you must analyze the following three layers:

• Where the data you need is currently stored

• How you can access this data

• How you can upload it to SAP BW





• How you will store the data in SAP BW

• Which InfoProviders you will need

• Which levels of storage

• How the data is accessed by your power users and end users. (For example, which reporting tools are used)

The figure, SAP BW Three Layers Architecture gives an overview of the three layers of the SAP BW architecture.

d Reporting Tools

JBEx Query

Analytic Engine

DataWarehouse

InfoProviders

DataStoreObjects

InfoCubes

c3> &

MultiProviders

JL'J Characteristic j y 1 InfoObjects

Data Source

SourceSystem Examples SAP ERP Flat File

Figure 5: SAP BW Three Layers Architecture

A source system provides the SAP BW with data. You must distinguish between different types of source systems:

• SAP source systems, for example: SAP ERP, SAP BW, and SAP SCM.

• Non-SAP Sources, for example: databases from different vendors, web services that transfer data, files that hold relevant data.

An advantage of SAP BW is that it has an open architecture with external OLTP providers and other legacy systems. It is possible to connect SAP BW to all possible source systems and to use SAP BW as a consolidated database for reporting that covers the entire organization, particularly in a heterogeneous system landscape. SAP delivers tools that allow these interfaces to be implemented quickly and efficiently.

The figure, SAP BW Source Systems and Staging Technology, gives you an overview of the different source system types that can be connected to SAP BW and outlines the technological interface that is used for the connection and data staging.





Source Systems The following technologies are used to load data to SAP BW:

• Operational Data Provisioning (ODP)

To provide data via the ODP data replication Application Programming Interface (API) from different sources such as, SAP ERP Extractors, SAP BW, SAP HANA Views, SAP Business ByDesign, and SAP Landscape Transformation Replication Server (SLT).

• BW Service API (S-API)

The S-API is a technology package in SAP source systems of BW which facilitates a high level of integration for data transfer from the source systems to SAP BW. It allows for communication between SAP source systems and SAP BW. The S-API is installed on the SAP source system as part of the software component SAP Basis Plug-In.

• DB Connect

Allows relational databases to be accessed directly. DB multi-connect is used to create a connection to the Database Management System (DBMS) in the external database. By importing metadata and original data, the necessary structures can be generated in SAP BW, and the data can be loaded easily and efficiently.

• UD Connect

Using UD Connect, you can access almost all relational data sources. This technology runs on the J2EE Engine and supports the J2EE Connector Architecture.

• File Interface

SAP BW supports automatic import of files in CSV, ASCII, and XLS format for flat files.

• Web Services

Web services permit you to send data to SAP BW under external control.





• SAP Data Services

To use its tight integration when providing data via staging Business Application Programming Interfaces (BAPIs).

• Staging BAPIs

Staging BAPIs are open interfaces, which SAP Data Services and certified third party tools can use to extract data from older systems. The data transfer can be triggered by a request from SAP BW or by SAP Data Services or a third party tool.

Data that is extracted from a source system can be stored, initially, in the Persistent Staging Area (PSA) tables. Next, in most cases, you need to physically and permanently store this data in SAP BW.

For permanent storage, and to be able to access the BW data with reporting tools, you need to create InfoProviders. SAP BW offers a range of InfoProviders for various purposes. Some store data physically, while others provide an additional view of the data.

With transformations you can transform, enrich, and change the data that you extracted from the source system. This may be necessary for special reporting requirements or to harmonize the data of different source systems. The figure, SAP BW Classic InfoProviders gives on overview of the ways in which the different InfoProviders can be used in SAP BW. Each InfoProvider fulfills a separate role, and can be loaded with data from the source systems. The data can be accessed and reported using the SAP BW reporting tools.

Data Warehousing Workbench

(0[CIA]aA_OO3_SC&eTTA_EN 13

© - 4D a ta W arehou sing W orkben ch:

^ m t« <a & qIfiAH----------------- (SO® [

0 F*vorit#s

UflFnd

JB? Hstory

(Mj Data Hows InfoProvider

A P IntoCbjects ^ InfoSources

CP DataSourcas

’ ® Source Systems # Open Hub Destination

9 Warring Sequences 3 SAP HANA Analysis Process

* 8 Process Chens

pert cornection

[ Documents

I « C o n te n t"

f T ra ra la tcn

M etadata Repository

You can access necessary functions via the function areas in the Navigator on

the left.

Scheduling

Monitoring

Figure 7: Data Warehouse Workbench

To perform maintenance and administration tasks for your SAP BW, you need to learn the features and functions of the Data Warehousing Workbench, and how to access them. You also need general navigation skills, such as searching for objects and adding them to your favorites. Knowing how to use the search function and other functions will make working in SAP BW much easier.





The Data Warehousing Workbench (DWB) is the central tool for the Business Warehouse technical professional. This central transaction offers access to the numerous functions and tools that you will use during your everyday work with SAP BW. The transaction code for the Data Warehousing Workbench is RSA1.

You can drag commonly used objects to your

favorites* <1 H

Workbench: Modeling

& (Bl

(HE

• @ Favont« flQFrd

■ &Mstory■ ££ Data Flows

■ InfcfYcMdw• JP InfoObfccts

■ O InfoSources■ CJ? DataSouces

■ 0 Source Systems

■ # Open K ti Destrwticn

■ £1 Flam ng Sequences■ $ SAP HANA Analysis Process

■ 38 Process Chans

[ Transport Correction

Metadata Repository

Jump to the different trees

« EWISIBSISS Q0 lnfcfTovtdet► Busness Information Warehouse► O E-PTocurement Management Model (NW Demo EPM)- O BW T ra rrg

* 4* * Instructor Area• ♦ <*OLp00* LSA++ Case Study* Leoacy Objects (BW7.3)* Costcenter Scermo

" 3 U00 Actual Costs Oetais- N ft SOS UOO_OCO_CM_CCA_9 RK30800 •> AOSO UOO.ADSOA

ElCOrt Centers: Actual Costs Uttno Oefta Extraction)S UOO~OOSVTDDS TRANNGOO > ADSO UOO_ADSOA

ita Transfer Processes \UOO Cost Center Actual Data

0 Cost Center Actual Data from SAP hana \ Costs\CostCenter MD COS view

ostCenter MD COS View DataSource pstCenter TD COS View \stCenter TD COS view assoc.

» TD COS View DataSouce omposite osts

* 3 UOO Open OOS View 7 for Advanced DSO* 3 uoo Open Purchase Orders (InfoCibe)* 3 UOO Purchase Orders (Std.DSO)» 3 UOO PTjrchase Orders (wrtte-opt.)

Tech. Name CBWGD_NW_DEMO_EPMT_BWT_TRAIT€RUCDLSABW730UCD_CC_SCENARIOLOC_ADSOA054V1JBU7WMJYYMM4FZJQ... UOO_OC O_0M_CCA_9 OHT50KAZEOLCW P6LOYH... LCD JD S O ADTP_00O2SCFOF2R.YQCD...DTP_CDO2SOF0F2Pl YR5XZU..LOOJiDSOPUOO.COSVWOOlUCD_COSVMDOSLDO.OOSVTDOlUOO_COSVTDQ2LOO.COSVTDOSUOO.OCPUUOO_CPUUOO_COSTCUD.RESPLCD _ADS07UOO.ADSOlLC D AD S02UCD_ADS03

M.. Execute Fine. O .. C toject In fe r...

0RK3CL9OO

Jump to different functions

InfoCbjects Q InfoCbjects

Figure 8: Data Warehousing Workbench Modeling Function Area

When you open the Data Warehousing Workbench, a navigation pane appears on the left- hand side of the screen. There, you will find the individual function areas of the Data Warehousing Workbench.

The following are the function areas of the DWB:

• Modeling: This is the area where SAP BW objects and data flows are created.

• Administration: This is the area for load scheduling, monitoring, and data administration.

• Transport Connection: This is the specialized transport tool set.

• Documents: This is the central GUI for the maintenance of documents.

• Bl Content: Delivered Bl content can be activated for use.

• Translation: SAP BW object (for example, Queries, InfoCubes) descriptions can be translated for multiple language support.

• Metadata Repository: This is the area where power users and functional experts can find details on delivered and customer objects.

The Modeling function area is used to create and maintain objects that are relevant to the data staging process in the SAP BW. These objects are displayed in a tree structure, where the objects are ordered according to hierarchical criteria. You use context menus to access the relevant maintenance dialogs and functions of each of the objects in the object tree. You will access this area numerous times in the remainder of this course, while performing tasks such as creating InfoObjects, InfoCubes, and DataStoreObjects.





The Documents function area enables you to add documents to SAP BW objects. You can search, and create links between documents in various formats, versions, and languages.

Bl Content provides preconfigured information models based on metadata. You can use these objects in your system directly, or you can revise them. Bl Content enables companies to build data models in SAP BW in a fast prototype way.

In the Translation function area, you can translate the short and long texts that belong to SAP BW objects. For example, it will be much harder for a French person to find a query called Sales Analysis than to find one called Analyse de Ventes.

You use the Metadata Repository as a central point of access to information about the metadata objects of SAP Business Warehouse. This metadata includes important object properties and their relationships with other objects. In the integrated Metadata Repository browser, a search function enables you to access the metadata objects quickly. Other features include exchanging metadata between different systems, exporting HTML pages that list metadata, and displaying graphics for the objects.

E5[CIA]CIA_003_SCHOETTAJN S3

Menu <j © ▼ <i y

Process Chain Display Planning View

4= =$> □ is □ ^ a

Modolnfl___________[ A d m n s tra tc n

• 8 8 Process Chains

• ^ Administration Cockpit

► □ Monitors K ,

• Change Run

• 0 . Broadcasting

• $ 3 Analysis Authorizations

• c ? M etadata Search /D ocum ents

• <>* Migration 3 .x Objects

• 1 $ Remodefing

• S 5 Mass Activation o f BAdI SPOs

• e Analysis o f Bl Objects

• O External SAP HANA view

► Cl Housekeeping Tasks

► Cl Current Settings

* C3M entors;

• B Process Chains

• B Process Chains App

• B b w c c m s

• B L o a d Data

• B SAP HANA Analysis Process

• B Real-Time Data Acquisition

• B Change Run

• B c o p y Data Flow

• 0 Precalculation Server

• B Actrve/Non-Active Data

• Q DataStore Objects

• 3 Workload

• <•? Operational Delta Queue (OOQ)

• /§ ? 8 W Delta Queue

Figure 9: Data Warehousing Workbench Administration Function Area

The Administration function area provides information about the administration and optimal maintenance of your Data Warehouse. It lists the tasks and the corresponding tools and functions, and also refers to additional documentation that you need for the tasks. The Monitoring folder in the administration view enables you to monitor and control data-loading processes and any additional data processing in SAP BW. Here you can monitor everything, including the extraction monitor for incoming data and the open hub monitor for data being sourced from SAP BW to other systems.

Another significant function within the Administration function area is the creation, execution, and monitoring of process chains. This graphical scheduling and monitoring tool allows for complex dependencies between master data and transaction data loading, as well as other complex tasks to be performed in the data warehouse.

An important technical requirement in all SAP products is managing the metadata and configuration settings between your development, testing, and production environments. The

© Copyright. All rights reserved. 13 SAB




transport tools that are generic to all SAP products are enhanced with special functions to support the SAP BW. You use the Transport Connection to collect objects that have recently been created or modified. You use the Change and Transport Organizer (CTO) to transport these objects into other SAP BW systems (for example, from the development box to your quality assurance system box, then on to the productive system).




Unit 1 Exercise 1

Log in to BW and Navigate in the Data Warehousing Workbench

1. Log in to the BW CIA server using the following credentials. If you are already logged in, go to #2.

Field Value

Client 003User user##Password TraininglLogon Language EN

2. Go to the SAP Menu and in the Extras menu, change your settings to display favorites at the end of the list.

3. Display the help for the command field with the FI key. Use the command field to view the RSA1# transaction codes via SE93.

4. Go to the Data Warehousing Workbench via RSA1.

5. Use the icon legend [j[] to view the icon definitions. Use the refresh button for the BW Training InfoArea. Use the search to find the Otct_vcll InfoCube.

6. Set your Navigator and Tree view to hide in the Navigator Settings

Note:This is a clearer and simpler way to navigate in the Data Warehousing Workbench..

7. Display the 0TCT_VC11 InfoCube. Use the Show/Hide Navigator [ □ button to display and then hide the Navigation area and the Tree.

8. In the Source Systems area, go to the plug-in for the RK3CL800 system for the ODP-SAP (Extractors). Use the Customizing Extractors option in the context menu (right click). Return to RSA1.RK3CL800 is the ECC(ERP Central Component) system being used in class.

9. Display the data sources for the RK3CL800 system. Use the Hide/Show Empty Folders button to display your empty group folder. Return to the SAP Easy Access Menu.

© Copyright. All rights reserved. 15 SAR.



Unit 1 Solution 1

Log in to BW and Navigate in the Data Warehousing Workbench

1. Log in to the BW CIA server using the following credentials. If you are already logged in, go to #2.

Field Value

Client 003User user##Password Training!.Logon Language EN

a) Go to Start —» SAP Logon.

b) Highlight the CIA server and enter the provided data.

c) Press Enter.You are on the SAP Easy Access User Menu for USER## screen.

2. Go to the SAP Menu and in the Extras menu, change your settings to display favorites at the end of the list.a) Go to Menu and choose SAP Menu.

You are now on the SAP Easy Access SAP NetWeaver Business Warehouse screen.

b) Go to Extras, and in Settings choose Display Favorites at End of List.

c) Choose Continue ^ .

3. Display the help for the command field with the FI key. Use the command field to view the RSA1# transaction codes via SE93.

a) On the upper left click in the Command Field w | .

b) Choose FI to access the field level help and then close the dialog.

c) In the Command Field, enter /NSE93 and press Enter.

d) Next to Transaction Code enter rsaiYou can see all of the DW Workbench transaction codes.

e) Use the back .button until you reach the Easy Access Menu.

4. Go to the Data Warehousing Workbench via RSAI.





a) Expand Modeling and then double click Data Warehousing Workbench: Modeling.

b) If prompted, select 0 Do not show this question again and choose No.In the Data Warehousing Workbench: Modeling screen, you should be in the Modeling area located on the upper left. InfoProviders should be displayed.

5. Use the icon legend [ j ] to view the icon definitions. Use the refresh button for the BW Training InfoArea. Use the search to find the Otct_vcll InfoCube.

a) Click the Legend buttonThe icon legend appears and you can see the icons for objects such as InfoAreas and InfoCubes.

b) Close the dialog.

c) Highlight the 4 * BW Training InfoArea and click the Refresh button * * ] .

The refresh feature is useful when you are working in different areas of the workbench.

Note:You can also enter /nrsai in the command field to get a refresh as well.

d) Use the lower search button [ jjj to find the Otct_vcll InfoCube.

6 . Set your Navigator and Tree view to hide in the Navigator Settings

Note:This is a clearer and simpler way to navigate in the Data Warehousing Workbench..

a )

b)

c )

On the upper left, click Navigator Settings ^

Select Hide Navigator After Navigation: • Hide Navigator After Navigation

Select Hide Tree After Navigation: • Hide Tree After Navigation

7. Display the 0TCT_VC11 InfoCube. Use the Show/Hide Navigator [X] button to display and then hide the Navigation area and the Tree.a) Double click the 0TCT_VC11 InfoCube.

The definition of the InfoCube is shown in the Display InfoCube screen and the Navigation area and the Tree are hidden.

b) Click the Show/Hide Navigator [ □ button.The Navigation area and the Tree are displayed.

c) Click the Show/Hide Navigator [ □ button again.The Navigation area and the Tree are hidden.

d) Return i to the Data Warehousing Workbench: Modeling.




Education

SAP BW on HANA Materials