MM / P2Pintermediate

MM Stock Transport Order Part 2: STO End to End — Configuration and Process

Key takeaway

Configure and run STOs with delivery: shipping data for plants (supplying plant sales area, receiving plant as customer), delivery type and checking rule per document type and supplying plant, ATP at supplying plant, MRP special procurement key, delivery creation, GI, GR and monitoring.

Explanation

📌 KEY POINTS
✅ Shipping data for plants: supplying plant sales org/channel/division; receiving plant has a customer number.
✅ Delivery type (e.g. NL intra-company, NLCC cross-company) and checking rule are assigned per document type and supplying plant.
✅ ATP checks at the supplying plant; shipping point from supplying plant data.
✅ MRP special procurement key (stock transfer from plant X) creates STO requisitions automatically.
⚠️ Missing shipping data for the receiving plant means STOs can be saved but no delivery is created.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 introduced STOs. Now configuration and process.

━━━━━━━━━━━━━━━━━━━━
▶ 1. SHIPPING DATA

Receiving plant → customer number; supplying plant → sales area.

━━━━━━━━━━━━━━━━━━━━
▶ 2. DELIVERY TYPE AND CHECKING RULE

Per document type + supplying plant.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ATP AND SHIPPING

Availability at supplying plant, route, shipping point.

━━━━━━━━━━━━━━━━━━━━
▶ 4. MRP INTEGRATION

Special procurement key (e.g. 40 series "stock transfer from plant X", per config).

━━━━━━━━━━━━━━━━━━━━
▶ 5. PROCESS

STO → VL10B → pick → PGI → GR → monitoring.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Maintain shipping data for plants.
Assign delivery type/checking rule.
Create STO via MRP and deliver.

✅ CHECKPOINT: MRP-generated STOs create deliveries automatically.

Code example

ABAP Code

===== STEP 1: configuration (SPRO > MM > Purchasing > Purchase Order > Set up Stock Transport Order) =====Define shipping data for plants: plant 1100 → customer C1100; plant 1000 → sales org 1000 / DC 10 / div 00Assign delivery type and checking rule: UB + supplying plant 1000 → NL, checking rule BAssign document type: supplying plant 1000 → receiving plant 1100 → UB ===== STEP 2: MRP =====Material MRP2 at plant 1100: procurement type F, special procurement key "stock transfer from 1000" ===== STEP 3: process =====MRP → STO requisition → STO → VL10B → PGI → GR

Real project scenario

An STO could be saved but no delivery was created in VL10B. The receiving plant had no customer number in shipping data. Maintaining shipping data and adding it to the new-plant checklist fixed deliveries.

Common mistakes

Missing shipping data.
Wrong delivery type assignment.
No special procurement key.
Checking rule excludes stock.
No monitoring of undelivered STOs.

Best practices

Include STO setup in plant checklist.
Test ATP at supplying plant.
Use MRP special procurement.
Monitor VL10B backlog.
Document per plant pair.

Interview angle

Questions: "How do you configure an STO?", "Why is no delivery created?", "How does MRP create STOs?"
Strong answer: shipping data, delivery type/checking rule assignment, ATP, special procurement key, process.

Practice this lesson

Quick check

1. How does MRP create STO requisitions automatically at the receiving plant?

2. An STO can be saved but VL10B creates no delivery. What should be checked?

3. What must be maintained so a receiving plant can get an outbound delivery for an STO?

Interview questions

1. In a global template rollout, a client wants to use Stock Transport Orders (STOs) for intercompany services procurement where a service plant fulfills maintenance requests for another plant under a different company code. What architecture considerations apply?

Answer it in your own words first, then compare.

2. STOs for a new plant can be saved, but no deliveries are created and MRP doesn't generate STO requisitions. What do you configure?