milestone project

7/28/2019 Milestone Project

http://slidepdf.com/reader/full/milestone-project 1/7

Project with Milestone BillingSAP Best Practices for Services Industries(Germany)

SAP Best Practices



Scenario Overview – 1

Purpose

This business scenario addresses the typical business processes of an engineering or industrial design company.

Benefits

Project Management

Contract Management

Cross-Application Time Sheet

Milestone Billing according to performance of defined Milestones

Final Invoice

Key process flows covered

Creating a Project from a predefined template

Creating a Quotation (optional)

Creating a Customer Order

Time recording (CATS)

Report of Project Costs (planned/ actual)

Confirmation of Milestones

Creating Billing Document

Final Invoice and Technical closure of Project

Purpose and Benefits:




Required

SAP ECC 6.0 EhP3

Company roles involved in process flows

Sales Administration

Project Manager

Sales Billing

SAP Applications Required:




Project with Milestone Billing

This scenario addresses a consulting engagement in which project

management functionality is needed. The scenario starts with the creation of

the project by using a pre-defined project structure template. Then, the

project manager assigns the employees and defines the workload for each

project task. The project tasks are assigned to project phases which are

represented by WBS elements in the project template.

A sales order is created with reference to the created project by assigning the

top-level WBS element to the sales order. Optional the customer sales order

can be created with reference to the quotation.

After the employees involved in the project have carried out their work, they

record the hours worked and their trip costs in CATS. The recorded hours are

transferred to the project tasks. The Billing is done according to the

performance of milestones. Therefore each project phase has a Milestone

assigned which refers to the milestone billing in the sales order.

The final invoice shows the payments already made as well as the final

amount.

Detailed Process Description:



P r o j e c t M a n a g e r

Process Flow Diagram Project with Milestone Billing

S a l e s

A d m i n i s t r a t i o n

E

v e n t

S a l e s B i l l i n g

Create aQuotation(optional)

Purchaseorder

formalizingrequest for a

project isreceived

Create aCustomer

Order

Timerecording

CATS(211)

Create BillingDocument

Generate theSettlement Rule

Create Project

Report of project costs

(plan vs. actual)

Create finalInvoice

Confirmation of Milestones

Technicalclosure of

Project



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


Budget Planning: Indicates abudget planning document


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.

< F u n c t i o n >

E x t e r n a l

t o

S A P

BusinessActivity /

Event

Unit Process

ProcessReference

Sub-Process

Reference

Process

Decision

DiagramConnection

Hardcopy /Document

FinancialActuals

BudgetPlanning

ManualProces

s

ExistingVersion /

Data

SystemPass/F

ailDecisio

n



Appendix

Service Plant

Operating concern

Controlling area

Company code

Plant

Sales organization Distribution channel

Division

Contract type

Sold-to party

Material

Project template (std. WBS element and std. network) CATS Data entry profile

Personnel number

Master Data Used

milestone project

Documents