Sales Returns with Quality

Management & with Configured

Materials
SAP Best Practices for
Fabricated Metals V1.603
(France)

SAP Best Practices

Scenario Overview - 1
Purpose and Benefits:
Purpose
This scenario describes sales order returns processing with quality management
inspection lots.

Benefits

System integrated processing of Customers Returns and Quality Management.

Key process flows covered

SAP 2008 / Page 2

Return Sales order creation which references to the original billing document for
the goods.

Print RMA document (Return Material Authorization)

Delivery creation

Quality inspection for returns (QM in Sales)

Quality Usage Decision

Release Returns to Billing

Create Billing Document

Scenario Overview - 2
SAP Applications Required:
Required

SAP ECC 6.0 EhP3

Company roles involved in process flows

SAP 2008 / Page 3

Sales Administration
Sales Billing
Quality Specialist
Warehouse Clerk
Accounts Receivables Manager
Sales Billing

Scenario Overview - 3
Detailed Process Description:

Sales Returns with Quality Management & with

Configured Materials
This scenario describes sales order returns processing with
quality management inspection lots. The process starts
with the creation of a return sales order, which references
to the original billing document for the goods. An RMA
(Return Material Authorization) document is printed, and
forwarded to the customer to be attached to the incoming
goods. The goods are shipped back, and a return delivery
is created with reference to the sales order that is
specified on the RMA. An inspection lot is created, and
the material undergoes a quality evaluation, resulting in a
usage decision. The goods are inspected and
subsequently either returned to stock, scrapped, or
returned to the vendor. A credit memo is created from the
billing run, and posted to the customers account.

SAP 2008 / Page 4

Process Flow Diagram Sales Returns with

Quality Management & with Configured
Materials

Sales
Administration

Event

Sales
Scheduling
Agreement
with
Configured
Materials (362)

Customer
Needs to
Return
Product

Return
Confirmation

RMA Product
Arrived at
Dock

Billing
Document

Warehouse
Clerk

Create Return
Order

Quality
Specialist

Create Return
Delivery

Accounts

Receivable

Create Usage
Decision

Inspect Goods
Receipt

Sales
Billing

Delete Billing
Block

Billing

RMA = Return Material Authorization, GR = Goods Receipt, QA = Quality Assurance

SAP 2008 / Page 5

(Optional)
Assign Serial
Number

Post Good
Receipt

Inspection
Lot

Process Flow Diagram Sales Returns with

Quality Management & with Configured
Materials

Sales
Administrati
on

Event

Sales
Scheduling
Agreement
with
Configured
Materials (362)

Inspection
Lot

Return
from
Custom
er?

Yes

Post Good
Receipt

No

Create Return
Delivery

Create a
Inspection Lot
Manually
Quality
Inspection

Quality Specialist

Record Results

Goods
are OK?

No

Defects
Recording

Usage Decision

Yes

Warehouse
Clerk

Usage Decision

SAP 2008 / Page 6

Move Material
to Unrestricted
Stock

Move Material
to Block Stock
& Scrap

Legend

<Function>

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.

Role band
contains tasks
common to that
role.

Symbol

Diagram
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

External
to SAP

External Events: Contains events that start or end the

scenario, or influence the course of events in the
scenario.

Business
Activity /
Event

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 two
tasks in a
scenario
process or a
non-step event

Business Activity / Event: Identifies an action that

either leads into or out of the scenario, or an outside
Process that happens during the scenario

Does not
correspond to a
task step in the
document

Unit Process: Identifies a task that is covered in a

step-by-step manner in the scenario

Corresponds to
a task step in
the document

Unit Process

Process
Reference

SubProcess
Reference

Proces
s
Decisio
n

SAP 2008 / Page 7

Process Reference: If the scenario references another

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

Sub-Process Reference: If the scenario references

another scenario in part, put the scenario number,
name, and the step numbers from that scenario here

Process Decision: Identifies a decision / branching

point, signifying a choice to be made by the end
user. Lines represent different choices emerging
from different parts of the diamond.

Financial
Actuals

Does not
usually
correspond to a
task step in the
document;
Reflects a
choice to be
made after step
execution

Usage Comments

To next / From last Diagram: Leads

to the next / previous page of the
Diagram

Flow chart continues on the next /

previous page

Hardcopy / Document: Identifies a

printed document, report, or form

Does not correspond to a task

step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any
outgoing flow lines

Financial Actuals: Indicates a

financial posting document

Does not correspond to a task

step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any
outgoing flow lines

Budget Planning: Indicates a

budget planning document

Does not correspond to a task

step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any
outgoing flow lines

Manual Process: Covers a task

that is manually done

Does not generally correspond to

a task step in a document;
instead, it is used to reflect a task
that is manually performed, such
as unloading a truck in the
warehouse, which affects the
process flow.

Existing Version / Data: This block

covers data that feeds in from an
external process

Does not generally correspond to

a task step in a document;
instead, this shape reflects data
coming from an external source;
this step does not have any
incoming flow lines

System Pass / Fail Decision: This

block covers an automatic
decision made by the software

Does not generally correspond to

a task step in the document;
instead it is used to reflect an
automatic decision by the system
that is made after a step has been
executed.

Budget
Planning

Manual
Proces
s

Corresponds to
a task step in
the document

Corresponds to
a task step in
the document

Description

Existing
Version /
Data

System
Pass/F
ail
Decisio
n