ERPTwin
Menu
161MMME21NVL10Bintermediate

Return to Supplier with a Returns Purchase Order, Outbound Delivery and Movement 161

A document-based return: purchasing creates a returns item on a PO, shipping creates an outbound delivery to the supplier, goods issue posts movement 161, and the supplier's credit memo clears GR/IR — unlike the quick 122 return, which is posted directly in MIGO.

Educational content. SAP behaviour varies by configuration and release. Spotted something off? Report it.

Digital twin

Docsnone yet
SAP DOCUMENTSVisualization of Return to Supplier with a Returns Purchase Order, Outbound Delivery and Movement 161. All information shown in the scene is also available in the caption and the panels next to it.
Demo data

01Quick return or document-based?

Logistics needs a delivery note, packing and a shipment for the return. Which procedure?

Business scenario

10 EA of RM-1000 received last month are out of specification. The supplier agrees to take them back and issue a credit. Logistics wants a delivery document for the return shipment.

All companies, numbers and documents are fictional demo data.

Step-by-step flow

  1. 01

    Quick return or document-based? open in twin

    Logistics needs a delivery note, packing and a shipment for the return. Which procedure?

    122 references the original GR and is posted instantly; a returns PO plans the return with its own documents.

  2. 02

    No delivery document open in twin

    122 posts the return directly from the original receipt. There is no delivery for picking, packing or the shipping papers logistics asked for.

    It suits returns spotted at receipt; planned returns with shipping need a returns PO.

  3. 03

    Create the returns PO open in twin

    Returns PO 4500003000: 10 EA back to Demo Supplier Ltd., value ₹10,000.

    It reverses the direction: the 'receipt' becomes an issue and the invoice becomes a credit memo.

  4. 04

    Outbound delivery and goods issue (161) open in twin

    Delivery 84000300 picks the goods; goods issue posts 161: 500 → 490. GR/IR is debited.

    It mirrors a 101: stock out, GR/IR in the opposite direction.

  5. 05

    Supplier credit memo open in twin

    The supplier's credit memo for ₹10,000 is posted in MIRO and clears GR/IR.

    GR/IR balances again; the supplier balance is reduced.

  6. 06

    Return complete open in twin

    Returns PO → delivery → 161 → credit memo.

    Compare with 122 in the GR reversal process, which needs no PO but offers no delivery.

SAP documents

Drag to pan · Ctrl + scroll to zoom

Stock impact

StepPlant / SLocStock typeMvTChange
Outbound delivery and goods issue (161)1000 / 0001Unrestricted use161−10 EA

Accounting impact

Return to supplier via returns PO

Typical

Outbound delivery and goods issue (161)

  • Dr GR/IR clearing (WRX)₹10,000
  • Cr Inventory — raw materials (BSX)₹10,000

Inventory goes down and GR/IR is debited — it now expects a credit memo for the same value.

Credit memo for the returns PO

Typical

Supplier credit memo

  • Dr Supplier 100001 (payable)₹10,000
  • Cr GR/IR clearing (WRX)₹10,000

Reduces what is owed to the supplier and clears the GR/IR debit from the 161.

Typical conceptual flow. Actual G/L accounts and posting behaviour depend on material valuation, automatic account determination and system configuration.

Movement type

  • 161GR returns (returns PO)Reversal: 162

Returns goods to a supplier through planned purchasing and shipping documents, with a credit memo closing the financial side.

Transactions & Fiori apps

  • ME21N — Create PO (returns item)
  • VL10B — Create Deliveries
  • VL02N — Post Goods Issue
  • MIRO — Credit Memo
  • Manage Purchase Orders

Differences by SAP version

Returns PO with or without delivery; 161 via MIGO or delivery.

Configuration

  • Returns PO with delivery

    Configuration dependent

    Supplier must be linked to a customer number and a returns delivery type assigned. Requires configuration validation.

Prerequisites

  • Supplier set up for returns with shipping data (as a customer for deliveries, typical)
  • Delivery type for returns to supplier assigned

Master data

Supplier master
Linked customer for shipping (typical).

Organizational structure

  • Plant 1000
  • Shipping point 1000

Tables

TableDescription
EKPOReturns item indicator
LIKP / LIPSReturns delivery
MATDOC161

Integration

  • SDShipping functions for the return delivery.
  • FIGR/IR and supplier credit.

Common errors

  • “No delivery can be created for the returns PO”

    Likely causes: Supplier has no customer link; No delivery type for returns

    Where to look: Supplier master · Shipping data in the PO

Troubleshooting

Something went wrong? Work through these checks in order. They are diagnostic questions, not configuration instructions — confirm changes with your system owner.

  1. CHECK 1

    Delivery

    • Customer linked to supplier?
    • Returns delivery type?

Interview questions

  • Compare 122 and 161.

    122 is a return delivery posted in MIGO with reference to the original goods receipt — quick, no extra documents. 161 is the goods issue for a returns PO item, usually via an outbound delivery, so the return is planned and shipped with documents, followed by a credit memo.

Quiz

Q1 · Identify the movement type

Which movement type posts the goods issue for a returns PO item?

References

  • SAP SE — SAP Help Portal: Returns to Supplier (source)
  • SAP SE — SAP Help Portal: Returns Purchase Orders (source)

Explanations are original. They summarize standard behaviour; always validate against your system's release and configuration.

Version history

VersionChange
1.0.0Initial version.