301MMMIGOintermediate

Plant-to-Plant Transfer Posting (Movement Type 301)

Move stock from one plant to another in a single posting. Quantity leaves plant 1000 and arrives in plant 1100 at the same moment, with a value transfer between valuation areas.

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

Docsnone yet

Demo data

01Plant 1100 needs stock

Plant 1100 has 25 EA and needs 50 more from plant 1000.

Business scenario

Plant 1100 (Pune) runs short of RM-1000. Plant 1000 transfers 50 EA using a one-step transfer posting, then ships the goods.

All companies, numbers and documents are fictional demo data.

Step-by-step flow

01
Plant 1100 needs stock open in twin
Plant 1100 has 25 EA and needs 50 more from plant 1000.
Both plants belong to company code 1000, so a transfer posting can move stock without purchasing.
02
Post transfer 301 in MIGO open in twin
MIGO → Transfer posting, movement type 301, from plant 1000 to plant 1100. One posting: plant 1000 600 → 550 EA, plant 1100 25 → 75 EA, and the material document and accounting document are created together.
One step means issue and receipt are posted together; no stock in transit is created. In SAP the receiving plant owns the stock immediately — even though the truck has not left yet. With valuation at plant level each plant has its own material price.
03
Goods are shipped open in twin
The truck carries the goods to plant 1100.
With 301 the system shows the stock in plant 1100 throughout the journey. For long distances, a two-step transfer (303/305) or a stock transport order gives visibility of stock in transit.
04
Transfer complete open in twin
Physical and system stock agree at both plants.
Choose 301 for simple same-company transfers; STOs when you need planning, delivery documents or in-transit tracking.

SAP documents

Drag to pan · Ctrl + scroll to zoom

Stock impact

Step	Plant / SLoc	Stock type	MvT	Change
Post transfer 301 in MIGO	1000 / 0001	Unrestricted use	301	−50 EA
Post transfer 301 in MIGO	1100 / 0001	Unrestricted use	301	+50 EA

Accounting impact

Transfer between two valuation areas in the same company code

Configuration dependent

Post transfer 301 in MIGO

Dr Inventory — plant 1100 (BSX)₹50,000
Cr Inventory — plant 1000 (BSX)₹50,000

Typically valued at the issuing plant's price. If the receiving plant uses standard price and it differs, a price difference posts. Cross-company-code transfers behave differently.

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

Movement type

301TF transfer plant to plantReversal: 302
303TF removal from storage to plant (two-step)
305TF place in storage in plant (two-step)

Moves unrestricted stock between two plants of the same company code in one posting.

Transactions & Fiori apps

MIGO — Goods Movement (Transfer posting)

Transfer Stock – Cross-PlantAvailability depends on release

Differences by SAP version

Cross-plant transfers are typically done through Fiori apps; scope dependent.

Configuration

Valuation level
Typical
Plant-level valuation creates an FI document for cross-plant transfers.
Price control at receiving plant
Configuration dependent
Standard price at the receiver may lead to price differences.

Prerequisites

Material extended to both plants and storage locations
Account determination for both valuation areas

Master data

Material master: Must exist in both plants with accounting views.

Organizational structure

Company code 1000
Plant 1000
Plant 1100

Tables

Table	Description
MATDOC	Two lines: issuing and receiving
MBEW	Valuation per plant

Integration

FIValue transfer between valuation areas.

Common errors

“Material not maintained in receiving plant”
Likely causes: Missing plant extension
Where to look: MM01 / MM50
“Account determination error”
Likely causes: Missing BSX for receiving valuation area
Where to look: OBYC

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
Master data
- Material extended to receiving plant/SLoc?
CHECK 2
Account determination
- BSX maintained for both valuation areas?

Interview questions

One-step vs two-step plant transfer?
301 posts issue and receipt together. 303 removes stock into stock in transit; 305 places it in storage at the receiver. Two-step shows stock in transit.
Does 301 always create an accounting document?
With plant-level valuation, typically yes because value moves between valuation areas. With company-code level valuation there may be no value change — configuration dependent.

Quiz

Q1 · Configuration reasoning

Why does a 301 typically create an accounting document while 311 does not?

Plants are separate valuation areas301 needs a PO311 is not valuated stock

References

SAP SE — SAP Help Portal: Transfer Posting Plant to Plant (source)

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

Version history

Version	Change
1.1.0	SME decision — one posting, one step: both plants' stock changes, the material document and the accounting document now appear together in the 301 posting step.
1.0.0	Initial version.