JinJin48

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

July 15, 2026 · 9 min read

SAP FSM Skill

Skill is FSM’s master record for an individual technician competency or qualification — a welding certification, an electrical-work proficiency level, a product installation qualification, a spoken language. It is configured independently at the tenant level, then assigned to Person/Technician records (FSM-A04-04) to describe what each technician is actually qualified to do, and referenced by Skill Requirement (FSM-A04-07) records to state what a piece of Equipment or a Service Call demands. Skill is the first object in the Technician Management domain (Phase 3, Zone C) that this article opens, alongside Work Time Pattern, Region, Person/Technician, Crew, Absence, and Skill Requirement. This article maps every field FSM consultants configure on a Skill record, and how those fields connect to the Person/Technician and Skill Requirement masters around it.

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

1.1 What Is Skill?#

A Skill represents a single, named competency or qualification that can be held by a technician and demanded by a job. It is a deliberately small, flat master — it carries no organizational hierarchy of its own, and it means nothing in isolation: its entire purpose is to be assigned to technicians on one side and referenced by requirements on the other.

1.2 Skill Categories#

Skill Category is the one classification field carried directly on the Skill record, and it shapes how strictly a mismatch should be treated during dispatch. Getting the category wrong doesn’t just mis-file a Skill — it can quietly change how seriously an unmatched Skill Requirement is escalated.

Design principle: Skill Category is a classification field for filtering and reporting — it does not imply that one category outranks another, and Skill Requirement can reference a Skill from any category equally.

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)
          ── assigned to ──▶ Skill SK-ELEC — Electrical Work L3
          ── assigned to ──▶ Work Time Pattern WTP-STD
          ── assigned to ──▶ Region RG-KAN

Crew CR-TOK-A — Tokyo Team A (reference — groups technicians, does not own Person):
   Crew CR-TOK-A ── led by ──▶ Person P-001

Absence ABS-P001 — Annual leave (reference — blocks capacity on the Person it targets):
   Absence ABS-P001 ── blocks ──▶ Person P-001

Skill Requirement SR-EQ001 — Requires a Skill on an Equipment (cross-object link; not nested under either side):
   Skill Requirement SR-EQ001 ── requires ──▶ Skill SK-ELEC
   Skill Requirement SR-EQ001 ── applies to ──▶ Equipment EQ-001 (Zone B)

Design principle: Skill, Work Time Pattern, and Region are independent tenant-level masters configured before Person/Technician — Person is assigned to them via reference, not the reverse, and none of the three own Person. Crew, Absence, and Skill Requirement are drawn as reference objects with an arrow back to the Person or Skill they target; none of them nest underneath the object they reference.

1.4 Integration with Other Master Data Objects#

Skill does not stand alone. Every field on it exists so that a technician’s qualifications and a job’s requirements can be compared to each other.

Part 2: FSM-Specific Field Details#

2.0 Scope of FSM Ownership#

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

2.1 Core Identification & Categorization#

These three fields are the whole identity of a Skill record — FSM keeps this master deliberately lean, with no descriptive or hierarchy fields beyond them.

2.2 Validity Period#

Skill is time-bound rather than status-bound — there is no separate Active/Inactive flag; validity is expressed entirely through this date range.

2.3 Assignment & Requirement Linkage#

Skill has no meaning until it is picked up on one of two sides — held by a technician, or demanded by a requirement. These are the linkage facts consultants check most often when troubleshooting a dispatch-matching gap.

Prerequisite: A Skill Requirement referencing this Skill returns no eligible technician in Assisted Scheduling until at least one Person/Technician (FSM-A04-04) is actually assigned this Skill — creating the Skill record alone does not make any job dispatchable against it.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction

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