Quality Management: Goods Receipt

Inspection for Container Shipments

SAP Best Practices
Purpose, Benefits, and Key Process Steps

Purpose
Stock materials are placed in storage following a goods receipt. After the goods receipt
posting has been made for materials that require a quality inspection, an inspection log is
generated for quality inspections and the quantity is posted in the stock in quality inspection.
After a usage decision has been made, the quantity is posted to the corresponding stock (if
accepted, to the unrestricted-use stock, if rejected to the blocked stock).

© 2013 SAP AG. All rights reserved. 2

Purpose, Benefits, and Key Process Steps

Benefits
 Automatic inspection lot creation upon GR

 Activation of quality notification upon rejection

 Automatic return delivery creation

 Automatic inventory post with internal email as workflow

Key Process Steps

 Creating Purchase Order

 Posting Goods Receipt

 Quality Inspections (Inspection of Physical Samples )

 Quality Inspections (Inspection of Containers-Accept )

 Creating Invoice

 Quality Inspections (Inspection of Containers-Reject)

 Return to Vendor

© 2013 SAP AG. All rights reserved. 3

Required SAP Applications and Company Roles

Required SAP Applications

 Enhancement package 6 for SAP ERP 6.0

Company Roles
 Quality Specialist
 Purchaser
 Purchasing Manager
 Warehouse Clerk
 Accounts Payable Accountant

© 2013 SAP AG. All rights reserved. 4

Process Flow Diagram
Quality Management: Goods Receipt Inspection for Container Shipments
Purchase

Procurement Procurement
without without
r

QM(130) QM(130)

Quality Quality
Inspection(Ins Record Inspection(Ins
pection of Results
Physical pection of
Samples) Containers)
Quality Specialist

Goods
are OK?
No

Yes

Usage
Decision
Quality
Management for
Procurement
Move Material with Vendor
to Unrestricted Evaluation
(127)
Stock
Accountant
Accounts
Payable

Creating
Invoice

© 2013 SAP AG. All rights reserved. 5

 Legend

Symbol Description Usage Comments Symbol Description Usage Comments

Band: Identifies a user role, such as Accounts Role band contains To next / From last Diagram: Leads Flow chart continues on the next /
Payable Clerk or Sales Representative. This band tasks common to that to the next / previous page of the previous page
<Function>

can also identify an organization unit or group, role. Diagram

rather than a specific role. 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: Identifies a Does not correspond to a task
printed document, report, or form step in a document; instead, it is
External Events: Contains events that start or end used to reflect a document
Hardcopy /
the scenario, or influence the course of events in generated by a task step; this
nal to

Document
Exter
SAP

the scenario. shape does not have any

outgoing flow lines

Flow line (solid): Line indicates the normal Connects two tasks in
a scenario process or Financial Actuals: Indicates a Does not correspond to a task
sequence of steps and direction of flow in the a non-step event financial posting document step in a document; instead, it is
scenario. Financial used to reflect a document
Flow line (dashed): Line indicates flow to generated by a task step; this
Actuals shape does not have any
infrequently-used or conditional tasks in a outgoing flow lines
scenario. Line can also lead to documents
involved in the process flow.

Business Activity / Event: Identifies an action that Does not correspond Budget Planning: Indicates a Does not correspond to a task
either leads into or out of the scenario, or an to a task step in the budget planning document step in a document; instead, it is
Business outside Process that happens during the scenario document used to reflect a document
Activity / Event Budget generated by a task step; this
Planning shape does not have any
outgoing flow lines
Unit Process: Identifies a task that is covered in a Corresponds to a task
step-by-step manner in the scenario step in the document
Unit Process Manual Process: Covers a task Does not generally correspond to
that is manually done a task step in a document;
instead, it is used to reflect a task
Manual that is manually performed, such
Process Reference: If the scenario references Corresponds to a task Process as unloading a truck in the
another scenario in total, put the scenario number step in the document warehouse, which affects the
Process and name here. process flow.
Reference

Existing Version / Data: This block Does not generally correspond to

Sub-Process Reference: If the scenario references Corresponds to a task covers data that feeds in from an a task step in a document;
another scenario in part, put the scenario number, step in the document external process instead, this shape reflects data
Sub- name, and the step numbers from that scenario Existing coming from an external source;
Process here Version / this step does not have any
Reference Data incoming flow lines

Process Decision: Identifies a decision / branching Does not usually

point, signifying a choice to be made by the end correspond to a task System Pass / Fail Decision: This Does not generally correspond to
user. Lines represent different choices emerging step in the document; block covers an automatic a task step in the document;
from different parts of the diamond. Reflects a choice to decision made by the software instead it is used to reflect an
Process System automatic decision by the system
Decision be made after step Pass/Fail
execution Decision that is made after a step has been
executed.

© 2013 SAP AG. All rights reserved. 6

© 2013 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.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or
warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing
herein should be construed as constituting an additional warranty.

SAP 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 other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

© 2013 SAP AG. All rights reserved. 7