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
      

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

© SAP 2008 / Page 2

Scenario Overview - 2
SAP Applications Required:
Required

SAP ECC 6.0 EhP3 Sales Administration Sales Billing Quality Specialist Warehouse Clerk Accounts Receivables Manager Sales Billing

Company roles involved in process flows
     

© SAP 2008 / Page 3

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 Retur ns with Quality Management & with Configur ed Materials
t nev E
Sales Scheduling Agreement with Configured Materials (362) Customer Needs to Return Product Return Confirmation RMA Product Arrived at Dock Billing Document

es uoher a W se a S l kr e not art s n m A l Ci i i d

Create Return Order

Create Return Delivery

(Optional) Assign Serial Number

Post Good Receipt

Inspection Lot

Create Usage Decision

Inspect Goods Receipt

y il a u Q t t sl a ce p S i i

Delete Billing Block

se a S s nuocc A l t gnlli B e bav ece R i l i

Billing

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

© SAP 2008 / Page 5

Process Flow Diagram – Sales Retur ns with Quality Management & with Configur ed Materials
t nev E
Sales Scheduling Agreement with Configured Materials (362) Yes Return from Custom er? No

Inspection Lot

se a S l t art s n m A i i d no i

Post Good Receipt

Create Return Delivery

Create a Inspection Lot Manually Record Results Quality Inspection

Goods are OK?

No

Defects Recording

Usage Decision

t sl a ce p S y il a u Q i i t

Yes

Usage Decision

© SAP 2008 / Page 6

es uoher a W kr e C l

Move Material to Unrestricted Stock

Move Material to Block Stock & Scrap

Legend
Symbol Description Usage Comments Symbol Description Usage Comments

<Function>

Band: Identifies a user role, such as Accounts Payable Role band contains Clerk or Sales Representative. This band can also identifytasks common to an organization unit or group, rather than a specific role. that 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.

To next / From last Diagram: Leads to the next / previous page of the Diagram

Flow chart continues on the next / previous page

Diagram Connection

External Events: Contains events that start or end the scenario, or influence the course of events in the scenario.

Hardcopy / Document

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

l an e x E r t PAS o t

Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario. Flow line (dashed): Line indicates flow to infrequentlyused 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 nonstep event

Financial Actuals: Indicates a financial posting document

Financial Actuals

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

Business Activity / 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

Budget Planning: Indicates a budget planning document

Budget Planning

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

Unit Process: Identifies a task that is covered in a step-by- Corresponds to a step manner in the scenario task step in the document

Manual Process: Covers a task that is manually done

Unit Process

Manual Proces s
Process Reference: If the scenario references another scenario in total, put the scenario number and name here. Corresponds to a task step in the document

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.

Process Reference

SubProcess Reference

Sub-Process Reference: If the scenario references another Corresponds to a scenario in part, put the scenario number, name, and the task step in the step numbers from that scenario here document

Existing Version / Data

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

Proces s Decisio n

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.

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

System Pass/F ail Decisio n

System Pass / Fail Decision: This block Does not generally correspond to a covers an automatic decision made by task step in the document; instead it is the software used to reflect an automatic decision by the system that is made after a step has been executed.

© SAP 2008 / Page 7

Copyright 2008 SAP AG. All Rights Reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

© SAP 2008 / Page 8

Sign up to vote on this title
UsefulNot useful