SAP LE Returns Processing

You are an SAP Logistics Execution (LE) specialist. The user wants to process product returns end-to-end: create return orders, post goods receipts, and generate credit memos in SAP.

What to check first

• Access to transaction LO01 (Logistics Information System) or VL02N (Change Delivery) to verify returns module is active
• Check SPRO > IMG > Sales and Distribution > Returns to confirm return order type and credit memo procedure are configured
• Run SE16N on table TVSLS to verify your sales organization has return delivery types assigned (e.g., delivery type "RL" for returns)

Steps

1. Navigate to VA01 (Create Sales Order) and select document type "RM" (Return Merchandise) or "KR" depending on your config; enter customer, material, and return reason
2. In the return order, specify the Return Reason Code (table TVGR) and reference the original sales order via Reference Order field
3. Create a Delivery for the return order using VL01N (Create Delivery); system automatically proposes return delivery type and warehouse location
4. Post Goods Receipt in LT11 (Receipt Processing) by scanning/entering the return material number; system updates stock and triggers return lot tracking
5. Run VF01 (Create Billing Document) and select document type "CR" (Credit Memo Request) or "G2" (Credit Memo); reference the return delivery
6. In the credit memo, verify Return Deduction Logic: system pulls original invoice prices and applies any restocking fees (customizable in TVSLS) or condition types (e.g., RMRE for return material rebate)
7. Post the credit memo with VF02 (Change Billing Document) and execute VF04 (Billing Due List) to confirm GL accounts are hit correctly
8. Reconcile via VBRK/VBRP (Billing Header/Item) reports to ensure debit/credit balancing and verify stock movements in MB51 (Material Document List)

Code

*&---------------------------------------------------------------------*
*& Report: Returns Processing Workflow
*&---------------------------------------------------------------------*
REPORT zle_returns_processing.

DATA: lt_return_orders TYPE TABLE OF vbak,
      ls_return_order TYPE vbak,
      lv_return_doc_num TYPE vbeln,
      lv_delivery_num TYPE likp-vbeln,
      lv_credit_memo TYPE vbrk-vbeln,
      lv_return_reason TYPE tvgr-vgrat.

CONSTANTS: gc_return_doc_type TYPE vbak-vbtyp VALUE 'RM',
           gc_credit_memo_type TYPE vbrk-vbtyp VALUE 'G2',
           gc_return_reason_defective TYPE tvgr-vgrat VALUE '01'.

*&

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change