Unlock-SEM200 - Business Warehouse for Strategic Enterprise Management

SEM200Business Warehouse for Strategic

Enterprise ManagementmySAP Financials

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 2005 Q2Course Duration: 5 Day(s)Material Number: 50075637

An SAP course - use it to learn, reference it for work

Copyright

Copyright 2005 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. Additionally this publication and its contents are provided solelyfor your use, this publication and its contents may not be rented, transferred or sold without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server areregistered trademarks of Microsoft Corporation.

IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390,AS/400, OS/390, and OS/400 are registered trademarks of IBM Corporation.

ORACLE is a registered trademark of ORACLE Corporation. INFORMIX-OnLine for SAP and INFORMIX Dynamic ServerTM are registered trademarks

of Informix Software Incorporated. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks ofCitrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World WideWeb Consortium, Massachusetts Institute of Technology.

JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP

EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com aretrademarks or registered trademarks of SAP AG in Germany and in several other countries allover the world. All other products mentioned are trademarks or registered trademarks of theirrespective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLYDISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUTLIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT,GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. INNO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL,CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDINGWITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROMTHE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.

About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The following typographicconventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as well asmenu names, paths, and options.

Also used for cross-references to other documentationboth internal (in this documentation) and external (inother locations, such as SAPNet).

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These include reportnames, program names, transaction codes, table names,and individual key words of a programming language,when surrounded by body text, for example SELECTand INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of a program.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2005/Q2 2005 SAP AG. All rights reserved. iii

About This Handbook SEM200

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructorspresentation.

iv 2005 SAP AG. All rights reserved. 2005/Q2

ContentsCourse Overview ...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Course Goals.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiCourse Objectives .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Unit 1: Positioning SEM...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1Overview of SEM and BW... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Unit 2: Data Structures in BW ...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Architecture: SAP-BW .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15InfoObjects and Master Data in BW... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Data Targets and Info Providers .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Data Modelling .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Extractions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Unit 3: Planning with BPS ...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103Planning Design and Architecture .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

Unit 4: SAP-BW Reporting ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147BW Reporting ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148

Unit 5: Retraction..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197Push and Pull Retractions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198

Unit 6: BW- based SEM-BCS...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217Data Model for BW based consolidations .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218Consolidation Process .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239Optional: Reporting... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245

Unit 7: Integration of SEM-CPM ...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265Measure Builder . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266Balanced Scorecard.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279Management Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293

2005/Q2 2005 SAP AG. All rights reserved. v

Contents SEM200

Unit 8: Optional: Authorizations in SEM ...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313Optional: Authorizations in SEM... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314

Appendix 1: Appendix for Exercises ... .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333

vi 2005 SAP AG. All rights reserved. 2005/Q2

Course OverviewThis course is intended to facilitate the understanding of the integration between BWand SEM. Participants will also acquire an understanding of the SEM components.

The information in this course pertains to the following SAP Software Componentsand releases:

SEM/BW Release 4.0

Target AudienceThis course is intended for the following audiences:

Project team members responsible for introducing SEM and BW within theircompany.

Project team members responsible for SEM and BW installation or support. Customers interested in SEM and BW functions. SAP Consultants and SAP_SEM partners.

Course PrerequisitesRequired Knowledge

SAPFIN - MySAP Financials Solutions Overview SEM010 Strategic Enterprise Management

Course GoalsThis course will prepare you to:

Understand the basic concepts of BW. Comprehend the integration between BW and SEM. Gain an overview of SEM components. Understand SEM component integration.

Course ObjectivesAfter completing this course, you will be able to:

Position SEM and BW

2005/Q2 2005 SAP AG. All rights reserved. vii

Course Overview SEM200

Utilize BW for SEM Understand how BW and SEM interact with each other

SAP Software Component InformationThe information in this course pertains to the following SAP Software Componentsand releases:

viii 2005 SAP AG. All rights reserved. 2005/Q2

Unit 1Positioning SEM

Unit OverviewThe start of this course on Business Warehouse (BW) for Strategic EnterpriseManagement (SEM) provides an overview of all SEM applications. The integrationinterfaces between SEM, BW, the R/3 System, and technical dependencies areexplained.

Unit ObjectivesAfter completing this unit, you will be able to:

Explain the functions of Strategic Enterprise Management Describe the advantages of using an integrated system Understand release dependencies between SAP-BW and SAP-SEM

Unit ContentsLesson: Overview of SEM and BW.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

2005/Q2 2005 SAP AG. All rights reserved. 1

Unit 1: Positioning SEM SEM200

Lesson: Overview of SEM and BW

Lesson OverviewIn this lesson we will learn about the applications in SEM and the integration linkswithin SEM and BW. We will also discuss the release dependencies between SEMand BW.

Lesson ObjectivesAfter completing this lesson, you will be able to:

Explain the functions of Strategic Enterprise Management Describe the advantages of using an integrated system Understand release dependencies between SAP-BW and SAP-SEM

Business Example You are on the SAP-SEM implementation team and want to start by positioning

SEM functions. You also want to position SAP-SEM in comparison to otherSAP solutions.

In addition, you want to find out about integration between SAP-SEM andSAP-BW, and understand release dependencies between BW and SEM.

2 2005 SAP AG. All rights reserved. 2005/Q2

SEM200 Lesson: Overview of SEM and BW

Figure 1: SAP Strategic Enterprise Management

Strategy Management using the Balanced Scorecard (SEM-BSC) and PerformanceMeasurement using theManagement Cockpit (SEM-MC). The Balanced Scorecardis designed as both a conceptual and maintenance tool with a graphical interface. Aswell as goals and subgoals, it uses critical success factors to measure achievementof targets. The Management Cockpit is an additional tool for use by CFOs duringmeetings enabling ergonomic reports on critical success factors to be generated. Italso enables you to create online simulations provides instant checking of objectivedeviation. The Measure Builder is an essential tool for those wanting to workwith the Balanced Scorecard and Management Cockpit. It comprises a catalog ofgroup-wide critical success factors and, technically speaking, is the integration toolfor SEM-CPM components.

BPS can be used for both operational and strategic planning. It can be used to createa representation of the entire company. You can then use it to carry out simulationsand monitor how this influences company success. If the planning is integrated withBalanced Scorecard, reports can be generated on any changes to critical successfactors as a result of alternating plans.

SEM-BCS also provides consolidated actual data on the source system. This includeslegal and management consolidation. Consolidation of planning data is also possible.



Figure 2: Performance Monitoring Using the Balanced Scorecard and theManagement Cockpit

The above graphic shows critical success factors saved in the Balanced Scorecard andManagement Cockpit. These can be used to control the success of a company.

See Unit 7 for further information, especially how to integrate critical success factorsinto SEM-BSC and SEM-MC.



Figure 3: Modeling an Integrated Overall Plan

Working with SEM-BPS enables you to take an integrated view of various planningareas.

The main advantage of planning with SEM-BPS is that you can create a cause-effectchain between the different profitability views, a function that is not available in theSAP system. You can also define the granularity of the plan as you wish.

Once you have built up these cause-effect chains, we can start to talk about a BusinessPlan, an integrated plan that demonstrates how success can best be acheived infinancial terms. This makes it possible to plan revenue as part of sales planning forexample (income statement view), then from the net sales deduce the receivables forthe financial statement view. From receivables, you then identify cash inflows. This isknown as the liquidity view. This holistic approach is not possible in the SAP system.Here, data for the different views is always reported separately for each application.



Figure 4: Integrated SEM-Data Basis

Installation of an SAP-BW Business Information Warehouse is essential to be ableto work with SAP-SEM. BW provides the technical infrastructure for data storage andreporting for all SEM-functions in the form of characteristics and key figures.

Different SAP-BW data stores can be used for the different SEM functions.SEM-BPS (planning) works with InfoCube type data stores whereas SEM-BCS(consolidation) uses InfoCubes for updating totals records, but ODS objects forupdating elimination documents for instance. Data for SEM-CPM (CorporatePerformance Monitor) uses BW reporting functionality data from differentInfoProviders via Multiproviders.

The above graphic explains the use of key figures in BW and SEM.

Key figures in BW having values like Revenue = 10 EUR. A key figure that isphysically present in a BW InfoCube, for example, the revenue key figure, is knownas a basic key figure. SEM-BPS and SEM-BCS can only relate to basic key figures.

Data is gathered using queries for which further key figure types can be created.The values of these are not contained physically in the data store, but deduced bycalculation and displayed at query run time.

Any values created by calculated key figures, restricted key figures or structuresat run time can only be used by SEM-CPM however.



Figure 5: Integrated Planning 1/2

Using BPS, you can model across InfoCubes. To do this you can use themulti-planning areas technique.

The above diagram shows how integration works and the basic modelling process inBPS.

The multi-planning areas technique is also demonstrated in more detail in a later unit.At this point it only intended to position this technique roughly.



Figure 6: Integrated Planning 2/2

The above diagram demonstrates integration between BPS and the SAP system. Thescenario starts with the extraction of current manufacturing costs. Sales quantity andrevenue are planned in BPS. A contribution margin scheme can also be created inBPS. In the end, sales volume and revenue planned in BPS are retracted to the costbased CO-PA, which sets off a reaction in the operative system. Details are thenadded in CO-PA, such as SD conditions, CO-PA conditions and a cost element schemafor product calculation. No BW extractors are provided for customizing conditionsand the cost element schema. If customers do want to view these amounts in BW andSEM however, absolute maximums for these can be extracted using CO-PA extractors.You can also write your own extractor to transfer customizing information from theSAP system to BW.

If sales volume is retracted to CO-PA, plan integration in the SAP system starts up.This means sales volume is transferred to SOP (Sales and Operations Planning) bymeans of an acquisition report to give the production quantity. This can also be usedto provide scheduled resource quantities for bills of labor and bills material. Activityquantities are passed on to cost center accounting. The cost centers then determinetheir planned activity quantities. Before activity prices are determined, differencesbetween planned vs. Scheduled activity quantities must be resolved.



Another calculation process now starts up to determine the new manufacturing costs.Another extraction to BW provides an up-to-date contribution margin in BPS. You canalso perform a new evaluation in cost based CO-PA, whereby the contribution marginscheme is compared in the SAP system, based on the updated manufacturing costs.

Figure 7: BW and SEM Technical Dependencies

SAP-BW is part of the standard SAP-SEM package. There are three possibility forinstallation:

Using a local BW system: SAP-BW and SAP-SEM are installed on the samelogical system. In this case it is essential that the release dependencies described inthe above graphic are maintained. If you want to upgrade the SEM system in thisscenario, the local BW must first be upgraded before SEM is upgraded to maintainthe release combination. Otherwise BW cannot be used locally. Either the BWsystem supplied with SAP-SEM or a BW system already in existence in a companycan be used as the local BW system. You must keep to the release dependenciesdescribed above when using an existing BW system however. This enables SEMto be connected as an add-on.

Customers already in possession of one or more BW systems (known as externalBW systems) who want to use SEM as an add-on, will usually have to connectboth systems together using RFC destinations. In this case the BW-SEM releasedependency is less restrictive than in the local scenario. Note that in such cases, anSEM release can only be connected with a BW release that is just as high or lower(see graphic above). For example, SEM 3.5 will function with an external BW 3.3or lower but not with external BW 3.5.



Lesson Summary

You should now be able to: Explain the functions of Strategic Enterprise Management Describe the advantages of using an integrated system Understand release dependencies between SAP-BW and SAP-SEM


SEM200 Unit Summary

Unit SummaryYou should now be able to: Explain the functions of Strategic Enterprise Management Describe the advantages of using an integrated system Understand release dependencies between SAP-BW and SAP-SEM


Unit Summary SEM200


Unit 2Data Structures in BW

Unit OverviewIn this unit we will begin by understanding the SAP-BW architecture with an emphasison BW terminology. We will discuss the delivered Business Content as well asunderstand the importance of InfoObjects and how they are used. We will look at howto extract master data in the form of text, attributes and hierarchies. We will studythe the administration of an Infocube and explain the basic procedure for creatingmulti-dimensional data models. An extraction of transaction data from R/3 to BW willalso be executed.

Unit ObjectivesAfter completing this unit, you will be able to:

Understand how SAP-BW is structured Explain the functions of the Adminstrator Workbench Explain master data in the form of attributes, texts and hierarchies Explain the basic process for defining and managing both basic and transactional

InfoCubes Understand the importance of InfoObjects and how they are created Understand how to extract master data in the form of attributes and texts from

SAP systems Understand the procedure for extracting hierarchies using CO-PA as an example Understand the differences between data modeling for planning and reporting Understand essential information regarding the administration of an InfoCube Explain the basic procedure for creating a multi-dimensional data model Understand the concept of data modeling in SAP-BW with reference to

SAP-SEM As well as the different steps involved in data modeling And distinguish between key figures and account modeling of InfoCubes Understand the extraction of transaction data based on various scenarios


Unit 2: Data Structures in BW SEM200

Unit ContentsLesson: Architecture: SAP-BW .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Lesson: InfoObjects and Master Data in BW... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Exercise 1: InfoObjects and Master Data in BW ... . . . . . . . . . . . . . . . . . . . . . . . . . 29Lesson: Data Targets and Info Providers .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Lesson: Data Modelling .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Exercise 2: Data Modelling... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Lesson: Extractions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Exercise 3: Extraction... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79


SEM200 Lesson: Architecture: SAP-BW

Lesson: Architecture: SAP-BW

Lesson OverviewIn this lesson we will learn about the SAP-BW architecture and SAP deliveredbusiness content.


Understand how SAP-BW is structured Explain the functions of the Adminstrator Workbench Explain master data in the form of attributes, texts and hierarchies Explain the basic process for defining and managing both basic and transactional

InfoCubes

Business Example You are on the SAP-SEM implementation team and want to understand how the

SEM-based BW system works to get an idea of the SAP-SEM and SAP-BWintegrated modeling concept.

You also have a special interest in the structure of the data model and methods ofextracting master and transaction data from source systems.



Figure 8: Architecture: SAP-BW

The SAP Business Information Warehouse stores and displays data from aheterogenous system landscape in a highly flexible uniform evaluationenvironment that is optimized for specific user requirements.

This consists of three levels: The extraction level, which is the source systems levelfrom which data is extracted (or loaded) to the BW system. This may be informationon SAP products (such as the SAP system) or other source systems, or flat files. Thesecond level is the BW server, where data is saved in its appropriate data stores suchas InfoCubes for aggregated data or ODS-Objects for document level detail. Thethird level is the reporting level, which you can use to view data either in an Excelenvironment using Business Explorer or as a web application using a web browser.You can also use an interface to transfer data to third-party products.

The Administrator Workbench is the central access point for creating and managingdata structures, incorporating source systems, defining rules necessary for data transferfrom source systems and initiating extraction procedures.

BW includes a wealth of Business Content consisting of pre-programmed andoptimized data structures for a wide variety of applications and processes.



Figure 9: Architecture: SAP-BW and SAP-SEM

SEM functions are designed to simply add on to SAP-BW.

Two types of interface are generally used for this purpose:

SEM-BPS and SEM-BCS each use read-write interfaces. In the case of SEM-BPS,this is addressed using manual layouts or planning functions. SEM-BCS uses aninterface that can also write data to BW using flexible upload but, unlike the BPSinterface, can also transfer to ODS objects.

SEM-CPM uses the OLE DB for OLAP interface. This is a read-only interface.



Figure 10: Delivered Business Content

The SAP-BW Business Content makes available predefined information structures.These include extractors, DataSources, InfoObjects, InfoProviders, queries, templatesund roles.

Customers can use the standard delivered Business Content or adapt this to suit theirown personal needs. Example data is also available for presentation purposes.

Using Business Content reduces the amount of implementation time required to useBW. The Business Content continues to grow with each new release. InfoCubesdelivered as standard are optimized for performance beforehand.

SAP-BW Business Content is structured in hierarchies and can be activated fromany hierarchy level. You can also activate, copy and adapt each individual elementseparately. Examples of content available include mySAP CRM, mySAP SRM,mySAP SCM, mySAP PLM, mySAP Financials and mySAP Human Ressources.

There are also industry-specific structures for aerospace & defence, the publicsector, automotive and chemical industries, consumer products, banking, healthcare,insurance, media, pharmaceuticals and many more.

You should note when activating Business Content that there is an underlyingobject-version concept. (D = delivered version; M = modified version; A = activeversion). In some cases it will be necessary to carry out a comparison procedurewith existing structures.



You can make comparisons at http://help.sap.com/ SAP NetWeaver SAPBusiness Information Warehouse.

Figure 11: Activating Business Content

You need to follow several steps to activate Business Content.

First of all it is worth checking in theMetadata Repository to see which contentobjects are available. This contains descriptions of all BW data structures.

Then you need to specify which objects are to be activated.



You set the various structures for activation by clicking the Grouping button. Fourvariants are available:

Required objects only: Each selected object is activated, together with thedata structures necessary for the object's existence. For example: You want toactivate a query. The system proposes activating the corresponding InfoCubeas a necessary object as well.

In Data Flow Before: All objects located before the object selected in the dataflow are automatically collected and proposed for activation. For example:You want to activate a query. The system proposes activating update rules andInfoSources as well as the necessary objects.

In Data Flow Afterwards: All objects located after the selected object areautomatically collected and proposed for activation. For example: You want toactivate a query. The system proposes activating workbooks and roles as well asthe necessary objects.

In Data Flow Before and Aftrwds: All structures located before and after theselected object in the data flow are collected and proposed for activation aswell as the necessary objects.

You can now activate all objects that have been selected and proposed for activation.You can carry out a simulation first. For objects already active from an earlier contentversion, you should carry out a comparison of modified settings.



Lesson Summary

You should now be able to: Understand how SAP-BW is structured Explain the functions of the Adminstrator Workbench Explain master data in the form of attributes, texts and hierarchies Explain the basic process for defining and managing both basic and transactional

InfoCubes



Lesson: InfoObjects and Master Data in BW

Lesson OverviewIn this lesson we will learn about InfoObjects that are referred to as characteristics andkey figures. We will evaluate the different types of InfoObjects in BW. We will alsolearn about extractions, including master data and transactional data.


Understand the importance of InfoObjects and how they are created Understand how to extract master data in the form of attributes and texts from

SAP systems Understand the procedure for extracting hierarchies using CO-PA as an example

Business ExampleYou are on the SAP-SEM and BW project teams and you need to know aboutInfoObjects and executing extractions. You know that InfoObjects contain allinformation on master and transaction data. You now need to decide which ones youwill require for your organization. You also need to know about the BW extractionstructure that needs to be created in order to load the different types of data yourequire to execute your queries.


SEM200 Lesson: InfoObjects and Master Data in BW

Figure 12: InfoObjects

InfoObjects are the smallest unit of information in BW. They contain all informationon master and transaction data and are used throughout the system, to set up databasesand structures. Technical names for user-defined InfoObjects must start with a letterand have a maximum of nine characters. Generally speaking, there are two types ofInfoObjects: Characteristics and key figures.

Characteristics cannot hold any transaction data. They describe the master datastructure for transaction data, that is, the organizational unit, the material, and periodfor the corresponding transaction data, and the currency or unit used. In the example,the division characteristic consists of the values plastic, ceramic, glass. Keyfigure InfoObjects contain transaction data values in data stores, for example, inthe InfoCube.

You can assign other characteristics or key figures to a characteristic in the form ofattributes, provided these characteristics or key figures provide further details on thereference characteristic. These provide additional explanatory information. Examplesof attributes for the cost center characteristic include person responsible or profitcenter. The net weight key figure could be assigned as an attribute to the materialcharacteristic. If you want to assign attributes, you must select theWith Master Datafield in InfoObject maintenance. You can also use display attributes in SEM-BPS.



Characteristics can also use hierarchies, which can be created manually or extracted.Hierarchies can be version- or time-dependent and are stored in their own hierarchytables. Hierarchies cannot have more than 98 levels and are used in different SEMapplications as well as in BW reports.

When characteristics are compounded, certain dependencies are fixed. For example,it is possible to create cost center 1234 for different controlling areas. This means thatwhen storing and evaluating data, a controlling area must always be specified to makeit clear which cost center is to be selected.

Figure 13: Master Data Extraction 1/2: Attributes and Texts

You need to install a suitable SAP system plug-in in the source system to loaddata. SAP system plug-ins are interfaces enabling data transfer between one or moreSAP systems and other SAP products such as BW or CRM. SAP system plug-insare add-ons to the SAP system.

For more information on SAP System Plug-Ins, go to the SAP Service Marketplace:http://service.sap.com/BW SAP BW Extractors Plug-In.

See also SAP note 181255 (overview note on SAP system plug-ins) and 214503(release strategy for SAP system plug-ins).

Master data is generally uploaded using a full update.



DataSources are used to transfer master and transaction data and use field structuresto describe the data range of a source system. The extraction structure containsall source system fields made available by extractors. Extractors are programs forgathering data from source systems. One data source for master data must be createdfor each characteristic.

This DataSource and its underlying extract structure are made known to BW by aprocess of replication. Once this replication process has been completed, the fieldsare contained in the BW Transfer Structure.

An InfoSource is a group of associated InfoObjects that contains all existinginformation on a particular business process. We call the technical structure onwhich the InfoSource is based the communication structure. Unlike the transferstructure described below, the communication structure is not dependent on thesource system, as the structure can be fed by a variety of source systems. Note thatonly one InfoSource can be assigned for each source system of a DataSource.

Figure 14: Master Data Extraction 2/2: Attributes and Texts

You use transfer rules to determine which InfoObjects of the communicationstructure are filled, and from which fields of the transfer structure and whichmethods should be used to do this.

As part of transfer structure maintenance in BW, you need to determine whichfields of the extraction structure are to be transferred to BWby assigning aDataSource and InfoSource. At data upload, data is transferred to the BW transfer



structure 1:1 from the source system transfer structure, and then transferred to the BWcommunication structure using transfer rules. A distinction is made here betweenDataSources for transaction data and DataSources for master data (attributes,texts, and hierarchies).

There are two types of InfoSources:

InfoSources with direct update

For this type, an InfoSource is created for a characteristic and the systemgenerates the communication structure automatically. The user only needs todefine the transfer structure and transfer rules. Master data attributes and textsare extracted separately for this type.

InfoSources with flexible update

For this type, the user must maintain the communication structure, transferstructure and transfer rules him or herself. You can extract attributes and textsfrom master data in one step, however. If you have different data sources andwish to merge the information you can use a flexible InfoSource structure. Youmust use flexible upload for transaction data.

An InfoPackage defines conditions for data requests from a source system, forexample, selection conditions, start conditions, data update options and error handlingtypes. InfoPackages can be combined using the process chain.

Figure 15: Extraction of Hierarchies CO-PA-Hierarchies



SAP system plug-ins can be used as extraction modules, to extract a range ofhierarchies from SAP systems. These include cost center and cost element accountinghierarchies from the SAP CO system, GL accounts hierarchies from the SAP FIsystem, customer hierarchies from the SAP SD system or materials hierarchies fromthe SAP MM system.

Use transaction sbiw to create a DataSource for CO-PA hierarchies in the SAP system.Then navigate as follows: Data Transfer to the SAP Business Information Warehouse Settings for Application-Specific DataSources (PI Basis) Profitability Analysis Create Hierarchy DataSource.

The extraction procedure for CO-PA hierarchies is generally the same as for uploadingattributes and texts. The DataSource for hierarchies is replicated to the BW systemand assigned to the existing InfoSource from previous attribute and text uploads.You can determine which hierarchy should be extracted for your characteristic in theInfoPackage.



Exercise 1: InfoObjects and Master Data inBW

Exercise ObjectivesAfter completing this exercise, you will be able to: Create InfoObjects and assign them to your info catalogue Understand how to extract master data into BW

Business ExampleThe Senior Management team is interested in reporting results using differentcharacteristics and key figures, specifically revenues by customers. These InfoObjectsneed to be created by the BW consulting team.

Task 1:The objective of the following exercise is to use template objects to create twoInfoObjects: a Z_CUSTY## characteristic and Z_REVY## key figure. BothInfoObjects will be used later in the multi-dimensional data model.

Hint: In technical InfoObject names, Y stands for your group numberand ## stands for your terminal number.

1. Log on for training in English and go to the local BW system of your SEMsystem.

2. Create one InfoObject Catalog for the characteristic and one for the keyfigure in the InfoArea by selecting Training BW for SEM InfoAreaSEM200_Training_Rel_40.

Define the catalog for SEM200C_Y## characteristics using YXX SEM200Characteristics.

Technical name of catalog: SEM200C_Y##Description of catalog: Y## SEM200 Characteristics

Activate the InfoCube.

Repeat the procedure to construct a key figure catalog for the InfoArea.

Continued on next page



Technical name of catalog: SEM200K_Y##Description of catalog: Y## SEM200 Key Figures

Activate this catalog as well.

3. Now create the key figure Z_REVY## with the description Y## Revenue inyour SEM200K_Y## key figure catalog.

Use the key figure with the technical name 0G_AVV010 as a template(description for Revenue template key figure).

Check the key figure you have created with respect to the following:

What is the underlying data type for the key figure?

How many decimal places have been set as default?

Task 2:Your task is to carry out a master data upload for a Y## Customer characteristicthat you have defined. You must first create the characteristic using a templatecharacteristic. Now load the master data information from the KNA1 customer masterdata table of the SAP System.

1. In your characteristic catalog, create the characteristic Z_CUSTY## with thedescription Y## Customer. Use z_cust00 as a template characteristic. Activatethe characteristic.

Within the characteristic you have created, clickMaintain to check that nocharacteristic values exist for the characteristic you have copied. On theHierarchies tab, verify that hierarchies are permitted for this characteristic. Onthe Attributes tab, check which attributes are assigned to this characteristic.

2. First, define an InfoSource, then create three DataSources for this (attributes,texts, hierarchy).

Create the InfoSource for the BW Application Components for SEM ApplicationComponents.

When defining the InfoSource, choose Direct update of master data. Choosethe Z_CUSTY## characteristic that you have created.

3. Now define a data source for the source system to extract characteristic valuesand attributes from the KNA1 customer master table in the source system for theSAP source system. Use the technical name T90CLNT090.




Enter Customizing Extractors in the connected SAP system using this sourcesystem and define a generic DataSource for theMasterData Attributes variant.

Enter Z_CUSTY##_A as the technical name for the DataSource.

Applic.Component:

CO-PA-IO (Meaning: CO-PA master data)

View/Table: KNA1 (Customer Master Table in SAP system)

Short description: Y## Customer AttributeMediumdescription:

Y## Customer Attribute

Long description: Y## Customer Attribute

Hint: If the system prompts you for a development class, select LocalObject.

If asked about a Transport Workbench request, click the Create buttonto create one.

Select the Customer Number 1 field.

Your DataSource is now defined for loading character values and attributes inthe SAP system.

Hint: If you are prompted to enter a Workbench request number in anyof the following exercises, create a new request. If you are prompted toenter a development class, create the local objects development class.

Hint: The DataSource you create is replicatd once-off by your trainer.Notify your trainer once you have created the DataSource, so that s/hecan start the run for all groups.




Task 3:After the replication run has been completed, search for your DataSourceZ_CUSTY##_A under DataSource Overview on the Source Systems area. The easiestway to do this is to use the search function.

1. You must assign the replicated Z_CUSTY##_A DataSource to the Z_CUSTY##InfoSource that you created at the beginning and then maintain the transfer rules.Store the mapping record for the SAP field KUNNR with your Z_CUSTY##InfoObject.

First, select the replicated Z_CUSTY##_A DataSource, then assign yourZ_CUSTY## InfoSource for the Others variant.

Activate the InfoSource once the characteristics have been assigned.

2. Now go toModeling InfoSources to your Z_CUSTY## InfoSource and createan InfoPackage to extract attributes for your source system with the technicalname T90CLNT090.

Perform an upload for customers no. 1000 to 2500.

3. From the InfoPackage, go toMonitor and click the Configure Tree icon. Dragand drop the Person Responsible icon to theMonitor icon to check whether theupload for your group was successful. Click Transfer to confirm your selection.

Use theMaster Data fast entry, to view the extracted master data.

Task 4:Next upload the texts to the Z_CUSTY## characteristic.

The procedure is the same as for uploading attributes.

1. Return to Customizing Extractors for your source system using the technicalname T90CLNT090 and define a generic DataSource of type Texts. Thetechnical name for this DataSource is Z_CUSTY##_T. Enter Y## CustomerTexts as the description.

Enter the same information as in Exercise 2-3 and follow the same procedure.


2. Go to the InfoSources area and, using the search function, search for yourZ_CUSTY## InfoSource.




Select your InfoSource Z_CUSTY## and assign it your DataSource from theT90CLNT090 source system.

Your Z_CUSTY##_T DataSource will then appear for selection.

Assign the field 0TXTMD field NAME1. This field may appear by default.

Activate your entries.

3. Finally create an InfoPackage Z_CUSTY##_T again with the technical nameT90CLNT090 for your InfoSource T_CUSTY##_T and your source system.


Go to the Monitor. Once the upload has been completed, click Texts, andnavigate to the table for the Z_CUSTY## characteristic. The final Descriptioncolumn should now be filled.

Task 5:Finally, extract an external hierarchy from the CO-PA to the BW.

1. Go to your T90CLNT090 source system and then to Customizing Extractorsand open a second mode. Using transaction KES3, go to Hierarchy Version100 for the CO-PA Customer characteristic. Select IDEA and the CostingBased option.

2. Define a DataSource for CO-PA hierarchies and enter the following data:

(P_DS) Name of DataSource: 0CO_CO_HIER_Z_CUSTY##_H(P_DP) Description: Y## Hierarchy(P_CH) InfoObject: Z_CUSTY##(P_C1) CO-PA

characteristic:KNDNR

Select the local development class.





3.

Hint: The DataSource you create is replicatd once-off by your trainer.Notify your trainer once you have created the DataSource, so that s/hecan start the run for all groups. For hierarchies, the replication is carriedout for the CO-PA-IO node of the application component hierarchy andnot for the CO-PA node.

4. Search for and select your replicated DataSource0CO_PA_HIER_Z_CUSTY##_H. Assign you InfoSourceZ_CUSTY## under the Others option. Select Yes to confirm the assignment.Enter Z_CUSTY## in the InfoObjects field. Carry out the search as normal.

5. Now create a Z_CUSTY##_H InfoPackage for your Z_CUSTY## InfoSourceand T90CLNT090 source system and start the upload.



Solution 1: InfoObjects and Master Data inBWTask 1:The objective of the following exercise is to use template objects to create twoInfoObjects: a Z_CUSTY## characteristic and Z_REVY## key figure. BothInfoObjects will be used later in the multi-dimensional data model.


1. Log on for training in English and go to the local BW system of your SEMsystem.

a) Business Information Warehouse Modeling AdministratorWorkbench: Modeling

Double-click Local BW System to start the training.

2. Create one InfoObject Catalog for the characteristic and one for the keyfigure in the InfoArea by selecting Training BW for SEM InfoAreaSEM200_Training_Rel_40.

Define the catalog for SEM200C_Y## characteristics using YXX SEM200Characteristics.

Technical name of catalog: SEM200C_Y##Description of catalog: Y## SEM200 Characteristics

Activate the InfoCube.

Repeat the procedure to construct a key figure catalog for the InfoArea.

Technical name of catalog: SEM200K_Y##Description of catalog: Y## SEM200 Key Figures




Activate this catalog as well.

a) You should now find yourself in Administrator Workbench. SelectModelingInfoObjects.

Position your cursor on the InfoObjects node, and select the Findin Subtree icon. Enter SEM200_Training_Rel40 in the SearchFor field.

Now click FIND. Select the found InfoArea. Now click the Expand andPosition button.

Next select the InfoArea (topic nodes have two green squares). Open thecontext menu with the right mouse button and select Create Info ObjectCatalog.

In the first available field in the InfoObjCat line, enter the technicalname SEM200C_Y##. In the second field, after InfoObjCat, enter Y##SEM200 Characteristics.

Choose the Char option (Characteristics) for the InfoObject Type field.

Click the Create icon to go to the catalog. Click Activate to activatethe catalog.

Click Back to return to the previous screen.

3. Now create the key figure Z_REVY## with the description Y## Revenue inyour SEM200K_Y## key figure catalog.

Use the key figure with the technical name 0G_AVV010 as a template(description for Revenue template key figure).

Check the key figure you have created with respect to the following:

What is the underlying data type for the key figure?




How many decimal places have been set as default?

a) Select your SEM200_KY## key figure catalog, right-click the catalog andselect Create InfoObject.

In the Key Fig field, enter the technical name Z_REVY##.

Enter Y## Revenue in Long description.

In the Template field, enter 0G_AVV010 as the technical name of thetemplate key figure.

Click the Continue icon to open the master record.

Type/DataType: AmountDataType: CurrDecimal Places: Select Activate to activate the key figure and

then choose Exit to go to the higher-levelscreen.

Task 2:Your task is to carry out a master data upload for a Y## Customer characteristicthat you have defined. You must first create the characteristic using a templatecharacteristic. Now load the master data information from the KNA1 customer masterdata table of the SAP System.

1. In your characteristic catalog, create the characteristic Z_CUSTY## with thedescription Y## Customer. Use z_cust00 as a template characteristic. Activatethe characteristic.




Within the characteristic you have created, clickMaintain to check that nocharacteristic values exist for the characteristic you have copied. On theHierarchies tab, verify that hierarchies are permitted for this characteristic. Onthe Attributes tab, check which attributes are assigned to this characteristic.

a) Select and right-click your SEM200_Y## Characteristics catalog andthen select Create InfoObject.

Enter the technical name Z_CUSTY## in the Char field.

In the Long description field, enter Y## Customer.

In the template field, enter the characteristic Z_CUST00.

Click Continue.

Click the Activate icon to activate your characteristic.

b) Activate theMaintain Master Data icon within your master record.

Then click the Execute icon and ensure no characteristic values areavailable for this characteristic.

Double-click the Exit icon to go back to the master record for yourcharacteristic.

Go to the Hierarchy tab and make sure that that with hierarchies isselected.

The Attributes tab shows a list of attributes for the characteristic.

Click the Exit icon to exit master data maintenance.

2. First, define an InfoSource, then create three DataSources for this (attributes,texts, hierarchy).

Create the InfoSource for the BW Application Components for SEM ApplicationComponents.




When defining the InfoSource, choose Direct update of master data. Choosethe Z_CUSTY## characteristic that you have created.

a) In theModeling area select InfoSources. Select the InfoSources node andclick the Find in Subtree (binoculars).

In the Search for field, enterBW for SEMApplication Components.Thenclick Find.

Position the cursor over the entry when it is found and single click.

Right-click the application components that have been found and selectCreate InfoSource.

Select the Direct Update of Master Data variant and in the InfoObjectfield, store your Z_CUSTY## characteristic.

Click the Transfer icon. In the prompt that appears, click the Continueicon.

3. Now define a data source for the source system to extract characteristic valuesand attributes from the KNA1 customer master table in the source system for theSAP source system. Use the technical name T90CLNT090.

Enter Customizing Extractors in the connected SAP system using this sourcesystem and define a generic DataSource for theMasterData Attributes variant.

Enter Z_CUSTY##_A as the technical name for the DataSource.

Applic.Component:

CO-PA-IO (Meaning: CO-PA master data)

View/Table: KNA1 (Customer Master Table in SAP system)

Short description: Y## Customer AttributeMediumdescription:

Y## Customer Attribute

Long description: Y## Customer Attribute

Hint: If the system prompts you for a development class, select LocalObject.

If asked about a Transport Workbench request, click the Create buttonto create one.

Select the Customer Number 1 field.




Your DataSource is now defined for loading character values and attributes inthe SAP system.

Hint: If you are prompted to enter a Workbench request number in anyof the following exercises, create a new request. If you are prompted toenter a development class, create the local objects development class.


a) In theModeling area, select Source Systems.Select the source systemT90CLNT090.

Right-click to open the context menu, and select Customizing for theExtractors.

In the SAP system, go to DataSource master data maintenance by selectingGeneric DataSources and thenMaintain Generic DataSources.

SelectMasterData Attributes. Enter Z_CUSTY##_A as the technicalname for the DataSource (A stands for attribute). SelectCreate, andenter the following:

Applic. Component: CO-PA-IO (Meaning: CO-PA master data)View/Table: KNA1 (Customer Master Table in SAP system)Short description: Y## Cust AttributeMedium description: Y## Customer AttributeLong description: Y## Customer Attribute

Then click the Save icon to save your DataSource.

On the next screen, select Customer number 1 in the Selection column.

This enables you to restrict the loading procedure to individual customernumbers later on when starting the extraction. Save your entries. SelectBack three times to return to the BW screen.




Task 3:After the replication run has been completed, search for your DataSourceZ_CUSTY##_A under DataSource Overview on the Source Systems area. The easiestway to do this is to use the search function.

1. You must assign the replicated Z_CUSTY##_A DataSource to the Z_CUSTY##InfoSource that you created at the beginning and then maintain the transfer rules.Store the mapping record for the SAP field KUNNR with your Z_CUSTY##InfoObject.

First, select the replicated Z_CUSTY##_A DataSource, then assign yourZ_CUSTY## InfoSource for the Others variant.

Activate the InfoSource once the characteristics have been assigned.

a) Select the DataSource Z_CUSTY##_A that has just been replicated.Right-click the mouse to open the context menu, and choose AssignInfoSource.

A window appears. Select Others, and enter the Z_CUSTY##InfoSource in the appropriate entry field. Select Transfer.

When prompted to save the assignment, choose Yes.

Now maintain the transfer rules on the following screen.

On the TransferRules tab, enter the Z_CUSTY## InfoObject in theTransfer_Structure/Transfer_Rule section under the Assign Inf.Objct.field for the KUNNR field, and select Transfer in Transfer Rule, orselect Enter.

Hint: A yellow symbol should now appear in place of the red crossunder Transfer rules for the field Z_CUSTY##. This indicatesthat a transfer rule for the original SAP field has been found.

Note that a transfer rule is not maintained for each field, as theindicator light for the InfoSource as a whole will remain yellow asa result.

Click Activate to activate your InfoSource by.

Select EXIT to close InfoSource maintenance.

2. Now go toModeling InfoSources to your Z_CUSTY## InfoSource and createan InfoPackage to extract attributes for your source system with the technicalname T90CLNT090.





a) UnderModeling select InfoSources. In the InfoSource structure, selectthe top node. Choose Find in Subtree, and search for the InfoSourceZ_CUSTY##. (This procedure has already been described above).

Below this InfoSource, you will found a sub-icon that represents yoursource system and the assigned DataSource.

Select this system,right-click the mouse to open the context menu, thenchoose Create InfoPackage.

In the InfoPackage Description field, enter the technical nameZ_CUSTY##_A.

Select your DataSource Z_CUSTY##_A. This is indicated by two greensquares in parentheses. Click the Save icon to go to the InfoPackage.

On the Data Selection tab, enter the customer number 1000 in the FromValue field and 2500 in the To Value field.

Check the different tabs without changing any settings. Got to the Scheduletab, and start the upload by selecting Execute;Schedule (Start).

3. From the InfoPackage, go toMonitor and click the Configure Tree icon. Dragand drop the Person Responsible icon to theMonitor icon to check whether theupload for your group was successful. Click Transfer to confirm your selection.




Use theMaster Data fast entry, to view the extracted master data.

a) You should now be n the InfoPackage. ClickMonitor.

In the Monitor, click Configure Tree.

You should now see a worklist of the icons on the right hand side of thescreen.

Select the Person Responsible icon and move this to the Monitor icon.Now click Transfer.

Open the Detail tab and answer any questions that appear with Yes.

When the indicator light is entirely green, the upload has beensuccessful.

If the process takes a little longer, click the Refresh Requests symbol.

From the Master Data icon, go to master data maintenance and clickExecute in the template window that appears without any furtherrestrictions. Check that the characteristic values are contained in the table.

Hint: Check nothing is contained in the final column, Descript.The descriptions should only be filled once texts have beenuploaded.

Select the Exit icon four times to leave the screen.

Task 4:Next upload the texts to the Z_CUSTY## characteristic.

The procedure is the same as for uploading attributes.

1. Return to Customizing Extractors for your source system using the technicalname T90CLNT090 and define a generic DataSource of type Texts. Thetechnical name for this DataSource is Z_CUSTY##_T. Enter Y## CustomerTexts as the description.




Enter the same information as in Exercise 2-3 and follow the same procedure.


a) In theModeling area, select Source Systems. Select T90CLNT090 asyour source system.

Right-click to open the context menu, and select Customizing for theExtractors.

In the SAP system, go to DataSource master data maintenance by selectingGeneric DataSources and thenMaintain Generic DataSources.

Select Text and enter Z_CUSTY##_T as technical name for theDataSource. Enter KNA1 and CO-PA-IO.

Select Create.

Select the customer number field again.

b) Click Exit and keep this pressed until you return to the BWsystem.

Caution: Stop and let your instructor replicate yourZ_CUSTY##_T DataSource to the BW system.

In Modeling, go to SourceSystems. Select your SourceSystem andright-click the mouse to open DataSource Overview. Search for thereplicated DataSource (or CO-PA-IO) again.

2. Go to the InfoSources area and, using the search function, search for yourZ_CUSTY## InfoSource.

Select your InfoSource Z_CUSTY## and assign it your DataSource from theT90CLNT090 source system.

Your Z_CUSTY##_T DataSource will then appear for selection.

Assign the field 0TXTMD field NAME1. This field may appear by default.

Activate your entries.




a) Select the InfoSource, right-click, and choose Assign Data Source.

In the Source System field, enter T90CLNT090. Select the Transferbutton.

Select the DataSource that appears, and confirm by choosing Copy.

Click Yes to confirm the assignment.

To activate the InfoSource, click Activate, then click Exit to close thescreen.

3. Finally create an InfoPackage Z_CUSTY##_T again with the technical nameT90CLNT090 for your InfoSource T_CUSTY##_T and your source system.


Go to the Monitor. Once the upload has been completed, click Texts, andnavigate to the table for the Z_CUSTY## characteristic. The final Descriptioncolumn should now be filled.

a) Below your Z_CUSTY## InfoSource you will find a sub-icon thatrepresents your source system and the assigned DataSource.

Select this system,right-click the mouse to open the context menu andselect Create InfoPackage.

Enter the technical name Z_CUSTY##_T in the InfoPackage Descriptionfield.

Then select your Z_CUSTY##_T DataSource.

This is symbolized by a green legend icon. Click Save to go to theInfoPackage. If prompted, select Continue.

On the Data Selection tab, enter the customer number 1000 in the FromValue field and 2500 in the To Value field.

Check the individual tabs without changing any settings. On Scheduletab, choose Execute;Schedule (Start) to start the upload.

b) Click theMonitor icon, click Texts and go to the master data maintenancearea. Click Execute and check that the Description column is nowpopulated.

To close the screen and Monitor, click Exit several times. You will returnto the Administrator Workbench start screen.




Task 5:Finally, extract an external hierarchy from the CO-PA to the BW.

1. Go to your T90CLNT090 source system and then to Customizing Extractorsand open a second mode. Using transaction KES3, go to Hierarchy Version100 for the CO-PA Customer characteristic. Select IDEA and the CostingBased option.

a) In theModeling area, select Source Systems. Select the source systemT90CLNT090.

Right-click the mouse to select Customizing for the Extractors.

Then select System Create Session to open another session in theSAP system.

In second mode, enter Transaction KES3 in the transaction field to opento CO-PA hierarchy maintenance.

Select IDEA, and choose the Costing-Based option. Choose Enter toconfirm.

Select the Customer field and enter 100 in the Variant field. ChooseDisplay, and close the second mode.

Verify the hierarchy structure. Finally, click Exit to close the screen.

2. Define a DataSource for CO-PA hierarchies and enter the following data:

(P_DS) Name of DataSource: 0CO_CO_HIER_Z_CUSTY##_H(P_DP) Description: Y## Hierarchy(P_CH) InfoObject: Z_CUSTY##(P_C1) CO-PA

characteristic:KNDNR




Select the local development class.


a) In the menu, select: Data Transfer to SAP Business Warehouse Settingsfor Application Specific DataSources (PI) Profitability Analysis Create Hierarchy DataSource.

Enter the above given information in the form that now appears.

Click Execute to create the DataSource.

The system displays a success message once the DataSource has beencreated.

If the system prompts you for a development class, select Local Objectand save.

Click Exit to close the screen.

Select System End Session to delete the second mode.

To return to you BW system, click Exit in the remaining.

3.

Hint: The DataSource you create is replicatd once-off by your trainer.Notify your trainer once you have created the DataSource, so that s/hecan start the run for all groups. For hierarchies, the replication is carriedout for the CO-PA-IO node of the application component hierarchy andnot for the CO-PA node.

a) In Modeling, go to SourceSystems. Select your SourceSystemT90CLNT090 and right-click the mouse to open DataSource Overview.

Locate the Profitability Analysis application components as described inthe exercises above.

Caution: Stop, and let your instructor select these applicationcomponents. Right-click to open the context menu and chooseReplicate DataSources (instructors only). After the replication,proceed to the next section.




4. Search for and select your replicated DataSource0CO_PA_HIER_Z_CUSTY##_H. Assign you InfoSourceZ_CUSTY## under the Others option. Select Yes to confirm the assignment.Enter Z_CUSTY## in the InfoObjects field. Carry out the search as normal.

a) Select DataSource Z_CUSTY##_H, right-click the mouse and then chooseAssign DataSource.

Then select Others -> enter z_custY## and click Yes.

Your InfoSource should now contain only one DataSource/Transfer-Structure tab.

Here, enter the characteristic 0CO_PA_HIER_Z_CUSTY##_H for theInfoObject field.

Z_CUSTY## should automatically appear as the source characteristic inField.

Choose Save to save the InfoSource and Exit to close the screen.

5. Now create a Z_CUSTY##_H InfoPackage for your Z_CUSTY## InfoSourceand T90CLNT090 source system and start the upload.

a) In Modeling, select the T90CLNT090 source system for yourZ_CUSTY## InfoSource in the InfoSources area. Then right-click themouse and choose Create InfoPackage.

Select the DataSource 0CO_PA_HIER_Z_CUSTY##_H, and select Saveto navigate to the InfoPackage.

On the Hierarchy Selection tab in your InfoPackage, select the custhie100hierarchy, then Relevant for BW.

On the Scheduler tab, click Execute;Scheduler to perform the updateprocedure without altering any of the other settings.

In theMonitor, choose Hierarchies to verify that the upload has beensuccessful.

Finally, click Exit to close the screen.



Lesson Summary

You should now be able to: Understand the importance of InfoObjects and how they are created Understand how to extract master data in the form of attributes and texts from

SAP systems Understand the procedure for extracting hierarchies using CO-PA as an example



Lesson: Data Targets and Info Providers

Lesson OverviewIn this unit we will learn about Data targets and InfoProviders in SAP-BW. Datatargets are data stores carrying physical data while InfoProviders include bothnon-Data targets and Data targets. We will also learn about the two types ofInfoCubes, basic and transactional. We will discuss the properties of each and howthey are used in BW Queries.


Understand the differences between data modeling for planning and reporting Understand essential information regarding the administration of an InfoCube Explain the basic procedure for creating a multi-dimensional data model

Business ExampleWe have learned about InfoObjects in our previous lesson. We now need toincorporate these InfoObjects into an InfoCube , distinguising between the basic cubesand transactional cubes in the process.


SEM200 Lesson: Data Targets and Info Providers

Figure 16: Data Targets and InfoProviders in SAP BW

InfoProvider is a term which includes all objects that can form the basis for aBEX-Query (data stores and logical views of data stores). This means that besidescarrying physical data such as InfoCubes or ODS objects, InfoProviders also containobjects such as MultiProviders that hold no data themselves and only combine datausing a logical process from physically-updated objects such as InfoCubes or ODSobjects.

Data targets are data stores carrying physical data such as InfoCubes, ODS objectsor characteristics.

From the point of view of extraction from a source system, data is written tocorresponding data targets while, for reporting, these same tables found in the sourcesystems can be accessed for viewing by other Infoproviders.



Figure 17: Data Targets and InfoProviders for SAP-SEM

InfoCube type data stores are central objects in the BW multidimensional model.They are used in SAP BW to store aggregated data for reporting and can be modeledaccording to the required business queries. In the context of SEM, the transactionalInfoCube variant is used to retain data for planning with SEM-BPS and to updatetotals records in consolidation with SEM-BCS.

ODS Objects are used to update single documents. The transactional variants areused in consolidation in SEM-BCS to store standardizing and elimination entries.When single documents are updated in SEM-BCS, the totals records are also updatedinto the InfoCube.

MultiProviders themselves do not contain any data, but create structural relationshipsbetween different data sets stored in InfoCubes, ODS objects or characteristic tables.This enables data distributed over various data stores to be evaluated simultaneously inone query. MultiProviders are chiefly used in SEM as data providers for SEM-CPM,but are also used for reporting within consolidation (SEM-BCS) and BusinessPlanning and Simulation (SEM-BPS). They are not suitable for writing data (planning,consolidation).

Virtual InfoCube types include RemoteCubes and Virtual InfoCubes with Services.Virtual Cubes themselves do not contain any data, but extract data from a sourcesystem at query run time. Both these types can also be used in SEM-CPM as a basis



for reporting. Virtual InfoCubes with Services consist of function modules enablingdata to be selected for reporting in SEM-BCS according to posting levels and partnerrelationships.

Figure 18: Properties of BasicCubes and Transactional InfoCubes

There are two types of InfoCube. As a data target for extracting data from a sourcesystem, BasicCubes are used. Transactional InfoCubes are used as a data target forwriting data from planning or consolidation. Both InfoCubes can be used in reportingand as InfoProviders for SEM-CPM.

BasicCube and transactional InfoCube properties are shown in the above diagram.The fact table is the central table into which transactional data is loaded duringextraction. Characteristic values do not immediately become visible in the fact table.Dimension tables are used to read data from characteristic tables. Dimension keysonly are stored in the fact table. These refer to entries in the dimension tables. Thesein turn reference the corresponding characteristsic values in the characteritic table.

The following terms apply:

Key figures: A maximum of 233 key figures can be savedin a fact table for oneInfoCube.

Dimension tables: A maximum of 16 dimension tables may be created for oneInfoCube

Characteristics: Each dimension table can hold up to 248 characteristics.



Figure 19: Comparing BasicCubes and Transactional InfoCubes

BasicCubes are InfoCubes optimised for extraction and thus for reading data. Thesystem provides a data request number, known as a Request ID, automatically, whichhelps data loaded during extraction to be clearly identified later. A status managementfunction indicates whether the loading process has been completed successfully, isstill in progress or has failed for each Request ID (green = request completed), (yellow= request still in progress) (red = error).

BasicCubes cannot be used for write accesses from planning or consolidation. ABasicCube creates its own request and Request ID for each write access from planningor consolidation. This may have negative effects on performance however. For thisreason BW Release 2.0B saw the introduction of the transactional InfoCube withoptimized write access. This assigns requests in a different way. The first time writeaccess is made to a fact table, a request is opened and Request ID assigned. Thisrequest remains open after write access. This is indicated with the status yellow. Allsubsequent write accesses are also performed in this open request until 50,000 datarecords have been exceeded for one storage procedure. The request is then closed anda new request is opened.

Open requests cannot normally be read from queries. If you want to report plan datafrom open requests from transactional InfoCubes, you need to transfer the Mostcurrent Data variables for the Data Package characteristic (techn: 0REQUID) tothe filter or empty characteristics.



From BW Release 3.0A onwards, you can also carry out extractions in TransactionalInfoCubes, as Transactional InfoCubes can be switched to load mode. They canthen be switched back to plan mode later for planning purposes.

Figure 20: InfoCube Administration

Using the Manage function, you can view fact tables with dimensions keys or withspecific characteristic values and you can also delete requests that have been loadedincorrectly and collapse contents of tact tables.

Note that data extracted can only be evaluated in a query if the the status colour isgreen. If this status is yellow or red, this data cannot be displayed. This isalso the case for any subsequent requests, even if the status is green. In such cases,unsuccessful loading procedures (yellow or red status) can be closed manually anddeleted.

Each request has a unique number that identifies its data loading process. Datarequired for each request is unpacked from the source system into data packagesduring extraction and loaded to BW.



Figure 21: Collapsing the InfoCube

To help understand this function, imagine a large amount of planning data is to bewritten to the same planning segment. The corresponding data records will appear inthe fact table of the assigned InfoCube and these will differ in terms of updated figuresbut not in characteristic combinations. To calcuate the net in advance when carryingout reports and improve performance in the process, use theManage function on theCollapse tab to get the system to net all data records with the same or different requestID from one segment. Carrying out a collapse reduces the number of data records infact tables. The request ID will be removed from the fact table. You can still see thison the requests tab however. A checkbox indicates that collapsing has taken place.Collapsing thus deletes the request ID and saves memory space. You should thereforecollapse data on a regular basis.

Please note that to use this function a closed request ID is required. This is also truewhen planning for a very small scenario in SEM-BPS where you would still like tocollapse even though there are less than 50,000 data records, or where you wish todelete all plan data at once. It is essential in such cases that requests can be closedeither manually or via the program. See also OSS note 406625.



Lesson Summary

You should now be able to: Understand the differences between data modeling for planning and reporting Understand essential information regarding the administration of an InfoCube Explain the basic procedure for creating a multi-dimensional data model



Lesson: Data Modelling

Lesson OverviewWe will learn in this lesson that the data model and construction of data structures inBW is largely determined by reporting requirements. We will familiarize ourselveswith the steps required for data modelling, and analyze the different types of modelsused for planning, key figure models, and account models.


Understand the concept of data modeling in SAP-BW with reference toSAP-SEM

As well as the different steps involved in data modeling And distinguish between key figures and account modeling of InfoCubes

Business ExampleWe now know about InfoObjects and their structures. We need to determine whichinfoobjects we will need in our infocubes to complete our reporting requirements. Wealso need to isolate the types of data models (i.e. key figure or account models) wewill need to execute our queries.


SEM200 Lesson: Data Modelling

Figure 22: Aspects of Data Modeling: Key Figures

For reporting and also in connection with SEM-CPM, you need to consider questionsregarding modeling of key figures.

Contribution margin I, for instance, is a derived key figure as it is calculated fromthe difference between revenue and direct costs, and is not the direct result of anassignment. You can map derived key figures such as this in BW in two ways:

By using a key figure, in which values of the derived key figures are storedin the InfoCube:

Option 1: Calculation before upload in source system

Option 2: Calculation during upload using a routine

Option 3: Calculation using planning functions from SEM-BPS

Using a formula in the query which calculates the values of the derived keyfigure during query run time. We call these calculated key figures (Option 4).

From the point of view of planning in SEM-BPS, the following is applicable, as is itsreverse connotation: If a derived key figure is NOT saved in the InfoCube, but thevalue only produced as a calculated key figure in the query, you cannot use it duringplanning as well. You can therefore not use it for direct updates, planning or applyplanning functions to it.



This means if you want to plan with SEM-BPS using derived key figures, these mustbe represented physically in the InfoCube by a key figure type InfoObject.

Figure 23: Account Model Versus Key Figure Model in BW

InfoCubes used in the SEM context can be modeled in two ways.

A feature of the key figure model is that each business evaluation object (for example,revenueor manufacturing costs for revenue) is represented by its own InfoObject ofthe key figure type. The number of key figures in the fact table is limited to 233.

The accounts model does not contain its own InfoObject of the key figure typefor all business evaluation objects. This means that amounts where currency is akey figure (e.g. 0AMOUNT) and quantities where the second key figure is a unit(e.g. 0QUANTITY) can be conducted without having to classify them as differentbusiness evaluation objects. In consolidations, if numerical amounts have a keyfigure for transaction currency, a second may be added for local currency and thirdfor group currency. Business evaluation objects are differentiated in this case byadding a characteristic such as the account (0ACCOUNT) characteristic, the itemcharacteristic (0CS_ITEM) in consolidation, or the plan position (0SEM_POSIT) orthe measure characteristic (0MEASURE).

You can find more information on both models in SAP note 407563.



Figure 24: Key Figure Model

A key figure model is used in cases where less key figures are used and output datais extracted for strategic planning from the cost-based profitability analysis in theSAP System, for instance, which works with value fields controlled by key figuresduring data extraction.

As profitability planning is not based on extracted actual data, you can also workwith an account model directly. This saves considerable time spent on modelingand data transfer.

A feature of the fact table is that this has its own key figure column for each businessevaluation object.



Figure 25: Granularity of Planning and Accounts Model

You need to work with the accounts model for balance sheet planning. With respectto granularity of planning, you need to first decide whether you want to use roughplanning or detailed scheduling.

With SEM-BPS, SAP-BW contains characteristics that enable you to use eitherapproach.

When modeling accounts groups (rough planning), the 0SEM_POSIT characteristicis usually used. You can also use the 0MEASURE characteristic however.0MEASURE is the reference characteristic of 0SEM_POSIT, which meanscharacteristic values maintained with 0MEASURE are automatically available for0SEM_POSIT.

For detailed scheduling on accounts level you can also use the 0ACCOUNTcharacteristic (compounded to 0CHRT_ACCTS).



Figure 26: Accounts Model

The extraction of cost types or G/L accounts to BW generally uses InfoCubesstructured according to the account model, as more than 233 business evaluationobjects need to be displayed and this is close to the maximum possible for a keyfigure model.

You should also use an accounts model for financial statement planning or cost centerplanning when you need to include a lot of statement positions or cost types. Forconsoldiation, InfoCubes are also structured according to the accounts model.



Exercise 2: Data Modelling

Exercise ObjectivesAfter completing this exercise, you will be able to: Understand the data modeling concepts in BW Provide insight into the definition of Dimensions, Fact Tables and InfoObjects

and how they are inter-related Understand how to extract data from CO-PA to BW and conducting flat-file

upload

Business ExampleInfoproviders need to be created so that data can be loaded from R/3 and other sourcesystems. Two InfoCubes will be created to facilitate management's different reportingrequirements.

Task 1:The task in the following is to build a suitable InfoCube that you can use to extracttransaction data from the CO-PA later.

You realize you can use one InfoCube to extract actual and plan data; however, youprefer using two separate InfoCubes with identical structures. For this reason, youshould create the first InfoCube for extracting actual data from the CO-PA manually,then use this as a template to create the second.

1. In the Administrator Workbench of your local BW system, go to theSem200_training_rel40 InfoArea.

Create your BAS_COY## InfoCube for this InfoArea. Enter Y## BasicCubefor CO-PA extraction as a description.

Select BasicCube as the InfoCube type.


Select the following characteristics:




Character Long description0Comp_Code Company Code0CO_Area Controlling Area0Curtype Currency Type0Division Division0Material Material0Matl_group Material group0Plant Plant0REC_type Transaction/event type0Valuation Valuation View0Version Version0Vtype Value Type for Reporting

Hint: Should you require the search function to find the InfoObjects,use the Place Cursor icon rather than the Find icon, as the first optionsearches through the entire list from beginning to end, whereas thelatter starts the search from the last characteristic and may not findthe InfoObject required.

Select the following time characteristics:

Time characteristics Long description0FISCPER Fiscal Year/Period0FISCVARNT Fiscal Year Variant0FISCYEAR Fiscal Year

Select the following key figures:

Key figures Long description0G_AVV010 Revenue0G_QVVIQT Invoiced Quantity


Unlock-SEM200 - Business Warehouse for Strategic Enterprise Management

Documents

Transcript of Unlock-SEM200 - Business Warehouse for Strategic Enterprise Management