JinJin48

SAP Consultant | BTP · S/4HANA · US Global Rollout

July 15, 2026 · 11 min read

SAP FSM Van Stock

Van Stock is FSM’s master record for a technician’s mobile, vehicle-based inventory — the quantity of a given Item currently carried in a specific Person/Technician’s van, replenished from a designated Warehouse rather than picked ad hoc from wherever stock happens to be available. Unlike Warehouse (FSM-A05-04) and Item (FSM-A05-01), both synced in from S/4HANA, Van Stock is FSM-native: it has no S/4HANA equivalent, even though both of its prerequisite objects — Warehouse and Person/Technician (FSM-A04-04) — are themselves synced from S/4HANA. Van Stock is the fifth and final object — Item (FSM-A05-01), Generic Tool (FSM-A05-02), Serialized Tool (FSM-A05-03), Warehouse (FSM-A05-04), and Van Stock — that this series covers in the Material & Tool Management domain (Phase 4, Zone D), and its landscape ID convention (VS-P001) reflects its direct dependency on a specific technician (P-001): a Van Stock record answers “what does this technician currently have in their van, and where was it replenished from,” the direct mobile counterpart to Warehouse’s fixed physical location. This article maps every field FSM consultants see on a Van Stock record, and how those fields connect it to Warehouse, Person/Technician, and Item. With Van Stock complete, Zone D (Material & Tool Management) closes out; the series continues next into Zone E (Partner Management) — Partner Invitation, Partner Registration, Crowd Partner, and Partner Technician (FSM-A06-01 through FSM-A06-04).

Part 1: Van Stock — Core Concepts (All Modules)#

1.1 What Is Van Stock?#

A Van Stock represents mobile inventory — physical stock that has left a fixed stocking location and now travels with a specific technician — rather than a location or a tool in its own right. Where Warehouse (FSM-A05-04) answers “where does inventory sit before it is issued,” Van Stock answers “what has already been issued to this technician, and how much of it do they currently have.”

1.2 Van Stock Usage Patterns#

Van Stock carries no dedicated “type” field of its own — the same five fields (Van Stock ID, Person ID, Warehouse ID, Item ID, Quantity) apply regardless of how a given technician’s van is stocked and replenished operationally. Even so, consultants generally see the same handful of usage patterns repeat across implementations, and getting the pattern clear up front shapes how a Regional Warehouse’s replenishment cadence should be designed.

Design principle: There is no dedicated Van Stock Type field on the record — how a given Van Stock is replenished and tracked (fixed par-level, on-demand, consignment, or cross-crew shared) is an operational/business-process decision, not a value stored on the record itself.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example (Zone D · Material & Tool Management — tenant-level; FSM has no Company Code / Plant scoping above these objects)

Client (FSM Tenant)
   │
   ├── Item ITM-001 — Air Filter, Item Type = Part            (S/4HANA-synced; FSM-A05-01)
   │
   ├── Generic Tool GT-001 — Torque Wrench (tool type record; FSM-A05-02)
   │      └── Serialized Tool ST-001 — SN TW-2024-001 (individual instance; FSM-A05-03)
   │
   └── Warehouse WH-001 — Tokyo Warehouse, Plant 1000, Storage Location 0001 (S/4HANA-synced; FSM-A05-04)
          │
          └── Van Stock VS-P001 — P-001's mobile inventory (this article; FSM-native, no S/4HANA sync)
                 Van Stock VS-P001 ── stocks ──▶ Item ITM-001 (a Van Stock line item can reference any
                 Item, including a Tool-type Item a Generic Tool is defined against)
                 Van Stock VS-P001 ── assigned to ──▶ Person/Technician P-001 (Zone C; cross-zone chip;
                 Person/Technician is itself S/4HANA-synced — see 1.4)

Serialized Tool ST-001 ── current location (reference, not drawn as a landscape line) ──▶
   Warehouse WH-001, or Van Stock VS-P001 (this article) if currently checked out to the technician

Design principle: Van Stock is the only Zone D object with two prerequisite objects rather than one or zero — it requires both an existing Warehouse (the replenishment source) and an existing Person/Technician (the assignment target) before it can be created, in contrast to Generic Tool (prerequisite: Item), Serialized Tool (prerequisite: Generic Tool), or Warehouse (no FSM-side prerequisite — sourced from S/4HANA). Van Stock is also the only Material & Tool Management object that depends on two S/4HANA-synced upstream masters (Warehouse and Person/Technician) while remaining itself entirely FSM-native — the landscape marks Van Stock with no dashed border, unlike either of the objects it is built on top of.

1.4 Integration with Other Master Data Objects#

Van Stock does not stand alone. Every field on it exists to answer one question: which technician has how much of what, and where was it replenished from?

Part 2: FSM-Specific Field Details#

2.0 Scope of FSM Ownership#

Legend: ◎ = Owner / Critical, ○ = Direct involvement

2.1 Core Identification#

This one field establishes which technician’s mobile inventory record this is, before any assignment or stock detail is layered on top.

2.2 Technician & Warehouse Assignment#

These two fields exist because Van Stock has no meaning in isolation — it only becomes usable once tied to the technician it belongs to and the Warehouse it is replenished from.

2.3 Stock Content & Quantity#

Once a Van Stock record is tied to a technician and a Warehouse, these two fields carry the actual line-item detail — what is in the van, and how much of it.

Prerequisite: A Van Stock record requires both an existing Warehouse (FSM-A05-04) and an existing Person/Technician (FSM-A04-04) before it can be created — the only Material & Tool Management object in this series with two prerequisite objects rather than one (Generic Tool: Item; Serialized Tool: Generic Tool) or none on the FSM side (Item, Warehouse — both sourced from S/4HANA).

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction