EHP5 for SAP ERP
6.0
December 2011
English
Return to Vendor (136)
Business Process Documentation
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Return to Vendor (136): BPD
Copyright
© 2011 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.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z,
System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,
OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+,
POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System
Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,
AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of
IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of
Adobe Systems Incorporated in the United States and/or other countries.
Oracle and Java are registered trademarks of Oracle.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork,
SAP HANA, 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.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions,
Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business
Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks of
Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data
contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. 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 AG
Page 2 of 21
SAP Best Practices
Return to Vendor (136): BPD
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
External Process
Business Process Alternative/Decision Choice
Typographic Conventions
Type Style
Description
Example text
Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
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. Pointed brackets indicate that you replace these
words and characters with appropriate entries.
© SAP AG
Page 3 of 21
SAP Best Practices
Return to Vendor (136): BPD
Contents
1
Purpose ................................................................................................................................... 5
2
Prerequisites............................................................................................................................ 5
2.1
Master Data and Organizational Data .............................................................................. 5
2.2
Business Conditions ......................................................................................................... 6
2.3
Roles ................................................................................................................................ 6
2.4
Preliminary Steps ............................................................................................................. 7
2.4.1
Return Reason “02 Quality test failed (to blocked stock)” ........................................ 7
2.4.2
Return Reason “Wrong material delivered” .............................................................. 7
2.4.3
Return Reason “Delivered quantity too high”............................................................ 7
2.4.4
Return Reason “Wrong Trading Good in sales order” ............................................. 8
3
Process Overview Table ......................................................................................................... 8
4
Process Steps ......................................................................................................................... 9
5
4.1
Creating Return Purchase Order ..................................................................................... 9
4.2
Stock-/Requirements List (Optional) .............................................................................. 10
4.3
Initial Stock Posting (Optional) ....................................................................................... 11
4.4
Stock Movement (Optional)............................................................................................ 12
4.5
Stock Overview (Optional) ............................................................................................. 13
4.6
Delivery Due List for Purchase Orders .......................................................................... 14
4.7
Picking Confirmation and Goods Issue Posting ............................................................. 15
4.8
Manual Review of Pending Credits ................................................................................ 16
4.9
Credit Memo ................................................................................................................... 17
Appendix................................................................................................................................ 18
5.1
Reversal of Process Steps ............................................................................................. 18
5.2
SAP ERP Reports .......................................................................................................... 20
5.3
Used Forms .................................................................................................................... 20
5.3.1
© SAP AG
Procurement ........................................................................................................... 21
Page 4 of 21
SAP Best Practices
Return to Vendor (136): BPD
Return to Vendor
1
Purpose
Document
The purpose of this document is to describe the process of returning goods back to the vendor.
Target group are buyers, warehouse employees and accounting clerks.
Scenario
The return to vendor process begins with a requirement to return an item to a vendor. The initial
activity is to request a Returns Material Authorization (RMA) from the vendor. This is a manual
step and the RMA number is entered into a text field in the return purchase order. The
Purchasing Administrator then creates a return purchase order in the system. The return
purchase order is similar to a standard purchase order except the return flag which sets up the
return delivery to enable shipment of the item(s) back to the vendor.
The return purchase order confirmation goes to the vendor and the return delivery is sent to the
shipping department where the item(s) are picked and shipped back along with a delivery note.
When the shipping department creates the delivery the item(s) are withdrawn from stock. A
credit memo is generated which nullifies the liability to the vendor.
2
Prerequisites
2.1 Master Data and Organizational Data
SAP Best Practices Standard Values
A range of indispensable master and organizational data was created in your ERP system in the
implementation phase, such as the data that reflects the organizational structure of your
company, as well as master data that suits its operational focus, for example, master data for
materials, vendors, and customers.
This master data usually consists of standardized SAP Best Practices default values and
enables you to go through the process steps of this scenario.
Using Your Own Master Data
Note that you can also test the scenario with other material, or organizational data
for which you have created master data. To find out how to create master data, refer
to the Master Data Procedures documentation.
Use the following master data in the process steps described in this document:
Manufacturing / Trading
Production Plant
Master data
Value
Other mat.
Comments
Vendor 300001:
© SAP AG
Page 5 of 21
SAP Best Practices
Return to Vendor (136): BPD
Master data
Value
Other mat.
Comments
Material
RAW12 (R12)
PD planning, no Serial no.; no
batch
Material
RAW15 (R15)
PD planning, no Serial no.; batch
Material
RAW18 (R18)
PD planning, no Serial no.; no
batch
Material
RAW19 (R19)
PD planning, no Serial no.; batch
Material
TRADE12 (H12)
Reorder point planning, no
Serial; no batch
Material
TRADE20 (H20)
Reorder point planning, Serial
no.; no batch
Plant:
1000
Storage
location:
Returns (1060)
Purchasing
org.:
1000
Purchasing
group:
100
Company
Code:
1000
Vendor:
300001
HR, with ERS, with returns
vendor
2.2 Business Conditions
The business process described in this Business Process Documentation is part of a bigger
chain of integrated business processes or scenarios. As a consequence, you must have
completed the following processes and fulfilled the following business conditions before you can
start going through this scenario:
Business condition
Scenario
You have completed all relevant steps described in the
Business Process Documentation Prereq. Process
Steps (154).
Prereq. Process Steps (154)
2.3 Roles
Use
The following roles must have been installed to test this scenario in the SAP NetWeaver
Business Client (NWBC). The roles in this Business Process Documentation must be assigned
to the user or users testing this scenario. You do not need these roles if you are not using the
NWBC interface, but the standard SAP GUI.
Prerequisites
The business roles have been assigned to the user who is testing this scenario.
© SAP AG
Page 6 of 21
SAP Best Practices
Return to Vendor (136): BPD
Business Role
Technical name
Process step
Transaction
Employee
(Professional User)
SAP_NBPR_EMPLOYEE_S
Assignment of this role is
necessary for basic
functionality.
Production Planner
SAP_NBPR_PRODPLANNE
R_S
Display Stock/
Requirements List
MD04
Warehouse Clerk
SAP_NBPR_WAREHOUSE
CLERK_S
Other Goods Receipt
Transfer Posting
Create Delivery
Change Delivery
MB1C
MIGO_TR
VL10B
VL02N
Purchaser
SAP_NBPR_PURCHASER_
S
Create Purchase Order
Review of Pending Credits
ME21N
ME2L
Warehouse
Manager
SAP_NBPR_WAREHOUSE
MANAGER_M
Stock Overview
MMBE
Accounts Payable
Accountant
SAP_NBPR_AP_CLERK_S
Enter Credit Memo
MIRO
2.4 Preliminary Steps
2.4.1
Return Reason “02 Quality test failed (to blocked
stock)”
During the goods receipt process the quality test failed. Therefore the material was posted into
blocked stock and moved into storage location for returns (for example, 1060).
To get a demand for returns to a vendor you can use building block 127 – Quality
Management for Procurement with vendor Evaluation, section Usage decision and
Quality Notification Creation.
2.4.2
Return Reason “Wrong material delivered”
During the goods receipt process the warehouse clerk detects that wrong material was delivered.
Therefore the material was posted into the blocked stock and moved into the storage location for
returns (for example, 1060).
This situation can be the result of building block 130, step 4.7.
2.4.3
Return Reason “Delivered quantity too high”
During the goods receipt process the warehouse clerk detects that too much material was
delivered. Therefore the additional material was posted into the blocked stock and moved into
the storage location for returns (for example, 1060).
© SAP AG
Page 7 of 21
SAP Best Practices
Return to Vendor (136): BPD
This situation can be the result of building block 130, step 4.7.
2.4.4
Return Reason “Wrong Trading Good in sales order”
A wrong material number of a trading good was posted into a sales order accidentally. The
customer sends the goods back and reminds the delivery of the right ones. The wrong Trading
goods must be sent back to the vendor.
This situation can be the result of building block 130, step 4.3.
3
Process Overview Table
Process Step
Business
condition
Business
Role
Transaction
code
Expected results
Create Return
Purchase Order
Need to return to
vendor
Purchaser
ME21N
Return PO is
created.
Review
requirements
Return PO sent
to vendor
Production
Planner
MD04
Return PO to
vendor and Delivery
Due List to
Shipping.
Stock Movement
(optional)
This step is to be
used if business
requirement
exists to move
inventory
(physically and
transactional)
from a shop floor
location to the
shipping
location.
Warehouse
Clerk
MIGO
Stock is moved from
a shop floor location
to the shipping
location.
Stock Overview
(Optional)
Overview on
stocks in plant
Warehouse
Manager
MMBE
Stock information
has been provided
Delivery due list
for purchase
orders
Request to pick
item to return
Warehouse
Clerk
VL10B
Item is picked.
Post Goods Issue
Item returned
and removed
from inventory.
Warehouse
Clerk
VL02N
Delivery note is
printed.
Manual Review
of Pending
Credits
Ensuring credit
for returned
materials
Purchaser
ME2L
A list of items where
the invoiced quantity
is less than zero.
(Credit return)
Credit Memo
Liability removed
Accounts
Payable
Accountant
MIRO
Credit memo is
generated and
vendor balance is
updated.
© SAP AG
External
process
reference
Page 8 of 21
SAP Best Practices
4
Return to Vendor (136): BPD
Process Steps
4.1 Creating Return Purchase Order
You now have the possibility to store the data of purchase orders as template for the data you
use most of the time. To save the data to a template, choose Save as Template.
To load data from a template, choose Load from Template.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics → Materials Management → Purchasing →
Purchase Order → Create → Vendor/Supplying Plant
Known
Transaction code
ME21N
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Purchaser
(SAP_NBPR_PURCHASER_S)
Business role menu
Purchasing → Purchase Order → Purchase Order →
Create Purchase Order
2. On the Create Purchase Order screen, make the following entries:
Field name
Description
User action and values
Comment
Vendor
<Vendor no.>
Purchasing
Organization
1000
Tab page: Org.
Data
Purchasing Group
100
Tab page: Org.
Data
Company Code
1000
Tab page: Org.
Data
Material
<material no.>
Deliv.Day
Change to tomorrow
Plant
1000
Storage Location
Returns (1060)
Quantity
10
Returns Item
Select the checkbox
© SAP AG
first checkbox in
item overview
section
Page 9 of 21
SAP Best Practices
Return to Vendor (136): BPD
Enter price PBXX for the PO when the system prompts to input. If there is no tax
code at tab Invoice in the field Tax Code, enter a valid tax code.
Do not forget to flag the item line as a return item!
3. Optional: If a Returns Material Authorization (RMA) number from the vendor is available, put
the number and some additional description into the item text field item text.
4. Choose Enter and then Save.
Result
A returns purchase order is created.
4.2 Stock-/Requirements List (Optional)
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics → Materials Management → Inventory Management
→ Environment → Stock → Stock/Requirements List
Transaction code
MD04
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Production Planner
(SAP_NBPR_PRODPLANNER_S)
Business role menu
Production → Evaluations → Reports → Display
Stock/Requirements Situation
2. On the Stock/Requirements List: Initial Screen, enter the following values:
Field name
Description
User action and values
Material
<material no.>
Plant
1000
Comment
3. Choose Enter. Review the overview screen and details as required.
Result
Reviewing stock requirements helps to determine the timing/urgency and to decide, if a normal
process to replenish returned items is sufficient or if a purchase order will have to be created
immediately.
© SAP AG
Page 10 of 21
SAP Best Practices
Return to Vendor (136): BPD
4.3 Initial Stock Posting (Optional)
Use
If there is not enough stock of the material to be returned to vendor, initial stock must be created.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics → Materials Management → Inventory
Management → Goods Movement → Goods Receipt →
Other
Transaction Code
MB1C
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Warehouse Clerk
(SAP_NBPR_WAREHOUSECLERK_S)
Business role menu
Warehouse Management → Consumption and Transfers →
Other Goods Receipts
2. On Enter Other Goods Receipts: Initial Screen, enter the following data; then choose Enter:
Field name
Description
User action and values
Movement Type
561
Plant
1000
Storage Location
Returns (1060)
Comment
3. On the Enter Other Goods Receipts: New Items screen, enter the following data then choose
Enter:
Field name
4.
Description
User action and values
Material
<material no.>
Quantity
10
Comment
If a serial number profile is defined in the material master, after having pushed Enter, there
will appear the window Maintain serial numbers. Either you can enter the numbers manually
or you choose Create Serial Number automatically.
5. If batch management is activated in the material master, you can enter a batch number in
the Batch field. If you do not enter a number, after choosing Enter the Automatic batch
number allocation window appears. Confirm it by choosing Yes.
6. If the material has a Minimum Remaining Shelf Life, you have to enter the Date of
Manufacture or the Shelf Life Expiration / Best-Before Date in the Manuf. Date/BBD field on
the Enter other goods receipts: Item 0001 screen.
Enter the date of yesterday and choose Enter.
On the following screen, choose Next screen (F8).
© SAP AG
Page 11 of 21
SAP Best Practices
7.
Return to Vendor (136): BPD
Choose Post (Ctrl+S).
Result
You have posted initial stock.
4.4 Stock Movement (Optional)
Use
This step is to be used if business requirements exist to move inventory (physically and in the
system) from a shop floor location or stores location to the return goods shipping location. For
example, if the storage location filled in the return purchase order is Storage_Location_Returns
(1060), return goods need to be transferred to return goods storage location.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics → Materials Management → Inventory Management →
Goods Movement → Transfer Posting (MIGO)
Transaction code
MIGO_TR
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Warehouse Clerk
(SAP_NBPR_WAREHOUSECLERK_S)
Business role menu
Warehouse Management → Consumption and Transfers →
MIGO Transfer Posting
2. On the initial screen, confirm that the first field in the top left corner of the screen shows A08
Transfer Posting and the second field shows R10 Other. Enter movement type 311 in the top
right field (TF trfr within plant) and choose Enter.
If you change the movement type the dialog box Tip (Change to Default Values)
appears. Choose Enter.
3. Under Detail Data, on the Transfer Posting tab page, make the following entries:
Field name
Description
User action and values
Material number
<material no.>
Plant
1000
Storage Location
(From)
1050
Storage Location
(Dest.)
1060
Unit of Entry
10
© SAP AG
Comment
Enter quantity
from the return
purchase order
Page 12 of 21
SAP Best Practices
Return to Vendor (136): BPD
4. Choose Enter.
5. If batch management is activated in the material master, you have to enter the batch number
on the Transfer posting tab page in the From field.
If you do not know the batch number you can choose Stock Overview and you will get a
survey of all the batches in all the storage locations of your plant.
In the Dest field enter the same batch number for the new storage location.
6. If a serial number profile is defined in the material master, you have to enter the serial
numbers of the individual parts, which you want to transfer on the Serial numbers tab page.
If you do not know the serial numbers of the individual parts, choose Find.
On the Display Material Serial Number: Serial Number Selection screen, make the following
entries:
Field name
Description
User action and values
Material
<material>
Period Frm
<today>
Period to
<today>
Plant
1000
Storage Location
<storage location of the
material with serial number>
Comment
Choose Execute.
On the Display Material Serial Number: Serial Number List screen, select the serial numbers
of the parts you want to transfer and choose Choose.
7. Choose Post.
8. The system message Material document 49xxxxxxxx posted displays at the bottom of the
screen.
Result
The stock movement is posted.
4.5 Stock Overview (Optional)
Use
You can use this step to get a survey of the batches in the storage locations of a plant.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics → Materials Management → Inventory Management
→ Environment → Stock → Stock Overview
Transaction code
MMBE
© SAP AG
Page 13 of 21
SAP Best Practices
Return to Vendor (136): BPD
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Warehouse Manager
(SAP_NBPR_WAREHOUSEMANAGER_M)
Business role menu
Warehouse Management → Inventory Control → Environment
→ Stock Overview
2. Choose Search Criteria and make the following entries:
Field name
Description
User action and values
Material
<material>
Plant
1000
Comment
3. Choose Apply.
Result
You get a survey of all the batches in plant 1000.
4.6 Delivery Due List for Purchase Orders
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics → Logistics Execution → Outbound Process → Goods
Issue for Outbound Delivery → Outbound Delivery → Create →
Collective Processing of Documents Due for Delivery →
Purchase Orders
Transaction code
VL10B
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Warehouse Clerk
(SAP_NBPR_WAREHOUSECLERK_S)
Business role menu
Warehouse Management → Shipping → Delivery Due →
Purchase Orders Due for Delivery
2. On the Purchase Orders, Fast Display screen, enter the following:
Field name
User action and values
Comment
Shipping Point
Shipping_Point 100R
(100R)
field is optional
Delivery Creation
Date
Today’s date at minimum
CalcRuleDefltDlv
CrDt
Blank
© SAP AG
Description
All Up To
Maximum
Number of Days
Page 14 of 21
SAP Best Practices
Return to Vendor (136): BPD
3. Choose the Purchase orders tab page.
4. Enter a purchasing document (This is an optional entry.).
5. Choose Execute.
6. Select purchase orders from the list. Choose Create Delivery in Background (SHIFT + F7).
7. Choose Show/Hide Delivery (SHIFT + F8), and note down the return delivery number shown
in the SD Doc. field: __________________________________.
Result
A return delivery is created.
4.7 Picking Confirmation and Goods Issue Posting
Use
This activity picks, packs, and ships components to the vendor.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics → Logistics Execution → Outbound Process →
Goods Issue for Outbound Delivery → Outbound Delivery →
Change → Single Document
Transaction code
VL02N
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Warehouse Clerk
(SAP_NBPR_WAREHOUSECLERK_S)
Business role menu
Warehouse Management → Shipping → Outbound Delivery →
Change Delivery
2. On the Change Outbound Delivery screen, enter the delivery document number from the
earlier section and choose Enter.
3. On the Returns (Pur. Ord.) XXXXXXXX Change: Overview screen, choose the Picking tab
page, enter the storage location 1060 Returns and the picked quantity equal to the delivery
quantity.
4. If a serial number profile is defined in the material master, go to the menu bar and choose
menu path (NWBC: More…) Extras  Serial Numbers. Either you can enter the numbers
manually or you push the button Create serial number automatically. Then choose Continue.
5. If batch management is activated in the material master, you have to enter the batch number
in the Batch field of the item.
© SAP AG
Page 15 of 21
SAP Best Practices
Return to Vendor (136): BPD
If you do not know the batch number you can use Transaction MMBE (see chapter 4.5) to
get a survey of all the batches in all the storage locations of plant 1000.
6. Check the entries and choose Save.
7. On the Returns (Pur.Ord.) XXXXXXXX Change: Overview screen, choose Post Goods
Issue.
Result
The components are picked and shipped to the vendor. A goods issue for the return delivery is
posted.
To report stock in transit, use transaction MB52 (use menu path Logistics 
Logistics Execution  Information System  Goods Receipt  Lists for Material
Stock  Warehouse Stocks per Material).
4.8 Manual Review of Pending Credits
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics → Materials Management → Purchasing → Purchase
Order → List Displays → By Vendor
Transaction code
ME2L
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Purchaser
(SAP_NBPR_PURCHASER_S)
Business role menu
Purchasing → Purchase Order → Purchase Order →
Purchase Orders by Vendor
2. On the Purchasing Document per Vendor screen, make the following entries:
Field name
Description
User action and values
Comment
Vendor
<vendor no.>
see ME21N
Purchasing
Organization
1000
Scope of List
ALV
ALV Grid Control
Selection
parameters
RECHNUNG
Open Invoices
Plant
1000
3. Choose Execute.
© SAP AG
Page 16 of 21
SAP Best Practices
Return to Vendor (136): BPD
Result
A list of open invoices is displayed, including a list of items with an invoiced quantity of less than
zero. Go to the To be inv. (Still to be invoiced) field where you can review pending credit memos.
4.9 Credit Memo
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics → Materials Management → Logistics Invoice
Verification → Document Entry → Enter Invoice
Transaction code
MIRO
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Accounts Payable Accountant
(SAP_NBPR_AP_CLERK_S)
Business role menu
Accounts Payable → Posting → Invoices → Enter Incoming
Invoice w/ PO Reference
2. On the Enter Incoming Invoice: Company Code XXXX screen, make the following entries:
Field name
Description
User action and values
Comment
Transaction
Credit Memo
Invoice date
Enter today’s date
credit memo date
Amount
<amount from purchase
order document> (including
tax)
see ME21N
Purchasing
Document
Number
Enter the returns PO number
created in step Create Return
Purchase Order (see ME21N)
On the PO Reference
tab page in the lower
screen area.
3. Choose Enter and then Post.
4. The system message Document no. XXXXXXXXXX created is displayed at the bottom of the
screen.
© SAP AG
Page 17 of 21
SAP Best Practices
5
Return to Vendor (136): BPD
Appendix
5.1 Reversal of Process Steps
In the following section, you can find the most common reversal steps, which you can take to
reverse some of the activities described in this document,
Post Goods Issue
Transaction code (SAP GUI)
VL02N
Reversal:
Cancel Material Document
Transaction code (SAP GUI)
MBST
Business role
Warehouse Clerk
(SAP_NBPR_WAREHOUSECLERK_S)
Business role menu
Warehouse Management  Consumption and Transfers 
Cancel Material Document
Comment
You must delete the item line in the quotation
Create Return Purchase Order
Transaction code (SAP GUI)
ME21N
Reversal:
Change Purchase Order
Transaction code (SAP GUI)
ME22N
Business role
Purchaser
(SAP_NBPR_PURCHASER_S)
Business role menu
Purchasing  Purchase Order  Purchase Order
Comment
If the shown purchase order number is wrong, enter the
relevant PO by choosing Other Purchase Order. Select the
relevant items or select all items by the button Select All.
After that push the delete button and save the purchase
order.
Create Outbound Delivery for Purchase Order
Transaction code (SAP GUI)
VL10B
Reversal:
Change Outbound Delivery
Transaction code (SAP GUI)
VL02N
Business role
Warehouse Clerk
(SAP_NBPR_WAREHOUSECLERK_S)
Business role menu
Warehouse Management  Shipping  Outbound Delivery
Change Delivery
Comment
Cancel return delivery
© SAP AG
Page 18 of 21
SAP Best Practices
Return to Vendor (136): BPD
Convert Assigned Requisitions to Purchase Orders
Transaction code (SAP GUI)
ME57
Reversal:
Reverse a Purchase Order
Transaction code (SAP GUI)
ME22N
Business role
Purchaser
(SAP_NBPR_PURCHASER_S)
Business role menu
Purchasing  Purchase Order  Purchase Order
Comment
Select PO and choose Edit Purchase Order.
Set deletion flag for order item line
Approval of Purchase Orders
Transaction code (SAP GUI)
ME28
Reversal:
Cancel Release of Purchase Order
Transaction code (SAP GUI)
ME28
Business role
Purchasing Manager
(SAP_NBPR_PURCHASER_M)
Business role menu
Purchasing  Approval  Purchasing Documents
Comment
Select the release Code 01 and set Cancel Release. Fill the
document number into the field document number
(optional). In the following view Release Purchasing
Documents with Release Code 01 select the PO line and
the button Cancel Release.
Receive Goods from Vendor to the Purchase Order
Transaction code (SAP GUI)
MIGO
Reversal:
Cancel Material Document
Transaction code (SAP GUI)
MBST
Business role
Warehouse Clerk
(SAP_NBPR_WAREHOUSECLERK_S)
Business role menu
Warehouse Management  Consumption and Transfers 
Cancel Material Document
Comment
If the material document number is not known, you can find it
out by watching into the PO item line tab Purchase Order
History (Transaction code ME22N: Materials Management 
Purchasing  Purchase Order  Change).
© SAP AG
Page 19 of 21
SAP Best Practices
Return to Vendor (136): BPD
Invoice Receipt by Line Item
Transaction code (SAP GUI)
MIRO
Reversal:
Cancel Invoice Document
Transaction code (SAP GUI)
MR8M
Business role
Accounts Payable Accountant
(SAP_NBPR_AP_CLERK_S)
Business role menu
Accounts Payable  Posting  Invoices Cancel Invoice
Document
Comment
If the invoice number is not known, you can find it out by
watching into the PO item line tab Purchase Order History
(Transaction code ME22N: Materials Management 
Purchasing  Purchase Order Change).
5.2 SAP ERP Reports
Use
The table below lists the most frequently used reports that help you to obtain additional
information on this business process.
You can find detailed descriptions of the individual reports in the following BPD
documents, which provide a comprehensive compilation of all important reports:

Financial Accounting: SAP ERP Reports for Accounting (221)

Logistics Processes: SAP ERP Reports for Logistics (222)
Note that the descriptions of some reports that are an indispensable part of the process flow may
be located directly in the section where they belong.
Reports
Report title
Transaction code
Comment
Material Documents
MB51
A list of the material documents which
were posted for one or more materials.
Purchasing Group Analysis
MCE1
A list with summarized data.
Vendor Analysis
MCE3
Direct access to vendor-related data.
Stock Overview
MMBE
A list of stock is displayed.
Release Purchasing
Documents
ME28
A list with all purchasing orders.
5.3 Used Forms
Use
In some of the activities of this business process, forms were used. The table below provides
details on these forms.
© SAP AG
Page 20 of 21
SAP Best Practices
5.3.1
Return to Vendor (136): BPD
Procurement
Common form
name
Form type
Used in process step
Output
type
Technical name
Purchase Order
SmartForm
Assign requisition and
create purchase order
NEU
YBHR_MMPO
© SAP AG
Page 21 of 21