5/28/2018 932_E

1/18

Investment Management in PMSAP Best Practices for Chemicals (Germany)

SAP Best Practices

5/28/2018 932_E

2/18

SAP 2008 / Page 2

Purpose

The purpose of to describe business processes related to InvestmentManagement within Plant Maintenance.

Purpose and Benefits:

Scenario Overview

5/28/2018 932_E

3/18

SAP 2008 / Page 3

Required SAP EHP3 for SAP ERP 6.0

Company roles involved in process flows Plant Maintenance Specialist

SAP Applications Required:

Scenario Overview

5/28/2018 932_E

4/18

SAP 2008 / Page 4

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 youcapitalize 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).

5/28/2018 932_E

5/18

SAP 2008 / Page 5

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, Controllingand Plant Maintenance

5/28/2018 932_E

6/18

SAP 2008 / Page 6

The Asset Life-Cycle

Operating

Production

Maintenance

Quality assurance

Research &Development

Asset

retirement

Decision forInvestment

Construction

Projection

Procurement

process

BuildingAssembling

EAM

5/28/2018 932_E

7/18

SAP 2008 / Page 7

General Program structure

Shows the structure of

the enterprise

Based on technical

structure

5/28/2018 932_E

8/18

SAP 2008 / Page 8

Integration IM/PS and PM

Investment program

Projects

Work

order

Maintenance program

Projects

Work

order

5/28/2018 932_E

9/18

SAP 2008 / Page 9

Invest Program Structure

5/28/2018 932_E

10/18 SAP 2008 / Page 10

Maintenance Program Structure

5/28/2018 932_E

11/18 SAP 2008 / Page 11

Budgeting Maintenance

IM-Program

position

Work order

Budget

Budget

Planned

Values Actual Costs

Active availability

check

Aggregationassignments by

Functional

location

5/28/2018 932_E

12/18 SAP 2008 / Page 12

Process Cost planning

Cost planning based on:Objects - Count / Types

Scale of planned measures

Components and services

Estimation of unplanned measures

Budget

Actual

Compares Modifying

Costs:Workt

Components

other costs

Reporting

Adjustment

5/28/2018 932_E

13/18 SAP 2008 / Page 13

Example: Scenario Plant Maintenance

CH-MAINT

BP01

PRO

OP

Program:

Projects:

Pr 1.1

Pr 1

Pr 1.2 Pr 1.3

K1

PROD

K2 K3

Plan

Plan

Budget

Cost center

Ball system 1

BP01-PM-20

Plan

BP01

KMA

KMA1

Technical structure:

Work order

Cost centerWBS

Internal laborComponents

Settlementto cost centger

Ball system 2 Ball system 3

Operational Maintenance

5/28/2018 932_E

14/18 SAP 2008 / Page 14

Fiscal year changing

Program position 2006

Budget1000

Distrib.1000

Work order 1closed 300

Project X 600

Work order 2closed 100

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

2006

Program position 2007

Budget year before 600Budget new 3000

Whole 3600distributed

Project Y 1000

Work order 3 1000

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

2007

Project XBudget 600+ Addition 1000

Year changing

5/28/2018 932_E

15/18 SAP 2008 / Page 15

Reporting

Example: AvailabilityProgram 2006

Budget Act. Obligo Avail.

Roll-up

Budget Actual Obligo Avail.

Program position

assignedoperative Objects

Work order 1

Work order 2

Project X

Project Y

1300 800 200 300

100 20 - 80

200 180 50 -30

400 150 100 150

600 450 50 100

!

5/28/2018 932_E

16/18 SAP 2008 / Page 16

Scenario Overview

Measure

Budgeting

Measure

Structuring

Close of

Measure

Measure

Planning

Execution of

Measure

Release of

Measure

InvestmentManagement

Reports

Fiscal YearChanging of

Programs

Program

Budgeting

Program

Structuring

Program

Planning

(costs)

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

investment programs and maintenance programs

5/28/2018 932_E

17/18 SAP 2008 / Page 17

Project&Measure

PlantMaintenance

E

vent Planning and

BudgetingOld/new

Approval YearInvestmentPrograms

Release projectdefinition

Create / Change /Display Measures

InvestmentProgramStructure

Assign WBSElement to

Functional Location

Acco

unting

Plan Costs on

Projects

Investment

Program

Budget Investment

Program Budget Distribution

Release Measures

Assignment of CapitalInvestment

Projects/Maintenance Projectsto a Maintenance Order

Process Flow Diagram

5/28/2018 932_E

18/18

Legend

Symbol Description Usage Comments

To next / From last Diagram:Leadsto the next / previous page of theDiagram

Flow chart continues on the next /previous page

Hardcopy / Document: Identifies aprinted document, report, or form

Does not correspond to a taskstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines

Financial Actuals: Indicates afinancial posting document

Does not correspond to a taskstep in a document; instead, it isused to reflect a documentgenerated by a task step; this

shape does not have any outgoingflow lines

Budget Planning: Indicates abudget planning document

Does not correspond to a taskstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines

Manual Process: Covers a taskthat is manually done

Does not generally correspond toa task step in a document;instead, it is used to reflect a taskthat is manually performed, suchas unloading a truck in thewarehouse, which affects theprocess flow.

Existing Version / Data: This blockcovers data that feeds in from anexternal process

Does not generally correspond toa task step in a document;instead, this shape reflects datacoming from an external source;this step does not have anyincoming flow lines

System Pass / Fail Decision: Thisblock covers an automaticdecision made by the software

Does not generally correspond toa task step in the document;instead it is used to reflect anautomatic decision by the systemthat is made after a step has beenexecuted.

DiagramConnection

Hardcopy /Document

Financial

Actuals

BudgetPlanning

ManualProces

s

ExistingVersion /

Data

SystemPass/F

ailDecisio

n

Symbol Description Usage

Comments

Band: Identifies a user role, such as AccountsPayable Clerk or Sales Representative. This band

can also identify an organization unit or group,

rather than a specific role.

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.

Role bandcontains tasks

common to that

role.

External Events: Contains events that start or end the

scenario, or influence the course of events in the

scenario.

Flow line (solid):Line indicates the normal sequence

of steps and direction of flow in the scenario.

Flow line (dashed):Line indicates flow to infrequently-used or conditional tasks in a scenario. Line can

also lead to documents involved in the process flow.

Connects twotasks in ascenarioprocess or anon-step event

Business Activity / Event:Identifies an action thateither leads into or out of the scenario, or an outsideProcess that happens during the scenario

Does notcorrespond to atask step in thedocument

Unit Process: Identifies a task that is covered in astep-by-step manner in the scenario

Corresponds toa task step inthe document

Process Reference: If the scenario references anotherscenario in total, put the scenario number and namehere.

Corresponds toa task step inthe document

Sub-Process Reference: If the scenario referencesanother scenario in part, put the scenario number,name, and the step numbers from that scenario here

Corresponds toa task step inthe document

Process Decision: Identifies a decision / branchingpoint, signifying a choice to be made by the enduser. Lines represent different choices emergingfrom different parts of the diamond.

Does notusuallycorrespond to atask step in thedocument;Reflects achoice to be

made after stepexecution

External

toSAP

BusinessActivity /

Event

Unit Process

ProcessReference

Sub-Process

Reference

Process

Decision