Overhaul Management - 886

Process Flow Diagram

Overhaul Management
Event

Investment Planning and Approval Year

Programs Budgeting
Project Financial Controller

Fiscal Year Change of Programs

Roll-Up Budgeting Procedure Procedure Close Old
Create/Change Planned Costs Overhaul Reporting Reporting
Program Approval Year
to the Overhaul Maintenance Planned Values Budget Values
Structure Maint. Program Program
Controlling Budget vs. Actual Costs
Plan Costs on (Reporting) Open New
Create/Change/
Display Projects Budget Approval Year
(Bottom-Up Distribution Repeat Run
Measures Planning)

Confirm
Network Close Project
Network Release Activities Open New
Scheduling Measures Approval Year

Assign WBS Create Close the

Maintenance

Element to Maint.Order Maint. Order

Functional Business View
Planner

and Assign to
Location WBS/Network

Settle the
Releasing the Maintenance
Maintenance Order
Order
Wareh
Clerk
ouse

Goods Issue to
Maintenance
Order

Technically
Tech.
Main.

Individual Time Complete a

Confirmation Maintenance
Order
Contro

Period End
ller

Settlement

2016 SAP SE or an SAP affiliate company. All rights reserved. 2

 Legend
Symbol Description Usage Symbol Description Usage Comments
Comments

Band: Identifies a user role, such as Accounts Role band To next / From last Diagram: Leads Flow chart continues on the next /
to the next / previous page of the previous page
<Function>

Payable Clerk or Sales Representative. This band contains tasks

Diagram
can also identify an organization unit or group, common to
Diagram
rather than a specific role. that role. 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
printed document, report, or form step in a document; instead, it is
Hardcopy / used to reflect a document
External Events: Contains events that start or end Document generated by a task step; this
External
to SAP

the scenario, or influence the course of events in shape does not have any outgoing
the scenario. flow lines

Connects two Financial Actuals: Indicates a Does not correspond to a task

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

Budget Planning: Indicates a Does not correspond to a task

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

Manual Process: Covers a task Does not generally correspond to

Unit Process: Identifies a task that is covered in a Corresponds to that is manually done a task step in a document;
step-by-step manner in the scenario a task step in Manual instead, it is used to reflect a task
the document Proces that is manually performed, such
Unit Process as unloading a truck in the
s warehouse, which affects the
process flow.

Process Reference: If the scenario references Corresponds to

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

2016 SAP SE or an SAP affiliate company. All rights reserved. 3

 2017 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

2014 SAP SE or an SAP affiliate company. All rights reserved. 4