JinJin48

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

July 14, 2026 · 12 min read

SAP FSM Equipment

Equipment is FSM’s master record for a serviceable asset — a piece of installed machinery, an HVAC unit, a pump, or any other physical object at a customer site that requires ongoing field service. It captures identification, Business Partner and location assignment, hierarchy, and lifecycle status, and it anchors two closely related objects covered in their own articles: Equipment Hierarchy (parent-child structure) and Service History (past service calls). This article maps every field FSM consultants configure and maintain when creating an Equipment record, and how those fields connect Equipment to the Business Partner, Address, Skill Requirement, and Serialized Tool masters around it.

Part 1: Equipment — Core Concepts (All Modules)#

1.1 What Is Equipment?#

Equipment represents an individual serviceable asset — a physical unit installed at a customer’s premises that a technician can be dispatched to inspect, repair, or maintain. It is the anchor object of FSM’s Equipment Management domain: every Service Call, Service History entry, and Skill Requirement traces back to a specific Equipment record.

1.2 Equipment Status and Lifecycle#

Equipment status is the single field that determines whether a technician can be dispatched against the asset at all. Getting a status wrong either blocks legitimate service work or lets dispatch proceed against equipment that should already be retired.

Design principle: Decommissioning Equipment should never delete the record — Service History and warranty audit trails depend on the Equipment master surviving retirement.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example (Zone B · Equipment Management — tenant-level; FSM has no Company Code / Plant scoping above Equipment)

Client (FSM Tenant)
   │
   ├── Equipment EQ-001 — AC Unit A (Serial SN-2024-001)
   │      ↗ references Business Partner BP-001 — ABC Corp (Zone A)
   │      ↗ references Address AD-A — 1-1 Marunouchi, Tokyo (Zone A)
   │      │
   │      └── Equipment Hierarchy EQ-001-01 — Sub-unit of EQ-001
   │
   ├── Equipment EQ-002 — Pump B (Serial SN-2024-002)
   │      ↗ references Business Partner BP-002 — XYZ Ltd (Zone A)
   │      ↗ references Address AD-B — 2-2 Umeda, Osaka (Zone A)
   │      │
   │      └── Equipment Hierarchy EQ-002-01 — Sub-unit of EQ-002
   │
   └── Equipment EQ-003 — Chiller C (Serial SN-2024-003)
          ↗ references Business Partner BP-002 — XYZ Ltd (Zone A)
          │
          └── Equipment Hierarchy EQ-003-01 — Sub-unit of EQ-003

Service History (reference log — points back to its Equipment, not nested under it):
   Service History SH-001 ── refers to ──▶ Equipment EQ-001
   Service History SH-002 ── refers to ──▶ Equipment EQ-002

Design principle: Equipment is a tenant-level (client-level) master in FSM — there is no Company Code / Plant hierarchy above it, unlike ECC-style Equipment (EQUI) which sits under a Maintenance Plant. Business Partner and Address are referenced, not owned, by Equipment; Equipment Hierarchy is true parent-child containment; Service History is a reference log, not a child node.

1.4 Integration with Other Master Data Objects#

Equipment does not stand alone. It is the reference point that a customer’s Business Partner and Address, a technician’s required Skill, and a service tool’s usage log all connect back to.

Part 2: FSM-Specific Field Details#

2.0 Scope of FSM Ownership#

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

2.1 Core Identification & Classification#

These fields establish what the Equipment record actually is, and — when replicated from S/4HANA — how it maps back to the source system’s Equipment master.

2.2 Status & Lifecycle#

Status governs dispatch eligibility (see 1.2) and must be maintained accurately as equipment moves through its operational lifecycle.

2.3 Business Partner & Location Assignment#

Equipment must resolve to exactly one owning Business Partner and one installation Address — both are prerequisites synchronized (per the Master Data Setup Flow) before Equipment can be created.

2.4 Hierarchy & Service History Linkage#

These are the fields carried on the Equipment record itself that establish its position in a multi-level installation and surface its service track record — the detailed field sets of Equipment Hierarchy and Service History as standalone objects are covered in their own articles.

2.5 Skill Requirements & Self-Service#

These fields connect Equipment to dispatch-time technician matching and to the customer-facing self-service check-in experience.

Prerequisite: Skill Requirement matching only functions when the corresponding Skill (FSM-A04-01) is also assigned to at least one Person/Technician (FSM-A04-04) — otherwise Assisted Scheduling returns no eligible technician for any Service Call raised against this Equipment.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction