1.BW360SAP BI Performance & AdministrationInternalOnly SAP NetWeaver Information IntegrationPartnerUse Date Training CenterSAPSAP Instructors Education WebsitePartnerUseInternalOnly Participant Handbook Course Version: 2006 Q2 Course Duration: 5 Day(s) Material Number: 50081099 An SAP course - use it to learn, reference it for work

2. Copyright Copyright 2006 SAP AG. 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 AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Trademarks Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. InternalOnly 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.Partner 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 of Use Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. SAPSAP 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 are Partner trademarks or registered trademarks of SAP AG in Germany and in several other countries allUse over the world. All other products mentioned are trademarks or registered trademarks of their respective companies. DisclaimerInternal THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT Only LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS. 3. About This Handbook This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study. Typographic ConventionsInternalOnly American English is the standard used in this handbook. The following typographic conventions are also used.Type StyleDescriptionPartnerExample textWords or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as well asmenu names, paths, and options.UseAlso used for cross-references to other documentationboth internal (in this documentation) and external (inother locations, such as SAPNet).SAPSAPExample textEmphasized words or phrases in body text, titles ofgraphics, and tablesEXAMPLE TEXTNames of elements in the system. These include reportPartnerUsenames, program names, transaction codes, table names,and individual key words of a programming language,when surrounded by body text, for example SELECTand INCLUDE.InternalExample textScreen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of a program.OnlyExample textExact 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. 2006/Q2 2006 SAP AG. All rights reserved. iii 4. About This Handbook BW360 Icons in Body Text The following icons are used in this handbook.IconMeaningFor more information, tips, or backgroundNote or further explanation of previous pointInternalOnlyException or cautionPartnerProceduresUseIndicates that the item is displayed in the instructorspresentation.SAPSAPPartnerUseInternalOnly iv 2006 SAP AG. All rights reserved. 2006/Q2 5. Contents Course Overview ............................................................................. vii Course Goals.................................................................................vii Course Objectives ...........................................................................vii InternalOnly Unit 1: SAP NetWeaver .......................................................................1 SAP NetWeaver: IT Practices, IT Scenarios, and Usage Types ....................... 2 Unit 2: InfoProviders......................................................................... 13Partner InfoCube Data Model ...................................................................... 15 Data Store Object Architecture ........................................................... 33 MultiProvider ................................................................................ 36 Use Virtual Providers ............................................................................ 42 Real-time InfoCubes ....................................................................... 48 Data Store Object for Direct Update ..................................................... 60 SAPSAP Unit 3: Process Chains...................................................................... 65 Process Chains Design .................................................................... 66 Managing Process Chains ................................................................ 76 PartnerUse Unit 4: InfoProvider Administration and Tuning .....................................103 Managing InfoCubes ...................................................................... 105 Managing Data Store Objects............................................................ 114Internal Relational DBMS Indexes in BI .......................................................... 125 Indexing for InfoProviders ................................................................ 141 Table Partitioning in BI .................................................................... 158 Only Unit 5: Reporting Performance...........................................................171 Design Guidelines for Optimal Query Performance................................... 172 OLAP Caching ............................................................................ 179 Unit 6: BI Statistics and Monitoring .....................................................201 BI Statistics ................................................................................. 203 BI Statistics Technical Content........................................................... 210 BI Administrator Cockpit .................................................................. 223 BI Trace Tool ............................................................................... 232 2006/Q2 2006 SAP AG. All rights reserved.v 6. Contents BW360 Unit 7: Aggregates ..........................................................................239Relational DBMS Aggregate Basics..................................................... 241Missing Aggregates ....................................................................... 252Analyzing Aggregate Usage.............................................................. 262Aggregate Maintenance .................................................................. 270 Unit 8: Data Acquisition Performance ..................................................313Data Load Cycle ........................................................................... 314 InternalOnlyTechnical Details ........................................................................... 318Parallelization .............................................................................. 336Optimizing Data Acquisition Performance.............................................. 344 Unit 9: Information Life Cycle Management...........................................365PartnerInformation Life Cycle Management in BI .............................................. 366 Unit 10: Transport Management .........................................................393 UseSystem Landscape ........................................................................ 395Standard Transport System .............................................................. 401Object Versions and Metadata ........................................................... 405 SAPTransporting in BI .......................................................................... 410SAPBEx Objects ................................................................................ 422Transporting Roles and Workbooks ..................................................... 426System Copy ............................................................................... 429Transport Strategies and Troubleshooting ............................................. 434 PartnerUse Unit 11: BI Accelerator .....................................................................441BI Accelerator Introduction ............................................................... 443BI Accelerator Architecture ............................................................... 453InternalImplementing BI Accelerator Indexes ................................................... 464BI Accelerator Monitoring................................................................. 481 Only Unit 12: Appendix ...........................................................................495BI and OLTP System Comparison....................................................... 496BI Database Settings...................................................................... 499Web Application Server Settings ........................................................ 503Reorganizing Tables....................................................................... 521Sizing BI Systems ......................................................................... 526 Index ............................................................................................535 vi 2006 SAP AG. All rights reserved. 2006/Q2 7. Course Overview The focus of this course in on advanced BI administration and performance. This course provides a detailed look at the BI architecture and system landscape. Initially the various types of InfoProviders are discussed, then more details are covered that include the managing of InfoProviders for optimal performance. In order to manage the Enterprise Data Warehousing environment, sophisticated monitoring tools areInternalOnly essential. This course provides a detailed look at various monitoring tools in BI. Important statistics are collected for system wide analysis. This course discusses how the statistics are collected and analyzed. Participants will learn techniques to improve both query performance and data acquisition performance. Participants will learn how to create and maintain effective aggregates. This course also discusses the TransportPartner Management system, and the different methods that are used to handle Transports in BI. Participants will also learn about Information Life Cycle management and archiving in BI. A new technology to enhance query performance is introduced withUse the BI Accelerator. Target AudienceSAP This course is intended for the following audiences:SAP Project team members with extensive BI knowledge. Course PrerequisitesPartnerUse Required Knowledge Knowledge of the subject matter covered by BW310 (BI Data Warehousing).Internal Course GoalsOnly This course will prepare you to: Administer and monitor BI systems. Improve query performance. Improve data acquisition performance. Transport data in BI systems. Course Objectives After completing this course, you will be able to: 2006/Q2 2006 SAP AG. All rights reserved. vii 8. Course OverviewBW360 Describe the BI architecture and data models. List techniques to enhance query performance. Describe how implement BI Statistics Technical Content. Use BI monitoring and tracing tools to analyze BI performance. List techniques to improve data acquisition performance. Create effective aggregates to improve query performance. Implement partitioning techniques for optimal performance. Describe how the BI Accelerator can be used to improve query performance. InternalOnly SAP Software Component Information The information in this course pertains to the following SAP Software Components and releases:Partner Use SAPSAP PartnerUseInternal Only viii 2006 SAP AG. All rights reserved.2006/Q2 9. Unit 1 SAP NetWeaver InternalOnly Unit Overview NetWeaver is SAPs application and integration platform that forms the technical foundation for mySAP Business Suite and SAP xApps. It delivers a complete, open, and flexible infrastructure that easily enables integration to SAP and non-SAPPartner applications. As of SAP NetWeaver 2004s, SAP retired the component terms as a method of Use describing the bundling features and functions. Now the concept for SAP NetWeaver and its enablement of IT is through the new cross-organizational and cross-technology IT practices and IT scenarios. SAPSAP Unit Objectives After completing this unit, you will be able to: Describe SAP software is organized. PartnerUse Define IT practices. Define IT scenarios and scenario variants. Define usage types.Internal Unit Contents Lesson: SAP NetWeaver: IT Practices, IT Scenarios, and Usage Types ...... 2 Only 2006/Q2 2006 SAP AG. All rights reserved.1 10. Unit 1: SAP NetWeaver BW360 Lesson: SAP NetWeaver: IT Practices, IT Scenarios, and Usage TypesLesson OverviewWith SAP Netweaver 2004s, a new evolution of SAP software is introduced. SAPsoftware is now organized around the new concepts of IT Scenarios, IT strategies andUsage Types. Separate components such as, Enterprise Portal, Business Intelligence,Process Integration, Mobile Intelligence, Web Application Server, and Master DataInternalOnlyManagement, are now organized together as a single platform. This extremelycomprehensive technical platform provides a powerful base for deploying theEnterprise Service-Oriented Architecture.This new platform enhances BI in many ways. Business reporting and analyticalPartnercapabilities are expanded by the integration of the BEx frontend with EnterprisePortal. This new platform also enables enhanced Enterprise Data Warehousingfeatures including new objects for modeling and implementing the EDW layers.UseThis lesson provides information about the new concept and the corresponding newterminology.SAPLesson ObjectivesSAPAfter completing this lesson, you will be able to:Describe SAP software is organized.PartnerDefine IT practices.UseDefine IT scenarios and scenario variants.Define usage types.InternalBusiness ExampleYour company is now running SAP Netweaver 2004s. You need to become familiarOnlywith the new concepts and terminology that are introduced in this release.Terms Used by SAP Software Organization and DeliveryIT Practices, Scenarios, and Scenario VariantsIT practices identify how you can use SAP NetWeaver to solve specific businessproblems by deploying integrated IT scenarios in a way that does not disrupt yourexisting operations. IT practices look at the overall SAP NetWeaver platform invertical slices that focus on key business issues, rather than on isolated technology 2 2006 SAP AG. All rights reserved. 2006/Q2 11. BW360Lesson: SAP NetWeaver: IT Practices, IT Scenarios, and Usage Types components. These include goals familiar to almost any IT organization, for example, the need to combine different integration technologies, to develop composite applications leveraging existing system investments, or to build new business processes in a flexible way. Other examples of IT practices include data unification and Business Information Management. InternalOnlyPartner Use SAPSAP Figure 1: SAP NetWeaver 2004s and IT Practices PartnerUse To address the broad challenges in each IT practice, SAP NetWeaver provides predefined IT scenarios, introduced fully with SAP NetWeaver 2004s. By implementing IT scenarios, customers can adopt the core functionality of SAP NetWeaver in incremental phases. Each practice can be broken into one or multiple ITInternal scenarios, providing organizations with a process-oriented approach to making best use of SAP NetWeaver. Only IT practices serve as high-level starting points. They give structure to IT scenarios as the IT implemental things connected to documentation and configuration. An IT scenario is a set of IT processes, grouped to attain a defined business goal. Targeting the business of IT, IT scenarios help the technical community to more quickly and to easily develop, compose, and run applications. They also help IT build, enhance, 2006/Q2 2006 SAP AG. All rights reserved. 3 12. Unit 1: SAP NetWeaverBW360and operate an IT infrastructure that integrates people, information, and processes.In many cases, further grouping is necessary, and the next level of organization is ascenario variant, which is a smaller grouping of IT processes. Note: IT scenarios replace the previous component view of SAP NetWeaver. All product information will be rolled out based on IT scenarios. InternalOnlyPartner Use SAPSAPFigure 2: IT Practices, IT Scenarios, and Variants PartnerUseThe aim of IT scenarios is to help customers and partners install and operate SAPNetWeaver. You utilize IT scenarios to run business applications both custom-builtand packaged applications or to implement a defined IT concept, such as evolving acompanys system landscape into a services-based architecture.InternalFocusing on the flow of activities, IT scenarios are meaningful groupings of processestypically performed by one department. In this context; application development,adaptation and configuration, or business process management are typical examples of OnlyIT scenarios. In summary, we chose a scenario-based approach to ease the transitionfrom your business requirements to a system landscape that will enable them. 4 2006 SAP AG. All rights reserved.2006/Q2 13. BW360 Lesson: SAP NetWeaver: IT Practices, IT Scenarios, and Usage TypesInternalOnlyPartnerUse Figure 3: IT Scenarios and IT Practices IT scenarios can cross IT practices. The figure below demonstrates this using Enterprise Data Warehousing as an example. A scenario-based approach to ease theSAPSAP transition from your business requirements to a system landscape that enable them. The IT Scenario Enterprise Data Warehousing (EDW) detailed in the preceding graphic and the scenario variants Modeling and Running the EDW detailed below are the focus of this class.PartnerUseInternalOnly Figure 4: Scenario Variants for Enterprise Data Warehousing 2006/Q2 2006 SAP AG. All rights reserved. 5 14. Unit 1: SAP NetWeaverBW360Usage TypesIn previous releases, SAP delivered and organized around IT-specific softwarecomponents. The key capabilities of SAP NetWeaver were delivered as softwarecomponents. Note: Although components exist, and are shown when you access the System Status path on the SAP GUI, they are not relevant in business discussions. In addition, implementation is focused on usage types not components.InternalOnlyPartnerUseSAPSAPPartnerUseFigure 5: How Should We Group and Deliver SAP NetWeaver?Now, instead of an IT focus, SAP is moving to a business-based focus and deliveringInternalthe actual software you need to run an IT scenario. This business focused delivery ofsoftware crosses IT focused software componentsand is easier to understand for all.Only 6 2006 SAP AG. All rights reserved.2006/Q2 15. BW360 Lesson: SAP NetWeaver: IT Practices, IT Scenarios, and Usage Types InternalOnlyPartner Use Figure 6: Business-Focused Usage Types Usage types as an organizational tool have many advantages over software components by themselves. The figure below lists some of the advantages of usage types. SAPSAPNote: This figure also shows that some usage types are dependant on others.For example, usage type EP requires usage type AS Java. PartnerUseInternal Only Figure 7: Usage Types 2006/Q2 2006 SAP AG. All rights reserved. 7 16. Unit 1: SAP NetWeaver BW360In addition to SAP NetWeaver software components being packaged and deliveredunder usage types, other software is needed in an SAP implementation.Standalone engines are additional, installable software units that do not work asfull-blown systems of SAP NetWeaver, but provide a specific (server) function incombination with one or multiple SAP NetWeaver systems. They are not part of ausage type, and do not run on Web AS ABAP or Web AS Java. One example of anengine is the Search and Classification (TREX) engine, used for search and retrievalin large document collections, text mining, automatic document classification, andsearch and aggregation over structured data in SAP applicationsInternalOnlyClient programs are, again, additional installable programs not considered as usagetypes in any way. This category of software either resides on local front-end PCaccessed by users or on back-end systems acting as a client program within a SAPNetWeaver system landscape. Front-end and back-end clients are part of the systemPartneror standalone engine installation for various reasons.Usage types and client programs and dedicated engines categorize all the softwareneeded in an SAP environment. This is shown in the figure below.UseSAPSAPPartnerUseInternalFigure 8: Usage Types and Client Programs and Dedicated EnginesOnlyThe organization of multiple usage types is often needed to build up a usable system.The figure below shows the interaction between clients, systems, and standaloneengines. 8 2006 SAP AG. All rights reserved. 2006/Q2 17. BW360Lesson: SAP NetWeaver: IT Practices, IT Scenarios, and Usage TypesInternalOnlyPartnerUse Figure 9: Clients, Systems, and Standalone Engines The concepts in this lesson are critical for your success. One example, installing the software, is shown in the following two figures.SAPSAPPartnerUseInternalOnly Figure 10: Usage Types Drive Installation of SAP NetWeaver 2006/Q2 2006 SAP AG. All rights reserved.9 18. Unit 1: SAP NetWeaver BW360InternalOnlyPartnerUseFigure 11: Installation: Selection of Usage TypeAlthough not every link below is focused solely on implementation, usage types, orIT scenarios, they will be very helpful in your future.SAPSAPPartnerUseInternalOnlyFigure 12: Where to Go for More Information 10 2006 SAP AG. All rights reserved.2006/Q2 19. BW360Lesson: SAP NetWeaver: IT Practices, IT Scenarios, and Usage Types Lesson Summary You should now be able to: Describe SAP software is organized. Define IT practices. Define IT scenarios and scenario variants. Define usage types. Related InformationInternalOnly Use the last figure in this lesson to find links to a wealth of information about BI. Note 917950 has a lot of detail on BEx related usage types.PartnerUseSAPSAPPartnerUseInternalOnly 2006/Q2 2006 SAP AG. All rights reserved. 11 20. Unit SummaryBW360Unit SummaryYou should now be able to:Describe SAP software is organized.Define IT practices.Define IT scenarios and scenario variants.Define usage types. InternalOnlyPartner Use SAPSAP PartnerUseInternal Only 12 2006 SAP AG. All rights reserved. 2006/Q2 21. Unit 2 InfoProvidersInternalOnly Unit Overview In this unit, you will learn about BI InfoProviders. The BI Extended Star Schema is discussed in detail. You will learn how to design the star schema for performance. You will also learn about Data Store Objects and the important role they play in BI.Partner Other InfoProviders discussed in this unit include MultiProviders, Virtual Providers and Real Time InfoProviders.Use Unit Objectives After completing this unit, you will be able to:SAPSAP Describe the SAP BI Extended Star Schema. Describe the performance aspects of the Star Schema. Explain the difference between a display attribute and a navigational attribute. Describe the purpose of line item dimensions.PartnerUse Describe the Data Store Object Architecture. Describe the process of activating Data Store Objects. Describe how to create a MultiProvider.Internal Explain the performance implications of query processing on MultiProviders. List the administration and performance benefits of utilizing Multiproviders.Only Create Virtual Providers. Describe the benefits of Virtual Providers. Explain the impact on query performance when Virtual Providers are read. Create a Real-time InfoCube and write into it Create a Data Store Object for Direct Update. Unit Contents Lesson: InfoCube Data Model ..................................................... 15Exercise 1: Examine Data Model ............................................. 23 2006/Q2 2006 SAP AG. All rights reserved. 13 22. Unit 2: InfoProviders BW360Exercise 2: Create an InfoCube ............................................... 29 Lesson: Data Store Object Architecture .......................................... 33 Lesson: MultiProvider ............................................................... 36 Lesson: Virtual Providers ........................................................... 42 Lesson: Real-time InfoCubes ...................................................... 48Exercise 3: Real-Time InfoCubes ............................................. 55 Lesson: Data Store Object for Direct Update .................................... 60InternalOnlyPartnerUseSAPSAPPartnerUseInternalOnly 14 2006 SAP AG. All rights reserved.2006/Q2 23. BW360 Lesson: InfoCube Data Model Lesson: InfoCube Data Model Lesson Overview In this lesson, you will learn about the need for data models. You will also learn about the BI Extended Star Schema and how to design the star schema. Lesson Objectives After completing this lesson, you will be able to:InternalOnly Describe the SAP BI Extended Star Schema. Describe the performance aspects of the Star Schema. Explain the difference between a display attribute and a navigational attribute.Partner Describe the purpose of line item dimensions. Business ExampleUse You are working in the Data Warehousing department of a chemical company. You need to load data separately into the master data tables, text tables, and hierarchy tables.SAPSAP Introducing Data Models Do not underestimate the importance of the data model.PartnerUse It is the basis of all BI application tuning. Create the blueprint very carefully. The effects of a bad data model are visible first with mass data load.InternalOnly 2006/Q2 2006 SAP AG. All rights reserved. 15 24. Unit 2: InfoProviders BW360 InternalOnlyPartner Figure 13: Data Model Design Use BI performance begins with the data model. The design phase is the ideal time to discuss the performance implications of BI SAP models. A poorly designed model will cause overall performance problems in terms ofSAP reading and loading BI objects. The design of BI models should include performance considerations from the beginning. PartnerUseInternal Only 16 2006 SAP AG. All rights reserved. 2006/Q2 25. BW360 Lesson: InfoCube Data Model BI Extended Star Schema InternalOnlyPartner Use Figure 14: SAP BI Star Schema SAPSAP The SAP BI Star Schema is made up of a Fact table and Dimension tables. There can be a maximum of 16 dimension tables in one Star Schema. The Star Schema is also called and InfoCube. The InfoObjects in the dimension tables are called characteristics. The InfoObjects in PartnerUse the fact table are key figures. All characteristics have a SID (surrogate ID) table. The characteristic SID table gets created when the characteristic is activated. The SID table contains a SIDID for each characteristic value. The SIDID represents the characteristic value in numericInternal INT4 format and is generated by the system when values are loaded. Because each characteristic in a dimension table is represented by a numeric SIDID, the read performance on the InfoCube is greatly enhanced. (Reading numeric values is much Only faster than reading alphanumeric values.) If a characteristic, such as Customer or Product, also has master data tables, then the SID table is also the link between the master data and the characteristic in the dimension tables. Use transaction LISTSCHEMA to display the tables in the Star Schema. The BI extended star schema is subdivided into a solution-dependent part (InfoCube) and a solution-independent part: attribute tables, text tables, and hierarchy table. The attribute, text and hierarchy tables are also shared among the other InfoCubes. 2006/Q2 2006 SAP AG. All rights reserved.17 26. Unit 2: InfoProviders BW360InternalOnlyPartnerUse Figure 15: Extended Star Schema The attributes of the characteristics are located in the master data tables.SAP A great challenge when designing a solution is to decide whether to store data as aSAP characteristic in a dimension table (and therefore in the InfoCube) or as an attribute in a master data table. Data is loaded separately into the master data tables (attribute tables) text tables andPartner hierarchy tables.Use AttributesInternalOnly 18 2006 SAP AG. All rights reserved.2006/Q2 27. BW360Lesson: InfoCube Data ModelInternalOnly Figure 16: Display and Navigational Attributes A display attribute is an attribute of an InfoObject that can be displayed together with the InfoObject. It cannot be used on its own. A navigation attribute is an attribute of an InfoObject that can be displayedPartner independently of the InfoObject and also used to navigate. For example it can be used to filter data.Use It has to be enabled as a navigation attribute in the InfoObject that it is based on and switched on for each InfoCube. The naming convention for a navigational attribute is: InfoObject__Attribute, such as 0customer__0country.SAPSAPPartnerUseInternalOnly Figure 17: Navigational Attribute: Read Execution 2006/Q2 2006 SAP AG. All rights reserved. 19 28. Unit 2: InfoProvidersBW360 Designing the Star Schema Small dimensions. Few dimensions (less important than small dimensions). Only as many details as necessary. Hierarchies only if necessary. Time-dependent structures only if necessary. Avoid MIN, MAX - Aggregation for key figures in huge InfoCubesInternalOnly If MIN or MAX Aggregation is used in key figures, no delta changerun in Aggregates is possible. For each change run, a total rebuild of the aggregate is done. When modeling real world processes, different interests generally conflict with one other. A good design is therefore a compromise that allows the most important partsPartner of each aspect to be represented without disregarding the other aspects. Some questions to ask when determining requirements:Use Will delivered business content meet many requirements? What granularity of data do the users really need to access most frequently? Which user requirements are, in reality, exception reporting?SAPSAP Are users basing their requirements on simply replicating reports from a legacy system? Granularity is the level of detail of data. A decision about the granularity of modeling is one of the main results of the data modeling phase. Granularity deeply influences:PartnerUse Reporting capabilities Query Performance Required Disk SpaceInternal Data load performanceOnly Figure 18: Designing the Data Model 20 2006 SAP AG. All rights reserved. 2006/Q2 29. BW360Lesson: InfoCube Data Model Line Item Dimensions For good performance, the number of rows in the dimension tables should be small compared to the number of rows in the fact table. A general rule of thumb is the number of dimension table rows should be less than 15% of the number of fact table rows. Line item dimensions solve the problem of too many rows in the dimension table. The prerequisite is that there can be only one characteristic in the dimension. Line item dimensions improve both reporting and data load performance.InternalOnly F4 Help usually uses the dimension table for selection. In a line item dimension, there is no dimension table. Therefore, the S-table has to be used. An InfoCube can for example only uses 4 material numbers, but the BI system knows 10.000 material numbers. The material numbers, which are stored in the InfoCube, can be found in the dimension table. All material numbers of the BI system can be found in thePartner S-table. This means the F4-help can access a table with 10.000 entries instead of a table with 4 entries.UseSAPSAPPartnerUseInternal Figure 19: Line Item DimensionOnly 2006/Q2 2006 SAP AG. All rights reserved.21 30. Unit 2: InfoProvidersBW360InternalOnly Figure 20: Create a Line Item DimensionPartnerUseSAPSAPPartnerUseInternalOnly Figure 21: Aspects of Design During the design phase of the project, there is an important balance between analysis aspects and performance aspects. 22 2006 SAP AG. All rights reserved. 2006/Q2 31. BW360 Lesson: InfoCube Data Model Exercise 1: Examine Data Model Exercise Objectives After completing this exercise, you will be able to: Examine the data model of InfoCubes Business Example InternalOnly Check for the data model of an existing InfoCube. Task 1: Examine the data model of InfoCube T_PU_SLOW (technical name).Partner 1. Analyze the InfoCube T_PU_SLOW.Find and display the data model of the InfoCube Use 2. Transaction LISTSCHEMAOpen another window to call up the schema viewer for InfoCubes.What is the name of the database table for the InfoCube F fact table? SAPSAPExpand to view the names of the dimension tables. 3. Analyze the InfoCubes F fact table and dimension tablesGo to transaction RSRV and determine the number of records for the F fact PartnerUsetable and dimension tables.Which one of these dimensions tables is the best candidate to be a Line Itemdimension?Internal Task 2: Learn more about data models., Choose the InfoCube with the technical name Only T_ATTR. For this InfoCube two queries exist, run both queries (technical names T_ATTR1 and T_ATTR2). Describe what you see, why do you see this difference? 1. Open the BEx Analyzer (call transaction RRMX). 2006/Q2 2006 SAP AG. All rights reserved. 23 32. Unit 2: InfoProvidersBW360 Solution 1: Examine Data Model Task 1: Examine the data model of InfoCube T_PU_SLOW (technical name). 1.Analyze the InfoCube T_PU_SLOW. Find and display the data model of the InfoCube a) Go to transaction RSA1. Choose Modeling, then InfoProvider. GotoInternalOnlyInfoArea BW Training BW Customer Training BW360 Performanceand Administration Unit02. Highlight the InfoCube, context menu,and choose Display Data Model.Expand the Key Figures folder, and note the key figures that make up thisPartnerInfoCubes fact table. Expand each dimension (three triangles icon), to seewhat characteristics make up each dimension table of the InfoCube. Listthe dimensions that were built by the designer of the InfoCube.Use 2.Transaction LISTSCHEMA Open another window to call up the schema viewer for InfoCubes. What is the name of the database table for the InfoCube F fact table?SAPSAPPartnerUseInternalOnly Continued on next page 24 2006 SAP AG. All rights reserved. 2006/Q2 33. BW360Lesson: InfoCube Data ModelExpand to view the names of the dimension tables.a) In the box at the top left of the screen, type in /oLISTSCHEMA. In the field InfoCube Type, type in B, and type in the technical name T_PU_SLOW of the InfoCube, then select the Execute icon. The name of the database F fact table for the InfoCube is /BIC/FT_PU_SLOW. These are the dimension and their tables:InternalOnly T_PU_SLOWP: /BIC/DT_PU_SLOWP T_PU_SLOWT: /BIC/DT_PU_SLOWT T_PU_SLOWU: /BIC/DT_PU_SLOWU T_PU_SLOW1: /BIC/DT_PU_SLOW1 T_PU_SLOW2: /BIC/DT_PU_SLOW2Partner T_PU_SLOW3: /BIC/DT_PU_SLOW3 T_PU_SLOW4: /BIC/DT_PU_SLOW4 T_PU_SLOW5: /BIC/DT_PU_SLOW5Use T_PU_SLOW6: /BIC/DT_PU_SLOW6 T_PU_SLOW8: /BIC/DT_PU_SLOW8 T_PU_SLOWA: /BIC/DT_PU_SLOWASAP 3. Analyze the InfoCubes F fact table and dimension tablesSAPGo to transaction RSRV and determine the number of records for the F facttable and dimension tables.PartnerUseInternalOnly Continued on next page 2006/Q2 2006 SAP AG. All rights reserved.25 34. Unit 2: InfoProviders BW360 Which one of these dimensions tables is the best candidate to be a Line Item dimension? a) Go to transaction RSRV. Goto to Tests All Elementary Tests Database. Highlight the Test Database Information about InfoProviderTables, right-click (context menu), and choose Select Test.On the right side, expand the test and make the parameter entryInfoProvider T_PU_SLOW. Choose the button Transfer. Execute the testby selecting the Execute button in the top of the left side. Display theprotocol with the button Display. Expand your whole protocol. Now you InternalOnlycan see the tables with their records.The dimension T_PU_SLOW8 with 188557 entries (23% of F fact table)in the table /BIC/DT_PU_SLOW8 is the best candidate to be a HighCardinality dimension and a Line-Item dimension. It can be a linePartneritem dimension because, as you have seen in the data model, there is onlyone characteristic inside that dimension. All dimensions with only onecharacteristic can be a good candidate for a line item dimension. Use SAPSAP PartnerUseInternal OnlyContinued on next page 26 2006 SAP AG. All rights reserved.2006/Q2 35. BW360Lesson: InfoCube Data Model Task 2: Learn more about data models., Choose the InfoCube with the technical name T_ATTR. For this InfoCube two queries exist, run both queries (technical names T_ATTR1 and T_ATTR2). Describe what you see, why do you see this difference? 1. Open the BEx Analyzer (call transaction RRMX).a) Open Query InfoAreas BW Training BW Customer Training BW360 Performance and Administration Unit 02 Query withInternalOnly attribute country 1 OK. Open the second query Query with attribute country 2 the same way you did for the first query. The first query displays EN for the country. The second query displays DE for country. Both queries look the same, toPartner see the difference (it doesnt matter if you can open the change dialog only in display mode): Change Change Query (global definition) Technical Names on.Use The country characteristic used in query one is the country InfoObject itself. The country characteristic used in query 2 is the navigational attribute of InfoObject Airport. Hence the second query displays the country from the master data table (/BIC/PT_AIRPORT) and the first querySAPSAP takes the value for the country out of the InfoCube. The queries themselves display in both cases just country as the name of the object, in order to avoid mistakes always choose a different name for the navigational attribute!PartnerUseInternalOnly 2006/Q2 2006 SAP AG. All rights reserved.27 36. Unit 2: InfoProviders BW360 InternalOnlyPartner Use SAPSAP PartnerUseInternal Only 28 2006 SAP AG. All rights reserved. 2006/Q2 37. BW360 Lesson: InfoCube Data Model Exercise 2: Create an InfoCube Exercise Objectives After completing this exercise, you will be able to: Create InfoObjects. Create an InfoCube. Identify the database tables that are created. InternalOnly Business Example Business requirements determine that a new InfoCube must be created to hold flight data. (The transaction data will be loaded later from the OLTP system.}Partner New InfoObjects are also needed to be included in the InfoCube. For performance reasons the InfoCube should have two dimensions, and each dimension should be a line item dimension with high cardinality. Use Task: Before you create your InfoObjects you need to create an InfoObject catalog. After SAP you have created your catalog create your own InfoObjects.SAP 1. Create an InfoObject catalog, Group##_char. In the catalog create characteristicInfoObjects: T_CARID##, and T_CONID##. 2. Create InfoCube TRANSP##, with two line item dimensions: CARRID PartnerUseand CONNID. Make each a line item dimension with high cardinality. Inthe CARRID dimension insert InfoObject T_CARID##, and in the CONNIDdimension insert InfoObject T_CONID##. Include the Key Figure T_FLPRICEand 0CALDAY in your InfoCube.Internal Only 2006/Q2 2006 SAP AG. All rights reserved.29 38. Unit 2: InfoProvidersBW360 Solution 2: Create an InfoCube Task: Before you create your InfoObjects you need to create an InfoObject catalog. After you have created your catalog create your own InfoObjects. 1.Create an InfoObject catalog, Group##_char. In the catalog create characteristic InfoObjects: T_CARID##, and T_CONID##. a) In transaction RSA1 choose InfoObjects and go to InfoArea: BW TrainingInternalOnly BW Customer training BW360 Unit02 Group##. b) From the context menu of your InfoArea Group##, choose CreateInfoObject Catalog. Enter the name GR##_char and check InfoObjectType Chars.Partner c) Activate your InfoObject catalog. d) From the context menu of your InfoObject catalog choose CreateUseInfoObject. Field NameValuesSAP InfoObjectT_CARID##SAP Description Group ## Carrid TemplateT_CARID98PartnerUse e) Activate. f) From the context menu of your InfoObject catalog choose CreateInfoObject..Internal Field NameValues InfoObjectT_CONID##Only Description Group ## Connid TemplateT_CONID98 g) Activate.Continued on next page 30 2006 SAP AG. All rights reserved. 2006/Q2 39. BW360 Lesson: InfoCube Data Model 2. Create InfoCube TRANSP##, with two line item dimensions: CARRIDand CONNID. Make each a line item dimension with high cardinality. Inthe CARRID dimension insert InfoObject T_CARID##, and in the CONNIDdimension insert InfoObject T_CONID##. Include the Key Figure T_FLPRICEand 0CALDAY in your InfoCube.a) From RSA1, choose Modeling InfoProvider. Go to InfoArea BW Training BW Customer training BW360 Unit 01 Group##.b) From the context menu of your InfoArea choose Create InfoCube. InternalOnlyField Name ValuesInfoCube TRANSP##DescriptionGroup ## InfoCubePartnerc) Press Create.d) Rename Dimension1 to CARRID and change properties. From the context Use menu of your dimension choose Properties and select Line Item and High Cardinality.e) Press Continue. SAPSAPf) From the context menu of your CARRID dimension choose InfoObject.Direct Input. Enter T_CARID##.g) From the context menu of the Dimensions folder, select Create new Partner dimensions. Enter CONNID for the description and select Line Item andUse High Cardinality. Press continue.h) From the context menu of the TIME dimension choose InfoObject.Direct Input. Enter 0CALDAY.Internali) From the context menu of the Key Figures folder choose InfoObject.Direct Input. Enter T_FLPRICE. Onlyj) Activate your InfoCube. From the context menu of your InfoCube choose Display Data Model.k) Go to transaction LISTCHEMA. Enter TRANSP##. Expand the hierarchy and view the tables that were created. 2006/Q2 2006 SAP AG. All rights reserved.31 40. Unit 2: InfoProviders BW360 Lesson Summary You should now be able to: Describe the SAP BI Extended Star Schema. Describe the performance aspects of the Star Schema. Explain the difference between a display attribute and a navigational attribute. Describe the purpose of line item dimensions.InternalOnlyPartnerUseSAPSAPPartnerUseInternalOnly 32 2006 SAP AG. All rights reserved.2006/Q2 41. BW360Lesson: Data Store Object Architecture Lesson: Data Store Object Architecture Lesson Overview This lesson will give you an overview of the Data Store Object Architecture. It will also describe the processes of loading and activation of Data Store Objects Objects. Lesson Objectives After completing this lesson, you will be able to: InternalOnly Describe the Data Store Object Architecture. Describe the process of activating Data Store Objects.Partner Business Example Your organization uses Data Store Objects to store huge amounts of data. As an employee of this chemical company, you need to understand the Data Store Use architecture. Data Store Architecture SAPSAP PartnerUseInternal Only Figure 22: Data Store Object Architecture 2006/Q2 2006 SAP AG. All rights reserved. 33 42. Unit 2: InfoProviders BW360 Data Store Objects consist of three tables: Activation Queue: In this table the new data is stored before activation. The structure is like a PSA table. The key is made up of the request, data package, and record number. After activation, a request is deleted from the Activation Queue. Table with active data: In this table the currently active data is stored. The table has a semant key defined by the data modeler for example.order number, order item). Reporting is done on that table. Change Log: During activation, changes in the active data are stored in the Change Log. You can find the entire history of activations for the Data StoreInternalOnly Object in that table because data is not automatically deleted from that table. If data targets are supplied with data from the Data Store Object, in a delta process the data is read from the Change Log. The Change Log is a PSA table and can be maintained in the PSA tree of the administrator workbench. That isPartner why the Change Log also has a technical key that consists of the request, data package, and record number. Upload and activation process: New data is loaded to the Data Store Object and theUse technical key is added to the records. Requests can be loaded independently from each other (sequentially or in parallel). All requests are stored in the activaton queue first. Activation can be triggered manually or automatically. At the beginning of the activation, the data is sorted by the semantic key and the technical key. Therefore,SAPSAP records with identical semantic keys are activated in the same data package and in the right order. Data packages for activation are then created. The size of those packages can be customized. Those packages can be processed in parallel. The maximum number of packages and the server group the activation runs on can alsoPartnerUse be customized.InternalOnly 34 2006 SAP AG. All rights reserved. 2006/Q2 43. BW360 Lesson: Data Store Object Architecture Lesson Summary You should now be able to: Describe the Data Store Object Architecture. Describe the process of activating Data Store Objects.InternalOnlyPartnerUseSAPSAPPartnerUseInternalOnly 2006/Q2 2006 SAP AG. All rights reserved.35 44. Unit 2: InfoProvidersBW360 Lesson: MultiProvider Lesson Overview This lesson will help you understand the concept of MultiProviders and explain the types of queries on MultiProvider. It will also help you describe high-level partitioning. Lesson Objectives InternalOnly After completing this lesson, you will be able to: Describe how to create a MultiProvider. Explain the performance implications of query processing on MultiProviders.Partner List the administration and performance benefits of utilizing Multiproviders. Business Example Use As an employee of the Data Warehousing department of a chemical company, you need to improve the performance of a query. A smaller-sized query results in faster read performance. To do this, you can divide a query into sub-queries that run SAP against the smaller basic InfoCubes. This can be achieved by using MultiProvidersSAP that break reporting scenarios down into smaller units. As a result, you need to create MultiProviders. Partner Overview on MultiProviderUse BI Partitioning: Concepts MultiProviders are a type of partitioning on a conceptual level.Internal Only 36 2006 SAP AG. All rights reserved. 2006/Q2 45. BW360Lesson: MultiProvider InternalOnlyPartner Use Figure 23: MultiProvider Example Plan InfoCube has a few columns. SAPSAP Actual InfoCube has several columns. If you use both in one Cube, you would end up with a sparse InfoCube. Reporting Benefits PartnerUse MultiProviders break reporting scenarios down into smaller units. Specificqueries run fast against the smaller basic InfoCubes, and a small amount of datais read. Smaller sized datasets result in faster read performance.Internal A query against a MultiProvider is divided into sub-queries that run againstthe smaller basic InfoCubes.These sub-queries are a form of parallel queryprocessing. Parallel processing is generally faster than queries executed Onlysequentially. These sub-queries also can run against the aggregates built forthe BasicCubes. Disadvantages:Overhead for splitting queries (may be minimal). 2006/Q2 2006 SAP AG. All rights reserved.37 46. Unit 2: InfoProviders BW360 Data Load Benefits Each load request is a relatively small set of data being loaded into a relatively small InfoCube. Fewer records to load, and a smaller data target imply better load performance. Disadvantages- None. Sub-queries can run against the aggregates of the Basic Cube, but the OLAP processor does not combine several aggregates as it sometimes does for normal query processing. In rare cases, this can lead to degraded performance.InternalOnly Multi Providers MultiProviders are a combination of InfoProviders (database union). NoPartner additional data storage. Queries on MultiProviders are split automatically and distributed toUse InfoProviders.Usage is transparent for reporting.SAPSAPPartnerUseInternal Figure 24: Query on MultiProvider - PARALLELOnly If enough system resources are available, queries on MultiProviders are split up to access in parallel the different BasicCubes. Every sub-query runs with its own workprocess, so you need more system resources while they run. 38 2006 SAP AG. All rights reserved. 2006/Q2 47. BW360 Lesson: MultiProvider The run time of the query is like the longest access to one BasicCube, in this example 40 seconds.InternalOnlyPartnerUse Figure 25: Query on MultiProvider - NOPARALLEL Runtime of the query is now the sum of all accesses to the different Aggregates or InfoCubes, in this example (15+1+3+2+2) 23 seconds.SAPSAPPartnerUseInternalOnly Figure 26: Non-Parallel Reads 2006/Q2 2006 SAP AG. All rights reserved. 39 48. Unit 2: InfoProviders BW360 In the following cases, the system chooses sequential (non-parallel) processing: You want to In table RSADMIN, entry QUERY_MAX_WP_DIAG has value (column value) 1. The query is configured for non-parallel processing in RSRT. The entire query consists of one sub-access only. The query is running in a batch process. The query was started from the query monitor (transaction RSRT) using various InternalOnly debug options (for example, SQL query display, execution plan display). The query requests non-cumulative key figures. Insufficient dialog processes are available when the query is executed. These are required for parallel processing.Partner The result of the query is saved in a file or a table. Use SAPSAP PartnerUseInternal Only 40 2006 SAP AG. All rights reserved.2006/Q2 49. BW360Lesson: MultiProvider Lesson Summary You should now be able to: Describe how to create a MultiProvider. Explain the performance implications of query processing on MultiProviders. List the administration and performance benefits of utilizing Multiproviders.InternalOnlyPartnerUseSAPSAPPartnerUseInternalOnly 2006/Q2 2006 SAP AG. All rights reserved. 41 50. Unit 2: InfoProviders BW360 Lesson: Virtual Providers Lesson Overview This lesson describes the purpose and benefits of creating VirtualProvides. Lesson Objectives After completing this lesson, you will be able to: InternalOnly Create Virtual Providers. Describe the benefits of Virtual Providers. Explain the impact on query performance when Virtual Providers are read.Partner Business Example The data that you need for analysis resides on the source system. You need to be able Use to read the data, real time, from the source system. Virtual Providers SAPSAP PartnerUseInternal Only Figure 27: SAP Virtual Provider Architecture A Virtual Provider is a type of InfoCube where the data is not managed in BI. The data is managed externally. Only the structure of the VirtualProvider is defined in BI. The data is read for reporting using an interface with another system. Using a VirtualProvider , reporting can be done on data from external systems without having to physically store transaction data in BI. A VirtualProvider can be created to read data from an external SAP system or from an external non-SAP system. 42 2006 SAP AG. All rights reserved.2006/Q2 51. BW360 Lesson: Virtual ProvidersInternalOnlyPartnerUse Figure 28: Example: Using a Virtual Provider for Data Reconciliation Data reconciliation for DataSources allows you to ensure the consistency of data that has been loaded into BI and is available and used productively there. DataSAPSAP reconciliation is based on a comparison of the data loaded into BI and the application data in the source system. The data in the source system is accessed directly to perform this comparison. The term Productive DataSource is a DataSource that is used for data transfer in the productive operation of BI. Data reconciliationPartner DataSource is a DataSource that is used as a format for accessing the application dataUse in the source system directly. With this method, BI transaction data can be compared with the transaction data on the source system. The data from the DataStore object can be combined with the dataInternal that is read directly by creating a Multiprovider. Queries based on the MultiProvider, can compare the loaded data with the application data in the source system.Only 2006/Q2 2006 SAP AG. All rights reserved.43 52. Unit 2: InfoProvidersBW360 There are 3 types of VirtualProviders: VirtualProvider based on Data Transfer Process This type of VirtualProvider is defined based on a DataSource or an InfoProvider and uses the same characteristics and key figures. There is no need to program interfaces in the source system. The same extractors are used to select data in the source system as you use to load data into the BI system. This type of Virtual InfoProvider is used when an SAP system is the source system, VirtualProvider with BAPIs InternalOnly VirtualProviders whose transaction data for reporting is read from an external system using a BAPI. Any read tool that supports the interface for a non-SAP system can be used. Since the transaction data is not managed in the BI system, there is very little administrative effort on the BI side.Partner VirtualProvider using Function Modules This Virtual InfoProvider displays data from non-BI data sources in BI without Use having to copy the dataset into the BI structures. The data can be local or remote. This method can transform the data before it is passed to the OLAP processor. In comparison to other VirtualProviders, this Virtual InfoProvider is more generic. It offers more flexibility, but also requires a higher implementation effort SAPSAP PartnerUseInternal Only 44 2006 SAP AG. All rights reserved. 2006/Q2 53. BW360 Lesson: Virtual Providers InternalOnlyPartner Use Figure 29: Virtual Provider using BAPI During query execution, the data is read on the source system. SAPSAP The structures which store the data are designed for transactional performance not optimized for reporting performance. Virtual Providers offer one option for providing operational reporting without Partner storing transaction data within BI.Use Summarized data can be stored within BI InfoCubes for analysis reporting. Reporting on transactional data might be less utilized, and therefore aperformance trade-off may be desirable. Most queries would run fastInternalsince they go against summarized data, but the rare operational reportwill require a longer time to run. The data is loaded when the report is executed. Only The total amount of data loaded to the Data Targets is reduced, therebyimproving the performance of the normal data loads. Loading data when a report is run adds another component to the responsetime observed by the end user. 2006/Q2 2006 SAP AG. All rights reserved.45 54. Unit 2: InfoProviders BW360 Direct Access Any DataSource (transaction datasource or master data datasource), that supports the relevant mode in the metadata can be accessed directly using the data transfer process. DataSources for source systems of type File and DB Connect are also available for direct access. The Data Transfer Process can be used to access data in an InfoProvider directly. The prerequisite is that the transformation and dataflow must be established between the source and target object. InternalOnlyPartner Use SAPSAP PartnerUseInternal Only 46 2006 SAP AG. All rights reserved.2006/Q2 55. BW360 Lesson: Virtual Providers Lesson Summary You should now be able to: Create Virtual Providers. Describe the benefits of Virtual Providers. Explain the impact on query performance when Virtual Providers are read. Related Information InternalOnly See https://service.sap.com/biHow to....Create Virtual InfoProvider with services.Partner Use SAPSAP PartnerUseInternal Only 2006/Q2 2006 SAP AG. All rights reserved. 47 56. Unit 2: InfoProvidersBW360 Lesson: Real-time InfoCubes Lesson Overview In this lesson, you will learn how to create a Real-time InfoCube and load data into it. Lesson Objectives After completing this lesson, you will be able to:InternalOnly Create a Real-time InfoCube and write into it Business Example Your organization currently uses InfoCube. While writing data to these, each userPartner creates his own request ID. As a result, the F-fact table consists of many small requests, which in turn leads to bad performance. As an employee of this chemical company, you need to create a transaction InfoCube then write data to it.Use Real-time InfoCubesSAPSAP Requested functionality: Users would like to write their own data into data targets, usually small amounts of data. Real-time updates are done in BI.PartnerUse Problem Writing into InfoCube: each user would create own request ID,F-fact table would consist of many small requests bad performance.Internal Solution Real-time InfoCube all users will write into the same requestOnly The Real-time InfoCube is a BI function, although it is heavily used in applications like Business Planning and Simulation, BPS, during planning functions. The idea behind a Real-time InfoCube is that in some applications only small amounts of data need to be written to an InfoCube. The point about this requirement is that an InfoCube is designed for mass data loads. Hence, SAP needed a technology to deal with lots of small updates in an efficient way. The Real-time InfoCube does not create a new Request ID for each data load. All users share the same request in an InfoCube. 48 2006 SAP AG. All rights reserved. 2006/Q2 57. BW360 Lesson: Real-time InfoCubesInternalOnlyPartner Figure 30: Business Scenario - BPSUse On this graphic, you can a see a typical scenario where a Real-time InfoCube is used. The scenario above is Business Planning and Simulation, BPS, with a Business Consolidation System (BCS) scenario. There are two types of data entries for this application: (1) user enters the data manually, (2) run automatic planning functionsSAPSAP which might copy or revaluate data from existing records. In both upload cases, the BPS application calls an Real Time interface in order to write the data directly into the InfoCube without any data staging technologies. The Real Time interface is a function module which was originally developed for Real TimePartnerUse applications, but can be used for other applications as well.InternalOnly Figure 31: Creating Real-Time InfoCubes 2006/Q2 2006 SAP AG. All rights reserved. 49 58. Unit 2: InfoProvidersBW360 The screen shot shows how to create a Real-time InfoCube. The creation of a normal InfoCube and a Real-time InfoCube is similar. For a Real-time InfoCube the check box Real-time must be selected. InternalOnlyPartner Use SAP Figure 32: Writing into a Real-time InfoCubeSAP An F-Fact table consists of different requests. In the example above, the InfoCube consists of three requests, the first two requests are closed requests, but the third request is an open request. All users write into the same (open) request, it can also PartnerUse happen that one User writes multiple times into that request. The open request in the Data Warehousing Workbench is displayed with a yellow status information. The short text for all the InfoPackages which were or are a open request just indicates that the request was created by the Real Time interface.Internal The closed requests do have status information, but they do not have any monitor entries. Only 50 2006 SAP AG. All rights reserved. 2006/Q2 59. BW360 Lesson: Real-time InfoCubes Accessing a Real-time InfoCube 1. Possibility: BI InterfaceNormal BI technologyInfoPackage 2. Possibility: Real Time interface Read function modules InternalOnlyRSDRI_INFOPROV_READRSDRI_INFOPROV_READ_RFC Write function modulesRSDRI_CUBE_WRITE_PACKAGEPartnerRSDRI_CUBE_WRITE_PACKAGE_RFC No InfoPackages, Use Basically there are two possibilities to load data to a Real-time InfoCube. The first possibility is to load the data via the BI interface with standard data staging. The second possibility is to load the data using the Real Time interface. To load data to a Real-time InfoCube using he Real Time interface, different function modules must SAP be called.SAP If these function modules are used, no InfoPackages are used. The function modules provide direct access to the Real-time InfoCube. Partner See note 302937 for debugging possibilities.Use Switching Data Load Technologies Switch Real Time Interface BI InterfaceInternalUnsaved data will be lost Switch BI Interface Real Time Interface OnlyAll requests have to be green or redNot possible if yellow request exist Switch via1.DataWarehousing Workbench manual (see screenshot on the next graphic)2.Function moduleRSAPO_SWITCH_TRANS_TO_BATCHRSAPO_SWITCH_BATCH_TO_TRANS 2006/Q2 2006 SAP AG. All rights reserved. 51 60. Unit 2: InfoProviders BW360 Different things have to be considered if the data load technology will be switched in order to guarantee a problem free operation. The switch from Real Time Interface to BI interface will close the open request and all data which is not saved will be lost (for example, manual data entry in BPS-BCS). The user does not recognize the switch until the user will try to save his or her data. In order to avoid losing data, this maintenance function should be done only when there are no users actively planning.InternalOnlyPartnerUseSAPSAP Figure 33: Switching a Real-Time InfoCubePartnerUse The screen shot above just shows how the data load technology of a Real-time InfoCube can be switched. Regardless of the data load technology, the InfoCube is in both cases a Real-time InfoCube.InternalOnly 52 2006 SAP AG. All rights reserved.2006/Q2 61. BW360 Lesson: Real-time InfoCubes InternalOnlyPartner Figure 34: Closing of an Open Request Use The open request will be closed automatically after 50,000 data records. This threshold value cannot be changed. If the open request should be closed earlier, a function module (rsapo_close_trans_re- quest) can be used. SAPSAP Furthermore, the request will be closed if the data load technology is switched. PartnerUseInternal Only Figure 35: Aggregates and Real-time InfoCube 2006/Q2 2006 SAP AG. All rights reserved.53 62. Unit 2: InfoProviders BW360 In order to see data of an open request, the variable 0s_rqmrc has to be activated from business content. Afterwards, this variable has to be used in in the free characteristics or filter section. The variable can be found in the packet dimension in BEx. See note 382744 for a description of the explanations above. If that variable is used for reporting, the system can access data from an aggregate and the data which is missing in the aggregate is taken out of the open request. This functionality guarantees that the technique of performance tuning with aggregates can still be used for Real-time InfoCubes. InternalOnlyPartner Use SAPSAP PartnerUseInternal Only 54 2006 SAP AG. All rights reserved.2006/Q2 63. BW360Lesson: Real-time InfoCubes Exercise 3: Real-Time InfoCubes Exercise Objectives After completing this exercise, you will be able to: Create and load data into a Real-Time InfoCube. Business ExampleInternalOnly A possible business scenario would be realtime updates into BI where some application (in this exercise a simple ABAP) writes data directly into a Real-Time InfoCube. Task 1:Partner Creation of a Real-Time InfoCube 1. Create your Real-Time InfoCube.UseCopy the Real-Time InfoCube T_TIC00 to T_RTC##, choose Real-TimeInfoCube ## for the description.Choose the same InfoArea for your InfoCube as the InfoArea used forT_TIC00. Although you copy the Real-Time InfoCube you have to set the flagSAPSAPReal-Time, otherwise you do not have a Real-Time InfoCube. 2. Create your Real-time BI application.Copy the report ZT_BW360_FILL_TCUBE to ZT_BW360_FILL_TCUBE_##PartnerUseOpen the ABAP editor and change the necessary lines of coding.Change every T_TIC00 to T_RTC## in the coding. (It has to be changed threetimes.)InternalCheck and activate your ABAP, execute it twice. Task 2:Only Technology of open requests 1. From the Data Warehousing Workbench, check how the open request isdisplayed. Check the fact table of your InfoCube. Note that both data loads havethe same request ID. 2. Close your open request. 2006/Q2 2006 SAP AG. All rights reserved.55 64. Unit 2: InfoProviders BW360 Solution 3: Real-Time InfoCubes Task 1: Creation of a Real-Time InfoCube 1.Create your Real-Time InfoCube. Copy the Real-Time InfoCube T_TIC00 to T_RTC##, choose Real-Time InfoCube ## for the description. InternalOnly Choose the same InfoArea for your InfoCube as the InfoArea used for T_TIC00. Although you copy the Real-Time InfoCube you have to set the flag Real-Time, otherwise you do not have a Real-Time InfoCube. a) Creation of Realtime BI InfoCube.PartnerGoto transaction RSA1 choose Modeling then InfoProvider.Goto BW Training BW360 Performance and Administration Unit1. UseRight mouse on Unit1 then choose Create InfoCube. Field NameValues SAP InfoCubeT_RTC##SAP InfoCube DescriptionReal-Time InfoCube ## Copy from T_TIC00 Partner InfoCube Type BasicCube, Real-TimeUse 2.Create your Real-time BI application. Copy the report ZT_BW360_FILL_TCUBE to ZT_BW360_FILL_TCUBE_##Internal Open the ABAP editor and change the necessary lines of coding. Change every T_TIC00 to T_RTC## in the coding. (It has to be changed three Only times.)Continued on next page 56 2006 SAP AG. All rights reserved.2006/Q2 65. BW360Lesson: Real-time InfoCubesCheck and activate your ABAP, execute it twice.a) Goto transaction SE38 and enter ZT_BW360_FILL_TCUBE, then choose copy.Field NameValuesTarget programZT_BW360_FILL_TCUBE_## Press Enter. Exchange in lines 18, 20 and 23 T_TIC00 with T_RTC##.InternalOnly Press save, checkand activate. Go back to transaction SE38 and press the execute (F8). Press execute(F8) once more. You have now loaded two sets of data into your new InfoCube. ThisPartner effectively simulates planning steps that users would carry out in an BPS planning scenario.Use Task 2: Technology of open requestsSAP 1. From the Data Warehousing Workbench, check how the open request isSAPdisplayed. Check the fact table of your InfoCube. Note that both data loads havethe same request ID.a) Goto transaction RSA1 choose Modeling then InfoProvider.PartnerUse Goto InfoArea BW Training BW360 Performance and Administration Unit1. Right mouse click on your InfoCube Real-Time InfoCube ##. Choose manage and the tabstrip Requests.Internal You see one request without a QM status, this is your open request. Goto transaction SE16.OnlyField NameValuesTable Name/BIC/FT_RTC## Press Table Content (F7) and then Execute (F8). In the column for the InfoPackage you see that all data records have the same request number.Continued on next page 2006/Q2 2006 SAP AG. All rights reserved.57 66. Unit 2: InfoProvidersBW360 2.Close your open request. a) To close the request go to transaction SE37. Field NameValues Function module RSAPO_CLOSE_TRANS_REQUESTPress single test (F8). InternalOnly Field NameValues I_INFOCUBET_RTC##Press execute (F8). You see exactly the data you expect compared to thePartnerfact table. Use SAPSAP PartnerUseInternal Only 58 2006 SAP AG. All rights reserved. 2006/Q2 67. BW360Lesson: Real-time InfoCubes Lesson Summary You should now be able to: Create a Real-time InfoCube and write into itInternalOnlyPartnerUseSAPSAPPartnerUseInternalOnly 2006/Q2 2006 SAP AG. All rights reserved.59 68. Unit 2: InfoProvidersBW360 Lesson: Data Store Object for Direct Update Lesson Overview In this lesson, you will learn to create a Data Store Object for Direct Update and write to it. Lesson Objectives After completing this lesson, you will be able to:InternalOnly Create a Data Store Object for Direct Update. Business ExamplePartner Your organization currently uses an Data Store Object. While writing data to Data Store Object, each user writes into the same activation queue and starts the activation. This in turn leads to bad performance. You need to create a Data Store Object forUse Direct Update. Creation of a Data Store Object for Direct UpdateSAPSAPPartnerUseInternalOnly Figure 36: Create Data Store Object for Direct Update A Data Store Object for Direct Update is created like any other Data Store Object. In the definition of the Data Store Object, you simply have to change the type from standard to Direct Update. 60 2006 SAP AG. All rights reserved. 2006/Q2 69. BW360 Lesson: Data Store Object for Direct Update InternalOnlyPartner Use Figure 37: Writing into a Data Store Object for Direct Update A Data Store Object for Direct Update just consists of the active data table. Although the system creates the delta queue table and activation queue table, it wont use these tables. SAPSAP This restriction means that no delta update from a Data Store Object for Direct Update to another data target is possible. The restriction itself is due to the fact that no standard staging techniques are used. PartnerUse Writing into a Data Store Object for Direct Update RSDRI_ODSO_INSERT RSDRI_ODSO_INSERT_RFCInternal RSDRI_ODSO_MODIFY RSDRI_ODSO_MODIFY_RFC Only RSDRI_ODSO_UPDATE RSDRI_ODSO_UPDATE_RFC RSDRI_ODSO_DELETE_RFC Due to performance reasons, it should be considered carefully which function module will be used. The insert function module should only be used if it can be ensured that the operation will be an insert and not an update. The same is true for the update function module 2006/Q2 2006 SAP AG. All rights reserved.61 70. Unit 2: InfoProvidersBW360 However, when either an Update or an Insert could occur, the function module modify should be used. The modify function module will first try to update an existing set of data, and if such a data record does not exist, an insert will be performed. There is no RSDRI_ODSO_DELETE function module. Additional Information Reading from Data Store Object for Direct Update BAPI_ODSO_READ_DATAInternalOnly InfoSet Query No BEx Query In order to read from a Data Store Object for Direct Update, either a BAPI or anPartner InfoSet Query can be used, but no standard BEx Query. Switching a Data Store Object for Direct Update is only possible if it is empty.UseSAPSAPPartnerUseInternalOnly 62 2006 SAP AG. All rights reserved.2006/Q2 71. BW360Lesson: Data Store Object for Direct Update Lesson Summary You should now be able to: Create a Data Store Object for Direct Update.InternalOnlyPartnerUseSAPSAPPartnerUseInternalOnly 2006/Q2 2006 SAP AG. All rights reserved.63 72. Unit Summary BW360Unit SummaryYou should now be able to:Describe the SAP BI Extended Star Schema.Describe the performance aspects of the Star Schema.Explain the difference between a display attribute and a navigational attribute.Describe the purpose of line item dimensions.Describe the Data Store Object Architecture.Describe the process of activating Data Store Objects. InternalOnlyDescribe how to create a MultiProvider.Explain the performance implications of query processing on MultiProviders.List the administration and performance benefits of utilizing Multiproviders.Create Virtual Providers.PartnerDescribe the benefits of Virtual Providers.Explain the impact on query performance when Virtual Providers are read. UseCreate a Real-time InfoCube and write into itCreate a Data Store Object for Direct Update. SAPSAP PartnerUseInternal Only 64 2006 SAP AG. All rights reserved.2006/Q2 73. Unit 3Process Chains InternalOnly Unit Overview In this lesson, you will learn about the design, properties and structure of process chains. Next, you will learn about process chain maintenance.Partner Unit Objectives After completing this unit, you will be able to: Use Describe the design properties of process chains. Describe the structure of a process chain. Create a Process Chain. SAPSAP Describe the three different views to process chains Explain process chains and data target administration Describe system-wide monitoring of process chains PartnerUse Unit Contents Lesson: Process Chains Design ................................................... 66 Lesson: Managing Process Chains ............................................... 76InternalExercise 4: Create a Process Chain .......................................... 93 Only 2006/Q2 2006 SAP AG. All rights reserved.65 74. Unit 3: Process ChainsBW360 Lesson: Process Chains DesignLesson OverviewIn this lesson, you will learn about the design and properties of process chains. Next,you will learn about Process Chain Maintenance. Finally, you will learn about thestructure of a process.Lesson Objectives InternalOnlyAfter completing this lesson, you will be able to: Describe the design properties of process chains. Describe the structure of a process chain.Partner Create a Process Chain.Business Example UseYour organization performs different activities that have to be scheduled to preparethe data for reporting. The sequence of activities is critical and complex scheduling isnecessary because of the dependencies of the different activities. As an employee of SAPthe company, you need to build self-defined event chains to solve the dependenciesSAPbetween the different processes. PartnerUseInternal Only 66 2006 SAP AG. All rights reserved. 2006/Q2 75. BW360 Lesson: Process Chains Design Design Properties InternalOnlyPartner Use SAPSAP Figure 38: Introduction: Typical Data Load Cycle PartnerUseInternal Only 2006/Q2 2006 SAP AG. All rights reserved.67 76. Unit 3: Process ChainsBW360Transaction RSPC: Process Chain Maintenance InternalOnlyPartner Use SAPFigure 39: Transaction RSPC: Process Chains MaintenanceSAPTransaction RSPC: Process Chain Maintenance enables: Easy creation of process chains via Drag & Drop PartnerUse Creation of itemsWhen you connect processes, you are prompted to indicate whether the subsequentprocess should execute based on the success or the failure of the predecessor process.In other words, it is possible to schedule a process to run only if the predecessorInternalprocess fails. Only 68 2006 SAP AG. All rights reserved. 2006/Q2 77. BW360Lesson: Process Chains Design Collector Processes Collectors are used to manage multiple processes that feed into the samesubsequent process. The collectors available for BW are: AND: All of the processes that are direct predecessors must send an eventin order for subsequent processes to be executed. OR: At least one predecessor process must send an event.The first predecessor process that sends an event triggers the subsequentInternalOnlyprocess. EXOR: Exclusive ORSimilar to regular OR, but there is only ONE execution of the successorprocesses, even if several predecessor processes raise an eventPartner Collector processes allow the designer of a process chain to trigger a subsequent process based on whether certain conditions are met by multiple predecessor processes.Use Application processes are the other type of processes these represent BW activities such as aggregate rollup. Application ProcessesSAPSAP Application processes represent BW activities that are typically performed aspart of BW operations. Examples include:Data loadPartnerUseAttribute/Hierarchy Change runAggregate rollupReporting Agent Settings Other special types of application processes exist:Internal Starter a process that exists to trigger process chain execution ABAP programOnly Another process chain Remote process chains Operating System command Customer built processes A starter process is part of every process chain. 2006/Q2 2006 SAP AG. All rights reserved.69 78. Unit 3: Process Chains BW360InternalOnlyPartnerUseFigure 40: Start ProcessThe process variant could be used just by one process chain.SAPSAPEach process chain could be started manually or via RFC connection with the functionmodule, RSPC_API_CHAIN_START.Basic PrinciplesPartnerUse Openness abstract meaning of process: Any activity with definedstart and defined ending. Security founding on the batch administration:Internal Processes get planned before they run and can be viewed with standardbatch-monitor. Dumps and Aborts are caught and thus can be treated as failures.Only Responsibility:Each process have to care for all necessary information and dependencies for its own, when it is added to the process chain.A predecessor process is not responsible to start the correct successors and provide them with necessary information. 70 2006 SAP AG. All rights reserved.2006/Q2 79. BW360 Lesson: Process Chains Design Functions of the predecessor and successor processes: The predecessor process runs then signals when it has completed, writinginformation about the completed task to a database table (RSPCPROCESSLOG). The successor process reacts to the event which is triggered by the predecessor,reads the database table (RSPCVARIANT, RSPCVARIANTATTR) to obtainany needed information, then executes. Additional administrative process is to check the sequence of the processes. InternalOnly Structure of a ProcessPartner Use SAPSAP PartnerUseInternal Figure 41: Structure of a Process A process type is an ABAP OO object. Only The object is initiated when it is time for a process to run. The variant holds the specific configuration information for a process. Variant Configuration Each process can have one or several variants. The maintenance of variant is specific for every process type. 2006/Q2 2006 SAP AG. All rights reserved. 71 80. Unit 3: Process Chains BW360Instance: (instance for process is like request for infopackage) A snapshot of the variant configuration (table RSPCVARIANT*) at runtimeand written to table RSPCINSTANCE. Log information about the different processes collected at runtime and written totable RSPCPROCESSLOG.InternalOnlyPartnerUseSAPSAPFigure 42: Example: Structure of a Process - Process TypePartnerUseStandard process types can be changed depending on their name space (transactionSE06).You can create your own process types (see HOW TO - Guides on service.sap.com/biInternal service How To ... Guide).RSPC Settings Maintain Process type. Table/maintenance viewRSPROCESSTYPES) (SM30)] contains all information about the defined processOnlytypes. 72 2006 SAP AG. All rights reserved.2006/Q2 81. BW360 Lesson: Process Chains DesignInternalOnlyPartnerUse Figure 43: Example: Structure of a Process - Variant Variants have to be created for the process types. With variant settings, the process type gets necessary information for execution.SAPSAP For example, if you assign the process type Attribute Change run to a process chain, you must define a variant. With this variant, you have to define the InfoObjects for which you want to activate the master data. There are four different possibilities:Partner HIERARCHY: Direct selection of the hierarchy, which need to be activatedUse INFOOBJECT: Direct selection of the infoObjects, which need to be activated LOADING: Indirect selection: Reference to an InfoPackage, which must beloaded before in the process chain. Combined with the metadata of these objectsInternaland the instance information the system derives the affected InfoObjects andhierarchies. If the chosen LOADING object is not in the process chain, thesystem automatically inserts the chosen infopackage in the process chain.Only REPORTVARIANT: Indirect selection: Reference to a change run variantwhich you can define with RSDDS_AGGREGATES_MAINTAIN (SE38) orTCode RSATTR Executing the Attribute/hierarchy change run with Variant:Instead of applying the InfoObjects or hierarachies directly to theprocess variant in RSPC you can create a central variant for the reportRSDDS_AGGREGATES_MAINTAIN. You can assign InfoObjects andhierarchies to this report variant. This central variant could be used by severalprocess variants in RSPC. The benefits are central maintenance. 2006/Q2 2006 SAP AG. All rights reserved. 73 82. Unit 3: Process ChainsBW360Using a reference object like LOADING or REPORTVARIANT is sometimes moreflexible. InternalOnlyPartner Use SAPSAP PartnerUseInternal Only 74 2006 SAP AG. All rights reserved.2006/Q2 83. BW360Lesson: Process Chains Design Lesson Summary You should now be able to: Describe the design properties of process chains. Describe the structure of a process chain. Create a Process Chain.InternalOnlyPartnerUseSAPSAPPartnerUseInternalOnly 2006/Q2 2006 SAP AG. All rights reserved.75 84. Unit 3: Process Chains BW360 Lesson: Managing Process ChainsLesson OverviewThis lesson will focus on the three different views to process chains. It will thendiscuss process chains and data target administration. Finally, it will give you anoverview of system-wide monitoring of process chains.Lesson Objectives InternalOnlyAfter completing this lesson, you will be able to: Describe the three different views to process chains Explain process chains and data target administrationPartner Describe system-wide monitoring of process chainsBusiness Example UseYour organization uses process chains to perform activities in which sequence andscheduling is critical. As an employee of the organization, you need to performmaintenance checks, such as ensuring consistency and checking the plan status of SAPthe process chains. You can use different views and display object trees for suchSAPmaintenance activities.Designing Process Chains PartnerUseA process chain is a sequence of processes that are organized to perform certainfunctions, such as loading master data or transaction data. Process chains can bescheduled or triggered by events. Some processes may trigger an event that can, inturn, start other processes.InternalProcess Chains: Automate the complex job schedules in B.I Only Visualize the processes by using network graphics . Centrally control and monitor the processes.A process chain consists of a start process, individual application processes and thecollection processes.Process Chains all have a Start process. All other chain processes are scheduled towait for an event. 76 2006 SAP AG. All rights reserved.2006/Q2 85. BW360Lesson: Managing Process Chains The application processes are the actual processes. BI supports process types of the following categories: General services Load process and post processing processes Data target administration processes, Reporting Agent processes Other BI processes, as well as custom created processes. InternalOnlyPartner Use SAPSAP Figure 44: Process Chain General Services PartnerUse The OS Command allows you to check, for example, whether a particular file exists in a directory before you load data to it. If the file is not in the directory, the load process can be repeated at pre-determined intervals. The workflow and decision process types support the event Process ends with complexInternal status. This process type controls the process chain process on the basis of multi-value decisions. The process does not have to end simply successfully or with errors; for example, the week day can be used to decide that the process was successful and Only determine how the process chain is processed further. With the workflow option, the user can make this decision. With the decision process type, the final status of the process, and therefore the decision, is determined on the basis of conditions. These conditions are stored as formulas. 2006/Q2 2006 SAP AG. All rights reserved. 77 86. Unit 3: Process ChainsBW360InternalOnlyPartnerFigure 45: 3 Different Views to Process ChainsUseThere are three main views in the icon bar with different views: Planning view (shows if the process chain is active)SAPSAPGrey: Unplanned processes (such as not activated process chain)Green: Planned processes (process chain is active and the start process has been released)Yellow: Planned but unknown processesPartnerUseRed: Multiple planned processes Checking view (consistency check such as double used start variants, missingindex deletion and recreation, wrong references in variants.InternalGreen: Error-free processesYellow: Process with warningsRed: Process with errorsOnly Log view Grey: Not yet run Green: Finished without error Yellow: Running Red: Aborted or failed 78 2006 SAP AG. All rights reserved.2006/Q2 87. BW360 Lesson: Managing Process Chains Note that the log information is usually a mixture of : Log information of maintenance activities for example new process, changeof design, activation) Log information of activities (such as, previous executions of process chains)InternalOnlyPartnerUseSAPSAP Figure 46: Different Object Trees for Process Chain Administration (1)Partner Folders in the process chain are called display components.Use For maintenance of display components you have to use process chains attributes display components.Internal For reassignment of process chain to different display component For creation of new display componentOnly 2006/Q2 2006 SAP AG. All rights reserved. 79 88. Unit 3: Process ChainsBW360InternalOnlyPartnerUseFigure 47: Different Object Trees for Process Chain Administration (2)SAPSAPPartnerUseInternalFigure 48: Maintain Process Chains - Detail ViewOnlyWhen collector processes are built into a process chain, there are actually severalbackground jobs scheduled with events in order to construct the conditional natureof collector processes. 80 2006 SAP AG. All rights reserved. 2006/Q2 89. BW360Lesson: Managing Process Chains The simple view displays the processing chain as it exists logically. The detail view displays the processing chain with the extra collector processes. InternalOnlyPartner Use SAP Figure 49: Maintain MessageSAP Email can be sent to indicate the successful completion of a process too. PartnerUseInternal Only Figure 50: Monitoring Features of the Log View (RSPC) 2006/Q2 2006 SAP AG. All rights reserved.81 90. Unit 3: Process ChainsBW360Process Chains can be copied by selecting Copy from the Process Chain menu. Whena Process Chain is copied, the original Process Chain and all process variants aresaved with a new name.Process Chain attributes are displayed by selecting Attributes from the Process Chainmenu.InternalOnlyPartnerUseFigure 51: Process Chain AttributesSAPSAPIf errors occur while processing alerts can be sent. Process chain maintenance usesalert management for this purpose.The alert is sent to the user who scheduled the process chain. Additional recipientsPartnermay be assigned by roles or specifying individual users in alert category maintenanceUse(transaction ALRTCATDEF).The recipients display program displays the alerts. The display program can be theUniversal Worklist (UWL) in the portal, the alert inbox (transaction ALRTINBOX) orInternalan application that calls alerts using API.Alerts can also be sent by email, fax or SMS. This is dependent on the configuration.OnlyIf you are using Process Chains in a client-specific application, you use theclient-specific display to determine the clients in which the chain can be used. Whenthe client number is entered here, the Process Chain can only be displayed, executed,edited and scheduled from this client.When a Process Chain is executed the user can be displayed by selecting Executionuser from the Process Chain menu. The default setting Background user can also bechanged to execution user here. 82 2006 SAP AG. All rights reserved. 2006/Q2 91. BW360 Lesson: Managing Process Chains During the check, the system calculates the number of parallel processes according to the structure of the tree. It compares the result with the number of background processes on the selected server (or the total number of all available servers if no server is specified in the attributes of the process chain). If the number of parallel processes is greater than the number of available background processes, the system highlights every level of the process chain where the number of processes is too high, and produces a warning. Maintenance of Process Chains is protected by the authorization object S_RS_PC. This authorization checks process chain maintenance and locks the process chain, and InternalOnly the processes of the chain, against actions by unauthorized users. Process Chains and Data Target AdministrationPartner Use SAPSAP PartnerUseInternal Figure 52: Process Chain and Data Target Administration Only 2006/Q2 2006 SAP AG. All rights reserved.83 92. Unit 3: Process Chains BW360Process Chains: Facts Process chains are transportable.There are icons for writing to a change request when maintaining a process chain in RSPC.Process chains can be selected from the transport connection wizard within the Data Warehousing Workbench. Special background jobs are run to facilitate the execution of the process chain:InternalOnlyBI_PROCESS_TRIGGERGenerated jobs BI_EVEN*Activation,