Investment Management in Plant

Maintenance
SAP Best Practices for Chemicals

Purpose. Key Process Steps • Creating / Changing Program Structure • Create / Change / Display Measures • Assign WBS Element to Functional Location • Plan Costs on Projects (Bottom-Up Planning) • Roll-Up Planned Costs to the Investment Program • Budgeting Investment Program • Release Measures • Assignment of Maintenance Projects to Maintenance Orders • Assignment of Capital Investment Projects to a Maintenance Order • Controlling Budget vs. and Key Process Steps Purpose The purpose is to describe business processes related to Investment Management within Plant Maintenance. Benefits. Benefits The Budget planner can plan and distribute budget data to the overhaul maintenance project network/activities. Actual Costs (Reporting) • Procedure Reporting Planned Values • Procedure Reporting Budget Values • Fiscal Year Changing of Programs • Procedure Open New Approval Year • Procedure Open New Approval Year • Procedure Closing Old Approval Year © 2011 SAP AG. All rights reserved. 2 .

3 .Required SAP Applications and Company Roles Required SAP Applications SAP ECC 6. All rights reserved.00 enhancement package 5 Company Roles • Chemicals: Maintenance Specialist • Investment Manager © 2011 SAP AG.

is not limited only to investments you capitalize for bookkeeping or tax purposes. All rights reserved. An investment in this context can be any measure that initially causes costs. © 2011 SAP AG. investment. and financing processes for: • Capital investments. © SAP 2008 / Page 4 4 . and that may only generate revenue or provide other benefits after a certain time period has elapsed (for example.Overview The Investment Management (IM) component provides functions to support the planning. therefore. such as continuing education of employees or establishing new markets • Maintenance programs The term investment. plant maintenance). such as the acquisition of fixed assets as the result of-house production or purchase • Investments in research and development • Projects that fall primarily under overhead.

Controlling and Plant Maintenance © 2011 SAP AG. Asset-Accounting. Maintenance projects and operational maintenance activities • Application module PS (Project System) Module PS as planning and controlling tool for individual measures • Application module PM (Plant Maintenance) Maintenance work orders as cost collector for handling of operational and project-related activities • It is fully integrated process of Financials.Features • Application module IM (Investment Management) Module IM for overall planning. budgeting and controlling of Investment projects. 5 . All rights reserved.

All rights reserved. Production Maintenance Quality assurance 6 .The Asset Life-Cycle Construction Projection Procurement process Decision for Investment Building Assembling EAM Research & Development Operating Asset retirement © 2011 SAP AG.

7 . All rights reserved.General Program structure • Shows the structure of the enterprise • Based on technical structure © 2011 SAP AG.

All rights reserved.Integration IM/PS and PM Investment program Maintenance program Projects Projects Work order Work © 2011 SAP AG. order 8 .

Budgeting Maintenance IM-Program position Budget assignments by Functional location Work order Aggregation Planned Actual Values Costs Active availability check Budget © 2011 SAP AG. 9 . All rights reserved.

All rights reserved. 10 .Process Cost planning Cost planning based on: • Objects .Count / Types Adjustment • Scale of planned measures • Components and services • Estimation of unplanned measures Budget Compares Reporting Modifying Actual Costs: • Workt • Components • other costs © 2011 SAP AG.

3 Ball system 1 Ball system 2 Ball system 3 Plan Cost center K1 K2 K3 Settlement to cost centger PROD © 2011 SAP AG.Example: Scenario Plant Maintenance Program: CH-MAINT BP01 Technical structure: KMA BP01 KMA1 PRO Cost center WBS Work order OP Plan Plan Components Internal labor Budget Projects : Pr 1 BP01-PM-20 Operational Maintenance Pr 1. 11 .1 Pr 1. All rights reserved.2 Pr 1.

All rights reserved.Process Flow Diagram Creating / Changing Program Structure © 2011 SAP AG. Actual Costs (Reporting) 12 . Planning and Budgeting Create / Change / Display Measures Old/new Approval Year Assign WBS element to Function Location Fiscal Year Changing of Programs Plan Costs on Projects (Bottom-Up Planning) Assign Projects to Maintenance Order Procedure Reporting Budget Values Roll-Up Planned Costs to the Investment Program Budgeting Investment Program Procedure Open New Approval Year Release Measures Budgeting Distribution Procedure Closing Old Approval Year Fiscal Year Change of Programs Investment Programs Investment Manager Chemicals: Maintenance Specialist Event Investment Management in Plant Maintenance (932) Procedure Reporting Planned Values Controlling Budget vs.

it is used to reflect a document generated by a task step. instead. put the scenario number and name here. report. All rights reserved. and the step numbers from that scenario here Corresponds to a task step in the document Process Decision: Identifies a decision / branching point. Existing Version / Data: This block covers data that feeds in from an external process Does not generally correspond to a task step in a document. it is used to reflect a task that is manually performed. instead. name. Corresponds to a task step in the document Sub-Process Reference: If the scenario references another scenario in part. this step does not have any incoming flow lines System Pass / Fail Decision: This block covers an automatic decision made by the software Does not generally correspond to a task step in the document. such as Accounts Payable Clerk or Sales Representative. Lines represent different choices emerging from different parts of the diamond. Does not usually correspond to a task step in the document. rather than a specific role. instead. External to SAP External Events: Contains events that start or end the scenario. which affects the process flow. it is used to reflect a document generated by a task step. instead. Hardcopy / Document Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario. or influence the course of events in the scenario. this shape reflects data coming from an external source. Connects two tasks in a scenario process or a non-step event Business Activity / Event: Identifies an action that either leads into or out of the scenario. Symbol Diagram Connection The other process flow symbols in this table go into these rows. This band can also identify an organization unit or group. Role band contains tasks common to that role.Legend <Function> Symbol Description Usage Comments Band: Identifies a user role. this shape does not have any outgoing flow lines Manual Process: Covers a task that is manually done Does not generally correspond to a task step in a document. You have as many rows as required to cover all of the roles in the scenario. or form Does not correspond to a task step in a document. instead. Reflects a choice to be made after step execution © 2011 SAP AG. signifying a choice to be made by the end user. instead it is used to reflect an automatic decision by the system that is made after a step has been executed. such as unloading a truck in the warehouse. this shape does not have any outgoing flow lines Budget Planning: Indicates a budget planning document Does not correspond to a task step in a document. it is used to reflect a document generated by a task step. Line can also lead to documents involved in the process flow. put the scenario number. this shape does not have any outgoing flow lines Financial Actuals: Indicates a financial posting document Does not correspond to a task step in a document. Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. or an outside Process that happens during the scenario Does not correspond to a task step in the document Unit Process: Identifies a task that is covered in a step-by-step manner in the scenario Corresponds to a task step in the document Financial Actuals Process Reference: If the scenario references another scenario in total. Business Activity / Event Unit Process Process Reference SubProcess Reference Process Decision Usage Comments To next / From last Diagram: Leads to the next / previous page of the Diagram Flow chart continues on the next / previous page Hardcopy / Document: Identifies a printed document. Description Budget Planning Manual Process Existing Version / Data System Pass/Fail Decision 13 .

This document is provided without a warranty of any kind. and PowerPoint are registered trademarks of Microsoft Corporation. POWER5. Sybase 365. OpenPower. S/390 Parallel Enterprise Server. iAnywhere. System i5. the Adobe logo. PostScript. X/Open. or transmitted in any form or for any purpose without the express prior written permission of SAP AG. VideoFrame. System Storage. Business Objects and the Business Objects logo. GPFS. Crystal Decisions. Netfinity. This limitation shall not apply in cases of intent or gross negligence. Inc. used under license for technology invented and implemented by Netscape. pSeries. MetaFrame. eServer. Power Architecture. OSF/1. System z9. MVS/ESA. Web Intelligence. Oracle is a registered trademark of Oracle Corporation. Inc. Outlook. or consequential damages that may result from the use of these materials. graphics. Windows. OS/2. HTML. Business Objects is an SAP company. indirect. or non-infringement. Excel. System p. and/or development. and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. RACF. Microsoft. Program Neighborhood.S. StreamWork. AS/400. All rights reserved. z9. PowerPC. Linux is the registered trademark of Linus Torvalds in the U. or other items contained within this material. WebSphere. System x. World Wide Web Consortium. DB2. either express or implied. XHTML and W3C are trademarks or registered trademarks of W3C®. POWER6. WinFrame. and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business. Sybase is an SAP company. XML. copied. SAP NetWeaver. SAP does not warrant the accuracy or completeness of the information. PartnerEdge. 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. BatchPipes. and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase. SAP BusinessObjects Explorer. product strategy. zSeries. All other product and service names mentioned are the trademarks of their respective companies. AIX. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. OS/400. Please note that this document is subject to change and may be changed by SAP at any time without notice. Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. BusinessObjects.© 2011 SAP AG. and MultiWin are trademarks or registered trademarks of Citrix Systems. fitness for a particular purpose. special. Massachusetts Institute of Technology. and other countries. RETAIN. 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. text. xSeries. System p5. System z. National product specifications may vary. developments. The statutory liability for personal injury and defective products is not affected. System z10. POWER. z10. SAP shall have no liability for damages of any kind including without limitation direct. Parallel Sysplex. OS/390. R/3. Xcelsius. HACMP. SQL Anywhere. ICA. © 2011 SAP AG. JavaScript is a registered trademark of Sun Microsystems. and Motif are registered trademarks of the Open Group. IBM. SAP assumes no responsibility for errors or omissions in this document. ByDesign. 14 . S/390. and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. iSeries. Acrobat. Adobe. Data contained in this document serves informational purposes only. BladeCenter. Java is a registered trademark of Sun Microsystems. i5/OS. z/OS. links. This document contains only intended strategies. Citrix. Inc. SAP. No part of this document may be reproduced. Intelligent Miner. z/VM. UNIX. PowerVM. DB2 Universal Database. System i. The information in this document is proprietary to SAP. Sybase and Adaptive Server. Inc.. including but not limited to the implied warranties of merchantability. POWER5+. Redbooks. POWER6+. Crystal Reports. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Duet. DB2 Connect.