JinJin48

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

July 15, 2026 · 12 min read

SAP FSM Technician

Person/Technician is FSM’s master record for an individual field service resource — a dispatchable technician with contact details, a Plannable flag, and references to the Skill, Work Time Pattern, and Region records that describe what that technician can do, when they work, and where they cover. It is the central object of the Technician Management domain (Phase 3, Zone C): Skill (FSM-A04-01), Work Time Pattern (FSM-A04-02), and Region (FSM-A04-03) are all configured independently first and then assigned to Person/Technician, while Crew (FSM-A04-05) and Absence (FSM-A04-06) both exist only in reference to a Person/Technician record. Person/Technician is listed as a required master alongside Business Partner, Skill, and Region — an FSM tenant with no Plannable technician record has nothing for Assisted Scheduling, Route Optimization, or the Planning Board to dispatch. This article maps every field FSM consultants configure on a Person/Technician record, and how those fields connect to the Skill, Work Time Pattern, Region, Crew, and Absence masters around it.

Part 1: Person/Technician — Core Concepts (All Modules)#

1.1 What Is Person/Technician?#

Person/Technician represents a single, individually identifiable field service resource — the record a dispatcher assigns to a Service Call and the record a technician logs into the mobile app with. Unlike Skill, Work Time Pattern, or Region, which are small, self-contained catalogs, Person/Technician is deliberately the richest record in Zone C, since it is the one place where competency (Skill), availability (Work Time Pattern), and geography (Region) all come together for a single dispatchable resource.

1.2 Technician Types#

Person/Technician carries no single coded classification field of its own for how a technician is sourced — Person ID, Person Name, and the rest of the fields covered in Part 2 are identical regardless of employment relationship. What varies in practice is how the technician came to be onboarded, and — for one of the three patterns below — whether the resource is even modeled as a Person/Technician record at all.

Design principle: Internal and External technicians share one record structure and one set of Zone C assignments (Skill, Work Time Pattern, Region). Partner-sourced technicians are the exception — they are onboarded through the Partner Portal into a dedicated object rather than into Person/Technician, because they sit outside the organization’s own workforce data.

1.3 Organizational Levels and Data Hierarchy#

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

Client (FSM Tenant)
   │
   ├── Skill SK-ELEC — Electrical Work L3                 (configured independently; tenant-level catalog)
   ├── Work Time Pattern WTP-STD — Mon–Fri 09:00–18:00     (configured independently; tenant-level catalog)
   ├── Region RG-KAN — Kanto (Asia/Tokyo)                   (configured independently; tenant-level catalog)
   │
   └── Person / Technician P-001 — Hanako Yamada (Plannable = Yes)
          ── assigned to ──▶ Skill SK-ELEC — Electrical Work L3            (N:M — a technician can hold more than one Skill)
          ── assigned to ──▶ Work Time Pattern WTP-STD                     (N:1 — many technicians may share one Pattern; exactly one active per technician)
          ── assigned to ──▶ Region RG-KAN — Kanto (Asia/Tokyo)            (N:M — a technician may cover more than one Region)
          │
          └── Absence ABS-P001 — Annual leave, 2024-08-10–2024-08-16      (1:N — true containment; an Absence record has no meaning without its Person)

Person / Technician P-001 ── leads ──▶ Crew CR-TOK-A — Tokyo Team A
   (Crew aggregates a lead plus multiple member technicians; it is a reference relationship, not single-owner containment)

Van Stock (Phase 4, Material & Tool Management, drawing from Warehouse WH-001) ── assigned to ──▶ Person / Technician P-001
   (forward cross-zone reference — Person/Technician is a prerequisite for Van Stock, not the reverse)

Skill Requirement SR-EQ001 — Requires a Skill on an Equipment (cross-zone; attaches to Equipment, NOT Person/Technician directly):
   Skill Requirement SR-EQ001 ── requires ──▶ Skill SK-ELEC
   Skill Requirement SR-EQ001 ── applies to ──▶ Equipment EQ-001 (Zone B)
   (Matched against Person/Technician P-001's own assigned Skills by Assisted Scheduling at dispatch time — a run-time comparison, not a stored field-level link)

Design principle: Person/Technician is Zone C’s hub — Skill, Work Time Pattern, and Region are independent tenant-level masters configured first, then assigned to Person/Technician rather than the reverse. Absence is true containment (an Absence record belongs to exactly one Person), while Crew is a reference relationship (a Crew aggregates a lead plus multiple member technicians, so no single Person record owns it outright). Skill Requirement attaches to Equipment, not to Person/Technician — Assisted Scheduling performs the Skill match at run time rather than through any stored field on either record. Unlike Equipment, Person/Technician carries no direct reference to Business Partner in the FSM data model.

1.4 Integration with Other Master Data Objects#

Person/Technician does not stand alone — it is the record every other Technician Management object either feeds into or reads back out of, and the one record Material & Tool Management (Van Stock) reaches forward into from the next Phase.

Part 2: FSM-Specific Field Details#

2.0 Scope of FSM Ownership#

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

2.1 Core Identification#

These two fields are what every other Zone C object — Skill assignment, Region assignment, Work Time Pattern assignment, Crew membership, Absence, and Van Stock — ultimately references back to.

2.2 Contact Details#

Both fields exist to connect the technician to the systems and people that need to reach them — the FSM mobile app on one side, and dispatchers and customers on the other.

2.3 Planning & Dispatch Configuration#

This single Boolean field is what turns a technician record from an administrative entry into an actual dispatchable resource.

2.4 Skill Assignment#

This one field is what lets Assisted Scheduling treat a technician as qualified — or not — for a given piece of work.

2.5 Scheduling Assignment#

Together with Skills, these two references are what actually make a technician plannable in practice — Skills say what the technician can do, and this section says where and when.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction

Zone crop source: 04-fsm-a01-master-landscape.png (mtime: 2026-07-15 11:04)