You are on page 1of 19

Investment Management in PM

SAP Best Practices for Chemicals (Germany)

SAP Best Practices


Scenario Overview

Purpose and Benefits:

Purpose
 The purpose of to describe business processes related to Investment
Management within Plant Maintenance.

© SAP 2008 / Page 2


Scenario Overview

SAP Applications Required:


Required
 SAP EHP3 for SAP ERP 6.0

Company roles involved in process flows


 Plant Maintenance Specialist

© SAP 2008 / Page 3


Overview

The Investment Management (IM) component provides functions to support


the planning, investment, and financing processes for:

•Capital investments, 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, such as continuing education of


employees or establishing new markets

• Maintenance programs

The term investment, therefore, is not limited only to investments you


capitalize for bookkeeping or tax purposes. An investment in this context can
be any measure that initially causes costs, and that may only generate
revenue or provide other benefits after a certain time period has elapsed (for
example, plant maintenance).

© SAP 2008 / Page 4


Features

Application module IM (Investment Management)

Application module PS (Project System)

Module IM for overall planning, budgeting and controlling of


Investment projects, Maintenance projects and operational
maintenance activities

Module PS as planning and controlling tool for individual measures

Maintenance work orders as cost collector for handling of operational


and project-related activities

Fully integrated process of Financials, Asset-Accounting, Controlling


and Plant Maintenance

© SAP 2008 / Page 5


The Asset Life-Cycle

Construction Procurement
Projection process

Decision for Building


Investment Assembling

EAM

Research &
Development Operating
Production
Asset Maintenance
retirement Quality assurance

© SAP 2008 / Page 6


General Program structure

•Shows the structure of


the enterprise
•Based on technical
structure
© SAP 2008 / Page 7
Integration IM/PS and PM

Investment program Maintenance program

Projects Projects

Work Work
order order

© SAP 2008 / Page 8


Invest Program Structure

© SAP 2008 / Page 9


Maintenance Program Structure

© SAP 2008 / Page 10


Budgeting Maintenance

Budget
Budget
IM-Program Aggregation
position
assignments by
Functional
location
Planned Actual Costs
Distribution Values
Work order

Active availability
check

Budget
Budget

© SAP 2008 / Page 11


Process Cost planning

Cost planning based on:


• Objects - Count / Types
Adjustment
• Scale of planned measures
• Components and services
• Estimation of unplanned measures

Budget Reporting
Compares Modifying
Actual
Costs:
• Workt
• Components
• other costs

© SAP 2008 / Page 12


Example: Scenario Plant Maintenance

Program: CH-MAINT Technical structure: BP01

KMA
BP01
KMA1

PRO
Cost center
WBS
Work order

OP
Plan Plan
Components
Budget Internal labor
:
Projects Pr 1 BP01-PM-20
Operational Maintenance

Pr 1.1 Pr 1.2 Pr 1.3 Ball system Ball system Ball system


1 2 3

Plan Settlement
to cost centger
Cost center K1 K2 K3

PROD

© SAP 2008 / Page 13


Fiscal year changing

J F M A M J J A S O N D J F M A M J J A S O N D

2006 2007

Program position 2006 Program position 2007


Budget Distrib. Budget year before 600
1000 1000 Year changing Budget new 3000
Whole 3600
distributed
Project X
Project X 600
Budget 600
Work order 1 + Addition 1000
closed 300
w
ne Project Y 1000
Work order 2
closed 100 w
ne Work order 3 1000

© SAP 2008 / Page 14


Reporting

Program 2006
Example: Availability Budget Act. Obligo Avail.
Roll-up

Budget Actual Obligo Avail.


Program position 1300 800 200 300

assigned
operative Objects
Work order 1 100 20 - 80
Work order 2 200 180 50 -30 !
Project X 400 150 100 150
Project Y 600 450 50 100

© SAP 2008 / Page 15


Scenario Overview

Business Requirement: Support planning, investment, and financing processes for


investment programs and maintenance programs

Program
Program Planning Program
Structuring Budgeting
(costs)

Measure Measure Measure Release of Execution of Close of


Structuring Planning Budgeting Measure Measure Measure

Investment Fiscal Year


Management Changing of
Reports Programs

© SAP 2008 / Page 16


Process Flow Diagram

Investment Planning and Old/new


Programs Budgeting Approval Year
t nev E

Release project Investment Create / Change /


Program Release Measures
definition Structure Display Measures
er us ae M &t c ej or P

Assignment of Capital
Assign WBS Investment
Element to Projects/Maintenance Projects
Functional Location to a Maintenance Order
ec nanet ni a Mt nal P

Plan Costs on Investment Budget Investment Budget Distribution


Projects Program Program
gni t nuocc A

© SAP 2008 / Page 17


Legend

Symbol Description Usage Comments Symbol Description Usage Comments

Band: Identifies a user role, such as Accounts Payable Role band contains To next / From last Diagram: Leads to Flow chart continues on the next /
Clerk or Sales Representative. This band can also tasks common to the next / previous page of the previous page
Diagram
identify an organization unit or group, rather than a that role.
<Function>

specific role. Diagram


Connection
The other process flow symbols in this table go into
these rows. You have as many rows as required to cover
all of the roles in the scenario.
Hardcopy / Document: Identifies a Does not correspond to a task step in
printed document, report, or form a document; instead, it is used to
Hardcopy / reflect a document generated by a task
External Events: Contains events that start or end the step; this shape does not have any
scenario, or influence the course of events in the Document outgoing flow lines
scenario.
l anr et x E
PAS ot

Financial Actuals: Indicates a financial Does not correspond to a task step in


Flow line (solid): Line indicates the normal sequence of Connects two tasks posting document a document; instead, it is used to
steps and direction of flow in the scenario. in a scenario reflect a document generated by a task
Flow line (dashed): Line indicates flow to infrequently- process or a non- Financial step; this shape does not have any
step event Actuals outgoing flow lines
used or conditional tasks in a scenario. Line can also
lead to documents involved in the process flow.

Business Activity / Event: Identifies an action that either Does not Budget Planning: Indicates a budget Does not correspond to a task step in
leads into or out of the scenario, or an outside Process correspond to a task planning document a document; instead, it is used to
that happens during the scenario step in the reflect a document generated by a task
Business document Budget step; this shape does not have any
Activity / outgoing flow lines
Planning
Event

Unit Process: Identifies a task that is covered in a step-by- Corresponds to a


step manner in the scenario task step in the Manual Process: Covers a task that is Does not generally correspond to a
document manually done task step in a document; instead, it is
used to reflect a task that is manually
Unit Process Manual performed, such as unloading a truck
Proces in the warehouse, which affects the
s process flow.

Process Reference: If the scenario references another Corresponds to a


scenario in total, put the scenario number and name task step in the
here. document
Process Existing Version / Data: This block Does not generally correspond to a
Reference covers data that feeds in from an task step in a document; instead, this
external process shape reflects data coming from an
Existing external source; this step does not
Version / have any incoming flow lines
Sub-Process Reference: If the scenario references another Corresponds to a Data
scenario in part, put the scenario number, name, and the task step in the
step numbers from that scenario here document
Sub-
Process System Pass / Fail Decision: This block Does not generally correspond to a
Reference covers an automatic decision made by task step in the document; instead it is
System the software used to reflect an automatic decision
Pass/F by the system that is made after a step
Process Decision: Identifies a decision / branching point, Does not usually ail has been executed.
signifying a choice to be made by the end user. Lines correspond to a task Decisio
represent different choices emerging from different parts step in the
of the diamond. document; Reflects n
Proces a choice to be made
s after step execution
Decisio
n

© SAP 2008 / Page 18


Copyright 2008 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.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge 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 in several other countries all over the world. All other product and service names
mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National
product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This
document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of
business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness
of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied,
including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials.
This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. 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.

© SAP 2008 / Page 19