641101MMME21NVL10Badvanced

Intra-Company Stock Transport Order with Outbound Delivery

Plant 1100 orders stock from plant 1000 with an STO. An outbound delivery and goods issue (641) put the goods into stock in transit; a goods receipt (101) at plant 1100 completes the transfer.

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

Docs

Demo data

01Plant 1100 creates an STO

A stock transport order requests 100 EA from supplying plant 1000.

SAP

STO 4500001300

Supplying plant: 1000
Receiving plant: 1100
Quantity: 100 EA

Business scenario

Plant 1100 needs 100 EA of RM-1000 from plant 1000 (same company code). The transfer is planned and tracked with a stock transport order and an SD outbound delivery.

All companies, numbers and documents are fictional demo data.

Step-by-step flow

01
Plant 1100 creates an STO open in twin
A stock transport order requests 100 EA from supplying plant 1000.
The STO enables MRP, delivery processing and in-transit visibility — benefits a plain 301 does not give.
02
Outbound delivery is created open in twin
Shipping creates outbound delivery 80000123 for the STO (VL10B).
Delivery-based STOs require shipping data for the supplying plant and the receiving plant set up as a customer — configuration dependent.
03
Picking and loading open in twin
100 EA are picked from SLoc 0001 and loaded onto the truck.
Picking quantities are confirmed on the delivery before goods issue.
04
Post goods issue (641) open in twin
One posting: plant 1000 600 → 500 EA, stock in transit at plant 1100 0 → 100 EA, and the material document and accounting document are created together.
The quantity now sits in the receiving plant's stock in transit and is not yet usable. Stock in transit is valuated stock of the receiving plant. Physical arrival alone changes nothing in SAP: only the receiving plant's 101 goods receipt transfers the quantity from stock in transit into the destination stock type.
05
Truck travels to plant 1100 open in twin
The goods are on the road; SAP shows them as stock in transit.
Stock in transit can be monitored per STO; long-open in-transit stock is a common reconciliation topic.
06
Goods receipt at plant 1100 (101) open in twin
In transit: 100 → 0. Plant 1100 unrestricted: 25 → 125 EA.
Stock moves from in transit to unrestricted at the receiving storage location.
07
STO complete open in twin
STO → delivery → 641 goods issue → stock in transit → 101 goods receipt.
The STO history now shows the goods issue and goods receipt.

SAP documents

Drag to pan · Ctrl + scroll to zoom

Stock impact

Step	Plant / SLoc	Stock type	MvT	Change
Post goods issue (641)	1000 / 0001	Unrestricted use	641	−100 EA
Post goods issue (641)	1100	Stock in transit	641	+100 EA
Goods receipt at plant 1100 (101)	1100	Stock in transit	101	−100 EA
Goods receipt at plant 1100 (101)	1100 / 0001	Unrestricted use	101	+100 EA

Accounting impact

Intra-company STO goods issue between valuation areas

Configuration dependent

Post goods issue (641)

Dr Inventory — plant 1100 (stock in transit) (BSX)₹1,00,000
Cr Inventory — plant 1000 (BSX)₹1,00,000

Value transfers at goods issue for intra-company STOs; freight conditions and price-control differences can add lines. Inter-company STOs involve billing and invoice verification instead.

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

Movement type

641TF to stock in transit (delivery)Reversal: 642
101GR from stock in transit
351GI to stock in transit (STO without delivery)
643GI for cross-company STO

Plans and executes stock transfers between plants with purchasing, shipping and in-transit tracking.

Transactions & Fiori apps

ME21N — Create STO
VL10B — Create Deliveries for POs
VL02N — Post Goods Issue
MIGO — Goods Receipt
MB5T — Stock in Transit

Manage Stock Transport OrdersAvailability depends on release
Post Goods Receipt for Inbound Delivery / Purchasing Document

Differences by SAP version

Process unchanged in principle; stock in transit reporting available through Fiori apps and MB5T.

Configuration

Set up stock transport order
Configuration dependent
Assign document type, delivery type and checking rule per supplying/receiving plant combination.
One-step vs two-step receipt
Configuration dependent
Determined by settings and movement types; two-step is common with deliveries.

Prerequisites

Supplying plant assigned in STO configuration
Receiving plant set up as a customer (for delivery-based STO)
Shipping data / shipping point determination
Material extended to both plants with sales and purchasing views where needed

Master data

Material master: Plant data in both plants; sales data in supplying plant for deliveries.
Customer for receiving plant: Required for delivery processing.

Organizational structure

Company code 1000
Plants 1000 and 1100
Shipping point (demo)
Sales area for intra-company delivery (configuration dependent)

Tables

Table	Description
EKKO / EKPO	STO header / item
EKBE	STO history (GI and GR)
LIKP / LIPS	Delivery header / items
MATDOC	641 and 101 movements

Integration

SDOutbound delivery and goods issue.
FIValue transfer between valuation areas.

Common errors

“No delivery created by VL10B”
Likely causes: STO configuration incomplete; Receiving plant not assigned to a customer; Shipping data missing
Where to look: STO customizing · Material sales views
“Stock in transit not cleared”
Likely causes: GR not posted at receiving plant
Where to look: MB5T · STO history

Troubleshooting

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

CHECK 1
Configuration
- Is the plant combination set up in STO customizing?
- Is a delivery type assigned?
CHECK 2
Master data
- Is the receiving plant linked to a customer?
- Does the material have sales views in the supplying plant?

Interview questions

Difference between 301 and an STO?
301 is a single posting with no planning or in-transit stock. An STO supports MRP, delivery, transport and shows stock in transit between goods issue and goods receipt.
Who owns stock in transit in an intra-company STO?
The receiving plant — it is valuated stock of the receiving plant at plant level.
Intra-company vs inter-company STO?
Inter-company involves two company codes, billing and invoice verification; intra-company stays within one company code.

Quiz

Q1 · Document flow

Order these documents in a delivery-based STO.

STOOutbound delivery641 goods issue101 goods receipt

References

SAP SE — SAP Help Portal: Stock Transport Order (source)
SAP SE — SAP Help Portal: Stock Transport Order with Delivery via Shipping (source)

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

Version history

Version	Change
1.2.0	SME decision — one posting, one step: the 641 goods issue and its accounting document now appear together in the goods issue step.
1.1.0	SME correction (step 4): 641 creates stock in transit; the receiving plant's 101 transfers it into the destination stock type; physical arrival is distinct from the SAP receipt posting.
1.0.0	Initial version.