303305MMMIGOMB5Tintermediate

Two-Step Plant-to-Plant Transfer: Removal (303) and Placement (305)

A plant transfer in two postings: 303 removes the stock from the issuing plant into stock in transfer of the receiving plant, and 305 places it into the receiving storage location when it physically arrives. Compare with the one-step 301 and with a stock transport order.

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

Docsnone yet

Demo data

01One step or two?

The goods will be on the road for a day. How should the transfer be posted?

Business scenario

Plant 1000 sends 100 EA of RM-1000 to plant 1100 (same company code) by its own truck. The trip takes a day, so the plants want the stock visible as 'on the way'.

All companies, numbers and documents are fictional demo data.

Step-by-step flow

01
One step or two? open in twin
The goods will be on the road for a day. How should the transfer be posted?
With two steps, the system matches the physical situation while the goods travel.
02
Stock arrives before the truck open in twin
301 books the stock into plant 1100 at once. For a day the system shows stock there that nobody can find.
For longer journeys the receiving plant would be planning with stock that is not there yet.
03
Removal from plant 1000 (303) open in twin
303: plant 1000 500 → 400 EA; stock in transfer of plant 1100 +100. Value moves to plant 1100.
Stock in transfer is held at plant level for the receiving plant, with no storage location yet.
04
On the road open in twin
The truck drives to plant 1100. The stock is visible as 'in transfer' (MB5T / stock overview).
Stock in transfer is not available for consumption in either plant.
05
Placement in plant 1100 (305) open in twin
305: stock in transfer −100; plant 1100 / 0001 50 → 150 EA. No accounting document.
The value already moved at 303, so 305 changes only location and availability.
06
Transfer complete open in twin
303 → transport → 305. The journey was visible the whole time.
Use an STO instead when you need delivery documents, shipping and planning integration.

SAP documents

Drag to pan · Ctrl + scroll to zoom

Stock impact

Step	Plant / SLoc	Stock type	MvT	Change
Removal from plant 1000 (303)	1000 / 0001	Unrestricted use	303	−100 EA
Removal from plant 1000 (303)	1100	Stock in transfer (plant)	303	+100 EA
Placement in plant 1100 (305)	1100	Stock in transfer (plant)	305	−100 EA
Placement in plant 1100 (305)	1100 / 0001	Unrestricted use	305	+100 EA

Accounting impact

Removal for a two-step plant transfer

Typical

Removal from plant 1000 (303)

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

The plants are separate valuation areas, so the value moves from plant 1000's inventory to plant 1100's stock in transfer at removal. With different prices in the two plants, a difference would arise here — configuration and price control dependent.

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

Movement type

303Removal plant to plant (two-step)Reversal: 304
305Placement in storage plant to plantReversal: 306

Moves stock between plants of one company code in two postings so the stock is visible while it travels.

Transactions & Fiori apps

MIGO — Transfer posting
MB5T — Stock in transit / in transfer
MMBE — Stock overview

Transfer Stock — Cross-PlantAvailability depends on release and scope

Differences by SAP version

MB1B/MIGO for 303/305; MB5T for stock in transfer.

Configuration

Valuation level
Configuration dependent
With valuation at plant level the plants are separate valuation areas, so 303 posts a value transfer.

Prerequisites

Material extended to both plants
Receiving storage location

Master data

Material master in both plants: Valuation price in each plant.

Organizational structure

Company code 1000
Plants 1000 and 1100

Tables

Table	Description
MARC	Stock in transfer is held at plant level
MATDOC	303 and 305

Integration

FIValue moves between valuation areas at 303.

Common errors

“Stock 'missing' between plants”
Likely causes: 303 posted, 305 not yet posted
Where to look: MB5T · Stock overview of the receiving plant

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
In transfer
- Was 305 posted?
- Check MB5T

Interview questions

Compare 301, 303/305 and an STO.
301 transfers plant to plant in one posting. 303 removes into stock in transfer of the receiving plant and 305 places it, so the journey is visible. An STO adds a purchase-order document, delivery, shipping and MRP integration, with stock in transit (641/101).

Quiz

Q1 · Identify the movement type

Which movement type places stock in transfer into the receiving storage location?

305303301

Q2 · Identify the accounting impact

Which posting carries the value transfer between plants?

303305Both, half each

References

SAP SE — SAP Help Portal: Stock Transfer Between Plants (source)
SAP SE — SAP Help Portal: Two-Step Transfer Posting (source)

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

Version history

Version	Change
1.0.0	Initial version.