Storage Location to Storage Location Transfer (Movement Type 311)
Move stock between storage locations inside one plant. Quantity moves; value typically does not.
Educational content. SAP behaviour varies by configuration and release. Spotted something off? Report it.
Digital twin
01Line-side store runs low
SLoc 0002 has 10 EA and needs 40 more from SLoc 0001.
Business scenario
The line-side store (SLoc 0002) needs 40 EA of RM-1000 from the main store (SLoc 0001) in plant 1000.
All companies, numbers and documents are fictional demo data.
Step-by-step flow
- 01
Line-side store runs low open in twin
SLoc 0002 has 10 EA and needs 40 more from SLoc 0001.
Storage locations separate stock physically inside one plant.
- 02
Post transfer 311 open in twin
MIGO → Transfer posting, movement type 311, 0001 → 0002.
Issue and receipt are posted at once.
- 03
Quantity moves open in twin
0001: 600 → 560 EA. 0002: 10 → 50 EA.
Plant stock is unchanged; only the split across storage locations changes.
- 04
No accounting document open in twin
The ledger stays still — value does not move.
Valuation happens at plant (or company code) level, not storage location level. Moving stock inside the valuation area does not change its value.
- 05
Forklift moves the goods open in twin
40 EA are carried to the line-side store.
A two-step transfer (313/315) is an alternative when stock in transfer between storage locations should be visible.
- 06
Transfer complete open in twin
Plant total unchanged at 610 EA; distribution changed.
311 is a quantity-only movement within one plant in the standard case.
SAP documents
Stock impact
| Step | Plant / SLoc | Stock type | MvT | Change |
|---|---|---|---|---|
| Quantity moves | 1000 / 0001 | Unrestricted use | 311 | −40 EA |
| Quantity moves | 1000 / 0002 | Unrestricted use | 311 | +40 EA |
Accounting impact
No accounting impact in the steps shown.
Typical conceptual flow. Actual G/L accounts and posting behaviour depend on material valuation, automatic account determination and system configuration.
Movement type
Relocates stock between storage locations of the same plant.
Transactions & Fiori apps
- MIGO — Goods Movement (Transfer posting)
- Transfer Stock – In-Plant
Differences by SAP version
MARD quantities are derived from MATDOC via compatibility views.
Configuration
Automatic creation of SLoc data
Configuration dependentAllowed per plant and movement type.
Prerequisites
- Material extended to both storage locations (or automatic creation allowed)
Master data
- Material master
- Storage location views.
Organizational structure
- Plant 1000
- SLoc 0001
- SLoc 0002
Tables
| Table | Description |
|---|---|
| MATDOC | Material document |
| MARD | Storage location stock |
Integration
Common errors
“Material not maintained in storage location”
Likely causes: SLoc view missing; Auto-creation not allowed
Where to look: MMSC · Customizing: automatic creation of storage location data
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
- Is SLoc 0002 maintained for the material?
Interview questions
Does 311 create an accounting document?
Typically no — storage locations sit inside one valuation area, so value does not change. Special cases (e.g. split valuation or stock type changes combined with other effects) should be validated.
Quiz
References
- SAP SE — SAP Help Portal: Transfer Posting Storage Location to Storage Location (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. |