7/27/2019 110 Scen Overview en In

1/6

Free of Charge DeliverySAP Best Practices Baseline Package

(India)

SAP Best Practices

7/27/2019 110 Scen Overview en In

2/6

Scenario Overview 1

Purpose

This scenario describes the process of providing goods to a customer at no cost(Free of Charge Sales Order)

Benefits

System integrated Free of Charge sales order processing

Key processflows covered

Create sales order with free of charge items

Pick and ship items

Post goods issue

Purpose and Benefits:

7/27/2019 110 Scen Overview en In

3/6

Scenario Overview 2

Required

SAP ECC 6.0 EhP3

Company roles involved in process flows

Sales Administration

Warehouse Clerk

SAP Applications Required:

7/27/2019 110 Scen Overview en In

4/6

Scenario Overview 3

Free of Charge Delivery

A unique sales order type is created that is non-billing relevant. The

order is confirmed based on the availability of goods. A delivery is

then created; the goods are subsequently picked, confirmed, and

delivered to the customer.

Detailed Process Description:

7/27/2019 110 Scen Overview en In

5/6

Process Flow DiagramFree of Charge Delivery

Sales

Administration

WarehouseClerk

Event

Customer

Sales OrderEntry

Free of ChargeRequirement

Initiated

OrderConfirmation

InventoryFree of Charge

Delivery

DailyShipmentWorklist,

EnoughInventory

Delivery DueList

Pick List

Delivery Note

End Process

Goods Issue

Bill of Lading

Check Batches/Assign Serial

NumbersPicking

7/27/2019 110 Scen Overview en In

6/6

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