sap bp scenario 932 overview

Investment Management in PM SAP Best Practices for Chemicals (Germany)

SAP Best Practices

© SAP 2008 /

Purpose The purpose of to describe business processes related to Investment

Management within Plant Maintenance.

Purpose and Benefits:

Scenario Overview

© SAP 2008 /

Required SAP EHP3 for SAP ERP 6.0

Company roles involved in process flows Plant Maintenance Specialist

SAP Applications Required:

Scenario Overview

© SAP 2008 /

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 /

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 /

The Asset Life-Cycle

OperatingOperatingProduction

Maintenance Quality assurance

Research & Development

Asset retirement

Decision for Investment

Construction Projection

Procurementprocess

Building Assembling

EAM

© SAP 2008 /

General Program structure

• Shows the structure of the enterprise• Based on technical structure

© SAP 2008 /

Integration IM/PS and PM

Investment program

Projects

Work order

Maintenance program

Projects

Work order

© SAP 2008 /

Invest Program Structure

© SAP 2008 /

Maintenance Program Structure

© SAP 2008 /

Budgeting Maintenance

IM-Program position

Distribu tion

Work order

Budget

Budget

Planned Values

Actual Costs

Active availability check

Aggregation

assignments by Functional location

© SAP 2008 /

Process Cost planning

Cost planning based on: • Objects - Count / Types • Scale of planned measures • Components and services• Estimation of unplanned measures

Budget

ActualCompares Modifying

Costs: • Workt • Components• other costs

Reporting

Adjustment

© SAP 2008 /

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

PlanBudget

Cost center

Ball system 1

BP01-PM-20

Plan

BP01

KMA

KMA1

Technical structure:

Work order

Cost center WBS

Internal laborComponents

Settlement to cost centger

Ball system 2

Ball system 3

Operational Maintenance

© SAP 2008 /

Fiscal year changing

Program position 2006Program position 2006BudgetBudget

10001000Distrib.Distrib.

10001000

Work order 1Work order 1closedclosed 300300

Project XProject X 600600

Work order 2Work order 2closedclosed 100100

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

2006

Program position 2007Program position 2007Budget year before Budget year before 600600Budget newBudget new 3000 3000

WholeWhole 36003600distributeddistributed

Project YProject Y 10001000

Work order 3Work order 3 10001000

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

2007

Project XProject XBudgetBudget 600600+ Addition+ Addition 10001000

Year changing

new

new

© SAP 2008 /

Reporting

Example: AvailabilityProgram 2006Program 2006

BudgetBudget Act. ObligoAct. Obligo Avail.Avail.

Roll-up

BudgetBudget ActualActual ObligoObligo Avail.Avail.

Program position

assignedassignedoperative Objectsoperative Objects

Work order 1Work order 1

Work order 2

Project XProject X

Project YProject Y

1300 800 200 300

100100 2020 -- 8080

200200 180180 5050 -30-30

400400 150150 100100 150150

600600 450450 5050 100100

!

© SAP 2008 /

Scenario Overview

Measure Budgeting

Measure Structuring

Close of Measure

Measure Planning

Execution of Measure

Release of Measure

Investment Management

Reports

Fiscal Year Changing of Programs

Program Budgeting

Program Structuring

Program Planning

(costs)

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

© SAP 2008 /

Pro

ject

& M

easu

reP

lant

Mai

nten

ance

E

vent Planning and

BudgetingOld/new

Approval YearInvestment Programs

Release project definition

Create / Change / Display Measures

Investment Program Structure

Assign WBS Element to

Functional Location

Acc

ount

ing

Plan Costs on Projects

Investment Program

Budget InvestmentProgram Budget Distribution

Release Measures

Assignment of Capital Investment

Projects/Maintenance Projects to a Maintenance Order

Process Flow Diagram

© SAP 2008 /

Legend

Symbol Description 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, report, or form

Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines

Financial Actuals: Indicates a financial posting document


Budget Planning: Indicates a budget planning document


Manual Process: Covers a task that is manually done

Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow.

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; instead, this shape reflects data coming from an external source; 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; instead it is used to reflect an automatic decision by the system that is made after a step has been executed.

Diagram Connection

Hardcopy / Document

Financial Actuals

Budget Planning

Manual Proces

s

Existing Version /

Data

System Pass/F

ail Decisio

n

Symbol Description Usage Comments

Band: Identifies a user role, such as Accounts Payable 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 band contains 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 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, 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

Process Reference: If the scenario references another scenario in total, put the scenario number and name here.


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


Process Decision: Identifies a decision / branching point, signifying a choice to be made by the end user. Lines represent different choices emerging from different parts of the diamond.

Does not usually correspond to a task step in the document; Reflects a choice to be made after step execution

<Fun

ctio

n>E

xter

nal t

o S

AP

Business Activity /

Event

Unit Process

Process Reference

Sub-Process

Reference

Process

Decision

sap bp scenario 932 overview

Documents