PLM318 Analytics in Enterprise Asset Management

PLM318Analytics in Enterprise Asset

ManagementmySAP ERP Operations: Support

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 2006/Q2Course Duration: 2 DaysMaterial Number: 50080292

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

Copyright

Copyright © 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

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

Trademarks

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

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

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

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

VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarksof Citrix Systems, Inc.

� HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.

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

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

EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.comare trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks oftheir respective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLYDISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDINGWITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTSCONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANYKIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOSTPROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDEDSOFTWARE COMPONENTS.

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

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

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

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

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

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

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

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

<Example text> Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2006/Q2 © 2006 SAP AG. All rights reserved. iii

About This Handbook PLM318

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

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor'spresentation.

iv © 2006 SAP AG. All rights reserved. 2006/Q2

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

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

Unit 1: Source Data in the ERP System ...... . . . . . . . . . . . . . . . . . . . . . . . . 1Analyzing Source Data in the ERP System .... . . . . . . . . . . . . . . . . . . . . .2Plant Maintenance Information System (PMIS)... . . . . . . . . . . . . . . . . 13

Unit 2: Data Storage in BW ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Basics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36BI Content Enterprise Asset Management ... . . . . . . . . . . . . . . . . . . . . . 53Working with Queries in Enterprise Asset Management.. . . . . . . . 65

Unit 3: Budget Planning for Plant Maintenance and CustomerService (MCB)..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Budget Planning.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

2006/Q2 © 2006 SAP AG. All rights reserved. v

Contents PLM318

vi © 2006 SAP AG. All rights reserved. 2006/Q2

Course OverviewThis course explains all aspects of reporting that are relevant to Enterprise AssetManagement, from initial operational data and its update in the ERP system todifferent reports in the Business Information Warehouse (BW).

The course therefore provides an interface between application- andtechnology-specific issues. Although we will take a brief look at basic technicalconcepts of BW, we will not discuss administration or the data extraction processin this application. These issues are the responsibility of BW administrators andoperators, and they are dealt with in the relevant BW courses.

Target AudienceThis course is intended for the following audiences:

� Members of the project team

Course PrerequisitesRequired Knowledge

� PLM300 - Maintenance

Recommended Knowledge

� Basic knowledge of Data Warehousing� Basic course on Business Information Warehouse

Course GoalsThis course will prepare you to:

� Describe key elements of reporting in Enterprise Asset Management� Run technical and controlling-specific reports relevant to Enterprise Asset

Management

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

� Run maintenance-specific reports in the ERP system� Explain basic principles of data update in Enterprise Asset Management� Describe data modeling in BW� Explain and use business content for Enterprise Asset Management in BW

2006/Q2 © 2006 SAP AG. All rights reserved. vii

Course Overview PLM318

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

viii © 2006 SAP AG. All rights reserved. 2006/Q2

Unit 1Source Data in the ERP System

Unit OverviewThis unit explains the context in the ERP system by describing how to displayoperational data and update it in PMIS.

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

� List the relevant source data in Enterprise Asset Management� Run different lists that demonstrate the granularity of the source data� Describe the structure of PMIS� Explain the principle of data update� Perform standard analyses

Unit ContentsLesson: Analyzing Source Data in the ERP System ... . . . . . . . . . . . . . . . . . . . . . . .2

Exercise 1: Analyzing Source Data in the ERP System... . . . . . . . . . . . . . . .9Lesson: Plant Maintenance Information System (PMIS) ... . . . . . . . . . . . . . . . . 13

Exercise 2: Plant Maintenance Information System (PMIS) ... . . . . . . . . 25

2006/Q2 © 2006 SAP AG. All rights reserved. 1

Unit 1: Source Data in the ERP System PLM318

Lesson: Analyzing Source Data in the ERP System

Lesson OverviewThis unit demonstrates the different initial operational data available in the ERPsystem.

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

� List the relevant source data in Enterprise Asset Management� Run different lists that demonstrate the granularity of the source data

Business ExampleYou carry out maintenance measures for your technical systems in the ERPsystem, and would like to display an overview of the structure of all available data,to allow you to run specific reports at a later stage.

Source Data in the ERP System

Figure 1: Source Data

Maintenance-related source data is stored in the maintenance history in the ERPsystem. In addition to the notification history, order history, equipment usage list,and the material where-used list, the maintenance history contains the basic datathat can be displayed and evaluated in the form of lists and reports.

2 © 2006 SAP AG. All rights reserved. 2006/Q2

PLM318 Lesson: Analyzing Source Data in the ERP System

Figure 2: Maintenance History - Notifications and Orders

You can use lists and reports to analyze operational data both during and after taskperformance. The system displays the data at the document level in granularand unaggregated form.

Lists and Reports for Technical Objects and MaterialsMultilevel lists

You can use multilevel lists to monitor functional locations and equipment. Theselists allow you use a filter to activate or deactivate different objects (for example,notifications, orders, measuring points).



Figure 3: Multilevel List Functional Locations - Transaction IL07

Serial Number List

You can use the serial number list to monitor inventory-managed equipment.Here, you can display information on equipment and inventory.

Figure 4: Serial Number List - Transaction IQ09



Lists and Reports for Notifications and OrdersOrder and operation list

You can use the order and operation list to monitor, steer, and analyze orders. Youcan select entries based on order header and order operation data. A hitlist displaysorder header and operation data on one screen. As we can see, the system providesa number of options for editing and monitoring standing orders in particular.

Figure 5: Order and Operation List - Transaction IW37N

CO Reports for Orders

In addition to maintenance reports, reports are available in the Controlling (CO)component.

For example, you can set up order groups for specific maintenance order types,such as maintenance orders, to examine the cost situation (for example, a report onplanned and actual costs and any variations that may occur).



Figure 6: CO Reports for Orders - Transaction S_ALR_87012993

Material Availability

You can use the material availability list to steer and monitor spare parts planningin ongoing maintenance orders. This list provides a clear overview of theavailability or reasons for unavailability of stock and non-stock materials fora specific quantity of orders.

Figure 7: Material Availability List - Transaction IWBK

Material Where-Used List

The material where-used list provides information on the usage of materials. Youcan use it to compare planned quantities with the quantities actually withdrawn orwith unplanned withdrawals.



Figure 8: Material Where-Used List - Transaction IW13





Exercise 1: Analyzing Source Data in theERP System

Exercise ObjectivesAfter completing this exercise, you will be able to:� Use lists and reports in Enterprise Asset Management (EAM) and CO, to

display operational source data in the ERP system

Business ExampleYou are a maintenance manager, and would like to display an overview of theinitial ERP data used for reports and analyses in LIS and BW.

Task:Lists and Reports in EAM

1. Check the usage periods for the functional location K1-B01-1 in the firsttwo quarters of 2006.

When was equipment installed or removed?

2. Check the usage list for equipment P-1000-N001 as well. In which periodwas this equipment installed in the functional location K1-B02?

3. Open a material where-used list in the functional location 20 for the firsttwo quarters of 2006.

How many distance rings were reserved, how many withdrawn, and howmany returned?

4. Use a CO report to run a cost analysis of maintenance orders in the functionallocation 20. Select a report that compares the planned and actual costs, andspecifies any variation. Use the order group W20 to identify the orders.

How do you proceed?

What is the cost element breakdown for the costs?



Solution 1: Analyzing Source Data in theERP SystemTask:Lists and Reports in EAM

1. Check the usage periods for the functional location K1-B01-1 in the firsttwo quarters of 2006.

When was equipment installed or removed?

a) SAP Menu→ Logistics→ Plant Maintenance→ Management ofTechnical Objects→ Functional Location→ List Editing→ Display(Multilevel)

Enter the functional location K1-B01-1 and deactivate allindicators in the Filter area. Then activate the indicators FunctLoc,EquipUsagePeriod, and Equipment. Execute the function.

Period from January 01, 2006 to June 30, 2006

EquipUsagePeriod Equipment23.08.2004 1000417114.04.1999 M-1000-N05111.05.2005 P-1000-DF0111.05.2005 P-1000-DF0211.05.2005 P-1000-DF0314.04.1999 P-1000-N00109.09.2002 P-2000-N002

2. Check the usage list for equipment P-1000-N001 as well. In which periodwas this equipment installed in the functional location K1-B02?

a) Using the multilevel lists for the functional location K1-B01-1,double-click equipment P-1000-N001 and

select Extras→ Usage List.

Equipment Installation period on functionallocation K1-B02

P-1000-N001 06.02.1998 � 14.04.1999

Continued on next page



3. Open a material where-used list in the functional location 20 for the firsttwo quarters of 2006.

How many distance rings were reserved, how many withdrawn, and howmany returned?

a) SAP menu→ Logistics→ Plant Maintenance→ MaintenanceProcessing→ History→ Material Where-Used List

Select the order status Outstanding, In process, Completed, enter thefunctional location 20* and the date January 01, 2006 to June 30, 2006.

Material Description Reserved Withdrawn ReturnedKR117185 Distance

plate16 8 (total of

12)4(displayedas -4)

4. Use a CO report to run a cost analysis of maintenance orders in the functionallocation 20. Select a report that compares the planned and actual costs, andspecifies any variation. Use the order group W20 to identify the orders.

How do you proceed?

What is the cost element breakdown for the costs?

a) SAP menu→ Accounting→ Controlling→ Internal Orders→Information System→ Reports for Internal Orders→ Plan/ActualComparisons→ Orders: Actual./Plan/Variance

Controlling area 1000Fiscal year 2006From period 1To period 6Plan version 0Order group W20

Cost elements:

Cost element Description400000 Consumed raw materials 1615000 Repairs655901 PM orders



Lesson Summary

You should now be able to:� List the relevant source data in Enterprise Asset Management� Run different lists that demonstrate the granularity of the source data


PLM318 Lesson: Plant Maintenance Information System (PMIS)

Lesson: Plant Maintenance Information System (PMIS)

Lesson OverviewThis unit provides an overview of the structure and handling of standard analysesin the Plant Maintenance Information System (PMIS).


� Describe the structure of PMIS� Explain the principle of data update� Perform standard analyses

Business ExampleYou would like to obtain an overview of the options available for analyzingbusiness data related to Asset Management, using standard analyzes that do notrequire additional formatting.

To do this, you would like to find out more about how the PMIS is structured andhow data is updated, to make any required changes or set up your own structures.

Data Storage in the Logistics Information System (LIS)

Figure 9: Logistics Information System (LIS)



SAP Logistics offers several application-related information systems, all of whichhave the same user interface and similar basic functions. The way in which data isstored is identical in all Logistics Information Systems. A number of special toolsand working methods serve to highlight the typical character of a Data Warehousein the Logistics Information System.

Individual Logistics Information Systems include:

� Sales Information System (SIS)� Purchasing Information System (PURCHIS)� Inventory Controlling (INVCO)� Warehouse Management Information System (WMIS)� Production Planning Information System (PPIS)� Quality Management Information System (QMIS)� Plant Maintenance Information System (PMIS)� Retail Information System (RIS)

Figure 10: Levels in the LIS

Recent Data Warehouse concepts use a triple-level model to implement moreefficient integrated information systems. The three levels break down overalldata flow, from data acquisition in operational systems to the presentation ofinformation.

Operational integrated applications in Online Transaction Processing (OLTP)systems provide the basis for obtaining information. These systems contain largequantities of master and process data, which is then presented in in informationsystems in a clear and user-friendly manner.



To do this, the application data is broken down into a few, meaningful key figureamounts, and managed separately in the database tables of a Data Warehouse.

At the third level of the Logistics Information System, a number of analysistools are available for evaluating the statistical data obtained. These tools offer awide range of options for effectively analyzing and presenting comprehensivestatistical data, and provide an efficient instrument for rapid decision-making instate-of-the-art managerial environments.

Analyses

Figure 11: Drilldown Lists in a Standard Analysis

Standard analyses contain a wide range of functions for generating comprehensivepresentations and analyses of LIS data.

The data for a standard analysis is identified by defining the analysis object (forexample, purchasing group, vendor or material group) and by setting defaultselections.

The data can then be displayed in a structured form using an initial list, and anumber of drilldown lists. Individual analyses can be archived.

Master data or documents can be displayed using standard application transactionsfrom the different explosion levels.

A number of special functions are available for individual analysis of the keyfigures and characteristics attributes on which an analysis is based. All functionsfor evaluating statistics are supported graphically.



Figure 12: User Settings for a Standard Analysis

For each standard analysis, you can make default settings centrally that are validfor each user. These settings may also be controlled on a user-specific basis.You can also configure default settings for the standard drilldown, and predefinekey figures, a selection period and different list parameters for designing the listlayout. You can change the key figure selection and list layout design in thestandard analyses at a later stage.

Data WarehouseThe individual physical tables of the Logistics Data Warehouse are known asinformation structures, or info structures for short. These are described in atransparent manner in the SAP Data Dictionary. Info structures are structuredin the usual way.



Figure 13: Data Warehouse

Analysis objects from the day-to-day business market are transferred as evaluationgroups to the info structures in the form of characteristics. Statistical informationis updated for characteristics such as functional locations or equipment inaggregated form. Organizational elements, such as location, plant section ormaintenance planner group are used as characteristics in info structures.

The time-base offers another possibility for aggregating data. Data is compiledfor each period and for each characteristic. With regard to the period unit, youcan choose between daily, weekly and monthly data compression for each infostructure. Logistics key figures are updated for each characteristic combinationand period unit. These include quantitative amounts, which provide informationon measurable objects. Key figures can be ascertained for each evaluation groupusing accumulation, such as actual costs, or they can be simple counters, such asnumber of orders.

Info Structures



Figure 14: Info Structures

In the SAP standard system, info structures are available for a number ofapplication areas. User-friendly tools enable you to group characteristics and keyfigures into individual info structures according to your own criteria and supplythem with data using separate update programs.

Figure 15: Info Structures in PMIS



The info structure S115 contains the characteristics Order type, Maintenanceactivity types, Functional location, Equipment, and Month.

It also contains all PM cost key figures and the key figures for created, planned,and unplanned orders.

Figure 16: Example: Info structure S115 - Cost Analysis

Standard field catalogs provide the info structure with characteristics and keyfigures. The field catalogs refer to the communication structures.

The info structure S070 contains the characteristics object class, functionallocation, equipment, and month.

The key figures MTTR and MTBR are determined using the individual history ofa technical object.



Figure 17: Example: Info Structure S070 - Breakdown Analysis

The key figureMean Time To Repair (MTTR) displays the mean time for whichthe object in question was not operational. The key figureMean Time BetweenRepair (MTBR), on the other hand, represents the time for which the objectin question was fully operational. Both key figures are displayed in hours, andare based on all damage reports that were created from the start-up date, and forwhich the breakdown indicator is selected.

For technical objects for which no start-up date is entered in the master record,the system uses the end date of the first malfunction report for which thebreakdown indicator is selected. In this case, the system does not take account ofthe first malfunction report in subsequent calculations.

The system also only evaluates malfunction reports for which the start and theend of the breakdown is entered. It does not support evaluations based on thestart time or downtime.

The number of actual breakdowns is then calculated based on the total numberof breakdowns. When calculating this time, the system merges two breakdownsthat overlap or occur in immediate succession into one actual breakdown. Thereference date/time for assigning the key figures MTTR and MTBR to a statisticsperiod is the start of the actual breakdown. For longer-term breakdowns, this maymean that the key figures for subsequent periods cannot be calculated. Note that,in this context, the system only supports periodicity at the monthly level.



Principles for Updating Data

Figure 18: Update in the LIS

Special update modules are used to anchor the Logistics information systemsto the SAP ERP system. The LIS update function uses data aggregation toimplement one of the most important basic principles of the entire LIS concept.Update programs reduce the amount of operational data to its statistically-relevantparts. They compress data using periodical and object-related accumulationprocedures and calculate meaningful key figures from the operational data usingformulas and conditions.

Statistical data for the LIS can be updated in parallel to the processing ofoperational data, to ensure that LIS information is consistent with data fromoperational applications. The data can also be updated periodically, to reducesystem overload in the application systems.



Figure 19: Results of Maintenance Update

Object and document data is transferred to the interface between the applicationand information system when you end the relevant editing function by creating orchanging and then saving your data. The communications interfaces only makethe data available within the program, and the data is not stored in a permanentlocation.

The update program of the relevant information structure records the data requiredfor the corresponding key figure and updates it in the corresponding informationstructure. The data updated here is permanent and is available for the relevantstandard analysis and all other evaluation tools.

Figure 20: Cost Update in PMIS



Maintenance costs are updated by the following key figures in the informationstructures S061, S062, S065 and S115:

� Total costs planned� Total costs (actual)� Internal wage costs� Internal material costs� External labor costs� External material costs� Service costs� Other costs

The key figures for total costs are summarily updated independently of all othercriteria, to provide the planned and/or consumed resources for an order. Updatesto the other six key figures refer to the actual costs for an order and may bedifferentiated using value categories. In Customizing, you can determine whichvalue categories are relevant for updating which key figures.

Figure 21: Update Using Info Structure S115 as an Example

The maintenance order is debited with the completion confirmation in time. Thecost element that is assigned to the activity type (CO) is debited.

The cost element is assigned to a value category (in this case, value category 615).

The value category is in turn assigned to a key figure (such as the internalpersonnel costs IAPERKOSE).



The key figure (in this case, IAPERKOSE) is part of the communication structure(in this case MCIQF) and is provided by a standard field catalog (in this case,BI12).

The information structure (in this case, S115) consists of a combination ofcharacteristics and key figures with a time reference. A standard analysis is basedon the information structure.



Exercise 2: Plant Maintenance InformationSystem (PMIS)

Exercise ObjectivesAfter completing this exercise, you will be able to:� Use standard analyses in PMIS, to monitor specific key figures in Plant

Maintenance.

Business ExampleYou would like to use standard analyses to obtain an overview of the cost andtechnical status of your objects, based on relevant key figures. Unlike applicationlists, this view will contain aggregated data on specific characteristics.

Task 1:Use different standard analyses

1. Run a cost analysis for functional location 20 for 2006.

How do you proceed?

Set the required layout, to check target and actual costs.

What are the actual costs for this period?

2. In the above analysis, what are the actual costs for inspection work carriedout in 2006?

3. Compare the key figures Total planned costs and Total actual costs.

How do you proceed?

4. In the above list, analyze the actual costs for repairs.

In which month were these measures carried out?

Drill down the order type and maintenance activity type.

5. Run a breakdown analysis for equipment TEQ-20 for the first two quartersof 2006.

What are the values for MnTmToRepair and MnTmBetRepair, and what istheir significance? To make things clearer, drill down to the characteristicMonth.




Task 2:Get to know the PMIS structure and the principle of data update

1. In Customizing in the Logistics Information System, check info structureS115 (cost analysis).

What are the characteristics of the info structure?

2. Identify the field name for key figures for internal wage costs and internalmaterial costs.

How do you proceed?

3. Check which value categories are used to supply the key figures displayedabove.

How do you proceed?

4. Check the update rules for info structure S115.

Which event triggers updating for the key figure Internal wage costs?

What is the currency?



Solution 2: Plant Maintenance InformationSystem (PMIS)Task 1:Use different standard analyses

1. Run a cost analysis for functional location 20 for 2006.

How do you proceed?

Set the required layout, to check target and actual costs.

What are the actual costs for this period?

a) SAP menu→ Logistics→ Plant Maintenance→ Information System→ Standard Analyses→ Cost Analysis

In the Functional Location field, enter the value 20*; month 01.2006 to12.2006 as the period to analyze, and EUR as the analysis currency.Run the cost analysis.

Select Edit→ Choose Key Figures. Select the key figuresTotalplanned costs and Total Actual Costs and transfer them from Poolto Section criteria.

Move the key figures for Planned orders, Unplanned orders, No.immediate orders, and Total planned costs from Selection criteria toPool.

Set the following characteristics:

Settings→ Characteristic display→ Key and description

Settings→ Column width→ Characteristic, for example, columnwidth of 30

Save the user settings:

Settings→ Save settings

2. In the above analysis, what are the actual costs for inspection work carriedout in 2006?

a) In the above analysis, choose Switch drilldown and chooseMaintActivityType.

Characteristic Description Actual costsMaintenance activitytype

Inspection EUR 347.17




3. Compare the key figures Total planned costs and Total actual costs.

How do you proceed?

a) In the above analysis, position the cursor on the Total planned costs keyfigure, and choose

Select Edit→Comparisons→ Two key figures . Choose the keyfigure Total actual costs.

4. In the above list, analyze the actual costs for repairs.

In which month were these measures carried out?

Drill down the order type and maintenance activity type.

a) Start the cost analysis as described above. Double-click the ordertype PM01 Maintenance order, and then maintenance order activitytype103 Repair. Then double-click the functional location 20-B02, andequipmentTEQ-20.

The repair work was carried out in the months 01.2006 and 05.2006.

5. Run a breakdown analysis for equipment TEQ-20 for the first two quartersof 2006.




What are the values for MnTmToRepair and MnTmBetRepair, and what istheir significance? To make things clearer, drill down to the characteristicMonth.

a) SAP menu→ Logistics→ Plant Maintenance→ Information System→ Standard Analyses→ Breakdown Analysis

In the Equipment field, enter TEQ-20 and select the date 01.2006 to06.2006.

View→ Switch drilldown

>Month

Month Actualbreakdowns

MnTmToRe-pair

MnTmBetRe-pair

Total 2 14.559 H 51,002.442 H01.2006 1 6.617 H 99,008.383 H05.2006 1 22.500 H 2,996.500 H

Mean Time To Repair: The average duration of a breakdown inhours. This key figure is calculated using the actual duration of the nthbreakdown, divided by the number of actual breakdowns: (End ofthe nth breakdown - Start of the nth breakdown) / Number of actualbreakdowns).

Mean Time To Repair: The average duration between two machinebreakdowns in hours. This key figure is calculated using the period oftime between the end of the last breakdown and the start of the nextbreakdown, divided by the number of actual breakdowns: (Time of thenth breakdown - Time of the (n-1)th breakdown - downtime of the(n-1)th breakdown) / Number of actual breakdowns

Task 2:Get to know the PMIS structure and the principle of data update

1. In Customizing in the Logistics Information System, check info structureS115 (cost analysis).




What are the characteristics of the info structure?

a) SAP menu→ Tools→ Customizing→ IMG→ Execute Project

Select SAP Reference IMG.

Logistics - General→ Logistics Information System→ Logistics DataWarehouse→ Data Basis→ Information Structures→ MaintainSelf-Defined Information Structures

Double-click display. Enter info structure S115.

CharacteristicsOrder typeMaintenance activity typeFunctional locationEquipment

2. Identify the field name for key figures for internal wage costs and internalmaterial costs.

How do you proceed?

a) In info structure display (see above), double-click Internal wage costsand Internal material costs.

Description Field nameInternal wage costs IAPERKOSEInternal material costs IAMATKOSE

3. Check which value categories are used to supply the key figures displayedabove.




How do you proceed?



Plant Maintenance and Customer Service > Information Systems forPlant Maintenance and Customer Service > Assign Value Categoriesto Maintenance Cost Key Figures

Key figures Field name Value categoryInternal wage costs IAPERKOSE 615Internal materialcosts

IAMATKOSE 400, 890

4. Check the update rules for info structure S115.

Which event triggers updating for the key figure Internal wage costs?

What is the currency?



Logistics - General→ Logistics Information System (LIS) →Logistics Data Warehouse→ Updating→ Updating Definition→Specific Definition Using Update Rules→Maintain Update Rules

Double-click Display.

Enter info structure S115 and update group 26.

Double-click the key figure Internal wage costs:

Key figure Event CurrencyInternal wage costs I3 (= order) 76 (= acquisition

currency)



Lesson Summary

You should now be able to:� Describe the structure of PMIS� Explain the principle of data update� Perform standard analyses


PLM318 Unit Summary

Unit SummaryYou should now be able to:� List the relevant source data in Enterprise Asset Management� Run different lists that demonstrate the granularity of the source data� Describe the structure of PMIS� Explain the principle of data update� Perform standard analyses


Unit Summary PLM318


Unit 2Data Storage in BW

Unit OverviewThis unit describes data storage in BW, and explains business-content aspects ofmaintenance.


� List the basic concepts of the Business Information Warehouse� Describe BI Content in the area of Enterprise Asset Management� Run different queries in Enterprise Asset Management

Unit ContentsLesson: Basics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Exercise 3: Basics.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Lesson: BI Content Enterprise Asset Management .. . . . . . . . . . . . . . . . . . . . . . . . 53

Exercise 4: BI Content Enterprise Asset Management.. . . . . . . . . . . . . . . . 61Lesson: Working with Queries in Enterprise Asset Management .. . . . . . . . 65

Exercise 5: Working with Queries in Enterprise Asset Management . 77


Unit 2: Data Storage in BW PLM318

Lesson: Basics

Lesson OverviewThis lesson provides a brief overview of key concepts, the data model, and dataflow in BW.


� List the basic concepts of the Business Information Warehouse

Business ExampleYou want to use the Business Information Warehouse (BW), to run analyses inall system components. Before you do this, you will learn about basic conceptsand processes in BW.

IntroductionThe Business Information Warehouse (BW) is a system that is independentof other SAP systems. It extracts data from diverse source systems (both SAPand non-SAP systems), restructures and reformats this data, and compiles it intoefficient and user-friendly analyses.

BW can run as an independent system together with other SAP or non-SAPsystems, or it can be integrated into a mySAP ERP system.


PLM318 Lesson: Basics

Figure 22: BW at a Glance

The cornerstone of BW is the BW server , which has preconfigured BI Contentfor the core areas of your company.

BI Content is preconfigured role- and task-based information models that arebased on consistent metadata.

It provides a range of information that specific roles in a company require toperform their tasks. The Business Explorer (BEx) provides your company withflexible reporting and strategic analysis tools, to support the decision-makingprocesses.

Technical RequirementsFrom a technical point of view, BW represents Business Intelligence (BI) in theSAP NetWeaver integration and application platform.

SAP NetWeaver facilitates implementation of the Enterprise Services Architecture(ESA). It allows you to standardize business processes across technologicalboundaries, integrate applications required by your employees, and easily accessstructured information and format it in line with your needs.



Figure 23: Business Intelligence Within the Framework of SAP NetWeaver

SAP NetWeaver is the underlying platform for all SAP solutions. For example, themySAP Business Suite uses all key areas of SAP NetWeaver. The mySAP ERPbusiness solution is also based on SAP NetWeaver.



Figure 24: The mySAP ERP solution

Hint: It is worth differentiating between the license-, software-, andhardware-specific views. The fact that the mySAP ERP license includesSAP NetWeaver and, as a result, the Business Intelligence (BI) component(Business Intelligence with BW) does not necessarily mean that ERP andBW run on the same server. In most cases, BW will run on its own server,primarily to optimize performance.

Basic ConceptsCommunication between the source system and BW is broken down into thefollowing steps:

� Provision of source system data� Extraction of data from source system� Storage of data in BW entry layer� Transformation of data to a consistent format� Loading of data to info provider� Running of analysis



Figure 25: Data Flow

Caution: Note that both the data model and data flow in Releases BW3.xand SAP NetWeaver 2004s BI differ, even as regards basic concepts suchas DataSource and InfoSource. For more information, refer to the SAPHelp Portal or the relevant BW course.

Data that logically belong together are available in the source system in the formof DataSources.

A DataSource comprises a number of fields that are provided in a flat structure(extraction structure) for data transfer to BW. It also describes the properties ofthe corresponding extractor for data transfer to BW.

The extraction structure provides the DataSource with data in the source system.It contains the quantity of the fields that are provided by an extractor in the sourcesystem for the data loading process.

An extractor is a method (for example, a function module) for loading data fromsource system datasets to a DataSource extraction structure.

The transfer structure is the structure in which data from the source system istransported into BW. It represents a selection of the fields in the source system'sextraction structure.

A Persistent Staging Area (PSA) is the BW entry layer in which inbound data issaved transparently in its original form.



An InfoSource in BW describes the quantity of all available data of a businesstransaction type (such as Cost Center Accounting). An InfoSource alwaysrepresents a quantity of InfoObjects that logically belong together. The structurein which they are stored is called a communication structure.

An InfoObject is a business evaluation object. It is a superordinate term forcharacteristics, key figures and units.

InfoProvider is the superordinate term for BI objects that represent data views orinto which data is loaded. This data can usually be analyzed using BEx queries.Examples of InfoProviders include InfoCubes or DataStore objects (formerlyknown as ODS objects).

InfoCubes are data containers used for reports and analyses in BW. They containordered characteristics and key figures, depending on their size. These are referredto as InfoObjects in BW.

The dimension is a set of characteristics whose content is grouped togetherunder a common superordinate term. If the dimension contains a characteristicwhose value already uniquely defines the values of all other characteristics from abusiness point of view, then the dimension is named after this characteristic.

A DataStore object (ODS) is used to store clean, consolidated transaction ormaster data at the document level (basic level). This data can be analyzed ina BEx query. A DataStore object contains key fields (such as document numberand item) and data fields that can contain key figures and character fields (suchas order status and customer. DataStore object data can be updated in InfoCubesby delta update, in other DataStore objects or master data tables (attributes ortexts) in the same system, or across the entire system. Unlike multidimensionaldata storage for InfoCubes, data in DataStore objects is stored in transparent,non-nested database tables. Fact and dimension tables are not created.



Figure 26: Basic Concepts

Extraction is scheduled and implemented at specific intervals by BW. This meansthat data is not updated online between the source system and BW. As a result,data is obsolete if long periods of time elapse between extractions.

This problem can be solved by scheduling regular extractions or by usingreal-time data acquisition.

Real-time data acquisition supports the tactical decision-making process. Asregards data procurement, it supports operational reporting as it allows data to besent to the BW entry layer in real time (delta queue or PSA table). From there,it can be transferred to DataStore objects in the Operational Data Store Layerat short intervals.

Data is stored persistently in BI. We recommend that you use real-time dataacquisition if you wish to transfer data to BI more regularly than the scheduledintervals (every hour or minute), and if reporting data must be updated severaltimes in one day.

The DataSource must support real-time data acquisition. This is one possiblecharacteristic of Web service DataSources and DataSources from the SAP sourcesystem. In DataSource maintenance, this characteristic is displayed under RealTime on the Extraction tab. DataSources from SAP source systems can be usedfor real-time data acquisition provided that BI Content DataSources are enabledfor real-time data acquisition.

The characteristic for real-time enabled must be set for generic DataSourcesin the generic delta settings (see the section on delta transfer to BI). Note thatDataSources from SAP source systems can support real-time data acquisition insource systems as of BI Service API for SAP NetWeaver Release 2004s (plug-in



2005.1). Also, only Web Service DataSources that you have defined usingDataSource maintenance in BI can be used for real-time data acquisition. You usetransformation between the PSA and the DataStore object and run the data transferprocess to update data from PSA to the DataStore object.

Example: Structure of an InfoCube (Sales)The sections outlined below use a Sales and Distribution InfoCube to illustrate aself-contained business dataset that is stored in BW.

Figure 27: InfoCube in Sales and Distribution

The InfoCube displayed in the graphic above contains three dimensions: Time,customer, and material.

Each dimension has its own dimension table.

The dimension table groups together the characteristics that logically belongtogether (the customer name and region belong to the customer dimension, forexample). Adhering to this design criterion ensures that the dimensions remainlargely independent of each other and that the data volume of the dimension tablesremains small, which helps optimize performance.

From a technical point of view, several characteristics values are mapped to anabstract dimension key (DIM-ID) to which the values in the fact table relate.The characteristics selected for an InfoCube are distributed to InfoCube-specificdimensions when the InfoCube is created.



Figure 28: Dimension Tables in Sales and Distribution

The fact table contains the InfoCube's key figures.

Fact tables and dimensions are linked with each other by identifiable abstractnumbers (IDs), that are in the key part of the relevant database table. The keyfigures of the InfoCube are related to the characteristics of the dimension. Thecharacteristics define the granularity (the fineness) of the key figures in theInfoCube.

Fact tables and dimension tables are relational database tables.

Figure 29: Fact Tables in Sales and Distribution



The InfoObjects are grouped in the InfoCube according to the star schemaprinciple, that is, there is a (large) fact table that contains the InfoCube key figures,and several (smaller) dimension tables surrounding it that contain the InfoCube'scharacteristics (see the sections below).

The characteristics point to the master data and its attributes and text descriptions.All InfoObjects (that is, characteristics with their master data and key figures)are available to all InfoCubes, unlike dimensions, which represent the specialorganizational structure of characteristics in an InfoCube.

The BW master data is transferred by uploading it from the source system. It canbe enhanced with other data from external systems.

Figure 30: Star Schema

Example: Data Flow of an InfoCube (PlantMaintenance)The InfoCube 0PM-C07 (Plant Maintenance orders: Scheduling) is part of BIContent.



Figure 31: Data Flow Using InfoCube 0PM_C07 as an Example



Exercise 3: Basics

Exercise ObjectivesAfter completing this exercise, you will be able to:� Describe the basic structures in BW from the point of view of Enterprise

Asset Management

Business ExampleYou use BW in the integrated ERP system, and would like to get to know itsbasic structures.

Task:Learn about basic structures in BW from the point of view of Enterprise AssetManagement

1. Display the object overview and data model for the InfoCubeMaintenanceOrders: Costs and Allocations andMaintenance Orders: Scheduling.

What are the keys for these InfoCubes?

What is the difference between the object overview and the data model?

What is the dimension of the InfoCube? Maintenance Orders: Scheduling?

Caution: For technical reasons, only some of the BI content isactivated for Enterprise Asset Management/Plant Maintenance.

2. What key figures does InfoCube 0PM_C07 have?

How are these key figures mapped in BW?

What type or data category do the key figures Number of Orders Completedon Schedule and Total Actual Costshave?

What is the technical name in each case?



Solution 3: BasicsTask:Learn about basic structures in BW from the point of view of Enterprise AssetManagement

1. Display the object overview and data model for the InfoCubeMaintenanceOrders: Costs and Allocations andMaintenance Orders: Scheduling.

What are the keys for these InfoCubes?

What is the difference between the object overview and the data model?

What is the dimension of the InfoCube? Maintenance Orders: Scheduling?




Caution: For technical reasons, only some of the BI content isactivated for Enterprise Asset Management/Plant Maintenance.

a) SAP menu > Information Systems > Business InformationWarehouse > Modeling > Data Warehousing Workbench: Modeling

In the Info Provider area on the left of the screen, navigate to thePlant Maintenance component:

Select Product Lifecycle Management > Plant Maintenance.

In the Plant Maintenance component, display the InfoCubesMaintenance Orders: Costs and Allocations andMaintenanceOrders: Scheduling in the Object Overview:

>Select the InfoCube, open the context menu, and choose >ObjectOverview.

Display the Data Model:

>Select the InfoCube, open the context menu, and choose >DisplayData Model.

Maintenance Orders: Costs and Allocations has the key 0PM_C01.

Maintenance Orders: Scheduling has the key 0PM_C07.

The object overview shows a flat view of all characteristics and keyfigures.

The data model shows a view of characteristics and key figures that isstructured according to dimensions.

The InfoCubeMaintenance Orders: Scheduling has the followingdimensions (visible in the Data Model):

� Maintenance Planning Plant/Maintenance Planner Group� Functional Location/Equipment� Assembly� Order Type/Maintenance Activity Type� PM Processing Phase/PM Planning Indicator� Plant/Work Center� Controlling Area/Currency Type� Time� Data Package� Unit

2. What key figures does InfoCube 0PM_C07 have?




How are these key figures mapped in BW?

What type or data category do the key figures Number of Orders Completedon Schedule and Total Actual Costshave?

What is the technical name in each case?




In the Maintenance component, select the InfoCubeMaintenanceOrders: Scheduling. Open the context menu, and display the DataModel.

The following key figures appear in the data model's Key Figuresfolder:

� Planned Work for Operation� Number of Orders� Number of Orders with Status Completed� Number of Orders to be Executed Immediately� Number of Orders Completed on Schedule� Number of Orders with Status Not Executed� Number of Orders with Status Outstanding� Number of Planned Orders� Lead Time for Order in Calendar Days� Lead Time for Order in Workdays� Number of Unplanned Orders� Total actual costs� Total Planned Costs� Actual Work for Operation

The key figures are mapped as InfoObjects.

Type/Data Type:

Double-click the key figureNumber of Orders Completed on Schedule:

Type: Integer

Data Type: INT4, 4-Byte Integer

Technical name of InfoObject: 0ORD_INTIME

Double-click the key figure Total Actual Costs:Continued on next page



Type: Amount

Data Type: CURR (Currency field)

Technical name of InfoObject: 0PM_ACCOS



Lesson Summary

You should now be able to:� List the basic concepts of the Business Information Warehouse


PLM318 Lesson: BI Content Enterprise Asset Management

Lesson: BI Content Enterprise Asset Management

Lesson OverviewThis lesson explains BI content available in BW for the area of Enterprise AssetManagement.


� Describe BI Content in the area of Enterprise Asset Management

Business ExampleYou are about to implement BW, and would like to use BI Content provided bySAP for Enterprise Asset Management.

GeneralBI Content consists of predefined role- and task-related information models inmySAP Business Intelligence (BI) that are based on consistent metadata.

BI Content provides a range of information that specific roles in a companyrequire to perform their tasks.

These information models mainly consist of roles, workbooks, queries,InfoSources, InfoCubes, ODS objects, key figures, characteristics, update rules,and extractors for SAP applications.

BI Content is shipped as an add-on to mySAP BI. The add-on is called SAP NW2004s BI Content Add-On 3.

BI Content speeds up implementation and lowers implementation costs. It alsoprovides a model that incorporates implementation guidelines and experiencefrom previous go-lives.



BI Content can be made up of the following components:

� Extractor programs for SAP systems� DataSources� Process chains� InfoObjects� InfoSources� Data targets (InfoCubes and ODS objects)� Variables� Data mining models� Queries� Workbooks� Crystal Reports� Web templates� Roles

Figure 32: BI Content



The following BI Content is available for Plant Maintenance:

� Role of maintenance manager (0ROLE_0054)� Queries� InfoCubes� Data store objects (ODS)� InfoSources� DataSources

BI Content: Orders

Figure 33: InfoCubes for Orders

InfoCube 0PM_C01 contains the costs and allocations transferred from theconnected source system(s).

InfoCube 0PM_C02 contains information on the removal of an equipment and pastinstallation durations. Time segments of the equipment master record documentthe installation and dismantling of pieces of equipment at functional locations.Information on the equipment currently installed at which functional location andthe length of time it has been installed here is not stored in this InfoCube. Insteadit is saved in the time-based attributes for the Equipment info object.

InfoCube 0PM_C03 contains key figures on the frequency of and lead time forservice orders.

InfoCube 0PM_C04 contains the planned and actual work of operations in serviceorders.

InfoCube 0PM_C05 provides data for simulated maintenance costs. Maintenanceplans and maintenance task lists are calculated in the extractor.



InfoCube 0PM_C06 plans the maintenance budget. Special planning functions inthe BW-BPS application budget planning for Plant Maintenance and CustomerService (MCB) are used to transfer the data. The data is loaded from the InfoCubes0PM_C01 and 0PM_C05.

InfoCube 0PM_C07 provides data for scheduling maintenance orders.

InfoCube 0PM_C08 displays aggregated data on measurement results.

Figure 34: Data Flow Using InfoCube 0PM_C08 as an Example

MultiProvider 0PM_MC01 merges data from InfoCubes 0PM_C01 and0PM_C06. This allows you to compare current budget plans with historic actualcosts, for example. It can also be used to monitor the budget for the current fiscalyear.



Figure 35: Queries for Orders

Query 0PM_C01_Q001 provides you with an overview of variations in theplanned/actual costs of service orders.

Query 0PM_C02_Q001 displays the number of pieces of equipment dismantledon functional locations, and the average installation duration.

Query 0PM_C03_Q001 allows you to view the number of maintenance ordersand the average lead time. You can also drill down to technical objects andmaintenance activity types.

Query 0PM_C04_Q001 contains the planned and actual work for maintenanceorders on individual work centers.

Query 0PM_C07_Q001 displays released orders that have not yet been completed.It also includes overdue orders and those to be implemented in the future(0PM_STAGE = �Released� (value = 2)) 0CALWEEK = last 12 calendar weeks).

Query 0PM_C07_Q0002 contains released orders that are overdue (0PM_STAGE= �Released� (value = 2) 0CALWEEK < today).

Query 0PM_C07_Q0003 incorporates planned planned and preventive ordersthat were completed on time, compared with all planned and preventive orders(0PM_STAGE ≠ �Outstanding� (value = 0) and ≠ �Deletion indicator� (value = 4)0CALWEEK < today) 0PMPLANIND = 1).

Query 0PM_C07_Q0004 shows orders planned for a specific period that wereactually completed in this period (0PM_STAGE ≠ �Outstanding� (value = 0) and ≠�Deletion indicator� (value = 4) 0CALWEEK =last 12 calendar weeks includingcurrent week).



Query 0PM_C07_Q0005 displays all orders that are fully planned, and have abasic finish date in the future (0PM_STAGE = �Released� (value = 2) 0CALWEEK= next 12 calendar weeks).

Query 0PM_C07_Q0006 displays actual costs, compared with planned costs fororders for the last 52 weeks (0PM_STAGE ≠ �Outstanding� (value = 0) and ≠�Deletion indicator� (value = 4) 0CALWEEK = last 52 weeks).

Query 0PM_C08_Q0001 shows measurement documents at the equipment levelfor functional locations in the last 12 months (0CALMONTH = last 12 months).

Query 0PM_DS04_Q0001 contains the proportion of completed orders in therelevant planned week (0PM_STAGE ≠ �Outstanding� (value = 0) and ≠ �Deletionindicator� (value = 4) 0SCHEDFINCW = last 12 weeks).

BI Content: Notifications

Figure 36: InfoCubes for Notifications

InfoCube 0QM_C03 contains all transaction data related to notification items thatwas uploaded from the source system(s). Master data on notifications is requiredto evaluate this InfoCube. When defining queries for this InfoCube, note that theCube may contain data from the Quality Management and Plant Maintenancecomponents. Therefore, these queries should contain a filter for the notificationtypes, so that different analysis requirements are met, for example, evaluation oftechnical objects, or a customer- or vendor-oriented view of the key figures.

InfoCube 0QM_C06 contains characteristics and key figures on the causes oferror or damage items in quality, maintenance, and service notifications. It alsocontains characteristics from the notification and the notification item. Data isupdated from a self-defined InfoSource for each notification category.



InfoCube 0QM_C07 consists of characteristics and key figures for activitiesin quality, maintenance, and service notifications, irrespective of whether theactivities relate to the entire notification or a notification item. It also containscharacteristics from the notification and the notification item, if applicable. Datais updated from a self-defined InfoSource for each notification category.

InfoCube 0QM_C08 incorporates characteristics and key figures for tasks inquality, maintenance, and service notifications, irrespective of whether thetasks relate to the entire notification or one notification item. It also containscharacteristics from the notification and the notification item, if applicable. Datais updated from a self-defined InfoSource for each notification category.

InfoCube 0QM_C09 contains characteristics and key figures on the error anddamage items from quality, maintenance, and service notifications. It also containscharacteristics from the relevant notifications. Data is updated from a self-definedInfoSource for each of the three notification categories.

InfoCube 0QM_C10 displays key figures on quality, maintenance, and servicenotifications. Each of these three notification categories is updated using aself-defined InfoSource.

Figure 37: Queries for Notifications

Query 0QM_C06_Q001 contains information on the causes of damage in PlantMaintenance. It also allows you to drill down to the damage code and object.

You can use query 0QM_C06_Q0005 to determine information on the causes ofdamage in Plant Maintenance. You can display the damage codes for each object.This query was developed for the Maintenance Technician Business Package.Web template 0TPLI_QM_C06_Q0005_V01 is also available for this query.

Query 0QM_C06_Q0006 provides information on the cause of damage.



Query 0QM_C07_Q001 displays information on maintenance notificationactivities and their frequency.

Query 0QM_C08_Q001 displays the number and status of tasks triggered formaintenance notifications.

Query 0QM_C09_Q003 displays the damage codes entered, and the frequencywith which they occur.

Query 0QM_C09_Q0007 allows you to determine damage codes for maintenanceand service notifications. This query was developed for the MaintenanceTechnician Business Package. Web template 00TPLI_QM_C09_Q0007_V01 isalso available for this query.

You can use query 0QM_C09_Q0010 to evaluate the frequency with which aproblem occurs for each notification category.

Query 0QM_C10_Q001 contains information on the number of notificationsthat exist for technical objects.

The queries 0PM_DS02_Q0001 and 0PM_DS02_Q0002 determine the keyfigures MTTR (Mean Time to Repair) and MTBR (Mean Time between Repairs),based on the individual history of a technical object.

The key figure MTTR displays the mean time for which the object in questionwas not operational.

MTBR, on the other hand, represents the time for which the relevant object wasfully operational. The system uses all malfunction reports that were entered fromthe start-up date, and for which the breakdown indicator is selected, to calculatethese key figures. For technical objects for which no start-up date is entered inthe master record, the system uses the end date of the first malfunction report forwhich the breakdown indicator is selected. In this case, the system does not takeaccount of the first malfunction report in subsequent calculations. The system alsoonly analyzes malfunction reports in which the start and end of the breakdownis entered. It does not support evaluations based on the start time or downtime.The system then calculates the actual number of breakdowns based on the totalnumber of notified breakdowns for a technical object. It merges two breakdownsthat overlap timewise into one actual breakdown.

The reference date/time for assigning the key figures MTTR and MTBR to astatistics period is the start of the actual breakdown. For longer-term breakdowns,this may mean that the key figures for subsequent periods cannot be calculated.

MTTR = Total of actual downtime/Number of actual breakdowns

MTBR = Total of actual time between breakdowns/Number of actual breakdowns

Web Template 0TPLI_PM_DS02_Q0002_V01 is also available for query0PM_DS02_Q0002.

Query 0PM_DS02_Q0003 displays the frequency of breakdowns and the degreeof technical availability.



Exercise 4: BI Content Enterprise AssetManagement

Exercise ObjectivesAfter completing this exercise, you will be able to:� Describe the BI Content available for Enterprise Asset Management

Business ExampleYou use Enterprise Asset Management in the ERP system, and would like toimplement the relevant analyses and evaluations in BW.

To this end, the BI Content delivered in BW for Enterprise Asset Management isto be checked and used if applicable.

Task:Check the BI Content for EAM

1. Display the object overview for the DataStore object (ODS)MTTR/MTBR.

What key figures are available in this DataStore object?

How does the DataStore object differ from the InfoCube?

Can a DataStore object be used as a basis for a query?

2. Display the details for the standard role delivered for the role ofMaintenancemanager delivered as standard BI content.

How do you proceed?

What queries can be implemented in this standard role?

On which InfoCube are these queries based?



Solution 4: BI Content Enterprise AssetManagementTask:Check the BI Content for EAM

1. Display the object overview for the DataStore object (ODS)MTTR/MTBR.

What key figures are available in this DataStore object?

How does the DataStore object differ from the InfoCube?

Can a DataStore object be used as a basis for a query?




In the Maintenance component, select the DataStore objectMTTR/MTBR:

Open the context menu and choose >Object Overview.

Key figures:

� Number of notifications� Number of Outages� Actual Time Between Outages� Actual Outage Time

Unlike the InfoCube, the DataStore object (ODS) is only a flat tablethat is not structured according to dimensions.

DataStore objects can also be used as a basis for a query (in this case:Queries 0PM_DS02_Q0001 and 0PM_DS02_Q0002).

2. Display the details for the standard role delivered for the role ofMaintenancemanager delivered as standard BI content.

How do you proceed?

What queries can be implemented in this standard role?




On which InfoCube are these queries based?


In the Business Content area on the left of the screen, select Roles;

In the Roles area on the right of the screen:

Double-click Standard Roles. On the Roles tab, select MaintenanceManager

RoleSAP_BW_0ROLE_0054

TheMenu tab contains the standard role menu, from which you can callWeb Reports, queries, and Microsoft-Excel-based queries.

Queries in the area of maintenance work:

In the role menu folder, select Analysis Maintenance

� SAP_BW_QUERY - Outstanding Tasks� SAP_BW_QUERY - Overdue Tasks� SAP_BW_QUERY - Planned Maintenance Tasks� SAP_BW_QUERY - Adherence to Deadlines� SAP_BW_QUERY - Future Tasks� SAP_BW_QUERY - Plan/Actual Deviations� SAP_BW_QUERY - Orders Schedule

InfoCube:

Position the cursor on one of the queries, open the context menu, andselect Display Details

InfoCube 0PM_C07



Lesson Summary

You should now be able to:� Describe BI Content in the area of Enterprise Asset Management


PLM318 Lesson: Working with Queries in Enterprise Asset Management

Lesson: Working with Queries in Enterprise AssetManagement

Lesson OverviewThis lesson looks at practical aspects of working with queries in Enterprise AssetManagement.


� Run different queries in Enterprise Asset Management

Business ExampleYou implement maintenance tasks for technical equipment in your company inthe ERP system. You would like to run different reports and analyses for thesebusiness transactions in BW, using standard queries available in the system.

You also want to use Web templates to access analyses.

The Front-End � Business Explorer (BEx)The Business Explorer (BEx) SAP NetWeaver's Business Intelligence Suite. Itprovides you with flexible reporting and evaluation tools to carry out strategicanalyses and support decision-making processes in your company.

BEx contains the following tools:

� BEx Query Designer� BEx Web Application Designer� BEx Broadcaster� BEx Analyzer

Provided you are authorized to access the system, you can display different levelsof detail for historic and current data, and analyze this data from different anglesusing the Portal or Microsoft Excel.

BEx tools also allow you to create planning applications, and enter data inBI-integrated planning.



Figure 38: BEx Suite

BEx Query Designer

The data used in SAP NetWeaver BI is broken down into standalone,business-specific data areas known as InfoProviders. You can define InfoProviderqueries in the BEx Query Designer, allowing you to evaluate BI data. Byselecting and combining InfoObjects (characteristics and key figures) and reusablestructures in a query, you can determine how the system analyzes data for therelevant InfoProvider.

BEx Web Application Designer

The BEx Web Application Designer is a desktop application that allows you tocreate Web applications. You can use it to generate HTML pages that contain avariety of BI-specific content such as tables, charts, and maps.

Web applications are based on Web templates that you can create and change inthe Web Application Designer. You can save the Web templates and access themfrom the Web browser or Portal.

Web templates are referred to as Web applications once they have beenimplemented in the Web.

The Web Application Designer also allows you to use standard markup languagesand the Web Design API to create tailor-made scenarios with user-specificinterface elements.

The Web applications that you create in this way are BEx Web-based applicationsfor data analysis, reporting, and analytical applications.

BEx Broadcaster



BEx Information Broadcasting allows you to distribute by e-mail BI Content (suchas Web templates, queries, query views, reports, and workbooks) as predefineddocuments with historic data, for example, or as links with live data. Alternatively,you can make this content to to a wider audience by publishing it on the Portal (inthe Knowledge Management folder or in collaboration rooms).

In addition to predefined documents that contain historic data, you can createonline links to queries and Web applications. The Business Explorer portal roleillustrates the options available to you when working with BI Content in the Portal.

BEx Analyzer

The BEx Analyzer is an evaluation, reporting and design tool available in theBusiness Explorer. It is integrated inMicrosoft Excel. The BEx Analyzer allowsyou to evaluate specific InfoProvider data, and use this data for planning purposes,by navigating queries created by the BEx Query Designer. You can use the contextmenu or the drag and drop function to this end.

You can insert design items such as dropdown boxes, radio button groups andbuttons in your Microsoft Excel worksheets, to customize the interface for yourqueries. In this way, you can transform a Microsoft Excel worksheet into acomplete query application.

Calling a QueryYou can call a query from the BEx Analyzer or from the role menu, using a Webtemplate.

Queries format InfoProvider data (for example, an InfoCube or DataStore object)in a specific manner, and provide a range of filters that you can use to analyzedifferent aspects.

You can use the following options:

� Save views� Set filters� Set bookmarks� Define variables� Create exceptions� Create conditions� Insert comments� Export data (to Microsoft Excel, for example)� Display different graphical displays� Broadcast information

All EAM queries use a standard Web template.



The standard template contains the following screen elements:

� Query view header� Analysis� Graphic display� Information� Sending and publishing (Information Broadcasting)

The Information tab displays general information on a query, and can be used tosect the following restrictions:

Static filter: Filter set in the query definition.

Dynamic filter: Runtime filter set by user

Variables: Variables with valuation set in the query definition

Information Broadcasting allows information to be sent by e-mail or to the portal.

Queries provide a range of analysis and export functions. For example, it allowsyou to filter a dataset using specific criteria.

Figure 39: Query Filter

You can adjust the query layout from the context menu.



Figure 40: Query Layout (1)

For example, you can display the both the key and description for a planner groupor piece of equipment.

Figure 41: Query Layout (2)

You can also define exceptions.



Figure 42: Query Exception (1)

Figure 43: Query Exception (2)

Portal IntegrationYou can seamlessly integrate BI Content into the Portal using the BEx Broadcaster,KM Content, the SAP Role Upload or the Portal Content Studio.

Depending on the type of integration, you generate different objects with differentdisplays in the Portal.

The Portal allows you to access applications from other systems and sourcessuch as the Internet or Intranet. This means that you can access structured andunstructured information from a central point of access. In addition to KnowledgeManagement, Internet, and Intranet content, you can access business data fromdata analysis.



Figure 44: BI � Portal Integration

The Portal content area can contain the following types of BI Content:

� BEx Web Application as an iView� Predefined BEx Web Application as a document in Knowledge Management� BEx Web application as a link in Knowledge Management� BEx Analyzer workbooks� BI documents� Web interface (from BW-BPS)

BEx Web Application as an iView

A BEx Web Application as an iView displays current data from the BI report.From a technical point of view, the BEx Web application is called directly in theBI system. You can combine the BEx Web Application as an iView, as part of aportal page, with other iViews from different systems. You can change the iViewcharacteristics, to display BI bookmarks or BEx queries.

Predefined BEx Web Application as a Document in Knowledge Management

You can use BEx Information Broadcasting to predefine BEx Web applicationsand store them as a document in Knowledge Management. The predefined BExWeb applications contain historic data on specific points in time. These documentscan also be displayed in an iView.

BEx Web Application as a Link in Knowledge Management



You can create links to BEx Web Applications in Knowledge Management. Thelinks display current data from the BI report. Unlike BEx Web applications as aniView, this call is made indirectly using Repository Manager for BI metadata. Youcan use collaboration functions as documents and links to BEx Web applications.It is not possible to use collaboration with BEx Web applications as an iView.

BEx Analyzer Workbooks

In addition to BEx Web Applications as iViews or as documents, BEx Analyzerworkbooks play a particularly key role. Workbooks can be incorporated into andcalled from the Portal. They are opened in a separate Microsoft Excel window.For technical reasons, it is not possible to open workbooks from the Web browserwindow.

BI Documents

You can use the Repository Manager to integrate the documents and metadatastored in the BI system (in particular the metadata documentation) into the Portal'sKnowledge Management area, where they are displayed for users with otherdocuments in a folder structure. Individual documents can also be displayed asan iView.

Web Interface (From BW-BPS)

AWeb interface (from BW-BPS) is a Web-enabled planning application structuredas a business server page application (BSP application) that is created using theWeb Interface Builder. You can combine a Web interface as part of a portal pageas an iView, together with other views such as BEx Web applications.

SAP AnalyticsSAP Analytics contains both cross-industry and industry-specific analyticapplications.

It is based on the SAP NetWeaver platform, which optimizes the use of existingapplication components, irrespective of the provider in question. Functions foranalyses, transactions, and collaboration are seamlessly integrated.

SAP Analytics is implemented using composite applications (xAPPs).

xAPPs are meta applications that provide functional services for existingapplications, providing a new application in the process.

The development tools contained in the SAP NetWeaver Visual Composerprovide easy access to fine-tuned visualization functions. These include thecomprehensive, robust functions of Macromedia Flex, which can be used toautomatically create Flash graphics, simplifying and optimizing the user interfacefor most users.



Figure 45: SAP NetWeaver Visual Composer

Three analytical applications that are based on this technology are available inEnterprise Asset Management:

� Downtime Analysis� Maintenance Cost Monitor � Work View� Maintenance Cost Monitor � Equipment View

Figure 46: Breakdown Analysis



Downtime Analysis uses data from the maintenance notification, and provides themaintenance manager with an overview of technical equipment and its availability.

From a technical point of view, the InfoProviders 0PM_DS02 and 0QM_C06, andthe queries 0PM_DS02_Q0003 and 0QM_C06_Q006 are used.

The system views the key figure Technical Availability, which can be displayedas a quotient of the standard operation time and downtime (MTBR/(MTBR +MTTR)).

This key figure is color-coded using specific threshold values, allowing you toeasily identify if a situation is critical:

� Green = OK (technical availability: 100 � 96 %)� Yellow = Not OK (technical availability: 95.9 � 80%)� Red = Critical (technical availability: 79.9 � 0%)

If necessary, you can drill down to a detail view for critical items (objects, objectparts, damage, causes), to effectively address the problem.

Figure 47: Maintenance Cost Monitor � Work View

This application displays the maintenance costs for work centers, broken downinto planned and actual costs. You can drill down to the cost element if necessary.

From a technical point of view, the InfoProvider 0PM_C01 and the query0PM_C01_Q0002 are used.



Figure 48: Maintenance Cost Monitor - Equipment View

This application displays the maintenance costs for equipment, broken down intoplanned and actual costs. You can drill down to the cost element if necessary.

From a technical point of view, the InfoProvider 0PM_C01 and the query0PM_C01_Q0003 are used.





Exercise 5: Working with Queries inEnterprise Asset Management

Exercise ObjectivesAfter completing this exercise, you will be able to:� Working with practical queries in EAM

Business ExampleYou are a maintenance manager, and would like to use queries in EAM BI Content,to obtain an overview of the availability of technical equipment in your company.You would also like to display the maintenance costs incurred for a specific period.

Task 1:Run a query forPlanned/actual costs deviation.

1. Execute the queryPlanned/actual costs deviation.

Use the role-specific menu for the maintenance manager to do this.

First of all, check what default settings apply for the query in the standardversion.

How do you proceed?

Hint: For technical reasons, this query starts in the maintenancemanager's role menu in the backend system. This has been modifiedfor the training course and is slightly different to the standard menu(0ROLE_0054).

2. Format the data so that the system only displays the costs in the maintenanceplant Hamburg (plant 1000).

How do you proceed?

3. Add the Cost element characteristic to the standard drilldown, so that the costelement is displayed in the lines of the diagram.

How do you proceed?

In which cost element have the majority of actual costs been incurred?

4. Change the query settings so that the cost element characteristic is onlydisplayed with its key.

How do you proceed?




Task 2:Run the query forOverdue Tasks.

1. Execute the query Overdue tasks for maintenance orders.



How do you proceed?

Set a filter for the view so that only the values for maintenance planningplant 1000 are displayed. How do you proceed?

What is used to measure the number of overdue orders?


Task 3:Run the query MTTR/MTBR.

1. Execute the queryMTTR/MTBR.



Identify the following parameters for equipment TEQ-20 for the secondquarter of 2006 (period from 04.2006 to 06.2006):

No. of actual breakdowns ?Actual outage time ?Actual time between outages ?

How do you restrict the timeframe?





Task 4:OPTIONAL

Create your own query using an existing query, and a standardWeb template.

1.

Hint: The following exercise runs on the Windows Terminal Server(WTS) specified by your instructor. Make sure that the trainingsystem specified by your instructor is entered in the SAPLogondialog box before you start the exercise.

Only use BW Frontend 3.5.

Call the Web Application Designer.

Load the standard Web template 0ADHOC and save it under a new namewith the following entries:

Description: Web template group ##

Technical name: ZADHOC_G##

How do you proceed?

2. What views are available in the Web Application Designer?

3. Link your Web template with the query planned/actual cost deviation. Savethe Web.

How do you proceed?

4. From the Web template, load the query to the Query Designer and savethe query as follows:

Description: Planned/actual costs deviation group ##

Technical name: ZPM_C01_Q0001_G##

Hint: The new query must be assigned to the template again (asdescribed above).

5. Change the query so that the planning plant with the default setting 1000acts as a static filter, and the cost element is available in the standarddrilldown in the lines that follow the planner.

How do you proceed?



Solution 5: Working with Queries inEnterprise Asset ManagementTask 1:Run a query forPlanned/actual costs deviation.

1. Execute the queryPlanned/actual costs deviation.



How do you proceed?


a) In the BW system, select User menu.

User menu→ Maintenance Manager→ Planned/Actual CostsDeviation (Web Template)

In the query, call the Information tab, and check the areas Static Filter,Dynamic Filter, and Variable Values.

Default Settings::

Static Filter: Currency type (= Currency of controlling area) and keyfigure type (= 1000 - corresponds to: numeric).

Dynamic Filter: No entries

Variable values: The variables Equipment and Functional Locationexist; no values are set.

2. Format the data so that the system only displays the costs in the maintenanceplant Hamburg (plant 1000).

How do you proceed?

a) A filter must be set in the query. To set this filter, select Data Analysis,and choose Plant Hamburg using the filter icon in the Maintenanceplant row.

3. Add the Cost element characteristic to the standard drilldown, so that the costelement is displayed in the lines of the diagram.




How do you proceed?

In which cost element have the majority of actual costs been incurred?

a) In the query in the Free characteristics area, select the icon Drill downto lines. This moves the characteristic to the Lines area, and the dataarea is displayed again (drilldown by planning group and cost element).

4. Change the query settings so that the cost element characteristic is onlydisplayed with its key.

How do you proceed?

a) In the query area, select the Cost element characteristic, and chooseEnhanced menu. In this menu, select Characteristics. In theCharacteristics of cost element characteristic area in the Display field,set the value toKey and choose Copy.

Task 2:Run the query forOverdue Tasks.

1. Execute the query Overdue tasks for maintenance orders.



How do you proceed?

Set a filter for the view so that only the values for maintenance planningplant 1000 are displayed. How do you proceed?




What is used to measure the number of overdue orders?



User menu→ Maintenance Manager→ Overview Tasks (WebTemplate)

Default Settings::

Static Filter: None in this case

In the standard system, set to: Calendar day (< today's date) andprocessing phase maintenance (= 2 - corresponds to: Released).

Dynamic Filter: None

Variable values: None

Filter by maintenance planning plant:

In the Lines area in the Maintenance planning plant, select the filtericon, and plant 1000. Then choose Copy

Number of overdue orders:

All orders with status REL that have past their basic finish date.

.

Task 3:Run the query MTTR/MTBR.

1. Execute the queryMTTR/MTBR.



Identify the following parameters for equipment TEQ-20 for the secondquarter of 2006 (period from 04.2006 to 06.2006):

No. of actual breakdowns ?Actual outage time ?Actual time between outages ?




How do you restrict the timeframe?



User menu → Maintenance Manager→ MTTR/MTBR (WebTemplate)

Default Settings::

Static Filter: None

Dynamic Filter: None

Variable values: Plant, work center, planner group, month/calendaryear, equipment, cost centers, functional location � no value set forall of these items.

Display equipment with key:

In the query area, select the Equipment characteristic, and chooseEnhanced menu. In this menu, select Characteristics. In theCharacteristics of equipment characteristic area in the Display field,set the value toKey and choose Copy.

To restrict the timeframe:

Button Variable dialog

Enter month/calendar year for the variable. Enter 04.2006 to06.2006 and select Copy.

No. of actual breakdowns 1Actual outage time 22.5 hActual time between outages 2,996.5 h




Task 4:OPTIONAL

Create your own query using an existing query, and a standardWeb template.

1.

Hint: The following exercise runs on the Windows Terminal Server(WTS) specified by your instructor. Make sure that the trainingsystem specified by your instructor is entered in the SAPLogondialog box before you start the exercise.

Only use BW Frontend 3.5.

Call the Web Application Designer.

Load the standard Web template 0ADHOC and save it under a new namewith the following entries:

Description: Web template group ##

Technical name: ZADHOC_G##

How do you proceed?

a) Start→ Programs→ Business Explorer→Web Application Designer

Web Template→ Open . Enter 0ADHOC in the Description/TechnicalName field. Make a selection from the list.

Web template→ Save as

Enter a description and technical name as described above.

2. What views are available in the Web Application Designer?

a) Web Items view (on the top left - components of the Web templatessuch as tables and charts)

Characteristics view (on the bottom left � with tabs General and WebItem).

View of loadedWeb template (right � large window � with thetabsLayout, HTML, and Overview).

3. Link your Web template with the query planned/actual cost deviation. Savethe Web.




How do you proceed?

a) In the Web Application Designer, go to the work area on the right of thescreen and select the Overview tab. In the Characteristics view on thebottom left, choose the General tab;

In the Query/View field, choose Select Query;

Select InfoAreas and navigate to Product Lifecycle Management→Plant Maintenance→Maintenance Orders - Costs and Allocations→ Planned/Actual Cost Deviation . Select the query and save the Webtemplate (by selecting the disk icon).

4. From the Web template, load the query to the Query Designer and savethe query as follows:

Description: Planned/actual costs deviation group ##

Technical name: ZPM_C01_Q0001_G##

Hint: The new query must be assigned to the template again (asdescribed above).

a) In the Web Application Designer, select the Overview tab in the workarea (in the large window on the right). Position the cursor on thetop line (TITLE);

Select Tools→ Query Designer

Save the query by selecting the Save query as button (with yellow andwhite triangle). Enter the description and technical name as describedabove.

Assign the new query to the template (as described above). Save thetemplate.

5. Change the query so that the planning plant with the default setting 1000acts as a static filter, and the cost element is available in the standarddrilldown in the lines that follow the planner.




How do you proceed?

a) The characteristics Planning plant and Cost element are in the Freecharacteristics area;

move the Planning plant characteristic from here to the Filter areausing the drag and drop function.

Select the right mouse button and chooseRestrict; transfer the value1000 to the selection area;

Move the Cost element characteristic to the Lines area using the dragand drop function.

Save your query.

From the Web Application Designer, execute the query in the browser:

Web template→ Execute in browser.



Lesson Summary

You should now be able to:� Run different queries in Enterprise Asset Management


Unit Summary PLM318

Unit SummaryYou should now be able to:� List the basic concepts of the Business Information Warehouse� Describe BI Content in the area of Enterprise Asset Management� Run different queries in Enterprise Asset Management


PLM318 Test Your Knowledge

Test Your Knowledge

1. InfoObjects in BW are the info structures that are extracted from theLogistics Information System.Determine whether this statement is true or false.□ True□ False

2. InfoCubes are multidimensional data containers made up of differentInfoObjects.Determine whether this statement is true or false.□ True□ False

3. The extractor is the superuser responsible for extracting data from the sourcesystem.Determine whether this statement is true or false.□ True□ False

4. A query is an automatically generated program that extracts data from thesource system, and compares the field lengths between the ERP systemand BW.Determine whether this statement is true or false.□ True□ False


Test Your Knowledge PLM318

Answers

1. InfoObjects in BW are the info structures that are extracted from theLogistics Information System.

Answer: False

InfoObjects are characteristics, key figures and units in BW.

2. InfoCubes are multidimensional data containers made up of differentInfoObjects.

Answer: True

InfoCubes are data containers that represent a self-contained businessarea, and are structured according to dimensions. The dimension is a setof characteristics whose content is grouped together under a commonsuperordinate term. This means that an InfoCube systematically evolvesfrom a quantity, after a specific evaluation target of structured InfoObjects.

3. The extractor is the superuser responsible for extracting data from the sourcesystem.

Answer: False

An extractor is a program that can load data from source system datasets intothe extraction structure of a DataSource.

4. A query is an automatically generated program that extracts data from thesource system, and compares the field lengths between the ERP systemand BW.

Answer: False

A query is an analysis that is based on an InfoCube or other InfoProvider,and evaluates a business-specific dataset using specific criteria (for example,planned and actual costs in maintenance orders for a specific plant).


Unit 3Budget Planning for Plant

Maintenance and Customer Service(MCB)

Unit OverviewThis unit explains how maintenance budgets are planned in both the ERP systemand BW.


� Use the planning function BW-BPS to plan maintenance budgets

Unit ContentsLesson: Budget Planning .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92


Unit 3: Budget Planning for Plant Maintenance and Customer Service (MCB) PLM318

Lesson: Budget Planning

Lesson OverviewThis lesson provides an overview of how to plan maintenance budgets in BW-BPS.


� Use the planning function BW-BPS to plan maintenance budgets

Business ExampleYou would like to use consolidated data in BW to plan the maintenance budget forthe coming year, using the zero-based and history-based budgeting method.

Maintenance Cost Budgeting (MCB)You can use BW-BPS (Business Information Warehouse - Business Planningand Simulation) to plan budgets in Plant Maintenance and Customer Services.A maintenance budget generally refers to the budget for all costs that arise inrelation to the inspection, maintenance, and repair of technical assets in a certaintime period.

Figure 49: MCB Process


PLM318 Lesson: Budget Planning

The ERP system transfers the required data to BW, and the Maintenance CostBudgeting (MCB) application provides an integrated planning environment forthe data.

The planning process contains at least the following individual steps:

� The responsible manager/maintenance manager creates one or more planningversions for specifying the budget (for example, minimum version, maximumversion). He or she can draw on historic data as the basis for budget planning.

� The manager sends a version of the specified budget to the responsiblemaintenance planner.

� The maintenance planner uses BW reports to draw up a budget proposal.These reports are created, for example, by extracting maintenance data fromERP EAM (zero-based or history-based). The maintenance planner sendsthe budget proposal to the manager.

� The manager approves or rejects the proposal (iterative process).� The result of this approval process can be forwarded to the ERP system using

a BAdI. This forms the basis for the actual maintenance planning process.

Hint: Retraction of the planned budget in the ERP system is notautomatically carried out in the ERP system. You can use the BADIUPA_MCB_RETRACT to implement it manually (more informationis available in transaction SE18).

After retraction, the budget can be assigned in ERP as follows:

� From Project System using WBS elements� From Investment Management using investment program items

It is still not possible to directly assign the budget to the technical object.



Figure 50: MCB Roles

You must carry out a number of tasks, depending on the role assigned to youin your company's maintenance organization. SAP has identified the followingroles for the planning process:

� MCB administrator: Responsible for MCB Customizing, and definingthe budget planning process

� Maintenance manager: Responsible for defining, triggering, monitoring,and completing the budget planning process

� Maintenance budget planner: Responsible for planning the budget forhis/her own area of responsibility

� Maintenance engineer: Responsible for ensuring that operationalmaintenance master data is complete and correct (not an MCB user)

� BW operator: Responsible for BW-BPS data (not an MCB user)



Figure 51: Planning scenarios

The planning scenarios outlined in the graphic above are available for thehistory-based and zero-based budgeting methods. You can use budgetcategories to classify a budget in relation to the planning of a maintenancemeasure (for example, preventive, planned, or unplanned).

� Preventive ($M): Costs from routine maintenance work that is plannedusing maintenance plans

� Planned ($P): Costs from sporadic maintenance work, that is planned usingtask lists or individually using orders.

� Unplanned ($U): Costs that arise from an unplanned maintenance measure,such as repair of a machine breakdown caused by damage

The individual budget categories are linked to the specified planningscenarios by the zero- or history-based budgeting method. In the standardconfiguration, the costs for the budget category proposal can be brokendown as follows:

For the zero-based budgeting method, the values are determined using themaintenance plan scenario.

For the history-based budgeting method, the values are determined using thehistoric or ad-hoc scenario.



Figure 52: History-Based Planning Scenario

For the history-based budgeting method, you create your maintenance budgetusing historic data, in particular historic actual costs from maintenance and serviceorders.

You upload historic data for actual costs from maintenance orders or settlementsfrom your ERP system into InfoCube 0PM_C01 in BW.

Data from InfoCube 0PM_C01 must be copied into the BPS Planning Cube0PM_C06 using the Cube Copy function. This is how you aggregate your datafor your MCB planning application.

This data serves as the planning basis for your maintenance budget.

The following planning scenarios exist for the history-based budgeting method:

� History-based scenario: This planning scenario is based on historic data, forexample, the equipment history, or maintenance orders for your vehicles,equipment, and pumps.

� Ad-hoc scenario: This planning scenario is based on ad hoc or customizeddata entry. That is, when you create budget proposals using this budgetingmethod, you do not have to base them on historic data.



Figure 53: Zero-Based Planning Scenario

When using the zero-based budgeting method, you create a budget based onplanned data, in particular simulated planned costs.

Rather than being determined using actual data, the budget is drawn up basedon planned tasks.

Task lists and maintenance plans are used as planning aids. The planned valueof the services in the budget (work, external services, material) is determinedautomatically and are used as simulated costs to form the basis of budget planning.

You upload the planned data from existing task lists or maintenance plans in yourERP system into InfoCube 0PM_C05 in BW. Data from InfoCube 0PM_C05 mustbe copied into the BPS Planning Cube 0PM_C06 using the Cube Copy function.This is how you aggregate your data for your MCB planning application.

The following planning scenarios exist for the zero-based budgeting method:

� Task list scenario: Planning based on the cost simulation of task lists� Maintenance plan scenario: Planning based on the cost simulation of

maintenance plans� Ad-hoc scenario: Planning scenario based on ad-hoc or customized data

entry. That is, when you create budget proposals for this budgeting method,you do not have to base them on historic data.



Figure 54: Budget Distribution

The maintenance planner can use history-based or zero-based budgeting methodsto create budget proposals. The planner can distribute the data to the definedperiods manually or using planning functions.

You can use the following planning functions to distribute the budget:

History-based budgeting method: For the history-based scenario you can leaveperiod distribution the same as the way in which costs were incurred for pastorders.

Alternatively, you can use the ad-hoc scenario to distribute the budget proposalevenly across the periods.

Zero-based budgeting method: For the task list scenario, the budget proposal isdistributed evenly across the periods based on task lists.

For the maintenance plan scenario, the budget proposal is divided across theperiods in the same way that the costs are incurred in the maintenance planschedule.

For the ad-hoc scenario, the budget proposal is distributed evenly across theperiods.



Figure 55: Data Model

The budget data cube (0PM_C06) provides the content displayed in the Webinterface. The Web interface is a single point of access to all planning scenariosfor planners and managers.

Customizing functions are available in three different areas in MCB:

� Centralized Customizing settings (IMG)� BPS (transaction BPSO)� BW for hierarchy information

You can use the status and tracking system in budgeting for Plant Maintenanceand Customer Service, to monitor the automated progress of different tasks in thebudgeting cycle and set up automatic e-mail dispatch.



Figure 56: Status and Tracking System



Lesson Summary

You should now be able to:� Use the planning function BW-BPS to plan maintenance budgets


Unit Summary PLM318

Unit SummaryYou should now be able to:� Use the planning function BW-BPS to plan maintenance budgets


PLM318 Course Summary

Course SummaryYou should now be able to:

� Run maintenance-specific reports in the ERP system� Explain basic principles of data update in Enterprise Asset Management� Describe data modeling in BW� Explain and use business content for Enterprise Asset Management in BW


Course Summary PLM318


FeedbackSAP AG has made every effort in the preparation of this course to ensure theaccuracy and completeness of the materials. If you have any corrections orsuggestions for improvement, please record them in the appropriate place in thecourse evaluation.
