Bins, activity areas and the link to inventory management

A warehouse with 600 high-rack positions does not want 600 hand-typed bin records. This lesson covers how bins are generated, how activity areas and sort sequences turn bins into walkable work, and how EWM stock ties back to the plant and storage location stock that finance and planning see.

Creating bins at scale

A bin is identified by a coordinate of up to 18 characters that must be unique within the warehouse, often aisle-stack-level such as 01-14-3. Bins can be created one at a time (transaction /SCWM/LS01 in most systems), uploaded from a file, or generated from a storage bin structure. The structure uses a template in which each position of the name is numeric, alphabetic or constant, plus start and end values and increments for aisle, stack and level. One structure for storage type 0010 with aisles 01–06, stacks 01–20 and levels 1–5 generates all 600 bins.

Each bin carries more than a name: its storage type and optional section, a bin type (its relative size or real dimensions), a bin access type (which resources may reach it), verification data for scanning, capacity limits (weight, volume, total capacity) and, if used, X/Y/Z coordinates that drive travel-distance calculations. Coordinates are populated reliably only through structure generation or an upload that includes them.

Activity areas and sort sequence

An activity area is a logical group of bins used for a warehouse activity such as picking, putaway or physical inventory. It can cover a whole storage type or a slice of aisles, and it can span several storage types. Activity areas matter more than they look: warehouse order creation rules and queues are determined per activity area, so a wrong assignment sends work to the wrong people. The one activity area every warehouse needs is the one for physical inventory, because physical inventory areas are built on it.

For each activity area and activity you define a sort sequence: the order in which bins are visited. Sorting is written into the bin master, so it must be rerun whenever bins or activity areas change. A classic test finding is a pick list that zig-zags across the building because bins were added after the last sort run.

Where EWM stock meets inventory management

EWM does not keep the plant and storage location on each quant. Instead it uses availability groups. Customizing maps each combination of plant, storage location and warehouse number to an availability group, and the availability group plus the inventory-management stock category (unrestricted, quality inspection, blocked) gives the EWM stock type. Read the other way round: every EWM stock type points to one plant and storage location in inventory management.

The usual design uses two storage locations per warehouse. Received on dock (ROD) holds goods that have arrived but are not yet in their final bins; available for sale (AFS) holds goods that are put away. When putaway completes, EWM posts a change from ROD to AFS. Contoso uses storage location 171R for ROD and 171A for AFS. That is why a sales order sees stock as available in 171A only after the pallet is in its bin, not while it waits at the door.

EWM also records two business partners on all stock: the owner and the party entitled to dispose. Normally both represent plant 1710. For supplier consignment the supplier is the owner and the plant is entitled to dispose. If the business partner for the plant is missing or wrong, documents fail in ways that look like process errors, so it belongs on the master data checklist.