Stock Transfer With Delivery in SAP MM - Intra and Inter Company STO | SAP MM-SD Integration

Overview (topic + series context)

• This video is Part 2/series on SAP MM stock transfer.
• It focuses on the 3rd process: Stock Transfer with Delivery using SAP MM–SD integration, covering both:
  • Intra company code STO (delivery route via SD)
  • Inter company code STO (delivery route + billing/invoicing)
• Earlier parts covered:
  • Inventory management route (MM-only movement postings: e.g., 301/303/305 and 351/101 in STO without delivery)
  • Purchasing route using STO + goods issue 351 + goods receipt 101

---

1) Intra-company-code STO using Delivery (MM–SD integration)

Business flow / transactions (4-step, two-step option)

1. Receiving plant creates STO

   • T-code: ME21N
   • STO document type: UB

2. Supplying plant creates delivery against STO

   • T-code: VL10B
   • Delivery type: NL

3. Supplying plant posts Goods Issue against the delivery

   • T-code: VL02N (picking/post GI)
   • Movement type:
     • 641 for two-step
     • 647 for one-step
   • Key difference: GI is posted against delivery, so 351 is not used

4. Receiving plant posts Goods Receipt

   • Movement type: 101
   • GR can be posted against delivery (recommended) or STO
   • Posting GR against delivery ensures SD-side document flow updates

Financial/document handling notes (intra-company)

• When 641 is posted:

  • Financial entries happen
    • Inventory credit for supplying side
    • Inventory debit for receiving side (same company code)

• When 101 is posted:

  • No additional FI document
  • Only quantity placement in receiving plant storage location

Stock in transit validation

• After GI 641 but before GR 101:
  • Stock in transit visible via MB5T
• After GR 101:
  • Stock in transit removed

Document flow visualization

• Posting GR against outbound delivery enables the complete SD/MM flow:
  • STO → delivery → picking → 641 → GR against 641

---

2) Configuration required to make STO-with-Delivery work (intra-company)

A core concept is: the system populates a “Shipping” tab in STO (ME21N) only if SD-related + MM-related configuration is complete.

The “shipping tab” importance

• Shipping tab appears only when the STO is treated like a sales order-like document from the supplying plant, so the supplying plant can create a delivery.
• The video shows:
  • STO created using the MM route → shipping tab missing
  • STO created with the delivery route config → shipping tab present

Required setup areas (4 main parts)

1. SD configuration

   • Create Sales Area:
     • Sales Organization + Distribution Channel + Division
   • Assign sales area to the supplying plant’s company code

2. Sales master data

   • Create/extend:
     • Customer master for the receiving plant (customer role concept)
     • Material master sales views for the supplying plant’s sales area

3. MM configuration (plant shipping data + delivery type + step model)

   • Define shipping data for plants (links):
     • Supplying-plant → sales area
     • Receiving-plant → customer code
   • Configure delivery type by:
     • STO document type (UB) + supplying plant
     • Delivery type becomes NL
   • Configure one-step vs two-step procedure:
     • Two-step: 641 then 101
     • One-step: 647 then simultaneous 101

4. Logistic execution config

   • Shipping point determination from:
     • Shipping condition (from receiving plant customer master)
     • Loading group (from material master)
     • plus shipping point/assignment to plant
   • This shipping point fills the shipping tab

Tutorial-style demonstration: one-step vs two-step (intra-company)

• After enabling one-step:
  • Movement type changes from 641 → 647
  • System creates 647 and 101 simultaneously
• Storage location requirement changes in one-step:
  • Since GR posts automatically, you must set storage location in the STO
  • Otherwise, GI fails with “storage location required”

---

3) Inter-company-code STO using Delivery (delivery + billing + invoicing)

Key conceptual differences vs intra-company

Inter-company involves more SD/MM financial steps:

• GI triggers sales-like accounting + consumption (COGS)
• Delivery leads to billing
• Receiving plant GR leads to invoice receipt (Miro)
• Sending plant effectively handles order-to-cash side

Comparative note:

• Intra-company: often only GI stage has FI impact; GR has none (as demonstrated)
• Inter-company: FI postings occur at multiple stages including GR, billing, and invoice receipt

Business flow (two-step + one-step variants)

Two-step (as demonstrated)

1. Receiving plant creates STO

   • T-code: ME21N
   • STO document type: NB
   • Uses supplier code (vendor) of the supplying plant

2. Supplying plant creates delivery

   • T-code: VL10B
   • Delivery type: NLCC

3. Supplying plant posts Goods Issue

   • T-code: VL02N
   • Movement type: 643 (two-step)

4. Supplying plant creates billing document

   • T-code: VF01
   • Billing type: IV

5. Receiving plant posts Goods Receipt against outbound delivery

   • Movement type: 101
   • In inter-company, GR posts FI entries
     • inventory debit + GRI clearing credit

6. Receiving plant posts invoice (Miro)

   • T-code: MIRO
   • Vendor = supplying plant

One-step variant

• GI movement type becomes 645
• System posts 645 and GR (101) simultaneously

Financial posting highlights (inter-company)

• At GI (643/645):

  • Sales-like posting:
    • inventory credit (supplying)
    • COGS/consumption debit

• At GR (101):

  • inventory debit
  • credit to GRI clearing account

• At Billing (IV):

  • customer debit
  • sales revenue credit

• At Invoice receipt (MIRO):

  • clears GR/GRI clearing
  • credits vendor (supplying plant)

Validation/demonstration steps

• Demonstrates:
  • accounting differences between intra vs inter at GI stage
  • document flow in delivery/billing documents
  • FI document links to each stage via PO history / FI document display

---

4) Configuration summary for order types & movement/delivery/billing logic (final recap)

STO order/document types

• Inventory management route: order type not applicable
• STO without delivery: UB
• STO with delivery (intra-company): UB
• STO with delivery (inter-company): NB

Movement types by scenario

• STO without delivery (two-step):

  • 351 (GI) and 101 (GR)

• Intra-company STO with delivery:

  • two-step: 641 + 101
  • one-step: 647 + 101

• Inter-company STO with delivery:

  • two-step: 643 + 101
  • one-step: 645 + 101

Delivery types / schedules

• Intra-company delivery type: NL
  • Schedule line category: NN
• Inter-company delivery type: NLCC
  • Schedule line category: NC

Billing/invoicing only for inter-company

• Billing type: IV
• MIRO processing is performed for the receiving plant

Pricing/valuation concept

• For MM-based STO variants (including the demonstrated delivery STO cases):
  • pricing generally uses supplying plant’s valuation price
• In inter-company STO, the demo indicates manual price input affects invoice processing

---

Main speakers / sources (end)

• Speaker: the YouTube creator/host (referred to only as “Hey everyone” / “welcome back”; no explicit name given in subtitles)
• Source system: SAP (MM–SD integration concepts demonstrated using standard SAP transactions such as ME21N, VL10B, VL02N, MIGO, MB5T, VF01, MIRO, and configuration via SPRO)