Stock Transfer without delivery in SAP MM | Mvt. type 301, 303, 305 & 351 | STO without Delivery

Technological concepts & key product/process features (SAP MM Stock Transfer)

Goal of Stock Transfer in SAP MM

• Stock transfer is used when a receiving plant needs material, but instead of going through the full procure-to-pay process, it checks whether another plant already has stock.
• Stock availability can be checked using:
  • MMBE
  • MB52
• If the supplying plant agrees, stock is transferred between plants using Stock Transfer Order (STO) concepts.

---

Main STO methods covered (with what they involve)

1) Inventory Management Route (in SAP via movement postings)

• Implemented by posting material movements directly.
• Uses movement types:
  • 301 = single-step stock transfer (instant inventory transfer in SAP)
  • 303 + 305 = two-step process to support in-transit stock
    • 303: posts stock to “stock in transfer/in-transit” (quantity not yet available in receiving storage)
    • 305: posts stock into receiving storage location → moves from in-transit to unrestricted use

FI posting behavior (important detail)

• Intra-company code transfer (same company code for both plants) using 301
  • Results in one accounting document under the parent company code
  • Contains:
    • Credit to inventory GL (supplying plant)
    • Debit to inventory GL (receiving plant)
  • Transaction key mentioned for inventory lines: BSX
• Intra-company code transfer with 303
  • FI documents are posted at 303 stage (value-based posting)
  • Quantity becomes available later when 305 is posted
• Inter-company code transfer (different company codes) using 301
  • Results in two accounting documents (one per company code)
  • In addition to inventory GL postings, includes intercompany clearing GL
  • Transaction keys referenced:
    • BSX for inventory posting
    • BUV for intercompany clearing

---

2) Purchasing Route (STO created as a Purchase Order + delivery by GI/GR)

• Requesting plant creates a Stock Transport Order (STO) using:
  • ME21N
• Document type used in demo: UB (stock transport order)
  • Behavior change: vendor field becomes supplying plant
• Then the supplying plant issues material against the STO via MIGO:
  • Movement type: 351 (goods issue / issue for STO)
• Receiving plant performs Goods Receipt using MIGO:
  • Movement type: 101

In-transit tracking feature

• Uses MB5T to verify stock in transit against the STO:
  • Shows quantity and which stock transport order it belongs to
• After 101, stock in transit is cleared and stock is updated in receiving plant (e.g., unrestricted use via MMBE).

FI posting behavior (important detail)

• In this STO method, financial documents are posted at the 351 stage
  • Value transfers to receiving side at 351
  • Quantity is only placed into receiving storage at 101 (no additional FI posting at 101)
• For moving average price scenarios:
  • Transfer price comes from the sending plant
  • Receiving plant may update valuation when material is transferred on value basis during 351
  • 101 does not create FI entries

---

Configuration highlighted for Purchasing Route (document type control)

• In SPRO (SAP Reference IMG), the logic is based on purchase order document type settings:
  • Materials Management → Purchasing → Purchase Order → Define Document Types for Purchase Order
• For document type UB:
  • A control indicator T is present, meaning transport/stock transport order
  • This drives:
    • automatic mapping of supplier field to supplying plant
    • allowed item category for STO:
      • item category U (stock transfer)
  • In the created STO:
    • item category U is selected automatically
    • the supplying plant field appears/gets used accordingly

---

Demo flow mentioned (practical steps)

Inventory management route

1. Check sending plant stock (MMBE/MB52)
2. Confirm receiving plant has no stock
3. Post 301 via MI (transfer posting against other)
4. Validate accounting entries and inventory updates
5. Demonstrate two-step 303 (in-transit) then 305 (unrestricted receipt)
6. Contrast intra- vs inter-company code FI results

Purchasing route

1. Create STO via ME21N using document type UB
2. Issue with MIGO movement type 351
3. Verify in-transit with MB5T
4. Receive with MIGO movement type 101
5. Check receiving stock update and purchase order history
6. Confirm FI postings occur at 351 only

---

What the video promises next

• Part 2 will cover the Logistic Execution route (MM-SD integration):
  • Both plants do their SD/MM activities
  • Supplying plant posts SD-related documents
  • Receiving plant performs goods receipt
  • Will also compare intercomp vs intracomp STO in that logistics scenario

---

Main speakers/sources

• Single presenter / YouTube channel owner (narrator of “welcome back / stay tuned / like and subscribe” segments)
• SAP system functionality, reflected through T-codes and movement types:
  • MMBE, MB52, MI, MIGO, ME21N, MB5T, SPRO