JinJin48

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

July 15, 2026 · 12 min read

SAP FSM Generic Tool

Generic Tool is FSM’s master record for a non-serialized tool type — a torque wrench, a ladder, a set of hand tools — tracked by category and quantity rather than by an individual serial number. It is defined against an existing Item record (Item Type = Tool) and can, when a specific physical unit needs to be traced individually, be specialized further into one or more Serialized Tool records; a Generic Tool with no serialized instances is simply tracked as pooled stock across Warehouse and Van Stock. Generic Tool is the first of four objects — Generic Tool, Serialized Tool (FSM-A05-03), Warehouse (FSM-A05-04), and Van Stock (FSM-A05-05) — that this series now covers in the Material & Tool Management domain (Phase 4, Zone D), following Item (FSM-A05-01), the material/spare-part master already established earlier in this phase that every Generic Tool record depends on. This article maps every field FSM consultants configure on a Generic Tool record, and how those fields connect Item, Serialized Tool, Warehouse, and Van Stock around it.

Part 1: Generic Tool — Core Concepts (All Modules)#

1.1 What Is Generic Tool?#

A Generic Tool represents a single, named tool type — not a specific physical object. It exists only as a specialization of an Item record already typed as Tool, and it means nothing about location or identity on its own: quantity and location are tracked separately through Warehouse and Van Stock, and individual traceability (serial number, current holder) is added only if and when a Serialized Tool record is created against it.

1.2 Generic Tool Configuration Scenarios#

Whether a Generic Tool is left as pooled, quantity-tracked stock or specialized into individual Serialized Tool instances is a configuration decision, not a fixed property of the tool type — getting it wrong either creates unnecessary serial-tracking overhead for a commodity hand tool, or leaves a high-value, calibration-sensitive tool with no individual traceability at all.

Design principle: The Category field on a Generic Tool is descriptive, not a strict, system-enforced type list — it is the presence or absence of a linked Serialized Tool record, not the Category text, that determines whether a given tool type is tracked individually or as pooled stock.

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→FSM sync; tenant-level catalog; shown
   │                                                            here as the representative Item/Warehouse/Van
   │                                                            Stock example elsewhere in this diagram)
   ├── Warehouse WH-001 — Tokyo Warehouse, Plant 1000          (S/4HANA→FSM sync; tenant-level catalog)
   │
   └── Generic Tool GT-001 — Torque Wrench (tool type record)
          ── references ──▶ Item (reference, Item Type = Tool — a distinct Tool-type Item record from
                              ITM-001 above, which illustrates a Part-type Item; not itself drawn as a separate
                              node in this shared Zone D crop)

Serialized Tool ST-001 — SN TW-2024-001 (individual physical instance; FSM-A05-03):
   Serialized Tool ST-001 ── instance of ──▶ Generic Tool GT-001
   Serialized Tool ST-001 ── services ──▶ Equipment EQ-001 (Zone B; cross-zone chip)

Van Stock VS-P001 — P-001's mobile inventory (FSM-A05-05):
   Van Stock VS-P001 ── stocks ──▶ Item ITM-001 (illustrative; a Van Stock line item can reference any Item,
   including a Part such as ITM-001, a Consumable, or the Tool-type Item a Generic Tool is defined against)
   Van Stock VS-P001 ── assigned to ──▶ Person/Technician P-001 (Zone C; cross-zone chip)

Design principle: Generic Tool is a specialization of Item, not a sibling master alongside it — it cannot exist without a referenced Item, but it adds no location or quantity fields of its own beyond what Item, Warehouse, and Van Stock already track. Serialized Tool is, in turn, an instance of Generic Tool, never of Item directly; the “instance of” step happens exactly once, at the Generic Tool layer.

1.4 Integration with Other Master Data Objects#

Generic Tool does not stand alone. Every field on it exists to answer one question: what type of tool is this, and does it need individual traceability or not?

Part 2: FSM-Specific Field Details#

2.0 Scope of FSM Ownership#

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

2.1 Core Identification#

These four fields establish what a Generic Tool record actually is, before any quantity or location detail is layered on top.

2.2 Quantity & Stock Tracking#

These fields apply specifically to a Generic Tool left as pooled, non-serialized stock (Requires Serialization = No, see 2.1) — once a tool type is fully serialized, quantity is tracked per Serialized Tool instance instead.

2.3 Location & Assignment#

Generic Tool carries no location field of its own — these are the linkage facts consultants check when tracing where a pooled tool type’s stock actually sits and how it moves.

Prerequisite: A Generic Tool record cannot be created until its referenced Item (FSM-A05-01) already exists and is typed Tool — Generic Tool stores no properties beyond that reference, the Requires Serialization decision, and the pooled quantity/location facts layered on top of the Item’s own stock.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction