Sie sind auf Seite 1von 7

894: Budget Planning and Maintenance Cost Reporting with SAP NetWeaver BW

SAP Best Practices Utilities Package V1.603 (China)

SAP Best Practices

Scenario Overview 1
Purpose and Benefits
Purpose

The document is to provide general information on reporting with SAP NetWeaver Business Warehouse

Benefits

Provide you with reliable tools for creating individual application. Analyzes, integrates, and distributes timely information that support decisionmaking at all levels

Scenario Overview 2
SAP Applications Required

SAP ECC 6.0 EhP3 SAP NetWeaver BW

Company Roles Involved in Process Flows


Maintenance Manage Enterprise Controller Budget planning

BW reports covered

Maintenance Cost and Asset Values Maintenance Cost and Number of Order MTTR/MTBR Mean Time to Repair/Mean Time between Repair PM Notification Project Analysis Project Overview Projects Cost Budget planning

Scenario Overview 3
Detailed Report Usage
Maintenance Cost and Asset Values
This report will show the maintenance cost and related asset values and their proportion.

Maintenance Cost and Number of Order


This report will show the subtotal of maintenance costs and number of orders in a given month for the specific order types

MTTR/MTBR Mean Time to Repair/Mean Time between Repair


This report will show the mean time to repair and between repairs, by various characteristics.

PM Notification
This report will show the subtotal of maintenance costs and the number of orders in a given month for the specific order types.

Scenario Overview 3
Detailed Report Usage
Project System - Dates
This report will show the projects information base on the date

Project Overview This report will show project overview and focus on the cost control view Project Cost Analysis This report will analyze the cost of project system by WBS elements .

Scenario Overview 3
Budget Planning in BW
In SAP Netweaver BW MCB component, you can plan you budget of next year base on maintenance history cost. The budget also can be splitted to period and every elements, function location, etc.

Detail steps of Budge planning, The maintenance history for the plant has been uploaded into the BW system during installation of this scenario. Then you can create an annual budget proposal based on the actual cost of maintenance history. Here you enter budget data for each functional location that will be involved in the overhaul maintenance, afterwards, you can distribute the annual budget proposal to each period so that the management can check the period budget. If some equipment/functional location has no maintenance history and needs to have maintenance in the new budget, you can create budget data for these functional locations by using Ad hoc annual planning. After budget planning has been finished, you can check budget planning data using the report, and sends it to the manager for approval via SAP Office.

Legend
Symbol Description Usage Comments
Role band contains tasks common to that role.

Symbol

Description

Usage Comments

<Function>

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. External Events: Contains events that start or end the scenario, or influence the course of events in the scenario.

Diagram Connection

To next / From last Diagram: Leads to the next / previous page of the Diagram

Flow chart continues on the next / previous page

External to SAP

Hardcopy / Document

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

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

Financial Actuals: Indicates a financial posting document

Financial Actuals

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

Budget Planning: Indicates a budget planning document

Business Activity / 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

Budget Planning

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

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

Unit Process

Corresponds to a task step in the document

Manual Process: Covers a task that is manually done

Manual Proces s

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

Process Reference

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

Corresponds to a task step in the document

Existing Version / Data

Existing Version / Data: This block covers data that feeds in from an external process

SubProcess Reference

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

Corresponds to a task step in the document

Proces s Decisio n

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

System Pass/F ail Decisio n

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.