PLM318 Analytics in Enterprise Asset Management

May 29, 2016 | Author: tricky777 | Category: Topics
Share Embed Donate


Short Description

plant maintenance module asset management...

Description

PLM318 Analytics in Enterprise Asset Management mySAP ERP Operations: Support

Date Training Center Instructors Education Website

Participant Handbook Course Version: 2006/Q2 Course Duration: 2 Days Material 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 purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Trademarks •

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.



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



ORACLE® is a registered trademark of ORACLE Corporation.



INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.



UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.



Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.



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



JAVA® is a registered trademark of Sun Microsystems, Inc.



JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.



SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

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

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

Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used. Type Style

Description

Example text

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal (in this documentation) and external (in other locations, such as SAPNet).

2006/Q2

Example text

Emphasized words or phrases in body text, titles of graphics, and tables

EXAMPLE TEXT

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

Example text

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

Example text

Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation.



Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© 2006 SAP AG. All rights reserved.

iii

About This Handbook

PLM318

Icons in Body Text The 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's presentation.

iv

© 2006 SAP AG. All rights reserved.

2006/Q2

Contents Course Overview ......................................................... vii Course Goals ...........................................................vii Course Objectives .....................................................vii

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

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

Unit 3: Budget Planning for Plant Maintenance and Customer Service (MCB)............................................................. 91 Budget Planning....................................................... 92

2006/Q2

© 2006 SAP AG. All rights reserved.

v

Contents

vi

PLM318

© 2006 SAP AG. All rights reserved.

2006/Q2

Course Overview This course explains all aspects of reporting that are relevant to Enterprise Asset Management, from initial operational data and its update in the ERP system to different reports in the Business Information Warehouse (BW). The course therefore provides an interface between application- and technology-specific issues. Although we will take a brief look at basic technical concepts of BW, we will not discuss administration or the data extraction process in this application. These issues are the responsibility of BW administrators and operators, and they are dealt with in the relevant BW courses.

Target Audience This course is intended for the following audiences: •

Members of the project team

Course Prerequisites Required Knowledge •

PLM300 - Maintenance

Recommended Knowledge • •

Basic knowledge of Data Warehousing Basic course on Business Information Warehouse

Course Goals This 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 Objectives After completing this course, you will be able to: • • • •

2006/Q2

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 SAP AG. All rights reserved.

vii

Course Overview

PLM318

SAP Software Component Information The information in this course pertains to the following SAP Software Components and releases:

viii

© 2006 SAP AG. All rights reserved.

2006/Q2

Unit 1 Source Data in the ERP System Unit Overview This unit explains the context in the ERP system by describing how to display operational data and update it in PMIS.

Unit Objectives After 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 Contents Lesson: Analyzing Source Data in the ERP System ..........................2 Exercise 1: Analyzing Source Data in the ERP System..................9 Lesson: 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 Overview This unit demonstrates the different initial operational data available in the ERP system.

Lesson Objectives After 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 Example You carry out maintenance measures for your technical systems in the ERP system, 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 ERP system. In addition to the notification history, order history, equipment usage list, and the material where-used list, the maintenance history contains the basic data that 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 task performance. The system displays the data at the document level in granular and unaggregated form.

Lists and Reports for Technical Objects and Materials Multilevel lists You can use multilevel lists to monitor functional locations and equipment. These lists allow you use a filter to activate or deactivate different objects (for example, notifications, orders, measuring points).

2006/Q2

© 2006 SAP AG. All rights reserved.

3

Unit 1: Source Data in the ERP System

PLM318

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

4

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Analyzing Source Data in the ERP System

Lists and Reports for Notifications and Orders Order and operation list You can use the order and operation list to monitor, steer, and analyze orders. You can select entries based on order header and order operation data. A hitlist displays order header and operation data on one screen. As we can see, the system provides a 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 on planned and actual costs and any variations that may occur).

2006/Q2

© 2006 SAP AG. All rights reserved.

5

Unit 1: Source Data in the ERP System

PLM318

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 planning in ongoing maintenance orders. This list provides a clear overview of the availability or reasons for unavailability of stock and non-stock materials for a 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. You can use it to compare planned quantities with the quantities actually withdrawn or with unplanned withdrawals.

6

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Analyzing Source Data in the ERP System

Figure 8: Material Where-Used List - Transaction IW13

2006/Q2

© 2006 SAP AG. All rights reserved.

7

Unit 1: Source Data in the ERP System

PLM318

8

2006/Q2

© 2006 SAP AG. All rights reserved.

PLM318

Lesson: Analyzing Source Data in the ERP System

Exercise 1: Analyzing Source Data in the ERP System Exercise Objectives After 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 Example You are a maintenance manager, and would like to display an overview of the initial 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 first two quarters of 2006. When was equipment installed or removed?

2.

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

3.

Open a material where-used list in the functional location 20 for the first two quarters of 2006. How many distance rings were reserved, how many withdrawn, and how many returned?

4.

Use a CO report to run a cost analysis of maintenance orders in the functional location 20. Select a report that compares the planned and actual costs, and specifies any variation. Use the order group W20 to identify the orders. How do you proceed? What is the cost element breakdown for the costs?

2006/Q2

© 2006 SAP AG. All rights reserved.

9

Unit 1: Source Data in the ERP System

PLM318

Solution 1: Analyzing Source Data in the ERP System Task: Lists and Reports in EAM 1.

Check the usage periods for the functional location K1-B01-1 in the first two quarters of 2006. When was equipment installed or removed? a)

SAP Menu → Logistics → Plant Maintenance → Management of Technical Objects → Functional Location → List Editing → Display (Multilevel) Enter the functional location K1-B01-1 and deactivate all indicators in the Filter area. Then activate the indicators FunctLoc, EquipUsagePeriod, and Equipment. Execute the function. Period from January 01, 2006 to June 30, 2006

2.

EquipUsagePeriod

Equipment

23.08.2004

10004171

14.04.1999

M-1000-N051

11.05.2005

P-1000-DF01

11.05.2005

P-1000-DF02

11.05.2005

P-1000-DF03

14.04.1999

P-1000-N001

09.09.2002

P-2000-N002

Check the usage list for equipment P-1000-N001 as well. In which period was 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 functional location K1-B02

P-1000-N001

06.02.1998 – 14.04.1999

Continued on next page

10

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Analyzing Source Data in the ERP System

3.

Open a material where-used list in the functional location 20 for the first two quarters of 2006. How many distance rings were reserved, how many withdrawn, and how many returned? a)

SAP menu → Logistics → Plant Maintenance → Maintenance Processing → History → Material Where-Used List Select the order status Outstanding, In process, Completed, enter the functional location 20* and the date January 01, 2006 to June 30, 2006.

4.

Material

Description

Reserved

Withdrawn

Returned

KR117185

Distance plate

16

8 (total of 12)

4 (displayed as -4)

Use a CO report to run a cost analysis of maintenance orders in the functional location 20. Select a report that compares the planned and actual costs, and specifies 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/Actual Comparisons → Orders: Actual./Plan/Variance Controlling area

1000

Fiscal year

2006

From period

1

To period

6

Plan version

0

Order group

W20

Cost elements:

2006/Q2

Cost element

Description

400000

Consumed raw materials 1

615000

Repairs

655901

PM orders

© 2006 SAP AG. All rights reserved.

11

Unit 1: Source Data in the ERP System

PLM318

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

12

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Plant Maintenance Information System (PMIS)

Lesson: Plant Maintenance Information System (PMIS) Lesson Overview This unit provides an overview of the structure and handling of standard analyses in the Plant Maintenance Information System (PMIS).

Lesson Objectives After completing this lesson, you will be able to: • • •

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

Business Example You would like to obtain an overview of the options available for analyzing business data related to Asset Management, using standard analyzes that do not require additional formatting. To do this, you would like to find out more about how the PMIS is structured and how 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)

2006/Q2

© 2006 SAP AG. All rights reserved.

13

Unit 1: Source Data in the ERP System

PLM318

SAP Logistics offers several application-related information systems, all of which have the same user interface and similar basic functions. The way in which data is stored is identical in all Logistics Information Systems. A number of special tools and working methods serve to highlight the typical character of a Data Warehouse in 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 more efficient integrated information systems. The three levels break down overall data flow, from data acquisition in operational systems to the presentation of information. Operational integrated applications in Online Transaction Processing (OLTP) systems provide the basis for obtaining information. These systems contain large quantities of master and process data, which is then presented in in information systems in a clear and user-friendly manner.

14

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Plant Maintenance Information System (PMIS)

To do this, the application data is broken down into a few, meaningful key figure amounts, and managed separately in the database tables of a Data Warehouse. At the third level of the Logistics Information System, a number of analysis tools are available for evaluating the statistical data obtained. These tools offer a wide range of options for effectively analyzing and presenting comprehensive statistical data, and provide an efficient instrument for rapid decision-making in state-of-the-art managerial environments.

Analyses

Figure 11: Drilldown Lists in a Standard Analysis

Standard analyses contain a wide range of functions for generating comprehensive presentations and analyses of LIS data. The data for a standard analysis is identified by defining the analysis object (for example, purchasing group, vendor or material group) and by setting default selections. The data can then be displayed in a structured form using an initial list, and a number of drilldown lists. Individual analyses can be archived. Master data or documents can be displayed using standard application transactions from the different explosion levels. A number of special functions are available for individual analysis of the key figures and characteristics attributes on which an analysis is based. All functions for evaluating statistics are supported graphically.

2006/Q2

© 2006 SAP AG. All rights reserved.

15

Unit 1: Source Data in the ERP System

PLM318

Figure 12: User Settings for a Standard Analysis

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

Data Warehouse The individual physical tables of the Logistics Data Warehouse are known as information structures, or info structures for short. These are described in a transparent manner in the SAP Data Dictionary. Info structures are structured in the usual way.

16

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Plant Maintenance Information System (PMIS)

Figure 13: Data Warehouse

Analysis objects from the day-to-day business market are transferred as evaluation groups to the info structures in the form of characteristics. Statistical information is updated for characteristics such as functional locations or equipment in aggregated form. Organizational elements, such as location, plant section or maintenance planner group are used as characteristics in info structures. The time-base offers another possibility for aggregating data. Data is compiled for each period and for each characteristic. With regard to the period unit, you can choose between daily, weekly and monthly data compression for each info structure. Logistics key figures are updated for each characteristic combination and period unit. These include quantitative amounts, which provide information on measurable objects. Key figures can be ascertained for each evaluation group using accumulation, such as actual costs, or they can be simple counters, such as number of orders. Info Structures

2006/Q2

© 2006 SAP AG. All rights reserved.

17

Unit 1: Source Data in the ERP System

PLM318

Figure 14: Info Structures

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

Figure 15: Info Structures in PMIS

18

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Plant Maintenance Information System (PMIS)

The info structure S115 contains the characteristics Order type, Maintenance activity 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 key figures. The field catalogs refer to the communication structures. The info structure S070 contains the characteristics object class, functional location, equipment, and month. The key figures MTTR and MTBR are determined using the individual history of a technical object.

2006/Q2

© 2006 SAP AG. All rights reserved.

19

Unit 1: Source Data in the ERP System

PLM318

Figure 17: Example: Info Structure S070 - Breakdown Analysis

The key figure Mean Time To Repair (MTTR) displays the mean time for which the object in question was not operational. The key figure Mean Time Between Repair (MTBR), on the other hand, represents the time for which the object in question was fully operational. Both key figures are displayed in hours, and are based on all damage reports that were created from the start-up date, and for which 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 the breakdown indicator is selected. In this case, the system does not take account of the first malfunction report in subsequent calculations. The system also only evaluates malfunction reports for which the start and the end of the breakdown is entered. It does not support evaluations based on the start time or downtime. The number of actual breakdowns is then calculated based on the total number of breakdowns. When calculating this time, the system merges two breakdowns that overlap or occur in immediate succession into one actual breakdown. The reference date/time for assigning the key figures MTTR and MTBR to a statistics 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. Note that, in this context, the system only supports periodicity at the monthly level.

20

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Plant Maintenance Information System (PMIS)

Principles for Updating Data

Figure 18: Update in the LIS

Special update modules are used to anchor the Logistics information systems to the SAP ERP system. The LIS update function uses data aggregation to implement one of the most important basic principles of the entire LIS concept. Update programs reduce the amount of operational data to its statistically-relevant parts. They compress data using periodical and object-related accumulation procedures and calculate meaningful key figures from the operational data using formulas and conditions. Statistical data for the LIS can be updated in parallel to the processing of operational data, to ensure that LIS information is consistent with data from operational applications. The data can also be updated periodically, to reduce system overload in the application systems.

2006/Q2

© 2006 SAP AG. All rights reserved.

21

Unit 1: Source Data in the ERP System

PLM318

Figure 19: Results of Maintenance Update

Object and document data is transferred to the interface between the application and information system when you end the relevant editing function by creating or changing and then saving your data. The communications interfaces only make the data available within the program, and the data is not stored in a permanent location. The update program of the relevant information structure records the data required for the corresponding key figure and updates it in the corresponding information structure. The data updated here is permanent and is available for the relevant standard analysis and all other evaluation tools.

Figure 20: Cost Update in PMIS

22

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Plant Maintenance Information System (PMIS)

Maintenance costs are updated by the following key figures in the information structures 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 other criteria, to provide the planned and/or consumed resources for an order. Updates to the other six key figures refer to the actual costs for an order and may be differentiated using value categories. In Customizing, you can determine which value 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. The cost 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 internal personnel costs IAPERKOSE).

2006/Q2

© 2006 SAP AG. All rights reserved.

23

Unit 1: Source Data in the ERP System

PLM318

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 of characteristics and key figures with a time reference. A standard analysis is based on the information structure.

24

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Plant Maintenance Information System (PMIS)

Exercise 2: Plant Maintenance Information System (PMIS) Exercise Objectives After completing this exercise, you will be able to: • Use standard analyses in PMIS, to monitor specific key figures in Plant Maintenance.

Business Example You would like to use standard analyses to obtain an overview of the cost and technical status of your objects, based on relevant key figures. Unlike application lists, 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 carried out 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 quarters of 2006. What are the values for MnTmToRepair and MnTmBetRepair, and what is their significance? To make things clearer, drill down to the characteristic Month.

Continued on next page

2006/Q2

© 2006 SAP AG. All rights reserved.

25

Unit 1: Source Data in the ERP System

PLM318

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

In Customizing in the Logistics Information System, check info structure S115 (cost analysis). What are the characteristics of the info structure?

2.

Identify the field name for key figures for internal wage costs and internal material costs. How do you proceed?

3.

Check which value categories are used to supply the key figures displayed above. 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?

26

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Plant Maintenance Information System (PMIS)

Solution 2: Plant Maintenance Information System (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 to 12.2006 as the period to analyze, and EUR as the analysis currency. Run the cost analysis. Select Edit → Choose Key Figures. Select the key figuresTotal planned costs and Total Actual Costs and transfer them from Pool to Section criteria. Move the key figures for Planned orders, Unplanned orders, No. immediate orders, and Total planned costs from Selection criteria to Pool. Set the following characteristics: Settings → Characteristic display → Key and description Settings → Column width → Characteristic, for example, column width of 30 Save the user settings: Settings → Save settings

2.

In the above analysis, what are the actual costs for inspection work carried out in 2006? a)

In the above analysis, choose Switch drilldown and choose MaintActivityType. Characteristic

Description

Actual costs

Maintenance activity type

Inspection

EUR 347.17

Continued on next page

2006/Q2

© 2006 SAP AG. All rights reserved.

27

Unit 1: Source Data in the ERP System

3.

PLM318

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 key figure, and choose Select Edit →Comparisons → Two key figures . Choose the key figure 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 order type PM01 Maintenance order, and then maintenance order activity type103 Repair. Then double-click the functional location 20-B02, and equipmentTEQ-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 quarters of 2006.

Continued on next page

28

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Plant Maintenance Information System (PMIS)

What are the values for MnTmToRepair and MnTmBetRepair, and what is their significance? To make things clearer, drill down to the characteristic Month. 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 to 06.2006. View → Switch drilldown >Month Month

Actual breakdowns

MnTmToRepair

MnTmBetRepair

Total

2

14.559 H

51,002.442 H

01.2006

1

6.617 H

99,008.383 H

05.2006

1

22.500 H

2,996.500 H

Mean Time To Repair: The average duration of a breakdown in hours. This key figure is calculated using the actual duration of the nth breakdown, divided by the number of actual breakdowns: (End of the nth breakdown - Start of the nth breakdown) / Number of actual breakdowns). Mean Time To Repair: The average duration between two machine breakdowns in hours. This key figure is calculated using the period of time between the end of the last breakdown and the start of the next breakdown, divided by the number of actual breakdowns: (Time of the nth 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 structure S115 (cost analysis).

Continued on next page

2006/Q2

© 2006 SAP AG. All rights reserved.

29

Unit 1: Source Data in the ERP System

PLM318

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 Data Warehouse → Data Basis → Information Structures → Maintain Self-Defined Information Structures Double-click display. Enter info structure S115. Characteristics Order type Maintenance activity type Functional location Equipment

2.

Identify the field name for key figures for internal wage costs and internal material costs. How do you proceed? a)

3.

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

Field name

Internal wage costs

IAPERKOSE

Internal material costs

IAMATKOSE

Check which value categories are used to supply the key figures displayed above.

Continued on next page

30

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Plant Maintenance Information System (PMIS)

How do you proceed? a)

SAP menu → Tools → Customizing → IMG → Execute Project Select SAP Reference IMG. Plant Maintenance and Customer Service > Information Systems for Plant Maintenance and Customer Service > Assign Value Categories to Maintenance Cost Key Figures

4.

Key figures

Field name

Value category

Internal wage costs

IAPERKOSE

615

Internal material costs

IAMATKOSE

400, 890

Check the update rules for info structure S115. Which event triggers updating for the key figure Internal wage costs? What is the currency? a)

SAP menu → Tools → Customizing → IMG → Execute Project Select SAP Reference IMG. 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:

2006/Q2

Key figure

Event

Currency

Internal wage costs

I3 (= order)

76 (= acquisition currency)

© 2006 SAP AG. All rights reserved.

31

Unit 1: Source Data in the ERP System

PLM318

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

32

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Unit Summary

Unit 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 • Describe the structure of PMIS • Explain the principle of data update • Perform standard analyses

2006/Q2

© 2006 SAP AG. All rights reserved.

33

Unit Summary

34

PLM318

© 2006 SAP AG. All rights reserved.

2006/Q2

Unit 2 Data Storage in BW Unit Overview This unit describes data storage in BW, and explains business-content aspects of maintenance.

Unit Objectives After completing this unit, you will 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

Unit Contents Lesson: Basics ................................................................... 36 Exercise 3: Basics........................................................... 47 Lesson: BI Content Enterprise Asset Management ......................... 53 Exercise 4: BI Content Enterprise Asset Management................. 61 Lesson: Working with Queries in Enterprise Asset Management ......... 65 Exercise 5: Working with Queries in Enterprise Asset Management . 77

2006/Q2

© 2006 SAP AG. All rights reserved.

35

Unit 2: Data Storage in BW

PLM318

Lesson: Basics Lesson Overview This lesson provides a brief overview of key concepts, the data model, and data flow in BW.

Lesson Objectives After completing this lesson, you will be able to: •

List the basic concepts of the Business Information Warehouse

Business Example You want to use the Business Information Warehouse (BW), to run analyses in all system components. Before you do this, you will learn about basic concepts and processes in BW.

Introduction The Business Information Warehouse (BW) is a system that is independent of other SAP systems. It extracts data from diverse source systems (both SAP and non-SAP systems), restructures and reformats this data, and compiles it into efficient and user-friendly analyses. BW can run as an independent system together with other SAP or non-SAP systems, or it can be integrated into a mySAP ERP system.

36

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Basics

Figure 22: BW at a Glance

The cornerstone of BW is the BW server , which has preconfigured BI Content for the core areas of your company. BI Content is preconfigured role- and task-based information models that are based on consistent metadata. It provides a range of information that specific roles in a company require to perform their tasks. The Business Explorer (BEx) provides your company with flexible reporting and strategic analysis tools, to support the decision-making processes.

Technical Requirements From a technical point of view, BW represents Business Intelligence (BI) in the SAP NetWeaver integration and application platform. SAP NetWeaver facilitates implementation of the Enterprise Services Architecture (ESA). It allows you to standardize business processes across technological boundaries, integrate applications required by your employees, and easily access structured information and format it in line with your needs.

2006/Q2

© 2006 SAP AG. All rights reserved.

37

Unit 2: Data Storage in BW

PLM318

Figure 23: Business Intelligence Within the Framework of SAP NetWeaver

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

38

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Basics

Figure 24: The mySAP ERP solution

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

Basic Concepts Communication between the source system and BW is broken down into the following steps: • • • • • •

2006/Q2

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

© 2006 SAP AG. All rights reserved.

39

Unit 2: Data Storage in BW

PLM318

Figure 25: Data Flow

Caution: Note that both the data model and data flow in Releases BW3.x and SAP NetWeaver 2004s BI differ, even as regards basic concepts such as DataSource and InfoSource. For more information, refer to the SAP Help Portal or the relevant BW course. Data that logically belong together are available in the source system in the form of 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 of the 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 source system for the data loading process. An extractor is a method (for example, a function module) for loading data from source system datasets to a DataSource extraction structure. The transfer structure is the structure in which data from the source system is transported into BW. It represents a selection of the fields in the source system's extraction structure. A Persistent Staging Area (PSA) is the BW entry layer in which inbound data is saved transparently in its original form.

40

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Basics

An InfoSource in BW describes the quantity of all available data of a business transaction type (such as Cost Center Accounting). An InfoSource always represents a quantity of InfoObjects that logically belong together. The structure in which they are stored is called a communication structure. An InfoObject is a business evaluation object. It is a superordinate term for characteristics, key figures and units. InfoProvider is the superordinate term for BI objects that represent data views or into which data is loaded. This data can usually be analyzed using BEx queries. Examples of InfoProviders include InfoCubes or DataStore objects (formerly known as ODS objects). InfoCubes are data containers used for reports and analyses in BW. They contain ordered characteristics and key figures, depending on their size. These are referred to as InfoObjects in BW. The dimension is a set of characteristics whose content is grouped together under a common superordinate term. If the dimension contains a characteristic whose value already uniquely defines the values of all other characteristics from a business point of view, then the dimension is named after this characteristic. A DataStore object (ODS) is used to store clean, consolidated transaction or master data at the document level (basic level). This data can be analyzed in a BEx query. A DataStore object contains key fields (such as document number and item) and data fields that can contain key figures and character fields (such as order status and customer. DataStore object data can be updated in InfoCubes by delta update, in other DataStore objects or master data tables (attributes or texts) in the same system, or across the entire system. Unlike multidimensional data storage for InfoCubes, data in DataStore objects is stored in transparent, non-nested database tables. Fact and dimension tables are not created.

2006/Q2

© 2006 SAP AG. All rights reserved.

41

Unit 2: Data Storage in BW

PLM318

Figure 26: Basic Concepts

Extraction is scheduled and implemented at specific intervals by BW. This means that 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 using real-time data acquisition. Real-time data acquisition supports the tactical decision-making process. As regards data procurement, it supports operational reporting as it allows data to be sent 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 Layer at short intervals. Data is stored persistently in BI. We recommend that you use real-time data acquisition if you wish to transfer data to BI more regularly than the scheduled intervals (every hour or minute), and if reporting data must be updated several times in one day. The DataSource must support real-time data acquisition. This is one possible characteristic of Web service DataSources and DataSources from the SAP source system. In DataSource maintenance, this characteristic is displayed under Real Time on the Extraction tab. DataSources from SAP source systems can be used for real-time data acquisition provided that BI Content DataSources are enabled for real-time data acquisition. The characteristic for real-time enabled must be set for generic DataSources in the generic delta settings (see the section on delta transfer to BI). Note that DataSources from SAP source systems can support real-time data acquisition in source systems as of BI Service API for SAP NetWeaver Release 2004s (plug-in

42

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Basics

2005.1). Also, only Web Service DataSources that you have defined using DataSource maintenance in BI can be used for real-time data acquisition. You use transformation between the PSA and the DataStore object and run the data transfer process 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 a self-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 belong together (the customer name and region belong to the customer dimension, for example). Adhering to this design criterion ensures that the dimensions remain largely independent of each other and that the data volume of the dimension tables remains small, which helps optimize performance. From a technical point of view, several characteristics values are mapped to an abstract dimension key (DIM-ID) to which the values in the fact table relate. The characteristics selected for an InfoCube are distributed to InfoCube-specific dimensions when the InfoCube is created.

2006/Q2

© 2006 SAP AG. All rights reserved.

43

Unit 2: Data Storage in BW

PLM318

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 abstract numbers (IDs), that are in the key part of the relevant database table. The key figures of the InfoCube are related to the characteristics of the dimension. The characteristics define the granularity (the fineness) of the key figures in the InfoCube. Fact tables and dimension tables are relational database tables.

Figure 29: Fact Tables in Sales and Distribution

44

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Basics

The InfoObjects are grouped in the InfoCube according to the star schema principle, 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's characteristics (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 special organizational structure of characteristics in an InfoCube. The BW master data is transferred by uploading it from the source system. It can be enhanced with other data from external systems.

Figure 30: Star Schema

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

2006/Q2

© 2006 SAP AG. All rights reserved.

45

Unit 2: Data Storage in BW

PLM318

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

46

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Basics

Exercise 3: Basics Exercise Objectives After completing this exercise, you will be able to: • Describe the basic structures in BW from the point of view of Enterprise Asset Management

Business Example You use BW in the integrated ERP system, and would like to get to know its basic structures.

Task: Learn about basic structures in BW from the point of view of Enterprise Asset Management 1.

Display the object overview and data model for the InfoCube Maintenance Orders: Costs and Allocations and Maintenance 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 is activated 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 Completed on Schedule and Total Actual Costshave? What is the technical name in each case?

2006/Q2

© 2006 SAP AG. All rights reserved.

47

Unit 2: Data Storage in BW

PLM318

Solution 3: Basics Task: Learn about basic structures in BW from the point of view of Enterprise Asset Management 1.

Display the object overview and data model for the InfoCube Maintenance Orders: Costs and Allocations and Maintenance 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?

Continued on next page

48

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Basics

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

SAP menu > Information Systems > Business Information Warehouse > Modeling > Data Warehousing Workbench: Modeling In the Info Provider area on the left of the screen, navigate to the Plant Maintenance component: Select Product Lifecycle Management > Plant Maintenance. In the Plant Maintenance component, display the InfoCubes Maintenance Orders: Costs and Allocations and Maintenance Orders: Scheduling in the Object Overview: >Select the InfoCube, open the context menu, and choose >Object Overview. Display the Data Model: >Select the InfoCube, open the context menu, and choose >Display Data 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 key figures. The data model shows a view of characteristics and key figures that is structured according to dimensions. The InfoCube Maintenance Orders: Scheduling has the following dimensions (visible in the Data Model): • • • • • • • • • •

2.

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

What key figures does InfoCube 0PM_C07 have? Continued on next page

2006/Q2

© 2006 SAP AG. All rights reserved.

49

Unit 2: Data Storage in BW

PLM318

How are these key figures mapped in BW? What type or data category do the key figures Number of Orders Completed on Schedule and Total Actual Costshave? What is the technical name in each case? a)

SAP menu > Information Systems > Business Information Warehouse > Modeling > Data Warehousing Workbench: Modeling In the Info Provider area on the left of the screen, navigate to the Plant Maintenance component: Select Product Lifecycle Management > Plant Maintenance. In the Maintenance component, select the InfoCube Maintenance Orders: Scheduling. Open the context menu, and display the Data Model. The following key figures appear in the data model's Key Figures folder: • • • • • • • • • • • • • •

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

50

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Basics

Type: Amount Data Type: CURR (Currency field) Technical name of InfoObject: 0PM_ACCOS

2006/Q2

© 2006 SAP AG. All rights reserved.

51

Unit 2: Data Storage in BW

PLM318

Lesson Summary You should now be able to: • List the basic concepts of the Business Information Warehouse

52

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: BI Content Enterprise Asset Management

Lesson: BI Content Enterprise Asset Management Lesson Overview This lesson explains BI content available in BW for the area of Enterprise Asset Management.

Lesson Objectives After completing this lesson, you will be able to: •

Describe BI Content in the area of Enterprise Asset Management

Business Example You are about to implement BW, and would like to use BI Content provided by SAP for Enterprise Asset Management.

General BI Content consists of predefined role- and task-related information models in mySAP Business Intelligence (BI) that are based on consistent metadata. BI Content provides a range of information that specific roles in a company require 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 NW 2004s BI Content Add-On 3. BI Content speeds up implementation and lowers implementation costs. It also provides a model that incorporates implementation guidelines and experience from previous go-lives.

2006/Q2

© 2006 SAP AG. All rights reserved.

53

Unit 2: Data Storage in BW

PLM318

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

54

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: BI Content Enterprise Asset Management

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 the connected source system(s). InfoCube 0PM_C02 contains information on the removal of an equipment and past installation durations. Time segments of the equipment master record document the installation and dismantling of pieces of equipment at functional locations. Information on the equipment currently installed at which functional location and the length of time it has been installed here is not stored in this InfoCube. Instead it 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 for service orders. InfoCube 0PM_C04 contains the planned and actual work of operations in service orders. InfoCube 0PM_C05 provides data for simulated maintenance costs. Maintenance plans and maintenance task lists are calculated in the extractor.

2006/Q2

© 2006 SAP AG. All rights reserved.

55

Unit 2: Data Storage in BW

PLM318

InfoCube 0PM_C06 plans the maintenance budget. Special planning functions in the BW-BPS application budget planning for Plant Maintenance and Customer Service (MCB) are used to transfer the data. The data is loaded from the InfoCubes 0PM_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 and 0PM_C06. This allows you to compare current budget plans with historic actual costs, for example. It can also be used to monitor the budget for the current fiscal year.

56

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: BI Content Enterprise Asset Management

Figure 35: Queries for Orders

Query 0PM_C01_Q001 provides you with an overview of variations in the planned/actual costs of service orders. Query 0PM_C02_Q001 displays the number of pieces of equipment dismantled on functional locations, and the average installation duration. Query 0PM_C03_Q001 allows you to view the number of maintenance orders and the average lead time. You can also drill down to technical objects and maintenance activity types. Query 0PM_C04_Q001 contains the planned and actual work for maintenance orders 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 orders that 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 were actually completed in this period (0PM_STAGE ≠ ‘Outstanding’ (value = 0) and ≠ ‘Deletion indicator’ (value = 4) 0CALWEEK =last 12 calendar weeks including current week).

2006/Q2

© 2006 SAP AG. All rights reserved.

57

Unit 2: Data Storage in BW

PLM318

Query 0PM_C07_Q0005 displays all orders that are fully planned, and have a basic 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 for orders 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 level for functional locations in the last 12 months (0CALMONTH = last 12 months). Query 0PM_DS04_Q0001 contains the proportion of completed orders in the relevant planned week (0PM_STAGE ≠ ‘Outstanding’ (value = 0) and ≠ ‘Deletion indicator’ (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 that was uploaded from the source system(s). Master data on notifications is required to evaluate this InfoCube. When defining queries for this InfoCube, note that the Cube may contain data from the Quality Management and Plant Maintenance components. Therefore, these queries should contain a filter for the notification types, so that different analysis requirements are met, for example, evaluation of technical objects, or a customer- or vendor-oriented view of the key figures. InfoCube 0QM_C06 contains characteristics and key figures on the causes of error or damage items in quality, maintenance, and service notifications. It also contains characteristics from the notification and the notification item. Data is updated from a self-defined InfoSource for each notification category.

58

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: BI Content Enterprise Asset Management

InfoCube 0QM_C07 consists of characteristics and key figures for activities in quality, maintenance, and service notifications, irrespective of whether the activities relate to the entire notification or a notification item. It also contains characteristics from the notification and the notification item, if applicable. Data is updated from a self-defined InfoSource for each notification category. InfoCube 0QM_C08 incorporates characteristics and key figures for tasks in quality, maintenance, and service notifications, irrespective of whether the tasks relate to the entire notification or one notification item. It also contains characteristics from the notification and the notification item, if applicable. Data is updated from a self-defined InfoSource for each notification category. InfoCube 0QM_C09 contains characteristics and key figures on the error and damage items from quality, maintenance, and service notifications. It also contains characteristics from the relevant notifications. Data is updated from a self-defined InfoSource for each of the three notification categories. InfoCube 0QM_C10 displays key figures on quality, maintenance, and service notifications. Each of these three notification categories is updated using a self-defined InfoSource.

Figure 37: Queries for Notifications

Query 0QM_C06_Q001 contains information on the causes of damage in Plant Maintenance. 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 of damage 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.

2006/Q2

© 2006 SAP AG. All rights reserved.

59

Unit 2: Data Storage in BW

PLM318

Query 0QM_C07_Q001 displays information on maintenance notification activities and their frequency. Query 0QM_C08_Q001 displays the number and status of tasks triggered for maintenance notifications. Query 0QM_C09_Q003 displays the damage codes entered, and the frequency with which they occur. Query 0QM_C09_Q0007 allows you to determine damage codes for maintenance and service notifications. This query was developed for the Maintenance Technician Business Package. Web template 00TPLI_QM_C09_Q0007_V01 is also available for this query. You can use query 0QM_C09_Q0010 to evaluate the frequency with which a problem occurs for each notification category. Query 0QM_C10_Q001 contains information on the number of notifications that exist for technical objects. The queries 0PM_DS02_Q0001 and 0PM_DS02_Q0002 determine the key figures 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 question was not operational. MTBR, on the other hand, represents the time for which the relevant object was fully operational. The system uses all malfunction reports that were entered from the start-up date, and for which the breakdown indicator is selected, to calculate these key figures. 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 the breakdown indicator is selected. In this case, the system does not take account of the first malfunction report in subsequent calculations. The system also only analyzes malfunction reports in which the start and end of the breakdown is 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 total number of notified breakdowns for a technical object. It merges two breakdowns that overlap timewise into one actual breakdown. The reference date/time for assigning the key figures MTTR and MTBR to a statistics 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 query 0PM_DS02_Q0002. Query 0PM_DS02_Q0003 displays the frequency of breakdowns and the degree of technical availability.

60

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: BI Content Enterprise Asset Management

Exercise 4: BI Content Enterprise Asset Management Exercise Objectives After completing this exercise, you will be able to: • Describe the BI Content available for Enterprise Asset Management

Business Example You use Enterprise Asset Management in the ERP system, and would like to implement the relevant analyses and evaluations in BW. To this end, the BI Content delivered in BW for Enterprise Asset Management is to 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 of Maintenance manager 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?

2006/Q2

© 2006 SAP AG. All rights reserved.

61

Unit 2: Data Storage in BW

PLM318

Solution 4: BI Content Enterprise Asset Management 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? a)

SAP menu > Information Systems > Business Information Warehouse > Modeling > Data Warehousing Workbench: Modeling In the Info Provider area on the left of the screen, navigate to the Plant Maintenance component: Select Product Lifecycle Management > Plant Maintenance. In the Maintenance component, select the DataStore object MTTR/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 table that 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 of Maintenance manager delivered as standard BI content. How do you proceed? What queries can be implemented in this standard role?

Continued on next page

62

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: BI Content Enterprise Asset Management

On which InfoCube are these queries based? a)

SAP menu > Information Systems > Business Information Warehouse > Modeling > Data Warehousing Workbench: Modeling 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 Maintenance Manager RoleSAP_BW_0ROLE_0054 The Menu tab contains the standard role menu, from which you can call Web 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, and select Display Details InfoCube 0PM_C07

2006/Q2

© 2006 SAP AG. All rights reserved.

63

Unit 2: Data Storage in BW

PLM318

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

64

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Working with Queries in Enterprise Asset Management

Lesson: Working with Queries in Enterprise Asset Management Lesson Overview This lesson looks at practical aspects of working with queries in Enterprise Asset Management.

Lesson Objectives After completing this lesson, you will be able to: •

Run different queries in Enterprise Asset Management

Business Example You implement maintenance tasks for technical equipment in your company in the ERP system. You would like to run different reports and analyses for these business 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. It provides you with flexible reporting and evaluation tools to carry out strategic analyses 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 levels of detail for historic and current data, and analyze this data from different angles using the Portal or Microsoft Excel. BEx tools also allow you to create planning applications, and enter data in BI-integrated planning.

2006/Q2

© 2006 SAP AG. All rights reserved.

65

Unit 2: Data Storage in BW

PLM318

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 InfoProvider queries in the BEx Query Designer, allowing you to evaluate BI data. By selecting and combining InfoObjects (characteristics and key figures) and reusable structures in a query, you can determine how the system analyzes data for the relevant InfoProvider. BEx Web Application Designer The BEx Web Application Designer is a desktop application that allows you to create Web applications. You can use it to generate HTML pages that contain a variety of BI-specific content such as tables, charts, and maps. Web applications are based on Web templates that you can create and change in the Web Application Designer. You can save the Web templates and access them from the Web browser or Portal. Web templates are referred to as Web applications once they have been implemented in the Web. The Web Application Designer also allows you to use standard markup languages and the Web Design API to create tailor-made scenarios with user-specific interface elements. The Web applications that you create in this way are BEx Web-based applications for data analysis, reporting, and analytical applications. BEx Broadcaster

66

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Working with Queries in Enterprise Asset Management

BEx Information Broadcasting allows you to distribute by e-mail BI Content (such as Web templates, queries, query views, reports, and workbooks) as predefined documents 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 (in the Knowledge Management folder or in collaboration rooms). In addition to predefined documents that contain historic data, you can create online links to queries and Web applications. The Business Explorer portal role illustrates 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 the Business Explorer. It is integrated in Microsoft Excel. The BEx Analyzer allows you 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 context menu or the drag and drop function to this end. You can insert design items such as dropdown boxes, radio button groups and buttons in your Microsoft Excel worksheets, to customize the interface for your queries. In this way, you can transform a Microsoft Excel worksheet into a complete query application.

Calling a Query You can call a query from the BEx Analyzer or from the role menu, using a Web template. 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 analyze different 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.

2006/Q2

© 2006 SAP AG. All rights reserved.

67

Unit 2: Data Storage in BW

PLM318

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 to sect 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 allows you to filter a dataset using specific criteria.

Figure 39: Query Filter

You can adjust the query layout from the context menu.

68

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Working with Queries in Enterprise Asset Management

Figure 40: Query Layout (1)

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

Figure 41: Query Layout (2)

You can also define exceptions.

2006/Q2

© 2006 SAP AG. All rights reserved.

69

Unit 2: Data Storage in BW

PLM318

Figure 42: Query Exception (1)

Figure 43: Query Exception (2)

Portal Integration You 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 different displays in the Portal. The Portal allows you to access applications from other systems and sources such as the Internet or Intranet. This means that you can access structured and unstructured information from a central point of access. In addition to Knowledge Management, Internet, and Intranet content, you can access business data from data analysis.

70

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Working with Queries in Enterprise Asset Management

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 the BI system. You can combine the BEx Web Application as an iView, as part of a portal page, with other iViews from different systems. You can change the iView characteristics, 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 applications and store them as a document in Knowledge Management. The predefined BEx Web applications contain historic data on specific points in time. These documents can also be displayed in an iView. BEx Web Application as a Link in Knowledge Management

2006/Q2

© 2006 SAP AG. All rights reserved.

71

Unit 2: Data Storage in BW

PLM318

You can create links to BEx Web Applications in Knowledge Management. The links display current data from the BI report. Unlike BEx Web applications as an iView, this call is made indirectly using Repository Manager for BI metadata. You can 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 Analyzer workbooks play a particularly key role. Workbooks can be incorporated into and called 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 browser window. BI Documents You can use the Repository Manager to integrate the documents and metadata stored in the BI system (in particular the metadata documentation) into the Portal's Knowledge Management area, where they are displayed for users with other documents in a folder structure. Individual documents can also be displayed as an iView. Web Interface (From BW-BPS) A Web interface (from BW-BPS) is a Web-enabled planning application structured as a business server page application (BSP application) that is created using the Web Interface Builder. You can combine a Web interface as part of a portal page as an iView, together with other views such as BEx Web applications.

SAP Analytics SAP Analytics contains both cross-industry and industry-specific analytic applications. It is based on the SAP NetWeaver platform, which optimizes the use of existing application components, irrespective of the provider in question. Functions for analyses, transactions, and collaboration are seamlessly integrated. SAP Analytics is implemented using composite applications (xAPPs). xAPPs are meta applications that provide functional services for existing applications, providing a new application in the process. The development tools contained in the SAP NetWeaver Visual Composer provide easy access to fine-tuned visualization functions. These include the comprehensive, robust functions of Macromedia Flex, which can be used to automatically create Flash graphics, simplifying and optimizing the user interface for most users.

72

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Working with Queries in Enterprise Asset Management

Figure 45: SAP NetWeaver Visual Composer

Three analytical applications that are based on this technology are available in Enterprise Asset Management: • • •

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

Figure 46: Breakdown Analysis

2006/Q2

© 2006 SAP AG. All rights reserved.

73

Unit 2: Data Storage in BW

PLM318

Downtime Analysis uses data from the maintenance notification, and provides the maintenance manager with an overview of technical equipment and its availability. From a technical point of view, the InfoProviders 0PM_DS02 and 0QM_C06, and the queries 0PM_DS02_Q0003 and 0QM_C06_Q006 are used. The system views the key figure Technical Availability, which can be displayed as a quotient of the standard operation time and downtime (MTBR/(MTBR + MTTR)). This key figure is color-coded using specific threshold values, allowing you to easily 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, object parts, damage, causes), to effectively address the problem.

Figure 47: Maintenance Cost Monitor – Work View

This application displays the maintenance costs for work centers, broken down into 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 query 0PM_C01_Q0002 are used.

74

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Working with Queries in Enterprise Asset Management

Figure 48: Maintenance Cost Monitor - Equipment View

This application displays the maintenance costs for equipment, broken down into 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 query 0PM_C01_Q0003 are used.

2006/Q2

© 2006 SAP AG. All rights reserved.

75

Unit 2: Data Storage in BW

76

PLM318

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Working with Queries in Enterprise Asset Management

Exercise 5: Working with Queries in Enterprise Asset Management Exercise Objectives After completing this exercise, you will be able to: • Working with practical queries in EAM

Business Example You 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 standard version. How do you proceed? Hint: For technical reasons, this query starts in the maintenance manager's role menu in the backend system. This has been modified for 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 maintenance plant Hamburg (plant 1000). How do you proceed?

3.

Add the Cost element characteristic to the standard drilldown, so that the cost element 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 only displayed with its key. How do you proceed? Continued on next page

2006/Q2

© 2006 SAP AG. All rights reserved.

77

Unit 2: Data Storage in BW

PLM318

Task 2: Run the query forOverdue Tasks. 1.

Execute the query Overdue tasks for maintenance orders. 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 standard version. How do you proceed? Set a filter for the view so that only the values for maintenance planning plant 1000 are displayed. How do you proceed? What is used to measure the number of overdue orders? Hint: For technical reasons, this query starts in the maintenance manager's role menu in the backend system. This has been modified for the training course and is slightly different to the standard menu (0ROLE_0054).

Task 3: Run the query MTTR/MTBR. 1.

Execute the queryMTTR/MTBR. 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 standard version. Identify the following parameters for equipment TEQ-20 for the second quarter 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? Hint: For technical reasons, this query starts in the maintenance manager's role menu in the backend system. This has been modified for the training course and is slightly different to the standard menu (0ROLE_0054). Continued on next page

78

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Working with Queries in Enterprise Asset Management

Task 4: OPTIONAL Create your own query using an existing query, and a standard Web template. 1. Hint: The following exercise runs on the Windows Terminal Server (WTS) specified by your instructor. Make sure that the training system specified by your instructor is entered in the SAPLogon dialog 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 name with 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. Save the Web. How do you proceed?

4.

From the Web template, load the query to the Query Designer and save the 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 (as described above).

5.

Change the query so that the planning plant with the default setting 1000 acts as a static filter, and the cost element is available in the standard drilldown in the lines that follow the planner. How do you proceed?

2006/Q2

© 2006 SAP AG. All rights reserved.

79

Unit 2: Data Storage in BW

PLM318

Solution 5: Working with Queries in Enterprise Asset Management 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 standard version. How do you proceed? Hint: For technical reasons, this query starts in the maintenance manager's role menu in the backend system. This has been modified for the training course and is slightly different to the standard menu (0ROLE_0054). a)

In the BW system, select User menu. User menu → Maintenance Manager → Planned/Actual Costs Deviation (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 key figure type (= 1000 - corresponds to: numeric). Dynamic Filter: No entries Variable values: The variables Equipment and Functional Location exist; no values are set.

2.

Format the data so that the system only displays the costs in the maintenance plant Hamburg (plant 1000). How do you proceed? a)

3.

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 Maintenance plant row.

Add the Cost element characteristic to the standard drilldown, so that the cost element is displayed in the lines of the diagram. Continued on next page

80

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Working with Queries in Enterprise Asset Management

How do you proceed? In which cost element have the majority of actual costs been incurred? a)

4.

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

Change the query settings so that the cost element characteristic is only displayed with its key. How do you proceed? a)

In the query area, select the Cost element characteristic, and choose Enhanced menu. In this menu, select Characteristics. In the Characteristics 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. 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 standard version. How do you proceed? Set a filter for the view so that only the values for maintenance planning plant 1000 are displayed. How do you proceed?

Continued on next page

2006/Q2

© 2006 SAP AG. All rights reserved.

81

Unit 2: Data Storage in BW

PLM318

What is used to measure the number of overdue orders? Hint: For technical reasons, this query starts in the maintenance manager's role menu in the backend system. This has been modified for the training course and is slightly different to the standard menu (0ROLE_0054). a)

In the BW system, select User menu. User menu → Maintenance Manager → Overview Tasks (Web Template) Default Settings:: Static Filter: None in this case In the standard system, set to: Calendar day (< today's date) and processing 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 filter icon, 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. 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 standard version. Identify the following parameters for equipment TEQ-20 for the second quarter of 2006 (period from 04.2006 to 06.2006): No. of actual breakdowns

?

Actual outage time

?

Actual time between outages

? Continued on next page

82

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Working with Queries in Enterprise Asset Management

How do you restrict the timeframe? Hint: For technical reasons, this query starts in the maintenance manager's role menu in the backend system. This has been modified for the training course and is slightly different to the standard menu (0ROLE_0054). a)

In the BW system, select User menu. User menu → Maintenance Manager → MTTR/MTBR (Web Template) Default Settings:: Static Filter: None Dynamic Filter: None Variable values: Plant, work center, planner group, month/calendar year, equipment, cost centers, functional location – no value set for all of these items. Display equipment with key: In the query area, select the Equipment characteristic, and choose Enhanced menu. In this menu, select Characteristics. In the Characteristics 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 to 06.2006 and select Copy. No. of actual breakdowns

1

Actual outage time

22.5 h

Actual time between outages

2,996.5 h

Continued on next page

2006/Q2

© 2006 SAP AG. All rights reserved.

83

Unit 2: Data Storage in BW

PLM318

Task 4: OPTIONAL Create your own query using an existing query, and a standard Web template. 1. Hint: The following exercise runs on the Windows Terminal Server (WTS) specified by your instructor. Make sure that the training system specified by your instructor is entered in the SAPLogon dialog 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 name with 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/Technical Name 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 templates such as tables and charts) Characteristics view (on the bottom left – with tabs General and Web Item). View of loaded Web template (right – large window – with the tabsLayout, HTML, and Overview).

3.

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

Continued on next page

84

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Working with Queries in Enterprise Asset Management

How do you proceed? a)

In the Web Application Designer, go to the work area on the right of the screen and select the Overview tab. In the Characteristics view on the bottom 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 Web template (by selecting the disk icon).

4.

From the Web template, load the query to the Query Designer and save the 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 (as described above). a)

In the Web Application Designer, select the Overview tab in the work area (in the large window on the right). Position the cursor on the top line (TITLE); Select Tools → Query Designer Save the query by selecting the Save query as button (with yellow and white triangle). Enter the description and technical name as described above. Assign the new query to the template (as described above). Save the template.

5.

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

Continued on next page

2006/Q2

© 2006 SAP AG. All rights reserved.

85

Unit 2: Data Storage in BW

PLM318

How do you proceed? a)

The characteristics Planning plant and Cost element are in the Free characteristics area; move the Planning plant characteristic from here to the Filter area using the drag and drop function. Select the right mouse button and chooseRestrict; transfer the value 1000 to the selection area; Move the Cost element characteristic to the Lines area using the drag and drop function. Save your query. From the Web Application Designer, execute the query in the browser: Web template → Execute in browser.

86

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Working with Queries in Enterprise Asset Management

Lesson Summary You should now be able to: • Run different queries in Enterprise Asset Management

2006/Q2

© 2006 SAP AG. All rights reserved.

87

Unit Summary

PLM318

Unit Summary You 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

88

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Test Your Knowledge

Test Your Knowledge 1.

InfoObjects in BW are the info structures that are extracted from the Logistics Information System. Determine whether this statement is true or false.

□ □ 2.

True False

InfoCubes are multidimensional data containers made up of different InfoObjects. Determine whether this statement is true or false.

□ □ 3.

True False

The extractor is the superuser responsible for extracting data from the source system. Determine whether this statement is true or false.

□ □ 4.

True False

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

□ □

2006/Q2

True False

© 2006 SAP AG. All rights reserved.

89

Test Your Knowledge

PLM318

Answers 1.

InfoObjects in BW are the info structures that are extracted from the Logistics Information System. Answer: False InfoObjects are characteristics, key figures and units in BW.

2.

InfoCubes are multidimensional data containers made up of different InfoObjects. Answer: True InfoCubes are data containers that represent a self-contained business area, and are structured according to dimensions. The dimension is a set of characteristics whose content is grouped together under a common superordinate term. This means that an InfoCube systematically evolves from a quantity, after a specific evaluation target of structured InfoObjects.

3.

The extractor is the superuser responsible for extracting data from the source system. Answer: False An extractor is a program that can load data from source system datasets into the extraction structure of a DataSource.

4.

A query is an automatically generated program that extracts data from the source system, and compares the field lengths between the ERP system and 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).

90

© 2006 SAP AG. All rights reserved.

2006/Q2

Unit 3 Budget Planning for Plant Maintenance and Customer Service (MCB) Unit Overview This unit explains how maintenance budgets are planned in both the ERP system and BW.

Unit Objectives After completing this unit, you will be able to: •

Use the planning function BW-BPS to plan maintenance budgets

Unit Contents Lesson: Budget Planning ....................................................... 92

2006/Q2

© 2006 SAP AG. All rights reserved.

91

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

PLM318

Lesson: Budget Planning Lesson Overview This lesson provides an overview of how to plan maintenance budgets in BW-BPS.

Lesson Objectives After completing this lesson, you will be able to: •

Use the planning function BW-BPS to plan maintenance budgets

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

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

Figure 49: MCB Process

92

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Budget Planning

The ERP system transfers the required data to BW, and the Maintenance Cost Budgeting (MCB) application provides an integrated planning environment for the data. The planning process contains at least the following individual steps: •

• •

• •

The responsible manager/maintenance manager creates one or more planning versions for specifying the budget (for example, minimum version, maximum version). 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 responsible maintenance planner. The maintenance planner uses BW reports to draw up a budget proposal. These reports are created, for example, by extracting maintenance data from ERP EAM (zero-based or history-based). The maintenance planner sends the 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 not automatically carried out in the ERP system. You can use the BADI UPA_MCB_RETRACT to implement it manually (more information is 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.

2006/Q2

© 2006 SAP AG. All rights reserved.

93

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

PLM318

Figure 50: MCB Roles

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

94

MCB administrator: Responsible for MCB Customizing, and defining the budget planning process Maintenance manager: Responsible for defining, triggering, monitoring, and completing the budget planning process Maintenance budget planner: Responsible for planning the budget for his/her own area of responsibility Maintenance engineer: Responsible for ensuring that operational maintenance master data is complete and correct (not an MCB user) BW operator: Responsible for BW-BPS data (not an MCB user)

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Budget Planning

Figure 51: Planning scenarios

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

Preventive ($M): Costs from routine maintenance work that is planned using maintenance plans Planned ($P): Costs from sporadic maintenance work, that is planned using task 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 planning scenarios by the zero- or history-based budgeting method. In the standard configuration, the costs for the budget category proposal can be broken down as follows: For the zero-based budgeting method, the values are determined using the maintenance plan scenario. For the history-based budgeting method, the values are determined using the historic or ad-hoc scenario.

2006/Q2

© 2006 SAP AG. All rights reserved.

95

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

PLM318

Figure 52: History-Based Planning Scenario

For the history-based budgeting method, you create your maintenance budget using historic data, in particular historic actual costs from maintenance and service orders. You upload historic data for actual costs from maintenance orders or settlements from your ERP system into InfoCube 0PM_C01 in BW. Data from InfoCube 0PM_C01 must be 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. This data serves as the planning basis for your maintenance budget. The following planning scenarios exist for the history-based budgeting method: •



96

History-based scenario: This planning scenario is based on historic data, for example, the equipment history, or maintenance orders for your vehicles, equipment, and pumps. Ad-hoc scenario: This planning scenario is based on ad hoc or customized data entry. That is, when you create budget proposals using this budgeting method, you do not have to base them on historic data.

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Budget Planning

Figure 53: Zero-Based Planning Scenario

When using the zero-based budgeting method, you create a budget based on planned data, in particular simulated planned costs. Rather than being determined using actual data, the budget is drawn up based on planned tasks. Task lists and maintenance plans are used as planning aids. The planned value of the services in the budget (work, external services, material) is determined automatically 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 your ERP system into InfoCube 0PM_C05 in BW. Data from InfoCube 0PM_C05 must be 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: • • •

2006/Q2

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.

© 2006 SAP AG. All rights reserved.

97

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

PLM318

Figure 54: Budget Distribution

The maintenance planner can use history-based or zero-based budgeting methods to create budget proposals. The planner can distribute the data to the defined periods 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 leave period distribution the same as the way in which costs were incurred for past orders. Alternatively, you can use the ad-hoc scenario to distribute the budget proposal evenly across the periods. Zero-based budgeting method: For the task list scenario, the budget proposal is distributed evenly across the periods based on task lists. For the maintenance plan scenario, the budget proposal is divided across the periods in the same way that the costs are incurred in the maintenance plan schedule. For the ad-hoc scenario, the budget proposal is distributed evenly across the periods.

98

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Budget Planning

Figure 55: Data Model

The budget data cube (0PM_C06) provides the content displayed in the Web interface. The Web interface is a single point of access to all planning scenarios for 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 Maintenance and Customer Service, to monitor the automated progress of different tasks in the budgeting cycle and set up automatic e-mail dispatch.

2006/Q2

© 2006 SAP AG. All rights reserved.

99

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

PLM318

Figure 56: Status and Tracking System

100

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Lesson: Budget Planning

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

2006/Q2

© 2006 SAP AG. All rights reserved.

101

Unit Summary

PLM318

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

102

© 2006 SAP AG. All rights reserved.

2006/Q2

PLM318

Course Summary

Course Summary You should now be able to: • • • •

2006/Q2

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 SAP AG. All rights reserved.

103

Course Summary

104

PLM318

© 2006 SAP AG. All rights reserved.

2006/Q2

Feedback SAP AG has made every effort in the preparation of this course to ensure the accuracy and completeness of the materials. If you have any corrections or suggestions for improvement, please record them in the appropriate place in the course evaluation.

2006/Q2

© 2006 SAP AG. All rights reserved.

105

View more...

Comments

Copyright ©2017 KUPDF Inc.