Customer Returns QI
Customer Returns QI
Customer Returns QI
Copyright
© Copyright 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.
Typographic Conventions
Type Style Description
Example text Words or characters quoted from the screen. These include field names, screen
titles, pushbuttons labels, menu names, menu paths, and menu options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, graphic titles, and table titles.
EXAMPLE TEXT Technical names of system objects. These include report names, program
names, transaction codes, table names, and key concepts of a programming
language when they are surrounded by body text, for example, SELECT and
INCLUDE.
Example text Output on the screen. This includes file and directory names and their paths,
messages, names of variables and parameters, source text, and names of
installation, upgrade and database tools.
Example text Exact user entry. These are words or characters that you enter in the system
exactly as they appear in the documentation.
<Example text> Variable user entry. Angle brackets indicate that you replace these words and
characters with appropriate entries to make entries in the system.
EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.
Solution Manager Content for Customer Returns with Quality Inspection ................................ 5
1 Customer Returns with Quality Inspection .......................................................................... 5
2 Configuration of Customer Returns with Quality Inspection ............................................... 9
2.1 Configuration of Returns Order Creation in SAP ERP ............................................... 12
2.1.1 Configuring Copy Control for Returns Orders in SAP ERP ................................. 13
2.1.2 Configuring Tax Calculation for Returns Orders in SAP ERP ............................. 14
2.1.3 Configuring Allowed Sales Areas for Sales Document Types in SAP ERP ........ 14
2.1.4 Configuring Document Types for Returns Deliveries in SAP ERP ...................... 16
2.2 Configuration of Returns Delivery Creation................................................................ 16
2.2.1 Checking Document Types and Item Types........................................................ 17
2.2.2 Checking Determination of Document Types and Item Types ............................ 18
2.2.3 Checking Determination of Date Types ............................................................... 20
2.2.4 Checking Determination of Warehouse Process Types ...................................... 22
2.2.5 Configuring Determination of Staging Areas, Doors, and Goods Movement Bins
...................................................................................................................................... 22
2.3 Checking Handling Unit Creation ............................................................................... 24
2.4 Check of Warehouse Order Creation ......................................................................... 25
2.4.1 Checking Warehouse Process Types ................................................................. 26
2.4.2 Checking Activity Areas for Putaway ................................................................... 27
2.4.3 Checking Determination of Destination Bins for Putaway and Scrapping ........... 28
2.4.4 Checking Warehouse Order Creation Rules ....................................................... 30
2.5 Configuring Printing of Warehouse Orders ................................................................ 31
2.6 Configuration of Quality Inspection ............................................................................ 33
2.6.1 Checking Work Centers for Quality Inspection .................................................... 33
2.6.2 Configuring Quality Inspection Basics ................................................................. 34
2.6.3 Checking Settings for Inspection Rules ............................................................... 35
2.6.4 Checking Quality Inspection Results ................................................................... 38
2.6.5 Checking ERP Version Control for Communication of Quality Inspection Results
to SAP ERP .................................................................................................................. 40
2.6.6 Checking Quality Inspection in the Warehouse ................................................... 41
2.6.7 Configuring Quality Inspection Rules .................................................................. 41
2.7 Checking Exception Handling .................................................................................... 42
2.8 Scheduling Background Jobs for Posting Goods Issues ........................................... 43
3 Test Case for Customer Returns with Quality Inspection ................................................. 44
You use this business process to handle customer returns. In this process, only small
quantities (for example, single pieces) are returned. When you receive the rejected goods,
you perform a 100% inspection. The quality inspection is triggered and carried out in SAP
Extended Warehouse Management (SAP EWM). Depending on the inspection result, you
decide if the goods are put away or scrapped.
The following figure illustrates the correlation between the physical process and the manual or
automatic activities in the system:
By phone, a customer informs a sales clerk about a coming return and requests an identifier
for it. The sales clerk creates a returns delivery and communicates the number to the
customer. The customer labels the goods with the delivery number and returns them. A truck
arrives with the rejected goods. When the goods are unloaded, a goods receipt (GR) office
clerk posts the GR. A quality inspection (QI) document is created automatically. A warehouse
worker brings the rejected goods to the QI work center. A QI specialist checks the goods. He
or she packs undamaged goods into cartons and puts damaged goods into a wire basket. He
or she also enters the decision codes in the system. According to the decision codes, the
system creates warehouse orders (WOs) for moving the goods to the putaway bins or to the
scrapping zone. The putaway WOs are printed automatically. The QI specialist attaches the
printouts to the corresponding cartons. The warehouse worker brings the cartons with the
undamaged goods to the final bins and passes the printouts to the internal office. A
warehouse clerk confirms the WOs in the system. The WOs for moving the damaged goods
to the scrapping zone are confirmed automatically. The warehouse worker brings the wire
basket with the damaged goods to the scrapping zone as soon as the wire basket is full. A
background job runs regularly to empty the scrapping zone.
Unauthorized returns
Prerequisites
Billing documents for outbound deliveries exist in SAP ERP.
For more information about the configuration prerequisites, see Configuration of Customer
Returns with Quality Inspection [Page 9].
Process
The business process runs in SAP ERP and EWM as follows:
By phone, a customer informs a sales clerk about a coming return and requests an
identifier for it. The sales clerk creates a returns order in SAP ERP with reference to
the invoice for the previously delivered goods. The system creates a returns delivery
automatically and sends it to EWM. During the creation of the returns delivery in
EWM, the system automatically assigns the door designated for returns. The sales
clerk communicates the returns delivery number as the identifier to the customer. The
customer writes the returns delivery number on the delivery notes and the packages
with the rejected goods, and sends the rejected goods back.
The truck with the rejected goods arrives at the checkpoint and the truck driver brings
the delivery note to a checkpoint clerk. With the help of the returns delivery number
listed on the delivery note, the checkpoint clerk finds the corresponding returns
delivery in EWM and informs the truck driver about the door for unloading the rejected
goods. The truck driver leaves the checkpoint and drives the truck to that door.
A warehouse worker unloads the truck. The truck driver hands over the delivery note
to a warehouse clerk. The warehouse clerk checks the information on the packages,
including the rejected goods, against the delivery note, and writes differences on the
delivery note. The warehouse clerk takes the revised delivery note to the GR office.
A GR office clerk adapts the returns delivery according to the revised delivery note.
If there is a quantity deviation or a missing product, the GR office clerk adjusts the
quantity in the system with an appropriate process code. If an additional product has
been returned, the GR office clerk initiates the creation of a new returns order for the
additional product by the sales office.
The GR office clerk creates one handling unit (HU) for the returns delivery with the
returns delivery number as an external number. If an additional returns delivery is
created as an additional product arrives, the GR office clerk packs that returns
delivery into the same HU as the original returns delivery.
Finally, the GR office clerk posts the GR. The system finds a QI rule for the delivery
item type and creates inspection documents. The system posts the GR directly to the
QI zone with reference to the QI documents. The system sends the GR to SAP ERP.
The warehouse worker brings the rejected goods from the staging area to the QI
zone.
At the QI work center, a QI specialist finds all items that belong to the returns delivery
with the help of the external HU number. He or she checks the goods. He or she puts
damaged goods into a wire basket and undamaged goods into cartons so that each
carton contains only a single product.
The QI specialist enters the decision code (Accept or Reject) in the system using a
desktop transaction. The system proposes the putaway follow-up action for goods
rated as undamaged, and scrapping for goods rated as damaged. If the physical
quantity differs from the returns delivery quantity, the QI specialist enters an
exception code to adjust the returns delivery item quantity.
After saving the check results, the system automatically creates WOs for moving the
goods to the putaway bins or to the scrapping zone. The system confirms the WOs
for moving the damaged goods to the scrapping zone immediately. The WOs for
putting away the undamaged goods contain a single warehouse task (WT) for each
WO. The WOs for putaway are printed automatically. The QI specialist puts the
printout of the putaway WO in the carton with the corresponding product.
The warehouse clerk in the internal office monitors the open putaway WOs and
instructs the warehouse worker to work on these WOs as soon as a certain workload
is reached. The warehouse worker brings the cartons with undamaged goods to the
final putaway bin listed on the printouts. Afterwards he or she brings the printouts
back to the internal office. The warehouse clerk confirms the WOs in the system.
9. Move the goods to the scrapping zone and empty the scrapping zone (EWM)
If the wire basket with the damaged goods is full, a warehouse worker moves it to the
scrapping zone and puts the goods into the container designated for scrapping. In
this step, no interaction with the system is necessary. A background job runs
regularly to empty the scrapping zone in the system. The system sends the goods
issue to SAP ERP.
Process Monitoring
In this business process, you can use the following monitoring functions:
Warehouse Order .
More Information
For more information about how to run this business process in the system, see Test Case for
Customer Returns with Quality Inspection [Page 44].
For more information about the functions used in this business process, see SAP Library for
SAP Extended Warehouse Management on SAP Help Portal at http://help.sap.com/ewm.
You use this process to configure the business process Customer Returns with Quality
Inspection [Page 5].
You can use this configuration process in the following warehouses in SAP Extended
Warehouse Management (EWM):
This is the recommended way of getting started with EWM. For more information, see
the business scenario Warehouse Management with Preconfigured Processes
[External].
To set up the preconfigured business processes in standard warehouse W001, implement all
configuration steps except the steps marked with Optional. These steps help you to
understand the configuration of the processes but do not require a manual activity.
To configure the processes in your own warehouse, implement all configuration steps. In the
steps marked with Optional, check if you need to adapt the existing entries to your own
warehouse and carry out changes as needed.
All configuration steps require activities in EWM unless the documentation explicitly tells you
to carry out an activity in SAP ERP.
Prerequisites
For more information, see Configuration of Warehouse Management with Preconfigured
Processes [External].
Process
1. Configuration of Returns Order Creation in SAP ERP [Page 12]
Result
You have configured the business process Customer Returns with Quality Inspection. In
warehouse number W001, you can run the business process as described in the Test Case
for Customer Returns with Quality Inspection [Page 44].
Example
You configure this business process in warehouse W001 using the following data (see
Configuration of Warehouse Structure and Master Data for SAP EWM [External]):
Warehouse Structure
Storage Type Description
Door Explanation
Master Data
Customer Description
Product Description
D1 Dummy HU
DUMMY_HU Dummy HU
Printer Explanation
PR02 Printer located at the quality inspection work center (storage type T820)
Process-Specific Settings
Warehouse Process Description
Type
You use this procedure to configure how the system creates returns orders with reference to
billing documents in SAP ERP, as well as how it automatically creates outbound deliveries.
Prerequisites
In SAP ERP, you have the standard ERP Customizing available.
Process
1. Configuring Copy Control for Returns Orders in SAP ERP [Page 13]
2. Configuring Tax Calculation for Returns Orders in SAP ERP [Page 14]
3. Configuring Allowed Sales Areas for Sales Document Types in SAP ERP [Page 14]
4. Configuring Document Types for Returns Deliveries in SAP ERP [Page 16]
Example
You create a returns order with document type RE based on a billing document with document
type F2 in SAP ERP. A returns delivery is automatically created with document type LR.
You use this procedure to configure how the system creates returns orders based on billing
documents. You configure the copy control for returns order creation with reference to a
billing document with billing document type F2.
Procedure
1. In Customizing for Sales and Distribution, choose Sales Maintain Copy Control
for Sales Documents .
2. In the dialog structure, choose activity Copying Control: Billing Document to Sales
Document and then Header.
4. In the dialog structure, choose Item and create the following entry:
More Information
For more information, see the Customizing documentation.
You use this procedure to configure a condition record for calculating the price including tax
during sales order creation.
Procedure
1. On the SAP Easy Access screen, choose Logistics Sales and Distribution
Master Data Conditions Select Using Condition Type Create .
DE 0 0 - - <Today's 9999- A0
Date> 12-31
Result
You have created a condition record for condition type MWST and for tax code A0 used for
price calculation during sales order creation in SAP ERP.
If you create a sales order in SAP ERP and you enter the amount without having a condition
record for condition type MWST, the system issues a pricing error.
You use this procedure to configure the sales area that is allowed for the sales document
type. You assign the order type RE to distribution channels 01 and 02 in sales organization
0001. If you then create a sales order with order type RE in SAP ERP, you can use
distribution channel 01 or 02 in sales organization 0001.
Procedure
1. In SAP ERP, combine the sales organizations as follows:
3. Change the entry for your sales organization, for example, 0001:
3. Change the entry for your sales organization, for example, 0001:
3. Change the entry for your sales organization, for example, 0001:
4. Assign the sales order types permitted for sales areas as follows:
2. Choose the activity Assign sales order types permitted for sales areas.
Result
You have assigned the order type RE to distribution channels 01 and 02 in sales organization
0001.
If you create a sales order with order type RE in SAP ERP, you can use distribution channel
01 or 02 in sales organization 0001.
You use this procedure to configure the document type for returns deliveries and to set up
automatic creation of a returns delivery in SAP ERP when a returns order is created.
Procedure
1. In SAP ERP, check the following entry in Customizing for Logistics Execution under
Shipping Deliveries Define Delivery Types :
LR X
2. Change the entry for document type RE in Customizing for Sales and Distribution
under Sales Sales Documents- Sales Document Header Define Sales
Document Types :
Result
You create a returns order in SAP ERP with sales document type RE. A returns delivery is
automatically created with document type LR.
More Information
For more information about delivery split configuration, see Activating Transaction Data
Transfer in ERP [External] in Integration of SAP ERP with SAP EWM [External].
You use this process to configure how the system creates returns deliveries.
Process
1. Checking Document Types and Item Types [Page 17] (Optional)
2. Checking Determination of Document Types and Item Types [Page 18] (Optional)
You can use this procedure to check the document type and item types for the following
documents:
Document in the inbound delivery process containing all relevant logistics data from
the initiator of the inbound delivery process (such as the shipping notification, delivery
note or purchase order, for example). The inbound delivery notification is used to
create an inbound delivery.
Inbound delivery:
Document that contains all data necessary for triggering and monitoring the complete
inbound delivery process. This process starts with the receipt of the goods in the yard
and ends with the handing over of the goods for final putaway, production, or
outbound delivery.
Procedure
1. Check the following entries in Customizing for Extended Warehouse Management
under Goods Receipt Process Inbound Delivery Manual Settings Define
Document Types for Inbound Delivery Process :
IRET IRET
IRET ITXT
DQE QM Inspection -
DCO Completion -
5.
6. For archiving purposes, the inbound delivery needs to have the status
value Completed for the status type DCO.
7. Status types DQE and DQP for the inbound deliveries are relevant for
quality inspection in Customer Returns with Quality Inspection.
8.
More Information
For more information, see SAP Library for SAP Extended Warehouse Management on SAP
Help Portal at http://help.sap.com/ewm under Delivery Processing Documents in Delivery
Processing .
You can use this procedure to check how the system determines the document types and
item types for returns deliveries.
Procedure
1. Check the following entry in Customizing for Extended Warehouse Management
under Interfaces ERP Integration Delivery Processing Define ERP Document
Types for Differentiation Attribute :
LR RETCU
LR IRET
If you use a delivery type other than LR, create the entries for your ERP
delivery type. This is the case, for example, if you want to start the process with a
sales order to be created in SAP ERP.
Document Type from Item Type from Document Mapping of ERP Item
ERP ERP Type Type
If you use a delivery type other than LR or different item types, create the
entries for your ERP delivery type and item types accordingly.
Result
You create a returns delivery with document type LR and item type REN in SAP ERP. The
inbound delivery is then created with document type IRET and item type IRET in SAP EWM.
More Information
For more information, see the following:
Business Add-In (BAdI) for the determination of the document and item type in
Customizing for Extended Warehouse Management under Business Add-Ins
If you want to define document types and item types that differ from those used for the
inbound delivery notification, see the following:
You can use this procedure to check the relevant date types for inbound delivery notifications
and inbound deliveries, and the configuration of the delivery date mapping from SAP ERP to
SAP Extended Warehouse Management (EWM).
Procedure
1. Check the following entries in Customizing for Extended Warehouse Management
under Goods Receipt Process Inbound Delivery Manual Settings Define
Document Types for Inbound Delivery Process :
For the item types ITXT (Text Inbound Delivery), no date profile is required
as these items are not relevant for warehouse activities and are intended as
information only.
EUNLD -
SUNLD -
TDELIVERY -
TDELIVERYF X
TINYARD -
5. Check the date/time types for each date profile mentioned above.
The mapping below is defined to set the planned delivery date to the date of
type TDELIVERY in the inbound delivery notification.
Result
You have checked that the planned delivery date from SAP ERP is mapped to the planned
delivery date in the inbound delivery notification.
More Information
For more information, see the following:
You can use this procedure to check how the system determines the warehouse process type
when inbound deliveries are created.
Procedure
1. Check the following entry in Customizing for Extended Warehouse Management
under Cross-Process Settings Warehouse Task Define Warehouse Process
Type :
(No
Special
Process)
Result
You create an inbound delivery with document type IRET. The warehouse process type P430
is then determined for the inbound delivery items in SAP Extended Warehouse Management
(EWM).
More Information
For more information, see the Business Add-In (BAdI) for determining the warehouse process
type in Customizing for Extended Warehouse Management under Business Add-Ins
(BAdIs) for Extended Warehouse Management Cross-Process Settings Delivery
Processing Determinations in Delivery BAdI: Determination of Warehouse Process Type
.
You use this procedure to configure the determination of staging areas, doors, and goods
movement bins when returns deliveries are created.
Procedure
1. Check the following entry for the storage type used as a staging area in Customizing
for Extended Warehouse Management under Master Data Define Storage Type
:
In the business process Customer Returns with Quality Inspection, the physical
move from the staging area to the quality work center is not modeled in the
system. The staging area used is already the quality work center. To allow this
setup, the storage type for quality inspection is configured with storage type role
I.
2. Create the following entries on the SAP Easy Access screen under Extended
Warehouse Management Settings Shipping and Receiving Staging Area and
Door Determination (Inbound) :
3. Check the following entries on the SAP Easy Access screen under Extended
Warehouse Management Settings Shipping and Receiving Access Sequence to
Staging Areas and Door Determination :
W001 I (Inbound) 1 X X
W001 I (Inbound) 2 X -
4.
5. The goods movement bin is set to the staging bay automatically. No additional
setup is necessary for Customer Returns with Quality Inspection.
o Staging bay
Since a storage bin is not assigned in the system to door DI01 and no source
storage bin is set in warehouse process type P430, the goods movement bin is
set to the staging bay.
Result
You create a returns delivery in SAP ERP with document type RE. The system creates a
returns delivery notification with document type IRET in SAP Extended Warehouse
Management (EWM). The system determines the warehouse process type P430 for the
returns delivery items. As a consequence, staging area QUAL-I01 and door DI01 are
determined for the returns delivery items when the returns delivery is created in EWM.
You can use this procedure to check how the system creates handling units (HU) before
goods receipt posting. This includes the packaging material to be used and the configuration
that the returns delivery item needs to be packed before goods receipt posting.
Procedure
1. Check the following entry in Customizing for Extended Warehouse Management
under SCM Basis Pack Handling Units Define HU Types :
HU Type Description
D1 Dummy HU
W001 D1 -
W001 PT03 -
5. Check the entry on the SAP Easy Access screen under Extended Warehouse
Management Master Data Product Maintain Product :
DUMMY_HU PT03 D1
Result
You have specified that the returns delivery items are packed into an HU with an external
number only. The HU type to be used is D1. Due to the settings in the storage type used for
the goods movement bin, it is not possible to post a goods receipt without packing the items.
More Information
For more information, see the following:
You can use this process to check how the system creates warehouse orders. This includes
the setup for the following:
Putaway warehouse tasks for moving the goods to storage type T051
To create a putaway warehouse task, you set up the putaway strategy to transfer the
goods into the section for small, midsize, and large parts in storage type T051. The
warehouse order creation rule is set up to ensure that warehouse orders contain
single warehouse tasks only.
For information about the printing of putaway warehouse orders, see Configuring
Printing of Warehouse Orders [Page 31].
To create scrapping warehouse tasks that are confirmed immediately, you set up
storage types and warehouse process types.
Process
1. Checking Warehouse Process Types [Page 26] (Optional)
3. Checking Determination of Destination Bins for Putaway and Scrapping [Page 28]
(Optional)
Result
You have checked the warehouse order creation for putaway and scrapping after quality
inspection.
You can use this procedure to check the configuration of the warehouse process types for the
putaway and the scrapping activities.
Procedure
1. Check the following entries in Customizing for Extended Warehouse Management
under Master Data Define Storage Type :
W001 T051 - X X 3 - Y - -
W001 T840 E - X 2 BB - S 4
In this step, you check the configuration for the destination storage types used in
Customer Returns with Quality Inspection. The storage type used during
scrapping after quality inspection is the destination storage type in the warehouse
process type. The storage type for the final putaway into a bin in storage type
T051 is not determined by the warehouse process type. For more information,
see Checking Determination of Destination Bins for Putaway and Scrapping
[Page 28].
The setting for the location-independent stock type specifies that a change to
blocked stock is posted when a warehouse task with a storage bin is confirmed.
The change specifies the storage type as the destination bin.
Warehouse Warehouse Description Warehouse Activity WOCR Confirm Propose Control Destination
Process Process Activity Immediately Confirmation f. HU- Storage
Type Category Area Pick Type
More Information
For more information, see the field helps.
You can use this procedure to check the activity areas for putaway and the sorting of the
storage bins in the activity areas for activity PTWY.
Procedure
1. Check the following entries in Customizing for Extended Warehouse Management
under Master Data Activity Areas Define Activity Area :
2. On the selection screen, enter the following data and choose Display:
The sorting is used to identify the destination bin for putaway (see Checking
Determination of Destination Bins for Putaway and Scrapping [Page 28]) and defines
the putaway path within one warehouse order.
More Information
For more information, see Checking Activity Areas and Activities [External] in Configuration of
Warehouse Structure and Master Data for SAP EWM [External].
You can use this procedure to check how the system determines the destination bins for
putaway.
You have already checked the determination of destination bins for scrapping. For
more information, see Checking Warehouse Process Types [Page 26].
Procedure
1. Check the following entry in Customizing for Extended Warehouse Management
under Goods Receipt Process Strategies Storage Type Search Define
Storage Type Search Sequence for Putaway :
You define a storage type search sequence to specify in which storage types the
system searches for possible destination storage bins when a warehouse order is
created.
Depending on the attributes (in this business process, the warehouse process
type), the system determines a storage type search sequence.
W001 0 X X
W001 1 X -
W001 2 - X
You define a storage section indicator so that during putaway, specific products
are put away into specific storage sections. The storage section indicator can be
assigned to products in the warehouse-specific product master data.
8. Check the following entries on the SAP Easy Access screen under Extended
Warehouse Management Master Data Product Maintain Warehouse Product :
Result
For the creation of putaway warehouse tasks with warehouse process type P430 as used in
Customer Returns with Quality Inspection, the destination bin is determined in storage type
T051 depending on the storage section indicators maintained in the product master data. For
example, the small part PROD-S02 with storage section indicator SI10 is put away into a
storage bin in storage section S001 of storage type T051. In case the stock for a given
product does not fit into one storage bin, the system uses several destination bins for the
putaway according to the sorting of the storage bins by activity PTWY. For more information,
see Checking Activity Areas for Putaway [Page 27].
You can use this procedure to check the warehouse order creation rule (WOCR) to group
warehouse tasks into warehouse orders and thus create optimum work packages for
putaway.. You set up a warehouse order creation rule to create a separate warehouse order
for each warehouse task to support paper-based putaway.
Procedure
1. Check the following entry in Customizing for Extended Warehouse Management
under Cross Process Settings Warehouse Order Define Limit Values for the
Size of a Warehouse Order :
Result
For warehouse tasks created with warehouse process type P430, the system determines the
warehouse order creation rule R005 depending on the warehouse process type only.
Warehouse orders created with warehouse order creation rule R005 consist of a single
warehouse task.
More Information
For more information, see the following:
SAP Library for SAP Extended Warehouse Management on SAP Help Portal at
http://sap.help.com/ewm under Warehouse Order Creation
You use this procedure to check how the automatic printing of putaway warehouse orders is
configured.
Procedure
1. Check the determination procedure as follows:
PWO PW 0001
1 1 0001
3. Check the following entry on the SAP Easy Access screen, choose Extended
Warehouse Management Work Scheduling Print Settings Maintain
Warehouse-Specific Printing Parameters :
W001 01 - X X X 1
You maintain warehouse-specific printing parameters such as the spool data for
grouping printing parameters (for example, the time of printing, printer, handling
of spool job after printing, text for the cover page, and so on). The spool data can
then be used to create condition records.
The condition record determines whether printing should take place. Once the system
has determined the need for a printout, the condition record forms the basis for
determining the printer, form, and spool data.
2. On the selection screen, enter application PWO, maintenance group PWO, and
choose Execute (F8).
The printer can be determined directly from the condition record (first
priority), the spool data (second priority), or the user defaults (third
priority).
5. For more information about any issues during printing, you can activate the
application log on the SAP Easy Access screen under Extended Warehouse
Management Work Scheduling Print Settings Activate Application Log .
More Information
For more information, see the following:
SAP Library for SAP Extended Warehouse Management on SAP Help Portal at
http://help.sap.com/ewm under Warehouse Order Creation Printing Warehouse
Orders and Warehouse Tasks
Process
1. Checking Work Centers for Quality Inspection [Page 33] (Optional)
More Information
For more information, see SAP Library for SAP Extended Warehouse Management on SAP
Help Portal at http://help.sap.com/ewm under Quality Management.
You can use this procedure to check how a work center for quality inspection is configured.
Procedure
1. Check the following entry in Customizing for Extended Warehouse Management
under Master Data Work Center Specify Work Center Layout :
2. Check the following entry for defining a storage type as a work center in Customizing
for Extended Warehouse Management under Master Data Define Storage Type
:
Result
You have checked the configuration of the work center for quality inspection, which you can
find on the SAP Easy Access screen under Extended Warehouse Management
Execution Quality Inspection and Count .
More Information
For more information, see Configuring Work Centers [External] in Configuration of Warehouse
Structure and Master Data for SAP EWM [External].
You use this procedure to make basic settings for quality inspection for customer returns. This
includes the following:
Procedure
1. In Customizing for Extended Warehouse Management under Cross-Process
Settings Quality Management Basics Generate Inspection Object Types Version
, select the entry for inspection object type 3 (Q-Inspection Returns Delivery) and
choose Generate New Version to generate version 1.
You can enter any value from the customer name space for the index
number, for example, Z.
Properties Position
DOCCAT 9
DOCID 10
DOCTYPE 5
ENTITLED 8
HUIDENT 7
ITEMTYPE 6
LGNUM 2
PARTYNO 4
PRODUCTID 3
VERSION 1
You can use this procedure to check how the main quality inspection objects are configured.
This includes the following:
Procedure
1. Check the following entry in Customizing for Extended Warehouse Management
under Cross-Process Settings Quality Management Settings for Inspection
Rules Define Number Ranges for Inspection Documents . In the activity, choose
Define Number Ranges.
03 003000000000 003999999999
SIOT3 03
03 003000000000 003999999999
3. Select the element type SITMCR, choose Properties in the dialog structure,
and check the following entries:
Property Selected
CHARG -
COO -
DOCCAT X
DOCID X
DOCTYPE X
ENTITLED X
HUIDENT X
ICATLOCN -
ITEMTYPE X
LGNUM X
PARTYNO X
PRODUCTID X
QGRP -
VERSION X
01 001000000000 009999999999
3. Select finding type SFTCR, choose Attributes in the dialog structure, and
check the following entries:
NUMB_EXT - -
NUMB_FIND X -
NUMB_INT - -
NUMB_UNITS - -
SYSTEMATIC - -
4. Choose Catalogs in the dialog structure and check the following entries:
5. Choose Catalog Filter in the dialog structure and check the following entry:
6. Select the catalog filter SCFCR, choose Values in the dialog structure, and
check the following entries:
/SCWM/DEFECT SFCR
/SCWM/EFFORT SFCR
You can use this procedure to check how quality inspection results are handled. This includes
the following:
The definition of decision code groups is also relevant for Configuring Quality Inspection
Rules [Page 41].
Procedure
1. Check the follow-up action as follows:
PTWY Putaway
SCRP Scrap
3. Select the follow-up action PTWY, choose Follow-Up Actions for Quality
Results in the dialog structure, and check the following entry:
5. Select the entry for follow-up action SCRP, choose Follow-Up Actions for
Quality Results in the dialog structure, and check the following entry:
6. Choose Code Group in the dialog structure and check the following entry:
7. Select the entry for follow-up action SDCCR, choose Assign Follow-Up Actions
in the dialog structure, and check the following entry:
Follow-Up Action
PTWY
SCRP
3. Choose Code Group in the dialog structure and check the following entry:
4. Select the code group SDCCR, choose Codes in the dialog structure, and
check the following entries:
SI Simple Check
CO Complex Check
3. Choose Defects in the dialog structure and check the following entries:
DA Damage
MF Malfunction
4. Choose Defect Group (Catalog Filter) in the dialog structure and check the
following entry:
5. Select the code group SFCR, choose Defect in the dialog structure, and check
the entries DA and MF.
6. Choose Efforts in the dialog structure and check the entries SI and CO.
You can use this procedure to check that quality inspection results are not reported to SAP
ERP.
Procedure
1. In Customizing for Extended Warehouse Management, choose Interfaces ERP
Integration General Settings Set Control Parameters for ERP Version Control .
2. Check that Quality Confirmation for Returns is set to 1 (Do Not Communicate
Inspection Results to SAP ERP) for the business system of your SAP ERP system.
More Information
If you have not configured version control to prevent the inspection results from being
communicated to SAP ERP, you need to make additional Customizing settings in SAP ERP
similar to the setup of SAP Extended Warehouse Management (EWM). For more information,
see Customizing for Logistics Execution:
You can use this procedure to activate and control the quality inspection in the warehouse.
Procedure
1. In Customizing for Extended Warehouse Management, choose Cross-Process
Settings Quality Management Basics Warehouse-Dependent Activation of
Inspection Object Type .
You use this procedure to create inspection rules. Inspection rules control whether and how
quality inspection takes place, for example, for which products. For this business process, you
set up a 100% inspection for all returns delivery items.
Procedure
1. On the SAP Easy Access screen, choose Extended Warehouse Management
Master Data Quality Management Maintain Inspection Rule .
2. Create an inspection rule for process Q-Inspection Returns in warehouse W001 with
the following data:
You can use this procedure to check the exception codes. Exceptions that might occur in this
business process are the following:
Procedure
1. Check the process code profile for returns delivery items in Customizing for Extended
Warehouse Management under Goods Receipt Process Inbound Delivery
Manual Settings Define Item Types for Inbound Delivery Process :
3. Select this entry, choose Process Codes in the dialog structure, and check
the following entries:
3. Check the process code for delivery rejection in Customizing for Extended
Warehouse Management under Cross-Process Settings Delivery Processing
Process Codes Define Process Codes :
Delivery Quantity)
4. Check the process code for quantity deviation during quality inspection in
Customizing for Extended Warehouse Management under Cross-Process Settings
Delivery Processing Process Codes Define Process Codes :
6.
7. To check the data, you need to select the exception code and navigate top-down
in the dialog structure.
8.
Result
You have checked the process codes I001 (Quantity Deviations During Quality Check) and
CR01 (Inbound Delivery Rejection). You have also checked the exception code DIFD used for
quantity deviations encountered during quality inspection.
You reject a complete returns delivery for which you do not want to post a goods receipt.
During the quality check, you also discover a quantity difference between the physically
returned products and the returns delivery item quantity. You report the difference during the
quality inspection decision in the work center by using exception code DIFD.
You can test the exception code setup in Customizing for Extended Warehouse Management
under Cross-Process Settings Exception Handling Test Configuration of Exception
Codes .
You use this procedure to schedule the report for posting the goods issue for scrapped
products.
The same procedure is carried out for the configuration of the business process
Unplanned Scrapping Due to Damaged Stock. It is enough to schedule this report
once.
Procedure
1. On the SAP Easy Access screen, choose Extended Warehouse Management
Execution Post Unplanned Goods Issue and create a variant with the following
data:
2. Schedule this transaction with the variant to run as a background job on a daily basis.
You can use this test case to run the business process Customer Returns with Quality
Inspection [Page 5] in warehouse number W001.
Prerequisites
This test case requires the following roles:
Sales clerk with authorization for creating and changing returns orders and returns
deliveries in SAP ERP
Background user with authorization to schedule and run various reports in the
background
On the SAP Easy Access screen for Logistics under Sales and Distribution Billing
Billing Document Process Billing Due List (transaction VF04), you have created a billing
document for an outbound delivery in SAP ERP. During the billing document creation, you
have entered the item price condition PR00 for the items.
Outbound Process Using Wave, Pick-HU, Packing, Staging, and Loading [External]
For more information, see the prerequisites of the business process Customer Returns with
Quality Inspection [Page 5].
Features
This test case uses the following transactions that you can find on the SAP Easy Access
screen for Logistics:
This test case uses the following transactions that you can find on the SAP Easy Access
screen for Extended Warehouse Management:
Activities
Step Step Step Input Data Expected Results
Description Processor
o Division: 01 Document
Type: IRET
3. Choose Create with Reference.
Item Type:
4. On the BillDoc tab, enter the IRET
billing document you have
created, for example, Warehouse
90000025. Process Type:
P430
5. Choose Copy.
Warehouse
6. Adjust the quantities and Door: DI01
remove items that you do not
want to return. Goods
Movement Bin:
QUAL-I01
8. Choose Save.
o Packaging material
DUMMY_HU with
packaging material
type PT03
8. Choose Save.
9. Go back.
8 Put away - - -
the goods
(EWM)
8.1 Move the Warehouse This step is carried out outside of the -
goods to the worker system.
final bin
9 Move the - - -
goods to the
scrapping
zone and
empty the
scrapping
zone
(EWM)
9.1 Move the Warehouse This step is carried out outside of the -
goods to the worker system.
scrapping
zone
9.2 Empty the Automatic 1. Start transaction /SCWM/ADGI. The goods issue is
scrapping step posted. The scrapping
zone scheduled 2. Enter the following data: zone is empty.
by
background o Warehouse Number:
user W001
o GI Process: SCRP
(Scrapping)