191 scen overview en xx

8/3/2019 191 Scen Overview en XX

http://slidepdf.com/reader/full/191-scen-overview-en-xx 1/8

Travel Management

SAP Best Practices



© 2011 SAP AG. All rights reserved. 2

Purpose, Benefits, and Key Process Steps

Purpose

To pr ovide fully integrated management of all incurred travel expenses.

Benefits

Record Travel Expenses

Key Process Steps

Create Trip and Enter Receipts

Appr ove and Settle Trip

Transfer Costs to Accounting




Required SAP Applications and Company Roles

Required SAP Applications

Enhancement package 5 f or SAP ERP 6.0

Company Roles

Employee

Travel Accountant




Detailed Process Description

Travel Management

Create Trip and Enter Receipts

Appr ove and Settle Trip

Transfer Costs to Accounting




Process Flow DiagramTravel Management

T r a v e l A c c o

u n t a n t

E v e n t

E m p l o y e e

TripApproved

?

Create Tripand Enter Receipts

TravelExpensesNeed to beManaged

Settle TripTransfer Coststo Accounting

EndProcess




Legend

Symbol Description Usage Comments

To next / Fr om 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 t askstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines

Financial Actuals: Indicates a

financial posting document

Does not correspond to a t ask

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

Budget Planning: Indicates abudget planning document

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

Manual Pr ocess: 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 tr uck in the

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

E x t e r n a l

t o

S A P

BusinessActivity / Event

Unit Process

ProcessReference

Sub-ProcessReference

ProcessDecision

DiagramConnection

Hardcopy /Document

FinancialActuals

BudgetPlanning

ManualProcess

ExistingVersion /Data

SystemPass/FailDecision

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

Flow line (dashed): Line indicates flow to

infrequently-used or conditional tasks in ascenario. Line can also lead to documents involved

in the process flow.

Connects two tasks ina scenario process or

a non-step event

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

Does not correspondto a task step in thedocument

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

Corresponds to a taskstep in the document

Pr ocess Reference: If the scenario references

another scenario in total, put the scenario number and name here.

Corresponds to a task

step in the document

Sub-Pr ocess Reference: If the scenario referencesanother scenario in part, put the scenario number,name, and the step numbers from that scenariohere

Corresponds to a taskstep in the document

Pr ocess 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 not usuallycorrespond to a taskstep in the document;Reflects a choice tobe made after stepexecution

< F u n c t i o n >




Appendix

Master Data Used

Trip

Personnel Number




No part of this publication may be repr oduced or transmitted in any f orm or f or any purposewithout the express permission of SAP AG. The inf ormation contained herein may bechanged without prior notice.

Some software pr oducts marketed by SAP AG and its distributors contain pr oprietarysoftware components of other software vendors.

Micr osoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Micr osoftCorporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,

Pow

erVM, Pow

er Architecture, POWER

6+, POWER

6, POWER

5+, POWER

5, POWER

,OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,RET AIN, DB2 Connect, R ACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Inf ormix are trademarks or registeredtrademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acr obat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Gr oup.

Citrix, IC A, Pr ogram Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W 3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Micr osystems, Inc.

JavaScript is a registered trademark of Sun Micr osystems, Inc., used under license f or technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, and other SAP pr oducts and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

© 2011 SAP AG. All rights reserved

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, W eb Intelligence, Xcelsius, and other Business Objects pr oducts and servicesmentioned herein as well as their respective logos are trademarks or registered trademarksof Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybasepr oducts and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other pr oduct and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves inf ormational purposes only. Nationalpr oduct specifications may vary.

The inf

ormati

on in this d

ocument is pr

oprietary t

oSAP. N

opart

of this d

ocument may berepr oduced, copied, or transmitted in any f orm or f or any purpose without the express prior

written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or anyother agreement with SAP. This document contains only intended strategies, developments,and functionalities of the SAP® pr oduct and is not intended to be binding upon SAP to anyparticular course of business, pr oduct strategy, and/or development. Please note that thisdocument is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility f or err ors or omissions in this document. SAP does notwarrant the accuracy or completeness of the inf ormation, text, graphics, links, or other itemscontained within this material. This document is pr ovided without a warranty of any kind,either express or implied, including but not limited to the implied warranties of merchantability, fitness f or a particular purpose, or non-infringement.

SAP shall have no liability f or damages of any kind including without limitation direct,special, indirect, or consequential damages that may result fr om the use of these materials.This limitation shall not apply in cases of intent or gr oss negligence.

The statutory liability f or personal injury and defective pr oducts is not affected. SAP has no contr ol over the inf ormation that you may access thr ough the use of hot links contained inthese materials and does not endorse your use of third-party Web pages nor pr ovide anywarranty whatsoever relating to third-party Web pages.

191 scen overview en xx

Documents