Setup Step 7 — Create Storage Locations

MANDATORY Layer 2 · Logistics · owned by MM ⏱️ ~10 min OX09

🎯 Why this setting exists

A storage location is a sub-division inside a plant — the physical spot where stock actually sits: a yard, a shelf, a cold store, a returns cage. Stock cannot exist in SAP without one, so it is entered on almost every goods movement. Crucially, a storage location holds quantity only — value lives at the plant level. That means moving stock between two storage locations of the same plant changes where the goods are but creates no FI document: the company's balance sheet is untouched because nothing left the plant.

💡 Easy example

Inside the Karachi factory (PK01), the building is one plant — but the materials are not piled in a single heap. RAWM is the raw-material yard where incoming iron ore waits, WIPS is the work-in-progress floor where half-finished billets sit, and FNGD is the finished-goods store where ready bars wait to ship.

They are different shelves in the same building. Carting a billet from the WIP floor to the finished store (movement type 311) moves it between storage locations — the factory still owns it, its value never changed, so Finance sees nothing.

🔗 How this connects to everything else

A storage location only makes sense once its plant exists, and once it does it shows up on nearly every stock transaction. Here's the web around it.

⬆️ Depends on (must exist first)

Step 3 — Plants: a storage location is created under a plant; the plant must exist before you can add locations to it.

⬇️ Enables (what this unlocks)

Goods receipt into a specific location — stock now has a place to land.
Stock transfers between locations (Scenario 3, movement type 311).
Stock-by-location reporting — table MARD stores quantity per plant + storage location.

🧩 Who owns it & why MM cares

MM Pure MM. Storage locations are the sub-divisions inside a plant where stock physically sits, and they are entered on almost every goods movement — receipt, issue, transfer. You configure and reference them constantly.

🔮 Links to other modules (now & later)

WM / EWM: a warehouse is set up under a storage location. If you later turn on warehouse management, it attaches here — the storage location becomes the doorway into bin-level control.

🔧 Configuration — fields & steps

OX09 · SPRO → Enterprise Structure → Definition → Materials Management → Maintain Storage Location

Action sequence

Run OX09
Enter Plant PK01 → Continue
Click New Entries and create the SLs (see table below)
Save
Repeat for plants PK02, PK03, AE01

Storage locations to create per plant

Plant	SLs to create	Why these
PK01 Karachi Factory	VPK1 General, RAWM Raw mat, WIPS WIP, FNGD Finished, QHLD Quality hold, RTRN Returns, BLKD Blocked	Full manufacturing — needs all stock types
PK02 Lahore Factory	Same 7 SLs as PK01	Same — second manufacturing site
PK03 Karachi DC	VPK1, FNGD, RTRN	DC — only handles finished + returns, no raw
AE01 Dubai DC	VPK1, FNGD, EXPT	DC + export staging area for international

💡 Tip: same SL code in different plants is fine

SL RM01 in Plant PK01 is INDEPENDENT from RM01 in Plant PK02. Same code, different records. They share no relationship. This is by design.

🚨 Issues & fixes

⚠️ Common gotcha — "no FI document" is correct, not a bug

Beginners often expect a transfer between two storage locations of the same plant to post an accounting document. It does not — and that's correct. Storage locations carry quantity only; value lives at the plant. A same-plant transfer (movement type 311) just relocates stock, so Finance sees nothing. You only get an FI document when stock crosses a plant (and therefore a valuation area) boundary.

✅ Verification

Run SE16N → table T001L → ~20+ storage-location rows total across all plants

✅ Step 7 complete — storage locations created for all plants

← Previous

Step 6: Activate Valuation Grouping Code

Step 8: Create Purchasing Organizations