Stock transfer in SAP is one of the most misunderstood areas in Materials Management. Most consultants only know fragments:
- Some know only MIGO‑based stock transfers
- Some know only Stock Transport Orders (STO)
- Some know only intercompany scenarios
- Some know only 1‑step vs 2‑step movement types
- Some know only delivery‑based STO or billing‑based STO
Very few people see the complete picture. This master guide is designed to change that. It brings together every major stock transfer scenario, every key movement type, and every STO variant into one clean, logical, real‑world framework.
How to use this master guide
This page is your navigation hub. It explains the full structure of SAP stock transfer and links to detailed configuration and execution guides for each scenario. Start with the branch that matches your current project, then follow the numbered posts to build a complete, consistent design.
The two main branches of SAP stock transfer
All SAP stock transfer scenarios can be grouped into two major families:
- Branch A: Stock Transfer without STO (MIGO‑based)
- Branch B: Stock Transfer with STO (Purchase Order‑based)
Once you understand these two branches, every movement type, document type, and integration point falls into place.
A — Stock transfer without STO (MIGO‑based)
This is the simplest form of stock transfer in SAP. There is no purchase order, no delivery, and no billing. Everything is executed directly in MIGO using stock transfer movement types.
- Executed via MIGO
- No STO, no delivery, no billing
- Works for both intra‑company and inter‑company stock transfers
- Key movement types: 301, 303, 305
A1 — Main guide: MIGO‑based stock transfer
This post is your starting point for all MIGO‑based stock transfers. It explains both intra‑company and inter‑company scenarios, and the difference between 1‑step and 2‑step stock transfers.
👉 Stock Transfer in SAP: The Best Guide with All Scenarios Explained
- A1.1 — Intra‑company stock transfer
- A1.1.1 — 1‑step intra‑company stock transfer (301)
- A1.1.2 — 2‑step intra‑company stock transfer (303 + 305)
- A1.2 — Inter‑company stock transfer
- A1.2.1 — 1‑step inter‑company stock transfer (301)
- A1.2.2 — 2‑step inter‑company stock transfer (303 + 305)
As you go through the MIGO scenarios…
…you’ll see the limitations of pure movement‑type‑based stock transfers. Once you understand those limits, the next logical step is to move into STO‑based stock transfers for better control, traceability, and integration.
B — Stock transfer with STO (Purchase Order‑based)
The second branch uses Stock Transport Orders (STO). Here, stock transfer is driven by a purchase order, optionally followed by delivery and billing. This is where integration with SD and FI comes into play, especially in intercompany scenarios.
- Uses Stock Transport Orders (STO)
- Can include delivery and billing
- Supports both intra‑company and inter‑company stock transfers
- Integrates MM, SD, and FI in advanced scenarios
B0 — Overview: Mastering SAP Stock Transport Orders (STO)
This post introduces the STO concept and explains the three main STO‑based stock transfer processes: without delivery & billing, with delivery but without billing, and with delivery & billing.
👉 Mastering SAP Stock Transport Orders (STO)
From here, the STO branch splits into three core process types:
- B1 — STO without delivery & without billing
- B2 — STO with delivery & without billing
- B3 — STO with delivery & with billing (intercompany STO)
B1 — STO without delivery & without billing
This is the simplest STO‑based process. There is a Stock Transport Order, but no delivery document and no billing. The stock transfer is executed in two steps using a goods issue and a goods receipt.
- PO document type: UB
- Movement type: 351
- Always a 2‑step process
- Works for both intra‑company and inter‑company (depending on plant company codes)
👉 Stock Transfer with STO but without Delivery & Billing — Configuration Guide
B2 — STO with delivery & without billing
In this scenario, the Stock Transport Order triggers an outbound delivery, but there is still no billing between the plants. This gives you better logistics control and warehouse integration without creating intercompany invoices.
- PO document type: UD
- Delivery type: NL
- 1‑step stock transfer: 647
- 2‑step stock transfer: 641 + 101
- Works for both intra‑company and inter‑company
👉 Stock Transfer with STO & Delivery but Without Billing — Setup & Execution
B2.1 — Special case: 1‑step STO with delivery between the same plants
There is a powerful special case where you configure a 1‑step STO with delivery between the same plants, even when the standard process uses 2‑step STOs. This is achieved using special document and delivery types.
- Special PO document type: YUD
- Special delivery type: YNL
- 1‑step STO between the same plants, alongside existing 2‑step STOs
B3 — STO with delivery & billing (intercompany STO)
This is the most advanced STO scenario and is often called the intercompany STO with delivery and billing. Here, the sending plant belongs to a different company code than the receiving plant, and the process integrates MM, SD, and FI.
- PO document type: NB
- Delivery type: NLCC
- Billing document created in the supplying company code
- Logistics Invoice Verification (LIV) in the receiving company code
👉 How to Configure SAP Intercompany STO Process with Delivery & Billing
B3.1 — Logistics Invoice Verification (LIV) for the receiving plant
The billing document created in the supplying company code becomes a vendor invoice in the receiving company code. The configuration and execution of this step are covered in a dedicated guide.
👉 How to Configure Logistics Invoice Verification in SAP S/4HANA
B3.2 — Accounting entries in intercompany STO
To fully understand the financial impact of intercompany STO with delivery and billing, you need to see the accounting entries at each step of the process. This is covered in a dedicated accounting entry guide.
👉 Mastering Accounting Entries in the SAP Intercompany STO Process with Delivery & Billing
B3.3 — MM pricing procedure for STO scenarios
Wherever pricing is applicable in STO scenarios, the MM pricing procedure becomes critical. This includes intercompany STOs with delivery and billing, and any scenario where internal prices or transfer prices are required.
👉 Ultimate Guide to SAP S/4HANA MM Pricing Procedure
How to get the maximum value from this series
To get the most out of this complete SAP stock transfer series, follow this sequence:
- Start with A1 to understand MIGO‑based stock transfers and movement types.
- Move to B0 to understand the role of STO in stock transfers.
- Study B1 and B2 to master STO without billing.
- Deep‑dive into B2.1 if you need 1‑step STO with delivery between the same plants.
- Finish with B3, B3.1, B3.2, and B3.3 to complete your understanding of intercompany STO, LIV, accounting, and pricing.
Don’t treat stock transfer as a single configuration topic.
It is a complete integration story across MM, SD, and FI. When you understand all nine scenarios in this series, you don’t just know how to post a movement — you know how to design a robust, auditable, and scalable stock transfer landscape in SAP S/4HANA.
