1 / 27

Business Planning & Simulation and BW Monitoring

Business Planning & Simulation and BW Monitoring. UNWBW1 – Business Information Warehouse NetWeaver Support Consultant Training. Content. Introduction Reporting Business content Data loading InfoCube Design Aggregates BW-BPS Business Planning & Simulation

gaius
Télécharger la présentation

Business Planning & Simulation and BW Monitoring

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Business Planning & Simulationand BW Monitoring UNWBW1 – Business Information Warehouse NetWeaver Support Consultant Training

  2. Content • Introduction • Reporting • Business content • Data loading • InfoCube Design • Aggregates • BW-BPS Business Planning & Simulation • Monitoring & Technical Risks

  3. Top Down Top Down Manager · per business unit · per quarter Regional Manager Regional Sales Manager · per region · per month · per customer · per article · per month Bottom Up Bottom Up General Concepts of Planning • Business Planning & Simulation (BPS) enables you to produce planning applications. • Actual data is available in InfoCubes, Planning data is to be determined in planning sessions. There are two main directions: Aggregation Allocation

  4. Planning Area Planning Level Planning Level Planning Package Planning Package Planning Package Planning Package ... ... Objects in Planning (I) • Planning area: A standard planning area is assigned 1:1 to an InfoCube (not necessarily transactional), either local or in a remote system. It provides all characteristics and key figures contained in the InfoCube. Data can also be restricted by using characteristic relationships. A Multi planning area is a view over several standard planning areas. • Planning level: A planning area can be divided into planning levels via restriction to a subset of characteristics and key figures and by selecting certain characteristic values. • Planning package: A planning package is actually used for planning functions or manual planning. It is again a subdivision or subset of a planning level using further restrictions on characteristic values provided by the planning level. A planning level always contains the planning package 0-ADHOC, with selections identical to the planning level. ...

  5. Complexity Functionality Objects in Planning (II) - Methods • Manual planning: A layout that is used to display data and for manual data entry. Each layout is assigned to a planning level and can be executed for each contained planning package. It can be displayed as ALV Grid or as Microsoft Excel spreadsheet. • Planning function: Definition of an automatic function that can be used to manipulate data. There are three main types: • · Predefined planning functions (such as copy, revaluation, distribution,…) • · Fox-formulas (self defined, e.g. quantity x price) • · Exits (self-defined, e.g. calculate revenue depending on number of workdays in company calendar)

  6. The Planning Workbench – BPS0 Hierarchy of Planning Areas, Levels and Packages Detail area for selected object Hierarchy of Planning functions, sequences, parameter groups and layouts (manual planning) assigned to selected planning level

  7. Excel Interface ALV Interface Planning Layout – Manual planning Planning Layouts are used for display and manual entry of planning data. Appearance of characteristics in header, lead or data column can be customized. Totals can be switched on/off and displayed as hierarchy.

  8. Planning Functions and Parameter Groups Each planning function requires in its definition the fields to be changed or the fields for condition, respectively. It is possible to gather planning functions with their parameter groups in a local or global planning sequence. The functions are then executed collectively in dialog or in background. The parameter group determines the values of the parameters of the planning function.

  9. Planning Frontends • Web Interface Web interfaces can easily be customized in the Web Interface Builder using web enhancements like style sheets. Also, the Excel Web component can be used (not shown here). • Planning Folder Interface Planning folders can be configured quite similar to web interfaces via drag&drop. The Excel interface can be used here, too.

  10. Performance Analysis – Tools • Tools for the performance analysis of Planning Functions: • BPS_TRACE: Trace the execution of a planning function • BPS_STAT0: Analysis of single execution of a planning function • BPS_STAT1: Statistical analysis of manual planning, planning functions etc. • STAD • ST03 • ST05 • SM04 • SM50 • ... BPS related System related BPS_STAT0

  11. Content • Introduction • Reporting • Business content • Data loading • InfoCube Design • Aggregates • BW-BPS Business Planning & Simulation • Monitoring & Technical Risks

  12. Monitoring Tools • RSA1 • ST03 • RSRT • RSRV • RSRTRACE • STAD • ST05 • SM04 • SM50 • ... • RSMO • RSPC BW related System related ST03 RSRT

  13. Monitor for Data Extraction and Load (RSMO) Green: successful data extraction / load Yellow: extraction / load not finished Red: extraction / load failed Drill down on failed InfoPackage for details

  14. RSMO Monitor Details Tab Details provides more information about points of failure during extraction and load Select node and right-click for context menu showing options including Help and IDoc details (where appropriate) When a step is highlighted, its status information is shown below

  15. Sizing Project Risks (I) Background There should be a sizing roadmap for all future project steps (for example the GoLive of additional functionality or an increase in data volume).

  16. Sizing Project Risks (II) Background Uploading less than 1 million rows per hour is usually no critical issue. Higher Volumes than 1 million rows per hour can be achieved but this needs to be carefully tested and tuned

  17. BW Sizing Strategy: T-Shirt Model For a detailed sizing use the quicksizer (alias /quicksizer)

  18. High Availability Risks • Background • Not all components are really critical for the customer‘s business. Try to find out. Identify where the customer needs a sophisticated HA concept. For general information see SAP Service Marketplace, alias /ha

  19. Landscape Risks Background Several R/3 Systems connected to one BW System: • Since more than one R/3 source system is used it’s necessary that all R/3 source systems do have a current and valid plug-in installed. • Since more than one source system are connect it’s necessary to organize an upload scenario from the different source system into the BW system that takes care of the workload situation in the source system as well as in the BW system. Additionally, it needs to be organized that time windows for upload are available to minimize the influence of upload during the reporting time windows.

  20. Landscape Complex Landscape Upload from several source systems Connected systems in different time zones

  21. System Management Risks Background Since the data maintenance jobs do have a large impact on the system workload, all kind of these activities need to be coordinated, even though the different application areas are independent from each other.

  22. Data Modeling Risk Background • Operational reporting is typically time critical and the involved objects may become very large over time. It’s very important that customers have a clearly defined retention time for that data. • Tactical reporting and or strategy reporting which normally report over a longer period than operational reporting should not use the operational data for reporting, otherwise the detailed data would have to remain for too long in the system.

  23. Reporting Risks Background The more features and data a query uses and or processes the longer the processing time gets. Additionally large graphics and WAN connection slow down the performance of the queries as well. Performance problems can be avoided if a close monitoring is in place and if the right aggregates are built.

  24. EarlyWatch Alerts EarlyWatch Alert: red rating for BW KPIs  Report is red

  25. EarlyWatch Alerts • BW KPIs – Aggregates • NrDelAggr (Number of Aggregates recommended to delete) • Number of aggregates not used during query execution/aggregates that are almost as large as the InfoCubeAttention: don’t delete them without a careful review! • NrAggr0Call (Number of aggregates with no calls) • Number of aggregates not used at all during query execution • NrBuildAggrCube (Number of aggregates recommended to build - cube level) • Stastistics on Cube level indicate missing aggregates • NrBuildAggrQuery (Number of aggregates recommended to build - query level) • Stastistics on query level indicate missing aggregates

  26. EarlyWatch Alerts • BW KPIs – Runtime • Runtime>20sec • Percentage of queries running more than 20 sec • AvgRuntime • Average runtime of all queries • Avg.OLAPINIT time • Avg.OLAP time • Avg.DB time • Avg.FRONTEND time • FE/DB time • Relation between FRONTEND and DB time • *See Note 130696 for further details*

  27. EarlyWatch Alerts • BW KPIs • DB Size > 10 TB • Nav.Steps • Total number of navigation steps • Indication for the workload • Avg.Cells • Average number of Excel Cells send to Frontend

More Related