overview en cz

Upload: syed-aijlal-jillani

Post on 03-Apr-2018

217 views

Category:

Documents


0 download

TRANSCRIPT

  • 7/28/2019 Overview en CZ

    1/7

    Travel ManagementSAP Best Practices Baseline Package

    SAP Best Practices

  • 7/28/2019 Overview en CZ

    2/7

    Scenario Overview 1

    Purpose

    To provide fully integrated management of all incurred travel expenses

    Benefits

    Record Travel Expenses

    Key process flows covered Create Trip and Enter Receipts

    Approve and Settle Trip

    Transfer Costs to Accounting

    Purpose and Benefits:

  • 7/28/2019 Overview en CZ

    3/7

    Scenario Overview 2

    Required

    SAP EHP3 for SAP ERP 6.0 EhP3

    Company roles involved in process flows Employee

    Travel Accountant

    SAP Applications Required:

  • 7/28/2019 Overview en CZ

    4/7

    Scenario Overview 3

    Travel Management

    Create Trip and Enter Receipts

    Approve and Settle Trip

    Transfer Costs to Accounting

    Detailed Process Description:

  • 7/28/2019 Overview en CZ

    5/7

    Process Flow DiagramTravel Management

    TravelAcc

    ountant

    E

    vent

    Employee

    TripApprove

    d?

    Create Trip andEnter Receipts

    TravelExpensesNeed to beManaged

    Settle TripTransfer Coststo Accounting

    End Process

  • 7/28/2019 Overview en CZ

    6/7

    Legend

    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 twotasks in ascenario

    process 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 another

    scenario in total, put the scenario number and namehere.

    Corresponds to

    a 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 bemade after stepexecution

    Symbol Description Usage Comments

    To next / From last Diagram: Leads

    to 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; thisshape 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.

    External

    to

    SAP

    BusinessActivity /

    Event

    Unit Process

    ProcessReference

    Sub-Process

    Reference

    Process

    Decision

    DiagramConnection

    Hardcopy /Document

    FinancialActuals

    BudgetPlanning

    ManualProces

    s

    ExistingVersion /

    Data

    SystemPass/F

    ailDecisio

    n

  • 7/28/2019 Overview en CZ

    7/7

    Appendix

    Trip

    Personnel Number

    Master Data Used